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.
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.)
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.
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.
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.
Marco, thanks for that. I was flying b6 in no/very low winds which could explain why I was finding it so difficult to make rhyme or reason for some of the behaviours I was seeing, and why I was finding it difficult to replicate performance when backtracking steps. I will use yours and Igor's guides and the advice above when I get to fly again. Cheers, Bill
nicely fixed! and quick!
dont crash it again (but if you do, Thanks again from all of us!) Video as always are NEEDED!
Good job Marco and team!
I would like to see a super guide to HIL and SIM for reall dummy... like from how to connect all electronics and TX to computer and major software tuning and config.... you know a real source on how to do it right.
Winter is not ending so flying sim in HIL is the only way for me now... I want to start doing it but not sure where to start... seem simple when looking at how you all do it!
Well, the future will be assured the crash, I do not fly very quiet! :-)
You're right, miss a good guide for the HIL section, when we will implement the tests with the new version of AeroSim will be completed in order to provide detailed instructions even inexperienced users.
However, Jean-Louis gave instructions about this, on its Google space.
Who is supplied only to APM1 you must still provide a USB/TTL converter, they are found on Ebay a few $.
Those who also has the IMU OilPAN just use the usual USB cable that is also used for programming / parameterization.
Obviously a receiver connected to APM and simulation software.
Were you flying 3-blade props before as well?
Timing is good indeed,snow wil prevent disaster crash.... ;-)
Yeah, but not with my (bugs) epic crash! :-)
they you/they squash that bug? so at least we can say it give you some closure on the crash and lost! :)
GOOD NEWS!!! You can (at your own risk) fly 2.2b6 pretty much out of the box on most standardish mulitcopter frames.
BETTER NEWS!!! You can also follow Igors new method (above) to achieve 'that' feel of PIDT1 but now in 2.2b6 :)
My quad now has rate_d 0.012, rate_p 0.140, rate_i 0.05, stab_d 0, stab_p up to 9 again and it feels like it would take a sledge hammer to take it out of the sky, and no oscillations (almost none - little bit of tuning left to do) :D
Only trouble is i have the 5 seconds of initial 'wobbles' back - a minor niggle considering.
This is the best news I've had in my multicopter 'career'
Simply brilliant, Thanks all. Jason - Enjoy your break, have a beer on me :D
Nice Dave... anyway have you tried Acro mode?
In my 3m by 3m test room? I'm not warthox you know ;)
Might try in the garden later.
For clarification Marco, what rate_***P are you running, not 3.000 i presume? Mines 0.14 currently.
Can you remind me - was there a solution to the 'wobble' ?
Indoor video uploading