HVAC CPU Configuration: Resolving Summer Humidification

Regenerate the reference project with every installed option matched to the commissioned project, changing only the steam humidifier from winter-only to always available. Compare every input of the Configuration macro; if Code (SCADA) and Code (Sens) then match and only CPU Command differs, change only CPU Command in the customized project. The sequencer can coordinate cooling, electric reheat, and steam humidification, but stable control still depends on equipment capacity, sensor quality, loop tuning, and correct commissioning.

Choose the Correct Configuration Change

Do not replace the complete project or transplant the entire Configuration macro before establishing which configuration inputs actually changed. The safest comparison uses two generated projects:

• The original configuration, reproduced exactly as installed.
• The revised configuration, identical except that the steam humidifier is available in all seasonal modes.

Compare all values applied to the inputs of the Configuration macro. The relevant values in this case are Code (SCADA), Code (Sens), and CPU Command. If all three differ, first check the project selections rather than assuming that all differences belong to the humidification change. Options such as supply and extract filters, an alarm lamp, and other peripheral devices can alter the generated codes.

After regenerating both projects with those secondary options matched, the installation described here produced only a different CPU Command. That isolated difference identifies the value to transfer into the customized project.

What the Three Configuration Values Control

These values are not interchangeable labels. A mismatch is diagnostic evidence that the two generator runs may describe different systems. The absence of an automatic SCADA package or an SMH 2G panel does not make unexplained differences in the other codes acceptable. First make the generated projects structurally identical; then decide which value must change.

Why the Humidifier Can Operate With Cooling and Reheat

The configured air-handling unit uses a variable-frequency drive, one extract path without standby, a water cooling coil, a water heating coil, an electric heating stage, and a steam humidifier. Its original seasonal strategy assigned the water cooler to summer temperature and humidity control, the water heater to winter temperature control, the electric heater to summer temperature control, and the humidifier to winter humidity control.

Changing the humidifier to always available removes the seasonal inhibit; it does not mean every output must remain energized continuously. The sequencer evaluates temperature and humidity demand and stages the available devices according to its control strategy. During warm, dry-air conditions, cooling may be required for temperature or moisture treatment, electric reheat may restore the supply-air temperature after cooling, and steam humidification may add moisture. Those demands can legitimately overlap.

The controller can issue those commands, but it cannot compensate for an undersized coil, heater, humidifier, valve, steam supply, or electrical service. It also cannot produce stable humidity if sensors are poorly located, slow, biased, or exposed to unevaporated steam. A successful code change therefore proves configuration acceptance, not process capacity.

Procedure for Updating the Customized Project

1. Record the installed equipment selections and every secondary option represented in the existing generated project, including filters, alarm indication, and peripheral devices.
2. Generate a clean reference project that reproduces the current installation and its winter-only humidifier selection.
3. Generate a second reference project using the same selections, changing only the humidifier availability to always.
4. Compare Code (SCADA), Code (Sens), CPU Command, and every other input exposed by the Configuration macro.
5. If more than CPU Command differs, return to the generator and find the unmatched selection. Do not transfer values until the discrepancy is explained.
6. When CPU Command is the only difference, back up the commissioned project and enter the revised value at the corresponding macro input. Preserve the site-specific cosmetic and functional modifications.
7. Compile or validate the project using the normal engineering workflow. Resolve type, range, or configuration errors before placing the controller into service.
8. Commission the revised sequence through each relevant operating state and confirm that interlocks, alarms, actuator commands, and shutdown behavior remain intact.

If multiple configuration values legitimately change after a verified comparison, update all corresponding macro inputs as a matched set. Copying only one value from a materially different generated configuration can leave the controller and interface descriptions out of alignment.

Commission and Verify the Combined Sequence

Test the sequence under a real humidity demand rather than checking only whether the humidifier output turns on. Trend the supply and controlled-space temperature and relative humidity, together with cooling, heating, and humidifier demands. Also observe fan proof, airflow permissives, valve or heater commands, and active alarms.

1. Start in summer mode with humidity above setpoint and confirm that the original cooling and temperature-control behavior remains functional.
2. Create or wait for a dry-air condition. Verify that the seasonal state no longer blocks the steam humidifier.
3. Confirm that humidification receives the required airflow and equipment permissives before steam is enabled.
4. Observe simultaneous cooling, electric reheat, and humidification when the process demands them. Confirm that the outputs modulate instead of repeatedly saturating or cycling.
5. Verify that the controlled humidity approaches its target without unacceptable temperature deviation, condensation, or opposing loops that remain at full output.
6. Test stop commands, fan failure, loss of airflow, sensor fault handling, and alarm indication. The humidifier and electric heater must return to their designed safe states through the existing interlocks.

If temperature is stable but humidity remains low with maximum humidifier demand, investigate steam capacity, steam delivery, airflow, outside-air moisture load, and leakage. If humidity oscillates, inspect sensor placement and response before retuning the loop. If cooling, reheat, and humidification fight continuously, review setpoints, deadbands, staging logic, and sensor calibration.

Recurring Configuration and Control Pitfalls

• Comparing unlike generated projects: A forgotten filter, alarm lamp, or peripheral selection can change configuration codes and conceal the one intended difference.
• Treating interface codes as irrelevant: Even without planned SCADA or an SMH 2G panel, a code mismatch signals that the generator inputs may not match.
• Replacing the whole macro unnecessarily: This can overwrite commissioned customization. Transfer the verified input value or matched input set instead.
• Equating permission with continuous operation: Always-available humidification permits the sequencer to use the humidifier in summer; demand and interlocks still determine its output.
• Accepting output activation as proof: The final acceptance criterion is stable room temperature and humidity under representative load, not merely energized equipment.
• Ignoring plant interaction: Cooling, reheat, and steam addition affect both temperature and moisture. Capacity limitations or poor tuning can make valid sequencing appear defective.

FAQ