OWON SDS7102V - Ethernet port - Page 1
Forum section: electronics / testgear

author: akis
author_rank: Frequent Contributor
timestamp: September 26, 2013, 04:59:02 pm
content: Hello, I have connected the ethernet port, and I can ping the Owon from the network, however when I try to connect to it with the "DS-WAVE" application, version 2.0.8.17, it does not "see" the Owon. I have set the correct LAN settings of course. Has anyone else got it to work over the ethernet?

author: AndrejaKo
author_rank: Frequent Contributor
timestamp: September 26, 2013, 05:22:32 pm
content: Works fine for me. I know that some people had problems with bogon filtering, since Owon seems to be using wild MAC addresses, but if you can ping the scope, then your problem isn't related to that.Did you double-check everything on the scope and the program?Also what happens if you try to ping the scope on its port (ping Ipaddress PortNumber) or if you try to telnet to it? My scope freezes for a couple of seconds when that happens, so this is how you'll know if communication to the scope works

author: akis
author_rank: Frequent Contributor
timestamp: September 26, 2013, 08:08:51 pm
content: I can ping it, and I can telnet to it. When I telnet to it it does not send me anything. The oscilloscope software cannot connect to it, I mean I am expecting to see the waveform on my PC screen, but nothing, and then I get errors like the attached.

author: Mr Simpleton
author_rank: Unknown
timestamp: September 26, 2013, 08:29:15 pm
content: Do you have a firewall enabled?? If so, try to disable and then reconnect.

author: AndrejaKo
author_rank: Frequent Contributor
timestamp: September 26, 2013, 09:01:52 pm
content: I just tried running the software with scope disconnected and noticed that for me, progress fields are actually blank while you get 0 KB. Try running the software with the scope disconnected and see what happens. If the 0KB doesn't appear, it could mean that the communication between the software and the scope starts, but then later on fails at certain point.What's the version number of your firmware?Also one idea is to try with an older version of software. Previous version is available on owon.co.uk. An even older version is available at owon.ca.

author: akis
author_rank: Frequent Contributor
timestamp: September 26, 2013, 10:10:39 pm
content: Same with an older version 2.0.8.11 - nothing happens.One question: did you have to change the default IP settings on the scope or did you use the default ones? I had to change mine because my home network is on 192.168.0.x and not on 192.168.1.x which is the default. Maybe something inside the scope and/or software expects to find 192.168.1.x even though I have changed it on the scope and on the application.Edit: whilst trying the old version, 2.0.8.11 I managed to download one curve, I am not sure how it happened. It was not a real-time feed, I think it downloaded something and then it stopped and then it displayed on the screen the file it had downloaded. I cannot get it to do it again.And I was rather hoping for a live feed

author: AndrejaKo
author_rank: Frequent Contributor
timestamp: September 26, 2013, 11:36:28 pm
content: I usually use default values.I did some testing and I've noticed that if my computer is connected to scope by a wired connection, everything works fine, but in case of wireless connection, software won't download the data. I don't have drivers capable of capturing wireless traffic on my computer at the moment. I'll see if I can set them up tomorrow and do some probing.Another thing I've noticed that may be problematic is that the scope seems to be set to 10 Mb/s and full duplex and at the same time doesn't support duplex auto-detection. Problem with that is that other side which does support auto-detection will assume that scope is running in 10 Mb/s with half-duplex.I did some packet capturing in Wireshark and I get some problems with missing and duplicate ACKs when trying to transfer full memory of both channels. If I remember correctly, those are common symptoms of duplex mismatch.I really have no idea why this wouldn't work over wireless network. I'll see if I can dig up something about method of operation of the PC program and try to figure out if the issue could be at its side.

author: akis
author_rank: Frequent Contributor
timestamp: September 27, 2013, 03:46:21 pm
content: I can ping it over the wireless but cannot download.I cannot ping it over ethernet over homeplug devices.?!!!! arp cannot even see it. I added it manually "arp -s 192.168.0.85 xx-xx-xx-xx-xx" and pinged it a few times then nada. Crap.I can ping it over normal ethernet.I can download over ethernet cable.On retrospect I should have saved for a good quality scope, the Owon was not exactly cheap anyway.

author: AndrejaKo
author_rank: Frequent Contributor
timestamp: September 27, 2013, 06:34:03 pm
content: I agree that it isn't cheap at all. In fact, if I were in the US, I could have gotten a Rigol DS2072 for the amount of money I payed for Owon...I wonder if their software is doing something with ARP resolution in the background. From what I can see, the scope doesn't reply to ARP requests at all. I tried sending it some requests with ARPING and it isn't replying. Could it be that PC software is doing something strange with ARP and that's failing in case of non-wired Ethernet?

author: TomC
author_rank: Frequent Contributor
timestamp: September 29, 2013, 01:31:54 am
content: I'm not sure if this will help, but my router originally didn't let me reserve an address for the Owon because of the Owon's default MAC. I had to change the Owon's MAC for it to finally work, see attached image. I don't remember what the original MAC was when this happened.I'm also running the latest firmware version, my scope displays 3.2. This upgrade was recently posted at the Owon site, but for some reason it has the same name (version 3.3) as the previous version released some time ago. Although not advertised the new version has LAN interface fixes. For example, before this upgrade I couldn't capture images via LAN.I also just posted the results of an Arp and Ping test via wirelesshere.

author: lemon
author_rank: Frequent Contributor
timestamp: September 29, 2013, 07:57:57 am
content: Quote from: TomC on September 29, 2013, 01:31:54 amYeap, the last two fws have the same display 3.2 but if you see the properties of the two installers files, you'll see as modified day "Thursday, March 28, 2013, 10:52:06" and "Wednesday, August 21, 2013, 09:22:06" respectively.It seems Owon does some minor improvements to this fw at the end of August.