Computing · Year 6

Active learning ideas

Inputs: Sensing the Environment

Active learning works well for this topic because students physically connect sensors to microcontrollers and test real-time responses, turning abstract concepts into concrete experiences. Hands-on trial and error with circuits and code helps students grasp how inputs trigger outputs, building lasting understanding through direct engagement.

• National Curriculum Attainment Targets
• KS2: Computing - Programming and Algorithms
• KS2: Computing - Computer Systems and Networks

• 25–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Stations Rotation
• 45 min · Small Groups

Stations Rotation: Sensor Stations

Prepare three stations with light, sound, and touch sensors wired to microcontrollers. Students predict outputs, write simple if-then code, test responses, and log data. Groups rotate every 10 minutes to compare sensor behaviours.

Analyze how sensors act as the 'senses' of a computer system.

Facilitation Tip

During Station Rotation, circulate with a multimeter to demonstrate how voltage changes across sensors, reinforcing the connection between physical signals and code values.

What to look for

Present students with images of different devices (e.g., a doorbell with a button, a night light, a motion-activated camera). Ask them to identify the primary sensor input for each device and explain what output it might control. For example, 'What sensor does the night light use, and what does it turn on?'

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 02

• Inquiry Circle
• 35 min · Pairs

Pairs Challenge: Light Gate

In pairs, connect a light sensor to control a motor or LED that activates when light breaks. Adjust sensitivity thresholds through code tweaks and test with hands or torches. Pairs present their working gate to the class.

Differentiate between different types of sensors and their applications.

Facilitation Tip

For the Pairs Challenge, provide stopwatches to time how long the light gate signal stays active, linking duration to programming logic for precise control.

What to look for

Give each student a card with a scenario: 'Imagine you are programming a robot to water plants. What sensor would you use to know when the soil is dry, and what action (output) would the robot take?' Students write their sensor and action on the card.

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Activity 03

• Inquiry Circle
• 40 min · Small Groups

Whole Class: Sound Monitor

Program sound sensors class-wide to light LEDs at set volume levels, simulating a concert decibel checker. Collect group data on thresholds, then discuss variations in a plenary.

Construct a program that uses a light sensor to turn on an LED when it gets dark.

Facilitation Tip

In the Whole Class activity, use a decibel meter app to show students how sound levels translate to sensor readings, making the invisible visible.

What to look for

Facilitate a class discussion: 'How is a light sensor like a human's eyes? What are the limitations of a light sensor compared to eyes? Can you think of a situation where a computer needs to 'sense' something to work properly?'

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

Activity 04

• Inquiry Circle
• 25 min · Individual

Individual Debug: Touch Toggle

Each student codes a touch sensor to toggle an LED on and off with presses. They debug wiring or code errors independently before sharing fixes.

Analyze how sensors act as the 'senses' of a computer system.

Facilitation Tip

During Touch Toggle, ask students to press and hold the button for different lengths to observe how timing affects output behavior and code logic.

What to look for

Present students with images of different devices (e.g., a doorbell with a button, a night light, a motion-activated camera). Ask them to identify the primary sensor input for each device and explain what output it might control. For example, 'What sensor does the night light use, and what does it turn on?'

• Analyze
• Evaluate
• Create
• Self-Management
• Self-Awareness

A few notes on teaching this unit

Teachers should emphasize the separation of concerns: wiring the hardware first, then coding the logic to interpret input values. Avoid rushing to solutions—let students experience failures during testing, then guide them to diagnose issues by checking connections and code together. Research shows that guided trial and error with immediate feedback strengthens understanding of input-output relationships more than demonstrations alone.

Successful learning looks like students accurately wiring sensors to microcontrollers and writing programs that respond to environmental changes. They should explain why inputs need calibration, identify sensor types, and debug errors by checking both wiring and code. Clear evidence includes working systems and confident explanations of how inputs and outputs relate.

---

Watch Out for These Misconceptions

• During Sensor Stations, watch for students who assume the sensor alone turns on the LED without programming.

  Set up a station with a disconnected sensor and ask students to observe that nothing happens, then guide them to connect it and write the minimal code to activate the LED, showing the necessity of both hardware and software.

• During Station Rotation, watch for students who think all sensors work the same way.

  Have students measure and record the resistance values of the light sensor in bright and dim light, compare the sound sensor’s signal shapes, and test the touch sensor’s response time, highlighting their unique behaviors.

• During Touch Toggle, watch for students who believe computers can sense touch without physical hardware.

  Ask students to disconnect the touch sensor and test the program, then reconnect it to observe the difference, reinforcing that hardware is essential for real-world sensing.

---

Methods used in this brief

• Stations Rotation
• Inquiry Circle