# Evolving PID tuning rules

## A brief history, starting with the earliest PID controllers to the most recent developments. There is more continuity than you might expect.

Looking into the distant past of automation history, one can see the underlying concept of a PID controller exhibited in a nineteenth-century steam engine governor design, with the first real PID-type controller developed by Elmer Sperry in 1911. The first theoretical analysis of a PID controller was published by Nicolas Minorsky in 1922. His observations grew out of efforts to design automatic steering systems for the U.S. Navy. He realized that a helmsman controlled the ship based not only on the current error, but also on past error and current rate of change. Proportional control could provide stability against small disturbances, but it was insufficient for dealing with a steady disturbance, which required adding the integral term. Adding the derivative term further improved control. Currently, the basic principle is applied in many variations, but for our discussion we assume commonly used basic standard ISA PID controller in discrete form:

(1)

where

*OUT(k)* – Controller output

*K _{p}* – Controller proportional gain

*SP* - Controlled parameter setpoint

*PV* – Process value, controlled parameter measurement

*e(k)* – Control error, *e(k)=SP-PV*

*T _{i} *– Controller integral time (reset) in seconds

*T _{d}* – Controller derivative time (rate) in seconds

Tuning a control loop is the adjustment of its control parameters (proportional gain *K _{p}*, integral time/reset

*T*, derivative time/rate

_{i}*T*) to the optimum values for the desired control response. Stability (bounded oscillation) is a basic requirement, but beyond that, different systems have different behavior, different applications have different requirements, and requirements may conflict with one another. In the following sections we briefly review the basic tuning techniques, focusing on objectives of the tuning and how they were achieved.

_{d}**Model-free tuning**

Model-free tuning techniques don’t use a process model for PID controller tuning in a direct way. They are based on the observation of a process which is under control, and became among the first initially applied for controller tuning. The most well-known techniques from this group are manual tuning and Ziegler Nichols tuning. In manual tuning the tuned loop remains in automatic mode. At first integral and derivative actions are removed by setting *T _{i}* to infinity (or very high) and

*T*to zero. Then, controller proportional gain

_{d}*K*is increased until the loop oscillates with constant amplitude. After that, the proportional gain

_{p}*K*should be set to approximately half of that value for a quarter amplitude decay type response.

_{p}*T*is adjusted until any offset is corrected in sufficient time for the loop operation. It should be noted that too low a value for

_{i}*T*may cause instability. Finally,

_{i}*T*is increased until the loop is acceptably quick to reach its reference after a load disturbance, without excessive overshoot.

_{d}Ziegler Nichols tuning also requires setting proportional-only gain *K _{p}* high enough to achieve loop oscillations with constant amplitude, similar to the manual tuning method. The difference is that the period of the oscillation

*T*should be measured. Controller gain at the test is named the ultimate gain,

_{u}*K*. The controller parameters are defined then from the formulas with no need for further loop testing like in the manual tuning shown in Table 1.

_{u}

[Table 1: Ziegler-Nichols calculations of P, PI, and PID controller parameters for a standard-form PID.]

There were some obvious drawbacks to these techniques, at least initially. Getting the loop to cycle continuously was a time-consuming process, and there was a risk that the oscillations would grow beyond stability since there was no deterministic way to specify or limit the oscillation magnitude.

The approach became significantly more attractive after introducing relay-oscillation auto-tuning, as described in Figure 1. Relay-oscillation auto-tuning delivers loop oscillation with amplitude limited by the relay step size, shown in Figure 2.

[Figure 1. Relay Oscillation Tuning Diagram]

[Figure 2. Trend plots of relay output and process output during active tuning]

The Ziegler Nichols method identifies the ultimate gain and ultimate period, so controller settings may be determined. The original Ziegler-Nichols tuning rules were designed to provide a quarter amplitude damped response to a load disturbance. Once considered ideal, the underdamped and oscillatory nature of Ziegler-Nichols tuning has been criticized for destabilizing control loops, actually increasing variability instead of reducing it.

There were several options for modifying original Ziegler-Nichols tuning. One way was to calculate a complete first order plus dead time model from the oscillation test and use model based tuning rules. Another method was to reduce the aggressiveness of the original Ziegler-Nichols tuning rules, which tend to provide the most oscillatory response when dead time is small. Therefore, an improvement can be achieved by making controller gain smaller and integral time larger (i.e., integral gain smaller) for smaller dead times. Dead time, in addition to the ultimate gain and ultimate period, can be easily defined during relay oscillation test shown in Figure 2. An example of such nonlinear adjustment of tuning parameters is given in Advanced Control Foundation (see additional reading list).

## Case Study Database

Get more exposure for your case study by uploading it to the *Consulting-Specifying Engineer* case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.