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

        • AMP 2.6 using 3.2 rc7 Arducopter Droid Planner 2.6 Beta from

          http://3drobotics.com/2014/06/follow-me-mode/   "using Nexus 7"

          Follow Me works just fine with this setup.

          Now 3.2 rc9 I can't get follow me to work. I do see a new droid Planner which I have not

          updated to yet.

           

    • Developer

      Thanks Rainer for your feedback.

  • Hi Marco.

    I am unable to use Hybrid Mode / PosHold with my Walkera QR-X350-Pro (APM Copter 3.2).  Loiter works fine, but it does not change into PosHold mode in Mission Planner when I activate it.  Nor does it work flying.  Any idea why this might be?  I noticed a few other people are also experiencing this problem with their QR-X350-Pro. 

    If you have any ideas, I would greatly appreciate it.  Thanks again to all you guys for your great work!  ;)

    - BaNe

    • Developer

      I'm sorry but i don't know what firmware is installed on that machine.
      It's possible that we have removed some features.

      • Actually, with the latest firmware from Walkera, Loiter is flying fast now.  But, I am trying to fly a 40 meter circle.  But, I get a partial circle then a corkscrew towards the center.  Any suggestions on the Circle_Rate parameter?  I believe the quad has a version of AC 3.2.  So that's in meters?  Thanks, Brother.

        I found out PosHold doesn't work on my Quad.  But, the new Loiter is fantastic.

  • I did my range finder setup. I have an EZ4 sonar and did the settings according to the online instructions sonar settings for arducopter 3.2. When i lift copter above 20 cm then the readings seem fine. When it goes below that the reading shoot upto 130? And stay there until i lift it up above 20cm. Will this cause it to shoot up when trying to auto land?
    • Pic 1 sonar reading when in land position
      Pic 2 sonar reading when lifted about 20cm

      Screenshot_2014-09-19-18-56-34.png

      Screenshot_2014-09-19-18-57-40.png

      https://storage.ning.com/topology/rest/1.0/file/get/3702519513?profile=original
      • MR60

        hi,

        the minimum distance the sonar can measure is 20 cm. This is normal.

        • Wont that cause any problems when landing in auto. And thanks for reply
          • Developer

            Definitely the bad sonar alt is not good and I'd expect problems when landing in AltHold or Loiter so we should get to the bottom of the problem.

            While landing in Auto, RTL it should be ok because it doesn't actually use the sonar for that (it just sets a target speed).

This reply was deleted.

Activity