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:
1. Perform the new accelerometer calibration in the mission planner (video). The auto-trim metho has also changed (video).
2. Add vibration dampening foam between your frame and the APM. Some suggested materials: DuBro, gel, hk foam.
3. If upgrading from 2.8.1, modify the throttle and altitude PID values:
- Increase your Throttle Rate P, reduce I to zero, increase D
- Increase Altitude Hold P, reduce I to zero
- Tune Throttle Accel P and I terms but try to keep P about 1/2 the size of I
Here is the list of major changes (a more detailed list can be found in the release notes):
- Alt hold using inertial navigation (Leonard, Randy, Jonathan)
- AUTO_VELZ_MIN, AUTO_VELZ_MAX parameters control the max climb/descent rate for the autopilot (cm/s)
- PILOT_VELZ_MAX controls max climb/descent rate for the pilot (in cm/s)
- Landing improvements (Leonard/Randy). Copter will descend to 10m or until an object is sensed with the sonar. Then slows to 50cm/s descent (speed can be adjusted with LAND_SPEED parameter). (video).
- Surface tracking with sonar (Randy/Leonard). Copter will attempt to maintain current distance from objects in front of sonar regardless of altitude. Only used in alt-hold and loiter, not used for missions. Sonar can be enabled/disabled with CH7 switch. (video)
- Failsafe improvements (Randy/Craig/John Arne Birkeland) including bug fixes, additional check for PPM encoder failure and implementation of battery failsafe. Set-up instructions are here.
- Mediatek gps driver accuracy improvements and use of SBAS [Craig]. Instructions on upgrading your mediatek to firmware 1.9 are here.
- Traditional Heli improvements (Rob) including (a) bringing heli code back into the fold, (b) enabled rate controller (previously only used angle controllers). (c) fix to rotor speed controllers - now operates by switching off channel 8. (d) allow wider collective pitch range in acro and alt hold modes vs stabilize mode (e) bug fix to allow collective pitch to use the entire range of servos
- Acro trainer (Leonard). Copter will return to be generally upright if you release the sticks in acro mode.
- ACRO_TRAINER : set to 1 to enable the auto-bring-upright feature
- ACRO_BAL_ROLL, ACRO_BAL_PITCH : controls rate at which roll returns to level
- Camera control improvements (Randy/Sandro Benigno): (a) AP_Relay enabled for APM2 (b) Trigger camera with CH7 or DO_DIGICAM_CONTROL command (c) Allow pilot override of yaw during missions and fixed CONDITIONAL_YAW command.
- PPM sum support for transmitters with as few as 5 channels (Randy/Tridge/John Arne Birkeland).
- Performance and memory useage improvements (Tridge).
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.
Replies
List of strange behavior in 2.9:
- (Auto) Restart after third point? Mission Why?
- When Switching to RTL mode, the hexa speeds off to an unknown (the same happened to Marvins, Willie Botha, Richard Boyhan, James W Powell, Jeff Cook, Vijay Singh, Dave Wilkeson ...). I have the hexa thanks to a miracle.
- When trying trigger the camera throught RC5, 2 motors started to spin (slow)
- When trying trigger the camera throught RC8, does not work, too.
- Camera trigger worked through RC10
- Modes in MP and APM do not match. For example RTL in APM shows acrobatics in MP.
Many Thanks for all your work. Really apreciated.
Ps. It´s a bit scaring to fly with 2.9. Is it possible to downgrade APM with the last MP?
Thank you.
Ps2. Sorry for my english.
Ps3. I attach telemetry.
2013-01-29 13-54-56.tlog
CubillosMP.txt
ArduCopter 2.9.1-rc1 (release candidate #1) is available for beta testers in the downloads area. We think this addresses the major issues raised since the 2.9 release two weeks ago.
Improvements over 2.9:
1) THR_MID parameter added to allow users to adjust the manual throttle so that vehicle hovers at about mid stick
2) bug fix for autotrim - roll axis was backwards
3) bug fix to set sonar_alt_health to zero when sonar is disabled
4) capture level roll and pitch trims as part of accel calibration
5) bug fix to ppm encoder false positives
It would be great if a few beta testers could give this a try and provide feedback. What's above should be the complete list of changes from 2.9.
Thanks for the reports and feedback so far!
Instead of software use soft hardware. :/
O ring arm mounts.
As I see, major improvement is "use inertial navigation to improve altitude hold".
I do not have the sonar on my quad and usually I am flying or hovering at +30m where sonar is not usable.
Do I need to upgrade from Arduccopter 2.8.1 to 2.9 if I am not using the sonar?
For me the Alt Hold and landing on 2.8.1 was acceptable, since I am doing manual landing (or Auto landing, but the motors myself when touch the ground).
If I intend to remain with ArduCopter 2.8.1, which Mission Planner should I use? I did upgrade MP to latest 1.2.32 and it looks the accelerometers are not more calibrating, HUD remain tilted and is not put is back horizontally.
I did notice on MP1.2.32, calibration page, is it mentioned "2.9+" under the calibration button. Do this means MP1.2.32 is only for 2.9+, correct?
So, which version of MP is the good one for ArduCopter 2.8.1?
Sorry for confusing questions, but I am also confused since the MP looks is not back compatible.
For people who like to do some copter tuning without having to use a computer to select what parameter to tune with CH6 :
MinimOSD with selectable parameter
Just a suggestion.
As the accelerometers are becoming more important and vibration more of an issue, might it be possible to have an instant reading that will show up in the MP tuning display?
Perhaps a 5 second moving average if it wont take up too much processing – and only turned on when needed.
It will help diagnose and experiment with vibration, perhaps even be useful for balancing.
Am I doing something wrong, it takes forever to download the logs and didn’t I read somewhere that CLI now worked over 3dR. Mine doesn’t.
Oh Oh.
I might have found the reason for these bad RTL's.
I'm sitting in my office and playing around making a mission, and I noticed the map was following my gps. It's two streets over, but thats normal. I'm surprised the when ever the gps gets a signal indoors.
Anyways, I looked at the Flight Data screen and it said "No GPS Fix".
BUT I looked at my quad and it had a SOLID BLUE LIGHT.
I just captured it on video, I'll upload.
Guys, I am setting up a hexa and I am still learning how to read graphs.
Vibes are ok?
Throttle trim is showing 551 value. It is underpowered? I fell it mushy and p rate it is already at 0,21 and its asking for more. I have to chase the hexa too much in my opinion....
Thanks guys.
My new quad in fast flight at over 60° angle...
Bests, Marco
From what I've seen on this and some of the other threads lately is that 2.9 represents a considerable change from past versions and that many things have been implemented in new and somewhat different ways meaning, of course, new problems too.
It also seems that with upcoming inertial navigation on GPS and the switch over to a HAL system there are going to be considerably more changes coming in version 2.9.2.
I am truly looking forward to these changes.
I do not expect them to be trouble free.
We are your secondary QC team.
Some of us just need to slightly better understand that this IS the bleeding edge, if you want to play you will bleed a bit.
-
16
-
17
-
18
-
19
-
20
of 26 Next