Updated document · High school professors

Run the lab like a studio, not a lecture.

Timing, stations, safety, mixed-ability tasks, and a 16-period sequence mapped onto the original Digital Challenge Arduino + Processing curriculum.

Grades 9–13Pairs of 2–3Informatics · Physics · TechnologyPrintable

What changed from the source PDF

The original document is an excellent student tutorial. This edition keeps its exercises, photographs, DigComp alignment, and hackathon scoring — then adds the missing teacher operating system.

  • Pacing for 45-minute and 90-minute high-school periods
  • A 16-period sequence that fits a semester club or a STEM elective
  • Station roles, kit quantities for 24 students, and a first-day protocol
  • Safety briefings for USB power, relays, pumps, and servos
  • Formative checks and a shared rubric you can use on every project
  • Skip the Processing menu encyclopedia; keep only what a class needs
Classroom workbench with Arduino kit
Photograph from the Digital Challenge document. Put one kit per station, not per student.
16 periods

Semester map

Each period is 45 minutes. Double periods cover a full project plus gallery walk.

P1–2

Arduino intro

Board anatomy, Blink on pin 13, external LED, first debug ritual.

P3–4

Processing intro

Window, shapes, serialEvent, CSV parse, send 1/0 back to the board.

P5–6

Project 1 DHT11

Library install, two-value serial, dual bars, heat alarm.

P7–8

Project 2 LDR

Voltage divider, analogRead, map(), night-light extension.

P9–10

Project 4 Ohm meter

Ohm’s law as a measurement tool. Physics crossover day.

P11–13

Project 3 Sonar

Distance, servo, then radar. The showcase project.

P14–16

Project 5 Irrigation

Threshold logic, relay safety, automatic watering demo.

+2 days

Hackathon

Scored challenges. Use as exam, open day, or Erasmus mobility.

45-minute lesson skeleton

Use this on every project day. Students learn the ritual; you stop reinventing the clock.

MinutesMoveWhat you doWhat they do
0–5Safety + goalOne physical demo on the projector. State the exit ticket.Kits closed. Listen. Assign roles.
5–12Theory punchOne diagram, one formula, one common fail.Copy the wiring table into the log.
12–32Build + codeCirculate. Do not debug for them — ask which layer failed.Simulate or wire, upload, then Processing.
32–40LevelsUnlock Basic / Intermediate / Advanced from the project page.Finishers extend; stuck pairs get a checkpoint sketch.
40–45ExitPhotograph working stations. Power down. Count jumpers.Write: what broke, what they changed, what they would add.

Station kit · class of 24

Eight stations of three. Shared laptop per station is enough.

ItemPer stationClass + spares
Arduino Uno + USB110
Breadboard + jumper pack110
LED + 220Ω220
DHT11 + 10kΩ110
LDR + 10kΩ110
HC-SR04 + SG90 + holder110
Known 1kΩ + unknown mix1 set10 + bag
Capacitive soil + relay + pump14–8 demo kits
Laptop with IDE + Processing18

Roles that actually work

WirerBuilds from the photograph. Speaks pin names out loud before power.
CoderTypes, uploads, keeps Serial Monitor closed when Processing runs.
LoggerPhotographs the board, records values, writes the exit ticket.

Shared rubric

Score every project on the same five dimensions. 20 points. Fast to mark during a demo.

Dimension134
WiringGuesswork, no GND checkMatches diagram, labeledClean routing, can explain every jumper
CodeCopied, does not compileRuns, names are readableComments, constants, no magic numbers
Serial + UINo data / frozen sketchValues updateParsed safely, mapped, labeled units
Debug process“It doesn’t work”Changed one thing at a timeCan say if the fault is power, code, or port
ExplanationCannot teach a peerDescribes the data pathConnects to physics / a real job
Differentiation

One room, four speeds.

Basic · everyoneWorking circuit, Serial Monitor values, one Processing number on screen.
Intermediate · mostmap() bar, units, one threshold color change.
Advanced · finishersCSV of two values, buttons that write back to Arduino, alarm logic.
Challenge · showcaseCSV log, scrolling graph, p5.js port, or a second sensor on the same board.

First-day protocol

  1. Install Arduino IDE 2.x and Processing 4.x on every station laptop before the period starts.
  2. CH340 / official Uno drivers tested. Print a COM-port cheat sheet.
  3. Board → Arduino Uno. Students screenshot Tools → Port.
  4. Upload Blink. Celebrate the onboard LED. Then, and only then, breadboards.
  5. Teach the golden rule: schematic → simulation → wiring → upload → test.
External LED wired to Arduino pin 8
Exercise 2 from the source document: pin 8 → 220Ω → LED anode; cathode to GND.