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

        Steve,

        Based on your previous posts, it looks like you're a new user to arducopter.  That's great of course but you should definitely stick with the nice and stable official firmware which is AC3.1.5.

        The First Time setup wiki is here which might help you get started.

        Alternatively if you have a dataflash log I can have a look at your flyaway issue.

        • Yes, Im a beginner. I cant use 3.1.5 because I have S.BUS problems.

  • Dear sir : whould you please read this
    _____in  ArduCopter 2.x (traditional heli) (224) _____About ::

    ::

    APM Heli V3.15 vs V2.73 _ The most we holp is :::

    I holp 2.73 add INS_MPU6K_FILTER is the best ...

    http://diydrones.com/forum/topics/apm-heli-v3-15-vs-v2-73-the-most-...

     

  • 3.2RC4, fly very well.

    Thank you for development staff.

    https://vimeo.com/103391672

    • That is smooth. I was going to wait for a final 3.2, but I'm finding it hard to resist flashing this.

      Anyone been flying rc2, 3, or 4 with a Y6B and APM 2.6? How is it?

  • Is there a list of changes from the latest stable to the 3.2rc4?

  • Need some help with this one please... 

    - Load 3.1.5 (no cal, no wizard, nothing but software load...).  Apply LiPo power, all ESC's beep:  beeep-beeep-beeep - beep-beep - followed by single ongoing beep, all motors wiggle.  Arms and flies normally.

    - Load 3.2-rc4 (no cal, no wizard, nothing but software load...).  Apply LiPo power, 1 ESC beeps:  beeep-beeep-beeep - beep-beep - followed by single ongoing beep, only that motors wiggles.  Arms but only one motor turns.  Disconnect / reconnect LiPo, 4 ESC do beeep-beeep-beeep  (no double beep, no ongoing beep), but that's it...  Arms but motors will not turn.

    - Reload 3.1.5, all operations normal, flies perfectly with no cal/wizard, etc...

    How can software loads affect the ESC in this manner?

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…