Skip to content
Documentation Menu

TC_066_CS — Get Composite Schedule

TC_066_CS — Get Composite Schedule

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 86.

Identification

FieldValue
Test case nameGet Composite Schedule
Test case IdTC_066_CS
System under testCharge Point

Description

The Central System sends 3 ChargingProfiles to a Charge Point and then requests (and validates) the composite schedule.

Purpose

To check whether the Charge Point is able to handle ChargingProfilePurposes as specified in OCPP.

Prerequisite(s)

  • The Charge Point supports the Smart Charging feature profile.
  • Configuration key MaxChargingProfilesInstalled is >= 3.
  • Configuration key ChargingScheduleMaxPeriods is >= 5.

Before (Preparations)

Configuration State(s):

  • N/a

Memory State(s):

  • F SetChargingProfile with ChargingProfile 1: chargingProfilePurpose is ChargingStationMaxProfile chargingProfileKind should be Absolute stackLevel should be 0 connectorId0 startSchedule<current dateTime - <Configured max time deviation> seconds> numberPhases<Configured numberPhases> ChargingSchedule: duration<86400 + <Configured max time deviation> seconds> chargingRateUnit<Configured chargingRateUnit>
  • Note: If <Configured chargingRateUnit> is W, then the limit field will be multiplied by 1000. startPeriod0, limit10

Reusable State(s):

  • N/a

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
2. The Charge Point responds with a GetCompositeSchedule.conf1. The Central System sends a GetCompositeSchedule.req

Tool validation(s)

Charge Point side:

Step 2:

(Message: GetCompositeSchedule.conf) statusAccepted connectorId is <Configured ConnectorId> ChargingSchedule: duration400 chargingRateUnit<Configured chargingRateUnit> scheduleStart<The time the GetCompositeSchedule.req was transmitted +/- <CoAnfigured max time deviation>> Note: If <Configured chargingRateUnit> is W, then the limit field will be multiplied by 1000. Note: The period of time between the scheduleStart from the SetChargingProfile.req with ChargingProfile 3 and the scheduleStart from the GetCompositeSchedule.conf is called x. RNote: The period of time between the scheduleStart from the SetChargingProfile.req with ChargingProfile 2 and the scheduleStart from the GetCompositeSchedule.conf is called y. startPeriod0, limit8 startPeriod(50 - x), limit10 startPeriod(200 - x), limit6 startPeriod(240 - x), limit10 startPeriod(260 - x + <Configured max time deviation>), limit8 startPeriod(300 - y + <Configured max time deviation>), limit10

Central System side:

Step 1:

(Message: GetCompositeSchedule.req)

  • connectorId is <Configured ConnectorId>
  • duration is 400
  • chargingRateUnit is <Configured Charging Rate Unit>

Expected result(s) / behaviour

Charge Point side:

The Charge Point is able to combine different ChargingProfiles from the Central System and return a composite schedule.

Central System side:

  • N/a