9.64
SEL-2032 Communications Processor Instruction Manual Date Code 20120126
Protocols
Distributed Network Protocol 3.0 (DNP3) LAN/WAN
Use the DNPMAP command in a virtual terminal to the SEL-2701 to display
the data points (object types, indices, default variation, and source) and
controls (object type, indices, and destination) that are accessible via DNP3.
The output of the DNPMAP command documents the DNP3 data map(s) in
the SEL-2701 to help with the configuration of the DNP3 master.
Note that if you issue a DNPMAP command at the command line, you will
get the (serial) DNP3 data map of the host device, if it exists. However, if you
issue a PORT command (PORT 5 on an SEL-400 series relays, PORT 17 or
PORT 18 on an SEL communications processor) to open a transparent session
to the SEL-2701 console, then a DNPMAP [x], you will get the DNPMAP
output from the SEL-2701. The PORT command redirects all input from a
serial port away from the command parser for the device and sends the stream
of data to the SEL-2701. Also, any data that comes from the SEL-2701 is
redirected out the serial port.
Specify the desired custom map using an integer parameter corresponding to a
DNPMAP number (1–5). For example, the command DNPMAP 2 would be
used to view the custom data map for DNP3 Session 2. If a DNPMAP number
is not specified, a summary of DNP3 map settings for all configured sessions
will be displayed.
Summary and detailed map configurations are also available in the
DNPMAP.TXT and DNPMAPnn.TXT files from the SEL-2701 FTP
interface. The individual file names associated with the detailed custom map
settings follow the DNPMAPnn.TXT naming convention.
Event Data
The same serial DNP3 event data objects are available for DNP3 over an
Ethernet network. However, configuration is slightly different. You can still
configure the SEL-2032 to either report the data without a polling request
from the master (unsolicited data) or hold the data until the master requests it
with an event poll message.
With the event class settings ECLASSB, ECLASSC, and ECLASSA, you can
set the event class for binary, counter, and analog information. Virtual terminal
information is not supported for DNP3 over Ethernet since Telnet is available
to provide this capability. As with serial DNP3, you can also use the classes as
a simple priority system for collecting event data.
For event data collection, you must also consider and enter appropriate
settings for dead band and scaling operations on analog points shown in
Table 7.2. You can set and use either default dead band and scaling according
to data type or use a custom data map to select dead bands on a point-by-point
basis. See Custom Data Mapping on page 9.56 for a discussion of how to set
scaling and dead-band operations on a point-by-point basis.
The setting ANADB defines default dead-band operation for analog events. A
DNP3 master may also impose its own default dead band that it will use for
event data for a specific channel that override the SEL-2032 ANADB setting.
Because the default variations of DNP3 Objects 30 and 32 use integer data,
you must use scaling to send digits after the decimal point and avoid rounding
to a simple integer value. Scaling on the Ethernet DNP3 connection is subject
to the same limitations of the serial interface. The master should also be
configured to perform the appropriate arithmetic conversion on the incoming
value to display it in proper engineering units.
Set the default analog value scaling with the DECPL setting. Application of
event reporting dead bands occurs after scaling the incoming value with
10
DECPL
. For example, if you set DECPL to 2 and ANADB to 10, a measured
current of 10.14 amps would be scaled to the value 1014 (10.14 • 10
2
) and
NOTE: Most RTUs that act as
substation DNP3 masters perform an
event poll that collects event data of
all classes simultaneously. Confirm
that the polling configuration of your
master allows independent polling for
each class before implementing
separate classes in the SEL-2032.
Courtesy of NationalSwitchgear.com