I've got an issue with my ArduCopter skyrocketing in the middle of its flight plan. I've tested this a few times and have been able to reproduce this glitch on at least 3 occasions. The quad will start off fine, and at some point in its flight it will suddenly begin climbing rapidly without any input from the controller.
What's weird is the log shows that it remains in Auto mode, yet the ThrOut value is ceilinged, despite no input from the control. When I revert to stabilize mode, the throttle value drops back to where it is. Clearly the quad remains in contact with the radio, and clearly it is staying it auto, and clearly it is aware of its own altitude as it logs its enormous climbs.
This is absolutely horrible. Even worse than releasing it with LOITER_TURNS malfunctioning.
Note how ThrOut spikes, while still in auto, and it reads an accurate altitude and ignores the WPAlt it is supposed to be maintaining. I don't see how this could be a hardware problem or pilot error. I tested out the ThrOut outputs in auto while tethered to USB and the ThrOut values are lot logged while in Auto. So it seems like this could not be coming from my controller (Spektrum Dx6i). At first I suspected it was slipping out of Auto mode somehow, but this log seems to rule that out.
Replies
Hi,
I get the same problem. Take a look at my discussion at the 3.0 forum. Could be a reason why the drone looks like rocket. If you find a good way to solve this huge problem, let me know !
Cheers
Some vibration data.
Another flight with same type of rapid ascent. Maybe Chris is right about the vibration; the ThrOut value is super shaky when in LOITER and AUTO, but looks pretty smooth when in STABALIZE. I'm also wondering if sunlight might be affecting the Bar Altitlude; I read about that on here.
Chris Anderson suggested this may be a vibration issue, which may be possible. But to me if this were caused by vibration I would think I would see inaccurate altitude readings. The logs suggest the AC was perfectly aware of the altitude it was supposed to be at and the altitude it was at. The only thing I see that is off is the ThrOut value, which should be ignored if it is in Auto mode.