GWInstek OpenWave LAN Setup?

[TimNJ]

Hi everyone,

I'm trying to set up OpenWave remote monitoring over LAN on my GDS-2000E series oscilloscope. In my experience, these types of programs are always a pain in the butt to get working. Maybe it's easier on something from Keysight or R&S, but I've also had my fair share of woes with LAN support on Agilent equipment in my college lab.

Has anyone got this to work?

1. I've got my scope attached to my LAN via an 8-port switch
2. I turned on DHCP and socket server on the scope menu, as per the README
3. I logged into my router at 192.168.1.1. I see the oscilloscope on the network as 192.168.1.39.
4. When I try to run the program from the command line, it says "No such file or directory "license.txt"", even though license.txt is in the same directory with it and I can call it from command line or opening up in explorer.
5. You can also run the .exe by double-clicking on it in explorer. The program launches, appears to find the license file, but says "Device not found!" Maybe it defaults to USB connection or something.

Any tips for configuring the scope? There are options to input the domain name on the scope. In the past, I've had some issues with Workgroups and domains under Windows 10 and getting everything to show up on the network.

I know most people don't usually bother with LAN, but if you have, I'd love to know how you got it working.

Thanks,
Tim

https://github.com/OpenWave-GW/OpenWave-2KE/blob/master/README.md

[TimNJ]

Alright, step #1, don't be a dumbass and learn some basic command prompt skills.

I thought by copying the OpenWave directory into the command prompt it would automatically 'cd' (change directory) to that directory. Not the case. Also, I saved the file in the root of a separate drive, so maybe that messed it up. Have to use the /d switch to change drives, as in" cd /d D:\"

Now it works...no need for domain names or anything like that, just the IP address + socket as in the README.

But, with 4 channels the update speed is horrendous. It appears to be sending every data point recorded, which is usually preferred, but seems to really kill the update rate over LAN. The program basically freezes up every time it's trying to make an acquisition. Takes 5 or 10 seconds to acquire 1 channel of data. Multiple by 4 if you want all channels.

I basically just wanted to check if my scope was triggered. (Trying to check for a spurious event, but don't want to sit there for hours on end.)

[TimNJ]

Update: The update rate can be greatly improved, almost real-time update, if you switch from Raw Data mode to Image mode. In image mode, it just takes a PNG screenshot a few times a second and refreshes the GUI. Apparently it's much easier to send a PNG than 24Megapoints of 10-bit data. Who knew.