3.3.
3.3.1.
3.3.2.
18
COM600 series, Version 5.0
DNP 3.0 Serial Slave (OPC) User's Manual
Object
DNP Serial IED
Data Object (DO)
Event Definitions
Building object tree
General information 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 Serial Slave OPC
Client object.
Before the DNP Serial 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 Serial Slave OPC Client
2. DNP Serial Channel
3. DNP Serial IED
4. Data objects
Adding DNP Serial Slave OPC Client object
To add the OPC client object:
Description
A DNP Serial 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 Serial Slave
OPC Client with the cross reference function. They are
shown as child objects of the DNP Serial IED object in
the object tree.
Event definitions are used for the diagnostic OPC A&E
Server.
1MRS755495