Skip to content
Documentation Menu

TC_058_2_CS — Central Smart Charging - Wrong transactionId

TC_058_2_CS — Central Smart Charging - Wrong transactionId

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

Identification

FieldValue
Test case nameCentral Smart Charging - Wrong transactionId
Test case IdTC_058_2_CS
System under testCharge Point

Description

The Central System sets a schedule for a transaction (that is not running).

Purpose

To check whether a Charge Point is able to reject a schedule with the wrong ChargingProfilePurpose

Prerequisite(s)

The Charge Point supports the Smart Charging feature profile and no transaction is running.

Before (Preparations)

Configuration State(s):

  • N/a

Memory State(s):

  • N/a

Reusable State(s):

  • Charging

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
2. The Charge Point responds with a SetChargingProfile.conf message.1. The Central System sends a SetChargingProfile.req message with a connectorId and a ChargingProfile that includes a transactionId and a ChargingProfilePurpose .

Tool validation(s)

Charge Point side:

Step 2:

(Message: SetChargingProfile.conf) status is Rejected

Central System side:

Step 1:

(Message: SetChargingProfile.req) The ChargingProfilePurpose is TxProfile The connectorId equals the connectorId from step 5 (and is > 0). The transactionId does NOT equal the transactionId from step 6.

Expected result(s) / behaviour

Charge Point side:

The Charge Point rejects the SetChargingProfile.req message.

Central System side:

n/a.