What the Receiver Tab Does in Betaflight
The receiver tab in Betaflight is where your flight controller translates radio commands from your transmitter into stick and switch inputs the software can understand.
If you want responsive control, correct channel mapping, and a safe arming setup, learning how to configure FPV drone receiver tab settings is essential.
This guide explains the full setup process, the most common receiver protocols, and the checks that prevent wrong directions, broken arm switches, and failsafe problems.
Before You Open the Receiver Tab
Receiver setup starts before you touch Betaflight.
You need a compatible radio transmitter, a working RF module or integrated radio system, and a receiver wired correctly to the flight controller.
- Transmitter: ExpressLRS, Crossfire, FrSky, FlySky, Spektrum, or another supported system.
- Receiver: Onboard, serial, or PWM receiver depending on your build.
- Flight controller: Betaflight-compatible board with a free UART if you use a serial receiver.
- Wiring: Power, ground, and signal lines connected to the correct pads.
If the receiver is not bound to the transmitter or the UART is misconfigured, the receiver tab will not show valid stick movement no matter how many settings you change.
How to Configure FPV Drone Receiver Tab Step by Step
1. Select the correct receiver mode
Open Betaflight Configurator and go to the Receiver tab.
Choose the receiver protocol that matches your hardware, such as Serial-based receiver, or a legacy PWM-based option if your setup is older.
For most modern FPV drones, Serial-based receiver is the correct choice.
This covers protocols such as CRSF for Team BlackSheep Crossfire, ExpressLRS, SBUS, and IBUS depending on your receiver and wiring.
2. Set the serial receiver protocol
After selecting Serial-based receiver, go to the Ports tab and enable the correct UART for your receiver.
Then choose the matching protocol in the Configuration tab or receiver settings area, depending on your Betaflight version.
- CRSF: Common for ExpressLRS and Crossfire.
- SBUS: Widely used with FrSky systems.
- IBUS: Common on FlySky receivers.
If the protocol and UART do not match the hardware, the receiver tab may show no movement or unstable channel values.
3. Power on the radio and confirm binding
Turn on your transmitter first, then connect the drone to USB or battery.
If the receiver is bound, the status LEDs on the receiver should indicate a link.
In Betaflight, the channel bars in the receiver tab should move when you move the sticks.
If binding fails, check the receiver manual for bind mode, model matching, or binding phrase requirements.
ExpressLRS, for example, often uses a binding phrase or Wi-Fi configuration instead of a traditional bind button process.
4. Verify stick movement
In the receiver tab, move the aileron, elevator, throttle, and yaw sticks one at a time.
Each corresponding channel bar should move smoothly from low to high without jumping or reversing unexpectedly.
For a basic Mode 2 radio layout, you should see:
- Aileron: Roll left and right
- Elevator: Pitch forward and back
- Throttle: Throttle up and down
- Yaw: Rudder left and right
At this stage, the most important task is not tuning but confirming that Betaflight is reading the correct inputs.
Set the Correct Channel Order
Incorrect channel order is one of the most common reasons a drone feels wrong on the bench.
If the bars do not match the stick you are moving, adjust the channel map in Betaflight or on the transmitter.
Common channel order standards include:
- TAER
- AETR
- ETAR
The right choice depends on your radio system and receiver.
Many pilots use AETR for Betaflight, but you should always verify by moving one stick at a time.
If throttle moves the roll bar, or yaw moves pitch, the map is wrong.
Once the order is correct, recheck the channel endpoints.
You want low values near 1000, center around 1500, and high values near 2000 for each control input.
Adjust Endpoints, Centers, and Deadband
Betaflight expects the receiver signal to cover a clean range.
Poorly calibrated endpoints can cause arming issues, jitter, or inconsistent flight behavior.
- Low endpoint: About 1000
- Center: About 1500
- High endpoint: About 2000
If your radio exposes subtrims, endpoint adjustments, or channel limits, use them to bring the values into range.
Keep the center as close to 1500 as possible on roll, pitch, and yaw.
Throttle should rest at the low end and move smoothly upward.
Use deadband only when necessary.
Too much deadband can reduce precision, but a small amount may help with jitter on older radios or noisy links.
Assign and Check Auxiliary Switches
Auxiliary channels control features like arming, flight modes, beeper, turtle mode, and GPS rescue.
In the receiver tab, toggle each switch and watch the corresponding channel bar or range marker.
Useful switch assignments include:
- ARM: Disarms or arms the motors
- ANGLE or HORIZON: Stabilized flight modes
- BEEPER: Helps locate the quad
- FLIP OVER AFTER CRASH: Commonly called turtle mode
Make sure the arm switch range is clear and does not overlap another mode range.
Overlapping ranges can produce confusing behavior and make troubleshooting harder.
Understand Receiver Failsafe Behavior
Failsafe is a safety feature that tells the flight controller how to react when radio signal is lost.
In FPV, the correct failsafe setup is critical because it prevents flyaways and reduces risk to people and property.
Modern Betaflight setups usually rely on receiver link loss handling combined with flight controller failsafe logic.
Your receiver should detect signal loss quickly, and Betaflight should disarm or drop the quad according to its configured failsafe procedure.
Test failsafe carefully on the bench with props off.
Turn off the transmitter and confirm that Betaflight reports signal loss and responds as expected.
If the receiver stays active after the transmitter is off, stop and fix the failsafe behavior before flying.
Common Problems in the Receiver Tab
No channel movement
If nothing moves in the receiver tab, check power, wiring, UART assignment, receiver protocol, and binding status.
Also verify that the correct serial receiver option is enabled.
Wrong stick direction
If roll moves yaw or pitch moves throttle, fix the channel order.
This is usually a mapping issue rather than a hardware problem.
Jittery or unstable bars
Small fluctuations can come from a weak link, poor antenna placement, electrical noise, or an improperly configured receiver.
Inspect antenna orientation and keep receiver antennas away from high-current wires and carbon fiber obstructions.
Arming does not work
Check that the arm switch is assigned correctly, the throttle is low, the craft is not in an error state, and all required pre-arm conditions are satisfied.
Betaflight will refuse to arm if it detects a safety issue.
Best Practices for Reliable Receiver Setup
- Use the receiver protocol designed for your radio system.
- Keep receiver antennas mounted with clear orientation and separation.
- Check channel order every time you change radio gear.
- Set safe switch ranges for arm and flight modes.
- Test failsafe with props removed before the first flight.
- Confirm values in the receiver tab before moving on to rates or PID tuning.
A clean receiver setup makes every other part of the build easier.
When Betaflight reads your inputs correctly, you get predictable control, simpler troubleshooting, and fewer surprises in the air.
Useful Terms to Know
- Betaflight: Open-source flight controller firmware used on FPV drones.
- UART: A serial port used for receiver communication.
- CRSF: A low-latency protocol used by Crossfire and ExpressLRS.
- SBUS: A serial protocol common in FrSky systems.
- Endpoints: The low, center, and high signal values from your transmitter.
- Aux channel: A non-stick channel used for switches and modes.
When you understand how to configure FPV drone receiver tab settings correctly, the rest of the build becomes much more straightforward, from arming and flight modes to failsafe testing and first hover checks.