You flash EdgeTX to your RadioMaster TX16S and stare at a blank model screen. Nothing is configured — no channels, no switches, no telemetry. The EdgeTX model setup is deliberately blank-canvas, unlike OpenTX wizards that held your hand. This frustrates new users but rewards those who learn the mixer pipeline. By the end of this guide, you’ll have a working FPV model with arming logic, mode switching, telemetry widgets, and ExpressLRS integration.
Model Creation and Base Setup
Press MDL, scroll to an empty slot, long-press ENTER, select Create Model. The wizard asks four things: Model Type (Plane/Multirotor/Heli), Channel Order (set to AETR for 99% of FPV quads — Betaflight default), Timer source (THs — throttle stick), and Model Name. Don’t skip the timer — a voice callout at 3 minutes has saved hundreds of my packs from over-discharge.
Set Internal RF to CRSF: In Model Setup → Internal RF, set Mode to CRSF. Baudrate 400k for EdgeTX 2.8+. Leave External RF OFF. CRSF at 400k delivers 150Hz update rate at 16 channels — more than any FPV quad needs.
ADC Filter: EdgeTX 2.9+ defaults to ADC filter OFF. Turn it ON. The gimbals on hall-effect radios produce electrical noise that shows up as jitter in Betaflight’s Receiver tab. ADC filter smooths this without adding perceptible latency.
Mixer Logic — The Engine Room
The EdgeTX mixer is NOT a channel mapping table. It’s a pipeline: Input → Mixer → Output. Understanding this prevents 90% of “why doesn’t my switch do anything?” head-scratching.
Inputs Layer
Define how physical controls are processed: stick curves, rates, expo. For FPV, leave all stick inputs at default (100% weight, no curve). Betaflight handles rates and expo internally — duplicating them in EdgeTX creates an exponential stack that feels mushy.
The ONE input you should configure: Throttle. Set a custom curve: -100, -80, -60, -40, -20, 0, 20, 40, 60, 80, 100 (linear). Add a 3% deadband at the bottom: first two points at -100 and -97. This prevents accidental spin-up when the throttle stick doesn’t perfectly center at zero.
Mixer Layer
Each channel gets a mixer line. For a basic FPV quad:
- CH1 (Aileron/Roll): Source = Ail, Weight = 100
- CH2 (Elevator/Pitch): Source = Ele, Weight = 100
- CH3 (Throttle): Source = Thr, Weight = 100
- CH4 (Rudder/Yaw): Source = Rud, Weight = 100
- CH5 (Arm): Source = MAX, Weight = 100, Switch = SA↑ (or your preferred switch)
- CH6 (Mode/Flight Mode): Source = MAX, Weight = 100, Switch = SB — then add a second line: Source = MAX, Weight = 0, Switch = SB↓, Multiplex = REPLACE
The REPLACE multiplex is the key concept. Without it, the second line adds to the first. With REPLACE, it overwrites when active. Your CH6 output becomes: 100% when SB↑, 0% when SB- (middle), -100% when SB↓. These correspond to Betaflight modes set in Adjustments tab.
Switch Mapping Strategy (5-inch Freestyle)
| Switch | Position ↑ | Position – | Position ↓ |
|---|---|---|---|
| SA (2-pos) | Armed | Disarmed | N/A |
| SB (3-pos) | Acro | Horizon | Angle |
| SC (3-pos) | Beeper | — | Turtle Mode |
| SD (2-pos) | Pre-arm ON | Pre-arm OFF | N/A |
| SF (2-pos momentary) | — | — | GPS Rescue |
| Pot S1 | Volume | — | — |
This layout separates safety (SA/SD) from flight feel (SB) from emergency functions (SC↓). The momentary switch for GPS Rescue is intentional — you can’t accidentally leave Rescue on because the switch springs back.
Pre-Arm Logic
Setting pre-arm on SD prevents accidental arming, but EdgeTX can enforce it at the radio level too. Add a logical switch: L01 = AND, SA↑, SD↑. Then set your Arm mixer line’s Switch to L01 instead of SA↑. The radio now requires BOTH switches to output an arm signal. This doesn’t replace Betaflight’s pre-arm — it’s an additional layer.
Telemetry Screen Configuration
EdgeTX discovers CRSF telemetry sensors automatically. Go to Model Setup → Telemetry → Discover new sensors. Spin up a motor — values populate. The key sensors for FPV:
- RxBt: Receiver voltage (should match your FC’s 5V/8V output)
- VFAS: Flight battery voltage (this is your fuel gauge)
- Curr: Current draw in amps
- Capa: Consumed capacity in mAh
- GPS: Speed, altitude, coordinates
- 1RSS: LQ (link quality) — more useful than RSSI dBm
- RSSI: Signal strength in dBm
Critical setup mistake: EdgeTX defaults to sensor ID matching, not sensor name. If you swap receivers, telemetry breaks because sensor IDs change. In Telemetry settings, set “Ignore instance” to ON for RxBt, VFAS, and RSSI.
Custom Telemetry Screens
EdgeTX supports up to 4 telemetry pages. Build a FPV-specific screen:
Page 1 (Flying): VFAS (large), 1RSS (bar), Capa, Timer, GPS Speed
Page 2 (Battery): VFAS, Cell Min, Curr, Capa, RxBt
Page 3 (GPS): GPS Alt, GPS Speed, GPS Heading, Satellites, Home Dist
Configure voice callouts: “Low battery” at 3.5V per cell (14.0V on 4S), “Critical” at 3.3V (13.2V), “RSSI low” at 50%. Set callout intervals: battery every 30 seconds below threshold, RSSI every 10 seconds.
ExpressLRS Lua Script Integration
The ELRS Lua script is YOUR primary configuration tool. Binding, WiFi mode, packet rate, telemetry ratio — all managed here. Put it on a telemetry page or assign it to a physical button.
Long-press SYS → Tools → ExpressLRS. Key settings:
- Packet Rate: 500Hz for racing, 250Hz for freestyle (better range), 150Hz for long-range
- Telemetry Ratio: 1:32 for racing (minimal overhead), 1:64 for freestyle, 1:128 for long-range
- Switch Mode: 8ch for basic quads, 16ch for full-featured builds with multiple modes
Packet rate tradeoff: 500Hz gives you 2ms latency advantage over 250Hz. If you can feel that, you’re either Mr. Steele or imagining it. 250Hz with 1:64 telemetry ratio is the sweet spot for 99% of pilots — rock-solid link with full OSD telemetry at ranges out to 3km.
EdgeTX Parameter Table
| Setting | Recommended Value | Alternative | Effect if Wrong |
|---|---|---|---|
| Internal RF Mode | CRSF | MULTI (for SPI receivers) | No bind, no telemetry |
| Baudrate | 400k | 115k (legacy) | Dropouts at 115k with >8ch |
| ADC Filter | ON | OFF | Jitter visible in Betaflight Receiver tab |
| Timer Source | THs | TH% | Timer counts at zero throttle unless THs |
| Stick Deadband | 2-3% | 0% | Drift at center, unwanted yaw/roll |
| Pre-arm Logic | L01 AND | None | Single-switch accidental arm |
| Telemetry Ignore Instance | ON | OFF | Broken telemetry after RX swap |
| ELRS Packet Rate | 250Hz | 150Hz/500Hz | Reduced range (500Hz) or higher latency (150Hz) |
| ELRS Telemetry Ratio | 1:64 | 1:32 / 1:128 | Missing OSD data (1:128) or reduced range (1:32) |
Common Mistakes & What Most Pilots Get Wrong
Mistake 1: Configuring rates in EdgeTX AND Betaflight
Stacking expo creates a response curve shaped like a hockey stick — dead-feeling center with a violent jump at stick edges. I’ve flown quads that were genuinely unflyable because the previous owner had 30% expo in both the radio and Betaflight.
Consequence: Unpredictable feel. The quad simultaneously feels sluggish and twitchy depending on stick position.
Fix: Zero out all EdgeTX rates and expo. Set a linear curve in Inputs. Do ALL flight feel tuning in Betaflight’s Rates tab.
Mistake 2: Not setting a throttle deadband
Hall-effect gimbals are precise — almost too precise. The throttle stick at -100 might output -99.7 due to temperature drift. Betaflight interprets this as “throttle slightly above zero” and the motors twitch.
Consequence: Motors twitch at zero throttle. In extreme cases, they spin slowly — a safety hazard on the bench.
Fix: Set throttle Input curve to -100, -97, -95… then linear. The 3% deadband absorbs gimbal noise.
Mistake 3: Forgetting to run Discover Sensors on a new model
Copying a model file doesn’t copy telemetry sensor IDs. EdgeTX shows “—” for all values until you discover.
Consequence: No telemetry on OSD, no voice callouts, no RSSI warning. You fly blind on battery and signal strength.
Fix: After creating any new model or swapping receivers, run Telemetry → Discover new sensors. Confirm VFAS and RSSI populate before flying.
Mistake 4: Using a latching switch for GPS Rescue
Easy to do — flip SC↑ for Rescue, get distracted, forget to flip back, land, arm next pack, and the quad immediately enters Rescue mode on the ground.
Consequence: Quad spools up at hover throttle on the bench because Rescue is active on arm.
Fix: Assign Rescue to a momentary switch (SF on most radios). It’s only active while you hold it physically.
Mistake 5: 16-channel mode without checking Betaflight’s channel limit
ExpressLRS in 16ch mode at 150Hz sends all 16 channels. Betaflight defaults to 12 or 16 depending on firmware. If Betaflight is set to 8, channels 9-16 are ignored — including potentially your Arm channel if you mapped it high.
Consequence: Switches on channels above 8 don’t register. Arm may not work at all.
Fix: In Betaflight Receiver tab, check you’re seeing all assigned channels. Set rx_max_aux_channels = 14 via CLI if needed.
⚠️ Regulatory Notice: The flight recommendations in this article should be followed in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
For ExpressLRS binding and firmware details, see our ExpressLRS 3.x flashing and migration guide. For telemetry integration in the OSD, see our ExpressLRS telemetry setup guide.
Further Learning
A quality upgrade for your EdgeTX radio: the RadioMaster AG01 CNC gimbals deliver hall-effect precision with adjustable tension — available at uavmodel.com, the difference in mid-stick feel is immediately noticeable.