Session 1 · 60 min
What makes a motor turn, and what tells it to?
Power and signal. A motor turns only when a battery pushes current through it. On our kit the battery's power goes through the robotics board to the motor; the micro:bit, powered by the board, sends only a small signal that tells the board how fast. The parts are looked at, not connected, and the simulator shows only the display.
The adult says first: “A motor needs power to turn. The micro:bit only sends a signal.”
Learner card
- Turn the motor shaft by hand.
- Power comes from the battery.
- The signal comes from the micro:bit.
- Sort each card: power or signal?
- Guess, then say why.
Key words (show each with a picture): motor · power · signal
Timing (10 of 60 min at the screen)
- 15 minAway from the screen: Look and feel: turn an unconnected motor's shaft by hand; find the board's motor terminals, switch and sockets.
- 15 minAway from the screen: Card sort: power path or signal path, with a guess and a reason for each card.
- 10 minAt the screen: MakeCode: the adult's blocks in the simulator. The number shows; A and B turn nothing.
- 10 minAway from the screen: Cut and mark the card disc; say what the real spinner will do on A and on B.
- 10 minAway from the screen: Fill in the table; say which parts carry the power and which sends the signal.
In the studio
No studio lab or activity.
Outside the studio: MakeCode editor and its micro:bit simulator (makecode.microbit.org)
Hands-on
Nothing is powered: this session uses picture cards, unconnected parts and the simulator only. First, away from the screen, each pair turns the shaft of an unconnected TT motor slowly by hand and feels the gearbox, then finds the robotics board's motor terminals, its on/off switch and its servo sockets, connecting nothing. The group sorts picture cards (battery, holder switch, board, motor, micro:bit, USB cable) onto a power path and a signal path, with a guess and a reason for each card. Then the adult opens MakeCode with the board's extension added and shows the adult's blocks: “on start” holding “turn off Motor 1” and “show number” 30; “on button A pressed” holding “Motor 1 on direction … speed …” set to Forward and 30; and “on button B pressed” holding “turn off Motor 1”. MakeCode's simulator has no robotics board: the board's motor and servo blocks run there but move nothing, so the simulator checks only what the display shows. The learner says what the real spinner will do when A is pressed, and when B is. Last, each pair draws round a cup on thin card, cuts out a disc at most 10 cm across with safety scissors, rounds its edge and draws a mark near the edge.
Starting blocks: Built from scratch: the adult builds “on start” holding “turn off Motor 1” and “show number” 30, “on button A pressed” holding “Motor 1 on direction … speed …” set to Forward and 30, and “on button B pressed” holding “turn off Motor 1”; the learner changes only the numbers and the direction in this unit.
Evidence to collect
A prediction for each card, a short test table (Card | My guess | Why) for six cards, filled in by the learner, and the learner's spoken explanation of which parts carry the power and which part sends the signal.
Test table columns: Card | My guess | Why
- Predict
- Before the simulator runs, the learner says what it will show, and whether anything will turn when A is pressed.
- Debug
- If a card fits neither path, ask: does it carry the battery's push, or only a message about what to do?
- Reflect
- Why can the micro:bit tell the motor what to do but not make it turn?
Works towards: Power vs signal