Skip to content
RoboLearn
Not completed

Mid-year robot challenge

ProjectsIntermediate1–2 hPractise the course ↓Before this: Line-following robot, Debugging code

What you’ll do

Teams bring together everything from the first half of the year (sensors, motors, if/else, loops, line following and debugging) in one timed challenge. The aim isn’t just to win: it’s to show a design process, with testing and improvements based on evidence.

The course

START ──── line ────╮
│ (curve)
╭───────────╯
│ [box on the line = obstacle]
╰──────── line ──────── [ FINISH zone ]
  • Black tape line about 2 cm wide on a light floor, 3–5 m long, with at least two curves.
  • One box placed on the line: the robot must stop before touching it (or detour round it for bonus points).
  • A finish zone marked with coloured tape or a black bar across the line.

Rules

  1. Teams of 2–4. Each team gets 3 runs; the best run counts.
  2. The robot must be autonomous: no touching or remote control after the start.
  3. Time limit: 2 minutes per run.
  4. Between runs teams get 5 minutes to change code or hardware, and must write down what they changed and why.
  5. A run ends when the robot reaches the finish, leaves the line for more than 5 seconds, or time runs out.

Scoring

Achievement Points
Follows the line past the first curve 10
Reaches the obstacle without losing the line 10
Stops before touching the obstacle 15
Detours round the obstacle and re-finds the line +20 bonus
Reaches the finish zone 20
Stops in the finish zone 10
Time bonus: finished under 60 s +10
Engineering log (see below) up to 25

The engineering log

For each run, the team records: what they changed, what they expected, what happened (with numbers), and what they’ll try next. This is worth as much as most of the course: good engineers learn from every run.

Finished this lesson?