Developer

ArduCopter 2.9 / 2.9.1 released

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).

3690987999?profile=original

2. Add vibration dampening foam between your frame and the APM.  Some suggested materials: DuBro, gel, hk foam.

3690988058?profile=original

 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

3690988113?profile=original

 

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.

 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Randy,Did the team discussed this sensor?

    http://www.invensense.com/mems/gyro/mpu9150.html

  • Moderator

    Can we expect alt and position hold somewhere close to this with v2.9.2? I am hoping...

    https://www.youtube.com/watch?v=u19pbJBB_yU

  • Hi 

    Something new to me ,anyone to tell me what it is about ? .

    After loading 2.9.1 to my APM2.5 I got the following message :

    "upload succeeded but verify failed :exp 70 got 48 at 110136"

  • I'm having trouble with the battery monitor, it shows -0.1A for current (yes, negative). This is with the 3dr power module.

    Is there something wrong with my PM or anyone else having similar issues ?

  • Developer
         I've put a patched version of 2.9.1 (called 2.9.1b) into the downloads area which hopefully resolves the more serious issues we've found with 2.9.1:
    1) reduce INS_MPU6K_FILTER to 20hz
    2) reduce InertialNav Z-axis time constant to 5 (was 7)
    3) increased max InertialNav accel correction to 3 m/s (was 1m/s)

    4) bug fix for alt_hold being passed as int16_t to get_throttle_althold_with_slew
    5) bug fix for throttle after acro flip (was being kept at min throttle if pilot switched out of ACRO mode while inverted)
    6) reduce yaw_rate P default to 0.20 (was 0.25)
         I was wondering if some people could give it a try before we push it to the mission planner?  The biggest questions are around #2 and #3.
         #2 - reducing the time constant shifts the balance of power towards the barometer (i.e. weakens the accelerometer).  This makes it safer for people more vibration but barometer misbehaviour appears.  In particular try a fast forward flight and then flatten out.  See this video around 1:55 where I'm testing a TC of 5 and you can see the drop after flattening out.
               Of course, people can always increase their TC back to 6 or 7 if their copters are flying well.
         #3 - this is probably the most important fix to reduce the risk of vertical fly-aways in Alt-Hold/Loiter/Auto.  This problem could appear if people have a lot of accel noise and it had a bias of over 1m/s (i.e when the motors were running there was aliasing which caused the acceleration to appear to be constantly over 1m/s up or down).  That limit is now 3m/s.  The downside is that if you have a hard landing an alt correction may build up and take a while (30 seconds?) to recover...so you could have a bad altitude for longer after a hard landing.

         Anyway, if a couple of people could give it a fly and report back then I'll push it into the MissionPlanner.  thanks!

  • Any news on a firmware update?
    Will it be V2.10 or V3.0 or what?

    .

  • Hi Guys

    I am not having any luck setting up a mates APM2 .

    I cannot get the green bars to show during calibration and no HUD movement.

    I have tried to erase and reset the logs, load arduplane FW and still nothing.

    Is there a definiative method to fix this?

    Thanks

  • what settings should i be using for loiter?

    it holds perfectly in light or no wind, but as soon as there 5-15kph wind it starts to toilet bowl and struggles to maintain altitude.

    also, this is my first APM board, i've been attempting to tune Alt hold - initially i was using the wiki page, which i now realize was completely wrong and I should have been just editing the thr accell (might want to update this as i wasted several days - this also led me to question the loiter tuning page)

    after "tuning" how accurate should this be? i have thr accell P value down to 1.1 (2.2 for I) and it seems OK, but still fluctuates by as much as 1-2 meters in light wind. How much should i be seeing the altitude fluctuate? like i said, im a noob so i dont know how much tuning will correct this! i guess im concerned if i lock alt hold at about 5 meters and fly around it will hit the ground.

    would love some help! the board flies fantastic in stabalise.

  • Had a few succesful flights in stable on this quad with 2.9.1, I cleaned the logs last night and everything seemed fine when today it decided to perform the flight of death, just a few feet from me :'( Now APM won't connect to MP and CLI>logs just crashes. I'm getting the 'No dataflash' message in CLI. Tried re-flashing but no luck, so I'm thinking my APM is toasted (?).
    3692663534?profile=original

  • Developer

    "ArduCoper V2.9.1" code on "VR Brain" FC board by "Virtual Robotix Italia" (MTK GPS):

    Special thanks to:

    - Roberto Navoni and Emile Castelnuovo (by "Virtual Robotix Italia")
    - 3DRobotics
    - ArduCopter Developer Team
    - DIY Drones community
    - Lorenzo Gualiumi (the filmer)

    Soon I'll start also same tests on PX4...


    Marco

This reply was deleted.

Activity

Jose Araujo liked Jose Araujo's profile
Aug 29
spencer harvey liked spencer harvey's profile
Jul 9
More…