• Reduced unnecessary memory consumption by waiting to load Internal Tags on demand instead of loading them all at once on startup. The on demand portion is driven by Clients connecting to the server and requesting items. For certain applications this update could yield a 50% reduction in memory use by the runtime.

• Updated the Runtime to require that the Windows TAPI service is a dependency when the Runtime is installed as a service. This change was made to resolve a problem where the Runtime could fail to load after PC reboot if the server project contained serial drivers. The issue was initially identified by internal testing and was seen on Windows 7 operating systems and above.

• Resolved an issue where pressing the Tab key when focus is in the Channel/Device pane and there are no Channels defined caused the Configuration to crash.

• Fixed a failure to show _Statistics at the device and channel level when working in the alias name dialog and the tag browser.

• Added the IEC 61850 MMS Client driver to the Communication Drivers feature tree. Additionally this driver will be preselected when the Power Suite is selected earlier in the install.

• Added the OPC XML-DA Client driver to the Communication Drivers feature tree. This driver has been added to the OPC Connectivity Suite. The OPC XML-DA Client driver can be installed and activated for unlimited use with an existing OPC Connectivity Suite (OPC DA and OPC UA Client Drivers) license. Simply re-process the existing activation ID through the license utility and online license portal.

• Added the EFM Simulator driver as a feature selection of the EFM Exporter plug-in. The EFM Simulator is a free component for users of the EFM Exporter. No license is required for the simulator.

• Added the EFM Suite to the list of selections in the Vertical Suite Selection page of the install.

• Removed VS2005 runtime redistributable from the payload of the install as it is no longer used.

• Updated the example for the Custom Interface Driver (CID) to remove bad characters from strings and string arrays.

• Improved the driver's EFM data collection performance and efficiency when intermittent communication errors are seen with the connection to the EFM data source. The optimizations are handled in the driver automatically and no project configuration changes are required in the driver UI.

• Added DB1 as a supported Protocol Version of the driver to support G1 and early G2 Totalflow FCUs. The default setting for the driver is DB2 so users must edit Totalflow Settings to select DB1 for applicable devices in the server project.

• Fixed an issue where the Access Type for Characteristic tags was set to Read/Write when it should have been Read Only.

• Added Device-level error message for Identity request failures.

• Added project change detection support for online and offline project edits. Device setting, "Synchronize with Controller after", is available on the Logix Options property page.

• Following a project download or edit is a period in which Logical reads/writes resort to Symbolic mode, after which the driver synchronizes with the controller so Logical reads/writes can resume. This time period has been lowered from 60 seconds to 30 seconds to improve recovery time.

• Fixed issue that was causing an unnecessary event log message to be posted if a project change occurs during a CIP reconnect (Idle Watchdog expires).

• Improved logic that determines how many reads or writes can fit in a single packet, yielding a slight increase in performance.

• Message size estimation for Symbol Instance reads was incorrect for array element blocks whose starting offset exceeded 255 (likely), making it possible to underestimate and overflow a request packet.

• Message size estimation and generation for Symbol Instance writes was incorrect for paths exceeding 255 in size (unlikely).

• Update for Logix FRN V21. Updated Predefined Data Types for offline ATG per Logix FRN V21:

• 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.

• 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 driver was using a Connection Type of Ethernet Encapsulation and the protocol selected was UDP.

• 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 tag quality was not updated after disabling the Enable Data Collection property.

• Improved the driver's EFM data collection performance and efficiency when intermittent communication errors are seen with the connection to the EFM data source. The optimizations are handled in the driver automatically and no project configuration changes are required in the driver UI.

• Enhanced the driver to support Configurable Addressing. This provides the flexibility to configure address ranges as needed to work with devices that do not use the standard Enron address extensions.

• Added option to automatically generate tags from the EFM configuration mapping.

• Added the EFM Mapping Device Property page to the Enron Modubs new device wizard. The Import and Export functions are not available in the new device wizard. Enabled the EFM mapping controls on the EFM Meters new device wizard property page.

• Made the "Meter Name" element non-optional in XML project schema. Made the min and max number of meters twelve in the XML project schema.

• Improved the driver's EFM data collection performance and efficiency when intermittent communication errors are seen with the connection to the EFM data source. The optimizations are handled in the driver automatically and no project configuration changes are required in the driver UI.

• Fixed an issue where the driver could incorrectly interpret the meter type returned by the device, potentially leading to missing EFM attribute data in the final EFM export.

• Enhanced the driver to support the reading of Symbolic addresses (for PACSystems devices) via multiple blocks within a single read packet, which dramatically improves the driver's read performance in large projects. Changed the default value of the Maximum Bytes Per Request device property from 256 to 2048.

• Enhanced the driver to support Bit-level access within Symbolic addresses within the PACSystems model selection of the driver. This change affects the following data types: BYTE, INT, UINT, WORD, DINT, DWORD, and array elements of those data types (in both discrete and non-discrete memory). Added new error messages for invalid bit index and invalid data type for bit access.

• Improved the driver's EFM data collection performance and efficiency when intermittent communication errors are seen with the connection to the EFM data source. The optimizations are handled in the driver automatically and no project configuration changes are required in the driver UI.

• Fixed a device password login problem that caused the driver to stop polling for data until the server runtime was restarted. The error was triggered when Ethernet Encapsulation devices returned "Exception Code 5" as a result of a login attempt with an incorrect password.