Ready-to-Fly Drones · Shop by specification
Find the right ready-to-fly drones faster.
Choose the aircraft type and package format that matches how quickly you want to get flying.

A radio transmitter and receiver must share more than a brand name. The protocol, frequency band, firmware family, regulatory region and configuration must agree, and the receiver must connect correctly to the flight controller. Treat the control link as a complete system that also includes antennas, power, failsafe and telemetry.
Frequency describes the radio band; protocol describes how the transmitter and receiver communicate. Two products can both use 2.4 GHz and still be incompatible. Conversely, one protocol family may offer different frequency-band versions that cannot bind to each other.
| Field | Must match or be supported | Common error |
|---|---|---|
| Protocol family | Exact transmitter-module and receiver protocol | Assuming all products from one brand bind together |
| Frequency band | For example, matching 2.4 GHz or the correct sub-GHz version | Buying a 915/868 MHz receiver for a 2.4 GHz module |
| Firmware generation | Compatible major version and target | Binding fails after only one side is updated |
| Region / domain | Legally configured and mutually compatible region settings | Mismatched regulatory domains or channel plans |
| Receiver output | Flight controller supports the receiver’s serial or other output | Wrong UART, inversion or receiver provider |
A radio may have an internal RF module, an external module bay or both. Record the exact radio model and module version. If using an external module, verify bay format, power requirements and firmware. Do not infer module compatibility from physical fit alone.
For a receiver, choose the band and antenna arrangement around the aircraft size and use case. A compact ceramic antenna can simplify a small build; a diversity receiver may improve installation options on a larger aircraft, but only if both antennas are mounted correctly and the receiver’s protocol and output are supported.
Check receiver input voltage, ground, serial output and telemetry wiring against both pinouts. A plug shape is not a pinout guarantee. Select an available UART, then configure the correct serial receiver option and protocol provider in the flight-controller software. Keep receiver antennas and signal wiring away from high-current battery leads, ESC noise and video transmitters where practical.
Failsafe is a required system check, not an optional radio feature. Remove propellers, power the aircraft safely and confirm the flight controller reports a valid receiver signal. Then test loss of control-link signal and verify the configured response. Repeat after firmware, receiver, radio or flight-controller changes.
Browse FPV radios and receivers, use the Beginner or Long Range build path, and review the component compatibility guide. If the protocol, firmware target or antenna version is uncertain, send WXBMW the exact radio, module, receiver and flight controller models.
No. Frequency alone is not enough; the transmitter module and receiver must support the same protocol and compatible firmware.
The RF link can be working while the receiver output, wiring, UART or serial-receiver configuration is wrong. Troubleshoot those layers separately.
Use only the exact band and regional configuration supported by the products and legal in the operating location. Do not assume sub-GHz versions are interchangeable.
Next step after this guide
Use the guide to define the required specifications, verify the aircraft-level Build path, then compare current WXBMW parts. Recheck voltage, mounting, protocol, connector and load compatibility before ordering.
No in-stock WXBMW option is shown for this exact category right now. Use the specification-match request instead of assuming a nearby item is compatible.
No account yet?
Create an Account