[Greg McKaskle]

One thing that can happen is that the code on the cRIO is constantly throwing errors and the error console is running almost constantly. It is bad enough that this slows things down, but in some situations, it can cause the deployment to drop its state. This means that both machines are waiting for each other, not aware that the conversation was dropped. The fix was too risky to put in this year, and the solution is to fix the issue that causes constant errors.

You can verify this is the issue by opening the Diagnostics tab and seeing lots of errors flowing by. You will also see high CPU usage at that point. Try other robot modes to see if the errors can be avoided. If not, use the imaging tool to set the no app switch. You could also ftp, delete a file, and reboot.

There is almost never a reason to image the cRIO except for at the beginning of the season or unless you've glob'ed when you shouldn't have with ftp. I'm not sure I've ever seen evidence of a corrupt file system. Of course the imaging step won't hurt, but it is the tin-foil hat for SW problems.

Greg McKaskle