betaflight/betaflight 4.0.4

Betaflight 4.0.4

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 a typo in CLI help (#8365);
• fixed OSD display of negative GPS coordinates (#8374);
• fixed bug in adjustment ranges when failsafe is active (#8386);
• fixed resource display of UARTs in CLI (#8392);
• fixed build error on targets without ESC sensor support (#8403);
• added missing osd_esc_rpm_freq_pos parameter in CLI (#8404);
• fixed bug affecting SmartAudio 2.1 (#8438);
• fixed bug affecting the detection of FrSky SPI RX (#8441);
• fixed invalid upper limit for filters (#8475);
• fixed MAX7456 OSD support for Unified Targets (#8504);
• fixed return of MAX7456 detection result over MSP (#8505);
• fixed build for targets without support for Dshot, LED_STRIP, and transponder (#8506).

Target Updates:

• removed unneeded configuration for barometer and compass from target SPRACINGF3NEO (#8332);
• added support for MPU6000 gyroscope to target KAKUTEF7 (#8375);
• added support for RacePIT mini to target FF_RACEPIT (#8387);
• fixed bug in gyroscope configuration and added PINIOBOX defaults to target EXF722DUAL (#8449);
• updated defaults and added PINIOBOX defaults to target CLRACINGF4 (#8463);
• updated the hardware configuration for target CLRACINGF7 (#8479).