Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copter: hard Yaw can cause all motors to idle when yaw released. #836

Closed
AndKe opened this issue Feb 11, 2014 · 5 comments
Closed

Copter: hard Yaw can cause all motors to idle when yaw released. #836

AndKe opened this issue Feb 11, 2014 · 5 comments
Labels

Comments

@AndKe
Copy link
Contributor

AndKe commented Feb 11, 2014

It's best if you try this for yourself, be sure to have idle spedd up on motors, or some might stall.
Fly at least 5 meters AGL (in my case, position hold) , and apply full yaw, You'll get up to something around 200deg/sec (default) let it reach full rotation speed, then release stick.
At least 50% of the time, rotation will break, the all motors will go to idle for half a sec or so,. causing a fall, then they recover.!

Attached screenshot:
from position 26.5, you can see 3 motors speed up, 3 go easier, I let the yaw stick go around pos27.16 you can see the pihhawk counter the rotation - then all motors go to thr_min, and it falls.

hard yaw1

And a zoomed in:
yaw2

@rmackay9
Copy link
Contributor

AndKe,
can you post the original flight logs? My guess is that the copter is in AltHold mode and it's related to centripetal forces throwing off the inertial navigation acceleration estimates.

@AndKe
Copy link
Contributor Author

AndKe commented Feb 12, 2014

Logs:
http://flyfoto-nord.no/stickbang_yaw.zip
I did it in loiter, the GPS/compass is not perfectly centered, it's 3-4cm toward front, making such position hold a greater challenge :)
Yes, this is just one of my crazy tests, I also used the flight to test rate_yaw_i (which got increased after this flight -i notices there's no option to tune it using RC6 ?)

Anyway - With your knowledge, you're most likely right regarding the reason, but I think it's funny it did not happened at the greatest rotation speed, but after the yaw speed were successfully reduced.

I did not test how fast/much rotation is needed,(like, if 180degree at full stick is enough) but I can imagine a fast approach with hard yaw right before touchdown, could result in crash.
Pixhawk is surprisingly fantastic :)

@AndKe
Copy link
Contributor Author

AndKe commented Feb 17, 2014

I guess this user's motor stalled/got out of sync while testing: he's log is not as clear, but I see similarity:
http://diydrones.com/forum/topics/ac-3-1-1-crash-need-help-in-analysis

@rmackay9
Copy link
Contributor

rmackay9 commented Mar 4, 2014

ok great. i'm going to close this issue then. If that's not ok just post a comment below and we can re-open.

@rmackay9 rmackay9 closed this as completed Mar 4, 2014
@AndKe
Copy link
Contributor Author

AndKe commented Mar 15, 2014

Please consider re opening.

This is pretty dangerous in hard wind, I did some one fast yaw today, and wind flipped the hexa once I released yaw, (because motors went to idle, and the angle toward the wind caused a extra quick flip) - It recovered with great authority and continued as if nothing happened :)
Please note that my hexa do not have sync issues, one that have, would most likely crash.

I do not have a new log for you, because logging stopped at line 220k due to the usual FAT/cluster problem, I am using a sd that have less problem with that, but not perfect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants