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

          • I also saw this pulsing only in Auto mode on 3.2rc1, but I described it as a 'pitching' motion.

            I now have loaded 3.2rc2 but have not retested since.

            Martin

            • pulsing is a serious problem. Imagine flying in auto mission then all of a sudden this happen? That's a total disaster! so it's important to know it's origin or cause.

          • @Henri, sorry on putting this question in your thread.

            Yes your right, I'm asking that in general. So to avoid that in the future.

      • Oops..

        In the file 10-05-32 you can see STA, Alt hold,Hybrid

        In the file 10-35-13 the short mission and the thr out pulsing is visible..

        Hope this helps

        Thank you randy.

        Henri

        _logs.rar

      • Hi Randy I did "rar" the two .log files.. not sure in which is the short mission..

        Thank you for your time.

        Henri

        _logs-30-May-14.rar

        https://storage.ning.com/topology/rest/1.0/file/get/3702653071?profile=original
  • Just do a DO_SET_ROI with all parameters set to zero, this will cancel the previous DO_SET_ROI.

    Umm... this was meant as a reply to http://diydrones.com/xn/detail/705844:Comment:1674176... guess I should enable Javascript.

    • Hopefully it will get added to the Wiki before the official release as there is no way of knowing that from this documentation http://copter.ardupilot.com/wiki/mission-command-list/#Do-Set-ROI

      I do prefer the new way on 3.2 where it holds the ROI thru all waypoints once it starts, way better than having to put it in every waypoint, but I still think something like a Do-Cancel-ROI would be more intuitive than setting all 0s for canceling it.

      Thanks Fabian for the info, Ill try it out.

  • First, I thank all the folks who are working so hard on 3.2. It looks very exciting. One issue I see looming in the very near "drone" future is safety. We are one serious accident and one lawsuit away from a lot of headaches. I'm not sure if this is the right forum to post this but, is anyone working at incorporating the new quad failure stability algorithms (in case of a lost motor) in to the APM or Pixhawk? I'm guessing only the Pixhawk would have the horsepower to implement this. Link here...

    http://www.gizmag.com/quadcopter-failure-algorithm/30031/

    I'm very interested in this. 

  • Is there anybody who already did a comparison of the PWM output signals with osciloscope? (APM and Pixhawk)

    Emin, you know, we can change the PWM positive and negative with BlHeli, right?

    So many posts about motor/ESC issues at the moment...

    I'm little scared to fly with new pixhawk when it arrives.

    •  just cant stop watching his amazing videos

      here is gimbal view , BLG at work...

      mwc hexa // blg flipI

This reply was deleted.

Activity