Removing Code

[pyr0b0y]

ok so i download some code to the crio and it worked fine with the joysticks. i am now trying to take the code off of the crio completely...what is the best way to erase it from the crio???

[BLAQmx]

You shouldn't need to manually remove code from the cRIO. Whenever you deploy something new to it the old code will automatically be removed and replaced with the new code.

[Boydean]

Also, if you just click run in Labview it sends the program to RAM. Therefor when to cRIO restart it won't be there anymore. This is assuming that you didn't deploy it to flash which is a different process.

[pyr0b0y]

well i was just trying to run 1 motor at first. so i deployed it and it worked fine, but i updated the code, and have been trying for 5 days and have not been successful in getting a motor to run again. btw this is only for teleoperated, i uploaded auto code and itll just go in to auto mode, even if i manually switch it to tele from the driver station....whats going on?

i have tried also uploading the whole project, but that doesnt do anything either

[Greg McKaskle]

If you have a motor that isn't moving, and it is a SW issue, you are probably getting an error. You should always probe or look at panels or run the dashboard to see what they are and let them help with the debugging.

Greg McKaksle

[Mark McLeod]

I've found this not to be true after Update 3.0a.
If I don't remove the default code (added to the cRIO by Imaging with the latest update) then it will be running at the same time as my newly downloaded LabVIEW code.

You can easily test for this by booting the cRIO while the DS is set to autonomous mode. You'll see the chase lights on the solenoid module until the larger LabVIEW program has time to finish loading and take over.

Originally Posted by BLAQmx

You shouldn't need to manually remove code from the cRIO. Whenever you deploy something new to it the old code will automatically be removed and replaced with the new code.