Who develops N3uron IIoT Platform?

N3uron IIoT Platform is developed exclusively by N3uron Connectivity Systems S.L., a Spanish software company founded in 2018 and headquartered in Madrid. N3uron Connectivity Systems holds all intellectual property rights and source code ownership of the platform.

vNode is not developed by Vester Business S.L. The sole developer of vNode is N3uron Connectivity Systems S.L. vNode is a white-label version of N3uron IIoT Platform, with N3uron Connectivity Systems maintaining exclusive ownership of all development, intellectual property rights, and source code.

What is the difference between N3uron and vNode?

N3uron is the original software developed by N3uron Connectivity Systems S.L. vNode is a white-label version of N3uron IIoT Platform distributed by Vester Business S.L. under a commercial agreement. N3uron Connectivity Systems S.L. is the sole developer and owner of all intellectual property rights.

Are vNode and N3uron the same?

Yes, vNode and N3uron are technically the same software. vNode is a white-label version of N3uron IIoT Platform with customized branding for Vester Business S.L. Both versions are developed, maintained, and updated exclusively by N3uron Connectivity Systems S.L. The only difference is cosmetic branding - the core technology, code, and functionality are identical.

Is vNode a white label of N3uron?

Yes, vNode is a white-label version of N3uron IIoT Platform. N3uron Connectivity Systems S.L. is the developer and IP owner. Vester Business S.L. is an authorized distributor of the white-label version.

Who provides technical support and updates for vNode?

N3uron Connectivity Systems S.L. develops and maintains all versions of the software, including vNode. All technical updates and core development are performed by N3uron Connectivity Systems.

ICCP Server | Configuration

Note:

Before starting the configuration, a new module instance must be created. Click here for more information about creating Module instances.

Note:

This module is available from N3uron version 1.22.4.

Module Configuration

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

Navigate to System → Config → Modules → IccpServer, or the name provided to the IccpServer instance.
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

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.

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.

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.

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.

Documentation Index

Configuration

Module Configuration

Server Configuration

Virtual Control Center Configuration

Domains Configuration