| 1 | Modbus RTU-to-TCP Gateway | Legacy device integration | Modbus RTU ↔ Modbus TCP | RS-485 on the serial side; Ethernet on the network side | Master-to-slave request forwarding, register mapping, exception-code forwarding, and serial parameter configuration | Modbus TCP normally uses TCP port 502. Modbus RTU uses binary frames with device address, function code, data, CRC, and a silent interval between frames. | Check the number of serial ports, supported slave devices, response-time handling, and whether simultaneous TCP clients are required. |
| 2 | Modbus TCP-to-RTU Gateway | SCADA and PLC access | Modbus TCP client requests ↔ Modbus RTU serial requests | 10/100 Ethernet; RS-485 or RS-232 serial port | MBAP-header processing, unit-identifier routing, function-code translation, and serial polling control | Modbus TCP replaces the RTU CRC with an MBAP header containing a transaction identifier, protocol identifier, length, and unit identifier. | Verify whether the gateway supports the required TCP client count, serial baud rate, parity, stop bits, and unit-ID range. |
| 3 | RS-485-to-USB Modbus Adapter | Engineering and maintenance | Computer application ↔ Modbus RTU | USB host connection; two-wire RS-485 transceiver | Transparent serial communication for reading coils, discrete inputs, input registers, and holding registers | RS-485 commonly uses a balanced two-wire bus and supports multidrop communication. USB adapters generally require an operating-system serial driver. | Use a galvanically isolated version where ground-potential differences, long cable runs, or electrical noise may damage the computer or disturb communication. |
| 4 | Modbus RTU Repeater and Isolator | Long or noisy RS-485 networks | Modbus RTU segment ↔ Modbus RTU segment | Isolated RS-485 ports, usually with screw-terminal connections | Signal regeneration, electrical isolation, bus-segment extension, and noise reduction | It does not translate Modbus data into TCP; it regenerates the serial signal and preserves the RTU frame format and timing requirements. | Check isolation voltage, automatic direction control, termination requirements, biasing, maximum segment length, and device-count limits. |
| 5 | Modbus TCP-to-TCP Router or Bridge | Separated Ethernet networks | Modbus TCP network ↔ Modbus TCP network | Dual Ethernet ports or routed Ethernet interfaces | TCP connection forwarding, subnet separation, unit-ID routing, access control, and network segmentation | Both sides use Modbus TCP messaging and normally communicate through TCP port 502; no RTU CRC conversion is required. | Evaluate routing rules, firewall behavior, simultaneous connections, network redundancy, and cybersecurity controls for industrial Ethernet. |
| 6 | Modbus RTU-to-RS-232 Converter | Single-device serial connection | RS-485 Modbus RTU ↔ RS-232 serial communication | RS-485 on one side; point-to-point RS-232 on the other | Transparent byte forwarding, baud-rate matching, parity configuration, and direction control | RS-232 is intended for point-to-point links, while RS-485 is designed for multidrop buses. The converter changes the electrical interface, not the Modbus application protocol. | Choose this type when a legacy controller has an RS-232 port and the field device uses Modbus RTU over RS-485. |
| 7 | Multi-Serial Modbus Gateway | Large mixed-device installations | Multiple Modbus RTU or ASCII channels ↔ Modbus TCP | Several isolated RS-485, RS-232, or RS-422 ports; Ethernet uplink | Independent serial settings, channel-to-unit routing, polling management, register mapping, diagnostics, and TCP server operation | Modbus ASCII uses ASCII characters and an LRC check, whereas Modbus RTU uses binary data and CRC. Each serial channel can require different communication parameters. | Confirm per-port isolation, maximum concurrent connections, routing flexibility, diagnostic counters, and the gateway's maximum register or transaction capacity. |