What BACnet Is
BACnet is an open building automation communication standard centered on objects, properties, and services. Unlike Modbus register maps, BACnet exposes semantic object types and strongly typed properties.
Common Network Layers
| Network | Transport | Typical Use |
|---|---|---|
| BACnet/IP | UDP/IP (BVLL) | Building backbone and supervisory systems |
| BACnet MS/TP | RS-485 token passing | Field controller trunks |
Object Model Basics
BACnet devices expose:
- Object type (for example
analogInput,binaryValue) - Object instance
- Property set (for example
presentValue,units,statusFlags)
Service Categories
- Discovery services (
Who-Is,I-Am) - Data exchange services (
ReadProperty,WriteProperty) - Subscription services (
COV)
Integration Risks
[!INFO] Most BACnet interoperability issues are profile/expectation mismatches rather than transport failures.
Typical mismatch vectors:
- Wrong device instance assumptions
- Unsupported write services
- COV behavior differences
- Object naming and point-list mismatch
MS/TP-Specific Cautions
[!WARNING] Duplicate MAC addresses or incorrect
Max Masterssettings can produce intermittent network instability that appears random at the supervisory layer.
Common Problems
- Devices not discovered — On multi-subnet networks, BACnet broadcast (Who-Is) does not cross IP routers without a BBMD. See BACnet Discovery & Network Architecture Reference.
- Wrong device instance — Gateway or BMS configured with incorrect device instance value. See BACnet Device Instance and BACnet Discovery & Network Architecture Reference.
- Intermittent MS/TP communication — Duplicate MAC addresses or incorrect Max Masters setting on the trunk. See Troubleshooting Guide for BACnet MS/TP Networks.
- Unexpected object types or missing properties — Profile mismatch between what the BMS expects and what the device exposes. See BACnet Object Types & Properties Reference.