[Greg McKaskle]

Just before kickoff, the Comm thread and FPGA were changed to update the Diagnostic with counts of even the smallest glitches. The latest DS definitely makes changes to improve the timing and eliminate many of the glitches.

At this point, it would be helpful if details of how to reproduce the glitches were posted. Before we go there, here are some things to consider.

The print statements do not differentiate between user induced disables and watchdog timeouts. Therefore, some of the diagnostics print statements will occur naturally.

If the dashboard runs on the same computer as the DS and is misbehaving, it is feasible that it could starve the DS thread enough to cause watchdog glitches. If the robot code misbehaves, it may be able to cause occasional glitches. Some teams have also noticed a .NET conversion tool that seems to get caught in a loop comsuming lots of CPU.

If you have a repeatable situation, please post the details. It may also be useful to notice the classmate CPU usage and cRIO CPU usage.

Greg McKaskle