You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UK smart charging regulations require a random delay whenever the charging current changes, either because of a start/stop of charging or if the current is adapted during charging (e.g. from 16 to 8 amps or 8 amps to 16 amps). The delay needs to be adjustable and should default to 600 seconds.
There are excemptions when the delay requirement does not apply, i.e. whenever the reason for the current change event itself was already sufficiently random.
The idea behind this is that all reasons for changing grid load that are synchronized over larger areas could cause problems in the power grid. E.g. When power comes back after a blackout not all EVs should start charging at the same time. But also a schedule coming from OCPP that is based on price signals is synchronized with many chargers and needs to have a random delay.
Finding out the root cause for a requested current change and verify whether it is already random or not is beyond the scope of everest-core. We should however implement helper functionality to enable those random delays and give external processes the possibility to cancel/enable/disable them.
The text was updated successfully, but these errors were encountered:
The UK smart charging regulations require a random delay whenever the charging current changes, either because of a start/stop of charging or if the current is adapted during charging (e.g. from 16 to 8 amps or 8 amps to 16 amps). The delay needs to be adjustable and should default to 600 seconds.
There are excemptions when the delay requirement does not apply, i.e. whenever the reason for the current change event itself was already sufficiently random.
The idea behind this is that all reasons for changing grid load that are synchronized over larger areas could cause problems in the power grid. E.g. When power comes back after a blackout not all EVs should start charging at the same time. But also a schedule coming from OCPP that is based on price signals is synchronized with many chargers and needs to have a random delay.
Finding out the root cause for a requested current change and verify whether it is already random or not is beyond the scope of everest-core. We should however implement helper functionality to enable those random delays and give external processes the possibility to cancel/enable/disable them.
The text was updated successfully, but these errors were encountered: