Developer

ArduCopter 3.2 ready for wider use

After months of testing, ArduCopter 3.2 (aka APM:Copter) is ready for widespread use and we invite all users to give it a try.  In order to manage the support load at first it will be available only through the Mission Planner and APM Planner2's Beta Firmwares link.  This link is visible from the regular "Install Firmware" page if you check the "Advanced View" on the Config/Tuning >> Planner page.  On APM Planner2 the "Advanced View" it is under the File menu.

In about two weeks we plan to replace AC3.1.5 with AC3.2 as the default version dispensed by the ground stations.

The full list of changes can be found in the ReleaseNotes but here are the highlights:
Flight Mode Enhancements:

  • PosHold flight mode: similar to Loiter but with direct response to pilot input during repositioning
  • ACRO mode handling improvement EXPO (for faster rotations)
  • Drift mode uses "throttle assist" (similar to AltHold)
  • Smoother transitions between flight modes (i..e when entering Loiter or RTL from high speeds)

Mission Enhancements/Fixes:

New Sensors/Devices:

Safety Features:

  • EKF/DCM check will switch to LAND mode if heading error > 60deg for 1 second
  • Baro glitch detection
  • Pre-arm check for Gyro calibration success
  • Pre-arm check that internal & external sensors (gyros, accels and compass) are consistent (Pixhawk only)
  • Parachute support (Pixhawk only)
  • Feedback to Pilot when taking off in AltHold, Loiter, PosHold (i.e. motors spin up a little as throttle is raised)
  • EKF (new attitude and position estimate system only used for reference in this release)

Bug Fixes:

  • Pixhawk GPS driver buffer overflow that could lead to missed GPS messages
  • Pixhawk I2C bug that could lead freeze up if I2C bus is noisy


Known issues/Warnings:

  • Pixhawk users will need to recalibrate their compasses
  • PosHold won't show up as option on FlightMode screen if you have an old version of mission planner.  Please select Help > Check for Updates
  • Landing detector is more strict meaning it may take longer to disarm after RTL, AUTO
  • Set THR_MID parameter especially if you have a very powerful copter because "Feedback to Pilot" raises throttle to 1/2 of THR_MID
  • Spline twitches slightly as it passes a waypoint especially if WPNAV_SPEED is set > 500.
  • Dropped support for NMEA and SIRF GPS on APM boards (ran out of Flash space)
  • Dropped ssupport for sonar for MultiCopters on APM1 and TradHeli on APM1 & APM2 (ran out of Flash space)

If you hit issues, please post them in the APM Forum and include a dataflash log file if possible.

Special thanks the Marco and the Beta Testing team from the AC3.2 beta testing thread who put their copters at risk in the pursuit of a smooth, safe release.  Here are links to some of their videos: Marco's DJIs900, Holger's Water Tower, Josh's Acro, Ray's TradHeli2&FPV, Raph's Hawaii, PhillS's CommandYawThor's Zombie Run&FollowMePhanivyas's Test, Rob's TradHeli, Christian's Test1&Test2Balloon's Spline, JimJ's FPV, Ultrojo's ROI & Spline&FollowMe1&FollowMe2, Troy's Mission

Thanks also to the code contributors to this release including Tridge, Jonathan, Leonard, RobL, Paul Riseborough, MichaelO, Julien Dubois, David Dewey, Andrew Chapman, Emile, Allyson and many more.  If you want to get involved check-out our dev wiki.

E-mail me when people leave their comments –

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

Join diydrones

Comments

  • I have, what I think is a Mission Planner/3.2/Pixhawk bug which may cause flyaways due to poor compass calibration. On the APM 2.6 it is okay but with Pixhawk the Mission planner calibration routine says calibration is complete after 15 or so seconds although I have only rotated through a little more than one axis. With the APM it waits until I tell it I am done. Calibration is inconsistent and with my CSG neo 8 the offsets are always too large and the internal compass is very different each time. This has been reported by at least one other user.   . 

  • I have, what I think is a Mission Planner/3.2/Pixhawk bug which may cause flyaways due to poor compass calibration. On the APM 2.6 it is okay but with Pixhawk the Mission planner calibration routine says calibration is complete after 15 or so seconds although I have only rotated through a little more than one axis. With the APM it waits until I tell it I am done. Calibration is inconsistent and with my CSG neo 8 the offsets are always too large and the internal compass is very different each time. This has been reported by at least one other user.   . 

  • Here is some experience of AruCopter3.2 on my Quad.
    There are two mechanically identical Quad copter.
    1) Motor: Turnigy Multistar 4108-600
    2) Wheel base: 640mm
    3) Battery: 4S5000mAh-35C
    4) FC: Pixhawk
    5) ESC:
    5-1) MultiStar 45A Simonk
    5-2) RCTimer 30A Simonk
    6) Propeller
    6-1) Length=14 inch / pitch=5.5 inch Carbon
    6-2) Length=13 inch / pitch=4.0 inch Carbon

    The combination of 5-2) and 6-1) is hardly fly and crash.
    Hovering current will 4.83A by eCalc.

  • as long as your TRIM_THRT is between 400 and 600  there is nothing to worry. if the TRIM_THROT is below 400 then you should consider reducing the prop size. second option is to add some weight to aircraft so that theTRIM_THROT value increases.

  • I had flown my quad with AC3.2-rc14 with APM2.6. on the second waypoint the aircraft got stuck. i gave RTL but it did not respond. finally i flew the aircraft manually to a safe landing. exactly same thing happened on a other aircraft that had AC3.2-rc14 with Pixhawk that also got stuck on the second waypoint and did not take RTL command. but after doing RTL couple of times it finally returned. somehow i do not have the logs for both of them. this has never happened before i upgraded to AC3.2-rc14 version. the auto missions have always been very accurate and reliable.

  • Hi MarkM,

    You are correct.  I thought MP had stayed in Beta.  My mistake but in any case I still think the all of the guys who put the software and hardware together do a fantastic job.

    I will try not to jump the gun again!  Sorry.  Alex

  • Thanks Winston. 

  • Hi Denny Rowland! APM Planner for mac not perform the calibration of the two compasses in AC3,2, at least not for now, you have to do with Mission Planner (windows OS) in its latest beta versions.

  • hi,

    another test flight in gusty weather using AC 3.2 and the default pids (no autotune!):

    https://www.youtube.com/watch?v=vOS9P3vtt-g

  • Hi Guys

    I have flashed 3.2 Beta from APM Planner2 (Mac) several times now but I always end up with this same message after completing compass calib.    "pre arm check - Compass not calibrated"

    The typical values I see are x=32.959  y= 33.959  z= 212.588. (These seem to work OK with 3.1.5)

    I have tried a different compass with the same result and have run out of ideas now.  

    After a 3 year hiatus, due to over indulgence in that Chinese stuff, I seem to have lost my way a bit with APM.  

    Guess I must be doing something wrong....

This reply was deleted.