Difference between Open-loop and closed-loop control

Automatic control operations can be described as either open-loop or closed-loop. The difference is feedback.

Arguably the most ingenious tool of the control engineering profession is the feedback loop shown in the Basic Feedback Loop graphic. It consists of five fundamental elements:
The process that is to be controlled
An instrument with a sensor that measures the condition of the process
A transmitter that converts the measurement into an electronic signal
A controller that reads the transmitter's signal and decides whether or not the current condition of the process is acceptable, and
An actuator functioning as the final control element that applies a corrective effort to the process per the controller's instructions.

In a closed-loop control system, information flows around a feedback loop from the process to the sensor to the transmitter to the controller to the actuator and back to the process. This measure-decide-actuate sequence-known as closed-loop control-repeats as often as necessary until the desired process condition is achieved. Familiar examples include using a thermostat controlling a furnace to maintain the temperature in a room or cruise control to maintain the speed of a car.

But not all automatic control operations require feedback. A much larger class of control commands can be executed in an open-loop configuration without confirmation or further adjustment. Open-loop control is sufficient for predictable operations such as opening a door, starting a motor, or turning off a pump.

Continuous closed-loop control

Continuing the analysis, it is clear that all closed-loop operations are not alike. For a continuous process, a feedback loop attempts to maintain a process variable (or controlled variable) at a desired value known as the setpoint. The controller subtracts the latest measurement of the process variable from the setpoint to generate an error signal. The magnitude and duration of the error signal then determines the value of the controller's output or manipulated variable which in turn dictates the corrective efforts applied by the actuator.

For example, a car equipped with a cruise control uses a speedometer to measure and maintain the car's speed. If the car is traveling too slowly, the controller instructs the accelerator to feed more fuel to the engine. If the car is traveling too quickly, the controller lets up on the accelerator. The car is the process, the speedometer is the sensor, and the accelerator is the actuator.

The car's speed is the process variable. Other common process variables include temperatures, pressures, flow rates, and tank levels. These are all quantities that can vary constantly and can be measured at any time. Common actuators for manipulating such conditions include heating elements, valves, and dampers.

Discrete closed-loop control

For a discrete process, the variable of interest is measured only when a triggering event occurs, and the measure-decide-actuate sequence is typically executed just once for each event. For example, the human controller driving the car uses her eyes to measure ambient light levels at the beginning of each trip. If she decides that it's too dark to see well, she turns on the car's lights. No further adjustment is required until the next triggering event such as the end of the trip.

Feedback loops for discrete processes are generally much simpler than continuous control loops since discrete processes do not involve as much inertia. The driver controlling the car gets instantaneous results after turning on the lights, whereas the cruise control sees much more gradual results as the car slowly speeds up or slows down.



Inertia tends to complicate the design of a continuous control loop since a continuous controller typically needs to make a series of decisions before the results of its earlier efforts are completely evident. It has to anticipate the cumulative effects of its recent corrective efforts and plan future efforts accordingly. Waiting to see how each one turns out before trying another simply takes too long.

Open-loop control

Open-loop controllers do not use feedback per se. They apply a single control effort when so commanded and assume that the desired results will be achieved. An open-loop controller may still measure the results of its commands: Did the door actually open? Did the motor actually start? Is the pump actually off? Generally, these actions are for safety considerations rather than as part of the control sequence.

Even closed-loop feedback controllers must operate in an open-loop mode on occasion. A sensor may fail to generate the feedback signal or an operator may take over the feedback operation in order to manipulate the controller's output manually.

Operator intervention is generally required when a feedback controller proves unable to maintain stable closed-loop control. For example, a particularly aggressive pressure controller may overcompensate for a drop in line pressure. If the controller then overcompensates for its overcompensation, the pressure may end up lower than before, then higher, then even lower, then even higher, etc. The simplest way to terminate such unstable oscillations is to break the loop and regain control manually.

There are also many applications where experienced operators can make manual corrections faster than a feedback controller can. Using their knowledge of the process' past behavior, operators can manipulate the process inputs now to achieve the desired output values later. A feedback controller, on the other hand, must wait until the effects of its latest efforts are measurable before it can decide on the next appropriate control action. Predictable processes with longtime constants or excessive dead time are particularly suited for open-loop manual control.

Open- and closed-loop control combined

The principal drawback of open-loop control is a loss of accuracy. Without feedback, there is no guarantee that the control efforts applied to the process will actually have the desired effect. If speed and accuracy are both required, open-loop and closed-loop control can be applied simultaneously using a feedforward strategy. A feedforward controller uses a mathematical model of the process to make its initial control moves like an experienced operator would. It then measures the results of its open-loop efforts and makes additional corrections as necessary like a traditional feedback controller.



Feedforward is particularly useful when sensors are available to measure an impending disturbance before it hits the process. If its future effects on the process can be accurately predicted with the process model, the controller can take preemptive actions to counteract the disturbance as it occurs.

For example, if a car equipped with cruise control and radar could see a hill coming, it could begin to accelerate even before it begins to slow down. The car may not end up at the desired speed as it climbs the hill, but even that error can eventually be eliminated by the cruise controller's normal feedback control algorithm. Without the advance notice provided by the radar, the cruise controller wouldn't know that acceleration is required until the car had already slowed below the desired speed halfway up the hill.

Open- and closed-loop control in parallel

Many automatic control systems use both open- and closed-loop control in parallel. Consider, for example, a brewery that ferments and bottles beer.

Brew kettles in a modern brewery rely on continuous closed-loop control to maintain prescribed temperatures and pressures while turning water and grain into fermentable mash.

A brewery's bottling line uses both discrete closed-loop control and open-loop control to fill and cap the individual bottles.

The conditions inside the brew kettles are maintained by closed-loop controllers using feedback loops that measure the temperature and pressure, then adjust steam flow into the kettle and flow pumps to compensate for out-of-spec conditions. Open-loop control is also required for one-time operations such as starting and stopping the mixer motors or opening and closing the steam lines to the heat exchangers.

Simultaneously, finished batches of beer are bottled using open-loop and discrete closed-loop control. A proximity sensor determines that a bottle is present before filling can begin, then a valve opens to fill each bottle until a level sensor determines that the bottle is full.

In general, continuous closed-loop control applications require at least a few ancillary open-loop control operations, whereas many open-loop control applications require no feedback loops at all.

Which is which?

The differences between continuous closed-loop control, discrete closed-loop control, and open-loop control can be subtle. Here are some snippets of pseudo-code to illustrate each:

Open-loop control

IF (time_for_action = TRUE) THEN
take_action(X)
END

Discrete closed-loop control

IF (time_for_action = TRUE) THEN
measure(Y)
IF (Y = specified_condition) THEN
take_action(X)
END
END

Continuous closed-loop control

WHILE (Y <> specified_condition)
take_action(X)
measure(Y)
wait(Z)
REPEAT

In the first two cases the time for action usually means that a particular step has been reached in the control sequence. At that point, an open-loop controller would simply execute action X and proceed to the next step in the program. A discrete closed-loop controller would first measure or observe some condition Y in the process to determine if action X needs to be executed or not. Once activated, a continuous closed-loop controller is always ready for action. It takes action X, measures condition Y, waits Z seconds, then repeats the loop unless Y had reached the specified condition. In the discrete case, the specified condition is usually a discrete event such as the completion of a prior task or a change in some go/no-go decision criteria. In the continuous case, the specified condition is usually met when the measured variable reaches a desired value.

Key concepts:
There are different types of control loops and the most critical characteristic that separates them is how they handle feedback.
The needs of an application should be the primary reason for choosing one type or another.
In some cases, human intervention may be more desirable than an automatic approach.

Source:

Vance VanDoren, PhD, PE, is a Control Engineering contributing content specialist. Reach him at controleng@msn.com.