Public lesson / Robotics

What Question Is the Sensor Answering?

A machine reports 347. Is that bright, close, tilted, pressed, or meaningless? A sensor reading becomes useful only when we know what was measured and how the program interprets it.

Lesson rhythm

The idea moves toward a demonstration.

  1. Story, problem, or provocation

    Name the problem before opening the build.

  2. Theory and concept

    Make the hidden rule visible with small tests.

  3. Guided build

    Use the idea inside a working project system.

  4. Modification challenge

    Change one rule and predict the effect.

  5. Demonstration and cleanup

    Explain the result, save safely, and leave a known state.

Learning goals

What students should be able to do and explain.

  • Identify what a sensor measures.
  • Read a changing value.
  • Choose and test a threshold.
  • Distinguish measurement from decision.
  • Explain noise or variation.

Theory kernel

Small examples before the larger build.

button = pressed

read a two-state input

distance < 15

compare a measurement with a threshold

light level

inspect a changing value

read repeatedly

sample over time

Guided-build preview

micro:bit Reaction Timer

Wait for an unpredictable signal, press as quickly as possible, and make the timer distrust suspiciously early presses.

Open Guided Project
Students build

A waiting state, Random start delay, Visible go signal, Button response.

Concepts in use

Input, Timing, Variables, Randomness, State.

Finish line

A working version, one modification, one repaired problem, and an explanation.

Teacher checkpoints

Evidence before adding complexity.

  1. 1Student names the measured quantity.
  2. 2Several readings are observed.
  3. 3A threshold is stated and tested.
  4. 4Output changes for a clear reason.
  5. 5Student identifies one limitation.

Common mistakes

Pause, inspect, and test one cause.

  • Treating readings as perfect.
  • Choosing a threshold from one test only.
  • Calling the sensor intelligent.
  • Changing output without recording the input value.

Modification challenge

Three levels, one concept kept visible.

Higher levels are optional. They deepen the current idea rather than turning a beginner lesson into an unrelated advanced task.

LEVEL 1

Builder

  • Display raw readings before deciding.
LEVEL 2

Inventor

  • Compare two candidate thresholds.
LEVEL 3

Boss Level

  • Smooth several readings before acting.

End-of-class demonstration

Explain the work while it is still visible.

  1. What does the sensor measure?
  2. What values did you observe?
  3. Where is the threshold?
  4. What does the code decide?
  5. When could the reading be wrong?