A setpoint change alone does not require PID autotuning. Autotuning characterizes how the controlled system responds under specific operating conditions; if those conditions and the process behavior remain unchanged, retain the existing tuning.
Separate the Setpoint From the Tuning Conditions
The setpoint defines the requested operating value. Autotuning serves a different purpose: it evaluates system response under a particular set of conditions. Changing only the requested value does not, by itself, establish that the system dynamics have changed.
The available information does not identify the controller, instruction, firmware, process, or autotuning method. Therefore, confirm any product-specific execution requirements in the applicable controller documentation before changing the implementation.
Use Operating Conditions as the Retuning Decision
| Observed change | Decision | Reason |
|---|---|---|
| Only the setpoint changed | Do not automatically rerun autotuning | The evidence does not indicate a change in system response. |
| Operating conditions changed | Reassess whether tuning remains suitable | The original autotuning result represents the conditions under which the system response was evaluated. |
| It is unclear whether process behavior changed | Verify response before deciding | A setpoint edit and a change in process dynamics are separate events. |
Apply and Verify the Setpoint Change
- Change the setpoint as required without automatically triggering autotuning.
- Confirm that the operating conditions represented by the existing tuning have not changed.
- Observe the controlled response after the change and compare it with the required behavior.
- If the response is no longer acceptable or the operating conditions have changed, reassess the tuning rather than attributing the issue to the setpoint change alone.
Do not schedule autotuning solely because an operator or program updates the setpoint. Base the retuning decision on whether the controlled system still behaves acceptably under the current conditions.
FAQ
Must I run PID autotuning every time the setpoint changes?
No. If only the setpoint changes and the operating conditions remain the same, the existing tuning can remain in use.
When should I reconsider PID tuning after a setpoint change?
Reconsider it when operating conditions have changed or when verification shows that the controlled response is no longer acceptable.
Does changing a PID setpoint change the process dynamics?
Not necessarily. Treat the setpoint edit separately from the conditions that determine system response, and verify the response before deciding to retune.