[Greg McKaskle]

I was at a week one regional, and we saw a number of issues with various languages. If the robot is occasionally having its I/O shutdown, there should be messages on the Diagnostics tab detailing what deadlines are not being met. It is most likely due to waits or large amounts of processing taking place in the telelop function or in the autonomous loop. If output updates don't happen often enough, the watchdog or safety VIs will shutdown the outputs. If you see this symptom and can't locate the issue, post your code.

I saw crashes with Java and C++, but they were pretty easy to track down using the DS practice matches and sometimes forcing the cRIO to boot first and then plugging in the DS. This helped track down dependencies between auto and tele and race conditions in the init code. We didn't see a LV crash, but heard of a team experiencing this at a different regional. We are hoping to get code to reproduce this, but haven't had a chance yet.

Greg McKaskle