Enables Edge-to-Edge connection of devices from a slave OpenEMS Edge via Modbus. This requires Controller Api Modbus/TCP Read-Write
to be active on the slave system, e.g. via the FEMS App Modbus/TCP Schreibzugriff for a FENECON Energy Storage System.
-
Setup a 'Slave' OpenEMS Edge instance, that controls one or more energy storage systems
-
Component-ID of the energy storage system or the ESS-Cluster is
ess0
-
Activate
Controller Api Modbus/TCP Read-Write
and addess0
to the configuredcomponent_ids
-
Note
|
At this point you can open OpenEMS UI and check the system profile under settings. Click on the ctrlApiModbusTcp0 component and download the generated Modbus/TCP register table. You should find ess0 listed there. An example Excel file can be found here: https://github.com/OpenEMS/openems/tree/develop/io.openems.edge.controller.api.modbus/doc
|
Note
|
This is the setup you will find after purchasing a "FEMS App Modbus/TCP Schreibzugriff" for a FENECON Energy Storage System |
-
Setup a 'Master' OpenEMS Edge instance.
-
Configure
Bridge Modbus/TCP
:-
id
:modbus0
-
ip
: IP-Address of the Slave instance
-
-
Configure
Edge-2-Edge ESS
:-
id
:ess0
-
remoteAccessMode
:AccessMode.READ_WRITE
(for default Read-Only access this would beAccessMode.READ_ONLY
) -
remoteComponentId
:ess0
-
modbus_id
:modbus0
-
-
Now you are able to access the remote energy storage system as if it was connected locally, e.g. configure a
Controller Ess Fix Active Power
oness0
to set a fixed charge or discharge command.
-