Closed darkoudeas closed 5 years ago
What I see in the log is that was a combination of following things:
I see no software problem, only hardware/user related
Thank you very much for your response.
I just recalibrated ESCs and will see how it goes.
1) Is angle mode protecting MR from flipping? 2) The AUX that enables airmode, also enables alt hold (same range) . Not really sure if activated during crash, but it logged only the airmode. Is this normal?
If you have 2 minutes to spend, have a look at the flight crash video. I understand that this is not the scope of github tracker.
Angle mode is not the solution. What you need is permanently enable AirMode (as a feature) which prevents those kinds of things where throttle is low. There is nothing new on the video that did not showed on the log itself. Evident lack of conrol on low throttle
Dear all,
I understand this is not the proper place for such a question. But it is driving me crazy since it happened back in August and didn't manage to get help in forums.
Omnibus F4 v5 equipped drone was flying just fine with Inav 1.9.1 . With no hardware changes I upgraded to inav 2.0 . After a few flights (generally it was flying smoothly) the following happened:
Attaching log file (have a look at 9 sec) and cli diff I personally don't believe it is a bug, but some kind of hardware "fault" or misconfiguration. I downgraded to 1.9.1 and had some test flights this week (7 batteries) without any problem. But I don't feel confident to make long range flights .
cli_diff.txt log_RC_VID_0008.TXT
I appreciate any help and sorry for posting here for support issues. Thank you