[Greg McKaskle]

Since folks are attempting to identify FCA failures from videos and data from other events, let me share some diagnostic detail. In particular, a blinking RSL on a robot that isn't moving does not mean FCA.

If a robot radio never connects to the field at all, it is something else.
If it connects to the field but stops moving ...
Does the DS indicate that it is connected to the robot? The alliance wall light also indicates whether communication is successful.
If it shows battery voltage and other signs of communication, it is something else.
If there is no communication with the robot, it is time to determine if the radio and cRIO are on or off. The RSL doesn't convey much info, but if it is active, the cRIO is up and at least some of the user code is active.

That leaves us with the radio. The LEDs on the front show whether it is in AP or bridge mode and whether it is bridged.

The odd symptoms that point towards FCA are a robot that can be pinged even though no communications succeed and the robot will either return too quickly to be a radio reboot or will not return at all.

The reason the report mentions cRIO reboot times was to try and identify definitively whether other failures could fit the symptoms. Unlike the radio, this is dependent on the team's code and needs to be measured for each robot.

Greg McKaskle