IronPulse Robot

Subsystem state-machine code for FRC 6941 IronPulse's REEFSCAPE 2025 robot. Programming leader; team qualified for the FIRST Championship in Houston.

  • Role: Programming Leader (sole lead over 20+ programmers)
  • Season: REEFSCAPE 2025 — team qualified for the FIRST Championship in Houston
  • Team: FRC 6941 IronPulse
  • Robot: Specter
  • Channel: @ironpulse6941 on YouTube

The robot — Specter (2025 REEFSCAPE reveal)

2025 REEFSCAPE season

2025 REEFSCAPE Regional Recap — how the season played out.
Chasing Dreams — IronPulse's Impact Award video, 2025.

Building the robot

Behind-the-scenes footage and photos from the shop — assembly, iteration, testing.

My contributions

State-machine code for the robot’s subsystems — intake, arm, elevator, scoring mechanism. In a competition robot, each subsystem has to transition between well-defined states quickly and predictably — intake running, intake stowed, arm scoring, arm resetting — because the drive team is making decisions on a 15-second time budget.

State machines are the right abstraction for this because:

  • The behavior is legible to both software and the drivers. The drive team can learn the robot by learning the state names.
  • Transitions are explicit. Illegal moves (e.g. extending the arm while stowed) are physically impossible rather than relying on code discipline.
  • Debugging under competition pressure is tractable. You can see which state the subsystem thinks it’s in and reason about why.

Also

For the matching web platform that captures and surfaces this match data, see IronPulse Scouting.