Three alternative approaches to better loop control

What's wrong with those ramps? Well, as the performance of control loops declines over time, there are better alternatives to properly handle potential problems. Check out what to avoid when tuning your ramps.

Share Print Related RSS
Page 1 of 2 « Prev 1 | 2 View on one page
By Martin Emond, TopControl Inc.

IN TODAY'S controllers, ramping block devices are widespread in most DCSes and PLCs as a built in feature. This consists of either ramping the setpoint from one operating point to another production rate, or limiting the rate of change of the controller output through a ramp. Most of the time, when people intend to use a ramp device, they attempt to: 

 

  1. Avoid overshooting during a setpoint change
  2. Respect equipment constraints such as electrical (over-current), thermal or mechanical stress or
  3. Make the transition from one operating point to another smoother.

For any of these three approaches, there is a better alternative to properly handle those potential problems. 

Avoiding Overshooting During a Setpoint Change
Wherever the ramp is located – either at the controller output or at the setpoint – there will certainly be an overshoot for a non-self-regulating process and a high potential of overshoot for a self-regulating process (higher potential for Lag dominant process model) according to the tuning’s aggressiveness (See Figure 1 below). This is what we see by looking at G2(s), G3(s) and G5(s): all of them are overshot. On the other hand, G1(s), which was step changed through a Lead/Lag filter, not only is overshot, but it reached the new setpoint faster with exactly the same tuning. Consequently, the ramp will postpone the setpoint response and make it overshot. Thus, the first statement that leads people to use ramp, happens to be unjustified for both self-regulating and non-self-regulating process types.

FIGURE 1: CONTROLLING ERROR

Performances based on a simulation for a self-regulating and non-self-regulating process model. A ramped SP versus a step changed SP going through a Lead/Lag filter has been applied.



WHAT IS THIS
Lead/Lag filter? This function is often available as a built-in device in most DCSes and PLCs on the market. It consists of a ratio between 0 and 1 of two time constants. One of them is the numerator and acts as the leader. The leader corresponds to the instantaneous portion of the step change applied to the controller. For instance, if the ratio is 0.7 then 70% of the step is instant or abrupt change and the other 30% is going through a first order filter, which is also called Lag.

The denominator is the lag, which is actually the time constant of a first order filter. Generally, this filter time constant will match the tuning value of the integral action in the controller. This type of mechanism will give you the best of the two worlds: no overshoot during setpoint change and fast load rejection.

Because of this Lead/Lag filter, tuning can be optimized for load disturbances without having any overshoot at all during a setpoint change. Furthermore, the load rejection will remain the fastest it can get during a load disturbance. Without a Lead/Lag filter, most people’s natural tendency is to relax the tuning to avoid overshooting too much on a set point change, or to use a ramp and get an overshoot of different magnitude depending on the tuning’s aggressiveness.

When using a Lead/Lag filter, the excitation signal sent to the PID controller has a sharp break at the beginning, then the rest of the pattern is very smooth. In fact, it has the same shape as a first order response. When using the ramp pattern, there are two abrupt changes: there is one at the beginning and a second one at the end when it reaches the new setpoint. The idea of a Lead/Lag function is to make a steep change at the beginning, when it is far away from the final value, then reduce the speed for the final approach. A two-degree of freedom PID controller (Integral only on SP change) will produce similar results.

The settling time can be improved by a factor of two without overshoot when using a Lead/Lag filter. Settling time is defined as the time that has passed for both the Process Value and Controller Output to reach steady state and remain within the range of a normal process noise.

The settling time is cut by a factor of two when using a Lead/Lag filter, as opposed to using a ramp applied on the set point or using a ramp limiter applied at the controller output where this latter acts as a slew rate limiter.

In addition to lengthening the settling time by 100%, the ramp caused (in this example) an overshoot of 10%. If the aggressiveness of the tuning and the slope of the ramp are reduced to lessen the overshoot as much as possible to the minimum, then the settling time could be increased by a factor as high as four, which is a considerable amount. Consequently, with a ramp, the reduction of the overshoot during a set point change implies a significant increase of the settling time. On the opposite, the Lead/Lag filter does not create overshoot for both types of process, that is to say self-regulating and non-self-regulating.

Respecting Equipment Constraints
For the second solution, which is intended to protect the equipment from being stressed, over-used or broken, there is a more appropriate approach to solve this issue than using a ramp limiter at the PID output. For instance, if the cause of the stress is brought about by a high heat flow rate phenomenon, then another controller could be acting as an override or constraint controller on the temperature differential between the two surfaces or two points. A constraint controller will override the valve through a low-select signal block. Since the stress from the heat is proportional to the heat flow, which is a consequence of the temperature differential between the two points, this constraint controller will take over by just the appropriate amount of output correction and avoid causing stress.

Page 1 of 2 « Prev 1 | 2 View on one page
Share Print Reprints Permissions

What are your comments?

Join the discussion today. Login Here.

Comments

No one has commented on this page yet.

RSS feed for comments on this page | RSS feed for all comments