Modbus Ethernet

See purchasing information for more details
modbus ethernet demo download

Product Overview

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

Kepware's implementation of the Modbus Ethernet driver supports master and slave operations simultaneously. The slave mode allows the server to receive data by exception from other Modbus Ethernet devices.

The Modbus Ethernet 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 directly 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

Features

  • Automatic Tag Generation
  • Supports Multiple PLCs via IP addressing
  • Supports Modicon Ethernet to Modbus Plus bridging
  • Supports Multiple or Single socket usage for better gateway resource management
  • Supports Tag import from Concept and ProWORX programming packages
  • Supports Advanced Statistics Tags, including _CommFailures and _ErrorResponses
  • Supports Memory Accesses to 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
  • 0xxxx - Output Coils, 1xxxx - Input Coils, 3xxxx - Internal Registers, 4xxxx - Holding Registers
  • All data types and arrays are supported

Protocols

  • Modbus Ethernet

Supported Devices

  • Applicom: Generic Modbus, TSX Premium, TSX Quantum
  • Fluenta FGM
  • Instromet
  • Mailbox
  • Modbus Ethernet
  • Roxar RFM

Available Languages

  • English
  • German
  • Japanese
  • Simplified Chinese

Application Support

  • 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) Version 1.01
  • SuiteLink and FastDDE for Wonderware

Release Notes

6.2.460.0

7/6/2017

  • Added Chinese language support.

6.1.601.0

4/4/2017

  • Fixed an issue where array length was converted to hex when the address is specified as hex.

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 introduced in the 5.19 release where the decimal array length was converted to hexadecimal if the address format was specified as hexadecimal.

5.20.396.0

5/3/2016

  • Added support for expanded blocking modes for CEG device model.
  • Changed the driver behavior to no longer send a FIN in response to a request timeout.
  • Increased the maximum channel limit from 256 to 1024.

5.19.467.0

10/20/2015

  • Added support for Advanced Statistics Tags, including _CommFailures and _ErrorResponses.
  • 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 Applicom and Fluenta.
  • Improved message logging to include socket errors in the Event Log.

5.18.662.0

6/23/2015

  • The driver now reports an error when receiving a message length in the Modbus header that is less than the actual message length.
  • Added support for "Double Precision Unsigned Long" encoding of Ints and UInts.

5.16.722.0

10/21/2014

  • Added the new CEG model and made protocol changes to slave mode to support a maximum of 500 register and 8000 coil tag reads.
  • Added the new CEG model and made protocol changes to slave mode to support a maximum of 500 register and 8000 coil tag reads.
  • The driver will now attempt a retry on receipt of a send socket error. Prior to this change, certain devices could respond with a socket error after the initial connection and cause an unnecessary disruption in communication with that device.
  • Fixed an issue introduced in KEPServerEX version 5.14 where tags on one or more devices may stop being serviced if another device under a channel has been deleted.

5.15.585.0

7/22/2014

  • Changed the driver's minimum Timeout setting from 50 milliseconds to 10 milliseconds.
  • Fixed an issue where a buffer overflow could result in the driver writing to erroneous coils.
  • Added support for importing string type tags via the Variable Import Settings page.

5.14.493.0

3/4/2014

  • Fixed an issue involving register block sizes of 1 to 4, or coil block sizes of 8 or 16 when using packed coils. The issue either resulted in a failure to add tags from a client or in tags being set to bad quality because of a malformed packet.

5.14.491.0

2/18/2014

  • The driver now closes socket connections when a device is disabled.
  • Created a new CEG model.
  • Fixed an issue where some errors returned by the device were not being properly reported by the server.
  • Fixed an issue resulting in bad quality data for 32 and 64 bits tags residing in the upper block boundary.
  • Fixed an issue resulting in bad quality data for packed coil tags defined at the upper block boundary.

5.12.140.0

6/18/2013

  • Updated the driver to change the unsolicited communications timeout value from -1 to 0 (if applicable) when loading a project. This invalid value may be present in projects that were saved using older driver versions, and will invoke an error pop-up message after the Unsolicited tab is viewed in Device Properties.

5.10.205

11/13/2012

  • Added support for tag-level Byte and Word order swapping to the Applicom device model.
  • Fixed address parser issues occurring in the Applicom device model where various invalid characters were accepted at the end of a valid address. Also fixed an issue where the 'D' and 'F' address types were allowing bit within word syntax even though the driver does not support bit in 32-bit values.

5.9.170

6/26/2012

  • Increased the character limit of the tag Description field from 64 to 255.
  • Fixed an issue where the driver was posting continuous "Failed to start unsolicited communications messages" in the Event Log when Port 502 was in use by another application at startup.
  • 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.

Note: Channel Serialization is not supported for unsolicited devices or mailbox model types.

5.7.84.0

10/24/2011

  • The "Use holding register bit mask writes" setting is now disabled by default for the Applicom sub-model type TSX Premium.
  • Added Boolean support for the "%M" and" %MX" syntax.
  • Added " %MWaaaa:Xb" to read a bit in a word (in addition to the current "%MWaaaa.b").
  • Added the ability to append an 'H' or 'L' to the end of an Applicom string address when defining byte order.
  • Fixed an issue where concurrent writes to multiple bits within the same register were not being retained if the channel was configured to use more than one socket per device and the device property "Use holding register bit mask writes" was unchecked.
  • Corrected Applicom string address syntax to use string length as length in words, not bytes.

5.6.122.0

7/25/2011

  • Added an Applicom model type to support Applicom-centric address syntax for Modbus Ethernet enabled devices. Selecting the Applicom model in the Device Wizard prompts a "Sub-Model" dialog that includes options for "Generic Modbus," "TSX Premium," and "TSX Quantum."

5.5.94.0

2/18/2011

  • Fixed an issue with unsolicited connections management and expanded the maximum unsolicited socket connections from 32 to 256.
  • Added a setting that allows users to select whether the driver will close the socket on timeout.
  • The driver will now check for License Activation upon receiving unsolicited communications.

5.4.131.0

10/28/2010

  • In a fix carried over from a patch to 4x, fail now tags immediately if the packet can't be transmitted (instead allowing retry logic to execute).

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.
  • Allow global settings that control unsolicited port and protocol to change on the fly.

5.1.71.0

10/21/2009

  • Added string data type support for Internal Registers.

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.