TC_045_1_CSMS — Get Diagnostics

TC_045_1_CSMS — Get Diagnostics

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

Identification

Field	Value
Test case name	Get Diagnostics
Test case Id	TC_045_1_CSMS
System under test	Central System

Description

The Charge Point uploads a diagnostics log to a specified location based on a request of the Central System.

Purpose

The purpose of this test case it to check whether Central System can trigger the Charge Point to upload its diagnostics.

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 GetDiagnostics.conf to the Central System.	1. The Central System sends a GetDiagnostics.req to the Charge Point.
[The Charge Point starts uploading the diagnostics log.]; 3. The Charge Point sends a DiagnosticsStatusNotification.req to the Central System.	4. The Central responds with a DiagnosticsStatusNotification.conf to the Charge Point.
[The Charge Point has finished uploading the diagnostics log.]; 5. The Charge Point sends a DiagnosticsStatusNotification.req to the Central System.	6. The Central responds with a DiagnosticsStatusNotification.conf to the Charge Point.

Tool validation(s)

Charge Point side:

Step 3:

(Message: DiagnosticsStatusNotification.req) The status is Uploading

Step 5:

(Message: DiagnosticsStatusNotification.req) The status is Uploaded

Central System side:

• N/a

Expected result(s) / behaviour

Charge Point side:

The Charge Point has uploaded the diagnostics log to the location that was sent in step 1.

Central System side:

• N/a