Discussions

Developer

ArduCopter-3.2 beta testing

Posted by Randy on May 11, 2014 at 7:45pm

Warning #1: PX4/Pixhawk users upgrading from AC3.1.5 (or earlier) may need to re-do their compass and accelerometer calibration because AC3.2 also uses the backup compass and accels.  Pre-arm checks have been added to ensure this has been done.

Warning #2: on the APM2.x the logs must be downloaded using MAVlink instead of the terminal.

AC3.2-rc14 is now available for BetaTesters through the mission planner’s Beta Firmwares link.  The full release notes can be found in ReleaseNotes.txt and changes from -rc13 can be seen below.

     Feel free to raise issues found during testing on this discussion or in the new support section in the APM Forum.

     It’s a big release with “the onion” restructure and a bunch of new features (including these 57 closed items) so we need to re-test almost everything including all flight modes, all mission commands and all the new features.  Marco and I will be maintaining (and adding to) this testing list.  Issues reported will first be checked by Jonathan, Marco and I and then confirmed bugs/issues will be put on the github issues list (and then hopefully fixed).

     Thanks especially to the beta testers who put their copters at risk testing each release.  Enjoy!

Changes from 3.2-rc13
1) Safety Features:
     a) fail to arm if second gyro calibration fails (can be disabled with ARMING_CHECK)
2) Bug fixes:
    a) DCM-check to require one continuous second of bad heading before triggering LAND
    b) I2C bug that could lead to Pixhawk freezing up if I2C bus is noisy
    c) reset DCM and EKF gyro bias estimates after gyro calibration (DCM heading could drift after takeoff due to sudden change in gyro values)
    d) use primary GPS for LED status (instead of always using first GPS)

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

Join diydrones

Tags: 32, arducopter, beta, testing
Email me when people reply –
Follow

Replies

  • Felixrising May 13, 2014 at 5:48am

    Congratulations to all the people involved in this release!

  • Craiginho May 13, 2014 at 3:34am

    Will there be support for *12 configuration (Coaxial Hexcopter configuration) in future releases? I think this option is a possibility on the pixhawk?

  • Peter May 12, 2014 at 6:12pm

    Is SBus RSSI input 0-5v working with 3.2 and the pixhawk?

  • Edgar Scott May 12, 2014 at 4:12pm

    Just tested Hybrid mode, as a NAZA and APM flyer I am so happy its coming...but...

    I started in Stabilize, flew a bit, flipped to Hybrid and my TBS Pro darted off across the street, I put it back into stabilize and it came home, no crash but a little scary.  Glad it headed away from me and not towards me :-)  In my NAZA if GPS(Hybrid) does not have enough sats it simply defaults to Alt-Hold then auto switches to GPS mode when all the sats have been captured, not saying thats the issue but just not sure what it is.

    TBS Disco Pro, APM 2.6, 3dr gps, 3.2 rc1

    I know wheres the log.  I tried, but it wont come up with the option, see screenshots

    3701733245?profile=original

    3701733134?profile=original

    • Edgar Scott > Edgar Scott May 12, 2014 at 7:53pm

      HDOP was okay3702491377?profile=original

      You can also see where it took off when I changed to mode 16 (Hybrid)

      3702491298?profile=original

      • Julien Dubois > Edgar Scott May 13, 2014 at 12:35am

        3702650096?profile=originalThe Roll/Pitch problem came when Hybrid engaged Loiter (when DPosX/Y are updated).

        We can see here the Copter rolls away its target position instead of maintaining it.

        You had no stick Input and the GPS was great so, maybe, check a compass issue.

        If the copter thinks he's goind to North but actually flies to South, that could, imo, bring that kind of behaviour.

        Please give another try to hybrid and also Loiter.

        Check as well your param values.

This reply was deleted.

Activity