Modbus RTU Server Serial (Modbus Unsolicited Serial)

Manufacturing Suite Get Modbus RTU Server Serial (Modbus Unsolicited Serial) as a part of this suite. Learn More Modbus Suite Get Modbus RTU Server Serial (Modbus Unsolicited Serial) as a part of this suite. Learn More

Product Overview

The Modbus RTU Server Serial device driver provides data exchange between OPC clients, Modbus Client, and Modbus RTU networks. The Modbus RTU Server Serial driver allows a OPC client application to appear as 1 to 247 Modbus RTU devices on the network. The server mode allows Kepware to receive data by exception from a Modbus RTU Client. Typical applications include connectivity with larger DCS systems that utilize Modbus RTU. As with any server device, the Modbus RTU Server driver will only transfer data when being read or written by a RTU client. Data integrity is ensured with our extensive error handling.

  • Word Order Swapping for Floating Point and Longs
  • Modbus RTU Multi-drop Supported
  • Full Address Range Support (0 - 65535)
  • Hex Addressing Support (0-FFFF)
  • Can appear as Multiple Modbus Server devices
  • Data Modbus RTU functions accepted by Server: 01, 02, 03, 04, 05,
  • Adjustable Address Base (0 or 1)
  • Station numbers selectable from 1-247
  • Modbus RTU Protocol
  • Any Modbus compatible devices
  • English
  • German
  • Japanese
  • Simplified Chinese
  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Clients
  • SuiteLink and FastDDE for Wonderware



  • Removed non-inclusive terms out of respect for users of our software. Renamed this driver in compliance with updated terminology.



  • The driver no longer sends a response to an invalid transaction.



  • Added Chinese language support.



  • Added German language support.
  • Added Japanese language support.



  • Fixed an issue where a buffer overflow could result in the driver writing to erroneous coils.



Increased the character limit of the tag Description field from 64 to 255.


  • The driver will now check for License Activation upon receiving unsolicited communications.


  • Added string data type support for Internal Registers.