Developer

ArduCopter-3.2 beta testing

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

Email me when people reply –

Replies

          • Developer

            Thorsten,

            If you're up for testing it, could you also test AC3.1.5?  I'm pretty sure you'll find the same issue is there as well.

            • T3

              Randy,

              yes, same issue there - if I remember correctly (95% confident ;-)). I'll make some further tests next week.

            • Thorsten, if some of the motors spin slower than the others when you raise the throttle, then, maybe, you need to do motors/esc calibration. Yes, that is confirmed by checking MOT/RCOUT to see if motors are out of synch.

              • T3

                Willy,

                thanks! Yes sure. That's what I did carefully.

  • T3

    Hi all,

    I just found that using rc5: 

    • the LOG_BITMASK 1854 does not include the Motors - just Default 
    • an option to log both IMU and Motors would also be good for testing purposes

    Kind regards,

    Thorsten

    • T3

      I searched for MOT. Was this renamed to RCOU?

      • Developer

        Thorsten,

             Yes it is.  A number of people have asked that we update the log bitmask, especially for the pixhawk to include everything so I'll make that change for -rc6.

             I was hoping to push out -rc6 this weekend but it's not quite ready.  Hopefully around Tuesday it'll go out.

        • T3

          Randy,

          Thanks! if I enable both IMU a RCOUT with Default in the Terminal the bitmask value is 1982. 

  • This reply was deleted.
    • Developer

      @sixtimesseven,

           I guess you're using a Px4 or Pixhawk?  Sounds very much like the compass isn't working.  The compass-external flag should automatically be set when it detects the external compass.

  • @Randy

    Would it be possible to merge this pull request in rc6?
    https://github.com/diydrones/ardupilot/pull/1150
    It is a very handy/simple gimbal for fpv.
This reply was deleted.

Activity

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