Micro Motor Community

BetaFlight 3.2 FINAL - on BetaFPV F3 OSD Whoop


#41

Set motor protocol to brushed on the configuration tab. Classic motors spinning on Lipo connection issue.


#42

After reading this I pulled out an old acrowhoop I couldnt get to work. It would bind but the sticks wouldn’t do anythbig. Set the sbus inversion off and it works again!


#43

Okay so I changed motor config tab to brushed and It’s somewhat working but now I’m just getting flips of death and had to use ppm? Anyone know anything else?

CLI

diff

Betaflight / BETAFLIGHTF3 (BFF3) 3.2.2 Nov 11 2017 / 00:21:21 (77782e602) MSP API: 1.36

name BF3.2-inverted
resource MOTOR 1 B08
resource MOTOR 2 B09
resource MOTOR 3 A06
resource MOTOR 4 A07

feature -RX_SERIAL
feature RX_PPM
map TAER1234
serial 0 0 115200 57600 0 115200
aux 0 0 0 1675 2100
aux 1 1 1 900 1225
aux 2 2 1 1300 1700
aux 3 28 1 1300 2100
set min_check = 1020
set max_check = 1980
set motor_pwm_protocol = BRUSHED
set motor_pwm_rate = 16000
set align_board_roll = 180
set bat_capacity = 200
set vbat_max_cell_voltage = 44
set vbat_min_cell_voltage = 29
set vbat_warning_cell_voltage = 31
set deadband = 5
set yaw_deadband = 10
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_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_min_rssi = OFF
set osd_stat_max_curr = OFF
set osd_stat_used_mah = OFF
set osd_stat_bbox = OFF
set osd_stat_endbatt = ON
set osd_stat_bb_no = OFF
set osd_stat_tim_1 = ON
profile 0

set level_limit = 90
rateprofile 0


#44

Post a diff.


#45

Thanks @Benedikt I’ve been flying so much i haven’t done much tuning to the quad itself yet.


#46

Finally took the time to get a diff from my BetaFPV board, so here it is:

diff

Betaflight / BETAFLIGHTF3 (BFF3) 3.2.2 Nov 11 2017 / 00:21:21 (77782e602) MSP API: 1.36

name BETAFPV 7

feature MOTOR_STOP
feature RSSI_ADC
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 -GPS_STATUS
beeper -RX_SET
beeper -ACC_CALIBRATION
beeper -ACC_CALIBRATION_FAIL
beeper -READY_BEEP
beeper -MULTI_BEEPS
beeper -DISARM_REPEAT
beeper -ARMED
beeper -SYSTEM_INIT
beeper -ON_USB
beeper -BLACKBOX_ERASE
map TAER1234
aux 0 0 0 1925 2100
aux 1 1 1 900 1200
aux 2 2 1 1300 1700
aux 3 27 2 1400 2100
aux 4 28 1 1825 2100
set gyro_notch1_hz = 0
set gyro_notch1_cutoff = 0
set gyro_notch2_hz = 0
set gyro_notch2_cutoff = 0
set min_check = 1000
set max_check = 2000
set min_throttle = 1040
set use_unsynced_pwm = ON
set motor_pwm_protocol = BRUSHED
set motor_pwm_rate = 16000
set failsafe_kill_switch = ON
set bat_capacity = 250
set vbat_max_cell_voltage = 44
set ibata_scale = 2200
set yaw_motors_reversed = ON
set deadband = 3
set yaw_deadband = 3
set osd_vbat_pos = 44
set osd_rssi_pos = 1
set osd_tim_1_pos = 54
set osd_tim_2_pos = 2102
set osd_flymode_pos = 333
set osd_throttle_pos = 225
set osd_vtx_channel_pos = 377
set osd_crosshairs = 200
set osd_ah_sbar = 200
set osd_ah_pos = 200
set osd_current_pos = 392
set osd_mah_drawn_pos = 353
set osd_craft_name_pos = 362
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 = 266
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 = 329
set osd_avg_cell_voltage_pos = 2082
set osd_pit_ang_pos = 257
set osd_rol_ang_pos = 289
set osd_battery_usage_pos = 392
set osd_disarmed_pos = 138
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_bbox = OFF
set osd_stat_endbatt = ON
set osd_stat_bb_no = OFF
profile 0

set setpoint_relax_ratio = 90
set dterm_setpoint_weight = 30
set i_pitch = 40
set d_pitch = 25
set p_roll = 50
set i_roll = 30
set d_roll = 20
set p_yaw = 75
rateprofile 0

set rc_rate = 125
set rc_rate_yaw = 125
set rc_expo = 10
set rc_expo_yaw = 10


#47

and what exactly is your problem?
still stats not showing properly?


#48

Yes, they just flash quickly and disapear.
And if there is a way to calibrate or offset the voltage in the OSD? It shows a value that is too low.


#49

After trying to use the BF OSD menu i realized thats not working either.
Anyone that know a way of getting in touch with BetaFPV since they dont seem to have a customer support?


#50

Afaik it done via this helpdesk thing.
Seems they want u to open a support ticket…
Support Ticket
But havent used it, cant say if it ‘works’…


#51

@Animalistik did you reflash that FC? Whenever weird stuff like this happens, I always reflash using full chip erase. So many things have been fixed this way!

If the same problem persist after a reflash, I would assume hardware failure and contact the vendor. Did you purchase the FC directly from BetaFPV?


#52

I did reflash many times with different versions of BF. Nothing helped.
Untill yesterday, i flew my BetaFPV with OSD that i ordered of AliExpress and finally modded a camera to get the OSD. That worked like a charm. And my last pack i put insde my older Beta65s setup that gave me headaches, this time OSD works flawlessly. So wierd, cant understand how this could be, i didnt even connect it to BF.
But im really happy now i got 2 Whoops running OSD :smiley:

Edit: Mystery solved, i realized that when i disarmed my Beta65s the throttle jumped up to 1999. On my Other Beta FC it did not.

Next question, why did the throttle value go up on disarm?


#53

Throttle jumping to 1999 when disarming?
Thats odd, but it certainly might be related to the OSD disappearing.

I cant see a way to misconfigure the FC to do that.
On the Tx though, it would be easy to setup a mixer line that will cause the throttle to react to the arm switch.
Are you using a different model on your Tx for this FC?
Have you checked in your output monitor on the Tx that it is not sending a high throttle signal on disarm?


#54

Oh sorry, forgot to mention that it was the TX setup that gave me this wierd problem. I used my other setup on the TX by misstake and noticed the OSD was working like it supposed to. So you say its a mixer setting? Wierd thing is i have not touched any other settings (if not by misstake) then the normal stuff thats need to be done to get flying…


#55

So all this OSD trouble was indeed caused by your Tx. Yeah that makes sense.
Is that a OpenTX radio? Then you should find a hint in either the input or the output mixer.


#56

Yes, a Q X7. I will have to look into that, as i have a problem with many of my brushed builds revving up briefly on disarm.


#57

I have just installed BF 3.2.3 on one of my boards.
Works exactly like 3.2.2, I cannot see any difference.
Takes the exact same settings, flys and works exactly the same.


#58

@benedikt… Is the new version maybe just correcting its latest flaws? (“small_angle”, etc…)


#59

Appreciate you posting the dump of your BetaFPV FC. I updated my Beta65 with 3.2.3 (from 3.2.2) and it went smooth and it flies just the same. The one thing I noticed is that I didn’t have to go in and reset any of my non-default settings. 3.2.3 saved them before it flashed and reapplied them afterwards from the behavior I saw.

0n 3.2.0 and 3.2.2 updates, I had to reapply my diffs but not with 3.2.3. Progress! I went ahead and updated my Beta65s and 75 as well and they fly the same as well.


#60

I have read through the release notes and saw nothing relevant to this FC.
But there are probably lots of little things that have changed, which dont make their way into the release notes.

Oh, nice I didnt notice that. I always flash with full chip erase and then copy my settings file into the CLI.