OWN the world,
one sensor at a time.
Pathways turns a Raspberry Pi and a handful of inexpensive sensors into a way to see the world — the weight of the air, the shake of the floor, the fingerprint of light, the beat of your own heart. Every project pairs real science and making with a DBT mindfulness skill, so curiosity and emotional steadiness grow in the same breath.
This is hands-on learning the self-reliant, DIY way: source your own parts, substitute what you have, and think asymmetrically about how to reach the result. Every project is compatible with — but does not require — a Piper Play Computer. A bare Raspberry Pi and a few cheap components do everything here.
Observe · Wise Mind · Non-judgmentally — to observe the world honestly is the scientific stance, and the mindful one.
You don't need to be an engineer.
Pathways is built on a philosophy of productive struggle and self-reliance — the idea that meaningful learning happens when we're a little stuck and have to improvise our way through. Every module includes a plain-English explanation, substitution suggestions for parts you don't have, troubleshooting prompts, and a mindfulness anchor so frustration becomes a teachable moment instead of a roadblock.
It all runs on a bare Raspberry Pi and a handful of inexpensive parts — source them, substitute freely, and think asymmetrically about how to reach the result. Already own a Piper Computer Kit? Everything works on one too; its build-specific guides live in the Piper tab.
Set up your Pi
Flash Raspberry Pi OS, gather a few parts, and get to a desktop. The Shopping List shows three ways to do it, from $0 to a full kit.
Start with one sensor
Pick a first project — the ultrasonic theremin or color-mood lamp are friendly entries. Wire one sensor, run the code, see it work. Confidence compounds.
Work through Pathways
Fifty original projects across audio, sensors, breadboard electronics, the sciences, space radio, and growing — each braided with a mindfulness skill.
Invent something
Combine sensors, remix the code, build something nobody assigned. The whole arc is a runway to that moment of self-directed making.
The project library.
Tap a card to open the full module: materials list, step-by-step instructions, code, a mindfulness anchor, teacher notes, and extension challenges. Audio projects focus on signal processing and music. Sensor projects explore the world through measurement.
Ultrasonic Theremin
Wave your hand above the sensor and play a sci-fi instrument. Distance becomes pitch — the most satisfying first project in audio coding.
Chromatic Sequencer
Slide the color sensor across paper strips of different colors — each color triggers a note. You've built an optical step sequencer.
Thermal Ambient Generator
Breathe on the temperature sensor. Ice cube nearby. The music responds — cold becomes minor and sparse, warm becomes bright and faster.
Granular Distance Delay
Move closer for tight echoes. Pull back for cavernous reverb. Real-time DSP with the ultrasonic sensor as your effects knob.
Reaction-Time Drum Machine
Five buttons, five drum pads. The ultrasonic sensor sweeps a filter cutoff like a real DJ. Snap your hits to a beat grid.
Audio-Reactive LED Visualizer
Run a Fast Fourier Transform on live audio. Bass hits one LED, treble hits another. Watch one of engineering's most important algorithms light up.
Morse Code Translator
Tap a button to send dots and dashes. The buzzer plays them back; the screen decodes them. A first taste of encoding and protocols.
Color-Mood Lamp
Point the color sensor at any object — the LEDs (or screen) recreate that color. A physics-of-light lesson in disguise.
Hot or Cold Treasure Hunt
Hide a target. The buzzer beeps faster as the player gets closer. A classroom-wide game that teaches feedback loops.
Plant Whisperer
Aim the color sensor at a leaf daily. Log RGB over weeks. Watch chlorophyll change. Real environmental data collection.
Memory Color Game
The screen flashes a color sequence; the player has to present colored cards back in order. Simon, but with a real sensor.
Distance-Based Music Box
Each height "zone" plays a different note. A multi-octave keyboard with no keys. Bridges audio and sensor work nicely.
Stealth Detector
Aim ultrasonic down a hallway. Anyone who crosses sets off the buzzer and LEDs. Add a logging feature to learn about event data.
Color-Sorting Helper
Hold a colored item up — the program tells you which bin it goes in via LED color. The same principle real recycling sorters use.
Cymatics Simulation
Combine audio + sensor + visuals. Temperature controls a buzzer pitch; the screen draws Chladni-pattern geometry at that frequency.
Build a real effects-pedal rig.
A second curriculum thread: real-time audio effects, the kind of signal processing that lives inside every guitar pedal, mixing board, and music production app. Six modules progressing from a clean signal path through wah, distortion, delay/looper, modulation, and ending with a multi-effects patchbay. Best for grades 6–8 after they've completed Modules 1–6 of the main track.
💡 Pair these with the virtual oscilloscope — students can see what their pedal does to the waveform, which is half the magic.
The Clean Signal Path
Before any effect, you need a working audio chain: mic in, processing, speaker out. Build a "buffer pedal" that does nothing — the cleanest test there is.
Ultrasonic Wah
A sweeping bandpass filter controlled by your hand's distance from the sensor. Hendrix sound, no foot pedal required. The most fun first effect.
Soft-Clip Distortion
The mathematical heart of distortion — clipping the waveform. See it on the oscilloscope. Add a tone knob via the color sensor.
Echo & Looper
Build a delay line first, then extend it into a record-and-loop pedal in the spirit of a Boss RC-1. Tap a button, capture a phrase, layer.
Tremolo & Vibrato
Two effects that sound similar but work very differently — one modulates amplitude, the other modulates pitch. Compare on the oscilloscope.
Multi-FX Patchbay
The capstone. Combine 2–3 of the previous pedals. Switch effects with buttons. Order matters. A real performance instrument.
The breadboard-pedal series.
The most advanced track in this curriculum. Students construct real analog effect pedals on breadboards using transistors, op-amps, and diodes — then route a real electric guitar through the builds, into the Pi for live oscilloscope visualization, and out to a school amplifier. Four modules: a JFET buffer, a one-transistor fuzz, an op-amp overdrive, and a capstone studio signal chain. Best for grades 7–8 after the six software pedals (P1–P6) are familiar.
🔌 Hardware needed: electric guitar + amp (battery-powered preferred), USB audio interface (Behringer UCA202 ~$30 recommended), additional breadboards, 9V batteries, jumper wires, components per BOM. Adult supervision required throughout — these are real circuits.
📈 Live oscilloscope: the companion guitar_scope.py script
reads from the USB audio interface and shows real-time waveform + spectrum + clipping indicator —
students literally see their analog circuits at work.
Breadboard Buffer
Your first real analog pedal. JFET source-follower buffer on a breadboard. Establishes the full signal chain: guitar → buffer → audio interface → Pi (scope) → amp. The most boring pedal and the most important one to build.
Bazz Fuss
The legendary one-transistor DIY fuzz pedal. One 2N3904 transistor, one diode, a handful of resistors and caps. See clean sine waves become square waves on the scope. Same hard-clip math as Pedal 03, in silicon.
Op-Amp Overdrive
The "real" overdrive architecture — same as the Tube Screamer, Klon, and every boutique drive in your local music store. TL072 op-amp + symmetric diode clipping. Soft-clip math, in silicon. After this, commercial pedals are no longer mysterious.
Studio Signal Chain
The full capstone. Combine P7, P8, and P9 into a working signal chain. Real guitar in, real amp out, live oscilloscope monitoring on the Pi. Students choose chain order, settings, and record a 60-second performance. Wise Mind in practice.
The Science Lab.
The same Raspberry Pi that runs a theremin can read the weight of the air, feel the floor shake, fingerprint light, and draw your heartbeat. These flagship modules reach across the sciences — meteorology, geology, astronomy, physics, chemistry, biology, environmental science, and the science of your own mind — each turning an invisible phenomenon into something you can see, with a mindfulness skill that fits the work.
🔭 One flagship per field to start. Each runs on a bare Raspberry Pi plus one inexpensive sensor (most $3–25) — no Piper kit required, though it works on one too. The depth (full prep checklists, standards, handouts) gets filled in over time; this is the broad map.
Observe · Wise Mind · Non-judgmentally — the OWN framework runs through every project here, the same way it does the rest of the curriculum. To observe the world honestly is the scientific stance.
Body & Mind.
This is where the OWN framework stops being an idea and becomes something you can feel and measure. These projects turn your own body into the instrument: your breath, your heartbeat, your reaction time, the temperature of your hands. Watch your body respond to your mind — and learn, in data, that you can steer your own state.
🫁 Start with the Breathing Coach below — it needs no hardware at all. The sensor-based modules build on the Science Lab's heart (S6) and stress-signal (S9) projects and run on any Raspberry Pi.
The Breathing Coach · no hardware needed
Pick a pattern, press Begin, and follow the orb. A long, slow out-breath is the body's brake pedal. Open full-screen ↗
The Body & Mind modules
Space.
One $30 USB dongle — a software-defined radio — turns any Raspberry Pi into a receiver that climbs outward. These five projects form a ladder: first the local FM band, then the aircraft overhead, then live images from weather satellites, then the voices of the crewed Space Station, and finally the faint hydrogen-line hum of our own Milky Way. Each rung reaches farther from Earth, and each carries a mindfulness skill that fits the work.
📡 It all runs on one RTL-SDR dongle (~$30). The first projects use the kit's own antenna; the satellite and galaxy modules add a simple home-built antenna (and, for the hydrogen line, a low-noise amp). No Piper required — any Pi works.
Observe · Wise Mind · Non-judgmentally — the unit opens by simply observing a sky full of signals and ends in the Wise Mind blend of awe and rigor needed to hear a galaxy.
The Growing Lab.
The most tangible science there is: you can grow a plant — or lose one — based on what your data tells you. These six projects trace the whole arc of growing, from reading the water in the soil, to automating a plant's care, to driving growth with light, to starting seeds, to watching compost turn scraps into soil, and finally to tending a whole living environment at once.
🌱 Each runs on a bare Raspberry Pi plus inexpensive parts (most $5–15). The analog soil sensor reuses the same MCP3008 ADC pattern from the Calm Dashboard, and the automated modules use a relay so the Pi can safely switch pumps, lights, and heat mats. No Piper required — any Pi works.
Observe · Wise Mind · Non-judgmentally — the unit opens by simply observing what the soil holds and ends in the Wise Mind work of tending a whole system whose needs pull against each other.
The virtual oscilloscope.
Generate waveforms, apply effects, and watch what happens to the signal in real time. This is the teaching companion for the Effects Pedals and Breadboard Builds — students can see clipping, tremolo, delay, and filtering on screen before they ever touch hardware.
Open the full oscilloscope in a new tab ↗
The embedded version below works in most browsers. If it appears blank (some browsers block embedded local files), use the button above to open it directly.
Module quizzes.
Quick checks tied to the modules. Pick a quiz, answer the questions, and see how you did. When you're finished, you can submit your results to your teacher through Google Classroom, download a results sheet, or copy them to turn in however your class does it.
The Teacher Portal.
Everything you need to bring Pathways into your classroom: pacing guides, lesson scaffolds, assessment ideas, classroom-management tips, and quick answers to the questions you don't want to ask in front of your students.
A Suggested Year Arc
This arc assumes a bare Raspberry Pi and the DIY path. If your class is using Piper Computer Kits, swap Weeks 1–5 for the kit's build-and-StoryMode sequence in the Piper tab — everything after that is identical.
Set Up & Source
Flash Raspberry Pi OS, get to a desktop, run the one-time Python setup (Troubleshooting → “ImportError”), and gather parts. Students learn what a Pi is, how to source components, and how to improvise substitutes — self-reliance from day one.
First Light
Wire one sensor and blink an LED; run your first script. The goal is the thrill of "I made the physical world respond to code" — pick one or two of the easiest modules.
Python Basics (Thonny)
Variables, loops, conditionals, events — taught through the sensor code students are already running. Thonny ships with Raspberry Pi OS and needs no setup.
Pathways Modules
Pick 6–10 modules across audio, sensors, and the Science Lab. Two weeks per module is comfortable.
Sonic Pi Deep Dive
Live coding music. Even reluctant students engage when the loop is "code → hear it instantly." Free on any Pi.
Build & Invent
Students propose, design, and build their own project — combining sensors and remixing code. They'll surprise you.
Showcase
Present, reflect, document. Reset the kits and parts for next year's group.
How Each Module is Structured
We use a modified 5E framework (Engage, Explore, Explain, Elaborate, Evaluate) woven with DBT mindfulness practice. Every module follows this rhythm:
Engage (5–10 min)
A "hook" — a sound, a video clip, a quick demo. Pair this with the Mindful Moment named for that module. Ground students before they touch the kit.
Explore (15–25 min)
Wiring time. Hands on the breadboard. This is where things go sideways — and that's exactly the point. The mindfulness anchor pays its rent here.
Explain (10 min)
Whole-class pause. Pull up the code. Walk through what each line does. Ask: "What surprised you?"
Elaborate (15 min)
Pick a challenge from the Extensions section. Encourage remixing — the goal is divergence from the recipe.
Evaluate (5–10 min)
Use the Reflection Prompts. Verbal share-out or written exit ticket. Sample rubric in the Assessment card below.
Mindful Close (3 min)
End every session with one breath cycle and a single sentence: "One thing I noticed today was ___."
Classroom Management Tips
Pair Students Thoughtfully
This work goes best in pairs. Pair a confident student with a hesitant one, and rotate roles every session: Driver (hands on hardware), Navigator (reads the steps aloud).
Establish a "Pause Signal"
Frustration spikes with electronics. Teach one signal — three slow breaths, hands flat on the table — that any student can call. The whole group respects it. It models the Wise Mind skill in action.
Color-Code Your Wires
Use the same color conventions every project. Red = power, black = ground, yellow = signal. Reduces cognitive load enormously, especially K–3.
Have a "Help Queue"
A clipboard at the front. Students write their name + question. You triage. Prevents the "twelve hands up at once" classroom panic.
Photo-Document Wiring
Before a session ends, have each pair photograph their breadboard. Saves 15 minutes of rewiring next time and teaches documentation.
Celebrate "Beautiful Mistakes"
Once a week, ask: "Who made the most interesting mistake?" Sometimes those become next year's lesson plans. Always: this destigmatizes failure.
Assessment Approaches
Demonstration Rubric
Each module has a "minimum viable demonstration" — does the theremin make sound? Does the color sensor pick up red?
- Emerging: Wired correctly with help, code partially works
- Developing: Wired independently, baseline code works
- Proficient: Works fully; can explain one part of the code
- Advanced: Completed at least one Extension challenge
Engineering Journal
A composition notebook per student. Each session, three entries:
- One sketch of the circuit
- One sentence: "What I tried that didn't work"
- One sentence: "What I noticed today" (the mindfulness piece)
Peer Teach-Back
At module completion, a pair teaches their build to a different pair. You learn what they actually understand in 90 seconds. (Also: Vygotsky was right.)
Self-Assessment
A 5-question reflection at module end:
- What worked the first time?
- What did you fix? How?
- What's still confusing?
- What would you try next?
- How did you feel when stuck?
Standards Alignment (Quick Map)
These modules align with multiple frameworks. Use this as a starting point for your curriculum mapping.
CSTA K–8 Computing
1B-AP-08 (algorithms), 1B-AP-10 (variables), 2-AP-10 (designing programs), 2-AP-13 (modularity).
NGSS Engineering
3-5-ETS1-1, 3-5-ETS1-2 (engineering design); MS-ETS1-3, MS-ETS1-4.
NGSS Physical Science
4-PS3-2 (energy transfer); 4-PS4-1 (waves); MS-PS4-1 (wave properties).
SEL / DBT Skills
CASEL self-awareness & self-management. DBT Mindfulness "What" and "How" skills throughout.
Math Practice
CCSS.MATH.PRACTICE: MP.1 (persevere), MP.4 (model), MP.5 (use tools).
ISTE Standards for Students
4 (Innovative Designer), 5 (Computational Thinker), 6 (Creative Communicator).
Safety Considerations
Eye Protection
Not strictly required, but encourage when soldering or working with sharp tools. Snipped wire ends fly.
Heat Awareness
The Raspberry Pi runs warm under load. Not dangerous, but worth noting. Resistors can also warm up if mis-wired.
No Mouth Contact
Small parts. Especially with younger students. Set the expectation explicitly on day one.
Hearing
Audio modules can get loud. Set volume caps. Keep a quiet-zone for over-stimulated students.
Classroom management for a maker room
A room full of breadboards, sensors, and excited kids is a different beast than a worksheet day. Here's what actually works, learned the hard way.
The "no code until the wiring's checked" rule
One whole-class rule cuts debugging time in half: nobody runs code until a partner OR you have eyeballed the wiring. It also quietly teaches the Observe skill.
Parts accounting
Count components out at the start and back in at the end. A magnetic parts tray per pair saves the "where did the JFET go" panic. (It's on the floor. It's always on the floor.)
Designate roles
Per pair: one "Driver" (touches the breadboard), one "Navigator" (reads the steps). Swap halfway. Cuts the "I never get to do it" friction in half.
The two-minute rule
If a pair has been stuck for two minutes, they raise a "help flag" (a red cup works) and move to a parallel task while they wait. Stops the logjam at your elbow.
Volume governor
Set amp/speaker caps BEFORE class. Establish a universal "hands up, volume down" signal. A fuzz pedal into a wide-open amp is a fire alarm with extra steps.
The reset ritual
Last 5 minutes: photo of the breadboard (for tomorrow), parts back in the tray, lids closed. Non-negotiable. Future-you teaching 4th period will weep with gratitude.
The teacher's lounge ☕
Just for you. Students don't see this section. Pour the burnt lounge coffee and let's be honest for a second.
You will say "please don't put that in your mouth" to a 13-year-old holding a resistor. They are old enough to know better. They will do it anyway. This is the job. Caffeinate accordingly.
Somewhere in third period, a kid will wire a fuzz pedal, crank it, and discover the exact frequency that makes the whole room say "OHHH." You'll pretend to be annoyed. You will secretly be thrilled. That's the good stuff.
The lesson plan says 90 minutes. Reality says 45 minutes of building, 30 minutes of "it's not working" (it was the battery), and 15 minutes of pure chaos you'll later describe to admin as "collaborative inquiry."
You have explained virtual ground four times. Three kids get it. One is using the multimeter probes as drumsticks. This is a 75% success rate. In this economy, that's a win. Take it.
A parent will email asking why their child won't stop talking about "clipping the waveform" at dinner. That email is the entire reason you do this job. Print it. Frame it. Read it in May when your soul is a husk.
Your most "difficult" student will be the one who quietly builds the cleanest op-amp overdrive in the class and then acts like it was nothing. Keep an eye on that one. They're going somewhere. Also they still owe you three worksheets.
You're doing real work that matters, even on the days it feels like herding caffeinated raccoons through a circuits lecture. The fact that you're reading the teacher portal of a free curriculum tool at all says everything. Go get 'em.
Testing & submission (Google Classroom / Forms)
The Quizzes tab gives students module-aligned checks they can take in the app. There are five quizzes (Sensors, Sound, Distortion & Effects, Circuits & Components, and the OWN framework), each auto-graded with explanations. Students submit results in whatever way fits your room:
Option 1 — Google Classroom (simplest)
Post an assignment in your Classroom. Students finish a quiz, tap "Submit to Google Classroom," pick your class, and attach the auto-generated results summary. Their score + every answer travels with it.
Option 2 — Google Form (most automatic)
Build one Google Form. Students tap "Submit to Google Form" and it opens pre-filled with their name, quiz, and score. Submissions land in your linked Google Sheet — instant gradebook. Setup steps below.
Option 3 — Download / Copy (no Google)
Students can download a results sheet (a .txt file) or copy to clipboard and turn it in however you like — LMS upload, email, printed. Works with zero setup.
Answer keys
Every quiz auto-grades and shows the correct answer with a one-line explanation the moment a student checks their work — so the explanation becomes a teaching moment, not just a score. You can preview any quiz yourself from the Quizzes tab.
Differentiation
Quizzes are tagged by grade band. The OWN-framework quiz works for all ages; Circuits & Components is best saved for the grades 7–8 breadboard cohort. Assign selectively.
Write your own
Quiz data lives in quizzes.js in a simple, readable format. Copy a block, change the questions, and your new quiz appears automatically. No coding needed beyond careful copy-paste.
Every component, every possibility.
At the heart of every project is a Raspberry Pi — which can talk to essentially any sensor or component the maker community has built. (A Piper Computer Kit is just a Raspberry Pi in a friendly wooden shell, so everything here applies to one equally.) Below is a catalog: what's core, what's a simple add-on, and what's an advanced upgrade.
Included with the Kit — shipped in the box
Raspberry Pi 3 Model B
The microcomputer at the heart of everything. 1.2GHz quad-core ARM, 1GB RAM, 40-pin GPIO header for sensors, built-in WiFi and Bluetooth.
HC-SR04 Ultrasonic Rangefinder
Sends a pulse of high-frequency sound and times the echo. Accurate to about 2cm–400cm. The same physics bats use.
Temperature Sensor
Likely a DS18B20 or similar digital probe. Reads ambient temperature in Celsius via a single data wire.
Color Sensor
Likely a TCS34725. Uses RGB photodiodes and a built-in white LED to read the color of any surface placed in front of it.
5× 10mm LEDs
Light-emitting diodes — current passes through and they glow. Need a small resistor (~330Ω) in series to protect them.
Buzzer (Piezo)
A small speaker that vibrates a piezoelectric crystal. Active buzzers make one tone; passive buzzers play any frequency you send them.
5× Push Buttons
Momentary contact switches. Press to close the circuit; release to open. Need a pull-up or pull-down resistor for clean reads.
Switches
Toggle switches stay where you flip them, unlike push buttons. Good for "mode" controls.
Breadboards (large + small)
A grid of holes connected in rows underneath. Lets you build circuits without soldering — pull a wire out, try again.
10× Jumper Wires
Pre-made wire bridges. Some are male-male (for breadboard), some male-female (for the Pi's GPIO header). Color matters for sanity, not function.
7" Touch-Free Display
A 7-inch LCD with HDMI input and a built-in amplifier — so it can also output sound.
Lithium-Ion Battery Pack
A rechargeable USB battery. Makes the kit fully portable, which transforms what kinds of projects are possible.
Simple Add-Ons — $5–$25 each, plug-and-play
PIR Motion Sensor
Detects body heat moving across its field of view. Different from ultrasonic — it senses warm bodies specifically.
Photoresistor (LDR)
Resistance changes with light. Pennies-cheap and the easiest analog sensor to grasp intuitively.
DHT22 Humidity + Temp
A more advanced env. sensor — gives temperature AND relative humidity from one chip. Slightly slow but very accurate.
Soil Moisture Sensor
Two metal prongs measure electrical conductivity in soil. Wet soil conducts; dry soil doesn't.
Tilt / Vibration Sensor
Little metal ball that rolls between contacts when the sensor moves. Cheapest "is it moving?" sensor on Earth.
Reed Switch (Magnetic)
Closes when a magnet is near. Used in real door alarms and laptop lid sensors.
SG90 Micro Servo Motor
A motor that turns to a specific angle on command (0–180°). The basis of robot arms, gates, dispensers.
WS2812B LED Strip ("NeoPixel")
A strip of individually-addressable color LEDs. Each one can be any color independently.
SSD1306 OLED Display (0.96")
A tiny black-and-white screen, sharp as paper. Connects with 4 wires (I2C). Cheap, durable, and great for status info.
Vibration Motor
The same kind in phones — a small motor with an off-balance weight that buzzes. Quieter than a piezo.
Potentiometer (Knob)
A rotary resistor — turn the knob, change the resistance. Needs an analog-to-digital chip (MCP3008) since the Pi has no built-in ADC.
Joystick
Two potentiometers + a button in one stick. Needs an ADC chip. Same hardware as a game controller thumbstick.
Force-Sensitive Resistor (FSR)
Press harder = lower resistance. Like a single piano key with velocity sensitivity.
Capacitive Touch Sensor (TTP223)
Detects a finger touch through any non-metal surface — even paper or glass. No physical button needed.
MCP3008 ADC Chip
8-channel analog-to-digital converter. The Pi only reads digital signals; this lets you read all the cheap analog sensors.
Advanced Upgrades — for older students, science fairs, capstones
MPU-6050 Accelerometer + Gyro
Senses motion in three dimensions plus rotation. The chip inside a Wii remote.
BME280 / BME680 Environmental Sensor
Temp, humidity, barometric pressure (and gas/VOCs on the 680). Used in real weather stations.
Raspberry Pi Camera Module
A 5–12MP camera that plugs directly into a dedicated port on the Pi. Real-time video.
INMP441 I2S Microphone
A high-quality digital microphone. The "real" upgrade for any audio-input project.
RC522 RFID Reader
Reads RFID/NFC cards — the same tech as transit passes and hotel keys. Comes with sample cards and keyfobs.
MAX30100 Pulse / Pulse-Ox
Reads your heart rate and blood oxygen via your fingertip. Be thoughtful — not a medical device.
Stepper Motor (28BYJ-48)
A motor that turns in precise increments — 4096 steps per revolution. The motor inside 3D printers and CD drives.
DC Motor + L298N Driver
A continuous-rotation motor and the driver chip that lets you control speed and direction safely.
Relay Module
An electronic switch that can control real household-voltage devices. Adult supervision required if used with anything above 12V.
16×2 I2C LCD Display
A two-line text display. Old-school but extremely readable. 4-wire connection.
NRF24L01 Radio Module
A 2.4GHz radio transceiver. Two Pis can talk to each other over distance without WiFi.
GPS Module (NEO-6M)
Receives signals from satellites and computes the device's location.
Common Substitutions — if something's missing
Inevitably, a piece will go missing or break. Here's a quick guide to what you can swap in.
Use any other LED
Any 3mm/5mm/10mm LED works. Just match a 220–330Ω resistor in series. Even Christmas-tree-string LEDs work in a pinch.
Two in series or parallel
Two 220Ω in series = 440Ω. Two in parallel = 110Ω. A great teaching moment about Ohm's law.
Stripped speaker wire
Any thin solid-core wire works — even unwound from a twist-tie or a paperclip in a pinch. Insulation isn't required for short bridges.
Two wires that touch
Tap two stripped wire ends together to "press." Honestly more memorable for K–3 because it makes the concept of a switch obvious.
Use the screen's speaker
The 7" screen has a built-in amp. Route sound via 3.5mm jack or HDMI audio. Every Pi has working audio out of the box.
Pi Camera + Python
Capture a frame, average the RGB of a center pixel. Less elegant but more flexible — and a great Pi Camera intro.
Photoresistor as proximity
The closer your hand, the less light reaches the sensor. Not as accurate but works for theremin-style projects.
Cardboard + brass fasteners
Old-school. Push brass fasteners through cardboard, wire to them. Real engineers built prototypes this way in the 1950s.
Pi's CPU temperature
The Pi reports its own internal temperature. vcgencmd measure_temp. Great for understanding how laptops throttle.
Headphones split with adapter
Any 3.5mm headphone works. A "Y-splitter" lets two students listen at once — also great for partner work.
What you need to buy.
This curriculum was written for the Piper Computer Kit V4B with Sensor Explorer — a lovely all-in-one wooden Raspberry Pi kit. It's also not cheap, so here's the honest truth: you don't need it. Every project runs on a bare Raspberry Pi plus a handful of inexpensive parts, and the software lessons, quizzes, and oscilloscope run in any web browser. Pick the path that fits your budget — all the Piper instructions still apply if you own one.
A complete parts table with quantities, prices, and which module needs what lives in
SHOPPING-LIST.md in this folder. The essentials are below.
Piper Computer Kit
The polished all-in-one: a Raspberry Pi, screen, battery, and the build-it-yourself story, with sensors bundled in the Sensor Explorer add-on. The smoothest classroom experience.
Bare Pi + parts à la carte
Same projects, about a third of the price. A Raspberry Pi 4, an SD card, the three sensors, a USB mic, and an electronics starter kit. Best value for a maker on a budget.
Use what you have
Already own a Pi or some parts? Just fill the gaps. And the app, the virtual oscilloscope, and the quizzes run in any browser on any computer with zero hardware.
The essentials by category
Computer
Piper Kit or Raspberry Pi 4/5 (a 3B+ works too) + 32GB microSD + power supply. Or any computer with a browser for the software-only path.
Sensors
HC-SR04 ultrasonic (~$3), TCS34725 color (~$8), and a temperature sensor — TMP102/TMP117/DS18B20 (~$6). Bundled in the Piper Sensor Explorer; cheap individually otherwise.
Audio
A USB microphone (~$15) and headphones/speaker. For the hardware pedals (P7–P10): a Behringer UCA202 USB audio interface (~$30).
Electronics
An electronics starter kit (~$30) covers breadboards, jumper wires, LEDs, resistors, capacitors, and buttons. Add semiconductors (2N5457, 2N3904, TL072, 1N4148), pots, jacks, and 9V batteries for the breadboard pedals.
Guitar gear (P7–P10 only)
An electric guitar and amp — the school may already have them. Plus ¼-inch cables and an RCA-to-¼-inch adapter for the audio interface.
Tools & software
A multimeter (~$20) for the pedal builds. All software is free: Raspberry Pi OS, Python 3, Sonic Pi, and a browser.
Science Lab (S1–S10)
One sensor per field, mostly $5–15 I²C boards sharing the same four wires: BME280, ADXL345, QMC5883L, AS7341, MAX30102, SGP30, plus a Pi Camera, an AMG8833 thermal camera (~$35, the one big-ticket item), a GSR sensor with an MCP3008 ADC, and a pair of IR break-beams.
Body & Mind (B1–B4)
The Breathing Coach needs nothing at all. The rest reuse the Science Lab heart and skin sensors, plus a push button and an MLX90614 IR thermometer (~$10).
Space (SP1–SP5)
One RTL-SDR USB dongle kit (~$30) covers FM and aircraft. Add a home-built 137 MHz V-dipole (~$10) for weather satellites and the ISS, and a 1420 MHz low-noise amp plus a dish (~$50) for the hydrogen line.
Growing Lab (G1–G6)
Capacitive soil sensor, BH1750, DHT22, DS18B20 probe, the shared MCP3008, three relay modules, a small 5V pump, and a low-voltage (USB or 12V) grow light and heat mat (~$50–75 in all). Wall-powered lights or mats go through an enclosed GPIO-controlled outlet, never a breadboard relay.
Troubleshooting, calmly.
Things will go wrong. That's not a bug in your teaching — it's the substance of engineering. Here are the most common stumbles and honest ways to recover. Click any item to expand.
Hardware & Build Issues
Step 1: Is the power supply adequate? A Pi needs a solid 5V supply (3A for Pi 4/5). Underpowered phone chargers cause boot failures and a lightning-bolt icon on screen.
Step 2: Is the power cable seated all the way into the Pi? It should click. USB connectors can feel "in" without actually making contact.
Step 3: Is the SD card seated? Pop it out, blow on the contacts, push it back firmly. Many Pi problems are actually SD card problems.
Step 4: Look for the Pi's on-board LEDs. A red LED = power; a blinking green = it's reading the SD card. No green blink means the card isn't being read — re-seat or re-image it.
Using a Piper kit? See the Piper tab for battery-pack-specific steps.
Reseat the HDMI cable on both ends — Pi side and screen side. The HDMI is the single most common failure point.
If still black: the Pi may have booted "headless" because the screen wasn't plugged in at startup. Power-cycle with the screen connected from the beginning.
Last resort: a fresh SD card image fixes 90% of mystery problems. Have one pre-imaged spare ready for the classroom.
Polarity. LEDs are directional. The longer leg = positive (anode), shorter leg = negative (cathode). Try flipping it.
Resistor. Did you include a 220–330Ω resistor in series? Without one, LEDs can blow out instantly.
Bridge breaks. On the breadboard, the middle gap separates the two rails. A wire that looks "connected" across the gap actually isn't.
Right GPIO pin? Software uses BCM or BOARD pin numbering. If your code says pin 17 but you wired to pin 11, nothing happens.
This is normal. The sensor reads many times per second, and small surface variations cause noise.
Fix in code: take 5 readings, average them. This is called a "moving average filter" and is genuinely how real engineers handle sensor noise.
Fix in hardware: Make sure the two metal cylinders are aimed at a flat surface. Soft surfaces (carpet, clothing) absorb the pulse and give wonky readings.
Show students the noisy readings and the smoothed readings side by side — this is one of the most valuable signal-processing lessons in the whole curriculum.
White LED off? The TCS34725 has a tiny white LED that must be on for color readings (it provides the reflection light). Check if your code activated it.
Object too far? Hold the colored item within 1cm of the sensor. The sensor reads reflected light only — distance kills the signal fast.
Ambient light interference? Bright sunlight or a desk lamp overwhelms the sensor. Try cupping your hand around it as a shade.
Calibrate first. Read a known-white surface and a known-black surface; use those as the "max" and "min" for normalizing readings. This is a great math lesson about scaling.
You probably have a passive buzzer (which needs a frequency signal) but your code is treating it like an active one (which makes its own tone when given power).
Active buzzer: GPIO.output(pin, GPIO.HIGH) = beep.
Passive buzzer: needs PWM, e.g. buzzer = GPIO.PWM(pin, 440) then buzzer.start(50) for a 440Hz tone at 50% duty cycle.
The "active vs passive" distinction is one of the most useful early electronics concepts. Worth a short whole-class moment.
This is called contact bounce. The physical contacts inside the button vibrate briefly, registering as multiple presses.
Software fix: after detecting a press, sleep for 50ms before listening again. This is debouncing.
Real engineers debounce every physical input. Showing this to students helps them appreciate that "software hides hardware messiness everywhere."
The sensor sits right on top of the Pi, which generates heat. It's reading the Pi's heat as much as the room's.
Fix: extend the sensor on longer wires and place it a few inches away from the Pi. Or read just after powering on, before the Pi warms up.
This is genuinely how IoT sensors work in industry — placement matters as much as the sensor itself.
Not installed? Sonic Pi no longer comes with Raspberry Pi OS. Download the Raspberry Pi package from sonic-pi.net (check it matches your Pi OS release), then double-click to install.
Output device: Right-click the volume icon (top-right of the Pi's desktop) and verify audio is routing to the right place — HDMI for screen audio, "Analog" for headphone jack.
Click the Run button: Sonic Pi requires you press the green Run arrow. Code in the editor doesn't play until you do.
Audio server crashed: Restart Sonic Pi entirely. The internal audio engine occasionally locks up.
Volume: Powered speakers and monitor-built-in amplifiers have their own volume knobs — students sometimes turn them all the way down and forget. (On a Piper, that's the screen's built-in amplifier.)
On current Raspberry Pi OS the first user you create is already in the gpio group, so scripts should run without sudo. If not, add yourself: sudo usermod -aG gpio $USER, then log out and back in.
Avoid sudo python3 … if you set up the pathways-env environment below — sudo runs the system Python, which can’t see the libraries you installed there.
Worth mentioning to students that permissions exist for safety — random programs can't just take control of your hardware.
The library isn't installed. Current Raspberry Pi OS (Bookworm and later) blocks system-wide pip with an “externally-managed-environment” error, so set up one shared environment for Pathways once:
sudo apt update && sudo apt install -y python3-venv python3-lgpio python3-gpiozero
python3 -m venv --system-site-packages ~/pathways-env
source ~/pathways-env/bin/activate # once per new terminal
pip install rpi-lgpio # lets "import RPi.GPIO" run unchanged, incl. on a Pi 5With it activated, every pip3 install X in the modules works as written. In Thonny, pick the same interpreter under Tools → Options → Interpreter (~/pathways-env/bin/python3).
Common ones for these projects: rpi-lgpio (provides RPi.GPIO), adafruit-circuitpython-tcs34725, numpy, sounddevice, scipy.
Pre-install all of these on each kit's SD card before the school year. Saves a lot of mid-class hair-pulling.
The original RPi.GPIO library can’t reach the Pi 5’s GPIO chip. Install the drop-in replacement rpi-lgpio inside your pathways-env environment (see “ImportError” above): pip install rpi-lgpio. The module code stays exactly the same.
If the system python3-rpi.gpio package is also installed, remove it (sudo apt remove python3-rpi.gpio) — the two can’t share one Python environment.
Non-judgmentally: nothing is wrong with your wiring. The hardware changed under the software; the fix is one install.
Always have a freshly-imaged backup SD card per classroom. Two if you can — one in use, one ready to swap.
To re-image: download Raspberry Pi Imager on any computer (free), select Raspberry Pi OS, write it to the card, swap, boot, then re-install your project libraries. (Using a Piper? Grab its SD image from playpiper.com support instead — see the Piper tab.)
Teach this process to one or two students per class. They become your "tech aides" and it's genuinely empowering for them.
This is the moment for DBT skills, not more code. Three steps:
1. Name it. "It looks like this is really frustrating." Just naming the emotion lowers its grip.
2. Step back. Have the student stand up, walk to the window, take three breaths. Two minutes. The kit will wait.
3. Smaller chunk. When they return, find one tiny piece that works (does the LED still light? does the sensor read anything?). Build from there.
Sometimes the deepest learning isn't the project — it's that frustration is workable. This is the heart of DBT in the classroom.
The Piper Computer Kit.
Pathways is built for the bare-Raspberry-Pi, DIY path — but it began life around the Piper Computer Kit V4B with Sensor Explorer, and every module runs on one beautifully. A Piper is, at heart, a Raspberry Pi 3 in a friendly wooden shell with a screen, battery, and sensors bundled in. If you own one (or are deciding whether to buy one), everything specific to it lives here. Nothing in this tab is required — the other 50 modules work identically on any Pi.
The Piper build arc (Weeks 1–5 alternative)
If your class uses Piper kits, replace the DIY "Set Up & Source / First Light" weeks in the Teacher Portal year arc with this sequence. Everything afterward — the Pathways modules, Sonic Pi, the Science Lab — is identical.
The Build
Assemble the Piper itself, following the included blueprint. Students learn screws, wires, and the satisfaction of finishing something physical — no code yet.
StoryMode
Run through Piper's built-in Minecraft missions. Circuits taught implicitly through play — build a button, place a block, level up.
PiperCode Basics
Piper's Blockly drag-and-drop environment: loops, conditionals, events. A gentle bridge before moving to Python/Thonny for the Pathways modules.
The original four-phase Piper arc
Start with the Build
Assemble the Piper, following the blueprint. Screws, wires, and the satisfaction of finishing something physical.
Play in StoryMode
Built-in Minecraft missions teach circuitry without it feeling like a lesson.
Move into Pathways
Every module in this app runs on the Piper exactly as written.
End in Creative Mode
Students invent something nobody told them to build. The whole arc is a runway to that moment.
Piper-specific troubleshooting
Step 1: Is the battery charged? Plug it into the wall and look for the LED on the battery pack. If no LED, leave it on the charger 30 minutes before assuming it's broken.
Step 2: Try the AC adapter directly to bypass the battery. If it works that way, the battery is the issue.
Step 3: Re-seat the power cable into the Pi (it should click) and re-seat the SD card. Then see the general power steps in Troubleshooting.
The Piper's screen has a built-in amplifier with its own volume — students often turn it all the way down and forget. Check that first.
Then verify audio routing on the Pi desktop (HDMI vs. Analog) and that Sonic Pi's Run button was pressed. See the general audio steps in Troubleshooting.
Download Raspberry Pi Imager (free) on any computer, then download Piper's official SD card image from playpiper.com support. Write the image, swap the card, boot.
Keep a freshly-imaged spare per classroom. Teach the process to one or two students — they become your tech aides.
Piper Computer Kit and PiperCode are trademarks of Piper Learning, Inc. Pathways is an independent curriculum, not officially affiliated with Piper Learning, Inc., and references the Piper kit for educational interoperability only.
Mindfulness is the secret circuit.
The hardware teaches engineering. Mindfulness teaches the relationship students have with engineering — with their mistakes, their frustration, their curiosity. DBT (Dialectical Behavior Therapy) mindfulness skills, originally developed for emotional regulation, translate beautifully into the maker space. Every Pathways module includes a specific DBT anchor.
The "What" Skills
What we do when we practice mindfulness. Three modes — only one at a time.
Observe
Just notice. Don't change anything, don't judge it, don't explain it. Just see what's happening.
Describe
Put words to what you observed. Use only facts — no opinions, no judgments, no "shoulds."
Participate
Throw yourself into the moment. Stop watching yourself do the thing — be the thing.
The "How" Skills
How we observe, describe, and participate. The quality of our attention.
Non-judgmentally
Drop the labels of "good" and "bad," "right" and "wrong." Things just are. Errors are information, not failures.
One-mindfully
One thing at a time. Wire one circuit, then read the code, then run it. Multitasking with electronics destroys focus.
Effectively
Do what works. Not what feels right, not what should work — what actually solves the problem in front of you.
States of Mind
DBT names three states. Recognizing which one you're in is half the work.
The Logic Brain
Facts, plans, analysis. Useful for reading documentation and tracing a bug. Cold and capable.
The Feeling Brain
Pure feeling, no facts. Useful for inspiration and connection. Not useful for debugging.
The Integration
Where logic and feeling meet. You acknowledge the frustration AND you check the wiring. This is the goal.
A Sample Mindful Opening (3 minutes)
Use this as your "bell" at the start of every Piper session. It works for K through 8 with minor adjustments. Adapt the wording to your voice.
- "Sit with both feet flat on the floor." (Grounds the body.)
- "Take one slow breath in. Hold for one second. Slow breath out." (Repeat 3×.)
- "Look at your setup. Just observe it. What do you notice about the parts in front of you? What sound does the room make right now?" (30 seconds of pure observation.)
- "Today we're working on [project]. If you get stuck — and you might — that's not a problem. That's the project."
- "One more breath. Hands ready. Let's begin."
A Sample Mindful Close (1 minute)
- "Put your hands flat on the desk."
- "Without judging — just noticing — finish this sentence in your head: 'One thing I noticed today was ___.'"
- "One slow breath."
- "Thank you for being here. We're done."
Optional: have students write that one noticed thing in their Engineering Journal. Over a semester, these reflections become a striking record of growth.