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

    • Both compasses have high offsets. GPS modes need a good compass reading.

  • I'm sure this has been answered, but couldn't find it.

    When attempting to download logs via Mavlink (usb), I get "error receiving log list". What is the causing that?

    Thanks.

    • This reply was deleted.
      • 3.2

        1.3.17

  • This reply was deleted.
    • This reply was deleted.
      • This reply was deleted.
        • This reply was deleted.
          • Hello Alex

            Thanks for taking the time to help.

            To answer a few questions,

            Set PID's back to default

            Their is foam over the Barometer sensor

            Increased  INS_MPU6K_FILTER to 10 the 20. Default 0. Noticed slight improvement

            Note INS_MPU6K_FILTER set back to 0 for log

            Throttle set to mid

            Props balanced

            Balance of copter good. Hung by string at mid point.

            Still pulses in alt and loiter

            Log attached Default + IMU

            Hope this helps

            Cheers John H

            New Zealand

    • Can you test by using a house fan or something indoors and see if it affects the altitude reading as you manually rotate the copter at different angles to the wind?

  • H1 all

    I have a problem with POSHOLD.

    I have set the quad up as best I can. It flies very stable in Stabilize mode. and is very responsive.

    When switching to POSHOD it starts to bounce up and down. Motors quick accelerate and decelerate. moving copter about 100mm in either direction. I have set mid throttle as per log.

    Log attached.

    Cheers John H

    3691173134?profile=original

    2015-01-18 19-18-09.bin

    • Another suggestion, check your vibrations level, I had some issue in one copter and that was the problem

  • 3701915334?profile=originalBased on the logs it looks like motor 1 and 3 where trying to keep the copters nose up.  This could have been caused by wind or the front of the copter is heavier.  When you selected Loiter the copter which was coming down would now try to level off which will cause the motors to change.  At that point the copter was starting to pitch over on its right side badly as motor 2 was told to idle with no effect as the copter flipped several times.

    It did recover when you put it into Stabilize mode but then motor 1 went to idle and then to max?

    This is where if we had motor feed back we could see what the motors did.

     

    Mike

     

This reply was deleted.

Activity

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