Air-handling units that hold one leaving-air or space setpoint through an entire winter invite condensation on cold surfaces—camera housings included—and a queue of operator overrides. The wrong instinct is to “ADD five degrees to the setpoint when it is cold.” That pattern either drifts forever each scan or destroys the meaning of a setpoint. Studio 5000 (RSLogix 5000) can implement seasonal and humidity compensation cleanly if the architecture keeps a base value, computes an effective setpoint each scan, and lets PID chase the result.

Effective setpoint composition—not destructive edits to Temp_SP—keeps HVAC loops stable across seasons.

Why direct setpoint mutation fails

A rung that repeatedly executes ADD 5 AHU.Control_Temp AHU.Temp_SP (or any accumulating write into the same SP tag) produces runaway drift: every scan adds again. Even a once-per-day ADD is still the wrong model. The setpoint must remain the desired condition; ambient and humidity information should adjust an offset that is recomputed from known inputs, not accumulate into history.

Correct philosophy:

• Base_Setpoint defines the manually curated comfort or process target
• Seasonal_Offset and humidity offsets are bounded additives
• Temp_SP (effective) = Base + seasonal term + humidity term, calculated fresh each scan
• PID / burner logic compares Control_Temp to Temp_SP ± deadband

Tag set for seasonal compensation

Seasonal mode and effective SP rungs

// Summer_Mode true for months 5–10 (adjust for climate)
GRT Clock.Month 4
LES Clock.Month 11
OTE Summer_Mode

// Rebuild effective SP every scan — never accumulate
MOV AHU1.Base_Setpoint AHU1.Temp_SP
XIO Summer_Mode
ADD AHU1.Temp_SP AHU1.Seasonal_Offset AHU1.Temp_SP
ADD AHU1.Temp_SP AHU1.Temp_Offset_From_Humidity AHU1.Temp_SP

Northern plants may keep winter mode active from October through April. Document the month window beside the HMI so operators understand why Temp_SP differs from Base_Setpoint without assuming the PID “is broken.”

Humidity-triggered offsets address condensation risk more directly than calendar month alone.

Humidity-based compensation

When cameras fog because surface temperature drops below dew point, a humidity loop is the preferred primary compensation. Keep a humidity PID (typically slower than temperature) that raises a bounded Temp_Offset_From_Humidity when RH exceeds Humidity_SP. Clamp the offset so a failed wet sensor cannot command an absurd room temperature. Maintain RH targets in the 45–55% band unless the process specification says otherwise, and verify sensor calibration monthly.

Burner / coil deadband logic

Start and stop sequences must compare Control_Temp against Temp_SP with deadband, not against a constantly moving raw ambient. Typical structure: permissive run bits, LES Control_Temp (Temp_SP − deadband) to request heat, and a separate LES/GRT pair to clear the request when the band is satisfied. Use comparison instructions (LES, GRT, LIM)—not informal inequality text pasted into comments.

COP array subscript errors

Recipe-style seasonal tables often fail with “Invalid array subscript specifier” when engineers write compound expressions inside COP brackets or invent comma-separated 2D indexes. Pre-calculate a single DINT index, then COP from a 1D array:

MOV AHU_No_Select AHU_Array_Index
SUB AHU_Array_Index 1 AHU_Array_Index
// optional quarter offset: ADD AHU_Array_Index Clock_Quarter AHU_Array_Index
COP AHU_Temp_SetPoints[AHU_Array_Index] AHU1.Temp_SP 1

Commissioning and pitfalls

1. Force Summer_Mode false; confirm Temp_SP equals Base + Seasonal_Offset
2. Force Summer_Mode true; confirm Temp_SP returns to Base (plus any humidity term)
3. Inject humidity above SP; confirm offset rises and clamps
4. Verify Burner_Req / cool request edges at Temp_SP ± deadband
5. Trend Control_Temp and Temp_SP for at least thirty minutes across a mode change

Avoid runaway ADD patterns, sensors that read supply air instead of space, deadbands so narrow the burner chatters, and RTC transitions without a one- or two-day buffer that flip Summer_Mode every midnight near the boundary month. Keep Base_SP and Offset visible separately on the HMI so operators trust the calculation.

AHU controllers share revision control and sparing with the rest of the plant’s Logix PAC fleet—document the compensation equations in the same project package as the PID gains.