@mikeller mikeller released this Aug 14, 2018 · 48 commits to master since this release

Assets 142

Wait, there is one more thing we can do to make it better!

This is what we realised about two months ago, as we were preparing for the release of Betaflight 3.4.0. And this is what led to the 'Feed Forward PID controller' being born. But when we came up with it it was already too late to add it to 3.4.0, and it needed some more refinement before it was ready to go out anyway. So we decided to do Betaflight 3.5.0, a release that focuses on more flight improvements. We put the Feed Forward PID controller into it, we have made the dynamic notch filter a whole lot more awesome, and we made improvements to how anti gravity works. Man, all of these improvements show when you fly it!

To get the best out of the flight performance improvements, please read these tuning tips.

If you are upgrading from an earlier version of Betaflight, please read the following section containing a list of things that you might have to change in your configuration.

We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.

We also have a Facebook Group: If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this here.

Happy Props!

Important information when upgrading

  • A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.4.0(installation instructions here), please update your Betaflight configurator to at least this version;
  • if you are using the Blackbox Log Viewer, there is an updated version 3.2.0 to go with Betaflight 3.5 (installation instructions here). Please update to at least version 3.2.0;
  • a new 'Feed Forward PID' algorithm has been implemented, replacing setpoint weight (#6355). In addition to this, the dynamic notch filter (#6411) and anti-gravity (#6220) have been optimised for improved flight performance. For all of these changes, default values have been chosen that should result in good flight characteristics for most setups. It is recommended to start testing with default settings, incorporating tuned settings from previous versions if needed, where needed. For more in-depth instructions for tuning Betaflight 3.5, please consult these notes.
  • unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: CRAZYBEEF3FR, CRAZYBEEF3FS, FRSKYF3, FURYF3, FURYF3OSD, OMNIBUS, SPRACINGF3, SPRACINGF3EVO, SPRACINGF3MINI, SPRACINGF3NEO (#6497, #6501);

Major features:

  • Added support for feed forward to the PID controller (#6355);
  • Improved the performance of the dynamic notch filter (#6411).

Minor features:

  • Improved the performance of anti-gravity (#6220);
  • Added support for linking of modes (#6335);
  • Added support for dynamic filter in dual gyro mode (#6428).

Changes from Release Candidate 2:

Fixes:

  • Fixed altitude display in CRSF telemetry (#6513);
  • Fixed reporting of extended ESC sensor data in SmartPort (#6516);
  • Fixed error in barometer QMP6988 driver (#6523);
  • Fixed detection of crash flip activation when arming is delayed (#6525);
  • Fixed bug on targets without PWM input support (#6549).

Target Updates:

  • Added new target FLYWOOF405 (#6526);
  • Removed target SPRACINGF3OSD (#6529);
  • Changed voltage scaling for DALRCF722DUAL (#6538);
  • Added camera control pin for FF_FORTINIF4_REV03 (#6540).
Pre-release
Pre-release

@mikeller mikeller released this Aug 2, 2018 · 77 commits to master since this release

Assets 141

Important

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

Important information when upgrading

  • A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.4.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.4.0 or better, or use the CLI for now;
  • if you are using the Blackbox Log Viewer, there will be an updated version 3.2.0 to go with Betaflight 3.5 (installation instructions here). Please update as soon as it becomes available;
  • a new 'Feed Forward PID' algorithm has been implemented, replacing setpoint weight (#6355). In addition to this, the dynamic notch filter (#6411) and anti-gravity (#6220) have been optimised for improved flight performance. For all of these changes, default values have been chosen that should result in good flight characteristics for most setups. It is recommended to start testing with default settings, incorporating tuned settings from previous versions if needed, where needed. For more in-depth instructions for tuning Betaflight 3.5, please consult these notes.
  • unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: CRAZYBEEF3FR, CRAZYBEEF3FS, FRSKYF3, FURYF3, FURYF3OSD, OMNIBUS, SPRACINGF3, SPRACINGF3EVO, SPRACINGF3MINI, SPRACINGF3NEO (#6497, #6501);

Major features:

  • Added support for feed forward to the PID controller (#6355);
  • Improved the performance of the dynamic notch filter (#6411).

Minor features:

  • Improved the performance of anti-gravity (#6220);
  • Added support for linking of modes (#6335);
  • Added support for dynamic filter in dual gyro mode (#6428).

Changes from Release Candidate 1:

Fixes:

  • Fixed incorrect voltage and current sensor filter frequencies (#6452, #6466);
  • Fixed check for anti gravity being enabled (#6461);
  • Fixed A-Tail mixer (#6465);
  • Enabled support for the ICM20601 gyro and fixed the output scaling in its driver (#6475);
  • Fixed the loop time calculation when 32 kHz gyro ouptut is used (#6481);
  • Changed the default gyro loop frequency to 2.67 kHz for targets with I2C gyro (#6483);
  • Disabled DYNAMIC_FILTER feature if the gyro loop frequency is less than 2 kHz (#6484);
  • Fixed the parameters for dynamic filter for gyro loop frequencies less than 4 kHz (#6485);
  • Enabled configuration of throttle boost in CMS (#6496, #6503).

Target Updates:

  • Renamed the SKYF405 target to SKYZONEF405 (#6458);
  • Fixed the LED pins for KISSFCV2F7 (#6459);
  • Enabled SDIO on NUCLEOF722 (#6473);
  • Fixed the feature list for OMNIBUSF4 variants (#6486);
  • Added new target DALRCF722DUAL (#6489);
  • Removed features from F3 to make the firmware fit into flash (#6497, #6501).

@mikeller mikeller released this Aug 2, 2018

Assets 141

Maintenance Release

Please read the Betaflight 3.4 Release Notes.

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

We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.

We now also have a Facebook Group. If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this by joining our Facebook Group.

Important information when upgrading from an earlier version of 3.4

  • unfortunately, bugfixes in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: CRAZYBEEF3FR, CRAZYBEEF3FS, FRSKYF3, FURYF3, FURYF3OSD, OMNIBUS, SPRACINGF3, SPRACINGF3EVO, SPRACINGF3MINI, SPRACINGF3NEO (#6444, #6449, #6497);

Fixes:

  • Fixed the reliability of telemetry on FPort with newer RX firmware (#6098);
  • Fixed the display of warnings when the ESC sensor is enabled (#6339);
  • Fixed task statistics in CLI (#6344);
  • Fixed display corruption in OSD (#6359);
  • Enabled support for the ICM20601 gyro and fixed the output scaling in its driver (#6377, #6475);
  • Fixed problem with unreliable SmartPort telemetry (#6382);
  • Fix early disarming with GPS rescue when sanity checks are enabled (#6392);
  • Fixed compilation error for custom built targets (#6419);
  • Fixed A-Tail mixer (#6423, #6465);
  • Fixed bug in OSD initialisation causing various crashes (#6439);
  • Fixed incorrect disabling of telemetry when Jeti XBUS or Spektrum SRXL are disabled (#6442);
  • Fixed incorrect voltage and current sensor filter frequencies (#6452, #6466);
  • Fixed the loop time calculation when 32 kHz gyro ouptut is used (#6481);
  • Disabled DYNAMIC_FILTER feature if the gyro loop frequency is less than 2 kHz (#6484).

Target Updates:

  • Added new target IRCSYNERGYF3 (#6342);
  • Added support for DShot beacon on AG3X (#6394);
  • Fixed motor 3 and 4 Dshot output on KAKUTEF7 (#6436);
  • Removed features from F3 to make the firmware fit into flash (#6444, #6449, #6497);
  • Fixed I2C support on YUPIF7 (#6446);
  • Renamed the SKYF405 target to SKYZONEF405 (#6458);
  • Fixed the LED pins for KISSFCV2F7 (#6459);
  • Fixed the feature list for OMNIBUSF4 variants (#6486);
  • Added new target DALRCF722DUAL (#6489).
Pre-release

@mikeller mikeller released this Jul 25, 2018 · 123 commits to master since this release

Assets 140

Important

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

Important information when upgrading

  • A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.4.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.4.0 or better, or use the CLI for now;
  • if you are using the Blackbox Log Viewer, there will be an updated version 3.2.0 to go with Betaflight 3.5 (installation instructions here). Please update as soon as it becomes available;
  • a new 'Feed Forward PID' algorithm has been implemented, replacing setpoint weight (#6355). In addition to this, the dynamic notch filter (#6411) and anti-gravity (#6220) have been optimised for improved flight performance. For all of these changes, default values have been chosen that should result in good flight characteristics for most setups. It is recommended to start testing with default settings, incorporating tuned settings from previous versions if needed, where needed. For more in-depth instructions for tuning Betaflight 3.5, please consult these notes.

Major features:

  • Added support for feed forward to the PID controller (#6355);
  • Improved the performance of the dynamic notch filter (#6411).

Minor features:

  • Improved the performance of anti-gravity (#6220);
  • Added support for linking of modes (#6335);
  • Added support for dynamic filter in dual gyro mode (#6428).

@mikeller mikeller released this Jul 8, 2018 · 290 commits to master since this release

Assets 139

Version 3.4.0: The best Betaflight ever!

We recognise that most of our users just want to two things with new firmware: Install it, and then go fly it. That's why we have spent a lot of time on working out default settings that fly great on most quads. Just install it and try for yourself! To make your craft fly even better, we've added a brand-new, experimental mode to improve the response to stick input by filtering it instead of interpolating. For more info on setting up 3.4 to optimise flight performance, read these notes.

We've also put a lot of effort into optimising the performance of the firmware, especially for boards with an F7 MCU. Now you can go and buy that shiny new F7 board, while your friends still struggle with their boards with F3 and F4. 😉

For pilots who are into long range flying, we have added the brand new 'GPS Rescue' mode. It is a simplified version of the 'return to home' mode that exists in other, more navigation oriented firmware, and the great news is that all it needs to work is a GPS, no fiddling to make a compass work required!

Last but not least, we've also added a bunch of new features to improve the convenience of using Betaflight: You can now copy / paste your logs from an SD card or the on board flash chip by mounting the flight controller as a storage device, and you can use your flight controller / TX to emulate a joystick with no extra hardware needed, in order to fly on a simulator.

If you are upgrading from an earlier version of Betaflight, please read the following section containing a list of things that you might have to change in your configuration.

We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.

We now also have a Facebook Group. If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this by joining our Facebook Group.

Happy Props!

Important information when upgrading

  • A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.3.1 (installation instructions here). Please update your Betaflight configurator to version 10.3.1. If you are using the Blackbox Log Viewer, there is an updated version 3.1.0 to go with Betaflight 3.4 (installation instructions here);
  • as part of the overhaul of the various filter stages, and improvements to the PID loop, the default settings have been re-evaluated and updated. The new default values are designed to make optimal use of the new filtering and improved PID loop, and be flyable with (almost) any hardware. Even if your current set up is working ok, it is probably worthwhile to try and only restore the non-filtering / PID loop settings, and have a go with the new default values (store your old diff in a safe place, just in case you don't like the new values 😉). (#6036);
  • also as part of the filtering overhaul, the names of the debug modes available to log filtering / tuning data have been improved NOTCH (gyro data after scaling, before filtering) is now GYRO_SCALED, GYRO (gyro data after all filtering has been applied) is now GYRO_FILTERED (#6059);
  • the upper limit of dterm_setpoint_weight has been increased to 2000 (corresponding to a value of 20 for 'D Setpoint Weight' in Betaflight configurator). This means that pilots wanting a more 'locked in' stick feeling can increase this value beyond the previous maximum of 254. At the same time, an undocumented scaling change was reverted, and the scale is now again how it is described in the Betaflight configurator. If you are using a custom setting for dterm_setpoint_weight, divide your value by 1.27 to get the new value that will give you the same feeling as between 3.1.6 and 3.4.0 (#5945, #6052);
  • Dshot beacon configuraton has been changed. Now the beacon CLI command can be used analogous to how the beeper command is used. This allows for the Dshot beacon to be disabled individually for the conditions that are supported by it (RX_SET and RX_LOST at the moment). The old way of disabling the Dshot beacon by setting beeper_dshot_beacon_tone to 0 is no longer supported. The Dshot beacon is disabled for all conditions by default, if you want to enable it, use beacon <condition name|ALL> in CLI (#5891, #6070);
  • in previous versions of the firmware, there was a race condition that could cause Dshot commands (e.g. activation of crash flip) to be ignored by the ESC when the Dshot beacon was active. To prevent this, a timeout has been added to the Dshot beacon that prevents arming for 1.2 seconds after the Dshot beacon was active (#6079);
  • validation has been added for the RSSI configuration. Unlike in previous versions, it is no longer possible to have multiple sources for RSSI configured simultaneously, since only one can be active at any one time. If you have got more than one of the supported RSSI sources (frame error count / ADC / RX channel) configured, all but the first on this list will be disabled (#5644);
  • scaling has been added to all RSSI sources. If the RSSI mechanism that you are using does not give you the output range that you want for RSSI, you can now use the rssi_scale / rssi_offset CLI variables to set the scale and offset for RSSI (#6001, #6032);
  • the functionality of the crash flip mode has been improved: In addition to the existing front / back / left / right spinning of 2 propellers, it now supports spinning only 1 propeller (by moving the roll / pitch stick diagonally), and spinning 2 props that are diagonally opposite (by moving yaw), in order to yaw the overturned craft. The largest stick deflection in any of these directions determines which properllers are spun (#5163);
  • the setting moron_threshold for the acceptable noise limit during gyro calibration was renamed to gyro_calib_noise_limit. Additionally, a new setting gyro_calib_duration was added. This allows users to configure a longer minimum gyro calibration duration (in 1/10ths of seconds, default: 125). Using a larger setting here will result in reduced gyro drift, which is helpful when flying line of sight (#5932);
  • unfortunately bugfixes and improvements in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: BETAFLIGHTF3, COLIBRI_RACE, FRSKYF3, FURYF3OSD, LUX_RACE, MIDELICF3, OMNIBUS, RCEXPLORERF3, RG_SSD_F3, SPRACINGF3EVO, SPRACINGF3NEO;
  • the OSD elements osd_crosshairs (crosshairs) and osd_ah_sbar (artificial horizon sidebar) have been renamed in CLI to osd_crosshairs_pos and osd_ah_sbar_pos to make them consistent with the naming of OSD elements. If you are using these elements, please manually change the names in your backup before restoring (#5534);
  • the range of the vtx_band parameter in CLI was extended to start at 0 instead of 1. Setting vtx_band = 0 allows users of VTX using the SmartPort or Tramp protocols to set the desired frequency directly via the vtx_freq parameter. Since direct frequency setting is not supported by the RTC6705 (onboard) VTX driver vtx_band = 0 does not work for these VTX, and should not be used (#5465).

Major features:

  • Overhauled and improved filtering (#5391, #5458);
  • Optimised and massively improved the performance on F7 (#5674);
  • Added GPS rescue mode (#5753, #5764);
  • Added support for accessing SD card / onboard flash as USB mass storage device (MSC) (#5443, #5629, #5650);
  • Added support for reading RC input as USB joystick (HID) (#5478, #5596);
  • Added support for CMS configuration over CRSF (#5743);
  • Added support for experimental filter based RC channel smoothing (#6017).

Minor features:

  • Added acro trainer mode (#5970);
  • Added throttle boost mode (#5508);
  • Added support for throttle limiting (#5608);
  • Added PID loop improvements (#5968, #5963, #5962);
  • Added support for accelerated yaw spin recovery (#5706);
  • Added support for direct adjustment of PID values through an RC channel (#5584);
  • Added support for multiple overclocking speeds (#5193);
  • Added MCU temperature monitoring (#5322);
  • Added paralyse mode (#5851);
  • Added support for QMC5883L compass (#5309);
  • Added support for W25M flash chips (#5722).

New targets:

  • Added SPRACINGF7DUAL with dual gyro support (#5264).

Changes from Release Candidate 5:

Fixes:

  • Fixed Frsky D SPI RX frame rate detection (#6279);
  • Fixed lockup in CLI on 'smix reverse' (#6280);
  • Fixed lockup in CMS menu for CRSF (#6286);
  • Fixed immediate rearming after landing / abort in 'GPS_RESCUE' mode (#6291);
  • Fixed problem with initialisation of telemetry data if ESC sensor is unavailable (#6292);
  • Added a warning if rc smoothing initialization has not completed when arming (#6299);
  • Fixed frame received detection logic for SmartPort (#6300).

Target updates:

  • Fixed target YUPIF7 (6271).
Pre-release

@mikeller mikeller released this Jul 2, 2018 · 310 commits to master since this release

Assets 139

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 any bugs you find back to us by opening an issue at https://github.com/betaflight/betaflight/issues. Thank you.

Important information when upgrading

  • A number of changes and improvements in this release require changes to the Betaflight configurator. These changes have been added to Betaflight configurator 10.3.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.3.0 or better, or use the CLI for now;
  • as part of the overhaul of the various filter stages, and improvements to the PID loop, the default settings have been re-evaluated and updated. The new default values are designed to make optimal use of the new filtering and improved PID loop, and be flyable with (almost) any hardware. Even if your current set up is working ok, it is probably worthwhile to try and only restore the non-filtering / PID loop settings, and have a go with the new default values (store your old diff in a safe place, just in case you don't like the new values 😉). More detailed tips for tuning 3.4 can be found here (#6036);
  • also as part of the filtering overhaul, the names of the debug modes available to log filtering / tuning data have been improved NOTCH (gyro data after scaling, before filtering) is now GYRO_SCALED, GYRO (gyro data after all filtering has been applied) is now GYRO_FILTERED (#6059);
  • the upper limit of dterm_setpoint_weight has been increased to 2000 (corresponding to a value of 20 for 'D Setpoint Weight' in Betaflight configurator). This means that pilots wanting a more 'locked in' stick feeling can increase this value beyond the previous maximum of 254. At the same time, an undocumented scaling change was reverted, and the scale is now again how it is described in the Betaflight configurator. If you are using a custom setting for dterm_setpoint_weight, divide your value by 1.27 to get the new value that will give you the same feeling as between 3.1.6 and 3.4.0 (#5945, #6052);
  • Dshot beacon configuraton has been changed. Now the beacon CLI command can be used analogous to how the beeper command is used. This allows for the Dshot beacon to be disabled individually for the conditions that are supported by it (RX_SET and RX_LOST at the moment). The old way of disabling the Dshot beacon by setting beeper_dshot_beacon_tone to 0 is no longer supported. The Dshot beacon is disabled for all conditions by default, if you want to enable it, use beacon <condition name|ALL> in CLI (#5891, #6070);
  • in previous versions of the firmware, there was a race condition that could cause Dshot commands (e.g. activation of crash flip) to be ignored by the ESC when the Dshot beacon was active. To prevent this, a timeout has been added to the Dshot beacon that prevents arming for 2 seconds after the Dshot beacon was active (#6079);
  • validation has been added for the RSSI configuration. Unlike in previous versions, it is no longer possible to have multiple sources for RSSI configured simultaneously, since only one can be active at any one time. If you have got more than one of the supported RSSI sources (frame error count / ADC / RX channel) configured, all but the first on this list will be disabled (#5644);
  • scaling has been added to all RSSI sources. If the RSSI mechanism that you are using does not give you the output range that you want for RSSI, you can now use the rssi_scale / rssi_offset CLI variables to set the scale and offset for RSSI (#6001, #6032);
  • the functionality of the crash flip mode has been improved: In addition to the existing front / back / left / right spinning of 2 propellers, it now supports spinning only 1 propeller (by moving the roll / pitch stick diagonally), and spinning 2 props that are diagonally opposite (by moving yaw), in order to yaw the overturned craft. The largest stick deflection in any of these directions determines which properllers are spun (#5163);
  • the setting moron_threshold for the acceptable noise limit during gyro calibration was renamed to gyro_calib_noise_limit. Additionally, a new setting gyro_calib_duration was added. This allows users to configure a longer minimum gyro calibration duration (in 1/109ths of seconds, default: 125). Using a larger setting here will result in reduced gyro drift, which is helpful when flying line of sight (#5932);
  • unfortunately bugfixes and improvements in the flight controller core functionality have led to an increase of the firmware size, causing it to overflow the available space on a number of F3 based flight controllers. As a result, some features have had to be removed from a number of F3 based flight controllers in order to make the firmware fit into flash. The following targets are affected: BETAFLIGHTF3, COLIBRI_RACE, FRSKYF3, FURYF3OSD, LUX_RACE, MIDELICF3, OMNIBUS, RCEXPLORERF3, RG_SSD_F3, SPRACINGF3EVO, SPRACINGF3NEO;
  • the OSD elements osd_crosshairs (crosshairs) and osd_ah_sbar (artificial horizon sidebar) have been renamed in CLI to osd_crosshairs_pos and osd_ah_sbar_pos to make them consistent with the naming of OSD elements. If you are using these elements, please manually change the names in your backup before restoring (#5534);
  • the range of the vtx_band parameter in CLI was extended to start at 0 instead of 1. Setting vtx_band = 0 allows users of VTX using the SmartPort or Tramp protocols to set the desired frequency directly via the vtx_freq parameter. Since direct frequency setting is not supported by the RTC6705 (onboard) VTX driver vtx_band = 0 does not work for these VTX, and should not be used (#5465).

Major features:

  • Overhauled and improved filtering (#5391, #5458);
  • Optimised and massively improved the performance on F7 (#5674);
  • Added GPS rescue mode (#5753, #5764);
  • Added support for accessing SD card / onboard flash as USB mass storage device (MSC) (#5443, #5629, #5650);
  • Added support for reading RC input as USB joystick (HID) (#5478, #5596);
  • Added support for CMS configuration over CRSF (#5743);
  • Added support for experimental filter based RC channel smoothing (#6017).

Minor features:

  • Added acro trainer mode (#5970);
  • Added throttle boost mode (#5508);
  • Added support for throttle limiting (#5608);
  • Added PID loop improvements (#5968, #5963, #5962);
  • Added support for accelerated yaw spin recovery (#5706);
  • Added support for direct adjustment of PID values through an RC channel (#5584);
  • Added support for multiple overclocking speeds (#5193);
  • Added MCU temperature monitoring (#5322);
  • Added paralyse mode (#5851);
  • Added support for QMC5883L compass (#5309);
  • Added support for W25M flash chips (#5722).

New targets:

  • Added SPRACINGF7DUAL with dual gyro support (#5264).

Changes from Release Candidate 4:

Fixes:

  • Fixed RC smoothing issues with slow protocols (PPM), and RC filtering issues with Crossfire (#6259);
  • Fixed issues with lock ups on the OSD statistics screen for boards without a flash chip (#6261).
Pre-release

@mikeller mikeller released this Jul 1, 2018 · 314 commits to master since this release

Assets 139