so that means the hardware i have bought yesterday is buggy???
it was expensive for my budget though, i bought it for 300AUD
Don't panic.
The first consideration is just what might be affected by the version of firmware supplied. From what I can glean here, it seems to be working fairly well for most users.
Check the firmware version it has when you get it. Also, this meter has the ability to update the firmware - so you're ahead with that feature!
Sorry I thought David had put v2.00 on the website, I've just added it now.
Improvements include improved resistance autoranging speed, and update speed on higher resistance ranges. Plus various capacitance range improvements.
Wow, the improvement in ohms autorange is _huge_.
I ran some resistance tests on 1.58 and 2.00 and my opinion is that the new firmware has improved speeds. My informal test process used to take ~15 seconds on 1.58 (if I moved crazy fast it sometimes was as low as ~10 seconds), but now is ~9 seconds on 2.00 (normal pace). Unfortunately for the 121GW, the same test is only ~5 seconds on the BM235 and many of my other meters.
Hi,
the ohm autorange is faster now, still not my fastest multimeter, but it is ok.
The "low capacitance bug" seems still present, a 220pF NP0 ceramic capacitor is shown as 0.160nF at the first time, then as 0.180nF after that as 0.200nF... The more often I switch the meter off and on, the closer the reading comes to the actual value. Also if I first use a small capacity, then a bigger one (e.g. several hundred nF) and then again the small capacity, the 121GW every time shows a different reading. I am not able to get a steady reading of small capacities with the 121GW. Can other users reproduce this behavior? This is really odd. For higher capacitances the meter shows correct values and the autorange speed seems also faster in capacitance mode now.
Sorry I thought David had put v2.00 on the website, I've just added it now.
Improvements include improved resistance autoranging speed, and update speed on higher resistance ranges. Plus various capacitance range improvements.
Thanks!
Hopefully also the manual changelog will be soon updated with the recent f/w history changes.
Hi,
the ohm autorange is faster now, still not my fastest multimeter, but it is ok.
The "low capacitance bug" seems still present, a 220pF NP0 ceramic capacitor is shown as 0.160nF at the first time, then as 0.180nF after that as 0.200nF... The more often I switch the meter off and on, the closer the reading comes to the actual value. Also if I first read the small capacity, then a bigger one (e.g. several hundred nF) and then again the small capacity, the 121GW every time shows a different reading. I am not able to get a steady reading of small capacities with the 121GW. Can other users reproduce this behavior? This is really odd. For higher capacitances the meter shows correct values and the autorange speed seems also faster in capacitance mode now.
We talked about this issue and was confirmed , but ... probably they don't care or can't fix it .
It seems to me that only the comunity will solve all the issues ... when someone pissed off will write a better firmware .
Anyone wondering if they should bother to update firmware to V2.0?
My advice for what its worth is to do it! The update certainly speeds up the meter's responsiveness for resistance and gives it a faster feel all round.
I did it successfully but there is a "Gotcha" in this. The .bin file is named EEVBlog2_00.bin. That name will not upload into the meter. Rename it to EEVBlog.bin, as it has been in the past and the upload will work. I will also remind people that the Analog bar will show the progress of the upload. If it does not move, it's not doing anything.
I can also confirm (though do not recommend) that after a couple minutes, of "Douun" ... turning the meter off caused no harm. If you are sitting there and the download to the meter is not working, despite cautions in the instructions, I did turn if off (and did this twice) without ill effect. Then I just renamed the file name as explained above and all was well.
EEVBlog folks may wish to repost the 2.0 zip with the .bin file name modified to avoid confusion and match past releases. Suggestion for 2.0+ is to not display "Douun" if the meter could not find a file to load, either because it was not the correct name (as here) or some other reason. It should post something like "Err" and then restart after a few seconds.
Now the ranges for voltage switch at 55000 counts up and 50000 counts down ( before was at 45000 down) , this is fairly normal and the switching is faster ... so it could be done , why took so long it's a interesting question .
I did it successfully but there is a "Gotcha" in this. The .bin file is named EEVBlog2_00.bin. That name will not upload into the meter. Rename it to EEVBlog.bin, as it has been in the past and the upload will work.
I wouldn't call this a "Gotcha". This has been a requirement from the very beginning.
I would strongly suggest that you always keep the firmware showing the version number in the filename and ONLY change it when copied to the card for uploading.
My recommendation: NEVER, EVER, EVER put up a file named EEVBlog.bin here or anywhere else -
because you won't know what version it is.
I did it successfully but there is a "Gotcha" in this. The .bin file is named EEVBlog2_00.bin. That name will not upload into the meter. Rename it to EEVBlog.bin, as it has been in the past and the upload will work.
I wouldn't call this a "Gotcha". This has been a requirement from the very beginning.
I would strongly suggest that you always keep the firmware showing the version number in the filename and ONLY change it when copied to the card for uploading.
My recommendation: NEVER, EVER, EVER put up a file named EEVBlog.bin here or anywhere else - because you won't know what version it is.
No. Keep it in the zip file where it's protected from accidental corruption until you need it. The zip file can have the version number in the name but the bin file inside should be the correct name to just extract it on to the microSD without any messing about renaming it.
Sent from my SM-N9005 using Tapatalk
That's not unreasonable, but it does put a greater risk of getting it wrong when the firmware is zipped by Dave/David.
I'm happier with the fail safe method currently in use. When things go wrong now - no damage is done and is fixed by a simple rename.
That's not unreasonable, but it does put a greater risk of getting it wrong when the firmware is zipped by Dave/David.
I'm happier with the fail safe method currently in use. When things go wrong now - no damage is done and is fixed by a simple rename.
Whoever zips the firmware is welcome to call it whatever they want until they zip it. (Hopefully it's arriving from UEI already in a zip file and not just as an unprotected email attachment)
But please after zipping it in an appropriately named zip file rename it so it's ready to use when I extract it to the microSD card.
I still don't like the idea.
I can see why you are asking - but is a simple rename too much to ask?
Edit: I say this because after more years than I care to remember in the software development game, version control is extremely important and easily stuffed up.
Suggestion for 2.0+ is to not display "Douun" if the meter could not find a file to load, either because it was not the correct name (as here) or some other reason. It should post something like "Err" and then restart after a few seconds.
That's not a bad idea.
I don't think that change is possible, as that code would be in the fixed protected bootloader code.
They have no way to reprogram the boot loader? Even if they create an application to reprogram the boot? Seem odd they wouldn't have considered that.
They have no way to reprogram the boot loader?
Of course there is, but it requires a programmer and a special cable. Not something you'd ordinarily instruct or encourage customers to do unless the circumstances were dire.
Countless products follow this exact principle.
The factory can certainly update the bootloader for new units shipped.
BTW, I don't know how they actually do it at the factory, but they could buy the ARM chips pre-programmed with the bootloader and so wouldn't ordinarily program the bootloader at the factory.
It would be good if somebody could do another side by side comparison video to show how much better this meter performs now with the new firmware.
Hi,
the ohm autorange is faster now, still not my fastest multimeter, but it is ok.
The "low capacitance bug" seems still present, a 220pF NP0 ceramic capacitor is shown as 0.160nF at the first time, then as 0.180nF after that as 0.200nF... The more often I switch the meter off and on, the closer the reading comes to the actual value. Also if I first use a small capacity, then a bigger one (e.g. several hundred nF) and then again the small capacity, the 121GW every time shows a different reading. I am not able to get a steady reading of small capacities with the 121GW. Can other users reproduce this behavior? This is really odd. For higher capacitances the meter shows correct values and the autorange speed seems also faster in capacitance mode now.
does anyone care about this problem?
Thanks, I will have a look at that video shortly.
I just found this video on Youtube where someone has created a splendid addition to the tilt stand on the 121GW meter.
https://www.thingiverse.com/thing:3666409