Noise and disturbances in process control
W ere it not for noise and disturbances, a feedback controller could fairly easily maintain output of the controlled process (process variable) close to its desired value (setpoint). However, forces other than the controller's efforts can often change the process variable. An example is sun shining in on a room cooled by an automatic air conditioner. In spite of the thermostat's efforts to lower the room temperature to a 72°F setpoint, the room may actually get hotter. These uncontrollable influences are known as disturbances.
Noise, on the other hand, makes the process variable appear to deviate from the setpoint whether any real disturbance is at work or not. Noise is generally a result of the technology used to sense or measure the process variable. With electrical signals, measurement noise is often due to interference from other electrical sources. Noise can also be caused by wear and tear on the sensor or some physical obstruction that causes the sensor to send an inaccurate reading to the controller.
Errors between the setpoint and the process variable also occur when the setpoint changes. However, setpoint changes are relatively easy for a controller to implement if it's programmed with enough data about the dynamic behavior of the process. It is the random nature of disturbances and the fictitious effects of noise that make feedback controllers work so hard.
An everyday example
Consider a large truck being driven down the highway through a crosswind. The driver's brain is the controller and his eyes are the sensors that measure the truck's position. Based on what he sees, the driver uses his steering wheel to maintain the truck's lateral position between the white lines.
If the wind is light and visibility is good, the driver need only concern himself with updates to the truck's desired position necessitated by the curves in the road. Such setpoint changes are relatively easy for him to make, assuming he knows how the truck will react when he turns the steering wheel.
However, a strong wind can blow the truck off the course the driver has chosen to follow. To compensate for such disturbances, the driver must adjust his steering to correct his position errors. Worse still, if the wind's speed or direction changes at random, the driver's corrective efforts will have to be more frequent and more dramatic.
Now suppose the wind is accompanied by snow. The driver may not be able to see the white lines very well, so he may end up changing his course to compensate for a nonexistent position error. Snow constitutes a visual 'noise' that corrupts the position measurements taken by the driver's eyes.
In a more typical process control situation, a PID controller is responsible for applying a corrective effort in proportion to the error between the process variable and the setpoint plus the integral and derivative of that difference. It is the derivative action that is most affected by noise and disturbances.
On the plus side, a PID controller tuned to provide aggressive derivative action can react quickly to an error and start the control effort moving in the right direction immediately after a disturbance begins. This can shorten the time required to compensate for a disturbance compared to a controller that uses only proportional and integral action.
However, the derivative action will amplify any noise embedded in the measurement, since the derivative of a fluctuating signal also fluctuates. This can lead to unnecessary and potentially counter-productive control efforts. Most PID controllers are equipped with noise filters to suppress extraneous fluctuations that the derivative action would otherwise generate.
|Search the online Automation Integrator Guide|
Case Study Database
Get more exposure for your case study by uploading it to the Control Engineering 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.