How to deploy code?

[BenGrapevine]

I don't know about anyone else, but this is what I do:

1. Plug a crossover cable into the cRIO (unplug the bridge cord or whatever that is called (ethernet cable) that is currently in the cRIO and place that instead) and into the ethernet port on the PC that contains the code
2. Turn the robot on
3. Open the program cRIO Imaging Tool, and apply "controller settings" (or something like that) once it's detected the cRIO
4. Go the project folder for your program in labVIEW, find "Build Specifications" (usually at the bottom, never seen it anywhere else ._.) and right click on it
5. Click on "Build"
6. Once complete right click on "Build Specifications" again and this time click "Deploy"
7. Turn the robot off, and unplug the crossover
8. Place everything where it needs to be (ethernet back into the cRIO, etc)

It seems to stay on there for me, but I know last year we had to do something like this:

Skip the "Deploy" step.
1. Build
2. Run as startup

Hope that helps (may not I'm a bit scatterbrained at the moment)

[Alan Anderson]

Originally Posted by BenGrapevine

I don't know about anyone else, but this is what I do:

1. Plug a crossover cable into the cRIO (unplug the bridge cord or whatever that is called (ethernet cable) that is currently in the cRIO and place that instead) and into the ethernet port on the PC that contains the code

You shouldn't be disconnecting and reconnecting things like that. You can have many things on the network simultaneously. Just plug the programming computer into the robot's D-Link router along with the cRIO. You can even connect the computer wirelessly, so you can do reprogramming without having to have the robot physically tethered to anything.

3. Open the program cRIO Imaging Tool, and apply "controller settings" (or something like that) once it's detected the cRIO

There is usually no need to use the Imaging Tool unless you want to change which language you're using, or to load or remove a CAN plugin, or if there's an updated image released.

5. Click on "Build"
6. Once complete right click on "Build Specifications" again and this time click "Deploy"

If you want the code to run on the cRIO each time it's turned on, it's generally a good idea to click "Run as startup" instead of "Deploy".

[Andrew T.]

I tried all those steps that all you guys posted but it still not working. When I reboot the robot, it says "No Robot Code." Is there any other way to deploying the code so each time I on the robot the code will be there.

-Andrew

[Alan Anderson]

Originally Posted by Andrew T.

I tried all those steps that all you guys posted but it still not working. When I reboot the robot, it says "No Robot Code."

Check the cRIO's switches. Is perhaps the NO APP switch turned on? All switches should be off unless you know exactly why you would turn one on.

Is there any other way to deploying the code so each time I on the robot the code will be there.

There are other less convenient ways to copy the standalone real-time executable file to the cRIO, but if "Build" followed by "Run as startup" does not work, the other methods aren't likely to work either.

[j.cole]

I personally find the distinction between on and off with those switches very confusing so that may be your problem.