DNP3 Polling

Digital Transformation Group Operational Technology

DESIGN STANDARD DS 43-01

DNP3 Polling

VERSION 1

REVISION 1

APRIL 2018

Design Standard No. DS 43-01

DNP3 Polling

Uncontrolled if Printed of 24

Ver 1Rev 1

© Copyright Water Corporation 2009-2018

FOREWORD

Supervisory Control and Data Acquisition (SCADA) Design Standards are prepared to ensure that the Water

Corporation’s staff, consultants and contractors are informed as to the Water Corporation’s design standards and

recommended practices. Design standards are intended to promote uniformity so as to simplify design and drafting

practice and have as their ultimate objective the provision of safe and functional plant at minimum whole of life

cost.

The Water Corporation design standards and recommended practices described in this design standard have

evolved over a number of years as a result of design and field experience and these have been investigated and

documented.

Users are encouraged to forward submissions for continuous improvement to the Principal SCADA Engineer who

will consider these for incorporation into future revisions.

Manager, Operational Technology

This document is prepared without the assumption of a duty of care by the Water Corporation. The document is not intended

to be nor should it be relied on as a substitute for professional engineering design expertise or any other professional advice.

Users should use and reference the current version of this document.

© Copyright – Water Corporation: This standard and software is copyright. With the exception of use permitted by the

Copyright Act 1968, no part may be reproduced without the written permission of the Water Corporation.


DNP3 Polling


Ver 1Rev 1


REVISION STATUS

The revision status of this standard is shown section by section below.

REVISION STATUS

SECT. VER./

REV.

DATE PAGES

REVISED

REVISION DESCRIPTION

(Section, Clause, Sub-Clause)

RVWD. APRV.

ALL 0/0 25/05/01 All New Edition DW JB

ALL 1/0 27/08/14 All Complete revision JGB MH

ALL 1/1 11/4/18 All Updated for Operational

Technology

JGB RP


DNP3 Polling


Ver 1Rev 1


DESIGN STANDARD DS 43-01 DNP3 Polling

CONTENTS Section Page

1 OVERVIEW .................................................................................................................................. 6

1.1 Purpose ......................................................................................................................................... 6

1.2 Scope.............................................................................................................................................. 6

2 REFERENCES .............................................................................................................................. 7

3 DEFINITIONS .............................................................................................................................. 8

4 CLASSIFICATION OF DATA ................................................................................................... 9

4.1 General .......................................................................................................................................... 9

4.2 Non-class data: ............................................................................................................................. 9 4.2.1 Class 0 data: ................................................................................................................................... 9 4.2.2 Class 1 data: ................................................................................................................................... 9 4.2.3 Class 2 data: ................................................................................................................................... 9 4.2.4 Class 3 data: ................................................................................................................................... 9 4.2.5 Urgent Data .................................................................................................................................... 9 4.2.6 Buffered Event Data .................................................................................................................... 10 4.2.7 Event Data .................................................................................................................................... 10 4.2.8 Static Data .................................................................................................................................... 10


DNP3 Polling


Ver 1Rev 1


4.3 Assignment of Class ................................................................................................................... 10

4.4 Indications (IINs) ....................................................................................................................... 11

5 POINT INDEXES ....................................................................................................................... 12

5.1 General ........................................................................................................................................ 12

6 DATA TRANSFER ..................................................................................................................... 13

6.1 Client and Server ....................................................................................................................... 13

6.2 Outstation-To-Master data transfer ........................................................................................ 13

6.3 Outstation-To-Outstation data transfer .................................................................................. 13

6.4 Data Concentrator-To-Master Station data transfer ............................................................. 13

6.5 Outstation-To-Data Concentrator data transfer .................................................................... 14

6.6 Data Routing............................................................................................................................... 14

7 DATA TRANSFER FAILURE AND RECOVERY ................................................................ 15

7.1 Retries ......................................................................................................................................... 15

7.2 Failures ....................................................................................................................................... 15

7.3 Recovery...................................................................................................................................... 15

8 MASTER STATION COMMS REDUNDANCY .................................................................... 16

9 DATA STANDARDS. ................................................................................................................. 17

10 INPUT/OUTPUT POINT DEFINITIONS. .............................................................................. 18

11 APPENDIX A – SAMPLE I/O LIST ........................................................................................ 19


DNP3 Polling


Ver 1Rev 1


1 OVERVIEW

1.1 Purpose

This technical standard describes how the DNP3 SCADA protocol should be configured for use in the

Water Corporation’s SCADA network.

1.2 Scope

The standard applies to the configuration of all of Water Corporation’s devices that communicate

using the DNP3 protocol. It shall be followed by all staff and contractors configuring DNP3 capable

devices for use on Water Corporation assets.


DNP3 Polling


Ver 1Rev 1


2 REFERENCES

[B1] IEEE1815-2012, IEEE Standard for Electric Power Systems Communications—Distributed

Network Protocol (DNP3)


DNP3 Polling


Ver 1Rev 1


3 DEFINITIONS

For the purposes of this standard, the following definitions shall apply:

Corporation Water Corporation (of Western Australia)

DFDCS Dynamic Field Data Collection Standard

DNP3 A SCADA communications protocol

GPRS A mobile telephone transmission service

RTU Remote Terminal Unit

PLC Programmable Logic Device

PSTS or PSTN Public Switched Telephone Service or Network

Unsolicited reporting Where the transfer of event data is initiated by the outstation without

a request (poll) being sent from the master. Requires Report By

Exception.

Report by Exception

(RBE)

Where a significant change in the state or status of a data object

causes an event to occur that will later be reported to the SCADA

master or that will initiate an unsolicited message.


DNP3 Polling


Ver 1Rev 1


4 CLASSIFICATION OF DATA

4.1 General

The DNP3 protocol allows for data to be classified according to the reporting requirements. The

DNP3 protocol standard does not specify the use of the data classes and it is up to the implementer, in

this case Water Corporation, to assign data to classes as appropriate. The classes are as follows:

4.2 Non-class data:

This describes data that is not assigned to any class. It will not be reported in an integrity poll but may

be retrieved by individual object polls. For example a binary input point that is not in any class

category may be retrieved by issuing a Binary Input (Group 1, variation 1 or 2) or Analog Input

(Group 30, variations 1 to 6 ) poll to this point. Information such as RTU serial number, firmware

version, etc. may be in this category. Non-class data will not generate any event information.

4.2.1 Class 0 data:

Polls for data assigned to this Class will result in the current state of the object being reported. It is

essentially a snapshot of the state of the data taken at the time of the response to the master station’s

request. This is non-event data in that changes in the Class 0 object’s value will not produce an event.

Any object that is included in the following event classes must also be reported in a Class 0 response.

4.2.2 Class 1 data:

Polls for data assigned to this class will result in the Class 1 Events being reported. That is any

significant changes in the data objects that have occurred in objects that have been assigned to Event

Class 1 since the last time they were successfully reported. This Event Class is reserved for Urgent

event data (see below).

4.2.3 Class 2 data:



Class 2 since the last time they were successfully reported. This Event Class is reserved for non-

urgent or Buffered event data (see below).

4.2.4 Class 3 data:



Class 3 since the last time they were successfully reported. This Event Class is reserved for event data

that is essentially information only (see below).

Note: Events in any of the event classes (1, 2, 3) may be configured to report events with the time of the event (time-

stamped) or not.

4.2.5 Urgent Data

This is the highest priority data and is assigned to Event Class 1. Events of this type are reported with

a time-stamp. Any significant change in a point assigned to Event Class 1 (e.g. by a digital point

changing state or by an analog point exceeding a deadband) shall result in an unsolicited response

being sent to the master. In an installation that uses PSTN dial-up the outstation should immediately

initiate a call to the master when an event of this type occurs.


DNP3 Polling


Ver 1Rev 1


4.2.6 Buffered Event Data

A data change that is not urgent but is required to be reported as an unsolicited time-stamped event is

assigned to Class 2. When a Class 2 event occurs it is placed into an event buffer. When a

configurable number of events are in the buffer and/or when an event has been in the buffer for a

configurable time period, an unsolicited response shall be generated containing all the events in the

buffer.

Due to the connection set up time and protocol overhead the type of connection shall determine the

buffer parameters. A permanent connection shall have a relatively low ‘number of events’ and/or

‘time in buffer’ before an unsolicited response is generated when compared with a non-permanent

connection. This may also be the case when satellite communications is used

4.2.7 Event Data

Data that is neither urgent nor required to generate an unsolicited response, but is required to be a

time-stamped event is assigned to Class 3. When a Class 3 event occurs it shall not generate an

unsolicited response. Class 3 events shall be transmitted in response to a Class 3 poll or as part of an

Integrity Poll.

4.2.8 Static Data

This is data assigned as non time-stamped static data Class 0. The static data shall be transferred

during a poll for Class 0 data or as part of an Integrity Poll. Static data refers to the current state of the

data point and is not generated as the result of an event or change of state.

4.3 Assignment of Class

Data should be assigned a class as close to its point of origin as possible, in most cases the RTU or

PLC. Once data has been assigned a class it shall retain that class as it moves through the system.

Table 1: Class data reporting

Reported in Specific

Object Poll

(other than events)

Reported in Class

Poll

(Integrity Poll)

Reported in Event

poll

Unsolicited

No Class Yes No No No

Class 0 Yes Yes No No

Class 1 No Yes Yes Yes

Class 2 No Yes Yes Yes

Class 3 No Yes Yes Yes (not

allowed for

Water

Corporation

data)


DNP3 Polling


Ver 1Rev 1


4.4 Indications (IINs)

Internal indications are a set of 16 flags that are returned with every response message from an

outstation. Included in these IINs are flags that indicate that there are class 1, 2 or 3 events in the

outstations event buffers that are waiting to be sent. These events are those that would not be sent as

unsolicited such as buffered events or where there are too many events to send in one DNP3 frame.

The master station may or may not request the outstation to transmit these events depending on

various factors.

Table 2 DNP3 Internal Indications

LSB

IIN1.0 All stations

IIN1.1 Class 1 events



IIN1.4 Need time

IIN1.5 Local control

IIN1.6 Device trouble

IIN1.7 Device restart

MSB

IIN2.0 Function code not supported

IIN2.1 Object unknown

IIN2.2 Parameter error

IIN2.3 Event buffer overflow

IIN2.4 Already executing

IIN2.5 Configuration corrupt

IIN2.6 Reserved

IIN2.7 Reserved


DNP3 Polling


Ver 1Rev 1


5 POINT INDEXES

5.1 General

Gaps in the point numbers in the DNP3 protocol will result in increased bandwidth requirements due

to the points requiring individual point index headers. The DNP3 Protocol Specification [B1] states

“Within a point type, gaps in the point index range are permissible, but should be avoided wherever

possible.”

It has been common practice for Water Corporation integrators to have a standard point index map for

the Schneider SCADAPack RTUs and to leave point gaps when the points are not required at a

particular installation.

Points that are optional, depending on the application, or which are not assigned to any class should

be located in the upper part of the address map.

DNP3 point indexes start at 0. In older Serck RTUs it was not possible to assign index 0 to a point and

they started at index 1. This has been corrected in later versions.

Any future devices should be configured so that the DNP3 indexes are contiguous and start at index 0.


DNP3 Polling


Ver 1Rev 1


6 DATA TRANSFER

6.1 Client and Server

The terms client and server may be used to define the software processes that run in devices. A server

is a device that delivers information, typically an RTU or a PLC. It is often called an outstation or

slave device in DNP3 terminology. A client is a device that requests information from a server,

typically a SCADA Master. A client is effectively a “customer” of the server.

6.2 Outstation-To-Master data transfer

Assuming a permanent connection, the ‘number of events’ and ‘time in buffer’ parameters for

Buffered Events may be configured to a low value. Configured this way most event data will be

transmitted as unsolicited responses, with the SCADA Master periodically polling the RTU for other

data.

The master station poll period shall be configurable and shall define the time it takes for the SCADA

Master to recognize a communications failure to the RTU.

6.3 Outstation-To-Outstation data transfer

Where data is to be transferred between outstations, the outstation storing the information shall run a

server, or slave, process and the RTU requiring the information shall run a client, or master, process.

Where the transfer of information is bi-directional then the RTUs shall run both the client and server

processes.

Assuming a permanent connection all RTU-to-RTU data shall be Urgent Data, with the client RTU

periodically polling the server RTU to check communications. This poll period shall be configurable.

A logic mechanism should be put in place so that a loss of communications between the two RTUs

will not result in an unsafe condition.

6.4 Data Concentrator-To-Master Station data transfer

A Data Concentrator is a device that acts as a master and polls outstations for data. The data is then

stored in the Data Concentrator for later forwarding to the SCADA Master. The point indexes

assigned by the Data Concentrator will probably be different from those assigned at the data source.

Data Concentrators may also act as protocol converters for example converting from the Modbus

protocol used by local control PLCs to the DNP3 protocol for transmission to the SCADA master.

Assuming non-permanent communications it is desirable to reduce the amount of communications

connections between the Data Concentrator and the SCADA Master. The ‘number of events’ and

‘time in buffer’ parameters for Buffered Events will be high to reduce the number of times the

outstation dials out to the master, The SCADA Master will periodically polling the Data Concentrator

for other data and to ensure the outstation is still active.

The poll periods shall be configurable for each Data Concentrator and shall define the time it takes for

the SCADA Master to recognise a communications failure to a Data Concentrator.

The quality flags and the DNP3 class of the data assigned at the source device shall be maintained by

the data concentrator.

A Data Concentrator may also be required to perform DNP3 addressed based routing. See section 6.6.


DNP3 Polling


Ver 1Rev 1


6.5 Outstation-To-Data Concentrator data transfer

Where the communications from the Scheme to the SCADA Master is not permanent (e.g. dial-up

PSTN or GSM) a Data Concentrator may be used to collect and process RTU data and send it back to

the SCADA Master..

The Data Concentrator shall run a client process that shall communicate with the RTUs in the scheme.

Assuming a permanent connection most data will be transmitted as unsolicited responses, with the

Data Concentrator periodically polling the RTUs for other data.

The poll periods shall be configurable for each RTU and shall define the time it takes for the Data

Concentrator to recognize a communications failure to an RTU.

6.6 Data Routing

In order to transmit DNP3 Data through the network it is sometimes necessary for devices to route

messages based on the DNP3 Data Link Destination Address.

For example in order to remotely configure an RTU from the Master Station it may be necessary to

send DNP3 Data directly to it. In a situation where an intermediate RTU is used then it must route the

DNP3 Data received from the Master Station to the target RTU.

Both Data Concentrators and RTUs shall be required to perform DNP3 Data Routing.

Another example is the routing of messages from one RTU to another within the scheme. It is

preferable that this routing is done by the radios either configured as a talk through repeater, or using

a built in DNP3 routing functionality. If this is not possible, then either the Gateway or Data

Concentrator shall perform this function.

The use of TCP/IP communications is becoming more widespread. Data routing based on the IP

address is more flexible and preferred to routing based on DNP3 address. IP based routing allows for

multiple protocols, for example FTP and SNMP, to also be used. IP based communications has its

own issues with respect to security and IP address management. All IP based communications should

be referred to BaTS for design and management.


DNP3 Polling


Ver 1Rev 1


7 DATA TRANSFER FAILURE AND RECOVERY

7.1 Retries

In the event of an unsuccessful data transaction the initiating device, either client or server, shall

perform up to two Application Layer retries (three transactions in total). Data Link Layer retries shall

not be used. If the three transactions fail then the data transfer is considered to have failed.

7.2 Failures

If the Data Transfer has failed then the initiating device shall ‘back-off’ and attempt to re-establish

communications with the failed device at configurable intervals. For a non-permanent

communications connection this interval should be chosen carefully as it may cause many

unnecessary connections under failure conditions.

When a failure occurs the initiating device shall raise a communications alarm. In some cases an

outstation device will be configured to expect to be polled within a pre-configured period (e.g. an

RTU may expect to be polled by the SCADA Master). If the device is not polled within this period a

communication alarm shall be raised and the outstation device should change to the standby

communications channel if one is configured and available.

7.3 Recovery

When communications is re-established the communications link shall be reset in accordance with the

requirements of DNP3. This will be transparent to the user.


DNP3 Polling


Ver 1Rev 1


8 MASTER STATION COMMS REDUNDANCY

Master stations utilise redundant communications channels when communicating with critical

outstations. The purpose for this is that if the primary communications channel fails then the master

will switch over to the secondary, back up channel. In the case of ClearSCADA the secondary channel

is not monitored and is only used when the master detects that the primary channel has failed. In a

normal poll-response configuration this is not a problem: the master station will know that the channel

has failed because it is consistently polling the outstations in a round-robin scenario. If a channel does

not respond the master will switch to the backup channel.

Water Corporation makes extensive use of Unsolicited Reporting where the outstation initiates the

communications dialog. The master polls for data infrequently and then only to ensure that the

database held by the master is synchronised with the outstation database. This form of polling strategy

results in a very efficient use of bandwidth as, for the vast majority of transactions, data is only

transferred when an event has taken place.

Extensive use of Unsolicited Reporting does have its disadvantages and can lead to difficulties when

the master is not monitoring the secondary communications channel. If the primary communications

channel fails and the outstation tries to send a message the outstation will swap communications

channels. However the master will not be listening on the secondary channel and so will not be aware

of the failure. Change over to the secondary channel will only occur when the master attempts to poll

the outstation.

It is therefore important that the master station makes watchdog polls of the communications channels

at appropriate intervals. These polls will tell the master that the communications channel is active.

The interval of these polls is dependent on the outstation site. It should be based on the expected

unsolicited response interval and the criticality of the site.


DNP3 Polling


Ver 1Rev 1


9 DATA STANDARDS

SCADA is the means by which data is gathered from the remote devices for use by the Water

Corporation’s business applications. The Dynamic Field Data Collection Standard (DFDCS) (Docs

#393540) defines the minimum data requirements for Water Corporation’s business applications. The

type of data, the frequency of measurement, units of measure, accuracy, etc are defined in this

document. The DFDCS is an evolving document and is subject to change. At the time of writing the

DFDCS was not complete however it provides a substantial amount of information on most of Water

Corporation’s business applications data requirements.

It should be noted that not all data defined in the DFDSC is required to be gathered by SCADA and it

may be gathered by some other means, eg site visit, if appropriate. Also the DFDSC does not define

the data required for operational or maintenance purposes.


DNP3 Polling


Ver 1Rev 1


10 INPUT/OUTPUT POINT DEFINITIONS

In addition to the DFDCS, the I/O points that should be mapped to the DNP3 protocol can be found in

the Object I/O List that is downloadable from the version control application called MDT Autosave.

Only registered users may access Autosave. People wishing to become registered may apply to the

SCADA Help Desk.

An example of a page from the Object I/O List is shown in Appendix A. Note that the internal points,

that is points that are derived, number from 50,000. This is because the eNet RTU stores all its point

information for the communications, physical I/O and process variables in a database that is based on

the DNP3 object types. Consequently all the points in the eNet must have a DNP3 address regardless

of whether or not the point is reported to the master station. The internal points are located at the top

end of the point index map so as to allow for “real” points below.

This type of point mapping is not ideal, does not comply with the recommendations of the DNP3

Users Group and should not be used for other manufacturers’ RTUs or PLCs.


DNP3 Polling


Ver 1Rev 1


11 APPENDIX A – SAMPLE I/O LIST

Explanation notes:

0 means Class 0 – non-event data

1T means Event Class 1, Triggered or Urgent (Unsolicited)

2B means Event Class 2, Buffered

3B means Event Class 3, Buffered

L means Local (not assigned to any class)

Version 1.00.100

10 April 2008

General Physical SCADA PI Functional

Description Input/Output Type

IED Tag P&ID Tag Units Used Point

No Min Raw

Max Raw Min EU Max EU Point No Class DB DC

Point No

Equip.

Name Point Name State 0 State 1 Severity Tag Location

ISaGRAF 1 Halted

Internal RTU Digital Input

0 0 0 0 50100 1T 0 RTU Program 1 State

Running Halted Urgent Yes

ISaGRAF 2 Halted


0 0 0 0 50101 L 0 RTU Program 2 State

Running Halted Urgent

Local IO Module Failure


0 0 0 0 50205 1T 0 RTU LIO Module Normal Failure Urgent Yes

Local IO RTU Supply Low


0 0 0 0 50206 1T 0 RTU LIO Supply Voltage

Healthy Low Urgent Yes

Local IO Calibration Parameters Invalid


0 0 0 0 50208 2B 0 RTU LIO Calibration

Normal Failure Warning Yes

Remote IO 1 Module Failure


0 0 0 0 50209 L 0 RTU RIO 1 Module

Normal Failure Urgent

Remote IO 1 RTU Supply Low


0 0 0 0 50210 L 0 RTU

RIO 1 Supply Voltage

Healthy Low Warning

Remote IO 1 Calibration Parameters Invalid


0 0 0 0 50212 L 0 RTU RIO 1 Calibration

Normal Failure Warning

Configuration Changed by RTUConfig


0 0 0 0 50204 2B 0 RTU

Configuration Status

Normal Change In Progress

Event No

RTU Type Internal RTU 16 bit Analog Input

-

32767

32767 -32767 32767 50000 RTU Type No

Firmware Revision

Internal RTU 16 bit Analog Input

0 32767 0 32767 50001 RTU Firmware No

RTU Uptime Internal RTU 32 bit Analog Input

Long Period

0 214748364

7 0

2147483647

50010 RTU Uptime No

RTU Configuration Revision


0 214748364

7 0

2147483647

50050 RTU Configuration Revision

No

RTU Input Voltage

Internal RTU Short Float Input

V

0 30 0 30 50060 2B 0.166

% RTU

Input Voltage

Warning Yes

RTU Serial Number


0 214748364

7 0

2147483647

50082 RTU Serial Number

No

ISaGRAF 1 Version Number


0 1000 0 1000 52000 RTU Program 1 Version

No

ISaGRAF 2 Version Number


0 1000 0 1000 52007 RTU Program 2 Version


DNP3 Polling


Ver 1Rev 1


ISaGRAF 1 Application Name

Internal RTU String

50100 RTU

Program 1 Name

No

ISaGRAF 2 Application Name

Internal RTU String

50101 RTU

Program 2 Name

Reset Reason SCADA Master 32 bit Analog Input

RT00001_STA1

0 1023 0 1023 1000 2B 1 RTU Reset Reason

Yes

EOF


DNP3 Polling


Ver 1Rev 1


Version 1.00.100

10 April 2008

General Physical SCADA PI Functional

Description Input/Output Type

IED Tag P&ID Tag

Units Used Point No

Min Raw

Max Raw

Min EU

Max EU

Point No Class DB DC

Point No

Equip. Name Point Name State 0 State 1 Severity Tag Location

Equipment 1 Start Requested

SCADA Master Digital Input

ZM00000_RTR1 ZC

* 2B * Zone Control.Equipment 1

Requested Off On Event No



ZM00000_RTR2 ZC





ZM00000_RTR3 ZC





ZM00000_RTR4 ZC





ZM00000_RTR5 ZC



Equipment 1 Comms State


ZM00000_COM01A


Comms State Healthy Fault Warning No



ZM00000_COM02A





ZM00000_COM03A





ZM00000_COM04A





ZM00000_COM05A



Equipment 1 Inhibit


ZM00000_INH01


Inhibit Inactive Active Event No

Equipment 2 Inhibit


ZM00000_INH02



Equipment 3 Inhibit


ZM00000_INH03



Equipment 4 Inhibit


ZM00000_INH04



Equipment 5 Inhibit


ZM00000_INH05



Equipment 1 Force Start

SCADA Master Digital Output Pulse

ZM00000_FRC1C

* 0 * Zone Control.Equipment 1

Force Start

No



ZM00000_FRC2C


Force Start

No



ZM00000_FRC3C


Force Start

No



ZM00000_FRC4C


Force Start

No



ZM00000_FRC5C


Force Start

No


DNP3 Polling


Ver 1Rev 1


Equipment 1 Current Start Setpoint

SCADA Master 32 bit Analog Input

ZM00000_STR1 m

0 1000

0 0 x * 2B 1 *

Zone Control.Equipment 1

Start SP No

Equipment 1 Current Stop Setpoint


ZM00000_STP1 m

0 1000

0 0 x * 2B 1 *


Stop SP No



ZM00000_STR2 m

0 1000

0 0 x * 2B 1 *


Start SP No



ZM00000_STP2 m

0 1000

0 0 x * 2B 1 *


Stop SP No



ZM00000_STR3 m

0 1000

0 0 x * 2B 1 *


Start SP No



ZM00000_STP3 m

0 1000

0 0 x * 2B 1 *


Stop SP No



ZM00000_STR4 m

0 1000

0 0 x * 2B 1 *


Start SP No



ZM00000_STP4 m

0 1000

0 0 x * 2B 1 *


Stop SP No



ZM00000_STR5 m

0 1000

0 0 x * 2B 1 *


Start SP No



ZM00000_STP5 m

0 1000

0 0 x * 2B 1 *


Stop SP No

On Peak Start Time

SCADA Master 32 bit Analog Output

ZM00000_LTR01SC

0 2359 0 235

9 * 0 * Zone Control On Peak Time

No

Off Peak Start Time


ZM00000_LTR02SC

0 2359 0 235

9 * 0 * Zone Control Off Peak Time

No

Equipment 1 Off Peak Start Setpoint


ZM00000_STR01C

m

0 1000

0 0 x * 0 *


Off Peak Start SP

No

Equipment 1 Off Peak Stop Setpoint


ZM00000_STP01C

m

0 1000

0 0 x * 0 *


Off Peak Stop SP

No

Equipment 1 On Peak Start Setpoint


ZM00000_STR02C

m

0 1000

0 0 x * 0 *


On Peak Start SP

No

Equipment 1 On Peak Stop Setpoint


ZM00000_STP02C

m

0 1000

0 0 x * 0 *


On Peak Stop SP

No



ZM00000_STR03C

m

0 1000

0 0 x * 0 *


Off Peak Start SP

No



ZM00000_STP03C

m

0 1000

0 0 x * 0 *


Off Peak Stop SP

No



ZM00000_STR04C

m

0 1000

0 0 x * 0 *


On Peak Start SP

No



ZM00000_STP04C

m

0 1000

0 0 x * 0 *


On Peak Stop SP

No



ZM00000_STR05C

m

0 1000

0 0 x * 0 *


Off Peak Start SP

No

Equipment 3 SCADA Master ZM00000_STP05C m 0 1000 0 x * 0 * Zone Off Peak Stop No


DNP3 Polling


Ver 1Rev 1


Off Peak Stop Setpoint

32 bit Analog Output

0 Control.Equipment 3

SP



ZM00000_STR06C

m

0 1000

0 0 x * 0 *


On Peak Start SP

No



ZM00000_STP06C

m

0 1000

0 0 x * 0 *


On Peak Stop SP

No



ZM00000_STR07C

m

0 1000

0 0 x * 0 *


Off Peak Start SP

No



ZM00000_STP07C

m

0 1000

0 0 x * 0 *


Off Peak Stop SP

No



ZM00000_STR08C

m

0 1000

0 0 x * 0 *


On Peak Start SP

No



ZM00000_STP08C

m

0 1000

0 0 x * 0 *


On Peak Stop SP

No



ZM00000_STR09C

m

0 1000

0 0 x * 0 *


Off Peak Start SP

No



ZM00000_STP09C

m

0 1000

0 0 x * 0 *


Off Peak Stop SP

No



ZM00000_STR10C

m

0 1000

0 0 x * 0 *


On Peak Start SP

No



ZM00000_STP10C

m

0 1000

0 0 x * 0 *


On Peak Stop SP

No

EOF


DNP3 Polling


Ver 1Rev 1


END OF DOCUMENT

DNP3 Polling

Documents

Transcript of DNP3 Polling