Thread: Disable.vi
View Single Post
  #3   Spotlight this post!  
Unread 10-02-2012, 09:29
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: Disable.vi

Use the Set Output from the same motor palette and wire in a zero.

Any motor that might possibly have been moving at the moment when the robot was Disable should be set to neutral.
The reason is that you might come out of the Disabled state doing something different than when you entered Disabled, e.g., switch to Autonomous from Teleop, or switch to Teleop from Autonomous, or restart Autonomous.
If Teleop last had an arm motor moving up when you disabled, then if you don't set it to neutral in Disabled.vi and switch over to test autonomous, but autonomous doesn't use the arm until later, the arm will immediately continue moving upwards on it's own. The motor will continue executing the last output it was told.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 10-02-2012 at 09:37.
Reply With Quote