Our code won't stay on the robot/crio.
 

Our code that we keep having to build onto the robot won't stay so we have to run the main each time how can we fix this or is this normal?

Re: Our code won't stay on the robot/crio.
 

Do you do both of these actions?

1. "Build"
2. "Run as startup"

Re: Our code won't stay on the robot/crio.
 

I don't know if you already saw this, but here is a good walk-through of that process.
http://www.frcmastery.com/labview-fo...-startup-code/

Re: Our code won't stay on the robot/crio.
 

Follow this link to a video that shows how it'e done.
http://www.frcmastery.com/labview-fo...-startup-code/

Re: Our code won't stay on the robot/crio.
 

Build is greyed out...quick advice?

Re: Our code won't stay on the robot/crio.
 

It looks like this, but with the word "Build" grayed out?
Does your Project Explorer window look different from this one in other ways as well?

Re: Our code won't stay on the robot/crio.
 

Are you deploying with the shown menu above? If so "Build" then "Deploy" should work.

The main toolbar menu might be grayed out in the beginning for build. I had that problem when I first started.

Re: Our code won't stay on the robot/crio.
 

Aaahh...yes we have that, thanks. I was looking at the "Tools" drop-down menu.

Re: Our code won't stay on the robot/crio.
 

The main toolbar Project->Build will be grayed out if no Build Specification is selected. It doesn't know what it is you want to build.

In the picture I posted the highlighted line is selected.
There can be more than one of these Build Specifications as you get more sophisticated.

Re: Our code won't stay on the robot/crio.
 

When I permanently deploy, I don't choose Run as Startup... I just click Deploy since I just enable the code through Driver Station.

I'm not sure whether or not Run as Startup actually enables code as soon as you turn on the robot(like it did two years ago) since it (must?) receive an enable signal from the DS, but choosing Deploy itself might be safer.

Re: Our code won't stay on the robot/crio.
 

"Run as startup" is safer to use.

Both are functionally equivalent if you chose the "Always run deployed code at startup" option when you formatted/imaged your cRIO.
If you don't chose that option then the deployed code will not execute when you power up your robot and it'll just sit there on the field, like a rock.

A normal operational robot always has it's code running if it's on.
The Driver Station doesn't activate your code on the robot. It just enables/disables the outputs so your motors will do what your code has been telling them to do all along.