[Greg McKaskle]

I suspect that this is caused not by CPU load, but because the cRIO is pumping out so many error messages. Each time it does so, it causes a number of thread transitions. We discovered late last year that during those thread transitions, it is possible for the cRIO code to drop the deployment protocol.

If your Diagnostics tab is streaming errors, try another mode, tele, disable, etc. Then try to deploy.

If Test is causing lots of errors, that would probably be because some I/O was not opened correctly. Test mode reads every single I/O value and displays it, so if there was a rarely used or not used Open call, it will complain about it anyway.

Greg McKaskle