Light It Up

Overview

Students build confidence using a NeoPixel strip with a micro:bit in Kittenblock. They learn to identify power, ground and data connections, connect hardware safely, find NeoPixel blocks, and create, test and revise a simple coloured-light sequence. No prior electronics or coding knowledge is assumed.

Learning intentions

• WALT identify NeoPixel power, ground and data connections.
• WALT connect a NeoPixel safely to a micro:bit.
• WALT use sequence and decision blocks in Kittenblock.
• WALT test, debug and improve an algorithm with a partner.

Success criteria

• I can explain what power, ground and data do.
• I can connect the NeoPixel correctly and unplug before changing connections.
• I can create a sequence of at least three coloured lights.
• I can use a checklist to find and fix a problem.

Curriculum links

• Digital Technologies — computational thinking through algorithms, sequence, decisions, testing and debugging.
• Digital Technologies — designing, developing and evaluating a digital outcome for a purpose.
• Technology — technological practice through planning, making, testing and improving.
• Key competencies — thinking; managing self; participating and contributing; relating to others.

Lesson structure (60 minutes)

1. 0–5 min · Hook and confidence check. Teacher displays a NeoPixel and asks, “How could we make a light show without touching each light?” Open with the introduction and hook slides and reassure students that today’s goal is safe exploration, not perfect coding. Students complete a quick fingers rating from 1 (new to this) to 5 (confident) and share one question with a partner.

2. 5–15 min · Safe setup demonstration. Teacher uses the slides and a large model or projected image to introduce power, ground and data. Explain: power supplies energy, ground completes the circuit, and data carries instructions. Demonstrate the routine: turn off or unplug the micro:bit/NeoPixel power before moving any wire; check connections; reconnect only when directed. Model matching NeoPixel labels to micro:bit pins, including the data pin selected in Kittenblock. Students watch, repeat the safety routine aloud and identify each connection on their own kit without plugging in.

3. 15–25 min · Kittenblock walkthrough. Teacher live-demonstrates opening the NeoPixel blocks, choosing the number of pixels and data pin, setting a pixel or strip colour, showing the pixels, waiting, and clearing them. Build a three-step example: red, then green, then blue. Think aloud about the algorithm as ordered instructions and show one intentional error, such as the wrong data pin, then debug it. Students open Kittenblock, locate the blocks and predict what the sequence will do before running it. Refer again to the block-location and demonstration slides.

4. 25–42 min · Pair programming challenge ladder. Teacher places students in pairs, assigning Driver (controls the computer) and Navigator (reads the steps and checks safety); swap roles halfway. Distribute the NeoPixel setup and challenge worksheet. Students connect hardware only after the teacher’s signal, then complete one level at a time:

• Level 1 — Make it glow: display one colour, wait, then clear.
• Level 2 — Create a sequence: display three different colours in a chosen order, with a short wait between each.
• Level 3 — Add a decision: use a button press to trigger the sequence, or create two different light responses for two buttons.

Partners test after each change, record what happened, and revise their algorithm. Students who finish early improve timing, add a repeat, or explain why their chosen sequence is clear and effective. Use the challenge ladder and pair-programming instructions throughout.

5. 42–52 min · Troubleshooting and peer test. Teacher pauses the class and models calm debugging: describe the symptom, change one thing, test again, and record the result. Students use this checklist with another pair:

• Is the NeoPixel power connected to power?
• Is ground connected to ground?
• Is data connected to the selected micro:bit pin?
• Is the number of pixels correct?
• Does the Kittenblock program use the same data pin?
• Did we show or update the pixels?
• Did we unplug before changing connections?

Pairs give one specific warm feedback comment and one suggested improvement. The teacher checks connections and asks selected students to explain their debugging choice.

6. 52–60 min · Share and exit ticket. Invite two or three pairs to show their sequence or describe their algorithm. Revisit the learning intentions using the plenary and reflection slides. Students complete an individual exit ticket: “What do power, ground and data do?”, “Write the safe connection-changing routine”, and “Name one problem you solved or question you still have.” Students replace components carefully and leave kits disconnected.

Resources

• Computers with Kittenblock installed
• Micro:bits, NeoPixel strips or rings, batteries and connecting leads
• Projector and teacher demonstration kit
• the NeoPixel introduction and demonstration slide deck
• the NeoPixel setup and challenge worksheet
• NeoPixel connection diagram or enlarged component labels
• Troubleshooting checklist displayed or printed on the worksheet
• Coloured pens or pencils for planning sequences

Assessment

• Observe whether students correctly identify power, ground and data before connecting.
• Question pairs during programming: “What should happen next?”, “Which instruction might be causing the problem?”, and “What did you change?”
• Collect exit tickets and worksheet evidence to check safe setup, algorithmic thinking and debugging. Note students needing a supported re-teach of connections or Kittenblock blocks.

Differentiation

• Support: provide colour-coded leads, a labelled connection diagram, partially completed starter code, block screenshots and sentence starters such as “The problem was… I changed… The result was…”.
• Pair students deliberately and use Driver/Navigator roles; allow students to rehearse the safety routine verbally before handling equipment.
• EAL and learning support: pre-teach power, ground, data, sequence, decision and debug with icons and gestures; give instructions one step at a time and check understanding privately.
• Extension: students complete Level 3, use two different button decisions, add a repeat or timing pattern, and justify how testing led to an improvement.