Control valve hunts in AUTO but runs smoothly in MANUAL
If a valve cycles in automatic and goes quiet in manual, the feedback path is generating the cycle. What that rules out, what it leaves, and how to finish the analysis.
Start from what the loop is actually doing. Each page works through the causes in the order they usually turn out to be the answer, and says plainly which ones tuning cannot fix.
If a valve cycles in automatic and goes quiet in manual, the feedback path is generating the cycle. What that rules out, what it leaves, and how to finish the analysis.
When the output swings and the process does not follow, the loop is working hard for nothing. The four causes, and how to tell them apart from a trend.
PID oscillation that decays is a tuning problem; constant amplitude is a valve limit cycle. How to tell decaying, growing and sustained oscillation apart.
Stiction produces a distinctive limit cycle: stepped PV against a smoothly ramping output, constant amplitude, gone in manual. How to confirm it.
PID hunting and control valve hunting are usually stiction or an oversized trim, not the constants. Thirty seconds in manual tells you which.
A loop that will not hold setpoint is PID offset, a pegged output, or a selector that dropped this loop — not a loop that needs more gain.
Flow loops are fast and noisy, which makes them intolerant of derivative action and of reset set faster than the loop's dead time. What to check.
The output stays on its limit after the process variable has crossed setpoint, then overshoots hard. How to tell windup from aggressive tuning.
Overshoot on a setpoint move but not on a load change is derivative kick or windup, not a gain problem. How to tell them apart before you detune.
A PID output stuck at 0% or 100% is a saturated controller: no tuning change reaches the valve. Which limit you are on, why windup follows, what to check.
A sluggish control loop is not always under-tuned. A filter, a drive ramp or the constants can all produce it, and only one of those yields to retuning.
A cascade that hunts is usually two loops being moved at once, or a slave that is not actually faster. How to tell which loop is generating the cycle.
The controller output is at 0% and the process variable still will not come down. A passing valve is a leak, not a PID.
A setpoint step produces an output spike when derivative acts on error. The fix is derivative on PV, not less gain.
Two loops sharing a process will hunt when each treats the other as a disturbance. How to tell interaction from a single bad tune.
A chattering valve is usually derivative action amplifying measurement noise. How to tell that apart from real process noise and from an instrument fault.
On a VFD-driven loop the drive's own accel and decel ramps are often the dominant lag. What to check before re-tuning a hunting speed loop.
Backlash shows as a flat spot on the PV every time the output reverses. How to measure the deadband and what causes it.
Switching to automatic makes the output step. Bumpless transfer has failed. What to check before you blame the tune.
Two photos, thirty seconds, no signup. The pre-flight check finds the structural problems that no amount of tuning will fix — before you touch the controller.