Use the guided Receiver app
For a dedicated Windows computer with Npcap and a separately connected ALFA AWUS036ACM. The app links a station and proves the capture path before it can upload.
Download Windows receiverA Layer400 receiver listens for compatible broadcast Remote ID nearby, then sends signed observations to the network. Choose the path that matches the computer you already have.
Every route ends with the same account, private station record, device-held key and contributor view. Your Layer400 password never belongs on a receiver.
For a dedicated Windows computer with Npcap and a separately connected ALFA AWUS036ACM. The app links a station and proves the capture path before it can upload.
Download Windows receiverUse a current 64-bit Raspberry Pi OS installation, Ethernet for the uplink and one dedicated monitor-mode USB Wi-Fi radio. Begin indoors on a desk.
Read the Pi guideProtect the ADS-B services already running. Layer400 needs its own Wi-Fi adapter and must never take over the interface or SDR used by your existing feeder.
Check coexistenceProve the complete receiver indoors first. Outdoor mounting adds weather, power, condensation, surge and work-at-height risks that the radio range alone cannot justify.
Plan the outdoor buildLayer400 separates the person, site and receiver so one password compromise does not become a fleet compromise.
Create and protect the contributor account in the browser.
Layer400 assigns the station record. Exact receiver coordinates are not shown publicly.
The device creates its own key and uses a single 15-minute claim. It never stores your password.
A real accepted observation, not registration alone, confirms that the station is contributing.
The first Layer400 receiver profile covers standards-based Wi-Fi Beacon Remote ID on one configured channel. It does not detect proprietary links, Bluetooth, Wi-Fi NAN or every possible channel. A quiet map is not proof of quiet airspace.