Product specifications

Accessing 800xA via OPC
3BDS011222-510 B 417
800xA OPC Support exposes interfaces for OPC Data Access, OPC Alarm and
Event and OPC History Data Access. These are three central interface specifications
as stated by the OPC Foundation. Refer to the System 800xA, System Planning
(3BSE041389*) manual for a definition and explanation of OPC.
In order to use OPC Support both hardware and software must be configured in
certain ways. The following sections explain this in more detail.
Hardware Setup
800xA does not impose any restrictions on which machine the third party OPC
client software is to be installed. It can be installed directly on the 800xA
connectivity servers or on an 800xA workplace client. Installation on an 800xA
workplace client gives a slightly better system performance and it gives the 800xA
connectivity servers a better fault isolation from poorly implemented OPC clients.
Accessing the 800xA OPC DA Server
OPC DA Server Support in the 800xA system enables you to read, write or
subscribe to system properties from a third party OPC DA client.
The status of the server is checked by calling the method GetStatus on IOPCServer.
The client should wait for the return code OPC_STATUS_RUNNING before calling
the other methods.
OPC DA Program Identities
The Program Identity for the System 800xA OPC DA Server to be used by third
party OPC DA clients is ABB.AfwOpcDaSurrogate (local server).
When a new client connection is established the new client will share a running
ABB.AfwOpcDaSurrogate process if possible. If not, a new process will be started
for the new client connection. Use the DCOMCNFG tool to set the DCOM security
setting, see DCOM Security Settings for OPC on page 457.
OPC DA Compliancy
The System 800xA OPC Server is compliant with the OPC Data Access Standard
Version 1.0 and 2.05A with some comments.