The FLEXeCHARGE Gateway Connect features an integrated Modbus TCP Server, enabling dynamic control of the maximum cluster current during runtime.
Enabling Modbus TCP Service
For security reasons, the Modbus TCP service is disabled by default. To enable this service, please contact your local FLEXeCHARGE support team, who will activate it for you.
Modbus Dynamic Cluster Limit Register
The dynamic cluster limit register is an unsigned 16-bit register that can be modified using Modbus Function Code 6 (Write Single Holding Register).
-
Unit ID: 255
-
Register Address: 0x0
Setting the Dynamic Maximum Cluster Limit
The load management engine operates with two cluster limits:
-
Configured Maximum Cluster Limit (Hard Limit)
-
This is a static limit set during system configuration.
-
The load management engine will never exceed this limit.
-
Represents the maximum current rating of the electrical supply infrastructure.
-
Must be configured via the FLEXeCHARGE platform as outlined in the configuration guide.
-
-
Dynamic Cluster Limit
-
This can be modified in real-time via the Modbus TCP register.
-
If the dynamic cluster limit is set higher than the configured maximum cluster limit, the system will default to the hard limit and will never exceed it.
-
Load Management Engine Behavior
In specific scenarios, the load management engine may automatically adjust or override the dynamic cluster limit. For example:
-
If Unbalanced Load Prevention is active, the engine may reduce the limit to maintain phase balance. If a higher limit is later set via Modbus, the system will respect the lower limit enforced by the engine.
-
Once the phase imbalance is resolved, the system will revert to the last Modbus-set cluster limit.
Suspending Charging via Modbus
Setting the dynamic cluster current to 0A will suspend all charging, ensuring that no charge current is allocated.
For further details, refer to the FLEXeCHARGE platform configuration guide or contact technical support.
Comments
0 comments
Article is closed for comments.