[mattiej]

Originally Posted by 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 you motors just until the next command packet arrives at the robot.

What would we need to do to fix this? I have safety config enabled.

Originally Posted by Mark McLeod

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

I've connected both wireless and tether, and I have still gotten this error. My computer is also only running labview and the Driver station. What else could cause this?

Originally Posted by Mark McLeod

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

Not entirely sure why it is doing this. Since we aren't using the camera, is it okay to just get rid of that code?

Originally Posted by Mark McLeod

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

Ohhhhh okay. That makes sense. Is this Viewer utility in LabView or the driver station?

Originally Posted by Mark McLeod

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

I tried switching out the battery with what I've been told was a fully charged battery. I'll charge up another battery and try again, but with the new battery it didn't fix the problem.