TC_045_2_CS — Get Diagnostics - Upload Failed

TC_045_2_CS — Get Diagnostics - Upload Failed

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

Identification

Field	Value
Test case name	Get Diagnostics - Upload Failed
Test case Id	TC_045_2_CS
System under test	Charge Point

Description

When getting the diagnostics of a Charge Point, the upload of the log fails.

Purpose

Check whether the Charge Point can exchange valid messages for the situation that the upload fails when getting the 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 failed 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 UploadFailed

Central System side:

Step 1:

(Message: GetDiagnostics.req) retries is 0 location is ftp://127.0.0.1:21/files/failedLocation

Expected result(s) / behaviour

Charge Point side:

The Charge Point continues normal operation.

Central System side:

• N/a