---
title: "ICCP Server | Configuration | N3uron KB V1.22"
slug: "iccp-server-configuration"
description: "N3uron ICCP Server provides IEC 60870-6/TASE.2 connectivity for real-time data exchange with authorized SCADA, EMS, control-centre and dispatch systems."
status: "new"
updated: 2026-07-13T08:27:05Z
published: 2026-07-13T08:27:05Z
canonical: "docs.n3uron.com/iccp-server-configuration"
---

> ## 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.

# Configuration

**Note:**

Before starting the configuration, a new module instance must be created. [**Click here for more information about creating Module instances**](/v122/docs/platform-create-new-module-instance).

Note:

This module is available from **N3uron** version **1.22.4**.

## Module Configuration

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

As shown in the screenshot to create a new Server follow these steps:

1. Navigate to **System → Config → Modules → IccpServer,** or the name provided to the **IccpServer** instance.
2. In the **Model** panel, click the menu **(≡)** and choose **New Server** to add additional **IccpServer** instances. You can also **Load CSV** to import or **Save CSV** to export a model configuration. Below is an explanation of the various configuration options.

### **Server Configuration**

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

A server represents the physical medium to which one or more client devices can be linked. Each server requires the following settings to be configured.

| **Settings** | **Description** |
| --- | --- |
| Enabled | Enables or disables this ICCP/TASE.2 server instance. When disabled, the server will not be initialized or accept any client connections. |
| Server | - **Server type:** Specifies whether the server uses plain TCP or TLS-encrypted connections. - **Standard ICCP:** The server communicates over plain TCP without encryption. - **Secure ICCP (TLS):** The server uses TLS encryption. A server certificate must be configured. Optionally, mutual TLS (mTLS) can be enabled by providing a CA certificate for client verification. - **Network interface:** Specifies the IP address of the network interface the server should bind to. Use **0.0.0.0** to listen on all available interfaces. - **TCP port:** Specifies the TCP port the server will listen on. The standard port for ICCP/TASE.2 (ISO TSAP / RFC 1006) is **102**. **Important:** The combination of network interface and port must be available; otherwise, the server will fail to start due to a socket binding error. - **Max. connections:** Specifies the maximum number of simultaneous client connections that the server will accept. Exceeding this limit will result in new connection attempts being rejected. The maximum configurable value is **100** connections. - **Allowed IP addresses:** A comma-separated list of IPv4 addresses that are authorized to establish a connection with this server. This feature enhances security by restricting access to a predefined list of clients. If this field is left empty, the server will accept connections from any IP address. - **Password:** Optional password for authenticating ICCP/TASE.2 client connections. If left empty, no password authentication is required. All passwords are encrypted for security reasons. |

#### **Virtual Control Center Configuration**

Once a **Server** has been configured, new data points can be added to **Virtual Control Center**. To create a new **DataPoint**, you can click on the **3-dotted icon** → **New DataPoint**. Each DataPoint requires the following settings to be configured.

| **Settings** | **Description** |
| --- | --- |
| Tag | Select the **N3uron** tag associated with this data point. For indication types, this tag is the source whose value is exposed to ICCP clients. For command types, this tag is the destination that receives values when an ICCP client issues a command. |
| Data type | Specifies the ICCP/TASE.2 data type for this data point. **Indication types** - **State:** Double-point status **encoded as a 2-bit value** per IEC 60870-6-503 - not a plain boolean. It models a nominally two-state device (e. g. open/close) but takes **four** possible values: *Off, On, Intermediate* (mid-transition), and *Invalid.* - **Discrete:** Integer value for discrete quantities, for example, tap positions or counters. - **Real:** Floating-point value for analog measurements, for example, voltage, power, or frequency. **How the source tag maps to a State value** The source tag value is translated following the IEC 60870-5 double-point convention: - 0 **→Intermediate** (transitioning between states). - 1**→Off.** - 2**→On.** - Boolean false **→ Off,** boolean true **→ On.** - Any other value - 3, non-integer, or out-of-range - is reported as **Invalid.** **Suffixes (indications)** - **Q:** Includes quality flags, (validity, current source, normal value). - **Q TimeTag:** Includes quality flags and a timestamp. - **Q TimeTag Extended:** Includes quality flags and an extended timestamp with millisecond precision. - **Extended:** Includes additional fields such as change-of-value counter. **Command types** - **Command:** Discrete command (integer). Used for switching operations (e. g. open/close breaker). - **Discrete Setpoint:** Discrete setpoint (integer). Used for integer control values (e. g. tap position). - **Real Setpoint:** Analog setpoint (floating-point). Used for continuous control values (e. g. voltage reference). Each command type is available as **Direct Operate** (immediate execution) or **Select Before Operate (SBO)**, (two-step confirmation). SBO commands require a checkback ID and a select timeout. |

#### **Domains Configuration**

Once a **Server** has been configured, new Domains can be added to **Server**. To create a new **Domain**, you can click on the **3-dotted icon** → **New Domain**. You can also **Load CSV** or **Save CSV** to import or export the model configuration.

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

Once a **Domain** has been configured, new **Bilateral Tables** can be added to **Domain**. Each Bilateral Table requires the following settings to be configured.

| **Settings** | **Description** |
| --- | --- |
| Bilateral Table ID | Identifies this domain within the ICCP/TASE.2 bilateral agreement. This string uniquely identifies the bilateral table between two control centers and must match the value configured on the remote end. |

To create a new **Data Point**, you can click on the **Data Points** ellipsis button and select **New DataPoint**. Please refer to Data point Settings table in previous section for more information. To create a new **Data Set**, you can click on the **Data Sets** ellipsis button and select **New DataSet**. You can also **Load CSV** or **Save CSV** to import or export the model configuration.

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

Once a **Dataset** has been configured, new **Data Set Members** can be added to **Dataset**. To create a new **Member**, you can click on the **3-dotted icon** → **New DataSetMember**. You can also **Load CSV** or **Save CSV** to import or export the model configuration.

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

Note:

The Point Reference setting should be selected from VCC → Data Point or Domain → Data Point, so **Data Points** need to be created first based on the scope required for deployment.

Each DataSetMember requires the following settings to be configured.

| **Settings** | **Description** |
| --- | --- |
| Point reference | References a data point by its name. The referenced point can belong to any Domain or to the VCC. |