Lost my posting for some reason, site bombed me out!
Just picked up my meter. v1.17
Tried to update to 1.26 and nothing happened. Followed the instructions as per page 70 of the latest manual. The meter just sat there showing 'down'. File on SD card is there and changed to EEVBlog.bin.
Tried to download 1.17, same result.
Any suggestions?
Thanks
Geoff
Lost my posting for some reason, site bombed me out!
Just picked up my meter. v1.17
Tried to update to 1.26 and nothing happened. Followed the instructions as per page 70 of the latest manual. The meter just sat there showing 'down'. File on SD card is there and changed to EEVBlog.bin.
Tried to download 1.17, same result.
Any suggestions?
Strange, first report of someone having issue with this.
Lost my posting for some reason, site bombed me out!
Just picked up my meter. v1.17
Tried to update to 1.26 and nothing happened. Followed the instructions as per page 70 of the latest manual. The meter just sat there showing 'down'. File on SD card is there and changed to EEVBlog.bin.
Tried to download 1.17, same result.
Any suggestions?
Thanks
Geoff
Does the meter write to the card if you start logging?
Alexander.
Haven't tried to write from the meter. I'll give it a go in the morning.
The 50 Mohm range uses 20nA reference current by its internal R9 = 10MOhm reference resistor, which causes a susceptibility to leakage currents (I will demonstrate that later). Maybe it's possible to increase the Vref (by firmware) from about 0.2V to 2V, to get 200nA test current, but probably that's not possible due to supply/reference voltage limitation, as in total >4V would be required. See HY3131 Configuration document, page 31.
The 50 Ohm configuration also follows the HY3131 document, see page 33, so R26 = 1k is used also for 50 Ohm, giving 470µA test current only, and a sensitivity of 470nV on the last digit, causing the noise trouble. The analog multiplex bus of the HY3131 is completely occupied, so it's not possible to add another 100 Ohm reference resistor for 5mA test current.
Frank
Can you remind me which Configuration Document you're referring to?
Can you remind me which Configuration Document you're referring to?
Somebody recently posted the HY3131 configuration document, you have to look for it.
Frank
Lost my posting for some reason, site bombed me out!
Just picked up my meter. v1.17
Tried to update to 1.26 and nothing happened. Followed the instructions as per page 70 of the latest manual. The meter just sat there showing 'down'. File on SD card is there and changed to EEVBlog.bin.
Tried to download 1.17, same result.
Any suggestions?
Thanks
Geoff
Does the meter write to the card if you start logging?
Alexander.
Hi Alexander,
Data logged this morning ok. Viewed Excel file and all the data was there. Tried again to update with 1.26 and same result as meter stays showing "douun", bar graph remains at zero. Waited 10 mins, no change.
Geoff.
Tried again to update with 1.26 and same result as meter stays showing "douun", bar graph remains at zero. Waited 10 mins, no change.
And if you press the "SETUP" button while the meter is showing "douun", still nothing happens?
What is the actual filename of the firmware file you put on the microSD card?
It is supposed to be
EEVblog.bin as per the note on
https://www.eevblog.com/product/121gw/ (click on the
firmware link)
FIRMWARE
Note: When upgrading a multimeter the “.bin” file must be renamed “EEVBlog.bin”:
Brumby, you will see from my first post that I have changed the file name as required.
IanB, yep, just sits there.
Brumby, you will see from my first post that I have changed the file name as required.
Have you tried with other versions other than 1.26?
Check upper/lower cases in the bin file, I think they need to match. Also BIN or bin? My meter takes the .CSV on upper cases which is a pain!
JS
This is how the file change instruction in the manual has it. I think we might have heard by now if others were having this trouble. Appears its just me
“EEVBlog.bin”
Tried another version, same thing. I can read/write to the SD card from the PC, and read from the meter but can't write to the meter.
Geoff
This is how the file change instruction in the manual has it. I think we might have heard by now if others were having this trouble. Appears its just me
“EEVBlog.bin”
Tried another version, same thing. I can read/write to the SD card from the PC, and read from the meter but can't write to the meter.
Geoff
Yes, appears it's just you. If you want to fix it yourself the bootloader is in the reverse engineering docs so you can write it with a st-link. Before doing so try writing your cal data to the sd file and decode it with the phyton routing that's there as well, to checl it makes sense. Then take what's in the stm with the st-link, save it and then write the new bootloader to it, then try installing the new firmware with the SD again. Looks like it's that or shipping it back for a fix at Dave's HQ.
JS
Thanks JS but I'll wait and see what Dave comes back with as I registered the issue on the web site's "Report an Issue".
Geoff
Thanks JS but I'll wait and see what Dave comes back with as I registered the issue on the web site's "Report an Issue".
Geoff
That's fine, I think he's aware of your case, he answered your first post on this IIRC... I'm just saying something that might solve your issue, and what reaources there are to do so, in case he gives you green light to poke with it.
JS
Thanks JS but I'll wait and see what Dave comes back with as I registered the issue on the web site's "Report an Issue".
Geoff
OK...so my bad!! This is the text from the web site;
Note: When upgrading a multimeter the “.bin” file must be renamed “EEVBlog.bin”:
So being a literal being, that's exactly what I did already knowing it was a bin file, I assumed the program looked at the "name" wanting to see a .bin. So I had in effect EEVBlog.bin.bin. The penny dropped when I saw Dave's email from EEVBlog with a included file to try. Now I have v1.26.
Sorry all for the distraction. I'll now email Dave and apologies
Geoff
I think I can withdraw my apology..........
Brumby, you will see from my first post that I have changed the file name as required.
Oooof. Sorry.
So being a literal being, that's exactly what I did already knowing it was a bin file, I assumed the program looked at the "name" wanting to see a .bin. So I had in effect EEVBlog.bin.bin. The penny dropped when I saw Dave's email from EEVBlog with a included file to try. Now I have v1.26.
Sorry all for the distraction. I'll now email Dave and apologies
Geoff
Dont worry be happy! I did something similar but got pointed in the right direction by all the good people who read the 121GW threads.
Guaranty we wont make that mistake ever again
Hi, new one, I've seen some comments on this but now I'm aeeing it on my meter. On the low ohms range sometimes it just measures zero when you short the leads, or a low resistance path, sometimes as expected I need to zero out the leads and it's left with a few counts and sometimes it is left with a few tens of counts left.
Turning it off and on again changes this, in which of the states it is at.
Have you seen this? Do you know something about that?
JS
On this 600V meter, the latest version of the manual August 30, 2018, still confusingly specifies AC and DC VA as 500VA without mentioning its limited to 50V for whatever reason
On this 600V meter, the latest version of the manual August 30, 2018, still confusingly specifies AC and DC VA as 500VA without mentioning its limited to 50V for whatever reason
I don't understand that limitation, everything is in the meter to measure higher voltages and that's all that should be required. I guess I'm missing something but measuring VA directly on mains would be nice.
JS
Agree with that , this could be usefull sometime for DC ( ex. power supply ) and AC ( mains , power amplifiers ) . 10A x 500V . For minuscule VA ranges i can't think of any practical usage ... I remember reading somewhere that David said that is not enough "room " in the micro for all ranges and in this case some lower ranges must disappear .