| Modbus RTU | Serial communication, commonly over a two-wire RS-485 bus | Binary frames with a slave address, function code, data field, and CRC error check | Source or destination protocol | Connecting meters, sensors, drives, controllers, and remote I/O devices | Baud rate, parity, stop bits, device address, bus termination, and wiring polarity must match across the serial network |
| Modbus ASCII | Serial links such as RS-232 or RS-485 | Human-readable hexadecimal characters enclosed by start and end characters; uses an LRC error check | Legacy serial interface | Older control systems where readable serial messages or slower communication are acceptable | It uses more characters and generally transfers data less efficiently than Modbus RTU |
| Modbus TCP | Ethernet using TCP/IP, normally through an RJ45 or industrial Ethernet connection | Modbus application data is carried inside a 7-byte MBAP header and TCP/IP packets; the serial CRC is not used | Ethernet-side protocol | Linking PLCs, supervisory software, industrial computers, and Ethernet-enabled instruments | Network addressing, TCP port 502, connection limits, timeouts, and firewall rules must be configured correctly |
| Modbus RTU to Modbus TCP | RS-485 on one side and Ethernet on the other | Maps serial register requests and responses into Modbus TCP messages while preserving function codes and register values | Protocol bridge | Allowing an Ethernet-based monitoring system to access existing serial field devices | The converter must manage serial timing, TCP connections, request queues, response timeouts, and exception codes |
| Modbus TCP to Modbus RTU | Ethernet on the control-system side and RS-485 on the field-device side | Removes the TCP/IP and MBAP transport information, then creates a correctly timed Modbus RTU frame with CRC | Remote device access | Connecting an Ethernet controller to legacy serial meters, actuators, or process instruments | One TCP client may need to communicate with multiple serial device addresses; polling order and serial response time affect performance |
| Modbus to CAN | RS-485 or Ethernet on the Modbus side and a Controller Area Network bus on the other side | Register reads and writes are mapped to CAN identifiers and data fields according to the gateway configuration | Cross-network gateway | Sharing industrial measurements or commands between Modbus equipment and CAN-based machinery | Register size, byte order, CAN identifier assignment, message priority, and update rate require explicit mapping |
| Modbus to Fieldbus | Modbus serial or Ethernet combined with a fieldbus network | Modbus coils, discrete inputs, input registers, and holding registers are mapped to fieldbus process data | Control-system integration | Integrating instruments or subsystems that use Modbus into a larger automation network | Data types, cyclic update time, diagnostic information, device profiles, and read/write permissions must be aligned |
| Modbus to OPC UA or MQTT | Serial or Ethernet Modbus connected to an IP-based software or cloud interface | Modbus register values are converted into named variables, structured data points, or publish/subscribe messages | Data and application gateway | Sending machine data to dashboards, historians, analytics platforms, or supervisory applications | Tag naming, timestamp quality, scan interval, security credentials, data type conversion, and network availability are essential |
| Any Modbus Converter | Depends on the selected interfaces, such as RS-232, RS-485, Ethernet, CAN, or another industrial network | Reads one protocol's message structure, interprets the requested data, and generates an equivalent message for the target protocol | Translation and isolation | Connecting equipment that uses different interfaces, speeds, addressing methods, or data models | Check electrical isolation, maximum bus length, supported function codes, register mapping, latency, diagnostics, and environmental rating |