3 Vendor-specific implementation
3.1 Protocol instances
The protocol can be started and run in up to five instances, one instance for each
possible IEC 60870-5-104 client attached. The instances operate independently of
one another, so it is possible to use different network link (TCP) and transport layer
settings for each instance.
The protocol is not in use by default in the device. A function block I5CLPRT1…
5 representing the protocol instance must first be dragged to the application
configuration sheet using Application Configuration. If only one instance is used,
instance block 1 should be chosen. Additional instances can then be added freely.
After the function block has been added to the application configuration sheet,
it needs to be enabled by assigning the protocol setting parameter
Operation
to
"1-On".
In order for the protocol instance to populate its own database based on the point
mapping defined by the
Map Select
parameter, the device must be restarted once.
So, whenever
Operation
or
Map Select
settings are changed, the device must be
restarted for the protocol instance to be properly set up according to the new
configuration.
Figure 2: Function block
3.2 IEC 60870-5-104 data objects
Most of the device's internal IEC 61850 process data objects can be mapped to
the IEC 60870-5-104 protocol. However, the potential protocol objects are not
pre-mapped by default, so these objects should be mapped using Communication
Management in PCM600.
The potential protocol objects have been pre-assigned into specific protocol ASDU
types based on the source objects’ IEC 61850 common data class (CDC) types. This
pre-assignment cannot be changed.
3.2.1 Single-point information
Single-point information is derived from several IEC 61850 boolean data attributes
(CDC.attribute/attribute/ …).
2NGA001859 A
Vendor-specific implementation
REX615
IEC 60870-5-104 Communication Protocol Manual
15
To Next Page
Loading...
