Consistent disabling every ~30 seconds

[omentic]

Upon connecting to, enabling the robot, and waiting anywhere from five to thirty seconds, the robot seems to disable itself without user input - the RSL stops flashing, and the dashboard and console note that all running commands were interrupted.

When the robot disables itself, no out-of-the-ordinary messages appear in the logs. Every command is interrupted the same as if the robot was manually disabled. ConsoleDS does not reflect that the robot has been disabled. The RoboRIO is still pingable when this happens. Quitting the ConsoleDS application, waiting ~10 seconds, and relaunching lets you reconnect to the robot.

This behavior has only been noted to happen on (2) Linux-based system(s) running ConsoleDS. I have not tested (nor have access to) a Windows computer running the official driver station.

A typical log is available here.

[omentic]

This issue was fixed by one or more of the following:

• Deploying the code available on the debugging branch and then redeploying the current master code
• Unplugging / plugging various wires from the radio
• Connecting to the radio with an ethernet cable (although there are no more issues over wifi either)
• Pinging the RoboRIO (10.49.15.2) while connected