This working group focusses on the communication between the charging station (EVerest) and the management system(s) (CPMS)
Meeting Notes:
14 February 2024
General updates
- PR and issue templates merged (https://github.com/EVerest/libocpp/pull/436)
- Ongoing work and improved stability of libwebsockets implementation
Smart Charging implementation: https://github.com/EVerest/libocpp/issues/468
- Slight incompatabilities between 1.6 and 2.0.1 for Smart Charging make it hard to find a common implementation for both
- Decision made to have separate implementations of OCPP1.6 and OCPP2.0.1 Smart Charging
OCPP Test naming convention: https://github.com/EVerest/libocpp/issues/467
Status: Websocket refactor update @Soumya Subramanya @Maaike Zijderveld @Marc Emmers
- Maaike will continue to work on the refactor and use this PR: https://github.com/EVerest/libocpp/pull/410
Auth Cache Cleanup PR: https://github.com/EVerest/libocpp/pull/243
- Will be used as an example for the database migrations discussed here: https://github.com/EVerest/libocpp/issues/450
7 February 2024
When to send signed meter values
- End of the transaction is most logical.
- Looks like code currently does not store values in the DB.
- An libOCPP API change is needed to merge the signed meter values pull request.
- The is an existing old pull request that also provides such a change.
DB Migration tools: See issue: https://github.com/EVerest/libocpp/issues/450
- List of tools to investigate:
- Action Item: Robert will ask LFE for tools used in other projects.
Status OCPP 2.0.1 development:
- Shared sheet is not updated. Current coverage is getting to 100%, but that is not reflected in the sheet as agreed.
- OCTT takes about 2 days to run all tests manually, API for CI/CD integration not yet available
- Action Item: Robert will ask OCA about potential license issues with OCTT running in LFE build pipelines.
31 January 2024:
Faking MeterValue
- Make faking MeterValue and TransactionEvent timestamps a configurable feature
- Keep talking to OCA and OCTT team to find out more detailed requirements
Websocket refactoring:
- Alfen to work on charge_point and websocket interface
- Pionix to support on websocketpp and libwebsocket implementations of the interfaces
- Discussion how we split up PRs (between interfaces and implementations) still ongoing @Soumya to provide feedback
Smart Charging:
- Bug found within clear charging profiles: https://github.com/EVerest/libocpp/issues/432
- Agreed on common base classes for OCPP1.6 and OCPP2.0.1 Smart Charging handling
- Goal is to reuse as much of OCPP1.6 implementation for common smart charging implementation