Developer

ArduCopter 3.2 ready for wider use

After months of testing, ArduCopter 3.2 (aka APM:Copter) is ready for widespread use and we invite all users to give it a try.  In order to manage the support load at first it will be available only through the Mission Planner and APM Planner2's Beta Firmwares link.  This link is visible from the regular "Install Firmware" page if you check the "Advanced View" on the Config/Tuning >> Planner page.  On APM Planner2 the "Advanced View" it is under the File menu.

In about two weeks we plan to replace AC3.1.5 with AC3.2 as the default version dispensed by the ground stations.

The full list of changes can be found in the ReleaseNotes but here are the highlights:
Flight Mode Enhancements:

  • PosHold flight mode: similar to Loiter but with direct response to pilot input during repositioning
  • ACRO mode handling improvement EXPO (for faster rotations)
  • Drift mode uses "throttle assist" (similar to AltHold)
  • Smoother transitions between flight modes (i..e when entering Loiter or RTL from high speeds)

Mission Enhancements/Fixes:

New Sensors/Devices:

Safety Features:

  • EKF/DCM check will switch to LAND mode if heading error > 60deg for 1 second
  • Baro glitch detection
  • Pre-arm check for Gyro calibration success
  • Pre-arm check that internal & external sensors (gyros, accels and compass) are consistent (Pixhawk only)
  • Parachute support (Pixhawk only)
  • Feedback to Pilot when taking off in AltHold, Loiter, PosHold (i.e. motors spin up a little as throttle is raised)
  • EKF (new attitude and position estimate system only used for reference in this release)

Bug Fixes:

  • Pixhawk GPS driver buffer overflow that could lead to missed GPS messages
  • Pixhawk I2C bug that could lead freeze up if I2C bus is noisy


Known issues/Warnings:

  • Pixhawk users will need to recalibrate their compasses
  • PosHold won't show up as option on FlightMode screen if you have an old version of mission planner.  Please select Help > Check for Updates
  • Landing detector is more strict meaning it may take longer to disarm after RTL, AUTO
  • Set THR_MID parameter especially if you have a very powerful copter because "Feedback to Pilot" raises throttle to 1/2 of THR_MID
  • Spline twitches slightly as it passes a waypoint especially if WPNAV_SPEED is set > 500.
  • Dropped support for NMEA and SIRF GPS on APM boards (ran out of Flash space)
  • Dropped ssupport for sonar for MultiCopters on APM1 and TradHeli on APM1 & APM2 (ran out of Flash space)

If you hit issues, please post them in the APM Forum and include a dataflash log file if possible.

Special thanks the Marco and the Beta Testing team from the AC3.2 beta testing thread who put their copters at risk in the pursuit of a smooth, safe release.  Here are links to some of their videos: Marco's DJIs900, Holger's Water Tower, Josh's Acro, Ray's TradHeli2&FPV, Raph's Hawaii, PhillS's CommandYawThor's Zombie Run&FollowMePhanivyas's Test, Rob's TradHeli, Christian's Test1&Test2Balloon's Spline, JimJ's FPV, Ultrojo's ROI & Spline&FollowMe1&FollowMe2, Troy's Mission

Thanks also to the code contributors to this release including Tridge, Jonathan, Leonard, RobL, Paul Riseborough, MichaelO, Julien Dubois, David Dewey, Andrew Chapman, Emile, Allyson and many more.  If you want to get involved check-out our dev wiki.

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • I just replaced the 5v bec i was using to supply 5v to the FC .. if you are using a Power module ..try with only a new 5v source ..

  • Hi Rui .. I had a similar problem on one copter i built a few moths ago.. it used to fly well for a few mins then just falls out of the sky .. there was no indication of power supply issues or brown outs in the logs .. But I discovered the 4.8 to 5.0v feed was not enough seems the processor just needed a little more power, I changed the 5v supply now reads 5.6v..Never had an issue since.
  • Ah...  I somehow thought DG was having the problem.  Sorry Rui. 

  • @DG,

    Was the flight yesterday?  If so, did you check Solar Storm activity?  I noted last evening K-Index was 5 (red condition) which means it's possible you may have had GPS lock issues.

  • Rui,

      I'll look at your logs; no expert here but am improving :)

    Try using 'APM Flight Log Analyzer" http://www.rcgroups.com/forums/showthread.php?t=2151318

    Maybe it will give you helpful information; it did for me.

  • Developer

    The PM fail can be ignored (PM = PerforMance).  What's happening there is the PM messages aren't ignoring the delays that occur during the gyro calibration when arming.

    The GPS issue is unlikely to be a firmware issue.  It's more likely that the vehicle really didn't have GPS during the flight.

  • This has me worried:

    Size (kb) 8554.380859375
    No of lines 114684
    Duration 6 days, 22:11:00
    Vehicletype ArduCopter
    Firmware Version V3.2
    Firmware Hash c8e0f3e1
    Hardware Type
    Free Mem 0
    Skipped Lines 1

    Test: Autotune = UNKNOWN - No ATUN log data
    Test: Balance/Twist = GOOD -
    Test: Brownout = GOOD -
    Test: Compass = GOOD - mag_field interference within limits (8.12%)

    Test: Dupe Log Data = GOOD -
    Test: Empty = GOOD -
    Test: Event/Failsafe = GOOD -
    Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99
    Test: IMU Mismatch = GOOD - (Mismatch: 0.62, WARN: 0.75, FAIL: 1.50)
    Test: Parameters = GOOD -
    Test: PM = FAIL - 17 slow loop lines found, max 7.20% on line 108374
    Test: Pitch/Roll = GOOD -
    Test: Thrust = GOOD -
    Test: VCC = GOOD -

    In the logs there are no gps issues (NSat and hdop). I don't know what PM is.

    Took off in stab (no simple/ss), switched to poshold to test before flying a mission, then it started twitching and drifting. I was able to land, but will not attempt again until knowing what is going on.

    Anyone?

  • If you look at the parameters, there is already trim built in by default. I didn't know that when I first got the 3DR Y6B and it kept pulling to the right and forward. Being a noob on that much copter gave me fits getting it in the air without rolling over. It so happened I also had the copter CG off in the same direction as the default trim, which compounded the problem.

    So my suggestion would be to first make sure the trims are zero in Mission Planner, then balance your copter by whatever method, and it should take off straighter assuming everything else is set up correctly.

    I ended up using scales to balance my Y6's. If the idea is to have equal weight distribution, it works great. .$8 on Ebay.

    RnXrcVc.jpg

  • thanks for the clarification! still does not work for me via usb, though - not sure why (never did)

  • I can assure you. I am only able to download dataflash logs over USB. It doesn't work for me over 3DR radio.  

    I assume you are talking about the removal of the CLI (command line interface) from the APM boards, you do not need the CLI for log download.

    To download logs over USB you need to click the 'Dataflash logs' tab on the main mission planner screen (the tab is a few tabs across from the 'status' tab). From there you can download logs.

This reply was deleted.