Modbus Serial

See purchasing information for more details
modbus serial demo download

Product Overview

The Modbus Serial device driver works in conjunction with KEPServerEX to provide data exchange between OPC clients and Modbus Serial protocol compliant PLCs and other devices. KEPServerEX automatically optimizes your data acquisition based on client demand. Data integrity is ensured with our extensive error handling.

Special handling has been added to support the native memory formats of the OMNI Flow Computer including string support. Additional configuration parameters allow this driver to tailored to a wide range of Modbus Serial compatible devices, including JBUS.

The Modbus Serial driver now offers direct integration with Modicon Concept and ProWORX programming packages. If you are using either of these packages, you will be able to import the tags used in your PLC application directly into KEPServerEX. This time-saving step instantly makes all of the relevant PLC data available to your OPC client applications.

Resources

Performance

  • Ethernet Encapsulation
  • Supports the TSXCUSBMBP USB adapter for the Modbus Plus Network
  • Modbus RTU Multi-drop Supported
  • Automatic Tag Generation
  • Supports Broadcast Messages using device ID 0
  • Full Address Range Support (0 - 65535)
  • Hex Addressing Support (0-FFFF)
  • User Definable Read Block Sizes
  • Adjustable Address Base (0 or 1)
  • Word Order Swapping for Floating Point and Longs
  • Byte Order Swapping on all 16 bit and 32 bit values
  • Adjustable RTS Flow timing for Radio Modems
  • Supports all memory types and data types
  • Support accessing Holding register memory as string data with HiLo/LoHi byte order
  • RTU Functions used: 01, 02, 03,04, 05, 06, 16
  • Supports tag import from Concept and ProWORX programming packages
  • Modem Support
    • Automatic Dial Configuration
    • Multiple Phone Number Management
  • Communication Serialization

Protocols

  • Modbus RTU Protocol

Supported Devices

  • Daniel S500 Flow Computer
  • Dynamic Fluid Meter
  • Elliot Flow Computer
  • Magnetek GPD 515 Drive
  • Modbus Compatible Devices
  • Omni Flow Computer (Enron Modbus)
  • TSXCUSBMBP USB Adapter

Available Languages

  • English
  • German
  • Japanese
  • Simplified Chinese

Release Notes

6.2.460.0

7/6/2017

  • Added Chinese language support.

6.1.601.0

4/4/2017

  • Removed redundant default setting from the Daniel S500 model.
  • Fixed an issue where array length was converted to hex when the address is specified as hex.
  • Increased the channel limit from 256 to 2048.

6.0.2107.0

11/15/2016

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

5.21.114.0

3/20/2017

  • Fixed an issue where the "First Word Low” setting under the Data Encoding device property for Daniel S500 model was always enabled.
  • Fixed an issue introduced in the 5.19 release where the decimal array length was converted to hexadecimal if the address format was specified as hexadecimal.

5.19.467.0

10/20/2015

  • Added support for padding addresses for both 5 digit and 4 digit format. If 5 digits or more are used, the address entered is padded to 5 digits (400001). If 4 digits or fewer are used, the address entered is padded to 4 digits (40001). This applies to all model selections except Omni and Daniel S500.

5.18.662.0

6/23/2015

  • Enhanced the driver to support Advanced Statistics tags, including "_CommFailures" and "_ErrorResponses".
  • Fixed an issue where switching models did not update controls availability.

5.10.205

11/13/2012

  • Updated the driver with the new Connection Sharing feature.
  • Fixed an issue where the RTS Delay and Inter-Request Delay settings were not respected during the write portion of a Read/Modify/Write transaction.
  • Fixed an issue where write tags were orphaned if extra bytes were received in the response to the read portion of a Read/Modify/Write transaction.

    Note: A Read/Modify/Write transaction occurs when writing to a bit within a register if "Holding Register Bit Mask Writes" is not used.

5.9.170

6/26/2012

  • Increased the character limit of the tag Description field from 64 to 255.
  • Added the new device-level internal tag "_FailedConnection" that indicates the driver failed on its attempt to connect to the device.

5.8.109.0

2/21/2012

Added support for Channel Serialization.

5.6.122.0

7/25/2011

  • Fixed a potential heap corruption issue (when an expandable buffer was being overwritten) by reading an Omni Custom Packet Tag. A maximum size of 250 bytes was assigned for an Omni Custom Packet Tag instead of allowing the tag data type to determine the buffer allocation size.

5.4.131.0

10/28/2010

  • Increased the number of channels from 100 to 256.

5.2.133.0

2/18/2010

  • Fixed issue with write-only tags introduced in 5.0. The value of the tag was not updating when a value was written to it. The correct value was written to the device, just not displayed in the data client.

5.1.71.0

10/21/2009

  • Added string data type support for Internal Registers.
  • Added block string read support.

What Is a Driver?

KEPServerEX is more than an OPC server—it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.

A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices.

Drivers may be licensed individually or in suites. Additional drivers can be licensed on demand as connectivity needs evolve.


© PTC Inc. All Rights Reserved.