This working group focusses on the communication between the charging station (EVerest) and the management system(s) (CPMS)
...
Meeting Notes:
20 March 2024
Discussed:
- Optional requirements:
- Long term EVerest should support as much functionality as possible.
- For now it is ok to skip optional requirements.
- If an optional requirement just allows (slightly) incorrect behaviou
- K01.FR.44 specific: we will not implement, this allows bad behavior from a CSMS, not ideal.
- Document implemented use case/functional requirements status:
- Add the list of use cases in one file in Github, make it a table
- Requirement number, status, remark
- Table per functional block
- Add status of Google Sheet in this file
- Add checkmark to the pull request template
Action Items:
- Robert: Make table of OCPP 2.0.1 function requirements in Github
- Robert: Move status from Google sheet into the github list
- Robert: Update pull request template: Add "list of functional requirements updated."
13 March 2024
Discussed
- WebSocket compression. Is required for an CSMS, optional for a Charging Station. But a really nice to have.
- How to setup security profile 2 and 3. Proposal to make an MRE to demonstrate this.
- PKI and governance and policies for validation of certificates
- Device Model
- Currently supports all standardized variables (specified in the OCPP2.0.1 spec)
- Defined mechanism to access EVSE and Connector components upcoming (Piet will create issue)
- Functional requirements are sometimes ambigous because its not clear to wich component a referenced variable belongs to
6 March 2024
Discussed:
- Pull requests: 440 & 452
- Possible multi-threading problem during reconnects and (re)sending message during reconnects: triggering another reconnect 3 seconds later.
- IdToken case insensitive, required by OCPP, where to handle this in EVerest? libOCPP? Some use cases might need case sensitive tokens.
...