Developer

ArduCopter 3.2.1 released

Warning: there was a period of about 12 hours after this blog was first posted where an older version (AC3.1.2) replaced AC3.2.1 for APM2.  If you think you may have downloaded for the APM2 during these initial period, please check the version on your board by looking at the title bar of the Mission Planner (see the 5th comment from me below for a screenshot)

ArduCopter 3.2.1 has completed beta testing and has been released as the official version available through the mission planner and other ground stations.  If upgrading from AC3.2 there should be no need to re-do any configuration.

Changes from AC3.2 are listed below and in the ReleaseNotes:
1) Enhancements:
    a) reduced twitch when passing Spline waypoints
    b) Faster disarm after landing in Auto, Land, RTL
    c) Pixhawk LED turns green before arming only after GPS HDOP falls below 2.3 (only in flight modes requiring GPS)
2) Safety Features:
    a) Add desired descent rate check to reduce chance of false-positive on landing check
    b) improved MPU6k health monitoring and re-configuration in case of in-flight failure
    c) Rally point distance check reduced to 300m (reduces chance of RTL to far away forgotten Rally point)
    d) auto-disarm if vehicle is landed for 15seconds even in Auto, Guided, RTL, Circle
    e) fence breach while vehicle is landed causes vehicle to disarm (previously did RTL)
3) Bug Fixes:
    a) Check flight mode even when arming from GCS (previously it was possible to arm in RTL mode if arming was initiated from GCS)
    b) Send vehicle target destination in RTL, Guided (allows GCS to show where vehicle is flying to in these modes)
    c) PosHold wind compensation fix
    d) prevent infinite loop with do-jump commands pointing at each other
    e) pixhawk memory corruption fix when connecting via USB
    f) vehicle stops at fence's alt limit in Loiter, AltHold, PosHold (as it did in AC3.1.5)
    g) protect against multiple arming messages from GCS causing gyro calibratoin failure

Thanks very much to Marco and our beta testers who put their copters at risk over the past several weeks to help us iron out these issues.  Also Thanks to Raph for the video (this is actually a video from AC3.2).

E-mail me when people leave their comments –

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

Join diydrones

Comments

  •  b) improved MPU6k health monitoring and re-configuration in case of in-flight failure

    Could you expand on what exactly happens in this scenario with the new firmware?
    I've had the in flight hardware failure so I'm curious.

    Thanks

  • good news Randy, Im already have a px4flow hardware.
    what sort of implementation for px4flow? full supports for all features? (optical flow, sonic range finder etc)

  • Developer

    We had a slight hiccup in the release tagging so if you loaded the firmware within 1.5h of this blog post appearing you may have loaded AC3.1.2 (instead of AC3.2.1).  This has now been corrected.

    You can see the version easily by connecting with the mission planner and right at the very top it has the version number.  It should show AC3.2.1 as shown below.

    3701932342?profile=original

  • Developer

    @Alp, yes, it won't be too long before the first AC3.3 release candidate goes out.  Hopefully within 2 weeks.

    The first AC3.3 release candidate will have the EKF on by default, PX4Flow support (i.e. optical flow sensor) and retractable landing gear (and a few other things).

    Later release candidates will include Return-To-Me and AutoTune for yaw.

    We'd really like to get Terrain Following and some basic form of obstacle avoidance into the final AC3.3 but those are still not even close to complete yet so we can't make any promises about that.

  • Thank's Randy

  • Thats Cool, What about the v3.3 beta release :)

  • Bravo Randy & Dev Team...

This reply was deleted.