Products > Test Equipment
EEVBlog 121GW Discussion thread
golftango:
for now, i have no need for any logging although i will test in a couple of days after i've tested the other functions just in case a use case comes up. in fact, when i started meteor for the first time i was supremely annoyed that it just started logging automatically and it literally took me 20 minutes to go through every menu item and to realize that to keep it from doing that i had to set the sample size to zero. :)
but when i do install other versions i'll post back here as to your queries.
/guy
JDW:
--- Quote from: golftango on March 08, 2023, 02:48:07 am ---...when i started meteor for the first time i was supremely annoyed that it just started logging automatically and it literally took me 20 minutes to go through every menu item and to realize that to keep it from doing that i had to set the sample size to zero. :)
--- End quote ---
You had to see the "ln" sample size on the meter to zero (which means: 200ms/sample), as opposed to some setting in the Meteor app, correct?
golftango:
i didn't set anything in the meter. the bt was literally the 2nd thing i did after updating the firmware. i'm still going through the manual and i haven't even gotten into the setup module yet. i need to do that now to get the time set--the date was ok.
just went through setup and changed a couple of things. the interval was at '0' which the manual says is 200ms/maximum. i changed this to 6 seconds for now to make calculations easier when i test it.
i connected to the meteor app and set the sample size to 100 but the app didn't seem to honor this cut off and kept counting up. when i set it back to zero it said it had logged 104 items, but by that time the counter had gone up to 170+ or so. very confusing. it was obvious the app didn't honor my 1 every 6 seconds setting, but it didn't seem to be at 200ms either. maybe 400-800ms ??? perhaps you can tell from the timestamps:
# Source: 121GW 0
# Mode: Voltage Low Z
# Start time: 03/07/2023, 21:06:44.586 CST
Timestamp, Elapsed time (s), Value, Units
21:07:37.536, 52.950, 0, V
21:07:38.048, 53.462, 0, V
21:07:39.036, 54.450, 0, V
21:07:39.547, 54.960, 0, V
21:07:40.056, 55.470, 0, V
21:07:40.535, 55.949, 0, V
/guy
J-R:
Has the official ACV calibration procedure been discovered/published? I couldn't find it. I experimented with this and it seems the ACV calibration procedure as I understand it is not correct. If you perform the 10% offset and full-scale calibration at a specific frequency, then the DMM is completely out of whack at other frequencies and I had to restore the previous calibration data. Looking at the Kane555 calibration procedure, it seems possible the frequency calibration needs to be performed 3 times at various frequencies after the ACV calibration, but this is not clear, nor are the frequencies for the 121GW (the Kane 555 lists 60Hz, 10kHz and 100kHz).
JDW:
--- Quote from: golftango on March 08, 2023, 02:56:43 am ---21:07:37.536, 52.950, 0, V
21:07:38.048, 53.462, 0, V
21:07:39.036, 54.450, 0, V
21:07:39.547, 54.960, 0, V
21:07:40.056, 55.470, 0, V
21:07:40.535, 55.949, 0, V
--- End quote ---
Similar timestamps as the Meteor app on my iPhone 7 generates. I assumed the 3 digits at the far right of each time stamp to be milliseconds, so: 1000ms - 536 + 48 = 512ms, 1000ms - 48 + 36 = 988ms, and so on. It's certainly not a stable sampling speed. Maybe that is the only sampling speed the BlueTooth module of the 121GW can send data at? But based on the Meteor app settings, it seems you can store up to 1 million samples.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version