Oh no! What did I do?

[Roadking]

I was messing around in Betaflight and must have touched something but my Tinyhawk won't fly anymore. I was trying to input the Mockingbird settings.

I can arm it, but as soon as I give it any throttle it just shakes and flips over.

If i hold it in my hand and arm it and give it slight throttle the props spin, but if I tilt it while I'm holding it the front motor stops. If I turn it 180, front to back, and tilt it, the opposite motor stops.
I assume this is why it's flipping over.

I tried reloading the original CLI dump, the updated CLI and starting over, but nothing I'm doing seems to be fixing whatever I touched. Is there a way to reset it back to factory settings beyond what I've done?

Any ideas are appreciated. Thank you for any help you can provide.

 

[rtkDarling]

When you go into the motors tab and spin each motor up individually are they in the correct order?

 

[Roadking]

When you go into the motors tab and spin each motor up individually are they in the correct order?

Yes, I checked that and they are all spinning the correct direction but the symptoms are like that would be the problem.

 

[Roadking]

This thing is driving me nuts. I checked and triple checked everything but I'm obviously missing something.
Here is what it does:
Tinyhawk won't fly

 

[Roadking]

could it be something I touched here?

 

[rtkDarling]

Make sure they're in the correct order as well, not just the direction they spin. I'm surprised that reverting to the default didn't clear this up...

This is the default CLI if you dare...



# Betaflight / MATEKF411 (MK41) 3.5.1 Sep 8 2018 / 05:32:10 (d9fb5ca13) MSP API: 1.40





board_name MATEKF411


manufacturer_id





# name


name Tinyhawk





# resources





# mixer





# servo





# servo mix








# feature


feature -SOFTSERIAL


feature -TELEMETRY


feature AIRMODE





# beeper





# beacon


beacon RX_SET





# map


map TAER1234





# serial


serial 1 2048 115200 57600 0 115200





# led





# color





# mode_color





# aux


aux 0 0 0 1775 2100 0 0


aux 1 1 1 1700 2100 0 0


aux 2 2 1 1350 1650 0 0


aux 3 13 2 1575 2100 0 0


aux 4 35 3 1600 2100 0 0





# adjrange





# rxrange





# vtx





# rxfail





# master


set acc_calibration = -125,69,1


set baro_hardware = NONE


set max_check = 2000


set rssi_channel = 9


set dshot_idle_value = 600


set motor_pwm_protocol = DSHOT600


set vbat_max_cell_voltage = 45


set vbat_min_cell_voltage = 32


set vbat_warning_cell_voltage = 33


set crashflip_motor_percent = 20


set small_angle = 45


set pid_process_denom = 1


set osd_warn_core_temp = OFF


set osd_vbat_pos = 2421


set osd_rssi_pos = 2372


set osd_tim_2_pos = 2389


set osd_vtx_channel_pos = 2403


set osd_craft_name_pos = 2442


set osd_warnings_pos = 329


set vtx_band = 5


set vtx_channel = 4


set vtx_freq = 5769


set vcd_video_system = NTSC





# profile


profile 0





set dterm_lowpass_hz = 80


set dterm_lowpass2_hz = 170


set dterm_notch_cutoff = 0


set feedforward_transition = 25


set iterm_rotation = OFF


set iterm_relax = RPY


set yaw_lowpass_hz = 100


set throttle_boost = 4


set p_pitch = 100


set i_pitch = 120


set d_pitch = 90


set f_pitch = 90


set p_roll = 100


set i_roll = 120


set d_roll = 90


set f_roll = 90


set p_yaw = 90


set i_yaw = 90


set d_yaw = 40


set f_yaw = 80


set p_level = 25


set i_level = 20


set level_limit = 25


set abs_control_gain = 5





# rateprofile


rateprofile 0





set thr_expo = 50


set roll_rc_rate = 80


set pitch_rc_rate = 80


set yaw_rc_rate = 80


set roll_expo = 60


set pitch_expo = 60


set yaw_expo = 20


set roll_srate = 60


set pitch_srate = 60


set yaw_srate = 60

 

[Roadking]

I tried the original CLI that it came with (which I saved first thing) and the updated CLI. I too assumed that reflashing would restore everything back to working order. The props are new too, and I was sure to put them on correctly (also triple checked that).
I'll keep trying. Thanks for your help.

 

[HighTechPauper]

I would try reflashing the FC with the original BF rev and dump the CLI back into it.

 

[Roadking]

PROBLEM SOLVED! Thank you very much for your help. What would I do without you guys.
Seriously, I'm trying to learn this and really appreciate your help. Everytime I break something I learn more. I think it's fair to say that in FPV if you're afraid of breaking something find another hobby.
There was a newly publish CLI which I flashed and reset everything and now it works. I think the older CLI's would have corrected the problem too, but I may not have been doing it correctly. Thank again.

 

[ecturner11]

I was inputting mockingbird setting on my tiny hawk 2 and something I did caused my entire beta flight to crash. Had to uninstall and reinstall it. And now no matter what I do, it will not connect to beta flight. Says failed to open port. I have uninstalled and reinstalled all the drivers and still nothing. Can I reset the drone to factory settings without using beta flight? And if so, how?

 

[HighTechPauper]

I was inputting mockingbird setting on my tiny hawk 2 and something I did caused my entire beta flight to crash. Had to uninstall and reinstall it. And now no matter what I do, it will not connect to beta flight. Says failed to open port. I have uninstalled and reinstalled all the drivers and still nothing. Can I reset the drone to factory settings without using beta flight? And if so, how?

You have a bad flash, you can reflash it again by using the boot button on the FC to get it back into bootloader mode so you can reflash the proper target for that FC.