Controls and BMS integration: controllers, BACnet and Modbus in HVAC quotations

A protocol name on a datasheet is not an integration. Ask for the point list, the version and who commissions it.

Almost every HVAC unit now arrives with its own controller. Whether that controller can talk to the building management system, and who makes it do so, is one of the most common gaps between a quotation and a working plant. A datasheet that says "Modbus" or "BACnet" tells you a protocol exists. It does not tell you which values are exposed, whether they can be written, or who maps them.

Two protocols you will meet most

BACnet is the building automation protocol developed under ASHRAE and published as ANSI/ASHRAE Standard 135, later also adopted by ISO. It describes equipment as standard objects, such as analogue inputs or schedules, so that a supervisor can discover and use them. Conformance is tested through BACnet Testing Laboratories. ASHRAE Guideline 13 shows how a specification should ask for BACnet devices and documentation.

Modbus is an older, simpler register-based protocol from industrial automation. It runs over serial links such as RS-485 (Modbus RTU) or over Ethernet (Modbus TCP). It has no built-in description of what each register means, so a register map is essential.

What to ask for

A point list is the most useful single document: every value the controller exposes, its unit, whether it is read-only or writable, and its alarm states. Ask for the protocol version, the physical interface and any gateway or licence needed. Ask who configures the mapping, who tests it on site and what happens when the controller software is updated.

Ask what the controller does on its own when communication is lost. Most chillers and heat pumps should continue on local control, and the default behaviour should be written down.

How this appears on the site

Several pages show protocol claims without the details that make them usable. The Dunham-Bush non-reversing defrost heat pumps name an RS485 Modbus touchscreen, and Dunham-Bush describes building communications for its central plant. The Xinwuxin parallel screw packages mention Modbus monitoring, while the Zhongda water-cooled screw catalogue does not name the controller protocol at all.

Process and data-centre equipment adds tool and site interfaces. The AIRSYS VENUS-GTS06 page asks for the tool controller compatibility, and AIRSYS INNOVA cooling integration needs the included software, licence and point map. Envicool's MC power-container cooling relies on dry contacts and alarms, and the Envicool EMA cabinet air conditioners need agreed filter-alarm behaviour.

Heat stations and air-side controls are no different. The Jinghai JH-IMC heat-exchange stations need the protocol version and point map, the Huifeng constant air volume dampers need the actuator, controller and gateway defined, and the Qinye dampers distinguish a thermal fuse from a commanded smoke-control signal.

Stand-alone controllers are products in their own right: the Elitech MC-1000 industrial chiller controller is one example, and Sino King's low-temperature screw family describes controller fault diagnosis. In vehicles, the Cling EZDD heat pumps must agree the control boundary with the vehicle controller.

Questions to put in the enquiry

Which protocol, version and physical interface does the quoted controller support as standard, and which need a gateway or licence? Can you send the point list or register map for this exact model and software version? Which points are writable, and which setpoints are protected? Who configures, tests and documents the integration, and is site commissioning included? What happens on loss of communication or power?

For chillers, read our chiller quotation guide so that the part-load data and the control strategy refer to the same operating modes. For air handling units and fans, the operating point the controller holds should match the selection in our duty-point guide.

Common questions

Is BACnet always better than Modbus? Not for every project. BACnet describes devices more fully; Modbus is simple and widespread. What matters is that the building system and the equipment use a compatible, documented option.

Does "BMS ready" mean plug-and-play? No. It usually means an interface is available. Mapping, testing and commissioning still have to be assigned.

By HVACDeck Editorial · Updated 2026-11-06