Notify Charging Limit

Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.33 (Messages); Use Cases K11 — Set/Update External Charging Limit With Ongoing Transaction, K12 — Without Ongoing Transaction (Functional Block K. SmartCharging)

Overview

The Charging Station sends NotifyChargingLimitRequest to communicate to the CSMS a charging limit that was set by an external system (e.g. EMS, SO/DSO, Local Controller) — not by the CSMS via SetChargingProfile.

The message carries:

• The chargingLimit (source + flag whether it is grid-critical).
• An optional chargingSchedule[] describing the limit profile over time.
• An optional evseId (must be > 0 if present) — when omitted, the limit applies to the whole Charging Station.

Pairs with ClearedChargingLimit (K13) when the external limit is later released.

Sequence Diagram

Charging Station  ──── NotifyChargingLimitRequest ────▶  CSMS
                       (evseId?, chargingLimit, chargingSchedule[]?)
Charging Station  ◀─── NotifyChargingLimitResponse ────  CSMS

Initiator

Charging Station → CSMS

Fields

ChargingLimitType

Examples

{
  "evseId": 1,
  "chargingLimit": {
    "chargingLimitSource": "EMS",
    "isGridCritical": false
  },
  "chargingSchedule": [
    {
      "id": 1,
      "chargingRateUnit": "W",
      "chargingSchedulePeriod": [
        { "startPeriod": 0,    "limit": 11000.0 },
        { "startPeriod": 1800, "limit": 7400.0  }
      ]
    }
  ]
}

{}

Schema

Source: schemas/NotifyChargingLimitRequest.json, schemas/NotifyChargingLimitResponse.json (OCPP 2.0.1 FINAL)