Discussions

Developer

ArduCopter-3.2 beta testing

Posted by Randy on May 11, 2014 at 7:45pm

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

Tags: 32, arducopter, beta, testing
Email me when people reply –
Follow

Replies

    • Developer
      Randy > Edgar Scott May 29, 2014 at 4:12am

      Nice video.  Great to see spline in action.

      • Edgar Scott > Randy May 29, 2014 at 10:33am

        Randy,

        I read the wiki and it said in 3.2 DO_SET_ROI will hold the nose without entering multiple commands, as shown this video it did just that.  Problem is I have clue how to cancel and get it to return it back to normal yaw(nose) position.  So once set seemed as it was always set.  How do I cancel the DO_SET_ROI?  Do we need an END_SET_ROI?

        http://copter.ardupilot.com/wiki/mission-command-list/#Do-Set-ROI
        (Note: in AC3.2 it will be possible for DO_SET_ROI without entering multiple commands).

        Thanks, Ed

        • Bravojul > Edgar Scott May 29, 2014 at 11:51pm

          IIRC, a DO_SET_ROI with lat,lon set to 0,0 cancels the command

  • This reply was deleted.
    • Developer
      Randy May 28, 2014 at 5:43am

      Peter,

           Txs for the report.  The EKF shouldn't affect the autotune so you should be able to stick with the previous PIDs.  Generally the EKF (which only runs on the Pixhawk) should perform just like the existing DCM+inertial nav (it replaces both) although it should be more resistant to vibration and other sensor noise.

    • Jay Galleno May 28, 2014 at 2:44am

      Same question I posted here earlier but there's no response, even from the dev team.

  • Ravi May 27, 2014 at 9:26pm

    @christian , thanx for the list. i did not realize that the sunrise 20A ESC have SiLab processor. I have ordered sunrise 20A BLheli firware ESC. I am glad the ESC in in this list. the list should be updated regularly since there so many brands of ESCs in market. I still think the ESC sync  with pixhawk is a major issue and could be a cause to some unexplained crashes. honestly, i never had a crash in last two years. this is my first crash (really bad) and i would try to eliminate this cause forever.

  • This reply was deleted.
    • Developer
      Randy May 28, 2014 at 5:40am

      Gary,

          Thanks for the report.  A few others have made similar complaints about the slow-response in yaw.  There are some parameters starting with ATC_ (i.e. ATtitude Control) that could be increased and might improve this but basically we need to increase the default rates probably.  We should be able to sort this for -rc3.

  • Jiro Hattori May 27, 2014 at 3:53pm

    @Felix, it is better to open here to show  my understanding.

    As you already know a lot on this area, Pixhawk consists from PX4FMU-V2+PX4IO-V2.

    The firmware for PX4IO-V2 that is provides by ArduCopter 3.1.X dose not support THFSS-Air.

    That of ArduCopter 3.2 rc2 support THFSS-Air.

    Both ArduCoter 3.1.X and ArduCopter 3.2 support S-FHSS could handle S-BUS receiver FASST.

    If you want to use telemetry feature with T10J-R3008SB then you need everything.

    1) Bind T10J-R3008SB with THFSS-Air for telemetry

    2) Connect Pixhawk R/C input port and R3008SB S-BUS

    3) Load ArduCopter 3.2 to Pixhawk

    4) Calibrate R/C on Mission Planner

    5) Connect Futaba CAR-VIN-700 external voltage cable to your R3008SB

    That is all.

    I hope the release of ArduCopter 3.2 includes new S-BUS communication feature;)

This reply was deleted.

Activity

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