Betaflight Basics for iFlight BNF DronesUpdated 2 months ago

iFlight BNF drones are delivered with a complete factory Betaflight configuration. In most cases, customers do not need to change Betaflight settings except for personal preferences such as Modes, Rates, OSD layout, or channel mapping.

Changing firmware, presets, UARTs, receiver protocols, motor settings, or PID/filter values without knowing the correct setup can cause serious issues.

Important before changing anything

Before making any changes in Betaflight:

Save a backup of your current configuration
Do not flash firmware unless necessary
Do not apply random presets
Do not change UARTs unless you know which device is connected
Do not change receiver protocol unless your receiver system changed
Do not change motor direction, motor order, or board orientation unless you are troubleshooting a specific issue

Incorrect Betaflight settings can cause:

No receiver input
RXLOSS
No OSD
Wrong motor order
Drone flips on takeoff
DJI or ELRS not working
GPS Rescue not working
Flight controller sensors not detected

Backup your configuration first

Before making changes, create a backup.

Recommended methods:

Open Betaflight Configurator
Connect the flight controller
Go to the Presets tab and save a backup if available
Or open CLI and enter:

1diff all

Copy and save the output as a text file.

For a full backup, you may also save:

1dump

Keep this file safe. It may be needed to restore your drone later.

Should I update Betaflight firmware?

In most cases: No, not unless there is a specific reason.

Do not update Betaflight just because a newer version exists.

Firmware updates may require:

Correct flight controller target
Correct board configuration
Correct factory presets
Correct UART setup
Correct receiver protocol
Correct motor mapping
Correct OSD setup

Flashing the wrong firmware target or losing the factory configuration can make the drone unusable until it is restored correctly.

Only update Betaflight if:

iFlight support recommends it
You need a specific firmware feature
You know the correct target and configuration
You have saved a working backup
You have access to the correct iFlight factory preset or dump

Connecting to Betaflight

To connect your drone:

Remove all propellers
Use a data-capable USB cable
Connect the flight controller to your computer
Open Betaflight Configurator
Select the correct COM port
Click Connect

If no COM port appears, the most common causes are:

Charge-only USB cable
Missing driver
USB hub issue
Wrong USB port
DFU mode
Damaged USB connector

Please check our separate “Flight Controller not detected / no COM port” article for detailed troubleshooting.

Safe settings customers may adjust

For most users, only these settings should be changed:

Modes

You may assign switches for:

ARM
ANGLE
HORIZON
BEEPER
TURTLE MODE / FLIP OVER AFTER CRASH
GPS RESCUE, if configured correctly

Always verify that the correct switch range activates the intended mode.

Rates

Rates can be adjusted to personal preference.

Change rates gradually and test carefully.

OSD

You may adjust the OSD layout and select which information appears in your goggles, such as:

Battery voltage
Flight time
Link quality
RSSI dBm
Warnings
GPS satellites
Flight mode

Receiver channel map

If stick movements appear on the wrong channels, check the channel map, commonly:

AETR
TAER

Do not change receiver protocol unless you know your receiver system.

Motor testing

Do not test motors by arming the drone on the table and raising throttle.

This is not a reliable bench test. With Air Mode and stabilization active, motors may continue spinning fast without propellers because Betaflight is trying to stabilize the drone without normal aerodynamic feedback.

The correct way to test motors is the Betaflight Motors tab:

Remove all propellers
Open the Motors tab
Confirm the safety warning
Test motors individually at low RPM

Use this only for short, controlled tests.

Do not run motors at high RPM without propellers for extended periods.

Receiver settings

Do not change receiver settings unless you know which receiver system your drone uses.

Common examples:

ELRS: CRSF
TBS Crossfire: CRSF
DJI Remote Controller: SBUS or SBUS_FAST, depending on setup
FrSky: SBUS

Changing receiver protocol or UART settings incorrectly can cause no stick input or RXLOSS.

DJI, ELRS, and UART settings

Do not randomly change UARTs.

UART settings control connected devices such as:

Receiver
DJI Air Unit
GPS
ESC telemetry
VTX control

Changing the wrong UART can break receiver input, OSD, GPS, or DJI control.

If you changed UARTs and something stopped working, restore your backup or use the correct iFlight factory preset.

PID tuning and filters

PID and filter tuning should only be changed by experienced users.

Incorrect PID or filter settings can cause:

Oscillations
Hot motors
Poor flight behavior
Desync
Instability
Crash risk

For iFlight BNF drones, factory PID and filter settings are already configured for the intended setup.

GPS Rescue

GPS Rescue must be configured carefully and tested safely.

It is not a guaranteed return-to-home system.

Incorrect GPS Rescue settings can cause unsafe behavior. Do not enable or modify GPS Rescue unless you understand the required settings and limitations.

If something stopped working after changes

If your drone stopped working after changing Betaflight settings:

Do not continue changing random settings
Save screenshots of your current configuration
Restore your saved backup if available
Use the correct iFlight factory preset or dump
Contact support if you are unsure

Before contacting support

Please collect:

Order number
Drone model
Flight controller model
Betaflight version
Description of what was changed
Screenshot of the Ports tab
Screenshot of the Receiver tab
Screenshot of the Modes tab
CLI diff all output
Photos of wiring if hardware was changed

Contact our support team at:

[email protected]

Was this article helpful?

Yes