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

[Mark McLeod]

Originally Posted by umangv620

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.

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