BetaFlight 3.2 FINAL - on BetaFPV F3 OSD Whoop


#1

This is the BF3.2 firmware thread for the BetaFPV F3 OSD:

The following settings are as stock as possible, which means I changed only what was necessary to make it fly and unclutter OSD, but left all rates etc. at their defaults.

name BF3.2-inverted

#flip board with plugs up
set align_board_roll = 180

#remap motor outputs
resource MOTOR 3 A06
resource MOTOR 4 A07
resource MOTOR 1 B08
resource MOTOR 2 B09

#arm on AUX1
aux 0 0 0 1300 2100

#angle on AUX2 high 
aux 1 1 1 900 1700

#airmode on AUX2 mid/high 
aux 2 28 1 1250 2100

#increase motor PWM to make the sound less annoying. Reduce to 4000 for a little more power and more motor noise.
set motor_pwm_rate = 16000

#increase inclination angle limit to make it more agile in agile mode
set level_limit = 90

#enable serial Rx port, disable PPM Rx
feature -RX_PPM
feature RX_SERIAL
serial 0 0 115200 57600 0 115200

   #configure input channels as Throttle, Aileron, Elevator, Rudder. Adjust this line to your transmitter settings.
map TAER1234

   #assuming Tx travel from 1010 to 1990. Adjust your Tx travel to these numbers, or adjust below min_check and max_check to be just (e.g. 10ms) inside your most extreme inout values.
set min_check = 1020
set max_check = 1980

set deadband = 5
set yaw_deadband = 10


#disable most OSD features, reposition the rest
set osd_units = METRIC
set osd_rssi_alarm = 20
set osd_cap_alarm = 2200
set osd_alt_alarm = 100
set osd_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_tim1 = 2560
set osd_tim2 = 513
set osd_vbat_pos = 2087
set osd_rssi_pos = 40
set osd_tim_1_pos = 54
set osd_tim_2_pos = 2096
set osd_flymode_pos = 333
set osd_throttle_pos = 225
set osd_vtx_channel_pos = 377
set osd_crosshairs = 2248
set osd_ah_sbar = 200
set osd_ah_pos = 200
set osd_current_pos = 385
set osd_mah_drawn_pos = 353
set osd_craft_name_pos = 33
set osd_gps_speed_pos = 218
set osd_gps_lon_pos = 82
set osd_gps_lat_pos = 65
set osd_gps_sats_pos = 51
set osd_home_dir_pos = 302
set osd_home_dist_pos = 303
set osd_compass_bar_pos = 42
set osd_altitude_pos = 247
set osd_pid_roll_pos = 423
set osd_pid_pitch_pos = 455
set osd_pid_yaw_pos = 487
set osd_debug_pos = 1
set osd_power_pos = 321
set osd_pidrate_profile_pos = 345
set osd_warnings_pos = 2186
set osd_avg_cell_voltage_pos = 76
set osd_pit_ang_pos = 33
set osd_rol_ang_pos = 65
set osd_battery_usage_pos = 392
set osd_disarmed_pos = 2315
set osd_nheading_pos = 311
set osd_nvario_pos = 279
set osd_esc_tmp_pos = 82
set osd_esc_rpm_pos = 83
set osd_stat_max_spd = OFF
set osd_stat_max_dist = OFF
set osd_stat_min_batt = ON
set osd_stat_min_rssi = OFF
set osd_stat_max_curr = OFF
set osd_stat_used_mah = OFF
set osd_stat_max_alt = OFF
set osd_stat_bbox = OFF
set osd_stat_endbatt = ON
set osd_stat_bb_no = OFF
set osd_stat_tim_1 = ON
set osd_stat_tim_2 = ON

#tune alarms and thresholds
set bat_capacity = 200
set vbat_max_cell_voltage = 44
set vbat_full_cell_voltage = 41
set vbat_min_cell_voltage = 29
set vbat_warning_cell_voltage = 31
set vbat_hysteresis = 1
set current_meter = ADC
set battery_meter = ADC
set vbat_detect_cell_voltage = 30
set use_vbat_alerts = ON
set use_cbat_alerts = OFF
set cbat_alert_percent = 10
set vbat_cutoff_percent = 100
set vbat_scale = 110

To use above setting on your flight controller, flash the “BetaFlightF3 3.2” target, then copy all lines from above setting dump in the CLI, press enter, type “save”, press enter.


#2

Are you having any issues getting the FC into DFU mode? I have tried the button to no avail…


#3

Have you tried typing bl in cli?


#4

I have not. I will try that. Thank you.


#5

I did not try to put it into DFU mode, all my flashing on these boards went nice and smooth so far.
Did you have any issues flashing it, or why do you want DFU?


#6

configured the OSD and dumped the settings, added to first post.


#7

My mistake I was able to get it to work. I needed DFU mode in order to update the firmware.


#8

Anyone know if “FPV_Angle_Mix” has been fixed in the latest 3.2?

I went back to 3.1.6 a few months ago as I was getting arm dip on my AcroWhoop V2 DSMX and my Blade Torrent, and FPV Angle Mix just didn’t work at all…it was like you’d put in 20 degrees and it wouldn’t get the degrees right.

Now I’m on BetaFPV DSMX and FrSky FC’s on my whoops so, wondering how 3.2 is working now!


#9

Put 3.2.1 on my BetaFPV SBUS (non-OSD) and it really doesn’t fly well at all compared to 3.1.6. I’m getting some arm dip, especially on split-s maneuvers.

I’m not doing much when I set it up:

Betaflight / SPRACINGF3EVO (SPEV) 3.2.1 Oct 15 2017 / 19:48:22 (434db9a36) MSP API: 1.36

name FrSkyWhoop

feature -RX_PPM
feature -TRANSPONDER
feature RX_SERIAL
feature DYNAMIC_FILTER
beeper -GYRO_CALIBRATED
beeper -RX_LOST
beeper -RX_LOST_LANDING
beeper -DISARMING
beeper -ARMING
beeper -ARMING_GPS_FIX
beeper -BAT_CRIT_LOW
beeper -BAT_LOW
beeper -RX_SET
beeper -ACC_CALIBRATION
beeper -ACC_CALIBRATION_FAIL
beeper -READY_BEEP
beeper -MULTI_BEEPS
beeper -ARMED
beeper -SYSTEM_INIT
beeper -ON_USB
beeper -BLACKBOX_ERASE
serial 1 64 115200 57600 0 115200
aux 0 0 0 1850 2000
aux 1 1 1 1350 1675
aux 2 2 1 1750 2100
rxrange 0 999 1985
rxrange 1 1005 2002
rxrange 2 1001 2000
rxrange 3 1000 2018
set gyro_notch1_hz = 0
set gyro_notch1_cutoff = 0
set gyro_notch2_hz = 0
set gyro_notch2_cutoff = 0
set baro_hardware = NONE
set serialrx_provider = SBUS
set min_throttle = 1040
set failsafe_delay = 0
set small_angle = 180
set deadband = 4
set yaw_deadband = 4
profile 0

set dterm_lowpass_type = PT1
set anti_gravity_gain = 2000
set p_pitch = 100
set i_pitch = 130
set d_pitch = 45
set p_roll = 80
set i_roll = 110
set d_roll = 45
set p_yaw = 190
set i_yaw = 120
set p_level = 100
set i_level = 30
set d_level = 50
rateprofile 0

set rc_rate = 103
set rc_rate_yaw = 104
set roll_srate = 87
set pitch_srate = 87
set yaw_srate = 87


Need help to setup Taranis X9D+, Spektrum DM9 and Beecore V1 (flashed with Betaflight 3.2.2)
#10

Brilliant! Just what I’ve been looking for. I can study this to learn how this works. Very helpful. Thank you.


#11

Hi everyone I just found this post and greatly appreciate it it’s going to help a lot I’m completely new to beta flight I’m afraid I really messed up my betafpv f3 osd for a dxe spectrum transmitter if I follow the above post will it get me up in the air thank you in advance!!!


#12

I agree with with @PJC, there are some issues with how 3.2.x flies compared to older version. As long as its all working fine, its all good. But from time to time, it just drops a wing or yaw gets totally out of whack. Especially when pushing through high-G maneuvers, when applying yaw under low throttle settings, and when going from low to high throttle quickly.
I have tried various setting changes, and even though some improved it a little, nothing fixed it completely.
I have seen people in other forums complain about erratic behaviour like this on other platforms, thats why Im hesitating to start a bigger discussion about this, but rather wait for the next update to see if anything changes. When the next version is still behaving like this, something needs to happen…
Unless its pushed to the edge, BF 3.2 flies so nice!
Im optimistic the kinks will be ironed out eventually.

In the meantime, I played around more with the OSD and found good values for the voltage alerts. I updated the first post here with the following setting lines:

#disable most OSD features, reposition the rest
set osd_units = METRIC
set osd_rssi_alarm = 20
set osd_cap_alarm = 2200
set osd_alt_alarm = 100
set osd_ah_max_pit = 20
set osd_ah_max_rol = 40
set osd_tim1 = 2560
set osd_tim2 = 513
set osd_vbat_pos = 2087
set osd_rssi_pos = 40
set osd_tim_1_pos = 54
set osd_tim_2_pos = 2096
set osd_flymode_pos = 333
set osd_throttle_pos = 225
set osd_vtx_channel_pos = 377
set osd_crosshairs = 2248
set osd_ah_sbar = 200
set osd_ah_pos = 200
set osd_current_pos = 385
set osd_mah_drawn_pos = 353
set osd_craft_name_pos = 33
set osd_gps_speed_pos = 218
set osd_gps_lon_pos = 82
set osd_gps_lat_pos = 65
set osd_gps_sats_pos = 51
set osd_home_dir_pos = 302
set osd_home_dist_pos = 303
set osd_compass_bar_pos = 42
set osd_altitude_pos = 247
set osd_pid_roll_pos = 423
set osd_pid_pitch_pos = 455
set osd_pid_yaw_pos = 487
set osd_debug_pos = 1
set osd_power_pos = 321
set osd_pidrate_profile_pos = 345
set osd_warnings_pos = 2186
set osd_avg_cell_voltage_pos = 76
set osd_pit_ang_pos = 33
set osd_rol_ang_pos = 65
set osd_battery_usage_pos = 392
set osd_disarmed_pos = 2315
set osd_nheading_pos = 311
set osd_nvario_pos = 279
set osd_esc_tmp_pos = 82
set osd_esc_rpm_pos = 83
set osd_stat_max_spd = OFF
set osd_stat_max_dist = OFF
set osd_stat_min_batt = ON
set osd_stat_min_rssi = OFF
set osd_stat_max_curr = OFF
set osd_stat_used_mah = OFF
set osd_stat_max_alt = OFF
set osd_stat_bbox = OFF
set osd_stat_endbatt = ON
set osd_stat_bb_no = OFF
set osd_stat_tim_1 = ON
set osd_stat_tim_2 = ON

#tune alarms and thresholds
set bat_capacity = 200
set vbat_max_cell_voltage = 44
set vbat_full_cell_voltage = 41
set vbat_min_cell_voltage = 29
set vbat_warning_cell_voltage = 31
set vbat_hysteresis = 1
set current_meter = ADC
set battery_meter = ADC
set vbat_detect_cell_voltage = 30
set use_vbat_alerts = ON
set use_cbat_alerts = OFF
set cbat_alert_percent = 10
set vbat_cutoff_percent = 100
set vbat_scale = 110

#13

I’ve noticed some of the behaviors your mentioning in 3.2 as well @Benedikt . Specifically an issue with yaw. It does seem to be when your on the edge of what our little machines are capable of rate/vector wise. A friend of mine has magnet wired a data chip to his hoop and we have been seeing some very interesting BB traces. We have pestered a few of the beta devs to look at our data, so we will see what happens.


#14

I’ve tried to tune it out, and altered my PID’s, filters, etc, but for all the good stuff in 3.2, I finally just went back to 3.1.6 this morning. Maybe it’s how I’m flying with lots of fast tricks, but I got tired of those instances causing unreliable flight behavior. I wish I could figure out what’s going on as a lot of people are loving 3.2 on their Whoops.


#15

Something to look into/test. I have not flown betaflight on a whoop in some time but I have experienced similar issues when tuning silverware and was able to correct them. There are predefined limits for pid-sum values and integral-sum values. Both if these user set limits chop off the accumulation of error causing correction force to be maintained. I had to at least double these values which are normally fine for any other craft to prevent blowouts on high g manuvers with a whoop. I have noticed similar settings accessible on the cli in betaflight … may be worth a test to increase the limits for the yaw axis which is giving you trouble. As large brushless crafts get more powerful - I wouldn’t be surprised to see the gap grow between the default settings that work for them vs. the completely different set up that underpowered micros require.


#16

By the way - did any of you encounter other issues like ‘cannot set max arming angle’ (text box is blank after reboot) or ‘RSSI stuck on value of 15’?
Additional - my other BG FrSky beecore transmits RSSI & Bat1 volts… the BetaFPV one does not?


#17

A few weeks ago, BetaFPV updated this FC, and the new version has the Rx connected over SBUS. This makes for a much more precise connection between FC and receiver.

I have updated the top post with settings to configure the FC for use of SBUS and disable PPM.


#18

@NotFastEnuf I heard BF 3.2.1 has issues that 3.2.0 and 3.2.2 do not have. Some yaw related filter was removed, and that causes trouble.
So dont install 3.2.1! Use 3.2.0, and then skip to 3.2.2 when its released.

@mcRich this FC does not do any telemetry. I asked why and they said they had resourced to implement telemetry or OSD, and they decided for the latter.


#19

The non-OSD FrSky does Telemetry…RSSI only.

That’s an interesting thought. The only quad I have 3.2 on (3.2.2) is my 3 inch Hellbender and it runs great. My QAV105 and Torrent just don’t run that great and remind me of the issues I had on my Whoops. I haven’t tried 3.2.2 on either one of the lighter quads, or my Whoops, but maybe I’ll try it again.

3.2.2 on my Hellbender is smoov like butta…but 3 inch 1306 might just be my favorite anyway. :stuck_out_tongue: That QAV105 (running 1105’s) is just too lightweight and floaty!


#20

Thanks for this piece of information, sir.
Sooo, that would include RSSI on OSD? (i should 've said: RSSI on OSD stuck to like 14 - 15. in previous post)

Shall i open new thread regarding my probs with BetaFPV OSD board?