Unlock Connector

Source: OCPP 1.6 Specification — Section 5.18 (Operation), Sections 6.53 / 6.54 (Messages)

Overview

Central System can request a Charge Point to unlock a connector. To do so, the Central System SHALL send an UnlockConnector.req PDU.

The purpose of this message: Help EV drivers that have problems unplugging their cable from the Charge Point in case of malfunction of the Connector cable retention. When an EV driver calls the CPO help-desk, an operator could manually trigger the sending of an UnlockConnector.req to the Charge Point, forcing a new attempt to unlock the connector. Hopefully this time the connector unlocks and the EV driver can unplug the cable and drive away.

The UnlockConnector.req SHOULD NOT be used to remotely stop a running transaction, use the Remote Stop Transaction instead.

Upon receipt of an UnlockConnector.req PDU, the Charge Point SHALL respond with an UnlockConnector.conf PDU. The response PDU SHALL indicate whether the Charge Point was able to unlock its connector.

If there was a transaction in progress on the specific connector, then the Charge Point SHALL finish the transaction first as described in Stop Transaction.

IMPORTANT: UnlockConnector.req is intended only for unlocking the cable retention lock on the Connector, not for unlocking a connector access door.

Sequence Diagram

Figure 40. Sequence Diagram: Unlock Connector

Central System  ──── UnlockConnector.req ────▶  Charge Point
                     (connectorId)
Central System  ◀─── UnlockConnector.conf ────  Charge Point
                     (status)

Initiator

Central System → Charge Point

Fields

UnlockStatus values

• Unlocked — Connector has been successfully unlocked.
• UnlockFailed — Failed to unlock the connector.
• NotSupported — Charge Point has no connector lock.

Examples

{
  "connectorId": 1
}

{
  "status": "Unlocked"
}

Schema

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