We have tried since we received this device (GPS-22429) in June to figure out what was going on with the ethernet port, including swapping in known good cables, switching to known working jacks, checking things on the router, etc. I’ve spent hours with our director of networking to see if there was anything we could figure out. Nothing seems to work, and we get a simple message that the ethernet is disconnected in the serial interface to the unit (via USB). We get great data from satellites, etc., so at least that part of things is working, as are both USB ports. Wifi is not a stable enough option, since this is intended to be a base reference station.
Any thoughts on next steps? Definitive tests? We also don’t see the device from the router.
Thanks for the response. When connected to a network jack, the lights on the ethernet port on the RTK Reference Station are simply on, not blinking as I would expect with communication.
I haven’t been able to get the Config via Ethernet to work yet, but I think I need to dismount the unit to properly interact with the buttons to get it to the right state. Were you thinking about a direct connection over the network cable between the unit and a computer? Or through a router?
No whitelisting requirement - and I was working with the Networking engineer who set up our network at our institution, so I’m doubtful that’s an issue. He even set up our DHCP to provide the MAC address of the unit with a known IP address when it connects (we do this frequently for devices that need a stable IP), but we see no sign that it’s communicating.
Please post a screenshot of the Ethernet menu. It should look something like this:
Please also post a photo of the OLED. Do you see a scrolling IP number and Ethernet icon?
Please also let us know which version of RTK Firmware your unit is running. It flashes up on the OLED when you turn the unit on. You can also find it when you open the serial menu:
To start Config via Ethernet, you need to select “Cfg Eth” from the OLED menu, using the MODE button. Please follow this link and scroll down to MODE Button.
Please also see the Tried and Tested Configurations section. The golden rule is: is you don’t need Bluetooth, turn it off. It saves a load of RAM.
I am wondering if Ethernet is not starting because nothing actually needs Ethernet? Certainly the newer RTK Everywhere Firmware (which runs on our newer RTK products) only starts Ethernet when it actually needs it: e.g. for NTRIP or NTP. Starting NTP would be a good way to test if Ethernet is working or not. If that fails, i.e. you don’t see/get an IP address, then please start a return.
Thanks for the insights! I think your intuition about not-starting ethernet unless needed was right on, based on what I’ve seen now.
We were able to get to the RTK Reference Station using the Cfg Eth setting, and were able to confirm that we had access whether we had hard-coded a stable IP or used DHCP (which was set to force the same IP for that MAC address.
So I’m comfortable that we can now move on. (Although it’s still weird that the device would report that the Ethernet cable was disconnected.)
