- This topic has 5 replies, 2 voices, and was last updated 7 years, 2 months ago by
.
- Posts
…today. So won’t jump to conclusions.
First impression, hardware side, is positive. Solid box, test leads, case ; professional level.
The App (latest iOS on iPhone 6+) is version 1.06 (215).
Firmware: I noticed the fw version of this device (1445847981) is less than the one posted by somebody else on this forum a few days ago. Is the “automatic” update working on iOS?
Or is there something special to force an update?Bluetooth. All the tests I’ve been conducting today had the MM and iPhone 25 cm (10 inches) apart. But the bluetooth indicator (top of MM app) indicates between ~ -25dB to -60dB… ; and at times, while being used, the Meter view goes back to the scan view (maybe the reason is the low signal, but, again, they’re so close…).
Is that a “normal” behavior?Meter settings displays MAX, 1s , 10s, 1m. A wild guess tells me that’s the logging frequency (?) as it doesn’t seem to be related to the graph (and couldn’t find a doc about this)?
Can you kindly mention what MAX would be, roughly?Graphing
Graphing is the main reason I purchased the MM, mainly for the Burst mode (or Trend as explained below?). However it seems there are two important limitations in Burst mode, please correct me if I’m wrong:– tapping the screen starts the sampling, which lasts about 1 second (for 0.25 second of data, 2 Ch). Does the sampling starts exactly (say within 0.1″) when the “tapping” occurs or is there a delay?
– the sampling represents only 0.25 second of data. At least 3″ would be needed. The Trend mode would be ideal in this case but it seems its max resolution lies around 0.3~0.5 second. Can the Trend mode samples more quickly than that, or could the Burst mode last (e.g.) 3″?
Documentation (Thanks Google)
Is there a place to find an up-to-date documentation, having all the detailed information about the device and the App?Thank you.
Hi Yves,
Is the “automatic” update working on iOS?
Or is there something special to force an update?Automatic update is working in iOS. But manual update is still an option if you want it, you can force that to happen by rebooting the meter and connecting to it in the first 5 seconds (when it is giving long slow flashes).
-25dB to -60dB… ; and at times, while being used, the Meter view goes back to the scan view (maybe the reason is the low signal, but, again, they’re so close…).
Is that a “normal” behavior?Those signal strengths look good, I can usually maintain a connection all the way down to -75dBm. Falling back to scan view if the meter loses connection is normal behavior, but I don’t usually see that happen at -60dBm. Quick test – does the disconnect happen if you leave the meter sitting in DC mode, or only when you switch to AC? This is related to some other user reports for an iOS bugfix in the pipeline.
Can you kindly mention what MAX would be, roughly?
MAX frequency will have no delay between subsequent readings, so the resulting frequency depends on the sampling settings. For example, if your sample settings are 32 samples at 125 Hz, you’ll get a logging frequency of roughly (125/32) = 3.9Hz– tapping the screen starts the sampling, which lasts about 1 second (for 0.25 second of data, 2 Ch). Does the sampling starts exactly (say within 0.1″) when the “tapping” occurs or is there a delay?
Sampling will start as soon as the meter receives the tap notification, which should be between 0.01 and 0.05s (depends on the phone).
– the sampling represents only 0.25 second of data. At least 3″ would be needed. The Trend mode would be ideal in this case but it seems its max resolution lies around 0.3~0.5 second. Can the Trend mode samples more quickly than that, or could the Burst mode last (e.g.) 3″?
Hmm – I’m not sure exactly what you’re trying to measure so I will try to give answers to make both burst and trend work for you: Burst mode captures a complete frame of data from the meter and transfers it to the phone at whatever sample rate was set in the main “meter” screen. So if you set the meter to “256 samples, 125Hz”, that should give you a 2 second frame of data.
Trend mode receives processed samples (not raw buffers) and plots them as they are received. You can make it update faster by adjusting the sampling parameters in the main meter screen – for example changing from 125Hz, 32samples to 125Hz, 16samples should increase the density of points in trend mode.
Also I have a large update to this feature in the works, I hope to release it in the next week or so.
Documentation (Thanks Google)
Most of it is here, but I acknowledge it’s quite out of date since we’ve been continually releasing updates and detailing the changes in the blog.
https://moosh.im/documentation/
But even I search google with “PHRASE site:moosh.im” quite often. We just shot a new product video and will be making some website changes shortly as well.
I hope this helps, please let me know if you have other questions. Best
~JamesThanks James. That’s valuable information.
● Burst graph: Indeed, changing the sampling frequency to the min (125 Hz) and the number of samples to the max (256) gives ~2 seconds of data. Could have probably figured that out myself – but if it’s nowhere in any doc (and not self explained in the app), a number of other beginners may miss that feature as well.
To answer your question, I’m analyzing how A and V are behaving in an electro mechanical system, during ~2-3″. 125 Hz is enough, but if possible 1024 samples would allow in this case 8″ of data, more time to setup → less stress and handing error..
● Code Pretty busy now, but I’d love to look at the code and customize a few things. The git code is 3 month old seemingly. Will it receive the new coming update?
Is the firmware on git as well?My subjective 2 cents:
All in all I’m pretty satisfied with the MM, and the extended burst sampling to 2″ is good news.
The device seems pretty strong. Noticed during hibernation the led flashes every ~2″ (instead of 10) but maybe the doc was not updated. Also had some troubles to wake it up and see it in the app (removed batteries, reset, …, killed the app…). Now it seems the sleep/wake cycle operates flawlessly [could have been the beginner’s mistake!].
I look forward to the upgrade, especially graph side!
Keep up the good work!Thanks
Yves
Thank you Yves,
To answer your question, I’m analyzing how A and V are behaving in an electro mechanical system, during ~2-3″. 125 Hz is enough, but if possible 1024 samples would allow in this case 8″ of data, more time to setup → less stress and handing error..
Very cool. Another product on the horizon that might be of interest to you:
http://www.aeroscope.io/It’s not mine but I’m friends with Jonathan. We’re talking about synchronizing our BLE profiles so we can share apps, but nothing there is finalized yet so no promises.
● Code Pretty busy now, but I’d love to look at the code and customize a few things. The git code is 3 month old seemingly. Will it receive the new coming update?
Is the firmware on git as well?That’s accurate, I’ve been deep in a firmware overhaul and haven’t touched the iOS or Android app for a few months. I have not open sourced the firmware, only the apps themselves.
I’m testing the new firmware right now, the update goes deep. The biggest thing it does is really clean up the BLE interface, so hopefully by the time you get to look at the app source code it will be much simplified.
Anyway, thanks again for the feedback! Let me know how else I can help. Best
~James
