Regarding power; I think the copter is in a good range. I need only 40% throttle to hoover:
Regarding sync - maybe its the wrong description. I dont know, if it is a sync problem between esc and motor.
I can assume, that the P-Values have been just to sharp for autotune with AutoTune aggressiveness on max (0.1) and Rate Roll /Pitch Values on 1.8.
Maybe I should try again with AutoTune Aggr on 0.5 and _P on 1.0?
Your lucky it didn’t flip itself into the ground as happened when I forgot to change the Filter and Aggr settings on a large Octo.
Just set the Aggr to min and take your filters down to 10 or even 8.
Start from there and work your way up.
It’s a known problem large props (heavy) and low kv motors, you can try lower diameter or up voltage and see what happens, tuning can be a maze wihtout exit in this case.
Edit: I forgot esc… thinking are compatible with motors, try lower timing and up start power, do some tests before tuning.
Can you provide the log of Autotune where you thought you saw the sync loss. I will have a look.
What ESC are you using?
Have you done any bench testing to check for sync loss?
Just a quick chime in. I just finished tuning a 15+ kg hexa with 30’ props and 12s100kv motors. Filters at 6 and autotune aggressivity 0.05.
Is was a little frightening at the first, but autotune went through nicely and got a very well locked in beast. So I can confirm that it is possible to autotune heavy lifters as well.
Thanks to Leonard for providing all the info above.
So just to reiterate to eveybody.
You should make sure your initial tune is good enough to recover from the disturbance that Autotune creates.
So start with a manual tune, check the stability, then do autotune.
Thank you Leonard and Andreas
I definitely will try that! As soon as the weather is better and the winds are gone.
As my copter has not 15 but 11kg, I’ll try with a ATC_RAT_RLL_FILT and ATC_RAT_PIT_FILT to 8Hz. Tune manually again first, then AutoTune with agressiveness on 0.05
Thanks for your advises. I’ll let you know how it works.
Here is one lesson that I learned from testing non-standard drive setups and probably crashing more than a dozen of prototypes: never ever think about a first flight with a certain drive setup if you did not ensure on the test bench that there is no possible input signal that can stall the drive.
I use a hacked ArduCopter firmware for that purpose that is able to replay bin logs, plus a python script to generate arbitrary signal forms. Most promising patterns are step functions between rather low and rather high output levels (not necessarily 0->100%, but also things like 30% -> 80%). Some drives even desync when decelerating. Be careful when doing these tests - I have broken a few props, especially larger ones.
If certain drive setup survives this kind of torture, I replay logs containing severe oscillations, with different frequencies (recorded with different airframes). For some reason, this seems to trigger sync losses even if the step functions don’t - may be this is the reason why AutoTune is so good at triggering a sync loss.
And here are the bad news: even if a drive is impossible to stall on the bench, there is still a slight chance to see a stall in the air due aerodynamic loads. But this will definitely need more than just AutoTune
Sorry, what are you suggesting here?
For the SkyViper stuff tridge added a motor-test mode where it would
replay motor outputs based on a compile-time #include of prepared data.
Sounds like Holger wrote much the same thing, which isn’t a great use of
people’s time. Pulling tridge’s stuff out of the toy mode loops should be
possible - or perhaps some mish-mash of Holger’s and the current in-tree
Until today I was not able to get an Autotune done by my 29inch T-Motors Setup. Your advises dint help. I tried ATC_RAT_RLL_FILT and ATC_RAT_PIT_FILT down to to 5Hz and AutoTune with agressiveness on 0.05. Maybe I should reduce ANGLE_RATE_MAX (controls the maximum requested rotation rate in the roll and pitch aixs (default is 18000 (180deg/sec)) to 12000 or less?
I tuned the copter manually to a not to bad level, but would be still be very interested to get it running, since I have to do a lot more tuning work on similar frames in the near future. And manual tuning is realy time consuming. Anyone?
Do you have a log I can look at?
I was running 5hz on my 17kg x8, but Leonard said to go back to 20. Any thoughts Leonard? Just heading back out to re tune everything as I change my setup from U8170kv on 8s to U8II’s, Alpha FOC esc’s and 12s along with 28" folding Tmotor props.
Sorry but I don’t recall the conversation where I told you to do that but I suspect it was because I was seeing strange issues with Autotune responses that may be caused by excessive delay caused by low filter settings.
My general approach is to set the filter as low as possible until it starts to impact the results of autotune. I really need to add some system identification code to make it easier to define these filter frequencies with confidence.
So, I did a lot of fiel test the last weeks.
Regarding auto-tune - there was no way to Auto-tune the 29inch-Prop-T-Motor 170kv setup on 6s. Whatever we tried.
We finally tuned it manually. First the 29inch setup, that was tunable to some point. But in the end we where not happy with the setup.
Now we changed to 26 inch props on a T-Motor 190kv Setup on 6s, and this one sounds very promising. Even there the auto-tune was not possible. But manually tuned, we got quite good results so far.
Hi, this may be help. I’m tuning a 9.5Kg quadcopter, U8-135 motors. I used to use 29inch propellers, but my lipo configuration is 12S, so the motors was warmed. I changed to 22inch propellers and do Autotune. The quad flight well in stabilize and althold mode, in loiter and auto I’m having some throubles (Big quad in Loiter, high wind, Pitch axis Oscillation in auto mode, big copter). I’ll do test with 26 and 29 inch propellers in next weeks, attach the parameter from autotune
U8 170kv don’t work at 6S the minimum it’s 8S
Yes, we are using 137KV motors and they need 12S to perform with only 24" props.
Same here with a similar build, except a quad config. Auto-tune did the trick!