Tuning for larger props, issue revisited…

I am still trying to understand how to tune well for bigger props. I had a dismal failure with my first copter where I had 16 inch props on low kV motors (340 kV) and was trying to tune it, and the result was that it was either not stable enough, or had low amplitude high frequency stable oscillations which allowed a very safe flight, but made the platform almost unusable for camera. And it took me more than two weeks to figure out the best settings for this copter. Shawn helped a lot, and I also have learnt a lot in the process, so probably I could do it now much faster, but still, there seems not to exist a perfect tune.

Now when I am talking about big props, 16 inch is not very big compared to 24 or even 30 inch which are flying around, I am not sure if the criteria is the ratio of prop size to distance of motor from the CG, or the copter weight (disc loading), or both, and how they relate to each other (weight versus distance from CG). The first copter had 16 inch props 2.5 kg flying weight and a diagonal span of 75 cm. Switching to 15 inch improved significantly its behaviour, but unfortunately, the low kV motor mean that I would have to go to 7S or 8S to have enough thrust for high altitude safe flying, and I do not have ESCs nor batteries for this.

I built another copter, this time with 600 kV motors running on 5S and 13 x 5 props, 2.2 kg, and diagonal base of 65 cm, and it flew almost perfectly, with oscillations in the order of 0.2 degrees.
I tried to mount 15 x 5.5 EOLO props, did standard autotune with aggressiveness of 0.1, and that resulted in oscillations of the order of 0.4 … 0.6 degrees, about 2 … 3 times the amplitude of the copter when flying with 13 x 5 EOLO props.

The biggest advantage of 15 versus 13 inch prop is the efficiency – for hover, there is was a reduction of about 10 % of power with 15 inch props, and also much more efficient climb (maybe 15 % more efficient), but probably lower efficiency for horizontal flying, at least at sea level.

My options are:
A. Abandon completely the idea of bigger prop and maximum efficiency in favour of more usable, but less efficient smaller props.
B. Someone has ideas about the tuning of such copters, or even changing the design (bigger span) and could share his ideas about that.
C. Fighting out with LUA scripts, i.e. changing the PIDs on the fly based on the flight phase and potentially on oscillations present. This would involve a lot of fine tuning and testing, and the result would be highly dependable on the concrete copter, so it would be a lot of work for one of a kind, or rather one of a type copter. The concept probably is not too complicated, because in some flight phases (the criteria would be overall power, vertical descent, and attitude), the PIDs would have to be adjusted by LUA, but the exact values to be used both for criteria for changing the PIDs and the PIDs themselves would either involve a lot of experimental work, or theory which I do not master.

Any input?

Have considered trying INAV? I have the INAV on a 10 in, and the tune is not bad.

For INAV, they have preset for 5 in and 7in. For something larger, just use 7 in preset, and adjust filtering cutoff frequency. The rate setting (in deg/s) can go down quite a bit too.

INAV is really designed for Acro flying. You can try Betaflight too, but it comes only with GPS rescue, and position hold, waypoint navigation will probably come in another 2 more years.

I am not sure that I would want to change for INAV, although my very first experiments with VTOL were with INAV.

Also, 10 inch and 16 inch props… that is a “small” difference…

For me Betaflight does not exist…

I am flying in Acro mode about 90% of the time, although I use it for slow, smooth maneuvers.

Hi, There is Eztune for Inav. I don’t recommend using Eztune for large quads, but it is good to see the recommended parameters.

You can adjust the gyro cut-off frequency. Take off in angle mode around 5 m, and control the quad a few roll, pitch, yaw.

There is PID toolbox: https://pidtoolbox.com/

Some very good feature in INav is that you can switch profile in flight. Fly high and switch (preset) pids and test.

Well, one can do the same thing (changing and adjusting PID values and other parameters) in flight by using the LUA scripts, they are much more versatile and allow you to change any paramater either as a group, or bsed on some condition, etc.

Or by Transmitter based in-flight tuning. That has been in Arducopter for years.

Did you use the methodic configurator to setup the quad?

Yes… but it did not solve any problems, and autotune was giving me PID values about 50 % lower than I have now.

However, that is not to say that autotune was wrong, it simply reduces PIDs until there are no oscillations/backlash observable. However, these PIDs make the copter too unstable.

When I increase the PIDs, roughly by 60…80 % more than Autotune values with aggressivenes of 0.1, that does two things: oscillations appear, but they are manageable and not progressive, and the overall flight stability increases. So after that I was playing with different methods to make the tune as responsive as possible without making the oscillations progress.

Some possible strategies were:

  • Making I much higher than P (like P 0.1, I 0.25)
  • Changing Slew Rate,
  • Making vertical gains much softer (especially in the descent the copter has the tendency to develop stronger oscillations)
  • Making horizontal PSC values lower, so that Loiter Mode would not induce progressive oscillations.
  • Modifying the angle rate parameters and accelereations downwards, but it is not a straightforward issue, either.

And finally one could try and write some LUA script which would catch the oscillations, and cut them by temporarily reducing PIDs, and also changing them depending on the flight phase.

But overall, my conclusion is that the copter is simply untunable.

Comparing the step response of this copter and the next one, with 13 inch props, I have about 0.12 seconds for the pitch/roll response for the first copter, and 0.05 seconds for the second…

The Dev’s here would want to see the param file created by the MC software, that would be helpful for all.
Also, unless I missed it I didn’t see any logs attached for review.

Hard for anyone to help when we are getting the same perspective that has been looking at this issue from the beg.

If you want help then I would suggest attaching param (from MC) and log files for people to review

Well, there were several dozen logs at the beginning of January…in the thread: Tuning PID for multiple flight phases, TOW and altitudes on a 16 inch copter - #11 by amilcarlucas

Many logs, but no .zip file with the contents of the vehicle configuration directory created by AMC.

It has been two month ago when I seriously tried to setup that copter. I found one log file from that period which has close to best settings for the flight, it also includes the parameters at that moment (frankly, now I have dozens intermediate param files, logs, etc. from three different copters and 13,15, and 16 inch prop setups, so I am not very sure which is which.)
The one which follows is that copter with 16 x 5.5 RCtimer props, and a succesful real world flight.

https://www.ecoterrenos.cl/Flight3900new.bin

However, afterwards, I put up a HD camera and realized that there would be no way to get an acceptable feed due to oscillations.

One use I have in mind for this copter is to use it as a signal relay copter for flying the others copters beyond the ridges.
The other option is to dump the 340 kV motors and replace them with something like 600…700 kV Sunnysky and fly on 13 inch