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
Merge Oregon State Fair changes #3
Conversation
New intake is now fully functional. Added a few commands to facilitate the control of the intake. Most SmartDashboard.put* calls were also commented out to avoid cluttering the driver station. Modified shooter feedforward a bit, but we still need to dial it in.
Added some delays to TaxiThenShoot auto, as well as added intake homing as the first thing. Adjusted climb timings. Add an adjustable RPM offset to ShooterSubsystem. Change the behavior for ShooterMath.calculateRPM so that if the Limelight picks up a target outside of its calibrated range, it reverts to the default RPM.
We had some trouble getting the secondary to rumble, so we should probably check if that's an issue with the controller or just how we rumble it. The compressor is now enabled when telop starts (maybe) because we were having some issues with it not running, but that might have been due to it being at pressure.
Intake and indexer constants were also split up in Constants.java.
A bunch of files (mostly commands) were deleted since they weren't used anymore. TurnToAngleProfiled was renamed to TurnDegrees to better reflect what it actually does. Smart Motion turn-related constants were removed as well since they were unreliable & we got the NavX working pretty well. I'm also trying to remove old TODO comments, so some of those were deleted.
@@ -10,6 +10,7 @@ | |||
private double m_power; | |||
private final Timer m_timer = new Timer(); | |||
|
|||
// TODO: Rewrite this command to be more accurate |
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.
What is inaccurate about it?
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.
We don't account for the acceleration in the beginning which might throw off the calculated kV value? I'm not entire sure though.
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.
We're talking about a simple TimeRotation command, which uses ArcadeDrive internally...it's not doing Profiled path following / feed forward.
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.
Looks good. I think you did the right thing of removing homing and incorporating it into the raising code. It's an implicit assumption that simplifies the code a little.
Rather than returning the default RPM for y-angles outside of the calibrated range, it now returns the RPMs at the bound of that range (if that makes sense). Also applied Spotless, which reformatted a couple of unrelated files.
I'll probably also test this on the bot tomorrow to make sure I didn't break anything :) |
Everything seems to be working (I didn't test climb but I didn't make any changes to it beyond during competition). Merging it now :) |
Here's a short summary of what was changed:
SmartDashboard.put*
calls were commented out to avoid cluttering the dashboardI'll probably do some clean-up before finalizing this as well.