DNP3 (Distributed Network Protocol 3) is the dominant SCADA communication protocol for electric and water utilities. It was designed for reliable communication with remote, unattended field equipment over potentially unreliable communication links and is standardized by IEEE (IEEE 1815).

Does Mango by Radix IoT support DNP3?

Yes. Mango by Radix IoT includes a native DNP3 driver that functions as a DNP3 master station, supporting both DNP3 serial and DNP3 TCP/IP communication.

What types of DNP3 data objects does Mango by Radix IoT support?

Mango by Radix IoT supports binary inputs (single and double-bit), analog inputs (16-bit, 32-bit, floating point), counters, binary and analog events with timestamps, and binary and analog outputs.

Can Mango by Radix IoT receive DNP3 unsolicited responses?

Yes. Mango by Radix IoT processes unsolicited responses from DNP3 outstations, enabling immediate event reporting without waiting for a polling cycle.

Does Mango by Radix IoT support DNP3 over radio modem networks?

Yes. Mango by Radix IoT supports DNP3 serial communication, which is used with radio modems, dial-up modems, and other serial communication media common in utility SCADA.

What happens to DNP3 data during a communication outage?

Mango by Radix IoT polls Class 1, 2 and 3 events on a normal cycle and resumes that poll when the link is restored. Where the outstation has retained events in its own buffer, some of those records may still be received. There is no dedicated catch-up process that reconstructs the outage period, and events lost to buffer overflow on the device cannot be recovered.

What is NERC CIP and does DNP3 relate to it?

NERC CIP (Critical Infrastructure Protection) is the cybersecurity standard for bulk electric utilities in North America. DNP3 Secure Authentication (SA) is one mechanism utilities use to meet NERC CIP communication security requirements. Contact Radix IoT for guidance on NERC CIP-relevant monitoring configurations.

Can Mango by Radix IoT translate DNP3 data to other protocols?

Yes. Data collected over DNP3 can be republished through standard integrations and configurable publishers, including Modbus IP, BACnet IP, and the REST API. Systems that do not speak DNP3 can consume the same data in a format they do support.

DNP3 Monitoring with Mango by Radix IoT

Q: Is the DNP3 driver a separate purchase?

No. All protocol drivers are included in a standard Mango by Radix IoT installation and covered by the license. There are no separate driver licenses or per-protocol fees.

What Is DNP3

DNP3 (Distributed Network Protocol 3) is a communication protocol developed in the early 1990s for utility SCADA systems. It was designed to address the specific requirements of supervisory communication with remote, unattended field equipment over unreliable communication links — characteristics common in electric grid, water, and pipeline infrastructure.

DNP3 is standardized by IEEE (IEEE 1815) and widely adopted in North American electric utilities and water systems. It remains the dominant protocol for legacy utility SCADA and for new installations in environments where DNP3 equipment is already fielded.

DNP3 is used to monitor and control:

Electric utility substations: circuit breakers, reclosers, capacitor banks, transformers
Remote Terminal Units (RTUs) at unmanned field sites
Water and wastewater pump stations: pumps, valves, level sensors, flow meters
Natural gas pipeline SCADA: compressor stations, regulator stations, storage facilities
Hydroelectric and other generation assets
Distribution automation and smart grid equipment

DNP3 Protocol Features

DNP3 includes capabilities specifically designed for utility and critical infrastructure environments:

Unsolicited Responses

Field devices can send data to the master station (monitoring system) without being polled — when a significant event occurs (breaker trip, threshold crossing, equipment alarm), the RTU reports it immediately. This reduces communication overhead and enables faster event response.

Event Buffering

If communication to a field site is interrupted, the RTU continues logging events locally in its own buffer. When communication is restored, a master station polling for events may receive those buffered records in chronological order. Recovery depends on the outstation: buffers are finite, and events are lost if the buffer overflows before the link is restored.

Data Quality Indicators

DNP3 attaches quality flags to data values, indicating whether a value is online, offline, overrange, or was communicated with errors. Monitoring systems can distinguish between a “good” reading and a measurement that should be treated with caution.

Time Synchronization

DNP3 supports time-stamped event data, enabling the master station to reconstruct the exact sequence of events at a remote site even when multiple events occur within the same communication cycle.

DNP3 Secure Authentication (SA)

DNP3 Secure Authentication (SA), now standardized as part of IEEE 1815-2012, adds challenge/response authentication between the master and outstation to protect against unauthorized command injection. Critical for compliance with NERC CIP cybersecurity standards.

DNP3 Transport Variants

Variant	Transport	Typical Use
DNP3 Serial	RS-232 or RS-485	Direct serial connection to RTU; radio modem networks; legacy infrastructure
DNP3 TCP/IP	Ethernet / TCP	Modern substations with Ethernet connectivity; DNP3 over IP networks
DNP3 UDP/IP	UDP	Environments where UDP communication is preferred

Industries That Use DNP3

Electric Utilities

Electric transmission and distribution utilities use DNP3 for substation automation — monitoring transformer load, circuit breaker status, recloser operations, voltage and current measurements, and protective relay events. DNP3 is the standard protocol for SCADA communication between the utility’s energy management system (EMS) or SCADA master and field substations.

Water and Wastewater Utilities

Water utilities use DNP3 for pump station SCADA — monitoring well levels, storage tank levels, pump run status, flow rates, pressure, and water quality parameters. Remote pump stations report via DNP3 to a central operations center.

Natural Gas

Pipeline operators use DNP3 for compressor station monitoring, regulator station pressure and flow reporting, and storage facility status.

Hydroelectric and Renewable Generation

Hydroelectric plants and some renewable energy facilities use DNP3 for generation monitoring and control under utility interconnection SCADA arrangements.

How Mango by Radix IoT Implements DNP3

All protocol drivers, including the DNP3 driver, are included in a standard Mango by Radix IoT installation and covered by the license. There are no separate driver purchases, per-protocol licenses, or add-on fees. Mango by Radix IoT includes a native DNP3 driver that communicates with DNP3 outstations (field devices) as a DNP3 master station.

DNP3 Master Station Function

Mango by Radix IoT acts as a DNP3 master, polling outstations for data and receiving unsolicited responses. Configuration includes master station address, outstation address, communication parameters, and polling intervals.

Data Object Support

Mango by Radix IoT reads and processes standard DNP3 data objects:

Binary inputs (single and double-bit)
Analog inputs (16-bit and 32-bit, floating point)
Counter inputs
Binary outputs and analog outputs (for control, where authorized)
Time-stamped event data (binary events, analog events, counter events)

Unsolicited Response Handling

Mango by Radix IoT processes DNP3 unsolicited responses and stores event data with the timestamps provided by the outstation — preserving the event sequence as recorded by the field device.

Event Polling After a Reconnect

Mango by Radix IoT polls DNP3 Class 1, 2 and 3 events on a normal cycle. After a communication interruption it resumes that same poll rather than running a dedicated catch-up routine. If the outstation still holds events in its own buffer, some of those records may be received on the next poll. This is the device retaining the data, not Mango by Radix IoT reconstructing the outage. Buffers are not drained to empty, and any events lost to buffer overflow on the device are not recoverable.

Serial and TCP Communication

Mango by Radix IoT supports DNP3 over serial communication (for radio modem networks and direct serial connections) and DNP3 over TCP/IP (for modern Ethernet-connected substations and RTUs).

Use Cases: DNP3 + Mango by Radix IoT

Electric Utility Substation SCADA

A distribution utility monitors transformer load, breaker position, and voltage regulation at distribution substations via DNP3. Mango by Radix IoT aggregates real-time status from multiple substations, stores historical analog and event data, and delivers alarm notifications for overload conditions and equipment faults.

Water Utility Pump Station Monitoring

A water utility operates 40 remote pump stations across a service territory. Each pump station’s RTU communicates via DNP3 over radio modem. Mango by Radix IoT receives pump run status, wet well levels, flow rates, and alarm events — enabling operators at the central control room to manage the entire distribution network.

Multi-Protocol Utility SCADA

A utility uses DNP3 for substation communication and Modbus for metering and generation equipment. Mango by Radix IoT aggregates both protocol families into a single operational view, eliminating the need for separate SCADA platforms per protocol.

SCADA Modernization

An aging utility SCADA system is being replaced. The RTUs in the field are retained (they use DNP3 and will continue to operate). Mango by Radix IoT replaces the legacy SCADA master, connecting to existing DNP3 outstations without requiring any field device changes.