I just pushed Arducopter 2.2 to the Mission planner. This version went through extensive testing by a brave group of flyers and with both HIL and SIL testing.

See this link for more:


If you run into any problems please let me know here. If you find a reproducible bug, please add it to the issues list.

tuning tips:

If you run into Loiter issues, try adjusting LOITER_P. It's 2.0 right now which may or may not be to aggressive for your copter. Nav is no longer used in Loiter control, which should make tuning easier.

If you run into a circling issue, try lowering LOITER_I to 0 and see if it goes away. If not, check your compass declination. A negative error will produce CCW rotations, a positive error CW.

If you have issues with alt hold, try lowering your THROTTLE_P, it may be too high for higher thrust copters.

If you have wobbles and can't seem to get rid of them, there is a new term called STAB_D, which is a derivative term used to tune out the wobbles. You can increase it until they stop, but just like driving a cadillac, you loose some performance and handling. In the CLI "tune 16" in setup will let you control this in flight, and "tune" in test menu will let you see the value printed out interactively before flight. See the wiki for more detail.

Many testers gave me a thumbs up on the code, so if you have an issues please post the flash log from the copter. The tLog isn't that much help to me for debugging as it doesn't capture the needed values at high enough rates.

(Remember, if you'd rather pull the code from the repository and load it with Arduino, you must use the "relaxpatch" version of Arduino in our downloads section.)


Update 2.2b2

I believe I found the simple mode error. It was a bug that was working OK until Tridge fixed it so it was declared properly. Then the bug became active. I made the Simple mode function internal variables static and this should fix it hopefully.

I updated alt hold to not use dampener for now until we get more testing. Some folks saw a latency induced oscillation which was pumped up by the D term.

I added the automatic throttle cruise or hold value as a compile time option for testers. This basically looks at your throttle and climb rate while in stabilize or acro and determines your optimal hover value. This means you can enter any autopilot mode and not have to worry about your throttle position. It should make alt hold more reliable if it works. This is off by default until we get good field tests back.

Update pushed to GIT.

Update 2.2b3

Just some refinements. I added JLN's throttle curve mod for landing. Hopefully that's correctly implemented. 

Made the landing delay from RTL user settable

removed the ADC gyro filter, I was doing a lot of testing and determined it wasn't worth it.

Enabled the auto-throttle control by default. Please test in the sim

Altitude no longer resets when flying in Loiter mode

Pitch and roll dampening is smoother now. try values up to .08 for very dampened flight.

Mavlink can now trigger auto-land

I'll push a hex when I hear some good news from HIL testers.

Update 2.2b4

Flew today and saw the WP speed governor wasn't quite working right. It was going down to 0 rather than the minimum.
Made internal switch to CM for distance calcs. This should not make any change to gains or MP.
Modified a few default gains for jDrones frame based on AP test flights of this code in some heavy wind on my roof.
Fixed an issue with the landing code not kicking in right away.
Decreased the slowdown near WPs
Added a limit to the amount the pitch compensation can effect the throttle if the throttle input is really high or maximum


Update 2.2b6

This is a rollup of all the code that's been flying around for the last week as well as a few bug fixes. I'll be posting it saturday night after reviewing all of my logs.
A dampening term called STAB_D has been refined. A D term for all of the Rate based control loops has been added based on Igor's work. Landing for Baro and Sonar has been refined based on JLN's work. A slightly new approach to Loiter and Navigation is being used to try and linearize the pitch and roll for rate control. It tends to use lower gains, yet has a more assertive response in the air.
I have one small loiter control issue to sort out tonight based on my logs, then I'll post to GIT.
Here is the auto-landing code in action. 

OK, 2.2b6 is on GIT. The Mission planner is going to be out of sync until the release code. until then you can use the APM_Config.h or the parameters list in the Mission planner. 

STAB_D : This is the gyro accretion dampener. This can remove small wobbles during sharp changes in angle commands. Making this too high can have a negative effect in performance and add a memory effect that can cause temporary loss in control. The in flight tuning is ranged so you are just below that effect.

If you haven't noticed before the control loops are in two stages. The first is a PI stage that converts some sort of position or angle error into a desired rate. These generally do not need to be tuned. They are more of a user preference on how fast you want the copter to perform a motion. 

The second stage is the actual PID loop that needs to be tuned for the copter. This converts the desired rate into a motor command of some sort. I added a D term based on Igor's recommendation to the PI's for each rate controller. These should show up soon in the mission planner for the release. I cannot give you a concrete answer for how to tune the D terms, because they each depend on their function such as alt hold or loiter, etc.

Still, the absolute most important term is always the Rate_P term for each loop. Start tuning here.

The default PIDs are in the what flies great for a stock jDrones/3DR Quad with the purple motors in X mode.







Views: 61031

Reply to This

Replies to This Discussion

Yes Graham, i tried now, is because I have attached the "camera.pde" current, which provides for changes elsewhere.
That's because I cleaned this version so as not to make too personalized, free to all.
Thanks for the warning, you can fix the problem simply by overwriting the camera.pde with this attached.



aha, RickP said in an earlier post "1.0 isn't supported yet, use 0022-relax: http://code.google.com/p/ardupilot-mega/downloads/detail?name=ardui..."

Are you using 0022, not 1. What are the compile errors?

Nope still getting the same errors (posted a few minutes ago Gareth)

Will download the 0022 version and try again

You must use Arduino 0.22 relax patch!!!!! :-)
I've no compilation error here, first replace the camera.pde file with the latest...
And remember, only APM1 2560 or APM2, not for 1280!
I remind you that this version is absolutely not official, so use it at your own risk!

Message from Jason:

Hmmm. That's tough. you can certainly lower your stick output in radio.pde

4500 is the normal range, but you could lower that to 2500.




That will certainly limit your pitch and roll control.

thanks downloading now, will use at my own risk and report back.

Do not use the dafult parameters after download and reset, follow my example or read the blog post of Igor about tuning the pid, is much important!
There's six must important value for PIDT1, this one:


For tuning the "RATE D" (is the first much important step) follow the instruction of Igor.
Start with these, let absolutely "STAB R/P/Y I" to zero, and you are not too high with the "RATE R/P/Y P", a value like "0.90" is a good starting point.
Do not use the "autotrim", just the "level" function inside ther planner.
Jason is honing his "STAB_D" to get the same and i hope better performance, if I were you I would expect the official version ... : P
Anyway... i look forward to your feedback, good luck!

Argh, Frustration! Getting this now on compile: ....APM_RC\APM_RC.cpp:27:3: error: #error Please check the Tools/Board menu to ensure you have selected Arduino Mega as your target.

APM 2560 is my board and target!

I agree, you can certainly make the model stable by reducing the bone all pids, but then do not fly more, and a little wind goes where he wants... but if we are content to watch it in orbital missions, move on to all axis without moving the yaw, try loiter and company... for this is is good.
Sorry but not enough for me.
We find a stable and responsive/reactive flight model (without wobbling), then do the rest (IMHO).
Proposed patch to fix things will surely, could possibly cause problems in automatic flight, need absolutely debug and improvement but in the pure flight my video speaks for itself.

Ive loaded it and works, its feels alot better in the air, not as 'automated' in stab mode, does what i want, but has alot of 'glitching' like it quickly adjusts for stab, not sure if those are just my settings ?

Thanks Russel! :-)

Reply to Discussion


© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service