Redeploying Code without reimaging the cRIO

[AquaMorph]

I have been able to deploy code the the robot and it works fine. The problem I am having is every time I want to deploy new code, I have to reimaging the cRIO. Anytime I try to deploy code on top of existing code I get the "Unable to connect to Real Time Target" error. The weird thing is I am able to ping the cRIO. Is there something different you have to do when overwriting code?

[notmattlythgoe]

We had a problem several years ago where the code we had on the cRIO was using up 100% of the processing power, so we had to boot it into no code to load the new code onto it. It sounds like you could be having the same problem. Try toggling the "No Code" dip switch on and restart the cRIO, then load your code and toggle the dip switch back off, restart and you should have new code.

[AquaMorph]

Originally Posted by notmattlythgoe

We had a problem several years ago where the code we had on the cRIO was using up 100% of the processing power, so we had to boot it into no code to load the new code onto it. It sounds like you could be having the same problem. Try toggling the "No Code" dip switch on and restart the cRIO, then load your code and toggle the dip switch back off, restart and you should have new code.

Where is this dip switch?

[notmattlythgoe]

Hmm, after looking at the picture, there doesn't seem to be any on the 4 slot version. There is a way to check the CPU usage on the cRIO when you are plugged into it, but I can't remember off of the top of my head how to do it. That would be another way to verify that the 100% usage is the problem. IF that does turn out to be the problem then you probably need to put some delays in some of your loops.

[Mark McLeod]

There is a known bug when the Dashboard is operating that can block the download of new code.
The temporary workaround is to close the Dashboard before attempting to download code.

The NoApp switch for the 4-slot cRIO is reached through the cRIO Imaging tool (at the bottom of the window). The NoApp switch is set, then the cRIO needs to be reset for it to take effect.

The cRIO CPU % will be available on the Driver Station Charts tab after the next update release. Right now it's getting plotted incorrectly, so it can't be seen.