ELRS in the field: link budget, antennas, and a pre-flight checklist
RADIO // FIELD_REPORT

ELRS in the field: link budget, antennas, and a pre-flight checklist

Published
Updated
Read time6 min read

ExpressLRS (ELRS) took over for good reason: open-source firmware, great value, and a community that actually documents things. But it is still radio, and physics doesn’t care about your sticker.

This guide covers field habits: antennas, firmware matching, Betaflight failsafe, and a checklist you can copy before every session. For choosing ELRS vs Crossfire on a new build, see Crossfire vs ELRS in 2026. For 2.4 vs 900 MHz in Indian cities, see 2.4 GHz vs 900 MHz in urban India.

Link budget in plain English

ELRS in the field: link budget, antennas, and a pre-flight checklist: Link budget in plain English

You have a transmitter (a module or built into the radio) and a receiver on the quad. The margin between usable signal and noise plus losses is your link budget.

What eats margin fastest:

  • Cheap or damaged antennas (bent elements, cracked housings)
  • Orientation mismatches: ELRS uses linear antennas, not circularly polarised ones like video, so a vertical TX antenna and a horizontal RX antenna lose a lot of signal
  • Interference from a VTX or power wiring too close to the RX antenna
  • Flying behind yourself, with your body blocking the signal
  • Urban multipath: concrete, terraces, metal roofs

Fix the mechanical stuff before you turn the module up to 500mW or more.

SymptomCheck firstNot first
Failsafe at short rangeRX antenna, VTX too closeMax TX power
Dead zone in one directionAntenna orientation, body blockingA new receiver brand
Intermittent LQu.FL connector or lead, vibrationA random reflash

Hardware hygiene

  • Handle u.FL connectors gently; they are only rated for a limited number of connections.
  • Strain-relieve the RX antenna lead away from the stack; it often breaks after crashes.
  • Keep TX and RX on the same major firmware version (e.g. both 3.x), and update deliberately, not the night before an important day.
  • Keep VTX coax away from the RX antenna; interference causes ghost failsafes.

UART vs SPI receivers wire up and troubleshoot differently; read receiver UART vs SPI before you blame the bind phrase.

Antennas: same physics as video

The antenna placement rules for video apply here too. Two antennas zip-tied together for neatness interfere with each other. Roughly vertical antennas on both TX and RX is the boring habit that works.

Pack a spare RX antenna in your field repair kit; damaged antennas fail silently.

Betaflight-side habits

  • Confirm arm and failsafe behaviour in the Configurator before the first flight.
  • Know what your failsafe does: GPS Rescue is very different from "drop" failsafe, so configure what you actually intend. Read failsafe scenarios.
  • Put LQ on the OSD (OSD essentials) so you see the margin shrinking before it runs out.

Failsafe test:

1. Props off, battery in: arm, switch the radio off
2. Motors should stop (drop) or behave as configured within a second or two
3. Check the OSD shows failsafe and recovers when the radio comes back
4. Repeat after any receiver, FC or firmware change

Power and band choices

2.4 GHz is the default for most freestyle and whoop builds: smaller antennas and a wide choice of hardware. Sub-GHz gets discussed for penetration and noisy RF; test at your spots, not YouTube valleys. In India, sub-GHz ELRS should use the IN866 regulatory domain, not US 915 MHz.

Fly mostlyStarting bias
Open club field2.4 simplicity
Urban terrace / concreteTest sub-GHz only if 2.4 struggles
Tiny indoor whoop2.4; size wins

Module bays vary, so check your radio before you order. See radio gimbals and EdgeTX for model and arm-switch setup on the radio side.

India field realities

ELRS in the field: link budget, antennas, and a pre-flight checklist: India field realities

  • Dense apartment Wi-Fi affects 2.4 GHz. It is rarely fatal outdoors, but terrace tests are the worst case.
  • Buy modules and receivers from sellers with a sensible DOA policy (buying FPV gear in India).
  • In summer, let radios and modules cool after a hot car before long sessions.

Pre-flight checklist (copy to your notes)

1. Receiver bound; LQ on the OSD or radio telemetry
2. Failsafe tested since the last config change
3. Antennas roughly vertical and secure on TX and RX
4. VTX channel and power right for this spot
5. Pack healthy, not a nearly-flat "one more hover"
6. TX and RX on the same major firmware version
7. Arm switch needs a deliberate flick, not a bump

Common mistakes

  • Reflashing the TX the night before an event without a bench bind
  • Watching RSSI instead of LQ (LQ is the better warning)
  • Max TX power with the RX antenna kinked and buried in carbon
  • Skipping the failsafe test because "it bound fine"

ELRS is forgiving until it isn’t. Good antennas and a clean install are free range.

Packet rate and range (practical, not lab)

Higher packet rates feel crisper on the sticks but give up some range margin. Many pilots run the default rate for freestyle and only experiment for long range. Change one thing at a time and log LQ along your own field’s fence line, not against someone’s mountain video.

Bench bind ritual

1. Antennas attached BEFORE powering the TX or RX
2. TX module firmware version noted
3. RX firmware on the same major version
4. Same bind phrase on TX and RX (note it in the model notes)
5. Channels checked in the Betaflight Receiver tab
6. Failsafe saved and tested, props off

Powering an ELRS transmitter or receiver without its antenna can damage the RF stage, so step one comes first.

Urban range test (15 minutes, same spot every month)

Use one fence line or known path at your regular field, not a new spot.

1. Hover line-of-sight at the start point; note LQ on the OSD
2. Fly the path you actually fly: behind trees, low, not at mast height
3. Drop a map pin where LQ falls below your personal floor
4. Repeat after any receiver, antenna or VTX change
5. Log it: "Mar 2026, ELRS 2.4, LQ<50 at south tree"

Trends matter more than absolute distances. If the margin shrinks month after month, check antenna leads and VTX spacing before buying a new module.

Telemetry to radio vs OSD only

Data pathProsCons
LQ on the OSDAlways visible in gogglesClutter if the layout is poor
LQ on the radioSpoken or on-screen alerts without editing the OSDTelemetry must be set up on the model

Pick one main margin indicator and trust it.

See also

Discussion

Comments aren't open on this post yet. Share it with your build group, or start a thread on X.