View Single Post
  #11   Spotlight this post!  
Unread 18-01-2011, 23:26
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,795
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Our code won't stay on the robot/crio.

Quote:
Originally Posted by umangv620 View Post
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.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 18-01-2011 at 23:29.
Reply With Quote