Reflash of cRio to deploy labview code

[Joe Ross]

Rather the doing a full re-image of the cRIO, try going to the imaging tool and turning on the no-app switch and then reboot the cRIO, reload your code, and then go back the imaging tool and turn off the no-app switch. Unless the cRIO image is actually getting corrupted (not likely), this is a faster way to get no code running on the cRIO. The most common reason for deployment errors like this is the code already running on the cRIO.

To get to the root cause of the problem, what is the cRIO CPU usage and RAM usage when running. These are shown in the Driver Station charts tab. Swamping the CPU or using too much ram may interfere with the deploy process.

[Sparktracer]

Joe,
Thank you for your reply. I had worked with Andy from NI in the past and we have seen issues when using the no-app switch. I agree that this is a faster way to load code, but not the fix to the root of the problem.

Working with the CSA at Troy, we were able to locate the root cause of the problem.

We had a ref call in periodic tasks that had accidentally been disabled in begin. This was causing the controller to lock up during a deploy.

If you happen to have this problem, or one very similar, verify that you have good code in periodic tasks.