Skip to main content

Hands-on

Weekend projects

Written instructions you can follow at home or in a makerspace—without needing a full lab manual. Each project includes a student path (with clear adult-help moments) and a deeper station build for schools, families, and learning facilities.

Jump to: Student guide · Educator & facility guide

Featured project

Raspberry Pi display station

A small computer with its own screen—use it for coding practice, a class dashboard, digital signage, or robotics demos. Two guides: a supervised weekend build for students, and a full deployment for adults running a space.

Raspberry Pi 4 or 5HDMI or touchscreenRaspberry Pi OSOptional kiosk mode

For students (middle & high school)

Build a Raspberry Pi with a screen (supervised)

You will set up a Raspberry Pi—a credit-card-sized computer—and connect a monitor or touchscreen so you can use it like a tiny desktop. This is a real electronics project: go slowly, keep liquids away, and ask an adult whenever you see the stop icon moments below.

Adult involvement

An adult should flash the microSD card (or supervise closely), approve any purchases, and handle ribbon cables or GPIO if you use a special display that needs them.

At a glance

  • Time: One weekend afternoon for a simple HDMI setup; more if you troubleshoot Wi-Fi or drivers.
  • Best first build: Raspberry Pi 5 (or Pi 4) + official power supply + microSD + HDMI monitor you already have + USB keyboard and mouse.
  • Goal: Boot into Raspberry Pi OS, open the browser, and maybe show a full-screen page you picked with an adult.

What you need

  1. Raspberry Pi board (Pi 5 recommended; Pi 4 works for lighter tasks).
  2. Official Raspberry Pi USB-C power supply for your model—cheap phone chargers often cause random reboots.
  3. microSD card (64 GB is a comfortable size) and a way to plug it into a laptop or desktop for imaging.
  4. HDMI cable that fits your Pi (micro-HDMI to HDMI for Pi 4/5).
  5. A monitor or TV with HDMI in, plus keyboard and mouse (USB or wireless with a USB dongle).
  6. Optional: a case with a fan or heatsink so the Pi stays cool when the room is warm.

Safety and stop points

Stop and get an adult

If anything smells hot, sparks, or the board gets very hot very fast—unplug power and stop.

  • Do not touch the metal pins on the Pi while it is powered on.
  • Keep drinks and snacks away from the work area.
  • Never plug or unplug ribbon cables (flat flex) while power is on—that path is for advanced builds with an adult.

Steps (HDMI monitor path)

  1. With power unplugged, fit the heatsink or fan case onto the Pi if you have one.
  2. Ask an adult to image the card: on another computer install Raspberry Pi Imager, choose your Pi model, pick Raspberry Pi OS (64-bit) Desktop, set username/password/Wi-Fi in the advanced options, then write to the microSD card.
  3. Insert the microSD into the Pi (label side usually faces away from the board—check your board’s diagram).
  4. Connect HDMI from the Pi to the monitor. On Pi 4/5, use the HDMI port closest to the power USB-C if only one screen is attached.
  5. Plug in keyboard and mouse.
  6. Turn the monitor on first, then plug in the Pi’s power supply.
  7. When the desktop appears, connect to Wi-Fi if needed and run system updates from the menu when an adult says it is OK (updates can take a while).
  8. Optional stretch: with an adult, open Chromium and try a simple full-screen web page for a “kiosk” feel—your adult can help set startup behavior if you want that every boot.

If something goes wrong

  • Black screen: Confirm the monitor input is set to the right HDMI port; try the other micro-HDMI port on the Pi; re-seat the SD card with power off.
  • Lightning bolt icon: Undervoltage—switch to the official power supply and a short, good-quality cable.
  • Wi-Fi drops: Move closer to the router; check that the country code was set correctly in Imager.

What to try next

When your Pi is stable, you can explore Python, Scratch, GPIO LEDs (with a resistor and adult help), or attach a camera module for simple vision projects. For a full station plan—multiple devices, kiosks, and classroom rules—ask a teacher or parent to read the educator guide on this same page.

For educators, parents, and learning facilities

Raspberry Pi display station — full deployment guide

This track turns the same hardware into a repeatable “station”: imaged SDs, sensible defaults, kiosk-style browsing where appropriate, and a recovery path anyone on staff can execute. It assumes you can run Raspberry Pi Imager and basic Linux updates, but not that every reader is a Linux specialist.

At a glance — recommended default

Recommended stack

Raspberry Pi 5, 8 GB RAM, official 27 W USB-C power supply, active cooler, 64–128 GB A2-rated microSD, Raspberry Pi OS (64-bit) Desktop, and either a 7–10″ HDMI touchscreen (flexible labs) or the official Raspberry Pi Touch Display 2 on DSI (compact appliance / kiosk).

Treat each unit as a small edge computer: predictable hostname, labeled inventory, one “golden” SD image you clone, and a spare SD + spare PSU per handful of deployed units.

Trade-off: **DSI** gives a tidy integrated panel; **HDMI** is faster to swap, debug, and replace in busy rooms.

System picture

  • Compute: Raspberry Pi OS runs Chromium, Python, GPIO tools, cameras, and local services.
  • Display: HDMI is universal; DSI uses the flat-flex ribbon to the dedicated display port (touch may be DSI and/or USB depending on hardware).
  • Appliance layer: A common pattern is a small local web app (even a static page) plus Chromium opening that URL full screen so non-Linux staff can change what the station shows.

Build decisions (summary)

  • Power: Use the official PSU for your Pi model. Under-voltage causes flaky USB, dropped Wi-Fi, and corrupted SD cards.
  • Cooling: Active cooling or a fan case for Pi 5 is strongly recommended for enclosed mounts and warm rooms.
  • Storage: Prefer branded A2 cards; keep two pre-imaged spares per classroom or cart.
  • Accounts: Separate admin from everyday use; students get a locked-down account for kiosk stations.

Bill of materials and budget bands

**Reuse-monitor build:** Lowest cost—Pi + PSU + SD + existing HDMI display + input devices.

**Portable lab:** Pi 5 + small HDMI touchscreen + active cooling—good for rolling carts and workshops.

**Appliance / wall mount:** Pi 5 + official DSI touchscreen + enclosure—cleanest cable story, slower to swap.

**Robotics / AI demo add-ons:** Camera module, powered USB hub, speaker/mic, sensors—budget and cable plan per station.

Physical assembly — HDMI display

  1. Install cooler or fan case; insert the already-imaged microSD.
  2. Connect micro-HDMI to the display (prefer the primary HDMI port nearest USB-C on Pi 4/5 for single-display setups).
  3. If the panel is touch-capable over USB, connect its touch cable.
  4. Attach keyboard and mouse; power the display first, then the Pi.
  5. Verify boot, touch (if any), Wi-Fi, and correct screen orientation.

Physical assembly — DSI Touch Display 2

GPIO power wiring

Incorrect 5 V / GND wiring for display power can damage hardware. Double-check pinout against current official documentation before applying power.

  1. Power off completely. Never seat a DSI ribbon while powered.
  2. Use the correct flat-flex for your Pi generation (Pi 5 vs Pi 4 routing differs).
  3. Open the retaining clip, insert the ribbon with contacts oriented as documented, close the clip—both on the panel and on the Pi’s DSI connector.
  4. Connect the panel’s power leads only if your kit requires GPIO 5 V (follow official guides).
  5. Mechanically mount the Pi to the display without pinching the ribbon; insert SD; apply power.
  6. Allow up to a minute on first boot for display init; set rotation in Screen Configuration if the enclosure is landscape.

Operating system imaging

  1. Install Raspberry Pi Imager on a staff laptop.
  2. Select hardware model → Raspberry Pi OS (64-bit) Desktop → target microSD.
  3. Open OS customization: hostname, user, password, Wi-Fi, locale, SSH as policy requires.
  4. Write, verify if offered, then eject safely.
  5. First boot: `sudo apt update && sudo apt full-upgrade -y` then reboot; install baseline tools you standardize (`git`, `curl`, `htop`, Chromium, `unclutter`, etc.).

Display configuration

  • Use Preferences → Screen Configuration for resolution, primary output, and rotation.
  • For kiosks, disable screen blanking and test the on-screen keyboard if the UI is touch-only.
  • Quick health checks: `xrandr`, `hostname -I`, `vcgencmd measure_temp`, `vcgencmd get_throttled` (interpret throttled flags against official docs).

Kiosk / dashboard mode (pattern)

Serve a simple local page or app on `localhost`, then launch Chromium with `--kiosk` pointed at that URL. Newer Raspberry Pi OS versions differ in compositor (Wayland/labwc vs older X11 setups)—validate autostart on the exact image you deploy, after a cold boot.

  • Example launch flags: `chromium-browser --kiosk --noerrdialogs --disable-infobars --disable-session-crashed-bubble http://localhost:3000` (adjust port/path).
  • Wrap your Node or Python server with systemd (`Restart=always`, correct `User=` and `WorkingDirectory=`), enable the unit, and confirm `systemctl status` after reboot.

Education and robotics patterns

  • Bounded kiosk: One URL per class period—no general browsing.
  • Sensor dashboard: Local charts for temp, distance, air quality, etc.
  • Robot command deck: Video feed + low-latency controls with clear safety boundaries.
  • AI prompt station: Structured prompts only; pair with school acceptable-use policies.

Safety, security, and operations

  • Physical: enclosed cases, strain relief on cables, labeled PSUs, no hot-plugging DSI/GPIO.
  • Software: no default passwords on cloned images; SSH keys for admins where feasible; URL allow lists for kiosks; patch on a schedule, not mid-class ad hoc.
  • Inventory: asset tag each Pi and SD; spreadsheet with hostname, MAC, display type, image version, room assignment.
  • Spares: keep one spare PSU and one spare imaged SD per 5–8 active units; train staff on reboot → SD swap → escalate.

Reusable checklist

  1. Pre-build: pick HDMI vs DSI; flash and customize OS; unique hostname/password; label hardware.
  2. Build: install cooling/case; connect display/touch/input; run updates; set resolution, blanking, Wi-Fi, SSH.
  3. Deploy: start local app service; enable kiosk autostart; two cold-boot tests; document recovery steps.

Troubleshooting

SymptomLikely causeFix
No displayWrong HDMI input/port, loose cable, display power, bad imageUse primary HDMI port; power display first; re-seat cables; re-flash SD.
Touch deadMissing USB touch cable (HDMI touch) or bad DSI seatingAttach USB touch; power off and re-seat DSI ribbon.
Undervoltage iconWeak PSU or poor cableOfficial supply; shorter cable; reduce USB load or add powered hub.
Thermal throttlingNo airflow / no fan / enclosed caseAdd active cooling; reduce heavy web GL/video; improve venting.
Kiosk fails after updatesAutostart path differs under new compositorRe-test autostart recipe on target OS; confirm manual Chromium launch works.
Wrong rotationPortrait-native panel or rotated mountAdjust in Screen Configuration; set persistent mode for that display.
Browser instabilityRAM pressure, power, or SD wearPrefer 8 GB Pi 5 for heavy pages; verify power; replace suspect SD cards.

Display stacks and kiosk autostart evolve with Raspberry Pi OS. Always validate kiosk behavior on the exact image version you ship, including after a full power cycle.

← Back to the kit planner