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

  • Can someone tell me what is wrong with this flight plan? Why won't the DO_JUMP work to create an endless loop? It just goes to RTL after the last waypoint. I tried with the dummy waypoint both before and after the DO_JUMP command.

    3692816534?profile=original

  • I'm having trouble setting up a rudder-elevator only plane. I have set KFF_RDDRMIX to 1. When I switch to FBWA the rudder deflects to one side. This does not happen in stabilize mode.

    I have tried erasing the eeprom and done levelling and radio calibration multiple times. Nothing has helped. The rudder will always offset to one side when KFF_RDDRMIX is anything but zero. CH4 out is somewhere around 1800 ms.

    This issue has stopped me from even trying to tune the pid controllers. Any advice would be appriciated.

  • Hi all,

    I try to come up with a smooth waypoint flight but for a couple
    of days I can't make any progress.

    My original problem posted here
    http://diydrones.com/forum/topics/deviation-from-waypoint-track
    still exists. Later I reduced to only 4 waypoints at the corners but
    cycle three times the rectangle.

    I run 2.74b and an EasyStar like plane without ailerons. The
    aileron APM port is connected to rudder. I don't have an airspeed
    sensor and no telemetry on board.

    Today a beautiful day without any wind. I followed all of this thread
    and made the FBW-A tuning first. It looked fine as far as to what I
    understand it should look like.

    Switching over to AUTO will not fly something similar to a rectangle.
    It is overshooting the direct trail between waypoints very much. So
    I'm not really sure if I still have problems within the tuning or
    with waypoint handling.

    I don't want to waste your time but if someone is willing to
    look at the log and give some hints it would be great.

    thanks
    Wolfgang R.

    2013-08-29 09-31 1.log

  • I am having trouble with my RC RSSI in my new build. I have 2 other APM aircraft with no trouble but with the older firmware. I have tried several A pins and I always get an RSSI of about 180-190 displayed on the HUD (User items: rssi). When I turn of my DragonLink Tx it does not change. I tested the RSSI pin on the DL Rx and it reads 2.75v max, and .89v when the Tx is off. Right now I have RSSI_PIN set to 9, but it doesn't change the reading even if I disconnect it, so it must not be reading anything. I tried a different Rx and it's no different. Did this get broken in the newest firmware?
    Any ideas?
  • Non airspeed sensor airplane – how do I make it fly faster?

    In Loiter and Auto mission it flies between 50 and 54% throttle. I tried changing the cruise airspeed and cruise throttle but it makes no difference? What are the controlling parameters that I need to change?

    I even tried a higher pitch prop but the cruise speed was the same and the throttle % went down so that it wouldn’t go any faster. This really has me confused. I would like to cruise a little faster with a target throttle of 60-65%. How can I make this happen?

     

    .

     

  • Does anyone have a Skywalker parameter file with the new TECS controller settings that I can use as a starting point?
    I'm about to maiden a new 2013 Skywalker 1880.
    Thank you.
  • Moderator

    I had a flight on Saturday where I tested RTL towards the end of an AUTO mission (just a box I use to evaluate tuning). After successfully navigating home and circling home once I exited RTL mode and changed to FBW-A. Then the plane continued on it' merry way not wanting to respond to my commanded aileron inputs. It seemed at some points as though it was responding with a very flat rudder only turn, but no aileron. I then switched to STABILIZE and regained full control and landed. I'm not sure if I missed something on the proper way to exit RTL or if this is a bug in the control logic. When I look at the tlog during the RTL and FBW-A phase, I don't see any input on CH1 though I was definitely applying aileron. Once I switched to STABILIZE everything looks OK. Just to be sure I went back to another tlog where I was flying around in FBW-A and looked to see what the aileron CH1 input looks like and all is normal.

    The tlog 2013-08-17 15-58-07 shows RTL beginning at about 89%

    The tlog 2013-07-31 16-43-44 is for reference and shows normal FBW-A at 22.9% behavior without an RTL preceding it.

    In both examples I am using 2.74 and have mixed in rudder with aileron.

    Regards,

    Nathaniel ~KD2DEY

    2013-08-17 15-58-07.tlog

    2013-07-31 16-43-44.tlog

  • Is there a way to set up differential ailerons in a elevon configuration using the APM elevon mixer?

    I see in the Wiki directions for setting up differential ailerons using discrete aileron servos but I don't see anything when using elevons and the APM mixer.

    Thanks

  • I'm sorry for not too firmware specific question. I have a little flying wing, and I can't place APM 2.5 on center of plane. Can I place off axis (max 2-3 inch) the Ardupilot controller? Anyone try it?

    Thanks for help!

    Istvan from Hungary

  • Hello all,

    I have a problem with my APM2 with the calibration of accelerometers use the M.P. 1.2.67, and when I do the calibration, as wiki procedures, it gives me the following error "Calibration Failed", I run both in MP mode in the CLI. The gyroscopes and accelerators work as test CLI.

    APM2 fw 2.74b

    MP 1.2.67

    Regards, Fabio

    3692797344?profile=original

This reply was deleted.

Activity

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