DNP3 DataSheet V013
Content
CONTROL MICROSYSTEMS
Product Data Sheet
DNP 3 Protocol
Slave & Master Features:
Logic programming not required for most DNP applications Easily configured using TelePACE, ISaGRAF and RealFLO 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 serial communication ports Control Microsystems’ complete family of SCADAPack programmable logic controllers and gas flow computers are available with DNP3 Protocol. Today’s increasingly complex SCADA networks demand that data-transfer protocols be sufficiently flexible to meet communication challenges while remaining easy-to-configure. Control Microsystems’ intelligent implementation of the DNP3 protocol succeeds on both counts. Overview DNP3 - Distributed Network Protocol is a standards-based communications protocol developed to enhance interoperability among systems in the electric utility, oil & gas, water/waste water and security industries. It is a flexible and efficient, non-proprietary, layered protocol that offers higher data-transfer integrity than most conventional communication protocols. It is suitable for implementation anywhere within a SCADA environment, including PLC to IED, master-to-remote, peer-to-peer and network communication applications. The DNP3 User Group, (www.dnp.org), ensures continuous improvement of the protocol in the ever-changing technological climate of industrial control. Applications and Benefits SCADAPack controllers and gas flow computers are field-proven in a wide range of industries and applications around the world. The easy-to-use Control Microsystems DNP3 interface allows for rapid integration of SCADAPack controllers and gas flow computers. Some of the benefits of using DNP3 protocol include: I Unsolicited Reporting – data is sent when it changes. I Prioritized Data Reporting. I Multiple Masters – slaves are able to report events to more than one master/host. I Time Stamped Events. I Data Logging – storage of 10,000 events in a SCADAPack 100 controller to >30,000 events in a SCADAPack32 or 300 Series controller. I Extended PLC Addressing – up to 65,535 PLCs. I Extended Object-Type Addressing – up to 65,535 of each object type. I Large Messages – large message size enhances event uploads. I Remote PLC Configuration. I DNP device profile available from Control Microsystems. Easily Configured DNP3 is configured in TelePACE, ISaGRAF and RealFLO programming environments with an easy-to-use dialog. Application and data layers, master poll and mimic mode, address mapping, message routing and IO points are all configured on the same dialog. The majority of DNP3 applications can be configured using this dialog, thereby eliminating the need for additional logic programming. TelePACE, ISaGRAF, RealFLO and Firmware Loader applications also support DNP connections to controllers. Controller firmware and application programs can be downloaded to the controller and logic execution monitored on-line using a DNP connection. Additional DNP Functions Custom logic functions are available when additional DNP functionality is required. These functions allow the PLC logic application to trigger various DNP events, including class polls, clock synchronization and unsolicited response messages.
w w w. c o n t r o l m i c r o s y s t e m s . com
SCADA Host
DNP 3 Protocol
Another set of dedicated function blocks allows the PLC logic to access DNP Master DNP diagnostic information including Controller DNP connection status, event-count by point type and class, port communication statistics and station DNP Slave DNP Slave DNP Slave DNP Slave message statistics. Controller #3 Controller #4 Controller #1 Controller #2 Master Mode SCADAPack 32 and 300 Series controllers support DNP3 master functionality. A DNP master can initiate polls for static data (Class 0) SCADA Host and event data (Class 1, 2, 3) and DNP Master accept unsolicited event data from MIMIC-Disabled Controller slave PLCs. Local Data A typical DNP application consists of a (images have been mapped) DNP master controller, routinely polling a number of DNP slave controllers as shown below.
DNP Slave Controller #1 DNP Slave Controller #2 DNP Slave Controller #3
DNP Master MIMIC-Disabled Controller
Product Data Sheet
Unsolicited Messages An important feature of DNP3 is the ability for the PLC to generate unsolicited messages sent to the master PLC/host based upon a local PLC event. An application layer menu allows event-reporting rules for each object class (1-3) to be defined. Reporting Rules – These are defined for each object class and include: I Enable/Disable – Turns unsolicited reporting On/Off I Hold Time – period seconds I Hold Count – number of unread events in the PLC history Object Classes Data object classes allow for the management of message content and message triggering based upon userdetermined priority of the data. The data classes are assigned independently of the data priority. Supported DNP object classes could be configured with the following priority structure: I Class 1 – highest priority I Class 2 – medium priority I Class 3 – lowest priority Class 0 is always a reference used by a master to read all DNP data objects. These are instantaneous/last-read values. The master/host polls for Class 0 data objects, on an infrequent basis and after each restart of the master or slave. Ethernet and Serial Communication DNP3 is fully supported on all SCADAPack controller communication ports, including the serial RS-232 and RS-485 ports as well as the Ethernet TCP/IP port of the SCADAPack 32 and 300 Series controllers.
Local Data (images have been mapped)
In mimic mode the master maintains ‘images’ of remote site data for upload by the SCADA host (or other master). DNP Slave DNP Slave DNP Slave Controller #1 Controller #2 Controller #3 This is recommended in applications where the slave PLCs are on low speed or non-continuous links (eg. Dial-up).
SCADA Host
DNP Master MIMIC-Enabled Controller
Image #1
Image #2
Image #3
Local Data
DNP Slave Controller #1
DNP Slave Controller #2
DNP Slave Controller #3
DNP Master Controller
SCADA Host
DNP Slave Controller #1
DNP Slave Controller #2
DNP Slave Controller #3
DNP Master MIMIC-Enabled DNP Slave Controller Controller #4
This allows the master to respond to DNP Master SCADA host requests for remote slave Controller SCADA Host data from its buffered images as shown above. DNP Slave or Master Router In applications where data Controller DNP Slave DNP Slave DNP Slave DNP concentration is required, Local Data Slave the Controller #4 master Routed Controller #1 Controller #2 Controller #3 Messages is able to map remote data to its own local registers. This is accomplished using the master-mapping mode as DNP Slave DNP Slave DNP Slave shown below.#1 Controller #2 Controller #3 Controller
SCADA Host DNP Master MIMIC-Disabled Controller
Image #1
Image #2
Image #3
Local Data
In many applications the DNP master DNP slave PLC DNP Slave DNP Slave PLC or DNPSlave Controlleris simply #3 Controller #1 #2 Controller required to route SCADA Host messages to/from a SCADA host as shown below. DNP Master
MIMIC-Disabled Controller
Local Data (images have been mapped)
SCADA Host Local Data (images have been mapped) DNP Slave or Master Router Controller Routed Messages DNP Slave Controller #1
DNP Slave Controller #1
DNP Slave Controller #2
DNP Slave Controller #3
DNP Slave Controller #2
Local Data DNP Slave Controller #3
DNP Slave Controller #1
DNP Slave Controller #2
SCADA Host
DNP Slave Controller #3
In addition to message routing, master DNP Master MIMIC-Enabled functionality also includes data Controller concentration, using mimic and Image Image Image Local Data mapping modes. #3 #1 #2
DNP Slave DNP Slave DNP Slave CONTROL #2 Controller #3 Controller #1 Controller MICROSYSTEMS
Slave Mode All SCADAPack controllers and gas flow SCADA Host computers support DNP3 slave functionality. When configured as a DNP Master MIMIC-Enabled DNP3 slave, the PLC can be polled for Controller staticImage (Class 0), or event data data Image Image (Class#1 2, 3) by a#3 master. The 1, #2 DNP Local Data PLC is also able to send unsolicited messages containing event data to a DNP master and route messages DNP Slave DNP Slave DNP Slave to/from Controller #1DNP PLCs and DNP other Controller #2 Controller #3 devices.
SCADA Host
Within North America: (888) 267-2232
SCADA Host
I
Outside North America: (613) 591-1943
Routed Messages
I
Controller Ottawa I Calgary
DNP Slave or Master Router
w w w. c o n t r o l m i c r o s y s t e m s . com
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
Local Data
DNP Slave or
Product Data Sheet
DNP 3 Protocol
Slave & Master Features:
Logic programming not required for most DNP applications Easily configured using TelePACE, ISaGRAF and RealFLO 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 serial communication ports Control Microsystems’ complete family of SCADAPack programmable logic controllers and gas flow computers are available with DNP3 Protocol. Today’s increasingly complex SCADA networks demand that data-transfer protocols be sufficiently flexible to meet communication challenges while remaining easy-to-configure. Control Microsystems’ intelligent implementation of the DNP3 protocol succeeds on both counts. Overview DNP3 - Distributed Network Protocol is a standards-based communications protocol developed to enhance interoperability among systems in the electric utility, oil & gas, water/waste water and security industries. It is a flexible and efficient, non-proprietary, layered protocol that offers higher data-transfer integrity than most conventional communication protocols. It is suitable for implementation anywhere within a SCADA environment, including PLC to IED, master-to-remote, peer-to-peer and network communication applications. The DNP3 User Group, (www.dnp.org), ensures continuous improvement of the protocol in the ever-changing technological climate of industrial control. Applications and Benefits SCADAPack controllers and gas flow computers are field-proven in a wide range of industries and applications around the world. The easy-to-use Control Microsystems DNP3 interface allows for rapid integration of SCADAPack controllers and gas flow computers. Some of the benefits of using DNP3 protocol include: I Unsolicited Reporting – data is sent when it changes. I Prioritized Data Reporting. I Multiple Masters – slaves are able to report events to more than one master/host. I Time Stamped Events. I Data Logging – storage of 10,000 events in a SCADAPack 100 controller to >30,000 events in a SCADAPack32 or 300 Series controller. I Extended PLC Addressing – up to 65,535 PLCs. I Extended Object-Type Addressing – up to 65,535 of each object type. I Large Messages – large message size enhances event uploads. I Remote PLC Configuration. I DNP device profile available from Control Microsystems. Easily Configured DNP3 is configured in TelePACE, ISaGRAF and RealFLO programming environments with an easy-to-use dialog. Application and data layers, master poll and mimic mode, address mapping, message routing and IO points are all configured on the same dialog. The majority of DNP3 applications can be configured using this dialog, thereby eliminating the need for additional logic programming. TelePACE, ISaGRAF, RealFLO and Firmware Loader applications also support DNP connections to controllers. Controller firmware and application programs can be downloaded to the controller and logic execution monitored on-line using a DNP connection. Additional DNP Functions Custom logic functions are available when additional DNP functionality is required. These functions allow the PLC logic application to trigger various DNP events, including class polls, clock synchronization and unsolicited response messages.
w w w. c o n t r o l m i c r o s y s t e m s . com
SCADA Host
DNP 3 Protocol
Another set of dedicated function blocks allows the PLC logic to access DNP Master DNP diagnostic information including Controller DNP connection status, event-count by point type and class, port communication statistics and station DNP Slave DNP Slave DNP Slave DNP Slave message statistics. Controller #3 Controller #4 Controller #1 Controller #2 Master Mode SCADAPack 32 and 300 Series controllers support DNP3 master functionality. A DNP master can initiate polls for static data (Class 0) SCADA Host and event data (Class 1, 2, 3) and DNP Master accept unsolicited event data from MIMIC-Disabled Controller slave PLCs. Local Data A typical DNP application consists of a (images have been mapped) DNP master controller, routinely polling a number of DNP slave controllers as shown below.
DNP Slave Controller #1 DNP Slave Controller #2 DNP Slave Controller #3
DNP Master MIMIC-Disabled Controller
Product Data Sheet
Unsolicited Messages An important feature of DNP3 is the ability for the PLC to generate unsolicited messages sent to the master PLC/host based upon a local PLC event. An application layer menu allows event-reporting rules for each object class (1-3) to be defined. Reporting Rules – These are defined for each object class and include: I Enable/Disable – Turns unsolicited reporting On/Off I Hold Time – period seconds I Hold Count – number of unread events in the PLC history Object Classes Data object classes allow for the management of message content and message triggering based upon userdetermined priority of the data. The data classes are assigned independently of the data priority. Supported DNP object classes could be configured with the following priority structure: I Class 1 – highest priority I Class 2 – medium priority I Class 3 – lowest priority Class 0 is always a reference used by a master to read all DNP data objects. These are instantaneous/last-read values. The master/host polls for Class 0 data objects, on an infrequent basis and after each restart of the master or slave. Ethernet and Serial Communication DNP3 is fully supported on all SCADAPack controller communication ports, including the serial RS-232 and RS-485 ports as well as the Ethernet TCP/IP port of the SCADAPack 32 and 300 Series controllers.
Local Data (images have been mapped)
In mimic mode the master maintains ‘images’ of remote site data for upload by the SCADA host (or other master). DNP Slave DNP Slave DNP Slave Controller #1 Controller #2 Controller #3 This is recommended in applications where the slave PLCs are on low speed or non-continuous links (eg. Dial-up).
SCADA Host
DNP Master MIMIC-Enabled Controller
Image #1
Image #2
Image #3
Local Data
DNP Slave Controller #1
DNP Slave Controller #2
DNP Slave Controller #3
DNP Master Controller
SCADA Host
DNP Slave Controller #1
DNP Slave Controller #2
DNP Slave Controller #3
DNP Master MIMIC-Enabled DNP Slave Controller Controller #4
This allows the master to respond to DNP Master SCADA host requests for remote slave Controller SCADA Host data from its buffered images as shown above. DNP Slave or Master Router In applications where data Controller DNP Slave DNP Slave DNP Slave DNP concentration is required, Local Data Slave the Controller #4 master Routed Controller #1 Controller #2 Controller #3 Messages is able to map remote data to its own local registers. This is accomplished using the master-mapping mode as DNP Slave DNP Slave DNP Slave shown below.#1 Controller #2 Controller #3 Controller
SCADA Host DNP Master MIMIC-Disabled Controller
Image #1
Image #2
Image #3
Local Data
In many applications the DNP master DNP slave PLC DNP Slave DNP Slave PLC or DNPSlave Controlleris simply #3 Controller #1 #2 Controller required to route SCADA Host messages to/from a SCADA host as shown below. DNP Master
MIMIC-Disabled Controller
Local Data (images have been mapped)
SCADA Host Local Data (images have been mapped) DNP Slave or Master Router Controller Routed Messages DNP Slave Controller #1
DNP Slave Controller #1
DNP Slave Controller #2
DNP Slave Controller #3
DNP Slave Controller #2
Local Data DNP Slave Controller #3
DNP Slave Controller #1
DNP Slave Controller #2
SCADA Host
DNP Slave Controller #3
In addition to message routing, master DNP Master MIMIC-Enabled functionality also includes data Controller concentration, using mimic and Image Image Image Local Data mapping modes. #3 #1 #2
DNP Slave DNP Slave DNP Slave CONTROL #2 Controller #3 Controller #1 Controller MICROSYSTEMS
Slave Mode All SCADAPack controllers and gas flow SCADA Host computers support DNP3 slave functionality. When configured as a DNP Master MIMIC-Enabled DNP3 slave, the PLC can be polled for Controller staticImage (Class 0), or event data data Image Image (Class#1 2, 3) by a#3 master. The 1, #2 DNP Local Data PLC is also able to send unsolicited messages containing event data to a DNP master and route messages DNP Slave DNP Slave DNP Slave to/from Controller #1DNP PLCs and DNP other Controller #2 Controller #3 devices.
SCADA Host
Within North America: (888) 267-2232
SCADA Host
I
Outside North America: (613) 591-1943
Routed Messages
I
Controller Ottawa I Calgary
DNP Slave or Master Router
w w w. c o n t r o l m i c r o s y s t e m s . com
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
Local Data
DNP Slave or
