| Products > Test Equipment |
| Siglent SDS5034X web server Instrument Control interface not working |
| (1/5) > >> |
| MPech:
Hello, I got a new SDS5034X scope with 500 MHz promotion upgrade. Everything seems working fine, the only issue is that I cannot get the remote control panel using the web browser interface working at all. I tried all the resets to factory defaults, but still not solution. IP Config settings is at Automatic, the modem/router has the VNC 5900 port forwarding enabled. I can do everything from the web interface, send SCPI commands, change LAN configuration, but Instrument Control tab is empty and only the 4 arrow icon to go to full screen mode is present. I tried Chrome, Edge, and Waterfox Classic browsers with no functionality difference in between them. I also tried to use TightVNC and RealVNC viewers to connect to the scope directly but in both cases the VNC connection was refused or timed out. It looks like the VNC server is not running on the scope. TightVNC reported that "No connection can be made because the target machine actively refused it". I also tried the EasyScopeX, even though its compatibility with SDS5000X series seems not to be advertised by Siglent. It works well, I can do everything, the only thing which does not is when I tried the Virtual Panel button -- the response was "The feature is no supported!" Did anybody get the remote control panel working using the web browser on SDS5000X series? I have not tried to connect the Ethernet cable directory to the computer yet, I need to get the proper cable. Any help is appreciated. Thanks. Martin |
| tautech:
Welcome to the forum. It's simple enough to connect to your LAN however it's best to set the scope a unique IP rather than let DHCP give you one. So disable DHCP and use your LAN's Subnet and Gateway and assign the scope its own IP. Here I can see the scope on both a PC and iPad where I grabbed this iPad screenshot of Instrument Control via the webserver. Just enter the scopes IP into any browser and it will find it in a flash. Running 0.0.5R2 firmware here. |
| MPech:
Thanks for a reply! Setting fixed IP address made no difference. I waited with a reply until I got a crossover Ethernet cable. I tried a direct computer to scope Ethernet connection with crossover cable. Same thing. I can connect and do everything, EasyScopeX works as before, but there is just no Instrument Control showing in a browser. I am on Windows 10, tried add 5900 port to firewall rules, no help. Either something is wrong with the scope or something, more likely, with my network setup. Any help is appreciated. Thanks. Martin |
| tautech:
TBH Peer to Peer networking is a PITA however with some shagging around you can get it to work but it's not straightforward and so much simpler to have a cheap network switch near the bench and just plug it into the LAN with the scopes own IP that's maybe taped somewhere on the scope for future reference. Possibly your router settings are interfering with the connection. :-// W10 here too and been doing this stuff reliably since W7 days. Grab yourself a cheap network switch to have at the bench and connect it to your LAN and have your router do all the DHCP stuff. |
| 2N3055:
What AV program you use on a PC? Maybe it blocks something? It is very simple. Protocol used is VNC, on a standard port. It must work with any standard VNC client (no need for browser). There should be no problems. It's pretty standard stuff. So if that doesn't work, it's either you have something "firewalling" that connection or, like you said, VNC server component is not running on the scope.. ESET NOD32, for instance (and all of AV software from other manufacturers) lately have extensive protocol filtering and firewalling functionalities. Or maybe windows firewall is acting up (it shouldn't though). |
| Navigation |
| Message Index |
| Next page |