Quadcopter aggressive gains after autotune

I have a quadcopter equipped with a Pixhawk Cube Orange running firmware version 4.5.3.
I have followed all the steps from the initial setup through to AutoTune.
Attached are the tuning parameters obtained after Quick Tune and AutoTune.

The accelerations seem too aggressive for the size of quad I am using.
I would like to ask the experts: Is this tuning considered safe?
Should I reduce the acceleration values? If so, by what percentage? Additionally, will reducing these values affect the gains?

I kindly request guidance from the experts.
@amilcarlucas @xfacta @Leonardthall

If the motors are not warm, and it feels steady, congratulations you have a tuned vehicle.

Now, like described in the documentation, what you need to do is input shaping so that it feels slower to you, but it still is fast to reject wind disturbances.

1 Like

Without a log file to review who knows.

2 Likes

This is correct. It looks like you have a good tune. The next step is to make it feel the way you want it to feel.

ArduCopter lets you separate the way the aircraft is tuned from the way the aircraft feels to fly. This lets you have a very aggressive tune while at the same time having a docile and friendly aircraft to fly.

1 Like

Thanks for the positive response for this build. I have tested this vehicle-1 after the autotune and response is quite accurate.

But I have another build (vehicle-2) with the same configuration

Please see the image attached for the parameters after Quik tune and Autotune

After the auto tune process, I take off the drone around 10 meters but after few normal roll inputs it starts visible vibration at high frequency and luckily I have landed the drone safely.

Attached is the log of the flight after the vehicle-2 auto tune flight.

Please review this and help me find the issue

@amilcarlucas @Leonardthall

Does not look like a PID issue to me. It looks like a noise that should be addressed with hardware improvements and a notch filter.

Hello,

The log I have shared the HNTCH is already enabled. I did this flight with ATC_RATE_FF_ENAB=0 to test the tune.

I am using Pre filter logging and I have used the web tool for Filter Review (ArduPilot Filter Review)

The notch seems to be working maybe not perfect, do you see in the above image any kind of problem which i might have missed?