EEVBlog 121GW Software for Win & Android

[katerle]

So yesterday I asked two friends of mine in Belgium and Austria to test the install of the app from the Store. Same thing - nope.
I think it's really an EU-Problem.

@Dave: Why not pick the sideload-files on top or pack them on your Storeside of the 121er. The side needs also a update of the outdated links.
Good idea?

EDIT/OT: My friend in Austria said, as it's in fashion this time, they will make a crowdfunding to buy Australia, because it's nearer to Wien then to the Moon and the names are so similiar... 

[katerle]

The Meter has arrived...

... Meteor and Store-App are working... 
The only thing I don't see are the buttons. Any ideas?

Thanks to all of you!

EDIT: The buttons are there, but they are not visible. I can click and they react. 
Do I have to paint the buttons on the screen?

[Kean]

OK, I checked again on the PC that I side-loaded and the buttons look OK.  I thought maybe the side-load may have missed some images or translation...

Did you install all three Appx dependencies?

The files I installed in order were:

• Microsoft.NET.Native.Framework.2.1_2.1.27427.0_x64__8wekyb3d8bbwe.Appx
• Microsoft.NET.Native.Runtime.2.1_2.1.26424.0_x64__8wekyb3d8bbwe.Appx
• Microsoft.VCLibs.140.00_14.0.33519.0_x64__8wekyb3d8bbwe.Appx
• EEVblog.EEVblog121GW_1.4.65.0_neutral_~_882f7gxbm7ae0.AppxBundle

[katerle]

Yes, exact those four files with exactyl the same names. No error by any installation. On W10 I also have no buttons visible.
I will uninstall and install again. Intel-Graphics, newest driver. I also installed with thw winget-script-cli and the same. Three PCs, no buttons to see. Mysterious... 

[Kean]

The PC I tested on was also Intel graphics (older HP box).

Are all three PCs are running Windows install with German as default language?
I doubt it was tested on anything but Australian English, and comma/period numeric separators.

[katerle]

Yes, all three are german language and metric.
I've just un- and reinstalled in you order, the same.
I don't think the app needs Java or so?

[katerle]

You may be right with the language, see screenshot, yellow circled...

EDIT: So I will take an obsolete machine and install W10 in English (US).
I only have to look for a english keyboard and mouse... 
I can live without the buttons, but I want to see what's the reason, we are nearly 450 Millions of people here in EU (Without UK, Turkey and Suisse).
And they all have a right to see the buttons... 

[Micah Lindstrom]

It's not just an EU issue, I'm in the US with computer set to English (US) and don't see the buttons either. I'm running Win11 24H2 and installed from the Microsoft Store. When I clicked the app link from the 121GW page, I got a popup saying this was the UK store and did I want to switch to the US store. I'm 90% sure I switched to the US store.

That's a good find that the buttons still work, they're just invisible. I didn't even think to try clicking where the buttons ought to be.

I thought it might be related to display scaling. But no, even at 100% scaling I still don't see buttons.

All those four packages to install are only if you're trying to sideload right? If you can install from store, that should get everything already?

[katerle]

Jepp, the four files are only for sideloading the App. Installed from the Store everything will be installed, also the needed dependency Files.

I'm working for over 30 years in the IT now, but I'm no software-engineer.

Fact by now is, it has nothing to do with language, country, Store or not, Win-Version, Graphics, scaling, resolution.
What could be the reason? 

[Micah Lindstrom]

I tried sigrok smuview as well to no avail. Tried both 0.0.5 (current released) and 0.0.6 (beta), but nothing appears when I try to scan for it. I also tried pairing the meter to my computer and that didn't do anything either.

• https://www.sigrok.org/wiki/SmuView#Windows_installers_2
• https://github.com/knarfS/smuview/releases/tag/continuous
• https://www.sigrok.org/wiki/Sigrok-meter
• https://github.com/knarfS/smuview/issues/17

[Kean]

I took a quick look at sigrok, but it doesn't seem to support BLE connections natively which makes it tricky to use with the 121GW.

There is mention of a python script that can be used with an ESP/nRF device for a BLE to UART gateway (or natively on some platforms), but I don't think that will work on Windows.
https://www.sigrok.org/wiki/EEVBlog_121GW
https://sigrok.org/gitweb/?p=sigrok-util.git;a=blob_plain;f=util/eevblog-121gw/eev121gw-ble-uart-relay;hb=HEAD

Too much mucking around for me...

[katerle]

I also tried to pair the GW with a PC. That's no problem, but the GW ist found under BT-Devices.
It got's no com-port assigned.
As @Kean said, there is a possibility in sigrok to link it to a com-port via python script.
But that's IMHO not worth the action.
You need a platform on which sigrok supports BLE directly...
I think the finest solution is to make the buttons in the App visible, only how?
Holy cow... 

[PA0PBZ]

I had a look at the multi-platform source but all I found was a headache 
It looks quite complicated and the fact that it uses Xamarin which is no longer supported in Visual Studio doesn't help either. I think that creating a new version just for Windows would be easier but I don't have a 121GW and not planning to get one.

[katerle]

You're speaking from the Store-App or sigrok?

[PA0PBZ]

You're speaking from the Store-App or sigrok?

The Dave App: https://gitlab.com/eevblog/app-121gw
I guess this is the store App.

[joeqsmith]

I had put together some software for the 121 using LabView.  I thought a few others had made similar applications.

From what I remember, I ran into a few snags along the way but most were self inflicted.  I had tapped into the serial communications to the BLE controller so I could sniff both sides with the scope and PC.   

Seems like once I sorted out my problems, it worked fairly well.   

[katerle]

You converted the units BLE over cable to FTDI in normal BT with the possibility to assin a com-port?
And then write a module embedded in labview?
Good idea, but you have the cabels out of the meter. And labview is AFAIK no freeware...

[joeqsmith]

You converted the units BLE over cable to FTDI in normal BT with the possibility to assin a com-port?
And then write a module embedded in labview?
Good idea, but you have the cabels out of the meter. And labview is AFAIK no freeware...

There was only BLE.   The wired cable was to sniff the data going to the BLE controller.   Basically I wanted to make sure that the BLE chipset was not changing the data. 

After National Instruments (NI as they now identify as) changed to a rental license and attempted to extort their user base,  I now consider LabView a dead end path.   That said, I believe they still offer their free community edition.   I have never installed it and don't know what limitations it has if any.   Also, depending on your location, there may be restrictions.   If you have never used it, I don't recommend you start now.  Better to stay with what you know. 

My LabView example shows that custom applications for the 121GW can be written without too much effort.  It seems others had done something similar using different languages.   There is a lot of information on this site about the 121GW.   You may want to spend a little time researching it. 

I did use their software with my Windows 10 tablet.   I am sure I have this software archived if it would help.  Guessing it would be the same that is available today.   

[katerle]

Thank you Joe,
but I think I let my fingers away from labview. That's not my business and I do not have the time to work me in.
It is like it is, I have to live with what I have regarding the 121GW. So it's a nice meter and most Software works.
Maybe when there is time I will research the problem with the unvisible buttons...

@all: Have a nice week

[joeqsmith]

EDIT: The buttons are there, but they are not visible. I can click and they react. 
Do I have to paint the buttons on the screen?

I can live without the buttons, but I want to see what's the reason, we are nearly 450 Millions of people here in EU (Without UK, Turkey and Suisse).
And they all have a right to see the buttons... 

I think the finest solution is to make the buttons in the App visible, only how?
Holy cow... 

Thank you Joe,
but I think I let my fingers away from labview. That's not my business and I do not have the time to work me in.
It is like it is, I have to live with what I have regarding the 121GW. So it's a nice meter and most Software works.
Maybe when there is time I will research the problem with the unvisible buttons...

@all: Have a nice week

I have no idea what these buttons are that you keep referring to.   I wonder if you are thinking that the application somehow has control over the meter.   

BLUETOOTH
To enable Bluetooth communications, hold the “1ms PEAK” button until BT is displayed on the LCD.
Ensure that Bluetooth is enabled on the host device before running the appli-cation on the remote computing device.
The multimeter will continue to functional as normal in Bluetooth mode, but the display data will be transmitted via the Bluetooth connection.
To disable Bluetooth mode press and hold the 1ms Peak button until BT is not displayed.

You have to manually setup the meter like you normally would.  It just sends the data to the application.  There would be no need for buttons.

[katerle]

In principle you are right. The buttons are (I think four) from the eight on the meter, so i. e. you can switch hold on and off etc. Of course you can't change the range-knob.
You can click the unvisible buttons and they react, if you hit them. That means the BLE communication have to be bidirectional. It's a nice gimmick, but you can as good press them on the meter.
The interesting thing is only, why do some see them and others not, it's not the end of the world... 

[joeqsmith]

In principle you are right. The buttons are (I think four) from the eight on the meter, so i. e. you can switch hold on and off etc. Of course you can't change the range-knob.
You can click the unvisible buttons and they react, if you hit them. That means the BLE communication have to be bidirectional. It's a nice gimmick, but you can as good press them on the meter.
The interesting thing is only, why do some see them and others not, it's not the end of the world... 

Think about it.  The data is going to the PC.  Could the PC perform a Min/Max, Hold, Rel, Record without talking with the meter? 

As far as I know, the meter is a send only device.  What the software does with that data is independent. 

[katerle]

Good objection. I will try it out. I click "Hold" at the ghost-switch. When "Hold" appears on the meter, it has to be bidrectional, right? If not, the SW does it itsself. I haven't observed this until now.
I'll keep you updated...

[joeqsmith]

If there is ANYTHING you can do with the software that changes one of the meter's settings, let us know.   I am not aware of anything. 

[katerle]

So sorry, but I'm right. I can click the hold and the Meter itself goes on hold etc. I can switch from AC to DC etc. and the Meters shows it. The second button from left have to be the "Mode"-Button. Also I can remote control it in a few functions...
Could someone with visible buttons post a screenshot to know whitch button is where and what?
If you still have yours, simply try it out...