The arducopter tuning guide.
This guide was written at the time of the release of Arducopter 2.8.1 FW. It is a compilation of everything I have gathered from the experts in the field of flight controller tuning. It will help give you an understanding of how to tune any rotor based flight controller, but its specific to Arducopter and this firmware release.
I will update this as necessary, or if you can convince me any of it is incorrect just post below and I’ll update this text.
There is a summary/quick reference at the bottom, so once you’ve read this rather rambling explanation you won’t have to again, other than to check details :D
Tuning your flight controller is essential for a perfect flight. Even a fully stock frame will fly better if you tune. The default params will be close, but your battery or motors might be performing differently, your air maybe ‘thinner’ compared to the developer that last published the default params, so you should tune.
What we are trying to achieve is control. We start to accomplish this by modifying the amount of P, I and D in our control loops. All three react to our stick inputs and the errors created by measurements from our sensors, and all three will help us fly better. If we do not have enough of any of the params the copter will not feel like it’s under control, it will wander about, not resist wind and be hard to fly. Too much of any of the params and the copter will seem to have a mind of its own. It will over-react. At best you will see it oscillate, very fast, not so fast or somewhere in between, depending on which parameter has been overclocked. At worst it will simple flip over on take-off or be very unpredictable in flight.
We need to find a balance. You can tune each param up individually, but one will have an effect on another. Therefore we must tune one, then another, then go back and see if we can retune the first one again, this is the balance.
And this is where we adjust those parameters – Mission planner config page:
Before you start:
So let’s start tuning
Everything you read below will be demonstrated in the tuning video further down, so you know what to look for, and at the bottom is a summary for quick reference. I think, however, it’s important to include as much information here as possible as anyone starting into this hobby will often find this process to be a bit of a black art.
I’ve found the quickest way to tune the arducopter is to start with rate_D, (but you simply can’t do this unless you can hold your beast in hand or in a jig as the copter won’t fly without any rate_P or I) so a more universal way to start, and actually a more informative way is to start with rate_P.
Since this is about learning for everyone, let’s do it that way. I’ll give a brief low-down on the ‘rate_D’ tune (or Dave C tune, as it’s become known) ‘ later. (BTW, that’s very flattering but I’m only relaying info from the real experts, but hey, if I’m gonna be famous, why not for doing something I love :)) Anyway....
STEP ONE - Tuning rate_P
STEP TWO – Tuning rate_D
NOTE: once you have found your rate_D you can try something interesting - you will have to hold onto your bird for this obviously. Set rate_P to zero, then crank up your rate_D as you just have. You will discover that these fast oscillations occur at pretty much the same level of rate_D, no matter what you have set rate_P to. This is why I think it’s more than possible to start tuning rate_D then move on to P. But that’s a shortcut, and this is not what this guide is all about.
STEP THREE – Tuning rate_P even more
Congratulations, your copter should be flying better than it ever has done before.
STEP FIVE - HEAD OUTSIDE!!!
For now set Stab_P at 3.0 - 3.5, closer to 3.0 if you have a high power machine, just to get you flying in stab mode. Then spend your time tuning rate_I and stab_P.
If you find your set up immediately too harsh, back off on rate_P and rate_D by 10% each, and try a lower i-term, if it's still too harsh do that again!
All that’s left is to watch the video below so you can see what I’m describing and head outside for fine tuning. Oh, and await part two of the guide and amendments from any discussions raised, then we will have a proper tuning guide that will be integrated into the wiki advanced tuning guide :D
Results for tuning in this video were
Oh and as promised, below is Part One of the Summary Guide. I aim this to be on one sheet of A4 and tell you everything you need know ‘in the field’.
Summary of what you are looking for
Too much rate P will oscillate quickly, and cause to copter to sound angry under stick input, bouncing rather than smoothly following your inputs. It will also shake more at full throttle and under hard turning.
Not enough you will not feel like you have full control. It will feel sloppy and be very easy to over correct with your inputs. It will feel delayed.
Perfect is where it feels locked in, stiff in the air, but not shaky. (although if I’m sport flying I turn it up a bit for maximum ‘wang’ and just tolerate the slight oscillations)
Too much rate_I will oscillate if you get high enough (a much slower oscillation than a rate_P shake). But quite a long while before it oscillates it will have other detrimental effects on flight performance, like a sluggish feeling or a tendancy to flip over on take-off. This is why I suggest tuning this in flight rather than in your hand/jig.
Not enough will cause the copter to get pushed by a constant wind, then it will fight back using just P. It will not hold a very firm angle during forward flight and will need more correction. This will not be as smooth as it could be in either case.
The perfect amount will cause the copter to lean gracefully into a constant wind, but also allow you to set a lean angle and stay there as you fly about. As you dial rate_i in pay close attention to the feel of the copter, you are not looking to create oscillations here at all, you should notice a strange ‘feel’ long before this point.
Too much rate_D will oscillate very fast, you will see a twitch forming then a fast buzzing oscillation
Not enough rate_D will simply mean you can’t dial enough rate_P and so you will suffer the effects of having rate_P too low.
A perfect rate_D will help fight the wind and follow your sticks as its fast to react, but will also allow you to reach a maximum rate_P level for you frame, thus giving better control.
Below is my vibration log at Z axis:
Is it good enough?
since my quad still climb slowly at alt hold and loiter, even after increasing the THR_MID at my hover point as Richard Boyhan suggest.
I will have another look at the logs and do some extra flights.
Also will enable the inav logs.
If I'm not mistaken the alt baro and alt inav should match, if not too much vibration.
It is quite interesting to figure it all out but sometimes frustrating as well.
As I'm using a TBS like quad it's quite time consuming when changing setups (vibration reduction).
In a way it is all part of the game :-)
Still prefer this than out of the box and nothing else to configure.
I just made another flight to collect some data.
The accel-z doesn't look good unfortunately.
As mentioned I also enabled the inav logs.
The quad rises slowly to a certain point, then slowly descends to the initial alt hold setting, same for loiter mode.
I also included my latest log file.
Any thoughts are welcome.
To tune Alt Hold you should start by reducing the Accel P term keeping Accel_I 2xP. You should not need to tune the rate terms.
I solved the accel-z vibes and althold is fine now.
Vibes went away by adding a smale plate suspended by O-rings and some Kyosho zeal tape in between the APM and the plate.
It just needs a little tweaking, will keep the comment of Leonard in mind.
What I saw yesterday during the test filght was that in althold it dipped a little when doing fast roll commands left to right and back. When I did it more slowly I did not see this behaviour, so maybe a little more ALT_P?
Loiter an RTL are fine too but also could use a touch of PID tuning.
Nice tuning weather here so I've been out on the field and emptied about 6 lipo's.
I've been tuning the loiter and RTL parameters.
Loiter is fine but sometimes it twitches a little and then starts off in a toilet bowl spin (sometimes quite violently)
The next time I switch to Loiter it is very calm.
For the RTL part...
This is working but if I'm about 30m for the home position and I switch to RTL it very quikly picks up speed, overshoot a little, slams into the brakes (heavy tilting) and goed into toilet bowl.
When I engage the RTL from a closer distance it works well.
Auto landing is working as well.
When it is in a smooth RTL, it loiters for about 5sec, slowly descends and after a couple of minor hops it settles down.
Any thoughts on what to verify?
Here are my parameter settings (TBS like frame, 1100KV motors, 900gr weight)
I've just spent a couple of days trying to work out the same problem.
Flew beatifully in Stab, Alt hold was great, and I could get loiter in calm conditions almost rock solid (except for the MTK drift).
If the Hex was disturbed it went into the 'toilet bowl' manoeuvre, which, if left unchecked would result in a crash.
I found the most response was from Rate Loiter, lowering the P to 2.4, halved D to 0.2 and I down to .05 although it could probably have stayed where it was.
I was also able to get Loiter Speed to 0.7
The Hex still wandered and was not as locked in as I would like.
The biggest difference was made by replacing the MTK GPS with the UBlox.
I can now throw it around in Loiter, let go the sticks and it just locks into place.
Although sometimes I notice it gets into a drift to the right, and will just keep drifting until I give a bit of stick correction which locks it into that spot. It looks like one of the relocation variables is not being reset properly when the sticks are released.
Thanks for the feedback.
Sounds indeed lilke the same issue.
I'm also using the MTK GPS with an APM1.
I will try to tweak the Rate Loiter settings like you suggested as soon as the weather is fine.
I lowerd the loiter rate values to P:4 but not enough it seems.
Can someone suggest the parameter to change so the throttle stick position is about the same in Stabilize as in Loiter?
After updating to the latest firmware, when I go to Loiter from Stabilize the quad takes off rather quickly up. In Stabilize the throttle stick needs to be about mid point to hold an altitude about 5 meters. The stick needs to be only about 10% up to get Loiter to that altitude. This makes transitioning between modes problematic.
Second question, since I didn't save the parameters before I updated the firmware, is there any way to recover them from old flight logs? Loiter also jitters around a great deal now while Stabilize flies well. It would seem if I could recover those previous values I might just set the current parms to those and regain Loiter stability.