Code deploys but does not save to cRIO
 

heres what happens:

we have the laptop plugged by ethernet cable into the driver station. we will deploy the code we're working on and everything seems fine. the robot runs and all functions are OK till we stop. if we unplug the laptop and start the robot again nothing happens. its like we have to have a computer attached to the driver station to deploy each time we want the robot to work. it seems like the program we deploy is not saving to the cRIO.

How do we get our code to save on the cRIO so that it runs when it is powered up and without a laptop attached anywhere in the system? Is there a switch or something im supposed to flip or a special Save button? By the way, im not very computer savy so explain it in as much detail as possible please. thanks.

Re: Code deploys but does not save to cRIO
 

Ok, if you go to the project explorer window, and go down to where it says Build Specifications, then click the plus sign. Right click on FRC Boot-up Deployment, and click Build. Let it do its thing, then right click and hit run as startup. (you need to be communicating with the robot for this step). let it go until it asks to reboot. say yes. It should now do the code you built every time it boots.

Re: Code deploys but does not save to cRIO
 

I am having the same problem, but I dont have the FRC Boot Up Deployment. Is there a way i can get it?

Re: Code deploys but does not save to cRIO
 

It is a part of the template projects, both basic and advanced. If you don't have one, you can build it yourself. Here are the basic steps.

Go to the cRIO Build specs, right click and add a new RT EXE build spec. In the dialog that comes up add in the Robot Main as the startup VI, and I think that is it.

Greg McKaskle

Re: Code deploys but does not save to cRIO
 

You probably have only one build specification, which was created properly for you when you created the LabVIEW project from the robot template. It might be called "FRC Basic Robot Deployment" or something similar. Right-click it and you should see the menu containing the Build and Run as Startup options.

Re: Code deploys but does not save to cRIO
 

Awesome!
I see it now! Thanks guys, I would have never put that together by myself. That saved me a lot of headache.

Re: Code deploys but does not save to cRIO
 

I'm trying to follow Paul's instructions, but every time it starts to deploy, it loses connection and then says it was completed with errors. Has anybody else had this problem?

Re: Code deploys but does not save to cRIO
 

We also have the problem with errors.

For some reason, it doesn't like it if we have more than one open joystick, open motor, etc. When it runs, only one of each type of vi can run.

Is there maybe a way to rename these?

Re: Code deploys but does not save to cRIO
 

The template code has multiple opens, so I don't think there is an issue there. What isn't allowed is doing multiple opens of the same resource without closing the first one. Instead of doing this, you will normally want to branch a wire or sore the refnum and use it in other loops.

Greg McKaskle

Re: Code deploys but does not save to cRIO
 

We're having the same problem and tried following what you said but there's no plus box next to build spesifications. What do we do now??

Re: Code deploys but does not save to cRIO
 

1. Right-click on "Build Specifications"
2. Choose New -> Real-Time Application
3. Give it any name "Build specification name"
4. Click "Source Files" in the left Category column
5. Choose your Main vi from the Project Files list
6. Click the blue arrow next to the "Startup VIs" box. (That will put the Main vi in the Startup VIs box
7. Click "OK" at the bottom

You should now see your new real-time application specification for the cRIO listed under Build Specifications, and you can do a "Build", followed by "Run as startup".

Did you start from a normal default Robot Project, or do you just want to download an example permanently?
The examples don't normally have a Build Specification, but the default code that you should really begin with, does.

Re: Code deploys but does not save to cRIO
 

Thanks. We figured it out.