How the link works
TX — the air side
An OpenIPC camera runs the Waybeam encoder, turning the sensor into a stream and handing it straight to the radio. The frame rate set here decides most of your latency budget.
The radio link
devourer carries video, telemetry, and control over commodity Realtek adapters, straight from userspace — no association, no retransmit stalls, and rate, power and channel set per frame.
RX — your side
PixelPilot turns a Rockchip board into a dedicated ground station — the fastest way to receive. Aviateur runs on the Windows, Linux, or macOS machine you already own.
TX → devourer → RX
FPV: from lens to goggles
A fully open digital FPV system: no locked ecosystem, no paired hardware, no firmware ceiling. Build the air unit from a supported camera, pick your ground station, and tune every stage of the pipeline.
Beyond drones: robots and teleoperation
The same link carries video for industrial robots, AGVs, inspection rigs, and remote operation — anywhere a closed video system would lock you in or a cloud hop would add seconds.
On supported SoCs, frames carry wall-clock timestamps tied to the sensor frame start — millisecond-class synchronization for multi-camera rigs without extra hardware.
Building a product on this link? Talk to us — we do custom development and OEM work.
How fast, really
What decides your number is the ground station, far more than the resolution you pick. These are figures people report from flying this stack on their own hardware.
Reported in the OpenIPC and wfb-ng chats, not measured by us. Resolution barely moves the number; frame rate and screen refresh decide it — change nothing but the monitor and the same camera shifts by 120 ms.
Hardware
Air units are built from supported cameras and AIO boards — start from the supported hardware list. RunCam and other vendors ship OpenIPC-based FPV hardware out of the box.