Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UK smart charging regulations random delay #538

Closed
corneliusclaussen opened this issue Feb 9, 2024 · 2 comments
Closed

UK smart charging regulations random delay #538

corneliusclaussen opened this issue Feb 9, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@corneliusclaussen
Copy link
Contributor

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.

@corneliusclaussen corneliusclaussen added the enhancement New feature or request label Feb 9, 2024
@corneliusclaussen corneliusclaussen changed the title UK smnart charging regulations random delay UK smart charging regulations random delay Feb 9, 2024
@corneliusclaussen
Copy link
Contributor Author

corneliusclaussen commented Feb 9, 2024

Implementation provided in #530

@corneliusclaussen
Copy link
Contributor Author

Closed as feature has been merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant