Open Source Flight Controller Firmware
GPL-3.0 License
Bot releases are hidden (Show)
Published by mikeller over 6 years ago
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);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);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);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);rssi_scale
/ rssi_offset
CLI variables to set the scale and offset for RSSI (#6001, #6032);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);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);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).Published by mikeller over 6 years ago
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);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);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);rssi_scale
/ rssi_offset
CLI variables to set the scale and offset for RSSI (#6001, #6032);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);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).Published by mikeller over 6 years ago
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);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);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);rssi_scale
/ rssi_offset
CLI variables to set the scale and offset for RSSI (#6001, #6032);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);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).Published by mikeller over 6 years ago
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.
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);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).Published by mikeller over 6 years ago
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.
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);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).report_cell_voltage
without IBUS support (#5711);Published by mikeller over 6 years ago
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.
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;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.MSP_RAW_IMU
(#5417, #5451);ibata_offset
to accommodate certain Hall effect sensors (#5467);osd_crosshairs_pos
and osd_ah_sbar_pos
(#5534);MSP_VOLTAGE_METERS
and MSP_CURRENT_METERS
(#5547, #5554);Published by mikeller over 6 years ago
Welcome to version 3.3 of Betaflight!
There are no revolutionary new features in this release, but we've worked hard to make your flying experience even better, and make it easier and safer for new pilots to get into the hobby. We've ironed out some kinks, and we've added Runaway Takeoff Prevention to stay safe in those dodgy moments when your craft isn't set up the way you think it is. We've improved connectivity by adding support for configuring your craft from Spektrum transmitters, and adding the FrSky FPort protocol that gives you RC control, RSSI, and telemetry over just one wire.
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've tried to make this release as bug free as possible. If you still find a bug, please open an issue here. Thank you.
Happy Props!
runaway_takeoff_deactivate_delay
, runaway_takeoff_deactivate_throttle_percent
) to tune the function to work for you, and please report back your working configuration. See the wiki article for details.align_mag
to configure the correct orientation;sbus_inversion
has been changed into serialrx_inverted
, and the way it is applied has been changed as follows: It now applies to all RX protocols, not just SBus, and instead of switching the UART to normal when off and inverted when on, 'off' now means that the port is set to whatever the default is for the selected protocol (i.e. inverted for SBus, not inverted for SUMD), and 'on' means that the port is inverted from default (i.e. not inverted for SBus, inverted for SUMD);rc_rate
becomes roll_rc_rate
and pitch_rc_rate
, rc_rate_yaw
becomes yaw_rc_rate
, rc_expo
becomes roll_expo
and pitch_expo
, and rc_expo_yaw
becomes yaw_expo
. The same change also makes 'RaceFlight' type rate settings available. Set rates_type = raceflight
. After this, 'rc_rate_' is RaceFlight 'rate' (scaled down by a factor of 10), <axis>_expo
is RaceFlight 'expo', and <axis>_srate
is RaceFlight 'acro+';DISABLE 3D
mode is now called DISABLE / SWITCH 3D
(#5179). In default configuration it works in the same way it used to work before. With 3d_switched_mode = on
, 'switched 3d mode' is enabled: With the 3D switch on, the throttle goes from forward thrust idle (min) to forward thrust full (max), which is the same as with 3d_switched_mode = off
. With the 3D switch off, the throttle goes from reversed thrust idle (min) to reversed thrust full (max). This allows the pilot to fly 3d by using the full throttle range in normal / reversed position, by switching motor directions with the switch when flipping over;disarm_kill_switch
function that allowed (switch) disarming to be set up to be only possible on low throttle has been removed. There is no use case that requires it, and having it enabled introduces the safety risk of not being able to reliably disarm in an emergency;vtx_common
(#5313);updateArmingStatus()
is called periodically (#5327);osd_stat_rtc_date_time
to CLI (#5339);pidUpdateCountDown()
from fc_core
(#5343).Published by mikeller over 6 years ago
runaway_takeoff_threshold
, runaway_takeoff_activate_delay
, runaway_takeoff_deactivate_delay
, runaway_takeoff_deactivate_throttle_percent
) to tune the function to work for you, and please report back your working configuration;align_mag
to configure the correct orientation;sbus_inversion
has been changed into serialrx_inverted
, and the way it is applied has been changed as follows: It now applies to all RX protocols, not just SBus, and instead of switching the UART to normal when off and inverted when on, 'off' now means that the port is set to whatever the default is for the selected protocol (i.e. inverted for SBus, not inverted for SUMD), and 'on' means that the port is inverted from default (i.e. not inverted for SBus, inverted for SUMD);rc_rate
becomes roll_rc_rate
and pitch_rc_rate
, rc_rate_yaw
becomes yaw_rc_rate
, rc_expo
becomes roll_expo
and pitch_expo
, and rc_expo_yaw
becomes yaw_expo
. The same change also makes 'RaceFlight' type rate settings available. Set rates_type = raceflight
. After this, 'rc_rate_' is RaceFlight 'rate' (scaled down by a factor of 10), <axis>_expo
is RaceFlight 'expo', and <axis>_srate
is RaceFlight 'acro+';DISABLE 3D
mode is now called DISABLE / SWITCH 3D
(#5179). In default configuration it works in the same way it used to work before. With 3d_switched_mode = on
, 'switched 3d mode' is enabled: With the 3D switch on, the throttle goes from forward thrust idle (min) to forward thrust full (max), which is the same as with 3d_switched_mode = off
. With the 3D switch off, the throttle goes from reversed thrust idle (min) to reversed thrust full (max). This allows the pilot to fly 3d by using the full throttle range in normal / reversed position, by switching motor directions with the switch when flipping over;disarm_kill_switch
function that allowed (switch) disarming to be set up to be only possible on low throttle has been removed. There is no use case that requires it, and having it enabled introduces the safety risk of not being able to reliably disarm in an emergency.To get optimal support for configuration and tuning of the firmware, please use the latest version of the Betaflight configurator (10.2.0 at the time of this release), available here.
Published by mikeller over 6 years ago
runaway_takeoff_threshold
, runaway_takeoff_activate_delay
, runaway_takeoff_deactivate_delay
, runaway_takeoff_deactivate_throttle_percent
) to tune the function to work for you, and please report back your working configuration;align_mag
to configure the correct orientation;sbus_inversion
has been changed into serialrx_inverted
, and the way it is applied has been changed as follows: It now applies to all RX protocols, not just SBus, and instead of switching the UART to normal when off and inverted when on, 'off' now means that the port is set to whatever the default is for the selected protocol (i.e. inverted for SBus, not inverted for SUMD), and 'on' means that the port is inverted from default (i.e. not inverted for SBus, inverted for SUMD);rc_rate
becomes roll_rc_rate
and pitch_rc_rate
, rc_rate_yaw
becomes yaw_rc_rate
, rc_expo
becomes roll_expo
and pitch_expo
, and rc_expo_yaw
becomes yaw_expo
. The same change also makes 'RaceFlight' type rate settings available. Set rates_type = raceflight
. After this, 'rc_rate_' is RaceFlight 'rate' (scaled down by a factor of 10), <axis>_expo
is RaceFlight 'expo', and <axis>_srate
is RaceFlight 'acro+';DISABLE 3D
mode is now called DISABLE / SWITCH 3D
(#5179). In default configuration it works in the same way it used to work before. With 3d_switched_mode = on
, 'switched 3d mode' is enabled: With the 3D switch on, the throttle goes from forward thrust idle (min) to forward thrust full (max), which is the same as with 3d_switched_mode = off
. With the 3D switch off, the throttle goes from reversed thrust idle (min) to reversed thrust full (max). This allows the pilot to fly 3d by using the full throttle range in normal / reversed position, by switching motor directions with the switch when flipping over;disarm_kill_switch
function that allowed (switch) disarming to be set up to be only possible on low throttle has been removed. There is no use case that requires it, and having it enabled introduces the safety risk of not being able to reliably disarm in an emergency.motorDevConfig_t
, incremented EEPROM config version before 3.3.0 release (#5178);BOX3DDISABLE
and BOX3DONASWITCH
switches (#5179);Published by mikeller over 6 years ago
runaway_takeoff_threshold
, runaway_takeoff_activate_delay
, runaway_takeoff_deactivate_delay
, runaway_takeoff_deactivate_throttle_percent
) to tune the function to work for you, and please report back your working configuration;align_mag
to configure the correct orientation;sbus_inversion
has been changed into serialrx_inverted
, and the way it is applied has been changed as follows: It now applies to all RX protocols, not just SBus, and instead of switching the UART to normal when off and inverted when on, 'off' now means that the port is set to whatever the default is for the selected protocol (i.e. inverted for SBus, not inverted for SUMD), and 'on' means that the port is inverted from default (i.e. not inverted for SBus, inverted for SUMD);rc_rate
becomes roll_rc_rate
and pitch_rc_rate
, rc_rate_yaw
becomes yaw_rc_rate
, rc_expo
becomes roll_expo
and pitch_expo
, and rc_expo_yaw
becomes yaw_expo
. The same change also makes 'RaceFlight' type rate settings available. Set rates_type = raceflight
. After this, 'rc_rate_' is RaceFlight 'rate' (scaled down by a factor of 10), <axis>_expo
is RaceFlight 'expo', and <axis>_srate
is RaceFlight 'acro+';DISABLE 3D
mode is now called DISABLE / SWITCH 3D
(#5179). In default configuration it works in the same way it used to work before. With 3d_switched_mode = on
, 'switched 3d mode' is enabled: With the 3D switch on, the throttle goes from forward thrust idle (min) to forward thrust full (max), which is the same as with 3d_switched_mode = off
. With the 3D switch off, the throttle goes from reversed thrust idle (min) to reversed thrust full (max). This allows the pilot to fly 3d by using the full throttle range in normal / reversed position, by switching motor directions with the switch when flipping over.Published by mikeller over 6 years ago
Please read the Instructions for Upgrading.
This release contains bugfixes and target changes only. For a full list of new features see 3.2.0.
setpoint_relax_ratio
to avoid division by zero (#4961);Published by mikeller almost 7 years ago
Please read the Instructions for Upgrading.
This release contains bugfixes and target changes only. For a full list of new features see 3.2.0.
Published by mikeller almost 7 years ago
Please read the Instructions for Upgrading.
This release contains bugfixes and target changes only. For a full list of new features see 3.2.0.
Published by mikeller almost 7 years ago
Please read the Instructions for Upgrading.
This release contains bugfixes and target changes only. For a full list of new features see 3.2.0.
Published by borisbstyle almost 7 years ago
Please read the Instructions for Upgrading.
defaults
after upgrading, and restore from the backup (#4280);Published by mikeller about 7 years ago
Please read the Instructions for Upgrading.
This release contains bugfixes and target changes only. For a full list of new features see 3.2.0.
Published by borisbstyle over 7 years ago
Maintanence Release 3.1.7
For full release info see 3.1:
https://github.com/betaflight/betaflight/releases/tag/v3.1.0
New:
Fixes:
NOTE:
Make sure you check your modes after restoring old config as modes can be shifted
Published by borisbstyle over 7 years ago
Maintanence Release 3.1.6
For full release info see 3.1:
https://github.com/betaflight/betaflight/releases/tag/v3.1.0
New:
Fixes:
Known issues/bugs:
Published by borisbstyle over 7 years ago
Maintanence Release 3.1.5
For full release info see 3.1:
https://github.com/betaflight/betaflight/releases/tag/v3.1.0
Known Bugs/Issues:
Published by borisbstyle over 7 years ago
Maintanence Release 3.1.3
For full release info see 3.1:
https://github.com/betaflight/betaflight/releases/tag/v3.1.0
_IMPORTANT NOTE:_
If you were using the old multiwii throttle expo youwill experience totally different behaviour. You may better remove it.