Was flying perfectly well on stock PID settings but wanted to see if autotune could improve things.
About 3 minutes into the tuning whilst still on the first axis it suddenly flipped over and crashed without any warning. It looked like an overly aggressive roll command caused it rather than a motor cutting out or stalling. Conditions were calm at the time.
It had completed about 90% of a previous autotune without incident but didn't have enough battery to finish, was in the air for about 15 mins without incident in autotune mode but had to land.
Sent it up again with a fresh battery, this time without any payload to help ensure sufficient flight time to complete tuning on single lipo (New C of G was accounted for by shifting lipo position) and the crash happened.
RATE_RLL_FILT_HZ and RATE_PIT_FILT_HZ were set to 10hz as recommended for larger props and battery voltage scaling of PID gains was setup..
Spec:
Pixhawk on a 900mm Y6 frame with T-Motor 4008-18 380v motors, 10000mAh 6S lipo, 15" props.
If anyone fancies looking at the log, it would be most appreciated - I've checked a few things but still unsure on the exact cause - possibly the default AUTOTUNE_AGGR parameter which I left alone as per the instructions was simply too high?
Replies
So, against my better judgement, I tried Autotune again on the same craft. Geo Fence was turned off this time and the autotune aggressiveness lowered to half the default value.
It did EXACTLY the same thing again, flipping upside down on the roll axis and promptly crashing.
There are no errors in the log that I can see, so I think it's safe to say my issue is not geo fence related, as per the initial analysis.
Log attached - would appreciate if anyone can spot the issue this time.
226.BIN
Well it's not really a coincidence. Autotune demands large and fast attitude changes which demand rapid RPM changes from the power train. Any ESC, motor, or battery problems usually show up during auto tune. Look at it this way, if yout copter can make it through an auto tune, it will probably make it through just about anything the autopilot would need it to.
Mikko Korhonen said:
Mikko: looks that your batt drops and inmediately your copter crash
Thanks for taking a look. Batterys were full. I don´t understand this vcc or power value graph..i see a drop in the graph and i understand that voltage/current (?) went down at the end.. copter went mental before hitting the ground, it had plenty of power !, that didn't looked like a "brownout" etc. crash, i had one and i remember the power drop in that log..but like i said, i dont know how to interpret these power issue logs. Vibes and imu1&2 are next to look into. Thanks, im trying to find some info...gooogle! :)
Mikko,: your batt was full when you try AT? It's look low when you crash, can be the problem?
here´s my autotune crash bin. file
2.BIN
Cala said:
Yours and Ben log is the same?