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.
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 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.
// Logins & Submitting Your Work
🔑 Signing Into School & App Accounts
Need to log into Minecraft Education, Canva, or any other app that asks you to sign in? Most school and app accounts use the same login: your username is [email protected] (add a number if your name needs one, e.g. firstname.lastname2), and your password is the same one you use to log into your school computer.
📤 Submitting via Connect
Every project has at least one thing to hand in. Log into connect.det.wa.edu.au with your firstname.lastname and computer password, then head to your class and open the Submission section. Handing in more than one file? Zip them together first - total size must stay under 50MB.
// 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.
// 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.
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.
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.
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 footprint
180mm long x 130mm wide x 90mm tall - keep your armor within this footprint so it doesn't catch on the arena edge
Chassis frame holes
M4 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 thickness
3-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.
// 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.
SYSTEM ONLINE // YEAR 9-10 DIGITAL TECHNOLOGYMBOT2 ROBOT WARS PROJECT // 10 MISSIONS
// Digital Technology - Year 9 & 10 //
ROBOT WARS
10 missions. One mBot2. Build it from a box of parts, design and 3D print its armor, teach it to sense and drive, then push it into the sumo circle. You are the engineer, the coder and the pit crew.
🔧Build Your Bot🖨️3D Printed Armor🕹️Remote Control🥊Sumo Showdown
Use the arrow keys or the buttons below. Contents jumps to any mission.
// Contents
Pick a Mission
Review = that mission opens with a Daily Review (button in the mission's objective box on the page).
01
// Mission 01 · Week 1
🔧 Build & Power Up
// MISSION OBJECTIVE
Fully built robot powers on and shows the CyberPi home screen. mBlock account created.
// Mission 01 · What's in the box
Meet the mBot2
🧠
CyberPi
The brain. A mini computer with its own colour screen, buttons, speaker, lights and WiFi. Your code runs here.
👀
Ultrasonic Sensor
The "eyes" on the front. Measures how far away the closest object is, in centimetres.
🌈
Quad RGB Sensor
Four colour sensors underneath, pointing at the floor. Sees lines and colours on the ground.
Encoder motors
The two motors know exactly how far they have turned, so the bot can drive a set distance or turn a set angle.
Your kit number
Boxes are numbered 1 to 12. Your crew keeps the same box, same bot for all 10 missions. Write the number on your Reflection Log.
// Mission 01 · Build it right
Build Rules
Check every part against the parts list in the Makeblock build guide before you touch a screwdriver
Small parts go straight into the tray. Nothing loose on the desk
Follow the guide step by step. Screws finger-tight first, then firm
Sensors into the mBuild ports, motor cables into EM1 and EM2
Teacher check before first power on. A wrong cable is easy to fix now, hard to fix later
If it fights you, stopA screw or plug that won't go in is usually in the wrong hole or port. Forcing it is the fastest way to snap a part before the robot has even switched on.
// Mission 01 · Your crew
Three Jobs
🕹️
Driver
Drives in testing and on Robot Wars Day. Learns the controller and the bot's speed.
💻
Coder
Builds and saves the mBlock code. Keeps v1 and v2 as separate files.
🔧
Pit Crew
Keeps screws tight and batteries charged, and records what happens in every bout.
Before you go: create one free mBlock account for the crew so your work saves to the cloud.
02
// Mission 02 · Week 1
▶️ Hello mBlock
// MISSION OBJECTIVE
Your bot moves forward, turns and stops on command from code you wrote yourself.
// Mission 02 · Get connected
Connect Your Bot
🌐 Openide.mblock.cc and sign in
➕ DevicesAdd the mBot2 device
🔌 Plug inUSB cable for the first connection
🔗 ConnectClick Connect, pick the port
▶️ RunDrag in one block and test it
The Chassis blocks
The mBot2 Chassis category has the movement blocks: move forward, move backward, turn left and right, and stop moving.
Test one block at a time
Run a single "move forward" block on its own first. If six stacked blocks go wrong, you won't know which one broke it.
// Mission 02 · Your first program
Read the Code
// mBlock - Basic Movementwhen 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
Sequence
The blocks run top to bottom, one after another, in exactly that order.
Why the waits?
Without them the next block starts straight away. "Wait 1 second" is how long each move lasts.
Your task: forward, reverse, spin on the spot and stop, using at least 4 different blocks. Add a light or sound on the CyberPi for every move.
// Mission 02 · Level Up
Loops Save Blocks
// Drive a squarewhen green flag clickedrepeat 4
move forward at 50% power
wait 1 second
turn right 90 degrees
stop moving
A repeat block is a loop: write the side of the square once, run it 4 times.
Measure it
Does the bot end up on its start line? Measure how far off it is, then adjust the turn until it gets closer.
03
// Mission 03 · Week 2
📡 Sensing the World
// MISSION OBJECTIVE
An autonomous mission using the Ultrasonic Sensor that avoids or seeks an object, tested at least 3 times.
// Mission 03 · How the eyes work
Echo Location
📢 SendThe left eye sends a sound too high for us to hear
🧱 BounceIt hits an object and echoes back
👂 HearThe right eye catches the echo
⏱️ TimeLonger echo = further away
Fact
Number
Range it can measure
About 5 to 300 cm (Makeblock)
Nothing in front of it
Reads 300, its maximum
Accuracy
Within about 5%
Bats and parking sensors on cars use the same trick.
// Mission 03 · Decisions in code
If, Else, Forever
// mBlock - Obstacle Avoidforeverif distance (cm) < 15then
turn left 90 degrees
else
move forward at 50% power
endend
Forever
Keeps checking, over and over, as long as the program runs.
If ... else
A condition: if something is closer than 15 cm, turn. Otherwise, keep driving.
Start bigGet it working at 15 cm first, then shrink the number. Fine-tuning a block that doesn't work yet wastes your lesson.
// Mission 03 · Today's challenges
Avoid, Then Seek
🧱
Avoid
The bot stops or turns before it hits a wall. Test it at least 3 times.
🎯
Seek
Flip it: when something is close, drive toward it. This is the start of a sumo bot.
🚧
Navigate
Two objects on the floor. Get around both without a crash.
Think about sumoAn avoid bot runs away from its opponent. A seek bot charges at it. Which one would you rather have in the circle?
04
// Mission 04 · Week 2
🎮 Taking the Controls
// MISSION OBJECTIVE
Your bot is fully drivable by controller, with at least one custom button action mapped.
// Mission 04 · Pair up
Set Up the Controller
Put 2 x AA batteries in the Bluetooth Controller
In mBlock, add the Bluetooth Controller extension to get its blocks
Pair the controller with your CyberPi
Map the joystick to forward, back and turn
Map at least 2 buttons, including one custom action like a boost or a spin
One button at a timeMap a button, test it, then map the next. Wire up everything at once and nothing works, and you won't know which mapping is broken.
// Mission 04 · Events
When a Button Is Pressed
// mBlock - Controller Mappingwhen 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
Event
A "when ..." block waits for something to happen, then runs the blocks under it. Each button gets its own script.
Boost
Full power for half a second, then back to 50%. Short bursts save battery and control.
// Mission 04 · Test drive
The Taped Course
🏁
Lap test
Drive a full lap of the taped course without leaving the track. Swap drivers so everyone has a turn.
↩️
Level Up: escape
Map one more button to back the bot away for half a second. When would a driver use that in a sumo bout?
Manual vs autonomousLast mission the bot drove itself with the sensor (autonomous). Today a human drives it (manual). Next mission your crew picks which one wins bouts.
05
// Mission 05 · Week 3
🥊 Combat Strategy
// MISSION OBJECTIVE
Strategy chosen, v1 code built and saved, v1 armor designed and submitted for printing, crew roles assigned.
// Mission 05 · The rules
Robot Sumo
⭕
The circle
Two bots enter the circle. Push the other bot out to win the bout.
3 test bouts completed against another crew, reflection log filled in with at least one concrete change identified.
// Mission 06 · Friendly bouts
Test Like an Engineer
🔩 FitBolt on your v1 armor
⭕ Set upSumo circle with another crew
🥊 3 boutsPractice only, not scored
📝 RecordPit crew writes every result
For every bout, record
Example
Who won, and how
Lost: pushed out from the left side
What nearly went wrong
Drove off the edge chasing them
What the armor did
Wedge got under them, but rattled loose
// Mission 06 · Reflection Log 1
Pick One Change
What worked?
Keep it. Don't break something that wins.
What didn't?
Use the bout notes, not a feeling.
One change for v2
Code, armor, or both. Write why.
One properly fixed beats five half-doneYou only get one lesson to rebuild. A rattling or loose mount counts as real evidence: "tighten the mount" is a perfectly good v2 change.
Level Up: draw the circle from above and mark where each bout ended. Losing from the same side every time is a pattern. Submit Reflection Log 1 on Connect.
07
// Mission 07 · Week 4
🔁 Iterate: Build v2
// MISSION OBJECTIVE
v2 built and saved, with at least one meaningful change from v1 that you can explain.
// Mission 07 · The engineering loop
Build, Test, Reflect
🔧 Buildv1 in Mission 05
🏟️ TestArena Test 1
📝 ReflectPick one change
🔁 Build v2Today
🏟️ Test againMission 08
Iteration
Improving something in rounds, using what each test showed you. Real engineers never stop at v1.
Blend strategies
Learned something? Add sensor detection to a mostly manual bot, or a driver override to a Sentinel.
// Mission 07 · Never overwrite v1
Save a Copy
✅
Do
Save as a new file with v2 in the name. Duplicate your v1 Tinkercad design and edit the copy.
❌
Don't
Edit v1 and hit save. If v2 is worse, v1 is gone and you rebuild it from memory.
Printing a new armor piece?Submit it today so it prints in time for Mission 08.
Level Up: write a prediction with a number. "v2 will win at least _ of 3 bouts because _." You check it next mission.
08
// Mission 08 · Week 4
🏟️ Arena Test 2
// MISSION OBJECTIVE
3 test bouts completed against a new crew, second reflection completed with evidence-based reasoning.
// Mission 08 · Fair test
Did v2 Really Help?
New armor printed? Bolt it on first
Test against a different crew than last time
Run 3 bouts, same as Mission 06
Record every result the same way
Version
Bouts won
v1 (Mission 06)
1 of 3
v2 (Mission 08)
2 of 3
"We won more" is not evidence"Won 2 of 3, up from 1 of 3" is. Numbers make your reflection easier to write and harder to argue with.
// Mission 08 · Reflection Log 2
Evidence, Then Decide
The evidence
v1 score vs v2 score, plus what you saw.
Your prediction
Were you right? Why or why not?
Final tuning
One last change for Mission 09, or none.
Level UpPut v1 and v2 side by side in a small table or bar chart in Canva. Could someone who wasn't there see which version was better?
Submit Reflection Log 2 on Connect.
09
// Mission 09 · Week 5
🛠️ Polish & Tuning
// MISSION OBJECTIVE
Bot is competition-ready. Final code saved. Battery levels checked.
// Mission 09 · Pre-match checks
Pit Crew Checklist
Batteries: CyberPi charged, fresh AAs in the controller
Screws: armor mount still tight
Code: final version saved and submitted
Label: crew name and kit number on the bot
Practice bracket against the whole class
Flat battery
Loses more bouts than bad code ever does.
If it works, leave it
Last-minute changes to working code are the most common way to lose on the day.
// Mission 09 · Bonus Challenge
Network Duel
📶
The idea
The CyberPi has WiFi and can broadcast a message to every other mBot2 in the room.
❤️
Tag mode
A button broadcasts a "hit". Each bot keeps an HP variable on its screen and loses HP when a hit arrives.
For crews ahead of scheduleIt's not part of Robot Wars Day. Only start it once your bot is competition-ready and your final code is saved.
10
// Mission 10 · Week 5
🏆 Robot Wars Day
// MISSION OBJECTIVE
Compete in at least one bracket bout. Complete the post-event reflection as a crew.
// Mission 10 · Safety briefing
Arena Rules
🚧
Behind the line
Everyone not driving stays behind the line.
✋
Hands off
No touching a bot mid-bout.
⚖️
Referee
The referee's call is final.
FormatSingle-elimination bracket with the sumo rules from Mission 05. Knocked out? Referee a bout or run the scoreboard.
// Mission 10 · Finish strong
Before, During, After
🔋
Before
Collect your kit box. Charged bot, charged controller.
🧘
During
One slow breath before each bout. A calm driver beats a rushed one.
📝
After
Post-event reflection as a crew, submitted on Connect.
Robot Wars: The mBot2 build, your first mBlock code
Choral Response
CyberPi
The mBot2's brain: a mini computer with a screen, buttons, speaker and WiFi.
Choral Response
Sequence
Code runs top to bottom, one block after another, in that order.
As tell BsBs tell As
Your code
when green flag clicked move forward at 50% power turn right 90 degrees stop moving
Test run
The bot never drives forward. It just turns and stops. Why? How do you know?
As tell BsBs tell As
Your code
when green flag clicked move forward at 50% power turn right 90 degrees stop moving
Test run
There is no wait after "move forward". The next block starts instantly, so the forward move is cut off before the wheels get going. Add "wait 1 second" after each move.
Multiple Choice
Which of these are good build and code habits?
Check every part against the parts list
Force a screw that won't go in
Teacher check before first power on
Leave small parts loose on the desk
Test one block at a time
Stack 6 blocks, then test them all
Multiple Choice
Which of these are good build and code habits?
Check every part against the parts list
Force a screw that won't go inWrong hole or port: stop and check
Teacher check before first power on
Leave small parts loose on the deskThey go straight in the tray
Test one block at a time
Stack 6 blocks, then test them allYou won't know which one broke it
4 Grid
Name the Part
Write the part for each job
Measures distance in cm______________
Sees colours on the floor______________
Runs your code, has a screen______________
Where the motor cables plug in______________
4 Grid
Name the Part
Write the part for each job
Measures distance in cmUltrasonic Sensor
Sees colours on the floorQuad RGB Sensor
Runs your code, has a screenCyberPi
Where the motor cables plug inEM1 and EM2
Match
Match each term to its meaning. Write your pairs, e.g. A - ?
Sends a sound we can't hear and times the echo to measure distance.
Choral Response
Condition
A true or false test, like distance < 15, that decides what the code does next.
As tell BsBs tell As
Your code
forever if distance (cm) > 15 then turn left 90 degrees else move forward at 50% power end end
Test run
CyberPi distance: 300 empty room
Empty room: spins Next to a wall: drives into it
It spins in an empty room but drives into walls. Why? How do you know?
As tell BsBs tell As
Your code
forever if distance (cm) > 15 then turn left 90 degrees else move forward at 50% power end end
Test run
CyberPi distance: 300 empty room
Empty room: spins Next to a wall: drives into it 300 > 15 is true, so it turns
The sign is backwards: it should be < 15, not > 15. In an empty room the sensor reads 300, and 300 > 15 is true, so it turns. Near a wall the test is false, so it drives on.
Multiple Choice
Which of these are good sensor, controller and armor choices?
Start at 15 cm, then shrink the number
Map every button, then test
Armor inside the 180 x 130 mm footprint
A Sentinel shroud that covers the sensor
Mount holes in multiples of 8 mm
Glue the armor to the chassis
Multiple Choice
Which of these are good sensor, controller and armor choices?
Start at 15 cm, then shrink the number
Map every button, then testMap and test one at a time
Armor inside the 180 x 130 mm footprint
A Sentinel shroud that covers the sensorIt can't see the opponent
Mount holes in multiples of 8 mm
Glue the armor to the chassisBolt it on with the kit's M4 screws
4 Grid
Strategy & Sensor
Write the answer for each clue
Fully manual, wide and low______________
Fully autonomous, charges what it sees______________
Human drives, code boosts when close______________
Sensor reading with nothing in front______________
4 Grid
Strategy & Sensor
Write the answer for each clue
Fully manual, wide and lowThe Rammer
Fully autonomous, charges what it seesThe Sentinel
Human drives, code boosts when closeThe Tactician
Sensor reading with nothing in front300
Match
Match each term to its meaning. Write your pairs, e.g. A - ?
forever
A
W
How long the boost lasts
if ... else
B
X
An event that starts a script
when button A pressed
C
Y
Keeps checking over and over
wait 0.5 seconds
D
Z
Chooses between two actions
Match
Answer: A - Y B - Z C - X D - W
forever
A
W
How long the boost lasts
if ... else
B
X
An event that starts a script
when button A pressed
C
Y
Keeps checking over and over
wait 0.5 seconds
D
Z
Chooses between two actions
Complete the missing components
In pairs, fill in A to F.
Item
Manual or autonomous?
What does it do?
Learned in
Obstacle avoid code
A.
B.
Mission 3
Controller mapping
C.
D.
Mission 4
The Tactician
E.
F.
Mission 5
Complete the missing components
In pairs, fill in A to F.
Item
Manual or autonomous?
What does it do?
Learned in
Obstacle avoid code
A. Autonomous
B. Turns when the sensor sees something close
Mission 3
Controller mapping
C. Manual
D. Joystick and buttons drive the bot
Mission 4
The Tactician
E. Both
F. Driver steers, code adds a boost
Mission 5
1 / 1
Year 9 & 10 Digital Technology Daily Review
Robot Wars: Arena testing, iteration, evidence
Choral Response
Iteration
Improving a design in rounds, using what each test showed you.
Choral Response
Evidence
Real results you recorded, like "won 2 of 3", not a feeling.
As tell BsBs tell As
Reflection Log 1
v2 changes: new code new armor faster speed wider stance
Saved as
robot.mblock (saved over v1)
Arena Test 2
Version
Bouts won
v1
1 of 3
v2
1 of 3
"Which change made the difference?"
v2 did no better, and the crew can't work out why. Why? How do you know?
As tell BsBs tell As
Reflection Log 1
v2 changes: new code new armor faster speed wider stance
Saved as
robot.mblock (saved over v1)
Arena Test 2
Version
Bouts won
v1
1 of 3
v2
1 of 3
"Which change made the difference?"
4 changes at once: no way to tell which helped or hurt
They changed four things at once and saved over v1. One change might have helped and another hurt, and with v1 gone they can't go back or compare. One change per version, saved as a new file.
Multiple Choice
Which of these are good testing and reflection habits?
"Won 2 of 3, up from 1 of 3"
"We did heaps better"
One change per version
Save v2 over the top of v1
Test v2 against a different crew
Change working code just before the final
Multiple Choice
Which of these are good testing and reflection habits?
"Won 2 of 3, up from 1 of 3"
"We did heaps better"No numbers: not evidence
One change per version
Save v2 over the top of v1Save v2 as a new file
Test v2 against a different crew
Change working code just before the finalIf it works, leave it
4 Grid
Work It Out
Write the answer for each
v1 won 1 of 3, v2 won 2 of 3______________
3 bouts in each of 2 arena tests______________
Predicted 2 of 3, won 1 of 3______________
Holes 8 mm apart: hole 1 to hole 3______________
4 Grid
Work It Out
Write the answer for each
v1 won 1 of 3, v2 won 2 of 3v2 won 1 more bout
3 bouts in each of 2 arena tests6 bouts
Predicted 2 of 3, won 1 of 3Prediction was wrong
Holes 8 mm apart: hole 1 to hole 316 mm
Match
Match each term to its meaning. Write your pairs, e.g. A - ?