-
Notifications
You must be signed in to change notification settings - Fork 19
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
Tricopter looses control while doing “air jumps” #7
Comments
I haven't noticed such behavior, do you have a video or log of the behavior? |
unfortunately no. |
Have you calibrated the ESCs?
|
ESCs were calibrated when I upgraded to version 0.4 of triglight. I think Since I don't have flight data I suggest to just keep an eye and test this
|
I can test on mine next time I get to air. Weather is challenging.
|
is the acc data used while in acro mode? I might have forgotten to calibrate the accelerators after I flashed master. |
ACC is not used in acro mode. On 18 January 2016 at 10:37, pqueiros notifications@github.com wrote:
|
Closing this issue since could not reproduce it in the rebuilt tricopter, 9 batteries done without issues. In the post crash analysis I have noticed that one of the front motors was missing the lock washer that presents the shaft from sliding out. I was not sure if this was from before or after the crash. If it was from before it could have been the root cause of the crash since by doing full throttle could trigger the rotor to slide and lock half way making the copter tilt and crash. I think this was what happened. :). |
Did you use ground wire for ESC signals when you had this issue? |
pull latest betaflight to 4way-interface
Tricopter looses control while doing “air jumps”.
Use case:
Expected result:
Experienced result:
This occurred two times today, last crash was a really bad one (time to upgrade hw :)). I could not recover the flight in both occasions. It felt like something in the controller saturated somehow.
Normal flight felt quite ok.
Occurrence rate 2/10. Seems that requires a a significant amount of time at full throttle.
Source code used was f6d8753 from master.
cli settings:
99_tmp_cli_settings_before_autotune.txt
The text was updated successfully, but these errors were encountered: