---
title: "Modbus Server | Examples | N3uron KB V1.22"
slug: "modbus-server-examples"
description: "Modbus Server is a N3uron module designed to provide enhanced connectivity for all devices and third-party applications requiring Modbus communications…"
updated: 2025-09-30T15:55:34Z
published: 2025-12-23T12:18:43Z
canonical: "docs.n3uron.com/modbus-server-examples"
---

> ## 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 an Inverter data using Modbus Server

In this example, we are going to use **Modbus Server** to expose data coming from an **ABB** inverter that is being acquired through **N3uron**'s **Aurora Client** module.

Below is the memory map that shall be configured in **Modbus Server**:

| **Template: PV inverter** |
| --- |
| **Communication protocol: Modbus TCP** |
| **Tag Name** | **Modbus Address** | **Data type** | **Access** | **Units** | **Scaling** | **Description** |
| ALARMS/FAN_ERROR | 400108.2 | boolean | R |  | 1 | Alarm: Fan diagnostics error |
| ALARMS/IGBT_HIGH_TEMP | 400108.3 | boolean | R |  | 1 | Alarm: High temperature in drive |
| ENERGY_TODAY_VAL | 400101 | Int32 | R | W/h | 0.1 | Energy generated on current day |
| ERROR_CODE | 400103 | Int16 | RW |  | 1 | Error code: 0 - No error, 1 - AC error, 2 - DC error |
| FREQUENCY_VAL | 400104 | Int16 | R | Hz | 0.01 | Grid frequency |
| POWER_SP | 400105 | Int16 | RW | kW | 1 | Active power setpoint |
| POWER_VAL | 400106 | Int16 | R | kW | 0.1 | Active power generated |
| STATUS_CODE | 400107 | Int16 | R |  | 1 | Status code |

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/19-Current-tags.png)

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

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

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

- **Step 2:** Configure the Logger and API for the **Modbus Serve**r module. In this example, the default configuration has been left unchanged, since in most cases, this is a valid configuration option.
- **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-2-Creating-new-Modbus-Server-communication-channels.png)

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/12-2-Creating-a-new-module-instance.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/13-2-Configuring-Channel(1).png)

- **Step 5:** Next, add a "Map group" and set its configuration.
- **Step 6:** Finally, add a "Tag Map", and start creating all the tags from the Memory Map (shown above). The following Figures show the configuration settings for an Int16 and a Boolean tag respectively. The rest of the tags should be configured similarly.

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/14-Configuration-map.png)

![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/15-2-Map-configuration(1).png)