ExpressLRS dominates the conversation in 2026 — and for good reason: open-source, blistering 1000Hz packet rates, sub-$40 receivers, and range that rivals anything on the market. But TBS Crossfire is not dead. It still powers thousands of working rigs, offers the most polished MAVLink integration in the hobby, and delivers a setup experience that ELRS has only recently approached. If you fly Crossfire, are considering it for a new build, or want to understand the real differences between the two systems, this guide covers everything.
Crossfire Hardware Ecosystem
TBS Crossfire operates on the 868 MHz (EU) / 915 MHz (US/International) ISM band. The ecosystem has been stable for years with a clear product lineup:
TX Modules
- Crossfire Micro TX V2: The standard module. Fits JR bay on most radios (Taranis, Radiomaster, Jumper). Outputs 25mW–250mW on USB power, up to 1W when powered by the radio’s external battery. Most pilots run this.
- Crossfire Full-Size TX: Larger module with an internal battery, 2W maximum output, OLED screen, and built-in Bluetooth for telemetry bridging. Targets long-range pilots who need every dB of link budget.
- TBS Tango 2: Integrated radio with Crossfire built in. Compact, gamepad-style. Runs FreedomTX (OpenTX fork). No external module needed.
- TBS Mambo: Full-size tray radio with integrated Crossfire. Runs FreedomTX. Aimed at pilots who prefer a traditional form factor with integrated Crossfire.
Receivers
- Crossfire Nano RX: The standard receiver. 8.4g, single antenna, up to 4 PWM outputs. The default choice for quads.
- Crossfire Diversity RX: Two independent receiver chains with two antennas. Heavier (16g) but essential for builds where the battery or carbon frame blocks one antenna at certain orientations.
- Crossfire Micro RX V2: Legacy receiver, larger than the Nano. Mostly superseded but still available.
Binding Process
Crossfire binding is straightforward but different from traditional 2.4 GHz systems:
- Power the TX module and the receiver (the receiver needs power — typically 5V from your FC’s receiver pad).
- On the TX module, navigate to the Crossfire menu (on OpenTX/EdgeTX radios, this is under the SYS menu, page to Crossfire).
- Select “Bind” on the TX. The module enters binding mode for 10 seconds.
- Within those 10 seconds, press the bind button on the receiver (Nano: hold for 3 seconds until the LED flashes rapidly).
- Binding is confirmed when the receiver LED turns solid green. The TX will display the receiver’s firmware version.
Crossfire uses a permanent bind — once paired, the receiver remembers the TX until you rebind. There is no bind phrase or passphrase system like ELRS.
RF Profile Settings
The Crossfire TX menu offers several RF profiles that control power, packet rate, and telemetry ratio:
| Setting | Options | Recommendation |
|---|---|---|
| TX Power | 25mW, 100mW, 250mW, 500mW, 1W, 2W | Dynamic power (auto) |
| Dynamic Power | On / Off | On for all normal flying |
| Packet Rate | 50Hz, 100Hz, 150Hz | 150Hz for quads |
| Telemetry Ratio | 1:1 to 1:64 | 1:8 (default, good balance) |
Dynamic power is the killer feature. The TX starts at 25mW and only increases power when RSSI begins to drop. If you fly within 500 meters, the TX may never leave 25mW. If you push out to 5 km, it ramps to 1W transparently. This saves battery on the TX and reduces RF pollution for other pilots.
For packet rate, 150Hz delivers updates every 6.7ms — fast enough that no human can perceive additional latency. Dropping to 50Hz increases range slightly but adds roughly 10ms of latency. Use 150Hz for everything unless you are chasing multi-kilometer range records, where 50Hz gives marginally better SNR.
CRSF Protocol: Faster Than SBUS
Crossfire uses the CRSF (Crossfire Serial Frame) protocol between the receiver and flight controller. This is a bidirectional serial protocol running at 400 kbaud (configurable to higher rates). Compared to SBUS:
| Feature | SBUS | CRSF |
|---|---|---|
| Baud rate | 100 kbaud | 400+ kbaud |
| Channel resolution | 11-bit (2048 steps) | 11-bit (CRSF), up to 16-bit |
| Telemetry | No (SmartPort separate wire) | Yes (bidirectional on same wire) |
| Latency | ~14ms (150Hz) | ~6.5ms (150Hz) |
| Channel count | 16 | 16 standard, expandable |
CRSF is a single-wire connection: RX to a free UART TX pad on the FC. Unlike SBUS+SmartPort, you do not need a separate telemetry wire. Set the FC’s UART to “Serial Rx” in the Ports tab and select “CRSF” as the receiver protocol in the Configuration tab.
LQ and RSSI Configuration in Betaflight OSD
Crossfire reports two link health metrics: RSSI (Received Signal Strength Indicator in dBm) and LQ (Link Quality, 0–100%). Both are critical and should be in your OSD.
- RSSI dBm: Raw signal power. At 25mW TX, -95 dBm is poor. At 1W TX, -95 dBm is fine. RSSI alone does not tell you link health — it tells you path loss.
- LQ: Percentage of valid frames received. This is the number that matters. LQ above 90%: link is solid. LQ 70–90%: marginal, expect some latency. LQ below 70%: danger, turn back or increase power.
In Betaflight, RSSI is auto-detected when CRSF is selected. For LQ display, add the “Link Quality” element in the OSD tab. Some pilots also display “RSSI dBm” directly (separate from the scaled RSSI percentage) for precise signal analysis.
Configure your OSD warnings: set LQ warning at 75% and critical at 60%. When LQ drops, you will see the OSD flag immediately — do not wait for a failsafe.
Telemetry and MAVLink
Crossfire supports MAVLink encapsulation natively — a feature ELRS has only recently added and still lacks the polish of TBS’s implementation. If you run ArduPilot or INAV with MAVLink telemetry, Crossfire transparently bridges MAVLink packets between the FC and the TX module’s Bluetooth/WiFi interface. This means you can run Mission Planner or QGroundControl on a laptop or tablet while flying, with no additional hardware.
This is the feature that keeps Crossfire entrenched in the professional and commercial drone space. For FPV quad pilots, MAVLink support is less relevant — Betaflight uses MSP, not MAVLink — but if you ever branch into autonomous flight, Crossfire’s MAVLink bridge is plug-and-play.
Crossfire vs ExpressLRS: Complete Comparison
| Feature | Crossfire | ExpressLRS |
|---|---|---|
| Frequency band | 868/915 MHz | 2.4 GHz / 868/915 MHz |
| Max packet rate | 150Hz (250Hz with special FW) | 1000Hz (2.4G), 200Hz (900M) |
| Range (real-world) | 10–40 km (900 MHz) | 5–15 km (2.4G), 15–50 km (900M) |
| Latency at max rate | ~6.5ms | ~2–4ms |
| Receiver price | $30–40 (Nano) | $13–25 (various) |
| TX module price | $70–120 (Micro TX) | $40–60 (various) |
| Open source | No (closed) | Yes (GPL) |
| Ease of setup | Plug in, bind, fly | Bind phrase, Wi-Fi flashing (easy now) |
| MAVLink support | Mature, seamless | Experimental / developing |
| Telemetry | Bidirectional, mature | Bidirectional, improving |
| Ecosystem maturity | Stable, no major changes expected | Active development, frequent updates |
| Best for | MAVLink users, simplicity, long-range | Racers, latency-sensitive pilots, budget builds |
Where Crossfire Still Wins in 2026
ExpressLRS is the better choice for most new builds. It is cheaper, faster, and the open-source development pace means it will only get better. But Crossfire has three remaining strongholds:
- MAVLink users: If you fly ArduPilot with full MAVLink telemetry to a ground station, Crossfire works today with zero configuration. ELRS MAVLink support exists but is not yet battle-tested at scale.
- Simplicity above all: Crossfire’s binding process, RF profile management, and OSD configuration are simpler than ELRS. No Wi-Fi flashing, no bind phrases, no model matching. Power on, bind, fly. For pilots who want a radio link that just works and never needs firmware updates, Crossfire delivers.
- Existing fleet: If you have 5–10 quads on Crossfire, there is no compelling reason to replace them. Crossfire hardware is reliable and the protocol is mature. Fly it until something breaks, then evaluate ELRS for the next build.
Antenna Selection
- Immortal T (receiver): The standard antenna for Nano RX. Flexible, durable, and designed to be zip-tied to a standoff. Mount it vertically and as far from the VTX antenna as possible. The T-shape gives near-omnidirectional radiation in the horizontal plane.
- TBS Diamond (TX): Compact, rigid antenna for the TX module. Good for mid-range flying where a large directional antenna is impractical. Mount it vertically on the radio.
- TBS Triumph (TX): Flexible 900MHz antenna. Less range than a Moxon or Yagi but more durable and forgiving of orientation.
- Moxon rectangle (TX): Directional antenna with roughly 5 dBi gain. Aim it at the quad for maximum range. Not practical for freestyle where you are constantly turning, but excellent for long-range point-to-point flights.
Crossfire in 2026 is a mature, stable system that does exactly what it says on the box. It will not win a latency race against ELRS, but it will carry your quad 20 km and back with a link so boringly reliable you will forget it is there. For many pilots, that is exactly what a radio link should do.