TC_059_CS — Remote Start Transaction with Charging Profile
TC_059_CS — Remote Start Transaction with Charging Profile
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 93.
Identification
| Field | Value |
|---|---|
| Test case name | Remote Start Transaction with Charging Profile |
| Test case Id | TC_059_CS |
| System under test | Charge Point |
Description
The Central System starts a transaction on a Charge Point with a ChargingProfile
Purpose
To check whether the Charge Point is able to start a transaction with a Charging Profile initiated from the Central System.
Prerequisite(s)
The Charge Point supports the Smart Charging feature profile.
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- N/a
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 1. Execute Charging with a ChargingProfile with purpose TxProfile. | |
| 3. The Charge Point responds with a GetCompositeSchedule.conf | 2. The Central System sends a GetCompositeSchedule.req |
Tool validation(s)
Charge Point side:
Step 3:
(Message: GetCompositeSchedule.conf)
- status should be Accepted
- connectorId should be <Configured ConnectorId>
- The chargingSchedule fields:
- duration should be <Configured duration>
- chargingRateUnit should be <Configured Charging Rate Unit>
- Between startSchedule and the current time should be equal or fewer seconds than <Configured Max Time Deviation>
- chargingSchedulePeriod should be calculated accordingly.
Central System side:
Step 2:
(Message: GetCompositeSchedule.req)
- connectorId is <Configured ConnectorId>
- duration is <Configured duration>
- chargingRateUnit is <Configured Charging Rate Unit>
Expected result(s) / behaviour
Charge Point side:
A transaction is started on the Charge Point and the profile sent by the Central System is followed by the Charge Point.
Central System side:
- N/a