Unit 5: WPILib and Robot Code

This is a self-paced Unit. Work through the three lessons in order, keep the evidence you create, and finish with the Unit Wrap-Up. You do not need access to a competition robot for every task. When hardware is unavailable, use the simulation, diagram, log, photo, or documented-analysis path described in the lesson.

The question

How is robot software organized so that code can control hardware without becoming one giant file?

What you will understand

By the end of this Unit, you should be able to explain the central system relationships behind wpilib and robot code instead of relying on part names or memorized steps. You will trace cause and effect, identify important dependencies, and recognize at least one failure mode that can produce misleading symptoms.

What you will do

1. Read From Project to Robot Loop and build the foundation.
2. Continue with Subsystems, Commands, and Triggers and inspect the mechanism, boundary, or tradeoff.
3. Finish Simulate, Deploy, Observe, Debug by applying the reasoning to a real, simulated, or documented FRC system.
4. Keep the artifact and evidence you produce. You will reuse earlier work in the final competition-readiness dossier.

What you will produce

Your main Unit artifact is a command-based robot software map and a short tested code change. It should be understandable to another learner without a verbal explanation. Label assumptions, measurements, device names, paths, states, or decisions where they matter.

How this Unit builds

The course is cumulative. Each Unit adds another layer to the same robot:

game objective
    ↓
system architecture
    ↓
mechanism + electrical system
    ↓
robot software
    ↓
sensing + control
    ↓
autonomous + driver operation
    ↓
strategy + reliability
    ↓
competition readiness

Unit 5 contributes evidence to that chain. Do not throw away a useful diagram or test record just because the Unit is complete.

Key vocabulary

WPILib, robot lifecycle, subsystem, command, trigger, scheduler, simulation, log

Estimated time

Plan for roughly 2–4 hours. Hardware testing, CAD, fabrication, or deeper extensions may take longer. The goal is evidence, not racing the clock.

Evidence to keep

Keep the Unit artifact, at least one concrete observation or test result, one identified limitation or failure mode, and any revision you made after checking the evidence.