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.
I noticed when you make changes to "Standard Params", the first time the screen is used COPTER_LEDS is undefined (blank box, no "disabled"). Setting this to disabled before writing prevents the error from coming up. So still a bug, but yeah it's minor.
Regarding that pin conflict between COPTER_LEDS and radio RSSI... is there a fix planned for this? For now I'm using airmamaf's custom code for RSSI+LEDs, but those LED functions are not as fancy as the built in. I think with 2.9 APM is going to see a lot more interest from FPVers... smooth RSSI configuration should be a high priority. ;)
Yeah, all of my heli flying since... maybe September has been with GPS_Use = 1. I've never had a problem. The only issues is that when disarmed, the HUD moves around (and the heli servos), but soon as you arm, the HUD will stop moving.
Nice, thanks Rob!
Ive got theMB1260 Sonar do I set it at EZlO,many thank's,Marty.
Loaded 2.9 / I went through the calibration process with my quad . (880kv motors / APM2 / Ublox GPS / Sonar / ) Rate roll P set to 0.100
I had the APM set to disable the arming until there is GPS lock. I armed and flew. It was foggy and snow on the ground.
Got it up to around 7m alt, and flicked it into alt hold on its way up. It immediately dropped like a brick. I managed to put it into stab mode, raise the throttle to save it from a very hard landing. Is this something I have done ?
Marco, have you tried landing in auto with the big boy yet? My quad landed on a 15 degree icy slope today and still stayed on it's feet!
That happened shortly after i couldn't find ALT-HOLD_RTL :)
I much prefer the new name though.
I tested it as far as to watch the HUD jump around, not even sure if it was enabled for the 2.9 vid!
I will check and post the param file since i neglected to do so
It was an easy tune though for the bigger motors on a quad. Reduce rate_P to 0.13 and stab_P to 3.8. Everything else stock.
Maybe I can make a heli land on the ceiling? :D
Merci à l'équipe pour le travail:
Trop de mauvais temps,pluie verglas, neige pour tester 2.9 sur mon APM 1.4,Mais je suis vraiment dans l'attente..!
question: je compte actualiser mon équipement dois-je investir dans APM 2.5 ou Attendre encore un peu pour PX4 ????
Merci et encore Bravo
Just uploaded this to my tricopter...
Can't wait to give this a try. Whoop Whoop!
Thank you to everyone who was involve with this release, to Marco for making all of the test videos, and most importantly to Randy for replying to all of my newbie questions...
Hi everybody and thank you for your hard work on the new version 2.9 !!
I'm new on APM so perharps it's a stupid question, I got a APM 2.5 and a 3DR power module ,on the setting BATT_CURR_PIN I've got the choice betwen disabled/A1/A2 or A13 and no other choice possible The A13 pin is already on the BAT_Volt_PIN .On a forum I saw that I should put A12 for BATT_CURR_PIN but its not possible on mission planner .I tried also the values A1/A2/A13 on BATT_CURR_PIN but it gives a bas value (20A with engines stopped !)
I had the same thing on 2.81 and 2.9
Is it a issue or a mistake from me ...?
I can't find the parameter that sets the loiter radius.