- This topic has 1 reply, 1 voice, and was last updated 1 day, 6 hours ago by
.
-
Posts
-
Starter question — a frequently asked question posted by the MEP Center team to open this forum. Share your own experience below.
Our BMS specification requires integration of chillers, boilers, VFDs, energy meters and the VRF system. Equipment suppliers offer BACnet/IP, BACnet MS/TP, Modbus RTU or Modbus TCP, sometimes as an extra-cost card.
- What is the practical difference between BACnet and Modbus for plant integration?
- When is Modbus RTU fast enough?
- What should be written in the specification so integration actually works?
Use BACnet (BACnet/IP preferably) for equipment that needs alarms, schedules and many meaningful points, such as chillers and boilers; Modbus is acceptable and common for simple devices like VFDs and meters, provided the register map is supplied and the polling load is checked.
The practical difference
- BACnet (ASHRAE 135, ISO 16484-5) describes data as objects with names, units, status flags, alarms, schedules and trend logs. Devices can report changes of value instead of being polled. Interoperability is defined by device profiles and the protocol implementation conformance statement (PICS).
- Modbus is a simple master-slave register protocol. A register is just a number; meaning, scaling, units and data type (16-bit, 32-bit, float, byte order) come only from the manufacturer’s register map. There are no native alarms or schedules, and data is read by polling.
Physical layer
- BACnet MS/TP and Modbus RTU both use RS-485: daisy-chained twisted pair, up to about 1200 m (4000 ft) per segment at lower baud rates, 32 unit loads per segment without repeaters, end-of-line termination and correct shield earthing.
- BACnet/IP and Modbus TCP run on Ethernet and are much faster, but need IT coordination: addressing, VLANs and cybersecurity.
Worked example: Modbus RTU polling time
Twelve devices (VFDs and meters) on one RS-485 segment at 19,200 baud, 11 bits per character. Each device needs 3 read requests of 10 registers.
- Request 8 bytes + response (5 + 2 x 10) = 25 bytes, total 33 bytes = 363 bits = 363 / 19,200 = 18.9 ms on the wire.
- Silent interval of 3.5 characters before each frame: 38.5 bits = 2.0 ms, twice = 4.0 ms.
- Assumed device response delay 30 ms: about 53 ms per transaction.
- 36 transactions x 53 ms = about 1.9 s per full scan.
Two seconds is fine for monitoring and slow control, but too slow if the BMS must also write speed commands to many drives for fast loops. Larger systems should be split into several segments or use Modbus TCP or BACnet/IP. Note that real device response delays vary widely; ask the supplier.
What to specify
- Protocol and physical layer for each equipment item in an interface schedule.
- Points to be integrated per item (read/write, units, alarms), not “full integration”.
- For BACnet: PICS and required BIBBs or device profile. For Modbus: register map with data types and scaling, delivered before shop drawings.
- Who supplies the interface card or gateway and who tests the integration point by point.
- Network addresses, baud rate and segment layout on the BMS architecture drawing.
- Safety functions (fire shutdown, frost protection, plant trips) remain hardwired.
Common mistakes
- Gateways that expose hundreds of unused points and slow the network.
- No termination resistors or wrong biasing on RS-485, causing intermittent communication.
- Scaling or byte-order errors in Modbus floating point values found only at commissioning.
Related: HVAC commissioning checklist. For deeper study: HVAC systems design course.
Check the edition of the code that applies to your project.
- You must be logged in to reply to this topic.