|
RoboRIO Comms issues
Our team has been having issues with 2 of our 3 RoboRIOs this year, when the first one did it we blew it off because we had 2 more.
Recently our last roboRIO started doing the same thing as the other one, and our only good roboRIO is bagged with the bot.
The RoboRIO seems to be running fine, we can SSH into it from USB, web dashboard works over WiFi and USB, NetworkTables runs fine (it even passed GRIP numbers from the kangaroo plugged into the bridge to the driver-station PC on WiFi and USB), and we are even able to upload code and see that the code is running (program logs, on both WiFi and USB). The only issues are that we cannot connect to the RIO with the FRC Driver Station (both the normal comms light and the diagnostics one) and that we cannot image the RIO no matter what connection type we are using.
We have tried our normal driver-station laptop (Win10, firewalls off, USB, Ethernet and WiFi). We also tried our kangaroo (Ethernet to the same bridge as the RIO), and we tried our older driver station laptop (Win7, firewalls off, USB and WiFi).
EDIT: We were also had the Robot Radio light on, and were able to log into the radio to see that it was there. We are using an old DLink for the radio on our second bot because we fried our second new bridge.
Last edited by FRC2501 : 29-03-2016 at 10:45.
|