What is the difference between a serial device server and a protocol gateway?

A serial device server tunnels raw serial bytes over TCP/UDP without understanding the protocol content. A protocol gateway performs protocol-level conversion, such as translating Modbus RTU frames to Modbus TCP frames, handling CRC removal, MBAP header insertion, and transaction ID management. Protocol gateways provide more reliable conversion for known protocols.

How do I configure the inter-character timeout for Modbus RTU conversion?

The Modbus RTU specification defines a frame delimiter as 3.5 character times of silence. At 9600 baud, one character (11 bits with start, 8 data, parity, stop) takes 1.146 ms, so 3.5 characters equals approximately 4 ms. Set the converter's inter-character timeout to this value so it correctly identifies frame boundaries and does not split a single Modbus message across multiple TCP packets.

Can I connect multiple RS-485 devices through one serial-to-Ethernet converter?

Yes, a single RS-485 port on a serial-to-Ethernet converter can communicate with up to 32 devices (or 247 Modbus addresses) on one multi-drop bus. The converter acts as the bus master, polling each slave device by address. Ensure proper RS-485 bus termination (120-ohm resistors at each end) and biasing for reliable multi-drop operation.

Serial to Ethernet Conversion in Legacy Systems

The Serial Legacy Challenge

Millions of industrial devices in active service communicate exclusively via serial interfaces, RS-232 for point-to-point connections and RS-485 for multi-drop networks. PLCs, RTUs, flow computers, protective relays, variable frequency drives, and analyzers installed over the past 30 years use serial Modbus RTU, DNP3, or proprietary protocols. These devices function reliably but cannot connect directly to modern Ethernet-based SCADA systems, cloud platforms, or IP networks. Serial to Ethernet conversion bridges this gap without replacing proven equipment.

Serial Interface Fundamentals

RS-232

RS-232 provides point-to-point communication between two devices at distances up to 15 meters (50 feet). Common baud rates range from 9600 to 115200 bps. RS-232 uses voltage levels of +/- 3 to 15 volts and supports hardware flow control (RTS/CTS) and software flow control (XON/XOFF). In industrial applications, RS-232 typically connects a single device (RTU, meter, analyzer) to a local HMI, programming terminal, or serial port on a communication server.

RS-485

RS-485 uses differential signaling for superior noise immunity and supports multi-drop networks with up to 32 devices on a single bus (247 with Modbus protocol addressing). RS-485 operates at distances up to 1,200 meters (4,000 feet) at 9600 baud, making it the standard for industrial serial networks. Two-wire (half-duplex) RS-485 is most common in industrial settings, where a master device polls slave devices sequentially using protocols like Modbus RTU.

Types of Serial to Ethernet Converters

Serial device servers: Standalone hardware devices with 1-16 serial ports and one or more Ethernet ports. Examples include Moxa NPort, Digi Connect, and Lantronix. These are the most common solution for industrial environments.
Protocol gateways: Convert between serial protocols (Modbus RTU) and Ethernet protocols (Modbus TCP) with protocol-level translation. More intelligent than simple serial tunneling.
Terminal servers: Present serial ports as virtual COM ports on a remote computer over the network, allowing legacy software to communicate with distant serial devices as if directly connected.
Embedded modules: Serial-to-Ethernet converter modules (e.g., Lantronix XPort, Digi ConnectCore) embedded directly into OEM equipment during manufacturing.

Conversion Modes

Raw TCP/UDP Tunneling

The converter encapsulates raw serial data bytes in TCP or UDP packets without protocol awareness. The remote end must reassemble the byte stream exactly as the serial device transmitted it. TCP mode guarantees delivery through retransmission but adds latency. UDP mode has lower latency but can lose packets. Raw tunneling is protocol-agnostic but requires careful timeout configuration to avoid fragmented serial messages being split across multiple TCP packets.

Modbus RTU to Modbus TCP Gateway

Protocol-aware gateways convert Modbus RTU serial frames to Modbus TCP Ethernet frames and vice versa. The gateway handles the protocol differences: removing the CRC from RTU frames and adding the MBAP (Modbus Application Protocol) TCP header, managing transaction IDs, and translating between RTU slave addresses and TCP unit identifiers. This mode provides the most reliable conversion for Modbus networks and is the recommended approach when all serial devices use Modbus RTU.

Virtual COM Port

Virtual COM port software installed on a computer creates a software serial port that maps to a remote serial device server over the network. Legacy SCADA software that expects a local COM port (COM1, COM3, etc.) communicates through the virtual port transparently. This mode requires driver software on the computer and adds complexity but preserves complete compatibility with legacy applications that cannot be modified to use TCP/IP.

Configuration Best Practices

Reliable serial to Ethernet conversion requires matching every serial parameter between the converter and the connected device. Mismatched settings cause garbled data, CRC errors, or complete communication failure.

Baud rate: Must match exactly. Common industrial rates: 9600, 19200, 38400, 57600, 115200 bps
Data bits: Usually 8 for industrial protocols. Some legacy devices use 7 data bits with even parity
Parity: None, Even, or Odd. Modbus RTU devices commonly use 8N1 (8 data, no parity, 1 stop) or 8E1 (8 data, even parity, 1 stop)
Stop bits: 1 or 2. Two stop bits are sometimes used with no-parity configurations per Modbus specification
Inter-character timeout: Critical for Modbus RTU. The standard specifies 3.5 character times of silence to delimit frames. At 9600 baud, this is approximately 4 ms. Configure the converter's inter-character timeout to match.
Response timeout: Allow sufficient time for the serial device to process the query and respond. Typical values: 500-2000 ms depending on the device and query complexity

Network Architecture Considerations

When deploying serial device servers on IP networks, assign static IP addresses and document the IP-to-device mapping. Place converters on a dedicated VLAN or subnet for security and traffic management. Configure the converter's firewall to accept connections only from authorized SCADA servers. For remote sites connected via WAN links, account for network latency in the SCADA polling timeout calculations. A Modbus RTU device expecting a response within 1 second may not receive it in time if the WAN round-trip adds 200 ms and the serial timeout is set too aggressively.

Troubleshooting Serial Conversion Issues

The most common issues are baud rate mismatches (verify with an oscilloscope or serial analyzer), incorrect RS-485 wiring (swap A/B terminals if no communication), and timeout misconfiguration causing fragmented Modbus frames. Use the converter's built-in diagnostic tools, including serial data logging and traffic counters, to identify problems. Many converters provide a web interface showing real-time serial port statistics including byte counts, framing errors, and parity errors. NFM Consulting specializes in integrating legacy serial field equipment with modern Ethernet and IP-based SCADA systems.