As an addon to Marc's comments, all team programmers should get in the habit of checking their Driver Station log for each match when the robot comes back from the playing field.
It contains a wealth of information recorded 50 times a second for the entire match:
- Communication packet trip time
- Lost packet count
- Robot battery voltage
- cRIO CPU utilization %
- Markers for lost comms (and most importantly, the duration of lost comms: ~25 sec = radio reboot, ~40 sec=cRIO reboot)
- When Auto/Teleop occurred
Start -> All Programs -> FRC Driver station Log Viewer
Also, get in the habit of checking the built-in Window Task Manager or Resource Manager tools (Cntl-Alt-Del) for:
- PC CPU %
- Memory %
- Networking bandwidth