For teams having trouble downloading code

[jhersh]

Originally Posted by Tom Line

Our solution to this has been to format and leave the crio clean. Then we can run to our heart's content, and when we finally want to deploy permanently, we can do so.

The next time we want to "run", we do a reimage of the crio so that the code is all wiped, and go back to "running" the code rather than permanently deploying it.

That seems like a pretty drastic approach, but it does seem like it should work. I would think there are other, faster ways to do this such as the no app switch. Also, you could set it to not run at startup (as long as you didn't tell the imaging tool to "always run as startup"). You could also FTP to the cRIO and delete the startup application.

I never have this problem anyway... perhaps the code you are deploying is overly processor hungry? Perhaps you are cancelling when you don't need to (there are a number of poorly worded dialogs in LabVIEW RT that can mislead you into thinking there is a problem and luring you into aborting an operation in progress that would complete successfully if you don't read them carefully)?

-Joe