[Tom Line]

We are having an intermittent issue that is increasing in frequency.

What we are seeing is that when we are running the code from our laptop (i530 quad core, lots of memory, nothing other than labview running, CPU not maxed out) using our classmate as the driver station (basic dashboard with no modifications), our vision processing .vi and periodic tasks .vi will stop functioning, and probing of either will result in the probe showing 'not executed'.

Our code normally runs at about 70% CPU utilization until the fire button is pressed, then the vision runs and the cpu jumps to 100% until the trigger is released.

Each of our periodic tasks has a wait in it, with no weight shorter than 20 ms.

Why would periodic / vision processing stop executing? Is there some built in safety that shuts them off? This does not happen that we've seen with a permanent deploy to the robot.