Events
Robotics competitions
We run the events and host the teams that turn up to win them. Rules published in advance, judging criteria in the open, and the archive kept because history is the credibility.
Registration open
What is next
Nothing open at the moment.
No surprises on the day
How an event runs
- 01
Rules published
Four weeks before, as a versioned document. Every later change is listed with its date, so nobody builds against a rule that moved.
- 02
Registration and scrutiny
Team of two to five. Dimensional and safety scrutineering on arrival, and you get told what to fix rather than just failed.
- 03
Practice rounds
Track time before it counts. Every team gets the same allocation, drawn by lot.
- 04
Judged rounds
Scores shown live. The rubric is the same document you were sent four weeks earlier.
- 05
Debrief
Written feedback per team, whether you placed or not. This is the part most events skip and the part teams remember.
From the archive · highlights
AIRENA-2026
Three phases on one course. The hard part was never the driving: every machine ran micro-ROS on an ESP32 and decided nothing for itself. At the entry to each phase the team had to publish that phase's behaviour from a laptop running ROS, so the vehicle was steered by off-board compute over UDP while it drove.
-
PHASE 01
Line following
Track only. Follow the line end to end, nothing in the way, and a clean lap or nothing.
-
PHASE 02
Obstacle avoidance
No line to hold. An obstacle course crossed on sensing alone, with the behaviour for it published before the run began.
-
PHASE 03
Line following with obstacles
Both at once: hold the line, leave it to clear what is standing on it, and find it again on the other side.
Everything we have run
The archive
Kept in full, including the editions that were small. A history you can check is worth more than a number you cannot.
Colleges and institutions
Run one with us
We bring the arena, the scoring, the scrutineering and the marshals. You bring the room and the teams.