Term 3 — Lessons 8–10

Unit 3 — micro:bit: Physical Computing with Purpose. A genuine step up from MakeCode blocks: real Python code, on real hardware, doing something real.

Lesson 8 — micro:bit + Python Editor: First Steps

What you'll achieve: a micro:bit programme that displays your name, a custom 5x5 image, and the current temperature.

micro:bitPython editor
from microbit import *
The line at the top of every micro:bit Python programme that "unlocks" its features.
display.scroll()
A command that scrolls text across the micro:bit's LED display, letter by letter.
Image()
A way of creating a custom picture on the 5x5 LED grid by describing which LEDs should light up.

I Do

Same micro:bit, same logic — just a different way of writing it, using Python instead of MakeCode blocks. from microbit import * unlocks the device's features. display.scroll("text") scrolls a message; Image("90009:09090:...") builds a custom picture from a 5x5 grid, colons separating rows. temperature() reads the built-in sensor — really the chip's own temperature, not precise room temperature.

We Do

  1. As a class, type from microbit import *, then display.scroll("Hello") and send it to the device.
  2. Add display.show(Image.HAPPY), then build one custom Image() together, explaining the grid numbering.

You Do

  1. Scroll your own name, then design and show your own custom Image().
  2. Add a line reading temperature() and scrolling it using str(temperature()).
  3. Add sleep(1000) pauses between sections and send your finished programme to your micro:bit.

Before You Go

What did you learn today? Explain in your own words.

Exit Ticket

Show what you've learned today.

Open Exit Ticket →

Lesson 9 — micro:bit Radio: Two Devices Talking

What you'll achieve: a working encrypted messaging system between two micro:bits, using a Caesar shift.

micro:bit (pairs)Python editor
Radio module
A built-in feature that lets a micro:bit send and receive short messages wirelessly with nearby micro:bits, with no internet needed.
radio.send() / radio.receive()
Commands that broadcast a text message, and check whether one has arrived.
Caesar cipher
A simple encryption method where each letter is shifted a fixed number of places in the alphabet.

I Do

Every micro:bit has a small radio inside it, like a walkie-talkie — two devices on the same "group" number can send short messages directly, no internet needed. Linking back to cybersecurity: we'll add a simple Caesar shift so the message isn't sent as obvious readable text. It's one of the easiest ciphers to break — this is about learning the CONCEPT of encryption.

We Do

  1. As a class, set radio.config(group=...) and test a plain send/receive between paired devices.
  2. Add the provided Caesar shift function: shift before sending, shift back before displaying.

You Do

  1. With your partner, agree who writes SEND and who writes RECEIVE.
  2. Build the encode-then-send and receive-then-decode logic, matching your radio group number.
  3. Test with at least two different messages to confirm it works consistently.

Before You Go

What did you learn today? Explain in your own words.

Exit Ticket

Show what you've learned today.

Open Exit Ticket →

Lesson 10 — micro:bit Project: Build Something Real

What you'll achieve: a working micro:bit programme from a chosen project brief, plus a 45-second demo to the class.

micro:bitPython editor
Threshold
A fixed value used to trigger a response when a sensor reading goes above or below it.
Debounce
A short pause added after a button press to stop a single press being registered multiple times.
Lookup
A simple stored list of matching pairs — such as Morse patterns to letters — that a programme checks against.

I Do

Choose ONE project: (A) Environmental monitor — reads temperature and light, warns on a threshold. (B) Reaction timer — random countdown using random.randint(), timed with running_time(), tracking a best of 5. (C) Morse code transmitter — button A is a dot, button B a dash, A+B resets, then a lookup shows the matching letter. Build the simplest working version first, then add features.

We Do

  1. Choose your project, then everyone writes and tests the simplest possible working version first.
  2. Teacher circulates to check progress before students build out the full brief.

You Do

  1. Build out your full project from your simplest working version.
  2. Test thoroughly — try to break it, and fix anything you find.
  3. Prepare a 45-second demo: what it does, and one thing that was hard to build.

Before You Go

What did you learn today? Explain in your own words.

Exit Ticket

Show what you've learned today.

Open Exit Ticket →