OPC Data Access: Expert Workshop E143

Download as pdf or txt
Download as pdf or txt
You are on page 1of 46

Expert Workshop E143 Chapter 5

OPC Data Access

Extended Automation System 800xA


© ABB Consult IT - 1
Revision C
OPC
Data Access Data Access Subscribers

„ Workplace
„ Process Graphic displays
„ Faceplates

„ History Logs
„ Direct Logs

„ 3rd Party OPC clients


© ABB Consult IT - 2
Revision C
OPC
Data Access OPC Definitions

„ Defines the interaction between Client and Server.


2 Concepts
„ Name space (how objects are organized)
„ Object Hierarchy

„ OPC-Sever-Object
„ Top level object connection to Server
„ OPC-Group-Object
„ Organizes the items. Info about cycle time etc
„ OPC Item object
„ Represents attributes from Nodes and Leafs
© ABB Consult IT - 3
Revision C
OPC
Data Access Workplace Data subscription example

Workplace Graphic Fileset (.ocx)


Disk
Graphic Cache
Display

Plant Network

Connectivity Aspect
Server Server

Control Network

Controller
© ABB Consult IT - 4
Revision C
OPC
Data Access OPC DA Flow Chart
Automation clients such History and Trend Process Graphics 3rd party OPC
as VB code, Clients
C++ code, Excel sheets.

ABB Automation model


OPC Clients

Data Subscription
800xA OPC Data Aspect Directory
Access Server Structures
• Control Structure
•Service Structure
CS Lib

Injector Connector Connector Connector

PPA MB300 OPC OPC


Service Adapter Adapter Adapter

COM/DCOM
RTA Board AC800 OPC 3rd party OPC Data
© ABB Consult IT - 5

Server Servers
Revision C
OPC
Data Access Data Subscription Example Detailed

Control Structure 3 Find the Service


Group in the
Network Service
object Strucure
Data
Source 2
Definition
Aspect
Uploader Find the Service Structure
Aspect Data Source
OPCDA_Connector,
Definition
Service
One of the
Service Providers
SG_Network,
Controller Temperature will be selected
Service Group
object
4
Provider,
1 Control Property List Service
Connection - Type Provider
Find object
Aspect - Item ID in the Service
“temperature”
OPC Server. Provider
and property Provider,
- Permission Definition
“Value” Service
Provider
© ABB Consult IT - 6
Revision C
OPC
Data Access OPC Data Source Definition

Object X (a child to Control Network 1)

”Subscribe for live data”

AC800 OPC Server in CS1A


© ABB Consult IT - 7
Revision C
OPC
Data Access Diagnostics Overview
Diagnostic Window OPC Client (3rd party)
PPA Client
Workplace

OPC Handler

Connectivity Server (AC800)


AppLog Logfiles
OPC DA Connector

OPC Adapter

OPC Server
Panel
AC800 OPC Server
System Alarms & Events

MMS Service
© ABB Consult IT - 8
Revision C
OPC
Data Access Basic OPC DA Troubleshooting
No subscription in graphical display?

1. Check Control Connection Aspect for the object


2. Check Data Source Definition Aspect
3. Check the status of the Connector
4. Use a stand alone OPC Client and connect to the OPC Handler
and OPC Server
© ABB Consult IT - 9
Revision C
OPC
Data Access 1. Check control connection aspect

Quality must be good


© ABB Consult IT - 10
Revision C
OPC
Data Access 2. Check Data Source Definition Aspect

1. Check that ProgID is


according to desired OPC
server
2. Check node
3. Check that you have a data
key, which differs from zero
© ABB Consult IT - 11

4. Press View to check the


connector status
Revision C
OPC
Data Access 3. Connector Status

State must be Service


© ABB Consult IT - 12
Revision C
OPC
Data Access 4. Use 3rd Party Client

Start Æ Run… advdsopcclient


(or use any other 3:rd party OPC client)

1. Select OPC Server (browse)


2. Connect
3. Add Group (select update interval)
4. Advise
5. Add Item (via browser or ItemID)
6. Verify data
© ABB Consult IT - 13
Revision C
OPC
Data Access Graphics Diagnostics Overview

”<Alt> + <Shift> + mouse click”


© ABB Consult IT - 14
Revision C
© ABB Consult IT - 15
Revision C
OPC
Data Access
System Status
OPC
Data Access
© ABB Consult IT - 16 OPC Server Statistics

Controller must be
Revision C

selected
OPC
Data Access
OPC Communication Asynchronous Loops
Connectivity Server (AC 800M)

OPC Data Access Service

Asynchronous loop determined


by the subscription time in the
OPC group i.e. log configuration
OPC Server or graphic update time.

Asynchronous loop determined


by the update rate in the OPC
Controller panel.

T=0 T=2 T=4 T=6 T=8 T=10 T=12 T=14 T=16 T=18 T=20 T=22 T=24 T=26 T=28 T=30
Sampling in
T=0 T=5 T=10 T=15 T=20 controller
Sampling in OPC server. In this example the
© ABB Consult IT - 17

sampling is not an even multiple of the sampling


rate in the controller. The data you read is not
time tagged with a delta time of 5s.
Revision C
OPC
Data Access
© ABB Consult IT - 18
Revision C
AC800 Variable Communication Statistics
OPC
Data Access
© ABB Consult IT - 19
Revision C
AC800 MMS Connections
OPC
Data Access AC800 OPC Server – Tracing method 1

Change to
”true”

Session Log
I 2006-02-10 14:52:35.125 AddGroup 'AdvDsOPCAdapterGroup87' to OPCServer object da0168
I 2006-02-10 14:52:35.125 OPCGroup object constructor d96b60 ... Done
Active = true. Requested Update Rate = 1000. Revised Update Rate = 1000.
I 2006-02-10 14:52:35.156 Advise 2.0 on OPCGroup ... Done
I 2006-02-10 14:52:35.171 AddItems (new #items = 5) to OPCGroup d96b60 with 0 items...Done
I 2006-02-10 14:52:58.546 AddItems (new #items = 2) to OPCGroup db0b40 with 3 items...Done
I 2006-02-10 15:01:09.656 RemoveItems (#items = 5) from OPCGroup d96b60...Done
© ABB Consult IT - 20

I 2006-02-10 15:01:09.687 Unadvise 2.0 on OPCGroup ... Done


I 2006-02-10 15:01:09.718 RemoveGroup d96b60 from OPCServer object da0168
...I 2006-02-10 15:01:09.718 OPCGroup object destructor d96b60 ... Done
Revision C
OPC
Data Access AC800 OPC Server – Tracing Method 1

Changed system
variables can be seen in
the SetupWizard

Changed values must be set


back to their original values after
troubleshooting is done!
© ABB Consult IT - 21
Revision C
OPC
Data Access AC800 OPC Server – Tracing Method 2

OPCItemsDebug.cfg
Applications.Application_1.Signals.Sig2.Out
© ABB Consult IT - 22
Revision C
OPC
Data Access AC800 OPC Server – Tracing Method 2

Restart the AC800 OPC Server service

2006-02-10 16:12:05.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 35.54556 Quality=
GOOD Timestamp= 2006-02-10 15:12:05.109
2006-02-10 16:12:10.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 2.719116E-02
Quality= GOOD Timestamp= 2006-02-10 15:12:10.124
2006-02-10 16:12:15.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 35.54556 Quality=
GOOD Timestamp= 2006-02-10 15:12:15.124
2006-02-10 16:12:20.327 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 2.719116E-02
Quality= GOOD Timestamp= 2006-02-10 15:12:20.124
2006-02-10 16:12:25.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 35.54556 Quality=
GOOD Timestamp= 2006-02-10 15:12:25.124
2006-02-10 16:12:30.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 2.719116E-02
Quality= GOOD Timestamp= 2006-02-10 15:12:30.124
2006-02-10 16:12:35.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 35.54556 Quality=
GOOD Timestamp= 2006-02-10 15:12:35.124
2006-02-10 16:12:40.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 2.719116E-02
© ABB Consult IT - 23

Value= 2.719116E-02 Quality= GOOD


Quality= GOOD Timestamp= 2006-02-10 15:12:40.109 Timestamp= 2006-02-10 15:12:30.124
2006-02-10 16:12:45.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 35.54556 Quality=
GOOD Timestamp= 2006-02-10 15:12:45.124
2006-02-10 16:12:50.312 hr = 0 ODC for Group: AdvDsOPCAdapterGroup6 Applications.Application_1.Signals.Sig2.Out Value= 2.719116E-02
Quality= GOOD Timestamp= 2006-02-10 15:12:50.124
Revision C
OPC
Data Access AppLog Summary

„ AppLog is a developer tool.


„ AppLog is not documented.
„ AppLog is not intended for end customer use.
„ AppLog methods may have a negative impact on
performance.
„ Careless use of AppLog may cause application crashes
and/or system malfunction.
„ Test logs and operations at home office before doing it
live at a plant in production.
© ABB Consult IT - 24
Revision C
OPC
Data Access
© ABB Consult IT - 25
Revision C
Starting AppLog (AfwAppLogViewer.exe)
OPC
Data Access AppLog Application Overview
Nodes Operations

Filter

Logs

Processes
Results
© ABB Consult IT - 26
Revision C
© ABB Consult IT - 27
Revision C
OPC
Data Access
AppLog Example
OPC
Data Access Workplace – OPC Handler Log

ƒ Subscription request
2007-11-13 13:26:36:409, DCASCS12, AfwWorkplaceApplication, PID: 6540, Thread: 5048
OPC Communicator, Common, level = 3, Tag =
AddItems: 5 items, OPC group handles hC(4), hS(0) OpcHandler=0x9917658
ItemID = '{2C0C1797-1363-444D-8C92-D8CE69693A8D}:FUNCTION BLOCK:OUT'(VT_R4 (Requested
VT_EMPTY)): active(1), hC(1) hS(2563), blob(656/0), HR(0)

ƒ Subscription response
2007-11-13 13:26:36:471, DCASCS12, AfwWorkplaceApplication, PID: 6540, Thread: 5048
OPC Communicator, Common, level = 2, Tag =
NewValues_1_0: OpcHandler=0x9917658
GroupSH:0 Item cH(1), sH(2563), ItemID:'{2C0C1797-1363-444D-8C92-D8CE69693A8D}:FUNCTION
BLOCK:OUT', NewValue:value(VT_R4) = 12.3664, Quality:0xc0, TimeStamp:11/13/2007 13:26:35, Result:0x0
© ABB Consult IT - 28
Revision C
OPC
Data Access Subscription Cache

Contains Object and Item information


used for subscription.
If the information is inconsistent you
may delete the *.sub files

The OPC communicator log reveals if the BLOB information must be


rebuild or not i.e. can the contents be used from cache.

2007-11-14 10:32:52:213, DCASCS11, AfwWorkplaceApplication, PID: 7764, Thread: 4876


OPC Communicator, Common, level = 3, Tag =
AddItems: 5 items, OPC group handles hC(2), hS(0) OpcHandler=0x9799b48
ItemID = '{2C0C1797-1363-444D-8C92-D8CE69693A8D}:FUNCTION BLOCK:OUT'(VT_R4 (Requested VT_EMPTY)): active(1), hC(1)
hS(1025), blob(0/656), HR(0)
Indicate invalid BLOB when you
get a number right of the slash
© ABB Consult IT - 29

AddItems: 5 items, OPC group handles hC(4), hS(0) OpcHandler=0xcebe6c8


ItemID = '{2C0C1797-1363-444D-8C92-D8CE69693A8D}:FUNCTION BLOCK:OUT'(VT_R4 (Requested VT_EMPTY)): active(1), hC(1)
hS(1027), blob(656/0), HR(0)
Revision C

Indicate a valid BLOB when you


get a zero right of the slash
OPC
Data Access
© ABB Consult IT - 30
Revision C
OPC DA Connector Operations
OPC
Data Access OPC DA Connector Statistics (1/2)
-------------------Backends--------------------
Acc. num client connect: 4, last time: 2/13/2006 10:45:40 PM 718 ms
Acc. num client disconnect: 0, last time: -no time-

Total number of connected clients: 4

Connected clients:
Id: 0, BackendId: 0x00CD9370, Node: 'GIT3052', App: 'AdvEAEngine', User: '800xAService', Items:
5 (5 active + 0 inactive)
Id: 1, BackendId: 0x00CDCF20, Node: 'GIT3052', App: 'AdvHtHistorySrv', User: '800xAService',
Items: 15 (15 active + 0 inactive)
Id: 2, BackendId: 0x00CDD4B8, Node: 'GIT3052', App: 'AdvAeAlarmManager', User: '800xAService',
Items: 1 (1 active + 0 inactive)
Id: 3, BackendId: 0x00CE9BE0, Node: 'GIT3052', App: 'AfwWorkplaceApplication', User: ‘Admin',
Items: 2 (2 active + 0 inactive)

Reference to OPC groups


seen in Adapter Statistics
© ABB Consult IT - 31
Revision C
OPC
Data Access OPC DA Connector Statistics (2/2)
-------------------General--------------------
Acc. total num items added: 27 (27 active + 0 inactive), last time: 2/13/2006 10:45:52 PM 62 ms
Acc. num items removed: 4 (4 active + 0 inactive), last time: 2/13/2006 10:45:54 PM 15 ms
Acc. num items activated: 0, last time: -no time-
Acc. num items deactivated: 0, last time: -no time-

Total number of items: 23


Number of active items: 23

Acc. num adapter call errors: 0, num stored errors: 0, max stored errors: 50
Acc. num item errors: 0, num stored errors: 0, max stored errors: 500

Acc. num items changed: 950, last time: 2/13/2006 10:45:56 PM 46 ms

Acc. num read ops started: 0, last time: -no time-


Acc. num read ops completed: 0, last time: -no time-
Acc. num items read: 0
Gives an indication of the
Acc. num write ops started: 0, last time: -no time- total subscription rate
Acc. num write ops completed: 0, last time: -no time-
Acc. num items written: 0

-------------------Access Control Manager--------------------


Lock Monitoring status: DISABLED
Locked items (count = 0)
© ABB Consult IT - 32
Revision C
OPC
Data Access OPC DA Adapter (1/2)
***** OPC Adapter Statistics *****

---------------------------------------
Ack. num items added: 20, last time: 2/13/2006 10:45:52 PM
Ack. num items removed: 4, last time: 2/13/2006 10:45:54 PM

Ack. num recovery items added: 7, last time: 2/13/2006 10:35:07 PM


Ack. num recovery items removed: 0, last time: -no time-

Ack. num OPC call errors: 0, num stored errors: 0, max stored errors: 50

Ack. num item errors: 70, num stored errors: 70, max stored errors: 500
Last item error: AddItem, hr = 0xc0040007 (OPC_E_UNKNOWNITEMID(0xc0040007) The item is no longer
available in the server address space. ), time: 2/13/2006 10:53:08 PM

Ack. num items changed: 2079, last time: 2/13/2006 10:53:30 PM

Ack. num read ops started: 0, last time: -no time-


Ack. num read ops completed: 0, last time: -no time-
Ack. num items read: 0

Ack. num write ops started: 0, last time: -no time-


Ack. num write ops completed: 0, last time: -no time-
Ack. num items written: 0
© ABB Consult IT - 33
Revision C
OPC
Data Access OPC DA Adapter (2/2)
Number of clients: 4
Client #1(00000000): number of groups: 1
Group #1: name = 'AdvDsOPCAdapterGroup0', update rate = 1000 [ms], number of Items: 3

Client #2(00000001): number of groups: 4


Group #1: name = 'AdvDsOPCAdapterGroup1', update rate = 500 [ms], number of Items: 1
Group #2: name = 'AdvDsOPCAdapterGroup2', update rate = 1000 [ms], number of Items: 1
Group #3: name = 'AdvDsOPCAdapterGroup4', update rate = 5000 [ms], number of Items: 7
Group #4: name = 'AdvDsOPCAdapterGroup5', update rate = 20000 [ms], number of Items: 1

Client #3(00000002): number of groups: 1


Group #1: name = 'AdvDsOPCAdapterGroup6', update rate = 1000 [ms], number of Items: 1

Client #4(00000003): number of groups: 1


Group #1: name = 'AdvDsOPCAdapterGroup12', update rate = 1000 [ms], number of Items: 2

Total number of groups: 7


Total number of items: 16
Total number of items in recovery state: 7
Reference to the Subscribing
clients in the Connector statistic
© ABB Consult IT - 34
Revision C
OPC
Data Access OPC DA Adapter List OPC groups

* OPC Groups (focused clients marked with 'o' and focused groups marked with '+') *
Number of OPC groups: 5
Group #1: client id = 0, name = 'AdvDsOPCAdapterGroup0', environment = {F6590D3D-7BB4-4430-A21E-62C1F2A1518A},
group server handle = 0, update rate = 500 [ms], number of items: 2
Group #2: client id = 0, name = 'AdvDsOPCAdapterGroup1', environment = {F6590D3D-7BB4-4430-A21E-62C1F2A1518A},
group server handle = 1, update rate = 1000 [ms], number of items: 8
Group #3: client id = 0, name = 'AdvDsOPCAdapterGroup2', environment = {F6590D3D-7BB4-4430-A21E-62C1F2A1518A},
group server handle = 2, update rate = 2000 [ms], number of items: 2
Group #4: client id = 0, name = 'AdvDsOPCAdapterGroup3', environment = {F6590D3D-7BB4-4430-A21E-62C1F2A1518A},
group server handle = 3, update rate = 5000 [ms], number of items: 10
Group #5: client id = 4, name = 'AdvDsOPCAdapterGroup13', environment = {F6590D3D-7BB4-4430-A21E-62C1F2A1518A},
group server handle = 4, update rate = 1000 [ms], number of items: 10

Parameters to be used when


focus filter is going to be set
© ABB Consult IT - 35
Revision C
OPC
Data Access OPC DA Adapter Set Focus Filter

Parameters:
Client Id = A:4
Focus Policy =
Group Handle = A:4

Result:

****** View/Modify focus filter ******

Client id: 4 added to the focus filter!

Group server handle: 4 added to the focus filter!


© ABB Consult IT - 36

Focus policy is exclusive focus (1 = do not show focused groups outside focused clients).
Revision C
OPC
Data Access OPC DA Adapter and Workplace

2007-11-13 15:26:32:424, DCASCS12, AdvDsOPCConnector, PID: 284, Thread: 5768


AdvDsOPCAdapter, Basic, level = 2, Tag =
data: item cH(95), quality(c0), 11/13/2007 15:26:32, value(VT_R4) = 39.0211

2007-11-13 15:26:32:424, DCASCS12, AfwWorkplaceApplication, PID: 4564, Thread: 4208


OPC Communicator, Common, level = 3, Tag =
COpcGroup::NewValues OpcHandler=0x9c91a98

2007-11-13 15:26:32:424, DCASCS12, AfwWorkplaceApplication, PID: 4564, Thread: 4208


OPC Communicator, Common, level = 2, Tag =
NewValues_1_0: OpcHandler=0x9c91a98
GroupSH:0 Item cH(4), sH(768), ItemID:'{C717871D-CE16-4295-A107-A0DD25F20621}:FUNCTION
BLOCK:OUT', NewValue:value(VT_R4) = 39.0211, Quality:0xc0, TimeStamp:11/13/2007 15:26:32, Result:0x0
© ABB Consult IT - 37
Revision C
OPC
Data Access OPC DA Adapter Clear Focus Filter

Parameters:
Client Id = C
Focus Policy =
Group Handle = C

Result:

****** View/Modify focus filter ******

The client id focus filter is cleared!

The group focus filter is cleared!


© ABB Consult IT - 38

Focus policy is exclusive focus (1 = do not show focused groups outside focused clients).
Revision C
OPC
Data Access Third Party OPC Connection

„ General DCOM settings according to configuration


manual 3BDS011222
„ If you are not able to browse remotely the general
settings which allows OPCEnum is not correct. Check if
ANONYMOUS LOGIN is possible
„ Check the Identity on the specific OPC service both on
server and client. (Service account or a specific OPC
account available in 800xA)
„ Check that you don’t get any access denied messages
in the 800xA system event log.
© ABB Consult IT - 39
Revision C
© ABB Consult IT - 40
Revision C
OPC
Data Access
ABB Logo
Maintenenance Expert workshop

Exercise 5.1 Troubleshoot Data access

5.1.1 Description
This exercise deals with OPC DA troubleshooting tools and technique available to
debug OPC DA subscriptions in the 800xA system.

5.1.2 Objectives
Upon completion of this exercise you will be able to:
• Trace the flow of data from the controller to Process Graphics.
• Narrow down the area where data subscription problem exist.

5.1.3 Reference documentation


• Documentation in workshop binder.
• SV 5.0 Configuration Manual (3BDS011222R5001)

1/4
E143-05 Exercise 5.1 - RevC.doc

5.1.4 Exercise Steps


You suspect an OPC DA overload situation. Your task is to find out the current OPC
load situation. Do the following steps:
1. How many subscription items do you have on the AC 800M OPC servers?
Open a number of graphic displays notice how the number of item changes. Close
all graphics and work places. Who are the remaining subscribers, use the applog to
find out? Find also out which application produces the most number of OPC
subscription items, use the OPC variable statistics.

2. The number of OPC items you are subscribing on doesn’t really give a true
indication of the OPC load. A better value is the number of item changes. How
many item changes do you get when there is no workplace opened use applog
operations to find out the number of item changes you have? Open a number of
graphic displays how much do the number of item changes increase?

3. Start the application OPCClientAC800.exe on both servers. You find this


application in the application folder of E143 on the E partition. The application is
not implemented well. It gives a substantial increase of the MMS transactions.
Find out what is wrong by using system variables of the AC 800M OPC server.

2/4
Maintenenance Expert workshop

You suspect an intermittent subscription problem. You have seen that you get holes in
trend displays and you also get crosses in graphic displays. Your task is to determine if
the problem is related to the OPC server or upstream from the OPC server. The steps
below highlights more the technique since there is no problem in the test system Using
the applog technique is more difficult than just using subscribe for live data in control
connection aspects but you may need to use the applog technique when there is
nothing left or you want to log data for a longer time.

1. Start with logging the information from the AC 800M OPC server. Use a variable
which is changing all the time from any of the objects Sin1, SIG2 or Sig3. Create
an item trace by defining the full OPC tem path in the (OPCItemsDebug.cfg) file.
Examine the result in (OPCItemsDebug.log) file. What quality did you get?
Which time is used in the file of the logged values?

2. If you didn’t see any problem in the file concerning bad quality. You suspect that
the problem is located further up in the data flow chain. You will now set up a log
which logs the subscription from Graphic Displays on the workplace process. Use
the common log of the OPC DA communication component. Check that you get
values when you are opening graphic displays. Use the following graphic displays.
Send the result to files for offline analyzes.
Sin1Display
Sig2Display
Sig3Display

a) If you didn’t find any problem in the logs from the workplace application.
Your next task is to trace down the data flow in the OPC Data Access server.
This is the software component between the AC 800M OPC server and the
clients. In order to avoid a huge amount data to monitor you must concentrate
on one specific OPC group. Use the operation ListOPCGroups to find the
group of the graphic display of the workplace application. Use the Basic log of
the OPCAdapter. Set the level to 2. How is the OPC item presented as?

3/4
E143-05 Exercise 5.1 - RevC.doc

You want to investigate the handling of cached information. You suspect that cached
information is not used. You want to investigate what happens when the graphic is
newly deployed. What happens to Graphic displays when the workplace is restarted?
What happens to workplaces when you have made changes to control software?

1. Use the common log of the OPC DA communication component. Before you open
up the Graphic display Sin1Display check the box “Save incoming logs to file”.
Deploy the Graphic display. Is the BLOB information rebuild?

2. Close the graphic display. Call it up again what happens to the BLOB
information? Can it be reused? Close the Graphic display.

3. Make a change to the application containing the SIN1 object. Add a global
variable. Call up the same Graphic display again. Could the BLOB information be
reused?

4. Make a change to the object type by adding an internal variable. Could the BLOB
information be reused?

4/4
Maintenenance Expert workshop

Exercise 5.2 Add connection to 3:rd party OPC server

5.2.1 Description
This exercise deals with a connection to a 3: rd party OPC DA server. The exercise
emphasizes on the importance of DCOM settings.

5.2.2 Objectives
Upon completion of this exercise you will be able to:
• Set up a connection to a 3: rd party OPC server which is located on a different
node than the Connectivity Server.
• Be able to exchange data with the OPC server.
• Make a correct DCOM settings

5.2.3 Reference documentation


• Documentation in workshop binder.
• SV 5.0 Configuration Manual (3BDS011222R5001)

1/2
E143-05 Exercise 5.2 - RevA.doc

5.2.4 Exercise Steps


1. Install the Iconics OPC server on the client machine. Don’t do any DCOM
settings now.
2. Add an OPC connection to the Iconics OPC server on both connectivity servers.
a) Log on as 800xAAdmin on both machines. Can you subscribe on any values?

3. Log off from the client.


4. Try to make a subscription do you get any data?

5. What type of DCOM settings do need to do in order to correct the problems?

2/2

You might also like