Hi. - Happy new year.
Im new to copters but have been using arduplane for a while.
I have been setting up a new quadcopter and following Dave Cs guide. Its flying very nicely in all modes and I have done a few auto missions around my field.
Before the problem flight I had done exactly the same Flight Plan (route and heights) except at speed 2m/s.
For the second flight I set 6m/s and a halfway waypoint with speed change to 10/m/s. On the way back there was another speed change down to 2 m/s.
Height keeping on this last flight was not great but on the way back it just went into full climb reaching 227m before I rescued it. The green height bar on the flight data display is defiantly below.
It is not an error in the flight plan and the alt-error feed shows an increasing error.
I just cant see why it did this.
Any help appreciated. Logs attached.
Vince
Replies
Tony.
Not sure thats the right tlog as nothing happens.
My ‘headline’ flyaway was just in auto. It was behaving in all other modes, Loiter, RTL etc, and on previous slower missions. It was like it got an adrenalin buzz from flying fast and then didn’t want to turn the motors down. I vaguely remember I may have tweaked the ‘Throttle rate P’ up before that flight but not much.
Previously, while doing the PID tuning I had set a value on CH6 slider (cant remember what it was) but while adjusting it the copter just started climbing. It wasn’t until I got the throttle at the bottom that it chopped the motors. Whatever I was adjusting turned the throttle into an on-off switch. Fortunately I managed to drop the slider and recover.
The issue of covering up the pressure sensor from turbulence, I suspect would only cause height inaccuracies. I would be suppressed if it was responsible for these runaways.
Vince
Data files of a recent upset - probably prop downwash. The copter was on the bench for ages so its a big file. Crash is at about 95%
2013-01-03 14-26-10.rlog
2013-01-03 14-26-10.tlog
2013-01-04 14-47 78.log
log file for that flight uploaded
I think the strange home dist is after the last W.P. when it goes into loiter. GPS must have been OK as route nav was ok.
Is there a guide to de-bugging with the log files? I can graph log data in the CLI but cant see much different from the tlogs.
Did a 60 waypoint grid flight this morning at constant height and speed - no probs. Not confident it wont go ballistic again though.
Vince.
2013-01-02 11-56 65.log
Looking through the tlog, at 117sec the ‘throttle’ (graph this) seems stuck above 80 units. While the speed is high the height is not increasing much but after the slowdown to 2 m/s this excess throttle makes it climb.
Why is ‘throttle’ stuck above 80?