WRO SA Competition Preparation Guide

What is WRO SA?

The World Robot Olympiad South Africa (WRO SA) is the national qualifying round of the World Robot Olympiad — an international robotics competition that takes place in a different country every year. It brings together young people from around the world to develop their creativity and problem-solving skills through robotics challenges.

Key facts:

• Open to learners aged 8–19 (divided into age categories)
• Teams of 2–3 learners + 1 coach
• Multiple categories: RoboMission, RoboSports, Future Innovators, Future Engineers
• Regional rounds → National finals → International competition
• Website: wro-association.org and WRO SA on Facebook

WRO Categories Explained

RoboMission (Most popular for beginners)

• Robots must complete specific missions on a themed game mat
• The theme changes every year (e.g., "Earth Allies" 2024, past themes included healthcare, smart cities, food)
• Teams build and programme a robot to autonomously complete tasks (moving objects, following lines, navigating obstacles)
• No remote control — the robot must run entirely on its own programming
• Scored on: tasks completed, time taken, and robot design
• Categories by age:
  • Elementary: Ages 8–12
  • Junior: Ages 13–15
  • Senior: Ages 16–19

Future Innovators

• Open-ended project-based category
• Teams build a robot that solves a real-world problem related to the year's theme
• Judged on: innovation, engineering, programming, teamwork, and presentation
• Includes a poster and verbal presentation to judges
• Great for creative thinkers who want to invent something new

RoboSports

• Robot vs robot competitive games (e.g., robot football/soccer)
• Fast-paced, exciting, crowd-friendly
• Robots must be autonomous — react to the game environment in real-time
• Good for learners who enjoy competition and fast iteration

Future Engineers

• Self-driving car challenge
• Robot vehicle must navigate a track, avoid obstacles, and follow traffic rules
• More advanced: involves camera processing, path planning, and decision-making
• Best for senior learners with prior robotics experience

Typical Rules & Constraints

Rules vary each year, but these are common across most WRO categories:

Robot Specifications

• Size limit: Robot must fit within a 25cm × 25cm × 25cm box at the start
• Can expand: The robot may expand once the round begins
• Controller: Usually Arduino, LEGO, or other approved platforms
• Autonomous only: No remote control, no wireless communication during the run
• Build from scratch: At some events, robots must be assembled on-site (not pre-built)

Competition Format

• Teams get 2–3 attempts (runs) at the challenge
• Best score from all attempts counts
• Timed runs (usually 2 minutes per attempt)
• Practice time is provided before the scored rounds
• Judges may ask technical questions about your design and code

What's Allowed

• Any programming language (Arduino IDE, Python, LEGO Mindstorms software)
• Custom 3D-printed parts (in some categories)
• Sensors: ultrasonic, IR, colour, gyro, light, etc.
• No pre-programmed "solutions" — code must be team-written

8-Week Preparation Timeline

Week 1: Understand the Challenge

• Read the rules document carefully. Read it again. Then read it a third time
• Watch YouTube videos of past WRO competitions (search "WRO 2024" or "WRO SA")
• Discuss the challenge tasks as a team — break down each task individually
• List all the robot capabilities needed (line following, object detection, colour sensing, etc.)
• Output: A written list of every task the robot must complete

Week 2: Design Phase

• Sketch 2–3 robot designs on paper
• Consider: centre of gravity, wheel placement, sensor positions
• Decide on the base platform (custom or kit-based)
• Think about modularity — can you build attachments that swap for different tasks?
• Output: A chosen design sketch with labelled parts and dimensions

Week 3: Chassis Build

• Assemble the physical robot frame
• Mount motors and wheels
• Ensure it fits within the 25×25×25 cm starting size
• Test basic movement: forward, backward, left turn, right turn
• Output: A rolling robot that moves reliably in all directions

Week 4: Sensors & Wiring

• Mount all planned sensors (line sensors, ultrasonic, colour, etc.)
• Wire everything to the controller (Arduino, LEGO hub, etc.)
• Test each sensor individually — can you read values?
• Create a wiring diagram for reference
• Output: All sensors mounted, wired, and reading correctly

Week 5: Programming — Task by Task

• Break the challenge into individual tasks
• Programme each task separately first (e.g., "follow line to intersection", "pick up block", "turn 90 degrees")
• Test each task 10 times — note the success rate
• Debug failures — is it mechanical (physical) or logical (code)?
• Output: Each individual task working at 80%+ success rate

Week 6: Integration & Sequencing

• Combine all tasks into one continuous programme
• Handle transitions between tasks (e.g., "after line following, switch to obstacle avoidance")
• Time the full run — are you within the time limit?
• Use state machines or functions to keep the code organised
• Output: Full run completing all tasks (even if imperfect)

Week 7: Optimise & Refine

• Run the full challenge 20+ times
• Record success rate for each task in a table
• Fix the weakest points first — focus on reliability over speed
• Consider: lighting conditions, surface friction, battery levels
• Fine-tune sensor thresholds and motor speeds
• Practise on-site assembly (if rules require it)
• Output: 70%+ overall success rate on practice runs

Week 8: Competition Prep

• Mock competition: Run a timed practice with 2–3 attempts under pressure
• Pack everything: robot, spare parts, tools, batteries, chargers, laptop, USB cables
• Prepare a troubleshooting checklist (see below)
• Review rules one final time — any last-minute rule changes?
• Prepare your presentation (for Future Innovators or if judges ask questions)
• Get a good night's sleep
• Output: Team is confident, prepared, and packed

Robot Design Principles

Keep It Simple

Your robot doesn't need to be complex to win. The best competition robots are often the simplest — fewer moving parts means fewer things that can break.

Low Centre of Gravity

Heavy components (batteries, motors) should be as low as possible. A robot that tips over during a run loses valuable time.

Consistent Wheels

Make sure both drive wheels are identical and firmly attached. Even tiny differences in wheel size or traction cause the robot to drift.

Secure Wiring

Loose wires are the #1 cause of competition failures. Use cable ties, tape, or channels to secure every wire. A wire that comes loose mid-run means a restart.

Modular Attachments

If the challenge has multiple tasks, design attachments that can be swapped or deployed. Some teams use servo-powered arms that deploy at specific stages.

Test on the Actual Surface

Practice mats and competition mats may have different friction. If possible, get a practice mat printed at the same specifications. At minimum, test on a similar surface type.

Programming Strategy Tips

Use Functions

Break your code into functions: followLine(), turnLeft90(), pickUpBlock(), avoidObstacle(). This makes debugging much faster.

Calibrate Sensors

Hard-coded sensor values often fail in different lighting conditions. Add a calibration routine at the start of each run that reads the actual sensor values and sets thresholds dynamically.

Use Timeouts

If a task takes longer than expected, move on. A robot stuck trying to pick up a block wastes time that could be spent scoring points on other tasks.

Print Debug Info

Use Serial.println() during practice to see sensor values in real-time. This helps you understand exactly what the robot "sees" and why it's making certain decisions.

PID Control (Advanced)

For smooth line following, implement a PID (Proportional-Integral-Derivative) controller instead of simple on/off steering. This gives much smoother movement and faster following speeds.

Battery Management

Robot behaviour changes as battery voltage drops. Test with both fresh and partially-used batteries. Consider adding a voltage check at the start of each run.

Competition Day Checklist

What to Pack

The Robot:

• [ ] Robot (obviously!)
• [ ] All attachments and modular parts
• [ ] Spare parts: extra sensors, wires, connectors, screws, nuts
• [ ] Tools: screwdrivers, pliers, wire strippers, cable ties
• [ ] Spare Arduino / controller board
• [ ] USB programming cable
• [ ] Batteries (fresh set + spares)
• [ ] Battery charger + power bank
• [ ] Multi-plug extension cord

The Code:

• [ ] Laptop with latest code
• [ ] USB drive with code backup
• [ ] Printed code listing (for debugging without a screen)
• [ ] Arduino IDE installed and tested

The Team:

• [ ] Team registration documents
• [ ] School permission letters
• [ ] ID / proof of age for all team members
• [ ] Matching team shirts (if you have them — looks professional!)
• [ ] Water bottles and snacks
• [ ] Notebook and pen for recording observations

On Arrival

1. Register and get your team number/table assignment
2. Set up your workspace — lay out tools and parts neatly
3. Check the competition mat/arena — is it the same as your practice setup?
4. Calibrate sensors on the actual competition surface
5. Do a practice run during allocated practice time
6. Watch other teams — you can learn from their approaches
7. Stay calm. Things will go wrong. The teams that win are the ones that adapt.

During Competition

• Breathe. Nerves are normal
• Don't panic-rebuild between attempts — small adjustments only
• Use your attempts wisely — if Run 1 goes well, consider what to change for Run 2
• Talk to each other — communication is key. The navigator spots things the driver misses
• Enjoy it. Win or lose, you've built something incredible

After the Competition

Win or Lose

• Celebrate the effort. Getting to competition day is already a huge achievement
• Debrief as a team: What worked? What would you change?
• Document everything: Photos, videos, notes, scores — this helps next year's team
• Thank your sponsors and school with a report and photos
• Share on social media — inspire other schools to start their own clubs
• Start planning for next year while the motivation is high

Useful Links

• WRO Official: wro-association.org
• WRO SA Facebook: Search "WRO South Africa" on Facebook for local updates
• Rules Documents: Published annually on the WRO website (usually January/February)
• YouTube: Search "WRO 2024 competition" to see past events
• Arduino Reference: arduino.cc/reference

This resource is provided free by M²P INNOVATION Hub. We compete in WRO SA ourselves and are happy to mentor schools preparing for their first competition.