T314-05 OPC Connectivity - RevC
T314-05 OPC Connectivity - RevC
TABLE OF CONTENTS
Chapter 5 - 1
T314-05 OPC Connectivity - RevC
5.1.1 Objectives
On completion of this chapter you will be able to:
• Describe communication structure and data flow
• Explain the necessary settings
• Verify communication (live data)
5.1.2 Legend
> Indicates when you go from one menu to a sub-menu
Italic Indicates object and file names
“ “ Indicates dialog box buttons, tabs, menus etc.
Bold Indicates important topics
Indicates start/explanation of student activity
Chapter 5 - 2
System 800xA Training
The OPC Foundation is a non-profit corporation that has established a set of standard
OLE/COM interface protocols advancing interoperability between automation/control
applications, field system/devices and business/office applications in the process
control world.
While OLE was originally designed for office applications (e.g. Word, Excel). OPC
technology is an extension of that protocol for industrial applications.
NOTE! OPC is an open standard.
www.opcfoundation.org
OPC provides a mechanism to provide data from a data source and communicate the
data to any client application in a standard way.
OPC is a group defined protocol for process control data communication. It has three
interfaces as follows:
• OPC Data Access for real time data
• OPC Historical Data Access for historical data
• OPC Alarm and Event for event data
Chapter 5 - 3
T314-05 OPC Connectivity - RevC
Aspect
Server
Connectivity
Server
The OPC Server must be installed in the same physical node as the Connectivity
Server.
There are a number of basic rules that applies:
• One OPC Server is allowed to subscribe to data from a maximum of 24 PM861
controllers, or the equivalent number of variables from other controller types.
• A maximum of three OPC Servers are allowed to subscribe to Data Access and/or
Alarm and Event from one controller.
• Multiple OPC Clients can subscribe to data or event notifications from the same
OPC Server.
• A third-party OPC Client should, if possible, be installed on the same PC as the
OPC Server.
Chapter 5 - 4
System 800xA Training
MMS stands for “Manufacturing Message Specification” and is an ISO 9506 standard.
For further information look at:
www.nettedautomation.com/standardization/ISO/TC184/SC5/WG2
OPC Item
This is the syntax (tag name) used to reference a register or bit location in the field
device (PLC, valve, power monitor meter etc…)
OPC Client
OPC Client is a software application that attaches to an OPC Server application and
establishes the OPC Items it wishes to read/write.
Chapter 5 - 5
T314-05 OPC Connectivity - RevC
Aspect 800xA
Directory Clients
Client/Server
Network
Afw OPC Service
Service Group Service Group
Service Service Service Service
Provider Provider Provider Provider
redundant redundant
Connectivity Connectivity
Servers Servers
AC 800M
controllers Controller XXX
Using information from the Aspect Directory, a service handler provides one uniform
interface to the service, relieving the client applications from having to deal with
issues such as how the service is partitioned, redundant service providers, etc.
NOTE! A Service Provider resides always in a dedicated node.
Chapter 5 - 6
System 800xA Training
Client/Server
Network
OPC Server
Connectivity
DA AE
Server Data Access Alarm & Events
Control
Network
AC 800M
controller
The Afw OPC server concept allows many different OPC servers to be placed under
one common server that unifies access to data from different sources.
This common server provides one set of OPC compliant interfaces, eliminating the
need for client applications to know which OPC server to use for each data item.
Chapter 5 - 7
T314-05 OPC Connectivity - RevC
The controller addresses can be “dragged and dropped” from the list to the OPC
Server Configuration panel.
3. Press “Connect”. The “Smiley” indicates that the connection is up and running.
Chapter 5 - 8
System 800xA Training
2. Click onto the browse button and select the configuration file from disc.
3. Accept all dialogs.
Chapter 5 - 9
T314-05 OPC Connectivity - RevC
2. To get a view about the kind of OPC Server which is used in the System 800xA,
click onto the tab card “OPC Configuration”. This is configured by default as
ABB.AC800MC_OpcDaServer.3.
Chapter 5 - 10
System 800xA Training
You have to connect to an OPC Alarm Server (collector) before you can get any
alarms and events.
2. Select Service Group object (in our example it is called AC800M OPC AE
Collector).
Chapter 5 - 11
T314-05 OPC Connectivity - RevC
3. Select the “Configuration” tab of the Service Provider Definition aspect for the
Service Provider object. Verify that the service is enabled and that the node of
your Connectivity Server is selected.
Chapter 5 - 12
System 800xA Training
6. Verify that OPC AE Server for AC 800M is set in the Collection Definition drop-
down list box.
Chapter 5 - 13
T314-05 OPC Connectivity - RevC
Open the Config View for the Function Block aspect of an object in the Control
Structure. Select the tab card “Property View”. Enable the option “Subscribe for live
data” to get the live data from the OPC-Server.
If the Quality column displays “Good", then the connection to the OPC Server is ok.
Chapter 5 - 14
System 800xA Training
Right click on the object Sxx_V1 and select “Main Faceplate” to call up the faceplate
for the valve.
If the OPC connection works well, you can switch for instance the vale to Auto mode.
The variable AutoMode will change from “False” to “True”.
Mode
indication
A bad OPC connection is displayed on the faceplate as shown below and you will
not be able to operate the valve. Also the Quality column shows “Bad
communication” in the Property View.
Chapter 5 - 15
T314-05 OPC Connectivity - RevC
This aspect provides knowledge about the services of System 800xA. The OPC
connection is one of the services. The Event Collector service handles the OPC Alarm
and Event stream coming into the system.
The green color indicates that the service is running well. In case of problems a red
color indicates a failed service (displayed in the picture below).
Chapter 5 - 16