The same factory file includes all five board profiles. The device selects its profile on first boot; radio capability still depends on its installed adapter. Full image qualification is incomplete.
Choose your board
One factory file covers all five boards. Each board's page has its hardware, measured limits and install notes; compare them side by side.
NanoPi Zero2 →
A small, cheap board with one M.2 slot for a Wi-Fi 7 card. The most-tested build, with an illustrated parts and assembly guide.
One M.2 Wi-Fi 7 card (QCNCM865 or BE200) · BE200 captured 320 MHz outside the app; 160 MHz measured in itUnified imageRaspberry Pi 5 →
The board for 320 MHz capture and relative spectrum with a Qualcomm card, with USB 3 for extra adapters and an optional touch console.
PCIe card through an M.2 HAT, plus USB adapters · 320 MHz measured (QCNCM865)Unified imageRaspberry Pi 4 / WLAN Pi R4 →
No M.2 slot, but USB 3 ports for Wi-Fi 7 adapters. The original WLAN Pi R4 display and buttons are supported.
USB adapters only · 160 MHz measured (MT7925U)Unified imageWLAN Pi Pro →
Two Intel BE200 radios, PoE with battery backup, and front-panel menus. The choice for two channels at once.
Two Intel BE200 · 160 MHz in the app; BE200 can do 320Unified imageWLAN Pi Go →
A small enclosed BE200 sensor with internal antennas, managed and powered over one USB-C cable.
Intel BE200, internal antennas · 320 MHz on 6 GHz tuned; app offers 160What happens after flashing
Each device creates its own identity, asks for first-use setup and expands Data to its available storage. Flash a fresh image for each unit; don't clone a configured card or move it between board types. Complete setup with the one-time code, then use the app or the local device website.
Factory flashing erases storage. Signed OTA updates are for existing unified A/B installations and keep Data. Read the full installation guide and release evidence. Earlier releases are in the sensor changelog.
WLAN Pi community software
The image includes upstream WLAN Pi tools and front-panel software with original authors and contributors credited. Commander supports its documented integrations; support for inherited tool scripts and menu options is limited. Community and source credits.