My quad has been flying pretty well with 3.1RC7 but i have a persistent issue with yaw and roll pitch instability that is most obvious when flying in auto or guided mode.
The quad flies great in stabilize mode, alt hold and loiter without major issue. The quad will accept and navigate to waypoints in guided mode and has successfully run auto missions. However, if the mission calls for subsequent waypoints with more than about 90dg difference in heading, the rapid yaw commanded by autopilot is immediately followed by a roll/pitch instability and a dramatic loss in altitude .
This has happened 3+ times, with both 3.0.1 and 3.1RC7. Usually i note the signature "wiggle and dip" in time to throw it back into stabilize mode and save it. Today i wasn't so lucky and the quad hit the dirt after i gave a guided mode waypoint at ~ 180 heading from the quad's previous commanded position. The quad went unstable and dropped 30+ft to the field below.
After replacing broken frame parts and checking over the system, i took it for another test flight in stabilize mode only. I noticed during this flight that dramatic yaw input from the sticks shows similar behaviour in stabilize mode.
Is this a tuning issue? Is my Yaw PID set too aggressively (I'm at default)? Is there something in my logs i should be looking for to determine what the root cause of this is? I've reviewed my tlog from the guided mode flight that resulted in crash and i can't see anything obvious.
F450 clone frame, APM 2.5, xbee telemetry, 3700mah 3s LiPo, Turnigy 1000kV motors (D2830/11), GemFan 1045 props, canon sx 230 downward facing cam as payload. AUW is ~ 1400g. hovers well at ~45-50% throttle.
My tlog is attached. I can see the event, but nothing indicating what led up to it. You'll note that i accidentally left my telemetry on for a bit after the funny business...
Thanks in advance for any help!