Quote:
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!