Eaton PXM4K Series User manual

PXM 4/6/8K DNP3 Ethernet Communications User Manual
PXM 4/6/8K DNP3

ii
Contents
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
Contents
1. INTRODUCTION..................................................1
2. DNP3 PROTOCOL PRIMER .........................................1
2.1 Why DNP3? .......................................................1
2.2 Link Layer Responsibility.............................................5
2.3 Static and Event Data ...............................................6
2.4 Unsolicited Responses ..............................................7
2.5 Implementation Levels ..............................................7
2.6 Summary.........................................................7
3. DNP DEVICE PROFILE .............................................8
4. IMPLEMENTATION TABLE.........................................12
5. DNP3 ETHERNET COMMUNICATION SETUP CONFIGURATION UTILITY ..16
5.1 DNP3 Node Identification ...........................................17
5.2 Global Settings ...................................................18
5.3 Communication ...................................................19
5.4 DNP3 Input/Output Setup ...........................................23
5.5 Procedure to Create the DNP3 Database Configuration....................25
5.6 Assigning a Dead Band .............................................28
APPENDIX A POINTS LIST ..........................................29

1
1. Introduction
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
1. Introduction
This document contains the Power Xpert®Meter (PXM
Meter) 4000/6000/8000 Series device Distributed Network
Protocol (DNP) 3 ethernet communication Level-2 device
profile along with a detailed explanation of the web utility to
configure DNP3 parameters of the PXM Meter.
ote:N The PXM 4/6/8K supports DNP3 ethernet communi-
cation. DNP3 serial communication is not supported.
2. DNP3 Protocol Primer
Acknowledgment: Base materials used in Section 2 of this
manual were provided by and used with the permission of
the DNP Users Group www.dnp.org.
This is a primer for Users who want a quick understand-
ing of DNP3 without having to comb through the tedious
details of a complex specification. The writing style is
meant to be informal and personal.1
Let us start with what it is. Protocols define the rules by
which devices talk with each other, and DNP3 is a protocol
for transmission of data from point A to point B using serial
and IP communications. It has been used primarily by utili-
ties such as the electric and water companies, but it func-
tions well for other areas.
A typical electric company may have a common operations
center that monitors all of the equipment at each of its
substations. In the operations center, a powerful computer
stores all of the incoming data and displays the system for
the human operators. Substations have many devices that
need monitoring (Are circuit breakers opened or closed?),
current sensors (How many amperes are flowing?) and
voltage transducers (What is the line potential?). That only
scratches the surface. A utility is interested in monitor-
ing many parameters, too numerous to discuss here. The
operations personnel often need to switch sections of the
power grid into or out of service. Computers are situated
in substations to collect the data for transmission to the
master station in the operations center. The substation
computers are also called upon to energize or de-energize
the breakers and voltage regulators.
DNP3 uses the term outstation to denote remote comput-
ers as are found in the field. The term master is used for
the computers in the control centers.
DNP3 provides the rules for remotely located computers
and master station computers to communicate data and
control commands. DNP3 is a non-proprietary protocol that
is available to anyone by visiting the web site www.dnp.
org. Only a nominal fee is charged for documentation, but
otherwise it is available worldwide with no restrictions. This
means a utility can purchase master station and outsta-
tion computing equipment from any manufacturer and be
assured that they will reliably talk to each other. Vendors
compete based upon their computing equipment’s features,
costs and quality factors instead of who has the best pro-
tocol. Utilities are not bound to one manufacturer after the
initial sale.
What do the computers talk about? Outstation computers
gather data for transmission to the master.
 Binary input data that is useful to monitor two-state
devices. For example, a circuit breaker is closed or
tripped; a pipeline pressure alarm shows normal or exces-
sive.
 Analog input data that conveys voltages, currents, power,
reservoir water levels, and temperatures.
 Count input data that reports energy in kilowatt hours or
fluid volume.
 Files that contain configuration data.
The master station issues control commands that take the
form of:
 Close or trip a circuit breaker, start or stop a motor, and
open or close a valve; and/or
 Analog output values to set a regulated pressure or a
desired voltage level.
Other things the computers talk to each other about are
synchronizing the time and date, sending historical or
logged data, waveform data, and on and on.
2.1 Why DNP3?
DNP3 was designed to optimize the transmission of data
acquisition information and control commands from one
computer to another. It is not a general purpose protocol
like those found on the Internet for transmitting email,
hypertext documents, SQL queries, multimedia, and huge
files. It is intended for Supervisory Control and Data
Acquisition (SCADA) applications.
1 Readers should not assume this document contains formal rules, which are only provided by the DNP3 Specification volumes.

2
2. DNP3 Protocol Primer
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
2.1.1 Master and Outstation Databases
Figure 1 shows the master-outstation relationship and gives
a simplistic view of the databases and software processes
involved. The master is on the left side of Figure 1, and the
outstation is on the right side.
A series of square blocks at the top of the outstation depict
data stored in its database and output devices. The various
data types are conceptually organized as arrays. An array of
binary input values represents states of physical or logical
Boolean devices. Values in the analog input array represent
input quantities that the outstation measured or computed.
An array of counters represents count values, such as kilo-
watt hours, that are ever increasing (until they reach a maxi-
mum and then roll over to zero and start counting again).
Control outputs are organized into an array representing
physical or logical on-off, raise-lower, and trip-close points.
Lastly, the array of analog outputs represents physical or
logical analog quantities such as those used for set points.
Figure 1. Master and Outstation Relationship.
The elements of the arrays are labeled 0 through N - 1
where N is the number of blocks shown for the respective
data type. In DNP3 terminology, the element numbers are
called the point indexes. Indexes are zero-based in DNP3,
that is, the lowest element is always identified as zero.
Indexes are zero-based in DNP3, that is, the lowest element
is always identified as zero.
Notice that the DNP3 master also has a similar database
for the input data types (binary, analog and counter.) The
master uses values in its database for the specific purposes
of displaying system states, closed-loop control, alarm noti-
fication, billing, and much, much more. An objective of the
master is to keep its database updated. It accomplishes
this by sending requests to the outstation asking it to return
the values in the outstation’s database. This is termed
polling. The outstation responds to the master’s request
by transmitting the contents of its database. Arrows are
drawn at the bottom of Figure 1 showing the direction of
the requests (toward the outstation) and the direction of the
responses (toward the master). Later, we will discuss sys-
tems whereby the outstations transmit responses without
being asked.

3
2. DNP3 Protocol Primer
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
2.1.2 Layering
The master and the outstation shown in Figure 1 each have
two software layers. The top layer is the DNP3 user layer.
In the master, it is the software that interacts with the data-
base and initiates the requests for the outstation’s data. In
the outstation, it is the software that fetches the requested
data from the outstation’s database for responding to mas-
ter requests. It is interesting to note that if no physical
separation of the master and outstation existed, eliminating
the DNP3 might be possible by connecting these two upper
layers together. However, since physical, or possibly logi-
cal separation of the master and outstation exists, DNP3
software is placed at a lower level. The DNP3 User’s code
uses the DNP3 software for transmission of requests or
responses to the matching DNP3 User’s code at the other
end. More will be said about data types and software lay-
ers later, but first we want to examine a few typical system
architectures where DNP3 is used.
Figure 2. Common System Architectures.
2.1.3 System Architecture
Figure 2 shows common system architectures in use
today. At the top is a simple one-on-one system having
one master station and one outstation. The physical con-
nection between the two is typically a dedicated or dial-up
telephone line.
The second type of system is known as a multi-drop design.
One master station communicates with multiple outstation
devices. Conversations are typically between the master
and one outstation at a time. The master requests data
from the first outstation, then moves onto the next outsta-
tion for its data, and continually interrogates each outsta-
tion in a round robin order. The communication media is
a multi-dropped telephone line, fiber optic cable, or radio.
Each outstation can hear messages from the master and
is only permitted to respond to messages addressed to it.
Outstations may or may not be able to hear each other.

4
2. DNP3 Protocol Primer
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
In some multi-drop forms, communications are peer-to-peer.
A station may operate as a master for gathering information
or sending commands to the outstation in another station.
And then, it may change roles to become an outstation to
another station.
The middle row in Figure 2 shows a hierarchical type sys-
tem where the device in the middle is an outstation to the
master at the left and is a master with respect to the out-
station on the right. The middle device is often termed a
sub-master.
Both lines at the bottom of Figure 2 show data concentrator
applications and protocol converters. A device may gather
data from multiple outstations on the right side of the figure
and store this data in its database where it is retrievable by
a master station on the left side of the figure. This design is
often seen in substations where the data concentrator col-
lects information from local intelligent devices for transmis-
sion to the master station.
Figure 3. Master and Outstation Relationship – Layering.
2.1.4 TCP/IP
Many vendors offer products that operate using TCP/IP to
transport DNP3 messages in lieu of the media discussed
above. Link layer frames, which we have not talked about
yet, are embedded into TCP/IP packets. This approach has
enabled DNP3 to take advantage of Internet technology and
permitted economical data collection and control between
widely separated devices.
2.1.5 More On Layering
Communication circuits between the devices are often
imperfect. They are susceptible to noise and signal distor-
tion. DNP3 software is layered to provide reliable data
transmission and to affect an organized approach to the
transmission of data and commands. Figure 3 shows the
layering that was not shown in Figure 1.

5
2. DNP3 Protocol Primer
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
2.2 Link Layer Responsibility
The link layer has the responsibility of making the physical
link reliable. It does this by providing error detection and
duplicate frame detection. The link layer sends and receives
packets, which in DNP3 terminology are called frames.
Sometimes transmission of more than one frame is neces-
sary to transport all of the information from one device to
another.
A DNP3 frame consists of a header and data section. The
header specifies the frame size, contains data link control
information and identifies the DNP3 source and destination
device addresses. The data section is commonly called the
payload and contains data passed down from the layers
above.
DNP3 Frame
Header Data Section
Header
Sync Length Link Control Destination Source CRC
Figure 4. DNP3 Header and Data Sections.
Every frame begins with two sync bytes that help the
receiver determine where the frame begins. The length
specifies the number of octets in the remainder of the
frame, not including CRC check octets. The link control
octet is used for the sending and receiving link layers to
coordinate their activities.
2.2.1 Addressing
The destination address specifies which DNP3 device
should process the data, and the source address identi-
fies which DNP3 device sent the message. Having both
destination and source addresses satisfies at least one
requirement for peer-to-peer communications because the
receiver knows where to direct its responses. 65,520 indi-
vidual addresses are available. Every DNP3 device must
have a unique address within the collection of devices send-
ing and receiving messages to and from each other. Three
destination addresses are reserved by DNP3 to denote an
all-call message; that is, the frame should be processed
by all receiving DNP3 devices. One address is a universal
address, the details of which are not given here, and twelve
addresses are reserved for special needs in the future.
2.2.2 CRC Checks
The data payload in the link frame contains a pair of CRC
octets for every 16 data octets. This provides a high degree
of assurance that communication errors can be detected.
The maximum number of octets in the data payload is 250,
not including CRC octets. (The maximum length link layer
frame is 292 octets if all the CRC and header octets are
counted.)
2.2.3 Link Layer Confirmation
One often hears the term “link layer confirmation” when
DNP3 is discussed. A feature of DNP3’s link layer is the
ability for the transmitter of the frame to request the receiv-
er to confirm that the frame arrived. Using this feature is
optional, and it is often not employed because there are
other methods for confirming receipt of data. It provides
an extra degree of assurance of reliable communications.
If a confirmation is not received, the link layer may retry
the transmission. Some disadvantages to using link layer
confirmation are the extra time required for confirmation
messages and waiting for multiple timeouts when retries
are configured.
2.2.4 Transport Layer
The transport layer has the responsibility of breaking long
application layer messages into smaller packets sized for the
link layer to transmit, and, when receiving, to reassemble
frames into longer application layer messages. In DNP3 the
transport layer is incorporated into the application layer. The
transport layer requires only a single octet overhead to do
its job. Therefore, since the link layer can handle only 250
data octets, and one of those is used for the transport func-
tion, each link layer frame can hold as many as 249 applica-
tion layer octets.
2.2.5 Application Layer Fragments
Application layer messages are broken into fragments.
Maximum fragment size is determined by the size of the
receiving device’s buffer. The normal range is 2048 to 4096
bytes. A message that is larger than one fragment requires
multiple fragments. Fragmenting messages is the responsi-
bility of the application layer.
Note that an application layer fragment of size 2,048 must
be broken into 9 frames by the transport layer, and a frag-
ment size of 4,096 needs 17 frames. Interestingly, it has
been learned by experience that communications are some-
times more successful for systems operating in high noise
environments if the fragment size is significantly reduced.

6
2. DNP3 Protocol Primer
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
2.3 Static and Event Data
The application layer works together with the transport and
link layers to enable reliable communications. It provides
standardized functions and data formatting with which
the user layer above can interact. Before functions, data
groups, and variations can be discussed, the terms static,
events, and classes need to be covered.
In DNP3, the term static is used with data and refers to the
present value. Thus static binary input data refers to the
present On or Off state of a bi-state device. Static analog
input data contains the value of an analog at the instant it
is transmitted. One possibility DNP3 allows is requesting
some or all of the static data in an outstation device.
DNP3 events are associated with something significant
happening. Examples are state changes, values exceeding
some threshold, snapshots of varying data, transient data,
and newly available information. An event occurs when a
binary input changes from an On to an Off state or when
an analog value changes by more than its configured dead-
band limit. DNP3 provides the ability to report events with
and without time stamps so that, if desired, the master will
have the information to generate a time sequence report.
The master’s user layer can direct DNP3 to request events.
Usually, a master is updated more rapidly if it spends most
of its time polling for events from the outstation and only
occasionally asks for static data as an integrity measure.
The reason updates are faster is because the number of
events generated between outstation interrogations is small
and, therefore, less data must be returned to the master.
DNP3 goes a step further by classifying events into three
classes. When DNP3 was conceived, class 1 events were
considered as having higher priority than class 2 events,
and class 2 were higher than class 3 events. While that
scheme can be still be configured, some DNP3 Users have
developed other strategies more favorable to their opera-
tion for assigning events into the classes. The user layer
can request the application layer to poll for class 1, 2, or 3
events or any combination of them.
2.3.1 Variations
DNP3 has provisions for representing data in different
formats. Examination of analog data formats is helpful to
understand the flexibility of DNP3. Static, present value,
analog data can be represented by variation numbers as fol-
lows:
1. A 32-bit integer value with flag;
2. A 16-bit integer value with flag;
3. A 32-bit integer value;
4. A 16-bit integer value;
5. A 32-bit floating point value with flag; and
6. A 64-bit floating point value with flag.
ote:N The flag referred to is a single octet with bit fields
indicating whether the source is on-line, the data
source restarted, communications are lost with a
downstream source, the data is forced and the value
is over range.
Not all DNP3 devices can transmit or interpret all six varia-
tions. Later, DNP3 levels are discussed, but for now, suffice
it to say that DNP3 devices must be able to transmit the
simplest variations so that any receiver can interpret the
contents.
Event analog data can be represented by these variations:
1. A 32-bit integer value with flag;
2. A 16-bit integer value with flag;
3. A 32-bit integer value with flag and event time;
4. A 16-bit integer value with flag and event time;
5. A 32-bit floating point value with flag;
6. A 64-bit floating point value with flag;
7. A 32-bit floating point value with flag and event time;
and
8. A 64-bit floating point value with flag and event time.
The flag has the same bit fields as for the static variations.
2.3.2 Group
It appears by looking at the above variations that variation 1
and 2 analog events cannot be differentiated from variation
1 and 2 static analog values. DNP3 solves this predica-
ment by assigning group numbers. Static analog values are
assigned as group 30, and event analog values are assigned
as group 32. Static analog values, group 30, can be format-
ted in one of 6 variations, and event analog values, group
32, can be formatted in one of 8 variations.
When a DNP3 outstation transmits a message containing
response data, the message identifies the group number
and variation of every value within the message. Group and
variation numbers are also assigned for counters, binary
inputs, controls and analog outputs. In fact, all valid data
types and formats in DNP3 are identified by group and
variation numbers. Defining the allowable groups and varia-
tions helps DNP3 assure interoperability between devices.
DNP3’s basic documentation contains a library of valid
groups and their variations.
2.3.3 Objects
When data from an index is transmitted across the wire,
the sender must suitably encode the information to enable
a receiving device to parse and properly interpret this data.
The bits and bytes for each index appearing in the mes-
sage are called an object. That is, objects in the message
are the encoded representation of the data from a point, or
other structure, and the object format depends upon which
group and variation number are chosen.

7
2. DNP3 Protocol Primer
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
2.3.4 Reading Data
The master’s user layer formulates its request for data from
the outstation by telling the application layer what function
to perform, such as reading, and by specifying the data
types it wants from the outstation. The request can specify
how many objects it wants or it can specify specific objects
or a range of objects from index number X through index
number Y. The application layer then passes the request
down through the transport layer to the link layer that, in
turn, sends the message to the outstation. The link layer
at the outstation checks the frames for errors and passes
them up to the transport layer where the complete mes-
sage is assembled in the outstation’s application layer. The
application layer then tells its user layer which groups and
variations were requested.
Responses work similarly, in that the outstation’s user layer
fetches the desired data and presents it to the application
layer that, in turn, uses the group and variation numbers to
format user layer data into objects. Data is then passed
downward, across the communication channel and upward
to the master’s application layer. Here the data objects are
then presented to the master’s user layer.
2.3.5 Other Functions
Reading data was briefly described in Section 2.3.4, but
DNP3 software is designed to handle other functions. For
one, the master can set the time in the outstation. The
master can transmit freeze accumulator requests, and it
can transmit requests for control operations and setting of
analog output values using select-before-operate or direct-
operate sequences.
2.4 Unsolicited Responses
One area that has not been covered yet is transmission of
unsolicited messages. This is a mode of operating where
the outstation spontaneously transmits a response without
having received a specific request for the data. Not all out-
stations have this capability. This mode is useful when the
system has many outstations and the master requires noti-
fication as soon as possible after a change occurs. Rather
than waiting for a master station polling cycle to get around
to it, the outstation simply transmits the change.
Before configuring a system for unsolicited messages,
a few basics need to be considered. First, spontaneous
transmissions should generally occur infrequently, other-
wise, too much contention can occur, and controlling media
access via master station polling would be better. The sec-
ond basic issue is that the outstation should have some way
of knowing whether it can transmit without stepping on
another outstation’s message. DNP3 leaves specification of
algorithms to the system implementer.
2.5 Implementation Levels
One last area of discussion involves implementation levels.
The DNP3 organization recognizes that supporting every
feature of DNP3 is not necessary for every device. Some
devices are limited in memory and speed and do not need
specific features, while other devices must have the more
advanced features to accomplish their task. DNP3 orga-
nizes complexity into three levels. At the lowest level, level
1, only very basic functions must be provided and all others
are optional. Level 2 handles more functions, groups, and
variations, and level 3 is even more sophisticated. Within
each level, only certain combinations of request formats and
response formats are required. This was done to limit soft-
ware code in masters and outstations while still assuring
interoperability.
2.6 Summary
It should be apparent by now that DNP3 is a protocol that
fits well into the data acquisition world. It transports data
as generic values, it has a rich set of functions, and it was
designed to work in a wide area communications network.
The standardized approach of groups and variations, and
link, transport and application layers, plus public availability
makes DNP3 a protocol to be regarded.

8
3. DNP Device Profile
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
3. DNP Device Profile
DNP V3.0
DEVICE PROFILE DOCUMENT
This document must be accompanied by a table having the following headings:
Object Group Request Funcon Codes Response Funcon Codes
Object Variaon Request Qualifiers Response Qualifiers
Object Name (oponal)
Vendor Name: Eaton
Device Name: Power Expert Meter 4k/6k/8k
Highest DNP Level Supported:
For Requests : Level 2
For Responses : Level 2
Device Funcon:
Master
Slave
Notable objects, funcons, and/or qualifiers supported in addion to the Highest DNP Levels Supported.
For stac (non-change-event) object requests, request qualifier codes 07 and 08 (limited quanty), and 17
and 28 (index) are supported.
16-
16-bit and 32-bit Analog Change Events with Time are supported.
Floang Point Analog Output Status and Output Block Objects 40 are supported.
The read funcon code for Object 50 (Time and Date), variaon 1, is supported.
Maximum Data Link Frame Size (octets):
Transmied: 292
Received : 292
Maximum Applicaon Fragment Size (octets):
Transmied: Configurable up-to 2048
Received : 2048
Maximum Data Link Re-tries:
 None
 Fixed at ____

Configurable from 0 to 15
Maximum Applicaon Layer Re-tries:
 None
 Configurable


9
3. DNP Device Profile
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
Requires Data Link Layer Confirmaon:
 Never
 Always
 Somemes
 Configurable as:
When reporng Event Data.
When sending mul-fragment responses.
Requires Applicaon Layer Confirmaon:
 Never
 Always
 When reporng Event Data
 When sending mul-fragment responses
 Somemes
 Configurable as: “Only when reporng Event Data” or “When reporng event data and mul
fragment messages”.
Timeouts while waing for:
Data Link Confirm : None Fixed at ____ Variable Configurable.
Complete Appl. Fragment : None Fixed at ____ Variable Configurable.
Applicaon Confirm : None Fixed at 10 Sec Variable Configurable.
Complete Appl. Response : None Fixed at ____ Variable Configurable.
Others:

Transmission Delay, configurable

Select/Operate Arm Timeout, configurable 0 sec to 30 sec

Need Time Interval, configurable 1 sec to 86400 sec (1 day)

Data Link Confirm Timeout, configurable 0.1 sec to 30 sec

Binary Change Event Scan Period, fixed at 1 sec

Analog Change Event Scan Period, fixed at 1 sec
Counter Change Event Scan Period, fixed at 1 sec

Frozen Counter Change Event Scan Period, fixed at 1 sec







10
3. DNP Device Profile
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
Sends/Executes Control Operaons:
Reports Binary Input Change Events when no
specific variaon requested:
 Never
 Only me-tagged
 Only non-me-tagged
 Configurable to send both, one or the
other
Reports me-tagged Binary Input Change
Events when no specific variaon requested:
 Never
 Binary Input Change With Time
 Binary Input Change With Relave
Time
 Configurable to Binary Input Change
With Time and Binary Input Change With Relave Time
Sends Unsolicited Responses:
 Never
 Configurable
 Only certain objects
 Somemes
 ENABLE/DISABLE UNSOLICITED
Sends Stac Data in Unsolicited Responses:
 Never
 When Device Restarts
 When Status Flags Change
No other opons are permied.


11
3. DNP Device Profile
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
Default Counter Object/Variaon:
 No Counters Reported
 Configurable
 Default
Object
Variaon
 Point-by-point list aached
Counters Roll Over at:
 No Counters Reported
 Configurable
 16 Bits
 32 Bits
 Other Value: _____
 Point-by-point list aached
Sends Mul-Fragment Responses:
 Yes
 No
 Configurable as: “Always” or “When reporng Event Data”
Sequenal File Transfer Support:
Append File Mode : Yes No
Custom Status Code Strings : Yes No
Permissions Field : Yes No
File Events Assigned to Class : Yes No
File Events Send Immediately: Yes No
Mulple Blocks in a Fragment: Yes No
Max Number of Files Open : 0

12
4. Implementation Table
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
4. Implementation Table
The following table identifies which object variations, func-
tion codes, and qualifiers the PXM 4/6/8 K meter supports
in both request messages and in response messages.
For static (non-change-event) objects, requests sent with
qualifiers 00, 01, 06, 07, or 08, will be responded with quali-
fiers 00 or 01. Requests sent with qualifiers 17 or 28 will
be responded with qualifiers 17 or 28. For change-event
objects, qualifiers 17 or 28 are always responded.
Table 1. Object Variations, Function Codes, and Qualifiers.
Object
REQUEST
Master May Issue
Outstation Must Parse
RESPONSE
Master Must Parse
Outstation May Issue
Object
Number
Variation
Number Description
Function Codes
(dec)
Qualifier Codes
(hex)
Function Codes
(dec) Qualifier Codes (hex)
1 0 Binary Input – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
11 (default –
see note 1)
Binary Input 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
1 2 Binary Input with Status 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
2 0 Binary Input Change – Any Variation 1 (read) 06 (no range, or all)
07, 08 (limited qty)
2 1 Binary Input Change without Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
2 2 Binary Input Change with Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
10 0 Binary Output – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 27, 28 (index)
10 1 Binary Output 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 27, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 1)
10 2 (default –
see note 1)
Binary Output Status 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
12 1 Control Relay Output Block 3 (select)
4 (operate)
5 (direct op)
6 (dir. op, noack)
17, 28 (index) 129 (response) Echo of request
20 0 Binary Counter – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
7 (freeze)
8 (freeze no ack)
00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)

13
4. Implementation Table
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
Object
REQUEST
Master May Issue
Outstation Must Parse
RESPONSE
Master Must Parse
Outstation May Issue
Object
Number
Variation
Number Description
Function Codes
(dec)
Qualifier Codes
(hex)
Function Codes
(dec) Qualifier Codes (hex)
20 1 32-Bit Binary Counter (with Flag) 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
20 2 16-Bit Binary Counter (with Flag) 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
20 5 32-Bit Binary Counter without Flag 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
20 6 16-Bit Binary Counter without Flag 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
21 0 Frozen Counter – Any Variation 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
21 1 32-Bit Frozen Counter (with Flag) 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
21 2 16-Bit Frozen Counter (with Flag) 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
21 5 32-Bit Frozen Counter with Time Of
Freeze
1 (read) 00, 01 (start-stop)
06 (no range, or all)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 1)
21 6 16-Bit Frozen Counter with Time Of
Freeze
1 (read) 00, 01 (start-stop)
06 (no range, or all)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 1)
21 9 (default –
see note 1)
32-Bit Frozen Counter without Flag 1 (read) 00, 01 (start-stop)
06 (no range, or all)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
21 10 16-Bit Frozen Counter without Flag 1 (read) 00, 01 (start-stop)
06 (no range, or all)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
22 0 Counter Change Event – Any Variation 1 (read) 06 (no range, or all)
07, 08 (limited qty)
22 1 (default –
see note 1)
32-Bit Counter Change Event without
Time
1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
22 2 16-Bit Counter Change Event without
Time
1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
22 5 32-Bit Counter Change Event with Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
22 6 16-Bit Counter Change Event with Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)

14
4. Implementation Table
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
Object
REQUEST
Master May Issue
Outstation Must Parse
RESPONSE
Master Must Parse
Outstation May Issue
Object
Number
Variation
Number Description
Function Codes
(dec)
Qualifier Codes
(hex)
Function Codes
(dec) Qualifier Codes (hex)
23 0 Frozen Counter Event (Variation 0 is
used to request default variation)
1 (read) 06 (no range, or all)
07, 08 (limited qty)
23 1 (default –
see note 1)
32-Bit Frozen Counter Event 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
23 2 16-Bit Frozen Counter Event 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
23 5 32-Bit Frozen Counter Event with Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
23 6 16-Bit Frozen Counter Event with Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
30 0 Analog Input - Any Variation 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
30 1 32-Bit Analog Input 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
30 2 16-Bit Analog Input 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
30 3 (default –
see note 1)
32-Bit Analog Input without Flag 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
30 4 16-Bit Analog Input without Flag 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
30 5 Short floating point 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
32 0 Analog Change Event – Any Variation 1 (read) 06 (no range, or all)
07, 08 (limited qty)
32 1 (default –
see note 1)
32-Bit Analog Change Event without
Time
1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
32 2 16-Bit Analog Change Event without
Time
1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
32 3 32-Bit Analog Change Event with Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
32 4 16-Bit Analog Change Event with Time 1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
32 5 Short floating point Analog Change
Event without Time
1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)
32 7 Short floating point Analog Change
Event with Time
1 (read) 06 (no range, or all)
07, 08 (limited qty)
129 (response) 17, 28 (index)

15
4. Implementation Table
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
Object
REQUEST
Master May Issue
Outstation Must Parse
RESPONSE
Master Must Parse
Outstation May Issue
Object
Number
Variation
Number Description
Function Codes
(dec)
Qualifier Codes
(hex)
Function Codes
(dec) Qualifier Codes (hex)
34 0 Analog Input Dead band (Variation 0 is
used to request default variation)
1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
34 1 16 bit Analog Input Dead band 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
2 (write) 00, 01 (start-stop)
07, 08 (limited qty)
17, 28 (index)
34 2 (default –
see note 1)
32 bit Analog Input Deadband 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
2 (write) 00, 01 (start-stop)
07, 08 (limited qty)
17, 28 (index)
40 0 Analog Output Status 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
40 1 32-Bit Analog Output Status 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
40 2 (default –
see note 1
16-Bit Analog Output Status 1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
40 3 Short floating point Analog Output
Status
1 (read) 00, 01 (start-stop)
06 (no range, or all)
07, 08 (limited qty)
17, 28 (index)
129 (response) 00, 01 (start-stop)
17, 28 (index –see
note 2)
50 0 Time and Date
50 1 (default –
see note 1
Time and Date 1 (read) 07, (limited qty = 1) 129 (response) 07 (limited qty = 1)
2 (write) 07, (limited qty = 1)
60 1 Class 0 Data 1 (read) 06 (no range, or all)
60 2 Class 1 Data 1 (read) 06 (no range, or all)
07, 08 (limited qty)
60 3 Class 2 Data 1 (read) 06 (no range, or all)
07, 08 (limited qty)
60 4 Class 3 Data 1 (read) 06 (no range, or all)
07, 08 (limited qty)
80 1 Internal Indications 1 (read) 00, 01 (start-stop) 129 (response) 00, 01 (start-stop)
Note 1: A default variation refers to the variation responded when variation 0 is requested and/or in class 0, 1, 2, or 3 scans. Default variations are configurable; however, default set-
tings for the configuration parameters are indicated in the table above.
Note 2: For static (non-change-event) objects, qualifiers 17 or 28 are only responded when a request is sent with qualifiers 17 or 28, respectively. Otherwise, static object requests
sent with qualifiers 00, 01, 06, 07, or 08, will be responded with qualifiers 00 or 01. (For change-event objects, qualifiers 17 or 28 are always responded.)
Note 3: Writes of Internal Indications are only supported for index 4 or 7 (Need Time IIN1-4 or Restart IIN1-7)

16
5. DNP3 Ethernet Communication Setup Configuration Utility
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
5. DNP3 Ethernet Communication Setup
Configuration Utility
It is necessary to configure DNP parameters and DNP data-
base to match specific requirements/needs of an applica-
tion. A simple, easy to use web based interface is provided
to configure DNP parameters and database as per user
requirement. Installer can get connected to meter by enter-
ing IP address of meter in a web browser. No separate
software installation is required to configure DNP3 stack.
Below sections explain each steps of DNP3 configuration in
detail.
Figure 5. DNP3 Setup Page.
DNP3 configuration setup is located at Setup -> Meter
Setup & commissioning -> Communication -> Ethernet /
LAN Setup -> DNP3 Setup.
DNP3 setup is divided in subpages as per category
explained below.

17
5. DNP3 Ethernet Communication Setup Configuration Utility
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
5.1 DNP3 Node Identification
Figure 6. DNP3 Node Identification Page.
If the User wishes to change parameters’ then the User
first needs to press “Edit” option and “Authenticate” self to
avoid unauthorized access. After Authentication, the param-
eters shall be editable as shown in Figure 7.
Figure 7. DNP3 Setup Edit Page.

18
5. DNP3 Ethernet Communication Setup Configuration Utility
PXM 4/6/8K DNP3 Ethernet Communications User Manual MN150005EN January 2017 www.eaton.com
The User can set three parameters:
1. DNP Master Address
It is the address of DNP master with which the PXM
meter shall exchange DNP3 data. This address shall be
validated by PXM meter and responses shall be sent
ONLY if a request is sent by the DNP master with this
address. This address shall be used in DNP3 source
field in DNP frames from master to slave.
2. PXM Meter Address
This is the DNP3 address with which the DNP3 mas-
ter device shall identify the specific PXM meter in the
DNP network. This address shall be used in the DNP3
destination field in DNP frames from master to slave.
The PXM meter shall match the destination address in
the received frame and the User assigned PXM meter
address. If a match is found, then the frame shall be
processed further.
3. User Assigned ID/Code
The User can assign a name to the PXM meter for
identification. This helps in easy identification of the
PXM meter location by the user instead of remember-
ing the meter by the DNP3 address.
ote:N PXM DNP3 implementation uses port 20,000 for its
communication. This port is not configurable and is
fixed. To communicate with PXM meter over TCP/IP
DNP, the master must use 20,000 as port number.
5.2 Global Settings
When this page is selected, the User can configure the fol-
lowing parameters.
1. DNP Select Operation Timeout
This parameter is used for Select-Before-Operate (SBO)
operation on digital outputs (relays). If the SBO mode is
used by the master to operate meter’s digital outputs, then
“DNP Select operation timeout” parameter is used. In this
particular operation, the DNP3 master first sends a select
request for particular digital output. When this request is
received, the PXM meter starts a timer for duration speci-
fied by “DNP Select operation timeout” parameter. If the
operate command is received from DNP3 master before
this timer elapses, then that digital output is operated as
per the master request.
If this timer expires before the operate request is received,
then the operate request is rejected by PXM meter.
ote:N It is necessary that the digital I/O card is installed in
the PXM meter to use this option. SBO operation is
supported only on relays R1, R2, and R3 and these
relays should be selected in the DNP input output
section as explained later in this document.
2. DNP Default Object X Variation ( X =1, 2, 10, 20, 21, 22,
23, 30, 32, 34, 40)
The DNP3 master may send requests to get the DNP3
slave data (PXM data) objects with variation 0. In this
case, the meter can send responses with the default
variation. It is possible to configure object wise default
variation for the PXM meter on web page. The User
can select the default variation from the drop down list
given against each object.