How hammerheads5000/2024crescendo works
Project type and purpose
• This is an embedded control‐system project for an FRC competition robot (Team 5000, “Crescendo” 2024 season).
• It uses the WPILib command‐based framework, the PathPlanner trajectory library, vendor motor‐controller libraries (Phoenix, REV), and vision (PhotonVision/AprilTags).
File structure
• Build & config
– Gradle build scripts (build.gradle, settings.gradle, gradle/wrapper/…)
– vendordeps/*.json define external libraries (WPILib, Phoenix, REV, PathPlannerLib, photonlib)
• Path definitions
– pathplanner/ and src/main/deploy/pathplanner/… contain JSON navgrids and .path/.auto files that define autonomous trajectories and sequences.
• Java source tree (src/main/java/frc/robot)
– Core entry points: Main.java, Robot.java, RobotContainer.java, Constants.java
– Subsystems: packages under subsystems/ controlling hardware abstractions (Swerve drive, Shooter, Intake, TrapMechanism, Climber, Lights, AprilTag vision).
– Commands: under commands/ broken out by function (swerve, shooter, intake, trap mechanism, etc.) and autos.
• Deployment
– src/main/deploy/example.txt and pathplanner deploy files get pushed to roboRIO for runtime configuration.
Insights from README
• Confirms this is FRC Team 5000’s 2024 robot control code.
Be very detailed
• Break out each subsystem (Swerve, Shooter, Intake, TrapMechanism, Climber, Lights, Vision) as its own component
• Commands that orchestrate multi‐subsystem behaviors (e.g., PickUpNoteAndShootCommand)
• Vendor SDK layer between subsystems and physical actuators/sensors
• Autonomous routine loader (PathPlannerLib → CommandGroups)
• Don’t forget build/deploy pipeline: Gradle → roboRIO