Get Diagnostics
Source: OCPP 1.6 Specification — Section 5.9 (Operation), Sections 6.25 / 6.26 (Messages)
Overview
Central System can request a Charge Point for diagnostic information. The Central System SHALL send a GetDiagnostics.req PDU for getting diagnostic information of a Charge Point with a location where the Charge Point MUST upload its diagnostic data to and optionally a begin and end time for the requested diagnostic information.
Upon receipt of a GetDiagnostics.req PDU, and if diagnostics information is available, then the Charge Point SHALL respond with a GetDiagnostics.conf PDU stating the name of the file containing the diagnostic information that will be uploaded. Charge Point SHALL upload a single file. Format of the diagnostics file is not prescribed. If no diagnostics file is available, then GetDiagnostics.conf SHALL NOT contain a file name.
While the upload is in progress and afterwards, the Charge Point informs the Central System of upload progress via DiagnosticsStatusNotification.req.
Sequence Diagram
Figure 30. Sequence Diagram: Get Diagnostics
Central System ──── GetDiagnostics.req ────▶ Charge Point
(location, retries?, retryInterval?, startTime?, stopTime?)
Central System ◀─── GetDiagnostics.conf ──── Charge Point
(fileName?)
Initiator
Central System → Charge Point
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| location | anyURI | 1..1 | Required. This contains the location (directory) where the diagnostics file shall be uploaded to. |
| retries | integer | 0..1 | Optional. This specifies how many times Charge Point must try to upload the diagnostics before giving up. If this field is not present, it is left to Charge Point to decide how many times it wants to retry. |
| retryInterval | integer | 0..1 | Optional. The interval in seconds after which a retry may be attempted. If this field is not present, it is left to Charge Point to decide how long to wait between attempts. |
| startTime | dateTime | 0..1 | Optional. This contains the date and time of the oldest logging information to include in the diagnostics. |
| stopTime | dateTime | 0..1 | Optional. This contains the date and time of the latest logging information to include in the diagnostics. |
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| fileName | CiString255Type | 0..1 | Optional. This contains the name of the file with diagnostic information that will be uploaded. This field is not present when no diagnostic information is available. |
Examples
{
"location": "ftp://diag-user:secret@diagnostics.example.com/uploads/",
"retries": 3,
"retryInterval": 60,
"startTime": "2026-04-25T00:00:00Z",
"stopTime": "2026-04-27T12:00:00Z"
}{
"fileName": "diagnostics-CP-2026-000123-2026-04-27.tar.gz"
}Schema
Source:
schemas/GetDiagnostics.json,schemas/GetDiagnosticsResponse.json(OCPP 1.6, JSON Schema draft-04)