What effect does actuator saturation have on a controller, and how can it be mitigated?

• A. It increases system bandwidth; mitigate with higher gain
• B. It limits achievable output and can cause integral windup; mitigate with anti-windup, rate limiting, or feedforward
• C. It improves stability; mitigate by reducing sampling rate
• D. It reduces sensor noise; mitigate by filtering

Answer: (B)

Actuator saturation occurs when the controller requests a signal beyond what the actuator can physically provide. This clamps the plant input, so the controller’s output no longer matches what the controller has calculated, which can cause the integral term (in controllers with integral action) to wind up. That windup means the controller keeps accumulating error while the output is stuck at the limit, leading to large overshoots, longer settling times, or even instability once the actuator leaves saturation.

Mitigation focuses on keeping the controller’s commands within the actuator’s capability and preventing or curing windup. Anti-windup techniques (such as back-calculation or clamping the integral term to respect actuator limits) stop the integral term from growing when saturation occurs. Rate limiting on the actuator command prevents rapid pushes into saturation, and feedforward or model-based adjustments anticipate disturbances so the commanded effort stays within achievable bounds.

Increasing gain or bandwidth won’t fix saturation and can make the problem worse; reducing sampling rate doesn’t address the fundamental limitation, and filtering sensor noise doesn’t prevent the actuator from saturating.