Session 1 · 60 min
What turns a chassis into a robot?
A robot needs a frame (the chassis), something that moves it (two motors and wheels), something that powers the motors (the battery, through the board's motor drivers), something that decides (the micro:bit's program) and a way to stop. Balance matters too: a third point, the caster, holds the front up, and the heavy battery sits near the wheels. The parts are looked at and laid out, not connected.
The adult says first: “A robot has a frame, movers, power, a decider and a stop. Let's find each one.”
Learner card
- Lay the parts on the chassis.
- Sort each card. Guess first.
- Where should the battery sit?
- Roll it down the ramp.
- Draw your layout.
Key words (show each with a picture): chassis · caster · balance
Timing (10 of 60 min at the screen)
- 15 minAway from the screen: Lay the parts on the chassis; sort the picture cards with a guess and a reason.
- 15 minAway from the screen: Balance test: the holder near the front, then near the wheels, down a card ramp.
- 10 minAt the screen: MakeCode: the adult's blocks in the simulator. Nothing moves there.
- 10 minAway from the screen: Draw the layout from above, with the power path in arrows.
- 10 minAway from the screen: Fill in the table; say what each part adds.
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 unconnected parts, picture cards and the simulator only. First, away from the screen, each pair lays the parts on the chassis board without fixing anything: two motors with wheels at the back, the caster at the front, the battery holder, the robotics board and its micro:bit slot. They sort picture cards into frame, movers, power, decider and stop, with a guess and a reason for each. Then the balance test: with the holder taped first near the front and then near the wheels, each pair rolls the unpowered chassis gently down a short card ramp and watches whether it tips, drags its caster or runs straight. In MakeCode next, the adult shows the adult's blocks: “on start” holding “turn off all outputs”, “set armed to …” 0 and “show icon” set to Heart; “on button A pressed” holding “set armed to …” 1, “pause (ms)” 3000 and an “if then else” whose condition is “0 < 0” with 0 on the left and armed on the right: then “Motor 1 on direction … speed …” and “Motor 2 on direction … speed …” both Forward at 30, “pause (ms)” 2000 and “turn off all outputs”; and “on button B pressed” holding “set armed to …” 0 and “turn off all outputs”. 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 rover will do when A is pressed, and why B during the wait stops it from starting. Last, the pair draws its layout from above, with arrows for the power path.
Starting blocks: Built from scratch: the adult builds “on start” holding “turn off all outputs” and a Heart; “on button A pressed” holding a 3000 ms wait, a check that B was not pressed during it, both motors Forward at 30, “pause (ms)” 2000 and “turn off all outputs”; and “on button B pressed” holding “turn off all outputs”. The learner changes only the numbers and the directions in this unit.
Evidence to collect
A prediction for each card, a short test table (Part | My guess | Why) for six parts, filled in by the learner, and the learner's spoken explanation of what each part adds to a chassis, and where the battery balances best.
Test table columns: Part | My guess | Why
- Predict
- Before the balance test, the learner guesses where the battery should sit, and what the rover will do when A is pressed.
- Debug
- If the chassis tips or drags on the ramp, move the heaviest part and roll it again: change one thing at a time.
- Reflect
- Which part turns a moving chassis into a robot, and why?
Works towards: Mechanical assembly, Motor drivers