|
<< Click to Display Table of Contents >> Navigation: Components > E-Mobility > Dynamic load management V2 |
Dynamic charging management (DLM for short) is used for the automatic charging regulation of several charging stations. If this component is created, it counts as 2000 components and from the 11th station as 3000 components.
The component distributes the maximum available current (set value or smallest value of the 3 phase inputs) - minus a current reserve - evenly to all currently charging stations.
If the current available per station falls below a minimum, e.g. due to the start of charging at another charging station, all stations not currently charging are deactivated.
Data points of the component
Name |
Type |
Function |
|---|---|---|
Current ID Tag File [filename]. |
Output |
Output the URL for the ID tag file (save path) |
Reduce all charging points to the minimum |
Input |
With an On signal, all charging points are reduced to their minimum charging power. |
Send all logs (or only of the month) to Admin |
Input |
any value (except TRUE) -> Triggers sending all data to the administrator TRUE -> Triggers sending all previous data of the current month to the administrator |
Send all logs of the last month to admin (and user) |
Input |
any value (except TRUE) -> Triggers sending all data of the past month only to the administrator TRUE -> Triggers sending all data of the past month to the administrator and users. The users only receive their data. |
Alternative e-mail address for unknown users |
Bidirectional |
Specifies the alternative mail address (used when no user address is stored in the channel editor).
|
Export database (file name) |
Input |
Exports the OCPP database(s) (the transaction database, the user database and various values from the Runtime DB such as the last assigned transaction ID) to corresponding files. The path must be specified in the DP - e.g. via the file selection component 3 files are created. - The transaction data with the specified file name - The user ID data with "_users" appended to the file name - The runtime data with "_runtime" appended to the file name |
Import database (file name) |
Input |
Selection or specification of the transaction data file. The other two are searched for in the same folder with the above naming scheme and imported accordingly |
Delete database |
Input |
Deletes the transaction database |
Diagnosis (MQTT) [Text] |
Output |
Attention: Diagnostic or debug outputs are only intended for use in the event of an error. Please use only after consultation with the support team! If used, these can significantly affect the performance of the service. |
Diagnosis [Text] |
Output |
Attention: Diagnostic or debug outputs are only intended for use in the event of an error. Please use only after consultation with the support team! These may significantly affect the performance of the service if used. |
Diagnostic algorithm (Verbose) [Text] |
Output |
Attention: Diagnostic or debug outputs are only intended for use in the event of an error. Please only use them after consulting the support team! If used, they can significantly impair the performance of the service. If several drivers are available, the displays can be switchedvia the debugger. Extended information on the calculation algorithm of the DLM is displayed here (very detailed). |
Diagnostic algorithm [Text] |
Output |
Attention: Diagnostic or debug outputs are only intended for use in the event of an error. Please only use them after consulting the support team! If used, they can significantly impair the performance of the service. If several drivers are available, the displays can be switchedvia the debugger. Information on the calculation algorithm of the DLM is displayed here. |
Dynamic |
Folder |
See below for description. |
E-mail address of the administrator |
Bidirectional |
The e-mail address of the administrator(s) can be changed via this data point at runtime. Multiple addresses are separated with a ;. |
Send e-mails to users (load interruption) |
Bidirectional |
(De) Enable e-mail notification to the user when the load state changes to "load interruption". |
Send e-mails to user (end of transaction) |
Bidirectional |
(De) Enable e-mail notification to the user when the charge state changes to "transaction end" (finished charging). |
Energy prices in ct/kWh [csv]1 |
Input |
Input for the current electricity price as CSV. The format corresponds to the SMARD component (date/time ; price). |
Advanced Diagnostics |
Input |
With an ON signal, the diagnostic output is extended. |
ID Tags |
Folder |
This folder contains data points for reading or entering the ID tag configuration. |
ID Tags [CSV String] |
Output |
Outputs the ID Tags as text when the data item Export ID Tags [CSV String] is triggered. |
Export ID Tags [CSV String] Input |
Input |
Trigger input to output the ID-TAGs at the ID-Tags [CSV string] output. |
Export ID Tags [Filename] Input |
Input |
By specifying the absolute storage path, the ID tags are exported. (See below for the structure of the CSV file) |
Import ID tags - Result |
Output |
Output in text form whether the import was successful or not. |
Import ID tags [CSV string] Input |
Input |
By entering the ID tags as CSV text, the list can be imported here. |
Import ID tags [filename] Input |
Input |
By specifying the absolute storage path of the CSV file, the ID tags are imported. (See below for the structure of the CSV file) |
Load history |
Bidirectional |
Data point for the connection of the load history component . |
Activate mail dispatch |
Bidirectional |
(De) activates the entire mail dispatch. |
At least one station loads |
Output |
Outputs an on signal when at least one charging station is charging. |
Export MQTT Topics |
Input |
By specifying the storage path, the topics are exported as csv. |
MQTT connected |
Output |
If there is a connection to the MQTT broker, an ON signal is output, otherwise an OFF signal. |
Driver On/Off |
Bidirectional |
(De)Activate the component. |
Update trigger |
Input |
All inputs and outputs are updated with any signal. |
Distribute remaining current (delayed) |
Input |
With an on signal, the distribution of the remaining current is recalculated. If a station has more current available than it needs, the unused current can be redistributed to other stations. |
Distributor data |
Bidirectional |
Data point for the DLM distributor data component (see also connection schema) |
Distribution names |
Output |
Output of the distribution name as text. |
Time until update [s] |
Output |
The DLM data is updated after the time has elapsed. |
1 Note:
When using our SMARD component, a factor of 0.1 must be set there accordingly, as SMARD supplies the price in €/MWh by default.
The DLM will only allocate power to a charging station if the set maximum price (in the user editor or via the data point for the ID tag) is below the current price. Otherwise 0A will be allocated, UNLESS the global setting "Price limit - continue charging when started" is active, in which case charging will continue with minimum current.
Data points in the Distribution folder
Name |
Type |
Function |
|---|---|---|
Switch off |
Bidirectional |
With an ON signal, the distribution is switched off and there is no more management. |
Enable |
Output |
This output indicates whether charging is possible at this station (true) or not (false). |
Number of charging points |
Output |
Output of the number of charging points that are in the "Charging" status. This applies to this and all other sub-distributions. |
Number of charging points (local) |
Output |
Output of the number of charging points which are in the "charging" status. This only applies to this distribution and not to all other sub-distributions. |
At least one charging station is charging |
Output |
As soon as at least one station is in the charging mode, an ON signal is output. This applies to this and all other sub-distributions. |
At least one charging station is charging (local) |
Output |
As soon as at least one station is in the charging mode, an ON signal is emitted. This only applies to this distribution and not to all other sub-distributions. |
Priority |
Bidirectional |
Output or possibility to change the priority of the distribution |
Station |
Folder |
Description see below |
Current (Maximum) [A] |
Bidirectional |
Output or change possibility of the maximum current of the distribution |
Current (Minimum) [A] |
Bidirectional |
Output or modification possibility of the minimum current of the distribution system |
Current (reserve) [A] |
Bidirectional |
Output or modification possibility of the current reserve |
Current (assigned) [A] |
Output |
Output of the maximum current assigned to the distribution. |
Effective current (maximum) [A] |
Output |
Output of the effective, maximum, available current of the distribution (e.g. if a PV system would also feed in). |
Current measured L1 [A] |
Input |
Input for the measured current of the distribution |
Measured current L2 [A] |
Input |
Input for the measured current of the distribution |
Measured current L3 [A] |
Input |
Input for the measured distribution current |
Currents [A] |
Folder |
Description see below |
Current measurement valid |
Input |
If validation is set, an On signal must be present at this data point so that the measured values can be accepted. |
Transmitted energy (measured) - final value last month [Wh] |
Input |
Option of specifying the final energy value at the end of the last month. The energy consumption of the current month is derived from this (current total value - final value of last month)
|
Transmitted energy (measured) - consumption last month [Wh] |
Output |
Transferred energy of the last monthly period
|
Transferred energy (measured) - consumption current month [Wh] |
Output |
Transmitted energy of the current monthly period
|
Transmitted energy (measured) [Wh] |
Input |
Sets the total energy output above to a defined value. |
Transmitted energy (total) [Wh] |
Output |
Output for the total transferred energy. |
Data points in the Station folder
Name |
Type |
Function |
|---|---|---|
Switch off |
Bidirectional |
With an ON signal, the station is disabled and no more management takes place. |
Activate |
Output |
This output indicates whether charging is possible at this station (true) or not (false). |
Current user |
Output |
If a user has logged in, the name is output here. |
Current ID tag |
Output |
If a user has logged in, the ID tag is output here. |
Preferred charging point |
Output |
Due to 1 single-phase charging processes, some charging points can be marked as "Preferred" (true at this output). This provides a more symmetrical load due to the phase rotation of L1, L2 and L3. |
Charging point data on OCPP |
Bidirectional |
Connection to the charging station via EVCS or OCPP or... (see also connection diagram) |
Charging |
Input |
Input to start charging |
Only self-produced power |
Bidirectional |
With an ON signal, only self-produced power (for example from a PV system) is used for the charging station. |
Priority |
Bidirectional |
Output or change option of the priority of the distribution (0-10) |
Current (maximum) [A] |
Bidirectional |
Output or modification possibility of the maximum current of the station |
Current (minimum) [A] |
Bidirectional |
Output or change possibility of the minimum current of the station |
Current (assigned) [A] |
Output |
Set maximum current assigned to the charging station. |
Current effective (maximum) [A] |
Output |
Output of the effective, maximum, available current of the station (e.g. if a PV system would additionally feed in). |
Effective current (minimum) [A] |
Output |
Output of the minimum current of the station. |
Current [A] (measured) L1/L2/L3 |
Input |
Input for the measured current of the station. Measurement must be set in the channel editor for the data points to be visible. |
Currents [A] |
Folder |
Data points for output of currents not used but assigned. |
Transmitted Energy (Total) [Wh] |
Input |
The total transmitted energy of the station is transferred here. |
Transmitted energy (session) [Wh] Input |
Input |
The transmitted energy of the last charge at the station is transferred here. |
Data points in the folder Currents [A], each for L1, L2 and L3
Name |
Type |
Function |
|---|---|---|
Other (total) |
Output |
Total current not used by charging stations |
Other (Total local) |
Output |
Total current at this distribution which is not used by charging stations |
Other (sum sub-distribution) |
Output |
Total current from other sub-distributions that is not used by charging stations |
From Supply |
Output |
Current drawn from the supply line. |
Combined |
Output |
Sum of power supply and power from additional sources |
Charging stations (sum of sub-distributions) |
Output |
Current of the charging stations, which is drawn from additional sub-distribution boards. |
Charging stations (total) |
Output |
Current of all charging stations that is drawn at this distributor and also at its sub-distributors. |
Charging stations (total local) |
Output |
Current of all charging stations drawn from this distributor. |
Not used (related to maximum) |
Output |
Output of the currents that are not used. |
Not used (based on allocated current) |
Output |
Output of the currents that are not used by the station after allocation. |
Used (phase maximum) |
Output |
Output of the maximum current used for the charging stations. |
Additional sources (total) |
Output |
Output of the currents that come from additional sources of the distribution and also from further sub-distribution (for example PV system). It is the sum of Additional Sources (Sum Local) and Additional Sources (Sum Sub-distribution). |
Additional sources (sum local) |
Output |
Output of the currents that originate from additional sources only at this distribution (e.g. PV system). |
Additional sources (sum sub-distribution) |
Output |
Output of the currents that originate from additional sources that are fed in from the sub-distribution. |
Data points in the ID Tags folder
These data points can be used to change the "User/ID tags" settings at runtime.
Input only on the OCPP or only on the DLM. The ID tag import/export is used to synchronise OCPP and DLM.
name |
Type |
Function |
|---|---|---|
Expiry date |
Bidirectional |
Expiry date of the ID tag in the format dd.MM.yyyy - example: 06/06/2025 |
Limit to charging stations |
Bidirectional |
If this option is ON, the ID tag is limited to the specified charging stations. Off means that the tag can be used at any station |
Known ID tags |
Output |
Output of all taught-in ID tags so that they can be displayed in the list selection. |
Known charging stations (OCPP) |
Input |
Data point for the connection to the OCPP "Known station names [text]" |
Allow PV charging only |
Bidirectional |
Charging is only enabled via an ON signal if there is sufficient PV power. |
Remove authorised charging station |
Input |
A permitted charging station (station name) for the ID tag can be removed via a text entry. |
Add authorised charging station |
Input |
A permitted charging station (station name) can be added to the ID tag by entering text. |
Toggle authorised charging station |
Input |
A charging station can be added via a text entry or list selection. If this station already exists, it is removed. |
Allowed charging stations |
Bidirectional |
Input/output of all permitted charging stations, separated by semicolons |
Allowed charging stations - All |
Input |
With any command, all known charging stations are added to this ID tag. |
Allowed charging stations - None |
Input |
Any command is used to remove all known charging stations for this ID tag. |
Allowed charging stations (list view) |
Output |
Output for display in the list selection. |
ID |
Bidirectional |
Input for the selected ID tag from the list selection. |
Calendar limitation |
Bidirectional |
(De)activation of sharing only via calendar entries. |
Delete |
Input |
Delete the ID tag and all settings |
Send mail monthly |
Bidirectional |
(De)Activate the monthly e-mail. |
Send mail at end of transaction |
Bidirectional |
(De)Activate the e-mail at the end of the transaction. |
Mail address |
Bidirectional |
Input/output of the e-mail address for the report |
Maximum kWh price [ct] |
Bidirectional |
Maximum kWh price in cents for this user. 0 = no limit. The component receives the current electricity prices via the data point "Energy prices in ct/kWh [csv]". The format corresponds to the SMARD component.
|
Maximum flow |
Bidirectional |
Setting option for the maximum charging current. |
Minimum current |
Bidirectional |
Setting option for the minimum charging current. |
Name |
Bidirectional |
Input/output for the user name |
Priority |
Bidirectional |
A priority for the stations can be entered here. "0" the lowest and "10" the highest priority. |
Quota [kWh] |
Bidirectional |
The charging limit for this ID tag can be set by entering a value. |
Quota reset type |
Bidirectional |
Switching the reset method: 0 = manual, 1 = monthly and 2 = annual reset. |
Save |
Input |
Trigger to save the changes to the data points. |
Apply temporarily |
Input |
With any signal, the changes for priority and minimum/maximum charging current are accepted for the next transaction and then discarded. |
Properties of the component
Name |
Standard |
Function |
|---|---|---|
Channels |
0 |
Several distributions can be created in the channel editor. The charging stations are then assigned to the distributions. The description of the columns is listed in the "Channel editor" table. |
Define user |
0 |
The users of the system are created here. |
E-mail Server |
... |
Settings for the e-mail server that sends the messages to the users. |
Activate mail dispatch |
on |
(De) activates the entire e-mail dispatch. |
E-mail configuration |
|
Specification of the e-mail addresses and events that trigger an e-mail. |
MQTT Connection Settings |
|
Enter the MQTT broker data. |
MQTT Base Topic |
MyBase/DLM |
Setting for the base topic in MQTT. |
MQTT Retain |
|
If Retain is active, the last value from the client is retained at the broker. If a client or several clients connect to the broker again and have subscribed to this topic, this value is published immediately. |
Cyclical calculation - interval [s] |
60 |
All information and currents are updated at the set interval. |
Cyclical calculation after reactivation - interval [s] |
10 |
All information and currents are updated at the set interval. |
Validation of external measuring device |
|
Set to use an external measuring device for current measurement. If this measurement fails, a fallback (charging currents of the stations) is used |
Reserves only if measurement fails |
|
If deactivated, the reserve current from the channel editor is always used (deducted). Otherwise, the reserve is only used if the external measurement has failed. |
Use current measured values |
|
|
Offset sharing |
|
If active, the currents of stations with different priorities are increased evenly. Otherwise, the charging station with the highest priority receives the maximum current. |
On request, limit to 4kW per station |
|
If active, the power is limited to 4kW per charging point on request (data point of the component). Otherwise, it is limited to the defined minimum current of the charging point. |
Minimum change in measured values [mA] |
500 |
Measured values must change by at least the set value for a recalculation to be triggered. |
OCPP start delay [s] |
120 |
The distribution of the unused current is activated x seconds after the OCPP Ready signal is received. |
Log - CSV separator |
Semicolon |
Selection of the separator between the individual values. |
Log - Timestamp format |
dd.MM.yyyy HH:mm:ss |
Formatting setting for date and time. See also Formatting. |
Log - Culture |
de-DE |
Country setting for the display of numbers (e.g. thousands separator). |
Automatic backup |
|
Activation of the automatic backup function (upload to the EisBaer server with all DLM settings). |
Use user-specific FTP connection for automatic backup |
|
Activates or deactivates the user-specific connection. |
User-specific FTP connection for automatic backup |
|
Input option for the user-specific FTP connection. |
Continue PV charging if it has been started |
|
Activate to continue charging even if PV power is no longer available. |
Driver On/Off |
|
Defines whether the driver is activated automatically when the project is started. |
Channel editor
Name |
Description |
|---|---|
Name |
Freely definable name for the distribution and the stations |
Use (*) |
If checked, this distribution/station is used in the project, otherwise it does not contribute to the calculation. |
Type |
Setting whether this is a distribution, charging station or additional feed (PV or similar). |
Maximum current [A] (*) |
Specifies the maximum current that can be allocated. |
Minimum current [A] (*) |
Indication of the minimum current that can be allocated. |
Reserve [A] (*) |
The current reserve is not distributed among the charging stations. It is deducted from the maximum current. |
Distribute unused current (*) |
If a station has more electricity available than it needs, the unused electricity can be redistributed to other stations. |
Reserve Min Current [A] |
With this function, the charging station is always reserved the min current and is not distributed. |
PV only (*) |
Activate to use only the current of the additional supply. |
Measurement |
Distinguishes between no measurement, measurement with the additional supply or without measurement in the system. |
Setback Threshold [A] (*) |
The difference between the set current and the drawn current of a station must be greater than or equal to the setback threshold so that the current can be redistributed. |
Minimum difference [A] (*) |
If the current in the system changes by the value set here, the set currents for the stations are recalculated. |
Priority (*) |
A priority of the stations can be entered here. "0" is the lowest priority and "10" the highest priority. |
Ignore DLM package measurement |
By setting this, the measurement values that are sent via the DLM package are ignored. |
Charging stations can also be subsequently moved to other (sub-) distributions via "drag & drop".
Columns marked with an (*) can be edited together if several rows are selected.
Functionality:
Charging points:
- Station is or remains activated if the current not yet distributed is greater than the minimum current of a charging point
- If charging is currently taking place at the charging point, the assigned minimum current is deducted from the current still available for distribution
Distributions/multiple charging stations:
- Distributions are not deactivated, even if the current not yet distributed is less than the minimum current of a charging point
- If possible, the current currently used by the distribution + the set minimum current is allocated to the distribution
- The allocated current is deducted from the current still available for distribution (exception - the current used is less than the minimum current, in which case only the current currently used is deducted)
With distributions, care should be taken to ensure that the minimum current is high enough (if the supply lines and fuses allow it) so that all stations remain activated as far as possible during the start and initial distribution (it should be noted here that stations could already be charging at this moment and their minimum current is therefore not available for others and the distribution of the residual currents is only activated with a delay, depending on the setting). However, it should not be set too high, as this is then reserved for distribution and is not available for other distributions.
It has proved useful to use a starting point for distributions between 24A..32A. For complex and several parallel sub-distributions, we recommend a test project with simulation of charging points and simulating various charging park situations.
User:
Designation |
Description |
|---|---|
ID tag |
Enter the ID tag |
Name |
Sets the user name. |
Expiry date |
Entry of a validity date for the user |
Mail address |
E-mail address of the user. |
Send mail after transaction |
If this option is set, an email is sent to the user at the end of the transaction. |
Send monthly summary |
If this option is set, an email of all transactions in the past month will be sent to the user. |
Priority |
Specify the charging priority from 0 to 10. The higher the number, the higher the priority. |
Minimum Current [A] |
Specifies the minimum current that can be assigned. |
Maximum current [A] |
Indication of the maximum current that may be used. |
Max price [ct/kWh] |
The DLM will only allocate electricity to a charging station if the set maximum price is below the current price. |
Effect of Priority on Power Allocation
Priorities control the distribution of residual power via `childsByPriority`. With `childsByPriority.Keys.Reverse()`, the priority groups are processed in descending order—starting with the highest priority level. However, the effect depends crucially on the `OffsetSharing` flag:
Case 1: OffsetSharing == false (strict priority principle)
Before distribution, a preliminary calculation is performed for each priority group to determine the maximum amount of power its stations can still draw (MaxCurrent_Effective - TmpCurrentToSet). This demand is subtracted sequentially from the available remaining current (reaminingCurrentToShare_Tmp): The highest-priority group may draw up to its maximum, the next group receives only what remains after that, and so on. Lower priorities therefore receive nothing as long as higher priorities can consume all the current.
Case 2: OffsetSharing == true (Equal distribution with priority subordination)
Here, the remaining current is first distributed evenly among all stations capable of drawing current across all priority levels (additionalCurrentPerChargingStation = remaining current / total number). Each priority group receives a budget equal to the number of stations in the group multiplied by this share—priority thus has no influence on the initial allocation; each station receives the same offset.
Priority effect in both cases: Cascading of residual amounts
If a higher-priority group cannot fully consume its budget (e.g., due to GetActualCurrentLimit, charger reduction, or MaxCurrent_Effective), the unused remainder is passed on to the next lower-priority group via unusedCurrentToShareFromHigherPriorityGroup. In OffsetSharing, this is the only point at which priority has any effect at all: Higher priorities take precedence in “absorbing” unusable surpluses.
Within a priority group
The second sorting level is `energyInSession` (ascending). In the inner loop, charging stations are first balanced: As long as not all are at the same TmpCurrentToSet (allEven == false), the limit is capped at highestCurrent—so stations with lower supply catch up first, then all rise together.
Important Notes
•The function distributes only the additional power; power that has already been allocated is not redistributed (comment on line 1).
•PV-only stations (OnlySelfProducedCurrent_Effective) participate—regardless of priority—only if PV current (unasignedSelfProducedCurrent) is still available, and receive the minimum of the PV share and the normal share.
•Termination occurs when shares are < 0.5 A or when nothing changes anymore.
In short: When OffsetSharing == false, priority is the dominant allocation criterion (waterfall principle); when OffsetSharing == true, it plays only a secondary role through the redistribution of unused residuals.