Build, then Run as Startup results in Conflict?
 

Everytime we build, then run as startup, we notice we always get presented with this screen shot below. But we click "OK" and the code deploys and runs.

Is this NORMAL?

Why is it doing this? Anyone know?

Re: Build, then Run as Startup results in Conflict?
 

Yes it's normal. It's just a (very scary) way of telling you that you are overwriting already running code.

Re: Build, then Run as Startup results in Conflict?
 

Should we be cleaning? Or undeploy first? If so, what's the best way to clean the CRIO or initialize it to get it ready for new code? Is that a more recommended way? If so, the 2012 software documentation did not indicate this but makes sense maybe it should be done.

Re: Build, then Run as Startup results in Conflict?
 

It's not an error, just a warning. If you're trying to put a new program on the cRIO, you want to terminate the currently running program. Just click OK like you have been doing.

Re: Build, then Run as Startup results in Conflict?
 

We have the same problem, but it won't run at all. We get no robot code.:(

Re: Build, then Run as Startup results in Conflict?
 

What are you trying to run, and how are you trying to run it? If you Build the project and then Run as Startup, it should work. If you're just trying to Run a VI using the run arrow on the toolbar, only the Robot Main.vi will properly start the code running to establish communication with the Driver Station.

Re: Build, then Run as Startup results in Conflict?
 

Summary of what everyone said:
First, you must build the code. then you must deploy the code, and then run at 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.

Re: Build, then Run as Startup results in Conflict?
 

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".

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.