Experion HS

Release 511

DNP3 Interface Reference

EHDOC-XX31-en-511A
August 2019
 DISCLAIMER
This document contains Honeywell proprietary information. Information
contained herein is to be used solely for the purpose submitted, and no part of
this document or its contents shall be reproduced, published, or disclosed to a
third party without the express permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate,
Honeywell disclaims the implied warranties of merchantability and fitness for
a purpose and makes no express warranties except as may be stated in its
written agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or
consequential damages. The information and specifications in this document
are subject to change without notice.
Copyright 2019 - Honeywell International Sàrl

2
 Contents

CONTENTS
Contents 3
Chapter 1 - Planning considerations for DNP3 controllers 5
Devices supported by the DNP3 interface 6
Other documentation for DNP3 6
DNP3-specific terms 6
Architectures for DNP3 7
Communication settings for DNP3 8
Chapter 2 - DNP3 channel and controller reference 9
Main properties for a DNP3 channel 9
Port properties for a DNP3 channel 11
Redundant port properties for a DNP3 channel 16
Main properties for a DNP3 controller 17
DNP3 controller levels 22
Classes, unsolicited responses, and time synchronization properties for a
DNP3 controller 24
Timeouts properties for a DNP3 controller 27
Control properties for a DNP3 controller 30
Optimizing DNP3 scanning performance 31
Chapter 3 - DNP3 points reference 33
Defining a DNP3 address for a point parameter 33
Address Syntax 33
Analog point 35
Status point 35
Accumulator point 35
Configuring Integration with Honeywell RTU2020 39
Using ControlEdge Builder for Experion Integration 39

3
Contents

Main properties for an RTU2020 DNP3 controller 41

Defining Point Parameter Address using Address Browser 41

Chapter 4 - RTU2020 EFM meter templates reference 43

Main properties for an RTU2020 meter template 43
Interval Log properties for an RTU2020 meter template 43
Configuration Log properties for an RTU2020 meter template 44
Daily Log properties for an RTU2020 meter template 44
Alarm and Event properties for an RTU2020 meter template 44
Data Export properties for an RTU2020 meter template 45
Chapter 5 - Troubleshooting DNP3 issues 47
Testing DNP3 communications with the server 47
Troubleshooting DNP3 scanning errors 47
Troubleshooting Experion RTU2020 mismatch alarm 48
Notices 51

4
CHAPTER

1 PLANNING CONSIDERATIONS FOR

DNP3 CONTROLLERS
This reference provides the information you need to set up, configure, and
test DNP3 controller communications with the server.

Revision history
Revision Date Description

A August 2019 Initial release of document.

How to use this guide

The following table lists the steps for connecting and configuring a DNP3
controller. Complete each step before commencing the next step.

Steps: Go to

Connect and set up the DNP3 controller according to the Architectures for DNP3
controller's user manual's instructions
Use Quick Builder to define channels l DNP3 channel and
controller reference
l Quick Builder User’s
Guide
Use Quick Builder to define controllers l DNP3 channel and
controller reference
l Quick Builder User’s
Guide
Enable channels and test communications Testing DNP3
communications with the
server
Troubleshoot communication errors Troubleshooting DNP3
scanning errors
Use Quick Builder to define points Defining a DNP3 address for
a point parameter

5
Chapter 1 - Planning considerations for DNP3 controllers

Devices supported by the DNP3 interface

The server supports the Level 1, 2, and 3 subsets of the DNP3 V3.00
Application Layer Protocol. In addition, the writing of Analog Input Deadband
Objects in also supported, as per the Level 4 subset.
The server supports integration with RTU2020 controllers:

n For information about how to integrate with RTU2020 R120 and R140,
see this guide.
n For information about how to integrate with ControlEdge RTU R150 and
later, see the ControlEdge RTU Interface Reference.

NOTE: The RTU2020 controller name has been changed to

ControlEdge RTU from R140. The RTU Builder name has been
changed to ControlEdge Builder from R140.

Other documentation for DNP3

The latest DNP3 specification documents should be studied before
configuring a controller. You can download these documents from the
Document Library section of http://www.dnp.org.
The following documents complement this guide. You can download
Honeywell documentation from the
http://www.honeywellprocess.com/support website.

n ControlEdge Builder User’s Guide

n ControlEdge RTU Interface Reference
n Quick Builder User’s Guide
n Server and Client Configuration Guide
n Supplementary Installation Tasks Guide

DNP3-specific terms
DNP3
Distributed Network Protocol, Version 3.
DNP3-LX
When applied to a device indicates that the device implements DNP3 Subnet
Level X (1, 2, or 3).
Master
A device that initiates requests to gather data or perform controls using

6
 Chapter 1 - Planning considerations for DNP3 controllers

DNP3.
Slave
A device that gathers data or performs control operations in response to
DNP3 requests from a Master, and sends response messages in return. A
slave device may also generate DNP3 unsolicited responses.

Architectures for DNP3

Connect DNP3 controllers to the server in accordance with the appropriate
architectural diagram.

ATTENTION: Configuring redundant ports, redundant controllers

and/or redundant servers can be complex and can vary depending on
the controller used and the system architecture. If you have
redundancy-related problems, contact your local Honeywell
representative for assistance.

DNP3 point-to-point serial architecture

Figure 1-1: DNP3 point-to-point serial architecture

Server Controller

DNP controller
DNP master interface
DNP slave interface
RS-232

DNP3 redundant server serial architecture using a

terminal server

Figure 1-2: DNP3 redundant server serial architecture using a terminal server

7
Chapter 1 - Planning considerations for DNP3 controllers

Server A Controller
Terminal Server
DNP controller
DNP master interface
DNP slave interface

Network RS-232

DNP master interface

Server B

DNP3 redundant server network architecture

Figure 1-3: DNP3 redundant server network architecture

Controller
Server A
DNP controller

DNP master interface DNP slave interface

TCP/IP or UDP/IP

DNP master interface

Server B

Communication settings for DNP3

Serial communications settings should be the same as the terminal server or
server serial port, depending on which architecture is being used.
Ethernet communications settings should be the same as those used by the
server.

8
CHAPTER

2 DNP3 CHANNEL AND

CONTROLLER REFERENCE
This section describes the configuration and addressing information specific
to DNP3 channels and controllers.

Main properties for a DNP3 channel

The Main tab defines the basic properties for a DNP3 channel.
For information about how to create a channel, see "Building controllers and
channels" in the Quick Builder User’s Guide.

ATTENTION: Several of the settings described in the table are

marked with a (Sn ) or (Un ), where n is a number. To aid in the
troubleshooting, error messages in the server log associated with one
of these particular settings also contain the corresponding (Sn ) or (Un )
text.

Property Description

Name The unique name of the channel. A maximum of 10 alphanumeric characters

(no spaces or double quotes).

NOTE: In Station displays, underscore characters ( _ ) appear as

spaces.

Description (Optional) A description of the channel. A maximum of 132 alphanumeric

characters, including spaces.
Associated The Tag Name of the Asset to be associated with the controller.
Asset
Marginal The communications alarm marginal limit at which the channel is declared to be
Alarm Limit marginal. When this limit is reached, a high priority alarm is generated. To
change the priority of the alarm system wide, see the topic titled "Configuring
system alarm priorities" in the Server and Client Configuration Guide. To
change the priority of the alarm for one channel, see the topic titled "About
configuring custom system alarm priorities for an individual channel or
controller" in the Server and Client Configuration Guide.

9
Chapter 2 - DNP3 channel and controller reference

Property Description
A channel barometer monitors the total number of requests and the number of
times the controller did not respond or response was incorrect. The barometer
increments by two or more, depending on the error, and decrements for each
good call.

To calculate an acceptable marginal alarm limit, use the formula: Square root
of the number of controllers on the channel × Marginal Alarm Limit defined on
those controllers (Normally, you specify the same value for all controllers on a
channel).

For example, if there are 9 controllers on the channel and their Marginal Alarm
Limit is set to 25 , the value would be 3 (which is the square root of 9) × 25 = 75 .
Fail Alarm The communications alarm fail limit at which the channel is declared to have
Limit failed. When this barometer limit is reached, an urgent alarm is generated. To
change the priority of the alarm system wide, see the topic titled "Configuring
system alarm priorities" in the Server and Client Configuration Guide. To
change the priority of the alarm for one channel, see the topic titled "About
configuring custom system alarm priorities for an individual channel or
controller" in the Server and Client Configuration Guide.

Set this to double the value specified for the channel Marginal Alarm Limit.
Master DNP3 data link address of the server on the DNP3 channel. Valid range is from
Address for 0–65,519, and must be unique on the channel.
ServerA
In a redundant server system, Server A uses this setting for its DNP3 data link
address.
Master In a redundant server system, Server B uses this setting for its DNP3 data link
Address for address.
ServerB
Daemon Period in milliseconds that the DNP3 daemon looks for data from the channel
Period (serial only) and progress any outstanding requests (serial and Ethernet). Note
that the DNP3 daemon processes Ethernet data as soon as it arrives. Valid
range from 5 to 30,000. Default value is 50 .
Read time (Only applicable to Serial and TerminalServer port.)
per byte
(S0) The time in milliseconds that the DNP3 daemon allows to read a single byte.
Valid range from 1 to 1,000 milliseconds. This should be set in accordance with
the underlying serial communications speed. The default value is 40 .
Daemon Period in seconds that the DNP3 daemon keeps data from the device for the
Poll Timeout DNP3 scan task before deleting it.
(U0)

10
 Chapter 2 - DNP3 channel and controller reference

Property Description
Valid range from 1 to 300 seconds. The default value is 60 .
Ethernet The time (in seconds) that the server waits when trying to establish an Ethernet
Connect connection to the device. Valid range is 1–999 seconds. The default value is 1 .
Timeout
Item Type The type of channel specified when this item was created.
Last The date and time the channel properties were modified.
Modified
Last The date and time the channel was last downloaded to the server.
Downloaded
Item The unique item number currently assigned to this channel, in the format
Number CHNcccc, where cccc is the channel number.

You can change the Item Number if you need to match your current server
database configuration. The number must be between 0001 and the maximum
number of channels allowed for your system. For more information about
setting the maximum value, see the topic titled "Adjusting sizing of non-licensed
items" in the Supplementary Installation Tasks Guide. Note that the maximum
number of channels that may be used in a system is defined in the Experion
specification for that Experion release, This number is likely to be less than the
maximum number that can be configured in the database as shown in
"Adjusting sizing of non-licensed items."

Port properties for a DNP3 channel

The Port tab defines the communication-related properties for a channel. The
Port Type for a DNP3 channel can be:

n LANVendor . An Ethernet communications link using TCP/IP or UDP. See

"LANVendor port properties" on the next page.
n Serial. A serial communications interface, such as RS-232. See "Serial
port properties" on page 13.
n TerminalServer . A communications link that enables controllers with a
serial interface to be connected to a LAN. See "Terminal server port
properties" on page 15.

NOTE: RTU2020 supports the LANVendor port type only.

11
Chapter 2 - DNP3 channel and controller reference

LANVendor port properties

Property Description

Half If selected, only one request is outstanding on the port at any instance. When a
duplex request is in progress, subsequent requests are queued until the current request
polling is complete or has timed out. This setting is useful if there are multiple controllers
on the channel and there is at least a part of the communications pathway
between the server and the controller that has ineffective flow control. If
unsolicited responses are enabled, unsolicited responses from controllers are
still confirmed when in this mode.

If not selected, only one request per controller is outstanding on the port at any
instance. When a request is in progress for a controller, subsequent requests for
that controller are queued until the current request is complete or has timed out. If
there are multiple controllers on the channel this allows multiple requests to be
underway at the same time.

By default this option is not selected .

Note that regardless of this setting, queued requests are sent out in the first in,
first out order; the exception is control requests, which are always processed
before other types of requests such as data acquisition, diagnostics, class polling
and time synchronization.
Max. Each channel's link consists of a daemon process which may run out of
Daemon transaction table slots if the link is overloaded, or if there are large numbers of
Slots controllers on the link.

The number of transaction table slots in the daemon may be modified by using
this setting. The range is from 256 to 32767 . The default value is 32767 .
Diagnostic The period in seconds, for performing a diagnostic scan. Valid range from 5 to
Period 3,600 . The default value is 60 .

Protocol TCP or UDP.

RTU2020 supports TCP only.

Each UDP channel port built on a server must be built with a different UDP port
number (the default DNP3 port number is 20000). You can select a port number
for the channel link and then assign the port number for each controller on this
channel link with that port number. The port numbers on the physical controller
will also need to match this setting.

Only one UDP channel can be built per system and only one redundant link can
specify UDP as the transport protocol. If a second UDP link or channel is built or
if another application on the same system is using UDP port 20000, a Winsock
error 10049 will be reported in the log.

12
 Chapter 2 - DNP3 channel and controller reference

Property Description

Individual If selected, the DNP3 channel will make an individual TCP/IP connection for
TCP/IP each DNP3 controller, even if controllers in the channel share the same IP
connection address and port settings. This is recommended when the server is to connect
per directly to the controllers or when an intermediate device such as a gateway can
controller support an individual TCP/IP connection per controller.

If not selected, the DNP3 channel will share the connection for DNP3 controllers
that have the same IP address and port settings. This is recommended when an
intermediate device such as a concentrator can only support one TCP/IP
connection with the server for all controllers.

The default value is not selected .

Serial port properties

ATTENTION: The Serial Port settings must match the settings on

your communication devices.

Property Description

Half duplex If selected, only one request is outstanding on the port at any instance. All logical
polling controllers that are active on the channel are given equal 'round-robin' access to
the port. When a request is in progress, subsequent requests are queued until
the current request is complete or has timed out. This setting is useful if there
are multiple controllers on the channel and there is at least a part of the
communications pathway between the server and the controller that has
ineffective flow control. If this setting is used, it is recommended that unsolicited
responses be disabled on the controller.

If not selected, only one request per controller is outstanding on the port at any
instance. When a request is in progress for a controller, subsequent requests for
that controller are queued until the current request is complete or has timed out.
If there are multiple controllers on the channel this allows multiple requests to be
underway at the same time.

By default this option is not selected .

Note that regardless of this setting, queued requests are sent out in first in/first
out order; the exception is control requests, which are always processed before
other types of requests such as data acquisition, diagnostics, class polling and
time synchronization.
Max. Each channel's link consists of a daemon process which may run out of

13
Chapter 2 - DNP3 channel and controller reference

Property Description
Daemon transaction table slots if the link is overloaded, or if there are large numbers of
Slots controllers on the link.

The number of transaction table slots in the daemon may be modified by using
this setting. The range is from 256 to 32767 .

The default value is 32767 .

Diagnostic The period in seconds, for performing a diagnostic scan. Valid range is from 5 to
Period 3,600 . The default value is 60 .

Serial Port The device name of the serial port.

Name
The default value is COM1 .
Baud rate The number of data bits per second.

The default value is 9600 .

Number of The number of data bits used for transmission.
Data Bits
The default value is 8 .
Stop Bits The number of stop bits used for transmission.

The default value is 1 .

Parity Defines parity verification of each character and must match configuration on
the end device.

The default value is NONE.

Checksum Set to NONE (default).

Each block in a DNP3 data link frame has a 16-bit CRC appended to it. The
server handles this checksum by default in the data link layer.
XON/XOFF The type of XON/XOFF software flow control used to stop a receiver from being
overrun with messages from a sender. The types are:

l Input (useXON/XOFF to control the flow of data on the receive line)

l NONE (default)

l Output (use XON/XOFF to control the flow of data on the transmit line)

RS-232 These options are applicable to the RS-232 link:

l Enable RTS/CTS Flow Control. Select this if you want to use RTS/CTS for
flow control to stop a receiver from being overrun with messages from a

14
 Chapter 2 - DNP3 channel and controller reference

Property Description

sender.
l Detect DCD. Select this if the Data Carrier Detect communication status
line of the COM port requires monitoring (usually when using modem or
microwave linking). When selected, the communications fails if the
desired COM status line is not high—for example, on a dial-up link
connection for a modem.
l Detect DSR. Select this if the Data Set Ready communication status line
of the COM port requires monitoring (usually when using modem or
microwave linking). When selected, the communications fails if the
desired COM status is not achieved.
RS-485 These options are applicable to the RS-485 link:

l Enable Stallion RS-485 Half Duplex. Select if RS-232 to RS-485 is done

using a Stallion EasyConnection adapter.
l Echo (Required for Stallion RS-485 ports) . Select so that the server
expects the messages it sends to the port on the transmit line to be
echoed back on the receive line. Select for a Stallion EasyConnection
adapter or a Black Box converter.

Terminal server port properties

Property Description

Half If selected, only one request is outstanding on the port at any instance. When a
duplex request is in progress, subsequent requests are queued until the current request
polling is complete or has timed out. This setting is useful if there are multiple controllers
on the channel and there is at least a part of the communications pathway
between the server and the controller that has ineffective flow control. If
unsolicited responses are enabled, unsolicited responses from controllers are still
confirmed when in this mode.

If not selected, only one request per controller is outstanding on the port at any
instance. When a request is in progress for a controller, subsequent requests for
that controller are queued until the current request is complete or has timed out. If
there are multiple controllers on the channel this allows multiple requests to be
underway at the same time.

By default this option is not selected .

Note that regardless of this setting, queued requests are sent out in first in/first

15
Chapter 2 - DNP3 channel and controller reference

Property Description

out order; the exception is control requests, which are always processed before
other types of requests such as data acquisition, diagnostics, class polling and
time synchronization.
Max. Each channel's link consists of a daemon process which may run out of
Daemon transaction table slots if the link is overloaded, or if there are large numbers of
Slots controllers on the link.

The number of transaction table slots in the daemon may be modified by using
this setting. The range is from 256 to 32767 . The default value is 32767 .
Diagnostic The period in seconds, for performing a diagnostic scan. Valid range is from 5 to
Period 3,600 . The default value is 60 .

Host The host name of the terminal server to which the channel is connected. You can
Name specify either a TCP host name or an IP address, but it must match the TCP host
name used when you installed and internally configured the terminal server.
Terminal The port number of the terminal server to which the channel is connected.
Server
TCP Port
No.
Idle The time, in seconds, the channel waits for a successful connection to the server
Timeout before closing the connection.

A value of 0 indicates that the connection is never closed.

The Idle Timeout should be set to a number greater than the fastest polling period
on the channel.

This also applies to the Idle Timeout configured in the terminal server.

The default value is 180 sec.

Checksum Set to NONE (default).

Each block in a DNP3 data link frame has a 16-bit CRC appended to it. The
server handles this checksum by default in the data link layer.

Redundant port properties for a DNP3 channel

The Redundant Port tab defines the communication-related properties for a
redundant DNP3 channel.
The Port Type selected on this tab must be the same as the port type selected
on the Port tab.

16
 Chapter 2 - DNP3 channel and controller reference

NOTE: RTU2020 supports the RedundantLANVendor port type only.

Property Description

Port Type l None (Default)

l RedundantLANVendor
l RedundantSerial
l RedundantTerminalServer

Redundant communications relies on the controller functioning as follows:

1. Listening and responding to both ports as requested.

2. Simultaneously sending unsolicited data down both links or only sending
unsolicited data down the link that most recently was used for solicited
communications.

ATTENTION: Configuring redundant ports and/or redundant servers

can be complex and can vary from controller to controller. If you
encounter problems implementing a redundant port, contact your local
Honeywell representative.

Main properties for a DNP3 controller

The Main tab defines the basic properties for a DNP3 contoller.
For information about how to create a controller, see the topic titled "Building
controllers and channels" in the Quick Builder User’s Guide.

Property Description

Name The unique name of the controller. A maximum of 10 alphanumeric characters

(no spaces or double quotes). Note: In Station displays, underscore
characters ( _ ) appear as spaces. For LAN–connected controllers, the name is
used to look up the IP address in the TCP/IP database if you do not specify an
IP Address property.
Description (Optional) A description of the controller. A maximum of 132 alphanumeric
characters, including spaces.
Associated The Tag Name of the Asset to be associated with the alarm group.
Asset
Channel The name of the channel on which the controller communicates with the

17
Chapter 2 - DNP3 channel and controller reference

Property Description
Name server.

ATTENTION: You must have already defined a channel for it to

appear in this list.

Marginal The communications alarm marginal limit at which the controller is declared to
Alarm Limit be marginal. When this limit is reached, a high priority alarm is generated. To
change the priority of the alarm system wide, see the topic titled "Configuring
system alarm priorities" in the Server and Client Configuration Guide. To
change the priority of the alarm for one channel, see the topic titled "About
configuring custom system alarm priorities for an individual channel or
controller" in the Server and Client Configuration Guide.

A controller barometer monitors the total number of requests and the number
of times the controller did not respond or response was incorrect. The
barometer increments by two or more, depending on the error, and
decrements for each good call.

The default value is 25 .

Fail Alarm The communications alarm fail limit at which the controller is declared to have
Limit failed. When this barometer limit is reached, an urgent alarm is generated. To
change the priority of the alarm system wide, see the topic titled "Configuring
system alarm priorities" in the Server and Client Configuration Guide. To
change the priority of the alarm for one channel, see the topic titled "About
configuring custom system alarm priorities for an individual channel or
controller" in the Server and Client Configuration Guide.

Set this to double the value specified for the controller Marginal Alarm Limit.

The default value is 50 .

Dynamic Select the Dynamic Scanning check box to enable dynamic scanning of all
Scanning point parameters on this controller. The default setting for this check box is
selected .

Fastest Scan Define the fastest possible scan period (in seconds) that dynamic scanning will
Period scan point parameters on this controller. The default is 15 seconds.

The dynamic scanning period does not affect the static scanning rate for a
parameter. For example, if the scanning rate for a parameter is 10 seconds,
and the dynamic scanning rate for the controller is 15 seconds, the parameter
will still be scanned at a period of 10 seconds.
Device DNP3 data link address of the controller on the DNP3 channel. The valid

18
 Chapter 2 - DNP3 channel and controller reference

Property Description

Address range is from 0 to 65,519 , and must be unique on the channel.

Level The controller level:

l 1
l 2
l 3
For more information about these levels, see "DNP3 controller levels" on
page 22.
Default Data Specifies the register size to be used when not explicitly specified in the Point
Size address. Either 16-bit or 32-bit. If you modify this option, and you want existing
points to use the modified value, then you must rebuild those points.
Enable SOE Must be set if time stamped binary inputs are to be treated as SOE (Sequence
of Events). By default this option is not selected .

If you select this option, you must also configure SOE on a point parameter
basis. See "Defining a DNP3 address for a point parameter" on page 33.
Enable If selected, the server sends out enable (Function code 20) and disable
Unsolicited (Function code 21) unsolicited message requests, dependent upon the
Message controller's Accept Unsolicited Messages setting. Some controllers may not
Control be able to correctly interpret these requests.

If not selected, the sending of unsolicited messages is entirely controlled by

the controller itself. This setting should not be selected if the physical controller
is configured to never send unsolicited responses.
Request If selected, all subsequent points that are built use the with status variation. By
Status with default this option is not selected .
Data
If this option is modified, and you want existing points to use the modified
value, then those points must be rebuilt.
Enable Select this if binary input change with time, analog change event with time,
History and counter change event with time objects are to be backfilled into history.
Backfill The change values are inserted into history snapshots as if they were read by
the server at the time of the change's timestamp.

For points that have history backfill configured:

l History averages are NOT re-averaged

19
Chapter 2 - DNP3 channel and controller reference

Property Description

l Any Status point PV or OP with non-consecutive addressed bits is not

recalculated
An alarm is raised if change data is lost due to an overflow in the controller's
event buffer or an overload of the history backfill task. The priority of this alarm
is defined in sysflg (file 8, record 1, word 494, bits 0-1). Set these two bits only
to 0 for a journal entry, 1 for low, 2 for high, and 3 for urgent alarm priority.

If you select this option, you must also:

l Enable the history backfill option on the server. You must also specify
the maximum number of days that history will be backfilled. See
"Configuring history backfill" in the Server and Client Configuration
Guide.
l Configure history backfill on a point parameter basis.
By default, this check box is not selected .
Separate If selected, you can configure separately for each link, the settings on the
Link B Classes, Unsol & Time Sync tab and the Timeouts tab in Quick Builder.
Configuration This is recommended if channel links have markedly different characteristics
(such as full or half duplex, speed, latency, error rates, etc.) and therefore
require different configurations. When selected, Quick Builder duplicates and
renames the Classes, Unsol & Time Sync tab and the Timeouts tab as
Classes, Unsol & Time Sync – Link A, Classes, Unsol & Time Sync –
Link B, Timeouts – Link A, and Timeouts – Link B.

If not selected, the settings on the Classes, Unsol & Time Sync tab and the
Timeouts tab will be used for each link.

If you have redundant links with the same characteristics you can clear this
check box and the same settings will be used for both links.
Write If selected, the DNP3 interface will write Analog Input deadbands to the
Deadbands controller. The physical controller must also support the writing of analog input
to Controller deadbands to be able to use this setting.

An Analog Input deadband setting on a DNP3 controller defines the absolute

amount that a value can change before it is considered significant and thus be
communicated back to the server as an Analog Input Change Event. The
deadband setting can be used to suppress insignificant small variations in
value. The deadband setting may also be useful in reducing the amount of
network used by the controller. When this is selected, the deadband for an
Analog Input is calculated from the point parameter's engineering range low
and high and its drift deadband percentage. Multiple point parameters built on

20
 Chapter 2 - DNP3 channel and controller reference

Property Description

the same Analog Input will result in the small deadband value being written to
the physical controller.

Care should be taken to ensure that all Analog Input addresses referenced in
point parameters actually exist on the physical controller so that write
deadband requests are not rejected.

By default, this check box is not selected .

Rewrite If selected, the DNP3 interface will write all Analog Input deadbands to the
Deadbands controller when the physical controller restarts. This may be required if the
upon controller resets its deadbands when it restarts. By default, this check box is
Controller not selected and is only available if the Write Deadbands to Controller check
Restart box is selected.
IP Address 1 (Only applicable to LANVendor port.)

If redundant ports are configured, this should be the IP address of the device
on link 1. If this is not specified, the controller name is used as the host name
with an A appended to it.

If redundant ports are not configured, this should be the IP address of the
device. If this is not specified, the controller name is used as the host name.
Port For TCP/IP this is the port number on the controller to which it is connected.

For UDP/IP this is the port number on the controller to where the server
datagrams are sent. For UDP/IP this port number is also the port number that
the server listens for datagrams from the controller(s) on and must be the
same for all controllers on the channel. Each UDP/IP channel link on the
server must also use a different port number.
IP Address 2 (Only applicable to LANVendor port.)

The redundant IP address of the device. If this is not specified, the controller
name is used as the host name, with a B appended to it.
Port For TCP/IP this is the port number on the controller to which it is connected.

For UDP/IP this is the port number on the controller to where server
datagrams are sent. For UDP/IP this port number is also the port number that
the server listens for datagrams from the controller(s) on and must be the
same for all controllers on the channel. Each UDP/IP channel link on the
server must also use a different port number.
Item Type The type of controller specified when this item was created.

21
Chapter 2 - DNP3 channel and controller reference

Property Description
Last Modified The date and time the controller properties were modified.
Last The date and time the controller was last downloaded to the server.
Downloaded
Item Number The unique item number currently assigned to this controller, in the format
RTUnnnnn .

You can change the Item Number if you need to match your current server
database configuration. The number must be between 00001 and the
maximum number of controllers allowed for your system.

For more information about setting the maximum value, see the topic titled
"Adjusting sizing of non-licensed items" in the Supplementary Installation
Tasks Guide.

Note that the maximum number of controllers that may be used in a system is
defined in the Experion specification for that Experion release, This number is
likely to be less than the maximum number that can be configured in the
database as shown in "Adjusting sizing of non-licensed items."

DNP3 controller levels

Controller and Point configuration needs to be tailored according to the DNP3
controller level.

Level 1
For slave devices implementing DNP3 V3 Application Layer protocol Level 1.
This is the simplest DNP3 level, typically a small end-device such as a meter
or relay, whose I/O is local to the device. Typically, Level 1 devices rely on
either RBE or unsolicited methods for sending data to master devices. The
following controller and point configuration items are relevant:

n Point periods are irrelevant.

n Point object type, variation (such as data size and status flag) and object
address are relevant.
n Reads of all controller static data (class 0) occur at the configured rate.
This is inefficient, it would be better to have infrequent class 0 polls, and
rely on class 1/2/3 polling or unsolicited data for more frequent updates.
n Reads of all controller event data (classes 1, 2, and 3) at the configured
rate. This requires the slave assigning all required objects to the required

22
 Chapter 2 - DNP3 channel and controller reference

classes.
n Unsolicited data may be sent by the controller.
n Performing point control is inefficient because class 0 reads are the only
way to confirm the control was successful.

Level 2
For slave devices implementing DNP3 V3 Application Layer protocol Level 2.
This is typically a large Intelligent Electronic Device (IED) or a small Remote
Terminal Unit (RTU). Typically, the I/O is local to the device. Level 2
controllers are treated as Level 1 controllers with the following exceptions:

n Point periods are relevant. Periodic polling for static data (for the entire
object type) at the rate determined by the fastest point scanning
configured for any Point referencing that object type. Class 1/2/3 polling
and unsolicited data are still far more efficient than this method.
n Class 0 reads would typically be disabled (set to 0), as they are inefficient
compared to the above method.

Level 3
For slave devices implementing DNP3 V3 Application Layer protocol Level 3.
This is typically a medium size slave device, such as an RTU or Data
Concentrator. Level 3 controllers are treated as Level 2 controllers with the
following exceptions:

n DNP3 controller read requests are for a block of objects, of the same type
and period. This method replaces entire object type read used for Level 2
devices. Note that for some controllers it may be necessary for all objects
in the block to exist on the controller. That is, it may be necessary for
DNP3 objects to be built directly.
n Performing point control is efficient because single object reads can be
performed to confirm the control was successful.

ATTENTION: Level 3 is the only controller level supported in

RTU2020 integration.

23
Chapter 2 - DNP3 channel and controller reference

Classes, unsolicited responses, and time

synchronization properties for a DNP3 controller
If the Separate Link B Configuration check box on the Main tab is selected, two
tabs are visible; Classes, Unsol & Time Sync – Link A and Classes, Unsol &
Time Sync – Link B. The properties on these tabs are the same, one for Link A
and the other for Link B.
The Classes, Unsol & Time Sync tab defines the class requests, unsolicited
responses, and time synchronization settings for a DNP3 controller.

Class requests
Property Description

Enable Enables the classes to be requested. You can disable classes if your control
strategy does not require the use of all classes.

By default, the check boxes for each class are selected.

If you clear this check box, it disables the class being requested. If events are
being generated for the class, these events continue to fill the controller's event
buffer.

Check this setting when configuring existing controllers.

Poll Period Specifies the frequency at which the class data is polled. Valid range is from 0 to
(Seconds) 604800 seconds. The default values for Class 1, 2, and 3 is 0 . The default value
for Integrity Polls is 3,600 .

Class 1, 2, 3, and 0 requests all data on the device, so for large devices this
period should be at least 60 seconds, and it is recommended that it be greater
than 3,600 seconds.

To ensure that data is always processed in chronological order, whenever a

request for class 0 data is to be made, a request for class 1, 2, 3, and 0 data (in
that order) is actually made.
Max The maximum number of events that are requested at a time for each class.
Number of
Events If there are events remaining in the controller's event buffer then execute
repeats are configured. For more information, see the Combine classes 1, 2,
and/or 3 in a single request property. A value of 0 retrieves all of the class's
events.
Incremental If selected, the events in a controller's event buffer will be retrieved in
Startup increments, one class at a time.

24
 Chapter 2 - DNP3 channel and controller reference

Property Description
Urgent tasks (such as controls) or scheduled requests by other controllers in a
half duplex link can be performed while the controller is starting up.

If you clear this check box, all events are requested at the same time on
controller startup.

ATTENTION: The Combine classes 1, 2 and/or 3 in a single request

check box does not affect startup.

By default, this check box is selected for new controllers. Check this setting
when configuring existing controllers.
Class 0 (Only available when Incremental Startup is selected.)
During
Startup The minimum period at which a request for Class 0 data is appended to an
incremental startup request for class data. Valid range is from 0 to 3,600
seconds.

The default value is 0 .

ATTENTION:

l This setting does not cause additional incremental startup requests

to be made; it merely appends class 0 to class 1, 2 and/or 3
requests that would normally be made anyway.
l A non-zero value for this setting should be used with caution as it
may cause delays in incremental startup or may even stop it from
completing altogether. A non-zero setting will result in the class 0
responses updating the point parameters values during
incremental startup when they would otherwise remain bad.

Combine If selected, requests for classes are combined together with other classes
classes 1, scheduled at that time. Select an option button.
2, and/or 3
in a single l Request the maximum number of events once per poll (Do not repeat)
request If selected, no action will be taken if there are events remaining in the
controller's event buffer.
If a controller or address is generating events faster than they are being
retrieved, the DNP3 interface may not be able to keep up with the
generated events until the next integrity poll.
l Repeat requests for the maximum number of events until all of the events

25
Chapter 2 - DNP3 channel and controller reference

Property Description

are retrieved. Do the follow up requests only when the link is idle.
This mode is applicable to half duplex links only.
If selected, repeat requests for remaining events only when there are no
other actions scheduled on the half duplex link.
Use this mode to prevent one controller from affecting the retrieval of
other controllers on the same half duplex link.
l Repeat requests for the maximum number of events until all of the events
are retrieved. Do the follow up requests only when the controller is idle.
If selected, repeat requests for remaining events only when there are no
other actions scheduled for that controller.
Use this mode for fair processing of controller activities when they are
scheduled.
l Repeat requests for the maximum number of events until all of the events
are retrieved. Do the follow up requests as the next action for the
controller.
If selected, repeat requests for remaining events straight away.
Other periodic actions scheduled for this controller are queued until the
controller's event buffer for this class is emptied.
If you clear this check box, events are requested for each class from the
controller individually.

Unsolicited responses
Property Description

Accept If selected, unsolicited messages from the controller are accepted and
Unsolicited confirmed. If not selected, unsolicited messages are ignored.
Messages

Time synchronization
Property Description

Enable time If selected, the server attempts to synchronize the controller's time when the
synchronization channel is brought into service and when the controller sets IIN bit 4 in its
responses. If not selected, the server never attempts to synchronize the
controller's time.

26
 Chapter 2 - DNP3 channel and controller reference

Property Description

If the Enable LAN time synchronization option is disabled, selecting this

option allows the use of the standard DNP time synchronization method.
The server synchronizes the controller's time by issuing a Delay
Measurement (Function code 23) request then writing a Time and Date
object to the controller.

This method of time synchronization is only recommended for serial ports

due to the non-variable nature of serial communications delays (however
this setting can be selected for other port types). For LANVendor ports, an
alternative synchronization method can be enabled using the Enable LAN
time synchronization option.

Enable LAN Only applicable to LANVendor port with the Enable time synchronization
time option enabled.
synchronization
This option uses the LAN/WAN DNP time synchronization method (see the
Transporting DNP V3.0 over Local and Wide Area Networks document). If
selected, the server synchronizes the controller's time by issuing a Record
Current Time (Function code 24) request then writing a Time and Date at
Last Recorded Time object to the controller upon receipt of a Null response.
If not selected, the standard method of time synchronization will be issued.

EFM
Property Description

Enable If selected, explicit read requests for EFM data in a DNP3 controller is enabled.
read for For networks with very tight bandwidth constraints, this option can be disabled to
EFM allow the server to rely on class based polling to collect EFM data.
responses
NOTE: The class that EFM data is assigned to is selected in ControlEdge
Builder. For more information, see "Configuring DNP3 Slave" in the
ControlEdge Builder User's Guide.

Timeouts properties for a DNP3 controller

If the Separate Link B Configuration check box on the Main tab is selected, two
tabs are visible; Timeouts – Link A and Timeouts – Link B. The properties on
these tabs are the same, one for Link A and the other for Link B.
The Timeouts tab defines the following properties for a DNP3 controller.

27
Chapter 2 - DNP3 channel and controller reference

ATTENTION: Several of the settings described in the following table

are marked with a (Dn) or (An), where n is a number. To aid in the
troubleshooting, error messages in the server log associated with one
of these particular settings also contain the corresponding (Dn) or (An)
text.
In order for the changes to settings on the DNP3 tab to take effect after
they have been downloaded to the server, the channel and/or
controller should be taken out of service and then put back into service.

DNP3 data link layer settings

Property Description

Overall timeout Time allowed for any complete Data link layer request. This is an overall
(D1) timeout and should be set to allow for any RESET, REQUEST LINK
STATUS, USER DATA, or other frames that may need to be sent in
order to successfully send the data from the upper layer. Valid range from
1–30,000 milliseconds. Default is 800.
Ack/link status Time allowed for a data link ACK or LINK STATUS RESPONSE frame
timeout (D2) to be received. Valid range from 1–30,000 milliseconds. Default is 500.
Inter-frame write The number of milliseconds the DNP3 Interface will wait between
delay sending consecutive data link layer frames to the RTU. Valid range is 0 to
5,000 milliseconds.

A non-zero value for this setting should be used with a high degree of
caution as it will result in slower throughput; however it may be necessary
for controller(s) that cannot correctly interpret back-to-back data link layer
frames or application layer requests. When such controllers are used on
a point-to-multipoint link, where each controller receives all frames send
by the DNP3 Interface, this setting should be set consistently across all
controllers to ensure consistent inter-frame write delays.

Default value is 0 milliseconds (that is, no delay).

Number of reset (Only available when Acknowledgements is selected.)
retries (D3)
Number of times a data link RESET frame is resent in the event of an
error. Valid range from 0–100 retries. Default is 0.
Number of data (Only available when Acknowledgements is selected.)
retries (D4)
Number of times data link USER DATA frame is resent in the event of an
error. Valid range from 0–100 retries. Default is 0.

28
 Chapter 2 - DNP3 channel and controller reference

Property Description
Send RESET (Only available when Acknowledgements is selected.)
upon receipt of a
NACK with clear If selected, immediately after receiving a NACK frame with the DFC bit
DFC (D7) set to 0 the server sends a RESET LINK frame to the slave. The server
interprets the receipt of such a NACK frame as meaning the slave was
restarted and is waiting for its receiving link to be reset for the first time.

If not selected, the receipt of a NACK frame with the DFC bit set to 0
causes the server to behave as the same as if the DFC bit is set to 1. That
is, the configured number of REQUEST LINK STATUS tests will be
attempted. If the slave responds with a DFC set to 0 during these tests,
the data link layer transaction will be continued. Otherwise, the data link
layer transaction will be failed.

Default is selected.
Send NACK with Allows for when the server receives a frame from the slave with the FCV
clear DFC upon bit set to 1 before the server has received a RESET frame in its current
receipt of a set in-service session.
FCV before
RESET (D6) If selected and this situation occurs, the server sends a NACK frame to
the slave with a DFC bit set to 0. This should trigger the slave into
sending a RESET frame to the master.

If not selected and this situation occurs, the server does not send a
response to the received frame.

Although not discussed in the DNP3 V3 Data Link Layer specification,

this option may need to be selected to ensure proper recovery when the
channel or controller is taken in and out of service.

Selected by default.
Acknowledgments If selected, the slave is requested to acknowledge data link layer USER
DATA frames that are sent to it by returning an ACK frame. If set, a
RESET frame is sent when required to in order to synchronize the FCV
bit or the master and the slave.

If not selected, then the slave is not requested to confirm USER DATA
frames.

Not selected by default.

Data link acknowledgements are not to be configured for Ethernet

devices. It is also recommended that data link acknowledgements not be
used for serial devices.

29
Chapter 2 - DNP3 channel and controller reference

Property Description

Number of link (Only available when Acknowledgements is selected.)

status tests (D5)
Number of times a REQUEST LINK STATUS frame is sent if the slave
indicates that it cannot receive any more frames. Valid range from 0–100
retries. Default is 3.

DNP3 application layer settings

Property Description

Fragment Time allowed for an application fragment to be received after the initial request
timeout or after receipt of the previous fragment within the response. Valid range from 1–
(A2) 30,000 milliseconds. Default is 6000.
Response Time allowed for a complete application response (possibly multiple fragments)
timeout to be completely received. Valid range from 1–30,000 seconds. Default is 30.
(A3)
Maximum Maximum number of bytes in an application layer fragment. Valid range from
fragment 249–2,048. Default is 2048.
size
Number of Number of times an application layer request is retried in the event of an error.
request Valid range from 0–100 retries. Default is 0.
retries (A4)

Control properties for a DNP3 controller

The Control tab defines the following properties for a DNP3 controller.

DNP3 default control settings

Property Description

Control This is the default setting for new points built on the controller and can be changed
function on an individual point basis. It sets which Application layer function(s) are used to
control the Control Relay and Analog Output blocks.

Selecting Direct Operate causes the Direct Operate function to be used. Selecting
Select-Operate causes each control operation to use the Select function followed
by the Operate function.

The default value is Direct Operate .

30
 Chapter 2 - DNP3 channel and controller reference

Property Description
Control This is the default setting for new points built on the controller and can be changed
operation on an individual point basis. This setting sets whether to use Pulse or Latch when
controlling Control Relay Output Blocks.

If the Pulse setting is used without the Use trip/close relays, the control operation
attempts to pulse the corresponding Unpaired Momentary Relay.

The default value is Latch .

ATTENTION: This property is not the same as the Pulse Width property on
the Control tab of a status point.

Use This is the default setting for new points built on the controller and can be changed
trip/close on an individual point basis. This setting sets whether to use the Trip and Close
relays relay pair when controlling Control Relay Output Blocks.

If the Trip and Close relay pair is to be used for a point, the Control operation for
that point must be set to Pulse . This can be accomplished by setting the Control
Operation property for the controller to Pulse by default, or by specifying PU on the
point's address line.

When the Trip and Close relay pair is used, the Trip relay is pulsed on when the
point is controlled to the low state and the Close relay is pulsed on when the point
is controlled to the high state.
Pulse This is a controller-wide setting and cannot be modified on an individual point
width basis. It is the width of the pulse in milliseconds. Valid range is from 0 to 10,000
milliseconds.

The default value is 200 .

ATTENTION: This property is not the same as the Pulse Width property on
the Control tab of a status point.

Optimizing DNP3 scanning performance

In general, periodic polling for, or the unsolicited reporting of, DNP3 Class 1,
Class 2, and Class 3 events should be used in preference to periodic polling
for static data.
The maximum amount of static data that can be acquired from a controller is
influenced by the rate of sending scan packets to the controller. You should
gain an understanding of DNP3 scan packets in order to optimize data

31
Chapter 2 - DNP3 channel and controller reference

acquisition performance, and maximize the amount of data acquired with

each scan packet.
The scan packets that have been built can be listed by using the utility lisscn
(list scan). Listing scan packets helps verify the scanning strategy.

The ability to optimize scanning depends upon the DNP3 controller type used:

n Level 1 controllers should use RBE (class polls) and/or unsolicited

responses to achieve efficient scanning. Class 0 polling should be carried
out at a low frequency or avoided completely.
n Level 2 controllers should also use RBE and unsolicited responses to
achieve efficient scanning. Point parameters should not be polled at a
high frequency because it causes read requests for complete object types
to be sent to the device, at a rate equal to the fastest Point frequency
configured for that object type.
n Level 3 controllers allow for efficient scanning by combining DNP3 object
types into blocks (see the following table) of DNP3 objects with similar
scanning periods.
In circumstances where communication bandwidth is limited dynamic
scanning can be employed for Level 3 controllers so that data is scanned
at a faster rate only when it is required, for example, when an operator is
viewing a display.

DNP3 object type DNP3 level 3 maximum block size

BI/BO/SOE 233
16 bit AI/AO/Co 127
32 bit AI/AO/Co 85

32
CHAPTER

3 DNP3 POINTS REFERENCE

This section describes how to configure points for a DNP3 controller using
Quick Builder.

Defining a DNP3 address for a point parameter

For source addresses and destination addresses, the format for a DNP3
controller address is
ControllerName Address

Part Description

ControllerName The name of the DNP3 controller.

Address The address in the controller where the value is recorded. See "Address
Syntax" below.

For help when defining an address, click next to Address to display

Address Builder.

Address Syntax
The format for the address is:
ObjectType ObjectAddress [DataSize] [ControlOptions |
HistoryBackfill] [B:BitNumber | DataFormat]

Part Description

ObjectType Object type is the DNP3 object type being specified. See "Point parameter
addressing options" on page 35 and "DNP3 Objects options" on page 36.
ObjectAddress Specifies the object address of the specified object type. Range is 0–32767 .
DataSize Specifies the data size of analog and counter objects, either 16 or 32 (bits).
This value overrides the data size specified in the controller configuration.

Short floating point analog variations may also be specified.

Valid values are 16 , 32 , and FP.

33
Chapter 3 - DNP3 points reference

Part Description

Long floating point analog variations are NOT supported.

ControlOptions Applicable to BOC and AOC only:

l DO for use of Direct Operate control function or

l SO for use of Select - Operate control functions
Applicable to BOC only:

l TC for use of Trip and Control Relay Pair or

l NOTC for non-use of Trip and Control Relay Pair
l LA for Latch On/Latch Off control operations or
l PU for Pulse On control operations

NOTE: If the above settings are not specified when the point is first
built, the control options for the point are set to those of the point's
controller.

These settings are separate from the Pulse Width setting found on the
Control tab of a status point.
HistoryBackfill HIS can be added to the address to enable any source parameter to have its
history backfilled. The source parameter must be assigned to history.

The history backfill is performed regardless of the state of history gating

points configured for the parameter.

HistoryBackfill is only supported for status and analog point types.

HistoryBackfill must also be configured for the controller. See "Main

properties for a DNP3 controller" on page 17

For points that have HistoryBackfill configured:

l Standard history averages are NOT re-averaged

l Any Status point PV or OP with non-consecutive addressed bits is not
recalculated
BitNumber The valid range is 0 (default) to 15 , where 0 is the least significant bit.

The number of bits read is implied by the point type. Analog point parameters
read up to 16 bits. Status point parameters read 1, 2, or 3 consecutive bits.
DataFormat The data format acronym or starting bit number, depending on how you want

34
 Chapter 3 - DNP3 points reference

Part Description

the value to be read:

l Data format for scaling (see "Data format for scaling" on page 38)
l Data format for reading raw values without scaling (see "Data format
for reading raw values without scaling" on page 39)
l Data format for reading mode values (see"Data format for reading
mode values" on page 39)
If you want to use a user-defined data format, you must define the format on
the server. For more information, see "About user-defined data formats" in
the Server and Client Configuration Guide.

Example
Analog point

PV source: DNPCT 1 AI 163 FP HIS IEEEFP

SP destination: DNPCT_1 AO 162 16 U16B
SP destination: DNPCT_1 AO 200 16 SO U16B
Mode destination: DNPCT_1 BO 163
Status point

PV source: DNPCT_1 BI 201

OP destination: DNPCT_1 BOC 201 PU TC DO
Accumulator point

PV source: DNPCT_1 Co 171 C16

Point parameter addressing options

Note that all DNP3 devices may not accept the options described here. See
the device's DNP3 device profile document for more details.

35
Chapter 3 - DNP3 points reference

Data History
Point Bit # Data
Point type QB entry for object size backfil
parameter applic. format
(bits) applic.

Status PV/OP source BI/SOE/BO n/a No n/a Yes

DBI n/a Yes n/a Yes
AI/FAI/AO/CO/FCO 16 or Yes non- Yes
32 scaled
OP destin BOC n/a No n/a No
AOC 16 or Yes non- No
32 scaled
Accumulator PV source AI/FAI/AO/CO/FCO 16 or No non- Yes
32 scaled
Analog PV/SP/OP/A1- CO/FCO 16 or No all Yes
A4 source 32
PV/SP/OP/A1- AI/FAI/AO 16, 32, No all Yes
A4 source or FP
SP/OP/A1-A4 AOC 16, 32, No all No
source or FP
Status or Mode source BI/BO n/a No n/a Yes
Analog
DBI n/a Yes Yes
AI/FAI/AO/CO/FCO 16 or No mode Yes
32
Mode destin BOC n/a No n/a No
AOC 16 or Yes mode No
32

DNP3 Objects options

DNP3
Object Object type
object type Variation description
type description
#s

BI Binary input 1 With or without status

36
 Chapter 3 - DNP3 points reference

DNP3
Object Object type
object type Variation description
type description
#s
DBI Double bit binary 3 With or without status
input1
SOE Binary input 2 With or without status, can have timestamps
event
BO Binary output1 10 With status
BOC Binary output 12
command
CO Counter1 20 16-bit or 32-bit, with or without status. Delta
counter variations are NOT supported.
FCO Frozen counter1 21 16-bit or 32-bit, with or without status. Delta
counter variations are NOT supported.
AI Analog input1 30 16-bit, 32-bit, or short floating point, with or without
status.
FAI Frozen analog 31 16-bit, 32-bit, or short floating point, with or without
input1 status.
AO Analog output 40 16-bit, 32-bit, or short floating point, with or without
status.
AOC Analog output 41
command
Virtual Terminal 112 Used by EFM only, not addressable for a point
Output Block parameter.
Virtual Terminal 113 Used by EFM only, not addressable for a point
Event Data parameter.

SOE configuration
The SOE enable flag must be set for the controller, and status points must
have their PV source address specify SOE as the object type. Do not build
two point/parameters where one uses the SOE object type and the other uses
the BI object type with the same object address.

1Any periodic scans request static variations but both static and event groups are accepted from
the controller and processed

37
Chapter 3 - DNP3 points reference

Data format for scaling

You can scale point parameter values with a data format. Select the format
that corresponds to the raw data range in the controller.
When analog input deadbands are used, the absolute deadband value written
to the controller for scaled data formats is the deadband percentage of the
raw data range specified in the Description column below. For data formats
that are not scaled, the absolute deadband value written to the controller is a
percentage of the point's EU High and Low range.

Data format Description Scaled

C16 0–65535 No
HALFWD 0–65535 No
U100 0–100 Yes
U1023 0–1023 Yes
U4095 (default) 0–4095 Yes
S9999 –9999–9999 Yes
U9999 0–9999 Yes
u9998 0–9998 Yes
U999 0–999 Yes
U88 0–255 Yes
U148 0–16383 Yes
U158 0–32767 Yes
U168 0–65535 Yes
S88 –128–127 Yes
S168 –32768–32767 Yes
S328 –2,147,483,648–2,147,483,647 No
U32B 0–4,294,967,296 No
IEEEFP IEEE single precision floating point range No
REVWD 0–65535 No
U38CD 0–9999 in binary coded decimal Yes
U48CD 0–9999 in binary coded decimal Yes

38
 Chapter 3 - DNP3 points reference

Data format Description Scaled

LOWWORD 0–65535 No
HIGHWORD 0–65535 No

ATTENTION: If auxiliary parameters have a data format type that

requires scaling, they take the same range as the PV.

Data format for reading raw values without scaling

To read less than 16 bits without scaling, enter the starting bit number (1–15).
If you are not using scaling, the point range is still used for PV indicator bar
height only (the PV indicator bar is on the Point detail display on Station).

Data format for reading mode values

By default, modes are 1-bit values unless the 'mode' keyword is specified;
then modes are 4 bits wide.

Configuring Integration with Honeywell RTU2020

This section describes the configuration steps specific to integrating an
Experion Server with the Honeywell RTU2020 using the DNP3 protocol.
This integration method provides the following features:

n Reduces duplicate entry of data into the ControlEdge Builder program

and Quick Builder point configuration,
n Minimizes the risk of misalignment between the ControlEdge Builder
program and SCADA point configuration,
n Helps to provide consistency of point structure and, hence, user
interaction for common control strategy structures.
n Enables addressing of entities within the RTU2020 using Variable Names
rather than DNP3 addressing format.

Using ControlEdge Builder for Experion Integration

ControlEdge Builder is used to configure and maintain the RTU2020 and to
create the files required for integration of each RTU2020 with Experion
server.

39
Chapter 3 - DNP3 points reference

For more information, see the RTU2020 documentation that is available from
the Honeywell Process Solutions website
(http://www.honeywellprocess.com).
Integration between Experion server and RTU2020 is supported by
ControlEdge Builder R120 and later.
In order for RTU2020 Variable Names to be monitored from the Experion
server they must each be assigned to a DNP3 address in the SCADA
mapping tables. For more information about accessing and editing the
Experion SCADA mapping tables, see "Configuring communication" in the
ControlEdge Builder User's Guide.
This mapping data is downloaded to:

n The RTU2020 when the program is downloaded from the ControlEdge

Builder
n The Experion Server database when the RTU2020 controller is
downloaded from Quick Builder. The mapping data is contained in the
RTU2020 Experion Export file which is referenced in the Quick Builder
RTU2020 controller definition. For more information, see "Main properties
for an RTU2020 DNP3 controller" on the facing page .

To create an RTU2020 Experion Export file

1. Start ControlEdge Builder.
2. Open the project file for the target RTU2020.
3. Connect to the target RTU2020.
4. Click Export Configuration to Experion .
5. Enter the following data:
a. Save in:C:\ProgramData\Honeywell\Experion
PKS\Server\data\ControllerIntegration if you are on the primary server,
or \\PrimaryServerName\ControllerIntegration if you are on another
node.
b. File name: an appropriate name.
6. Click Save .
A zip file will be created with all the required data.

ATTENTION: An RTU2020 Experion Export file must be created

for each RTU2020 to be integrated.

40
 Chapter 3 - DNP3 points reference

Main properties for an RTU2020 DNP3 controller

This section defines only those properties in the Main tab for a DNP3
controller that are specific to RTU2020 integration. A DNP3 controller must
be created for each RTU2020.
For more information about how to create a DNP3 controller, see "Main
properties for a DNP3 controller" on page 17.

n Enable RTU2020 Integration: checkbox enabled.

n RTU2020 Experion Export File: Pathname to the RTU2020 Experion

Export file located at C:\ProgramData\Honeywell\Experion
PKS\Server\data\ControllerIntegration if you are on the
primary server, or
\\PrimaryServerName\ControllerIntegration if you are on
another node.
For more information, see "Using ControlEdge Builder for Experion
Integration" on page 39. Clicking the browse button can assist in entering
this data.

Defining Point Parameter Address using Address

Browser
You can use this method to define point parameter addresses for a RTU2020.
Connection to the RTU2020 is not required, only RTU2020 Integration
enabled and RTU2020 Experion Export File: pathname defined.
Open the Address Builder for the required parameter and enter the following
details:

Defining Address Syntax for RTU2020 point parameter

using the Address Browser
Part Description

Address Controller
Type
Controller Name of target DNP3 controller
Location Click on the browse button to open the RTU2020 Item Browser. You can now
browse through the RTU2020 address space to pick the Variable Name you want
to address.

where:

41
Chapter 3 - DNP3 points reference

Variable Name is a user defined name, configured in ControlEdge Builder

Configuration SCADA Mapping tables as a high level alternative to using a
DNP3 address. For further information on accessing and editing the Experion
SCADA Mapping tables, see "Configuring communication" in the
ControlEdge Builder User's Guide.

42
CHAPTER

4 RTU2020 EFM METER TEMPLATES

REFERENCE
This section describes the configuration information specific to RTU2020
meter templates on DNP3 controllers. For information about how to build
EFM meter templates and equipment, see "Building Electronic Flow
Measurement (EFM)" in the Quick Builder User’s Guide.

Main properties for an RTU2020 meter template

This topic lists the Main tab settings for an RTU2020 meter template on a
DNP3 controller. Different flow computers require different settings. The
Interval Log, Daily Log, and Alarm and Event Log logs are all optional.
However, you would configure at least one, if not all, of them. The
ControlEdge Builder User's Guide should provide addressing information for
addressing the RTU2020 logs.
For information about each field on this tab, see "Main properties for an EFM
meter template" in the Quick Builder User’s Guide.
To make configuring meter templates an easier task, samples of RTU2020
meter templates are included in Experion. For information about how to
import sample RTU2020 meter templates, see "Managing EFM meter
templates" in the Quick Builder User’s Guide.

Interval Log properties for an RTU2020 meter

template
The Interval Log tab appears only when the interval log is enabled on the Main
tab.
When creating RTU2020 meter templates for flow computers on DNP3
controllers, the properties you collect for the interval log are specific to the flow
computer. For the properties supported by the flow computer, see the
ControlEdge Builder User's Guide.
For information on how to add interval properties to this tab, see "Interval Log
properties for an EFM meter template" in the Quick Builder User’s Guide.

43
Chapter 4 - RTU2020 EFM meter templates reference

Configuration Log properties for an RTU2020

meter template
When creating RTU2020 meter templates for flow computers on DNP3
controllers, configuration log properties are specific to the flow computer. For
the properties supported by the flow computer, see the ControlEdge Builder
User's Guide.
If the configuration log requires compliance with API21.1 then the
configuration log properties configured here need to include at least those
listed in the API21.1 standard.
For information on how to add configuration properties to this tab, see
"Configuration Log properties for an EFM meter template" in the Quick
Builder User’s Guide.

Daily Log properties for an RTU2020 meter

template
The Daily Log tab appears only when the daily log is enabled on the Main tab.
When creating RTU2020 meter templates for flow computers on DNP3
controllers, the properties you collect for the daily log are specific to the flow
computer. For the properties supported by the flow computer, see the
ControlEdge Builder User's Guide.
For information on how to add properties to this tab, see "Daily Log properties
for an EFM meter template" in the Quick Builder User’s Guide.

Alarm and Event properties for an RTU2020

meter template
The Alarm and Event tab appears only when the alarm and event log is
enabled on the Main tab.
When creating RTU2020 meter templates for flow computers on DNP3
controllers, the properties you collect for the Alarm and Event Log are specific
to the flow computer. For the properties supported by the flow computer, see
the ControlEdge Builder User's Guide.
For information on how to add properties to this tab, see "Alarm and Event
properties for an EFM meter template" in the Quick Builder User’s Guide.

44
 Chapter 4 - RTU2020 EFM meter templates reference

Data Export properties for an RTU2020 meter

template
When creating RTU2020 meter templates for flow computers on DNP3
controllers, the data export formats you specify depend on the gas
measurement system receiving the exported EFM data. For the properties
supported by the flow computer, see the ControlEdge Builder User's Guide.
For information on how to configure data export formats on this tab, see "Data
Export properties for an EFM meter template" in the Quick Builder User’s
Guide.

45
Chapter 4 - RTU2020 EFM meter templates reference

46
CHAPTER

5 TROUBLESHOOTING DNP3 ISSUES

This section describes troubleshooting tasks for DNP3 that you can perform
either on the server or from any Station.

Testing DNP3 communications with the server

You use the DNP3 test utility, dnptst, to test communications between the
server and the DNP3 controller after you have downloaded channel and
controller definitions to the server database.

To run the dnptst utility

1. Open a Command Prompt window.
2. Type dnptst and then press Enter .
3. Follow the directions as prompted.

Troubleshooting DNP3 scanning errors

If the Point Detail display for a point shows a bad value (indicated by inverse
video), then the point might be built with an address that is syntactically valid
but not configured in the controller. If this is the case refer to the Event Log,
where there should be an event describing the problem.
Note the following items:

n Some DNP3 devices return an error if a block of objects is requested from

it and one of the objects in the block doesn't exist. In this case the valid
objects may not even be returned. The solution is to ensure all DNP3
objects in the controller are in contiguous addresses.
n If a controller sends data to the server as unsolicited data, or in response
to a class poll request, and the size variation differs from that specified in a
point/parameter address, then that point/parameter is not processed. The
solution is to specify the correct size (16 or 32) in the point/parameter
address.
n If scanning errors occur in DNP3 level 2 devices then all points built on the
controller are processed to BAD.
n The DNP3 daemon may run out of transaction table slots if the channel is

47
Chapter 5 - Troubleshooting DNP3 issues

overloaded or if there any large numbers of controllers on the channel.

The channel will be failed when this occurs and may be recovered by
periodic diagnostic requests. In such overload conditions, the number of
transaction table slots can be increased using the settings on the
channel's Port tabs.

Troubleshooting Experion RTU2020 mismatch

alarm
This topic explains how a mismatch between the Experion point database and
the RTU2020 configuration can occur, how it is diagnosed, and how it is fixed.
When changes or additions are made to an RTU2020 program it will usually
be necessary to also make corresponding changes or additions to the
SCADA Mapping Table. The effect of this will be to potentially invalidate the
data being scanned from the impacted RTU2020. Additionally an alarm will
be raised indicating a mismatch between the RTU2020’s SCADA Mapping
table and the Experion server’s database.
Knowledge of the sequence in which the RTU2020’s program and the
Experion server’s RTU2020 controller have been downloaded, and the state
of the Experion server when the download occurs, can help in understanding
how to fix a mismatch alarm.

Quick Builder RTU2020 controller download executed

with the Experion RTU2020 controller enabled
If an RTU2020 controller is downloaded from Quick Builder to the Experion
server whilst that controller is enabled, the new mapping data will not be
implemented but will be saved in a cache in the Experion server. When the
controller download from Quick Builder has completed, point scanning of that
controller will therefore continue unaffected.
If the RTU2020 program is then downloaded from ControlEdge Builder, the
mapping data in the RTU2020 will be newer than that in the Experion server
so a mismatch alarm will be raised.
To synchronize the mapping data in the Experion server with that in the
RTU2020 you need to call up the detail display of the impacted controller and
click the Platform tab. In the Integration section you will notice that the
Experion server’s mapping version is different from that of both the RTU2020
and the Experion server cache. Clicking the Apply cache button (requires
Engineer security level) will update the Experion server’s mapping data from
the Experion server cache version and the mismatch alarm will return to
normal.

48
 Chapter 5 - Troubleshooting DNP3 issues

Quick Builder RTU2020 controller download executed

with Experion RTU2020 controller disabled
If an RTU2020 controller is downloaded from Quick Builder to the Experion
Server whilst that controller is disabled, the mapping data in the Experion
server’s database will be updated. The old mapping data will be saved in a
cache in the Experion server.
Since the mapping data in the RTU2020 will be older than that in the Experion
server enabling the Experion server RTU2020 controller will cause a
mismatch alarm to be raised. There are two ways in which this condition can
be fixed. Either

1. Download the RTU2020 program from ControlEdge Builder thus

updating the mapping data in the RTU2020.
Implementing this method will result in the new RTU2020 program and
mapping data being used and hence the mismatch alarm will return to
normal; or,
2. Call up the detail display of the impacted controller and click the Platform
tab. In the Integration section it will be seen that the Experion server’s
mapping version is different from that of both the RTU2020 and the
Experion server cache. Clicking the Apply cache button (requires
Engineer security level) will update the Experion server’s mapping data
from the Experion server cache version. Implementing this method will
result in the old RTU2020 program and mapping data being used and
hence the mismatch alarm will return to normal.

Recommended steps to update an RTU2020 program

The recommended steps to modify an RTU2020 program without causing a
mismatch alarm to be raised are shown below.

ATTENTION: View of the impacted RTU2020’s data will be lost

during execution of these steps

1. Using ControlEdge Builder make the required updates to the RTU2020

program.
2. Ensure that all the RTU2020 Variable Names that are required to be
monitored by the Experion server are entered in the RTU2020 SCADA
Mapping table.
3. Create the RTU2020 Experion Export file. For more information, see
"Using ControlEdge Builder for Experion Integration" on page 39.

49
Chapter 5 - Troubleshooting DNP3 issues

TIP: Honeywell recommends that this new RTU2020 Experion

Export file be saved to the same location and with the same name
as (and therefore overwrites) the old one.

4. From Experion Station disable the impacted RTU2020 controller.

5. From ControlEdge Builder download the updated program, from steps 1
and 2, to the RTU2020.
6. Download the affected controller from Quick Builder to the Experion
server database.
7. From Experion Station enable the impacted RTU2020 controller.
8. Ensure that no mismatch alarm has been raised.
9. Optionally create and download any additional points required.
For more information, see “Automated Point Generation for an Integrated
Controller” in the Quick Builder User’s Guide.

50
 Notices

NOTICES
Trademarks
Experion®, PlantScape®, and SafeBrowse® are registered trademarks of
Honeywell International, Inc.

Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the
trademark owner, with no intention of trademark infringement.

Third-party licenses
This product may contain or be derived from materials, including software, of
third parties. The third party materials may be subject to licenses, notices,
restrictions and obligations imposed by the licensor. The licenses, notices,
restrictions and obligations, if any, may be found in the materials
accompanying the product, in the documents or files accompanying such third
party materials, in a file named third_party_licenses on the media containing
the product, or at http://www.honeywell.com/ps/thirdpartylicenses.

Documentation feedback
You can find the most up-to-date documents on the Honeywell Process
Solutions support website at: http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation,
send your feedback to: [email protected]
Use this email address to provide feedback, or to report errors and omissions
in the documentation. For immediate help with a technical problem, contact
your local Honeywell Technical Assistance Center (TAC).

How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software
defect or weakness that can be exploited to reduce the operational or security

51
Notices

capabilities of the software.

Honeywell investigates all reports of security vulnerabilities affecting
Honeywell products and services.
To report a potential security vulnerability against any Honeywell product,
please follow the instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx

Support
For support, contact your local Honeywell Process Solutions Customer
Contact Center (CCC). To find your local CCC visit the website,
https://www.honeywellprocess.com/en-US/contact-us/customer-support-
contacts/Pages/default.aspx.

Training classes
Honeywell holds technical training classes that are taught by process control
systems experts. For more information about these classes, contact your
Honeywell representative, or see http://www.automationcollege.com.

52