after doing the AutoTune the drone becomes too responsive (over sensetive)


After I did a AutoTune my drone became too responsive.

Before AutoTune flying was way more pleasant.

To rollback these settings do I have to change the PIDs to it's defauld settings?

This is my setup:

Pixhawk with Hexa Arducopter 3.2-rc14

Mission planner (Beta)

Below the screenschots of the PIDs before and after AutoTune:

i'm not familiar with these settings and not certain what to change.

any advice is welcome!

Views: 7106

Reply to This

Replies to This Discussion

I had similar result in my cuad and I change stabilize roll and pitch to 7 and flies smoother

Aha, my gimbal was active during AutoTune !!!!

Schould I power off the gimbal and just put the camera on it for the weight?

Please advice me on this.

Have a look at my previous answer, please...  "If you have a gimbal mounted it should be removed before attempting AutoTune, or at least secure all moving parts so nothing is hanging loose."

Instead of the camera you may want to put on something less valuable with the same weight during AutoTune and testing...


I did an Autotune yesterday as well and ended up with very high values


X8 Skyhero 850


David Ardis

There is the RC feel parameter you can change too.  Its in the tuning parameters I think, and maybe basic?  I cannot remember exactly where it is.  One way makes the response crisper and the other slower.  And by default I think it is set to full crisp response.  It works like expo I think.  Don't use expo in your transmitter to change the feel.  The APM does better with full inputs and letting the computer do the expo or feel changes.

The RC-Feel is not like Expo, it is basically a low-pass-filter on the stick inputs.  Expo curves the inputs so they are softer around the middle, but RC_Feel slows down any input changes.

You should also have a look at the Accel Damping parameters.  These can also really soften up the feel of the machine, while still allowing tight PID settings to allow the aircraft to be stable in winds.

I'm not sure if they are in the basic parameters, but you can see them in the Full Parameter list.

Ok, so here are the parameters you want to play with. I do not know why these seem to default to zero on 3.2.  During the development phase for 3.2, we used these.  They do not show up on either the Basic or Advanced parameters pages, but only the Full Parameters list, but they have absolutely no information attached to them.  I'm looking into why this is.

In the mean time, this is where you see them:

Try setting ATC_ACCEL_RP_MAX to 72000, and ATC_ACCEL_Y_MAX to 54000.  Then set ATC_RATE_FF_ENAB to 1. 

This should really make the whole thing feel much softer.  This equates to 720 deg/s/s acceleration rate in roll and pitch, and 540 for yaw.  It should feel much softer, but still controllable.  You can try changing them around a bit.  Both those numbers are probably the upper limits of what you might use for a multirotor.  Lower bounds are something like 54000 for R/P and 36000 for Yaw, but that's not cast in stone.  A really large multirotor might use down to 36000 for R/P, but now this will start to get very soft and unresponsive, you wouldn't want to fly like that in tight spaces for sure.

Helicopters use numbers like 144000 for a small sporty machine flying acro, and I use about 72000 for my camera ship.

most excellent.....Thx

So rc feel gives a linear input with a delayed response from the copter?

That is correct.  It's just an LPF.

The ATC_ACCEL parameters use a physical limit to the rate of change of the target angle.

Thanks Rob i am keen to give this a try

David Ardis

Thank's too Rob, so, when we do autotune and the cuad is too responsive it's better to change ATC params as you indicate and use Stab roll and pitch as autotune give Us?, I'm going to re-do autotune and try like this if my understand is correct.

I have a Tarot 650 cuad 1,4 kg (without 3 s batteries) 460kv motors, What values do you recommend for first try? Thank's.

Reply to Discussion


© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service