The first actual need I had to log data on the 121GW revealed a bug in the iOS app.
Meter FW: 1.22
iOS App: Build 1.6
AC Current reading is off on the iOS device by either 100x high or 10x low.
121GW App Range
1.0007 mA 100.07 mA Auto
1.0007 mA 100.07 mA First manual
1.002 mA 0.1002 mA Second manual
Alright, do you know if that is a permanent issue or just the first time it samples?
This can be resolved quite quickly, depending.
It happens all the time. It seems like there is some conversion issue that is wrong only for AC current. I could not find a problem with any other mode.
It happens all the time. It seems like there is some conversion issue that is wrong only for AC current. I could not find a problem with any other mode.
Found the issue, it will be released after I can get my hands on the test devices.
If you curious, there was a rouge 3 in the source.
If you curious, there was a rouge 3 in the source.
Is that colour-sensitive programming - or a misspelled "rogue"?
(sorry)
I can't get the Windows app working that's available here:
https://www.microsoft.com/en-au/store/p/eevblog-121gw/9n2681hjrtm8The 121gw BT pairing seems to be working and "121GW BluetoothLE#......" is displayed in the app - clicking this shows "Connecting..." for a few seconds - but then nothing - just a blank screen.
I'm using windows 10 v1803 and a HP Zbook g2 laptop.
On the Windows 10 app, I recorded a lot of data and then saved to a csv file, which was created OK. However, when I later went back to look at the log file I found it to have zero size and was empty. On a second attempt following the same steps with the same amount of data (about 10 minutes worth), the file was created successfully. So I don't know how to reproduce the problem.
(BTW, maybe this thread could be pinned like the other 121GW threads? I had to scroll down quite a bit to find it.)
Hi, I haven't been able to log the second display, not with the APP or to the SD card (forgot to check in VA mode which really should work)
Is there anything about this or is something that might be added in the future?
Thanks!
JS
(BTW, maybe this thread could be pinned like the other 121GW threads? I had to scroll down quite a bit to find it.)
I second that, the App and BT functionality is an important part of the 121gw package, perhaps this thread should be pinned trying to keep these specific issues out of the other 121gw threads.
On the Windows 10 app, I recorded a lot of data and then saved to a csv file, which was created OK. However, when I later went back to look at the log file I found it to have zero size and was empty. On a second attempt following the same steps with the same amount of data (about 10 minutes worth), the file was created successfully. So I don't know how to reproduce the problem.
OK, I just reproduced it a second time. I was running the app on Windows 10 and recorded several minutes of data (10 minutes or so). Then I tried to save it to a csv file. On the first attempt it produced a file with zero bytes. However, a second attempt succeeded.
The Bluetooth interface on Windows 10 seems very touchy. I got the meter to pair, but it wouldn't connect for more than a second or two before going back to paired. When the app was launched then most of the time the meter did not show up. When it did show up a connect attempt produced a "Connecting..." message from the app that lasted forever.
In the end I got it to work by rebooting the computer.
This might be a Windows 10 problem. Maybe it is outside your control. Many Bluetooth devices fail to work properly under Windows 10 as a quick Google search will verify.
(I have not seen any connection issues with iOS.)
Yeah very touchy indeed, my Zbook G2 is supposed to be BT 4.0 + LE compliant but as it seems not compliant enough. Disabling the BT in bios and using a cheap BT 4.0 dongle instead the Win 10 App works. Haven't tested it much more though, mainly wanted to check that wasn't a problem with the meter.
It is at least somewhat windows related, some drivers behave very differently.
You shouldn't actually need to pair at all. Might take a while to appear though...
If you didn't pair before try do that (even though it shouldn't be necessary, some drivers treat this slightly differently).
There is a new version of the windows up released, major changes.
There was a dependency that I was waiting for that wouldn't allow an update to be released until it itself was updated.
On the Windows 10 app, I recorded a lot of data and then saved to a csv file, which was created OK. However, when I later went back to look at the log file I found it to have zero size and was empty. On a second attempt following the same steps with the same amount of data (about 10 minutes worth), the file was created successfully. So I don't know how to reproduce the problem.
OK, I just reproduced it a second time. I was running the app on Windows 10 and recorded several minutes of data (10 minutes or so). Then I tried to save it to a csv file. On the first attempt it produced a file with zero bytes. However, a second attempt succeeded.
Looking into this, i the mean time are you able to try the latest update?
It is still processing and might take a day to appear everywhere in the store.
I will see if I can try the latest update some time in the next few days.
I will see if I can try the latest update some time in the next few days.
Awesome, I've been testing the file save issue for every 10 minutes for over an hour. No failures, has there been any common factors in the issue?
Awesome, I've been testing the file save issue for every 10 minutes for over an hour. No failures, has there been any common factors in the issue?
I can't think of anything special except I may have cleared the history once or twice before collecting the data I wanted to save. Everything looked right about the save operation except the file on disk was empty afterwards.
Awesome, I've been testing the file save issue for every 10 minutes for over an hour. No failures, has there been any common factors in the issue?
I can't think of anything special except I may have cleared the history once or twice before collecting the data I wanted to save. Everything looked right about the save operation except the file on disk was empty afterwards.
Did it take a second to save, app freeze for about a second?
Did it take a second to save, app freeze for about a second?
I don't recall, I'd have to try again.
Update for the windows app will now be automatically installed on client machines.
How is that iOS update coming? The current version expires in 15 days. I will be traveling in 10 days and may have to take an AC current source with me for testing unless I can test the new version (with the '3' removed) before then.
I will carry the 121GW with me in any case...
Thanks!
How is that iOS update coming? The current version expires in 15 days. I will be traveling in 10 days and may have to take an AC current source with me for testing unless I can test the new version (with the '3' removed) before then.
I will carry the 121GW with me in any case...
Thanks!
iOS version is on the app store
How is that iOS update coming? The current version expires in 15 days. I will be traveling in 10 days and may have to take an AC current source with me for testing unless I can test the new version (with the '3' removed) before then.
I will carry the 121GW with me in any case...
Thanks!
iOS version is on the app store
OK, I got iOS App v1.7 from the app store and still saw the AC mA problem with firmware 1.22.
Now I have upgraded to firmware 1.26 and I am still seeing the problem.
1.0011 mA on meter reads 100.11 on iOS app
or
0.983 on meter reads 0.0983 on iOS app
depending on range.
DCA does not have the problem
Do you need further diagnostics on this?
Thanks.
Yes, it happens on the Windows app too. Meter shows "AUTO AC 0.0798 mA", app shows "AUTO AC 7.98 mA".
Now the Windows app spontaneously fixed itself, but the iOS app still shows the wrong decimal place.