# Difference between revisions of "Control Loops"

This page presents the default control loops used by the Paparazzi airborne code for navigation, guidance and control.

# General Information

All the possible combinations of control loops might not be fully detailed. This is especially the case when using extra features such as AGR_CLIMB, STRONG_WIND, etc.

In the following diagrams, the block s is used for the derivative function and 1/s is used for the integrator function.

The variables' names are the ones used in the airborne code (written in C). Most of these can be used, all caps, in the Airframe Configuration file in order to define the default values of these variables. If you see all capital letters in the diagrams, the value is fixed and cannot be changed using Settings mechanism.

The most direct way to determine vehicle behavior is to look at the source code. When determining which control loops are engaged by various flight plan blocks and stages, it may be helpful to look at sw/airborne/subsystems/nav.h and the generated flightplan file in var/<AIRCRAFT_NAME>/<TARGET>/generated/flight_plan.h.

# Fixed-wing autopilot

## Global view

The elements servos, rc_commands, commands and command_laws correspond to specific section of the Airframe Configuration file. Most of the code located in these blocks is generated from the xml of the configuration file.

The value +/-9600 correspond to +/-MAX_PPRZ. This pprz unit is used as a normalized internal unit for input and output values of the control_laws block.

## Course loop

The course loop is the upper stage of the horizontal control. It is located in sw/airborne/firmwares/fixedwing/stabilization/stabilization_attitude.c (formerly fw_h_ctl.c).

## Roll loop

The roll loop is the lower stage of the horizontal control and is used for lateral attitude stabilization. It is located in stabilization_attitude.c. If H_CTL_ROLL_ATTITUDE_GAIN is undefined, the code will fallback to a attitude-only loop, where estimator_p is disregarded and the gain for estimator_phi is H_CTL_ROLL_PGAIN.

Note; estimator_phi is the measured roll angle, and estimator_p is the measured rate of change in roll angle.

## Altitude loop

The altitude loop is the upper stage of the vertical control. It is located in sw/airborne/firmwares/fixedwing/guidance/guidance_v.c (formerly fw_v_ctl.c) If AGR_CLIMB is defined in the airframe file, the altitude loop also sets the v_ctl_auto_throttle_submode for use in the climb loop.

## Auto Throttle and Auto Pitch climb loops

Two climb loops are available. The are called from the flight plan by changing the vertical navigation mode. The default mode is Auto Throttle. The Auto Pitch loop is only available if V_CTL_AUTO_PITCH_PGAIN is defined. Only one loop is active at a time. Note also that if USE_AIRSPEED is defined, then the Auto Throttle loop is replaced by the Auto Airspeed loop, see below.

### Auto throttle loop

If AGR_CLIMB is defined, then the auto throttle submode is used to determine setpoint outputs. This may be the standard control loop outputs, the aggressive outputs (static setpoints defined in airframe file) or a blend of both.

### Auto pitch loop

The climb loop is the intermediate stage of the vertical control. It is located in guidance_v.c.

## Pitch loop

The pitch loop is the lower stage of the vertical control and is used for longitudinal attitude stabilization. It is located in stabilization_attitude.c. The first sum block of the diagram is not completely accurate. The input to the pitch stabilization loop is h_ctl_pitch_setpoint, though v_ctl_pitch_of_vz is not a direct input. Rather h_ctl_pitch_setpoint is assigned in the main autopilot loop from nav_pitch, in general (in auto1, it is assigned directly from the pitch r/c input). The nav_pitch value is obtained in a few ways, depending on which control loop(s) are active. If auto throttle is active, nav_pitch is the sum of v_ctl_pitch_of_vz and a fixed setpoint defined using the pitch attribute in the flightplan. If AGR_CLIMB is set, nav_pitch is either the airframe file defined ascent and descent pitch setpoints, the standard sum, or a blend of each. If auto pitch is active, nav_pitch is defined directly from the output of that loop. If airspeed is active, nav_pitch is defined in the auto airspeed pitch loop.

## Control loops using Airspeed Sensor

Adding an airspeed sensor measures actual airspeed resulting in better throttle control and aircraft performance especially in windy conditions. The use of an airspeed sensor is described here.

The auto airspeed cascaded control loops control both pitch and throttle. This control loop set replaces the Auto Throttle climb loop; it is engaged in the same manner in the flight plan. It is located in guidance_v.c.

## Energy Control loops using Airspeed Sensor

Total Energy (speed + height) control for fixed wing vehicles developed by the MAVLab of the Technical University of Delft. An airspeed sensor is mandatory. The energy control loops control both pitch and throttle. This control loop set replaces the Auto Throttle climb loop and is located in energy_ctrl.c.

# Rotorcraft autopilot

The schemes of the multi-rotor autopilot were made with the drawing tool from Google docs. To edit the drawings, send an e-mail to microuav@gmail.com.

## Overview

The code for this autopilot is located in sw/airborne/firmwares/rotorcraft.

Since v5.0, the Supervision was replaced by Motor mixing. Alternatively, the stabilization commands can also be directly used in the servo command laws.

## Vertical Control

Depending on the general mode selected, one of the following vertical modes is used.

## Reference generators

z relates to altitude, zd to speed and zdd to acceleration

### from z dot set point (desired speed)

]

The adjust accel is a simple algorithm to set acceleration to zero when velocity reaches boundaries.

The code for these reference generators is located in guidance/guidance_v_ref.c

## Vertical loop

the source code is located in guidance\guidance_v.c

NOMINAL_HOVER_THROTTLE is the nominal thrust when hovering. It's calculated by default by an adaptative controller, in guidance\guidance_v_adpt.h.

Instead of the adaptative controller, NOMINAL_HOVER_TROTTLE can be set manually in the Airframe configuration file with:

<define name="NOMINAL_HOVER_THROTTLE" value="0.5"/>

The value is found after flying manually in hover: NOMINAL_HOVER_THROTTLE= THRUST/MAX_PPRZ (THRUST:mean value of ROTORCRAFT_FP THRUST message in hover, MAX_PPRZ:9600)

In most cases it makes more sense to not specify this explicitly and use the adaptive controller

## Horizontal Control

Depending on the general mode selected, one of the following horizontal modes is used.

### mode: GUIDANCE_H_MODE_HOVER

When this mode is entered, the measured position at the instance of initiation is set as guidance_h_pos_sp. This means that the rotorcraft will hover on that position.

rotation to body:

$\phi_{cmd_{body}}= -\sin \psi \cdot x_{cmd_{earth}} + \cos \psi \cdot y_{cmd_{earth}}$

$\theta_{cmd_{body}}= -\left( \cos \psi \cdot x_{cmd_{earth}} + \sin \psi \cdot y_{cmd_{earth}} \right)$

### mode: GUIDANCE_H_MODE_NAV

The set points guidance_h_pos_sp (x and y coordinates) are obtained from the navigation carrot after a 'NED of ENU' transformation:

Rotation to body is the same as in GUIDANCE_H_MODE_HOVER.

## Reference generators

### from euler attitude angle set point

Acceleration is set to zero when rate reaches min or max value.

The code for this reference generator is located in stabilization/stabilization_attitude_ref_euler_int.c.

### from angular rate set point

The code for this reference generator is located in stabilization/stabilization_rate.c.

### from pos set point

Acceleration is set to zero when rate reaches min or max value.

The code for this reference generator is located in guidance/guidance_h_ref.h.

## Attitude loop

The code for this loop is located in stabilization/stabilization_attitude_euler_int.c.

## Rate loop

The code for this loop is located in stabilization/stabilization_rate.c.

## Guidance horizontal hover loop

The code for this loop is located in guidance/guidance_h.c.

In v 5.14 (and probably even earlier), the integral action is implemented differently: the output of the PD controller is integrated, and the integral value thus represents the attitude trim.