5.13.191.0

Added the new "Max Timeouts" property (located in the Communications tab of Device Properties).

Fixed an issue where a Disable Unsolicited Request would not be sent when only one or two of the classes are configured with Unsolicited Messages disabled and no class is configured with Unsolicited Messages enabled.

5.12.140.0

6/18/2013

Addressed a security vulnerability that could allow a master station to be sent into an infinite loop by sending a specially crafted TCP packet or through serial communications. A successful attack exploiting this vulnerability could allow an attacker to put the master station into an infinite loop, causing a denial-of-service condition. The master station (KEPServerEX runtime service) must be manually restarted to recover from the loop condition.

Fixed an issue with g70v3 Open File requests, where the File Size and Time of Creation fields were not being initialized properly when the request was to open a file for writing on the slave.

Corrected an issue introduced through a fix in server version 5.10 in which events would continue to play back when a device was in an error state. Errors other than Device Not Responding (DNR) were not being considered. When event play back is enabled and the event poll times out while communicating, the .Value and .Timestamp tags will receive BAD quality (which was the previous behavior).

Fixed an issue introduced in server version 5.10 where integrity and/or event polls would not occur on schedule if channel serialization was in use with many .Explicit Tags.

Corrected an issue where an "Initialization Completed" message would be posted when no communications had occurred with the device.

Added support for legacy devices that use a local time zone adjusted with time reference instead of the UTC time base in events and during time synchronization.

Converted the Communications device property page to a grid control.

Fixed an issue where processing too many continuous internal/cache tags may have delayed the processing of device tags (especially when Channel Serialization was in use and devices were not communicating).

Fixed a rare issue where an erroneous file transfer failure message could be posted along with a file transfer completed successfully message when the file transfer was successful.

Corrected an issue where event play back paused during TCP connection attempts.

Corrected an issue where event play back paused while the device was demoted.

5.11.250.0

3/5/2013

Fixed an issue where the server could become unresponsive during automatic tag generation. This problem was introduced in the 5.10 release.

Fixed an issue where the driver failed to report an Event Log error message if the socket bind failed. This message failure occurred for bind failures where the protocol selected was UDP and the optional source port was set to a non-zero value.

Added an error message to be posted when a tag fails due to the DNP flags containing an exception condition. The error message will list the actual DNP flags byte in hexadecimal format as well as a comma delimited string listing the exceptions. An example of the message is as follows: Unable to read tag '1.0.0.Explicit' on device 'Channel1.Device1'. Device indicates one or more exception conditions (DNP flags byte='0x28' - 'Offline, Remote Force, Chatter Filter').

Fixed an issue where on-the-fly changes to channel properties that affect the socket did not consistently force a socket reconnect.

Fixed an issue where no 'Device Not Responding' message was logged and tags did not show Bad quality when the keep-alive request timed out and the project was configured with no event or integrity polling and no explicit read tags.

Fixed an issue where tag quality was not updated after disabling the Enable Data Collection property.

5.10.205

Fixed an issue where collected events did not continue to playback when the device was in an error state.

Tag quality will be Bad if the device error state continues after playback completes.

During device demotion, tags will have Bad Quality and no playback. After the device is promoted, tag quality will be Good and playback will continue.

Fixed an issue where collected events were incorrectly deleted from the driver's cache after specific communication failures.

Resolved an issue where the Auto-Demotion settings in device properties were not used on startup.

5.9.170

6/26/2012

Added the new internal tag "_TimeSyncStyle".

Fixed an issue where the driver would fail to send confirmations to unsolicited responses. This occurred if the slave failed to respond to a Link Status Request, and instead sent its own Link Status Request.

5.8.109.0

2/21/2012

Updated refresh logic to improve usability with projects that reference more than a hundred channels.

5.6.122.0

7/25/2011

DNP3 Enhancements for Phase-III support of WITS specification include File Control and Activate Configuration

On restart, Events received in the response to the initial integrity poll are no longer lost when the response did not complete within the response timeout.

Added an event message to report when the session has completed startup.

Added support for device auto-demotion.

Added an event message to report when an Enable Unsolicited Messaging request fails, and when an item is demoted/promoted. Added the ability to post an informational message when certain IIN bits are set in a response. Improved tag cleanup.

Added an event message to report when LAN Time Sync write to g50v3 is not supported.

To correctly open 4x-based projects, modified the XML schema transform file to check for out of range values and/or to assign defaults for the following channel and device properties: Protocol, DestinationIP, ResponseTimeoutMilliseconds, RequestTimeoutMilliseconds, UnsolicitedModeClass1, OperateMode, and EnableFeedbackPollAfterWrite.

Resolved an issue where items might not clean up properly when a client disconnected from the server if the items were in a bad quality state due to an non-responsive RTU.

• 70.<file index>.LocalFileName (on Master station)

• 70.<file index>.RemoteFileName (on RTU)

• 70.<file index>.Download

• 70.<file index>.Upload

• ActivateConfig

5.5.94.0

2/18/2011

Added support for writing to Device Attributes (Object Group 0). This feature is required to meet the DNP WITS standard.

Added support for writing to Data Sets (Object Group 87). This feature is required to meet the DNP WITS standard.

The driver now supports the ability to play back Data Set snapshot data.

New settings were added to the Device Properties page that allow for users to ignore forced flags when setting quality.

Fixed issues with loading legacy server (.xml) project files.

Fixed an issue where the first buffered event after startup was never displayed when the Playback Rate was shorter than the tag's Update Rate.

A "Device Not Responding" message will no longer be reported in certain situations where the device was actually communicating.

Fixed an issue where the driver was reporting "Failed to initialize communication stack" in situations where serialization was enabled.

Improved channel management when communication errors are encountered during startup.

Fixed an issue where data set CTLS and CTLV element types were shown as having bad quality.

Fixed an issue where Communication Serialization and Aggressive Mode Authentication were enabled.

Added informational message to report the number of data set tags per data set added during auto tag generation.

5.4.131.0

10/28/2010

Added Keep-Alive Interval device property to the Communication page as well as an Event Log message to warn the user if loading an XML project discovers a Keep-Alive interval configured for a UDP channel.

Enhancements for Phase I support of WITS specification include the following.

5.3.118.0

Featured Suites

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.