Hi,
I am finding that in firmware, arduplane 3.0.3 (I couldnt find a 3 forum), autotune: doesn't allow pilot input. It does seem to oscillate at first, then get super smooth, but never allows pilot input. It seemed to allow it on ground, but perhaps tuning dulls it down too much based on calibrating before takeoff?
Replies
I just tried it and it works great.
Maybe your radio calibration is off or you have low rates. You must get to 100% roll and pitch input for it to tune. I did it for one flight and recorded the value. I decided to do more tuning cycles and the PID values did increase. Don't give up too soon as it takes lots of cycles to get to the final PID values.
.
Here are the PID settings after autotune. looks like the roll never changed from default. The pitch does look different. I've also attached logs.
long flight several loiters peace drone 2014-06-12 20-32-12.log
I do not have an airspeed sensor. As you can see from video, it flys loiter quite well. The "ACRO" mode however did not provide enough pitch control for realistic flight.
https://www.youtube.com/watch?v=-xYFkBzWO_E&feature=youtu.be
Here is video of it flying in loiter. There is some oscillation that makes me think P is too high.
Peace drone: http://youtu.be/bxWtf24hlVs
I would try some basic manual tuning using the tuning guide in the wiki. Just leave the I and D values at zero to start. fly around in FBWA and keep turning up the P values until the plane responded reasonably well. Then try autotune and see what changes it does to your I and D values. You might find Autotune Level 5 to be not enough. I find 7 works best for me.
reserved
The following are the steps that I took
Description of behavior in autotune:
Could I be causing the problem by checking surfaces in autotune mode while plane is parked?