Autotune crash, lots of testing and can't seem to find why. It is repeatable

On that size of motor you should be fine. I know there were issues with someone having too small a cap on those ESCs so worth checking. Note that the higher the ramp rate the more need for a good cap as well.

Just to update…

Last night I downgraded the firmware on my esc’s to 2.18. Just ran fully through autotune and no issues at all. I have flown several times and no issues yet.

AM32 after update should be set to defaults, and then re-apply settings You are interested in. I would recommend PWM type by RPM and auto timing advance.

Seems there are some changes in way settings are stored and they are getting messed up after update 2.18 → 2.19. At least that is my experience.

Update…

I flew several packs today and have had zero issues since downgrading to 2.18 firmware.

I may in the future flash 2.19 again and see if it continues to do what it did or not.

1 Like

Is there any guidance or rule of thumb on the slew rate based on KV/prop size yet for Arducopter? Have you got any suggestion on how to test this non-destructively?

I literally have two datapoints:

  1. I have identical quads with 2150kv 6S motors, one on AM32, one on BLHeli 32.9. 12% slew rate gives me approximately the same tune on the AM32 one as the BLHeli one.
  2. Pete said use 8-10% on 1000kv motors with 10” props.

That’s it.

Higher slew rate will generate more torque which on larger motors with bigger props stands a higher chance of desync. But it obviously depends on a number of factors.

2 Likes