This working group focusses on the communication between the charging station (EVerest) and the management system(s) (CPMS)
...
Meeting Notes:
7 21 August 2024Cloud Communication: 2024-08-07
Development Update
- K08 pull request: processing review comments. Discussed some details. Datatype optimization not part of this PR yet, that is for the next PR.
- Component Schemas and configuration. Simplified the configuration to (re)initialize the database.
- Hardwired monitors are not possible to setup via the configuration: hardwired, factory default or pre-configured.
- California pricing for 2.0.1: hope to create a pull request soon.
- K02, K03, K04, K05 is almost done, feature branch is ready.
Smart Charging Alignment
- K01 PR: Small clean ups. Review can be requested.
- K08 PR: one of the OCTT beta test cases does not work. Piet will share the logs of the OCTT tool with Chris. As this is a beta test, so might also be a bug in OCTT.
- K09, K10: Is reviewed by AFS, when approved it can be merged.
Open Mic:
- https://github.com/EVerest/libocpp/issues/752
- The Python tools were always used without the non-modified files.
- The License does not allow to publish modified versions of the file
- We wont re-generate this code anymore. That has been done.
- Composite Schedule: Piet will add a function in EVerest core to retrieve the real composite schedule to be then used in libOCPP. PIONIX will work on this.
7 August 2024
Smart Charging Alignment
Coury: Pull Request for Smart Charging ready to merge: https://github.com/EVerest/libocpp/pull/711
Coury: Message handlers for Smart Charging are almost done: we can create a branch for early review, we still need to integrate the external constrains into the Energy Manager.
Piet: We can pick-up the implementation in the Energy Manager.
Marc: We will integrate in September. I will be on vacation coming weeks. PIONIX will take over my review tasks.
Open Issues:
https://github.com/EVerest/libocpp/issues/713
Coury: Proposal discussed last week to put Smart Charging profiles in the DB and reload into memory after reboot. But keeping them in-memory is no longer needed when stored in the DB. Proposal to make this a backlog item.
Agreed
https://github.com/EVerest/libocpp/issues/722
Coury: Unclear requirement from OCPP
Robert: I will look into this, I also see a question on the TWG mailing list for this.
https://github.com/EVerest/libocpp/issues/723
Coury: We implemented K01.FR.19 and 20 and already reject a message in that part.
Marc: K01.FR.19 and 20 are requirements for the CSMS, so no implmementation for EVErest really needed. 48 is the requirement for EVerest.
Device Model Integration:
Piet presented a proposal for a configuration service in EVerest. Simplifying to way variables can be defined in a EVerest module. Now not yet really possible, unless the API of the module is updated: extra call added.
https://github.com/EVerest/libocpp/tree/doc/variables-api/doc/variableAndConfigurationKeyIntegration
https://github.com/EVerest/everest-core/tree/doc/config-service/doc/config_service
...