Update Swerve Bot to account for new chassis size & motor location

[alexemrie]

Issue

Now that we have a new chassis, we need to ensure the constants generated are updated to reflect the new dimensions.

• These are located in our code in the TunerConstants.java.

Context

The Swerve Bot drive code project was generated using the CTR Swerve Project Generator. We can see this reflected in a code comment within TunerConstants.java.

// Generated by the Tuner X Swerve Project Generator // https://v6.docs.ctr-electronics.com/en/stable/docs/tuner/tuner-swerve/index.html

TODO

• Follow the instructions in documentation here to update project with our latest dimensions (try using the "Import Project" option).
• Test by deploying to robot.
• Push changes to update our GitHub project with the new code.
• Optional: Link commit in GitHub to this issue for future reference.

[alexemrie]

New repo created using updated chassis size.

• https://github.com/PumpkinBots/PumpkinBots_2024_Swerve_KitBot/

There was an issue with the forward/reverse direction when operating via teleop mode using Xboxcontroller after updating chassis size in Phoenix Tuner. A temporary fix was added which fixes the issue by reversing the sign on the joystick.

• Possible Cause: Mounting after new wiring may have switched some of the CANIDs? Missed drive validation?
• Fix: Repeat Encoder Calibration and/or Validating the Drivetrain from documentation.
• Why fix: Deviating from the boilerplate code could cause unwanted downstream side effects and make debugging more difficult.

  NOTE: Code comments no longer reflect the current behavior

TODO: Move repo for Swerve code to Pumpkin-Bots org.

• https://github.com/orgs/Pumpkin-Bots/repositories