The ardupilot development team is proud to announce the release of version 3.2.1 of APM:Plane. This is primarily intended as a bugfix release, but does have some new features.

The major changes in this release are:

  • fixed a mission handling bug that could cause a crash if jump commands form an infinite loop (thanks to Dellarb for reporting this bug)
  • improved support for in-kernel SPI handling on Linux (thanks to John Williams)
  • support UAVCAN based ESCs and GPS modules on Pixhawk (thanks to Pavel, Holger and and PX4 dev team)
  • Multiple updates for the NavIO+ cape on RaspberryPi (thanks to Emlid)
  • multiple automatic landing fixes, including improvements in flare detection, glide slope calculation and lag handling
  • fixed a bug that could cause a change altitude MAVLink command from causing a sudden descent
  • re-enable CLI on non-APM1/APM2 boards
  • Lots of EKF changes, including reducing impact of ground magnetic interference, reducing the impact of a GPS outage and integrating optical flow support
  • added initial support for the PX4 optical flow sensor. Just logging for this release.
  • added support for MAVLink packet routing
  • added detection and recovery from faulty gyro and accel sensors
  • improved arming checks code to detect a lot more error conditions, and change the ARMING_CHECK default value to check all error conditions.
  • added support for BBBMini Linux port
  • increased number of AVR input channels from 8 to 11
  • auto-set system clock based on GPS in Linux ports
  • added SBUS FrSky telemetry support (thanks to Mathias)


IMU Failure detection

Perhaps the most important change for this release is the improvement to the detection and recovery of bad IMUs. We have had a number of reports of bad IMU data in flight from both the mpu6000 and lsm303d. Where possible the drivers how try to detect the failing sensor and reset it. Sometimes it can't be reset, in which case it will be locked out and the other IMU will be used, unless it is the last available IMU, in which case it will still be used. In either case the user is notified of the failure via the GCS so they can land.


UAVCAN support

The main new feature in this release is support for UAVCAN ESCs, GPS modules, compasses and barometers. Note that while support is in for UAVCAN ESCs and I have been flying with a UAVCAN ESC on my test plane for a few weeks very successfully, support for configuring the ESC is still fairly basic. You will need a debug cable to connect to the ESC to configure it as per the http://uavcan.org website. We hope to add MAVLink enabled configuration soon.

Many thanks to everyone who contributed so much to this release with bug reports, patches and suggestions. My apologies that we didn't get everything done that we wanted to get done. We have pushed some things out to the next release to prevent the release date sliding back any further.

Happy flying!

Views: 3958

Comment by Jacko on February 5, 2015 at 4:03am

Cant wait to try it. Landing code is getting more impressive every release - great work going on here by this team. Just wish I could get hold of a SF02. The wait seems to go on forever....

Comment by ECODRONES on February 5, 2015 at 4:25am
Great news Andrew, thank you and all team!
Comment by Mikhail Avkhimenia on February 5, 2015 at 4:39am

Hurray, congratulations to all the developers and users!


Developer
Comment by Marco Robustini on February 5, 2015 at 4:57am

Nice job Team!

Comment by Mark on February 5, 2015 at 6:08am

SBUS FrSky telemetry support, does the mean the new smart port protocol?

Comment by Paul Meier on February 5, 2015 at 6:31am

Big thanks for everything.

Re: added SBUS FrSky telemetry support (thanks to Mathias)

any docs / how to ?

Comment by Rana on February 5, 2015 at 9:02am

Hey Tridge, well done man ! see the enormous amount of changes, shouldn't it be a 3.3 rather than 3.2.1 ?

Comment by Jeroen Brosens on February 5, 2015 at 12:17pm

"added SBUS FrSky telemetry support"

That should probably read: "added FrSky S.PORT telemetry support"


Developer
Comment by Andrew Tridgell on February 5, 2015 at 12:59pm

@Mark, yes, it is the smart port protocol

@Jeroen, yes, sorry for the typo

@Paul, I'm hoping Mathias will extend the wiki docs soon on how to use it

Cheers, Tridge


Developer
Comment by Andrew Tridgell on February 5, 2015 at 1:12pm
The docs on setting up FrSky S.Port support are here:
http://plane.ardupilot.com/wiki/common-frsky-telemetry/

Comment

You need to be a member of DIY Drones to add comments!

Join DIY Drones

© 2017   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service