During a test with Pixhawk 2, Arducopter 3.6.11, my drone just turned upside down on takeoff. Upon looking at the logs, I found that the there was a higher desired roll. I have been testing the same drone for quite a sometime, say around 2-3 months but I have never faced such issue.
2020-09-30 11-39-01.bin (196 KB)
Update to either 3.6.12 or 4.0.4
Make sure the copter is on a level surface before taking off. Make sure you take off directly after arming, do not wait too long before taking off.
Thank you for the response. I have two questions related to your reply:
Update to either 3.6.12 or 4.0.4 - Is there any existing issue with version 3.6.11?
Make sure you take off directly after arming, do not wait too long before taking off. - Why do you say this? Does waiting for few seconds cause any problem?
Regarding the update, can you precisely point out what is the issue with the version and how can we reproduce it? I am asking the question because I have been using the same version for around 6-8 months and have not seen anything like this.
Just went through the release notes https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/ReleaseNotes.txt
I could see only two changes in version 3.6.12 on line number 315.
Changes from 3.6.11
- More ChibiOS fixes for I2C storm
- COMPASS_SCALE param to allow manual correction of compass scaling
Just wondering how these changes are related to my issue.
Those changes are not fixing your issue. Your issue is caused by the stuff I told you above
But … do you want to have an I2C storm???
No certainly not
I just wanted to know about the specific issue. Thanks and I’ll update
I see high values at RCOU.C1 and RCOU.C4 and low at RCOU.C2 and RCOU.C3, so it must flip over pitch axis instead of the roll. Could it be wrong connection to motors?
I have cross-checked the motor connection. I think that RCOU.C1 and RCOU.C4 values could be high because of the high desired roll values incoming from the flight controller.
Triple check your motor connection order!
I have not touched the motor connection since a very long time and I have been testing the drone with the same motor connection for more than 2 months. Had it been the wrong motor connection order, then I would have observed the same on the first day itself.
What I can see in the plot is that, at timestamp 12:06:42.688, all RCOUT had 1161 value and desired roll was -3.61. At the very next timestamp 12:06:42.788, the desired roll becomes 2.39 and there are changes in the RCOUT values.
Also, the landing gears of my drone are small, so as soon as the drone rolled a bit, the propellors touched the ground and it turned upside down.
I can confirm again that the motor connection order is perfectly alright.