Heater Manual-to-Auto Transfer: Initialize the Integral State Without an Output Jump

System boundary

A PI temperature controller taking over an already permitted heater operation from manual control. The calculation concerns command continuity, not authorization to energize, independent protection, full PID derivative state or general anti-windup design.

Integration interfaces

Integration risks

Separate a mode change from permission to heat

Manual-to-automatic transfer changes who calculates a command. It does not by itself authorize heating after a fault, restore a disconnected load or prove that the sensor is healthy. Establish that the assembly is already in an approved operating state before using a continuity calculation. If permission is absent, the required inhibited output takes priority over any attempt to preserve the previous manual value.

Name the transfer event precisely. An operator selecting automatic mode, a supervisory sequence handing over control and a controller starting after a reboot are not automatically equivalent. This page addresses a live handover with a valid measurement and a known applied manual command. Power-recovery and fault-reset sequencing require the separate restart review linked below.

Identify what the controller actually stores as its integral state

For a parallel PI representation, write the automatic output as Kp times temperature error plus integral contribution I plus any feedforward contribution. Here I is already in output-command units. Some implementations instead store the accumulated error and multiply it by Ki later. Setting the same numerical value in those two representations produces different commands, so inspect the implemented controller rather than copying a preload constant from another platform.

Also identify offsets, output scaling and selection blocks. A display may show percent demand while the actuator receives a normalized fraction or another command. The preload calculation must use one consistent unit at one defined boundary. If an output limiter or selector changes the manual request, record the applied value used by the automatic controller's matching calculation.

Subtract the present proportional and feedforward contributions

At the transfer instant, require the automatic command to equal the applied manual command. Rearranging the PI output equation gives the required integral output directly. This is an algebraic state match, not a tuning rule. It remains useful even when the temperature error is not zero, provided the current error and other contributions are evaluated consistently at that instant.

The formula does not require forcing the setpoint to equal the measured temperature. Setpoint tracking can be a separate operating policy, but changing the customer's requested target merely to hide a handover jump changes the process objective. If the target is intentionally changed during transfer, use that new target in the proportional calculation and record the target change as a separate event.

A nonzero heat requirement does not imply a nonzero temperature error

Consider a hypothetical command expressed in percentage points. The applied manual output is 42 percent, the setpoint is 80 degrees Celsius, the measured temperature is 78 degrees Celsius, Kp is three percentage points per kelvin, and feedforward contributes ten percentage points. The proportional contribution is six, so the required integral output is 42 minus six minus ten, or 26 percentage points.

If the integral were cleared to zero, the automatic command would initially be only 16 percent, a negative jump of 26 percentage points. If a stale integral of 40 were retained, the command would be 56 percent, a positive jump of 14 points. Even at zero temperature error, clearing the integral would not reproduce a required manual heat input unless all that heat were already represented by another contribution.

Apply the state match in a defined execution order

Capture the accepted transfer event, valid measurement, selected target, gains, feedforward term and applied manual command from a coherent control sample. Calculate the preload using those values. Then generate the automatic output from the same values and the initialized state. A target or feedforward update between preload and output evaluation can reintroduce a jump despite a correct formula.

Define when normal integration resumes. If the implementation immediately adds Ki times error times the sample period after loading I, the first automatic output includes that increment. That may be intentional, but it is not the same as exact equality at the switching sample. Log enough state to distinguish the planned first control action from an unplanned transfer discontinuity.

Use tracking during manual operation when the implementation supports it

An alternative to loading the state at one instant is to keep the inactive automatic controller tracking the selected manual output. The tracking mechanism adjusts its internal contribution while manual control remains selected. A finite tracking response produces an approximate match whose residual depends on how quickly the manual command and other terms change. Verify the residual at the actual handover rather than assuming tracking implies exact equality.

Keep this handover function distinct from recovery after prolonged output saturation. Both may use information about the applied command, but they answer different state problems. The anti-windup review owns how integration behaves while authority is limited and how it recovers; this transfer review owns the command immediately before and after the selector changes.

Test the selector event before judging the thermal response

Record the mode signal, manual request, applied command, automatic calculated command, proportional contribution, integral output, feedforward and measured temperature. Compare the samples immediately around the transfer. A slow temperature sensor can conceal a brief command discontinuity, so a smooth temperature trace alone is not sufficient evidence that the command handover was smooth.

Repeat with positive and negative temperature error, several manual outputs and a changing feedforward term if used. Include any permitted output-limit conditions, and define behavior when a preload cannot be represented within the controller's state limits. Do not silently clip the integral and then claim exact matching; report the remaining command difference and the selected controlled transition behavior.

Preserve the transition contract with the controller configuration

The handoff should contain the PI form, stored-state meaning, output units, accepted manual-command boundary and event ordering. Include a small set of numerical transfer cases with expected preloads and first outputs. These cases are useful regression checks after firmware, gain scaling, feedforward or supervisory-control changes, even when the heater drawing itself has not changed.

After command continuity is verified, evaluate the subsequent temperature response under the intended load. Bumpless transfer does not guarantee good tuning, sufficient heating authority or absence of overshoot. It removes one avoidable discontinuity so that the later response can be assessed as a control-loop and thermal-assembly problem, rather than confused with a wrongly initialized integral state.