Last revision: 05/25/2010
This document contains important information about the Wonderware® MBTCP DAServer 2.0. Please carefully review this document for known issues in this version and changes, if any, to the MBTCP DAServer 2.0 documentation included on this CD.
MBTCP DAServer 2.0 and DIObjects incorporate the latest Microsoft C Runtime components. Additionally, the MBTCP 2.0 DIObjects require .NET 3.5 SP1 Framework and provide the Active on Demand and Time Propagation features. For these reasons, MBTCP 2.0 DIObjects are compatible only with Application Server 3.1 SP2 and later versions. The DAServer in stand-alone mode has no dependency on Application Server.
This release of the MBTCP DAServer 2.0 and
its DIObjects delivers significant enhancements in functionality; a new
version of the DAServer Runtime Components is also
being delivered to increase the MBTCP DAServer’s
performance. The MBTCP DAServer 2.0 offers the following new features and enhancements.
The MBTCP DAServer 2.0 offers the following enhancements:
The DAServer Manager provides the ability to assign redundant devices for fail-over protection in the event of device failure. Two identical devices are expected to be configured in the DAServer Manager having identical item syntax, connected to the same DAServer.
The DAServer supports only out-of-proc activation.
MBTCP 2.0 DAServer and DIObjects add support for the following operating systems:
Note: 64-bit processor support is provided through the use of Microsoft's WoW64 emulation component.
MBTCP DAServer supports UAC-enabled run-time operations without user privilege elevation.
As of this release, the default location for the DAServer configuration file and rule file is relocated out of the C:\Program Files\Wonderware\DAServer\DASMBTCP folder.
Existing configuration files from previous releases will automatically be moved to the new location during DASMBTCP 2.0 installation on the platform.
MBTCP 2.0 DAServer and DIObjects incorporate the latest Microsoft C Runtime components and the .NET 3.5 SP1 Framework. For this reason, MBTCP 2.0 DAServer and DIObjects are compatible only with Application Server 3.1 SP2 and later versions. Additionally, the MBTCP 2.0 DIObjects require .NET 3.5 SP 1 Framework and provide the Active on Demand and Time Propagation features. For these reasons, MBTCP 2.0 DIObjects are compatible only with Application Server 3.1 SP2 and later versions. The DAServer in stand-alone mode has no dependency on Application Server.
The MBTCP DIObjects version 2.0 support the following Operating Systems:
The DAServer supports Microsoft .NET 3.5 SP1 Framework.
Microsoft Internet Explorer 6.0 or higher is recommended on the computer where the product is installed.
Windows Vista User Account Control (UAC) must be disabled, or privileges must be elevated to Administrator level, when installing or configuring MBTCP DAServer. UAC can remain enabled without privilege elevation for all run-time operations.
Windows Vista and later operating systems do not support NetDDE. See DDE Compatibility for more information.
To run a DAServer, we recommend as a minimum the following hardware configuration:
For information about which versions of the Modbus controllers’ hardware and firmware are supported by the MBTCP DAServer version 2.0, see Appendix A in the MBTCP DAServer User's Guide.
Before installing the MBTCP DAServer 2.0, it is strongly recommended that you exit all Wonderware programs, including executable (.exe) files and services. Detailed installation instructions are included in the DAServer Installation Guide. It is recommended that you read the DAServer Installation Guide prior to beginning the installation process.
In addition to the procedures described in the DAServer Installation Guide, the following installation requirements and other requirements pertaining to the installation and uninstall orders have to be followed.
Note: A DAServer installation issue where Rainbow Sentinel installation failure prevented successful DAServer installation has been resolved with this release. See SR #23332134.
The following installation requirements are prerequisites for the MBTCP DAServer 2.0 to work properly.
The installation for the DAServers and other Wonderware FactorySuite™ products on the same computer must follow the order as outlined. A DAServer must always be installed last.
This installation order resolves any differences that may exist in the common components included with individual product releases, so that the products install and run without version conflicts. For future patches, follow the installation instructions from the patch.
After you install a DAServer on a computer with other Wonderware FactorySuite products, the following applies:
Note: ArchestrA™ products, such as InTouch 8.0 or greater, do not have any installation/uninstall order requirements with the DAServers.
L00089752:
The MBTCP DAServer was sending two messages to a device with maximum outstanding messages set to 1. For devices that support only one message, this caused the DAServer to enter slow poll mode. The issue has been resolved by modifying the method by which DASMBTCP counts messages. HotFix CR L00087813, SR 32811016, HF 1215
L00096176:
An invalid write command was sent to the PLC when writing to three consecutive registers and when the first item was a bit within a holding register (mask write holding register). This issue has been resolved by modifying Item and Message handling. HotFix CR L00094604, SR 22316176, HF 1574
At the time of this release
Although Wonderware DAServers can communicate with multiple client protocols at the same time, you should be aware of the advantages and disadvantages of the technologies used for any particular protocol. For example, the OPC Data Access protocol is based on Microsoft COM/DCOM technology. The DCOM technology has an inherent pinging mechanism that requires six (6) minutes before a DCOM connection is declared as timed-out. As a result, there may be a chance that when the DAServer is connected remotely with an OPC client and the network is interrupted, a delay of six (6) minutes may be experienced in the OPC client program before declaring the connection to the DAServer a failure.
Please note that this is expected; the DAServer remains active and continues to provide data connectivity to other clients that have good network connections. More information on the DCOM pinging mechanism can be found in Sections 2.5 and 2.5.1 of the specifications Distributed Component Object Model Protocol ... DCOM/1.0 from Microsoft.
The computer name used by NetBIOS is limited in length to MAX_COMPUTERNAME_LENGTH. For Windows operating systems the NetBIOS computer name is limited to 16 ASCII characters. If you install a DAServer on a computer with a long name (for example, "My_Very_Long_Computer_Name"), you may have issues accessing the DAServer diagnostics.
After installing this DAServer, the pre-existing WWLogger™ output is redirected to the new Log Viewer.
CPU Utilization:
The DAServer performance may be impaired if the CPU utilization reaches and remains at 100 percent. The DAServer may then become unresponsive.
If you only use the keyboard for navigation after starting the DAServer Manager, you cannot access the dialog boxes and other boxes on the configuration view. Also, if you are using the dialog boxes with the mouse, you can only move downward using the TAB key. Pressing the SHIFT+TAB keys to go back does not work.
The keyboard shortcuts for the user interface may not work according to Microsoft conventions. We recommend using the mouse to navigate in the DAServer Manager.
If you modify the default update interval while the DAServer is communicating with a PLC, the modification does not take effect until the current update interval completes.
You can add the historically reserved "Watchdog" item, but it logs the following two messages:
Ignore these messages; the item itself works.
You cannot rename a device group with the same name but in a different case (upper or lower). Device groups are case-insensitive.
System items do not show in the DAServer Manager Diagnostics, unless subscribed to by a client.
The DAServer Manager does not automatically refresh when the DAServer on a remote node is uninstalled or has gone off-line/online.
The MBTCP DAServer documentation set includes the following guides:
1.
DAServer Installation Guide. This
online Help provides information on installing the DAServer
2. Change Network Account Online Help. This Help documentation describes the tool you can use to manage credentials for node-to-node communications between ArchestrA™ components. This documentation can be accessed from the application's Help.
3.
Protocols Guide. This guide
4. MBTCP DAServer User's Guide. This guide describes the user interface and functions of the Wonderware MBTCP DAServer.
5.
DAServer Manager User's Guide. This
documentation describes the runtime Configuration
6. License Utility Guide. This guide describes the FactorySuite 2000 (Version 7.1) licensing strategy and explains how to use the License Utility to install license files and browse valid license files on the network.
7.
LogFlag Editor User's Guide. This documentation
describes the user interface and functions of the LogFlag Editor utility. This
utility can be opened only from the Log Viewer
8. Log Viewer User's Guide. This guide provides information about the Logger™ and the Log Viewer snap-in to the System Management Console.
Document numbers 3 through 8 are provided in the PDF form and can be printed; they are available in the <CD-ROM drive:>\UserDocs\English. Also, information included in these guides is provided in online Help, which can be accessed from the MBTCP DAServer's Help.
The documentation describing how to use this product is included on the CD
in PDF format. Viewing these guides requires the installation of the Adobe's
Acrobat Reader. This utility is not included on this CD
www.adobe.com/products/acrobat/readstep2.html
After downloading the file from Adobe
© 2010 Invensys Systems, Inc. All Rights Reserved.