Developer

APM:Plane 2.74 released

The APM dev team is delighted to announce the release of APM:Plane 2.74, a major new release with a lot of new features. This release is recommended for anyone flying fixed wing aircraft with an APM2 or PX4.

There are a lot of changes in this release, but some of the highlights are:

  • new APM_Control attitude controllers.
  • new TECS speed/height controller from Paul Riseborough.
  • two new flight modes, ACRO and CRUISE
  • new camera trigger by distance system, for better aerial mapping
  • dozens of small fixes and improvements from two months of development
  • lots more documentation, including tuning guides for all the new parameters

Scroll down for a more complete list of changes, but before that I'd like to give you a bit more detail on the highlights above.

New Attitude Controllers

The new "APM_Control" attitude controllers have been in development for a long time. Originally developed by Jon Challinger last year, they were extended by Paul Riseborough and made compatible with the existing parameter names. The key advantage of these new controllers is their improved handling of noise, and much better ability to tune for your aircraft. There is a new tuning guide in the wiki which gives detailed instructions on how to make the most of the new capabilities.

One of the big effects you will see with the new attitude controllers is better handling of pitch compensation in turns. The new PTCH2SRV_RLL parameter makes tuning for flat turns much easier, which has been a major source of frustration in the past.

The new controllers also handle sensor noise much better, especially if you use any D term in your roll or pitch controllers.

New Speed/Height Controller

The new TECS speed/height controller is the second major controller change in this release, and will make a world of difference for aircraft with an airspeed sensor. After a lot of testing I decided to make TECS the default in this release, although you can switch back to the old controllers using the ALT_CTRL_ALG parameter if need be. If for some reason you find you do need these old controllers then please let me know, as I am planning on removing the old controllers in the next release.

The previous airspeed controller for speed/height suffered from a major problem that it gave absolute priority to airspeed. If the aircraft could not achieve the target airspeed you had set then it would dive to gain speed, even to the point of diving into the ground. This made it quite fragile, and you had to be very sure of your airspeed configuration.

The new controller operates over a range of airspeed values, set using the ARSPD_FBW_MIN and ARSPD_FBW_MAX parameters. That controller will try to meet both the airspeed and altitude demands of the mission, but if it can't reach the target speed it will happily fly a bit slower, as long as it doesn't get below ARSPD_FBW_MIN. You can control the relative priorities of speed versus height using the TECS_SPDWEIGHT parameter. See the full tuning guide for details.

New ACRO flight mode

After a suggestion from Thomas in the 2.73 release thread, we have added a new ACRO flight mode.

This modes brings rate controlled stabilization to APM:Plane, and should help give you an "on rails" manual flight experience. It is a lot of fun to fly, but it is not for beginners!

We're planning on expanding the ACRO mode in future releases. Right now it is great for "locked in" flying, and also good for loops and handles inverted flight very nicely. It doesn't yet handle knife-edge or prop-hanging.

New CRUISE flight mode

After a suggestion from Hein, we now have a new CRUISE flight mode. This mode is ideal for longer distance flying without a pre-programmed mission. It is like FBWB, but also does ground track heading hold, with heading update via aileron or rudder.

I've been testing CRUISE at my local flying field, and it is the easiest mode to fly in APM. Just steer the plane around the sky, and when you stop steering it locks onto a ground track and holds it. It isn't a good mode for takeoff and landing, but once you are in the air it is great.

New camera trigger system

When using APM for aerial mapping where you want photos taken at regular distances, the previous system was to setup a grid mission with a "camera trigger" mission item at regular intervals within the mission. That worked, but led to overly large and complex missions. You can now just set a single parameter CAM_TRIGG_DIST to the number of meters of flight between photos, and the APM will take care of when to trigger the camera. This makes for much simpler missions, and also works in other flight modes, including FBWB and CRUISE.

Lots of smaller changes

As is usual with a new release after a couple of months of development there were a lot of smaller improvements based on feedback from users. Many thanks to everyone who gave feedback and contributed patches!

Here is a partial list of the changes:

  • added new GND_ALT_OFFSET parameter for ground station barometric correction
  • made it possible to set the failsafe battery voltage and battery level at runtime via parameters
  • added MIXING_GAIN parameter for controlling the elevon and v-tail mixers
  • fixed stick mixing range in AUTO modes  (thanks Soren!)
  • fixed mode logging in dataflash
  • added support for the EagleTree I2C airspeed sensor on PX4
  • added new RCMAP_* parameters for re-mapping control channels (good for DSM and SBUS receivers on PX4)
  • made it possible to configure board orientation at runtime, to make setup easier without rebooting
  • switched to new task scheduler for more accurate internal timing
  • added a new RELAY_PIN parameter for setting up camera trigger via a digital pin
  • added secondary rudder support, useful for when a separate servo is used for a nosewheel and the rudder, or for v-tail planes with nosewheels
  • fixed RTL glide slope when starting above the target RTL altitude. Descent should now be smooth over long distances. Many thanks to Kitsen13 for raising this.
  • fixed a bug with FBWB airspeed control. Many thanks to Gabor for reporting this
  • Added FS_LONG_TIMEOUT and FS_SHORT_TIMEOUT parameters. Many thanks for the suggestion by Aleck
  • fixed handling of deadzone parameters on RC channels. Many thanks to Soren for reporting this
  • many small C++ fixes from NeuroCopter. This sort of detailed review of our code is much appreciated!
  • fixed analog in handling with some unusual devices - thanks to Andi for noticing this!
  • added support for apparent versus true airspeed calculations based on pressure altitude, for better flight control at higher altitudes
  • avoid writing unchanged bytes to EEPROM, for faster updates and less wear on the chip
  • cope better with large yaw changes in the AHRS code
  • improved the reliability of USB connections on PX4
  • added PX4 support for RELAY (thanks to Marco Bauer)
  • fixed handling of high spin rates in AHRS (thanks Jurgen!)
  • removed support for the old APM1 1280 based boards.

This new release has a lot of new features that should improve the flying experience for all APM users. The APM dev teams wishes all APM users many enjoyable flights, and we hope you have as much fun flying this release as we had making it.

Happy flying!

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

Join diydrones

Email me when people reply –

Replies

  • APM2.5, ArduPlane 2.74, external power non 3DR.

    When I connect to Terminal menu in Mission Planner for Arduplane, I get the windows below.

    Is that safe to fly like this?

    All looks OK in Flight Data/Flighy Plane/etc and plane responds correct to all controls/GPS/Baro, modes, etc. I did all calibration 2 times and install 2.74 firmware 2 times also. Same issue.

    If I reset APM2.5 by reset button and connect again, then I see correct the ArduPlane prompter with menus (test/setup/logs, ect).

    I remember I did have the same windows with garbage chars when I did crash my plane 2 weeks ago. Not sure it was related to this.

    When I use ArduCopter (with another APM2.5) in same Mission Planner, I never did see this garbage in Terminal window.

    I am planning to fly tomorrow, please I need your input, I don't want another crash if this garbage is not normal.

    Thanks, Chris

    3692831537?profile=original

  • I posted some questions about the APM behavior here:

    http://diydrones.com/forum/topics/strange-happenings-on-waypoint-mi...

    I'm hoping somebody can take a look and advise. I have an important mapping flight scheduled for tomorrow and I want to make sure I'm ready. So far, no one has replied on my post.

    As a teaser, you get to see a video of what happens when the airspeed sensor is reset to zero during an Auto mission. The TECS did quite well, but was clearly working overtime to make sense of the input change.

    Tridge? Paul? Anyone?

     

  • Hi!! i have a question about setting a waypoint in to a "landing point"

    I have a nitro Nextar .46 and APM2.5 with internal compass+speed sensor. I've callibrated all the sensors, radio, etc. auto mission, rtl, circle, fbw a + b, all works great. 

    Last week i try auto landing, i started setting some waypoints at low altitude at the landing area ( works perfectly nice ). Then in the 3th try i put the las point "LAND". 

    The airplane comes great leavel, and drecreasing altitude, then it arrive at landing point at ~ 5 meters from the floor, then it make a 45 degree turn and then land, at this point i switch my radio selector between auto to manual but it was locked, i have no control until it lands ( perfect landing but not in the area i spected). The question is : When it arrives to landing point you can not switch between ato to manual or stab mode ???.

    THKS

    Sergio Oropeza from Queretaro, Mexico.

  • Hiya..  Loving 2.74b and flying my X8, but I'm having an interesting issue that I was hoping someone could comment on.  At times, it appears my plane, according to telemetry, is flying sideways or backwards, or occasionally in FBWA the telemetry will show the direction-to-waypoint arrow is in a random direction, no where near where the direction to ANY of the waypoints are.  I don't know if this is related, but in the OSD I see direction-to-home as being wrong "most of the time" while distance seems to be fine.

    The reason I'm mentioning this is because on the Initial-Setup screen under Compass, I regularly have to reenable my Compass and tell it to use the On Board APM compass.  It is an APM2.5.  I just bought a new GPS with built-in Mag, so I plug in its mag and say "External Compass" but later when I reconnect to MP, everything is unchecked again.  The last time I made a chance, I set it back to use On Board APM compass, because I tried re-seating the I2C cable and the block actually came off the board (RMA number received from 3dr, so that's cool, I'll get that fixed.)

    My questions are:

    -Is this an MP bug wherein the compass settings just aren't getting loaded properly, or is the compass setting actually getting disabled and that's why the telemetry data looks so weird?

    -Can I expect the external compass with the 3dr uBlox gps antenna to work with the APM2.5 (this should be yes, correct?)

    -Is the telemetry data supposed to be accurate as far as direction of flight, or is that issue related to the weirdness i'm seeing with the compass problem?

    -Is the OSD direction-to-home issue related to all of this or is that strictly an OSD issue that I can work with Gabor on?

    Sorry, I know it's a lot of questions, appreciate any and all input you may have..

    I've attached my param file as well, because last time I made the change directly to that rather than using the Initial-Setup screen and at least the enablement of the compass seems to have stuck.  To summarize that param file, both COMPASS_USE and MAG_ENABLE are set to 1.  I thought there was a param stored that remembered the type of compass used, but I can't seem to find it..

    Josh

    Compass.jpg

    X8_2.74b_10-Sept-2013.param

  • Hi all,

    does anyone know when the next release will be available ?

    We will have something new related with photomapping?

    Thank you,

    Alex

  • I've noticed that there's a ground altitude creep problem. Today I had an hour long flight/tuning session. During that time the home altitude changed by about 50 meters. So in the end the plane was actually flying at 50 AGL when it was supposed to be flying at 100 m AGL. So when I landed the plane MP showed it was at about 50 m elevation.

    In the end the plane also made high speed pass 20-30 meters from the ground during loiter. Then I knew it was time to land. That's not fun at all.

    After a reboot the ground alt was back to zero again. Is this kind of altitude creep normal and can I do anything to avoid it in the future?

  • Why is the WP Radius limited to 127ft?
  • Hiho!

    I am just building my orig APM 2.0 + Radian Pro setup. I did a lot of quadrocopterstuff in the past with that APM but planes are completely new to me so please forgive me my stupid questions but I was not able to find answers to that.

    1.: I mounted the APM in the canopy. But when attaching the lipo/power the canopy will be open and I will need some time to close it. Will the Gyrocalibration stop while I am fiddeling or will it produce unusable results, wich must lead to crash/unflyable result? Must I drill a hole to access the reset button or attach a switch to powerup APM seperately? Is there a timervariable I could set like: initialize gyros and fc after x seconds after powerup?

    2.: I will be facing some magnetometer issues for sure due to proximity to the motor (canopy already magnets removed). I think the gps groundcourse will be much more usable/important in planes and correct/override the mag to some extend??

    I will not be able to do a compassmot because a fixed radian pro with motor at full throttle will rip the nose off (seen video on YT). Maybe I can reverse the foldingprop - I will see in the further progress of my build.

    3.: Flaps. The guide here: http://plane.ardupilot.com/wiki/arduplane-setup/connecting-your-rc-... shows that I am not supposed to attach flaps. On the other hand here: http://plane.ardupilot.com/wiki/automatic-flaps/

    it says "To use flaps they must be configured on channel 5, 6, 7 or 8. If you wish to have manual control of the flaps then they must be on 5, 6, or 7" I think they are referring to the "Output line" of the apm? Or the channels in my RC? It is not so clear to me right now. Maybe showing the solderpoints in the main connection graphic for flaps would make it easier.

    What I've done so far:

    - Attached APM powermodule / also powers minimosd and frsky rx

    - Extra 2A UBEC to power the servos exclusively (just servo datalines connected to apm)

    - E-flite ESC just powers main motor, Bec is not used for anything else (from googling around I saw some radians pro biting the grass on the first flight without taking rc input anymore - I think the esc 5V was overstressed and tilted)

    So far my Plane newbie shit! Any comments or biting comments hints and tips welcome.

    Cheers Kraut Rob.

    • Take off your prop for saftey

  • I have RST_MISSION_CH set to channel 9 but it doesn't seem to be working. How can I see the output of the channels above 9? I only see channels 1-8 listed anywhere in MP.
This reply was deleted.

Activity

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