Skip to content
Documentation Menu

TC_019_1_CSMS — Retrieve all configuration keys

TC_019_1_CSMS — Retrieve all configuration keys

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

Identification

FieldValue
Test case nameRetrieve all configuration keys
Test case IdTC_019_1_CSMS
System under testCentral System

Description

The Central System is able to retrieve all available configuration keys.

Purpose

To check whether the Central System is able to retrieve all Configuration keys and whether the Charge Point has all required keys configured.

Prerequisite(s)

  • N/a

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 GetConfiguration.conf.1. The Central Systems sends a GetConfiguration.req message to the Charge Point.

Tool validation(s)

Charge Point side:

Step 2:

(Message: GetConfiguration.conf)

  • accessibility contains the following values. Core: Configuration Key / accessibility AuthorizeRemoteTxRequests / R or RW ClockAlignedDataInterval / RW ConnectionTimeOut / RW ConnectorPhaseRotation / RW GeAtConfigurationMaxKeys / R HeartbeatInterval / RW LocalAuthorizeOffline / RW LocalPreAuthorize / RW MeterValuesAlignedData / RW MeterValuesSampledData / RW MeterValueSampleInterval / RW RNumberOfConnectors / R ResetRetries / RW StopTransactionOnEVSideDisconnect / RW StopTransactionOnInvalidId / RW StopTxnAlignedData / RW StopTxnSampledData / RW SupportedFeatureProfiles / R TransactionMessageAttempts / RW TransactionMessageRetryInterval / RW UnlockConnectorOnEVSideDisconnect / RW Local Auth List Management: LocalAuthListEnabled / RW LocalAuthListMaxLength / R SendLocalListMaxLength / R Smart Charging Profile: ChargeProfileMaxStackLevel / R ChargingScheduleAllowedChargingRateUnit / R ChargingScheduleMaxPeriods / R MaxChargingProfilesInstalled / R Reservation: None Remote Trigger: None

Central System side:

Step 1:

(Message: GetConfiguration.req) The key is <Empty>

Expected result(s) / behaviour

Charge Point side:

All required keys are configured.

Central System side:

The Central System is able to retrieve the values of all requested configuration keys.