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.
On the meter display or the app display? (or both)
Only in the app, the meter is correct.
Does the SD card logged data show correct or incorrect readings?
I didn't try the SD-card since the log is of no use to me without timestamps.
I guess the invalid checksums must then be some electrical problem in my meter if no one else can see them.
Again, how are you validating your checksums? with your own software?
Yes with my own software, you have the raw readings in the post above, you could verify yourself.
I updated the meter to 1.10 and now the iphone app doesn't work. it connects (apparently) but there is no meter display in the app.
Any ideas? Fixes? Any idea when a real eevblog iOS app will be released?
I updated the meter to 1.10 and now the iphone app doesn't work. it connects (apparently) but there is no meter display in the app.
Any ideas? Fixes? Any idea when a real eevblog iOS app will be released?
The Bluetooth protocol changed, you have to use the correct application version (I do not know that yet, I am still waiting on my meter).
I updated the meter to 1.10 and now the iphone app doesn't work. it connects (apparently) but there is no meter display in the app.
Any ideas? Fixes? Any idea when a real eevblog iOS app will be released?
The Bluetooth protocol changed, you have to use the correct application version (I do not know that yet, I am still waiting on my meter).
EEVBlog: any ETA on an iOS app?
Should I downgrade the firmware? Will that work? Any idea to what version? I use that app!
Should I downgrade the firmware? Will that work? Any idea to what version? I use that app!
Anything < 1.10 should work, so I'd say use 1.07.
I updated the meter to 1.10 and now the iphone app doesn't work. it connects (apparently) but there is no meter display in the app.
Any ideas? Fixes? Any idea when a real eevblog iOS app will be released?
The Bluetooth packet changed as has been discussed on here.
We (EEVblog "we", not UEi) do not endorse nor have control over the UEi application that is currently on the iPhone store. We are not aware of if or when they are updating that.
David is starting working on the iPhone version shortly, we now have a mac setup to enable the compiler to do this.
I updated the meter to 1.10 and now the iphone app doesn't work. it connects (apparently) but there is no meter display in the app.
Any ideas? Fixes? Any idea when a real eevblog iOS app will be released?
The Bluetooth packet changed as has been discussed on here.
We (EEVblog "we", not UEi) do not endorse nor have control over the UEi application that is currently on the iPhone store. We are not aware of if or when they are updating that.
David is starting working on the iPhone version shortly, we now have a mac setup to enable the compiler to do this.
Thanks Dave that's good news. Looking forward to a spiffy iOS app.
Thanks Dave that's good news. Looking forward to a spiffy iOS app.
In theory it's as easy as pressing Compile for iOS, but we have not done this before, so
But remember, iOS users are used to a particular look and feel.
Sleek, stylish, streamlined - and it sets the parameters and tells the user what to do, because it knows best.
But remember, iOS users are used to a particular look and feel.
Sleek, stylish, streamlined - and it sets the parameters and tells the user what to do, because it knows best.
That's pretty much true of Apple.
But I think there is enough flexibility with the iOS UX framework that a flexible app could be designed.
Dave thanks for the last update on these meters. Since some people have cancelled and the meters have already been ordered, would it be possible to order more meters?
Also, it is well worth the wait for the bugs to be worked out, especially any hardware bugs.
Take care everyone!
Really really looking forward to get mine
thanks for all your work (Dave and all the forum users that helped to find, solve and test bugs!)
Hi Dave.
The survey link you posted in the Kickstarter comments section (Johnny B. Goode @
https://www.kickstarter.com/projects/eevblog/eevblog-121gw-multimeter/rewards/6297526/survey) to change the shipping address indeed doesn't work for me; it drives me back to kickstarter home page.
@all,
EDIT: No taking the audience for dummies, this is only for the sake of completeness.I had to use the button «
Show my contribution» (translated from French: «
Afficher mon engagement»). That button stands to the right of «
You are a contributor» and is visible once logged in and you're viewing the multimeter project. Then select the
Survey tab. From there you can change your shipping address
.
Otherwise use the kickstarter menu under your login icon on the top right corner of the page, click the EEVBlog multimeter and from there «
Show my contribution».
Thanks for the update. I'm still looking forward to the postman knocking at my door ;-) .
sweet
At the moment raw packet logging is not a feature of the app, I use debug outputs (in visual studio, with debug mode) to get the data.
I would still suggest you include the feature in your app.
It might be the linux bluetooth stack that is the reason for the errors, but it might also be some electrical problem with pullup/diode level shifter (R76/D4 in the schematic) in my (or others) meter. Maybe the resulting voltages are too narrowly specified.
With that feature more people could check easily if that's the case on more meters.
At the moment raw packet logging is not a feature of the app, I use debug outputs (in visual studio, with debug mode) to get the data.
I would still suggest you include the feature in your app.
It might be the linux bluetooth stack that is the reason for the errors, but it might also be some electrical problem with pullup/diode level shifter (R76/D4 in the schematic) in my (or others) meter. Maybe the resulting voltages are too narrowly specified.
With that feature more people could check easily if that's the case on more meters.
+1 for raw packet logging / debugging, it really comes in handy to eliminate possible failure modes when making protocols
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.
Since the 121GW seems to have an UART, I'd like to know precisely
where to get at the UART signals.
Are these at Pin 122 on U4 for Rx and Pin 119 for Tx?
Since the 121GW seems to have an UART, I'd like to know precisely
where to get at the UART signals.
Are these at Pin 122 on U4 for Rx and Pin 119 for Tx?
There is a schematic on the product page at
https://www.eevblog.com/product/121gw/.
Finally conduct updating the firmware of my 121GW multimeter.
I am happy with the autorange speed.
https://youtu.be/6Y1KzSA-BUE
I think I need to get better of improving video quality.
nice to see improvements like this
now Dave design an bench meter version loll
Dave thanks for the last update on these meters. Since some people have cancelled and the meters have already been ordered, would it be possible to order more meters?
Sorry, but no, not at this stage.
Oh can't wait. Need a new DMM.