If someone in Betaflight can fix this issue it would be great. The connect icon is grayed out and won't let me connect anymore.Hopefully there is a way to get this working again for us chrome users. Was this review helpful? PROJECT MOCKINGBIRD v4 for NBD BBLITE. PMB v4 for Betaflight 4.0.x is the first tune and setup for Betaflight 4.0, and introduces Integrated Yaw for even more control in Angle mode and delivers the same performance you had in 3.5.7 and more! New in Betaflight 4.2 Overview. Betaflight 4.2 Loop Rate Optimization. Betaflight 4.2 and Betaflight Configurator 10.7 Features Review. BAD TX Rate AND Betaflight 4.2 Settings to Improve. OpenTX ADC Filter: Disabling for Smoother Sticks. Betaflight Actual Rates Quick Rates & EmuFlight Dynamic Rates. Betaflight 7' Quad Tuning (6',7',10' etc.

What is CLI ?

CLI is abbreviation of the a Command Line Interface. It is special configuration mode where commands are given insted of the dedicated setting controls and inputs. Every flight controllers firmware configurator (Cleanflight, Betaflight, Butterflight, iNav, etc) has this mode. It is useful for more specific change of settings and detailed configuration the Flight Controller. It is also usefur for dumping the whole flight controller configuration, backuping and restoring the settings in the easy way. Read more about it below.

How to use CLI?

In order to start using CLI you have to connect to your flight controller with configurator software (See here how to install the standalone configurator software). Click on the “CLI” tab – this will enable flight controllers CLI mode. Write the command in the input field and hit the [Enter] to execute it.

You need to execute save command if you want all the commands and changes to be saved into Flight Controllers memory. Saving will reboot the flight controller. Close the CLI tab or send the exit command to exit the CLI mode without saving.

CLI Dump or Diff?

dump command dumps all the setting of the flight controller. This can be quite a long list
diff command was introduced in the BetaFlight version 3.0 and it dumps only the settings that are different from the defaults.
diff all command dumps only differencies from the defaults but also dumps all the PID profiles.

It is highly recommended to use diff instead of the dump as it results in the significant smaller settings list and only the ones that were changed or differ from the defaults.

How to Backup/Restore the settings using CLI?

Sometimes it is usefull to save the Flight Controller settings and restore them in case you need. These cases include FC firmware upgrade, restoring the FC to the point where it worked and etc. Backuping and restoring is very simple task.

Backup: Go to CLI, enter diff (or diff all if you have multiple PID profiles) and copy the provided text to anywhere just to save it for later use.

Restore: Go to CLI, paste the saved settings text to the command input field, hit [Enter]. Your FC settings are restored. Don’t forget to save the settings.

CLI commands list

Note that specific command list depends on the type of the firmware (BetaFlight, Butterflight, iNav) and firmware version you are using. For exact list of the commands type help in CLI mode.

Usefull CLI commands

bl or dfu command to enter the DFU mode without pushing the button. Reboots the FC board in bootloader mode.

set small_angle = 180 – sets any angle your quadcopter will be able to arm. Usefull when you land unexpectedly severely angled and you are unable to re-arm.

Betaflight Download

set ledstrip_visual_beeper = ON – When set to on, and the LEDLOW mode is active (i.e. LED strip off), blink the LED strip in synch with beeping, as a visual indicator in cases where the craft is too far away for the beeper to be heard / multiple craft are flying. Values available: [ON,OFF (default)]

Binding with integrated Receivers (connected via SPI):

For Betaflight 4.x – command bind_rx_spi
For Betaflight 3.x: – command frsky_bind
Don’t forget to issue save command after the sucessfull bind.

History:
2018-05-23 – article created
2019-02-13 – Usefull CLI commands updated
2019-07-01 – Usefull CLI commands updated

• Guide: How to Arm, PreArm and start your quad
  What is Arm and why do we need it? All modern quadcopters (or any
• ExpressLRS – Open Source Long Range radio control system – Complete Guide
  ExpressLRS is the Open Source Long Range radio control system, developed by Alessandro Carcione (aka AlessandroAU)

A lot of flight controllers that come with integrated receivers have them connected via SPI to the processor. If you have an AIO flight controller where the receiver is connected via SPI you do not need to push the physical bind button on the flight controller anymore - you can simply bind from the Betaflight CLI.

This is especially handy when the bind button is hard to reach. In the future bind buttons might be omitted on the boards at all - mechanical parts are expensive, so the manufacturers can save a couple of cents.

SPI stands for “Serial Peripheral Interface” and allows multiple devices to use the same serial wires. One device, in this case the MCU, is the master and other devices are the slaves. The communication always happens between the master and one of the slaves, in this case our receiver.

Binding from the Betaflight CLI can be used with a lot of the current brushless whoop AIO boards, for example the Crazybee F4 PRO flight controller - the flightcontroller for the trashcan has its receiver connected via SPI. But also the receiver of the Mobula7 is connected via SPI.

Depending on the Betaflight version you are using, there are different commands to put the receiver into bind mode:

For Betaflight 4.1.x and 4.2.x type

For Betaflight 4.0.x type

into the CLI and hit enter.

The beta version of Betaflight 4.0 used a different command:

So if the first command does nothing, try the second one. I found that a lot of the models that use the Crazybee F4 Pro AIO flight controller have a beta version of Betaflight 4.0 flashed so with those you have to use the bind command.

For Betaflight 3.x type

Betaflight 4.2

into the CLI and hit enter.

This will put your receiver into bind mode - same as pushing the physical button. From here you do everything on your transmitter as you would do it after pushing the button.

Betaflight Configurator

Other Receivers

Betaflight Camera Control

Unfortunately this method only works with SPI receivers, meaning you can not bind your FrSky R-XSR, XM+ or any other SBUS enabled receiver with this command, you will have to use your receivers native binding procedure instead. Usually this involves pressing a button on the receiver while plugging in power to the quadcopter.

Via Graphical User interface

Betaflight Configurator Releases

Betaflight Configurator

In the latest versions of the Betaflight Configurator you can now also activate SPI binding by clicking the “Bind Receiver” button from the “Receiver” tab.