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

STREET LEGAL

Over the next 10 lessons your garage crew will design a street racer in CAD, 3D print it, wire it up to a micro:bit, and code it to move - then find out how fast it really is on Race Day. You are the designer. You are the mechanic. You are the coder.

📐 CAD Design
🖨️ 3D Printed
💻 micro:bit Powered
🏁 Race Day
Your Garage
📐
Design Platform
Tinkercad - free browser-based CAD. Join your class below, then log in with your class login (not a personal Autodesk account).
💻
Coding Platform
makecode.microbit.org - runs in your browser, no install needed. You'll need the Kitronik extension - click the gear icon top-right, choose Extensions, search "Kitronik", and add the Klip Motor Driver tile.
🚗
The Hardware
A micro:bit V2, a Kitronik Klip Motor Driver, and a Micro Metal Gearmotor. No soldering - everything connects with crocodile clips.
🖨️
The Print Shop
5x FlashForge Adventurer 3 printers. Build volume is 150 x 150 x 150mm - keep your whole chassis design well under that, with room to spare for wheels.
🧠
AI Pit Crew
copilot.microsoft.com - ask it "How do I do X in MakeCode?" or "How do I do X in Tinkercad?" whenever you're stuck.
⚠ AI can get block names and menu locations wrong - always double check against the real editor!
🔧
Shared Garage Stock
11 Klip Motor Drivers and 11 gearmotors are shared between Year 9 and Year 10. Collect a set from the garage box at the start of every lesson and return it at the end - your design and code belong to you, the electronics belong to the garage. Most students work in pairs (one kit each). If your class has an odd number and you end up in a group of three, see the note in Lesson 3 - you'll build two cars and share one motor between them.
// Primary Objective

Design, build and program a battery-powered street racer from raw parts - then prove how fast it is, for real, on Race Day.

Design a chassis and drivetrain in Tinkercad that solves a real engineering problem: one motor, two wheels
Program your racer's movement and light show in MakeCode using the Kitronik Klip extension
Test your car for real on the track, not just in theory - record what actually happens
Iterate across two build cycles, using evidence from testing to improve your design, not guesswork
// Marking Key & Rubric
Criteria Pit Lane
(0-1)
Roadworthy
(2-3)
Race Ready
(4)
Podium
(5)
Score
Design & Fabrication Chassis incomplete, failed to print, or needed teacher rebuild Chassis fully designed, printed and assembled, holds together Motor and axle solve the drivetrain problem cleanly, parts fit with a snug friction-fit Design shows genuine problem-solving - grip, weight balance or wheel design beyond the basics / 5
Programming Car moves only with heavy teacher support Car drives forward and stops using code you wrote Reliable forward/reverse control plus a light or sound feature on the micro:bit Code is polished and combines movement with feedback smoothly, few bugs / 5
Testing & Iteration No testing evidence, reflection log incomplete At least one test run completed, one reflection written Clear v1 to v2 changes, each backed by a reason from testing Changes show genuine evidence (times, observations) and real improvement / 5
Race Day Did not participate, or car was not race-ready Competed in at least one heat, followed the rules Competed fully, worked well with garage crew throughout Strong sportsmanship, helped other crews, clear ownership of role / 5
Total / 20
Scroll sideways to see every column
Build Log
Week 1
01
🔑 Meet the Garage
▾
// BUILD OBJECTIVEOne sketch chosen as your Design 1 concept. Tinkercad class joined and MakeCode ready to go.
  • Get into your garage crew (pairs) and grab a Klip Motor Driver, a gearmotor and a micro:bit from the shared garage box so you can see and hold the real parts
  • Your teacher will walk through what each part does: the micro:bit is the brain, the Klip board plugs onto it and adds a 3xAA battery pack plus a motor output, and the gearmotor is what actually turns your wheels
  • Safety rules for shared gear: crocodile clips only, no forcing connections, batteries out when you're not actively testing, and everything gets returned to the garage box at the end of the lesson
  • On paper, sketch 2-3 rough ideas for your car body. Think about where the board, motor and battery pack will sit, and remember your whole car has to fit inside roughly 130 x 100 x 80mm to safely fit the printer bed
  • Choose your favourite sketch as your Design 1 concept and label it with your crew name
  • Join your class Tinkercad using the link in Your Garage above (both Year 9 and Year 10 log in with their last name), and sign in to MakeCode - these are where your work will live for the whole project
💡 HintStuck on what to sketch? Look at real cars first - a simple box body with 4 wheels is a completely valid design. You don't need anything fancy for Design 1, just something that will hold the parts and roll.
🔍 Google Image Search"simple toy car body design sketch"
// ASK AI"I'm designing a simple toy car body to 3D print. What basic shapes make a car body that's easy to print without extra support material?"
02
📏 Blueprint Bootcamp
▾
// BUILD OBJECTIVEComfortable using Box, Hole and Align in Tinkercad. Chassis base plate started, sized to the confirmed measurements.
  • Collect a Klip board and motor from the garage box so you can hold the real parts next to your screen while you model
  • Learn the core Tinkercad tools: Box, Cylinder, Hole (for cutting shapes out of other shapes), Align, and Group. Practice on a throwaway shape before touching your real design
  • Use the confirmed measurements below to size everything accurately - no guessing needed
📏 Confirmed Part Measurements
Klip Motor Driver board72mm long x 70mm wide - the biggest single part, plan your floor plate around it first
micro:bit V252mm long x 43mm wide - plugs straight into the Klip board's edge connector, sits on top of it
Gearmotor body25mm long x 12mm wide x 10mm tall - the rectangular gearbox block
Gearmotor output shaft9mm long, 3mm diameter, D-shaped (flat on one side) - sticks out the front of the gearbox
Suggested wheel diameter30-45mm - big enough for ground clearance, small enough to keep torque
Target chassis footprintUnder 130 x 100 x 80mm - leaves safe margin under the printer's 150mm limit
  • Build a simple "test block" in Tinkercad sized to fit your Klip board on top of it, using Hole shapes to mark where it would sit. This is just practice - don't submit it for printing
  • Start your real chassis: model the base plate/floor of your car from your Design 1 sketch, sized to the measurements above
💡 HintBuild in layers, not all at once. Model the flat floor plate first and get that right before you add walls, mounts or holes on top of it. It's much easier to fix one simple shape than to untangle a messy complicated one.
// ASK AI"How do I use the Align and Hole tools in Tinkercad to cut a shape out of another shape?"
// ASK AI"How do I resize a shape in Tinkercad to an exact measurement in millimetres, like 72mm long?"
// LEVEL UPModel a small motor mount: a solid block with a Hole shape cut into it for the 25 x 12 x 10mm gearbox, made about 0.3mm bigger than the motor so it slides in. Use Align to centre the hole in the block, then check every size against the confirmed measurements table.
Week 2
03
⚙️ Drivetrain Problem
▾
// BUILD OBJECTIVEDesign 1 chassis with a working axle-and-wheel system submitted for printing.
  • The engineering problem: you only have one motor, but a car needs at least 2 wheels moving together. The fix is a single rigid axle with a wheel fixed at each end - the motor turns the axle, the axle turns both wheels
  • The motor's shaft is 3mm diameter, 9mm long, and D-shaped (flat on one side) so it grips instead of spinning loose - your axle needs a matching D-shaped hole in the middle, sized just under 3mm, for the motor shaft to push into
  • The other axle (front or back, whichever isn't driven) just needs wheels that spin freely on round printed pegs - no motor needed there
  • Design your axles and wheels in Tinkercad and attach them to your chassis base plate from Lesson 2. Keep your whole design well under the 150mm printer limit
  • Finish your Design 1 file and submit it through Connect for the print queue - it'll be printed overnight or over lunch on one of the 5 printers
  • While you wait for other groups to finish designing, open MakeCode and start exploring - don't add the Kitronik extension yet, that's next lesson
💡 HintMake your D-shaped hole slightly smaller than 3mm, not exactly 3mm. A hole printed at exactly the same size as the shaft usually comes out too loose - a tiny bit tight is what gives you a proper grip fit.
💡 Groups of ThreeIf your group has three people sharing one motor kit, you're building two cars, one motor - slot-car style. Design both chassis with the exact same D-shaped hole spec from this lesson (same size, same position on the axle) so the motor drops straight into either car without any modification. If the two axle holes don't match, you won't be able to swap the motor over during testing - agree on the shared spec as a group before either of you starts modelling, and double-check both files against each other before submitting.
🔍 Google Image Search"D shaped shaft hole 3D print axle"
// ASK AI"How do I design a D-shaped hole in Tinkercad that a D-shaped motor shaft can push into?"
📤 Submit via ConnectYour Design 1 Tinkercad file (share link or exported .stl) - groups of three submit two files, one per car
// LEVEL UPGive your free (non-driven) axle its own design check: model each wheel hole about 0.4mm bigger than its round peg so the wheel spins freely, and write both sizes on your sketch. Moving parts need a bigger gap than the snug D-shaped motor grip.
04
🚦 First Laps in Code
▾
// BUILD OBJECTIVESaved MakeCode program: button-controlled forward/stop, with a 3-2-1-GO countdown on the LED screen.
  • In MakeCode, click the gear icon top-right, choose Extensions, search "Kitronik", and add the Klip Motor Driver tile - this unlocks the motor control blocks
  • Collect a Klip board, motor and micro:bit from the garage box. Push the micro:bit into the Klip board's edge connector, then use crocodile clips to connect the motor to the "Motor 1 Outputs" pads
  • Code: use the Kitronik blocks to turn motor 1 forward, then turn it off. Test it on the desk before your chassis exists - the motor shaft should spin freely
  • Map button A to drive forward and button B to stop - test that both work reliably
  • Add a drag-strip countdown: use the LED screen to show 3, 2, 1, then a "GO" pattern before the motor starts, just like a real starting light
  • Save your program with your crew name in the title - you'll build on this file for the rest of the project
💡 HintBuild your code in small steps and test after each one. Get the motor spinning first. Only add the countdown once forward/stop is working reliably - don't write the whole program in one go and then wonder why nothing works.
// ASK AI"How do I use the Kitronik Klip Motor Driver extension blocks in MakeCode to drive a motor forward and stop it?"
// ASK AI"My micro:bit motor isn't spinning when I run my MakeCode program - what are the most common reasons that happens?"
// Block layout to copy in MakeCode
on start
    show number "3"
    pause (ms) 500
    show number "2"
    pause (ms) 500
    show number "1"
    pause (ms) 500
    show icon "yes"   ← this is your GO signal

on button A pressed
    Klip Motor: turn motor 1 forward at speed 60

on button B pressed
    Klip Motor: turn off motor 1
// LEVEL UPMake your car launch by itself: add a "turn motor 1 forward" block to the end of your countdown so the car takes off on GO, and keep button B as your emergency stop. Test it on the desk first.
Week 3
05
🔥 First Burnout
▾
// BUILD OBJECTIVEDesign 1 physically tested and driven. Reflection Log 1 completed with one concrete change identified.
  • Collect your printed Design 1 chassis, plus a Klip board, motor, micro:bit and batteries from the garage box
  • Assemble: push the motor into its printed mount, push the axle with wheels onto the motor's D-shaft, push the free axle's wheels onto their pegs, then mount the Klip board and connect everything with crocodile clips exactly as your code expects
  • Load your saved program from Lesson 4 onto the micro:bit, add 3 fresh AA batteries, and test drive it - on carpet first, then on the concrete outside
  • Record what actually happens: does it drive straight? Does it move at all? Do the wheels slip? Does anything fall off?
  • Fill in your Reflection Log 1: what worked, what didn't, and one specific change you'll make for Design 2
💡 HintIf your car pulls to one side instead of driving straight, check both wheels on the driven axle first - one wheel pushed on slightly looser than the other is the single most common cause.
🔍 Google Image Search"toy car drifting to one side fix"
// ASK AI"My 3D printed car drifts to one side instead of driving straight. What are the most common causes and fixes?"
📤 Submit via ConnectReflection Log 1 (a photo or video of your test run counts as evidence)
06
🎨 Tuning the Ride
▾
// BUILD OBJECTIVERacing class chosen. Design 2 submitted with a clear reason for each change. One new code feature added.
  • As a crew, pick the racing class that matches how you want Design 2 to perform:
The SprinterLightweight body, smaller wheels, minimal extras. Wins on raw speed if the drivetrain holds together.
The BrawlerWider stance, bigger or treaded wheels for grip, stronger axle mounts. Wins on stability and reliability.
The ShowstopperBalanced speed, plus a standout LED light show and livery. Built to win Best Design, not just the race.
  • In Tinkercad, apply the fix from your Reflection Log - common fixes are a tighter D-shaped hole for the motor shaft, a wider wheelbase for stability, or adding a tread/grip pattern to your wheels (this is your open design challenge - try lines, chevrons or bumps)
  • Finish your Design 2 file and submit it through Connect for the print queue
  • In MakeCode, add one new feature to your program: a "boost" button for a short burst of full power, or an LED animation (headlights, flames, checkered pattern) that plays while driving
💡 HintChange one thing at a time between Design 1 and Design 2. If you change the wheels, the axle fit and the weight all at once, you won't know which change actually made the difference when you test it next lesson.
// ASK AI"How do I make my micro:bit motor run at full speed for one second and then drop back to normal speed, using MakeCode?"
// Boost button - add to your Lesson 4 program
on button A+B pressed  ← both buttons together = BOOST
    Klip Motor: turn motor 1 forward at speed 100
    pause (ms) 1000
    Klip Motor: turn motor 1 forward at speed 60
📤 Submit via ConnectYour Design 2 Tinkercad file
// LEVEL UPModel a second wheel tread pattern next to your first one. Predict which will grip better and write your reason in your Reflection Log. Only one can go on Design 2, so choose using evidence, not a hunch.
Week 4
07
🏎️ Grip & Speed Test
▾
// BUILD OBJECTIVETimed run recorded over 3 metres. Reflection Log 2 completed, comparing Design 1 and Design 2 with real evidence.
  • Collect your printed Design 2 chassis and assemble it the same way as Lesson 5
  • Test your grip challenge: try your car on a smooth surface and on grippy concrete. If it's still slipping, problem-solve on the spot - a rubber band stretched around the wheel rim is a legitimate, low-cost fix
  • Set up a marked 3 metre straight track. Time how long your car takes to cross the line with a stopwatch, best of 3 runs
  • Record your fastest time - this is your official qualifying time so far
  • Update your Reflection Log: compare Design 1 and Design 2. Did your change actually make it faster or more stable, or did it just feel like it should? Use your times and observations as evidence
💡 HintRun your time trial 3 times and use the middle result, not just your best or worst run. A single run can be a fluke - 3 runs tells you what your car actually does most of the time.
🔍 Google Image Search"rubber band wheel grip diy toy car"
// ASK AI"What are some simple, cheap ways to add grip to a 3D printed wheel so it doesn't slip?"
📤 Submit via ConnectReflection Log 2, including your fastest recorded time
// LEVEL UPIf you added a boost in Lesson 6, time 3 runs with the boost and 3 runs without it, then compare the middle results. Does the boost really make your car faster, or does it just make it harder to control?
08
🎟️ Race Day Prep
▾
// BUILD OBJECTIVELivery complete. Code tested end-to-end. Hardware checked and race-ready.
  • Design your car's livery - a race number, team name and colour scheme. Keep it simple: coloured paper wrap, marker, or a printed detail if your chassis has flat panels for it
  • Learn the Race Day rules: two cars run side by side down a straight lane, first to cross the line wins the heat. A false start (moving before the code's countdown finishes) is a re-run. No pushing, no touching a car mid-race
  • Run your full program start to finish exactly as it will run on Race Day: countdown, drive, any boost feature
  • Final hardware check: is every friction-fit still snug? Are your batteries fresh? Do all 4 wheels spin freely?
💡 HintJudges notice details. A clean, simple race number and colour scheme can win Best Design even if your car isn't the fastest one on the strip - don't skip this step because it feels less important than the code.
// ASK AI"Give me 5 creative team names for a small toy car racing competition"
Week 5
09
⏱️ Qualifying Day
▾
// BUILD OBJECTIVEAt least 2 practice heats completed. Best qualifying time recorded on the leaderboard.
  • Run at least 2 practice heats against other crews on the real race lane, exactly under Race Day rules
  • Record your results and best time on the class leaderboard
  • Only mechanical fixes allowed today - tightening a loose part, swapping a wheel, fresh batteries. No more Tinkercad redesigns, there won't be time to reprint
  • Confirm your final program is saved and ready - this is the version you'll race next lesson
💡 HintIf something breaks today, fix it the simplest way possible - hot glue or tape are fine for an emergency repair. There's no time left to reprint, so don't attempt a full redesign now.
// ASK AI"My car's wheel keeps falling off during testing - what quick fixes can I try without reprinting the part?"
10
🏁 Race Day
▾
// BUILD OBJECTIVECompeted in at least one Race Day heat. Final reflection submitted.
  • Arrive with a charged, race-ready car and your final program loaded onto the micro:bit
  • Safety briefing first - stay behind the line, no touching a car mid-race, referee's call is final
  • Head-to-head bracket down the drag strip, rules from Lesson 8
  • Awards: Fastest Car, Best Design, Best Livery, and Best Garage Crew (teamwork and sportsmanship)
  • Complete your final reflection as a crew and submit it through Connect
💡 HintNerves make people rush the start. Trust your countdown code and let it finish before you move - jumping the gun is a false start and you'll just have to re-run it anyway.
// ASK AI"Help me write a short paragraph reflecting on what my team learned during our design and technology project"
📤 Submit via ConnectFinal crew reflection
🏁

Race Day Awaits

After 10 builds and 2 full redesigns your street racer lines up on the strip for real. First across the line wins the heat. Every crew races, every crew reflects, and only one car takes the podium.

🏎️ Fastest car wins
📋 Head-to-head bracket
🏆 Real cars, real times

Find your garage crew, grab your parts // Build 01

SYSTEM ONLINE // YEAR 9-10 DIGITAL TECHNOLOGY STREET LEGAL // 10 BUILDS