Fenecon Dess GridMeter
The Fenecon DESS GridMeter is the grid-connection-point electricity meter component of the Fenecon DESS energy storage platform, used in residential and light-commercial PV-plus-storage installations. This ModbusCloud template reads the meter over Modbus TCP and exposes per-phase voltage, current, active power, and reactive power for all three phases, plus cumulative consumption and production energy totals. With this data in your portal you can track import and export trends, detect phase imbalances, and validate zero-feed-in operation in real time.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 14, read only
- Brand
- Fenecon
- Last updated
Registers (14)
14 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| original_active_consumption_energy | Wh | Read | |||
| original_active_production_energy | Wh | Read | |||
| current_l1 | A | Read | |||
| voltage_l1 | V | Read | |||
| active_power_l1 | W | Read | |||
| reactive_power_l1 | W | Read | |||
| current_l2 | A | Read | |||
| voltage_l2 | V | Read | |||
| active_power_l2 | W | Read | |||
| reactive_power_l2 | W | Read | |||
| current_l3 | A | Read | |||
| voltage_l3 | V | Read | |||
| active_power_l3 | W | Read | |||
| reactive_power_l3 | W | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Monitor per-phase active power on L1, L2, and L3 to detect load imbalances across the three phases.
- Track cumulative consumption and production energy totals to verify monthly self-consumption ratios.
- Alert on unexpected grid export spikes by comparing original_active_production_energy increments against expected PV output.
- Compare per-phase voltages across L1, L2, and L3 to identify voltage deviations outside grid tolerance.
- Report reactive power on each phase to evaluate power factor and flag excessive reactive draw by connected loads.
Installation
Confirm the Fenecon DESS FEMS unit has the Modbus TCP read access app active: in the FEMS online monitoring open Settings, then the system profile, and verify the ctrlApiModbusTcp component is present.
Connect the ModbusCloud Gateway to the same LAN segment as the FEMS unit, ensuring it can reach the FEMS IP address on TCP port 502.
In the ModbusCloud portal add the Gateway, import the Fenecon DESS GridMeter template, and set the unit ID to 1, which is the default Modbus slave ID for FEMS devices.
Spot-check register 11137 (voltage_l1) in the live data view and compare the displayed value against the FEMS online monitoring to confirm correct polling.
Things to watch for
All register values show zero or are unavailable. What is wrong?
The FEMS Modbus TCP read interface must be active. In the FEMS online monitoring go to Settings, open the system profile, and confirm the ctrlApiModbusTcp component is listed. If it is absent, the app has not been activated on the FEMS unit and no data will be returned.
Register addresses appear shifted by one compared to the FEMS documentation.
The FEMS Modbus TCP API uses zero-based register addressing. Some Modbus client tools default to a base address of 1. Set the base address to 0 in your client configuration. The ModbusCloud Gateway handles this correctly by default, so no adjustment is needed in the portal.
The Gateway connects but per-phase power readings look incorrect or implausible.
The active_power and reactive_power registers on this meter use uint16 data types. Values represent unsigned integers; if the FEMS firmware reports signed power flow through these registers in a specific version, the readings may wrap. Cross-check against the live FEMS monitoring dashboard and verify your FEMS firmware is up to date.
No TCP connection can be established to the FEMS unit at all.
Confirm the ModbusCloud Gateway and the FEMS unit are on the same physical network and that no firewall or VLAN separation blocks TCP port 502. The FEMS Modbus TCP interface only accepts connections from devices with direct network access to the FEMS IP address.
Want to see how it works?
