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.
The compiler will do... Angel, my comment is in your thread.
^ is the bitwise xor operator. c doesn't have an exponentiation operator.
You'll get (7 * x_actual_speed) xor 2. I.e. the 2nd lsb of the product will be flipped. ^ is way down on the operator precedence list.
OK, sure. I still don't understand the intent of the line though. Needs comments.
Flew with v2.2b2. Simple mode seems to work better now due to the fix. Didn't get much chance to test anything else due to my flying location.
However, I have found that since v2.2b and v2.2b2, my APM is no longer recording logs. Even after I try to enable them in CLI, it will not record anything. Has anyone else experienced this? I did not have this problem with previous versions.
No problem with logs for me.
Erase your logs and try again. I'm not seeing any log problem here.
I did some testing and found the data flash card had come lose on my APM 2.0. Must have been all of those crashes :)
It was strange because I was able to download old logs that I had erased, but once I erased them, it wasn't able to log any more. Not sure when the card became loose.
I will just make sure to check the card reader every once in awhile because the card seems to have some slop which may cause the card to come loose with vibrations over time.
I flew my large octo today in Wisconsin. It was around 20 degrees Fahrenheit with 15mph winds. I had lowered my rate p values before this flight to see if I could calm the octo down a bit, but I found that I lacked adequate control of the copter. The octo seemed to be very "squirrely" in the winds which is something that I had not experienced before in stabilized mode. Also, I am seeing the same issue as the previous release where if I apply pitch, the copter evens out over time (not that long maybe 3-5 seconds) and then I have to slowly reset the stick to center to be able to apply pitch again.
I must have been drawing a lot more current this time around because I blew my sparkfun voltage/current monitor mid flight and the copter dropped out of the sky like a rock. Luckily I was only about 7 ft off the ground over snow and my landing gear is designed to absorb impact. After the crash I tried to fly again, but this time the copter was almost totally unresponsive to my very drastic stick inputs. I think that could have been either my low rate values or the crash did something to the IMU. Perhaps the cold weather was throwing things off... I'm not really sure.
I reset everything on the board for another flight ASAP. Logs attached.
Also, anyone else out there fly this revision with a larger copter? I had good luck with Stab P values around 2.6. Anyone else had luck with PIDs?
see my previous videos. My hexacopter would be considered a bit larger I presume. I was flying with the default pids and I found it needed more yaw control. In addition, the wind wreaked havoc on stabilize mode, spinning the copter around quite easily in a minimal wind.
I plan to go out and do some more testing tomorrow if the weather holds out. It is quite cold here.. -10 celcius. I'm not sure if that is having any bearing on the APM.
I replied to your video post... let me know how your next flight goes!