This video clearly shows the "ghost" reading in resistance mode, for example at the 0:28 mark and at the 3:24 mark. If you have auto-hold turned on will it capture these ghost readings instead of the final correct reading? I would prefer that the display is suppressed until it settles on a final reading.
Some resistance ranges are still affected by noise , probably where the ADC is at the maximum sensitivity . Overall the measurement current is too small on all ranges if you compare it with a known brand multimeter and this force the ADC to be very sensitive and easily capturing any noise from the hands holding the probes . It would be fantastic if in real world we would measure resistors like in the video , without holding the probes .
Some resistance ranges are still affected by noise , probably where the ADC is at the maximum sensitivity . Overall the measurement current is too small on all ranges if you compare it with a known brand multimeter and this force the ADC to be very sensitive and easily capturing any noise from the hands holding the probes . It would be fantastic if in real world we would measure resistors like in the video , without holding the probes .
So you are claiming the Meter is faulty because of being used with poor technique with no evidence I have seen to back it up? Seriously what a load of
I just say that some people would use it working on something
not just for show .
Now it is much better than it was with some old firmware , but still in some ranges last 2 digits will fluctuate .
Sorry if I spoil somebody sensation that this is the perfect meter .
High res video of old man hands.
Looks much better (firmware, not your hands).
I did pick up both programming adapters for this meter. I reprogrammed the BLE controller on the prototype meter but have decided to hold off doing anything with the firmware.
I was thinking they could reprogram the boot from some other means but I agree most of the time, you would never do this on a handheld (or any product). Normally true for the application as well.
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.
Too bad the stand just wasn't wider at the base. I wonder thy they didn't print a whole new stand that would step out from the boot and then lay flat across the back rather than to snap in this extension. Seems like even adding even 5mm to to both sides would really help.
I was thinking they could reprogram the boot from some other means
No, and that's the whole point, so that the bootloaded is fully protected from idiot users.
In theory there should be no way you can crash the firmware upload and brick your meter, i.e. taking out the card during programming, or power interruption, or corrupted code etc.
I think I may have bricked my meter. I downloaded the V2 firmware, extracted the file, renamed it, transferred it on to a different Micro SD card that I'd formatted in Windows 10, then put it in the meter and tried to update it. It's been sitting at IAP- douun for over half an hour now. Help!
I think I may have bricked my meter. I downloaded the V2 firmware, extracted the file, renamed it, transferred it on to a different Micro SD card that I'd formatted in Windows 10, then put it in the meter and tried to update it. It's been sitting at IAP- douun for over half an hour now. Help!
It should only take about 5 seconds.
Say a prayer and switch off and on again.
Later:
I recommend this:
https://www.sdcard.org/downloads/formatter/ for formatting SD cards using Windows. Windows itself tends to format them in nonstandard ways that can confuse some devices.
Two hours after starting the upgrade it hadn't moved, so I took a deep breath turned it off and tried putting the new firmware on the original Micro SD. I put it in and tried uploading it and it worked, like you said - in less than 5 seconds. When I turn the meter on the backlight flashes briefly but it's done that since I upgraded to 1.57. I'll test the meter out later and hope like hell that I haven't shagged it. I was just trying to use a faster Micro SD. Oh well, we live and learn, and make dicks of ourselves.
Two hours after starting the upgrade it hadn't moved, so I took a deep breath turned it off and tried putting the new firmware on the original Micro SD. I put it in and tried uploading it and it worked, like you said - in less than 5 seconds. When I turn the meter on the backlight flashes briefly but it's done that since I upgraded to 1.57. I'll test the meter out later and hope like hell that I haven't shagged it. I was just trying to use a faster Micro SD. Oh well, we live and learn, and make dicks of ourselves.
That all sounds normal again.
That backlight flicks on for a moment on mine too.
Even when they work right firmware updates are scary, especially if you have no real idea how much thought has gone into making the process failure proof.
I had the same problem earlier today. Turns out you need to rename the file from EEVBlog2_00.bin to EEVBlog.bin; that did the trick and it updated to V2 in only a few seconds. Had the same "oh crap" thought when the "down" display just sat there...took a chance and cycled the power and fortunately the boot loader didn't have a problem!
I had the same problem earlier today. Turns out you need to rename the file from EEVBlog2_00.bin to EEVBlog.bin
You just like it tell you to do right above the very link you download it from?
I was thinking they could reprogram the boot from some other means
No, and that's the whole point, so that the bootloaded is fully protected from idiot users.
In theory there should be no way you can crash the firmware upload and brick your meter, i.e. taking out the card during programming, or power interruption, or corrupted code etc.
Perhaps your customers are just a bit overzealous causing them to experiment more than they should. After all, isn't that the jist of Don't Turn it on, Take it apart.
I just say that some people would use it working on something not just for show .
Now it is much better than it was with some old firmware , but still in some ranges last 2 digits will fluctuate .
Sorry if I spoil somebody sensation that this is the perfect meter .
It is my everyday driver in my toolbag and works fine. It is you who has the problem, sell your meter and stop being a sook.
I just say that some people would use it working on something not just for show .
Now it is much better than it was with some old firmware , but still in some ranges last 2 digits will fluctuate .
Sorry if I spoil somebody sensation that this is the perfect meter .
I just compared it to the Brymen BM869 and Keysight U1272A and they have exactly the same fluctuation when handling the leads, even worse perhaps, using the same 30M resistor with the same leads.
I was thinking they could reprogram the boot from some other means
No, and that's the whole point, so that the bootloaded is fully protected from idiot users.
In theory there should be no way you can crash the firmware upload and brick your meter, i.e. taking out the card during programming, or power interruption, or corrupted code etc.
Perhaps your customers are just a bit overzealous causing them to experiment more than they should. After all, isn't that the jist of Don't Turn it on, Take it apart.
All the more reason for me
not to encourage anyone to experiment with the bootloader, let alone provide them instructions to do so.
I just say that some people would use it working on something not just for show .
Now it is much better than it was with some old firmware , but still in some ranges last 2 digits will fluctuate .
Sorry if I spoil somebody sensation that this is the perfect meter .
It is my everyday driver in my toolbag and works fine. It is you who has the problem, sell your meter and stop being a sook.
Hey BeanFlying, I believe CDaniel is entitled to share his opinion just as you and I am!
You like the meter and its in your tool bag thats cool.
CDaniel wants to criticize certain functions of the meter and how it operates thats cool too!
We even have one person in this thread who shares his opinion on this meter and he doesn't even own or have one. Thats amazingly cool as well!
No need to get your knickers in a knot over opinionated people because as we all know, everyone has one (IMO)
I just say that some people would use it working on something not just for show .
Now it is much better than it was with some old firmware , but still in some ranges last 2 digits will fluctuate .
Sorry if I spoil somebody sensation that this is the perfect meter .
It is my everyday driver in my toolbag and works fine. It is you who has the problem, sell your meter and stop being a sook.
Hey BeanFlying, I believe CDaniel is entitled to share his opinion just as you and I am!
You like the meter and its in your tool bag thats cool.
CDaniel wants to criticize certain functions of the meter and how it operates thats cool too!
We even have one person in this thread who shares his opinion on this meter and he doesn't even own or have one. Thats amazingly cool as well!
No need to get your knickers in a knot over opinionated people because as we all know, everyone has one (IMO)
He had a first dig and as such I WILL REPLY if I think it warranted. Which I have done in this case. I will not be told by you or anyone that I shouldn't reply.
I had the same problem earlier today. Turns out you need to rename the file from EEVBlog2_00.bin to EEVBlog.bin; that did the trick and it updated to V2 in only a few seconds. Had the same "oh crap" thought when the "down" display just sat there...took a chance and cycled the power and fortunately the boot loader didn't have a problem!
For those having a whinge about, i've fixed the ZIP file.
I'll await the whinge when someone mistakes the eevblog.bin for an older eevblog.bin
I just say that some people would use it working on something not just for show .
Now it is much better than it was with some old firmware , but still in some ranges last 2 digits will fluctuate .
Sorry if I spoil somebody sensation that this is the perfect meter .
I just compared it to the Brymen BM869 and Keysight U1272A and they have exactly the same fluctuation when handling the leads, even worse perhaps, using the same 30M resistor with the same leads.
Also the BM235, and the Fluke 17B have exactly the same fluctuation.
Shall I keep going
I didn't say it's the highest range ... the reading fluctuate in 5K range for example when you hold the probes .
Just don't ask for proofs , I don't make videos for something that everyone with 2 hands and willingness to use them can replicate easily
...
Perhaps it is just a lack of filtration at the ADC input . Before firmware 1.57 was much worse , so something can be done .
It is at least silly to design a meter and not check if is stable when holding the probes ...
I didn't say it's the highest range ... the reading fluctuate in 5K range for example when you hold the probes .
Nope, doesn't do it for me. 5k resistor only varies +/-1LSD, maybe 2LSD at a pinch with cable handing.
And that's either touching cables (i.e. capacitive coupling) or touching either probe, and even rubbing my shoes on the carpet to generate some ESD.
No worse than a Keysight U1272A.
Are you using yours in high V/m field or something?
OK , a video with a 47K , even with no touching hands , just the bench noise . If I move the meter away from the table it is stable , but obviously something is not right
https://streamable.com/giz9s