Robust Control, Sensitivity & Loop Shaping
Robust control asks whether stability and performance survive a stated set of plant errors and disturbances. Sensitivity functions expose the trade-offs; loop shaping allocates gain by frequency; H∞ synthesis turns weighted worst-case amplification into an optimization problem.
A nominal controller is designed for one plant model . A robust claim quantifies what remains true for a set of plants, disturbances, sensor noise and implementation errors. “It worked in simulation” is nominal evidence unless the simulation varied the uncertainties that matter.
Sensitivity partitions the loop #
For loop transfer ,
- shapes output response to many load disturbances and plant perturbations.
- shapes reference transmission and measurement-noise paths, depending on architecture.
- exposes control effort and actuator demand.
At low frequency, large makes small and improves regulation. At high frequency, small keeps small and avoids chasing noise and unmodeled dynamics. Crossover is the negotiated boundary.
flowchart TD D["low-frequency disturbances"] --> S["small S wanted"] N["high-frequency noise and uncertainty"] --> T["small T wanted"] S --> L["shape loop L = PC"] T --> L L --> M["margins, effort and bandwidth"]
Because , both cannot be small at the same frequency. Bode's sensitivity integral adds a waterbed constraint: for important plant classes, pushing sensitivity down in one region forces it up elsewhere.
Describe uncertainty before proving robustness #
Useful models include:
- parametric ranges for gains, time constants and delays;
- additive uncertainty ;
- multiplicative uncertainty ;
- neglected high-frequency dynamics;
- nonlinear limits and mode changes tested outside linear robust analysis.
The weight should bound relative model error over frequency. If , a small-gain robust-stability condition for output-multiplicative uncertainty is
This statement is only as credible as the uncertainty bound. Data from one operating point do not justify a global .
Classical loop shaping #
Shape so it has:
- high enough low-frequency gain for tracking and disturbance rejection;
- crossover compatible with plant delay and uncertainty;
- adequate gain and phase margins;
- roll-off before noise and unmodeled resonances;
- tolerable peaks in and ;
- feasible control effort and rate.
The maximum sensitivity summarizes the worst disturbance/uncertainty amplification and relates to distance from the Nyquist critical point. It is more informative than tuning for a pretty step response alone.
H∞ formulation #
The norm of a stable transfer matrix is its maximum singular value over frequency. Weighted mixed-sensitivity design asks for a stabilizing controller that makes
encodes desired error/disturbance attenuation, control limits, and high-frequency robustness/noise requirements. The optimization is powerful because it handles multivariable interaction and worst-case amplification. It does not choose physically meaningful weights or uncertainty sets for the engineer.
Robustness workflow #
- Identify the decision-relevant operating region and uncertain mechanisms.
- Validate nominal dynamics and bound error in time and frequency.
- Write performance outputs and exogenous inputs explicitly.
- Shape or synthesize the controller.
- Verify nominal stability and performance.
- Verify robust stability separately from robust performance.
- Test nonlinear saturation, rate limits, sampling, quantization and mode changes.
- Validate on representative plants and disturbances, then update uncertainty bounds.
Robust control is not conservatism for its own sake. It is a reproducible claim of what the closed loop tolerates, where the claim applies, and which uncertainty would invalidate it.