Unit 03
Subsystems and Hardware
By the end of this unit you can write a subsystem that claims its own hardware and says what it can do, read a sensor into something a command can act on, and put every number in the one home its lifetime calls for.
Robotics Programming · members' unit
Subsystems and Hardware is behind a locked door
Units in Robotics Programming are for people taking the course. Getting in takes a link or a key — signing in on its own doesn't do it.
What's in this unit · 11 min read
- The part of the robot that stays
- One motor, one owner
- Name it once
- Where a number lives
- The dial that did nothing
- Reading a sensor
- A reading is not a decision
- State inside a subsystem
- When a command is one line
10 quick checkscode exercises
1 Sign in
With your school Google account. This is how your work reaches the gradebook — it doesn't open the unit by itself.
A key unlocks this browser and keeps your progress here; signing in keeps it with you across devices. Either way the key itself is only ever checked as a hash. Manage all of this on your account, read what signing in stores, or go back to Robotics Programming.
Sources
- GA-Moonshots — Artemis, the team base code
- Seattle Solvers — SolversLib documentation
- Gilmour Academy Competitive Robotics — Software Team course notes — the chapters these standards were harvested from