• Increased the maximum number of EFM meters allowed to 70 for Totalflow DB2 format.

• Added support for V28 firmware.
• Added support for L8 Series controllers.

• Resolved a defect that could cause a crash if a malformed packet with an incorrect header length response was received from the PLC. The driver now ignores the malformed packet.

• Fixed an issue where the driver could incorrectly report bad quality for tags in response to a device's BACnet-ComplexACK to the driver's ReadPropertyMultiple request.
• Fixed an issue introduced in the 5.18 release, where channel-level Device Discovery did not discover all the devices on a network.
• Resolved an issue were the driver incorrectly triggered the error state if it received a single error to a ReadPropertyMultiple request. The error state should only be set if the device is not responding.
• Enhanced the driver to support the Accumulator object.
• Added support for individually assigning a BACnet command priority to tags from a connected BACnet device. Previous versions allowed only one command priority to be used for all tags from a BACnet device.
• Added support for Confirmed and Unconfirmed Event Notifications for several Event States; including Changes of Value, Changes of State, Out of Range, and Unsigned Range.
• Added support for IBM/Microsoft DBCS character set.
• Included a Protocol Implementation Conformance Statement (PICS), documenting current BACnet supported properties and services.
• Assigned BACnet Vendor Identification Number 873, used in network WhoAmI communications.

• Fixed an issue with Event Playback that could cause tag quality to temporarily go “Bad” despite a successful unsolicited response.

• Fixed an issue with Event Playback that could cause tag quality to temporarily go “Bad” despite a successful unsolicited response.

• Added ability to read and write to two new data types (FP, U32) and added configuration support to EFM Exporter for these two new types.
• Added support for Extended Stations IDs (device IDs above 255). The new model type is referenced as “Extended Station ID” and supports device IDs up to 65535 and a maximum of 1024 devices per channel.

• Added the ability to set the maximum request size to 8 bytes. This provides access to non-contiguous macros below #1000.

• Added the ability to set the maximum request size to 8 bytes. This provides access to non-contiguous macros below #1000.

• Resolved a Time Sync issue where, if no reads are active; only the first four (4) devices successfully synchronize.
• Enhanced the driver to allow UDP tags to use the correct data type set (not default). This allows the data type of these tags to be manually modified.
• Fixed an issue where “Bad” quality was reported for historical data when new records were not available.

• Resolved a Time Sync issue where, if no reads are active; only the first four (4) devices successfully synchronize.
• Enhanced the driver to allow UDP tags to use the correct data type set (not default). This allows the data type of these tags to be manually modified.
• Enhanced the driver to support parameters 56 through 112 to Point Type 141.

• Resolved a Time Sync issue where, if no reads are active; only the first four (4) devices successfully synchronize.
• Enhanced the driver to allow UDP tags to use the correct data type set (not default). This allows the data type of these tags to be manually modified.

• Resolved a Time Sync issue where, if no reads are active; only the first four (4) devices successfully synchronize.
• Enhanced the driver to allow UDP tags to use the correct data type set (not default). This allows the data type of these tags to be manually modified.
• Fixed an issue where “Bad” quality was reported for historical data when new records were not available.

• Fixed an issue where an incorrect QOC could be sent in certain situations.

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

• Enabled 64-bit data type support (LLong, QWord).
• Added support for OPC Item Access Path using $ symbol for delimiters.
• Enhanced the driver to allow OPC DA Read and Write methods (Asynchronous or Synchronous) based on the Update Mode of the OPC Group. Asynchronous Read and Write methods are the default and remain the optimal choice for most applications.

• Added support for 64-bit data types (LLong, QWord).
• Fixed a race condition that could result in a runtime crash in limited scenarios.
• Improved driver to prompt the user to trust a connection to the UA server when creating an initial connection using security if the certificate is not yet trusted.

• Revised the Update Mode logic to allow more than one simultaneous subscription and prevent orphaned items and subscriptions.

• Fixed an issue that could cause a channel to stop communicating.

• Resolved an issue that could cause memory corruption and runtime crash.
• Corrected an issue where nested UDT structures within arrays weren't parsed correctly from ‘s7p’ files during Automatic Tag Generation.

• Fixed a deadlock situation that could occur when importing an MIB file with clients connected.

• Added support for revision 6 of MID 61, which relates to the Prevail Torque Compensate for the Last Tightening Results command set.
• Added support for using an asterisk as a pad character for the transaction header for the FEP model type.

• Added the ability to format Date and Time values as ACSII numeric strings.

• Fixed an issue that could cause intermittent communication loss.

• Fixed an issue that could cause intermittent communication loss.

• In Ethernet Encapsulation mode of all drivers that support it, the device timing has been modified to separate the connect timeout from the request timeout. To improve clarity and troubleshooting, a request timeout now only occurs if the connection succeeds, but the request fails.

• Resolved an issue where missing records on the device could prevent the Trend File upload from completing.
• Added an error for when the protocol version is not set correctly.

• Added support for V26 and V27 firmware.
• Resolved an issue where a dynamic array tag could be orphaned due to an abrupt disconnection of the client. On reconnect, the array tag was unable to be re-added by the client.
• Resolved issue that prevented reading arrays with more than 65535 elements when using the Logical Blocking protocol mode.

• Added a section to the manual describing how to configure modules not present in the module list.

• Renamed "AutomationDirect Productivity 3000 Ethernet" driver to "AutomationDirect Productivity Series Ethernet" to better represent support for the entire Productivity Series of controllers.

• Resolved an issue where memory could be corrupted in certain scenarios when filtering tags.

• Renamed the GE Focas Ethernet and GE Focas HSSB drivers to Fanuc Focas Ethernet and Fanuc Focas HSSB to reflect corporate changes by vendor.

• Added support for Advanced Statistics Tags, including _CommFailures, _ErrorResponses, and more.
• The driver now includes the #n syntax when auto-generating tags for similarly named point types in point type tables to avoid duplicate tag names. This may change the default name for some auto-generated tags from previous versions.
• Changed the alarm state from OFF to ON for string events.
• Resolved an issue where attempting to read a tag from a non-responsive device could falsely cause a timeout when reading the next tag on a different device.
• Resolved an issue where reading multiple tags in the same point type logical could result in two separate read requests rather than one.

• Added support for Advanced Statistics Tags, including _CommFailures, _ErrorResponses, and more.
• The driver now includes the #n syntax when auto-generating tags for similarly named point types in point type tables to avoid duplicate tag names. This may change the default name for some auto-generated tags from previous versions.
• Changed the alarm state from OFF to ON for string events.
• Resolved an issue where attempting to read a tag from a non-responsive device could falsely cause a timeout when reading the next tag on a different device.
• Resolved an issue where reading multiple tags in the same point type logical could result in two separate read requests rather than one.
• Corrected mappings for liquid temperature high and low limits to EFM exports.

• Added support for Advanced Statistics Tags, including _CommFailures, _ErrorResponses, and more.
• The driver now includes the #n syntax when auto-generating tags for similarly named point types in point type tables to avoid duplicate tag names. This may change the default name for some auto-generated tags from previous versions.
• Changed the alarm state from OFF to ON for string events.
• Resolved an issue where attempting to read a tag from a non-responsive device could falsely cause a timeout when reading the next tag on a different device.
• Resolved an issue where reading multiple tags in the same point type logical could result in two separate read requests rather than one.
• Corrected mappings for liquid temperature high and low limits to EFM exports.

• Added support for Advanced Statistics Tags, including _CommFailures, _ErrorResponses, and more.
• The driver now includes the #n syntax when auto-generating tags for similarly named point types in point type tables to avoid duplicate tag names. This may change the default name for some auto-generated tags from previous versions.
• Changed the alarm state from OFF to ON for string events.
• Resolved an issue where attempting to read a tag from a non-responsive device could falsely cause a timeout when reading the next tag on a different device.
• Resolved an issue where reading multiple tags in the same point type logical could result in two separate read requests rather than one.

• Resolved an issue where array indices of multi-dimensional arrays of card tags were transposed.

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

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

• Added support for "Execute" statements within the Query access method.
• Added an Execute tag for executing queries (e.g. Channel.Device.Execute).
• Added the ability to enable or disable the query time interval. This allows users to exclusively trigger queries on demand via the device’s Execute tag.
• Resolved an issue where a change in the query interval setting did not persist through shutdown and restart.
• Removed duplicate messages that occurred in the event log when automatically generating tags.
• Resolved issue with handling "money" and "smallmoney" data types as parameters to stored procedures in the stored procedure access methods.
• Resolved an issue with the Update Tags button on the query and stored procedure access methods.
• Resolved a configuration issue where a device prevents editing and reports that it is processing tags when no client references to the device exist.

• Enhanced Automatic Tag Generation for a device object while one or more clients are actively connected.
• Resolved an issue that could cause tag reads using ReadMaxAge to always read from cache.
• Resolved an issue that could cause the client to receive a newly written value, then a stale cached value, before receiving the new value again.

• Enhanced Automatic Tag Generation for a device object while one or more clients are actively connected.
• Resolved an issue that could cause the client to receive a newly written value, then a stale cached value, before receiving the new value again.
• Resolved an issue where the posted error message was not representative of the actual cause of the error.
• Resolved an issue that caused tag import to hang while loading large branches of tags.

• Enhanced Automatic Tag Generation for a device object while one or more clients are actively connected.
• Resolved an issue where the "KeepAlive" message was no longer sent under adverse network conditions.
• Resolved an issue that could cause the client to receive a newly written value, then a stale cached value, before receiving the new value again.

• Resolved an issue that could cause a channel to stop communicating.

• Added support for Advanced Statistics Tags, including _CommFailures, _ErrorResponses, and more.
• Enhanced the driver to allow the RTU P619 value to be queried prior to a Dynagraph request. The result of this request determines the "position inclusion and type character" parameter when building the Dynagraph transaction.

• Resolved an issue that could cause intermittent communication loss.

• Upgraded OpenSSL (open source library) to version 1.0.2d to address security vulnerabilities pertaining to certificate validation.

• Fixed an issue where validating invalid tag addresses with 16 or more continuous alpha characters could result in a crash of the Runtime. This could occur in two cases: after Auto Tag Generation from a device containing symbolic tags or if a client referenced tag names not defined in the server.

• For all drivers that support communication serialization, added a global setting called Network Mode. The default Network Mode is Load Balanced. Priority Mode was added for use with the Scheduler Plug-in. Changes to this mode affect all channels and the Network Mode is only applicable when the channel is assigned to a virtual network.
• Added support for a channel-level statistics tag "_NextReadPriority" to show the priority of the next read. This improves troubleshooting when using priority-based virtual networks.
• Added support for reporting socket errors for all serial drivers that support Ethernet encapsulation.
• From the Timing tab of Device Properties, increased the maximum value for the Request Timeout from 99,999 to 9,999,999 milliseconds.

• Enhanced the driver to support Trend File uploads. The new Trend File feature supports:
  • Publishing trend data to a CSV file
  • The ability to limit uploads based on time parameters
  • Optimized data uploads in limited-bandwidth scenarios (via segmented requests)
  • Scheduling uploads with the Scheduler Plug-in,
• Enhanced the driver to support Advanced Statistics tags, including "_CommFailures" and "_ErrorResponses".
• Enhanced the driver to support liquid EFM for model 6000 XSeriesG4
• Support Gen4 devices for liquid using the DB2 protocol.
• Support for hourly history, daily history, batch, liquid product, alarms, and events.
• Support for a single Totalflow device with both liquid and gas meters.
• No longer perform a time synchronization operation on startup when the Time Sync Method is Absolute.

• Added support for reporting socket errors in the Event Log when connecting, sending, and receiving data.
• Fixed an issue where the first read from a device that had been in an error state returned bad quality. The read now returns good quality if the device is available
• Fixed an issue where the thread count increased when changing the device ID via a System Tag.

• Fixed an issue where the driver was not immediately resetting the session ID if the device reset the TCP/IP socket when the driver was not prepared to receive data.

• Extended address range support to octal 77777.

• Added string array support to the server interface for the XLTable format type.

• The driver no longer attempts communication with the device if a client is only referencing System (internal) tags, which do not require device communication.
• Added the ability to disable time synchronization messages.
• Corrected an issue where a disabled device on a virtual network could block other devices from communicating.

• The driver no longer attempts communication with the device if a client is only referencing System (internal) tags, which do not require device communication.
• Added the ability to disable time synchronization messages.
• Corrected an issue where a disabled device on a virtual network could block other devices from communicating.
• Fixed a host name resolution issue when using a host name in Ethernet Encapsulation mode. The host name was not resolved correctly leading to bad quality communications.

• Enhanced the driver to gather historical data from gas chromatograph devices.
• Added support for configuring the historical and event date formats to be compatible with ABB and Daniels gas chromatographs.

• New Ethernet driver. Supports multiple ROC devices per channel, with each device having its own IP address.
• Added support for reading and writing to user tables using Opcodes 10 and 11.
• Added the ability to ignore extra bytes received on the wire that are not part of the ROC communications. These bytes are sometimes added by radio modems and other networked equipment.
• Enhanced the drivers to support Opcode 180. Enabled per device, this allows the driver to read multiple TLP and UDPs per read request.

• New Ethernet driver. Supports multiple ROC Plus devices per channel, with each device having its own IP address.
• Added support for reading and writing to user tables using Opcodes 10 and 11.
• Added the ability to ignore extra bytes received on the wire that are not part of the ROC communications. These bytes are sometimes added by radio modems and other networked equipment.
• Enhanced the drivers to support Opcode 180. Enabled per device, this allows the driver to read multiple TLP and UDPs per read request.

• The driver no longer performs a time synchronization operation on startup when the Time Sync Method is Absolute.
• Added support for reading and writing to user tables using Opcodes 10 and 11.
• Added the ability to ignore extra bytes received on the wire that are not part of the ROC communications. These bytes are sometimes added by radio modems and other networked equipment.
• Enhanced the drivers to support Opcode 180. Enabled per device, this allows the driver to read multiple TLP and UDPs per read request.

• The driver no longer performs a time synchronization operation on startup when the Time Sync Method is Absolute.
• Added support for reading and writing to user tables using Opcodes 10 and 11.
• Added the ability to ignore extra bytes received on the wire that are not part of the ROC communications. These bytes are sometimes added by radio modems and other networked equipment.
• Enhanced the drivers to support Opcode 180. Enabled per device, this allows the driver to read multiple TLP and UDPs per read request.

• The driver now supports millisecond resolution on timestamps provided from the device.

• Fixed an issue where write-only strings failed to write when "Perform block read on strings" was enabled.

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

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

• Enhanced error detection to support remote network errors to place the device in error state. This more accurate reporting supports redundancy failover.

• The driver no longer creates subscriptions and monitored items for inactive tags. This allows the driver to act in a cold redundancy mode when used with the Media Level Redundancy plug-in.
• Increased time for UA clients to disconnect when shutting down to allow for proper shutdowns.
• Changed the driver to request both the server and source timestamps from the UA server. The driver uses the source timestamp supplied by the UA server if it is available. If it is not available, the driver uses the UA server timestamp. If that is not available, the driver sets the timestamp to the current system time.
• Fixed an issue to allow importing a tag branch containing a tag with an unsupported data type.

• Fixed an issue where CTI 2500 controllers did not support the CAMP protocol to access DCP address types. The CAMP+Packed Task Code protocol option fixes this issue.

• Added support for string arrays, date arrays, and Boolean arrays.

• Fixed an issue where strings with a null value were truncated at the first null.

• Added support for FL-net Multi-Layer Link Communications.
• Fixed an issue when writing to bit-within-word tags before the word was read from the device.

• Added a new custom checksum: sum all bytes, invert all bits, truncate result to one byte, and add 1. The checksum is applicable to Emerald devices, from Industrial Indexing Systems.

• When loading an .OPF project file, a message is reported in the Event Log for each channel that uses the WeatherBug driver and those channel configurations are removed from the project. This change improves visibility after deprecating the WeatherBug driver in the previous server release.

• Increased the maximum channel limit from 512 to 1024.

• Added the SoftPLC device model type to expose the extended address range of SoftPLC controllers. SoftPLC does not support the ASCII memory type.
• Fixed an issue where the PLC5 model could read the wrong memory location for string types beyond element 780.

• Added support for V23 and V24 firmware.
• Updated the driver to work with future-generation devices and firmware. Before this fix, the driver experienced a communications failure with these devices.
• Increased the maximum channel limit from 256 to 1024.
• Fixed an issue where automatic tag generation from an L5K file failed if the L5K contained an AOI parameter that aliased another parameter. AOI alias parameters are not supported in automatic tag generation and should not be automatically generated.
• For Logix FRN V24, updated Predefined Data Types for offline automatic tag generation and added new members to AXIS_CIP_DRIVE, AXIS_CONSUMED, AXIS_GENERIC, AXIS_GENERIC_DRIVE, AXIS_SERVO, AXIS_SERVO_DRIVE, AXIS_VIRTUAL, and MOTION_GROUP per Logix FRN V24 changes.

• Fixed an issue where the driver produced a syntax error during tag validation if the data type was not supported. Some clients add items with a set data type regardless of the address. The driver now responds with bad type, allowing the driver library to validate again with the default type.

• Corrected an issue where the driver would produce a syntax error during tag validation if the data type was not supported. Some clients add items with a set data type regardless of the address. The driver now responds with bad type, allowing the driver library to validate again with the default type.
• Fixed an issue where Data Words Timers (V0-V377) and Counters (V1000-V1177) default to the BCD data type even if the address was a bit within data type; bit within BCD is not supported. For V addresses with bit-access syntax, the driver now defaults to the Short data type for the bit range 0 to 15 and to the Long data type for bit range 16 to 31.

• Fixed an issue where automatic tag generation failed if the device did not support segmentation. This issue was introduced in KEPServerEX version 5.15.
• Enhanced the driver to support manual configuration of the BACnet MAC address. This allows the driver to communicate through a gateway to other BACnet network types.

• Corrected an issue where the driver would produce a syntax error during tag validation if the data type was not supported. Some clients add items with a set data type regardless of the address. The driver now responds with bad type, allowing the driver library to validate again with the default type.

• Added support for 10 ms update rates to Event Class 1, 2, and 3 polling intervals.
• Fixed an issue where malformed packets could disrupt communications.
• Fixed an issue where an out-of-bound read vulnerability could exhaust resources and prevent the driver from working.

• Added support for 10 ms update rates to Event Class 1, 2, and 3 polling intervals.
• Fixed an issue where malformed packets could disrupt communications.
• Fixed an issue where an out-of-bound read vulnerability could exhaust resources and prevent the driver from working.

• Spaces are no longer allowed in liquid and gas meter names.

• Spaces are no longer allowed in liquid and gas meter names.

• Fixed an issue where the driver posted the error message "Device returned error code 0xFDFF reading symbolic variable data" when certain devices respond with unexpected bytes. The driver was updated to handle these responses.

• Fixed an issue where timestamp values sent from the device with the day-of-week field set to 0 (unused) were not displayed correctly in the Quick Client. The driver now calculates the correct day-of-week based on the timestamp.

• Fixed an issue where tags were not being generated correctly from SCL files when the type name is appended to the data attribute name in the SCL file (for example, "mag.f").

• Added schema files to support Version 1.2 and 1.3 of the MTConnect standard.

• Corrected an issue where the driver would produce a syntax error during tag validation if the data type was not supported. Some clients add items with a set data type regardless of the address. The driver now responds with bad type, allowing the driver library to validate again with the default type.

• Corrected an issue where the driver would produce a syntax error during tag validation if the data type was not supported. Some clients add items with a set data type regardless of the address. The driver now responds with bad type, allowing the driver library to validate again with the default type.

• Enhanced the driver to reconnect the UA session after encountering an invalid Session ID error.
• The Device _Error flag is now set if the driver is unable to connect on the initial connection.

• Added support for 64-bit data types, including QWord, LLong, and arrays of these two types.

• Fixed an issue where tags of type 'Date' could result in other tag values not being updated. This only occurred with tags that were in the same block as the Date tag.
• Added support for HEXSTRING data types.

• Fixed a runtime crash that could occur if there was a socket error while reading unsolicited data.

• Added support for 64-bit data types, including QWord, LLong, and arrays of these two types to both the 8-bit and 16-bit device models.

• Fixed an issue where global function blocks with commands CCmdWriteDeviceID or CCmdTestDeviceID could cause an XML configuration to fail to load.

• Deprecated the WeatherBug Driver.

• Fixed a project load/save issue that was introduced in the 5.16.722.0 release that could cause both the Configuration and Runtime to fail to load projects. The failure was intermittent and depended on the project layout.

• Fixed a channel deadlock issue that could cause the driver to stop communicating with certain devices. The failure could occur randomly after many hours of stable communication.

• Fixed an issue where the Auto Demotion failures counter was only reset when in a demoted state. This could result in early Auto Demotion for future communication failures.

• Fixed an issue where device reads may be starved for a device under a channel if another device under the same channel is not in an error state. This would prevented the device in an error state from coming out of the error state.
• Fixed an issue where a buffer overflow could occur with writes containing 500 or more characters.

• Fixed an issue where automatic tag generation from a *.tpy file would force all characters in the address to be uppercase. The case is now left as is in the *.tpy file.
• Fixed an issue where generating tags with the option Only import variables marked for OPC enabled would cause the server to become unresponsive after attaching a client.
• Corrected an issue where nested structures were not always being automatically generated correctly from a TwinCAT device.
• Corrected an issue where tags automatically generated from a device and from an equivalent *.tpy file would result in non-equivalent projects under certain conditions.

• Updated the maximum length of the XML schema Destination Host element to 255.

• Fixed a server deadlock that could occur when launching a client that had 100,000 or more tags configured for a device.

• This initial release of the serial driver provides connectivity to IEC 60870-5-101 slave devices in electrical substations that include RTUs, IEDs, controllers, and gateways.
• The following features are supported:
  • Balanced and Unbalanced modes
  • Configurable link layer and application layer settings
  • Event Playback
  • Background data updates
  • Cyclic data updates
  • Data Polling
  • Unsolicited data in Balanced Mode
  • Class Polls in Unbalanced Mode
  • Delay Acquisition for Time Synchronization operations
  • Test Procedure
  • General Interrogation (global group) and Counter Interrogation (global group)
• The following Application Service Data Unit (ASDU) types are supported:
  • Single Point Information
  • Double Point Information
  • Step Position Information
  • Bit string of 32 bit
  • Measured Value, Normalized Value
  • Measured Value, Scaled Value
  • Measured Value, Short Floating Point Number
  • Integrated Totals

• This initial release of the Ethernet driver provides connectivity to IEC 60870-5-104 slave devices in electrical substations that include RTUs, IEDs, controllers, and gateways.
• The following features are supported:
  • Configurable link layer and application layer settings
  • Event Playback
  • Background data updates
  • Cyclic data updates
  • Data Polling
  • Unsolicited data
  • Test Procedure
  • General Interrogation (global group) and Counter Interrogation (global group)
• The following Application Service Data Unit (ASDU) types are supported:
  • Single Point Information
  • Double Point Information
  • Step Position Information
  • Bit string of 32 bit
  • Measured Value, Normalized Value
  • Measured Value, Scaled Value
  • Measured Value, Short Floating Point Number
  • Integrated Totals

• Fixed an issue where a failure during automatic tag generation caused previously automatically-generated existing tags to be deleted.
• The configuration now allows the automatic tag generation of tags imported from Edition 2 *.icd files.

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

• Increased the maximum number of channels from 100 to 256.
• Updated the driver so that it will not force the access of tags added manually to be Read Only when the Set write access for imported database tags option is unchecked. This option only applies during automatic tag generation.
• Updated automatic tag generation to force the internal tags that should be Read Only to be Read Only.

• Fixed an issue where the driver was not working correctly when unexpected characters were received from a non-Omron device that supported the HostLink protocol.

• Fixed issues with reading and writing UTF-8 characters that exceeded the tag-defined length limit in bytes. Truncating the strings resulted in the strings being invalid. Strings are now truncated appropriately.
• Fixed an issue where device reads may be starved for a device under a channel if another device under the same channel is not in an error state. This prevented the device in an error state from coming out of the error state.
• Added automatic tag generation support for Date_And_Time variables.
• Updated the driver to use the configured Request Timeout while processing remote CPU Forward Close requests to expedite tag failures during communication timeouts.
• Added read and write support for the DateAndTime variable type.
• Fixed an issue where an address ending with a UTF-16 surrogate pair resulted in a Variable Address with the length field set to zero.
• Added support for reading and writing Unicode characters to STRING Controller Variables. The foreign languages supported include but are not limited to Chinese, Japanese, Korean, German, Russian, and Spanish.

• Enhanced the OPC DA Client Driver so that it will now attempt to re-add failed items.

• Changed the driver to pass through source timestamp to tags instead of server timestamp. The timestamp will not be updated if the source timestamp is not provided.

• Updated the Tag Editor in the Transaction Editor to enforce the rules for tag names; specifically, to not allow trailing whitespace. This solves issues where copying and pasting a name that contains whitespace at the end caused the tag to fail validation. The Tag Group and Tag Block Name dialogs were also updated to enforce this.

• Fixed an issue where generating tags with the option "Only import variables marked for OPC" enabled would cause KEPServerEX to become unresponsive after attaching a client.

• The driver now passes the source timestamp instead of the server timestamp to tags.

• Fixed an issue where the server could crash if an In-Process Server (which is a server that is a .dll not an .exe) threw an unhandled exception.

• Removed the potential for a hang when a client accesses tags containing UDP point types.

• Removed the potential for a hang when a client accesses tags containing UDP point types.

• Fixed an issue where Media Level Redundancy would not switch back to the primary device if a monitor item was not defined and the driver defaulted to using a system/internal driver tag to monitor the health of the secondary device.
• Fixed an issue with Media Level Redundancy where the driver would not switch back to the primary device if the secondary device was placed in a disabled state.
• Added a state to the device _DemandPoll Tag to indicate when a poll is occurring. The tag goes true after it is written to and false when the transaction completes.

• Fixed an issue where writes would not be processed when multiple devices on a channel were configured to use a Register Requests/Packet setting greater than 1.
• Enhanced the driver to cache the pointer file to disk so that it will not re-poll for data already collected on server start-up.
• Fixed an issue that would cause the driver to re-poll records starting at sequence number one in the event that the sequence number is less than the archive capacity.

• Added block read support for string memory type tags to both the SLC 5/05 Open and PLC-5 Family models.

• Added support for Weekly, Exception, and Calendar Objects. These objects are represented as custom formatted strings that can be read and written. For details and VB code samples, refer to the BACnet/IP Driver help file.
• Fixed an issue that allowed array element tags to use a zero index. This is no longer allowed.
• Increased the maximum device limit from 100 to 128.
• Fixed a typo in the Event Log message for a failed COV subscription.
• Fixed a UI issue where the Import File field was not disabled when the Import Method parameter was set to Device.
• Fixed an issue where the driver could improperly convert integer values to floats when reading and writing.
• Added support for BACnet Broadcast Management Devices (BBMD) to Device Discovery at the channel level.
• Fixed an issue where communications would fail after initial Automatic Tag Generation with a BBMD.
• Added support for a new discovery scope to send a Who-is/I-am to a specified IP address.

• Enhanced the driver to allow default data types to be replaced by the data type returned from the controller. This does not require clients to specify the data type upfront.
• Fixed an issue where Boolean array writes were not supported in Logical Mode.

• Fixed an issue that could cause handle leaks to occur while writing.
• Enhanced the write error return message to include a more specific reason for the error.

• Enhanced the driver to cache the pointer file to disk so that it will not re-poll for data already collected on start-up.
• Fixed an issue where the driver was producing duplicate EFM records for hourly history data.

• Enhanced the driver to cache the pointer file to disk so that it will not re-poll for data already collected on start-up.
• Added support for Point Type 98.

• Enhanced the driver to cache the pointer file to disk so that it will not re-poll for data already collected on start-up.

• Fixed an issue where the socket connection could not be re-used after a restart on some platforms.

• Fixed an issue where data quality was bad when using only symbolic addressing for a PAC Systems device.

• Increased the maximum channel count from 100 to 256.

• Fixed an issue where event playback would not work on initial load because the driver was not applying the playback settings correctly.

• Increased the maximum channel count from 100 to 256.

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

• Enhanced the driver to support Media Level Redundancy.

• Fixed an issue where a buffer overflow could result in the driver writing to erroneous coils.

• Enhanced the driver to cache the pointer file to disk so that it will not re-poll for data already collected on start-up.
• Added support for scaling EFM values using the EFM Mapping in the GUI.
• Updated the flow_time and meter_factor attributes to automatically apply scaling for legacy projects. These attributes were previously scaled but were not user-configurable.

• Increased the maximum channel limit to 512.

• Fixed an issue where an initial write caused a loss of communications following a PLC power cycle.

• New driver for communications with Omron Sysmac NJ-enabled devices.

• Enhanced the driver to support Media Level Redundancy.
• Modified the self-signed certificate to make the AppURI and SubjectAltName fields equal for OPC UA Compliance.

• Fixed an issue where AddGroup() calls would fail when CoInitializeEx () was called after CoInitializeSecurity ().

• Enhanced Automatic Tag Generation support to include extended (non-ASCII) characters.
• Fixed an issue where an uninitialized buffer could cause a buffer overflow and result in a crash.
• Fixed an issue where an invalid data length in a response could cause a buffer overflow and result in a crash.
• Fixed an issue where the driver would treat a WSAEWOULDBLOCK as an error when waiting to receive data. This could result in an error reported for a valid packet.

• Enhanced strings to support specifying the characters' byte order.

• Added Advanced Encryption Standard (AES) support for SNMP v3. This includes 128 bit encryption in compliance with RFC 3826, as well as Cisco-specific extensions to support AES 192 bit and 256 bit encryption.
• Made a change wherein the Username is now required in the SNMP v3 Security property page and validation displays the last valid name if the user tries to delete it.
• Passphrase characters are now obfuscated in the same manner for all passphrase fields. Content is obfuscated but length is not.
• Passphrase fields are no longer cleared when a change to the security level is applied in the SNMP v3 Security property page.

• Prevented the driver from immediately closing the socket connection when there is no client reference for a device. Instead, the driver will wait for the next Keep Alive before closing the socket.
• Fixed an issue where the driver would not refresh the TCP socket if either the IP Address or port was changed and the Connection Timeout setting was modified.
• Fixed an issue where the driver could stop receiving packets due a timeout.
• Fixed a threading issue that could cause a channel to stop communicating.

• Fixed a timing/synchronization issue that occurred when processing tags that could result in the Runtime crashing.

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

• Fixed an issue where applying scaling on an array value resulted in zeroes.

• Increased the ABB Totalflow Driver's maximum channel limit from 256 to 512.

• Updated the help file to include instructions on communicating with RSLogix5000 controllers.

• Fixed an issue where channels would suddenly stop communicating. This was a rare occurrence that had to do with improper event handling.
• Fixed an issue where reading arrays of 64 bit data types (LINTs) that spanned multiple transactions would fail.
• Fixed an issue where switching from Symbolic Mode to any Logical Protocol Mode without reinitializing the server would not honor the Logical Mode and would stay in Symbolic Mode.
• Expanded and made configurable the CIP Connection size for Logix models. The supported range is now 500 to 4000 where it had previously been hard set to 500.
• Note: CPU and EtherNet/IP modules must support Large Forward Open for connection sizes greater than 500 bytes.

• Added support for a Liquid EFM model to simulate liquid data. The driver now supports Gas EFM and Liquid EFM models.
• The EFM Simulator now specifies a contract hour and contract day of 0 instead of random values.

• Fixed a UI issue where a duplicate archive assignment check would be done even if a meter was disabled. The assignment check is no longer performed for disabled meters.

• Fixed an issue where Default data type was always returned for UDP tags, even if the UDP data type was known by the server. This could cause writes that occurred before an initial read of the UDP tag to fail.

• Added the new 809L and 827L models with support for Liquid EFM and export to Flow-Cal V7. The new models support EFM configuration, hourly history, daily history, batch, alarms, and events upload.
• Fixed an issue where Default data type was always returned for UDP tags, even if the UDP data type was known by the server. This could cause writes that occurred before an initial read of the UDP tag to fail.
• Fixed an issue where Gas EFM data would not upload if the meter being uploaded was preceded by a segment containing no TLP mappings.

• Changed tag addressing to define polled versus unsolicited tags by the address. All tags with the generic address are now polled. Unsolicited or RCB tags now have a special : address syntax. This allows clients to know if a tag is polled or unsolicited by looking at the address. Previously, there was one generic address syntax and a setting to enable RCBs. For legacy projects, all tags will become polled tags until the address syntax is changed.
• RCB are now enabled on first client reference to an unsolicited tag in the block, and disabled when the last client reference is removed.
• Updated automatic tag generation from SCL files to support <RCB>:<Data> syntax and to flatten the generated tag hierarchy. There are no longer tag groups for every nested 61850 object.
• Added a configurable Integrity Poll Rate (ms) parameter to Device Properties to report when the server loses connectivity to a device when using unsolicited tags.
• Fixed an issue where unsolicited tags would not receive an initial update.

• The Mitsubishi Ethernet Driver now handles the closing of a connection correctly whether it was initiated by the server or by the device.
• Fixed an issue with the A Series model where Boolean Special Int. Relays were bit shifted in memory.

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

• Fixed an issue with incorrect Boolean conversion handling. Booleans can now be set and cleared properly.

• Added support for Liquid EFM. The driver now supports both Liquid EFM and Gas EFM models. The Liquid EFM model supports EFM configuration, hourly history, daily history, batch, alarms, and events upload. It also has the ability to configure and map OMNI archives.
• Fixed an issue where flow time was not properly scaled. OMNI flow times are recorded in 500 millisecond ticks, and are now scaled to minutes for export to Flow-Cal and other formats.
• Fixed an issue where alarm state values exported to Flow-Cal CFX V5 files were being decremented by one.
• Added the archive number to the Event Log message that is displayed when the max size for an archive is set to zero in the device.
• Fixed issues where the device error state was being improperly cleared after being set because of a DNR during an EFM history upload.
• Fixed an issue where shared archive data would sometimes not be exported with a history record.

• Fixed a memory leak caused by unremoved items in a subscription. The leak occurred for Subscriptions using the "Poll" Update Mode.

• Fixed issues that were encountered when browsing for items on certain devices (such as SIMOTION controllers). Tags with the default data type can now be added and the data type will be determined on its first read.
• Added the ability to use the Max Items per Read setting when using Exception mode.
• Improved browsing speed when not using the leaf filter.

• Added a new S7-1500 model.
• Added support for automatic tag generation from a Step 7 project file for S-400 and S-300 controllers.

• Fixed an issue communicating with models 945, 946, and 947.

• Fixed an issue where tags would have bad quality if the data type length was in long form.
• Added (EncExtAsc) as an encoding identifier (appended to the OID in the Address field) so extended ASCII characters will be human readable instead of represented in Hex.

• Fixed an issue where a block tag was being incorrectly set in broadcasting mode.

• Resolved an issue where reading initially inactive subscriptions would fail on some devices. This issue could be seen with the Lufkin Modbus Serial Driver when a read was initiated on an inactive subscription and the block size was modified on-the-fly before the driver was able to update the tag with data from the device.
• Resolved an issue introduced in server version 5.12 that prevented duplicate names from being made unique during Automatic Tag Generation (ATG). This could be seen when performing ATG with the Fisher ROC Plus Serial Driver, which resulted in fewer tags being generated than in previous versions of the driver.

• Increased the maximum number of supported channels from 100 to 256.

• Fixed an issue introduced in server version 5.11 where in certain conditions, reads and writes would be performed in the reverse order in which they were submitted to the driver from a client application.
• Corrected the message size estimation for Symbolic Writes, which was making it possible to underestimate and overflow a request packet.

• Enhanced the driver to support ODVA Conformance. New features include Connected Messaging, ODVA Member ID, and EDS file.
• Corrected a problem in dimension detection for tag paths that contain 16 bit element offsets.
• Corrected a defect in element count calculation that was exposed by the Allen-Bradley Micro800 Ethernet Driver. The element count is now correct if the element offsets indicate that less than the specified element count need to be returned.
• Runtime tag values are no longer reset when a device's slot configuration is changed.
• Removed support that allowed users to specify Port 0 (system determined) for the EIP server binding. Because the driver binds a listen socket to both UDP and TCP for conformance, these ports must be the same.
• Removed the potential server hang that could occur if EIP messages were being processed while a channel's Network Interface or Port was changed.
• Corrected int64<->Double conversion to match behavior in ControlLogix Ethernet Master Driver.
• Removed support for the Media-Level Redundancy Plug-In because it was never intended.

• Updated to allow the PresentValue Property Tag of the Schedule Object to be set to Read/Write.

• Both a copy of TcAdsDll.dll and the Beckhoff TwinCAT Remote Manager Utility are no longer provided with the install. Users must obtain the TwinCAT ADS Communication Library from Beckhoff in order to access the tools that are required to configure successful AMS Remote Connections.
• Improved performance reading from TwinCAT 3 PLC by monitoring the OnlineChangeCnt global variable and not reading the symbolic information for every read.

• Increased the maximum number of supported channels from 100 to 512.

• Added Retry Attempts for the following requests: Integrity Poll, Event Poll, Disable Unsolicited, Data Set Exchange, Automatic Tag Generation, and Explicit Reads/Writes.
• 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.

• Added Retry Attempts for the following requests: Integrity Poll, Event Poll, Disable Unsolicited, Data Set Exchange, Automatic Tag Generation, and Explicit Reads/Writes.
• 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.

• Enhanced the Fisher ROC Serial Driver to support User-Defined Points. This includes support for Dynamic Tag Creation as well as Online and Offline Automatic Tag Generation.
• Added support for the following point ranges:
  • Lower UDP range: Points 22 through 39 (excluding 24)
  • Upper UDP range: Points 178 through 189
• Resolved an issue where, depending on the size and number of parameters in a block, the driver could request more parameters than will fit into a ROC serial response frame. An example of this is reading parameters 53 through 75 of point type 80 on a FloBoss Model 107 device, which would result in framing errors and bad quality for the entire block of parameters.
• Increased the maximum number of supported channels to 1024.
• Added support for FloBoss Model 107 specific parameters in point type 14. This support resolves an issue where adding or enabling parameter 37 of point type 14 would cause the entire set of point type 14 tags to go bad.
• Added support for FloBoss Model 107 specific parameters in point type 57. This support resolves an issue where adding or enabling parameter 5 of point type 57 would cause the entire set of point type 57 tags to go bad.

• Enhanced the Fisher ROC Plus Serial Driver to support User-Defined Points. This includes support for Dynamic Tag creation as well as Online and Offline Automatic Tag Generation.
• Added support for following point ranges:
  • Lower UDP range: Points 60 through 78
  • Upper UDP range: Points 196 through 254
• Increased the maximum number of supported channels to 1024.
• Resolved an issue where an EFM history upload from a device with five or less points configured in a history segment would fail due to framing error.
• Added support for point type 177, Wireless HART.

• Improved performance of the PACSystems model by requesting bytes instead of byte per bit when reading symbolic variables that are in discrete memory.

• Added the new "First word low in 32 bit data types" option (located in the Data Encoding tab of Device Properties). The default setting is the same as the legacy behavior, which is checked. Projects saved prior to this update will be loaded with the default setting.

• Fixed an issue where the driver could process the response for a different memory type other than what was issued in the request.

• Fixed an issue where certain queries would result in bad quality for all tags in the device. The driver would post the "Unable to open recordset on device (Reason: Query timeout expired)" error message in the Event Log. This issue was due to an unnecessary query being used to count the number of items in the table.

• Fixed an issue where one tag with a bad address would cause all tags to have bad quality with certain XML-DA servers.
• Added support for HTTP Authentication.

• Resolved an issue where the driver failed to import tags if the data type returned by the target server was VT_EMPTY.

• Fixed an issue where the driver sent a NULL terminator for CONT string writes.

• Enhanced the driver to allow users to set the Block Size, which is the number of registers that will be read in a single request. The valid block sizes are 16, 32, 64, and 128. The default setting is 16.
• Fixed an issue where the driver transmitted erroneous PAD characters (0xfe).
• Fixed an issue where the driver replied with the incorrect acknowledgement control frame.
• Fixed an issue where the driver sent the acknowledgement control frame as two separate transactions.
• Fixed an issue where the driver failed to send an acknowledgement control frame when it received an inquiry from the device and it did not have a tag to process.

• Resolved an issue where the driver would not send a start command before reissuing the last command (on a retry attempt) if the socket was closed.
• Fixed an issue where the driver refreshed the TCP socket when the Connection Timeout setting was modified.

• Fixed an issue where deadlock could occur if multiple pieces of outgoing data were queued while the driver was still processing incoming data. This change affects the Transmit and Transmit Byte Commands.
• Fixed an issue where data loss could occur if there was still data on the wire from a previous transmission when either a Transmit or Transmit Byte command was called.
• Added logic to handle writing packets larger than 1024.

• Resolved an issue where deadlock could occur after multiple user-driven Automatic Tag Generation attempts were triggered from the Server Configuration's Device Properties.

• Resolved an issue related to write performance where certain drivers with the ability to perform multiple writes per transaction were incorrectly performing single writes after an initial multi-write transaction. This change affects the following Ethernet drivers: BACnet IP, Beckhoff TwinCAT, Allen-Bradley ControlLogix Ethernet, Custom Interface, GE Ethernet (SRTP), Siemens TCP/IP Ethernet, Simatic TI 505 Ethernet, SNMP, Triconex Ethernet, and WeatherBug.

• Updated the driver to convert flow times reported by Totalflow devices in integer seconds to floating-point minutes. This makes flow times exported by the EFM Exporter for Totalflow meters consistent with other meter types.

• Changed a behavior where the driver will now retry tags instead of failing them upon detecting an Online or Offline edit (except for Downloads). It's likely that the next attempt will succeed. Also, Offline edits will take priority over Online edits if both occur before being detected by the driver.
• Fixed an issue where the Protocol Mode drop-down selection arrow would not redraw correctly if the selection invoked a vertical scroll bar in the grid.

• Initial release of this new Ethernet driver, which will be part of both the Allen-Bradley Suite and the Manufacturing Suite.

• Initial release of this new serial driver, which will be part of both the Allen-Bradley Suite and the Manufacturing Suite

• 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.
• Changed the Exchange Data Sets device property's default setting from True to False.
• 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 an issue where a non-empty Activate Configuration Object string incorrectly triggered automatic tag generation when other device properties were modified.
• 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.

• 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.
• Changed the Exchange Data Sets device property's default setting from True to False.
• 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 an issue where a non-empty Activate Configuration Object string incorrectly triggered automatic tag generation when other device properties were modified.
• 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.

• Fixed an issue where automatic tag generation would not create Point Types 101 through 109.
• Fixed an issue where automatic tag generation created point types with incorrect Logical Addresses.
• Added support for Point Types 98-x.53 through 98-x.60.
• Added a Set/Clear indication to the beginning of the alarm strings exported via the EFM Exporter Plug-In.

• Corrected an issue that occurred when reading symbolic variables with the PACSystems model, where symbolic array and array element tags might not be included in the same request

• The NIC card selected in Channel Properties is now respected by the driver. Prior to this fix, users could have encountered problems with device connectivity when selecting a non-default NIC card.
• Updated the driver to disconnect and reconnect to devices when the NIC selection is changed while clients are connected to the server and requesting item updates from the device.
• Resolved an issue that could occur when processing incoming data for multiple devices under a channel and result in communication deadlock

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

• Fixed faulty browsing logic where the driver would continue attempting to browse after an error was encountered. This could result in the driver being stuck in a loop while browsing.
• Corrected a failure to import tags from servers that do not return the item name in the GetProperties response.
• Fixed a defect where if the target XML-DA server returned OPC quality for an item, the driver would set the tag quality to Good during a subscription poll refresh.

• Added support for BOOL arrays.

• Added a check for the "EA" characters while parsing the response to the AT, AV, CM, CR, FP, and HM commands.

• Fixed an issue where writes to multiple Alarm Setpoints could result in erroneous DNR messages being posted in the Event Log.

• Fixed an issue that prevented Ethernet Encapsulation from binding to a network adapter.
  Note: This issue affects the following drivers: ABB Totalflow, Allen-Bradley Bulletin 900, Allen-Bradley DF1, Analog Devices, Aromat Serial, AutomationDirect DirectNet, AutomationDirect K Sequence, Contrex Serial, Contrex M-Series, Cutler-Hammer D50/300, Cutler-Hammer ELC Serial, Enron Modbus, Fuji Flex, GE CCM, Honeywell UDC Serial, IA Super SEL, Idec Serial, Lufkin Modbus Serial, Micro DCI, Mitsubishi FX, Mitsubishi FX Net, Mitsubishi Serial, Modbus ASCII Serial, Modbus RTU Serial, Omni Flow Computer, Omron FIN Serial, Omron Host Link, Omron Process Suite, Omron Toolbus, Partlow ASCII, Philips P8/PC20, Siemens S5 (3964R), Siemens S5 (AS511), Siemens S7 MPI, Siemens S7-200, Simatic/TI 505 Serial, Thermo Westronics Serial, TIWAY Host Adapter, Toshiba Serial, Toyopuc PC2 Serial, U-CON (User-Configurable), Weatherford 8500 Serial, Yaskawa MP Series Serial, Yokogawa Controller, Yokogawa Darwin Serial, Yokogawa HR2400, and Yokogawa YS100 Serial.
• Fixed an issue where Ethernet Encapsulation failed to load the Network Adapter that was selected in KEPServerEX 5.9 or older. The Network Adapter setting would revert to Default.
  Note: This issue affects the following drivers: ABB Totalflow, Allen-Bradley Bulletin 900, Allen-Bradley DF1, Analog Devices, Aromat Serial, AutomationDirect DirectNet, AutomationDirect K Sequence, Contrex Serial, Contrex M-Series, Cutler-Hammer D50/300, Cutler-Hammer ELC Serial, Enron Modbus, Fuji Flex, GE CCM, Honeywell UDC Serial, IA Super SEL, Idec Serial, Lufkin Modbus Serial, Mettler Toledo Serial, Micro DCI, Mitsubishi FX, Mitsubishi FX Net, Mitsubishi Serial, Modbus ASCII Serial, Modbus Slave RTU Serial, Modbus RTU Serial, Omni Flow Computer, Omron FIN Serial, Omron Host Link, Omron Process Suite, Omron Toolbus, Partlow ASCII, Philips P8/PC20, Siemens S5 (3964R), Siemens S5 (AS511), Siemens S7 MPI, Siemens S7-200, Simatic/TI 505 Serial, Thermo Westronics Serial, TIWAY Host Adapter, Toshiba Serial, Toyopuc PC2 Serial, U-CON (User-Configurable), Weatherford 8500 Serial, Yaskawa MP Series Serial, Yokogawa Controller, Yokogawa Darwin Serial, Yokogawa HR2400, and Yokogawa YS100 Serial.
• Prevented a server crash from occurring when processing incoming data using Unsolicited Ethernet Encapsulation. This issue only affects Metter Toledo Serial, Modbus Slave RTU Serial, and U-CON (User-Configurable).
• Fixed an issue where Unsolicited Ethernet Encapsulation loaded the host port instead of the source port. KEPServerEX 5.9 or older projects would break if the Port was not set to the default value (2101). This issue only affects Metter Toledo Serial, Modbus Slave RTU Serial, and U-CON (User-Configurable).

• Fixed an issue where synchronization failed on controllers with Firmware revision 15 or older that contained CAM_PROFILE Tags. This caused the driver to revert to and stay in Symbolic Mode.

• 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.
  1. In the event of an "Invalid or corrupt project" error during synchronization, we now wait 30 seconds until retrying again. Before we retried immediately which caused unnecessary upload attempts and event log errors.
  2. Added support for failing a synchronization in progress as soon as a project download is detected. Synchronization will be retried after 30 seconds.
• 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:
  1. Added new pre-defined types, DATALOG_INSTRUCTION and HMIBC.
  2. Added several new members to ALARM_ANALOG, ALARM_DIGITAL, and AXIS_CIP_DRIVE per V21 changes.

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

• Added support for a new service introduced in Logix FRN V21 for reading Native Tags, called Symbol Instance Addressing. Physical addressing has been deprecated for V21 but is still supported in the driver for Logix FRN V20 and below. Replaced Physical Non-Blocking and Physical Blocking with Logical Non-Blocking and Logical Blocking to encapsulate these two services.
• Improved the demotion of tags while in an error state by increasing the number of tags failed per transaction. The driver still attempts at least one read tag per transaction to recover from the error state. This does not apply when Auto Demotion is enabled.
• Fixed an issue where project correlation state information was not being properly reset when switching from one device connection to another which could result in that device using Symbolic mode indefinitely.
• Resolved a buffer overrun issue where the Device ID could become corrupt if the length of the portion preceding the comma exceeded 16 characters.
• Added an address validation check to ensure a tag's Symbolic address fits within a single CIP packet. If it exceeds a single packet, the tag will fail with "Address out of range".
• Floats and Doubles written to BOOL, SINT, INT, DINT, and LINT Tags are now clamped in order to prevent roll-over. For example, the Float 4294967395.0 is larger than a DWord (4294967295) and would roll-over to 0. With this fix, 4294967395.0 will be clamped to 4294967295.
• Fixed an issue that occurred when writing to BOOL and SINT Tags for Serial Gateway models.

• Changed the Data Link Layer Confirmation Timeout from 2 seconds to the configurable Channel Response Timeout.
• 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.

• Updated the driver with the new Connection Sharing feature.
• Changed the Data Link Layer Confirmation Timeout from 2 seconds to the configurable Channel Response Timeout.
• 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.

• Updated the driver with the new Connection Sharing feature.
• Fixed an issue where the RTS and Inter-Request Delay settings were not being respected during the write portion of a Read/Modify/Write transaction.

  Note: A Read/Modify/Write transaction occurs when writing to a bit within a register.

• Removed the ability for meter names to begin with an underscore, contain quotation marks or periods, or have leading or trailing whitespace.
• EFM upload (data collection) architecture was enhanced to improve application scalability for projects containing a large number of EFM meters per poll group.

• Added Electronic Flow Measurement (EFM) Support
• Updated the driver with the new Connection Sharing feature.
• Added a device setting to enable/disable sending a device login password.
• When transactions fail due to an Operator ID failure, a single custom error message will now be posted per device.
• Enhanced the driver to consume the extra bytes that may be received following a valid frame. This allows communication with ROC 300 devices, which may append an extra byte to every frame they transmit.

• Added Electronic Flow Measurement (EFM) Support
• Updated the driver with the new Connection Sharing feature.
• Enhanced the driver to consume the extra bytes that may be received following a valid frame.

• Added support for %W addresses above 65,535 for the PACSystems model type.
• Added support to Read/Write Symbolic Variables that are mapped to reference addresses for the PACSystems model type.
• Resolved an issue where the driver was not locking a process thread correctly, which could cause the driver to stop issuing polls to devices.
• Fixed a data alignment issue that occurred when reading and writing symbolic discrete array variables.
  • Symbolic discrete array element tags require two symbolic information requests in order to calculate the start byte based on the base array address and the array index.
  • Recalculate the native data size of symbolic discrete array and array elements depending on data type.
  • Fail request and report warning message occur if the symbolic discrete array native data size exceeds the maximum request size (because it cannot be caught in the address parser).
  • Corrected a pre-existing issue in the tag import to force the "{" on array element tag addresses.
  • Handle nested symbolic discrete array variables.
  • Clear previously collected symbol information after an invalid PVT version.

• Fixed data conversion for BCD and LBCD arrays.
• Added support of the Double data type for AI, AQ, and R memory types.
• Added hints for Array data types.

• Updated the driver with the new Connection Sharing feature.
• Resolved an issue where the Standard, Start, and Pump Up coil addresses were configured with the five card buffer instead of the single card buffer. Also corrected an issue where the Last Shutdown card was using the first of the five card buffers instead of the last of the five card buffers.

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

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

• Updated the driver with the new Connection Sharing feature.
• Updated the driver schema to improve EFM meter name validation.
• Fixed an issue where the RTS and Inter-Request Delay settings were not being respected during the write portion of a Read/Modify/Write transaction.

  Note: A Read/Modify/Write transaction occurs when writing to a bit within a register.

• Removed the ability of meter names to begin with an underscore, contain quotation marks or periods, or have leading or trailing whitespace.
• EFM upload (data collection) architecture was enhanced to improve application scalability for projects containing a large number of EFM meters per poll grou

• Previously, the driver would automatically filter out the data types that it could not resolve in a browser. It will now import these tags using the Default data type, and will also post a message to the Event Log.
• Fixed an exception that would occur when invalidating tags while unloading the driver.
• Fixed a reconnect issue where the shutdown sink flag was not cleared.
• Fixed an issue where valid data change events were thrown away because the driver received data change events on items before they were fully added.

• Fixed an issue where the Default data type on a Static Tag using a dynamic address had Bad Quality.
• Fixed an exception that would occur when invalidating tags while unloading the driver.

• Added Applicom address syntax to provide both Byte and Word order control at the tag level.
• Fixed a Read/Write issue introduced in 4.190 that can occur for S7-200 addresses utilizing the KT suffix.
• Added Read/Write support for the S7 TIME data type as String for the following memory types: DB, I, E, Q, A, PI, PE, PQ, PA, M, and F.
• Added Read/Write support for the S7 DATE data type as String for the following memory types: DB, I, E, Q, A, PI, PE, PQ, PA, M, and F.
• Added write support for the S7 TIME_OF_DAY data type as String for the DB memory type.
• Updated the Read/Write support for the S7 TIME_OF_DAY data type as String to include the following memory types: I, E, Q, A, PI, PE, PQ, PA, M, and F.
• Updated the read support for the S7 DATE_AND_TIME data type as String or Date to include the following memory types: I, E, Q, A, PI, PE, PQ, PA, M, and F.

• Fixed an issue where the Device ID could become corrupt if any three octets of the IP contained exactly three digits and the remaining octet was set to 44.
• Updated the "Supported Devices" list in the help file to display support for RS Logix V20.
• Added the '#' symbol to the ControlLogix Predefined Tag addressing syntax as an alternative to the '@' symbol. Previous usage of the '@' symbol conflicted with the dynamic tag addressing syntax used by the server.
• Added the new device-level internal tag "_FailedConnection" that indicates the driver failed on its attempt to connect to the device.

• Logix LINT arrays no longer allow a data type of Date array.
• Fixed an issue with the reading of and writing to Logix LINT data.
• Fixed an issue with the reading of String type values that are less than 32 characters.
• Fixed an issue with the reading of and writing to the following array types: Char, Byte, Short, Word, Long, DWord, Float, and Double.

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

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

Added support for the use of legacy tag names as part of Automatic Tag Generation. This enhancement was made to resolve a change introduced in the 5.8 release where tag formats created via Automatic Tag Generation were different than previous versions. This tag format issue only affects users who upgraded to version 5.8 and triggered tag regeneration.

For new installations of Fisher ROC Plus driver (server version V5.9 and up), the default setting for this checkbox is 'checked' so legacy tag names are used.

Added support for the use of legacy tag names as part of Automatic Tag Generation. This enhancement was made to resolve a change introduced in the 5.8 release where tag formats created via Automatic Tag Generation were different than previous versions. This tag format issue only affects users who upgraded to version 5.8 and triggered tag regeneration.

For new installations of Fisher ROC Serial driver (server version V5.9 and up), the default setting for this checkbox is 'checked' so legacy tag names are used.

• Enhanced the driver's Open model to support the Series 30i device.
• Fixed an issue where the driver was not communicating after the device was disconnected and then reconnected.

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

• Increased the character limit of the tag Description field from 64 to 255.
• Added a new option for handling illegal address exceptions that allows users to deactivate tags when an illegal address is detected.

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

• Fixed an issue where tags containing the "GUID" Node ID type were not being validated correctly.
• Fixed an issue in the Tag Import Browser where parent node tags would be imported even when only a child node was selected.

• Fixed an issue where the Byte Order (Big Endian or Little Endian) for a tag could unexpectedly change. This occurred when there were two or more devices under one channel that had tags pointing at the same address, but with a different Byte Order selected. This could result in an incorrect Byte Order for one or all of those tags.
• Added support for the Date data type for the Siemens DATE_AND_TIME (DT) data block memory type.
• Added write support for the Siemens TIME_OF_DAY (TOD) data block memory type.

• Fixed an issue where the configuration client would crash when the driver attempted to automatically generate tags while disconnected from the Runtime.
• Prevented a deadlock issue that could occur if multiple pieces of outgoing data were queued while the driver was processing incoming data. This change affects the Transmit and Transmit Byte Commands.
• Fixed an issue where the "Update Tag" command no longer fails when used in an unsolicited mode tag and the tag type is "Dynamic ASCII Format".
• DWord tags that use "ASCII Integer" or "ASCII Integer (packed 6 bit)" now support the full DWord range.
• The "Update Tag" command now updates a numeric data tag that uses the "Byte from 2 ASCII Hex Chars (hh)" or "Nibble from 1 ASCII Hex Char" format.
• Fixed an issue where transaction commands were unavailable from the Edit menu if the Transaction window was selected.
• Increased the character limit for Tag Group Names and Tag Names to 255.
• Added the new Custom Checksum "Custom #13 (8-bit)". This checksum sums the bytes and then subtracts the sum from zero.

• Fixed a threading issue where the driver would report the wrong value for a tag if there were multiple devices in a project and one of the devices responded with a negative number.
• Fixed an issue where a crash could occur if a device responded with unexpected packets.

• Fixed the blank message box displayed by some drivers (following an attempt to change a setting that is not allowed to change) while data collection is active on a channel or device.
• Added device-level diagnostic support to most drivers.

  Note: The following drivers do not support device-level diagnostics: AB Unsolicited Ethernet, Advanced Simulator, Dataforth IsoLynx, DDE Client, DNP Master Serial, DNP Master Ethernet, GE Ethernet Global Data, GE Focas1 Ethernet, GE Focas1 HSSB, Hilscher Universal, InTouch Client, Memory Based, Mettler Toledo Serial, Modbus Unsolicited Serial, ODBC Client, OPC DA Client, OPC UA Client, Simulator, Siemens TCP/IP Unsolicited Ethernet, and Telemecanique Uni-Telway Slave.

• Fixed the incorrect font that was applied to the Channel Wizard dialog "Suggestions" on Chinese language operating systems.
• Added support for the following pre-defined tags: @REVISION, @STATUS, @MODE, @VENDORID, @PRODUCTCODE, @PLCTYPE, and @PROCESSORNAME.
• Fixed an issue where the driver could report incorrect data to client applications if the value read was greater than 262,136 bytes (such as in an array of 65535 DINTs). This only occurred on devices configured for Physical Blocking Mode.
• Updates for RSLogix version 20. The following was included for offline automatic tag generation:
  • Added the new pre-defined types DCAF_INPUT and DCA_INPUT.
  • Added several new members to the following (per V20 changes): AXIS_CIP_DRIVE, AXIS_CONSUMED, AXIS_GENERIC, AXIS_GENERIC_DRIVE, AXIS_SERVO, AXIS_SERVO_DRIVE, AXIS_VIRTUAL, COORDINATE_SYSTEM, MOTION_INSTRUCTION, and MOTION_GROUP.
• Performance statistics are now properly disabled when non-ControlLogix models are selected.

• Corrected issues that prevented the Port Number device property from persisting in sheet mode.
• Corrected issues in wizard mode that caused changes to the Port Number to be lost after leaving the page and returning to wizard mode.
• For TwinCAT PLC models, do not attempt to read device version information if the API dlls are missing (or if generating tags from a symbol file).
• Optimized communications with TwinCAT PLC models by minimizing the overhead previously put on the device.
• Automatically generated tags no longer allow clients to override the assigned data type.

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

• Added the "Port Offset" device property to the Network Analyst sheet and wizard pages.
• Changed the "Points in Moving Average" key combination shortcut on the Network Analyst sheet and wizard pages from Alt-A to Alt-M.
• Increased the maximum number of channels from 100 to 256.

1. Added a new warning for situations where the model series received from the device does not match the model that was configured in the device. Reverted the behavior that was introduced in the 5.4 server release that reported an error and did not allow unsupported model series. Reverted to the previous behavior that ignored the invalid model series returned from the device. Set the model series to that of the configured model in this situation.
2. Added a new warning for situations where the model series is unsupported.
3. Displayed the model series string in the Model Tag even if it doesn't match a series in the list. Previously, the tag displayed Unknown with Bad quality when the model series was not supported.

- Added support for AS1 Advanced Security Option.

1. Added support for MX style 3 Firmware.
2. Added tag address "Unit.Firmware" to display the Firmware version information as a string of four hex octets.
3. Reports unit style and module count information to Event Log.
4. Corrected an issue where error 'FFFF' was erroneously reported on tags when a DNR was reported.

- Added support for Function File CS1. Applicable to the Micrologix 1500.
- Fixed Function File HSC:CU and CD to be Read-Only as documented in the Help File.
- Fixed issue where a write of LEN bytes to an ASCII (A File) string of length LEN would write two NULL terminators to the bytes following the string.
- Added SLC 5/05 to Model selection.
- Fixed Half-Duplex Master issue that would halt writes to a Slave if a previous Master Message write request was never received by the Slave.
- Fixed ASCII (A File) issue where the last element of an array would always read NULL for arrays of even length size starting at an odd byte offset.

- NetEdit launch has been moved to General tab on Device Properties dialog.
- Fixed issue in which reading a block of 32-bit values (i.e. Float) could exceed the maximum number of bytes allowed by the device, resulting in a 'Device Not Responding' error.
- Fixed write toggle issue when writing to Control Relays (C).
- Added array support for Data Words (V). Support includes Word, Short, BCD, DWord, Long, LBCD and Float arrays.

- Addition of the following new element types: CYCCNT, CAVSET, CAVCNT, ALARM.

- Added Bit within Word Support for the V Registers.

- Added support for an Inter-request delay.
- Added unsolicited support for function code 08, sub function code 00 support (AKA Loopback).
- Added unsolicited support for the following 3 data encoding options: Modbus byte order, First word low in 32 bit data types and First Dword low in 64 bit data types.
- Fixed issue where the "First Dword low in 64-bit data types" checkbox was not honored when reading/writing to tags of type double.
- Added support for multiple slave devices.