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

          • Funny you mentioned it possibly being next to s subwoofer at the post office... one of my spare external mag/compasses was accidentally placed in one of those shiny strongly magnetic screw/parts holders by my son while he was helping me clean my workbench. Needless to say when I later installed it, I got some pretty amazing compass readings when attempting to calibrate it. Luckily before giving up and tossing it, I remembered where it had been stored before I tried to use it. I brought it to work,  used a demagnetizer on it and it has been good-to-go ever since.

            On a side note: I also discovered the best place for me to calibrate a compass is outside with a long usb cord and my laptop. Wall mounted magnetic tool holders, magnetic parts/screw holders, PC with stack of hard drives, etc, etc... on/nearby my workbench proved to be not the best place to do it. :)  

            • This reply was deleted.
              • Yea, nothing like the joy of the usb cable disconnecting half-way through calibration. That and the look from neighbors when they see you performing some strange backyard seance with your UAV. I found that zip-tying the usb cable to the frame works well. 

                • I am using $9 bluetooth module connected to one copter. Sure, range is limited but still, 5m without cables is much better for configuration than cable :-)

                  And for Pixhawk - you need only cheap module from china and cable with DF13 to connect it (and one serial converter to configure bluetooth modul itself to 115K and reasonable name)

  • Hi,

    I had RC9 previously, after going into mission planner and upload to latest beta from there (hopefully RC14). pre arm is now saying I need to re-calibrate compass. Is that normal procedure? Just checking because I thought once I had 3.2 I do not need to do that again.

    Also, two quick questions.

    How / where can I download RC13?

    Where do I check to confirm which firmware my pixhawk is currently on?

    • Is POSHOLD mode in RC14?

      I only see "POSITION" and when I set that as a flight mode and flip my mode from stabilize to position. It does not show "position" as the flight mode in flight data.

      • I got it fixed. Had to update MP to latest beta and i saw back POSHOLD

    • Developer
      Please download 3.2 from the Beta menu.
      You can verify the code version by either looking at the messages received from the vehicle when the telemetry connects or by looking in the log file.

      Recalibrating your compass is required.
      • My compass calibration seems to be very fast. It normally takes long to complete.

        Is the new versions now faster with compass calibration ?

        • Yes the new Mission Planner ...I my case with pixhawk also less accurate. The Copter is yawing much more after new calibration. I did it several times with no good results.

  • This reply was deleted.
    • If tou read back some N amount of pages there was a discussion about demagnetizing the screws wich held pixhawk inside the case. I suggest first demaging those. Apperently some units are being assembled with a magnetized screw driver, this leaves the screws slightly magnetized. I actually had to heat up the screws till they were red than let them cool down,  this works too :) 

This reply was deleted.

Activity

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