-
Notifications
You must be signed in to change notification settings - Fork 0
Create feeder subsystem #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: development
Are you sure you want to change the base?
Conversation
| } | ||
|
|
||
|
|
||
| private static class FeederSubsystem extends SubsystemBase { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we break this out into its own file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't really think of the two subsystems as the same thing. It's always been a bit confusing to me why we didn't split it off initially. I think having separate files would help with findability as well as general organization.
| protected Command spinFeederAndStop(double speed) { | ||
| return startEnd(() -> feederMotor.set(speed), feederMotor::stopMotor); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can be more specific with the command(s) we define here. We're pretty much only ever going to have one intake and one eject. I'd handle the beam break logic within here. We can still publish this if we need it, but I'd rather have a more explicit interface here.
To prevent the use of one component of the shooter from stopping the use of the other