Physical Computing Using The Micro Bit

DASKEREL wrote this teaching and practice using Oak's sequence as a source. View the source lesson at Oak National Academy. Oak has not endorsed this material. Check Oak's terms and separate rights for third-party works.

Learning outcomes

Explain the input-process-output cycle on a micro:bit
Predict and test a simple LED display program

Vocabulary: microcontroller · input · process · output · LED · download

Retrieve previous learning

What is the order of a program's instructions called?

Check: Its sequence, triggered by a start or another named event.

Learn the concept

A micro:bit is a small physical computing device with inputs, processing and outputs. A program can display a heart on its LED matrix when it starts. In that case the start event is the trigger, stored instructions determine the pattern and the LEDs are the output. The device is not reading a person's feelings from the pattern.

Writing code in an editor and seeing a simulator are useful first steps, but the actual device must be checked separately. Transfer the approved program, observe the LED pattern and compare it with the planned grid. Hardware state, power and connection can differ from simulation. Preserve the editable source and a test note.

Use only school-approved devices and power arrangements. Never connect the board to mains or unapproved components. Provide a simulator, tactile or verbal equivalent where the LED display alone is inaccessible. A teacher needs to observe the actual transfer, run and correction.

Worked model

Draw a five-by-five heart grid using on/off positions.
Build a start-event block that displays that pattern in the approved editor.
Predict the displayed image in the simulator, then transfer and observe on the supervised device.
Record any mismatch and whether it came from pattern, transfer or device state.

Guided practice

The simulator shows a heart but the board stays blank. Is the algorithm proved wrong?

Hint: A simulation and physical run are separate checks.

Check the guided answer

No. Check approved power, connection and whether the current program transferred. Then inspect the start event and LED code. The blank board alone does not identify which step failed.

Independent practice

Write your own response to every question before viewing the model answers. Your writing stays in this page session; this activity does not submit, store or grade it. Avoid including private information.

Teacher observed practical evidence

A teacher must apply the school's risk assessment, allergy policy and any individual healthcare plan before the practical. Observe and record the criteria during supervised work. Written answers cannot certify practical safety or skill.

Teacher observes learner programming, connecting and testing a school-approved micro:bit and approved low-voltage components.
Learner demonstrates input-to-output behaviour, a boundary test and an identified correction using the saved code and device.
Teacher checks accessible participation and electrical safety; no mains connection, unsafe battery assembly or unsupervised wiring is implied by written work.

Find and correct a misconception

“A simulator success proves the device will always behave identically.”

Correction: Power, transfer and physical input conditions also need supervised device testing.

Extend and reflect

Change the arrow orientation and predict which LEDs change.

Guidance: Sketch before testing and compare the actual display, not only the editor view.

Where this lesson could lead · Computer Science GCSE → Daskerel Cloud and Infrastructure

This lesson practises: Explain the input-process-output cycle on a micro:bit. Algorithms, digital systems and safe practice support later software and technology work.

Next school subject: Computer Science GCSE. Check the subject and examination board that fit your school.
Later DASKEREL learning: Daskerel Cloud and Infrastructure. Explore further study and build evidence from practical work.
Later credential exploration: AWS Certified Cloud Practitioner is an example in this later specialism. Check current awarding-body requirements before planning an exam.
Example career direction: Cloud Support Engineer. Explore organisations and local support.

This is an exploratory route, not a promise of admission, a qualification, certification eligibility or employment. Years 7–9 learning is an early foundation; any later credential may require substantial study, experience or local approval.

Year 7 · Hardware, networks and the internet · original lesson pack

DASKEREL beta · internal AI review pending

Respond to a button input with an accessible output

DASKEREL wrote this teaching and practice using Oak's sequence as a source. View the source lesson at Oak National Academy. Oak has not endorsed this material. Check Oak's terms and separate rights for third-party works.

Learning outcomes

Use an event to control output
Test a button program across two inputs and reset

Vocabulary: button · event · state · output · test case

Retrieve previous learning

What must be checked after transferring a program to a physical board?

Check: The actual device output and input behaviour against the predicted result.

Learn the concept

A button press is an input event. A fictional classroom program can show A when button A is pressed and B when button B is pressed. The program must define behaviour for each event; merely naming two buttons does not ensure two distinct outputs. A start event may clear the display so testing begins from a known state.

Trace each event: initial blank display, press A, observe A; restart, press B, observe B. If both buttons can be pressed together, decide whether that case is in scope and what should happen. Do not claim a program handles it without testing. Event order and prior displayed state can otherwise confuse a result.

An LED letter alone may be inaccessible to some users. A simulator description, companion text or another approved output route can convey the same meaning. A teacher should observe both button tests on an approved device and record whether a correction was needed.

Worked model

Define a start event that clears the LED display.
Add separate button A and B handlers with distinct letter outputs.
Predict A and B results and test each after a reset.
Document simultaneous-press behaviour as tested or out of scope and provide a text equivalent.

Guided practice

Pressing B still shows A from a previous press. What should be investigated?

Hint: Inspect the B handler and display state.

Check the guided answer

Check whether button B has its own triggered handler and output, whether the program transferred, and whether A remained because no B update occurred. Reset and retest both events separately.

Independent practice

Write your own response to every question before viewing the model answers. Your writing stays in this page session; this activity does not submit, store or grade it. Avoid including private information.

Teacher observed practical evidence

A teacher must apply the school's risk assessment, allergy policy and any individual healthcare plan before the practical. Observe and record the criteria during supervised work. Written answers cannot certify practical safety or skill.

Teacher observes learner programming, connecting and testing a school-approved micro:bit and approved low-voltage components.
Learner demonstrates input-to-output behaviour, a boundary test and an identified correction using the saved code and device.
Teacher checks accessible participation and electrical safety; no mains connection, unsafe battery assembly or unsupervised wiring is implied by written work.

Find and correct a misconception

“If button A works, button B must work too.”

Correction: Each event handler and physical input needs its own test.

Extend and reflect

Specify a long-press action without confusing it with a short press.

Guidance: Define the time threshold and test just below, at and above it in an approved environment.

Where this lesson could lead · Computer Science GCSE → Daskerel Cloud and Infrastructure

This lesson practises: Use an event to control output. Algorithms, digital systems and safe practice support later software and technology work.

Next school subject: Computer Science GCSE. Check the subject and examination board that fit your school.
Later DASKEREL learning: Daskerel Cloud and Infrastructure. Explore further study and build evidence from practical work.
Later credential exploration: AWS Certified Cloud Practitioner is an example in this later specialism. Check current awarding-body requirements before planning an exam.
Example career direction: Cloud Support Engineer. Explore organisations and local support.

This is an exploratory route, not a promise of admission, a qualification, certification eligibility or employment. Years 7–9 learning is an early foundation; any later credential may require substantial study, experience or local approval.

Year 7 · Hardware, networks and the internet · original lesson pack

DASKEREL beta · internal AI review pending

Plan safe low-voltage input and output connections

DASKEREL wrote this teaching and practice using Oak's sequence as a source. View the source lesson at Oak National Academy. Oak has not endorsed this material. Check Oak's terms and separate rights for third-party works.

Learning outcomes

Explain why components need compatible power and shared reference
Trace a supervised external-input-to-output path

Vocabulary: pin · ground · voltage · circuit · sensor · actuator

Retrieve previous learning

What is an input on a physical device?

Check: A signal or event, such as a button press or sensor reading, that the program can process.

Learn the concept

A physical project may connect a school-approved sensor or output component to a micro:bit's labelled pins. A signal needs the appropriate input or output connection and a compatible ground/reference path. Component ratings, current limits and board version matter; wiring by colour alone is unsafe because colours are not a universal standard.

Plan the logic before touching hardware. For a fictional low-voltage light sensor, input is the measured level; the program compares it with a threshold; output is a text or LED indication. A threshold test should include just below, exactly at and just above the selected value. The result does not prove the sensor is calibrated for real safety decisions.

A teacher must select approved low-voltage parts, verify the manufacturer's connection guidance and supervise assembly. Do not connect to mains, improvised power sources or unknown loads. A simulated circuit or teacher demonstration can meet the conceptual goal when hands-on connection is inappropriate or inaccessible.

Worked model

State the fictional sensor's input, comparison rule and LED output.
Draw labelled board input, ground and approved component connections for teacher checking.
Predict outputs at values 29, 30 and 31 for a strict reading<30 condition.
Observe the supervised test and record differences from the predicted rule.

Guided practice

A rule is reading<30. Is output ON at 30?

Hint: Strict less-than excludes equality.

Check the guided answer

No. At exactly 30 the condition is false; output is OFF if that is the program's defined else state. Test 29, 30 and 31.

Independent practice

Write your own response to every question before viewing the model answers. Your writing stays in this page session; this activity does not submit, store or grade it. Avoid including private information.

Teacher observed practical evidence

A teacher must apply the school's risk assessment, allergy policy and any individual healthcare plan before the practical. Observe and record the criteria during supervised work. Written answers cannot certify practical safety or skill.

Teacher observes learner programming, connecting and testing a school-approved micro:bit and approved low-voltage components.
Learner demonstrates input-to-output behaviour, a boundary test and an identified correction using the saved code and device.
Teacher checks accessible participation and electrical safety; no mains connection, unsafe battery assembly or unsupervised wiring is implied by written work.

Find and correct a misconception

“Any external component can be connected to any pin if its plug fits.”

Correction: Electrical rating and pin function must match the board and approved component guidance under supervision.

Extend and reflect

Plan a simulated missing-reading test and a separate physical safety check.

Guidance: Use an explicit unavailable sentinel in simulation. Ask the teacher to specify whether approved hardware can detect disconnection; an analogue input may otherwise return a numeric value.

Where this lesson could lead · Computer Science GCSE → Daskerel Cloud and Infrastructure

This lesson practises: Explain why components need compatible power and shared reference. Algorithms, digital systems and safe practice support later software and technology work.

Next school subject: Computer Science GCSE. Check the subject and examination board that fit your school.
Later DASKEREL learning: Daskerel Cloud and Infrastructure. Explore further study and build evidence from practical work.
Later credential exploration: AWS Certified Cloud Practitioner is an example in this later specialism. Check current awarding-body requirements before planning an exam.
Example career direction: Cloud Support Engineer. Explore organisations and local support.

This is an exploratory route, not a promise of admission, a qualification, certification eligibility or employment. Years 7–9 learning is an early foundation; any later credential may require substantial study, experience or local approval.

Year 7 · Hardware, networks and the internet · original lesson pack

DASKEREL beta · internal AI review pending

Design a physical-computing solution from a brief

DASKEREL wrote this teaching and practice using Oak's sequence as a source. View the source lesson at Oak National Academy. Oak has not endorsed this material. Check Oak's terms and separate rights for third-party works.

Learning outcomes

Translate a user need into input, processing and output
Define safety, access and test criteria before building

Vocabulary: brief · prototype · input-process-output · constraint · acceptance criterion

Retrieve previous learning

Why must a component's voltage and pins be checked?

Check: Physical compatibility and safe operation cannot be inferred from wire colour or shape.

Learn the concept

A project begins with a bounded user need. A fictional classroom plant-care reminder might indicate when a teacher should check the pot; it must not claim to diagnose plant health or automatically water anything. Decide what the sensor actually measures and what the output means before selecting parts.

Write an input-process-output plan: read an approved sensor, compare a valid reading with a stated threshold, and show a labelled reminder. A simulated missing-input sentinel can show 'Reading unavailable'. A disconnected analogue pin may still return a number; physical detection requires a component-specific circuit or protocol designed and verified by the teacher. The threshold is a provisional classroom rule, not a plant-health diagnosis.

Acceptance criteria should be observable: the prototype indicates below and above threshold, responds safely to simulated missing input, and uses no unsafe wiring. A teacher checks board and component compatibility, decides whether physical disconnection detection is feasible, supervises low-voltage construction and provides an accessible alternative.

Worked model

Name the teacher user and the limited reminder purpose.
Sketch sensor input, validation, threshold comparison and labelled output.
Specify below, equal, above and missing-reading tests.
List approved parts, access alternatives and teacher safety checks before assembly.

Guided practice

A plan says 'The device proves the plant is healthy'. What narrower statement is justified?

Hint: The sensor measures one limited property.

Check the guided answer

Say 'The device reports this sensor reading relative to a chosen classroom threshold and reminds a person to check the plant'. It does not diagnose overall health.

Independent practice

Write your own response to every question before viewing the model answers. Your writing stays in this page session; this activity does not submit, store or grade it. Avoid including private information.

Teacher observed practical evidence

A teacher must apply the school's risk assessment, allergy policy and any individual healthcare plan before the practical. Observe and record the criteria during supervised work. Written answers cannot certify practical safety or skill.

Teacher observes learner programming, connecting and testing a school-approved micro:bit and approved low-voltage components.
Learner demonstrates input-to-output behaviour, a boundary test and an identified correction using the saved code and device.
Teacher checks accessible participation and electrical safety; no mains connection, unsafe battery assembly or unsupervised wiring is implied by written work.

Find and correct a misconception

“A sensor threshold is automatically a scientific diagnosis.”

Correction: A classroom threshold represents a chosen rule for one measurement; wider claims require relevant evidence and expert context.

Extend and reflect

Compare a sensor device with a simple manual inspection checklist.

Guidance: Explain when the added device helps and when the simpler method is safer or clearer.

Where this lesson could lead · Computer Science GCSE → Daskerel Cloud and Infrastructure

This lesson practises: Translate a user need into input, processing and output. Algorithms, digital systems and safe practice support later software and technology work.

Next school subject: Computer Science GCSE. Check the subject and examination board that fit your school.
Later DASKEREL learning: Daskerel Cloud and Infrastructure. Explore further study and build evidence from practical work.
Later credential exploration: AWS Certified Cloud Practitioner is an example in this later specialism. Check current awarding-body requirements before planning an exam.
Example career direction: Cloud Support Engineer. Explore organisations and local support.

This is an exploratory route, not a promise of admission, a qualification, certification eligibility or employment. Years 7–9 learning is an early foundation; any later credential may require substantial study, experience or local approval.

Year 7 · Hardware, networks and the internet · original lesson pack

DASKEREL beta · internal AI review pending

Build and debug a supervised device prototype

DASKEREL wrote this teaching and practice using Oak's sequence as a source. View the source lesson at Oak National Academy. Oak has not endorsed this material. Check Oak's terms and separate rights for third-party works.

Learning outcomes

Implement the planned logic in a safe prototype
Record a defect and a successful retest

Vocabulary: prototype · debugging · threshold · test log · fallback

Retrieve previous learning

What should an acceptance test specify?

Check: An input or condition and the expected observable output, including important boundaries or failure cases.

Learn the concept

Implement the smallest safe version first. In the fictional plant reminder, show a labelled status for a simulated sensor reading before connecting teacher-approved hardware. This isolates logic from wiring. For reading<30, decide explicitly whether 30 is normal or requires a check.

Test three values around the boundary and a missing-input case. Record expected and observed outputs. If the device says 'Check' at 30 despite a strict <30 rule, inspect the comparison rather than changing the written plan to match an accidental result. Keep a saved code version before the correction.

Only a teacher may approve and supervise the low-voltage setup and any external connection; never use mains or unknown loads. Simulate missing input explicitly, because a disconnected analogue input can still return a numeric value. Observe the actual device or accessible simulated equivalent. Practical competence requires seeing the learner build, run, explain and correct the prototype.

Worked model

Implement labelled output using simulated readings 29,30,31 and an explicit unavailable sentinel.
Compare each simulated result with the design's expected table.
Record one discovered mismatch, change the rule and rerun all four simulated cases.
Under teacher supervision, transfer to approved hardware and verify 29,30,31; test disconnection only if a component-specific detection method is designed.

Guided practice

A strict <30 program displays 'Check' at 30. Which code condition may be wrong?

Hint: Equality may have been included accidentally.

Check the guided answer

The program may use ≤30 instead of <30, or an else branch may be reversed. Inspect the actual blocks, correct the rule and retest 29, 30 and 31.

Independent practice

Write your own response to every question before viewing the model answers. Your writing stays in this page session; this activity does not submit, store or grade it. Avoid including private information.

Teacher observed practical evidence

A teacher must apply the school's risk assessment, allergy policy and any individual healthcare plan before the practical. Observe and record the criteria during supervised work. Written answers cannot certify practical safety or skill.

Teacher observes learner programming, connecting and testing a school-approved micro:bit and approved low-voltage components.
Learner demonstrates input-to-output behaviour, a boundary test and an identified correction using the saved code and device.
Teacher checks accessible participation and electrical safety; no mains connection, unsafe battery assembly or unsupervised wiring is implied by written work.

Find and correct a misconception

“A simulator result proves the external circuit is correctly connected.”

Correction: Simulation checks logic under modelled input; physical connections need separate supervised testing.

Extend and reflect

Design a version that shows the numeric reading as well as the label.

Guidance: Keep the unavailable state and explain how seeing the value helps debugging without implying medical or scientific certainty.

Where this lesson could lead · Computer Science GCSE → Daskerel Cloud and Infrastructure

This lesson practises: Implement the planned logic in a safe prototype. Algorithms, digital systems and safe practice support later software and technology work.

Next school subject: Computer Science GCSE. Check the subject and examination board that fit your school.
Later DASKEREL learning: Daskerel Cloud and Infrastructure. Explore further study and build evidence from practical work.
Later credential exploration: AWS Certified Cloud Practitioner is an example in this later specialism. Check current awarding-body requirements before planning an exam.
Example career direction: Cloud Support Engineer. Explore organisations and local support.

This is an exploratory route, not a promise of admission, a qualification, certification eligibility or employment. Years 7–9 learning is an early foundation; any later credential may require substantial study, experience or local approval.

Year 7 · Hardware, networks and the internet · original lesson pack

DASKEREL beta · internal AI review pending

Evaluate a physical prototype against its brief

DASKEREL wrote this teaching and practice using Oak's sequence as a source. View the source lesson at Oak National Academy. Oak has not endorsed this material. Check Oak's terms and separate rights for third-party works.

Learning outcomes

Use test evidence to evaluate the prototype
Explain a limitation and a next revision

Vocabulary: evaluation · evidence · limitation · revision · accessibility

Retrieve previous learning

Why test 29, 30 and 31 for a threshold of 30?

Check: They check just below, at and just above the boundary, exposing inclusive-versus-strict errors.

Learn the concept

Evaluate against the written criteria, not only whether the board lights up. Compare below/equal/above outputs on the supervised prototype and the explicit missing-sentinel case in simulation. A physical disconnected-input claim is only possible if an approved component-specific detection method was designed and tested. Include accessibility and electrical safety in the dated evidence table.

Separate what was demonstrated from what remains unknown. A classroom sensor reading can trigger a reminder but cannot prove a plant is healthy or that the device will work outdoors for months. If a test failed once, record it and explain the correction; hiding it removes evidence of the design process.

Suggest a realistic next revision, such as a clearer non-colour indication or a better missing-data message. Ask a user to interpret the output without coaching, then record their answer. A teacher must inspect the saved project and actual device; an evaluation paragraph alone is not practical sign-off.

Worked model

Revisit the original brief and four acceptance checks.
Compare expected and observed outputs, noting one defect and its retest.
State the limited claim the sensor evidence supports and an unresolved condition.
Prioritise one access or reliability revision and define a new task-based test.

Guided practice

Three physical threshold tests passed, but a disconnected analogue input still returned a number. Can the report claim automatic disconnection detection?

Hint: A numeric reading may not identify whether a sensor is attached.

Check the guided answer

No. Report the three passing threshold tests and the unresolved disconnection behaviour. Use an explicit missing sentinel in simulation; a teacher must specify and test a component-specific detection method before a physical unavailable state can be claimed.

Independent practice

Write your own response to every question before viewing the model answers. Your writing stays in this page session; this activity does not submit, store or grade it. Avoid including private information.

Teacher observed practical evidence

A teacher must apply the school's risk assessment, allergy policy and any individual healthcare plan before the practical. Observe and record the criteria during supervised work. Written answers cannot certify practical safety or skill.

Teacher observes learner programming, connecting and testing a school-approved micro:bit and approved low-voltage components.
Learner demonstrates input-to-output behaviour, a boundary test and an identified correction using the saved code and device.
Teacher checks accessible participation and electrical safety; no mains connection, unsafe battery assembly or unsupervised wiring is implied by written work.

Find and correct a misconception

“Reflection is just saying whether the project was enjoyable.”

Correction: Evaluation compares observed results with the design brief, records limitations and guides a specific revision.

Extend and reflect

Compare the prototype's reliability with a manual check method.

Guidance: Discuss when either method can fail and whether the device adds enough benefit to justify its complexity.