betaflight/betaflight 4.0.6

Betaflight 4.0.6

on GitHub

Maintenance Release

Please read the Betaflight 4.0 Release Notes.

This release contains bugfixes and target changes only. For a full list of new features see 4.0.0.

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 from an earlier version of 4.0

• a number of users reported issues with their craft taking off with throttle at idle when running on Betaflight 4.0.0's default settings. It was identified that the default settings did not have enough filtering for setups with a lot of vibrations. More filtering was added to the defaults in 4.0.1. It is recommended that you upgrade directly to 4.0.1 or newer, to eliminate the risk of unintended flyaways introduced by this problem (#8043);
• Betaflight 4.0.1 has a bug that is affecting all F3 based flight controllers, stopping them from working. A fix for this bug is included in 4.0.2. Users with F3 based flight controllers should upgrade directly to 4.0.2 or newer (#8148);
• the format of the CLI timer command that is used to configure a timer has been changed. It now uses the alternate function index that is also used in the hardware manufacturer's reference documentation: timer <pin> af<alternate function>. The format that was introduced with Betaflight 4.0.0 that used an arbitrary option number (timer <pin> <option>) is deprecated and will be dropped in Betaflight 4.1 (#8305, #8306, #8320);
• unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: AIORACERF3 (#8178).

Fixes:

• fixed formatting and help text of vtxtable in CLI (#8646, #8663);
• made SD card report as 'not supported' on targets with no configured SD card slot (#8656);
• fixed the UART pin definitions for STM32F411 (#8659);
• fixed compilation errors if USE_ABSOLUTE_CONTROL if defined but USE_ITERM_RELAX is not (#8683);
• fixed incorrect reporting of SD card capacity (#8703);
• fixed lockups in FrSky SPI RX when using SmartPort telemetry (#8702);
• fixed lockup when trying to use Dshot with missing DMA assignments (#8705);
• fixed display of date / time when no valid time is set (#8731);
• fixed compilation warning when USE_TASK_STATISTICS is not defined (#8765, #8782).

Target Updates:

• added new targets MERAKRCF405 and MERAKRCF722 (#8621);
• added new target MAMBAF411 (#8644);
• added target HAKRCF411 to Betaflight 4.0 (#8655);
• added barometer support for target FURYF4OSD (#8771);
• added new target TMOTORF7 (#8776).