Skip to content
Documentation Menu

TC_N_25_CS — Retrieve Log Information - Diagnostics Log - Success

TC_N_25_CS — Retrieve Log Information - Diagnostics Log - Success

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block N. Diagnostics, page 285.

Identification

FieldValue
Test case nameRetrieve Log Information - Diagnostics Log - Success
Test case IdTC_N_25_CS
Use case Id(s)N01
Requirement(s)N01.FR.01, N01.FR.02, N01.FR.04, N01.FR.07, N01.FR.08, N01.FR.09, N01.FR.13
System under testCharging Station
Functional blockN. Diagnostics

Description

This test case covers the functionality of getting log information from a Charging Station. The CSMS can request a Charging Station to upload a file with log information to a given location (URL). The format of this log file is not prescribed. The Charging Station successfully uploads a log file and gives information about the status of the upload by sending status notifications to the CSMS.

Purpose

To verify if the Charging station is able to successfully upload a log as described at the OCPP specification.

Prerequisite(s)

  • Charging Station has log information available.
  • A diagnostics logging server has been setup supporting one of the file transfer protocols supported by the Charging Station (This is configured at the configuration variable FileTransferProtocols).

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
2. The Charging Station responds with a GetLogResponse1. The OCTT sends a GetLogRequest; with logType DiagnosticsLog
Note(s):; - Charging Station is uploading log file
3. The Charging Station sends a LogStatusNotificationRequest4. The OCTT responds with a LogStatusNotificationResponse
Note(s):; - Log file is uploaded
5. The Charging Station sends a LogStatusNotificationRequest6. The OCTT responds with a LogStatusNotificationResponse

Tool validations

Step 2:

Message GetLogResponse

  • status Accepted
  • filename not omitted AND not empty

Step 3:

Message LogStatusNotificationRequest

  • status Uploading
  • requestId Same Id as the GetLogRequest

Step 5:

Message LogStatusNotificationRequest

  • status Uploaded
  • requestId Same Id as the GetLogRequest

Post scenario validations

  • N/a