In a building that has been running for years, the JACE is already in place and the MS/TP bus carries a string of controllers and terminal boxes. The requirement now is to change a controller parameter remotely, read a few points, or leave a commissioning channel open for a field engineer. The first reaction is usually to ask whether one more dedicated wireless adapter has to be bought. Devices of this class are called RS485 to Ethernet converter, and whether one can take over the job depends on whether the target is "a network" or "a specific device".

1. First, decide which layer the connection targets

In a BACnet system, the JACE does the routing work: one side is the MS/TP bus, the other is Ethernet, and BACnet messages are forwarded between them, with the network number identifying the bus side. When the configuration software connects, it sees an addressable BACnet network rather than a raw byte stream.

An RS485 to Ethernet converter does something different: it moves bytes from the serial line into a TCP connection. What is sent and received is a byte stream, with no protocol interpretation.

2. If the JACE can carry it, use the JACE first

Where the target devices are BACnet controllers and the configuration software itself speaks BACnet/IP, the JACE is usually enough, provided three things are set up: the IP port is enabled on the JACE, the network number for the bus side is registered in the routing table, and the software side is pointed at the JACE address plus that network number.

This route adds no hardware and costs the least. The divergence starts where it cannot reach.

3. Cases the JACE cannot cover

• Target devices that do not speak BACnet.Modbus RTU meters, water meters, UPS units and VFDs in the electrical cabinet, along with proprietary protocol ports on chillers, mean nothing on an MS/TP bus, and the JACE does not translate them into BACnet on its own.

• Connections to a device's own service port.Beyond the BACnet port, many controllers have a service or console port running a vendor-proprietary serial protocol. The JACE does not forward those messages.

• No JACE on site yet.A new panel is in factory commissioning with only bare controllers inside, or the JACE sits in another building, where running 485 cable over would mean cutting through walls.

• Debug actions that should not run on a live system.Clearing a database or editing points in bulk carries risk for the whole building if it runs on a JACE that is serving the site.

• Distance and node count against the limits of 485.Reading data from a serial chain across buildings or several floors runs into the distance limits of the serial bus itself.

4. Three checks on whether a converter on hand is enough

• Protocol layer.A converter that only handles transparent transmission and Modbus cannot enter configuration software that expects to recognize BACnet messages; a datasheet mentioning only Modbus and no BACnet layer usually falls into this category.
• Whether the software side has a driver.The same class of adapter can be recognized directly by the software when a dedicated PC-side driver is present, because the driver supplies the protocol layer; a pure network converter has no such layer to fall back on.
• Whether messages or bytes are being carried.Writing an application to send and receive Modbus RTU, using proprietary ASCII commands, or simply needing a transparent channel — a converter fits. Expecting it to perform device discovery and point read/write on behalf of the software — it does not.

All three point to the same conclusion: a converter moves bytes, not meaning.

5. How to deploy one where it does fit

Taking single-port RS485 to Ethernet as the example, the USR-TCP232-304 provides one RS485 port and one 10/100Mbps RJ45 port, with baud rates from 600 to 230.4Kbps, data bits of 5 to 8, stop bits of 1 or 2, and parity options of None, Odd, Even, Mark and Space, which covers most legacy controllers. Working modes include TCP Server, TCP Client, UDP Server, UDP Client and Httpd Client, and up to 16 connections are accepted in TCP Server mode, enough for several people to commission at the same time.

A few items that save effort: Modbus RTU to Modbus TCP conversion with multi-host polling lets supervisory software find devices over TCP; virtual COM software maps the remote serial port to a local COM port so existing serial applications need no changes; RFC2217-like support allows baud rate and other serial parameters to be changed from the network side while running, so uncertain parameters do not require repeated site visits; heartbeat and registration packets show whether a connection is still alive and distinguish between clients; no-data restart recovers the link when it stalls. On the hardware side, power is DC5.07.0V through a DC5.5×2.1mm connector at 150mA@5V; the enclosure measures 73.2×70×25mm and mounts on a wall; the operating temperature range is -2575℃; EMC passes IEC61000 Level 3 (surge, ESD, EFT), and the unit is CE certified.

A fixed configuration order is worth adopting: set a static IP on the web page first, align baud rate, data bits and parity with the field controller item by item, then choose the working mode. For remote scenarios, an outbound TCP Client connection passes firewalls more easily than letting the outside connect in.

6. Details that tend to cause rework

• Use twisted-pair shielded cable on 485, daisy-chain it rather than star-branching, and fit termination resistors at both ends of the bus.

• Baud rate, data bits and parity must match the controller exactly, and changes take effect after a restart.

• Do not map the converter's port straight to the public internet; route remote access through a VPN or gateway and close it when commissioning ends.

• The converter covers only the serial-to-Ethernet segment; how points are parsed and whether they enter a supervisory system remain separate decisions.

The judgment can be reduced to one line: for BACnet controllers, with software that speaks BACnet/IP and a reachable JACE, configure the IP port and routing table on the JACE first; for Modbus devices, proprietary serial protocols or device service ports, adding an RS485 to Ethernet converter is the more direct route.