ReportChargingProfiles

SmartCharging CS->CSMS OCPP 2.0.1

Sent by the Charging Station to deliver the results of a GetChargingProfiles request, reporting the currently installed charging profiles.

Quick Reference

Required Fields

requestId integer

The requestId from the GetChargingProfiles request

chargingLimitSource ChargingLimitSourceEnumType

Source of the reported profiles: EMS, Other, SO, or CSO

evseId integer

EVSE these profiles apply to

chargingProfile array[ChargingProfileType]

List of charging profiles installed on the station

Optional Fields

tbc boolean

To Be Continued - true if more messages will follow for this requestId

Example Payload

{
  "requestId": 1,
  "chargingLimitSource": "CSO",
  "evseId": 1,
  "tbc": false,
  "chargingProfile": [
    {
      "id": 1,
      "stackLevel": 0,
      "chargingProfilePurpose": "TxDefaultProfile",
      "chargingProfileKind": "Relative",
      "chargingSchedule": [
        {
          "id": 1,
          "chargingRateUnit": "W",
          "chargingSchedulePeriod": [
            {
              "startPeriod": 0,
              "limit": 7400
            }
          ]
        }
      ]
    }
  ]
}

Example Full Frame

[
  2,
  "msg-001",
  "ReportChargingProfiles",
  {
    "requestId": 1,
    "chargingLimitSource": "CSO",
    "evseId": 1,
    "tbc": false,
    "chargingProfile": [
      {
        "id": 1,
        "stackLevel": 0,
        "chargingProfilePurpose": "TxDefaultProfile",
        "chargingProfileKind": "Relative",
        "chargingSchedule": [
          {
            "id": 1,
            "chargingRateUnit": "W",
            "chargingSchedulePeriod": [
              {
                "startPeriod": 0,
                "limit": 7400
              }
            ]
          }
        ]
      }
    ]
  }
]

Format: [MessageType, MessageId, Action, Payload]

Overview

ReportChargingProfiles delivers the list of installed charging profiles in response to a GetChargingProfiles request. Large profile sets may be split across multiple messages using tbc.

Expected Response

Empty response {}.

Usage Notes

  • Use tbc: true if there are more profiles to report
  • The final message must have tbc: false or omit the field
  • requestId must match the GetChargingProfiles request

Testing Tips

  • Install multiple profiles, request all, and verify all are returned in the report
  • Test pagination with tbc: true for large profile sets