Robots not under driver control- does it happen- do you determine why?

[RoboMaster]

Yes, we've had this intermittently, but it never was a major problem, I believe. Last year with the new Classmate there was an internal issue that would periodically trip the watchdogs at a concerning rate, but we fixed it after searching on Chief Delphi. We sometimes get errors in the diagnostics tab when starting up, but we are quite confident that this is a common occurrence during boot-up (it doesn't affect control since we haven't enabled yet). Most of the time when the robot hiccups it's because of a watchdog error, although most of those times we don't even notice it; it seems to be instant. We often can't think of what might be wrong, though. But we would check for lagging code, the diagnostics tab of course, a dead battery, if the drivers are cranking on the controls and drawing too much current...mostly basic things (we don't have a plan like you mentioned). Sometimes we do image the cRIO and that's usually a good "reset" point to start from.