EasyManua.ls Logo

Schweitzer Engineering Laboratories SEL-421-4 - DNP3 Documentation

Schweitzer Engineering Laboratories SEL-421-4
1518 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
16.12
SEL-400 Series Relays Instruction Manual Date Code 20171006
DNP3 Communication
DNP3 Documentation
Testing
Use the TEST DB2 command to test the data mapping from the relay to your
DNP3 master. You can use the TEST DB2 command to force DNP3 values by
object type and label. Although the relay reports forced values to the DNP3 host,
these values do not affect protection processing within the relay. The TEST DB2
command operates by object type and label, so it works equally well with custom
mapping and the default DNP3 maps. See TEST DB2 on page 14.56 for more
information.
When you are using the TEST DB2 command to test DNP3 operation, the Relay
Word bit TESTDB2 will be asserted to indicate that test mode is active. The
DNP3 status bit will also show forced status for any object variations that include
status.
DNP3 Documentation
Object List
Table 16.8 lists the objects and variations with supported function codes and
qualifier codes available in the relay. The list of supported objects conforms to
the format laid out in the DNP3 specifications and includes both supported and
unsupported objects. Those that are supported include the function and qualifier
codes. The objects that are not supported are shown without any corresponding
function and qualifier codes.
NOTE: The TEST DB2 command will
override the state of all instances of
the forced bit or value for all active
CADI2 protocols. This includes DNP3
serial and LAN/WAN and IEC 61850
GOOSE and MMS. Before using the
command, take precautions to ensure
against unintended operations from
inadvertent messages sent as the
result of a TEST DB2 override, for
example, a bit used to trip a breaker
on a remote relay via IEC 61850
GOOSE.
Table 16.8 Relay DNP3 Object List (Sheet 1 of 6)
Obj. Var. Description
Request
a
Response
a
Funct. Codes Qual. Codes Funct. Codes Qual. Codes
0 211 Device attributes—User-specific sets of attributes 1 0 129 0, 17
0 212 Device attributes—Master data set prototypes 1 0 129 0, 17
0 213 Device attributes—Outstation data set prototypes 1 0 129 0, 17
0 214 Device attributes—Master data sets 1 0 129 0, 17
0 215 Device attributes—Outstation data sets 1 0 129 0, 17
0 216 Device attributes—Max. binary outputs per request 1 0 129 0, 17
0 219 Device attributes—Support for analog output events 1 0 129 0, 17
0 220 Device attributes—Max. analog output index 1 0 129 0, 17
0 221 Device attributes—Number of analog outputs 1 0 129 0, 17
0 222 Device attributes—Support for binary output events 1 0 129 0, 17
0 223 Device attributes—Max. binary output index 1 0 129 0, 17
0 224 Device attributes—Number of binary outputs 1 0 129 0, 17
0 225 Device attributes—Support for frozen counter events 1 0 129 0, 17
0 226 Device attributes—Support for frozen counters 1 0 129 0, 17
0 227 Device attributes—support for counter events 1 0 129 0, 17
0 228 Device attributes—Max. counter index 1 0 129 0, 17
0 229 Device attributes—Number of counters 1 0 129 0, 17
0 230 Device attributes—Support for frozen analog inputs 1 0 129 0, 17
0 231 Device attributes—Support for analog input events 1 0 129 0, 17

Table of Contents

Related product manuals