In case of making a DNP3 direct command to a SBO configured object, the desired
behavior can be defined in the Communication Management tool. In case the direct
control mode property is set to “Always allowed”, the DNP3 stack automatically
performs the two needed commands to the native control object. Direct control is
always allowed. In case the direct control mode property is set to “Control model”, the
DNP3 control command must follow the native 61850 objects control model. SBO
control must be used in the SBO mode.
The DNP3 stack has a protocol dependent parameter setting for the timeout between
Select and Operate commands. The default value is “10 seconds” but it can be changed
via CROB select timeout parameter. Also the native control object have a configured
timeout for the SBO operation. Since the control object may also be available for
Local (manual) control, a longer timeout is often required. The DNP3 timeout should
be set lower than the native control object timeout.
3.4.3.3 Command blockings
According to the DNP3 standard, an outstation is considered to have the states “Local”
or “Remote”. The IEC 61850 IED in turn can be in “Local”, “Station”, “Remote”,
“Off”, or “All” state. A DNP3 controlling station can perform control operations in
“Station”, “Remote”, and “All” protection relay states. However, it is the controlled
protection relay's application in the outstation that rejects or accepts control
operations based on the control allowance states and not the DNP3 protocol stack. In
an RTU (non-intelligent outstation) application, the DNP3 stack rejects the
commands.
3.4.4 Accessing of non-protocol-mapped data
The protection relay application includes a number of general-purpose I/O data. By
default, these data are mapped to this protocol. See the point list manual for the exact
mappings.
The general-purpose objects can be connected to any internal object in the protection
relay configuration application using the Application Configuration or Signal Matrix
tool. This gives additional opportunities for the protocols.
Example 1
Due to security reasons, protocols do not contain mappings for the direct control of
physical outputs. This way, the client cannot accidentally write a change to a physical
output.
It is possible to connect general-purpose outputs to physical outputs using the
Application Configuration tool. The general-purpose output can also be controlled
from the protocol.
Section 3 1MRS758757 A
Vendor-specific implementation
18 REC615 and RER615
Communication Protocol Manual