Protocols

Ravi's front-end speaks BACnet. Twenty-four VFDs only speak Modbus RTU. The chiller speaks Modbus TCP. The energy meters speak Modbus RTU on a different cable. The 'connected' building is not connected.

Manju inherits a 15-year-old building. Half the panels speak a legacy proprietary protocol; the new wing is BACnet IP. Two front-ends, two passwords, two engineers — for what should be one building.

Arun is reviewing four BMS bids. All four datasheets say 'BACnet compliant'. All four pass BTL listing. Yet only one is truly open. How does he tell the four apart before signing the spec?

Krishna has 47 Modbus devices on a Vizag refinery utility plant. Some on RS-485 daisy chain, some on Ethernet. The supervisor confuses RTU and TCP every meeting. Same protocol, two physical worlds.

Bhavani has BACnet IP working on the front-end. The 16 floor-level VAV boxes are MS/TP. The IT department won't allow new IPs on the corporate network. Two physical layers, one protocol — connected by a BBMD.

Rajesh's plant has industrial PLCs on the factory side and DDC controllers on the utility side. BACnet does not reach the PLCs. PROFINET does not reach the DDCs. OPC UA is the common floor where both meet.

Asha's pilot has 200 occupancy sensors and 40 air-quality nodes — battery-powered, Wi-Fi. BACnet is overkill for them. MQTT is the feather-light language they need to phone home.

Pradeep is on a hospital BMS riser for the first time. 18 Modbus slaves and 6 BACnet MS/TP devices. Some don't respond. Without a scanner, he is guessing — and guessing burns days.

Walk through how the BMS industry got here — Modbus 1979, vendor proprietary protocols 1985-1995, BACnet 1995, paper-BACnet 2000-2020, truly native BACnet today. The story of why most BMS front-ends still cannot talk to

OpenAPI Specification is a standard, machine-readable format for describing RESTful APIs, acting as a blueprint for how an API works. Swagger is a collection of tools (like Swagger UI, Editor, and Codegen) that help deve