Communication issues?

[ekapalka]

That's at least what I assume it is. My team recently agreed to present our robot at sports event (football game?) to show our support for breast-cancer awareness, and we forgot to check that the robot works first (how can you turn that down?). We booted up the robot today to do some diagnostics with the solenoids not properly functioning, and we found a new issue. The first time we turned it on, it was okay. It could drive and actuate two of the three solenoids. I was told to redeploy the code (because the hardware is apparently flawless), and we began having trouble. I should mention that before we started it up, we switched the target server to the proper one for a 4 slot cRIO. When it booted up, the "Robot Code" and "Communications" lights were on, but the robot itself was unresponsive. We tried re-imaging the cRIO, restarting the DriverStation, restarting the computer, and rebooting the robot. Every time resulting in a similar message:

Warning <Code> 44002 occurred at Ping Results:  link-GOOD,  DS radio(.4)-bad,  robot radio(.1)-bad,  cRIO(.2)-GOOD,  FMS-bad Driver Station
<time>10/9/2013 5:50:26 PM<unique#>12
FRC:  Driver Station ping status has changed.
WARNING <Code> 44008 occurred at FRC_NetworkCommunications <radioLostEvents>  6.501 <radioSeenEvents>
FRC:  Robot radio detection times.
Warning <Code> 44003 occurred at Driver Station
<time>10/9/2013 5:47:36 PM<unique#>11
FRC:  No robot code is currently running.
WARNING <Code> 44007 occurred at FRC_NetworkCommunications <secondsSinceReboot> 3.279
FRC:  Time since robot boot.
Warning <Code> 44002 occurred at Ping Results:  link-GOOD,  DS radio(.4)-bad,  robot radio(.1)-bad,  cRIO(.2)-GOOD,  FMS-bad Driver Station
<time>10/9/2013 5:47:20 PM<unique#>10
FRC:  Driver Station ping status has changed.
Warning <Code> 44002 occurred at Ping Results:  link-GOOD,  DS radio(.4)-bad,  robot radio(.1)-bad,  cRIO(.2)-bad,  FMS-bad Driver Station
<time>10/9/2013 5:47:15 PM<unique#>9
FRC:  Driver Station ping status has changed.

Warning <Code> 44004 occurred at Driver Station
<time>10/9/2013 5:47:15 PM<unique#>8
FRC:  The Driver Station has lost communication with the robot.

Warning <Code> 44002 occurred at Ping Results:  link-GOOD,  DS radio(.4)-bad,  robot radio(.1)-bad,  cRIO(.2)-GOOD,  FMS-bad Driver Station
<time>10/9/2013 5:44:05 PM<unique#>4
FRC:  Driver Station ping status has changed.
WARNING <Code> 44008 occurred at FRC_NetworkCommunications <radioLostEvents>  102.504 <radioSeenEvents>
FRC:  Robot radio detection times.
WARNING <Code> 44007 occurred at FRC_NetworkCommunications <secondsSinceReboot> 104.262
Warning <Code> 44001 occurred at No Change to Network Configuration: "Ethernet"<noNICConfig>
FRC:  Time since robot boot.

Driver Station
<time>10/9/2013 5:43:38 PM<unique#>3

ERROR <Code> -44009 occurred at Driver Station
<time>10/9/2013 5:43:38 PM<unique#>2
FRC:  A joystick was disconnected while the robot was enabled.

Warning <Code> 44006 occurred at Driver Station
<time>10/9/2013 5:43:38 PM<unique#>1
FRC:  Custom I/O is not enabled or is not connected to the driver station.

Most of these we've seen (switching network types, disconnecting the joystick, etc), but we're not sure what to make of some of these things. Were thinking it might be the DriverStation itself, because of something we had done earlier that day. We tried to set up the gyro on another robot (with an 8 slot cRIO). It was miserable. It starts at some huge number and counts up at an increasingly fast rate. This dynamic message continues to display on the DriverStation regardless of which robot (if any) is currently connected (by the way, we never got the gyro to work). Does anyone have any ideas as to what the cause of the problem is? Thanks!