Learn why an integral term keeps growing during saturation and compare practical anti-windup methods.
I(t)=Ki∫0te(τ)dτ
Integral action removes persistent error by accumulating it over time. During actuator saturation, however, the process cannot receive the requested command while the integrator may continue accumulating a correction that cannot be applied.
01
The hidden mismatch
Windup begins when the unclamped controller command differs from the applied actuator command. The response curve alone may not reveal this; plot both signals and the integral contribution.
SATURATION VIEW 01
Requested output can exceed the real actuator
The internal PID request continues above the physical limit while the applied output is clipped at 100 percent.
Raw PID requestActuator limitApplied output
READ THE PLOTWindup begins in the gap between requested and applied output
02
Conditional integration
Clamping pauses integration when the output is saturated and the error would drive it farther into saturation. It is simple and often effective, but transitions can be abrupt.
STATE VIEW 02
The integrator remembers an impossible command
Without protection, integral state keeps climbing during saturation. Clamping pauses it; back-calculation actively tracks what the actuator can deliver.
No anti-windupClampingBack-calculation
READ THE PLOTAnti-windup manages hidden controller state
03
Back-calculation
Back-calculation feeds the difference between limited and unlimited output into the integrator. The tracking gain controls how quickly the internal controller state follows the achievable actuator command.
RECOVERY VIEW 03
Anti-windup changes recovery, not actuator power
All cases hit the same output limit, but protected integrators unwind sooner and return the process to target with less overshoot.
SetpointNo anti-windupClampingBack-calculation
READ THE PLOTCompare the curve after it leaves saturation