Dear TechSupport – Dear Tech Support. I purchased two RS3Ds in November, and eventually got both working [though never at the same time]. This was greatly complicated in the first place by the security protocols of the network of my university [to which I need to connect them so that students can work with them], which led to errors in assigning IP addresses and the need to reburn each of the original microSD cards. After finally getting the first shake up and running and emplaced in a basement, we discovered that the microSD of the second had failed. I replaced that one with an industrial grade card (also 8Gb) with a new burn of the operating system, and that enabled us to get the second shake up and running.
Approximately (or exactly?) at the same time in early December [perhaps you can check that… these were the only two shakes in Middelburg, the Netherlands], the first one went offline. We haven’t be able to interface with it since then, despite the fact that all of the lights on the Pi and Shake boards are behaving as though everything is ok. The one light that consistently indicated a problem is the light at the port on the other end of the ethernet cable, where it is plugged into our network. This is yellow, wherever I plug it in.
Neither of the most typically recommended solutions [power off and then on again; replace the microSD with a new one] has changed any of these behaviors [Pi and Shake lights indicate no problem; external ethernet port lights and ping attempts indicate that the shake is unreachable].
HELP!
Dear Dr Joe Walcheren, welcome to our community!
Thank you for your detailed explanation together with the troubleshooting steps you have followed.
Two questions:
- Could you confirm the meaning of the “yellow” light on the other end of the LAN cable? I am assuming that color means not connected, but I would like to be sure
- Could you, as a test, disconnect the Shake from the current location, bring it to your home, and try to see if it manages to connect from a home network?
This will help remove the college network variable and thin down the possible causes of the issue.
Thank you for your collaboration.
Thanks for your response, and sorry to have bothered you… it turns out that our sysadmin changed the reserved static IP address without letting me know. I didn’t think of asking him that question until after I messaged the help forum. Station R27FB is up and running. Hopefully it soon will be fully connected to the RS network servers. [How long does that usually take?]
Hello again,
I understand, and glad you managed to get it back up. No trouble at all on our side.
It should be relatively quick, but if your station does not reappear on StationView (or our other endpoints) in 24 hours, please download the new logs and send them to me.
I can check them and see what is not working.