11/12/2014

Readme

Wonderware SIDirect DAServer 3.0 ReadMe

Last revision: 1/24/2012
This document contains important information about Wonderware SIDirect DAServer 3.0. Please carefully review this document for known
issues in this version and changes, if any, to the SIDirect DAServer 3.0 documentation included.

IMPORTANT NOTE: This version requires a new license. Be sure that you have the required license or else the DAServer
will operate in demo mode.
About This Release
System Requirements
Installation
Resolved Issues
Known Issues
SIDirect DAServer Documentation

About This Release

This release of the SIDirect DAServer 3.0 and its DI Objects delivers significant enhancements in functionality; a new version of the
DAServer Runtime Components is also being delivered to increase the SIDirect DAServers performance.
This version provides support for:
The latest versions of Siemens PLC firmware.
Fault-tolerant Siemens SIMATIC S7-400H controllers.
Communications to Siemens SIMATIC S7-400H PLCs with redundancy through an Ethernet connection. The DASSIDirect 3.0
provides connectivity support to S7-400H controllers in both stand-alone and redundant configurations.
In a stand-alone S7-400H configuration (no redundant controllers configured), DASSIDirect supports subscription,
poking, block services, alarms and events, and cyclic services communications.
When two S7-400H PLCs are configured in redundant mode through the RDO, subscription and poking communications
are supported. Alarm and event communications, cyclic services, and block services are not supported.
Siemens SIMATIC S7-1200 Compact controllers.
Virtualization using Microsoft Hyper-V technology. The SIDirect DAServer has been tested in the following virtualization
environments:
Microsoft Hyper-V Windows 2008 R2 SP1
VMWare (ESX Server 5.0)
The ArchestrA License Manager and the common ArchestrA license file. If you are still using software versions that use the
wwsuite.lic license file, and you do not have an ArchestrA.lic license file with the correct feature line, contact your distributor or
support provider.
< top of document >

System Requirements
Compatibility
SIDirect DAServer 3.0 incorporates the latest Microsoft C Runtime components and the .NET 3.5 SP1 Framework. The DAServer in standalone mode has no dependency on Application Server.

Operating Systems
The SIDirect DAServer 3.0 supports the following operating systems:
Microsoft Windows XP Pro SP3 (32-bit)

https://wdnresource.wonderware.com/support/patchfixes/1/DASSIDir30RM.HTML

1/5

11/12/2014

Readme
Microsoft Windows 2003 Server SP2 (Standard and Enterprise) (32-bit)
Microsoft Windows 2003 Server R2 (Standard and Enterprise) (32-bit)
Microsoft Windows Vista SP2 (32-bit and 64-bit) (Ultimate, Business, Enterprise) (see Windows Vista Restrictions)
Microsoft Windows 2008 SP2 (32-bit and 64-bit) (Standard and Enterprise)
Microsoft Windows 2008 Server R2 SP1 (64-bit) (Standard and Enterprise)
Microsoft Windows 7 SP1 (32-bit and 64-bit) (Professional and Enterprise)
Microsoft Windows 8 (32-bit and 64-bit) (Professional and Enterprise)
Microsoft Windows 2012 Standard (64-bit)

Notes: Microsoft Internet Explorer 6.0 or higher is recommended on the computer where the product is installed. 64-bit Windows Vista,
Windows 7 and Windows 2008 will be supported on hardware with x86-64 processor architecture. Itanium IA-64 processor architecture is
not supported. We recommend that all available Microsoft Windows patches and security updates are kept up to date on systems running
DASSIDirect and DIObjects.

Windows Operating System Restrictions

Windows Vista and above operating systems do not support NetDDE. See DDE Compatibility for more information.
A DDE client and an OPC client cannot simultaneously communicate with a DAServer. SuiteLink is the recommended
communications protocol.
When upgrading from Windows XP to Windows Vista operating systems, uninstall all DAServers and DAS Runtime Components
prior to upgrading the operating system. After upgrading the operating system, all DAServers and DAS Runtime Components can
be reinstalled.
When accessing a DAServer remotely using the SMC, Network Discovery on both nodes must be enabled.

DDE Compatibility
Local DDE is supported ONLY when the DAServer is configured as "Not a Service" and activated from its executable file or started
from the InTouch HMI.
On Windows Vista, Windows 7, and Windows Server 2008 operating systems, Local DDE is NOT supported when the DAServer is
activated in the System Management Console
(SMC).

Hardware Requirements
To run a DAServer, we recommend as a minimum the following hardware configuration:
Computer with 2 gigahertz (GHz) or higher processor (32-bit and 64-bit) clock speed
1 gigabyte (GB) of RAM or higher (512 MB minimum supported; may limit performance and some features)
8 gigabytes (GB) of available hard disk space
Super VGA (1024 x 768) or higher-resolution video adapter and monitor
CD-ROM or DVD drive
Keyboard and mouse or compatible pointing device
Note: The Intel Itanium processor is not supported.

Hardware and Firmware

Information on the versions of the hardware and firmware of Siemens components supported by the SIDirect DAServer 3.0 can be found in
the SIDirect DAServer User's Guide, Appendix A.
< top of document >

Installation
Before installing the SIDirect DAServer 3.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 before 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 was resolved

https://wdnresource.wonderware.com/support/patchfixes/1/DASSIDir30RM.HTML

2/5

11/12/2014

Readme

with a previous SIDirect DAServer release. See SR #23332134.

Installation Requirements
The following installation requirements are prerequisites for the SIDirect DAServer 3.0 to work properly.
Local administrator privileges are required to install a DAServer.
If there is a prior version of the DAServer installed on the computer, the SIDirect DAServer is able to detect it and performs an
upgrade. SIDirect DAServer 3.0 will allow you to install or upgrade from a previous version of SIDirect DAServer without an
uninstall of other DAServers that might be on the system. In addition, components common to all DAServers on the system, such
as the DASEngine and DAServer Manager, will also be upgraded.

Installation Order Requirements

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.
(If required) - InTouch 7.11 followed by application of the latest available InTouch patch
(If required) - Legacy I/O Servers
DAServer(s)
This installation order will ensure that any differences, which may exist in the common components included with individual product
releases, will install and run without version conflicts. In case of any future patch on the installed Wonderware FactorySuite products, follow
the particular installation instructions from the patch.

Uninstall Order Requirements

After installing a DAServer on a computer with other Wonderware FactorySuite products, the following applies:
If any Wonderware FactorySuite product is uninstalled from the computer, all other Wonderware FactorySuite products must be
uninstalled and reinstalled.
Note: ArchestrA products, such as InTouch 8.0 or greater, do not require any installation/uninstall order with the DAServers.
< top of document >

Resolved Issues
The following are important resolved issues in this release.
L00045236, DASSIDirect is showing only the value and quality in the Logger when updating the item: update item(, value=xx,
L00116598: quality=yy)
L00077839, SR 23516061: When an incorrect value is written to an item with a T Suffix, the value in the PLC is zeroed out.
L00116599:
L00101427: SR 32810604: Host name restrictions should be removed on objects that have a host name argument.
L00107968: SR 14432705: An SIDIRECT DAServer connection from the InTouch HMI to an S7-PLC would not reconnect to the PLC
after the network cable on the PC side was disconnected for 6-7 minutes and subsequently reconnected. Code has been
enhanced to provide for proper reconnection to the PLC.
L00111632: HF CR L00111191 (Hotfix 2411) SR 103120825: DASSIDirect was unable to poll for data for added items when the
connection between the DAServer and the PLC disconnected then reconnected. The PLC would reconnect but message
polling would not resume. Code has been modified to handle this type of disconnect/reconnect scenario.
L00112618: HF CR L00110203 (Hotfix 2269) SR 33410769: When multiple PLCs are configured, good connections will stop updates
when there is poking on a bad connection.
L00113248: SR 103121371: When a Historian topic disconnects from DASSIDirect, updates in other topics to WindowViewer are
interrupted.
L00114314: SR 103121982: The CP343-1 343-1EX30-0XE0 module should be supported.
L00115080: SR 14433068: When using the SIDirect DAServer, switching the Redundant Device Object (RDO) to the secondary device
using $sys$ForceFailover obtained updates from the secondary device, but restarting InTouch View no longer retrieved
values from the PLC. Code enhancements have addressed this redundancy scenario.
L00115203: HF CR L00108758 (Hotfix 2248) SR 103118795: An InTouch application connected to S7-300 PLCs randomly ceased
updating data in some items with no error appearing in the log viewer. This was caused by a communication timing issue,
which has been resolved.
L00116122,

HF CR L00113645 SR 103119766: DASSIDirect only partially recovered communication with a single PLC after the

https://wdnresource.wonderware.com/support/patchfixes/1/DASSIDir30RM.HTML

3/5

11/12/2014

Readme

L00116603: Ethernet cable was disconnected and then reconnected. Code has been enhanced to handle this type of communication
disconnect/reconnect scenario.
L00118342: SR 22317518: The PLC 200 object is not automatically getting data updates after being disabled and enabled.
L00118353: SR 103123578: The topic name should be included in the slow poll mode messages in the Logger.
< top of document >

Known Issues
Wonderware DAServer Compatibility with Other FactorySuite Products on the
Same Computer
At the time of this release, InTouch, Version 7.11 with Patch 03 or greater, and Wonderware FactorySuite 2000 I/O Servers, previously
released with support for Windows 2000 or greater, are the supported Wonderware product combinations on the same computer with the
DAServers. Please check the FactorySuite Product version-compatibility matrix at www.wonderware.com/support/mmi to determine if the
product-version combination associated with this install is supported.

Non-Wonderware Product Issues

L00021068: 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.

Installation
Long Computer Name:
The computer name used by NetBIOS is limited in length to MAX_COMPUTERNAME_LENGTH (for instance, the limitation is 16 characters for
Windows NT 4.0). That is why, when installing a DAServer on a computer with a long name (that is, "My_Very_Long_Computer_Name"),
you may have issues accessing the DAServer diagnostics.

WWLogger:
After installing this DAServer, the pre-existing WWLogger output will be redirected to the new Log Viewer.

The DAServer Manager Issues

CPU Utilization:
The DAServer performance may be impaired if the CPU utilization reaches and remains at 100%; the DAServer may then become userunresponsive.

Keyboard Navigation:
If using only the keyboard for navigation after starting the DAServer Manager, you will not be able to get to the dialog boxes and other
boxes on the configuration view. Also, once in the dialog boxes, using the mouse, you can only move in the downward direction using the
TAB key. Pressing the SHIFT+TAB keys to go back does not work.
Using the mouse to navigate in the DAServer Manager is recommended.
Hot Configuration:
Modifying the Default Update Interval, while the DAServer is communicating with a PLC, will not take effect until the current update interval
has completed.

Watchdog Item:
The historically reserved item "Watchdog" can be added, but will log the following two messages:

https://wdnresource.wonderware.com/support/patchfixes/1/DASSIDir30RM.HTML

4/5

11/12/2014

Readme

Unable to add item '..Watchdog' with access path 'xyz'

ProtCreatePoint::AddItems() method failed (hr=0x1) for item name='watchdog'
These messages are spurious, as the item itself will work.

Device Groups:
Attempting to rename a Device Group with the same name but different case (upper or lower) will fail. Device Groups are case insensitive
and, therefore, treat upper and lower cases of a character as the same character.
L00003667: System items do not show in the DAServer Manager Diagnostics, unless a client subscribes to them.
L00004239: The DAServer Manager does not automatically refresh when the DAServer on a remote node is uninstalled or has gone offline/online.
L00032697: Upgrading with the existing DAServer Manager open and the DAServer running will result in double "SMC -" listed under the
'Files in Use' area in the pop-up Warning dialog box from Installation Program.
< top of document >

SIDirect DAServer Documentation

The SIDirect DAServer documentation set includes the following:
DAServer Installation Guide. This online Help provides information on installing the DAServer, including options for installing all
components of the system or just individual ones. These include the DAServer Manager (including configuration components of
the DAServer), the DAServer (including OPC protocol capabilities), and the DDE/SuiteLink Plug-In (for communicating with the
legacy Wonderware products). This Help file can be accessed from CD-DASSIDirect as Install-DASSIDirect.chm.
Change Network Account Online Help. This Help documentation describes the tool you can use to manage credentials for node-tonode communications between ArchestrA components. This documentation can be accessed from the application's Help.
Protocols Guide. This guide provides background information on the main protocols used between components of the Wonderware
products. A protocol is the set of rules and standards for enabling computers to connect and exchange data over the network.
This guide also includes information on setting up and using some of these protocols.
SIDirect DAServer User's Guide. This guide describes the user interface and functions of the Wonderware SIDirect DAServer.
DAServer Manager User's Guide. This documentation describes the runtime Configuration, Diagnostics, and
Activation/Deactivation aspects of a Data Access Server (DAServer). These aspects of any DAServer are maintained through the
generic component called the DAServer Manager.
ArchestrA License Manager Guide. This guide describes the ArchestrA License Manager and how to use it to install, maintain, and
delete licenses and license servers on local and remote computers. The guide also describes how to use the ArchestrA License
Manager with hardware keys.
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, a part of the System Management Console suite of utilities.
Log Viewer User's Guide. This guide provides information about the Logger and the Log Viewer snap-in to the System
Management Console. Documents are provided in PDF form and can be printed, and are available in the CD-ROM
directory\UserDocs\English. Also, information included in these guides is provided in online Help, which can be accessed from the
SIDirect DAServer's Help.

Viewing PDF Documentation

The documentation describing how to use this product are included on the CD in PDF format. Viewing these guides requires the installation
of Adobe's Acrobat Reader. This utility is not included on this CD, but it can be downloaded for free from the Adobe's Web site at the
following Web address:
www.adobe.com/products/acrobat/readstep2.html
After downloading the file from Adobe, you must run the executable to install it on your computer. Follow the typical installation routine.
After installation, you can either open the Acrobat Reader and select a user's guide from the File menu, or double-click a user's guide on
the CD in Windows Explorer.
< top of document >
2012 Invensys Systems, Inc. All Rights Reserved.

https://wdnresource.wonderware.com/support/patchfixes/1/DASSIDir30RM.HTML

5/5