[ChrisH]

Originally Posted by willishf

We also have pneumatics for lifting our fork lift and have seen that behavior multiple times where it simply retracts the forklift. Something is causing the code to go into the startup state. This has happened to us in practice in the shop so the problem could still be communication related where a drop in communication does the same thing as not feeding the watchdog.

Not sure if it is possible to monitor the communication from the cRIO to have it log anytime it goes into "safe" mode.

If you are at an event get with the FTAA before your match and ask him to pay attention to your robot. He has a display and logs of the communication status between the field, the robot, and the driver station. He can also spot a big drop in battery voltage, which indicates other problems. The logs can be checked but it is easier to just catch stuff as it happens most of the time.