Assets 54

These are F3 board flight performance focused PRE-RELEASE of Betaflight 4.0 - Build betaflight#1222 as per the Betaflight Jenkins Site (https://ci.betaflight.tech/job/Betaflight/changes). If you are looking for F4 or F7 targets, see https://github.com/betaflight/betaflight/releases

These targets add the features:

  1. the Gyro Lowpass2 filter option
  2. Dynamic Lowpass Filters
  3. Throttle Boost
  4. iTerm Relax
  5. RC Smoothing - Filter
  6. LED Strip support for SPracingF3

support to F3 flight controllers. To make flash space available the PWM, SUMD (Graupner Hott), SUMH (Graupner Legacy) and XBUS (JR) receiver protocols were removed along with Servo Control support and some other internal functions. Smart FeedForward was not included in these builds.

Stock features removed varies per F1 and F3 board flash sizes. It really depends on their ROM space and other features of the board; like whether they have a baro or not, etc... OmnibusF3, BetaflightF3, some of the SPracingF3 targets and RCExplorerF3 are the hardest to get things to fit. Stock BF for those target removes things like: RTC_Time (BBL times based on radio time); RX_MSP; ESC_SENSOR_INFO, EXTENDED_CMS_MENUS; etc... (eg.: See --> https://www.screencast.com/t/PJbnv6ak4). Those features are still removed in this release.

See the branch commits for what is defined or not based on the board's flash size. If you type "STATUS" at the CLI, you can see how may Bytes the flash space is on your board (eg: see --> https://www.screencast.com/t/hnVBzx5jikX). Then you can look at the 'Performance Edition Edits' commits (last 2 or 3 commits) and specifically at the 'scr\main\target\common_pre.h' file to see what features are included based on available flash space or not. You will also need to look at your specific target's "target.h" file (under 'scr\main\target[target name]') to see if any feature were specifically "#undef" (undefined) downstream to make it all fit.

See my Playlist: https://www.youtube.com/playlist?list=PLcYNkvInloJFyMqJv0Lue-IsvkXTf_o5x to learn how to build your own targets to include whatever you like in BF or shoot me an email: spatzengr at yahoo.com if you have a question or need help.

See https://github.com/betaflight/betaflight/wiki/Tuning-Tips-for-Betaflight-3.4 and https://github.com/betaflight/betaflight/wiki/3.5-tuning-notes for an explanation of these new features and a tuning guide.

@spatzengr spatzengr released this Sep 14, 2018 · 73 commits to 3.5.x-Performance-Edition since this release

Assets 52

These are F3 board flight performance focused releases of Betaflight 3.5.1. If you are looking for F4 or F7 targets, see https://github.com/betaflight/betaflight/releases

These targets add the features: Smart FeedForward, Throttle Boost, Absolute Control, iTerm Relax, RC Smoothing Filter, Gyro Lowpass2 filtering, Extended CMS menus, RTC time, and ESC Sensor Info. support to F3 flight controllers. To make flash space available the PWM, SUMD (Graupner Hott), SUMH (Graupner Legacy) and XBUS (JR) receiver protocols were removed along with Servo support and some other internal functions.

[Note: stock features removed varies per F1 and F3 boards. a.k.a not all F3 boards have all the above features removed on the stock HEX builds. It really depends on their ROM space and other features of the board; like whether they have a baro or not, etc...]

See https://github.com/betaflight/betaflight/wiki/Tuning-Tips-for-Betaflight-3.4 and https://github.com/betaflight/betaflight/wiki/3.5-tuning-notes for an explanation of these new features and a tuning guide.

@spatzengr spatzengr released this Nov 5, 2018 · 501 commits to master since this release

Assets 52

These are F3 board flight performance focused releases of Betaflight 3.5.2a. What at is the ".2a" part you ask? Whelp, some of the commits between 3.5.2 leading up to the 3.5.3 release are included. If you are looking for F4 or F7 targets, see https://github.com/betaflight/betaflight/releases

These targets add the features: Throttle Boost, iTerm Relax, RC Smoothing Filter, Gyro Lowpass2 filtering, Extended CMS menus, RTC time, and ESC Sensor Info. support to F3 flight controllers. To make flash space available the PWM, SUMD (Graupner Hott), SUMH (Graupner Legacy) and XBUS (JR) receiver protocols were removed along with Servo support and some other internal functions.

Stock features removed varies per F1 and F3 boards. a.k.a not all F3 boards have all the above features removed on the stock HEX builds. It really depends on their ROM space and other features of the board; like whether they have a baro or not, etc... OmnibusF3, BetaflightF3 and some of the SPracingF3 targets are the hardest to get things to fit. See commits for what is included or not. See my Playlist: https://www.youtube.com/playlist?list=PLcYNkvInloJFyMqJv0Lue-IsvkXTf_o5x to learn how to build your own targets to include whatever you like in BF or shoot me an email: spatzengr at yahoo.com if you have a question or need help.

See https://github.com/betaflight/betaflight/wiki/Tuning-Tips-for-Betaflight-3.4 and https://github.com/betaflight/betaflight/wiki/3.5-tuning-notes for an explanation of these new features and a tuning guide.

Sep 10, 2018
Merge remote-tracking branch 'upstream/master'

@spatzengr spatzengr released this Sep 7, 2018 · 527 commits to Master-Performance-Edition since this release

Assets 50

These are F3 board flight performance focused releases of Betaflight 4.0, Build betaflight#1075. If you are looking for F4 or F7 targets, see https://ci.betaflight.tech/job/Betaflight/1075/artifact/obj/

These targets add the features: Smart FeedForward, Throttle Boost, Absolute Control, iTerm Relax, RC Smoothing Filter, Gyro Lowpass2 filtering, Extended CMS menus, RTC time, and ESC Sensor Info. support to F3 flight controllers. To make flash space available the PWM, SUMD (Graupner Hott), SUMH (Graupner Legacy) and XBUS (JR) receiver protocols were removed along with Servo support.

[Note: stock features removed varies per F1 and F3 boards. a.k.a not all F3 boards have all the above features removed on the stuck HEX builds, it really depends on their ROM space and other features of the board; like whether they have a baro or not, etc...]

See https://github.com/betaflight/betaflight/wiki/Tuning-Tips-for-Betaflight-3.4 and https://github.com/betaflight/betaflight/wiki/3.5-tuning-notes for an explanation of these new features and a tuning guide.