Skip to content
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

Merged
merged 18 commits into from Mar 31, 2022
Merged

Merge Oregon State Fair changes #3

merged 18 commits into from Mar 31, 2022

Conversation

5t0n3
Copy link
Member

@5t0n3 5t0n3 commented Mar 27, 2022

Here's a short summary of what was changed:

  • Homing and lowering of the new intake was implemented
  • We replaced the PCM and some solenoid ports got swapped; these were updated in Constants.java
  • A compressor toggle was added to the dashboard to avoid the battery voltage drops it causes, but ended up not being necessary
  • Most SmartDashboard.put* calls were commented out to avoid cluttering the dashboard
  • An RPM offset configurable during the match was added in case we were consistently over/undershooting

I'll probably do some clean-up before finalizing this as well.

nolanhergert and others added 10 commits March 23, 2022 16:55
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.
@5t0n3 5t0n3 self-assigned this Mar 27, 2022
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
Copy link
Contributor

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?

Copy link
Member Author

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.

Copy link
Contributor

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.

Copy link
Contributor

@nolanhergert nolanhergert left a 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.
@5t0n3
Copy link
Member Author

5t0n3 commented Mar 30, 2022

I'll probably also test this on the bot tomorrow to make sure I didn't break anything :)

@5t0n3
Copy link
Member Author

5t0n3 commented Mar 31, 2022

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 :)

@5t0n3 5t0n3 merged commit 8901277 into main Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants