TC_060_CS — Remote Start Transaction with Charging Profile - Rejected
TC_060_CS — Remote Start Transaction with Charging Profile - Rejected
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 94.
Identification
| Field | Value |
|---|---|
| Test case name | Remote Start Transaction with Charging Profile - Rejected |
| Test case Id | TC_060_CS |
| System under test | Charge Point |
Description
The Central System tries to start a transaction on a Charge Point but this is rejected.
Purpose
To check whether the Charge Point is able to reject a 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) |
|---|---|
| 2. The Charge Point responds with a RemoteStartTransaction.conf OR; with a CallError. | 1. The Central Systems sends a RemoteStartTransaction.req message to the Charge Point. |
Tool validation(s)
Charge Point side:
Step 2:
(Message: RemoteStartTransaction.conf) The status is Rejected OR (Message: CallError ErrorCode is PropertyConstraintViolation.
Central System side:
Step 1:
(Message: RemoteStartTransaction.req) The ChargingProfile.chargingProfilePurpose is NOT TxProfile
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a