HVAC integration patterns for KNX projects

Most large HVAC plants speak BACnet or Modbus, while terminal units like fan coils, valve actuators, and damper drives often speak KNX directly. The integration challenge is to bridge the two and present a unified user experience.

A typical layout in a mid-sized building: chillers and air handling units (AHU) on a BACnet/IP backbone managed by a Building Management System (BMS) controller, while every floor has a KNX line for room-level control of fan coils, lighting, blinds, and occupancy. A KNX-BACnet gateway exchanges setpoints, occupancy, and alarms between the two worlds.

For each fan coil unit (FCU), define at minimum: setpoint (DPT 9.001 temperature in degrees Celsius), measured temperature, mode (Comfort, Standby, Economy, Building Protection per DPT 20.102), fan speed (off / 1 / 2 / 3), valve position for heating, valve position for cooling, and a window-open contact. Status feedbacks for valve and fan are essential for diagnostics; without them, you cannot tell from the visualization whether a room call is being served.

Anti-condensation logic deserves attention in humid climates. Pair every cooling valve with a dewpoint sensor or a humidity sensor and a calculated dewpoint, and force the valve closed if the supply temperature falls below it. This logic sits naturally in the KNX FCU controller and prevents costly water damage.

Finally, plan a handover scenario for the BMS engineer. Document every gateway mapping in a single spreadsheet: BACnet object on one side, KNX group address on the other, units, and direction. The first BACnet point that does not match its KNX counterpart is the one that will haunt you for months.