Things were working fine.
Now suddenly I have this error.
Warning <Code> 44006 occurred at Driver Station
<time>2/23/2014 2:57:34 PM<unique#>1
FRC: Custom I/O is not enabled or is not connected to the driver station.
Enet, Bridge, Robot are green.
I can ping and ftp to the robot.
but communications / robot code lights stay red.
I’ve:
-rebooted the cRIO
-rebooted the driver station
-re-deployed code to the cRIO
-44006 is just a warning that the Cypress IO board isn’t being detected.
Not unusual if you aren’t using the Cypress board.
The status lights you report mean that the DS and ping the cRIO and robot bridge.
The lack of Communication/Robot code lights means the cRIO image is not running. (P.S. or in this case the DS is not connecting)
Do you have the NoApp switch set?
It’s on the face of an 8-slot cRIO, or on a 4-slot is checked with the cRIO Imaging Tool.
Fire up NetConsole to see if any error messages get reported when the cRIO is booted.
Mark,
Thank you for the advice. It turns out to be a bit more subtle than I first indicated.
It probably is related to TCP / IP settings. I accidentally found out that one other machine on the network can communicate. The machine that failed had been working, but then failed for no apparent reason in the middle of the afternoon.
I also learned that, if one machine has the Driver Station running, then no other machines can connect as Driver Station. This shouldn’t surprise me, in hindsight.
Amusingly enough, the machine that fails can still upload code and FTP to the cRIO.
Best,
Martin
Yep, the second Driver Station is expected behavior.
First DS to connect wins.
I’ve experienced that problem at demos when a programmer doing separate work fires up a second DS and blocks the driver’s controls DS when it comes up later.
As well, any number of other PCs can connect to upload code or monitor the cRIO.
For instance, the default setup is expected to be:
[LEFT]
At the event it’s: