NotifyEVChargingSchedule

SmartCharging CS->CSMS OCPP 2.0.1

Sent by the Charging Station to forward the charging schedule proposed by the EV via ISO 15118 power delivery negotiation.

Quick Reference

Required Fields

timeBase string (date-time)

Reference time base for the schedule

evseId integer

EVSE where the EV proposed the schedule

chargingSchedule ChargingScheduleType

The charging schedule proposed by the EV

Example Payload

{
  "timeBase": "2024-01-15T10:00:00Z",
  "evseId": 1,
  "chargingSchedule": {
    "id": 1,
    "chargingRateUnit": "W",
    "chargingSchedulePeriod": [
      {
        "startPeriod": 0,
        "limit": 11000
      },
      {
        "startPeriod": 7200,
        "limit": 7400
      }
    ]
  }
}

Example Full Frame

[
  2,
  "msg-001",
  "NotifyEVChargingSchedule",
  {
    "timeBase": "2024-01-15T10:00:00Z",
    "evseId": 1,
    "chargingSchedule": {
      "id": 1,
      "chargingRateUnit": "W",
      "chargingSchedulePeriod": [
        {
          "startPeriod": 0,
          "limit": 11000
        },
        {
          "startPeriod": 7200,
          "limit": 7400
        }
      ]
    }
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

NotifyEVChargingSchedule forwards the power delivery schedule that the EV proposed during ISO 15118 negotiation. The CSMS can use this to validate or adjust the schedule via SetChargingProfile.

Expected Response

status: Accepted or Rejected

Usage Notes

This is part of the ISO 15118 smart charging flow
The CSMS can accept or override the EV-proposed schedule
Used in conjunction with NotifyEVChargingNeeds

Testing Tips

Send an EV-proposed schedule and verify the CSMS responds with Accepted or adjusts it via SetChargingProfile

Common Errors

`TypeConstraintViolation`

Cause: chargingSchedule is not wrapped in an object

Solution: chargingSchedule must be a ChargingScheduleType object with id, chargingRateUnit, and chargingSchedulePeriod