Note: All commits are made by Grace (GP), I keep forgetting to write my initials sorry...

Welcome to the repository for Flagship 3140's Jackbot code for the 2024 FRC season. This README provides an overview of our robot, its subsystems, and how to use this codebase.

• https://www.youtube.com/@UnqualifiedQuokkasRi3D/featured
• Programming Style Guide: https://docs.google.com/document/d/1gFDDgxJKg1U1g2qiMRLbdnMCAiIlr2gexJFJaxHWk/edit?usp=sharing

Our robot, Jackbot, is designed to: pick up notes from the ground, pick up notes from the human player station, shoot notes in the speaker and amp, and drive under the stage. It has an arm subsystem, a climber subsystem, a shooter subsystem, an intake subsystem (the shooter and intake are grouped together though), and uses tank drive to move.

Teleop strategy: During teleop, the player will control the robot to pick up notes on the ground on its side of the field and also go across the field to pick up notes dropped by the human player. The robot will then shoot the notes in both the speaker and the amp until the endgame buzzer goes off, and climb onto a chain (the stage), possibly climbing with another robot.

Auto strategy (to be determined): [insert auto strategy here]

The arm uses two motors to move up and down, which are configured as a group, allowing the intake/shooter subsystem to move to the ground to pick up the notes and move back up to shoot them.

The intake and shooter are both in one subsystem, connected to the top of the arm and using one motor. It picks up a ground note using 2 sets of wheels, then another set of wheels pushes the note into a shooter where it is then shot into the air through another set of wheels.

The climber is made up of two hooks that lift the robot off the ground in endgame.

This robot uses tank drive to move, and it includes 4 TalonSRX motors, white/80A durometer HiGRip wheels, and an 8.46:1 gear ratio.

To deploy and run this code on the robot, follow these steps:

1. Open the project in your preferred IDE (we use WPIlib VSCode).
2. Ensure that all dependencies are correctly installed and configured.
3. Build the project to ensure there are no compilation errors.
4. Deploy the code to your robot using your preferred deployment method (we use Ethernet).
5. Test each subsystem to verify functionality.

If you would like to contribute to the robot code, please follow these guidelines:

• Do not code directly in the main branch, nor committ to main.
• Make your changes and ensure that the code compiles without errors.
• Test your changes thoroughly.
• Submit a pull request, describing the changes you've made and any relevant information.