Siglent SDS1204X-E Talking to it via LAN Port without a Network - Solved - Page 1
Forum section: electronics / testgear

author: daveyk
author_rank: Frequent Contributor
timestamp: June 17, 2019, 06:59:19 pm
content: Howdy,If I hook my Siglent SDS1204X to my network via a cable to a switch, I can get to it perfectly by typing in its IP address in a browser.Now, If I hook the scope directly to my laptop, I can not figure out how to talk to it via the LAN cable. I tried a twisted pair lan cable too. I've tried setting the IP address in IP4 settings for the port to something like 192.168.1.200 when the scope's address is 192.168.1.210. I haven't had luck.If I use just USB, I can not get screen shots from the scope. I always get capture errors. I do not have that problem with LAN, but without an existing network, I don't think you can talk to this puppy.If yaa all know how, please pass that on.ThanksDave

author: daveyk
author_rank: Frequent Contributor
timestamp: June 17, 2019, 08:01:38 pm
content: Okay, I had done it over and over again, and could not get it to work. I turned scope off and re-booted it, and got it to work under this configuration:Use a twisted Pair/NULL Network cableManually Configure the IP4 settings of the network adapator to a hard IP address of: 192.168.1.210Set the scope address to: 192.168.1.220Then us Chrome and type in web address of 192.168.1.220I also have the wireless network adapter turned off in the laptop at same time. I found with Win7 64 bit, that if the wireless is on and connected to the network, chrome will not look for 192.168.1.220 over the wired network cable. If the wireless is off and the computer not connected to the network, I can connect to the scope. I can then also turn the wireless back on and connect to the network and go to web sites and still stay connected to the scope. I can close the tab, and reopen a tab and still connect to the scope.That's weird, but if I follow that initial connection order, it does seem to work fine. I do seem to note, that if I turn off the wireless, the update rate of the screenshot seems to increase. That is not important. As long as I can see a good waveform (I always use AVERAGE acquire mode as I do noting high speed), that is all I need. I can hit print-screen, paste the shot in to Paint, select just the a-scan area I want, copy it and paste in to my Word certification documents.In the meantime, while fighting that, I tried USB on two separate computers. I could display a trace but Siglent's EasyScope software could not transfer a screen-shot via USB.I'm going on a field job this week and taking this scope (along with my Tek) as a novelty/board-um relief/Cool looking scope. It did get ISO17025 certified without issues a month ago, so I should try it. I love my TEK TDS3032s, and they do work great, but they do not look as modern as this cheap little Siglent. The cheap Siglent is more impressive than a $10K Tek scope to the layman. When doing a calibration run, show is half the job; impressive paperwork is a quarter and changing their calibration sticker is the rest.

author: tautech
author_rank: Super Contributor
timestamp: June 17, 2019, 08:14:06 pm
content: Workaround for direct LAN connection. (no router or switch)PCOpen cmd box.Type 'ipconfig' and note IP, Submask etc.DSOLAN = ON (WiFi OFF)DHCP = OFFEnter LAN settings and insert PC's IP +1 (eg 192.168.0.23 becomes 192.168.0.24)Mirror other LAN fields.SAVEPCIn browser now enter the new IP for the DSO (PC's IP +1)ORInstall EasyScopeX and NI VISA Runtime for the EasyScopeX utility......some 300 MB install.

author: daveyk
author_rank: Frequent Contributor
timestamp: June 17, 2019, 08:21:46 pm
content: Hello there Tautech,"PCIn browser now enter the new IP for the DSO (PC's IP +1)"I found I still needed a null modem LAN cable (twisted pair). Not many people probably have those. I made my own some time back. I use it with an instrument that I work on that communicated to software in my computer without going through a network. Other than that, I pretty much did what you said. I think re-booting the scope after setting the IP address helped.I do have NI VISA installed. I use that along with Agilent Connection Expert to talk to my other instruments. Connection expect could not see it, but I didn't try it after fixing the direct connect issue. At the same time Easy Scope could not see it either. I should try both now!Another issue is the computer that I needed to this to work on in my M4800 with 64 bit Windows 7. Everything, communications wise (NI VISA, GPIB, RS232, etc.,) seems to be a pain in the ass to get to work with the 64bit OS. I'll have it all working perfect, then microsoft will upload a Windows 7 update and then nothing works again. My bench computer is 32 bit and I do not have that problem.Okay Update: Agilent Connection Expert still does not see it, not does Easy Scope. Google Chrome does and that gets me working.Dave

author: tv84
author_rank: Super Contributor
timestamp: June 17, 2019, 08:25:56 pm
content: I don't know if I understood correctly your problem.You have to assign different network/mask adresses to your LAN and WLAN interfaces.You can't have a 192.168.1.xxx in LAN and 192.168.1.xxx in WLAN interfaces (all using 255.255.255.0 mask).You must, for example, use 192.168.2.xxx in LAN interface (with 255.255.255.0 mask). With this config, you can have both interfaces running. Of course, the scope must have also a 192.168.2.xxx address.

author: tautech
author_rank: Super Contributor
timestamp: June 17, 2019, 08:26:38 pm
content: NO crossover cable required but yes it should work with one.I've used my above method with W7 or W10.

author: daveyk
author_rank: Frequent Contributor
timestamp: June 17, 2019, 08:36:41 pm
content: "You can't have a 192.168.1.xxx in LAN and 192.168.1.xxx in WLAN interfaces (all using 255.255.255.0 mask)."Thank you TV84. I am not smart enough about networks to know that - lol. I mean that for real, not sarcastic in the least - lol. That helped me a lot. I changed the scope to 190.168.1.220. I still have to use the twisted pair lan cable, or so it seems. I wouldn't think most would have one of those? If I carry a small switch with me, then no I don't need a twisted pair cable, just a regular LAN cable then.Doing this also probably isolates the LAN based test equipment from the network and the innerwebs when using a home? I read somewhere that keeping this scope on the network poses a security risk? I though the router and all its security mitigated that anyway?Dave

author: daveyk
author_rank: Frequent Contributor
timestamp: June 17, 2019, 08:40:06 pm
content: "NO crossover cable required but yes it should work with one."Okay, I just tried and its fine now with a standard LAB cable. TV84 had suggested using a different network address from my main network address (So I changed from 192.168.1.220 to 190.168.1.220), and I think that helped a lot.I did find and confirm that if you change the IP address in the scope and save it, that change only takes effect after shutting down and re-booting.Dave

author: daveyk
author_rank: Frequent Contributor
timestamp: June 17, 2019, 08:45:31 pm
content: PCOpen cmd box.Type 'ipconfig' and note IP, Submask etc."I still find it is probably better for the LAN port on the PC to change the IP4 properties to force it to a network address of your choice. Otherwise, couldn't it automatically change the next time you had wire connect to your network? Yes, what I am talking about has to be done every time I use the port on the M4600, but on the bench computer there are two network ports. I can dedicate one to a test equipment net now.

author: tv84
author_rank: Super Contributor
timestamp: June 17, 2019, 09:00:46 pm
content: Quote from: daveyk on June 17, 2019, 08:36:41 pmYou're a little better protected this way.The bottom line:1. use static configuration in the LAN interface and scope. Use the DHCP for your WLAN network as you must be using.2. use different networks for both interfaces 192.168.xxx.xxx (assuming you set 255.255.255.0 as the usual mask).3. Use the crossover cable since it seems your PC LAN port doesn't do the automatic switching (? ? ? old PC...). If it did you could use any patch cord.