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

CIRCUIT CITY
ENGINEERS

Over the next 10 shifts you and a partner run an engineering firm in Circuit City. Simulate circuits in Tinkercad, build a smart street device with a micro:bit and Grove sensors, design and print its case, and switch it on at the City Expo.

🔌 micro:bit V2
🌡️ Grove Sensors
📦 3D Printed Case
🏙️ City Expo
Engineer Kit
📐
Tinkercad
Circuits (the simulator) for Shifts 01 and 02, then 3D for your case. Join your class and log in with your class login.
💻
MakeCode
makecode.microbit.org in Chrome or Edge, Blocks only. Gear icon, Extensions, search grove to add the Grove (and NeoPixel) blocks.
🌡️
Grove Inventor Kit
12 kits, one per pair: Grove Shield, Light Sensor, Ultrasonic Ranger, Rotary dial, Gesture sensor, 4-Digit Display, Red LED, Speaker and a 30-LED strip, plus a micro:bit V2.
⚠ micro:bit in the shield with the LED matrix facing up.
💾
Saving
Signed in, MakeCode saves to the cloud as you edit: watch the cloud status at the bottom of the editor. Every Download also keeps a .hex in Downloads as a backup. Project missing next lesson? Home screen, Import, Import File.
🧠
AI Assistant
copilot.microsoft.com - ask it why a sensor gives a strange number or how to plan your device. Check its answers against the blocks you can actually see.
⚠ AI often invents blocks - only use blocks that appear in MakeCode!
🏙️
City Expo
On the final day every device, in its printed case, goes on one class city map. Pairs demo live while the class tours, then vote: Smartest Sensor, Best Enclosure, Most Useful and People's Choice.
// Primary Objective

With a partner, design, code, case and demo one smart device that makes Circuit City's streets safer or brighter, from simulation to a working build at the City Expo.

Simulate inputs and outputs on a micro:bit in Tinkercad Circuits
Build with Grove sensors, LEDs, displays and sound in MakeCode Blocks
Design a 3D printed enclosure with clearance and openings that work
Test with a log, fix with evidence, and demo at the City Expo
// Marking Key & Rubric
Criteria Apprentice
(0-1)
Technician
(2-3)
Engineer
(4)
Chief
(5)
Score
Circuits & Code Layouts copied without changes, or the device does not run Device runs with help, one input and one output Device senses, decides with an if and acts, ports planned correctly Clear, tuned code you can explain block by block, extra outputs / 5
Enclosure No enclosure designed Enclosure designed, parts do not fit Prints and fits with clearance, openings for sensors and cables Neat, labelled, holds the parts still and suits its street spot / 5
Testing No tests recorded Some tests, one change made Six logged tests and a fix written as evidence, change, reason Fixes proven by a full retest, device reliable on the day / 5
Expo & Teamwork No demo, or very uneven teamwork Demo with help, info card started Live demo, info card, both partners built and coded Confident demo, feedback given and acted on / 5
Total / 20
Scroll sideways to see every column
Work Log
Week 1
01
🔌 Power Up
▾
// SHIFT OBJECTIVETinkercad class joined, two of Tinkercad's micro:bit tutorials finished in Tinkercad Circuits, and your pair's top three devices picked from the Device Menu.
  • Welcome to Circuit City. The council wants smart devices for its streets, and every pair is an engineering firm. You will design one device, code a micro:bit to run it, print it a case, and show it off at the City Expo
  • Join your Tinkercad class with the link in the Engineer Kit (Year 9 or Year 10), logging in with your last name
  • Open Tinkercad's micro:bit projects and do Lighting Up the Micro:bit LED Matrix. The Code button (top of the editor) opens the blocks and Start Simulation runs them
  • Then do Micro:bit Motion Sensor and Buttons. Every device in this project starts the same way: something goes in (a button, a sensor) and something comes out (lights, a number, a sound)
  • Read the Device Menu below with your partner. For each device, name its input and its output
  • Pick your top three and write one sentence each: which street problem does it solve?
💡 Smart Street LightLight Sensor in, Red LED or LED strip out. Turns on when it gets dark, off at sunrise.
🅿️ Parking SensorUltrasonic Ranger in, 4-Digit Display and Red LED out. Shows the gap and warns when a car is too close.
🚦 Pedestrian CrossingButton A (or a wave at the Gesture sensor) in, LED strip and Speaker out. Red, then green with beeps, then red.
🔊 Noise MonitorThe micro:bit V2's built-in microphone in, LED strip bar graph out. Shows how loud the street is.
🌈 LED BillboardLED strip out, Rotary dial and Light Sensor in. Animations that dim at night and change with the dial.
🚧 Boom Gate (stretch)A second micro:bit on a Klip Motor Driver opens a gate with a motor when your device sends a radio signal.
💡 HintA simulation cannot break anything. Try changing numbers and blocks just to see what happens, then put them back.
🔍 Google Image Search"smart city sensors street lights"
// ASK AI"What are some ways smart cities use sensors to make streets safer?"
02
🌙 Sense the City
▾
// SHIFT OBJECTIVEA simulated street light in Tinkercad Circuits: the micro:bit's light level turns an LED on a breadboard on when it gets dark and off when it is bright.
  • A sensor turns the world into a number. The micro:bit's light level goes from 0 (dark) to 255 (bright)
  • In Tinkercad's micro:bit projects, do Light and Temperature Sensors on Micro:bit. During the simulation, click the micro:bit: a panel opens with a temperature slider and a light slider (the sun). Slide the light to watch the reading change
  • Then do Using Micro:bit With External Components, which wires an LED to the micro:bit so your code can switch it
  • Now combine them: a street light. In a forever loop, if the light level is below a threshold (start with 50) the LED turns on, otherwise it turns off. Build it with the blocks those two tutorials used
  • Test it: slide the light level from bright to dark and back. Write down the reading where the LED switches
  • Share your circuit link with your partner so you both have it
🌙 Street Light Logic
InputLight level: 0 is dark, 255 is bright
RuleIf the light level is below the threshold, turn the LED on. Otherwise turn it off
OutputThe LED on your breadboard
LoopCheck again and again with forever
💡 HintIf the LED is on in the daytime and off at night, your rule is back to front: check whether you wrote below or above.
// ASK AI"What is a threshold in a sensor program, and how do I choose a good one?"
// LEVEL UPTry three thresholds: 30, 50 and 100. Slide the light level for each one and decide which would suit a real street light best. Write one sentence on why.
Week 2
03
💡 Real Hardware
▾
// SHIFT OBJECTIVEA real street light: micro:bit V2 on the Grove Shield, Light Sensor in, Red LED out, coded in MakeCode with the Grove extension and flashed to the micro:bit, and your pair's device chosen.
  • Collect a Grove Inventor Kit. Push the micro:bit into the Grove Shield with its LED matrix facing up (Seeed warns the other way round can damage the board)
  • With Grove cables, plug the Light Sensor into the P0/P14 port and the Red LED into the P1/P15 port
  • Open makecode.microbit.org in Chrome or Edge, click New Project and name it street-light. Click the gear icon, choose Extensions, search grove and click the Grove tile. (It also adds the NeoPixel blocks you need later)
  • Build the layout below. analog read pin [P0] reads the Light Sensor as a number from 0 to 1023
  • Flash it: plug the micro:bit's own micro-USB port into the laptop, click Download, then drag the .hex file from Downloads onto the MICROBIT drive (if a connect box opens instead, follow its steps). Cover the sensor with your hand: the LED should light
  • Tune the threshold for this room, then choose your pair's device from the menu and tell your teacher. Save: the Download also keeps a .hex in your Downloads (it follows you to any laptop). Next lesson: MakeCode home screen, Import, then Import File
// Blocks: street light (build it, no Copy)
forever
    set light to (analog read pin [P0])
    if <(light) < (300)> then
        digital write pin [P1] to (1)
    else
        digital write pin [P1] to (0)
    pause (ms) (200)
💡 HintNot sure what number to use? Add show number (light) inside the forever loop and read the sensor in the light and with your hand over it. Pick a threshold in between.
🔍 Google Image Search"grove shield microbit light sensor"
// ASK AI"Why does a light sensor give a different number in a bright room and a dark room?"
📤 Submit via ConnectYour street light .hex file and your pair's device choice
// LEVEL UPAdd on button [A] pressed with show number (light) inside, so pressing A shows the reading any time. Use it to check your threshold in three spots around the room.
04
📏 Distance & Display
▾
// SHIFT OBJECTIVEA parking sensor: the Ultrasonic Ranger's distance in cm shown on the 4-Digit Display, the Red LED lit closer than 10 cm, and five readings checked against a ruler.
  • Plug the Ultrasonic Ranger into P0/P14, the 4-Digit Display into P1/P15 and the Red LED into P2/P16
  • Plug a second micro-USB cable into the shield's USB port as well. Seeed says modules like the Ultrasonic Ranger need the shield's own USB power to work well
  • An ultrasonic sensor sends out a sound too high to hear and times how long the echo takes to come back. Longer echo, further away
  • New Project parking-sensor (add the Grove extension again). The 4-Digit Display block makes a variable for the display: rename it display. For distance use the block that starts (V2): Seeed added it for the micro:bit V2, which is what we use. Build the layout below and flash it
  • Ruler test: hold a book at 5, 10, 20, 30 and 50 cm and record what the display shows each time
  • Is the LED lighting at the right distance? Tune the number in the if block. Save: the Download also keeps a .hex in your Downloads (it follows you to any laptop). Next lesson: MakeCode home screen, Import, then Import File
// Blocks: parking sensor (build it, no Copy)
on start
    set display to 4-Digit Display at [P1] and [P15]
forever
    set distance to ((V2)Ultrasonic Sensor (in cm) at [P0])
    display show number (distance)
    if <(distance) < (10)> then
        digital write pin [P2] to (1)
    else
        digital write pin [P2] to (0)
    pause (ms) (100)
📏 Ruler Test
Real distance5, 10, 20, 30 and 50 cm
Display showsWrite each reading next to the real distance
Out by a lot?Check you used the (V2) block, the cable is in P0/P14 and the shield USB power is in, then point the sensor at something flat
💡 HintReadings jump about? Point the sensor at something flat and wide like a book, not a hand or a pen.
// ASK AI"How does an ultrasonic distance sensor work out how far away something is?"
// LEVEL UPMake it talk: inside the if, after the LED turns on, add show string ["STOP"] so the micro:bit warns the driver too.
Week 3
05
🚦 Light & Sound
▾
// SHIFT OBJECTIVEA crossing button that turns the LED strip from red to green with five beeps and back to red, plus the strip used as a bar graph of the micro:bit's sound level.
  • Plug the LED strip into P1/P15 and the Speaker into P0/P14, and keep the shield's USB power plugged in
  • The strip is 30 NeoPixel LEDs that can each be any colour. The NeoPixel block makes a variable called strip. Brightness goes from 0 to 255: 40 is plenty indoors
  • New Project crossing with the Grove extension. Build the crossing layout, flash it and press A
  • analog set pitch pin [P0] sends the beeps to the Grove Speaker. The micro:bit V2's own speaker plays them as well
  • Now the noise monitor layout: sound level is the micro:bit V2's microphone, from 0 (quiet) to 255 (loud). Flash it and clap
  • Write down which of today's ideas your own device will use. Save: the Download also keeps a .hex in your Downloads (it follows you to any laptop). Next lesson: MakeCode home screen, Import, then Import File
// Blocks: pedestrian crossing (build it, no Copy)
on start
    set strip to NeoPixel at pin [P1] with (30) leds as [RGB (GRB format)]
    strip set brightness (40)
    strip show color [red]
    analog set pitch pin [P0]
on button [A] pressed
    strip show color [green]
    repeat (5) times
        play [tone (Middle C) for (1 beat)] [until done]
        pause (ms) (500)
    strip show color [red]
// Blocks: noise monitor (build it, no Copy)
on start
    set strip to NeoPixel at pin [P1] with (30) leds as [RGB (GRB format)]
    strip set brightness (40)
forever
    strip show bar graph of (sound level) up to (255)
    pause (ms) (100)
💡 HintBrightness only changes things shown after it, so set it before you show a colour.
// ASK AI"Why do real pedestrian crossings beep as well as change colour?"
📤 Submit via ConnectYour crossing and noise monitor .hex files
// LEVEL UPPlug the Rotary Angle Sensor into P2/P16 and turn the noise monitor into a dimmer: in the forever loop put strip set brightness (map (analog read pin [P2]) from low (0) from high (1023) to low (0) to high (255)) before the bar graph.
06
📦 Enclosure Design
▾
// SHIFT OBJECTIVEAn enclosure for your device designed in Tinkercad that fits the Grove Shield with clearance, has openings for every sensor and cable, fits the 150 mm print bed, and is submitted for printing.
  • Your device needs a case for the Expo. Measure first: the Grove Shield is 72 x 72 x 13 mm (Seeed). Measure each module your device uses with a ruler and write the sizes down
  • Plan the openings: the Light Sensor needs light, the Ultrasonic Ranger needs both of its round eyes clear, the microphone needs a small hole, and every cable needs a slot
  • In Tinkercad 3D: a Box for the outside, a Hole box for the inside, then Group. Walls at least 1.2 mm (2 mm is stronger)
  • Holes print a little small, so make the inside 0.5 mm bigger on every side than the shield, and every opening 0.3 to 0.5 mm bigger than the part it fits
  • Keep everything inside the printer's 150 mm cube, and avoid overhangs steeper than about 45 degrees: design it to print lying flat, open side up
  • Check it from every angle, then submit the Tinkercad share link so your teacher can print it
📦 Enclosure Rules
Shield72 x 72 x 13 mm: plan around it first
ClearanceInside 0.5 mm bigger each side, openings 0.3 to 0.5 mm bigger
WallsAt least 1.2 mm, 2 mm is stronger
Printer150 mm cube, about 0.2 mm accuracy, no steep overhangs
💡 HintLeave the top open or make a separate lid. A closed box cannot be printed without supports filling the inside.
🔍 Google Image Search"microbit 3d printed enclosure case"
// ASK AI"How much clearance should I leave so a circuit board fits inside a 3D printed box?"
📤 Submit via ConnectYour enclosure's Tinkercad share link
// LEVEL UPAdd four small pegs or a ledge inside so the shield sits still, and a slot or hole sized for the shield's USB cable. Label your firm's name on the outside with Tinkercad's Text shape.
Week 4
07
🛠️ Device Build
▾
// SHIFT OBJECTIVEYour device built and coded: an input, process, output plan written, the full Blocks program flashed to the micro:bit, and a first test that shows it working.
  • Write your device's plan in three boxes: Input (what it senses), Process (the rule, e.g. closer than 10 cm), Output (what it does)
  • List the ports: which module goes in P0/P14, P1/P15, P2/P16. Two modules cannot share a port
  • Start from the layout closest to your device (street light, parking sensor, crossing or noise monitor) and change it to match your plan
  • Build in small steps: get the input showing a number first, then add the rule, then the output. Flash and test after each step
  • Flash it: plug the micro:bit's own micro-USB port into the laptop, click Download, then drag the .hex file from Downloads onto the MICROBIT drive (if a connect box opens instead, follow its steps)
  • Run your first full test and note one thing that works and one thing to fix. Save: the Download also keeps a .hex in your Downloads (it follows you to any laptop). Next lesson: MakeCode home screen, Import, then Import File
🛠️ Plan Card
InputWhich sensor or button, and which port
ProcessThe rule, with a number: below 300, closer than 10 cm, louder than 150
OutputLED, strip colour, display number or beep, and which port
TestHow you will prove it works
💡 HintNothing happens? Check three things in order: the cable is in the port your code names, the shield's USB power is in, and you flashed the newest .hex.
// ASK AI"Help me write an input, process and output plan for a micro:bit smart street device"
📤 Submit via ConnectYour device's .hex file and plan card
// LEVEL UPGive your device a second output, such as a show icon on the micro:bit screen or a beep, that tells people what it is doing.
08
🔧 Test & Tune
▾
// SHIFT OBJECTIVEA test log of at least six runs in different conditions, one fix written as evidence, change and reason, and your device working reliably.
  • Plan six tests that match your device: dark and bright, near and far, quiet and loud, button pressed fast and slow
  • Run each test and log it: what you did, what should happen, what did happen
  • Find the test that failed most and fix it. Usually that means tuning a threshold or a pause
  • Write the fix as evidence, change, reason, for example: Run 3 the LED stayed off in shade. Changed 300 to 400. A higher threshold switches on earlier
  • Run all six tests again with the fix and log the results
  • Collect your printed enclosure if it is ready and check the shield and cables fit. Save: the Download also keeps a .hex in your Downloads (it follows you to any laptop). Next lesson: MakeCode home screen, Import, then Import File
🔧 Test Log
TestWhat you did, e.g. torch on the sensor
ExpectedWhat should happen
ActualWhat did happen
Pass?Yes or no, then fix the no's
💡 HintChange one number at a time and test again. Change three at once and you won't know which one fixed it.
🔍 Google Image Search"engineering test log table"
// ASK AI"How should an engineer decide which problem to fix first after testing?"
📤 Submit via ConnectYour test log and your evidence, change, reason fix
// LEVEL UPBoom Gate stretch: on a second micro:bit pushed into a Klip Motor Driver (3 x AA batteries), clip a gearmotor to its motor 1 output and add the Kitronik extension. Code it with the gate layout below, and add the send layout to your device micro:bit. Press B and the gate motor runs for one second. The Klip and the Grove Shield both need the micro:bit's edge connector, so the gate needs its own micro:bit.
// Blocks: device micro:bit sends (build it, no Copy)
on start
    radio set group (7)
on button [B] pressed
    radio send number (1)
// Blocks: gate micro:bit on the Klip (build it, no Copy)
on start
    radio set group (7)
on radio received [receivedNumber]
    if <(receivedNumber) = (1)> then
        turn [motor 1] [forward] at speed (60)
        pause (ms) (1000)
        turn off [motor 1]
Week 5
09
🗺️ Expo Prep
▾
// SHIFT OBJECTIVEYour device fitted in its printed enclosure and working, an info card made in Canva, its spot on the class city map chosen, and a 60-second demo rehearsed.
  • Fit the device into its enclosure. Check every sensor can still sense and every cable reaches. Small fixes only: a reprint will not be ready in time
  • Make an info card in Canva: device name, your firm's name, the street problem it solves, its input, process and output, and one test result
  • Choose where it goes on the class city map: street lights on corners, crossings near schools, parking sensors at the car park
  • Rehearse a 60-second demo: the problem, the device working live, how it decides, and one thing you fixed
  • Demo to another pair and swap one piece of feedback each
  • Pack your device box: micro:bit, shield, modules, cables and the enclosure
💡 HintPlan your demo so it works without you touching the code: the right .hex already on the micro:bit, power in, sensor pointing the right way.
🔍 Google Image Search"city map model classroom expo"
// ASK AI"Help me write a 60-second demo script for a smart city device built with a micro:bit"
📤 Submit via ConnectYour info card and a photo of your device in its enclosure
10
🏙️ City Expo
▾
// SHIFT OBJECTIVEYour device running live on the class city map, demos given to visitors, awards voted, and your files and reflection submitted.
  • Set up the city: tables become streets, every device goes in its spot with its info card, power in and the right program running
  • Half the pairs demo while the other half tour the city, then swap. Give every demo you visit one piece of feedback
  • Visitors test the devices: cover the light sensor, walk up to the parking sensor, press the crossing button, make some noise
  • The class votes: Smartest Sensor, Best Enclosure, Most Useful and People's Choice
  • Write your reflection: what your device does, the hardest bug you fixed, and what you would add with more time
  • Submit your final .hex, your Tinkercad enclosure link, a photo and your reflection
💡 HintIf something breaks on the day, explain what should happen and why. Engineers talk through problems calmly.
// ASK AI"Help me write a short reflection about building a smart city device with sensors and a micro:bit"
📤 Submit via ConnectYour final .hex, enclosure link, photo and reflection
🏙️

The City Expo Awaits

After 10 shifts of simulating, wiring, coding, printing and testing, every pair's device takes its place on the class city map. Demo it live, tour everyone else's, then vote for the awards.

🗺️ One class city
⚡ Live demos
🏆 Four awards

Join Tinkercad, then power up // Shift 01

SYSTEM ONLINE // YEAR 9 & 10 DIGITAL TECHNOLOGY CIRCUIT CITY // 10 SHIFTS