-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Crash: Pixhawk 2.1 (Cube) with v1.7.4 Beta firmware #9260
Comments
@r0gelion The log ends when the pilot was maneuvering the drone in position control mode. Until then I cannot see any strange behavior, if you actually use the 3D view you can see that the vehicle followed the pilot's commands very well. |
@r0gelion Do you happen to have a mavlink log of this flight? |
@RomanBapst this is the log: |
@dagar @LorenzMeier This is a csv file which contains the relevant data from this flight. We analyzed it with @bkueng and found that the mavlink connection must have dropped about 4 seconds after the ulog stopped. This somehow makes sense because the logger writes to the SD card in certain intervals. Line 202: this attitude sample roughly corresponds to the last attitude sample in the ulog. While in the incident reported by @JohnSnowball the mavlink connecting did not seem to be interrupted after the log stopped in this case it clearly did. |
What was the state of the vehicle after the crash? |
Closing: #9271 (comment) |
Flying an F450 with Pixhawk 2.1 (Cube) and Here GPS, loaded v.1.7.4 Beta (e63f9d9).
The pilot reported the vehicle ended a mission and it was hovering in position hold and suddenly it flew to a side in a straight line descending and it crashed on a roof.
Here is the log:
https://review.px4.io/plot_app?log=34c46166-8fee-4cb8-b7de-38517de4122b
Thank you!
The text was updated successfully, but these errors were encountered: