This warning indicates that the DS does not detect a Cypress Board attached and properly configured. This warning will also be generated if the Cypress board is disconnected after the DS has started. If no Cypress Board is detected when the DS is started, this is the first warning printed.

This error is triggered when a Joystick is unplugged. Contrary to the message text this error will be printed even if the robot is not enabled, or even connected to the DS. You will see a single instance of this message occur each time the Driver Station is started, even if Joysticks are properly connected and functioning.

This warning is triggered by the Driver Station whenever it attempts to configure the network interfaces of the DS computer. The top warning shows an example of the Driver Station making no change to the wired interface (because it was already set correctly) and not being configured to set the wireless interface (indicated by "<noNICConfig>"). The second image shows an example of the message when the DS does change the configuration of the Network Interface.

This Warning message is printed whenever the Driver Station loses communication with the robot (Communications indicator changing from green to red). A single instance of this message is printed when the DS starts up, before communication is established.

A Ping Status warning is generated each time the Ping Status to a device changes while the DS is not in communication with the cRIO. As communications is being established when the DS starts up, a few of these warnings will appear as the Ethernet link comes up, then the connection to the robot radio, then the cRIO (with FMS mixed in if applicable). If communications are later lost, the ping status change may help identify at which component the communication chain broke.

This message is printed each time the DS begins communicating with the cRIO. The message indicates the up-time, in seconds, of the cRIO and can be used to determine if a loss of communication was due to a cRIO Reboot.

This message may be printed when the DS begins communicating with the cRIO and indicates the time, in seconds, since the last time the radio was lost and seen. In the first example image above the message indicates that the cRIO's connection to the radio was lost 19 seconds before the message was printed and the radio was seen again right when the message was printed. If multiple radioLost or radioSeen events have occurred since the cRIO booted, up to 2 events of each type will be included, separated by commas as seen in the second example image.

This message is printed when the DS begins communicating with the cRIO, but detects no robot code running. A single instance of this message will be printed if the Driver Station is open and running while the cRIO is booting as the DS will begin communication with the cRIO before the robot code finishes loading.