---
title: "DNP Server | Examples | N3uron KB V1.22"
slug: "dnp-server-examples"
description: "DNP Server is a N3uron module designed to provide enhanced connectivity for all devices and third-party applications requiring DNP3 communications…"
updated: 2025-12-23T11:43:04Z
published: 2025-12-23T11:43:18Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.n3uron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Examples

## Exposing Power Meter data using DNP Server

In this example, we are going to use **DNP3****Server** to expose data coming from a Power Meter that is being acquired through **N3uron**'s **Modbus Client**.

Below is the memory map that will be configured in **DNP3****Server**:

| **Power meter** **Communication protocol: DNP** |
| --- |
| **Tag Name** | **DNP Group** | **DNP Variation** | **Index** | **Access** | **Units** | **Scaling** | **Description** |
| ANGLE_PHASE | 30 | 5 | 0 | R | Degrees | 1 | Angle phase |
| CURRENT | 30 | 5 | 1 | R | A | 1 | AC current |
| ENERGY_ACTIVE_IMPORTED | 30 | 5 | 2 | R | kWh | 1 | Energy exported |
| ENERGY_ACTIVE_EXPORTED | 30 | 5 | 3 | R | kWh | 1 | Energy imported |
| FREQUENCY | 30 | 5 | 4 | R | Hz | 1 | Frequency |
| POWER_ACTIVE | 30 | 5 | 5 | R | kW | 1 | AC power |
| POWER_ACTIVE_MAX | 30 | 5 | 6 | R | kW | 1 | Max. AC power |
| POWER_APPARENT | 30 | 5 | 7 | R | kVA | 1 | Apparent power |
| POWER_FACTOR | 30 | 5 | 8 | R |  | 1 | Power factor |
| POWER_REACTIVE | 30 | 5 | 9 | R | kVAr | 1 | Reactive power |
| VOLTAGE | 30 | 5 | 10 | R | V | 1 | Voltage |

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/10-Electrical-meter-Tags.png)

- **Step 1:** Add a new module in the "Modules" section, choose a name, and select "Dnp Server" in the "Module type" field.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2011-%20Creating%20a%20new%20module.png)

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2012-%20Setting%20the%20instance%20type.png)

- **Step 2:** Configure the **Logger** and **API** for the **DNP3****Serve****r** module. In this example, the default configuration settings have been left unchanged, since in most cases, this is a valid configuration.
- **Step 3:**Add a new channel in the “Model” section and choose a name for it. The **Source IP addresses** field can be left empty in order to allow all IP addresses for incoming connections. However, specifying the **Source IP address** is strongly recommended, as this adds an extra layer of security.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/05-Creating-new-DNP-Server-communication-channels.png)

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2014-%20Configuring%20the%20channel.png)

- **Step 4:** Add a new device in the “Configuration” section and configure the device.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2015-%20Creating%20a%20new%20device.png)

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2016-%20Device%20configuration.png)

- **Step 5:**Next, add a "Map group" and set its configuration.
- **Step 6:** Finally, add a "Tag Map" and start creating all tags from the Memory-Map (shown above). The following Figure shows the configuration settings for an Analog input tag. The rest of the tags should be configured in a similar way.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/Figure%2017-%20Configuration%20map%20for%20an%20Analog%20input%20tag.png)