What is DNP3?

DNP3 stands for Distributed Network Protocol 3 and is an open communication protocol for remote monitoring and control, standardised as IEEE 1815. It connects control centres and SCADA systems (Supervisory Control and Data Acquisition) with remote terminal units, plant controllers and field devices. DNP3 is particularly widespread in the North American electric utility sector.

DNP3 at a glance

• It transmits measurements, operating states, events and control commands between control centres and energy systems.
• In addition to regular polling, the protocol supports event-based reporting, depending on device capabilities and configuration.
• Successful integration requires coordinated data point definitions and security functions; DNP3 support alone is not sufficient.

How does DNP3 communication work?

A master, such as a control centre, communicates with an outstation, such as a remote terminal unit or plant controller at the site. Communication can use serial connections or an IP network.

The outstation provides information such as power, voltage, current, meter readings, switch positions and fault indications. Depending on the data object, timestamps and quality flags accompany the values. This allows the control centre to determine, for example, when a state change occurred or whether a measurement is flagged as valid.

The master can request current values and stored events. Events occur, for example, when a switch changes state or a measurement changes by a sufficiently large amount. If both sides support and enable unsolicited responses, the outstation can also report changes without a preceding individual request.

In the opposite direction, the master sends switching commands or setpoints. With Select before Operate, a command is first selected and then triggered by a separate operate command. This procedure replaces neither authorisation checks nor electrical protection functions.

Where is DNP3 used?

In power grid operations, DNP3 connects control centres with geographically distributed stations. Operators can monitor operating states, detect faults and remotely switch suitable equipment.

For photovoltaic systems and battery energy storage systems, DNP3 can provide the interface between the installation and a supervisory control centre. For example, a plant controller reports the current active power and receives a new power setpoint. The local control system checks the setpoint against plant limits and implements it through the relevant device interfaces.

DNP3 transports data and commands. Operational optimisation, local control and electrical protection remain the responsibility of the connected systems.

Technical requirements and limitations of DNP3

Event reporting can reduce data traffic compared with frequent polling of all current values. Timestamped messages also help reconstruct the sequence of operating events and faults.

A coordinated data point list is essential. Both sides must consistently configure data point types, indices, scaling, units and command meanings. Sign conventions are also critical: a positive active power setpoint must not be interpreted differently by the sender and receiver.

Reliable timestamps require a dependable time reference. Event buffers have limited capacity. Extended communication outages or excessive event volumes can cause buffers to overflow and event data to be lost.

Independently of event buffering, the plant control system needs a defined response to communication failures and missing or outdated setpoints.

DNP3 alone does not ensure communication security. Secure Authentication Version 5 (SAv5) provides authentication and integrity checking for security-critical messages but does not encrypt the payload data.

The newer DNP3 Security Layer (DNP3-SL, formerly SAv6) additionally supports message encryption. This does not imply automatic availability in existing devices. The security functions actually supported and enabled must be checked for the devices used and the entire communication path.

What role does DNP3 play in EcoPhi projects?

EcoPhi uses DNP3 to communicate with supervisory systems, including in projects in South Africa. Its technical role is to provide operating data and receive external setpoints for local plant control.

The specific connection is coordinated for each project. This includes communication roles, data point lists, security requirements and available device interfaces. Which DNP3 functions are available directly or through a protocol converter depends on the devices used and the system architecture.

DNP3 in summary

It enables structured remote monitoring and control of distributed energy systems. Its practical value depends on correctly coordinated data point mapping, suitable event handling and secure communication. Implementing received setpoints remains the responsibility of the plant control system.

Frequently asked questions about DNP3

Is DNP3 a SCADA system?

No. DNP3 is a communication protocol that a SCADA system can use to exchange data with energy installations. Visualisation, archiving and operator interfaces are provided by the respective system.

Does DNP3 require an internet connection?

No. DNP3 can operate over serial connections or private IP networks. A connection to the public internet is not required.

Can existing systems be connected through a protocol converter?

In principle, yes, provided the converter supports the required functions of both protocols. In particular, it is necessary to verify that measurements, quality flags, timestamps and commands can be mapped correctly.