Repository navigation
Shooter Subsystem Rework: Add Flywheel Subsystem - #116
Open
CanineSatsuma6 wants to merge 3 commits into
Open
CanineSatsuma6 wants to merge 3 commits into
CanineSatsuma6 wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: This PR is one of several in a series of PRs designed to rework our shooter subsystem to address issues with maintainability and readability and reintroduce some semblance of simplicity. Any PR that's merging into the
shooter-subsystem-reworkbranch and NOTmainis a part of this series.Background
This PR adds in the "Flywheel" component of the larger shooter subsystem. It follows the same pattern for code structure outlined in the Background section of PR #114. For information on the overall design principles, see that section.
Code Structure
The overall design for the flywheel code looks something very similar to the rotor code, like this:
erDiagram Flywheel ||--|| FlywheelIO : "uses" FlywheelIO ||--|| FlywheelIOReal : "is (real robot)" FlywheelIO ||--|| FlywheelIOSim : "is (simulated robot)" Flywheel ||--|| FlywheelIOInputs : "uses" FlywheelIOInputs ||--|| FlywheelIOReal : "provides" FlywheelIOInputs ||--|| FlywheelIOSim : "provides"Flywheel Behavior
The overall method used to interact with the flywheel isn't changing. We still specify a target angular velocity and the flywheel follows it.
Much like the rotor, the flywheel PID controller for velocity control will need some further tuning.