Enlarge ⤢Simple starting pointALFA AWUS036ACS
~$25Compact dual-band adapter with one RP-SMA female antenna port.
View product ↗Outdoor antenna build
~$108
| Component | Part & product link | Budget |
|---|---|---|
| Raspberry Pi |  Enlarge ⤢Raspberry Pi 4 Model B · 2GB ↗Already have a compatible Pi 4 or Pi 5? Reuse it. | $55 |
| Wi-Fi adapter | Enlarge ⤢ ALFA AWUS036ACS ↗Dual-band 2.4 / 5 GHz. More adapter choices below. | $25 |
Choose one Wi-Fi adapter.Start with Wi-Fi for drone Remote ID. We recommend 2.4 and 5 GHz: drones can broadcast on either band, so a 2.4 GHz-only adapter can miss 5 GHz transmissions. Enlarge ⤢Simple starting point Enlarge ⤢Another dual-band optionPanda PAU0B / AC600~$25–$60MT7610U, with a detachable antenna. Check the connector on your exact revision. View product ↗ Enlarge ⤢Two antenna connectionsALFA AWUS036ACM~$40–$60MT7612U with two RP-SMA female ports. Both antenna chains listen on the same channel. View product ↗Cudy AC1300Already using a compatible Cudy? Keep it. AC1300 covers different models and revisions; the Cudy connector is unconfirmed, so match your actual socket before buying a cable. Compare Cudy models ↗Layer400’s Raspberry Pi software is designed for a broad range of monitor-mode-capable Wi-Fi adapters. The Linux driver, firmware and available channels still need to work on your Pi. These are recommended choices, not an exhaustive list. Why the ACM has two antenna portsIts two receive chains can expose separate signal-strength readings. Our live hardware capture confirmed this on both bands. That creates useful potential for comparing antennas and experimenting with directional panels. Current Layer400 capture does not retain those separate readings or provide direction finding. Both ports share one tuned channel; they are not two independently tuned radios. Future comparison or bearing features need software work and antenna calibration. Our tested ACM also retuned slowly, so it is better suited to fixed-channel or slower scanning experiments than rapid channel sweeping. | ||
| Outdoor antenna |  Enlarge ⤢Dual-band outdoor omni · 2.4 / 5.8 GHz ↗N-male antenna connection. Use an N-female cable end. | $20 |
Antenna choicesEnlarge ⤢Dual-band Wi-Fi omni · N male~$20Outdoor dual-band Wi-Fi antenna. Its N-male base needs an N-female pigtail. Listing advertises 10 dBi; actual reception depends on placement. View Wi-Fi antenna ↗Already have an N-female Wi-Fi antenna?Keep a compatible 50 Ω, 2.4 / 5 GHz outdoor antenna. Change the pigtail’s antenna end to N male; the dongle end still needs to match its SMA or RP-SMA socket. Check connector ends →1090 MHz ADS-B antenna · optional~$15–$30Separate aircraft antenna, for an RTL-SDR receiver. This does not replace the dual-band Wi-Fi antenna. View aircraft antenna ↗ | ||
| Antenna cable |  Enlarge ⤢20 cm RG402 · N female → RP-SMA male ↗Select N female to RP-SMA male, 20 cm. Matches the ALFA ACS/ACM and antenna above; RP-SMA male has a centre socket, not a pin. | $8 |
| Estimated listed parts | ~$108 | |
Approximate parts budget; currency follows your browser setting unless you choose another. Assumes you already have a working Pi power/storage arrangement. Mounting, weatherproofing, tax, shipping and optional extras are additional.
03 / OPTIONAL BLUETOOTH
Add BLE reception when you want it.
Bluetooth Remote ID is a separate reception path. You can start with Wi-Fi and add a BLE controller later.
Enlarge ⤢Optional · firmware required
April Brother USB dongle nRF52840
~$16The hardware used in our Pi 4 test setup, with an external antenna. Our unit runs test HCI firmware; the retail sniffer/bootloader firmware is not a plug-and-play Layer400 controller.
View dongle ↗Confirm compatible HCI firmware before buying. Other Linux BlueZ HCI LE controllers may work; actual scan capabilities matter more than the Bluetooth version on the box.
04 / OPTIONAL WIRED CONNECTION
One cable for data. PoE adds power.
We recommend Ethernet for a permanent receiver. Add a compatible PoE HAT to power the Pi over the same cable. Ordinary wired Ethernet does not need PoE.
HAT and Ethernet shop links follow your browser region; change it here if needed. Other parts use worldwide listings or manufacturer/local-reseller pages. Currency is a separate preference.
Enlarge ⤢Ethernet cable
~$5–$15Cat5e or Cat6, sized for your route. Choose solid-copper, outdoor-rated cable for exposed runs. An injector also needs a short router-to-injector patch lead.
Ethernet · Find a local Raspberry Pi reseller ↗
Enlarge ⤢Pi 5: Waveshare PoE HAT (H)
~$30–$45A neat, low-profile option that fits the official Pi 5 case and works with its Active Cooler. Isolated power supply, rated up to 5V / 5A. Use an 802.3at PoE+ source.
View HAT · Waveshare · worldwide ↗Check stock: UK and US listings were awaiting stock at review. This is a manufacturer-compatible option, not a Layer400-tested HAT.
Pi 4 and Pi 3B+: use the official PoE+ HAT · local resellers ↗ (~$20–$30). The Pi 5 HAT does not fit Pi 4.
Enlarge ⤢30W PoE+ injector
~$25Only needed for PoE power if you don’t have a suitable PoE+ switch. The Raspberry Pi injector supports 802.3af/at and Gigabit Ethernet. Add a local IEC mains lead.
View injector & regional sellers ↗PoE+ switch → Ethernet → HAT + Pi
Or: router → injector → Ethernet → HAT + Pi
Enlarge ⤢Optional · aircraft reception
RTL-SDR Blog V3
~$35–$40Add aircraft reception with a separate 1090 MHz antenna. RTL-SDR is not required for Wi-Fi or Bluetooth drone Remote ID.
View RTL-SDR products ↗SMA, RP-SMA and N-type: match the ends
The cable listing offers several connector variants. For the ACS/ACM and the N-male antenna above, choose N female → RP-SMA male; ordinary SMA male is not the same. Alternative link to the same cable listing ↗
RP-SMA swaps the centre contact. The threads can fit while the contacts do not, so check both.
| Connector | Thread | Centre contact |
|---|---|---|
| SMA male | Inside | Pin |
| SMA female | Outside | Socket |
| RP-SMA male | Inside | Socket |
| RP-SMA female | Outside | Pin |
Match SMA to SMA, or RP-SMA to RP-SMA, with complementary male/female ends. The Cudy connector is unconfirmed.
For our outdoor setup, we prefer 50 Ω N-type at the antenna: a sturdy threaded connection suited to a permanent installation. Weather-seal the joint and support the cable. Use a flexible lead at the dongle rather than hanging heavy connectors from it.
Use the 20 cm pigtail inside the receiver enclosure, rather than a 1-metre extension. Shorter cable reduces loss for the same cable type, especially at 5 GHz. Keep the radio near the antenna and run Ethernet for distance. RG402 is semi-rigid: support it without forcing a tight bend or loading the USB adapter. N-type alone does not increase reception range.
N-type reference ↗ · SMA / RP-SMA reference ↗Budget, compatibility & photo credits
Reviewed 18 October 2026. The displayed total adds the four rounded planning allowances in your selected currency; it is not a retailer quote or a complete installed-kit price. The total covers the default parts above; budget separately for alternative adapters. BLE, Ethernet, PoE and RTL-SDR are optional and excluded.
International product pages and the original AliExpress links let you choose a seller for your region. Availability, selected variants, taxes and delivery vary. Check the selected connector and length on each listing. The cable photo shows only the recommended N-female / RP-SMA-male option from the original listing. Select that connector pair and 20 cm when ordering; the link does not preselect a variant. The antenna listing image shows several sizes. Ethernet photograph is an example.
Currency estimates use a fixed ECB reference-rate snapshot from 16 October 2026 ↗, not live exchange rates or regional retail quotes. Without JavaScript, estimates display in USD.
Photos: ALFA Network, April Brother, The Pi Hut, Newegg, Panda Wireless and the linked AliExpress sellers. Driver and compatibility evidence is available on this page. Complete outdoor kits and physical Bluetooth Remote ID reception remain only partially qualified.
More help, when you need it.
Technical details & reception help
Already have a different adapter?
All known options are here. These are recorded reports, not a list of certified products.
ALFA AWUS036ACS
2.4 / 5 GHz · Reported working
Driver & evidence
The source reports RTL8821AU, but ALFA lists RTL8811AU. Check the revision and detected identity before buying.
RTL8821AU (community) / RTL8811AU (manufacturer). Confirm Linux driver support for the exact detected chipset.
Community report; not a Layer400 release test.
Panda PAU0B / AC600
2.4 / 5 GHz · Reported working
Driver & evidence
A candidate for channel scanning based on an external one-unit timing report; confirm it on your Pi.
MT7610U. Check the distribution’s MT7610U driver and firmware.
Community report; not a Layer400 release test.
ALFA AWUS036ACM
2.4 / 5 GHz · Reported working
Driver & evidence
The source suggests fixed-channel use because its tested unit switched slowly. This is not a measurement of every ACM or MT7612U adapter.
MT7612U. Linux mt76x2u family. A chipset match is not model verification.
Community report; not a Layer400 release test.
ALFA AWUS036NHA
2.4 GHz · Reported working
Driver & evidence
DroneAware reports Pi crashes when AR9271 adapters share a Pi with USB Bluetooth. Its exact environment is unspecified; this is not a Layer400-confirmed universal fault.
AR9271. Check AR9271 firmware and Linux driver availability.
Community report; Bluetooth coexistence warning is source-specific.
ALFA AWUS036N
2.4 GHz · Reported working
Driver & evidence
A 2.4 GHz candidate. No retune measurement is reported.
RT3070. Check Linux RT3070 driver and firmware availability.
Community report; not a Layer400 release test.
TP-Link TL-WN722N v1
2.4 GHz · Reported working
Driver & evidence
Do not confuse v1 with v2+. DroneAware reports an AR9271/USB Bluetooth coexistence crash; environment unspecified, not independently confirmed by Layer400.
AR9271. Check AR9271 firmware and Linux driver availability.
Community report; revision-specific.
Panda PAU0F
2.4 / 5 / 6 GHz · Driver issues reported
Driver & evidence
Listed band capability is not Layer400 reception support. The source reports driver issues; there is no Layer400 6 GHz qualification.
MT7921AU. Driver-dependent; check the exact kernel and monitor-mode behaviour.
Community report of issues; not a universal incompatibility finding.
Realtek RTL8812AU adapter family
2.4 / 5 GHz · Variable; driver needed
Driver & evidence
Different products share this chipset. Report your exact device rather than treating the family as a tested model.
RTL8812AU. Requires a suitable Linux monitor-mode driver; exact model and kernel matter.
Community family-level report; not a model certification.
TP-Link TL-WN722N v2+
2.4 GHz · Not working in the source setup
Driver & evidence
Not the v1 AR9271 model. This report does not prove that every kernel or alternative driver is incapable of monitor mode.
RTL8188EUS. The source advises avoiding this revision for its setup.
Community setup-specific negative report.
Cudy MT7612U observed unit
Bands unconfirmed · Working unit recorded by Layer400
Driver & evidence
Historical Pi 5 Beacon reception evidence exists for this USB identity. Retail SKU, exact band qualification and a current-release device benchmark remain unconfirmed. ACM timings do not apply to this unit.
MT7612U. Observed Linux driver: mt76x2u.
Layer400 observed unit, not a verified retail model/release combination.
USB identity: 0e8d:7612
Find the right parts.
Use the parts and adapter list above to match your radio. The notes cover specific models, revisions and Linux drivers.
Pi, radio and outdoor compatibility notes
- Raspberry Pi
- Use a compatible Raspberry Pi or other ARM64 Linux host. Pi 4 and Pi 5 are tested examples, not the only eligible boards. Check the current release details below and the download page for installation and older-version upgrade paths. Other boards and CPU architectures are not qualified by these checks.
- Wi-Fi
- Pi inspections found Realtek 0bda:b812 on the Pi 4 and MediaTek 0e8d:7612 on the Pi 5. USB identity alone does not establish the retail Cudy model or its antenna socket. Check the exact revision and its Linux driver.
- Outdoor builds
- Protect outdoor connections from rain and route cables with drip loops. We haven’t yet tested a complete outdoor kit.
Using Layer400 alongside an existing aircraft feed
Real Beast reception has been traced through to central storage with FR24 preserved. Current release acceptance and exact hardware limits are listed below. Existing feeds remain in control of their SDR; an unhealthy source or uncertain ownership is not permission to take it over.
Setup discovers supported existing decoder arrangements, including ADSB.im shared JSON. Choose local JSON, an owner-configured LAN JSON endpoint, or Beast TCP input. The existing decoder keeps its radio.
Current release: Pi, software and reception details
Layer400 0.1.0-63
Tested hardware examples: Raspberry Pi 4 Model B or Raspberry Pi 5 Model B · Compatible ARM64 Linux with APT/dpkg, systemd and resolvable dependencies · arm64.
Receiver 0.1.0-63 is available worldwide for fresh installs and updates on compatible ARM64 Linux systems. APT/dpkg, systemd and resolvable dependencies are required. Tested Pi models and OS versions are qualification examples, not installation allowlists. Get hardware help; keep your existing feeder and operating system in place.
- Wi-Fi Remote ID
Use a supported dedicated monitor-mode radio or receive-only sharing with an existing scanner. Shared mode follows the owner's channel without retuning it. Per-input automatic, receive-only and off controls preserve other applications and the internet uplink. Available channels depend on the driver and local rules.
Receiver 0.1.0-63 passed exact signed native ARM64 Debian 12/13 installation and recovery, plus physical Pi4/Pi5 upgrades preserving identity, settings, queues and FR24. Pi4 Wi-Fi capture recovery and Pi5 1090 MHz reception verified. Physical 978 MHz, two simultaneous SDRs and new over-air Remote ID/BLE qualification remain pending.
- ADS-B
Local readsb/dump1090/ADSB.im aircraft.json, owner-configured private-LAN JSON with local DNS or IPv6 and custom paths, or Beast TCP input. A compatible dedicated RTL USB SDR can use the installed decoder. Keep one decoder per SDR; remote feeds must represent the same saved station.
- Bluetooth Remote ID
Supported Bluetooth controllers can be Layer400-managed or receive-only alongside an existing scanner. Shared mode does not configure or stop the owner's scanning. Ordinary BLE transport and offline RID decoding tests passed; genuine over-air BLE RID, long-range PHY and universal adapter compatibility are not claimed.
Optional workshop lesson: listening time versus retuning
REPORTED TIMINGS, EXPLAINED
Why do some adapters scan faster?
This optional example helps you compare radios. You don’t need to choose a timing to install Layer400.
A scanning radio pauses briefly when it changes channel. Move the slider to see how the time spent listening compares with that switching delay. A faster-switching adapter can spend more of each cycle listening.
Example only. This slider does not change your receiver’s settings. The percentages are time spent listening—not the percentage of drones you will detect.
ALFA AWUS036ACS
Reported retune 22 ms
95.8% illustrative share of time listening
4.2% switching · 500 ÷ (500 + 22)
Panda PAU0B / AC600
Reported retune 111 ms
81.8% illustrative share of time listening
18.2% switching · 500 ÷ (500 + 111)
ALFA AWUS036ACM
Reported retune 1,007 ms
33.2% illustrative share of time listening
66.8% switching · 500 ÷ (500 + 1007)
DroneAware’s reported measurements ↗: one unit per model. Test date, sample count, driver environment and statistical method were not reported. These are not Layer400 benchmarks or measured reception interruptions.
Longer listening time reduces switching overhead, but other channels wait longer for a return visit. The calculation does not predict capture rate, range or the chance of detecting a drone. No timing is assigned to unmeasured adapters.
How would Layer400 test this?
A channel-switch command test and a measured reception interruption are different tests. A genuine test needs the exact radio, driver, release, bounded samples and a safe local control path. The website does not run a radio test on your Pi. Use your Pi’s existing status and technical details when reporting a problem.
Keep your feed. Add your contribution.
Share your readsb/dump1090 aircraft.json feed while its decoder keeps running. It can be on this Pi or another Pi at the same station. No second SDR needed.
Connecting a radio or sharing a feed
For direct reception, use a compatible dedicated RTL USB SDR and a 1090 MHz antenna. For an existing decoder, choose its JSON output or Beast TCP output in setup; do not assign its SDR to a second decoder.
Layer400 accepts Beast TCP input as well as JSON. SBS and AVR input are not supported. Its own decoder can also supply local Beast output for other feeders. Keep connections on your Pi or private network, not a public website.
From plugged in
to picking things up.
- Receiver connectedYour Pi is talking to Layer400. You’re ready to get started.
- Radio listeningYour radio is scanning for nearby broadcasts.
- Reception confirmedYour radio has picked up a broadcast.
- First contributionYour receiver has sent its first genuine observation to the network.
Connected, but no drones yet?
Take a look at your radio status, then leave it listening. You’ll hear compatible drones when they’re within range.
USB ports and radio reception
USB 3 devices and cables can interfere with nearby 2.4 GHz Wi-Fi and Bluetooth. If reception is intermittent, try the same capture adapter in a USB 2 port and use a short, well-shielded extension to move it away from the computer and USB 3 equipment. A black or blue socket is only a clue: check the measured USB link speed where the receiver shows it.
This is not a rule that USB 2 is always better. A 480 Mbit/s link does not exclude interference from other nearby equipment. Driver support, power, antennas, channels and the surrounding radio environment still matter. Monitor-mode capability alone is not a guarantee that every adapter works on every kernel.
Power for multiple radios
Allow for the computer, Wi-Fi and Bluetooth adapters, ADS-B SDRs and other USB devices together. An appropriately rated PoE or PoE+ HAT can be an alternative power supply; check its output rating, your exact Pi model, cooling and the switch or injector requirements. It does not remove the Pi USB current limit. Use a suitable separately powered USB hub that does not back-feed when the combined load needs it. The official Raspberry Pi PoE+ HAT is specified for Pi 3B+ and Pi 4, not Pi 5; choose an explicitly compatible product for Pi 5. See the manufacturer specification before buying.
Compare one thing at a time
- Record the adapter, port, antenna position and scan settings. Leave internet, storage and existing ADS-B radios connected.
- Observe one placement, then move only the capture adapter. Wait for it to reappear and for fresh listening status.
- Use the same duration and scan settings for each placement. Keep the antenna still when comparing ports alone; test an extension or antenna relocation separately.
- Repeat A → B → A. Save the results and any errors before changing anything else.
Ordinary Wi-Fi frames or Bluetooth advertising reports can demonstrate reception without a test drone. Quiet air is inconclusive. More traffic later is not proof of a better port, sensitivity, range or packet-loss percentage: transmitters and channel exposure may have changed. Rigorous RF comparisons need a controlled source and repeatable conditions. Onboard Bluetooth cannot be moved between USB ports; compare nearby equipment placement instead.
Guided local comparison
Use the passive USB placement comparison in the local Troubleshooting page. It stops incomplete samples on unplugging, capture restart, stale telemetry, changed scan settings or a hidden browser tab. Results remain in the tab and can be downloaded as hardware descriptions and counts, without automatically collecting drone identities, positions, Bluetooth addresses or packet contents.
Read the USB-IF/Intel interference paper and the published receiver release notes. Never disconnect power or storage to perform a radio-port comparison.
Outdoor builds & community
ROOM FOR YOUR BUILDFrom your workbench
From your workbench
to the community.
A neat enclosure, an ingenious mount, a lesson learned the hard way. The useful details are what make a build worth sharing.
We’re collecting our first build stories. Yours could help someone get started.
Share your build →It doesn’t need to be perfect.
Tell us what you used, what worked and what you’d change. A simple desk setup is just as welcome as a rooftop installation.
Send it privately to the team. We’ll ask before sharing your story.What will you try next?
A different position
Try your antenna in a few accessible spots and compare reception in My impact over several days.
A tidy enclosure
Give the cables a neat route and make it easy to reach your Pi when you need to. Keep outdoor connections protected from rain.
A useful report
Found a good adapter or made a clever mount? Share the details and help the next builder.
Share what you learned →See what your corner of the sky adds.
Explore your reception, activity and awards in My impact. Keep an eye on your station in My receivers, and join the leaderboard if you’d like to.
Active contributors get up to a year of drone playback, covering the recordings available on the network. Aircraft-only feeders can earn contributor access too.
Ask about your hardware
Share a result. Get a hand.
Tell us which adapter you tried and how it went. Your report goes into Layer400’s private hardware review queue, including devices that aren’t in the catalogue. Replies appear in “Your reports” below.
Need help with your setup now? Chat with the team. Mention your report reference if you have one. For a support file, ask the team what they need and review it before sharing; never send passwords or your .layer400pi setup file.