Energy Management (DLM)

Q: Why does the charger ignore new DLM power limits or charging profiles?
A: Common causes include unsupported SetChargingProfile commands by the charger, rejected profile updates, or firmware limitations. Always verify charger compatibility and response logs.

Q: Can DLM limits be set lower than the charger's max configuration?
A: Yes. DLM can override the charger's physical max current to meet grid constraints or prioritize other infrastructure. Chargers will follow the most restrictive profile received.

Q: Why does the system apply a 0A profile unexpectedly?
A: If external meter data reports zero or unstable load, the platform may temporarily restrict EV charging to prevent grid instability. A 0A profile is a safety fallback. Additionally, eMabler DLM sets a 0A default charging profile for all chargers, that is overwritten with a non-0A profile when a transaction starts. This is done because of fuse-protection in scenarios where the internet connectivity is cut unexpectedly.

Q: How is MaxCurrent dynamically adjusted based on external loads?
A: The system calculates EffectiveMaxCurrent as:
MaxCurrent - External Load - Load Margin (e.g., 3A).
This ensures small fluctuations don’t continuously trigger profile changes. Load margin avoids system oscillation.

Q: What is the role of the Notification & Control System in energy management?
A: It reacts to triggers like meter changes, MaxCurrent updates, or spot price shifts in real time using Azure Functions. Actions include recalculating EffectiveMaxCurrent, redistributing profiles, or pausing/resuming chargers automatically.

Q: Does the platform support utility or DSO-imposed limits?
A: Yes. MaxCurrent and DLM settings can reflect externally imposed grid caps or DSO limits, helping avoid regulatory penalties and ensuring infrastructure compliance.