Building Object Tree - ABB COM600 3.4 User Manual

3.3.
3.3.1.
16
Station Automation COM600 3.4
IEC 60870-5-101 Slave (OPC) User's Manual
Table 3.2-1 IEC101 OPC Client related objects
Object
IEC101 OPC Client
IEC101 Balanced Channel
IEC101 Unbalanced Channel
IEC101 Device (IEC101 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 IEC101 Slave OPC Client
object.
Before the IEC101 Slave OPC Client can be taken into use, configure an OPC server
for the process communication. For more information on this subject, 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. IEC101 Slave OPC Client
2. IEC101 Balanced Channel / IEC101 Unbalanced Channel
3. IEC101 Device (IEC101 IED)
4. Data objects
Description
An object representing the IEC101 OPC Client.
An object representing the IEC101 channel using bal-
anced communication mode (point to point connection).
An object representing IEC101 Channel using unbalanced
communication mode (polled multipoint connection).
IEC101 Device is used for a virtual station in COM600
representing the slave stations visible to the
IEC101master 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 IEC101 Slave OPC
Client with the cross reference function. They are shown
as child objects of the IEC101 Device object in the object
tree.
Event definitions are used for the diagnostic OPC A&E
Server.
1MRS755382