Hello guest, if you read this it means you are not registered. Click here to register in a few simple steps, you will enjoy all features of our Forum.
This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Betaflight flashed to 4.1, quad now flips after arming
#1
Hey everyone,

Another newbie question - LOL

I flashed my FC today to BF 4.1.1 (previously was running 3.5.0).  After the flash it seemed like my FC was completely erased so I had to start over, no big deal.  I got everything all set including adding my telemetry back.

It seems like the default PID settings in BF 4 are perhaps more aggressive?  When I arm my quad now, it seems like the blades spin up so fast that my quad just flips over and disarms.

I double checked that my motors are all spinning correctly, and that my props are installed correctly.

Any suggestions on what I should look at to troubleshoot this?  I'm wondering if there is just a BF setting I've overlooked somewhere.

Thank you as always!
Reply
Login to remove this ad | Register Here
#2
Things to check.

FC orientation, 3D model in BF correctly corresponding to real-life movement
Motors direction
Motors mapping, the correct signal to the correct motor
Props mounting direction.
All radio trims are centered
[-] The following 1 user Likes voodoo614's post:
  • eforden
Reply
#3
Run the following command in the CLI and it should fix your problem...

Code:
set gyro_1_align_yaw = 1800
save
[-] The following 1 user Likes SnowLeopardFPV's post:
  • eforden
Reply
#4
(19-Nov-2019, 01:26 AM)voodoo614 Wrote: Things to check.

FC orientation, 3D model in BF correctly corresponding to real-life movement
Motors direction
Motors mapping, the correct signal to the correct motor
Props mounting direction.
All radio trims are centered

All of those look good, BF is correctly responding correctly to the stick movements on my transmitter.
Reply
#5
(19-Nov-2019, 01:36 AM)SnowLeopardFPV Wrote: Run the following command in the CLI and it should fix your problem...

Code:
set gyro_1_align_yaw = 1800
save

I just tried that, but even after the "save" command and the quad disconnecting and reconnecting, it keeps defaulting back to 2700.. so, I instead went to the Configuration page, under the Board and Sensor Alignment section and changed the "First GYRO" drop-down from "CW 270" to "CW 180" and saved it..  I'm running the latest BF Configurator 10.6.0 so not sure why it wouldn't save through the CLI.

I'll try out the quad first thing tomorrow morning to see if it worked..
Reply
#6
(19-Nov-2019, 02:49 AM)eforden Wrote: I just tried that, but even after the "save" command and the quad disconnecting and reconnecting, it keeps defaulting back to 2700.. so, I instead went to the Configuration page, under the Board and Sensor Alignment section and changed the "First GYRO" drop-down from "CW 270" to "CW 180" and saved it..  I'm running the latest BF Configurator 10.6.0 so not sure why it wouldn't save through the CLI.

I'll try out the quad first thing tomorrow morning to see if it worked..

That's weird that it wouldn't save in the CLI on yours because it works fine on mine. Yes, the result you are looking for is First GYRO set to CW 180 so what you've done in the GUI instead is correct.

It will fix your problem. Don't ask me how I know Big Grin
[-] The following 1 user Likes SnowLeopardFPV's post:
  • eforden
Reply
#7
Can you post your dump file?
Reply
#8
(19-Nov-2019, 02:43 AM)eforden Wrote: All of those look good, BF is correctly responding correctly to the stick movements on my transmitter.

on the set page, first tab, that shows "calibrate accelerometer". There is a graphical representation of your quad. rotate your actual quad clockwise? does the graphic match the movement? pitch it forward? does it match? roll your quad left. does it match? if one of these actions does not follow suit, then one of your axis is off and needs to be adjusted. i.e. ROLL degree, YAW degree, PITCH degree located within the Configuration tab page.
Reply
#9
(19-Nov-2019, 02:58 AM)SnowLeopardFPV Wrote: That's weird that it wouldn't save in the CLI on yours because it works fine on mine. Yes, the result you are looking for is First GYRO set to CW 180 so what you've done in the GUI instead is correct.

It will fix your problem. Don't ask me how I know Big Grin

Yep, you were correct, that fixed the problem!!

I'm definitely curious about how you figured that out...
Reply
#10
(19-Nov-2019, 01:58 PM)eforden Wrote: Yep, you were correct, that fixed the problem!!

I'm definitely curious about how you figured that out...

It was an intelligent calculated guess based on a bit of knowledge and my own experience. I've got a Matek F405-STD flight controller which runs the MATEKF405 target and when I updated that from Betaflight 3.5.7 to 4.0 it required me to manually reconfigure the gyro orientation from the default of "270 CW" to "180 CW" as detailed on Matek's main product page for that FC (HERE).

The flight controller for the Tyro99 and the Tyro109 both use the same MATEKF405 Betaflight target...so...

2 + 2 = 4 Big Grin

I'm glad you are now back flying again Smile
[-] The following 1 user Likes SnowLeopardFPV's post:
  • eforden
Reply
#11
(19-Nov-2019, 06:52 PM)SnowLeopardFPV Wrote: It was an intelligent calculated guess based on a bit of knowledge and my own experience. I've got a Matek F405-STD flight controller which runs the MATEKF405 target and when I updated that from Betaflight 3.5.7 to 4.0 it required me to manually reconfigure the gyro orientation from the default of "270 CW" to "180 CW" as detailed on Matek's main product page for that FC (HERE).

The flight controller for the Tyro99 and the Tyro109 both use the same MATEKF405 Betaflight target...so...

2 + 2 = 4 Big Grin

I'm glad you are now back flying again Smile

Ahh!  Very nice, you were spot on with the MATEKF405.  I just took a look at that link and see the highlighted banner about updating that after flashing to BF 4.x.  Thanks so much again for your help, I just realized too that I completely forgot about specifying that my quad is the Tyro 109!  You obviously have a great memory to remember me from the other issues you've helped me with so far  Big Grin

Onto my next project - adding GPS to my Tyro 109!  Should be here later this week...
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Announcement Betaflight 4.5.0 *** FINAL RELEASE *** Now Available SnowLeopardFPV 1 222 28-Apr-2024, 05:50 PM
Last Post: SnowLeopardFPV
  Announcement Betaflight 4.5.0 Release Candidate 4 Now Available SnowLeopardFPV 8 2,378 15-Apr-2024, 06:50 PM
Last Post: SnowLeopardFPV
Exclamation Betaflight Configurator - HELP iFly4rotors 10 445 04-Apr-2024, 12:08 AM
Last Post: Pathfinder075
  Betaflight Configurator Windows - Bluetooth Connection norseman73 1 173 17-Mar-2024, 02:55 PM
Last Post: SnowLeopardFPV
Sad Mac/Betaflight no longer recognises Flight Controller after flashing Sev 1 198 02-Mar-2024, 03:31 PM
Last Post: Sev


Login to remove this ad | Register Here