RoboRio Communication Issues

[DessertDuel319]

Originally Posted by Greg McKaskle

Try using a USB cable between the laptop and roboRIO. Check that the team number enterer on the DS Setup tab is correct. Also click on the arrow next to this field and see if the robot is listed along with its IP.

If the USB cable doesn't work, in a windows cmd window, type ipconfig and see if the 172.22.11.1 interface shows up. If these things are present and it isn't working, please check the firewall again. Turn it off entirely.

If USB works, but ethernet doesn't, please check the laptop's control panel. Drill into the adapter settings and see that the laptop is set for DHCP.

Try the ethernet cable directly between the laptop and roboRIO and also try with them plugged into the robot radio.

Please report what you see and that will help identify the issue.

Greg McKaskle

Okay, so...

Ipconfig returns that 172.22.11.1 is there, along with what should be our robot IP from a wired connection. The firewall is disabled.

Neither USB nor ethernet work, for some reason DCHP was disabled but troubleshooting fixed that and now this computer can actually connect to the internet. The RoboRio has not changed in status, however.

[Greg McKaskle]

If 172.22.11.1 interface is there, can you ping 172.22.11.2? Do you have both ethernet and USB connected at the same time? Try pulling the enet cable.

Can you ping roboRIO-####-FRC.local or .lan? Does the web browser with 172.22.11.2 bring up the roboRIO web page showing you the IP settings of the RIO. That would be a good page to see a picture of.

Greg McKaskle

[DessertDuel319]

Originally Posted by Greg McKaskle

If 172.22.11.1 interface is there, can you ping 172.22.11.2? Do you have both ethernet and USB connected at the same time? Try pulling the enet cable.

Can you ping roboRIO-####-FRC.local or .lan? Does the web browser with 172.22.11.2 bring up the roboRIO web page showing you the IP settings of the RIO. That would be a good page to see a picture of.

Greg McKaskle

I ended up going to that webpage and found out the IP was something like 0.0.0.0 and the driver station was trying to connect to something that didn't exist. For some reason the RoboRio just decided to randomly erase itself or something; re-imaging it solved the problem and it's been running fine ever since. Thanks for the help!