ASHRAE 135 (BACnet) — Clause 6.1

ASHRAE 135 (BACnet) — Annex J, Wiring Topology

BACnet MS/TP requires a strict daisy-chain (bus) topology with no stubs or tees. A stub creates an impedance mismatch that causes signal reflections, corrupting communications for all devices on the trunk. Branch devices must be wired in-line on the bus, not teed off.

ASHRAE 135 (BACnet) — Clause 12

Simply using the BACnet physical layer (MS/TP) does not make a device BACnet compliant. True BACnet compliance requires supporting standard BACnet object types (Analog Input, Analog Output, Binary Input, Binary Output, etc.) and standard services. A device using only proprietary objects cannot interoperate with other BACnet devices. Look for BTL (BACnet Testing Lab) certification.

ASHRAE 135 (BACnet) — Clause 12.2

BACnet device instance numbers must be globally unique across the entire BACnet internetwork, not just per trunk. Duplicate device instances cause routing conflicts and make one or both devices unreachable from the operator workstation.

ASHRAE 135 (BACnet) — Clause 9, MS/TP MAC addressing

MS/TP reserves MAC 255 for broadcast and 128-254 for slave devices; 127 is the very top of the master range. Parking a field controller at 127 forces max_master to its ceiling, so every token rotation polls the entire 0-127 address space looking for masters that aren't there — network performance craters. Keep field controllers in a contiguous low range and set max_master just above the highest used address.

ASHRAE 135 (BACnet) — MS/TP Physical Layer

BACnet MS/TP requires a daisy-chain (bus) topology, not star topology. Star wiring creates signal reflections and communication failures. Each device must connect in series on the bus.

ASHRAE 135 (BACnet) — Object Types

Connecting a 0-10VDC analog output signal to a binary (digital) input terminal will not control the device properly. Binary inputs only read on/off states. Analog signals must connect to analog input terminals for proportional control.