Build a fixed receiver with a Raspberry Pi.

Layer400's Raspberry Pi receiver is in controlled early access. The signed public image, public package repository and automatic updater are not released. Use only the exact pilot archive and checksum supplied directly by Layer400.

• The Pi boots without an undervoltage warning.
• Security updates are installed and the system clock reports synchronised UTC.
• Ethernet, or a separate interface, provides the default Internet route.
• The dedicated USB Wi-Fi adapter is attached but not carrying Internet traffic.
• You have physical access to disconnect power if a check fails.

1. 01
   Protect your Layer400 account

   Verify the email address, use a unique password and add authenticator-app two-factor security.

2. 02
   Open the receiver area

   Sign in at Layer400, choose Receivers and create one fixed Wi-Fi station.

3. 03
   Name the site privately

   Use a recognisable private label rather than a street address. Enter the real antenna position and an honest accuracy estimate.

4. 04
   Check the station details

   A valid fixed station activates immediately. It is marked online only after its receiver sends accepted data.

The public Pi package is not released yet. During managed access, Layer400 supplies the archive and its exact 64-character SHA-256 digest through a separate authenticated handoff. A checksum file delivered beside an archive is not, by itself, proof that the archive is genuine.

sha256sum layer400-receiver-<release>.tar.gz

List the radios before changing an interface. This command omits MAC addresses and stable hardware serials.

sudo -u layer400-feeder \
  /opt/layer400/feeder/venv/bin/layer400-feeder radios

• The selected adapter is a separate USB device.
• The driver advertises monitor mode.
• The adapter does not own the default route.
• The configured channel is legal in the receiver's regulatory domain.

Once the station is active, open its receiver card, choose the manual or Raspberry Pi handoff, and issue a fresh claim. In the Windows-first download screen, expand Manual receiver details to reveal the one-use claim. The plaintext claim is shown once, lasts 15 minutes and can be redeemed once.

sudo layer400-receiver-setup --channel 6

The assistant selects a suitable dedicated adapter when exactly one is present, asks for the fixed antenna position, creates an Ed25519 key locally, accepts the claim at a hidden prompt and runs diagnosis. It leaves both services disabled.

Start the services only after setup passes and Layer400 confirms that the station and ingest route may be activated.

sudo systemctl enable --now layer400-radio layer400-feeder
sudo systemctl status layer400-radio --no-pager
sudo systemctl status layer400-feeder --no-pager
sudo -u layer400-feeder \
  /opt/layer400/feeder/venv/bin/layer400-feeder \
  --config /etc/layer400/feeder.toml status

1. 01
   Check capture health

   The dedicated radio and bounded decoder must be running.

2. 02
   Check the heartbeat

   The enrolled device must reach the gateway with synchronised time.

3. 03
   Use your own compatible aircraft

   Power and fly it only in a lawful, controlled test at the commissioned site.

4. 04
   Wait for accepted evidence

   A live contributor status requires a real compatible broadcast and an acknowledged signed batch.

Check persistent health

sudo -u layer400-feeder \
  /opt/layer400/feeder/venv/bin/layer400-feeder \
  --config /etc/layer400/feeder.toml diagnose

sudo layer400-support-bundle

The support bundle stays local until you choose to share it. It excludes the account password, claim, private key, exact coordinates, spool and raw RF records. Review it first.

Pause safely

sudo systemctl disable --now layer400-feeder.service layer400-radio.service

• Stop the receiver before moving the antenna or changing radio hardware.
• Recommission a materially changed location.
• Revoke and re-enrol after changing the authorised radio set.
• Revoke the receiver before selling, reassigning or erasing the Pi.
• Never infer airspace safety from an empty map.