Betaflight Versionen und Updates

  • Seit zwei Tagen ist BF 3.5 final:
    https://github.com/betaflight/betaflight/releases


    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).
  • Hi Leute ich bin wieder zurück zu Betaflight gewechselt und bin sehr zufrieden allerdings hatte ich heute fast ein Flyaway... Ich hatte zu Hause alle Failsafe Situationen getestet soweit alles ok. Jetzt war es so das ich merkte das es zum Bodenkontakt kommen wird und ich war mir eigentlich sicher das ich sofort Entarmed hatte irgendwie hat er nach dem Bogenkontakt einen Satz gemacht und steigt im ungünstig Winkel richtig Richtung Bäume ich konnte noch gegenlenken hatte aber kaum Kontrolle ...war so perplex in dem Augenblick weil ich so ne Reaktion vom Copter noch nie hatte. Kann das mit dem Discovery ( oder wie das nennt) zu tun haben?Wie kann ich das abstellen?Gruß Marc

  • Moin zusammen die Version 3.5.2 ist verfügbar:
    https://github.com/betaflight/betaflight/releases


    Safety Improvements

    • Added HEADFREE indicator to the OSD flight mode and warnings display elements (#6877).

    Fixes:

    • Fixed bug in anti windup protection (#6721);
    • Fixed bug in iterm relax (#6726);
    • Fixed Spektrum SRXL bug (#6743, #6899);
    • Fixed zero throttle deadband when using switched 3D modes (#6798);
    • Fixed bug causing an inactive telemetry port to be registered as a displayport (#6764);
    • Fixed bug in RSSI settings logging (#6806);
    • Fixed RunCam device support (#6810);
    • Fixed bugs in dual gyro support (#6844);
    • Fixed bug in XN297 driver (#6863);
    • Fixed bug in gyro overflow / yaw-spin logic (#6864);
    • Fixed bug causing lockups when an inserted SD card is not ready (#6882);
    • Cleanup of receiver protocols (#6905);
    • Fixed build warning in SmartPort code (#6907);
    • Fixed bug in CLI causing lockups (#6913);
    • Cleanup of telemetry protocols (#6918);
    • Fixed bug affecting stick arming (#6934).

    Target Updates:

    • Fixed MAG orientation on YUPIF7 (#6720);
    • Added camera control pin on DALRCF722DUAL (#6765);
    • Moved default for battery meter source to board config on STM32F7X2 (#6774);
    • Added new target SPEDIXF4 (#6779);
    • Added new target UAVPNG030MINI (#6781);
    • Added new target CRAZYBEEF3DX, updated CRAZYBEEF3FR, CRAZYBEEF3FS (#6790);
    • Fixed broken settings on AG3X, UAVPNG030MINI (#6794);
    • Added camera control pin on SPRACINGF7DUAL (#6800);
    • Fixed broken RSSI input pin on multiple targets (#6813);
    • Fixed broken ESC serial driver on WORMFC (#6819);
    • Fixed broken ESC serial driver on STM32F4DISCOVERY (#6820);
    • Fixed broken ESC serial driver on NOX (#6821);
    • Fixed broken ESC serial driver on MIDELICF3 (#6824);
    • Fixed missing default voltage meter source on KISSFCV2F7, MOTOLABF4 (#6827);
    • Fixed list of available pins on OMNIBUSF4FW (#6890);
    • Fixed broken I2C pins on FLYWOOF405 (#6912);
    • Re-added removed features on multiple targets (#6930).
  • https://github.com/betaflight/betaflight/releases


    Important information when upgrading from an earlier version of 3.5

    • a number of users reported issues with the firmware hanging during a diff or dump. The root cause of this was identified as a bug in the MSP protocol causing corrupted configurations. This was fixed in 3.5.1. If you are using 3.5.0, it is recommended that you upgrade to at least 3.5.1, to eliminate the risk of experiencing lockups during diff or dump caused by this bug (#6696);
    • 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: AIORACERF3, FRSKYF3, RACEBASE, RMDO, SPRACINGF3, SPRACINGF3MINI, SPRACINGF3NEO, and ZCOREF3 (#6815, #6887, #6994).

    Fixes:

    • Fixed problematic configuration settings for OSD causing malfunctions (#6971, #6974);
    • Fixed problem with MOTOR_STOP and auto-disarm activating when GPS Rescue is active (#6979);
    • Fixed incorrect throttle offset in airmode (#6981);
    • Fixed build error when USE_CMS is not defined (#7007);
    • Fixed garbled 'map' command defaults output in CLI (#7023);
    • Fixed smartport timeout issue (#7051);
    • Fixed error in flash detection when no flash chip is found (#7080);
    • Fixed bug when OSD and dashboard are both enabled (#7086).

    Target Updates:

    • Fixed SD card configuration for target F4BY (#6951);
    • Removed USE_LED_STRIP from individual targets (#6953);
    • Fixed camera control and LED_STRIP pin configuration for target FORTINIF4 (#6961);
    • Fixed motor and PWM pins for target HAKRCF722 (#6968);
    • Added MPU6000 support for target SKYZONEF405 (#6972);
    • Added new target FOXEERF722DUAL (#6976);
    • Fixed flash overflow for targets AIORACERF3, FRSKYF3, RMDO, SPRACINGF3, SPRACINGF3MINI, and ZCOREF3 (#6994);
    • Added new target MATEKF722SE (#7025);
    • Added new target HAKRCF405 (#7053);
    • Added new target PIRXF4 (#7020).
  • Hallo was Speicher ich denn am besten im Cli wenn ich die Firmware updat.Mit Diff fehlt mir irgendwie immer was. Und alles abspeichern wäre ja nicht so schlau dann brauch ich ja nicht upzudaten ...

    Hi,


    schau mal eins drüber... das muss wohl nen bug bei 3.5.0 gewesen sein... Das Problem mit diff und dump sollte ab 3.5.1 behoben sein.

  • Laut der Beschreibung oben, das hier:


    a number of users reported issues with the firmware hanging during a diff or dump. The root cause of this was identified as a bug in the MSP protocol causing corrupted configurations. This was fixed in 3.5.1. If you are using 3.5.0, it is recommended that you upgrade to at least 3.5.1, to eliminate the risk of experiencing lockups during diff or dump caused by this bug (#6696);


    Hatte ich aber persönlich keine Probleme


  • Moin zuammen,


    seit dem 17.12.18 ist die 3.5.4 verfügbar:

    Fixes:

    • Fixed MSC mode issues affecting MacOS (#7145);
    • Fixed 'looping' issue in SmartAudio when setting the frequency (#7157);
    • Fixed issues with retry after save in SmartPort / FPort lua scripts (#7182);
    • Fixed order of magnitude in GPS altitude reporting in SmartPort / FPort (#7200).

    Target Updates:

    • Added new target FLYWOOF7DUAL (#7098);
    • Added I2C support, removed non-working blackbox flash support on target CLRACINGF7 (#7175);
    • Added new target OMNIBUSF4V6 (#7129, #7230);
    • Added new target EXF722DUAL (#7184).
  • Version 3.5.5 ist raus:


    https://github.com/betaflight/betaflight/releases


    Fixes:

    • Fixed OSD temperature display for negative temperatures (#6973);
    • Fixed switching of PID profiles with stick commands (#7218);
    • Fixed potential error when printing configurations in CLI (#7232);
    • Added resetting of the GPS rescue maximum altitude and distance on arming (#7244);
    • Fixed a problem with the sanity checks in GPS rescue causing sporadic disarms (#7254, #7265));
    • Fixed on-board flash MSC emulation for MacOS on F7 (#7266);
    • Fixed sporadic twitching in FrSky X SPI when sending failsafe values from the TX side (#7345);
    • Hide stale altitude and vario in OSD when GPS fix is lost (#7368);
    • Check that a MSC capable storage device is selected for blackbox before rebooting into MSC emulation mode from CLI (#7380);
    • Fixed a boot loop if rebooting into MSC emulation mode and the storage device is not ready (#7382).

    Target Updates:

    • Fixed the pin assignment for the softserial 'TLM' pad on KISSCC (#7149);
    • Fixed a flash overflow on IMPULSERCF3 (#7239);
    • Updated STM32F3DISCOVERY to support the on-board gyro and acc (#7241);
    • Added a CAMERA_CONTROL_PIN on DALRCF722DUAL (#7248);
    • Added support for on-board flash on MATEKF722SE (#7257);
    • Added new targets CRAZYBEEF4FR, CRAZYBEEF4FS, and CRAZYBEEF4DX (#7263);
    • Added new target STM32F411DISCOVERY (#7289);
    • Added new target ELINF405 (#7296);
    • Added new target RUSHCORE7 (#7338);
    • Added new target FF_RACEPIT (#7344);
    • Added pin for pinio use on PYRODRONEF4 (#7389).
  • Betaflight 3.5.6 ist draußen und ja smartaudio 2.1 ist mit dabei. Darauf werden wohl die Meisten gewartet haben:

    https://github.com/betaflight/betaflight/releases

    Fixes:

    • Fixed build errors when building without support for blackbox (#7399);
    • Added validation for the existence of the selected blackbox device (#7400);
    • Fixed build errors when building without support for the 4 way ESC boot loader (#7409);
    • Made OSD available when building without support for CMS (#7410, #7576);
    • Fixed bug in serial driver on F4 (#7431);
    • Fixed the color range for the LED_STRIP when displaying battery voltage or RSSI (#7460);
    • Fixed bug in onboard flash initialisation (#7470);
    • Fixed bug in pinio initialisation causing the first switching event to be ignored (#7492);
    • Added error message when attempting to set invalid PID / rate profile in CLI (#7519);
    • Added support for connecting to SmartAudio 2.1 devices (#7461);
    • Fixed bug in USB driver on F7 (#7563).

    Target Updates:

    • Added new target JHEF7DUAL (#7398);
    • Added new target HAKRCF411 (#7425);
    • Fixed flash overflow on AIORACERF3 (#7527);
    • Added support for the Airbot Omnibus NanoV7 to the OMNIBUSF4V6 target (#7545).
  • Betaflight ist in der 4.0RC1 verfügbar. Nicht vergessen auch die GUI upzudaten...


    https://github.com/betaflight/betaflight/releases


    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.5.0 (to be released in the coming days, installation instructions here). Please update your Betaflight configurator to version 10.5.0 (or newer) as soon as it is available, or use the CLI for now;
    • if you are using the Blackbox Log Viewer, there will be an updated version 3.3.0 to go with Betaflight 4.0 (installation instructions here). Please update as soon as it becomes available;
    • there was a fix to how the min_check 'zero throttle' dead zone is applied. Before the fix, the dead zone was essentially doubled. In order to retain the same range for the 'zero throttle' dead zone, you need to double the amount of dead zone configured in min_check (offset from 1000). For users who have set a very small dead zone, this might lead to the dead zone never being reached with the fixed version, not allowing them to arm with a 'THROTTLE' reason even if throttle is at minimum - if you are getting this, increase your min_check (#7463);
    • there is a new 'Stick Overlay' OSD element that shows an overlay of the current stick positions. In order to use it, the font loaded onto the OSD needs to be updated to the latest version (available in configurator 10.5.0 or newer) (#7476);
    • the functionality of the 'crash flip arrow' OSD element was extended to activate as well when the craft is not in crash flip mode, but small_angle is set, and the craft is unarmed and tilted more than small_angle. This is to show pilots that they won't be able to arm from the current orientation, and allow them to activate crash flip mode and then right their craft (#7250);
    • As part of a consolidation of the CLI commands used to manage resources, the resource list subcommand was renamed into resource show. This aligns it with the new dam show and timer show commands (#7712);
    • the following parameters were renamed to more closely match their function: p_level => angle_level_strength, i_level => horizon_level_strength, d_level => horizon_transition (#6673);
    • 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 almost all F3 based flight controllers. As a result, features have had to be removed from all but a few of the currently supported F3 based flight controllers. Some of the affected targets are: AIORACERF3, BETAFLIGHTF3, CHEBUZZF3, CRAZYBEEF3FR, FURYF3, FURYF3OSD, IMPULSERCF3, LUX_RACE, LUXV2_RACE, MIDELICF3, OMNIBUS, RACEBASE, RMDO, SIRINFPV, SPRACINGF3, SPRACINGF3MINI, SPRACINGF3NEO, STM32F3DISCOVERY (#6900, #6955, #7037, #7038, #7045, #7306, #7381, #7392, #7402, #7421, #7501, #7508, #7518);
    • in addition to the above point, the following features had to be removed from all F3 based flight controllers in order to make the firmware fit into flash: Smart Feedforward, support for flashing / configuration of SimonK based ESCs (#7272, #7274, #7391);
    • support for status display through LED strips was removed from F3 based flight controllers, in order to be able to reclaim some flash space. In its place, LED Strip Profiles (except for the 'Status' profile which is not supported on F3) can be used to set LED strips to fixed colours. LED strip profiles are also available on F4 / F7, to enable simple configuration of the LED strip in OSD (#7485);
    • since the above three measures proved to be insufficient to keep flash space from overflowing on F3 based flight controllers, a system of classifying F3 based flight controllers into a number of 'feature cut' levels, and removing features according from them according to their level were introduced. This was used to reduce the number of features built into most F3 based flight controllers even more (#7429).

    Major features:

    • real time ESC RPM feedback, and notch filtering based on motor RPM (#7264, #7271);
    • d term management with D_min (#7373, #7538);
    • throttle based dynamic gyro and dterm filterig (#6943);
    • launch control (#6992);
    • switchable OSD profiles (#6714);
    • SPI attached Spektrum RX (#7210);
    • unified targets (#5824, #6837, #7620).

    Minor features:

    • cascaded dynamic notches (#7078);
    • thrust linearisation (#7304);
    • integrated yaw control (#6432);
    • switchable LED_STRIP profiles (#7303);
    • stick overlays in OSD (#7167);
    • profile switching based on battery cell count (#7516);
    • support for the Futaba SFHSS protocol on CC2500 (FrSky SPI) hardware (#6865);
    • EU LBT mode for the FrSky SPI RX (#7339);
    • support for STM32F765xx based flight controllers (#6669).
    • configuration over HoTT telemetry (#6224).
  • Gerade gesehen, das wir inzwischen schon bei der 4.0 bei RC6 sind....


    Changes from Release Candidate 5:

    Fixes:

    • fixed the gyro detection for multi gyro setups (#7914);
    • fixed setting of non-working low pass defaults when Betaflight configurator 10.4 is used (#7918);
    • fixed CMS over CRSF (#7919).

    Target Updates:

    • updated the configuration for target JHEF7DUAL for Betaflight 4.0 (#7906);
    • updated the configuration for target SYNERGYF4 for Betaflight 4.0 (#7913).