Each interface should have it's own ip-address so who would return should not be a problem. How ever I think implementing "services" on multiple interfaces is not trivial. So I can imagine only one (primary) interface get the services behind them. Maybe the first that gets an IP address, hence the difference between dhcp/static. But thats guessing, with a perfect implementation both interfaces could be used.
However I even experienced issues using only ethernet, like a SCPI session that gets broken, when using the web service simultaneously. (Solution: close the web-page)
As you say, all depends on the services/app running in the scope. I don't believe Siglent would go to the effort of devising such a thing just because someone wants to use both interfaces in the same network.
Each interface should have it's own ip-address so who would return should not be a problem. How ever I think implementing "services" on multiple interfaces is not trivial. So I can imagine only one (primary) interface get the services behind them. Maybe the first that gets an IP address, hence the difference between dhcp/static. But thats guessing, with a perfect implementation both interfaces could be used.
However I even experienced issues using only ethernet, like a SCPI session that gets broken, when using the web service simultaneously. (Solution: close the web-page)
As you say, all depends on the services/app running in the scope. I don't believe Siglent would go to the effort of devising such a thing just because someone wants to use both interfaces in the same network.
But it would be nice the UI would give insight in what interface is active, or let the user select one.
But it would be nice the UI would give insight in what interface is active, or let the user select one.
It does and always has.
Bottom right corner of the display shows when LAN or WiFi is selected
and if they each are active.
The WiFi signal strength indicator will be grey'ed out when out of range and the LAN indicator shows a small red x when not connected.
But it would be nice the UI would give insight in what interface is active, or let the user select one.
It does and always has.
Bottom right corner of the display shows when LAN or WiFi is selected and if they each are active.
The WiFi signal strength indicator will be grey'ed out when out of range and the LAN indicator shows a small red x when not connected.
I don't have the adapter and I won't get one either. Happy with ethernet. But I can imagine it doesn't show which of the interface actually works. (Assuming only one can)
Having an extra indication and a guide in the manual to solve the above issue would be
I think I figured out what my issue is. I have a router and access point using the same SSID and the scope does not like seeing two of the same SSID. All of my other wireless devices on the network has no issues with two of the same SSID. If I power off the access point the scope has no issues.
To All Thanks,
Mike
But it would be nice the UI would give insight in what interface is active, or let the user select one.
It does and always has.
Bottom right corner of the display shows when LAN or WiFi is selected and if they each are active.
The WiFi signal strength indicator will be grey'ed out when out of range and the LAN indicator shows a small red x when not connected.
I don't have the adapter and I won't get one either. Happy with ethernet. But I can imagine it doesn't show which of the interface actually works. (Assuming only one can)
It shows one or the other, only the active one (one selected) not both.
Having an extra indication and a guide in the manual to solve the above issue would be
Yep the manual should show the WiFi indicator as a example for users and I'll ask Siglent to include this in their next manual update.
This screenshot shows the WiFi ON but the signal indication is greyed out due to being out of range from my WiFi connection. (in another building)
Seen next to the USB drive indication.
Good that you found the issue
Also
for the good indication of what's active.
I think I figured out what my issue is. I have a router and access point using the same SSID and the scope does not like seeing two of the same SSID. All of my other wireless devices on the network has no issues with two of the same SSID. If I power off the access point the scope has no issues.
To All Thanks,
Mike
I was able to get the scope to work with both the router and access point power up and using the same SSID. The original settings had the access point using channel 4 (the weaker signal for the scope) and the router using channel 11 (the stronger signal for the scope). To get the scope working I changed the channel setting for the router to channel 1 (so the scope uses this channel first) and the access point to channel 6.
Mike
Why do you think IP 192.168.1.168 is scope?
Why do you think IP 192.168.1.168 is scope?
Look at the IP at the top of the photo and in the LAN Configuration.
But you are using ETH and WIFI, right?
While trouble shooting my wireless connection issue I found something interesting. If you have the scope set for a wireless connection and using a static IP it also gets a DHCP IP. See photos below, scope is set to a static IP of 192.168.1.212 also the scope is getting a DHCP IP of 192.168.1.168.
(Attachment Link)
(Attachment Link)
(Attachment Link)
(Attachment Link)
(Attachment Link)
That page is for the LAN config, which is the ethernet cable. the 168 address will be for your WiFi, therefore 2 addresses.
No, just WiFi, the Ethernet is not connected
When I was playing around checking the scope’s WiFi vs Ethernet capabilities, I seem to recall discovering that you could only ever have one or the other active, and I had to use different IP addresses for each.
This may have changed with the latest firmware, but worth checking out.
The remote response on the browser was always so much better over Ethernet, I only rarely use WiFi.
No, just WiFi, the Ethernet is not connected
Yep, cause you have static settings for each.
I have only the WiFi enabled set to a static IP of 192.168.1.212 and no Ethernet cable connected. With this setup I can ping both IP 192.168.1.212 and 192.168.1.168 also I can navigate to both IP's with a Web Browser.
Based on your last info, my only conclusion is that the scope must be routing the IP packets between both IP stacks internally.
If you get me a 3rd IP than I'll be amazed!!!
Based on your last info, my only conclusion is that the scope must be routing the IP packets between both IP stacks internally.
If you get me a 3rd IP than I'll be amazed!!!
That just might be possible too !
2 saved settings then turn DHCP ON to get a 3rd auto negotiated IP but don't Save it.
After thinking about it maybe the USB wireless adapter is getting the DHCP IP 192.168.1.168 and the scope is using the static IP of 192.168.1.212. Also the USB wireless adapter has its own MAC address different from the scope.
After thinking about it maybe the USB wireless adapter is getting the DHCP IP 192.168.1.168 and the scope is using the static IP of 192.168.1.212. Also the USB wireless adapter has its own MAC address different from the scope.
I thought you already knew that! The question is you accessing both IPs with just one connection. The scope behaves as having an internal network switch, as you configured both interfaces in the same network. Nice.
After thinking about it maybe the USB wireless adapter is getting the DHCP IP 192.168.1.168 and the scope is using the static IP of 192.168.1.212. Also the USB wireless adapter has its own MAC address different from the scope.
I thought you already knew that! The question is you accessing both IPs with just one connection. The scope behaves as having an internal network switch, as you configured both interfaces in the same network. Nice.
Nope, it can only use one or the other not both at once.
Nope, it can only use one or the other not both at once.
Yes, but through one interface you can "see" the other...
Which poses a problem: if you have all the network configured with DHCP, connected to the scope only via WIFI, but you have a static IP in the scope's ETH interface (as seems to be the case), one can have a problems of collision between IPs. Must choose DHCP pool with care or have both scope's interfaces configured with DHCP.