# PID Tuning

*Pieter P*

#### Table of Contents *list*

## Manual tuning

In this first section, we'll develop an intuition of what each of the four parameters of our PID controller does by tuning them manually. Later we'll use the heuristic Ziegler─Nichols method to get good starting values for the tuning parameters.

### Proportional control

We start by setting

For example, if the target position is

The figure above shows the results of four experiments with different values for the
proportional gain

The blue line is the reference or target position,
the orange line is the actual position of the fader, and the green line is
the control signal sent to the motor.

We can make two main observations based on these experiments:

- If the proportional gain is too low ─ as is the case in the top graph ─ the controller results in very poor tracking and in a large steady-state error.
- If the proportional gain is too high ─ such as in the bottom two figures ─ the tracking and steady-state errors are smaller, but the system overshoots the setpoint significantly, with ringing after steep transients, and oscillations while tracking the ramp.

### Proportional-derivative control

In order to minimize the overshoot, the derivative gain

- By increasing the derivative gain, the amount of overshoot decreases in the second graph, and is almost completely gone in the third graph.
- Increasing the derivative gain even further in the fourth graph makes the controller more sluggish, it takes much more time to get close to the target position after a setpoint change.
- The higher the derivative gain, the higher the noise in the control signal, which is noticeable as buzzing and slight rattling of the fader. This is because the derivative of the position is inherently noisy due to the discrete and quantized nature of the position measurement and the high-pass characteristics of the derivative operator.

### Proportional-integral-derivative control

The addition of the derivative component in the previous section worked well to minimize the overshoot, but there is still some constant tracking error while following the ramp. This is addressed by the integral component: if the actual position is consistently below the target position, the integral will sum up those positive errors over time, which increases the control signal and reducing the tracking and steady-state errors.

- The higher the integral gain, the smaller the tracking error for the ramp reference, and the faster the fader catches up with the reference.
- If the integral gain is very large, the fader sometimes slightly overshoots the setpoint after steep transients ─ e.g. the rightmost step in the bottom graph. Despite this overshoot, the controller settles to zero steady-state error rather quickly.

### Derivative filtering

We'll now address the noisy derivative component by enabling the low-pass filter,
tuning the cut-off frequency

- A lower cut-off frequency results in fewer noise in the control signal, which reduces the buzzing and rattling of the fader.
- If the cut-off frequency is too low ─ as in the bottom figure ─ the filter introduces too much delay into the
loop,
which causes the derivative component to lag behind the actual velocity of the fader, reducing the effect of
, and resulting in higher overshoot.${K}_{d}$

### Proportional fine-tuning

All parameters influence each other, so manual tuning is an iterative process. Now that we have a good baseline controller, we can iteratively fine-tune the parameters until we're satisfied with the results.

### Derivative fine-tuning

### Integral fine-tuning

## Ziegler─Nichols

Manual tuning requires trial-and-error and some knowledge of how the system is affected by each parameter. An alternative is to use a heuristic formula to choose the gains, such as the Ziegler─Nichols method.

### Ultimate gain

First, the integral and derivative gains are set to zero and the proportional gain is increased until
the system starts oscillating with a constant amplitude, recording the value of

In this experiment, the ultimate gain was determined to be

### PID gains

These values of

The resulting controller was relatively aggressive and had quite a bit of overshoot,
so