Unit 02
Writing a Command
By the end of this unit you can write each part of a command, say why each line lives where it does, and commit a movement command that gives up safely when it gets stuck.
Robotics Programming · members' unit
Writing a Command 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 · 17 min read
- One real command, all the way through
- Somewhere to put your own code
- Getting code onto the actual robot
- The constructor: what never changes
- initialize(): what depends on the moment
- execute(): a little work, then return
- isFinished(): arrived, or out of patience
- end(): leave it safe, and say how it went
- Why Artemis wraps the library’s turn
- Your first real command
8 quick checkssteppercode 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 0.3.6 source
- Gilmour Academy Competitive Robotics — Software Team course notes — the chapters these standards were harvested from