Get a Live Demo

You need to see DPS gear in action. Get a live demo with our engineers.

Get the DNP3 White Paper

Download our free DNP3 tutorial.

An introduction to DNP3 from your own perspective.

DPS is here to help.


Have a specific question? Ask our team of expert engineers and get a specific answer!

Learn the Easy Way

Sign up for the next DPS Factory Training!

DPS Factory Training

Whether you're new to our equipment or you've used it for years, DPS factory training is the best way to get more from your monitoring.

Reserve Your Seat Today

DNP3 Tutorial Part 1: An Introduction to DNP3

What is DNP3? DNP3, or DNP 3.0, is a communications protocol used in SCADA and remote monitoring systems. It is widely used because it is an open standard protocol. This means that any manufacturer can develop DNP3 equipment that is compatible with other DNP3 equipment.

Feel free to download the tutorial, or contact us for expedited monitoring.

Distributed Network Protocol (DNP or DNP3) has achieved a large-scale acceptance since its introduction in 1993. This protocol is an immediately deployable solution for monitoring remote sites because it was developed for communication of critical infrastructure status, allowing for reliable remote control.

GE-Harris Canada (formerly Westronic, Inc.) is generally credited with the seminal work on the protocol. This protocol is, however, currently implemented by an extensive range of manufacturers in a variety of industrial applications, such as electric utilities.

DNP3 is composed of three layers of the OSI seven-layer functions model. These layers are application layer, data link layer, and transport layer. Also, DNP3 can be transmitted over a serial bus connection or over a TCP/IP network.

The DNP3 Protocol Specification is Based An Object Model

DNP3 is based on an object model. This model reduces the bit mapping of data that is traditionally required by other less object-oriented protocols. It also reduces the wide disparity of status monitoring and control paradigms generally found in protocols that provide virtually no pre-defined objects.

Purists of these alternate protocols would insist that any required object can be 'built' from existing objects. Having some pre-defined objects though makes DNP3 a somewhat more comfortable design and deployment framework for SCADA engineers and technicians.

DNP3 uses a Master/Remote Model

DNP3 is typically used between centrally located masters and distributed remotes. The master provides the interface between the human network manager and the monitoring system. The remote (RTUs and intelligent electronic devices) provides the interface between the master and the physical device(s) being monitored and/or controlled.

DNP3 used in a master/remote architecture
A typical DNP3 master/remote monitoring system architecture.

The master and remote both use a library of common objects to exchange information. The DNP3 protocol contains carefully designed capabilities. These capabilities enable it to be used reliably even over media that may be subject to noisy interference.

The DNP3 protocol is a polled protocol. When the master station connects to a remote, an integrity poll is performed. Integrity polls are important for DNP3 addressing. This is because they return all buffered values for a data point and include the current value of the point as well.

Main DNP3 Capabilities

As an intelligent and robust SCADA protocol, DNP3 gives you many capabilities. Some of them are:

  • DNP3 can request and respond with multiple data types in single messages
  • Response without request (unsolicited messages)
  • It allows multiple masters and peer-to-peer operations
  • It supports time synchronization and a standard time format
  • It includes only changed data in response messages