What It Is
BACnet/IP carries BACnet application traffic over UDP/IP, typically on port 47808 (0xBAC0). It is the dominant BACnet transport for workstations, head-end supervisors, and IP-connected controllers.
Unlike BACnet MS/TP, it relies on IP network design, broadcast domains, and firewall policy rather than serial token passing.
Discovery And Broadcast Model
BACnet/IP discovery is built around Who-Is and I-Am. On a single subnet, broadcast discovery is straightforward. Across subnets, that discovery path needs BBMD or FDR design.
The most important engineering question is usually not “does BACnet/IP exist?” It is “what does this network do to UDP broadcast traffic between the client and the device?”
Where It Fits
- Supervisory BMS platforms
- Head-end integrations across buildings or VLANs
- Gateways that expose large object sets over Ethernet
- Sites where discovery, browsing, and object-level diagnostics matter during commissioning
Common Failure Modes
| Symptom | Likely Cause | First Check |
|---|---|---|
| Discovery works on one subnet only | Broadcasts stop at the router | BBMD or FDR design |
| Tool sees device but BMS does not | Unicast-versus-broadcast response handling | Packet capture from the production BMS path |
| Reads fail after discovery works | Object access or routing mismatch | ReadProperty support and path validation |
| Intermittent sitewide visibility | Duplicate Device Instance or unstable network path | Device identity plan and capture evidence |
Tools & Diagnostics
| Tool | Type | Description |
|---|---|---|
| CAS BACnet Explorer | Explorer | Discovery, object browse, read/write tests, and quick proof of path behavior |
| Wireshark | Packet analyzer | Best tool for confirming broadcast scope, BBMD forwarding, and response direction |
| QuickServer | Gateway and diagnostics platform | Useful when BACnet/IP must be bridged to Modbus or another supervisory protocol while keeping one clean BACnet object model |