Skip to content

Releases: cleanflight/cleanflight

v4.2.0-RC3

04 Jun 00:06
@hydra hydra
CLFL_v4.2.0-RC3
2663768
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.2.0-RC3 Pre-release
Pre-release

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/cleanflight/cleanflight/issues. Thank you.

Important information when upgrading

  • Cleanflight 4.2 brings some changes to how targets are downloaded and installed. The latest release of Cleanflight Configurator, 2.6.0, contains the changes necessary to support this. For this reason it is important that you update to the version 2.6.0 or newer of Cleanflight Configurator (installation instructions here) in order to get the latest version of your targets installed;
  • if you are using the Blackbox Explorer, there will be an updated version 3.5.0 to go with Cleanflight 4.2 (installation instructions here);
  • version 1.5.0 of the Cleanflight TX lua scripts will be released soon. This includes changes to go with Cleanflight 4.2 (installation instructions here);
  • 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 Cleanflight 4.2;
  • 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;
  • 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;
  • 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;
  • 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;
  • 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;
  • 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);
  • 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;
  • the name CLI command has been removed. Use set name = <name> instead.

Major Features:

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

Minor Features:

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

Changes from the previous Release Candidate:

  • fixed problem with corrupted blackbox headers when logging to SD card;
  • fixed reporting of altitude in MSP with a GPS;
  • made custom defaults persist through reflashing the firmware on STM32F745;
  • fixed parsing of pin names in CLI;
  • fixed processing of rangefinder output;
  • enabled the recalculation of mode switch box availability when reading the configuration;
  • fixed error when parsing over length fields in custom default headers in CLI.
Assets 21

v4.2.0-RC2

31 May 17:45
@hydra hydra
CLFL_v4.2.0-RC2
a361279
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v4.2.0-RC2 Pre-release
Pre-release

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/cleanflight/cleanflight/issues. Thank you.

Important information when upgrading

  • Cleanflight 4.2 brings some changes to how targets are downloaded and installed. The latest release of Cleanflight Configurator, 2.6.0, contains the changes necessary to support this. For this reason it is important that you update to the version 2.6.0 or newer of Cleanflight Configurator (installation instructions here) in order to get the latest version of your targets installed;
  • if you are using the Blackbox Explorer, there will be an updated version 3.5.0 to go with Cleanflight 4.2 (installation instructions here);
  • version 1.5.0 of the Cleanflight TX lua scripts will be released soon. This includes changes to go with Cleanflight 4.2 (installation instructions here);
  • 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 Cleanflight 4.1;
  • 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;
  • 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;
  • 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;
  • 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;
  • 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;
  • 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);
  • 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;
  • the name CLI command has been removed. Use set name = <name> instead.

Major Features:

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

Minor Features:

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

Changes from the previous Release Candidate:

  • fixed incorrect reporting of configured / detected OSD device over MSPl;
  • added missing pin ownership checks for I2C;
  • fixed typo in CLI help command;
  • increased the minimum values for gyro_rpm_notch_q and dterm_rpm_notch_q to address problem with too low values causing runaway acceleration;
  • fixed problem with setting negative values in CMS;
  • fixed incorrect value ranges for battery offsets in CMS;
  • fixed connection loss problems for ublox GPS.
Assets 21

v4.2.0-RC1

21 May 18:18
@hydra hydra
CLFL_v4.2.0-RC1
244710e
Compare
Choose a tag to compare
v4.2.0-RC1 Pre-release
Pre-release

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/cleanflight/cleanflight/issues. Thank you.

Important information when upgrading

  • Cleanflight 4.2 brings some changes to how targets are downloaded and installed. The latest release of Cleanflight Configurator, 2.6.0, contains the changes necessary to support this. For this reason it is important that you update to the version 2.6.0 or newer of Cleanflight Configurator (installation instructions here) in order to get the latest version of your targets installed;
  • if you are using the Blackbox Explorer, there will be an updated version 3.5.0 to go with Cleanflight 4.2 (installation instructions here);
  • version 1.5.0 of the Cleanflight TX lua scripts will be released soon. This includes changes to go with Cleanflight 4.2 (installation instructions here);
  • 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 Cleanflight 4.1;
  • 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;
  • 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;
  • 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;
  • 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;
  • 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;
  • 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);
  • 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;
  • the name CLI command has been removed. Use set name = <name> instead.

Major Features:

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

Minor Features:

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

v2.5.0

10 Jan 16:51
@hydra hydra
CLFL_v2.5.0
08348b7
Compare
Choose a tag to compare
v2.5.0 Latest
Latest

Cleanflight v2.5.0

Latest Cleanflight Configurator >= v2.5.0-RC1 is required.

Changes since v2.5.0-RC1:

  • None

Changes since v2.4.1:

  • Added support for feed forward to the PID controller.
  • Improved the performance of the dynamic notch filter.
  • Changes from Betaflight 3.5.2 merged - see Betaflight release notes for details.

Notes:

Known Issues:

  • Manual needs updating, volunteers wanted!
  • If you encounter issues with your settings not being correct after upgrading to the RC please report this via the feedback issue, then reset your settings and continue testing.
  • The mixer setting in the configurator may not have any effect. See #2764 - configure a custom mixer and use the mmix cli command, see manual.
  • Motors outputs need to be configured as servo outputs before using servos via the cli resource command.
  • Use of motor outputs 5-8 on SPRacingF7DUAL requires 'NO_VTX' firmware, get it here: #3049 (comment)

Future:

  • Cleanflight will end support for F1 based boards soon.

SAFETY:

  • When upgrading follow this simple procedure: Disconnect battery, remove propellers, flash/upgrade, configure, connect battery, test rx, test motors, test arming - only then should you re-attach your propellers.

OSD Slave usage:

  1. Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
  2. Enable OSD feature on the FC.
  3. Enable MSP on UART1 on the FC.
  4. Flash CF2.x onto the SPRACINGF3OSD/PDB board.
  5. Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
  6. Connect FC + OSD using stacking pins and power on board boards.
  7. Configure FC as usual.
  8. Set the current sensor source to "MSP sensor/OSD Slave"
  9. Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help:

  • Slack, Forums, Documentation, Facebook, IRC, BetaFlight WIKI

Thanks:

  • All contributors, especially the core CF/BF developers.
  • Everyone that has donated to the Cleanflight project.

All configurator versions are available here:
https://github.com/cleanflight/cleanflight-configurator/releases

Assets 153

v2.5.0-RC1

01 Oct 03:41
@hydra hydra
CLFL_v2.5.0-RC1
08348b7
Compare
Choose a tag to compare
v2.5.0-RC1 Pre-release
Pre-release

Cleanflight v2.5.0-RC1

Latest Cleanflight Configurator >= v2.5.0-RC1 is required.

Changes since v2.4.1:

  • Added support for feed forward to the PID controller.
  • Improved the performance of the dynamic notch filter.
  • Changes from Betaflight 3.5.2 merged - see Betaflight release notes for details.

Notes:

Known Issues:

  • Manual needs updating, volunteers wanted!
  • If you encounter issues with your settings not being correct after upgrading to the RC please report this via the feedback issue, then reset your settings and continue testing.
  • The mixer setting in the configurator may not have any effect. See #2764 - configure a custom mixer and use the mmix cli command, see manual.
  • Motors outputs need to be configured as servo outputs before using servos via the cli resource command.
  • Use of motor outputs 5-8 on SPRacingF7DUAL requires 'NO_VTX' firmware, get it here: #3049 (comment)

Future:

  • Cleanflight will end support for F1 based boards soon.

SAFETY:

  • When upgrading follow this simple procedure: Disconnect battery, remove propellers, flash/upgrade, configure, connect battery, test rx, test motors, test arming - only then should you re-attach your propellers.

OSD Slave usage:

  1. Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
  2. Enable OSD feature on the FC.
  3. Enable MSP on UART1 on the FC.
  4. Flash CF2.x onto the SPRACINGF3OSD/PDB board.
  5. Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
  6. Connect FC + OSD using stacking pins and power on board boards.
  7. Configure FC as usual.
  8. Set the current sensor source to "MSP sensor/OSD Slave"
  9. Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help:

  • Slack, Forums, Documentation, Facebook, IRC, BetaFlight WIKI

Thanks:

  • All contributors, especially the core CF/BF developers.
  • Everyone that has donated to the Cleanflight project.

All configurator versions are available here:
https://github.com/cleanflight/cleanflight-configurator/releases

Assets 149

v2.4.1

07 Aug 18:51
@hydra hydra
CLFL_v2.4.1
35fa38f
Compare
Choose a tag to compare
v2.4.1

Cleanflight v2.4.1

Latest Cleanflight Configurator >= v2.4.0-RC1 is required.

Changes since v2.4.0:

  • Fixed SPRACINGF3OSD slave 'Waiting for FC'.

Changes since v2.4.0-RC1:

  • None, if you have flashed v2.4.0-RC1 you do not need to re-flash.

Changes since v2.3.2:

  • Enhanced flight performance.
  • Changes from Betaflight 3.4 merged.

Notes:

Known Issues:

  • Manual needs updating, volunteers wanted!
  • If you encounter issues with your settings not being correct after upgrading to the RC please report this via the feedback issue, then reset your settings and continue testing.
  • The mixer setting in the configurator may not have any effect. See #2764 - configure a custom mixer and use the mmix cli command, see manual.
  • Motors outputs need to be configured as servo outputs before using servos via the cli resource command.
  • Use of motor outputs 5-8 on SPRacingF7DUAL requires 'NO_VTX' firmware, get it here: #3049 (comment)

Future:

  • Cleanflight will end support for F1 based boards soon.

SAFETY:

  • When upgrading follow this simple procedure: Disconnect battery, remove propellers, flash/upgrade, configure, connect battery, test rx, test motors, test arming - only then should you re-attach your propellers.

OSD Slave usage:

  1. Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
  2. Enable OSD feature on the FC.
  3. Enable MSP on UART1 on the FC.
  4. Flash CF2.x onto the SPRACINGF3OSD/PDB board.
  5. Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
  6. Connect FC + OSD using stacking pins and power on board boards.
  7. Configure FC as usual.
  8. Set the current sensor source to "MSP sensor/OSD Slave"
  9. Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help:

  • Slack, Forums, Documentation, Facebook, IRC, BetaFlight WIKI

Thanks:

  • All contributors, especially the core CF/BF developers.
  • Everyone that has donated to the Cleanflight project.

All configurator versions are available here:
https://github.com/cleanflight/cleanflight-configurator/releases

Assets 3

v2.4.0

07 Aug 14:24
@hydra hydra
CLFL_v2.4.0
9b9a778
Compare
Choose a tag to compare
v2.4.0

Cleanflight v2.4.0

Latest Cleanflight Configurator >= v2.4.0-RC1 is required.

Changes since v2.4.0-RC1:

  • None, if you have flashed v2.4.0-RC1 you do not need to re-flash.

Changes since v2.3.2:

  • Enhanced flight performance.
  • Changes from Betaflight 3.4 merged.

Notes:

Known Issues:

  • Manual needs updating, volunteers wanted!
  • If you encounter issues with your settings not being correct after upgrading to the RC please report this via the feedback issue, then reset your settings and continue testing.
  • The mixer setting in the configurator may not have any effect. See #2764 - configure a custom mixer and use the mmix cli command, see manual.
  • Motors outputs need to be configured as servo outputs before using servos via the cli resource command.
  • Use of motor outputs 5-8 on SPRacingF7DUAL requires 'NO_VTX' firmware, get it here: #3049 (comment)
  • OSD Slave always says 'Waiting for FC', see #3062

Future:

  • Cleanflight will end support for F1 based boards soon.

SAFETY:

  • When upgrading follow this simple procedure: Disconnect battery, remove propellers, flash/upgrade, configure, connect battery, test rx, test motors, test arming - only then should you re-attach your propellers.

OSD Slave usage:

  1. Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
  2. Enable OSD feature on the FC.
  3. Enable MSP on UART1 on the FC.
  4. Flash CF2.x onto the SPRACINGF3OSD/PDB board.
  5. Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
  6. Connect FC + OSD using stacking pins and power on board boards.
  7. Configure FC as usual.
  8. Set the current sensor source to "MSP sensor/OSD Slave"
  9. Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help:

  • Slack, Forums, Documentation, Facebook, IRC, BetaFlight WIKI

Thanks:

  • All contributors, especially the core CF/BF developers.
  • Everyone that has donated to the Cleanflight project.

All configurator versions are available here:
https://github.com/cleanflight/cleanflight-configurator/releases

Assets 148

v2.4.0-RC1

16 Jul 18:18
@hydra hydra
CLFL_v2.4.0-RC1
9b9a778
Compare
Choose a tag to compare
v2.4.0-RC1 Pre-release
Pre-release

Cleanflight v2.4.0

Latest Cleanflight Configurator >= v2.4.0-RC1 is required.

Changes since v2.3.2:

  • Enhanced flight performance.
  • Changes from Betaflight 3.4 merged.

Notes:

Known Issues:

  • Manual needs updating, volunteers wanted!
  • If you encounter issues with your settings not being correct after upgrading to the RC please report this via the feedback issue, then reset your settings and continue testing.
  • The mixer setting in the configurator may not have any effect. See #2764 - configure a custom mixer and use the mmix cli command, see manual.
  • Motors outputs need to be configured as servo outputs before using servos via the cli resource command.

Future:

  • Cleanflight will end support for F1 based boards soon.

SAFETY:

  • When upgrading follow this simple procedure: Disconnect battery, remove propellers, flash/upgrade, configure, connect battery, test rx, test motors, test arming - only then should you re-attach your propellers.

OSD Slave usage:

  1. Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
  2. Enable OSD feature on the FC.
  3. Enable MSP on UART1 on the FC.
  4. Flash CF2.x onto the SPRACINGF3OSD/PDB board.
  5. Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
  6. Connect FC + OSD using stacking pins and power on board boards.
  7. Configure FC as usual.
  8. Set the current sensor source to "MSP sensor/OSD Slave"
  9. Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help:

  • Slack, Forums, Documentation, Facebook, IRC, BetaFlight WIKI

Thanks:

  • All contributors, especially the core CF/BF developers.
  • Everyone that has donated to the Cleanflight project.

All configurator versions are available here:
https://github.com/cleanflight/cleanflight-configurator/releases

Assets 147

v2.3.2

22 Apr 21:53
@hydra hydra
CLFL_v2.3.2
208d4cc
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v2.3.2

Cleanflight v2.3.2

Latest Cleanflight Configurator >= v2.2.0-RC1 is required.

Changes since v2.3.1:

  • Fix PWM RX 100% cpu usage issue.

Changes since v2.3.0:

  • Fix missing transponder support for SPRacingF7DUAL.

Changes since v2.2.0:

  • Flight performance enhanced.
  • Added PID-Audio feature.
  • Many many many other changes and performance enhancements.
  • Changes from Betaflight 3.3 merged.
  • Improvements for OSD slave.

Notes:

Known Issues:

  • Enabling Dynamic Filtering on F7 causes lock-up - betaflight/betaflight#5429
  • Manual needs updating, volunteers wanted!
  • If you encounter issues with your settings not being correct after upgrading to the RC please report this via the feedback issue, then reset your settings and continue testing.
  • The mixer setting in the configurator may not have any effect. See #2764 - configure a custom mixer and use the mmix cli command, see manual.
  • Motors outputs need to be configured as servo outputs before using servos via the cli resource command.

Future:

  • Cleanflight will end support for F1 based boards soon.

SAFETY:

  • When upgrading follow this simple procedure: Disconnect battery, remove propellers, flash/upgrade, configure, connect battery, test rx, test motors, test arming - only then should you re-attach your propellers.

OSD Slave usage:

  1. Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
  2. Enable OSD feature on the FC.
  3. Enable MSP on UART1 on the FC.
  4. Flash CF2.x onto the SPRACINGF3OSD/PDB board.
  5. Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
  6. Connect FC + OSD using stacking pins and power on board boards.
  7. Configure FC as usual.
  8. Set the current sensor source to "MSP sensor/OSD Slave"
  9. Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help:

  • Slack, Forums, Documentation, Facebook, IRC, BetaFlight WIKI

Thanks:

  • All contributors, especially the core CF/BF developers.
  • Everyone that has donated to the Cleanflight project.

All configurator versions are available here:
https://github.com/cleanflight/cleanflight-configurator/releases

Assets 131

v2.3.1

03 Apr 19:42
@hydra hydra
CLFL_v2.3.1
38d1f44
Compare
Choose a tag to compare
v2.3.1

Cleanflight v2.3.1

Latest Cleanflight Configurator >= v2.2.0-RC1 is required.

Changes since v2.3.0:

  • Fix missing transponder support for SPRacingF7DUAL.

Changes since v2.2.0:

  • Flight performance enhanced.
  • Added PID-Audio feature.
  • Many many many other changes and performance enhancements.
  • Changes from Betaflight 3.3 merged.
  • Improvements for OSD slave.

Notes:

Known Issues:

  • Enabling Dynamic Filtering on F7 causes lock-up - betaflight/betaflight#5429
  • Manual needs updating, volunteers wanted!
  • If you encounter issues with your settings not being correct after upgrading to the RC please report this via the feedback issue, then reset your settings and continue testing.
  • The mixer setting in the configurator may not have any effect. See #2764 - configure a custom mixer and use the mmix cli command, see manual.
  • Motors outputs need to be configured as servo outputs before using servos via the cli resource command.

Future:

  • Cleanflight will end support for F1 based boards soon.

SAFETY:

  • When upgrading follow this simple procedure: Disconnect battery, remove propellers, flash/upgrade, configure, connect battery, test rx, test motors, test arming - only then should you re-attach your propellers.

OSD Slave usage:

  1. Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
  2. Enable OSD feature on the FC.
  3. Enable MSP on UART1 on the FC.
  4. Flash CF2.x onto the SPRACINGF3OSD/PDB board.
  5. Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
  6. Connect FC + OSD using stacking pins and power on board boards.
  7. Configure FC as usual.
  8. Set the current sensor source to "MSP sensor/OSD Slave"
  9. Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help:

  • Slack, Forums, Documentation, Facebook, IRC, BetaFlight WIKI

Thanks:

  • All contributors, especially the core CF/BF developers.
  • Everyone that has donated to the Cleanflight project.

All configurator versions are available here:
https://github.com/cleanflight/cleanflight-configurator/releases

Assets 3