
UART RX (a receiver that talks to the FC over a serial port) and SPI RX (a receiver chip built into the FC and run by Betaflight itself) both work. Mix them up on order day and you get a week of bind failures.
The receiver is the quad's end of the control link. How it talks to the flight controller decides your wiring, firmware, ELRS version and crash repair options.
For link budget and antennas after wiring is correct, see ELRS in the field. For new 5-inch wiring context, see building your first 5-inch.
UART receiver

A separate RX wired to a UART on the FC (four wires: 5V, GND, TX, RX).
Strengths:
- Flexible placement: mount the RX away from VTX heat
- Easy to replace after crashes without swapping the whole FC
- Runs current ELRS 3.x firmware and updates over Wi-Fi
Trade-offs:
- More wires and a little more weight on tiny builds
- One more antenna to strain-relieve
- Wrong UART or wrong protocol setting = bound, but no channels in Betaflight
Typical on: 5-inch freestyle, long-range, any build where the RX might die alone.
SPI receiver
An ELRS radio chip soldered onto the FC itself, with Betaflight running the receiver code over the SPI bus. It was common on whoop AIO boards for years.
Strengths:
- Compact and light; great for tiny builds
- Nothing extra to wire or snag
Trade-offs:
- Version tied to Betaflight: the receiver code lives in Betaflight, so you update it by flashing Betaflight, not with the ELRS Configurator. ELRS 3.x needs Betaflight 4.4 or newer; on 4.3 an SPI receiver only talks to ELRS 2.x radios
- The FC firmware must include SPI RX support for that board
- FC and RX fail together; a dead RX usually means a new board
Many current AIO boards use an onboard serial ELRS receiver instead: a full ELRS chip wired internally to a UART. It looks integrated but behaves like a UART RX and updates like one (ELRS Configurator or Wi-Fi). Check the listing for "SPI" or "serial/UART" before you buy.
Typical on: older tiny whoop and toothpick AIOs.
Comparison table
| Factor | UART RX | SPI RX |
|---|---|---|
| Replace after crash | RX only | Usually a whole FC |
| Firmware | Any target; set the UART to Serial RX, CRSF | Target must include SPI RX for that board |
| ELRS version | 3.x, updated on its own | 3.x on Betaflight 4.4+ (2.x on 4.3) |
| VTX/RX separation | Easier | Tighter |
| Whoop BNF | Onboard serial ELRS is now common | Older BNFs |
| Crossfire (CRSF) | UART | Not available |
Wiring checklist (UART)
□ A free UART, not the one GPS will need later
□ Crossed: RX's TX → FC's RX pad, RX's RX → FC's TX pad
□ Ports tab: Serial RX on that UART; Receiver tab: Serial, CRSF
□ No inversion needed for ELRS/CRSF
□ Solid 5V/GND, no intermittent brownouts
□ Antenna exit with strain relief
□ VTX antenna kept away from the RX antennaFirmware checklist (SPI)
□ FC firmware build includes SPI RX for your board
□ Receiver tab: SPI RX, ExpressLRS
□ Betaflight 4.4+ for an ELRS 3.x radio; bind with the bind button or
`bind_rx` in the CLI (or set the UID from your bind phrase)
□ After flashing, check channels in the Receiver tabCommon mistake: flashing a build without SPI RX support onto a whoop AIO. Everything else works; the receiver is dead.
Bind troubleshooting
| Issue | Check |
|---|---|
| No bind | Same ELRS major version on TX and RX (SPI on Betaflight 4.3 = 2.x); correct bind phrase; RX powered |
| Random failsafe | Antenna, VTX proximity, loose pad |
| One FC works, one not | Target definition / SPI vs UART mix-up |
| Channels move wrong | Channel map in radio model vs FC |
| Works bench, fails field | Antenna placement, carbon shadow, 2.4 urban RF |
Walk through ELRS checklist before assuming dead RX.
PnP and BNF builds
See the BNF vs scratch cost breakdown. A PNP quad has no receiver, so you choose the type. On a BNF whoop, check whether the receiver is SPI (updated through Betaflight) or onboard serial (updated like a separate RX); BNF 5-inch quads use UART receivers.
Tiny whoop upgrades sometimes mean swapping the AIO board; check the receiver type before the first arm.
Purchase decision tree
Frame class?
├─ 5" / 7" freestyle → UART ELRS RX
├─ 3" / toothpick → UART RX, or an AIO with onboard serial ELRS
└─ Whoop / AIO → either works on ELRS 3.x; SPI needs
Betaflight 4.4+, onboard serial updates itself
Already own an FC?
└─ Check the manual: SPI RX, onboard serial RX or bare UARTsRadio and failsafe layer

Receiver type doesn't change your failsafe scenarios; the FC still needs its failsafe stages configured, and each quad still needs its own EdgeTX model.
Put LQ on the OSD whichever type you run; see OSD essentials.
India stocking
UART receivers are cheap and small, so keep a spare before a trip. For whoop AIO boards, check that the seller has your exact board in stock (see the buying checklist), not a similar-looking one with a different receiver.
Order the right RX once; fly more, forum less.
ELRS receiver sizing
| Frame | Typical RX |
|---|---|
| 5" | EP2 or RP-series UART RX |
| 3" | EP-style UART RX, or AIO with onboard serial ELRS |
| Whoop | Onboard ELRS on the AIO (serial on newer boards, SPI on older) |
Antenna placement matters more than receiver type. On a sub-GHz link (in India, ELRS's 868 MHz IN866 band) the antenna is longer, and cramming it under a duct kills range.
Aftermarket FC swap
Moving from a whoop AIO to a separate 5-inch FC means a UART RX. Budget for one; salvaging the receiver from a dead whoop board isn't practical.
Betaflight receiver tab sanity
After install, open the Receiver tab with props off. Sticks should move smoothly from about 1000 to 2000, and aux switches should toggle without flicker. Flicker usually means a loose pad or poor link; fix it before your first flights.
Crossfire note
Crossfire receivers are always UART. SPI is ELRS-only, so don't order an SPI AIO if you're staying on Crossfire or other legacy gear.
UART resource planning on one FC
UARTs are limited. GPS, VTX control, RX and accessories compete for them. Plan before you solder:
| UART user | Typical need |
|---|---|
| ELRS / CRSF RX | One UART, usually the one the FC maker labels for RX |
| GPS | Dedicated UART, baud matters |
| VTX SmartAudio / Tramp | One UART shared or softserial, check FC docs |
| ESC telemetry | Sometimes same UART as RX, conflict |
Screenshot the Ports tab once everything works. Rebuilding from memory costs an evening.
Antenna routing by RX type
A 5-inch UART RX usually mounts at the rear, away from the VTX. A whoop's onboard RX antenna sits under the canopy, close to the VTX and battery. Route antennas so crashes don't yank pads; hot glue strain relief is ugly and effective.
Sub-GHz antennas need clearance; folding one under a duct kills range even if it binds fine. See 2.4 GHz vs sub-GHz in urban India when picking a link for your city.
Spare RX stocking
UART receivers fit in a small parts box; keep one flashed with your bind phrase before a trip. A failed onboard RX usually means a new AIO, so stock the exact board your fleet flies, not a similar-looking one with a different receiver.
Discussion
Comments aren't open on this post yet. Share it with your build group, or start a thread on X.