Skip to content

DSO RTU

Fluvius

Telecontrole with Fluvius over the Netflex interface (IEC 60870-5-104).

Fluvius operates telecontrole through its Netflex interface, based on IEC 60870-5-104 (IEC-104). The Voltmasters EMS implements the Netflex client interface per the Fluvius Netflex specification (interface data model version 1.0, Annex B).

This page describes what travels over the link. The pages below it cover the rest:

Connection

  • Physical link: the Fluvius RTU connects to the controller with a network (Ethernet) cable through an Ethernet-to-USB adapter on the controller. Any USB port can be used.
  • Protocol: IEC 60870-5-104.
  • Role: the EMS is the server; the Fluvius RTU connects to it as the client.
  • Port: TCP 2404 (standard IEC-104).
  • Common address (ASDU): 100. General interrogation is also accepted on the broadcast common address.
  • Initialization: after connect, the link is initialized (end of initialization), Fluvius performs a general interrogation, and the clock is synchronized from the Fluvius side.

See RTU connection for the on-site connection and the network requirements.

What Fluvius sends

Names follow the Netflex specification.

Commands

Function Type Description
Emergency stop production Single command Stop all injection (PV off, battery to 0 kW).
Emergency stop consumption Single command Stop all consumption (battery to 0 kW, loads off).
Test Single command Test operation, used during certification.
Q control mode Double command Select local or remote reactive-power control.

Setpoints (short floating point)

Function Spec name Description
Max production at connection point MINSETP Max injection, as % of the contractual injection capacity.
Max consumption at connection point MAXSETP Max consumption, as % of the contractual consumption capacity.
Max asset production MINSETAP Max production of the assets, as % of the registered production reference power.
Max asset consumption MAXSETAP Max consumption of the assets, as % of the registered consumption reference power.
Min reactive power MINSETQ Lower bound of the reactive-power band, as % of the registered production reference power.
Max reactive power MAXSETQ Upper bound of the reactive-power band, as % of the registered production reference power.
Reason P REDENP Reason code for the active-power control.
Reason Q REDENQ Reason code for the reactive-power control.

Every setpoint is an upper bound. A value of 100 % (or -100 % on the production side, since those arrive negative) imposes nothing; a lower value caps the installation but never asks it to produce or consume a given amount.

Reason codes

Code Meaning
0 Normal operation
1 Grid congestion
99 Test (used during certification)

What the EMS reports

  • Feedback mirroring every command and setpoint the moment it arrives (emergency-stop states, Q mode, the active P and Q limits, the asset setpoints) and the interface version.
  • Periodic measurements every 30 seconds of active power (P) and reactive power (Q), one message per value, grouped per measurement channel.

Measurement channels

Channel Category Reported from
1 Solar PV inverters registered in this channel
2 Wind Wind turbines registered in this channel
3 CHP Devices assigned to it
4 Storage Batteries registered in this channel
5 EV charging EV chargers
6 Flexible consumption Controllable loads, and batteries registered as flexible consumption
7 Other production Devices assigned to it

Which channel a device lands in follows the Fluvius dossier, not the device type: it is set per device under Netflex measurement channels. A device outside the flex registration is set to Not reported and sends nothing. Channels without devices are reported as zero.

Fluvius uses these measurements to check its setpoints: the sum of channels 1, 2, 3, 4 and 7 is the virtual asset coupling point that MINSETAP and MAXSETAP are compared against. Those five channels hold only the assets that are subject to technical flex, and the same assets are the ones whose powers make up the reference powers. Production or storage outside technical flex belongs in none of them: it does not contribute to the virtual asset coupling point, even though the EMS keeps steering it for the site's own optimisation. See asset setpoints.

Emergency stops

Fluvius can stop production and consumption independently. Each stop is enforced in software on every control cycle and, through the relay outputs configured per side, physically on the installation. Fluvius expects that physical disconnection. Wiring and configuration are on Emergency stop and in step 2 of the configuration.

Certification

A Fluvius telecontrole installation must pass an on-site certification before Fluvius approves it. The inspector sends the emergency stops, the connection point setpoints, the asset setpoints and the reactive band with the test reason code, and checks the measurements that come back. Commissioning and certification describes the sequence, what Fluvius checks, and how to follow every value on the DSO RTU dashboard during the test.