Precision, Accuracy etc are a matter of reference. You need to specify it to have a frame of reference. My biggest beef with the software/meter for logging is the BS timebase used not the 'accuracy' of the meter. The timebase can be post edited in a spreadsheet with a little maths but it shouldn't have to be.
Against my recently calibrated Keysight 34461A snd I haven't looked at recalibrating it against this and my in cal 34401A but it is well within the combined error margin of both.
Rough setup and plenty of possibilities for stray noise to play with the BT but looking for dropped results and NOPE.
30 minutes of logging with a rough setup as shown and lets look at the 'false recordings' and other random unsubstantiated claims of the Troll boy in chief - NOPE
Thanks for the test. Real experiment and real data is only important thing.
If you're willing to make another one let me suggest parameters that would be more relevant to dispense with all of the fluff once and for all.
Logging time should be at least 24h. Use case would be leaving meter to monitor battery state, or monitor charge/discharge cycle.
I see you have very nice SDG 2000X. Any AWG should do, actually.
Siggen should be set to create low frequency sine wave. Something like 20 second cycle ( 50 mHz ). Make it nice 4.8 V P-P.
Set meter to DC, 5V range manual.
Make a logging to a SD card and BT.
For 24 hours. Why 24 hours? Because that is what logging is for. 30 minutes is not proof.
Those who reported problems said meter can sometimes log for hours at a time without problems.
Why sine wave? Because of its nature, it is easy to detect any discontinuities, missed points, nonlinearities...
Post original data file here.
Can anybody make this 2 tests? To experimentally prove one or the other.
If it's working OK, great news. If there are problems, it will be quality data for manufacturer to fix the problem.
Regards,