KEPServerEX 4.5 Release Notes

Posted on 281 views

KEPServerEx is a 32-bit windows application that provides a means of bringing data and information from a wide range of industrial devices and systems into client applications on your windows PC. KEPServerEx falls under the category of a “Server” application. It is very common to hear the term “client/server application” in use across many software disciplines and business segments. In the industrial market, it has usually come to mean the sharing of manufacturing or production data between a variety of applications ranging from human machine interface software and data historians, to large MES and ERP applications.

KEPServerEX Release Notes (4.500.465) July 20, 2009
Driver Enhancements/Fixes
BACnet Driver

  • Fixed channel wizard issue that prevented user from moving to next page, incorrectly indicating that another channel was configured with same NIC and port.
  • Fixed an issue with processing “read property multiple” responses from certain brands of hardware, which resulted in toggling quality of all items associated with an object and repeated “device not responding” errors.

Beckhoff Driver

  • Fixed anomaly where writes to IO could fail, and reads from IO would not always report the correct values.

ControlLogix Ethernet Driver

  • Fixed performance issue for DH+ Gateway, ControlNet Gateway, ENI and Micrologix models where writes and priority reads could be starved in a low bandwidth/slow response time scenario.
  • Fixed issue where the driver generated names for imported array tags with ‘CONDENSED’ tag hierarchy incorrectly. The generated names were instead in the EXPANDED format.
  • Fixed L5K auto tag generation issue where L5K ENCODED_DATA and FBD_ROUTINE blocks were not being properly ignored.
  • Fixed issue where the driver could occasionally read/write empty data for string tags. This only happens for projects with multiple channels.

DNP Drivers

  • Fixed memory leak which would occur when buffering device data that was never requested from a client application.
  • We now respect changes to the Default Operate Mode setting when performing writes. Previously, we would obtain the setting on startup and use that mode for writes regardless if the user modified this setting.
  • Added support for blocking explicit reads
  • Fixed issue where we would set a Good Value for analog input deadband items that were non-existent in the device.
  • Fixed issue where under certain conditions we would continually post ‘Device Not Responding’ messages to the event log.
  • Fixed issue where the driver would cause an application fault when deleting a device and tags were still being processed by the communications stack.
  • Fixed issue where under certain circumstances we would send 2 initial updates for a tag with differing values (first incorrect, second correct).

UCON Driver

  • Fixed issue where the Event counter was not incrementing for unsolicited transactions when a command preceded the initial read response.
  • Fixed issue with ASCII Real and ASCII Real (packed 6-bit) formats where legacy projects failed to load a default value for the “Use decimal comma in place of decimal point” option in the format properties. This resulted in projects behaving as though it was set even though the check box was not marked. Viewing the dialog box would set the property to the default value (unchecked/false).
  • Fixed issue with ASCII Real and ASCII Real (packed 6-bit) formats where non-negative numbers with negative exponents only displayed the exponent.

Idec Driver

  • Added support for “Extra Data Register” (D10000-D49999) for the MicroSmart model. For MicroSmart modules (non Slim Type CPU modules) that do not support the “Extra Data Registers” the driver will report a failure when reading/writing these registers.

SquareD Driver

  • Fixed issue where the driver was not parsing received data packet correctly when the route ID contained one or more nodes that were not equal to 255.

Yokogawa CX Ethernet

  • Fixed issue where would inefficiently time out on the device if the device returned an error code, rather than processing the error and immediately moving on to the next request

Leave a Reply

Your email address will not be published. Required fields are marked *

86 − = 80