Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Case K09: Get Charging Profiles #309

Open
6 tasks
Tracked by #308
drmrd opened this issue Dec 14, 2023 · 1 comment
Open
6 tasks
Tracked by #308

Use Case K09: Get Charging Profiles #309

drmrd opened this issue Dec 14, 2023 · 1 comment
Labels
OCPP2.0.1 smart charging OCPP 2.0.1 Smart Charging Certfication Profile

Comments

@drmrd
Copy link
Collaborator

drmrd commented Dec 14, 2023

Scenario

  1. The CSMS asks the Charging Station for the installed charging profiles by sending a
    GetChargingProfilesRequest message.
  2. The Charging Station responds, indicating if it can report Charging Schedules by sending a
    GetChargingProfilesResponse message.
  3. Charging Station sends a number of ReportChargingProfilesRequest messages to CSMS.
  4. The CSMS acknowledges reception of the reports by sending a
    ReportChargingProfilesResponse to the Charging Station for every
    ReportChargingProfilesRequest.

Functional Requirements

  • K09.FR.01: When requestId is set in the GetChargingProfilesRequest, the Charging Station SHALL set the requestId in every ReportChargingProfilesRequest that is sent as a result of this GetChargingProfilesRequest.
  • K09.FR.02: When the charging profiles are reported in more than one ReportChargingProfilesRequest, the Charging Station SHALL set the tbc flag to true for all ReportChargingProfilesRequest messages except the last.
  • K09.FR.04: If evseId is set to a value greater than 0 in the GetChargingProfilesRequest, the Charging Station SHALL report the installed charging profiles for the specified EVSE that match all fields in chargingProfile.
  • K09.FR.05: If evseId is set to 0 in GetChargingProfilesRequest, the Charging Station SHALL only report charging profiles installed on the Charging Station itself (the grid connection) that match all fields in chargingProfile.
    • EVSE #0 can have a ChargingStation MaxProfile, ChargingStation ExternalConstraints or a TxDefaultProfile. Note, that a TxDefaultProfile is not applied to EVSE #0 but to all individual EVSEs (see K01.FR.14).
  • K09.FR.06: If evseId is NOT set in the GetChargingProfilesRequest, the Charging Station SHALL report all installed charging profiles that match all fields in chargingProfile.
  • Table 175, No. 7: When the Charging Station has no charging profiles that match the parameters in the GetChargingProfilesRequest the Charging Station SHALL respond with: NoProfiles.
@RobertDeLeeuw RobertDeLeeuw added the smart charging OCPP 2.0.1 Smart Charging Certfication Profile label Dec 18, 2023
@drmrd
Copy link
Collaborator Author

drmrd commented Jan 10, 2024

My team is actively working on this use case and others in the Smart Charging functional block.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCPP2.0.1 smart charging OCPP 2.0.1 Smart Charging Certfication Profile
Projects
None yet
Development

No branches or pull requests

2 participants