Betaflight Versionen und Updates

  • Betaflight 3.3.0 ist Stabel:
    https://github.com/betaflight/betaflight/releases


    Major features:

    • Added support for the FrSky FPort protocol (#4158);
    • Added Spektrum VTX control (#4434);
    • Added CMS configuration over Spektrum telemetry (#4545);
    • Added FrSky X SPI RX protocol (#4683);
    • Added fast Biquad RC+FIR2 filter (optimised version of Kalman gyro filter in #4890) (#4965);
    • Added Runaway Takeoff Prevention (anti-taz) (#4935).

    Minor features:

    • Added CMS power menu (#3724);
    • Added support for FlySky SPI receiver (#4060);
    • Added use TIM_UP and DMAR for all timer channels with Dshot (#4073, #4843, #4852);
    • Added '3D on a switch' mode (#4227);
    • Added Dshot beacon activation to BEEPER_RX_LOST_LANDING (#4231);
    • Added generic RunCam device protocol support (#4251);
    • Added a reasonable default OSD layout (#4260);
    • Added handling and display of date and time (#4289);
    • Added MSP command to disable arming (#4320);
    • Added support for Spektrum real RSSI from SRXL Rx and fake RSSI from both int and ext bound satellites (#4347);
    • Changed after flight OSD statistics screen to only show when enabled (#4428);
    • Added remaining time estimate based on flight used mAh rate to OSD (#4487, #4543, #4618);
    • Added setting of RSSI value with MSP (#4507);
    • Improved SmartAudio update frequency (make it QuietAudio) (#4532);
    • Updated PID calculations to use actual deltaT (#4556);
    • Added AND logic to modes (#4722);
    • Add TCM support to F7 (#4757);
    • Added Benewake TFmini/TF02 rangefinder support (#4793);
    • Added selectable RaceFlight rates (#4973);
    • Added KN (NRF24) SPI RX protocol (#4994);
    • Added Spektrum VTX status via telemtry (#5081);
    • Added PINIOBOX BOX to PINIO general purpose pin output mapper (#5110).

    New targets:

    • Added new target EachiWhoop (#4060);
    • Added new target XRACERF4 (#4255);
    • Added new target MATEKF411RX (#4937);
    • Added new target FPVM_BETAFLIGHTF7 (#5307).

    Changes from Release Candidate 3:

    Safety improvements:

    • Enhanced deactivation logic and removed unneeded parameters from Runaway Takeoff Prevention (#5337).

    Fixes:

    • Reverted power index change in vtx_common (#5313);
    • Changed rx data processing to ensure updateArmingStatus() is called periodically (#5327);
    • Fixed bug with negative core temperature (#5336);
    • Added missing osd_stat_rtc_date_time to CLI (#5339);
    • Removed conditional pidUpdateCountDown() from fc_core (#5343).

    Target updates:

    • Added camera control pin to DALRCF405 (#5294);
    • Added new target FPVM_BETAFLIGHTF7 (#5307);
    • Enabled DMAR and remapped LED_STRIP for FF_PIKOBLX (#5334).
  • Moin zusammen,


    ich hab hier einen Copter mit MircoMinimum OSD auf BF 3.3 geupdatet. Nach dem Update funktioniert das OSD nicht mehr. Bzw. sagen wir mal, das OSD braucht sicher ein Update. Voltanzeige blinkt mit 0 und Low Batterie.....


    Wer eine AIO hat, also Betaflight, Omnibus oder ähnliches. Wo der OSD Chip mit auf der FC ist und das OSD sich über BF Configurator einstellen lässt, braucht sich keine Gedanken machen. Da das OSD mit dem BF update aktuallisiert wird.....


    Bin auf die Schnelle bei dem Copter auf 3.2.5 zurück und OSD läuft wieder....

  • Moin zusammen,


    Verison 3.3.1 ist raus:


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

    Maintenance Release

    Please read the Important information when upgrading from 3.2 to 3.3.

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

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

    Important information when upgrading from an earlier version of 3.3

    • 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;
    • 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.

    Fixes:

    • Fixed build issues with legacy targets (F1) (#5359);
    • Unified enabling of EXTI for gyro on F7 with other architectures (#5364);
    • Fixed diff support for array data types (#5366);
    • Enabled disabling of acceleration rate limits (#5367);
    • Fixed possibility of getting stuck in F7 bootloader mode (#5370);
    • Changed the OSD statistics screen to be hidden in case of a runaway takeoff prevention triggered disarm (#5402);
    • Fixed build issue with MAG and GPS features (#5414);
    • Added correct rounding to MSP_RAW_IMU (#5417, #5451);
    • Fixed VTX power element in OSD (#5423);
    • Fixed saving / resetting of OSD slave settings (#5424);
    • Re-enabled VTX frequency selection mode in CLI (#5465);
    • Increased the range of ibata_offset to accommodate certain Hall effect sensors (#5467);
    • Fixed glitches of Dterm setpoint transition when going through stick center position (#5484, #5509);
    • Fixed inconsistency in the SD card parameter group (#5537);
    • Fixed potential buffer overrun in the OSD warning field (#5533);
    • Fixed naming inconsistency with the OSD elements osd_crosshairs_pos and osd_ah_sbar_pos(#5534);
    • Fix MSP data inconsistency in MSP_VOLTAGE_METERS and MSP_CURRENT_METERS (#5547, #5554);
    • Fixed the accelerometer initialization for MPU6000 and MPU9250 to use 16G range (#5559);
    • Fixed clearning of the crash flip mode flag on disarming (#5566);
    • Added default telemetry settings for iBus (#5570);
    • Fixed assignment of array parameters in CLI (#5589);
    • Fixed issue with PWM RX causing 100% CPU load (#5606);
    • Fixed arming state in IBUS telemetry (#5613).

    Target Updates:

    • Fixed SPI initialisation for SPRACINGF3OSD (#5352);
    • Added new target AIKONF4 (#5355);
    • Enabled Dshot burst by default for DALRCF405 (#5362);
    • Fixed FPVM_BETAFLIGHTF7 and OMNIBUSF7V2 gyro and accelerometer alignment (#5375);
    • Fixed TBS BST implementation on COLIBRI_RACE (#5409);
    • Added new target CRAZYBEEF3FR (#5420);
    • Added new target STM32F4DISCOVERY (#5442);
    • Moved ADC to DMA2_Stream0 to avoid conflict on KAKUTEF4 (#5481);
    • Added new target CRAZYBEEF3FS (#5495, #5590);
    • Added new target SPEEDYBEEF4 (#5552, #5590);
    • Added UART2 TX pin definition to FPVM_BETAFLIGHTF7 target (#5562);
    • Added new target REVOLTOSD (#5557);
    • Fixed LED inversion on NUCLEOF7 (#5602).
  • Moin zusammen,


    seit kurzem ist die Version 3.3.2 verfügbar

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

    Maintenance Release

    Please read the Important information when upgrading from 3.2 to 3.3.

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

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

    Important information when upgrading from an earlier version of 3.3

    • Unfortunately some of the bugfixes have led to an increase in the firmware size, pushing it over the limit of the available flash space for some targets. As a result of this, some features had to be removed from the following targets: OMNIBUS (HoTT telemetry), SPRACINGF3NEO (XBus RX). (#5812);
    • 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).

    Safety Improvements:

    • Enabled USE_BRUSHED_ESC_AUTODETECT for all targets (#5637).

    Fixes:

    • Removed mixer gain halving in 3D mode (#5582);
    • Resolved VTX Pit Mode control conflict between TX switch and Spektrum menu (#5621);
    • Exposed battery voltage divider and multiplier parameters in CLI (#5641);
    • Fixed blackbox P interval (#5645);
    • Fixed help text for 'diff defaults' (#5668);
    • Fixed broken BIDIR setting on PA9 (UART1 TX) for F4 (#5675);
    • Fixed MSP FLASHFS command if flashfs isn't supported (#5684);
    • Fixed setting of blackbox I interval to 32 ms even if PID denom isn't 1 (#5688);
    • Enabled setting of report_cell_voltage without IBUS support (#5711);
    • Fixed a typo in HMC5883L driver for F7 (#5714);
    • Fixed D-term spikes (#5728);
    • Fixed inconsistent handling of servos for USE_QUAD_MIXER_ONLY (#5747);
    • Fixed handling of passive beeper in case of non-existent timer (#5758);
    • Changed GPS speed and max speed to respect the units selection (#5765);
    • Fixed potential overflow in combined ESC sensor data (#5768);
    • Fixed I2C unstick (#5789);
    • Fixed incorrect double increment in MAX7456 screen drawing (#5793).

    Target Updates:

    • Added new target BeeStorm (#5662, #5717);
    • Fixed timer definition for REVOLTOSD (#5665);
    • Added timer for PA3 (PPM in) for OMNIBUSF7 (#5716);
    • Added onboard flash support for OMNIBUSF4SD (#5721);
    • Added onboard flash support for AlienWhoop (#5723);
    • Added new target OMNIBUSF4 Fireworks (#5749);
    • Changed barometer to be on I2C bus 3 for Revonano (#5757);
    • Added new target OmniNXT F4/F7 (#5769);
    • Changed motor output pins for YupiF4 (#5798);
    • Fixed firmware size overflow for OMNIBUS and SPRACINGF3NEO (#5812).
  • Seit kurzem die Version 3.3.3 verfügbar:

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


    Maintenance Release

    Please read the Important information when upgrading from 3.2 to 3.3.

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

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

    Important information when upgrading from an earlier version of 3.3

    • Unfortunately some of the bugfixes have led to an increase in the firmware size, pushing it over the limit of the available flash space for some targets. As a result of this, some features had to be removed from the following targets: OMNIBUS (HoTT telemetry), SPRACINGF3NEO (XBus RX). (#5812);
    • 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).

    Safety Improvements:

    Fixes:

    • Fixed the constraint on the D-term transition upper bound (#5701);
    • Fixed the symbols for GPS lat and lon in OSD (#5855);
    • Fixed the heli 120 mixer (#5857).

    Target Updates:

    • Updated the target SPEEDYBEE F4 (#5787);
    • Added new target STACKX (#5813);
    • Added new targets AG3XF4 / AG3XF7 targets (Asgard32 F4 / F7) (#5816);
    • Enabled Dshot burst for SPRACINGF4NEO (#5865);
    • Enabled Dshot burst for CLRACINGF7(#5922);
    • Added new target FOXEERF405 (#5950);
    • Removed nonfunctional RX_SERIAL default feature from OMNIBUSF4 (#5987);
    • Changed IMU support for KAKUTEF7 (#5796);
    • Added OSD support for ALIENFLIGHTNGF7 (AFNG F7 Horus30 board) (#6002).
  • Moin zusammen,


    seit heute ist die V3.4RC1 Verfügbar:
    https://github.com/betaflight/betaflight/releases

    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 😉) (#6036);
    • 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);
    • 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 smooting (#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).
  • Moin zusammen,


    neue GUI 10.3 verfügbar, jetzt mit unterstützung für 3.4


    https://github.com/betaflight/…rator/releases/tag/10.3.0


    Release Notes

    This release contains all of the changes necessary to support version 3.4 of the Betaflight firmware. If you are using firmware 3.4, it is essential that you upgrade to this version, in order to get support for configuring the new features of 3.4.

    We have also added some exciting new features that a lot of users have been asking for:

    • development builds and builds of special branches (e.g. the branches with a patch for AKK/RDQ owners) can now be downloaded and installed from within the configurator - enable 'Show unstable releases' to see them;
    • firmware hex files are now cached once they have been downloaded - no need to wait for the download to finish again if you are installing the same version for a second time;
    • if are artistically inclined, you can now add your own logo to the Betaflight OSD boot screen. See here for instructions;
    • Japanese and Portugese have been added to the list of supported languages.

    If your platform is not supported, but can run a recent version of Chrome, please follow these instructions to install the Betaflight Configurator from the Chrome web store.

    As usual, please report any bugs you find back to us by opening an issue here.

    Fixes:

    • fixed MSP_RX controls.

    New GUI support for the following firmware features:

    • added support for moving the artificial horizon / crosshairs to OSD;
    • other OSD improvements;
    • updated PayPal donate link.

    Improvements:

    • added support for customised OSD boot logo;
    • added current / consumption information into the 'Motors' tab;
    • added translations for Japanese and Portugese;
    • added local caching for downloaded firmware files;
    • added support for tab completion for commands in the CLI;
    • added support for downloading / installing development builds / builds for special version branches (e.g. AKK/RDQ support) from the CI server;
    • changed the installation to be uncompressed to achieve faster startup.
  • Moin zusammen,


    seit 01.07.2018 ist die RC4 verfügbar:


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


    New targets:

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

    Changes from Release Candidate 3:

    Safety Improvements:

    • Added disabling of GPS_RESCUE when 3D mode is enabled (#6251).

    Fixes:

    • Fixed RunCam device initialisation (#6213);
    • Fixed reboot into bootloader for F411 targets (#6221);
    • Fixed yaw / throttle handling in GPS_RESCUE mode (#6227);
    • Fixed and improved throttle correction (#6235);
    • Set unused default to 0 (#6241);
    • Fixed check for RC smoothing (#6250).

    Target updates:

    • Removed features from FURYF3OSD and STM32F3DISCOVERY to make the firmware fit into flash (#6242);
    • Fixed board alignment for YUPIF7 (#6192).
  • Vor 11 Stunden ist die V3.4 final raus:

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

    Da hab ich dann mit der RC5 heute wohl noch ne alte Version geflogen.... hat noch nen bisschen Propwash. Flight sich aber schon geil.... zwar nicht so geil wie KISS. Aber es kommt immer näher dran:


  • Kaum ist die V3.4 final tauchen auch schon die ersten prerealeses von V3.5 auf:

    https://ci.betaflight.tech/job…t/lastBuild/artifact/obj/


    Wer traut sich :D


    Neu sind Begriffe wie etracer und ctcsnooze.... bin dann ja mal gespannt, wann die FC nen eigenen Kühler braucht 8o


    offizelles Release für V3.5 soll dann der 5 August sein und die V4.0 soll dann am 1 Januar 2019 erscheinen.

  • Moin zusammen,


    hab heut mal nen Feierabendlipo mit der BF 3.4 geflogen. Fühlt sich gut an. Den Propwash müsst ich noch nen wenig elimieren. Aber immer Moment einfach keine Lust da viel rum zu tunen. Is eh nur mein Restecopter... die Prepoller sind da dran auch net mehr so frisch. Aber bei dem Teil nehm ich's net so genau: