TOP Server Release Notes (5.4.135.0) November 2, 2010

Plug-ins

• 
  Next and Previous buttons now apply changes to the current tag.
  
• 
  With regard to the Link Tags' “On Value” Trigger Mode, updated strings are now shown in the Comparison dialog to make the list format consistent.
  

• 
  Comparisons are now shown in the Sub-Condition dialog to make the list format consistent.
  

• 
  The trigger XML load routine now follows the GUI in enforcing the rule that either the Log on Static Interval or Log on Data Change must be set to true.
  
• 
  Fixed an issue with XML load bug with absolute triggers, wherein the days of the week value was not loading correctly.
  
• 
  Fixed an issue wherein sessions were not being closed if an error was thrown by the ODBC layer. This resulted in excess connections to the database.
  
• 
  Fixed an issue wherein Legacy 4x projects with Log on Static Interval unchecked failed to pass schema validation in 5.3. Fixed an issue wherein Legacy 5x projects with Log on Static Interval unchecked failed to display No in the Interval column on the Triggers tab in 5.3.
  

• 
  Added support for ISO 10646 (UCS-2) and ISO 8859-1 (Latin1) character sets.
  
• 
  Added a number of object properties to meet the 2008+ BACnet specification, in addition to support for simple array properties (arrays of primitive BACnet data types).
  
• 
  Increased the maximum number of channels from 32 to 128.
  
• 
  Added enumerated values and corresponding strings to support approximately forty new BACnet Error codes.
  
• 
  Added a new error class.
  
• 
  Fixed an issue wherein tags with a default client access of Read Only could not be set to Read/Write, even if Write access was allowed.
  
• 
  Addendum “Add-2004-135m” specifies a small change to the way segment ACK timeouts function. Before the change, Addendum timing started at the beginning of the Request window (during which one or more segments were sent). In some cases, this caused unnecessary timeouts for larger window sizes. Now, the timer starts after the first segment is sent, after all the segments in the window (1 or more) are sent, or after the last segment is sent to the device.
  
• 
  Modified BACnetNetworkLayer to be able to route COV notifications from a device on a different BACnet network where NPDUs do not contain the source address. Although the behavior does not appear to meet the BACnet spec, this precedent has been set by the support of other vendors. A channel property was added to enable/disable this setting. It is disabled by default (since it could degrade performance if the BACnet network has a large volume of broadcast messages).
  
• 
  Modified the driver so that duplicate Device IDs are not allowed on a channel.
  
• 
  Increased the COV re-subscription interval maximum value from 1 hour to 24 hours.
  
• 
  Added an option for ALC devices to use a Subscriber Process Identifier (SPID) of 0. ALC devices consider all subscriptions with an SPID of 0 to be 1 subscription.
  
• 
  Added an option to wait for the device to acknowledge COV cancellations. This prevents the Runtime from shutting down until all COV subscriptions have been cancelled. Note: In very large projects, this shutdown delay can make the Runtime seem unresponsive.
  

• 
  Added support for TwinCAT PLC version 2.9. The driver now queries the version information to determine what function codes can be used to communicate with the controller.
  

• 
  Fixed an issue with broadcast mode (Device ID of 0) wherein Write tags were not being released properly.
  

• 
  Added NAK handling for the half-duplex and radio modem link protocols. This situation may occur if communicating to a device configured for full-duplex.
  

• 
  Updated the driver to release items more quickly for unresponsive devices, following client disconnect.
  
• 
  Added Keep-Alive Interval device property to the Communication page as well as an Event Log message to warn the user if loading an XML project discovers a Keep-Alive interval configured for a UDP channel.
  
• 
  Enhancements for Phase I support of WITS specification include the following.
  
  • 
    Device Attribute - Object Group 0:
    

• 
  Standard Attributes at Index 0 (such as Vendor Name, Product Name, Site Name, Software Version, Hardware Version, Configuration File Names, and Configuration File Version).
  
• 
  User Defined Attributes for Index 1 and above.
  
• 
  Read Only.
  
• 
  Secure Authentication – Object Group 120:
  
  • 
    Challenge – Response.
    
  • 
    Pre-shared Update Keys.
    
  • 
    Aggressive Mode.
    
  • 
    Session Keys - bidirectional.
    
  • 
    Security Statistics.
    
• 
  Data Sets – Object Groups 85, 86, 87, and 88:
  
  • 
    Prototypes.
    
  • 
    Descriptors.
    
  • 
    Event and Static conditions.
    
  • 
    Outstation defined data sets.
    
  • 
    Read Only.
    
• 
  Added an error message for the situation in which a device's Slave address is a duplicate of another device's Master or Slave address.
  
• 
  Added an error message for the situation in which a device contains the same Master and Slave address.
  
• 
  Added the following internal tags:
  

• 
  _Protocol
  
• 
  _DestinationHost
  
• 
  _DestinationPort
  
• 
  _SourcePort
  
• 
  _ChannelResponseTimeout
  
• 
  _IntegrityPollInterval
  
• 
  _EventClass1PollInterval
  
• 
  _EventClass2PollInterval
  
• 
  _EventClass3PollInterval
  
• 
  _DeviceRequestTimeout
  

• 
  Updated the driver to release items more quickly for unresponsive devices, following client disconnect.
  
• 
  Added support for communication serialization.
  
• 
  Enhancements for Phase I support of WITS specification include the following.
  
• 
  Device Attribute - Object Group 0:
  

• 
  Standard Attributes at Index 0 (such as Vendor Name, Product Name, Site Name, Software Version, Hardware Version, Configuration File Names, and Configuration File Version).
  
• 
  User Defined Attributes for Index 1 and above.
  
• 
  Read Only.
  
• 
  Secure Authentication – Object Group 120:
  

• 
  Challenge – Response.
  
• 
  Pre-shared Update Keys.
  
• 
  Aggressive Mode.
  
• 
  Session Keys - bidirectional.
  
• 
  Security Statistics.
  
• 
  Data Sets – Object Groups 85, 86, 87, and 88:
  

• 
  Prototypes.
  
• 
  Descriptors.
  
• 
  Event and Static conditions.
  
• 
  Outstation defined data sets.
  
• 
  Read Only.
  
• 
  Added an error message for the situation in which a device's Slave address is a duplicate of another device's Master or Slave address.
  
• 
  Added an error message for the situation in which a device contains the same Master and Slave address.
  
• 
  Added the following internal tags:
  

• 
  _ChannelResponseTimeout
  
• 
  _IntegrityPollInterval
  
• 
  _EventClass1PollInterval
  
• 
  _EventClass2PollInterval
  
• 
  _EventClass3PollInterval
  
• 
  _DeviceRequestTimeout
  

• 
  Fixed an issue wherein Symbolic Tags were being forced to Read/Write.
  

• 
  Fixed an issue wherein all models except the Series 15i had one or more invalid address ranges. This issue was introduced with the addition of CNC status info tags.
  

• 
  Added SNP protocol specific error messages to the driver.
  

• 
  Added SNP protocol specific error messages to the driver.
  

• 
  Fixed an issue wherein the driver did not properly reject a response from a Device ID that was different than was sent in the request packet.
  

• 
  Resolved issue for native Boolean address types where driver returned “Bad Address” instead of “Bad Type” on first attempt at adding dynamic tag of data type Double.
  
• 
  Fixed an issue wherein the parser did not accept addresses for X, Y, W, and ZR if the hex component immediately followed the memory type.
  

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

• 
  Increased the number of channels from 100 to 256.
  

• 
  Fixed an issue with queries wherein the driver failed to read tags if the query included a UNION.
  
• 
  The EnableMiscellaneousQuerySettings registry setting was broken in 5x due to the separation of the Runtime and Configuration. The registry setting was removed, and the dialog page made visible to all users. A related wizard page was also added.
  

• 
  Added support for the CJ2 Model.
  
• 
  Modified the driver to handle the relay error frame when a fatal CPU error is present. The error messages were also updated to include “Main, Sub:” and “Net Addr, Node Addr:” in decimal notation: this should make it easier for users to compare to Device Property settings in the server project.
  
• 
  Added the reporting of device-level error conditions and detection of network relay error frames. We now output the following error messages instead of posting "Device not responding" messages:
  

• 
  Network relay error.[Net Addr, Node Addr: '0x00, 0x3A'], [End Code: '0x8302']
  
• 
  Fatal CPU Unit error.[End Code: '0x0080']
  
• 
  Non-fatal CPU Unit error.[End Code: '0x83C2']
  

• 
  Added support for the CJ2 Model.
  
• 
  Added the reporting of device-level error conditions and detection of network relay error frames. We now output the following error messages instead of posting "Device not responding" error messages:
  

• 
  Network relay error.[Net Addr, Node Addr: '0x00, 0x3A'], [End Code: '0x8302']
  
• 
  Fatal CPU Unit error.[End Code: '0x0080']
  
• 
  Non-fatal CPU Unit error.[End Code: '0x83C2']
  

• 
  When adding groups, the time bias is now properly initialized to zero. At this moment, this setting is not user-configurable.
  
• 
  Fixed an issue wherein the initial update was not passed on to client applications.
  
• 
  Removed the limit that prevented the creation of nested groups with depth greater than 8.
  

• 
  Fixed an issue wherein the initial update was not passed on to client applications.
  
• 
  Improved the browse code to report a single failure instead of multiple failures per browse request.
  
• 
  Added support for the browseNext method, allowing clients to browse and import nodes from a server that limits the max returned nodes.
  
• 
  Fixed a deadband issue wherein we were not correctly passing in the client item handle for the item to which deadband was applied.
  
• 
  Removed the driver tag address limit of 1024.
  
• 
  Fixed duplicate browse entries when performing a full refresh through the context menu in the server browser.
  

• 
  Modified the driver to support locale-specific multi-byte strings.
  

• 
  Ehanced MIB parsing capabilities by providing the ability to multi-select MIBs for import, and also made the parser more tolerant of minor MIB warnings (syntax or format) that should not prevent import.
  
• 
  The user is now prompted when a MIB dependency exists in both the repository and the Import target directory. If the user confirms overwriting, the repository file will be deleted and the target file will be added to the repository.
  
• 
  Importing a file that is contained in the repository now causes the existing file to be deleted, and the new file added. Before, the old file was not deleted and the two files coexisted.
  
• 
  Formatting change for user imported MIBs from "UserImported-" to
  
• 
  "UserImported-_".
  
• 
  Fixed an issue in the MIB Import tab of Device Properties wherein selecting "Customize" following removal of a module would re-add the previously removed module.
  
• 
  Added the SNMP GetBulk command in order to read multiple OIDs from individual tables more efficiently. This is a user-selectable device property and is only used for SNMP version 2c.
  
• 
  Fixed an issue wherein traps with snmpTrapOid varbinds with trailing “.0s” were not handled correctly.
  
• 
  Fixed an issue with processing trap events from devices that pad the timestamp of the trap event packet with zeros.
  

• 
  Fixed issue where projects created in server/driver version 5.3 that used WriteDeviceID and WriteEventCounter commands would fail version comparison and not load the project in 5.4.
  
• 
  Fixed an issue wherein legacy .opf projects saved as xml would fail to pass schema validation.
  
• 
  Modified Transaction Editor Write commands, and also added Data destination radio buttons for Read, Write, Scratch, and Global buffers for commands CmdWriteDeviceId, CmdWriteEventCounter, and CmdWriteCheckSum.
  
• 
  Increased the Device ID value limit from 255 to 65535.
  
• 
  The Transaction Editor posted an incorrect validation message when creating a Cache Write Value command without a preceding Transmit command. A Write Data command is required before a Cache Write Value command. A Transmit command is not required. Both the validation and error message have been updated.
  
• 
  Fixed an issue wherein the driver sometimes failed to respect signed data types if the device data format had fewer bytes than the data type. Signed data types would not correctly display negative values. The driver now always respects whether the data type is signed when converting to and from the device format.
  

• 
  Enabled error message posting for failed write tags from a non-responding device.
  
• 
  Fixed an issue wherein the driver would not properly release tag references under certain conditions. This resulted in stale tag data, and stopped further updates from being passed on to client applications.
  

• 
  Removed tag duplication during automatic tag generation.
  

• 
  Removed tag duplication during automatic tag generation.
  

• 
  Removed tag duplication during automatic tag generation.
  

• 
  Removed tag duplication during automatic tag generation.