View Single Post
  #8   Spotlight this post!  
Unread 02-05-2014, 23:23
gappleto97 gappleto97 is offline
Registered User
FRC #3617
 
Join Date: Oct 2013
Location: Marquette, MI
Posts: 12
gappleto97 is an unknown quantity at this point
Re: Setting custom disable behaviors

Quote:
Originally Posted by NotInControl View Post
Only PWM and Relay outputs are disabled. Digital In, Digital Out, and Analog In are all fully functional during the disabled state of the robot. You can set digital output pins high or low in disabled. Digital IO should never be used to drive actuators as per FRC rules, which is why its state are allowed to be commanded during disable.




Unless you are creating a new class which extends IterativeRobot, the super.DisableInit() does not exist. That implies that disabledInit() exist in the parent class you are inheriting from.

The first definition of DisabledInit() is in the IterativeRobot class, so is you are trying to call super.DisabledInit() inside of IterativeRobot, or CommandBasedRobot, that is probably why its failing.

Also do not include any @override annotations, as mentioned already they are not supported by the JVM on the cRIO.

Hope this helps,
Kevin
While this helps explain why it doesn't work, it doesn't explain how to make it work. Should I just put that in robotcode.java and see what happens?
Reply With Quote