Hi!
We have a quadcopter running pixhawk 2.4.8 using copter v4.4.4. after initial ground tuning we took it out for its flight. It was in althold during take off. it took off and after it barely got off the ground there was high yaw roll and pitch due to which it crashed. after looking at the logs we cant seem to make sense of why it happened.
Can someone please help in identifying the cause.
https://drive.google.com/drive/folders/1tyxYh49T7IraxZcdy9ayxSI9AagScEPP?usp=sharing
Here is a link to the log and a video of the crash:
Thanks
Have you checked that your motor order and directions are all correct?
Did you check that the orientation of your FC is correctly configured in the AHRS_ORIENTATION parameter?
Hi!
Motor order and directions are correct. FC is facing forward so AHRS_ORIENTATION is set to none.
Did you first follow the “First Time Setup” and “First Flight and Tuning” steps in the wiki?
yes we were following both. the drone is overpowered so we decided instead of taking off on stabilize or loiter we would do the first flight in althold and afterwards do autotune. but it crashed before that:(
It still looks like Motor Order. Confirmed using Mission Planners Motor Test understanding what motors should run when you select the A-D buttons?
I strongly suggest you follow these instructions to the letter
https://ardupilot.org/copter/docs/ac_tipsfornewpilots.html#first-flight
First takeoff in altitude hold mode is a very bad idea.
hey!
motors were tested for cw and ccw and had appropriate props on. we had a crash recently because of this so we took extra precaution there:p
And the motor order? Tested with Motor Test?
Page down to “Checking the motor numbering with the Mission Planner Motor test”
Hi!
Thank you and we’ll definitely start in stabilize from now on.
As for this we still aren’t sure of the cause of the crash and don’t wanna chalk it up to althold considering the way it crashed.
If possible could you provide some reasons as to why it crashed in the way it did?
yep abcd were in correct order
It sounds like something that is addressed in section 2.15 of the blog post
Try that if all else fails
As @amilcarlucas says, if there’s nothing else wrong with your setup, it could be that the default PID gains are too high.