Controller output saturated
When the controller output sits against a limit, the controller has stopped controlling. Whatever the tuning is, it is not reaching the process — the output cannot go any further in the direction the error is asking for.
This is worth taking seriously even when it is brief. Every period of saturation is a period where integral action accumulates against a limit it cannot act on, and the overshoot that follows is often blamed on tuning when it is really windup.
First, find out which limit
An output at 100% and an output at 0% mean opposite things. At 100% the loop is asking for more than the final element can deliver: not enough valve, not enough pump, not enough supply pressure, or a restriction somewhere. At 0% it is asking for less than the minimum the system will pass — a leaking valve, a bypass open, or a minimum flow that cannot be shut off.
Also check whether the limit is a real physical limit or a configured clamp. Output limits get added to stop a loop doing something specific and then stay long after the reason is forgotten. A loop clamped to a narrow span saturates on disturbances it should be able to handle comfortably.
Then look at what happens on the way out
If the output stays at its limit for a noticeable period after the process variable has passed setpoint, the controller has wound up. The integral term accumulated while the output was clamped and now has to unwind before the output will come off the limit.
That produces a large overshoot that looks exactly like aggressive tuning, and detuning the loop in response makes things worse — a slower loop spends longer saturated.
What causes it, most likely first
Valve or pump undersized for the duty
most common tuning cannot fix this
The final element genuinely cannot deliver what the process now needs, often because the process has changed since it was sized.
- How to confirm it
- The output reaches 100% under normal operating conditions, not just during upsets. Check the normal valve position over a typical day.
- What to do
- Check upstream supply first — pressure, strainers, pump curve. If the supply is healthy, the element is undersized.
A configured output limit nobody revisited
common tuning cannot fix this
An output clamp added for a specific reason, long ago, now restricting normal operation.
- How to confirm it
- Read the configured high and low output limits. A span much narrower than 0-100% deserves an explanation.
- What to do
- Find out why the limits are where they are before removing them — some are there for a good reason.
Missing or ineffective anti-reset windup
common tuning can fix this
Integral action continuing to accumulate while the output is clamped, producing overshoot on recovery.
- How to confirm it
- The output stays at its limit after the process variable has crossed setpoint.
- What to do
- Check the controller's anti-windup configuration. Most modern systems handle this correctly when configured; the setting is often just off.
An upstream constraint
common tuning cannot fix this
Supply pressure has fallen, a strainer is blocking, or a parallel user is taking capacity.
- How to confirm it
- Trend the upstream pressure alongside the loop.
- What to do
- Deal with the constraint. The loop is reporting a real problem accurately.
Questions that come up
The output is at 100% but the process is on setpoint. Is that a problem?
Yes. The loop has no capacity left to correct in one direction. It will hold setpoint until the first disturbance that needs more, and then it will not recover.
Related
Last reviewed 2026-08-01.