Fenecon Mini PvMeter

Installation

1. 1Enable the Modbus TCP read access app on the FEMS system via the FEMS App Center in the FENECON Online Monitoring portal, then confirm that the Modbus TCP server is active on port 502.
2. 2Connect the ModbusCloud Gateway to the same LAN segment as the FEMS box, ensuring no firewall blocks TCP port 502 between the Gateway and the FEMS IP address.
3. 3In the ModbusCloud portal, add a new device, import the Fenecon Mini PvMeter template, and set the Modbus unit ID to match the meter component ID configured in FEMS (the first production meter defaults to ID 6).
4. 4Trigger a manual poll on register 4006 in the portal and confirm the returned active power value matches the live reading shown in FENECON Online Monitoring.

Things to watch for

01

Register 4006 returns zero even when the PV array is generating.

Confirm that the correct FEMS component ID is mapped to this meter. If multiple production meters are configured, their Modbus IDs increment from 6 upward. Poll each unit ID in sequence to identify which one holds the active PV meter data, then update the unit ID in your ModbusCloud device settings.

02

The gateway connects but active power readings are always shifted or wrong.

FEMS Modbus TCP uses a zero-based register addressing scheme. If your polling tool or gateway defaults to a base address of 1, all register addresses will be off by one. Set the base address to 0 in your Modbus client configuration to align with the FEMS register table.

03

No Modbus TCP connection can be established to the FEMS box.

Read access via Modbus TCP must be enabled through the FEMS App Center. Check that the FEMS App Modbus TCP reading is installed and active. Also verify that the FEMS box IP address is reachable from the Gateway subnet, and that port 502 is not blocked by a local router or firewall rule.

04

Active power values look implausibly high or fluctuate erratically.

The active_power register is a uint16 value in watts with no scaling factor applied. If the returned value appears out of range, verify that the data type in the portal template is set to uint16 and that no additional scaling multiplier has been applied. Also check that only one Modbus client polls the FEMS concurrently, as simultaneous connections can cause response errors.

More Fenecon templates

Fenecon MasterBox2V0 Relay

Fenecon

Modbus TCP

12 registers

Fenecon COMMERCIAL40 CHARGER

Fenecon

Modbus TCP

57 registers

OpenEMS

Fenecon

Modbus TCP

Reads energy data from OpenEMS-based devices via Modbus TCP

39 registers75

Fenecon Dess PvMeter

Fenecon

Modbus TCP

3 registers

Fenecon Pro PvMeter

Fenecon

Modbus TCP

9 registers

Fenecon Mini Ess

Fenecon

Modbus TCP

97 registers

More TCP templates

Algodue Energy meter UEM80-2D E

Algodue Elettronica S.r.l.

Modbus TCP

Measures single-phase energy consumption and production via Modbus TCP.

12 registers46

Sigenergy SigenStore EC (grid)

Sigenergy

Modbus TCP

5 registers1

Fronius GEN24

Fronius

Modbus TCP

Monitors and controls Fronius GEN24 inverters and PV batteries via SunSpec Modbus TCP

0 registers762

HUAWEI SUN2000 Inverter & LUNA2000 battery

Huawei

Modbus TCP

Monitors HUAWEI SUN2000 inverter, LUNA2000 battery, and Smart Power Sensor via Modbus TCP.

4 registers1248

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597