cleanflight | C Ecosystem Directory

Bot releases are hidden (Show)

cleanflight - v4.2.0-RC3 Latest Release

Published by hydra over 4 years ago

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.

cleanflight - v4.2.0-RC2

Published by hydra over 4 years ago

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.

cleanflight - v4.2.0-RC1

Published by hydra over 4 years ago

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).

cleanflight - v2.5.0

Published by hydra almost 6 years ago

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

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 https://github.com/cleanflight/cleanflight/issues/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: https://github.com/cleanflight/cleanflight/issues/3049#issuecomment-405357538

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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.5.0-RC1

Published by hydra about 6 years ago

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

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 https://github.com/cleanflight/cleanflight/issues/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: https://github.com/cleanflight/cleanflight/issues/3049#issuecomment-405357538

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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.4.1

Published by hydra about 6 years ago

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

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 https://github.com/cleanflight/cleanflight/issues/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: https://github.com/cleanflight/cleanflight/issues/3049#issuecomment-405357538

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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.4.0

Published by hydra about 6 years ago

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

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 https://github.com/cleanflight/cleanflight/issues/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: https://github.com/cleanflight/cleanflight/issues/3049#issuecomment-405357538
OSD Slave always says 'Waiting for FC', see https://github.com/cleanflight/cleanflight/pull/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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.4.0-RC1

Published by hydra over 6 years ago

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

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 https://github.com/cleanflight/cleanflight/issues/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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.3.2

Published by hydra over 6 years ago

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

Known Issues:

Enabling Dynamic Filtering on F7 causes lock-up - https://github.com/betaflight/betaflight/issues/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 https://github.com/cleanflight/cleanflight/issues/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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.3.1

Published by hydra over 6 years ago

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

Known Issues:

Enabling Dynamic Filtering on F7 causes lock-up - https://github.com/betaflight/betaflight/issues/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 https://github.com/cleanflight/cleanflight/issues/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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.3.0

Published by hydra over 6 years ago

Cleanflight v2.3.0

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

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:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

Known Issues:

Enabling Dynamic Filtering on F7 causes lock-up - https://github.com/betaflight/betaflight/issues/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 https://github.com/cleanflight/cleanflight/issues/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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.3.0-RC1

Published by hydra over 6 years ago

Cleanflight v2.3.0-RC1

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

Changes since v2.2.0:

Flight performance enhanced.
Many many many other changes and performance enhancements.
Changes from Betaflight 3.3 merged.
Improvements for OSD slave.

Notes:

Some features are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.
OSD Slave users should upgrade both the FC and their OSD Slave.

Known Issues:

Enabling Dynamic Filtering on F7 causes lock-up - https://github.com/betaflight/betaflight/issues/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 https://github.com/cleanflight/cleanflight/issues/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:

Flash CF > v2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

cleanflight - v2.2.0

Published by hydra over 6 years ago

Cleanflight v2.2.0

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

Changes since v2.2.0-RC2:

Add support for SPRACINGF7DUAL with DUAL SIMULTANEOUS GYROS.

Changes since v2.2.0-RC1:

Various bug fixes.
Support for additional targets.

Changes since v2.1.0:

Flight performance enhanced.
Many many many other changes and performance enhancements.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.

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 https://github.com/cleanflight/cleanflight/issues/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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

Bug Reports ONLY:

https://github.com/cleanflight/cleanflight/issues/2972

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

cleanflight - v2.2.0-RC2

Published by hydra over 6 years ago

Cleanflight v2.2.0-RC2

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

Changes since v2.2.0-RC1:

Various bug fixes.
Support for additional targets.

Changes since v2.1.0:

Flight performance enhanced.
Many many many other changes and performance enhancements.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.

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 https://github.com/cleanflight/cleanflight/issues/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 in late 2017.

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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

Bug Reports ONLY:

https://github.com/cleanflight/cleanflight/issues/2972

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

cleanflight - v2.2.0-RC1

Published by hydra almost 7 years ago

Cleanflight v2.2.0-RC1

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

Changes since v2.1.0:

Flight performance enhanced.
Many many many other changes and performance enhancements.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.

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 https://github.com/cleanflight/cleanflight/issues/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 in late 2017.

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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

Bug Reports ONLY:

https://github.com/cleanflight/cleanflight/issues/2972

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

cleanflight - v2.1.0

Published by hydra about 7 years ago

Cleanflight v2.1.0

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

Changes since v2.0.x:

Flight performance enhanced.
Dynamic PID filtering - enable via cli feature DYNAMIC_FILTER.
Many OSD improvements.
Crash detection and recovery (see cli commands).
LED Strip can now show VTX frequency and other VTX settings.
RunCam SPLIT camera control.
EasyRaceLapTimer (ERLT) transponder support - CF now supports 3 IR transponder protocols.
SPRacingF3OSD/PDB current sensor can now be used by the FC, set the current sensor source in the FC to 'MSP sensor/OSD Slave'.
DSHOT ESC 1200 support.
PROSHOT ESC 1000 support.
Many CMS (Configuration menu system) improvements.
Support for many new targets.
Many many many other changes and performance enhancements.

Changes since v2.1.0-RC1:

Synced motor output twitches fixed.
Other minor fixes and improvements.

Changes since v2.1.0-RC2:

Fixed SPRACINGF3OSD SPI initialisiation.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disabled for some older targets like the NAZE32 and other targets with 256K flash or less. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.

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 https://github.com/cleanflight/cleanflight/issues/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 in late 2017.

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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

Bug Reports ONLY:

https://github.com/cleanflight/cleanflight/issues/2885

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

cleanflight - v2.1.0-RC2

Published by hydra over 7 years ago

Cleanflight v2.1.0-RC2

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

Changes since v2.0.x:

Flight performance enhanced.
Dynamic PID filtering - enable via cli feature DYNAMIC_FILTER.
Many OSD improvements.
Crash detection and recovery (see cli commands).
LED Strip can now show VTX frequency and other VTX settings.
RunCam SPLIT camera control.
EasyRaceLapTimer (ERLT) transponder support - CF now supports 3 IR transponder protocols.
SPRacingF3OSD/PDB current sensor can now be used by the FC, set the current sensor source in the FC to 'MSP sensor/OSD Slave'.
DSHOT ESC 1200 support.
PROSHOT ESC 1000 support.
Many CMS (Configuration menu system) improvements.
Support for many new targets.
Many many many other changes and performance enhancements.

Changes since v2.1.0-RC1:

Oneshot twitch fixed.
Other minor fixes and improvements.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disabled for some older targets like the NAZE32. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.

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 https://github.com/cleanflight/cleanflight/issues/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 in late 2017.

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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

Bug Reports ONLY:

https://github.com/cleanflight/cleanflight/issues/2885

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

cleanflight - v2.1.0-RC1

Published by hydra over 7 years ago

Cleanflight v2.1.0-RC1

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

Changes since v2.0.x:

Flight performance enhanced.
Dynamic PID filtering - enable via cli feature DYNAMIC_FILTER.
Many OSD improvements.
Crash detection and recovery (see cli commands).
LED Strip can now show VTX frequency and other VTX settings.
RunCam SPLIT camera control.
EasyRaceLapTimer (ERLT) transponder support - CF now supports 3 IR transponder protocols.
SPRacingF3OSD/PDB current sensor can now be used by the FC, set the current sensor source in the FC to 'MSP sensor/OSD Slave'.
DSHOT ESC 1200 support.
PROSHOT ESC 1000 support.
Many CMS (Configuration menu system) improvements.
Support for many new targets.
Many many many other changes and performance enhancements.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disabled for some older targets like the NAZE32. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md
OSD users should use the latest font from the latest configurator.

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 https://github.com/cleanflight/cleanflight/issues/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.
Oneshot output has jitter, fixed in v2.1.0-RC2

Future:

Cleanflight will end support for F1 based boards in late 2017.

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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Set the current sensor source to "MSP sensor/OSD Slave"
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

Bug Reports ONLY:

https://github.com/cleanflight/cleanflight/issues/2885

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

cleanflight - v2.0.5

Published by hydra over 7 years ago

Cleanflight v2.0.5

Latest Cleanflight Configurator >= v2.0.0 is required.

Changes since v2.0.5:

Fix servo filter initialisation.
SPRACINGF4NEO - Stabilise VBAT readings.

Changes since v2.0.3:

SPRACINGF4NEO - Enable faster updates for OSD.

Changes since v2.0.2:

SPRACINGF4NEO - Initial target support for the first F4 board from Seriously Pro / SP Racing.
HoTT telemetry fix.

Changes since v2.0.1:

RSSI via MSP fixed.
NAZE32 Rev5/6 use dataflash for blackbox by default.
SPRACINGF3NEO change default telemetry settings to support the XSR receiver.
Fix HoTT telemetry. See https://github.com/cleanflight/cleanflight/issues/2745.
Change 'sport_halfduplex' to 'tlm_halfduplex' to allow experimental support of one-wire HoTT.

Changes since v2.0.0:

SPRacingF3NEO button features implemented. See VTX section of the manual.
All VTXs can now be configured using OSD menu, sticks or buttons on any FC, e.g. use sticks to change VTX channels on Tramp/SmartAudio or Built-in VTX.
SPRacingF3 now supports connection to OSD Slave, note - uses low refresh rate while unarmed.
Other minor fixes.

Features:

SPRacingF4EVO - Initial target support for the first F4 board from Seriously Pro / SP Racing.
New OSD SLAVE SYSTEM. Remote display of Cleanflight OSD screen and menus on the SPRACINGF3OSD boards.
All the new latest features from Betaflight. (DSHOT, new PID controller, etc).
All the fixes and improvements you expect from Cleanflight.
ARCITIMER Transponder support.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disables for some legacy F1 targets like the NAZE32. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md

Known Issues:

Manual needs updating, volunteers wanted!
SPRacingF3OSD/PDB board sensors are unused, wait for v2.1.0 - OSD slave only.
The mixer setting in the configurator may not have any effect. See https://github.com/cleanflight/cleanflight/issues/2764 - configure a custom mixer and use the mmix cli command, see manual.

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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
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

Bug Reports ONLY:

https://github.com/cleanflight/cleanflight/issues/2720

Thanks:

All contributors, especially the core CF/BF developers.

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

cleanflight - v2.0.4

Published by hydra over 7 years ago

Cleanflight v2.0.4

Latest Cleanflight Configurator >= v2.0.0 is required.

Changes since v2.0.3:

SPRACINGF4NEO - Enable faster updates for OSD.

Changes since v2.0.2:

SPRACINGF4NEO - Initial target support for the first F4 board from Seriously Pro / SP Racing.
HoTT telemetry fix.

Changes since v2.0.1:

RSSI via MSP fixed.
NAZE32 Rev5/6 use dataflash for blackbox by default.
SPRACINGF3NEO change default telemetry settings to support the XSR receiver.
Fix HoTT telemetry. See https://github.com/cleanflight/cleanflight/issues/2745.
Change 'sport_halfduplex' to 'tlm_halfduplex' to allow experimental support of one-wire HoTT.

Changes since v2.0.0:

SPRacingF3NEO button features implemented. See VTX section of the manual.
All VTXs can now be configured using OSD menu, sticks or buttons on any FC, e.g. use sticks to change VTX channels on Tramp/SmartAudio or Built-in VTX.
SPRacingF3 now supports connection to OSD Slave, note - uses low refresh rate while unarmed.
Other minor fixes.

Features:

SPRacingF4EVO - Initial target support for the first F4 board from Seriously Pro / SP Racing.
New OSD SLAVE SYSTEM. Remote display of Cleanflight OSD screen and menus on the SPRACINGF3OSD boards.
All the new latest features from Betaflight. (DSHOT, new PID controller, etc).
All the fixes and improvements you expect from Cleanflight.
ARCITIMER Transponder support.

Notes:

Mag and Baro disabled by default for maximum flight performance.
Default ESC protocol in CF2.x is ONESHOT, not PWM - see SAFETY NOTE.
Some features, like GPS and SONAR, are disables for some legacy F1 targets like the NAZE32. See https://github.com/cleanflight/cleanflight/blob/master/docs/Customized%20Version.md

Known Issues:

Manual needs updating, volunteers wanted!
SPRacingF3OSD/PDB board sensors are unused, wait for v2.1.0 - OSD slave only.
The mixer setting in the configurator may not have any effect. See https://github.com/cleanflight/cleanflight/issues/2764 - configure a custom mixer and use the mmix cli command, see manual.

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:

Flash CF2.x onto a compatible stacking FC (SPRACINGF3, SPRACINGF4EVO, SPRACINGF3EVO).
Enable OSD feature on the FC.
Enable MSP on UART1 on the FC.
Flash CF2.x onto the SPRACINGF3OSD/PDB board.
Upload Cleanflight font to the SPRACINGF3OSD using the 'OSD' tab, set video mode.
Connect FC + OSD using stacking pins and power on board boards.
Configure FC as usual.
Access OSD menu using sticks by following on-screen prompts. (Yaw Left, Throttle Mid, Pitch Up)

User Support / Questions / Help: