Developer

ArduCopter-3.2.1 Beta Testing

ArduCopter 3.2.1-rc2 (release candidate #2) has completed beta testing and has been released as the official version available through the mission planner and other ground stations.

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 to Raph for the video.  This is actually a video from AC3.2 until we have one specific to AC3.2.1.

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

Join diydrones

Email me when people reply –

Replies

    • Developer

      Well, that's not good.  AC3.3-dev has not gone through beta testing yet so no guarantees it will work well.

      • I attempted to autotune today.

        The left-right part (the first half) was normal. During the forward-backward (second half) phase and in particular during the forward movement, I noticed that right after each oscillation the copter was adding a substantial amount of yaw towards the right. Wind wasn't strong enough to be a factor and was changing direction quite rapidly.

        Is it supposed to do so? I've never seen it when I've done autotune in the past, but I've changed motors and propellers since (to very well balanced KDE motors and 15 inch props). It flies fine otherwise. Autotune terminated and I saved the new PIDs, which are ok (not perfect but definitely better than the defaults).

        Log attached

        62.BIN

        https://storage.ning.com/topology/rest/1.0/file/get/3702692528?profile=original
    • most likely they got it from the dev repo 

  • Developer

    I've been a bit absent for the last 2 weeks because Tridge and I were in SanFran attending the Embedded Linux Conference and meeting with 3DR people in the Berkley office.Back in Japan now and we've apparently resolved the altitude issue that were holding up AC3.3-rc1 so hopefully AC3.3-rc1 will be out by this weekend (I've said that before but this time it should really happen).

    • Hi Randy,

      Is AC3.3-rc1 only for Pixhawk? Regards.

      • Developer

        Willy,

        Yes, only for Pixhawk and other fast CPU boards (Flymaple, PX4-v1, VRBrain, Linux, etc).

        • That's kinda cruel. I just bought APM 2.6 original hardware and now it's that I'm stuck with drifting height problem and incomplete EKF filter (which is in fact not working properly in this firmware, but it takes valuable ROM size, because lack of which development on APM stopped).

          Maybe you can at least fix altitude things and make 3.2.2?

          What should I do now? Send my APM to store and ask for moneyback because hardware is unusable for me? Man, that just destroys all positive image APM boards. :(

          • Developer

            Marko,

            I think Rob Lefebvre can help look into the specific issues some users are having with AC3.2.1 on the thread opened for that issue.  We went through months and months of testing including many APM2 users but if it turns out to be a firmware issue that can be fixed we can release a 3.2.2.

            I've also sent a note to the 3DR guys responsible for the store and asked them to add a note that recommends people purchase the Pixhawk instead of the APM2.6.

            • Great Randy :) I have the Pixhawk in my wishlist but, for the moment I'm part of the nostalgic APM users and if something can do to get more stable Pos hold it's great,  but I'm not worry because I learned a lot trying to have my copter more stable and now is another guy, but anything to be better is welcome and can help to test.

              I agree with Marko that 3DR have to alert buyers sometime ago that APM is not possible to update anymore.

              Anything I'm not shure with Pixhawk; I'm waiting yet for an external compass to solve compass interferences, If Pix have one internal compass that's means problems again? I read many post with Pix with compass interferences, any solution?  thank's

              • Hi Cala
                The Pixhawk internal compass works fine (my X8 uses it alone) provided:-
                a) The case screws are not magnetised
                b) It is far enough away from any other source of interference

                If this is not possible and/or for backup then an external compass is required.
This reply was deleted.

Activity

DIY Robocars via Twitter
May 15
DIY Robocars via Twitter
May 14
DIY Robocars via Twitter
May 13
DIY Robocars via Twitter
RT @f1tenth: Say hi to our newest #F1TENTH creation for @ieee_ras_icra next week in Philly. It’s going to be huge! 😎 🔥 @AutowareFdn @PennEn…
May 13
DIY Robocars via Twitter
May 11
DIY Robocars via Twitter
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Noticed my car zigzagged in last run. It turned out to be the grass stuck in the wheel and made the odometry less accura…
May 8
DIY Robocars via Twitter
RT @SmallpixelCar: Test my car. RTK GPS worked great. Thanks @emlid for their support. https://t.co/EkQ6qmjmWR
May 8
DIY Drones via Twitter
RT @chr1sa: @kane That's @diydrones circa 2009. Still have a box of those Canon cameras that we used to strap into planes, just like this.…
May 3
DIY Robocars via Twitter
RT @chr1sa: Our next @diyrobocars race is going to be outside at a real RC racetrack in Fremont on May 28. Fully autonomous racing, head-to…
Apr 30
DIY Robocars via Twitter
RT @f1tenth: Our Spring 2022 F1TENTH course @PennEngineers is coming to an end with a head-to-head race as a big finale. So proud of our st…
Apr 26
DIY Robocars via Twitter
RT @DanielChiaJH: I wrote a thing! Throughout the development of my @diyrobocars car I've been using @foxglovedev Studio to visualize and d…
Apr 23
DIY Robocars via Twitter
RT @SmallpixelCar: My new car for high speed. Low body, everything ( @NVIDIAEmbedded Jetson Xavier NX, @emlid RTK GPS, IMC) under the deck…
Apr 23
DIY Robocars via Twitter
Apr 21
DIY Robocars via Twitter
RT @f1tenth: F1TENTH Race training setup @PennEngineers for our upcoming ICRA2022 @ieee_ras_icra competition. @OpenRoboticsOrg @IndyAChalle…
Apr 21
DIY Robocars via Twitter
RT @fatcatFABLAB: Proud to be hosting a restarted DIY Robocars NYC Meetup April 26. Come by if you want to talk about and race self-driving…
Apr 17
More…