FENECON Modbus-API (grid)

Installation

1. 1Confirm the FEMS App Modbus/TCP Read Access is active on the FENECON system: log into FEMS Online Monitoring, open Settings, navigate to the system profile, and verify ctrlApiModbusTcp is listed as an active component.
2. 2Connect the ModbusCloud Gateway to the same LAN segment as the FENECON FEMS controller, ensuring the Gateway can reach the FEMS IP address on TCP port 502.
3. 3In the ModbusCloud portal, add a new device, import the FENECON Modbus-API (grid) template, and set the Modbus unit ID to 1 and the target IP to the FEMS IP address.
4. 4Spot-check register 315 (grid active power) in the portal live view and confirm the value matches the FEMS Online Monitoring display; if addresses appear shifted by one, set the client base address to 0.

Things to watch for

01

Register 315 returns a value shifted by one register. Why?

The FENECON Modbus-API uses zero-based register addressing. Many Modbus clients default to a base address of 1, which shifts all addresses by one. Change the base address offset in your client or in the ModbusCloud Gateway configuration to 0 to align with the FEMS register table.

02

The Gateway connects but grid power reads as zero or NaN.

The FEMS may not have grid meter data available if the grid meter is offline or not yet commissioned. Verify the grid meter is active in FEMS Online Monitoring. Also confirm the data type is float32 for register 315 (FC 4) and float64 for register 359 (FC 3); a type mismatch returns invalid values.

03

Modbus TCP connection is refused on port 502. What should I check?

The FENECON FEMS must be reachable on the same physical network as the ModbusCloud Gateway. Check that no firewall blocks TCP port 502 between the Gateway and the FEMS IP address. Also verify the FEMS App Modbus/TCP Read Access is installed and active, as the interface is only available when the app is enabled.

04

Energy register 359 seems to accumulate incorrectly after a FEMS restart.

Register 359 holds a cumulative float64 value maintained by the FEMS software. After a FEMS restart or firmware update, the counter may reset or briefly report stale values. Record a baseline reading in the ModbusCloud portal immediately after any FEMS update so you can apply an offset correction in your dashboard calculations.

Registers (2)

2 read / 0 write

More FENECON templates

FENECON Modbus-API (pv)

FENECON

Modbus TCP

2 registers

FENECON Modbus-API (battery)

FENECON

Modbus TCP

2 registers

More TCP templates

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

SunSpec Model 709 — DER Trip LF

SunSpec

Modbus TCP

9 registers

Victron Meter AcOut

Victron

Modbus TCP

16 registers

FoxESS Avocado (grid)

FoxESS

Modbus TCP

8 registers