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

                  • 41k... that can't be it. Anyway I will get it right and get it on here tomorrow

          • COMPASS_EXTERNAL  was / is 1 by default fyi.

  • Every time i load the latest Beta 3.2-rc1 on Pixhawk i get a pre flight check gps not calibrated from apm.

    I have re-calibrated everything several times. I would like to get this build running in order to use follow me mode. Any suggestions?

    • @Andrew Nicholas

      Just not sure: Why 3.2-rc1? We are at rc-5... 

      I'm now using M.P. 1.3.9 build 1.1.5346.13591 with pixhawk the error messages (e.g. didn't press the blinking red switch) bring wrong error message in mission planner.

      So what version of M.P. are you using?

      You talked about pixhawk and apm so which one are you referring to?

      Henri

      • Developer

        Henri,

        I've just tested and I'm correctly seeing the "Arm: Safety Switch" message when the safety switch is not pressed but it also arms correctly when the safety switch is pressed (i.e. not blinking).  I'm using MP 1.3.9.1 build 1.1.5350.14145 which is the latest beta release.

        I guess this is different to what you're seeing or maybe I'm misunderstanding the issue?

        • Thank you for answering Randy.

          I didn't fully understand Andrew Nicholas's query:

          "Every time i load the latest Beta 3.2-rc1 on Pixhawk i get a pre flight check gps not calibrated from apm"

           

  • Hi dev team and testers,

    Tested version 3.2 RC5 on APM 2.6 and Pixhawk. Works very well except in a fast descend, straight down, in Drift mode my Tarot 650 almost became unstable. I have not noticed this behaviour in PosHold. This video shows a test of Follow Me and PosHold.

  • Is 3.2 released?

    I see you have started with 3.3

    "Author: Randy Mackay <rmackay9@yahoo.com> Date: Mon Aug 18 12:56:22 2014 +0900 Copter: range check ACRO_EXPO to be no more than 1 APMVERSION: ArduCopter V3.3-dev"

    • Developer

      Goran,

           No, we've branched though so that we can limit any further changes getting into AC3.2.  Our release procedures are documented here by the way although it's a bit technical.

  • I'd like to know if anyone is testing sbus2 with the current beta.  I have a Futaba R7008SB sbus2 receiver connected to a Pixhawk via a 3DR PPM encoder.  I've been happy using rc2-rc4 via the PPM Encoder.  I haven't had time to load rc5.  Thank you to the devs for what has been an excellent experience(for me)!  I would like to take advantage of sbus2 at some point.  I don't see any mention in this discussion relating to testing/experiences.  I don't mind testing this.  However, it would be nice to hear the feedback of others on the topic relating to 3.2. 

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @donkey_car: Human-scale Donkey Car! Hope this makes it to a @diyrobocars race https://www.youtube.com/watch?v=ZMaf031U8jg
Saturday
DIY Robocars via Twitter
Saturday
DIY Robocars via Twitter
Jun 16
DIY Robocars via Twitter
RT @GrantEMoe: I won my first @diyrobocars @donkey_car virtual race! Many thanks to @chr1sa @EllerbachMaxime @tawnkramer and everyone who m…
Jun 13
DIY Robocars via Twitter
RT @gclue_akira: JetRacerで自動走行したコースを、InstantNeRFで再構築。データセットは別々に収集 #jetracer #instantNeRT https://t.co/T8zjg3MFyO
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: SPC 3.0 Now the motor also works. This car is doable. I just need to design a deck to mount my compute and sensors. http…
Jun 13
DIY Robocars via Twitter
RT @SmallpixelCar: My new car SPC 3.0. https://t.co/CKtkZOxeNQ
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: High speed at @diyrobocars thanks @EdwardM26321707 for sharing the video https://t.co/o4317Y2U1S
Jun 7
DIY Robocars via Twitter
RT @SmallpixelCar: Today at @RAMS_RC_Club for @diyrobocars. Used @emlid RTK GPS and @adafruit @BoschGlobal IMU. Lap time 28s https://t.co/R…
May 28
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
More…