As I mentioned in another thread, this is most probably coming from the unrealistic and unfulfilled expectation (=frustration) of a "close to perfection" product that had an unparalleled transparent development process. It is a new product and issues like these are bound to happen.
Yes of course. But I saw enough of Daves reviews to be able to imagine what he would have said about the meter.
What I am wondering about, is that the felt majority of posts is about the ohm autoranging speed and other cosmetic deficiencies. Wtf? This is the smallest of the problems the meter has and I don't get why everybody seems so excited about this problem.
I'm more concerned with the real problems of the firmware, like sending broken records via bluetooth, missing to write loglines onto the sd-card, file corruption on the sd-card, sending plain wrong data via bluetooth and using a braindead protocol to send data via bluetooth. One part of the data is decimal coded hex digits, the other part is hex coded hex digits and half of the records are garbled, wasting probably two thirds of the small available bandwidth of bluetooth LE. Wtf?
If you find issues like that, you start wondering, what else the firmware the guys will probably have messed up.
I'm not concerned that not everything on the first batch works as expected. I'm more concerned that someone writes the firmware for the meter who makes design errors like this. Writing data to an file system and transmitting data via a serial port to a bt-dongle is no rocket science. The bluetooth transmission is CRC protected so the meter clearly writes wrong data to the module. I'm too lazy to to solder a logic analyzer to the module connection to verify this. This is Dave's or whoever's homework.
What am I to expect from someone with this track record in the future?
Dave said: "It's ready when it's ready."
I guess he didn't look to closely. He knew about the wrong data via bluetooth. The app tries to filter it out, but fails in quite some cases.