Building Object Tree; General About Building Object Tree - ABB COM600 User Manual

Station automation, 3.4, dnp 3.0 lan/wan slave (opc)
Hide thumbs Also See for COM600:
Table of Contents

Advertisement

3.3.
3.3.1.
16
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual
Table 3.2-1 DNP LAN Slave OPC Client related objects
Object
DNP LAN Slave OPC Client
DNP LAN Channel
DNP LAN IED
Data Object (DO)
Event Definitions

Building object tree

General about building object tree

The object tree is built in the Communication structure of SAB600, see Figure 3.2-1. It
is built by adding objects in a logical order starting from the DNP LAN Slave OPC Client
object.
Before the DNP LAN Slave OPC Client can be taken into use, configure an OPC server
for the process communication. For more information on creating an OPC server, refer
to COM600 User's Manual.
You have several possible ways to add objects to the object tree in the Communication
structure:
You can right-click the object to which you want to add a child object.
You can copy the object.
Add the objects in the following order:
1. DNP LAN Slave OPC Client
2. DNP LAN Channel
3. DNP LAN IED
4. Data objects
Description
An object representing the DNP LAN Slave OPC Client.
An object representing the channel
A DNP LAN IED is used for a virtual station in COM600
representing the slave stations visible to the DNP master
system.
A data object is an instance of one of the IEC Common
data classes, for example single point status, measured
value etc. Depending on the class, each data object has
a set of attributes for monitoring and controlling the object,
for instance value, quality and control. Data objects are
connected from OPC servers to the DNP LAN Slave OPC
Client with the cross reference function. They are shown
as child objects of the DNP LAN IED object in the object
tree.
Event definitions are used for the diagnostic OPC A&E
Server.
1MRS755496

Advertisement

Table of Contents
loading

Table of Contents