Our roborio isn’t communicating to our planned driver station. I am able however to drive it on another computer. (both on windows 10) The driver stations are the same update, and the roborio is up to date as well.
How do I fix it?
Check that the firewall is turned off on the laptop that doesn’t work. If that doesn’t fix it, I’d open the network settings and see if anything was set up different than the docs.
Greg McKaskle
All firewalls are off and I have given the driver station special permissions through. I Can’t seem to find anything wrong with it, except for the obvious.
Click to the second tab, Diagnostics, and see whether the roboRIO is able to be pinged by the DS. If so, the green LED will be lit next to roboRIO.
If it cannot ping, then something is wrong with the network, the team number, or something in that domain.
If it can be pinged but can’t establish communications, then I’d first reboot the roboRIO, then perhaps use the web login or an ssh terminal window to see if the roboRIO still has the comms task running.
Greg McKaskle
Make sure DHCP is enabled on your WiFi/Ethernet adapter instead of a static IP. Try direct Ethernet to RIO. Make sure team number ends with -FRC (1234-frc) in DS. Can you access the RIO control panel from the browser?
Try restarting both the driverstation computer and the robot w/radio simultaneously (e.g. take everything down and restart).
Check the “Status” light on the roboRIO.