This working group focusses on the communication between the charging station (EVerest) and the management system(s) (CPMS)
...
Meeting Notes:
26 June 2024
Development update:
- Variable Monitoring work is progressing, first parts are merged
- Some minor updates
- Smart Charging: JOET is working on Smart Charging, to get to a base that can merged in.
EVerest release 2024.6:
Feature Freeze expected today.
Starting two week test period.
Updated the OCPP roadmap
Discussion on Composite Schedules.
How to take local and minChargingRate into account.
Currently libOCPP calculates a CompositeSchedule and send that the the EnergyManager.
libOCPP calculates profile per EVSE, it does the load balancing.
EnergyManager does not get ChargePointMaxProfile, minChargingRate etc.
So it cannot take these parameters into account when it needs to limit below the CompositeSchedules given by libOCPP.
JOET will make a proposal for a solution.
05 June 2024
Discussed:
- Smart charging implementation collaboration until July
29 May 2024
Discussed:
- Couple of OCPP issues that have come up last weeks:
- ACPhaseSwitchingSupported
- 15118 certificate per EVSE: Solved in OCPP 2.0.1 edition 3 on page
- 2.0.1: MonitoringBase: Switching monitoring base not 100% clear: different terms used: delete, clear, discard customer monitors. All mean: delete.
- OCPP 1.6: Rounding meter values
Topics for the agenda next week:
- OCPP roadmap/timeline
22 May 2024
Discussed:
- Pull Request for K01 in draft, ready to review: https://github.com/EVerest/libocpp/pull/611
08 May 2024
Discussed:
- OCPP 2.0.1 edition 3 is out: same message, improved documentation. All known errata have been merged into the spec itself.
- ChargeX: MREC (Minimum required error codes)
https://inl.gov/chargex/mrec/
Discussed that this is now implemented in 1.6.
Refactoring of error handling in EVerest at the moment, that will effect this.
https://github.com/EVerest/everest-framework/pull/186
OCPP 2.0.1 still needs to be done.
NotifyEvent is implemented, but no functionality yet that triggers this.
- Discussed the problem found with root certificates in folders.
More background info. Certificate is printed, but only the old one.
Might not even have worked before.
- Discussed how to handle 15118 V2G certificate per SECC in case of multiple EVSE. OCPP certificate handling does not seem to support this where 15118-1 gives both options.
02 May 2024
Discussed:
- Composite Schedule calculation: https://lfenergy.zulipchat.com/#narrow/stream/417676-EVerest.3A-Cloud-communication/topic/Problem.20with.20ChargePointMaxProfile.20Usage
- AFS/JOET starts to implement composite schedule calculation for OCPP2.0.1
- Line voltage of 230V is currently hard-coded in the smart charging handler; will be made configurable
- Decision: libocpp shall reject ChargingProfiles in Amps in case it manages at least one DC EVSE.
- TxProfile must not necessarily be stored in non-volatile memory, see: https://github.com/EVerest/libocpp/issues/543
17 April 2024
Discussed:
- Database Migrations now merged. Documentation added to explain how it works. When migrating to this version the first version needs manuel work. After this it will be automatic.
- Size of PRs. Larger or small, pros and cons
- Discussed meeting format: stick to weekly. Try to discuss ongoing on next planned use cases.
10 April 2024
Discussed:
- OCPP 2.0.1 status document merged. When adding new OCPP 2.0.1 features, please update the document.
- Pull request for database migrations is open. Developer documentation will be added.
- Discussed how to handle custom data fields.
3 April 2024
Discussed:
- Function requirement status doc:
- OCPP 2.0.1 status: Piet checked all not yet completed
- OCTT 2.0.1 test cases status: Robert will convert sheet do markdown and put in EVerest documentation or core.
- Configurable TxStart/TxStop points:
- Proposal to put functionality for this in EVerest core, not libOCPP for now. Quicker to implement, this functionality can later be moved to libOCPP.
- Nobody requires this functionality in libOCPP already.
27 March 2024
Discussed:
- Drop websocketpp and move to libwebsockets
- moving websocketpp to new websocket interface appears to require a lot of effort
- discussion about dropping support for websocketpp → decision postponed
- Review pull request process
- Draft PRs can be used for internal reviews
- Once PR is converted for review the maintainers will start the review process
- How to get list of functional requirements up to date
- https://github.com/EVerest/libocpp/pull/540
- Maintainers will update the list
- JOET will update the list for smart charging
- List of past OCTT test cases
- We will not add this to libocpp since it cannot be guaranteed that tests pass only with using libocpp → Correct integration of libocpp is required
- Such a list could be added to everest-core
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.
Action Items:
- Put Signed MeterValues on Agenda General Call next week.
- Write documentation on how to change OCPP 2.0.1 CSMS URL.
21 February 2024
CSR flexibility
...