Opc server for ac 800M, Installation and Configuration

Section 3 OPC Server Operation
Power Failure
3BSE035983-510
39
 
Power Failure
The OPC server runs as a service, and can be configured so that configurations are 
automatically loaded at startup. Groups and items always have to be re-configured 
after startup.
When an OPC client is stopped abruptly, it is detected by the OPC server, which 
stop making callbacks. After COM timeout, all memory allocated for the specific 
client, is released.
See also 
OPC Data Access Server Behavior at Power Fail
 on page 42, and 
OPC 
Alarm and Event Server Behavior at Power Fail
 on page 60 for more information.
Error Handling
In addition to standard OPC error handling, serious errors are logged as a log file. 
Errors are also presented in the OPC Server Configuration Panel.
Performance
For specific performance information regarding OPC Data Access Server and OPC 
Alarm and Event Server, see subsection Performance of respective section.

Performance
Section 3 OPC Server Operation
40
3BSE035983-510
 

3BSE035983-510
41
 
Section 4 Data Access
General
The OPC Data Access Server provides data from controllers programmed with 
Control Builder M through an OPC Data Access 2.0 and 1.0A interface. The 
program ID is: ABB.AC800MC_OpcDaServer.3
In order to receive data from the controller, it has to be connected to the OPC Server 
Configuration Panel. During compilation, Control Builder saves information about 
applications, hardware configuration and access variables to files. They are the 
.cdoXml,.rrsXml domain files for each application and the .ctdXml domain files for 
each controller. To connect to a specific controller, the OPC Data Access Server is 
dependent on these domain files. The OPC Server fetch the domain files 
automatically, when needed. See also 
File Management
 on page 16 or 
OPC Server 
Configuration Panel
 on page 21.
Controller and application names must be unique throughout the connected 
controllers. The OPC Server is not able to provide data for duplicate names. See 
also 
Address Space
 on page 47. 
The OPC Sever keeps its name references even when the communication to the 
controller is lost, consider the following scenario: 
Two SoftControllers and which both are configured in the OPC Server. An 
application is downloaded to the first SoftController, hence the OPC Server 
provides good data for it. If the Soft Controller will be terminated, the OPC Server 
will consider this as loss of communication, hence provides bad data. 
When the application is downloaded to the second SoftController, the OPC Server 
will still provide bad data for the application! 
The explanation is that the OPC Server has references to two applications with the 
same name, therefore good data will not be provided until the first SoftController is 
restarted (the OPC Server sees this as regained communication). Once the first 

Fast Initial Update
Section 4 Data Access
42
3BSE035983-510
 
SoftController has been restarted the OPC Server will remove the reference of the 
former application. Good data will be provided for the application in the second 
SoftController.

tải về 0.83 Mb.

Chia sẻ với bạn bè của bạn: