Escolar Documentos
Profissional Documentos
Cultura Documentos
In no event shall ABB be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shall ABB be
liable for incidental or consequential damages arising from use of any software or hard-
ware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB, and the contents thereof must not be imparted to a third party nor used
for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low
Voltage Directive 72/23/EEC.
TRADEMARKS
Registrations and trademarks used in this document include:
Section 1 - Introduction
What is OPC Server for AC 800M? ................................................................................13
System Configuration ......................................................................................................14
Network Considerations.......................................................................................15
Communication Considerations ...........................................................................16
OPC Server for AC 800M Functions ...................................................................17
Prerequisites and Requirements ......................................................................................18
Intended User...................................................................................................................18
3BSE035983R4101 5
Table of Contents
6 3BSE035983R4101
Table of Contents
Mapping of OPC..............................................................................................................52
Mapping IO Channel Status to OPC Quality .......................................................52
Interfaces Supported.............................................................................................52
States of Status .....................................................................................................53
OPC Data Access Overview.................................................................................53
Address Space ......................................................................................................54
OPC Variables ......................................................................................................54
Item Quality .........................................................................................................56
Writing .............................................................................................................57
Performance.....................................................................................................................57
INDEX
3BSE035983R4101 7
Table of Contents
8 3BSE035983R4101
About This Book
General
This book makes acquaintance with the OPC Server for AC 800M, its technical
characteristics and standards, as well as how to connect and what interfaces to use.
This publication addresses people involved in the installation procedure of OPC
Server for AC 800M and gives an in-depth study of the standards and the interfaces.
Section 1, Introduction, introduces OPC Server for AC 800M and what should be
considered before installing and configuring the product.
Section 2, Installation and Start-up gives a step-by-step instruction on how to install
OPC Server for AC 800M, as well as a description on how to set up the system and
start the OPC Server Configuration Panel for the first time and configure the
settings from there.
Section 3, OPC Server Operation deals with subjects applicable for both parts of
OPC Server for AC 800M. The different parts of OPC Server is described in Section
4 and Section 5.
Section 4, Data Access describes the OPC Data Access Server.
Section 5, Alarm and Event describes the OPC Alarm and Event Server.
Appendix A, Setting Up from Windows 2000 describes the setup procedure for
DCOM/COM when using the Windows 2000 Professional operating system.
3BSE035983R4101 9
Use of Warning, Caution, Information, and Tip Icons About This Book
Electrical warning icon indicates the presence of a hazard which could result in
electrical shock.
Warning icon indicates the presence of a hazard which could result in personal
injury.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
comply fully with all Warning and Caution notices.
10 3BSE035983R4101
About This Book Document Conventions
Document Conventions
The following conventions are used for the presentation of material:
The words in names of screen elements (for example, the title in the title bar of
a window, the label for a field of a dialog box) are initially capitalized.
Capital letters are used for the name of a keyboard key if it is labeled on the
keyboard. For example, press the ENTER key.
Lowercase letters are used for the name of a keyboard key that is not labeled on
the keyboard. For example, the space bar, comma key, and so on.
Press CTRL+C indicates that you must hold down the CTRL key while
pressing the C key (to copy a selected object in this case).
Press ESC E C indicates that you press and release each key in sequence (to
copy a selected object in this case).
The names of push and toggle buttons are boldfaced. For example, click OK.
The names of menus and menu items are boldfaced. For example, the File
menu.
The following convention is used for menu operations: MenuName >
MenuItem > CascadedMenuItem. For example: select File > New > Type.
The Start menu name always refers to the Start menu on the Windows
Task Bar.
System prompts/messages are shown in the Courier font, and user
responses/input are in the boldfaced Courier font. For example, if you enter a
value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
You may be told to enter the string TIC132 in a field. The string is shown as
follows in the procedure:
TIC132
Variables are shown using letters in Italic style.
MaxLimit
3BSE035983R4101 11
Terminology About This Book
Terminology
The following is a list of terms associated with OPC Server for AC 800M that you
should be familiar with. The list contains terms and abbreviations that are unique to
ABB or have a usage or definition that is different from standard industry usage.
Term Description
AE Alarm and Event
COM Component Object Model, which is the Microsoft binary standard,
defines how objects can interact.
DA Data Access
DCOM Distributed Component Object Model is an extension of COM. It
defines how objects can interact over a network. COM and DCOM
are available on most Windows platforms and on several Unix
platforms.
MMS Manufacturing Message Specification
POU Program Organization Unit
RNRP Redundant Network Routing Protocol
Applicable Specifications
This product meets the requirements specified in EMC Directive 89/336/EEC and in
Low Voltage Directive 72/23/EEC.
12 3BSE035983R4101
Section 1 Introduction
3BSE035983R4101 13
System Configuration Section 1 Introduction
OPC Client
COM/DCOM
MMS server
Ethernet MMS
System Configuration
There are a number of basic rules regarding system configuration and OPC servers:
One OPC Server for AC 800M is allowed to subscribe to data from a maximum
of 24 PM861 controllers, or the equivalent number of variables from other
controller types,
One OPC server can receive data or event notifications from multiple control
systems,
A maximum of two OPC servers are allowed to subscribe to Data Access
and/or Alarm and Event from one controller,
A control system can send data or event notifications to multiple subscribing
OPC servers,
14 3BSE035983R4101
Section 1 Introduction Network Considerations
Multiple OPC clients can subscribe to data or event notifications from the same
OPC server.
A maximum of five third-party OPC clients are allowed to subscribe to Data
Access and/or Alarm and Event from one OPC server,
A third-party OPC client should, if possible, be installed on the same PC as the
OPC server. Otherwise, there is a potential risk that communication will not
restart after a communication failure.
A maximum of four Ethernet links (two redundant) are supported via Ethernet
cards.
A maximum of four Point-to-Point Protocol (PPP) links are supported via
serial cards.
Network Considerations
All PC:s must have the same primary network as the OPC Server in order to be able
to communicate with this network.
If an Control Builder on PC A has network addresses 172.16.67.41 and
10.46.41.242, and Control Builder on PC B has the addresses 172.16.67.42 and
10.46.41.241, both PCs must have the 172.16 network as their primary network.
The primary network is the network defined as the first network in the network
setup.
The OPC server needs access to certain files in order to connect to a controller.
These files are stored by the Control Builder that performed the last download.
The OPC server can locate these files automatically after a new download.
This does not apply to Control Builder Professional, where the integrated
environment stores the files in the Aspect Directory. See File Management on
page 18.
3BSE035983R4101 15
Communication Considerations Section 1 Introduction
Communication Considerations
Communication handling has the lowest priority in a controller. It is therefore
important to consider controller CPU load if the communication handling is vital to
the application. Running at the maximum cyclic load will result in poor capacity
and response times for peer-to-peer and OPC Server for AC 800M communication.
It is recommended that peak cyclic controller load will be kept below 65%, and
static cyclic load below 60%, under all conditions. Even lower cyclic loads (30-
40%) are desirable if high communication throughput is important.
16 3BSE035983R4101
Section 1 Introduction OPC Server for AC 800M Functions
Clock Synchronization
OPC Server for AC 800M contains a function for clock synchronization. If enabled,
the OPC server will time synchronize all connected controllers at a certain interval
(also, see Clock Synchronization on page 32).
This type of clock synchronization should only be used if there is no clock master
synchronization throughout the controller network. The clock master could be an
AC800M controller, but also another type of controller, for example an AC400
controller.
3BSE035983R4101 17
Prerequisites and Requirements Section 1 Introduction
File Management
Control Builder M Professional
Control Builder M Professional can only be run in integrated mode, where all
data is stored in the Aspect Directory database. As a consequence, there is no
need for an FTP server, since all files in the Aspect Directory are updated
instantly when changed.
Intended User
The first two sections of this publication addresses people involved in the
installation procedure of OPC Server for AC 800M.
The following sections address people who want to configure OPC clients.
18 3BSE035983R4101
Section 2 Installation and Start-up
This section will guide you through the installation procedures for OPC Server for
AC 800M. Later on in this section, start-up information and basic information
regarding how to configure OPC Server for AC 800M is found.
1. If the CD-ROM is available via a network, this shared directory must be connected to your PC (the Installation
wizard requires this). Select Tools > Map network drive in the Windows XP Explorer and connect the PC to
the shared drive.
3BSE035983R4101 19
OPC Server Setup Wizard Section 2 Installation and Start-up
Note that the OPC Server Configuration Panel has additional settings, such as
system variables and auto-load configuration.
Some tabs have an Apply button. Specified settings will not be implemented until
this button is clicked.
All Setup Wizard dialog boxes contain a Show Settings button. Click this button to
print a log file on screen containing all available Wizard settings. This also prints a
list of system environment variables.
20 3BSE035983R4101
Section 2 Installation and Start-up OPC Server Account
System Settings
The Auto-Logon to Windows setting and the RNRP setting are identical for
Control Builder M, SoftController and the OPC Server for AC 800M. Any change
will affect all three installed products.
Auto-Logon to Windows
With this function enabled, the Windows operating system will automatically logon
a selected user when the PC is started. The function should only be used when
automatic start-up of the Control Builder is desired.
Enter the user name, password (twice) and the computer name (domain), to which
the user belongs. If an unknown user name is entered, the Auto-Logon function will
fail.
3BSE035983R4101 21
Product Settings Section 2 Installation and Start-up
Product Settings
Memory Reservation
The actual heap should be set to the size of the application but not exceed the
Maximum recommended heap size. Start by using the default value and then
increase the value according to the application demands.
The default OPC Server heap size is 64MB. However, in conjunction with large
projects, this has proven to be not sufficient, and as a result the OPC server has
crashed. If this should occur (the server cannot start), increase the heap size by
simply doubling the previously allocated heap size.
Check the OPC Server's About box shortly after the Server is up running again, and
make sure there is at least 30% spare heap.
For running with redundant Connectivity servers, a good precaution is to set
different heap sizes for the two OPC Servers. Set the heap sizes with an approximate
of 10% difference, for preventing that both OPC Servers stops at the same time.
The amount of free memory can be checked by opening the About... dialog box
in the OPC Server Configuration Panel Help menu. Heap size should be
increased when less than 30% remains.
22 3BSE035983R4101
Section 2 Installation and Start-up Product Settings
File Locations
OPC Server for AC 800M has a number of changeable, specific, file locations. Each
user may have a personal file location profile.
The Working folder and the MMS Server Working Folder is managed by Setup
Wizard.
Clicking Use Default Settings will reset your personal settings to the general
settings determined by the network administrator.
Click Modify... to change the file location path for the selected type. A browser will
open to assist you in locating the appropriate path. If the settings is to be personal,
click Change Personal Setting, if it is to be the default for any user, click Change
Product Setting. The latter needs Administrator privileges to be applicable.
Changes made to product settings will only affect users without a personal setting.
Click Change Product Setting to apply the change.
For more information on file management, see File Management on page 18.
3BSE035983R4101 23
Start-up and Configuration Section 2 Installation and Start-up
24 3BSE035983R4101
Section 2 Installation and Start-up OPC Server Configuration Panel
The files must then be placed in a directory named Files in the OPC Server
working directory. A browse dialog is displayed in the OPC Server Configuration
Panel to help you locate the missing files and the copying of files to the correct
location.
3BSE035983R4101 25
Connecting Controllers Section 2 Installation and Start-up
Connecting Controllers
Each of the controllers connected has an icon indicating the current status of the
connection to the controller.
To add more controllers, repeat the procedure above.
Each of the controllers connected has an icon indicating the current status of the
connection to the controller.
26 3BSE035983R4101
Section 2 Installation and Start-up Connecting Controllers
Disconnect Controller
When disconnecting a controller, data in that controller is no longer available to
clients of the OPC Server.
To disconnect a controller, select the controller from the Connected Controllers list
and click Disconnect.
3BSE035983R4101 27
Alarm and Event Settings Section 2 Installation and Start-up
28 3BSE035983R4101
Section 2 Installation and Start-up Alarm and Event Settings
Other system variables part from those presented here in the AE Settings dialog
box, can be configured in the System Variables dialog box (Settings > System
Variables). See Setting System Variables on page 67.
3BSE035983R4101 29
Setting Cache Update Rate Section 2 Installation and Start-up
The OPC Server should always have its update rate set twice as fast as the OPC
client(s) update rate.
The cache update rate controls how often the OPC Data Access Server updates its
internal cache with data from a certain controller. The cache update rate limits the
update rate an OPC client can have on an OPC group. To ensure that subscribing
OPC clients can access changed values at their requested update rate, the time
(value) for cache update rate should be set shorter than the fastest OPC group update
rate. To set the update rate, open Settings > Update Rate... dialog box from the
OPC Server Configuration Panel.
Settings > Update Rate is only available from the OPC Data Access Server, i.e.
when the Data Access tab is selected.
30 3BSE035983R4101
Section 2 Installation and Start-up Setting Cache Update Rate
To distinguish between fast and slow update rates there are five categories for
simple values (integer, real, bool) and a separate category for strings. The values in
the Requested column determines the update rate of the internal cache in the OPC
server, i.e. how often items in each category are read from the controller. When
OPC Server for AC 800M is started, the values are set to default values.
The values in the Actual column shows the current update rate. This value will vary
around the Requested value depending on the load. A zero value in this column
means that there is no MMS communication for that category at the moment.
The requested update rates must be given in ascending order, starting at the High
category. The lowest permitted update rate value for any category is 50 ms.
If any groups has been added, the update rate cannot be changed. The update rate
configuration should therefore be made at start-up of the OPC Server for
AC 800M, before any groups been added.
Example
An OPC client creates an OPC group with an update rate of 1000 ms. This means
that items added to this OPC group will be reported to the OPC client once every
second. In the OPC server, the MMS communication for this group is put in the
High category, which means that items in this category will be read from the
controller every 500 ms.
3BSE035983R4101 31
Clock Synchronization Section 2 Installation and Start-up
Clock Synchronization
OPC Server for AC 800M contains a function for clock synchronization. If enabled,
the OPC server will synchronize time in all connected controllers, at a certain
interval.
This type of clock synchronization should only be used if there is no clock master
synchronization throughout the controller network. Such a clock master could be
an AC800M controller, but also another type of controller, for example an AC400
controller.
To clock synchronize from the OPC Server Configuration Panel, open the
Settings > Time Synchronization... dialog box.
The accuracy of the time synchronization cannot be guaranteed, due to the fact
that it relies on MMS communication. For more information about Clock
Synchronization, see the OPC Server online help or the Control Builder online
help.
32 3BSE035983R4101
Section 2 Installation and Start-up Define System
Define System
To select a system and getting configuration data and later on saving cold retain
values, open the Settings > System Connections... dialog box, from the OPC
Server Configuration Panel.
3BSE035983R4101 33
Access Rights Section 2 Installation and Start-up
Access Rights
Access right is a setting that aims for protecting the OPC Server configuration panel
from unauthorized changes described with start from Connect Controllers to OPC
Alarm and Event Server on page 26.
With Access right enabled, all dialog entries will be dimmed, thus locked for
unauthorized changes. Please note that only an administrator can disable Access
Right and restoring the menu options given from the OPC Server configuration
panel.
Make sure you have administrator privileges before you enable the Access Right.
To enable Access rights, open the Settings > Access Right... dialog box, from the
OPC Server Configuration Panel.
34 3BSE035983R4101
Section 2 Installation and Start-up Save Configuration
Save Configuration
By clicking File > Save Configuration the current configuration settings of the
OPC server is saved to a file containing one section for each part of the OPC server.
The default extension of the file is .cfg and it is by default saved in the Files folder
of the OPC servers working directory.
3BSE035983R4101 35
Automatic Load of OPC Server Configuration Section 2 Installation and Start-up
36 3BSE035983R4101
Section 2 Installation and Start-upRunning the OPC Server and OPC Client on Different Computers
If you use the Windows 2000 Professional operating system, see Appendix A,
Setting Up from Windows 2000, subsection Running the OPC Server and OPC
Client on Different Computers on page 73.
If you are going to run the OPC server on one PC and the OPC client on another PC,
the following DCOM settings must first be performed.
Use the Windows XP DCOMCnfg tool on each of the PC:s.
DCOM should however only be used if absolutely needed, due to the risk for lost
connection as described in Lost Connection Between OPC Client and OPC
Server on page 40.
3BSE035983R4101 37
DCOM settings on the OPC Server PC Section 2 Installation and Start-up
8. In the Access Permissions dialog box, click the Add... button. In the Add
Users and Groups dialog box, select the user group(s) or the user account(s)
the OPC client is running under. The account must be known on the domain by
both PCs.
9. In the Add Users and Groups dialog box, click the Add button for your
selected user group(s) or user(s). They are listed in the Add Names: box. The
type of access should be Allow Access.
Click the OK button.
10. Click the OK button in the Access Permissions dialog box.
11. In the OPC Server for AC 800M Properties dialog box, under Launch
Permissions, select Customize and click the Edit button.
12. In the Launch Permissions dialog box, add the same user group(s) or user
account(s) as above.
13. In the OPC Server for AC 800M Properties dialog box, click the OK button.
If a parameter is incorrect, a DCOM Configuration message is displayed.
14. If, for some reason, you do not want the OPC Server to run under the Local
System account, you can change this in Control Panel > Administrative
Tools > Services > OPC Server for AC 800M > Properties > Log On. There
you select This account and enter the new user by browsing for it and enter its
password.
15. Reboot the PC.
38 3BSE035983R4101
Section 2 Installation and Start-up DCOM settings on the OPC Client PC
3BSE035983R4101 39
DCOM settings on the OPC Client PC Section 2 Installation and Start-up
40 3BSE035983R4101
Section 3 OPC Server Operation
General
This section cover information about OPC Server for AC 800M that are not specific
for the Data Access part or the Alarm and Event part of the OPC Server.
Here you find what is written into the session log, as well as what happens if power
failure occur. Some information regarding performance, indication of status and
maintenance will also be given.
Session Log
Messages concerning the system are logged in the session log. Types of messages
include direct printouts from code or system events. The session log can be opened
from OPC Server Configuration Panel.
3BSE035983R4101 41
Data Access Printouts to Session Log Section 3 OPC Server Operation
Printout Comment
OPC server started OPC Server has been started
OPC server stopped OPC Server has been stopped
COM: Waiting for active components Attempt to shut down OPC Server
with OPC clients still connected;
followed by a three second delay
OPC: The server had active components when OPC Server was shut down with
it was shutdown! OPC clients still connected (see
previous comment)
OPC Data Access: Connected to controller: Controller is connected to OPC
<IP-address> Data Access Server
OPC Data Access: Connected to controller: Controller with no contact to OPC
<IP-address>, warning: no contact Data Access Server has been
connected
OPC Data Access: Disconnected from Controller has been disconnected
controller: <IP-address> from OPC Data Access Server
OPC Data Access: Contact lost with controller Connection between controller and
<IP-address> OPC data Access Server has been
lost
OPC Data Access: Contact again with Connection between controller and
controller <IP-address> OPC Data Access Server has been
re-established
Autoloading configuration...
Autoload configuration finished
Autoload configuration failed
No FTP server available
42 3BSE035983R4101
Section 3 OPC Server Operation Alarm and Event Code Printouts to Session Log
Printout Comment
Saving cold retain files for application Save cold retain values function for
<ApplicationName> failed application has failed
Sending cold retain files for application
<ApplicationName> failed
3BSE035983R4101 43
Alarm and Event Code Printouts to Session Log Section 3 OPC Server Operation
44 3BSE035983R4101
Section 3 OPC Server Operation System Events to Session Log
3BSE035983R4101 45
System Events to Session Log Section 3 OPC Server Operation
46 3BSE035983R4101
Section 3 OPC Server Operation Power Failure
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 DCOM timeout, all memory allocated for the specific
client, is released.
See also OPC Data Access Server Behavior at Power Fail on page 50, and OPC
Alarm and Event Server Behavior at Power Fail on page 66 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.
3BSE035983R4101 47
Performance Section 3 OPC Server Operation
48 3BSE035983R4101
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 M saves information
about applications, hardware configuration and access variables to files. They are
the .cdo,.rrs domain files for each application and the .ctd domain files for each
controller.
In order 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.
To fetch these files the OPC Server must be able to communicate to the Control
Builder that made the last download to a controller. If the domain files are lost,
for example due to a damaged hard disk, Control Builder M will recreate when
online or online with download.
See also File Management on page 18 or OPC Server Online Help.
3BSE035983R4101 49
Fast Initial Update Section 4 Data Access
DCOM Time-out
Callbacks to the client are being made on separate lines, therefore the OPC server
never fails when DCOM problems occur. After DCOM time-out, all objects are
released according to standard COM.
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 by double-clicking
the icon . This brings up error information.
50 3BSE035983R4101
Section 4 Data Access What Data Can Be Accessed?
Applications
The Applications branch contains the applications running in the controllers
connected to the OPC Data Access Server. You can access variables and function
block and control module parameters.
Controllers
The Controllers branch contains the connected controllers to the OPC Data Access
Server. Each controller can access hardware variables and access variables.
For each controller, there are four items that reflects the connection between OPC
Server for AC 800M and the controller:
HWState
0 = StateOK
1 = StateError
HWStateChangeTime
Time for last change of HWState
ErrorsAndWarnings
0 = StatusOK
1 = CommunicationError
2 = FilesMissing
LatchedErrorsAndWarnings
0 = StatusOK
1 = CommunicationError
2 = FilesMissing
3BSE035983R4101 51
Hardware Variables Section 4 Data Access
Hardware Variables
You can access attributes in I/O channels and status channels of hardware units. All
attributes are read-only. Each channel has a default attribute that is sent when the
channel is accessed without specifying an attribute. When you browse the address
space, you cannot view the attributes of channels.
Mapping of OPC
Mapping IO Channel Status to OPC Quality
When an OPC client subscribes to an item, that is an IO channel, a Value, or an
IOValue component of a structured variable of IO data type (BoolIO, RealIO,
DIntIO, DWordIO), the quality of the item will be determined by the corresponding
Status component. When the client subscribes to such an item, the OPC server also
subscribes internally to the Status component (inside the IO data type) and uses its
value to calculate the quality when the client is updated with a new value.
The quality for all other items is decided by the MMS communication against the
controller. As long as the OPC server receives value updates from the controller the
quality is set to good. Since this functionality, with subscribing to the Status
component, means that extra variables will be communicated between the OPC
server and the controller, it will increase the load and might affect performance.
However, if you do not need this functionality, set the system variable
OPCGetQualityFromStatus to false (true by default). In that case item quality is
determined by the status of the MMS communication.
Interfaces Supported
All non optional interfaces are supported in accordance to the OPC Data Access
specification 2.04. Also, IOPCBrowseServerAddressSpace, and IPersistFile are
supported. The following services are not supported.
Public groups
Deadband
EU information on OPCITEMATTRIBUTES
The most efficient service when retrieving data is subscription.
52 3BSE035983R4101
Section 4 Data Access States of Status
States of Status
The OPC Data Access Server can be in one of the following states:
OPCDA_STATUS_RUNNING
At least one controller connected and communication is working
OPCDA_STATUS_NOCONFIG
No controllers are connected or no communication is working to the
controller(s) connected.
If no connection is detected when OPC Server for AC 800M is started, the state is
OPCDA_STATUS_NOCONFIG. When connecting to a controller, the OPC Server
for AC 800M goes into the OPCDA_STATUS_RUNNING state.If connection is lost
to all controllers, the OPC Server re-enters the OPCDA_STATUS_NOCONFIG
state.
3BSE035983R4101 53
Address Space Section 4 Data Access
Address Space
The address space for the OPC Server is built just like the tree structure in the
Project Explorer of Control Builder M. The top level contains two branches,
Applications and Controllers. Controller and application names must be unique
throughout the connected controllers. Item names are identified by the full path with
dot notation, for example Applications.MyApplication.MyProgram.MyDint.
OPC Variables
Variables can be accessed anywhere in the POU structure. Control module and
function block parameters can also be accessed. Variables with the attributes
Constant can only be read. An item is always of simple datatype.
You can reach access variables, which have been declared accessed from remote
systems, in the connected controllers. Access variables can be of simple data types
or structured data types.
54 3BSE035983R4101
Section 4 Data Access OPC Variables
Data type of
ID Description Type of property
returned VARIANT
1 VT_I2 Item canonical data type Standard OPC
(VARIANT type of the item property
value)
2 <varies> Item value Standard OPC
(current value) property
3 VT_I2 Item quality Standard OPC
(current quality) property
4 VT_DATE Item timestamp Standard OPC
(current timestamp) property
5 VT_I4 Item access rights Standard OPC
(readable/writable) property
6 VT_R4 Server scan rate (time Standard OPC
between cache updates) property
5000 VT_BSTR Item type name Server specific
(IEC 61131-3 data type) property
5002 VT_BSTR Item Attribute Server specific
(retain, cold retain) property
5005 VT_BSTR Item category (parameter or Server specific
variable) property
5006 VT_BSTR Parameter direction Server specific
(in, out or in/out) property
5007 VT_BSTR Path (Path to corresponding Server specific
POU variable) property
3BSE035983R4101 55
Item Quality Section 4 Data Access
Item Quality
An item can have one of the following states of quality:
Good,
Uncertain,
Bad.
For example, a non-working item have the status OPC_QUALITY_BAD.
For quality Good, the following substatus is issued:
OPC_QUALITY_LOCAL_OVERRIDE
This status is issued for I/O channels or items of I/O data type connected to an
I/O channel. The value has been Forced.
For quality Uncertain, the following substatus is issued:
OPC_QUALITY_LAST_USABLE_VALUE
This status is issued if the OPC Server does not read from the controller in
the same pace as it is supposed to update the OPC client.
OPC_QUALITY_ENGINEERING_UNITS_EXCEEDED
Used for I/O channels or items of I/O data type connected to an I/O
channel. The value is outside the limits defined for this parameter.
For quality Bad, either of the following substatuses are issued:
OPC_QUALITY_CONFIG_ERROR
This status is issued if some problem with the configuration for example,
the item in question has been deleted in the controller.
OPC_QUALITY_LAST_KNOWN_VALUE
This status is issued if the OPC Server has no contact with the controller
when it is time to update the OPC client with a new value, consequently
the OPC Server is giving the OPC client the last known value.
OPC_QUALITY_COMM_FAILURE
This status is issued if communications have failed. There is no last known
value available.
56 3BSE035983R4101
Section 4 Data Access Writing
OPC_QUALITY_OUT_OF_SERVICE
Is issued if the active state of the item or the group containing the item is
InActive.
OPC_QUALITY_UNIT_ERROR
Used for I/O channels or items of I/O data type connected to I/O channels.
A device failure has been detected. I/O value will be frozen to the last
known value.
OPC_QUALITY_CHANNEL_ERROR
Used for I/O channels or items of I/O data type connected to an I/O
channels. A channel error has been detected. The I/O value will be frozen
to the last known value.
Writing
Writing can either be done synchronously or asynchronously. If done
synchronously, the OPC Server is occupied while writing to an controller is
performed and updating of other clients are not possible. If writing is done
asynchronously, the OPC Server is able to update other clients while writing to the
controller.
If an OPC client gets status OK, this means the value was successfully written to the
controller.
Performance
OPC Server for AC 800M performance varies, considering the number of
controllers being used, what type of controller being used, and the number of
clients.
Below are some examples on how to calculate performance.
3BSE035983R4101 57
Performance Section 4 Data Access
With a 2.2 GHz PC or faster, more controllers can be handled in the configuration.
Time Stamping
Time Stamping of Data Access are done in OPC Server.
58 3BSE035983R4101
Section 5 Alarm and Event
General
From the OPC Alarm and Event Server, a stream of information is generated which
is distributed to the Alarm and Event clients. This information consists mostly of
event notifications and such a client can be an event viewer, Alarm/Event Manager,
or a logging system. Clients, on the other hand, can send acknowledges of alarms
and requests to the server.
OPC Server for AC 800M only supports compulsory interfaces. The default settings
are not applicable to the OPC standard but can easily be changed to follow the OPC
standard. This is done from the AE Settings dialog box (see Setting System
Variables on page 67).
3BSE035983R4101 59
Interfaces Supported Section 5 Alarm and Event
Interfaces Supported
The Alarm and Event part of OPC Server for AC 800M supports the OPC Alarm
and Events 1.02 standard. The program ID is: ABB.AC800MC_OpcAeServer.3
The interface contains methods (functions) to acknowledge, enable, and disable
alarm conditions, as well as methods (functions) for subscription of events.
OPC clients can also query the Alarm and Event server for information such as
condition names used, available vendor specific attributes, etc.
The list of objects with respective interfaces is as follows:
OPCEventServer object
OPCEventAreaBrowser object
OPCEventSubscription object.
OPCEventServer Object
Status Method
Implemented SetLocaleID (dwLcid)
Implemented GetLocaleID (pdwLcid)
Implemented QueryAvailableLocaleIDs (pdwCount, pdwLcid)
Implemented GetErrorString (dwError, ppString)
Implemented SetClientName (szName)
60 3BSE035983R4101
Section 5 Alarm and Event Interfaces Supported
Status Method
Implemented GetStatus (ppEventServerStatus)
Implemented CreateEventSubscription (bActive, dwBufferTime,
dwMaxSize, hClientSubscription, riid, ppUnk,
pdwRevisedBufferTime, pdwRevisedMaxSize)
Implemented QueryAvailableFilters (pdwFilterMask)
Implemented QueryEventCategories (dwEventType, pdwCount,
ppdwEventCategories, ppEventCategoryDescs)
Implemented QueryConditionNames (dwEventCategory,
pdwCount, ppszConditionNames)
Implemented QuerySubConditionNames (szConditionName,
pdwCount, ppszSubConditionNames)
Implemented QuerySourceConditions (szSource, pdwCount,
ppszConditionNames)
Implemented QueryEventAttributes (dwEventCategory,
pdwCount, ppdwAttrIDs, ppszAttrDescs,
ppvtAttrTypes)
Not implemented TranslateToItemIds (szSource, dwEventCategory,
szConditionName, szSubConditionName,
dwCount, pdwAssocAttrIDs, ppszAttrItemIDs,
ppszNodeNames, pCLSIDs)
Not implemented GetConditionState (szSource, szConditionName,
ppConditionState)
Not implemented EnableConditionByArea (dwNumAreas, pszAreas)
Implemented EnableConditionBySource (dwNumSources,
pszSources)
Not implemented DisableConditionByArea (dwNumAreas,
pszAreas)
3BSE035983R4101 61
Interfaces Supported Section 5 Alarm and Event
Status Method
Implemented DisableConditionBySource (dwNumSources,
pszSources)
Implemented AckCondition (dwCount, szAcknowledgerID,
szComment, pszSource, pszConditionName,
pftActiveTime, pdwCookie, ppErrors)
Not implemented CreateAreaBrowser (riid, ppUnk)
Status Method
Implemented EnumConnectionPoints (ppEnum)
Implemented FindConnectionPoint (riid, ppCP)
OPCEventAreaBrowser Object
Status Method
Not implemented ChangeBrowsePosition (dwBrowseDirection,
szString)
Not implemented BrowseOPCAreas (dwBrowseFilterType,
szFilterCriteria, ppIEnumString)
Not implemented GetQualifiedAreaName (szAreaName,
pszQualifiedAreaName)
Not implemented GetQualifiedSourceName (szSourceName,
pszQualifiedSourceName)
62 3BSE035983R4101
Section 5 Alarm and Event Interfaces Supported
OPCEventSubscription Object
Status Method
Implemented SetFilter (dwEventType, dwNumCategories,
pdwEventCategories, dwLowSeverity,
dwHighSeverity, dwNumAreas, pszAreaList,
dwNumSources, pszSourceList)
Implemented GetFilter (pdwEventType, pdwNumCategories,
ppdwEventCategories, pdwLowSeverity,
pdwHighSeverity, pdwNumAreas, ppszAreaList,
pdwNumSources, ppszSourceList)
Implemented SelectReturnedAttributes (dwEventCategory,
dwCount, dwAttributeIDs)
Implemented GetReturnedAttributes (dwEventCategory,
pdwCount, pdwAttributeIDs)
Implemented Refresh (dwConnection)
Implemented CancelRefresh (dwConnection)
Implemented GetState (ppActive, pdwBufferTime, pdwMaxSize,
phClientSubscription)
Implemented SetState (bActive, dwBufferTime, dwMaxSize,
hClientSubscription, pdwRevisedBufferTime,
pdwRevisedMaxSize)
Status Method
Implemented EnumConnectionPoints (ppEnum)
Implemented FindConnectionPoint (riid, ppCP)
3BSE035983R4101 63
Status Section 5 Alarm and Event
Status
The OPC Alarm and Event Server has the following states:
OPCAE_STATUS_RUNNING
OPCAE_STATUS_FAILED (not used for the moment)
OPCAE_STATUS_NOCONFIG
OPCAE_STATUS_SUSPENDED
The following applies to OPC Server for AC 800M:
When the OPC Server is started, the status is set to
OPCAE_STATUS_NOCONFIG.
When connected to at least one controller, the OPC Server status is always
OPCAE_STATUS_RUNNING.
If all controllers are removed from the panel, the OPC Server status returns to
OPCAE_STATUS_NOCONFIG.
The system variable SetFailedAtNoConn is used to control the behavior when
all connections to controllers are lost (for information on how to set this
variable, see Setting System Variables on page 67):
The default value of SetFailedAtNoConn is True.
With SetFailedAtNoConn set to True:
If there are controllers in the panel, but all connections are offline, the
OPC Server status is set to OPCAE_STATUS_SUSPENDED. As soon
one of the connections is restored, the OPC Server status returns to
OPCAE_STATUS_RUNNING.
With SetFailedAtNoConn set to False:
The OPC Server status is OPCAE_STATUS_RUNNING as long as there
are controllers in the panel, no matter if they have a working connection or
not.
64 3BSE035983R4101
Section 5 Alarm and Event Buffer Queues
Buffer Queues
There is a queue in the Alarm and Event Server for every connected Alarm and
Event client (see Figure 11). All data that passes the OPC Server, for example event
notifications and acknowledges will be queued. The maximum size of the queues
can be configured through the configuration interface. The data in these queues is
only held in the primary memory and is lost when the gateway shuts down or when
a power failure occurs. It is possible to have a second OPC Server in parallel to
increase the data security.
Connectivity Connectivity OPC Client
Servers Servers
Controller 1 Controller 2
3BSE035983R4101 65
OPC Alarm and Event Server Behavior at Power Fail Section 5 Alarm and Event
Note
The Alarm and Events Server has the following limitations.
Tracking-related events (events generated from operator interactions) are not
supported.
The optional Quality information is not supported.
The optional SubConditions are not supported. That means that our conditions
always only have one SubCondition (Single state conditions).
The optional Area concept from OPC alarm and event is not supported.
66 3BSE035983R4101
Section 5 Alarm and Event OPC Alarm and Event Clients
3BSE035983R4101 67
Setting System Variables Section 5 Alarm and Event
For more information about system variables, see the OPC Server for AC 800M
Online Help.
All the other system variables available, are presented in the AE Settings dialog
box, (Settings > AE Settings...). See Alarm and Event Settings on page 28.
68 3BSE035983R4101
Section 5 Alarm and Event Filtering of Event Notifications
The Process Simple Event and the Process Condition Event categories are used for
simple events respective condition-related events generated from applications.
The categories System Simple Event and System Condition Event are used for
system simple events and system alarms.
The OPC_SERVER_ERROR category is a simple event used to tell the OPC client
about refresh.
The last category, Process Data To Simple Event, is a simple event generated from
an application containing extra user defined data.
3BSE035983R4101 69
Refreshing OPC Clients Section 5 Alarm and Event
70 3BSE035983R4101
Section 5 Alarm and Event Performance
Performance
Response time to OPC clients will slow down considerable if more than 10 OPC
clients are connected to the OPC server.
Sending alarms to OPC server is done with the limitations of MMS traffic, but are
time stamped correctly.
3BSE035983R4101 71
Performance Section 5 Alarm and Event
72 3BSE035983R4101
Appendix A Setting Up from Windows 2000
This appendix addresses users who are running the Windows 2000 Professional
operating system and those cases where setup procedures may differ from how it
looks when setting up using Windows XP.
This subsection is the same as Running the OPC Server and OPC Client on
Different Computers on page 37, but addresses users of the
Windows 2000 Professional operating system.
If you are going to run the OPC server on one PC and the OPC client on another PC,
the following DCOM settings must first be performed.
Use the Windows 2000 Professional DCOMCnfg tool on each of the PC:s.
DCOM should however only be used if absolutely needed, due to the risk for lost
connection as described in Lost Connection Between OPC Client and OPC
Server on page 75.
3BSE035983R4101 73
DCOM settings on the OPC Server PC Appendix A Setting Up from Windows 2000
4. In the Applications tab, locate the OPC Server for AC 800M and click the
Properties ... button.
5. In the OPC Server for AC 800M Properties dialog box and in the General
tab, set Authentication Level to (None).
6. In the Security tab, select Use custom access permissions and click Edit ...
button to register access permissions.
7. In the Registry Value Permissions dialog box, click the Add... button. In the
Add Users and Groups dialog box, select the user group(s) or the user
account(s) the OPC client is running under. The account must be known on the
domain by both PCs.
8. In the Add Users and Groups dialog box, click the Add button for your
selected user group(s) or user(s). They are listed in the Add Names: box. The
type of access should be Allow Access.
Click the OK button.
9. Click the OK button in the Registry Value Permissions dialog box.
10. In the OPC Server for AC 800M Properties dialog box, select Use custom
launch permissions and click the Edit button.
11. In the Registry Value Permissions dialog box, add the same user group(s) or
user account(s) as above.
12. In the OPC Server for AC 800M Properties dialog box, click the OK button.
If a parameter is incorrect, a DCOM Configuration message is displayed.
13. Finally, in the Distributed COM Configuration Properties dialog box, click
the OK button.
14. If for some reason you do not want the OPC Server to run under the Local
System account, you can change this in Control Panel > Administrative
Tools > Services > OPC Server for AC 800M > Properties > Log On. There
you select This account and enter the new user by browsing for it and enter its
password.
15. Reboot the PC.
74 3BSE035983R4101
Appendix A Setting Up from Windows 2000 DCOM settings on the OPC Client PC
3BSE035983R4101 75
DCOM settings on the OPC Client PC Appendix A Setting Up from Windows 2000
Workaround: Reboot both the PC running the OPC Server and the PC running the
OPC Client. First restart the OPC Server, wait for some time and then the OPC
Client. The waiting time may vary dependent on the OPC Client. Recommended
waiting time is 15 minutes.
To ensure safe operation, display elements that are built in the HSI must make use
of the quality bad flag on the OPC attribute in order to alert the operator that the
communication is lost.
76 3BSE035983R4101
INDEX
A item quality 56
address space OPC groups 53
Data Access Server 54 performance 57
Alarm and Event Server 13, 59 power failure 50
interfaces supported 60 status indication 53
performance 71 writing 57
power failure 66 DCOM 17
status indication 64 set up in Windows 2000 73
asynchronous operations 16 set up in Windows XP 37
autoload
configuration 36 E
auto-logon to Windows event categories 69
set up 21 event notifications 69
C F
change file locations
personal settings 23 set up 23
product settings 23 file management 18
clock synchronization 17
set up 32 I
cold retain values 17 install
save 33 OPC Server for AC 800M 19
COM 17 interfaces supported
communication handling 16 Alarm and Event Server 60
configuration DA 52
autoload 36 item quality
save 35 Data Access Server 56
connect controllers 26
L
D limitations
Data Access Server 13, 49 asynchronous operations 16
address space 54 lost connection 40, 75
interfaces supported 52
3BSE035983R4101 77
Index
M configuration 35
maintenance session log 41
lost connection 40, 75 set up
power failure 47, 50, 66 auto-logon to Windows 21
memory reservation clock synchronization 32
set up 22 DCOM in Windows 2000 73
DCOM in Windows XP 37
O file locations 23
objects memory reservation 22
OPCEventAreaBrowser 62 RNRP 21
OPCEventServer 60 update rate 30
OPCEventSubscription 63 Setup Wizard 20
OPC Alarm and Event Server 13, 59 status indication
OPC Data Access Server 13, 49 AE Server 64
OPC groups Data Access Server 53
Data Access Server 53 system configuration 14
OPC Server 40, 75 system variables 67
OPC Server Configuration Panel 24
U
P update rate
performance 47 set up 30
Alarm and Event Server 71
Data Access Server 57 V
personal settings vendor specific attributes 70
change 23
power failure 47 W
Alarm and Event Server 66 writing
Data Access Server 50 Data Access Server 57
product settings
change 23
R
refresh 70
RNRP
set up 21
S
save
cold retain values 17, 33
78 3BSE035983R4101
BackCover.fm Page 19 Wednesday, October 20, 2004 10:27 AM
3BSE035983R4101. Printed in Sweden May 2005
Copyright 2003 - 2004 by ABB. All Rights Reserved
Registered Trademark of ABB.
Trademark of ABB.
http://www.abb.com/control