Weird Crio/Programming problem

[Mark McLeod]

Watchdog errors will cause your robot to stop moving. They are due to a communication loss or slow down between the Driver Station and the robot.
You might have code that's executing too slowly (often due to excess error messages). That'll throw Safety Config errors and stop your motors, just until the next command packet arrives at the robot.

A positive 44004 error is: FRC: The Driver Station has lost communication with the robot (which would cause the robot to halt)

A negative -44004 is an attempt to open the camera twice.

The sticking of the joystick sounds like a code problem. It's possible it could also be a malfunctioning joystick, since it can be fixed by jerking it, but I'd suspect the code first.

The loss of the cRIO CPU graph on the Charts tab is due to a Driver Station bug. It was mistakenly plotted against the 12v scale, so it'll disappear off the top as soon as code begins running. If you look at the log through the Viewer utility it should plot correctly.

Some of these symptoms can be caused by a low robot battery. It'll dip lower when you pour power into the motors.