Closed roshanr10 closed 5 years ago
we're waiting on #63 but theoretically this'll just follow the elevator going up when this is enabled to try to keep the robot level
i think this should be built as part of the existing elevator subsystem and kick in whenever the elevator subsystem tries to go farther negative (below the initial starting point), and then have a retract upward feature
one way to to do this would have the stilts PID on gyro values to be level when the stilts are activated– then once you're mostly on, you can override the PID and bring them up as well
blocked by #63
See climber branch.
Newest commit saw writing of untested code for stilts in climber subsystem. Included classes are DriveStilts and RetractStilts with buttons specified in #83.
To-Do List for this code for next meeting:
"The type ClimberSubsystem must implement the inherited abstract method Subsystem.initDefaultCommand()" error showing up on Climber Subsystem class when declared
Figure out which motor will be used for climber and fill this in in Climber Subsystem class for RobotMap object
Test code with robot
For future, WIP branches are nice because it allows for easier code comments and can eventually be merged in. I’ll take a look in a few hours.
I think I’ve seen the first issue in past, I’ll see what I can do.
On Wed, Feb 13, 2019 at 21:54 Shashank Jarmale notifications@github.com wrote:
See climber branch.
Newest commit saw writing of untested code for stilts in climber subsystem. Included classes are DriveStilts and RetractStilts with buttons specified in #83 https://github.com/FRCteam4909/2019-Deep-Space/issues/83.
To-Do List for this code for next meeting:
-
"The type ClimberSubsystem must implement the inherited abstract method Subsystem.initDefaultCommand()" error showing up on Climber Subsystem class when declared
Figure out which motor will be used for climber and fill this in in Climber Subsystem class for RobotMap object
Test code with robot
— You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/FRCteam4909/2019-Deep-Space/issues/56#issuecomment-463466675, or mute the thread https://github.com/notifications/unsubscribe-auth/AEUIR0z3c7ce2PK9db-5QCfdrR4L2OfNks5vNM_zgaJpZM4af18i .
There are two motors within the subsystem on entirely different gearboxes...see initial comment in issue.
You just need to implement initDefaultCommand()
as an empty method to avoid throwing the aforementioned error
To-Do for this Issue as of 02/17:
Hardware (discuss more w/ build on motor controllers, and encoders requirements)
Commands (works in conjunction w/ existing elevator setpoints)