Same BACnet application layer, two physically incompatible wires — and why a router, not a cable, is what bridges them.
It is easy to hear "MS/TP" and "BACnet/IP" and assume they are two competing building automation protocols, the way BACnet and Modbus are. They are not. Both carry the exact same BACnet application layer — the same objects, the same read/write services, the same data model a supervisory workstation or controller sees. What differs is everything underneath that: BACnet MS/TP (Master-Slave/Token-Passing) carries that application layer over RS-485 twisted-pair serial wiring, while BACnet/IPcarries the identical application layer over standard Ethernet. Both "speak BACnet" — but they are physically incompatible network types, and one cannot simply be wired into the other without a router in between.
MS/TP is a token-passing scheme: devices on a shared RS-485 twisted pair take turns holding a "token" that grants the exclusive right to transmit, one at a time, so two devices never talk over each other on the same wire. It runs at modest speeds — typically 76.8 kbps or slower — but the wiring itself is cheap, simple, and tolerant of long field runs, which is exactly why it's the standard choice for terminal equipment: VAV boxes, unitary controllers, fan coil controllers, dozens of them daisy-chained on one trunk. BACnet/IP instead frames that same BACnet application layer inside standard UDP/IP packets and rides ordinary Ethernet — the same switches, fiber, and cabling as the rest of the building's IT network — at speeds MS/TP was never designed for. That makes it the natural choice for the backbone: the segment connecting supervisory controllers, building-level control panels, and the workstation, where higher device counts and faster polling matter and the cost of Ethernet infrastructure is easily justified.
The BACnet application layer defines the data model — analog and binary objects, schedules, trend logs, the read and write services a controller exposes — completely independent of the wire underneath it. That separation is what makes both MS/TP and BACnet/IP legitimate, first-class BACnet options rather than one being a workaround for the other: a VAV box doesn't need Ethernet-grade speed or cost to report a damper position, and a supervisory controller polling forty pieces of equipment does need more bandwidth than RS-485 can offer. A BACnet/IP-to-MS/TP router's entire job is to translate the addressing and framing between the two network types — the BACnet Network Number and MAC addressing that let a message crossing from the IP side find the right device on the MS/TP segment and vice versa. It never has to translate the application-layer data itself, because that part was identical on both sides all along.
False, and it's one of the more common field mistakes on a controls job. "BACnet" describes the application layer that's shared — it is not a single uniform network you can plug any labeled "BACnet" device into. A device's physical wiring has to match what it's actually being connected to: an MS/TP device needs an RS-485 twisted-pair trunk, a BACnet/IP device needs an Ethernet drop, and the two are not interchangeable at the wire without a router translating between them. This trips up installers who assume that because a VAV controller and a supervisory panel both say "BACnet" on the spec sheet, they can simply be daisy-chained together — in reality, if one is MS/TP and the other is IP, a BACnet/IP-to-MS/TP router has to sit between them, or nothing on either side will ever see the other.
Explains that BACnet MS/TP and BACnet/IP are not two competing building automation protocols, but two different physical/network layers carrying the identical BACnet application layer — MS/TP over RS-485 serial for low-cost field-level device buses, BACnet/IP over Ethernet for the faster supervisory backbone — and why a router is required to bridge between them.
MS/TP (Master-Slave/Token-Passing) is BACnet's classic field-bus physical and link layer, running over RS-485 twisted-pair serial wiring. Devices on a shared trunk take turns holding a token that grants the exclusive right to transmit, avoiding collisions on the shared wire. Typical MS/TP speeds top out around 76.8 kbps, far slower than Ethernet, but the wiring is inexpensive, tolerant of long daisy-chained runs, and simple to install — which is exactly why it remains the standard choice for terminal-level equipment such as VAV box controllers, unitary controllers, and fan coil controllers, often dozens of them multidropped on a single trunk segment.
BACnet/IP carries the identical BACnet application layer — the same objects, properties, and services — inside standard UDP/IP packets over ordinary Ethernet. That gives it far higher throughput than MS/TP and lets building automation traffic share the same switches, fiber, and cabling infrastructure as the rest of the building's IT network. This makes it the natural fit for the backbone tier: supervisory controllers, building-level control panels, and operator workstations, where higher device counts, faster polling, and IT-standard infrastructure matter more than minimizing per-device wiring cost.
Because MS/TP and BACnet/IP are physically incompatible network types — different connectors, different signaling, different framing — a device on one cannot be wired directly into the other, no matter how compatible their BACnet application layer is. A BACnet/IP-to-MS/TP router sits at the boundary and translates addressing and low-level framing between the two network types, using BACnet's Network Number scheme to route messages to the correct device regardless of which side of the router it lives on. Critically, the router does not need to translate the application-layer data itself — the objects, properties, and services are already identical on both sides — it only bridges the physical/network layer difference.
No. RS-485 (used by MS/TP) and Ethernet are electrically and physically different network types — different connectors, voltage levels, and frame formats. A BACnet/IP-to-MS/TP router (or a BACnet Building Controller with routing capability) has to sit between the RS-485 trunk and the IP backbone; there is no direct wiring path between them.
No — that's the whole point of BACnet separating the application layer from the physical layer. The router only translates addressing and datalink framing between the MS/TP and IP sides using BACnet's Network Number and MAC addressing scheme. The objects, properties, and services being read or written are identical on both sides and require no data translation at all.
It's technically possible on some newer controllers, but MS/TP over RS-485 remains far cheaper to wire at the terminal-unit level — a single low-cost twisted pair can daisy-chain dozens of field devices, versus running (and powering, in the case of PoE) an Ethernet drop to every VAV box. Most designs still use IP for the backbone and MS/TP for the field tier specifically because that split matches cost to where speed is actually needed.
It depends on segment length, wire gauge, baud rate, and the specific transceivers used, but MS/TP segments commonly support on the order of 32 devices (sometimes more with repeaters or higher-drive transceivers) before signal integrity or token-rotation time becomes a practical limit — segment sizing is typically checked against the controller and cable manufacturer's specifications rather than assumed.
Try our Smart Buildings Studio
More calculators, simulators, and guides for this discipline.