[Greg McKaskle]

An internal short on the cRIO due to debris should definitely be added to the list of potential causes. From what I've seen, this is far less common than the other issues and belongs towards the bottom of the solutions list.

It sounds like we agree that forty seconds is not the typical boot time. The approach was to use the time between movement to help determine whether it was a power loss at only the radio, only the cRIO, or on both is useful to know when diagnosing and fixing the issue.

The cRIO-only reboot due to power sag can be approximated using a reset button press or duplicated by pulling and reattaching a cable. A team or CSA can measure this for a given robot and use this number to help diagnose what is happening on the robot. Typical numbers aren't nearly as accurate as a robot-specific boot time, but since most teams don't state that information in their problem statement, we fall back to typical values.

Personally, I'd be interested in seeing poll results on cRIO reset times. Quicker is obviously better, and this could help identify what impacts it. But this is an independent topic and far less of a priority than avoiding the immobility in the first place.

Greg McKaskle