micro:bit · Robotics & Coding

Turning embedded inputs and outputs such as buttons, LEDs, accelerometers, radio and sound into a real task using blocks or Python.

Completion evidence: MakeCode/Python programme, simulator test, device test and data record.

Test a small accelerometer- or button-driven programme first in simulation and then on the device; record differences in a table.

The order is recommended. Before a project page, complete evidence from foundation, practice and debugging lessons.

Turning embedded inputs and outputs such as buttons, LEDs, accelerometers, radio and sound into a real task using blocks or Python. A correct example alone is therefore insufficient. Completion evidence should be makecode/python programme, simulator test, device test and data record, tested with normal, boundary and invalid inputs.

In the first cycle, pair foundation and application among Variables and Loops, Buttons and Events, The Accelerometer, The LED Matrix, The MakeCode Editor. Predict the result, run or measure it, then explain any difference. Even when prediction and reality match, state which changed condition would break the result.

In the second cycle, complete this laboratory: Test a small accelerometer- or button-driven programme first in simulation and then on the device; record differences in a table. Do not close with one successful screenshot. Keep the input table, expected behaviour, actual behaviour, error or measurement and the correction in one file.

In the final cycle, connect Project: Bike Safety Light Prototype, Project: Wireless Scoreboard, Python on the micro:bit, Radio Communication, Measuring Temperature and Light. Let one lesson's output become another lesson's input; show where safe stopping is needed when data type, unit, wiring, timing or user expectation changes.

Repeat the same task one month later with less source support. Compare not only speed or appearance but test coverage, explainability, safety and whether another person can rebuild the work.

Use the foundation produced in Variables and Loops as an input to Pins and External Components. Then show in Measuring Temperature and Light how the same idea changes under the limits of a larger system. This bridge carries the goal of turning embedded inputs and outputs such as buttons, leds, accelerometers, radio and sound into a real task using blocks or python. beyond one isolated example.

Add three columns to the makecode/python programme, simulator test, device test and data record file: knowledge carried from the previous lesson, condition changed in the new lesson and result observed in testing. Sharing a word does not establish a connection; one lesson’s output should genuinely become the next process’s input.

Test the connection through this laboratory: Test a small accelerometer- or button-driven programme first in simulation and then on the device; record differences in a table. After the first attempt, add an edge condition such as empty data, wrong type, disconnected input, extreme value or user error. Record whether the system remains understandable and safe beyond the normal example.

• Name the previous lesson output
• State the one changed condition
• Separate expected and actual result
• Define safe stopping or error feedback
• Make one change in the second version