ACRO bug (fixed in 2.9.1b): while doing flips in ACRO mode, if you switch to Stabilize while inverted your throttle will go to minimum. To regain throttle control you need to switch back to ACRO then back to Stabilize again (i.e. switch to stabilize twice). You never lose control of roll/pitch/yaw.
Loiter/AltHold/Auto/RTL bug: if you switch into these modes with throttle at zero motors will go to minimum until you raise the throttle.
Auto mode altitude bug (fixed in 2.9.1b): setting a waypoint altitude greater than 320m over home altitude may wrap around and instead be interpreted as a low altitude.
ArduCopter 2.9 is now in the mission planner and the downloads area!
The major improvement is we use inertial navigation to improve altitude hold. This increased reliance on the accelerometers means you must do some additional set-up before flying:
3. If upgrading from 2.8.1, modify the throttle and altitude PID values:
Here is the list of major changes (a more detailed list can be found in the release notes):
As per usual PIDs are optimised for the 3DR/jDrones quad with 850 motors and 10" props. If you're using more powerful motors/props and are seeing bad flight behaviour in stabilize, start by turning down Rate Roll P in 25% steps.
Special thanks to our testing team lead Marco and the dedicated bunch on the 2.8.1 release thread who put their copters at risk while testing the pre-release version. Some of their videos are here: 1 2 3 4 5 6 7 8
Please feel free to report issues you find in the discussion below and/or add them to the issues list.
Yes Randy, but "override the yaw" is not useful if a user abort a mission and takes control of the quad manually, would the nose pointed in a direction to him difficult to understand.
In my case, and you can see it in any of my videos, if do a mission abort i resume manual control of the quad immediately because I know where it is pointed the nose.
Try to increase to "0.3".
I gave a test with your parameters.
Many thanks once again!
Nice! I've reported the "alt-hold" problem to the dev list for the "cosmetic release" 2.9.1.
Have tried to keep the quad stable at high altitude for at least 10 seconds to store the throttle_trim? It's important to store the hovering point.
So does that mean loiter doesn't look at this value? Or are you saying loiter and circle mode use it? If not, what does loiter do now as far as holding position, always try to hold it as close to 0 meters variance?
We added a bunch of things that should have stopped this. Can you add some logs?
When you applied Marco's parameters did you also apply all the parameters including these?
These are board specific parameters so if you used these and then didn't repeat your accelerometer calibration then your alt hold wouldn't work well.
That's right. Loiter doesn't look at this parameter at all. It tries to stay as close as possible to the location it was at when it was first engaged.
@Randy - I used compare values & select only the "PID-tuning values" Still my calibration might be wrong - e.g., I made the calibration by holding the hexa upright with hand, hexa standing on the floor (=there might have been some movement compared to full independent standing)
@Leonardthall - good to hear. I will dig out the logs & upload later.
my 2.9 testing today.
alt hold great but a bit jumpy i dont know why. need tuning
"jumpy" when throtle up during loiter (look at 3:23 )
also "jumpy" when do auto land at 3:31 min.
I did what you recommended. I set the Thr_Rate_D to 0.001 and the outcome was the same. It was still bouncing (jerking) up and down.
I even attempted to adjust the Thr_Rate_D to negative values and it produced the same results (jerking up and down).
One setting that I haven't adjusted is the Throttle Accel P. Per Randy's instruction above in step 3: Tune Throttle Accel P and I terms but try to keep P about 1/2 the size of I. I might give this a try.
If this doesn't fix the issue, I'm just going to use 3s lipos. The copter flies so well with 3s. It is solid in Loiter and Altitude modes.
It is worth checking your logs by turning on RAW and NTUN. Make sure that you don't have too much noise in the RAW logs.
If this is just a tuning problem you may start by reducing THR_ACCEL_P and THR_ACCEL_I. Start by keeping them at the same ratio. You may also try reducing the THR_RATE_D term however I would attempt to reduce the first two parameters first.