GetDiagnostics

Asks the charge point to upload a diagnostics file to a location you supply.

Version: OCPP 1.6
Direction: CSMS → Charge Point
Feature profile: Firmware Management

GetDiagnostics is the remote log pull. You give the charge point somewhere to upload to; it gathers its diagnostics and pushes them there, reporting progress via DiagnosticsStatusNotification.

The upload target is usually a pre-signed HTTP PUT URL or an FTP endpoint. The charger uploads directly, so the destination must be reachable from the charger's network.

Request

Field	Type	Required	Description
`location`	anyURI	Required	Where the charge point should upload the file.
`startTime`	dateTime	Optional	Include log entries from this time onward.
`stopTime`	dateTime	Optional	Include log entries up to this time.
`retries`	integer	Optional	How many times to retry a failed upload.
`retryInterval`	integer	Optional	Seconds between retries.

json

[2, "19223201", "GetDiagnostics", {
  "location": "https://diagnostics.example.com/upload/CP001",
  "startTime": "2026-09-08T00:00:00.000Z",
  "stopTime": "2026-09-09T00:00:00.000Z",
  "retries": 2
}]

Response

Field	Type	Required	Description
`fileName`	CiString255	Optional	The name of the file that will be uploaded. Absent means no diagnostics are available.

json

[3, "19223201", {
  "fileName": "CP001-diagnostics-20260909.tar.gz"
}]

Implementation notes

An empty response means there is nothing to upload. No fileName is not an error — it means the charger has no diagnostics for the requested window.

The file format is entirely vendor-defined. Nothing in OCPP says what is inside it.

Upload progress arrives through DiagnosticsStatusNotification, not through this response.