BACnet objects, services, BACnet/IP vs. MS/TP, device instance numbers, BBMDs, and how the dominant open protocol actually enables multi-vendor interoperability — plus the integration pitfalls that trip up real projects.
BACnet (ASHRAE/ANSI Standard 135) is the open, vendor-neutral protocol that lets a chiller controller from one manufacturer, a VAV box controller from a second, and a supervisory front-end from a third all speak the same language. This module works through how BACnet models equipment as objects (AI, AO, BI, BO, AV, BV, schedules, trend logs), how devices actually communicate through services (ReadProperty/WriteProperty, COV, alarming), and the two physical networks — MS/TP and BACnet/IP — nearly every real building runs together.
By the end of this module you should be able to explain why a device instance number conflict or a misconfigured BBMD can make a perfectly functional controller appear to vanish from a supervisory system's device list — and how reading a device's PICS before finalizing an integration design avoids the most common multi-vendor integration pitfalls this module closes with.