Reset

Source: OCPP 1.6 Specification — Section 5.14 (Operation), Sections 6.39 / 6.40 (Messages)

Overview

The Central System SHALL send a Reset.req PDU for requesting a Charge Point to reset itself. The Central System can request a hard or a soft reset. Upon receipt of a Reset.req PDU, the Charge Point SHALL respond with a Reset.conf PDU. The response PDU SHALL include whether the Charge Point will attempt to reset itself.

At receipt of a soft reset, the Charge Point SHALL return to a state that behaves as just having been booted. If any transaction is in progress it SHALL be terminated normally, before the reset, as in Stop Transaction.

At receipt of a hard reset the Charge Point SHALL attempt to terminate any transaction in progress normally as in StopTransaction and then perform a reboot.

NOTE: Persistent states: for example, Connector set to Unavailable shall persist.

Sequence Diagram

Figure 35. Sequence Diagram: Reset

Central System  ──── Reset.req ────▶  Charge Point
                     (type)
Central System  ◀─── Reset.conf ────  Charge Point
                     (status)

Initiator

Central System → Charge Point

Fields

Field Name	Field Type	Card.	Description
type	ResetType	1..1	Required. This contains the type of reset that the Charge Point should perform.

ResetType values

Hard — Restart (reboot) of the Charge Point.
Soft — Return to a state that behaves the same as just after being booted.

ResetStatus values

Accepted — Command will be executed.
Rejected — Command will not be executed.

Examples

{
  "type": "Soft"
}

{
  "status": "Accepted"
}

Schema

Source: schemas/Reset.json, schemas/ResetResponse.json (OCPP 1.6, JSON Schema draft-04)

Request schema (JSON Schema)

Response schema (JSON Schema)