@Dave: at the risk of sounding like an ungrateful asshole, while the beeper on/off option is fantastic (nice and quite now! ), it renders the continuity beeper also silent, which I would argue either should have it's own configuration option, or at least be on all the time, even if the beeper for functions/buttons is turned off.
That being said, I don't know that I would classify this as an "issue". A big thanks to UEi for getting issues in the FW addressed quickly!
Bluetooth and VA mode is still completely broken, even if you filter the invalid records.
It's also broken in the android app. It displays the same wrong readings.
The 391.2 mVA reading is the correct one.
I personally think the beeper is necessary in the following circumstances:
- Continuity (which even uses the sound symbol!)
- Diode test
- When you've been an idiot and left a probe in the A jack when the meter is in voltage mode (assuming it's using sensing jacks - can't remember if this is the case)
- Over-load warning on ranges where an overload could cause damage
Other than those, I'd normally want the beeper off, so I'd agree with everyone asking for a middle option (preferably as a third setting in addition to the current two)
a) Nothing was "removed in editing". The entire original 23 hour video is still being processed by youtube and will eventually be available online. It seems that only the final 2 hours is currently available.
b) By the "edited video" I presume you mean the one "How to do Lifecycle Testing". I simply extracted some content from the stream to create a new video were I talked about general range switch testing as I thought it might be interesting to people as separate video.
c) There is a uCurrent x100 amplifier used in the jig across the switch contacts, that is not shown in the equations.
The 24 hour video was no longer listed when I checked, so yes I was referring to your how-to video.Quote.. r=v/2300 and R=2740/((1/r)-1) . The second note stated the first column was V. So for v=128, R=2740/((2300/128)-1) = 152.5.
I assume it's not as simple as it being off by 100X or 0.152 ohms, seems way too low but maybe. Looking at V=1272, R = 1.516 in this case and I think it was much higher. Strange that the basics are not clear or just coded.
Maybe someone can explain to me what the problem is:
2 different function generators tested, JDS6600 and FeelTech FY6600. Identical settings, identical results.
For example: 4kHz SQRT with 2Vpp. Measured ACV with the 121GW and as comparison a Fluke 28II (highres mode).
Range AUTO: 121GW selects 5V range, Fluke selects 6V range
121GW reads 1,37xxVac, Fluke reads 0,99xxVac
Manual range 5V 121GW, 6V Fluke 28II:
121GW reads 1,37xxVac, Fluke reads 0,99xxVac
Manual range 50V 121GW, 60V Fluke 28II:
121GW reads 0,95xVac, Fluke reads 0,94xxVac
I uploaded video regarding roughly comparing Burden Voltage.QuoteOn your 121GW, you do have a fairly high resolution. In the Amps low range, I think its 10uA resolution which is what you have with the other meters. However, your burden voltage is to be VERY low. Maybe 200ish uv!! Try that and see what you think.?
I posted the above comment on YT. Looking in the manual, maybe it no longer works this but I'm pretty sure that the prototype did.
I uploaded video regarding roughly comparing Burden Voltage.QuoteOn your 121GW, you do have a fairly high resolution. In the Amps low range, I think its 10uA resolution which is what you have with the other meters. However, your burden voltage is to be VERY low. Maybe 200ish uv!! Try that and see what you think.?
I posted the above comment on YT. Looking in the manual, maybe it no longer works this but I'm pretty sure that the prototype did.
The 500mA range uses the Amps jack (and a x10 amplifier) unlike most meters. This gives a very low maximum burden voltage of 30mV/A, or 15mV for 500mA full scale.
Very few meters will be this low on the 500mA range.
With 50,000 count the resolution is 10uA.Thanks.
I had DL'ed the manual when you made it available. The one I have is 25th Nov. 17. I see a mention of the 500mA mode on page 11.QuoteA and 500mA 11A/1000V DC/AC, IR 20kA HRC FAST + DIODEand again on page 55QuoteA/500mA current input fuse: 11A/1000V DC/AC, IR 20kA HRC FAST
The table on page 14 does not mention it.QuoteThe following modes will use the x10 amplifier and may have additional off-set error that can be nulled out before measurement.
Maybe add something to page 32 where the current measurement is shown. When I looked at the burden on the pre-production, is was pretty impressive. From fanOfeeDIY's video, the manual may need a few small additions.
Maybe you (Dave) would consider making a short video showing the meter's burden compared to a few others and how to use it properly.
I am not quite following the discussion. [emoji22]
Especially "200ish uv!!" part.
Should I have used different range in my video?
Do the same test with your 121GW except attach the leads from the A 500mA connector and the COM. The 121GW will display the current with a resolution of 10uA just like the others you show. However, now if you look at the burden voltage for the meter, I suspect you will see something around 200uV rather then several mV as your video shows. I use "ish" as close enough.
I had modified a UNI-T UT61E which has a very high burden voltage, in an attempt to improve it. There was only so much I could do in the area available and the way the board was laid out. I think are real low current, the burden on this meter was lower than the 121GW but once I changed ranged, it was very clear just how good the 121GW was. It's impressive. Give it a try and see what happens. Post your updates, text is good enough.
I am not quite following the discussion.
Especially "200ish uv!!" part.
Should I have used different range in my video?
Do the same test with your 121GW except attach the leads from the A 500mA connector and the COM. The 121GW will display the current with a resolution of 10uA just like the others you show. However, now if you look at the burden voltage for the meter, I suspect you will see something around 200uV rather then several mV as your video shows. I use "ish" as close enough.
I had modified a UNI-T UT61E which has a very high burden voltage, in an attempt to improve it. There was only so much I could do in the area available and the way the board was laid out. I think are real low current, the burden on this meter was lower than the 121GW but once I changed ranged, it was very clear just how good the 121GW was. It's impressive. Give it a try and see what happens. Post your updates, text is good enough.
Maybe add something to page 32 where the current measurement is shown. When I looked at the burden on the pre-production, is was pretty impressive. From fanOfeeDIY's video, the manual may need a few small additions.
Thank you for your valuable comment on both YouTube and here.
I uploaded another video.
I am not quite following the discussion.
Especially "200ish uv!!" part.
Should I have used different range in my video?
Do the same test with your 121GW except attach the leads from the A 500mA connector and the COM. The 121GW will display the current with a resolution of 10uA just like the others you show. However, now if you look at the burden voltage for the meter, I suspect you will see something around 200uV rather then several mV as your video shows. I use "ish" as close enough.
I had modified a UNI-T UT61E which has a very high burden voltage, in an attempt to improve it. There was only so much I could do in the area available and the way the board was laid out. I think are real low current, the burden on this meter was lower than the 121GW but once I changed ranged, it was very clear just how good the 121GW was. It's impressive. Give it a try and see what happens. Post your updates, text is good enough.
Thank you for your valuable comment on both YouTube and here.
I uploaded another video.
https://youtu.be/ffP1Y0zp9KE
V1.09 firmware https://www.eevblog.com/wp-content/uploads/2017/11/EEVBlog1_09.zip
It fixes the issue with the VA mode Bluetooth connection sending garbage data.
I'm sure they run some sort of regression testing before they release updates and that is partly why UEI's response is slow.
Then again, now that Dave has stepped into the role of running life cycle testing maybe he needs to expand into some sort of firmware quality role as well.
gatttool -b 88:6B:XX:XX:XX:XX --char-write-req -a 0x0009 -n 0300 --listen | ./121gw.pl
gatttool -b 88:6B:XX:XX:XX:XX --char-write-req -a 0x0009 -n 0300 --listen | ./121gw.pl 2>&1 | tee logfile.txt
hcitool lescan
and press ctrl-C when it is found.V1.09 firmware https://www.eevblog.com/wp-content/uploads/2017/11/EEVBlog1_09.zip
It fixes the issue with the VA mode Bluetooth connection sending garbage data.
Not really, the main display is correct now, but the upper display lost any connection to reality.
The corrupted data records are still there but less frequent.
It seems 1.09 was a regression of other functionality in the VA mode.
The link has been removed.
V1.09 firmware https://www.eevblog.com/wp-content/uploads/2017/11/EEVBlog1_09.zip
It fixes the issue with the VA mode Bluetooth connection sending garbage data.
Not really, the main display is correct now, but the upper display lost any connection to reality.
The corrupted data records are still there but less frequent.
Can you confirm your setup was in DC mode? What were the conditions which resulted in the incorrect values of the secondary display on the 121GW?
Old post about this was removed as it seems it was not a regression and instead a different error.
Can you confirm your setup was in DC mode? What were the conditions which resulted in the incorrect values of the secondary display on the 121GW?
Old post about this was removed as it seems it was not a regression and instead a different error.
I used DC mode, 400mA, 3.7V, 1.42VA. Both displays on the meter itself are perfect.
The display via bluetooth on the secondary display is 2.9V and 255.86A, the main display is fine.
Are you on windows or Android, which version of the app?