Build, then Run as Startup results in Conflict?

[Alan Anderson]

Originally Posted by BrandonAbe

First, you must build the code. then you must deploy the code, and then run at startup.

The "deploy" step is both unnecessary and unhelpful. It will just take more time. All you need to do is "Build" and "Run as startup".

This error will occur when you are deploying the code, just because it is telling you that the robot is on. Just click okay, and then run on startup. When it then asks to reset the cRIO, click no, and manually turn your robot off and on. When you turn it back on, it should have the new code.

First, it's not an error. It's just an informative message telling you what will happen if you continue. Since what it says will happen is exactly what you want to happen, there's no problem.

Second, you should click Yes when it asks if you want to reboot the cRIO. That's how it starts running the newly loaded program. Removing power from the robot will make you need to wait for the DAP-1522 to boot and for the Driver Station to reconnect to it. That will take almost twice as long as just rebooting the cRIO from the prompt.