Bringing BACnet MS/TP devices onto an Ethernet network is a routine need in building automation. A pattern keeps surfacing in the Building Automation community: someone buys a cheap RS485-to-Ethernet adapter, wires it up, and finds that the BMS software receives nothing. The confusion is the same in every case — a working physical layer does not imply a working protocol layer. The two-pin screw terminal and the half-duplex electrical spec both check out, yet the link is silent. Almost everyone who touches MS/TP for the first time runs into the same trap, often after a long session of swapping cables, baud rates, and termination resistors.

Physical Layer Works, Protocol Layer May Not

RS485 only defines electrical characteristics — two-wire differential, half-duplex, up to 32 node loads. MS/TP runs on top of that physical layer and defines a full master/slave, token-passing bus protocol. Each frame carries a 0x55 preamble, destination and source addresses, a frame type, and a CRC. Master stations take turns holding the token before issuing requests; slave devices only respond when addressed. Typical MS/TP links in mid-size buildings operate at 38.4 kbps or 76.8 kbps with one or two masters and a few dozen field controllers — variable air volume terminals, fan coil units, lighting panels, smart meters — distributed across floors.

A plain RS485 to Ethernet converter works in a simple way — wrap serial bytes into TCP or UDP on one side, unwrap them on the other, and drop them back onto the serial line. It does not parse MS/TP frame headers, does not participate in token polling, and does not understand BACnet application-layer services such as ReadProperty or Who-Is. The end result: the converter forwards the BMS-side request bytes onto the bus verbatim, and the MS/TP master does not recognize the format. The link stays silent, and the operator is left wondering whether the adapter is faulty or the wiring is wrong.

Three Things a Plain Converter Cannot Do

Breaking that apart makes the gap more concrete:

• Frame recognition. MS/TP frame headers, CRC checks, and frame type fields all need to be identified. In transparent mode the converter only moves a byte stream — it cannot even mark where one BACnet frame ends and the next begins, so the host cannot tell valid frames from bus noise.
• Token arbitration. The MS/TP bus depends on master stations taking turns holding the token to issue requests. A forwarder is a passive relay with no token state machine, so it cannot act as a master or join the polling cycle. If the host needs to poll the bus actively, plain transparent mode will not get it there.
• Application-layer parsing. A BMS does not want a byte stream — it wants object properties such as "the airflow setpoint of a specific VAV terminal" or "the current zone temperature." Transparent mode only lifts bytes onto TCP; parsing still has to happen somewhere upstream, against a complete BACnet object model.

Any of these three tasks either falls on the host (with a BACnet protocol stack running on the PC or BMS server) or on a dedicated MS/TP-to-BACnet/IP router. An ordinary serial device server does not take them on, and that is by design — its job is to move bytes, not to speak the protocol.

Two Practical Approaches

If the converter is just a byte mover, the selection logic reduces to one question: which segment handles the protocol?

Approach one — protocol parsing lives on the host. This setup needs a stable transparent channel, with the BMS software carrying its own BACnet stack. For small projects with limited device counts, and where the host can run 24/7, this is the lowest-cost route. PUSR's USR-TCP232-304 fits this role: a single-port RS485 to Ethernet converter with TCP Server/Client, UDP, virtual COM, custom RFC2217, heartbeat packets, and registration packets — everything needed for a transparent channel between the BMS and the MS/TP bus.

Approach two — protocol conversion or data aggregation sits at the edge. This calls for industrial-grade reliability, long service life, and remote operations. On building sites, HVAC cabinets, VAV terminals, and lighting panels are typically installed above ceilings or in equipment closets, with hard requirements on wide temperature, EMC, wide input voltage, and a hardware watchdog. PUSR's USR-N510 (single-port), USR-N520 (two-port), and USR-N540 (four-port) belong to this tier: TCP/UDP/HTTPD Client modes, a Modbus RTU-to-Modbus TCP gateway with multi-host polling, up to 128 data points, and address mapping, MQTT 3.1.1, SSL/TLS encryption, two-way certificate authentication, a wide 5–36 V DC input with reverse polarity protection, and a built-in watchdog. If building data later needs to converge on a cloud platform for energy or operations analytics, the MQTT + JSON edge-computing channel can be used directly, with no extra glue code.

N510, N520, and N540 each come in two versions: RS232/485/422 or full RS485. BACnet MS/TP is 100% RS485, so the full-RS485 version can be taken as the default — higher node count, stronger interference immunity, and no last-minute device swaps on site when the field turns out to be purely MS/TP.

What to Look at When Selecting

• Protocol-side coverage. If the host already ships a mature BACnet stack, the 304 is enough. If the host is resource-tight or edge autonomy is required, the N5X0 series is the better fit.

• Port count. A single MS/TP bus typically needs one port; multi-bus layouts split by floor or subsystem call for 2-, 4-, or 8-port units, with one port per bus.

• Bus stability. Building sites are noisy — variable-frequency drives on AHUs, elevators with regenerative drives, large UPS units — so wide input voltage, a hardware watchdog, and EMC-rated hardware at industrial grade are the safer choice for a 24/7 install.

• Remote operations. For multi-building or multi-campus portfolios, cloud management (remote firmware upgrade, batch configuration push, link diagnostics) cuts the number of site visits needed over the equipment's lifetime.

• Compliance and certification. Tenders often require marks such as CE and FCC. Industrial-grade units ship with the relevant set already in place, which avoids last-minute sourcing changes at the procurement stage.

One closing sentence: whether a standard RS485 to Ethernet converter can carry BACnet MS/TP comes down not to "can an RS485-to-network adapter be bought" but to "which segment parses the protocol." Once that is clear, the "cheap adapter" trap is easy to avoid.