<<< Update 15/06/2020 >>>
Download
🐝 Betaflight 4.2.0 : link
(Betaflight Configurator 10.7.0)
Release Notes
This release contains all of the changes necessary to support version 4.2 of the Betaflight firmware. If you are using firmware 4.2, it is essential that you upgrade to this version, in order to get support for configuring the new features of 4.2. Please read the ‘Important information when upgrading’ section below. For a list of other new features that were added see ‘New Features’ below.
As an extra, we have included a preview version of the Betaflight Configurator for android that is currently under development. You can install the preview by downloading the .apk file onto your phone and opening it in a file manager, or by navigating to this page on your phone and clicking on the file in this release. Once the development of the android version has been completed it will be made available in the Google Play store.
We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.
If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.
Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.
Important information when upgrading MAC OS
Changes to the security model used in the latest versions of MacOS X 10.14 (Mojave) and 10.15 (Catalina) mean that the operating system will show an error message (‘ »Betaflight Configurator.app » is damaged and can’t be opened. You should move it to the Trash.’) when trying to install the application. To work around this, run the following command in a terminal after installing: sudo xattr -rd com.apple.quarantine /Applications/Betaflight\ Configurator.app.
github.com/betaflight/betaflight/wiki
🐝 Betaflight configurator 4.2.0
Betaflight TX Lua Scripts 1.5.0
CLI Command Reference Betaflight
Click on a command to jump to the relevant documentation page.
MODE DUF CLI = BL
IMPORTANT CLI : DUMP, STATUS, VERSION,
Command |
Description |
|---|---|
1wire <esc> |
passthrough 1wire to the specified esc |
adjrange |
show/set adjustment ranges settings |
aux |
show/set aux settings |
mmix |
design custom motor mixer |
smix |
design custom servo mixer |
color |
configure colors |
defaults |
reset to defaults and reboot |
dump |
print configurable settings in a pastable form |
exit |
|
feature |
list or -val or val |
get |
get variable value |
gpspassthrough |
passthrough gps to serial |
help |
|
led |
configure leds |
map |
mapping of rc channel order |
mixer |
mixer name or list |
mode_color |
configure mode colors |
motor |
get/set motor output value |
play_sound |
index, or none for next |
profile |
index (0 to 2) |
rateprofile |
index (0 to 2) |
rxrange |
configure rx channel ranges (end-points) |
rxfail |
show/set rx failsafe settings |
save |
save and reboot |
serialpassthrough |
serial passthrough mode, reset board to exit |
set |
name=value or blank or * for list |
status |
show system status |
version |
show version |
serial |
configure serial ports |
servo |
configure servos |
sd_info |
sdcard info |
tasks |
show task stats |
Description of arming prevention flags
What each flag means and what you should do to (probably) fix the issue.
This list should be kept up to date with the code in master (armingDisableFlags_e in src/main/fc/runtime_config.h) so can be used to find what flag corresponds to a certain index, however if you run an older version you’d have to check this manually as mentioned above.
| Name | Description | Beep code | Required Actions | |||||
|---|---|---|---|---|---|---|---|---|
| 3.2 | 3.3 | 3.4/3.5 | 4.0 | 4.1 | 4.2+ | |||
NOGYRO |
A gyro was not detected | 1 | 1 | 1 | 1 | 1 | 1 | You may have a hardware failure, if a previous firmware version works then it may be a firmware issue. |
FAILSAFE |
Failsafe is active | 2 | 2 | 2 | 2 | 2 | 2 | Rectify the failure condition and try again. |
RXLOSS(1) |
No valid receiver signal is detected | 3 | 3 | 3 | 3 | 3 | 3 | Your receiver is either faulty or has no link to the transmitter. |
BADRX(1) |
Your receiver has just recovered from receiver failsafe but the arm switch is on | 4 | 4 | 4 | 4 | 4 | 4 | Switch the arm switch off. |
BOXFAILSAFE |
The ‘FAILSAFE’ switch was activated | 5 | 5 | 5 | 5 | 5 | 5 | See FAILSAFE |
RUNAWAY |
Runway Takeoff Prevention has been triggered | 6 | 6 | 6 | 6 | 6 | Disarm to clear this condition. | |
CRASH |
Crash Recovery has been triggered | 7 | 7 | Disarm to clear this condition. | ||||
THROTTLE |
Throttle channel is too high | 6 | 7 | 7 | 7 | 8 | 8 | Lower throttle below min_check. |
ANGLE |
Craft is not level (enough) | 7 | 8 | 8 | 8 | 9 | 9 | Level craft to within small_angle degrees (default 25). |
BOOTGRACE |
Arming too soon after power on | 8 | 9 | 9 | 10 | 10 | 10 | Wait until pwr_on_arm_grace seconds (default 5) have elapsed. |
NOPREARM |
Prearm switch is not activated or prearm has not been toggled after disarm | 9 | 10 | 10 | 10 | 11 | 11 | Toggle the prearm switch. |
LOAD |
System load is too high for safe flight | 10 | 11 | 11 | 11 | 12 | 12 | Revisit configuration and disable features. |
CALIB |
Sensor calibration is still ongoing | 11 | 12 | 12 | 12 | 13 | 13 | Wait for sensor calibration to complete. |
CLI |
CLI is active | 12 | 13 | 13 | 13 | 14 | 14 | Exit the CLI. |
CMS |
CMS (config menu) is Active – over OSD or other display | 13 | 14 | 14 | 14 | 15 | 15 | Exit the CMS (or OSD menu). |
OSD |
OSD menu is active | 14 | 15 | 16 | Exit OSD menu. | |||
BST |
A Black Sheep Telemetry device (TBS Core Pro for example) disarmed and is preventing arming | 15 | 16 | 16 | 15 | 16 | 16 | Refer to the manual for your hardware. |
MSP |
MSP connection is active, probably via Betaflight Configurator | 16 | 17 | 17 | 16 | 17 | 17 | Terminate the Betaflight Configurator connection (disconnect). |
PARALYZE |
Paralyze mode has been activated | 18 | 17 | 18 | 18 | Power cycle/reset FC board. | ||
GPS |
GPS rescue mode is configured but required number of satellites has not been fixed | 19 | 18 | 19 | 19 | Wait for GPS fix, enable arming without GPS fix, or disable GPS rescue mode. | ||
RESCUE_SW |
GPS Rescue switch is in an unsafe position | 19 | 20 | 20 | Turn off the GPS Rescue switch to arm. | |||
RPMFILTER(2) |
Motor RPM-based filtering is not functioning | 21 | 21 | 21 | One or more ESC’s are not supplying valid RPM telemetry. | |||
REBOOT_REQD |
Reboot required | 22 | 22 | Reboot the flight controller for settings changes to take effect. | ||||
DSHOT_BBANG |
DSHOT Bitbang is not working | 23 | 23 | (3) | ||||
NO_ACC_CAL |
Accelerometer calibration required | 24 | Calibrate the accelerometer or disable features that use it | |||||
MOTOR_PROTO |
ESC/Motor Protocol not configured | 25 | Select the ESC/Motor protocol to use on the Configuration tab. | |||||
ARMSWITCH |
Arm switch is in an unsafe position | 17 | 18 | 20 | 21 | 24 | 26 |
Toggle the arm switch to arm. |
[FR] probleme installation BF
Si vous avez un problème comme : *Betafligh 1.7 * » est endommagé et ne peut être ouvert. Vous devriez éjecter l’image disque. »
Ouvrez Applications > Utilitaires > Terminal.
Entrez la commande suivante dans le terminal, suivi de votre mot de passe administrateur lorsque demandé :
sudo spctl –master-disable
Une fois l’installation terminée, retournez dans l’utilitaire Terminal et entrez la commande suivante, suivie de votre mot de passe administrateur lorsqu’il sera demandé :
sudo spctl –master-enable
Allez dans les Preferences Système. > Sécurité et Confidentialité de votre Mac. Cliquez sur le cadenas et entrez votre mot de passe administrateur. Choisissez N’importe où sous Autoriser les applications téléchargée.
