Repository navigation
Home
A Raspberry Pi that listens to the aircraft overhead and shows them on a tablet or a TV as a dot-matrix wall or an airport split-flap board. It can also feed what it hears to ADSB Exchange, FlightAware, Flightradar24 and Plane Finder, and post the aircraft crossing a radius to Bluesky.
Current version: 1.2.2 (15 November 2026: lot 2 of the Roadmap, the emergency squawk banner on the wall, the choice of the network that does MLAT, the receiver alert in the Telegram chat; all off or as before by default. 1.1, 14 November 2026: the first release after 1.0, lots 0 and 1 of the Roadmap, published before it ran on the reference Pi; Project status says what the Pi has shown since. 1.0.0, the same day: the owner closed the release candidate, fourteen days into its last month hands-off, the fresh install on a blank card redone. What is not proven on hardware stays said in Project status; features come again from 1.1, in lots: Roadmap).
Installation, the menus and every setting are in the README. This wiki does not repeat them. What it holds is the three things a README is a poor place for: where the project is going, what has really been proven, and how the software works inside.
- Roadmap — what is being worked on now, what comes next, and what will never be built.
- Project status — what runs on real hardware today, what is only unit-tested, and the field log.
- Architecture — the processes, the ports, the files, and who writes what.
-
Configuration reference — every setting in
config.env. -
Command reference — the whole
zenithboardcommand, with examples. - The wall — the dot grid, the boxes, the two looks, the per-tablet links.
- When a provider changes something — what happens when FlightAware, ADSB Exchange, Flightradar24 or Plane Finder move a file or change a key, and what to do.
- Routes, photos and data — the outside services, the caches, and what happens when they are down.
- Reliability and diagnostics — the watchdogs, the health screen, and how to read a bad night.
- Gain tuning — getting the dongle's gain right.
- Hardware — which Pi, measured: a 1 GB Pi 3B runs everything. What moving the card to a bigger Pi changes, and why it is rarely worth it.
- Code tour — a map of the modules and the systemd units.
- Testing — the test suite and the two patterns it is built on.
- Social sharing — the aircraft worth a post, on Bluesky, as a picture of the wall: dot-matrix with a map, split-flap with a map, or dot-matrix with the track in dots; off by default.
- Telegram — text messages to your own chat or group (0.99.6): the aircraft crossing the sharing radius, and the emergency squawks anywhere in range, never posted to Bluesky; off by default.
- Statistics — messages per hour, the farthest aircraft, aircraft per day; off by default.
- Translation plan — the console, the pages and the posts in 22 languages, and your own post templates with tags. French is out (0.47.0).
- Translating — the review sheets: correct your language beside the English, no account needed.
-
The menu — every screen of
sudo zenithboard menu, by what you want to do, starting with Start here. - Moving to a new card — your ZenithBoard on another card, step by step, with WinSCP from Windows.
- Fresh install — from a blank SD card to a finished ZenithBoard, step by step, ending in the web console.
- Backup and restore — one file to move to a new card: settings, statistics, graphs, logs, the networks' identities.
- Web console — the settings from a browser or a phone on your home network, a phone signed in by QR code; a test, off by default.
- Release process — versions, changelog, and how a change reaches a Pi.
- Contributing — how to propose a change, and the house style.
- Security — what is exposed, what is checked, what is trusted.
Direction
Getting started
How it works
- Architecture
- Configuration reference
- Command reference
- The wall
- Statistics
- Social sharing
- Telegram
- Web console
Running it
Working on it