I'm having a problem where I installed the driver station software on my development computer, but I've had problems with getting it to connect to our cRio sometimes (directly wired, so not a wireless problem).
Last night in particular, it refused to do anything other than say "No Robot Communication" However, it's definitely lying to me. Why do I say that?
- I can FTP things back and forth to the robot while it's saying this
- Netconsole works, I can see output from the robot. Nothing strange here
- Using wireshark, I can see packets going back and forth rapidly to/from the computer
- If I click the 'Reboot cRio' button on the driver station software, it works (even though the software warns me that it isn't connected to the cRio, so I will have to physically reboot the cRio)
- The 'robot' light in the diagnostics tab turns green for a second or two, then turns off. It also says 'pinging', then stops saying that.
-
VirtualDS 0.7 can communicate with the cRio and enable/disable it with no problems
I reformatted the cRio just in case, and no change. The driver station that I'm using shows version 11.30.11.00, and we're running with the C++ environment.
I vaguely remember having this problem before, and then it magically fixed itself when there was a joystick plugged in. Is it a requirement to have a joystick plugged in for the driver station to work? I'll try again tonight to see if that fixes it, as I didn't have a joystick available to me last night.
Any further thoughts are welcome.