Comments (1)
- K16.FR.01: Precondition CSMS sends a new SetChargingProfileRequest. Charging Station SHALL respond with a SetChargingProfileResponse with status = Accepted.
- K16.FR.02: Precondition K16.FR.01. Charging Station SHALL initiate schedule renegotiation with EV. Note: In ISO 15118 this is done by replying with EVSENotification=ReNegotiation to a CurrentDemandReq (for DC) or ChargingStatusReq (for AC) message.
- K16.FR.03: Precondition K16.FR.02. Charging Station SHALL provide the ChargingSchedule data to the EV. Note: In ISO 15118 this is done in the ChargeParameterDiscoverRes message
- K16.FR.04: Precondition EV returns a charging profile. Charging Station SHALL verify that provided charging profile is within boundaries of the ChargingSchedule from CSMS. Note: In ISO 15118 EV may provide this as part of the PowerDeliveryReq message.
- K16.FR.05: Precondition K16.FR.04. Charging Station SHALL send the EV charging profile in a
NotifyEVChargingScheduleRequest
message to CSMS. - K16.FR.06: Precondition K16.FR.05 AND EV charging profile is within limits of CSMS ChargingSchedule. CSMS responds with
NotifyEVChargingScheduleResponse
with status Accepted to Charging Station. Note: Already checked by Charging Station, but CSMS does its own check. - K16.FR.07: Precondition K16.FR.05 AND EV charging profile is NOT within limits of CSMS ChargingSchedule.
CSMS responds withNotifyEVChargingScheduleResponse
with status Rejected to Charging Station. - K16.FR.08: Precondition K16.FR.07. CSMS starts new renegotiation as per use case K16.
- K16.FR.09: Precondition When the Charging Station receives charging needs from the EV. The Charging Station SHOULD NOT send a
NotifyEVChargingNeedsRequest
to the CSMS. Note: CSMS initiated the renegotiation and has just sent a new charging profile, based on the initial charging needs from EV, energy already consumed by EV and whatever information has caused CSMS to update the charging profile. In ISO 15118 charging needs are sent via ChargeParameter-DiscoveryReq. - K16.FR.10: Precondition K16.FR.04. The Charging Station SHOULD take the schedule from the
NotifyEVChargingScheduleRequest
into account when calculating the actual Composite schedule. - K16.FR.11: Precondition K16.FR.02 AND current or power in new charging schedule is lower than actual current or power. The Charging Station SHALL request EV to lower current or power to a value matching the new charging schedule at the first possible opportunity. Note: In ISO 15118 this can be communicated in CurrentDemandRes (for DC) or ChargingStatusRes (for AC).
- K16.FR.12: Precondition K16.FR.09 AND Charging Station sends a
NotifyEVChargingNeedsRequest
. The CSMS SHALL send aSetChargingProfileRequest
. This situation is not desirable, because charging profile will likely be the same as in K16.FR.01, but this is added for robustness when Charging Station is not adhering to K16.FR.09. - K16.FR.13: Precondition EV does not return a charging profile. Charging Station IS RECOMMENDED to return an EV charging profile as a chargingSchedule in a NotifyEVChargingScheduleRequest message to CSMS that matches the schedule that was selected by the EV (i.e. chargingSchedule.id = SAScheduleTupleId) In ISO 15118-2 the EV charging profile and the selected schedule are returned as ChargingProfile and SAScheduleTupleId in PowerDeliveryReq.
from libocpp.
Related Issues (20)
- v1.6: Persist scheuduled changeAvailablity.req HOT 1
- Support ocpp 2.0.1: 2.14.6. ISO15118V2GCertificateInstallationEnabled
- Security Event notifications sent even when regisration is not accepted
- Rounding of Meter Values HOT 1
- Variable Monitoring Backend
- DatabaseHandler::authorization_cache_clear() is missing a return value, causing undefined behaviour
- validate_value() fails due to string comparison with whitespaces
- Charging Station Availability State isn't updated
- Error management when received incorrect OCPP message. HOT 4
- Device Model Database initialization: Move from python to C++ HOT 1
- Extend device model interface and implementation for variable monitoring
- Allow configuration of MonitoringBase ( , , )
- DatabaseMigrationException after update from EVerest 2024-03 to 2024-05 HOT 3
- SetVariablesResponse not sent on password update HOT 1
- init_websocket throws exception when all networkprofilexcsmsurl values are empty HOT 1
- set_variable_attribute_value triggers "database is locked" HOT 2
- callback_minimal called, but data->owner is nullptr HOT 1
- Exception during start: ComponentVariable that doesn't exist in the device model storage HOT 7
- DateTime parsing exception prevents initial EVerest start HOT 5
- OCTT - TC_E_22_CS - TC_E_24_CS - TC_E_25_CS - Testcases Fail HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from libocpp.