Check-in 5 min
Today is a competition. You build, program, adapt and run on your own, from loose parts to the last run.
Check in at the referee’s table with your loose parts, your hub, your laptop and your journal. From this moment your coach cannot help you. The referee answers questions about the rules only.
Check this season’s General Rules before the real event. Today follows the usual order of a WRO day, squeezed into 90 minutes.
The day 5 min
The referee reads the schedule aloud. Write the times down.
| Time | What happens | Rule |
|---|---|---|
| 0–15 | Check-in, the schedule, one last comparison | Parts stay loose. |
| 15–45 | Build and program | Robot from loose parts. Programs may be ready. |
| 45–55 | Inspection, then round 1 | Robot must fit the start box. One run of 2 minutes. |
| 55–60 | Repair time | Fix what round 1 showed you. |
| 60–70 | Surprise rule | The rule is announced now. Nobody knew it before. |
| 70–85 | Rounds 2 and 3, then results | Best round or total, as this season’s rules say. |
| 85–90 | Self-review | Honest, written, as a team. |
The rounds are short on purpose. Use your strategy from lesson 21: missions in points-per-second order, every risky step with a plan B, and a whole-run clock.
One last comparison 5 min
Look at how far you have come. This is the top of a competition program that picks a mission run from the hub.
SPIKE word blocks
Pybricks Python
from pybricks.tools import hub_menu, StopWatch from base import hub, robot, home_arm home_arm() choice = hub_menu("1", "2", "3") run_clock = StopWatch() if choice == "1": import run_one elif choice == "2": import run_two else: import run_three
| Block | Python | Watch out |
|---|---|---|
| (nothing) | hub_menu("1", "2", "3") | Choose the run with the hub buttons. No laptop needed at the table. |
| (nothing) | import run_one | Each run is its own program in Pybricks Code. |
| (nothing) | home_arm() | Home before the menu, so every run starts with arms in a known place. |
Four levels ago you dragged one block at a time. Today you can read every line of this and say why it is there.
Build and program 30 min
No coach from here to the end. Use your photo sheet, your programs, your journal and the Pybricks documentation.
- Build the robot from loose parts, from your photo sheet.
- Check every cable against the port list.
- Run
calibrateand update the numbers inbase. - Run each mission once on the mat. Fix the first thing that fails, then move on.
- With 5 minutes left, stop changing things. Charge the hub if you can, and check it starts the menu.
A pre-run check worth adding to base
def preflight(): mv = hub.battery.voltage() print("battery mV:", mv) print("left", left_eye.reflection(), "right", right_eye.reflection()) if mv < LOW_BATTERY_MV: hub.light.on(Color.RED) else: hub.light.on(Color.GREEN)
Inspection and rounds 25 min
- Inspection. The referee checks the robot fits the start box. If it does not fit, you fix it before you may run.
- Round 1. Two minutes. The referee scores it on the sheet. You may not touch the robot during the run, except as this season’s rules allow.
- Repair time. Five minutes. Change one thing that round 1 showed you, and only one.
- Round 2 comes after the surprise rule. Round 3 follows.
Sign each scoresheet. Check the referee’s sums before you sign. That is your job, not your coach’s.
Repair time 5 min
Use the checklist from lesson 19, in order: battery, mechanics, sensors, code. These three faults are the ones teams meet most often on a competition day. One mistake each.
Fault 1
choice = hub_menu("1", "2", "3")
if choice == 1:
import run_oneFault 2
from pybricks.tools import hub_menu
from base import hub, robot
choice = hub_menu("1", "2", "3")
home_arm()Fault 3
LEFT_THRESHOLD = 48 # measured at home
def on_black():
return left_eye.reflection() < LEFT_THRESHOLDFault 3 has nothing wrong with the code. The number was measured in a different room. What should the team have done this morning?
The surprise rule 10 min
No coach, no help. At WRO your coach may not touch the robot or the code. The referee will read the rule once and answer questions about the rule only.
The referee announces the surprise rule. You have until round 2 to obey it. Follow lesson 22: read, plan, change, test. Write your reading of the rule in one sentence before you change anything.
Done means: round 2 obeys your written reading of the rule, and you asked nobody for help.
Self-review 5 min
Write it as a team, honestly. Then compare it with what the coach recorded.
- scores for each round, and which mission lost the most points
- your build time, and whether calibrate found any changes
- each fault you found yourselves, and how long it took
- how many times you wanted to ask for help, and what about
- the three things to practise before the real competition, most important first
This is the end of Level 5. You can now build a robot from loose parts, program it in Python from a blank file, find your own bugs and solve a rule you have never seen. That is what WRO tests.