There is absolutely nothing stopping anyone writing their own firmware and making it open source.
Does that include YOU Dave ?
No, the ridiculous amount of time spent on the open source app taught us not to touch the firmware.
Confirmed issues (or annoyances) from what I've (re)-tested so far.
1. Slow auto-ranging: Ohms, Voltage, Capacitance
2. double double double beeps constantly going on when in diode mode
3. measuring any resistance (short or higher value) in diode mode gives a constant and loud beep
4. Wobbly selector/range switch: back an forth (vertical) when in diode mode it will even blink the back-light or completely switch off.
5. Strange to me is that when in diode mode a small green LED has a Vf of 1.79 in the 3V mode and a Vf of 1.98 in the 15V mode. And also is a bit brighter then.
Hope this helps,
6. on the lower current fuse is rated 600V and 400mA from ASTM. Which is different from the manual: 440mA and 1000V. I believe this was somewhere posted already?
3. measuring any resistance (short or higher value) in diode mode gives a constant and loud beep
That feature was requested by people.
5. Strange to me is that when in diode mode a small green LED has a Vf of 1.79 in the 3V mode and a Vf of 1.98 in the 15V mode. And also is a bit brighter then.
Expected, as they result in different test currents.
Manual Correction Dec 11:
The manual specifications is a bit vague on diode test currents. It mentions 1.4mA and 7mA short circuit but they don't really line up with the 3V range and 15V ranges.
It seems the actual currents are different on my meter (v1.01):
3V 0.7mA short circuit
15V 4.6mA
Page 44 mentions the Diode Test current is limited by a resistor + PTC totalling about 2.2K. Has this changed?
ChrisG: Your point 5 is not an issue - the two diode tests are at two different currents. The voltages are meant to be different.
The manual specifications is a bit vague on diode test currents. It mentions 1.4mA and 7mA short circuit but they don't really line up with the 3V range and 15V ranges.
It seems the actual currents are different on my meter (v1.01):
3V 0.7mA short circuit
15V 4.6mA
Short circuit current is a
maximum. It will be less when there's no short circuit.
The manual specifications is a bit vague on diode test currents. It mentions 1.4mA and 7mA short circuit but they don't really line up with the 3V range and 15V ranges.
It seems the actual currents are different on my meter (v1.01):
3V 0.7mA short circuit
15V 4.6mA
Short circuit current is a maximum. It will be less when there's no short circuit.
Huh? I am just mentioning a case where the specifications for short circuit current and the actual meter are different. Also the formatting of the specifications does not have values lining up correctly. It may be the resistor in the final meter are different from the prototype meter. That is all. Dave has mentioned that he wants to soon release an updated version of the manual. It is part of the product.
I wouldn't expect a low to mid-DMM diode check function to have particularly constant current.
Some quick checks on my meters over the reading range :
Fluke 87 (i and III) 0.8 to 0.15mA
Fluke 287 1mA up to 2V, then down to 0.8mA at 3v
Agilent 36641A 1mA constant
No one is suggesting constant current. I have done a report on short circuit currents of my meter because they are different from the spec. It would be useful if you can confirm my numbers, or if your 121GW meter matches the spec.
No one is suggesting constant current. I have done a report on short circuit currents of my meter because they are different from the spec. It would be useful if you can confirm my numbers, or if your 121GW meter matches the spec. O miss
0.7mA on 3V range
4.25mA on 15V range
0.71 mA on 3V range
4.61 mA on 15V range
Measured through a BM869s.
UPDATE:
UEi are aware of the various issues and are working on them.
The autoranging as you might expect is not necessarily trivial and will take a few more days to test this.
For the range switch they are waiting on a slightly modified part to see if that can solve it.
If UEi are fixing the Autoranging, it might be a good opportunity to fix the non-working DC mVA/VA autoranging with negative currents.
Hi Dave
On my meter pins PE13
(SPI1_SCK/FSMC_D10) and PE14
(SPI_MISO/FSMC_D11) of the STM32L1 are shorted together (continuity tested). The attached file has the best focused image I could get of this. Should I do anything about it?
Metal parts in range switch will make it more enjoyable to use...
On my meter pins PE13 (SPI1_SCK/FSMC_D10) and PE14 (SPI_MISO/FSMC_D11) of the STM32L1 are shorted together (continuity tested). The attached file has the best focused image I could get of this. Should I do anything about it?
That's VSSA and VREF-, they should be connected.
Looks like they used a direct track in-between pins which trapped the solder.
Nothing to worry about.
The switch on my meter (#000499) is also wobbly and has the problem described here.
I took it apart, and contacts and pcb looked ok. After I put it back together it worked allright for a while, but now it's back and I have to fiddle with the switch again to get it to display correct readings.
Dave, once UEi figures out a fix, will you send out a replacement part?
Thanks,
Ben
The switch on my meter (#000499) is also wobbly and has the problem described here.
I took it apart, and contacts and pcb looked ok. After I put it back together it worked allright for a while, but now it's back and I have to fiddle with the switch again to get it to display correct readings.
Dave, once UEi figures out a fix, will you send out a replacement part?
Yes we'll have to do that for those existing shipments who have problems.
Minor Issue:
I just opened my 2nd set of leads, note the positive lead, recessed threaded portion, and it's broken internally. Slightly flexing the break in the 2nd photo to accentuate the area.
It's electrically connected however. (Replacements not necessary, I got a zillion of them)
Minor Issue:
I just opened my 2nd set of leads, note the positive lead, recessed threaded portion, and it's broken internally. Slightly flexing the break in the 2nd photo to accentuate the area.
It's electrically connected however. (Replacements not necessary, I got a zillion of them)
It happens in large numbers. My BM235 with the same probes has done that the inside spins on when I screw on the banana jacks. So I’ve just been carful to not torque that one since I fear the wire might eventually twist to much and break off. I even had one probe new with the fluke 289 that was bent, they did replace that one since they reached out to me. I guess they saw it on the unboxing video.
I never bothered to mention it since I have the probematers and a few fluke probes. Like you, I have enough of them, but sometimes I have to run three meters and I usually use the probes they came with.
That brings up a good question, I know Brymen is responsive to fixing and communicating with customers to fix issues. So if the probes have an issue, who do we contact since Brymen makes the probes but UEI made the meter? Do we contact UEI, Brymen, or EEVBlog (Dave)?
inside spins
This one is tight, perhaps just in the wrong position when molded.
I suspect the wire lead is terminated at the break in my case above, which means it probably wouldn't last long in the field.
Just confirming an issue reported by Joe Smith on the prototype unit he tested still exists on my production unit.
As posted in the discussion thread at
https://www.eevblog.com/forum/testgear/eevblog-121gw-discussion-thread/msg1408767/#msg1408767And confirmed by maukka in a followup post
https://www.eevblog.com/forum/testgear/eevblog-121gw-discussion-thread/msg1408768/#msg1408768I wonder if someone could check the meter in the LowZ mode. In the early unit, if I applied a 1VRMS 60Hz signal, the meter would read zero as expected. However, when I would increase the frequency to 389KHz, the meter was displaying 181.3 volts even though there was still only a volt being supplied. There was something strange going on with it that I never looked into. I reported the problem when I discovered it but with as many problems that the meter still has, I wonder if this was addressed in the released version.
Joe, I can confirm this issue is still present in FW1.01.
I generated a 2.8Vpp 60Hz (& 1kHz) sine wave with my MSO1104Z-S and it read 0V in LowZ mode.
When I upped the freq to 389kHZ and I got a reading of 189.2Vac. See photo...
Edit: and it correctly read ~1V AC without LowZ up to maybe 100kHz, but that dropped to 0.773V AC at 389kHz
Confirmed... Though it does too vary a bit when changing frequencies.
Does this LowZ issue happen in the ACV's highest (600V) range? The two are calculated virtually identically in the software. If there's an issue with the routines or calibration data for that ACV mode, they should be broken in the same way. Of course, I'm not saying that them not behaving the same means it has to be fixed in hardware.
Edit: the calibration tables are also only specified up to 10KHz. Perhaps the 10KHz correction factor becomes invalid at such a high frequency? Can anyone
dump their calibration data (requires firmware 1.02) for me?
Edit: the calibration tables are also only specified up to 10KHz. Perhaps the 10KHz correction factor becomes invalid at such a high frequency? Can anyone dump their calibration data (requires firmware 1.02) for me?
Here you go, I attach it zipped.
So I toyed around in Python and got some interesting results. There is a routine which takes the measured input frequency and value, then calculates an offset based on these two factors. It is possible for a large negative calibration value to produce the behavior, but the required value seems kind of crazy (though the firmware would accept it as valid). See
for a graph of that result.
Some other notes:
- The number in question is a signed 2 byte big endian number located at 0x68 in CAL.BIN. The copy that I have has 26. Does anyone's have a very large negative number? The one at 0x6A is relevant as well, my calibration copy has 217.
- Low-Z mode has a hysteresis effect: it won't move off 0V until it believes the input is above 10V (incl. as a result of above calibration shenanigans) and will drop back to 0V if the input drops below 3V.
- But, the ACV mode switched to 600V range is identical in almost every respect to Low-Z in AC mode, software-wise. Can you duplicate the problem in ACV on the 600V range? I assume Kean's test probably used the 5V range. It should also give you a better picture at what's happening at lower frequencies when the believed input is <10V. ACV can also display the believed input frequency by pressing 'SETUP' enough times.