Blame | Last modification | View Log | Download
MBX OPC Server Version 6.0.0 + Update 20060112 Release NotesJanuary, 2006------------------------------------------------------------------Table Of Contents------------------------------------------------------------------1. What's New in MBX OPC Server 6.0.0 + Update 200601122. System Requirements1. What's New in MBX OPC Server 6.0.0 + Update 20060112-------------------------------------------------------* The ability to import server configuration from the Concept text delimited variablefiles has been added.* The OPC DA 3.0 Browse function could return a continuation point after returning thelast elements in the branch. With some OPC clients, this might result in an endlessbranch enumeration. The problem has been corrected.* Under some conditions, the continuation point returned from the OPC DA 3.0 Browsefunction could be built incorrectly. With some OPC clients, this might result in errorsduring browsing. The problem has been corrected.* The GetErrorString function for a few common error codes was not returning the errordescription string. These error codes are now properly handled.* The OPC server did not properly handle data conversions for arrays of variants. Theproblem has been corrected.* Under some conditions, the master quality returned from the read operations might havea value other than S_OK, even when the quality values for all returned data was GOOD.The problem has been corrected.* The OPC XML DA server layer has been upgraded to comply with the latest compliance testsfrom the OPC Foundation.* The OPCDAAuto.dll, which implements the OPC Data Access Automation 2.02 layer has beenadded.* "Using the Cyberlogic OPC Server via DCOM" white paper has been added.* Numerous updates to the help files have been added.* Installing the MBX OPC Server after another Cyberlogic OPC server has already beeninstalled was deactivating the current configuration file. The problem has beencorrected.* In some situations, the duplicate data item feature would not work asexpected in the OPC Configuration Editor. This has been corrected.* Floating point numbers that used commas instead of decimal points are nowproperly imported by the OPC Configuration Editor.* Some minor product installation issues have been corrected.* Some components have been updated to ensure consistency among allMBX products.2. System Requirements----------------------* MBX OPC Server Version 6.0.0 + Update 20060112 requiresWindows XP/2000/NT 4.0/Server 2003.******************************************************************* End of MBX Driver Version 6.0.0 + Update 20060112 ** Release Notes *******************************************************************6.0.0>MBX OPC Server Version 6.0.0 Release Notes6.0.0>September, 20056.0.0>6.0.0>------------------------------------------------------------------6.0.0> Table Of Contents6.0.0>------------------------------------------------------------------6.0.0>1. What's New in MBX OPC Server 6.0.06.0.0>2. System Requirements6.0.0>6.0.0>1. What's New in MBX OPC Server 6.0.06.0.0>-------------------------------------6.0.0>* To simplify repairs, Add/Remove Programs now lists a single product for the6.0.0> Suite, rather than separate entries for each component.6.0.0>6.0.0>* The MBX OPC Server now uses the same main OPC server component as the rest of6.0.0> the Cyberlogic OPC servers. As a result, the ProgID for the DA server changed6.0.0> from "Cyberlogic.MBX_OPCServer.5" to "Cyberlogic.OPCServerDA.6". The ProgID6.0.0> for the AE server changed from "Cyberlogic.MBX_OPCEventServer.5" to6.0.0> "Cyberlogic.OPCServerAE.6". When upgrading from version 5.0, the OPC client6.0.0> configurations need to be modified to reflect the new ProgIDs.6.0.0>6.0.0>* The file format for the configuration database files has changed. When upgrading6.0.0> from version 5.0, the old configuration .mdb files need to be imported into the6.0.0> version 6.0 configuration files. All configuration settings will be preserved.6.0.0>6.0.0>* Support for OPC DA 3.0 and OPC XML DA 1.0 has been added.6.0.0>6.0.0>* Support for OPC Alarms and Events has been upgraded from version 1.02 to 1.1.6.0.0>6.0.0>* Support for Global Data has been added.6.0.0>6.0.0>* The Maximum Concurrent Requests parameter for a Network Node has been added.6.0.0> Proper setting of this parameter may prevent overloading the node with messages6.0.0> and allow for better operation of other applications, such as PLC programming6.0.0> software, that access the same PLC.6.0.0>6.0.0>* Support for raw data bit-swapping at the bit, nibble, byte, word or double-word6.0.0> level has been added.6.0.0>6.0.0>* Server auto-configuration has been enhanced to support all network types,6.0.0> including the serial Modbus. Auto-configuration can detect all standard data6.0.0> sources (PLCs) and automatically sets their message optimization parameters.6.0.0>6.0.0>* For large data items, such as strings, arrays and bit fields, user can now6.0.0> configure either an atomic, single message access, or give server the permission6.0.0> to span data across multiple messages. Selecting an atomic access can prevent6.0.0> possible data tearing.6.0.0>6.0.0>* A number of new data types have been added. These include 8-bit and 64-bit6.0.0> integers, IEEE 64-bit floating point, 16-bit and 32-bit BCD, 16-bit UNICODE6.0.0> strings.6.0.0>6.0.0>* The ability to override the canonical data type, the default variant format6.0.0> (VT_xxx) in which data is sent to OPC clients, has been added. By default, the6.0.0> server matches the variant type to the item's raw data type.6.0.0>6.0.0>* Support for bit arrays has been added.6.0.0>6.0.0>* Support for writing to bit field data has been added.6.0.0>6.0.0>* Four commonly used address notations can now be used interchangeably: standard6.0.0> (400001) notation, separator (4:00001) notation, compact (4:1) notation, and IEC6.0.0> (QW00001) notation.6.0.0>6.0.0>* A register address wizard has been added to aid in creating sophisticated address6.0.0> expressions.6.0.0>6.0.0>* The unsolicited message filters can now be organized in multiple groups. Each6.0.0> group can be either priority or non-priority based. All groups have an equal6.0.0> priority and an unsolicited message must pass through at least one of these6.0.0> groups in order to be accepted by the server.6.0.0>6.0.0>* The ability to disable writes at the Network Connection and the driver agent (all6.0.0> connections) level has been added.6.0.0>6.0.0>* In addition to each Network Node, the DirectAccess can now be disabled at the6.0.0> Network Connection and the driver agent (all connections) level.6.0.0>6.0.0>* In addition to each Network Node, the DirectAccess writes can now be disabled at6.0.0> the Network Connection and the driver agent (all connections) level.6.0.0>6.0.0>* The DirectAccess register address format has been improved to be more consistent6.0.0> with other Cyberlogic OPC servers. The old format is still supported.6.0.0>6.0.0>* The configuration import/export in the configuration editor has been greatly6.0.0> improved.6.0.0>6.0.0>* The format for the comma delimited (.csv) and tab delimited (.tab) configuration6.0.0> export files has been improved. However, export files from version 5.0 can still6.0.0> be imported. The new format allows for easier editing of these files.6.0.0>6.0.0>* An XML file format for exporting configuration files has been added.6.0.0>6.0.0>* The ability to import directly from the Cyberlogic .mdb configuration files (old6.0.0> and new format) has been added.6.0.0>6.0.0>* The ability to import configuration files from other OPC server vendors has6.0.0> been added. This includes csv files from Ingear OPC Server, Kepware KEPServerEX6.0.0> and Matrikon OPC Server.6.0.0>6.0.0>* DCOM interoperability has been improved. Instead of using a single, fixed,6.0.0> security setting, the server allows three levels of DCOM security: Low, Medium,6.0.0> and Custom. The Low setting is the most commonly used and matches the setting6.0.0> used in version 5.0 of the MBX OPC server. The Medium is another popular6.0.0> setting used by many OPC clients. If neither of the two is correct, the6.0.0> Custom setting allows you to set the permissions yourself through the Windows6.0.0> DCOMCNFG utility.6.0.0>6.0.0>* The Cyberlogic OPC Client utility has many new features, including: support6.0.0> for OPC DA 3.0, error logging, three levels of DCOM security settings, and6.0.0> support for the IOPCShutdown interface.6.0.0>6.0.0>* Under some conditions (e.g. reloading of the PLC) the monitored tags might6.0.0> all switch to BAD quality and stay in that state. To recover from this6.0.0> condition, the Save & Update Server button had to be pressed. In the current6.0.0> version, the server will automatically recover from this condition.6.0.0>6.0.0>* When accessing an invalid register address, a monitored tag could show a BAD6.0.0> quality, even after the missing register had been added to the PLC's memory map.6.0.0> To recover from this condition, the Save & Update Server button had to be6.0.0> pressed. In the current version, the server will automatically recover from6.0.0> this condition.6.0.0>6.0.0>* The health state detection of a network node has been improved. For example,6.0.0> a PLC placed in a dim awareness mode is now flagged as unhealthy, forcing a6.0.0> switchover to a lower priority (but healthy) access path.6.0.0>6.0.0>* During writes, string variables that are shorter than the allocated space in6.0.0> the PLC are no longer padded with spaces. Instead, they are padded with NUL6.0.0> characters. This change was necessary for better compliance with the OPC6.0.0> Foundation's compliance test.6.0.0>6.0.0>* The runtime component of the OPC server has been greatly optimized, resulting6.0.0> in higher performance and significantly lower load on the system.6.0.0>6.0.0>* The server shutdown operation has been improved. The server deals better with6.0.0> the misbehaving clients when shutting down.6.0.0>6.0.0>* Various bugs ranging from unexpected operation to system exceptions have been6.0.0> corrected.6.0.0>6.0.0>* Some components have been updated to ensure consistency among all MBX driver6.0.0> products.6.0.0>6.0.0>2. System Requirements6.0.0>----------------------6.0.0>* MBX OPC Server Version 6.0.0 requires Windows XP/2000/NT 4.0/Server 2003.6.0.0>6.0.0>******************************************************************6.0.0>* End of MBX Driver Version 6.0.0 Release Notes *6.0.0>******************************************************************5.00.02>MBX OPC Server Version 5.00.02 Release Notes5.00.02>April, 20045.00.02>5.00.02>------------------------------------------------------------------5.00.02> Table Of Contents5.00.02>------------------------------------------------------------------5.00.02>1. What's New in MBX OPC Server 5.00.02?5.00.02>2. System Requirements5.00.02>5.00.02>1. What's New in MBX OPC Server 5.00.02?5.00.02>----------------------------------------5.00.02>* In some configurations, data quality was alternating between Good and5.00.02> Bad while reading data. This most commonly occurred when a large number5.00.02> of configured network nodes (i.e. PLC's) were not physically connected5.00.02> to the network. The problem has been corrected.5.00.02>5.00.02>* Some non-PLC devices (e.g. Square D ALTIVAR 58 drive controller) were5.00.02> not properly detected, resulting in inability to communicate to them.5.00.02> A new detection algorithm has been implemented to alleviate this problem.5.00.02>5.00.02>* Some components have been updated to ensure consistency among5.00.02> all MBX products.5.00.02>5.00.02>2. System Requirements5.00.02>----------------------5.00.02>* MBX OPC Server Version 5.00.02 requires Windows NT 4.0 or5.00.02> Windows 98/Me/2000/XP.5.00.02>5.00.02>******************************************************************5.00.02>* End of MBX OPC Server Version 5.00.02 Release Notes *5.00.02>******************************************************************5.00.01>MBX OPC Server Version 5.00.01 Release Notes5.00.01>September, 20025.00.01>5.00.01>------------------------------------------------------------------5.00.01> Table Of Contents5.00.01>------------------------------------------------------------------5.00.01>1. What's New in MBX OPC Server 5.00.01?5.00.01>2. System Requirements5.00.01>5.00.01>1. What's New in MBX OPC Server 5.00.01?5.00.01>----------------------------------------5.00.01>* Configuration changes can now be applied on-line, while the OPC5.00.01> clients are connected to the server.5.00.01>5.00.01>* Ability to undo recent edits has been added. Until new edits are5.00.01> saved, a user can always revert back to the previously saved5.00.01> configuration.5.00.01>5.00.01>* Support for bit fields in Direct Access has been added.5.00.01>5.00.01>* Some components have been updated to ensure consistency among5.00.01> all MBX products.5.00.01>5.00.01>2. System Requirements5.00.01>----------------------5.00.01>* MBX OPC Server Version 5.00.01 requires Windows NT 4.0 or5.00.01> Windows 98/Me/2000/XP.5.00.01>5.00.01>******************************************************************5.00.01>* End of MBX OPC Server Version 5.00.01 Release Notes *5.00.01>******************************************************************5.00.00>MBX OPC Server Version 5.00.00 Release Notes5.00.00>December, 20015.00.00>5.00.00>------------------------------------------------------------------5.00.00> Table Of Contents5.00.00>------------------------------------------------------------------5.00.00>1. What's New in MBX OPC Server 5.00.00?5.00.00>2. System Requirements5.00.00>5.00.00>1. What's New in MBX OPC Server 5.00.00?5.00.00>----------------------------------------5.00.00>* This is the first release of this product.5.00.00>5.00.00>2. System Requirements5.00.00>----------------------5.00.00>* MBX OPC Server Version 5.00.00 requires Windows NT 4.0 or5.00.00> Windows 98/Me/2000/XP.