Home
// Digital Technology - Year 9 & 10 //

ROBOT WARS

Over the next 10 lessons your crew will build an mBot2 from a box of parts, design and 3D print your own armor for it, teach it to think, and drive it into the sumo arena. You are the engineer. You are the coder. You are the pit crew.

🔧 Build Your Bot
🖨️ 3D Printed Armor
🕹️ Remote Control
🥊 Sumo Showdown
Your Kit
💻
Coding Platform
ide.mblock.cc - runs in your browser, no install needed. Create a free account so your work saves to the cloud. Desktop version on mblock.cc/download if you need it.
🤖
The Robot & Controller
mBot2 - a CyberPi brain, an Ultrasonic Sensor, and a Quad RGB Sensor. Build time is roughly 30-45 minutes as a crew. Drive it with the Bluetooth Controller V1 (needs 2x AA batteries), which pairs to your bot through mBlock's controller extension in Lesson 4.
✏️
Design & Print
Tinkercad, free in your browser - this is where you'll design your printed armor. Designs print on 5x FlashForge Adventurer 3 printers, 150mm x 150mm x 150mm build volume each. Submitted files print overnight or over lunch - you won't be waiting around for your own print.
🧠
AI Assistant
copilot.microsoft.com - ask it "How do I do X in mBlock?" whenever you're stuck. Always verify against the Makeblock Help Center.
⚠ AI can get sensor and block names wrong - always double-check!
🏟️
Crew & Kit Number
12 mBot2 kits and 12 controllers between the class - crews of 2-3 share one bot. Sort your driver, coder and pit crew roles early. Every kit box is numbered 1-12. Your crew is assigned one number for the whole project - same box, same bot, every single lesson. Write it on your Reflection Log.
🥊
Robot Wars Day Rules
Two bots enter the circle, first one pushed out (or that stops moving) loses the bout. No weapons, no launching from outside the ring.
// Primary Objective

Design, build and program a combat robot capable of holding its own in a 1-on-1 sumo bout - then prove it works, in person, on Robot Wars Day.

Assemble a working robot from raw parts, following technical instructions exactly
Design your own 3D printed armor in Tinkercad, matched to your combat strategy
Program movement using both manual controller input and autonomous sensor logic
Test & Iterate against real opponents in the arena, then improve across 2 build-test-reflect cycles using evidence, not guesswork
// Marking Key & Rubric
Criteria Standby
(0-1)
Operational
(2-3)
Combat Ready
(4)
Battle Hardened
(5)
Score
Build, Assembly & Armor Robot incomplete or needed teacher help to finish the build Robot fully assembled and powers on reliably; a printed armor piece is fitted Assembly is neat, secure, and wiring is tidy; armor is mounted securely with no rattling Build shows extra reinforcement or thoughtful design choices; armor design is clearly matched to your combat strategy / 5
Programming Robot moves only with heavy teacher support Robot drives via code and responds to the Ultrasonic Sensor Manual and autonomous control both work reliably Sensor and controller logic combined smoothly, few bugs / 5
Strategy & Iteration No clear strategy chosen, reflection log incomplete Strategy chosen, at least one reflection completed Clear v1 to v2 changes, each backed by a reason Changes show genuine testing evidence and real improvement over time / 5
Robot Wars Day Did not participate, or bot was not competition-ready Competed in at least one bout, followed the rules Competed fully, worked well with crew throughout Strong sportsmanship, helped others, clear ownership of role / 5
Total / 20
Scroll sideways to see every column
Mission Log
Week 1
01
🔧 Build & Power Up
▾
// MISSION OBJECTIVEFully built robot powers on and shows the CyberPi home screen. mBlock account created.
  • Get into your crew (2-3 people) and collect your assigned numbered kit box (1-12) - this is your bot for the whole project. Write the number on your Reflection Log
  • Open the official Makeblock build guide and check every part against the parts list before you touch a screwdriver. Small parts go straight into the tray - nothing loose on the desk
  • Assemble the base chassis, wheels and motors, following the guide step by step - screws finger-tight first, then firm
  • Mount the CyberPi brain, plug the Ultrasonic Sensor and Quad RGB Sensor into their mBuild ports, and connect the motor cables to EM1/EM2
  • Get a teacher check before you power on for the first time - a wrong cable is easy to fix now, hard to fix later
  • Power on the CyberPi and explore its built-in screen and buttons - it's more than just a brain, it's a mini computer
  • Go to ide.mblock.cc and create your free crew account - one account can be shared across the crew
💡 HintIf a screw or connector feels like it's really fighting you, stop and double-check you've got the right hole or port before forcing it. Forcing the wrong one is the easiest way to snap something before you've even switched the robot on.
🔍 Google Image Search"mbot2 assembly guide diagram"
// ASK AI"What does each mBuild port on the CyberPi connect to, and how do I tell them apart?"
02
▶️ Hello mBlock
▾
// MISSION OBJECTIVEYour bot moves forward, turns and stops on command from code you wrote yourself.
  • Collect your numbered kit box, open mBlock, add the mBot2 device under Devices, and connect your robot (USB cable is easiest for your first connection)
  • Explore the mBot2 Chassis blocks - drag a "move forward" block into the coding area and run it
  • Get your bot to drive forward, reverse, spin on the spot and stop, using at least 4 different blocks
  • Try changing a light or sound block on the CyberPi screen so it reacts every time your bot moves
💡 HintTest one block at a time. Drag a single "move forward" block in on its own and run it before you start chaining blocks together - if something goes wrong with 6 blocks stacked up, you won't know which one broke it.
// mBlock - Basic Movement
when green flag clicked
    move forward at 50% power
    wait 1 second
    turn right 90 degrees
    wait 1 second
    move forward at 50% power
    wait 1 second
    stop moving
// ASK AI"How do I make the mBot2 move forward, turn, and stop in mBlock?"
// ASK AI"What's the difference between 'move forward' and 'set motor power' blocks in mBlock?"
// LEVEL UPProgram your bot to drive a full square and finish where it started, using a repeat block instead of stacking the same blocks four times. Measure how far off the start line it ends up, then adjust your turn until it gets closer.
Week 2
03
📡 Sensing the World
▾
// MISSION OBJECTIVEAn autonomous mission using the Ultrasonic Sensor that avoids or seeks an object, tested at least 3 times.
  • Learn what the Ultrasonic Sensor measures and roughly how far it can "see" in front of the bot
  • Build a mission where your bot stops or turns before it hits a wall (obstacle avoid)
  • Stretch goal: flip it - make your bot seek out and drive toward an object instead of avoiding it
  • Challenge: place 2 objects on the floor and get your bot to navigate around both without a crash
💡 HintStart with a big, easy-to-hit distance like 15cm, not a tiny one. Get the "if too close, turn" logic working first, then shrink the number down once it's actually working - trying to fine-tune a broken block first just wastes your lesson.
// mBlock - Obstacle Avoid
forever
    if distance (cm) < 15 then
        turn left 90 degrees
    else
        move forward at 50% power
    end
end
// ASK AI"How do I use the Ultrasonic Sensor to make my mBot2 avoid or seek an object?"
04
🎮 Taking the Controls
▾
// MISSION OBJECTIVEYour bot is fully drivable by controller, with at least one custom button action mapped.
  • Install 2x AA batteries in your Bluetooth Controller
  • In mBlock, add the Bluetooth Controller extension blocks and pair your controller to your CyberPi
  • Map the joystick and at least 2 buttons to movement - forward/back/turn, plus one custom "boost" or "spin" action
  • Test drive your bot manually around a taped course - can you complete a lap without going off track?
💡 HintMap one button at a time and test it before you add the next one. If you wire up all your buttons at once and nothing works, you'll have no idea which mapping is the broken one.
// mBlock - Controller Mapping
when button A pressed
    play sound "boost"
    set motor power to 100%
    wait 0.5 seconds
    set motor power to 50%

when joystick pushed forward
    move forward at joystick speed
// ASK AI"How do I pair a Bluetooth Controller to my mBot2 in mBlock and map buttons to actions?"
// LEVEL UPMap one more action to a button of your choice: a quick "escape" that backs your bot away for half a second. Test it on the taped course. When would a driver actually use it in a sumo bout?
Week 3
05
🥊 Combat Strategy
▾
// MISSION OBJECTIVEStrategy chosen, v1 code built and saved, v1 armor designed and submitted for printing, crew roles assigned.
  • Learn the sumo rules: two bots enter the circle, first one pushed out (or that stops moving) loses the bout. No weapons, no launching from outside the ring
  • As a crew, choose your Combat Strategy for Robot Wars Day:
The RammerFully manual, driven by controller. Wins on speed, driver skill and a wide, low stance.
The SentinelFully autonomous. Uses the Ultrasonic Sensor to detect and charge an opponent - no driver at all.
The TacticianHybrid - a human drives, but code automatically boosts power when the Ultrasonic Sensor detects something close ahead.
  • Build your v1 code for your chosen strategy and save it
  • Assign crew roles for testing: Driver, Coder, Pit Crew
  • Open Tinkercad and design a v1 armor piece that matches your strategy - a wide flat plate for The Rammer, a low wedge for The Tactician, or a minimal shroud for The Sentinel that doesn't block the Ultrasonic Sensor's view
  • Mount your armor to the front of the chassis using the existing frame holes and M4 screws from your kit - no glue needed
📏 Confirmed Part Measurements
mBot2 assembled footprint180mm long x 130mm wide x 90mm tall - keep your armor within this footprint so it doesn't catch on the arena edge
Chassis frame holesM4 screws on an 8mm hole spacing (Makeblock's standard beam pattern) - space your mounting tab's holes in multiples of 8mm so they line up
Suggested armor thickness3-4mm - rigid enough to survive a hit, light enough not to slow your bot down
💡 HintIf you're not sure which strategy to pick, go with The Rammer first. It's the simplest to get working reliably, and you can always blend in Sentinel or Tactician logic later once the basics are solid.
// ASK AI"How do I combine Bluetooth Controller input and Ultrasonic Sensor logic in the same mBlock project?"
// ASK AI"How do I design a flat mounting tab with evenly spaced holes in Tinkercad?"
📤 Submit via ConnectYour chosen Combat Strategy, v1 code (screenshot or shared mBlock project link), and your v1 armor Tinkercad file (share link or exported .stl)
06
🏟️ Arena Test 1
▾
// MISSION OBJECTIVE3 test bouts completed against another crew, reflection log filled in with at least one concrete change identified.
  • Collect your printed v1 armor and bolt it onto the front of your chassis using the M4 screws from your kit
  • Set up the sumo circle with another crew and run 3 friendly practice bouts - this is not scored
  • Pit crew records what happened each bout - who won, why, and what nearly went wrong, and whether the armor helped, got in the way, or came loose
  • Fill in your Reflection Log: what worked? what didn't? what's one thing you'll change before v2 - code, armor, or both?
💡 HintPick just one change for v2, not five. A robot that gets one thing properly fixed beats a robot with five half-finished changes - you've only got one lesson to rebuild, whether that's code or a reprint.
💡 HintIf your armor rattles or falls off during a bout, that's real evidence for your reflection log - "loose mount" is a perfectly good v2 change to write down.
🔍 Google Image Search"sumo robot testing checklist"
// ASK AI"What are good questions to ask my crew when writing a robotics reflection log entry?"
📤 Submit via ConnectYour Reflection Log 1
// LEVEL UPDraw the sumo circle from above and mark where each of your 3 bouts ended: pushed out, stopped, or won. Do you see a pattern, like always losing from the same side? Use it to pick your v2 change.
Week 4
07
🔁 Iterate: Build v2
▾
// MISSION OBJECTIVEv2 built and saved, with at least one meaningful change from v1 that you can explain.
  • Make the change(s) you identified in your reflection log - new code, a redesigned armor piece, or both
  • Blend strategies if you've learned something - for example, adding autonomous detection to a mostly manual bot
  • Save your v2 code separately from v1 - don't overwrite it, you might want to compare later
  • If your armor is changing, edit a copy of your v1 Tinkercad file rather than starting from scratch, and submit it for printing straight away so it's ready by next lesson
💡 HintSave v2 as a new file (like "v2" in the filename), don't just edit v1 and overwrite it. If v2 turns out worse, you'll want to go straight back to v1 without rebuilding it from memory - same goes for your Tinkercad armor file.
// ASK AI"How do I save a copy of my mBlock project without overwriting the original?"
📤 Submit via ConnectYour v2 code (screenshot or shared mBlock project link), and your v2 armor Tinkercad file if it changed
// LEVEL UPBefore you test v2, write a prediction with a number: "v2 will win at least _ of 3 bouts because _". You will check it against the real result in Mission 08.
08
🏟️ Arena Test 2
▾
// MISSION OBJECTIVE3 test bouts completed against a new crew, second reflection completed with evidence-based reasoning.
  • If you printed new armor last lesson, collect it and bolt it on before you start testing
  • Test v2 against a different crew than last time - 3 bouts
  • Compare this result to Mission 06 - did your change actually help, or did it just feel like it should?
  • Update your Reflection Log: what's the evidence, and what's the next change for final tuning?
💡 Hint"We won more" is not evidence on its own - write down the actual score or bout count, like "won 2 of 3" vs last time's "won 1 of 3." Numbers make your reflection log way easier to write and way more convincing.
// ASK AI"What's a simple way to record and compare test results across two robot versions?"
📤 Submit via ConnectYour Reflection Log 2
// LEVEL UPTurn your v1 and v2 results into a small table or bar chart in Canva, with the same 3 bouts side by side. Would someone who wasn't there be able to see at a glance which version was better?
Week 5
09
🛠️ Polish & Tuning
▾
// MISSION OBJECTIVEBot is competition-ready. Final code saved. Battery levels checked.
  • Make your final round of changes based on Mission 08's evidence - if your v1/v2 strategy has been solid, polish rather than overhaul. Know when to stop changing things
  • Check batteries are fresh in both the CyberPi and the controller - a flat battery loses more bouts than bad code
  • Check your armor's screws are still tight - a loose mount is a common last-minute failure, not just an early one
  • Run a short practice bracket against the whole class to get a feel for the competition format
  • Save your final code and label your bot clearly with your crew name and kit number
💡 HintIf it's working, leave it alone. The most common way to lose a bout on Robot Wars Day is changing something at the last minute that used to work fine - only fix things that are actually broken today.
// ASK AI"What should I check on a battery-powered robot the day before a competition?"
⚡ Bonus Challenge - Network Duel The CyberPi has built-in WiFi and can broadcast a message to every other mBot2 in the room. Crews who are ahead of schedule can prototype a "tag" mode: press a button to broadcast a hit, give your bot an HP variable on screen, and dock HP when a hit is received. It's not part of Robot Wars Day, but it's a genuine extension if sumo feels solved.
📤 Submit via ConnectYour final competition-ready code
10
🏆 Robot Wars Day
▾
// MISSION OBJECTIVECompete in at least one bracket bout. Complete the post-event reflection as a crew.
  • Collect your numbered kit box, arrive with a charged robot and a charged controller
  • Safety briefing first - stay behind the line, no touching a bot mid-bout, referee's call is final
  • Single-elimination bracket, sumo rules from Mission 05
  • Knocked out? Referee a bout or run the scoreboard for the rest of the day
💡 HintNerves make people rush their driving. If you're up next, take one slow breath and remind yourself of your strategy before you step up to the circle - a calm driver beats a rushed one almost every time.
📤 Submit via ConnectYour final post-event reflection, as a crew
🏆

The Arena Awaits

After 10 missions and 2 redesigns your mBot2 rolls into the sumo circle for real. Push, don't get pushed. Every crew fights, every crew reflects, and only one strategy wins the bracket.

🥊 Push or be pushed
📋 Knockout bracket
🏆 Real bots, real stakes

Collect your crew's numbered kit // Mission 01

SYSTEM ONLINE // YEAR 9-10 DIGITAL TECHNOLOGY MBOT2 ROBOT WARS PROJECT // 10 MISSIONS