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.
Jason has pushed a fix for Simple Mode in the repository. He'll push a hex when he's finished testing.
Have you seen this error when trying to use the relaxpatch version of arduino?
"Could not find the main class: processing.app.Base. Program will exit"
I just downloaded and unzipped the folder, clicking on the arduino icon. This error pops up on startup. Am I missing a step or file?
Tested latest GIT 2.2ß2 with AeroSim:
- Simple: OK
- WP recorded with CH7 and the related mission "Auto": OK (note: if i record the latest WP with the quad at the ground then the landing in this case is perfect, the only difference have see is the increased speed of descent, maybe with "Land" mode we're coming down too slowly, please investigate...)
- Loiter: no difference here from previous version, need test in real flight
- Auto Throttle Hold: OK
- Autoland: doesn't work, the only one ok with this sim is the version inside 2.1.1R7
Just got a chance to test 2.2 in the field and had an issue. For some reason I could not arm the copter. I rebooted about 15 times. All the lights looked good and I was able to connect to the APM via my xbee. When I went to the configuration window to check my radio inputs they were all at zero (no radio input detected essentially). These are the steps I took when I setup the APM before leaving for the park.
1. Uploaded new code to board (2.2 with GPS fix)
2. Cleared EEPROM
3. Ran initial setup (Radio limits, modes, leveling), all of which went as usual
4. Set my PIDs
5. Disconnected from MP
6. Went to park and ran into the issue
How can I clear via button the eeprom in the newest mp version??
I used the CLI. Make sure your slider switch is in the CLI position. Then click on the terminal tab in the MP. Type setup, hit enter, type erase, hit enter. That should clear the EEPROM.
P.S. the slider is no longer required to enter CLI. Just go to terminal in Planner and hit enter 3 times.
Ok I know this, but why is the button eeprom remove deletet in the setup progress??
Is it automaticaly deletet when uploading via arduino or mp???
Ah- pretty sure that's now automatically done when the EEPROM map changes with new firmware. You can do it manually, but I think it was taken out for simplicity's sake.
you can go to setup menu in CLI and type reset. This will clear everything and start from 0.
Yes, EEPROM clears and log erases are now down automatically, only when needed by changes in the EEPROM map of file system.