DNP3 DataSheet V013

8/6/2019 DNP3 DataSheet V013

http://slidepdf.com/reader/full/dnp3-datasheet-v013 1/2

DNP 3 ProtocolSlave & Master

 Applications and Benefits

SCADAPack controllers and gas flowcomputers are field-proven in a widerange of industries and applicationsaround the world.

The easy-to-use Control MicrosystemsDNP3 interface allows for rapidintegration of SCADAPack controllersand gas flow computers.

Some of the benefits of using DNP3protocol include:

I Unsolicited Reporting – data is sent

when it changes.I Prioritized Data Reporting.

I Multiple Masters – slaves are able toreport events to more than onemaster/host.

I Time Stamped Events.

I Data Logging – storage of 10,000events in a SCADAPack 100 controllerto >30,000 events in a SCADAPack32or 300 Series controller.

I Extended PLC Addressing – up to65,535 PLCs.

I Extended Object-Type Addressing –up to 65,535 of each object type.

I Large Messages – large messagesize enhances event uploads.

I Remote PLC Configuration.

I DNP device profile available fromControl Microsystems.

Easily Configured

DNP3 is configured in TelePACE,ISaGRAF and RealFLO programmingenvironments with an easy-to-usedialog. Application and data layers,master poll and mimic mode, addressmapping, message routing and IOpoints are all configured on the samedialog. The majority of DNP3applications can be configured usingthis dialog, thereby eliminating theneed for additional logic programming.

TelePACE, ISaGRAF, RealFLO and

Firmware Loader applications alsosupport DNP connections tocontrollers. Controller firmware andapplication programs can bedownloaded to the controller and logicexecution monitored on-line using aDNP connection.

 Additional DNP Functions

Custom logic functions are availablewhen additional DNP functionality isrequired. These functions allow thePLC logic application to trigger various

DNP events, including class polls, clocksynchronization and unsolicitedresponse messages.

Features:

Logic programming not required for most DNPapplications

Easily configured using TelePACE, ISaGRAF andRealFLO environments

DNP Master and Slave modes supported

Unsolicited messaging supported

Change-of-State and Log-All event types supported

Available through Ethernet and RS232/RS485 serialcommunication ports

w w w . c o n t r o l m i c r o s y s t e m s . c o m

CONTROL

MICROSYSTEMS Product Data Sheet

Control Microsystems’ complete familyof SCADAPack programmable logic con-

trollers and gas flow computers areavailable with DNP3 Protocol.

Today’s increasingly complex SCADAnetworks demand that data-transferprotocols be sufficiently flexible tomeet communication challenges whileremaining easy-to-configure. ControlMicrosystems’ intelligentimplementation of the DNP3 protocolsucceeds on both counts.

Overview

DNP3 - Distributed Network Protocol isa standards-based communicationsprotocol developed to enhanceinteroperability among systems in theelectric utility, oil & gas, water/wastewater and security industries. It is aflexible and efficient, non-proprietary,layered protocol that offers higherdata-transfer integrity than mostconventional communicationprotocols.

It is suitable for implementationanywhere within a SCADA environment,

including PLC to IED, master-to-remote,peer-to-peer and networkcommunication applications.

The DNP3 User Group, (www.dnp.org),ensures continuous improvement of the protocol in the ever-changingtechnological climate of industrialcontrol.

8/6/2019 DNP3 DataSheet V013

http://slidepdf.com/reader/full/dnp3-datasheet-v013 2/2

DNP 3 Protocol Product Data Sheet

In mimic mode the master maintains‘images’ of remote site data for uploadby the SCADA host (or other master).This is recommended in applicationswhere the slave PLCs are on low speed

or non-continuous links (eg. Dial-up).

This allows the master to respond to

SCADA host requests for remote slavedata from its buffered images asshown above.

In applications where dataconcentration is required, the masteris able to map remote data to its ownlocal registers. This is accomplishedusing the master-mapping mode asshown below.

Slave ModeAll SCADAPack controllers and gas flowcomputers support DNP3 slavefunctionality. When configured as aDNP3 slave, the PLC can be polled for

static data (Class 0), or event data(Class 1, 2, 3) by a DNP master. ThePLC is also able to send unsolicitedmessages containing event data to aDNP master and route messagesto/from other DNP PLCs and DNPdevices.

Another set of dedicated functionblocks allows the PLC logic to accessDNP diagnostic information includingDNP connection status, event-count bypoint type and class, port

communication statistics and stationmessage statistics.

Master Mode

SCADAPack 32 and 300 Seriescontrollers support DNP3 masterfunctionality. A DNP master caninitiate polls for static data (Class 0)and event data (Class 1, 2, 3) andaccept unsolicited event data fromslave PLCs.

A typical DNP application consists of aDNP master controller, routinely polling

a number of DNP slave controllers asshown below.

In many applications the DNP masterPLC or DNP slave PLC is simplyrequired to route messages to/from aSCADA host as shown below.

In addition to message routing, masterfunctionality also includes dataconcentration, using mimic andmapping modes.

DNP MasterController

DNP SlaveController #1

DNP SlaveController #2

DNP SlaveController #3

DNP SlaveController #4

DNP SlaveController #1

DNP SlaveController #2

DNP SlaveController #3

DNP Slave orMaster Router

Controller

RoutedMessages

SCADA Host

Local Data

Unsolicited Messages

An important feature of DNP3 is theability for the PLC to generateunsolicited messages sent to themaster PLC/host based upon a local PLC

event. An application layer menu allowsevent-reporting rules for each objectclass (1-3) to be defined.

Reporting Rules – These are defined foreach object class and include:

I Enable/Disable – Turns unsolicitedreporting On/Off 

I Hold Time – period seconds

I Hold Count – number of unreadevents in the PLC history

Object Classes

Data object classes allow for themanagement of message content andmessage triggering based upon user-determined priority of the data. The dataclasses are assigned independently of the data priority.

Supported DNP object classes could beconfigured with the following prioritystructure:

I Class 1 – highest priority

I Class 2 – medium priority

I Class 3 – lowest priority

Class 0 is always a reference used by amaster to read all DNP data objects.These are instantaneous/last-readvalues. The master/host polls for Class 0data objects, on an infrequent basis andafter each restart of the master or slave.

Ethernet and Serial Communication

DNP3 is fully supported on allSCADAPack controller communicationports, including the serial RS-232 andRS-485 ports as well as the EthernetTCP/IP port of the SCADAPack 32 and300 Series controllers.

DNP SlaveController #1

DNP SlaveController #2

DNP SlaveController #3

DNP MasterMIMIC-Enabled

Controller

SCADA Host

Image#1

Image#2

Image#3

Local Data

DNP SlaveController #1

DNP SlaveController #2

DNP SlaveController #3

DNP MasterMIMIC-Disabled

Controller

SCADA Host

Local Data(images have been mapped)

CONTROL

MICROSYSTEMS w w w . c o n t r o l m i c r o s y s t e m s . c o m

Within North America: (888) 267-2232 I Outside North America: (613) 591-1943 I Ottawa I Calgary I Denver I Houston I Melbourne I Leiden

Control Microsystems reserves the right to change product specifications without notice. Printed in Canada I V013 I M01011-26