Reset
Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.48 (Messages); Use Cases B11 — Reset - Without Ongoing Transaction, B12 — Reset - With Ongoing Transaction (Functional Block B. Provisioning)
Overview
The CSMS sends ResetRequest to ask the Charging Station (or a specific EVSE) to perform a reset. OCPP 2.0.1 changes the reset semantics from Soft/Hard to Immediate vs OnIdle:
Immediate— perform the reset right away, terminating any ongoing transaction.OnIdle— wait until all transactions have ended, then perform the reset.
Optionally, an evseId can be supplied to reset just that EVSE rather than the whole Charging Station.
Sequence Diagram
CSMS ──── ResetRequest ────▶ Charging Station
(type, evseId?)
CSMS ◀─── ResetResponse ──── Charging Station
(status, statusInfo?)
Initiator
CSMS → Charging Station
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| type | ResetEnumType | 1..1 | Required. Type of reset. |
| evseId | integer | 0..1 | Optional. Reset just this EVSE instead of the whole CS. |
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| status | ResetStatusEnumType | 1..1 | Required. Whether the CS is able to perform the reset. |
| statusInfo | StatusInfoType | 0..1 | Optional. Detailed status information. |
ResetEnumType values
Immediate— Reset immediately, terminating any ongoing transactions.OnIdle— Wait until current transaction(s) are finished, then reset.
ResetStatusEnumType values
Accepted, Rejected, Scheduled.
Examples
{
"type": "OnIdle"
}{
"type": "Immediate",
"evseId": 1
}{
"status": "Scheduled"
}Schema
Source:
schemas/ResetRequest.json,schemas/ResetResponse.json(OCPP 2.0.1 FINAL)