Terrain Following

Copter 3.4 (and higher) support “terrain following” in AUTO, Guided, RTL and Land flight modes. This feature allows the vehicle to climb or descend to maintain a specified distance above the terrain using either a downward facing Lidar or Sonar or from terrain altitude data provided by the ground station using a mapping service such as Google maps. Details of how the Google maps data is used can be found on the plane terrain following page

Setting up a Mission to use Terrain data

  • If relying on a downward facing LIDAR ensure it is setup as described here

  • If using GCS provided terrain data set the TERRAIN_ENABLE parameter to 1

  • Using a recent version of Mission Planner (or other GCS that supports terrain following) on the Flight Plan screen, set the altitude type to “Terrain”. Once set all mission commands that include an “Alt” fields will be interpreted as altitudes-above-terrain.

  • Upload the mission to the vehicle and execute the mission as you normally would in AUTO

    ../_images/terrain_mission.png

Using Terrain Altitude during RTL and Land

Set the TERRAIN_FOLLOW parameter to 1 to enable using terrain data in RTL and Land flight modes. If set the vehicle will interpret the RTL_ALT as an altitude-above-terrain meaning it will generally climb over hills on it’s return path to home. Similarly Land will slow to the LAND_SPEED (normally 50cm/s) when it is 10m above the terrain (instead of 10m above home). Currently setting this parameter is not recommended because of the edge case mentioned below involving the somewhat unlikely situation in which the vehicle is unable to retrieve terrain data during the RTL. In these cases the RTL_ALT will be interpreted as an alt-above home.

Failsafe in case of no Terrain data

If the vehicle is executing a mission command that requires terrain data but it is unable to retrieve terrain data for two seconds (normally because the range finder fails, goes out of range or the Ground Station is unable to provide terrain data) the vehicle will switch to RTL mode (if it is flying) or disarm (if it is landed).

Note that because it does not immediately have access to terrain data in this situation it will perform a normal RTL interpreting the RTL_ALT as an altitude-above-home regardless of whether TERRAIN_FOLLOW has been set to “1” or not.

One common problem reported by users is the vehicle immediately disarms when the user switches to AUTO mode to start a mission while the vehicle is on the ground. The cause is the altitude reported by the range finder (which can be checked from the MP’s Flight Data screen’s Status tab’s sonar_range field) is shorter than the RNGFND_MIN_CM parameter which means the range finder reports “unhealthy” when on the ground. The solution is to reduce the RNGFND_MIN_CM value (to perhaps “5”).

Terrain Spacing and Accuracy

The TERRAIN_SPACING parameter controls the size of the grid used when requesting terrain altitude from the Ground Station (it is not used if using a Lidar). This is 100m by default but reducing to 30 may provide better accuracy at the expense of more telemetry traffic between the GCS and Flight controller. It is recommended that you use a TERRAIN_SPACING of at least 30 meters.

If the ground station does not have terrain data available at the resolution requested by the aircraft then the ground station will interpolate as necessary to provide the requested grid size.

Terrain Accuracy

The accuracy of the SRTM database varies over the surface of the earth. Typical accuracy is around 10 to 20 meters, but some developers have noticed inaccuracies of 35m. This makes terrain following suitable for aircraft that are flying at altitudes of 60 meters or more. For very accurate terrain following at lower altitudes it is recommended to use a downward facing Lidar or Sonar.

Example mission at 2m using Lidar