Sensitivity Functions in Feedback Systems
AI-Generated Content
Sensitivity Functions in Feedback Systems
Understanding how a control system reacts to the inevitable imperfections of the real world is the core of robust design. Sensitivity functions provide the precise mathematical language for this analysis, quantifying how closed-loop performance is affected by internal parameter drifts and external disturbances. Mastering these functions is essential for moving beyond naive stability and achieving systems that perform reliably despite component aging, manufacturing tolerances, and unpredictable operating environments.
Defining Sensitivity and Complementary Sensitivity
At the heart of feedback analysis are two fundamental transfer functions derived from the standard unity-feedback block diagram. The first is the sensitivity function, denoted as . For a system with forward path transfer function and feedback path transfer function , the sensitivity function is defined as the transfer function from a reference input to the tracking error, or equivalently, how the output responds to a disturbance at the output. Its mathematical form is:
The second key function is the complementary sensitivity function, denoted as . It is called "complementary" for a reason that will soon become clear. This function represents the closed-loop transfer function from the reference input to the system output. Its definition is:
A simple but profound algebraic truth emerges from these definitions: for any frequency , they sum to unity.
This equation, , is not just a curiosity; it is an absolute constraint that governs all feedback design, forcing critical trade-offs between different performance objectives.
Interpreting Sensitivity: Robustness to Variations and Disturbances
The sensitivity function’s primary role is to measure robustness. Specifically, it quantifies how sensitive the closed-loop system's performance is to variations in the plant's internal parameters. Consider a plant whose true transfer function is . If a particular parameter (like a motor's inertia or a circuit's resistance) changes, becomes . The sensitivity function directly relates the relative change in the overall closed-loop transfer function to the relative change in the plant.
More intuitively, also dictates disturbance rejection. A disturbance signal entering at the plant output is attenuated by the factor . Therefore, to achieve good disturbance rejection—for example, maintaining a room's temperature despite an open window—the magnitude of must be small at the frequencies where the disturbances are significant. Typically, disturbances are low-frequency phenomena (like slow thermal changes or constant load forces), which leads to a fundamental design rule: Achieve low sensitivity () at low frequencies.
This is accomplished by ensuring the loop gain is large in magnitude at those low frequencies. Since when , a large loop gain directly translates to small sensitivity and excellent disturbance rejection.
Interpreting Complementary Sensitivity: Tracking and Noise Response
While tells the story of robustness and disturbance rejection, the complementary sensitivity function governs reference tracking and sensitivity to measurement noise. As the closed-loop transfer function, the ideal is 1 across all frequencies, which would mean the output perfectly follows the reference. In practice, we strive for at low frequencies for good tracking of slow commands.
However, also describes how sensor noise propagates to the system output. High-frequency noise, inherent in all physical sensors, is fed back through the controller. The transfer function from measurement noise to the output is precisely . Therefore, to prevent the controller from frantically reacting to meaningless noise, we require to be small at high frequencies. This is achieved by ensuring the loop gain is small (rolling off) at those high frequencies, since when .
The Fundamental Design Trade-off: The Constraint
The algebraic constraint manifests as a critical, inescapable trade-off in the frequency domain. You cannot make both and small at the same frequency. If you design for perfect disturbance rejection () at a specific frequency, then you inherently have at that same frequency, meaning sensor noise is fully passed to the output.
This trade-off shapes the entire control design process. The standard design paradigm is:
- Shape to be small at low frequencies for disturbance rejection and tracking.
- Shape to be small at high frequencies for noise attenuation and robustness to high-frequency modeling errors.
- Manage the crossover region (where ) carefully, as this is where both and have magnitudes around 0.7. The slope and phase of here determine stability margins.
The performance limits are visualized on a Bode magnitude plot. The difference between the low-frequency gain and the high-frequency roll-off of the loop gain defines the bandwidth of the control system and highlights the region where the designer must balance the competing requirements dictated by and .
Common Pitfalls
1. Ignoring the Noise Implications of High Bandwidth. A common mistake is pushing for extremely high bandwidth (making small over a very wide frequency range) to achieve aggressive tracking. This inevitably makes near unity over that same wide range, amplifying any high-frequency sensor noise. The result can be a system with chattering actuators, wasted energy, and premature wear, even if its simulation with perfect sensors looks excellent. Always consider the practical noise spectrum of your sensors when specifying bandwidth.
2. Overlooking the "Waterbed Effect" for Non-Minimum Phase Systems. For stable, minimum-phase plants, you can roll off and as described. However, if the plant has right-half-plane zeros (non-minimum phase), a profound limitation called the waterbed effect occurs. The Bode Integral Theorem states that if you suppress sensitivity () over a range of frequencies, it will necessarily peak () at other frequencies. You cannot "push down" sensitivity everywhere; pushing it down in one band makes it bulge up elsewhere. Failing to account for this can lead to unexpected fragility at frequencies you weren't testing.
3. Confusing Output Disturbance Rejection with Input Disturbance Rejection. The sensitivity function directly applies to disturbances entering at the plant output. However, disturbances often enter at the plant input (e.g., a load torque on a motor shaft). The transfer function for input disturbance rejection is , not just . A design that achieves small at low frequencies will also reject low-frequency input disturbances if has sufficient gain at those frequencies. Forgetting this distinction can lead to a system robust to one type of disturbance but vulnerable to another.
4. Designing Based on Alone. While achieving a desired shape is important for tracking, designing a controller by focusing solely on ignores the robustness picture. A system can have a beautiful but a poorly shaped that has large peaks, indicating very poor robustness to parameter variations and poor disturbance rejection at specific frequencies. A complete design always analyzes both and to verify all performance and robustness specifications are met.
Summary
- The sensitivity function quantifies a closed-loop system's robustness to parameter variations and its ability to reject output disturbances. Small at low frequencies is a primary control objective.
- The complementary sensitivity function defines the closed-loop tracking response and the amplification of sensor noise. Small at high frequencies is necessary for noise attenuation.
- The fundamental algebraic constraint creates an unavoidable trade-off: you cannot make both functions small at the same frequency. This forces the standard design pattern of high low-frequency gain and high-frequency roll-off.
- Effective control design involves shaping the loop gain to simultaneously achieve desirable and characteristics, managing the trade-off across the frequency spectrum.
- Always consider practical limitations like sensor noise spectra and the waterbed effect in non-minimum phase systems, as these impose hard limits on achievable performance.