betaflight Betaflight 4.2.0 Release Candidate 3

[WaF Bot]

Important

This is a release candidate. It is intended for testing, and some things still need fixing and fine tuning. Please use it with caution and report back any issues at https://github.com/betaflight/betaflight/issues. Thank you.

Important information when upgrading

• Betaflight 4.2 brings some changes to how targets are downloaded and installed. The latest release of Betaflight Configurator, 10.7.0, contains the changes necessary to support this. For this reason it is important that you update to the version 10.7.0 or newer of Betaflight Configurator (installation instructions here) in order to get the latest version of your targets installed;
• if you are using the Blackbox Explorer, there is an updated version 3.5.0 to go with Betaflight 4.2 (installation instructions here);
• version 1.5.0 of the Betaflight TX lua scripts has been released. This includes changes to go with Betaflight 4.2 (installation instructions here);
• as you have come to expect, there is a detailed Tuning Notes for Betaflight 4.2. Use them, or use the improved tuning sliders in the Betaflight configurator 10.7.0 to get your craft tuned. Please do not paste tuning configurations from previous versions of the firmware. Some defaults have been changed, and some parameters are used in different ways, so previous tuning settings will not work well with Betaflight 4.1 (#8623, #8736);
• after installing new firmware or resetting the configuration, the motor output protocol selected by default is now 'disabled'. This means that the correct motor protocol has to be selected before the craft can be armed. But this also removed the limitation on the maximum possible PID loop speed imposed by the pre-selected legacy protocol (OneShot125) in earlier versions, resulting in the maximum possible PID loop speed for each MCU type being pre-selected. Arming will be disabled and a warning displayed in configurator until a motor output protocol has been selected (#9619);
• when enabling bidirectional Dshot, the maximum possible PID loop speed for Dshot protocols will be reduced by half to accommodate for the time taken by the ESC to send the RPM data packet to the flight controller. In particular, this means that with Dshot300 and bidirectional Dshot, the maximum PID loop speed is 4 kHz (#9642);
• the threshold for activation of the yaw spin recovery feature has had an automatic mode added - this mode sets the threshold to a value that is based on the currently configured maximum yaw rate, with a buffer added on top of it. This new mode is the default for yaw spin threshold, since it provides a setting that is safe to use for most users. Manual configuration of the yaw spin threshold is still possible (#9455);
• accelerometer calibration is now required before arming is allowed if any feature is enabled that requires the accelerometer. This is to prevent situations arising where the craft may try to self-level with an uncalibrated accelerometer, leading to unexpected or dangerous results. Arming will be disabled and a warning displayed in configurator until the accelerometer has been calibrated (#9031);
• the calculation for the virtual current meter device has been changed to be based on the throttle value used in the mixer, instead of the throttle channel RC input. This means that this value has things like throttle limiting and throttle boost applied, resulting in more accurate prediction of current and consumption. If you are using the virtual current meter device, make sure to calibrate it again after updating the firmware to make sure the calibration is still correct (#9153);
• the way that the 'RSSI dBm' value is tracked in the firmware has changed to use actual dBM value in a range of -130 to 0, instead of the previous version's 130 to 0 range. This means that if a custom setting for osd_rssi_dbm_alarm is used, this will have to be changed to be the inversion of its previous value (e.g. 60 becomes -60) (#9550);
• since stick arming is not recommended for multirotor craft because it can lead to accidental disarms, it has been disabled by default. If you want to use stick arming (at your own risk), it has to be enabled by setting enable_stick_arming to on (#9183);
• the name CLI command has been removed. Use set name = <name> instead (#8837).

Major Features:

• completely reworked the gyro loop, improved performance and made it always run at the native speed of the gyro (#9444);
• added new selectable ACTUAL and QUICK rates models (#9495, #9506);
• added compensation for sagging battery voltage, resulting in more consistent throttle / PID behaviour over for the entire flight time (#9561);
• Added level race mode ('NFE race mode' in Silverware) (#9481).

Minor Features:

• added the option to display the OSD logo on arming (#9244);
• added support for enhanced OSD / CMS devices, made it possible to support highligting of text or symbols (#9212);
• added support for FrSkyOSD OSD devices (#9127);
• added support for the Redpine RC protocol on devices with an SPI connected CC2500 chip (FrSky SPI) (#7601).

Changes from the previous Release Candidate:

• fixed incorrect reporting of configured / detected OSD device over MSP (#9807);
• added missing pin ownership checks for I2C (#9810);
• fixed typo in CLI help command (#9816);
• increased the minimum values for gyro_rpm_notch_q and gyro_rpm_notch_q to address problem with too low values causing runaway acceleration (#9841);
• fixed problem with setting negative values in CMS (#9842);
• fixed incorrect value ranges for battery offsets in CMS (#9849);
• fixed connection loss problems for ublox GPS (#9850).

Lire la source