[DonRotolo]

It would be wise to use the CPU status monitor to verify you are not maxing out the CPU. We had a failure on the field once which we attributed to CPU overload.

The regular symptoms are all the outputs of the cRio go dark for about 1/2 second, at a random interval between 10 and 30 seconds or so. The lights on the cRio, DSC and PDB stay solid, but the jaguar/victor/spike indicators blink off in unison. During match play/driving it's hardly noticed, but once we feel it was responsible for a momentory loss of control at a critical moment.

We removed some unnecessary code, but have yet to really analyze the code for inefficiencies. Our code was completely student-written, and the adults can't easily discern how it works yet, but that'll happen this and next week. (Student coders often lack discipline, elegance and efficiency, often whacking problems with brute force in convoluted and hard-to-follow ways. Max.)

Greg from NI helped us understand what to look for, and my team and I are grateful to NI for sending him to NJ, and even more grateful to Greg for consuming one of his weekends to travel from comfortable Texas to frozen NJ just to help FRC teams.