Heater and Cooler on One Temperature Loop: Define the Split-Range Deadband

System boundary

One temperature loop coordinating a resistive heater and a separate cooling actuator such as controlled airflow or a fluid valve. Cooling capability, process safety and actuator limits belong to the actual equipment design, not the heater element alone.

Integration interfaces

Integration risks

Name the signed demand and the two actuator commands separately

Let u range from minus one to plus one, with positive values requesting heating and negative values requesting cooling. Let h and c each range from zero to one and drive their respective actuators. These are three signals, not different names for one percentage. Record whether the cooling interface expects an increasing command to open a valve, increase fan speed or produce another physical action.

Verify direction at a permitted low-energy operating condition before closing the temperature loop. A mistaken sign can make a cooling request add heat or close the cooling path. Do not infer direction from a wiring color or a generic controller label. The actuator's actual response and its fail-state behavior must be documented at the installed interface.

Define a command deadband with a piecewise map

One explicit symmetric mapping uses a positive gap parameter d. Heating begins only when u exceeds d; cooling begins only when u is below minus d. Between those limits both commands are zero. The active branches are rescaled so that the endpoints still reach full command. This is an illustrative mapping, not the assumed behavior of every commercial controller's deadband setting.

The expression below uses clip to constrain a number between zero and one. Because d is in command units, the inactive interval is not directly a temperature tolerance. Integral action and process dynamics determine how the controller moves through it. If a purchased controller defines deadband in temperature units or as an offset between proportional bands, translate its actual definition before comparing settings.

Check the map at both boundaries and inside the gap

For a hypothetical d of 0.1, u equal to 0.55 gives a heating command of 0.5 and zero cooling. A demand of minus 0.55 gives zero heating and cooling of 0.5. Demands of minus 0.05, zero and plus 0.05 all produce zero on both branches. At exactly plus or minus 0.1 the corresponding active command is still zero in this continuous mapping.

Check these values as software tests before using the loop with a heater. A different implementation that subtracts the gap but forgets to rescale the remaining span would not reach full actuator command at u equal to one. Conversely, applying a minimum nonzero output at the boundary introduces a jump that is absent from the stated formula and needs its own control review.

Intentional overlap consumes both actuator resources

An overlap map can deliberately activate both branches around zero demand. For example, replacing the gap with a positive overlap parameter o in h equal to clip of u plus o divided by one plus o, and c equal to clip of minus u plus o divided by one plus o, gives both commands equal to o divided by one plus o at u equal to zero. The exact map must be stated rather than described only as negative deadband.

With o equal to 0.1, both commands are approximately 9.09 percent at zero signed demand. If hypothetical full-scale heating adds 200 watts while full-scale cooling removes 100 watts at the current condition, a linearized comparison gives about 9.09 watts of net heating, not zero. Equal percentages do not cancel unequal thermal authority. Real cooling is often condition-dependent, so its measured relationship is required.

Do not confuse an inactive gap with hysteresis or switching dwell

The static deadband map gives the same h and c for a given u regardless of whether demand is rising or falling. Hysteresis includes history: a branch's switching threshold depends on its previous state or direction. Minimum on/off dwell adds a time condition. These mechanisms solve different problems and can coexist, but they should not share one undocumented parameter name.

For example, a static gap can prevent simultaneous requested commands yet still allow rapid alternation when a noisy demand repeatedly crosses opposite boundaries. A history-dependent changeover policy may reduce that behavior, but it changes response and must be validated. Preserve the selected state machine and timings with the actuator map so a later controller replacement does not silently substitute another algorithm.

Measure heating and cooling gains instead of assuming symmetry

Heating and cooling may have different gain, delay, saturation and minimum useful command. A resistive heater's output can change quickly while a cooling valve takes time to move. A fan may remove little extra heat near ambient but much more at a higher surface temperature. One proportional gain for both directions may therefore produce very different closed-loop behavior.

Commission each branch under defined load conditions and retain the actual heat-addition or heat-removal response. If separate gains or a nonlinear cooling map are used, record their domain and transition behavior. Do not compensate for a blocked cooling path merely by increasing a cooling-gain setting; verify that the requested physical action occurs and that the available authority matches the process requirement.

Observe the real changeover after commands cross zero

Zero heater command does not remove stored heat, and zero cooling command may not immediately stop fluid flow or fan motion. During a reversal, log heater current, cooling flow or another direct actuator observation, surface/process temperatures and both commands. This distinguishes intended static exclusion from overlapping physical effects caused by actuator or thermal dynamics.

Define the permitted transition and any required interlocks using the actual equipment risk assessment. Do not use normal control deadband as the sole means of handling a stuck heater, failed valve or sensor fault. Protective interruption and recovery remain separate functions. Any abnormal test should use the reviewed containment and independent termination arrangements, not rely on the split map to make the test safe.

Accept the two-branch map before tuning the complete loop

Provide a tabulated input-output sweep through negative demand, both changeover boundaries and positive demand in both directions. Add step or ramp tests that expose actuator delay and any minimum command. Then evaluate temperature control under the intended heating, cooling and reversal conditions, using the same approved limits and load configurations.

The final handoff includes sign conventions, units, static mapping, hysteresis or dwell rules, branch gains and the observed physical transition. This gives the heater supplier and system integrator a precise division of responsibility. The printed element defines one heat source; the complete assembly and controller determine whether heating and cooling cooperate effectively around the customer's required temperature.