Oh can't wait. Need a new DMM.
I re-checked with 1.10 and get the same results. Can someone confirm my measurements?
Why is the 121GW reading wrong in auto range/manual 5V range in this situation?Can you reproduce the following measurements?
2.0V peak to peak sine wave 4kHz, No DC offset, duty cycle 50%. Both meters in AC mode. Firmware 1.07 on my 121GW with serial number EEVblog 000084
Auto mode on both meters, Fluke in highres mode:
121GW selects 5V range, reads 1.1133Vac
Fluke 28II selects 6V range, reads 0.7031Vac
manual mode on both meters:
121GW 5V range, reads 1.1133Vac
Fluke 28II 6V range, 0.7032Vac
121GW 50V range, reads 0.659Vac (and it looses the frequency measurement and displays 0.00kHz)
Fluke 28II 60V range, reads 0.663Vac
See the attached pictures.
I re-checked with 1.10 and get the same results. Can someone confirm my measurements?
Why is the 121GW reading wrong in auto range/manual 5V range in this situation?Can you reproduce the following measurements?
2.0V peak to peak sine wave 4kHz, No DC offset, duty cycle 50%. Both meters in AC mode. Firmware 1.07 on my 121GW with serial number EEVblog 000084
Auto mode on both meters, Fluke in highres mode:
121GW selects 5V range, reads 1.1133Vac
Fluke 28II selects 6V range, reads 0.7031Vac
manual mode on both meters:
121GW 5V range, reads 1.1133Vac
Fluke 28II 6V range, 0.7032Vac
121GW 50V range, reads 0.659Vac (and it looses the frequency measurement and displays 0.00kHz)
Fluke 28II 60V range, reads 0.663Vac
See the attached pictures.
1) Should the 500V AC VA mode be added at the expense of a few of the other lower ranges?
2) Is AC VA mode even useful to people? (obviously the DC VA mode is)
1) Should the 500V AC VA mode be added at the expense of a few of the other lower ranges?
2) Is AC VA mode even useful to people? (obviously the DC VA mode is)
Hello,
As don't have the 121GW yet was wondering before ordering if the PC Gui logging software will work with one of these please:
https://www.overclockers.co.uk/asus-usb-bt400-bluetooth-4.0-usb-adaptor-nw-076-as.html
Many thanks
Hello,
As don't have the 121GW yet was wondering before ordering if the PC Gui logging software will work with one of these please:
https://www.overclockers.co.uk/asus-usb-bt400-bluetooth-4.0-usb-adaptor-nw-076-as.html
Many thanks
Any 4.0 adapter that supports BLE mode should work.
I'm now asking if it's worthwhile having the 500V/10A AC VA range at all? I can't personally, but I'm not really an AC industry guy.
With regards to the requested 500V/5A (250VA) VA power mode.
It is possible to add this (with some sacrifice in other ranges), and we have tested a solution.
But now I'm I am wondering whether or not it's actually worthwhile?
After all the meter is only capable of measuring VA and not true Watts, as the chipset does not have the phase measurement capability.
With this in mind, how useful is VA measurement in AC mode to people without a true Watts capability?
Doe's this mean Joe noob (ie me) looking around for things to measure won't be able to look at all my energy wasting 110VAC stuff. I think my new fangled utility meter bills me measuring only VA?
Doe's this mean Joe noob (ie me) looking around for things to measure won't be able to look at all my energy wasting 110VAC stuff. I think my new fangled utility meter bills me measuring only VA?
The 5V range does appear wrong on your meter but we haven't been able to reproduce it, it could be an issue with your unit in that range.
Can you confirm that the Hz range functions correctly on your meter?
Can you also test the same range with 400Hz?
Is that 2500VA?
What is the sacrifice exactly? Isn't the next range down 500mVAC.
Doe's this mean Joe noob (ie me) looking around for things to measure won't be able to look at all my energy wasting 110VAC stuff. I think my new fangled utility meter bills me measuring only VA?
I was thinking of the spurious VA values. We no longer get these as it's been (as far as we can tell) fixed in software. So if spurious values are being seen, maybe that's a possible cause?
But if it's a checksum thing, then forget I said it.
But as I believe David (seppy) has said, we are no longer getting corrupted data, and hence no more checksum errors.
How could the range switch cause invalid xor checksums?
I don't see spurious VA values as in the early versions of the firmware.
With V1.10 I still see wrong voltage and current displays in certain parts of the measuring range, I see a spurious wrong decimal point in current display and I see wrong range display (A instead of mA) in the current display. All of this in DC VA-mode.
Apart from that the displayed values are consistently wrong.
I guess the invalid checksums must then be some electrical problem in my meter if no one else can see them.
As there seems no way to debug it further, I can't help you there.
Only thing i would change if possible would be the ability to remove/swap the micro sd card without taking the back off, a little hatch would be great and well if you do consider it