Fluvius Telecontrole v4 through an EME eCON++ Gateway
Prefer the native Fluvius Telecontrole support The Sofar EMS can talk to the Fluvius Telecontrole RTU directly, without an EME eCON++ Gateway or any other gateway in between. That setup is recommended and easier to commission, but it requires a Sofar EMS with two ethernet ports, because the Fluvius RTU is connected to a network port of its own. Only use the integration described on this page when the installation already has an EME eCON++ Gateway. See Adding Fluvius Telecontrole RTU.
On some medium voltage installations, Fluvius Telecontrole is not wired to the Sofar EMS directly, but through an EME eCON++ Gateway (Electro Mechanic Equipment nv, Glabbeek). This manual describes what that gateway does and how to configure both halves of the integration.
Fluvius does not speak Modbus. The chain looks as follows:
Fluvius RTU ──IEC 60870-5-104──► IEC104 gateway ──Modbus TCP──► EME eCON++ Gateway ──Modbus TCP──► EMS controller
(server/slave) (client/master)
The EME eCON++ Gateway is a Modbus TCP server; the Sofar EMS connects to it as a client on port 502. The gateway mirrors the Fluvius telecontrol signals onto its Modbus registers:
The device and the external signal driver always go together The device driver only reads the Fluvius commands and answers the feedback handshake. It does not curtail anything by itself. Translating the setpoints into actual limits is done by the Eme Fluvius Modbus TCP external signal driver. An installation with only one of the two is not functional:
Connect the Sofar EMS to the ethernet switch of the EME eCON++ Gateway and give it a fixed IP address in the same subnet as the gateway. The gateway must be reachable on TCP port 502. The IP addresses and the Modbus unit address are site specific; ask EME or the panel builder for the ones used in your installation.
The link between the Fluvius RTU, the IEC104 gateway and the EME eCON++ Gateway is configured by EME and is outside the scope of the Sofar EMS.
Fluvius sends its setpoints as a percentage, and the Sofar EMS converts them into power limits using the grid limits of the site. All four limits below must be filled in before the external signal driver can work.
The reactive limits are not optional Even when Fluvius only sends active power setpoints, the external signal driver reads all four limits on every remote control cycle. If the two reactive limits have never been saved on the site, the external signal driver fails and no Fluvius setpoint is applied at all. Open Advanced settings and save them explicitly, also when you keep the proposed values.
The device reports the Fluvius commands and the access point measurements it reads from the gateway:
| Measurement | Meaning |
|---|---|
controlMode | 0 = undefined, 1 = local control, 2 = remote control by Fluvius |
testOperation | Test operation requested by the Fluvius RTU (0 = low, 1 = high) |
powerSetpointPercentage | Active power setpoint from Fluvius, −100 % … +100 % |
reactivePowerSetpointPercentage | Reactive power setpoint from Fluvius, −100 % … +100 % |
actualPowerTot_W, reacPowerTot_VAr | Active and reactive power at the access point, as measured by Fluvius |
voltageL1L2_V, voltageL2L3_V, voltageL3L1_V | Phase-phase voltages at the access point |
Not a grid meter These measurements come from Fluvius and are only refreshed once per minute. Do not use this device as the main grid meter of the site — the control algorithms need a meter that is read at the normal measurement interval.
There is nothing to fill in: the external signal driver takes everything it needs from the device and from the grid limits of the site. See Fluvius (through an EME eCON++ gateway).
| Fluvius command | Behaviour of the Sofar EMS |
|---|---|
| Control mode = 0 (undefined) or 1 (local) | No action. The site keeps running on its own strategy. |
| Control mode = 2 (remote), active setpoint = 0 % | Import and export limit are both set to 0 W, so the site stops exchanging power with the grid. A small minimum band is kept for stability. |
| Control mode = 2, active setpoint > 0 % | Import limit = setpoint % × Allowed grid import power. |
| Control mode = 2, active setpoint < 0 % | Export limit = setpoint % × Allowed grid export power. |
| Control mode = 2, reactive setpoint > 0 % | Reactive power setpoint = setpoint % × Allowed grid import reactive power. |
| Control mode = 2, reactive setpoint < 0 % | Reactive power setpoint = setpoint % × Allowed grid export reactive power. |
Independently of the control mode, the device answers every command with the matching feedback and mirrors the heartbeat back to the gateway, so Fluvius keeps seeing a responsive EMS.
Fluvius allows the installation up to 3 minutes to settle on a new setpoint after it has changed.
controlMode and the setpoint percentages are
being read. As long as Fluvius is in local control, the control mode is 1.testOperation, and
the Sofar EMS answers it immediately.| Symptom | Cause |
|---|---|
| The external signal driver reports "No EME Modbus Device found in site devices." | The gateway device is not added, or is not communicating. Add it as described in step 3. |
| Setpoints are visible on the device, but nothing is curtailed | The external signal driver is not added, or the grid limits of the site are not completely configured — including the two reactive limits of step 2. |
| Fluvius reports that the EMS does not answer | The device is not communicating with the gateway, so the command feedback is no longer written. Check the IP address, port 502 and the Modbus unit address. |