Hello everyone! Sorry if this question has been asked before, I tried searching and didn’t find an issue like mine. Basically, what I am trying to do is have the RTKs connected to the network through the router, instead of through wifi. The reason is because the rover itwould have to operate at distances of up to 2km, so there is pretty much no way that the Reach’s wifi antenna can connect that far. The Reach on the Rover can probably connect, since the router is on the rover, but the base station one won’t be able to.
Reachview version: v2.10.0 (latest)
Now, I have gotten it all working through wireless. The base and rover RTK’s can communicate with each other through the network (and the rover RTK receives correction info). Through this setup, I could also use TCP to read the raw coordinates, which is also a necessity for automation purposes. I though that I could just “forget” the wifi networks, and use an ethernet adapter (USB OTG cable to USB to ethernet adapter, D-Link DUB-E100). It worked fine at first, but as soon as the RTK is rebooted, it keeps giving me “connection refused” errors, until I connect to the hotspot, load the GUI using 192.168.42.1, and then reconnect to my router. After that, I am able to use all the functions normally through ethernet.
Static IP is set through a router configured with DD-WRT, if it makes any difference.
Your step by step actions:
The actions that I took were rebooting the router, rebooting the Reach, trying to ssh into it (no luck), pinging it (no luck, times out). This occurs on both the Reach’s as well.
If using any additional hardware please provide exact make and model:
- The included OTG cable and the DUB-E100 D-Link ethernet adapter.
I am not as experienced with Linux and such, but I am learning as I am going. I was thinking maybe I am having this issue is because the adapter is not it’s default network device (the WiFi adapter is), so it doesn’t accept connections through it until a connection through the default one is established, in which case all I would have to do is set the OTG adapter as default. In the future, I would also disable wireless on this altogether to save power, which I know how to do (in theory). But, I cannot do that until I am able to connect to the Reach through the ethernet adapter at all times, so`any help would be appreciated! Let me know if more information is required, and apologies if I made a mistake (such as putting it in the wrong subforum)
Edit: Turns out I was wrong, even connecting to the hotspot and navigating to 192.168.42.1 gives connection refused errors. After a while, it magically starts working again, so I’m not sure what’s going on here. Connection to 192.168.42.1:5000 does bring up the WiFi page though, but that doesn’t really help me.