Thread: disabledInit()
View Single Post
  #4   Spotlight this post!  
Unread 15-03-2014, 00:22
NotInControl NotInControl is offline
Controls Engineer
AKA: Kevin
FRC #2168 (Aluminum Falcons)
Team Role: Engineer
 
Join Date: Oct 2011
Rookie Year: 2004
Location: Groton, CT
Posts: 261
NotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond reputeNotInControl has a reputation beyond repute
Re: disabledInit()

Quote:
Originally Posted by rrossbach View Post
Just to be really clear , from a programming perspective they are two different states.

This is incorrect. There is only one disabled state for the robot, and there is only one interface to that state from the programming perspective.


Quote:
Originally Posted by rrossbach View Post
Even though the WPI framework calls the same disabledInit() and disabledPeriodic() functions irrespective of whether you're in Auto/Teleop/Test, in your code you can use the isAutonomous(), isOperatorControl(), and isTest() functions to distinguish what state you're in if you really need to.
While this is true in proving that the robot has 4 states (disabled, autonomous, teleop, and test, this statement does not provide evidence that Autonomous Disabled and Teleop Disabled are two difference states as your original post implied, and the first sentence of your last post tries to back up.

Your original post mentioned Autonomous Disabled, and Teleop Disables which could be interpreted that they are two different functions on the programatic side. However they are not.

I will not argue semantics, if you feel to call them two separate states by all means go ahead, but passing that information on to others is completely incorrect.

Regards,
Kevin
__________________
Controls Engineer, Team 2168 - The Aluminum Falcons
[2016 Season] - World Championship Controls Award, District Controls Award, 3rd BlueBanner
-World Championship- #45 seed in Quals, World Championship Innovation in Controls Award - Curie
-NE Championship- #26 seed in Quals, winner(195,125,2168)
[2015 Season] - NE Championship Controls Award, 2nd Blue Banner
-NE Championship- #26 seed in Quals, NE Championship Innovation in Controls Award
-MA District Event- #17 seed in Quals, Winner(2168,3718,3146)
[2014 Season] - NE Championship Controls Award & Semi-finalists, District Controls Award, Creativity Award, & Finalists
-NE Championship- #36 seed in Quals, SemiFinalist(228,2168,3525), NE Championship Innovation in Controls Award
-RI District Event- #7 seed in Quals, Finalist(1519,2168,5163), Innovation in Controls Award
-Groton District Event- #9 seed in Quals, QuarterFinalist(2168, 125, 5112), Creativity Award
[2013 Season] - WPI Regional Winner - 1st Blue Banner