EV Charger Connector-Lock Fault Triage: Vehicle, Station or Reported Code?

Stop before triage when there is a hazard.

Do not touch or reconnect equipment with smoke, fire, arcing, a burning smell, abnormal heat, exposed conductors, collision damage, water ingress or visible connector damage. Keep people away and contact the site operator and local emergency services. Do not open an energized cabinet, bypass a lock or interlock, change protection settings, or perform live testing.

Step 1: identify what is physically retaining the connector.

1. Vehicle inlet: use the separate gated safe-release assistant and exact vehicle instructions. This triage result does not authorize removal.
2. Station socket or holster: do not force the station mechanism. Report the known asset and connector to the operator.
3. Will not lock or start: report the symptom and current session state. Do not improvise reconnection or reproduce the fault on another vehicle.
4. Unknown location: leave it unknown and ask the operator to reconcile existing evidence. Do not assign a failed part or guess which connector to control.

Step 2: keep the screen message and OCPP data separate.

Open Charge Alliance describes OCPP 1.6 StatusNotification with a standardized errorCode plus optional free-format info and vendorErrorCode fields. ConnectorLockFailure reports failure to lock or unlock a connector, but it does not authorize a mechanical release or identify a replaceable part by itself.

Do not copy a vehicle DTC, charger-screen code, OCPP 1.6 category, OCPP 2.0.1 event or manufacturer vendorErrorCode into one universal code table. Record the source and wording exactly.

Step 3: hand off the evidence, not a generic retry.

This guide and tool do not authorize reconnecting, resetting or repeating authorization attempts. Danger, damage or contamination, unconfirmed session state and recurring symptoms each require their own escalation. Ask the operator or manufacturer to review the exact equipment and applicable procedure; a browser checklist cannot establish those prerequisites.

The earlier “one ordinary reseat” wording has been removed from this article and its structured FAQ so that both match the tool's conservative guidance. No manufacturer-specific repair procedure is generalized here.

Bay 12 is not automatically connector 12.

In this fictional example, a driver reports a retained plug at parking bay 12. A support screenshot shows asset EVSE-A, connector 2 and a lock-related message, but nobody has established whether that record belongs to this bay. Similar numbers or nearby equipment do not establish the connection.

1. Keep the identifiers separate: write “reported bay: 12”, “backend record: EVSE-A / connector 2” and “mapping: unconfirmed”. These are illustrative labels, not a real customer record.
2. Reconcile existing records: ask the operator to check the installation asset map and matching session evidence. Preserve the original timestamp and time zone. Do not start another session or send commands to an assumed connector to discover its identity.
3. Keep the symptom separate from the code: record where the plug is reported held and the exact message source. An OCPP category is not proof of a failed vehicle latch or station part; vendor text and vehicle codes keep their own source labels.
4. Assign the next evidence task: name who will resolve the mapping and what remains unknown. Only then consider an equipment-specific support route, without treating identity confirmation as safety clearance.

The assistant now withholds vehicle/station routing when equipment identity or retaining location is unresolved, after its higher-priority danger, damage, session and recurrence checks. Editing answers clears old output. It reads your selections, not live device data, and does not validate an asset map.

If smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress is present, keep people away and contact the site operator and local emergency services. Do not approach the equipment to collect labels or photos. This original evidence workflow is not an OCA requirement or a mechanical-release procedure.

Open the connector-lock triage assistant ↗

One failed session is not permission for endless retries.

Consider an operator who has seen the same connector fail across several sessions. The latest session may now be stopped and the cable may look undamaged, but those two answers do not erase the recurrence. Our September 19 update routes repeated or intermittent symptoms directly to service review and removes the conflicting suggestion to reconnect once.

The tool checks possible danger first, then damage or contamination, then stopped-session confirmation, then recurrence. It stops at the first unresolved condition. A first-time, apparently undamaged result still does not authorize a retry or identify a defective part: the operator must consult the matching equipment instructions. The assistant uses user-entered observations, not device telemetry.

Keep three evidence records separate.

• Observed symptom: where the connector is held, what the user saw and whether it has happened before. Record uncertainty instead of guessing.
• Reported message: preserve exact text and its source—vehicle, station, app or protocol message. Do not turn similar wording into an assumed shared code.
• Support handoff: name the operator or manufacturer who will review it, the asset and connector involved, and the already observed session timeline. Do not reproduce a fault on more customer vehicles to gather evidence.

This is an original operational worksheet, not an OCA certification or a manufacturer's repair procedure. Run the gated lock-triage tool ↗ or prepare a sanitized incident brief ↗.

Evidence that shortens service escalation.

• Site, charger asset ID and connector or EVSE number
• Exact screen or app wording and its source
• OCPP version, status, errorCode, info and vendorErrorCode, when available
• Timestamp and time zone, session or transaction reference
• Vehicle make, model, model year, market and connector standard
• Whether the fault is first-time, recurring, or seen across multiple vehicles
• External condition photos only when it is safe to take them

Keep payment-card data, passwords, access tokens, personal identification and vehicle VINs out of shared incident records.

Will not lock and will not release need different evidence.

In OCA's OCPP 1.6 guidance, ConnectorLockFailure covers failure to lock or unlock. The category alone therefore cannot tell a support team which action the person observed. Preserve that distinction before assigning a vehicle or station part for repair.

Two fictional reports, not two diagnoses.

• Report A — start attempt: “The session did not start; the display mentioned a lock.” Record the exact display text and source, when the attempt happened, and whether energy transfer was ever confirmed. Do not upgrade “did not start” into a proven lock defect or an OCPP record.
• Report B — release attempt: “After the stop request, the plug remained held.” Record the stop request time, what the charger and vehicle each indicated, and any normal-unlock action already attempted. A stop request is not confirmation that charging stopped; missing or conflicting indications remain unresolved.
• Protocol evidence — only if available: attach the actual message with its version, timestamp and equipment identity. Keep errorCode, vendor fields, vehicle DTCs and screen wording in their own namespaces. Neither fictional report establishes that ConnectorLockFailure was sent.

The tool's final evidence prompts now follow the selected symptom. Danger, damage, unconfirmed stopped state, recurrence and unresolved identity still take priority; an invalid symptom selection requests clarification. This is an original support workflow, not a remote diagnostic, release instruction or OCA certification. The form reads your answers and cannot verify the equipment.

Use only existing observations and records. Do not reconnect, reset, force, pry, bypass a lock or protection, or repeat an action to complete a report. Electrical diagnosis belongs to qualified personnel. No mechanical emergency-release procedure is provided. For smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress, keep people away and contact the operator and local emergency services.

Build the symptom-specific lock-triage checklist ↗ · Prepare a sanitized incident brief ↗

One report says stopped. Another leaves the session unresolved.

A stopped message from one source does not resolve a conflicting or missing observation from the other side. Preserve each report with its source and time instead of choosing the most reassuring wording. This is an original support-handoff example, not a manufacturer-approved release procedure.

A fictional desk review.

• Station report: the operator's existing note records “Charging Stopped” at 14:10 PDT for the identified connector.
• Vehicle report: a driver note at 14:11 PDT says the charge indicator remains on; no current vehicle-side stopped confirmation is available. This does not establish a fault cause or prove that energy is still flowing.
• Unresolved field: retain both original observations. In this checklist, select session “Unknown” until the applicable equipment instructions and operator review establish the current stopped state. Do not translate an indicator, a stop request or a screen message into a universal protocol code.

For the fictional example only, suppose existing safe observations support no listed danger or damage, the equipment is identified and the connector has a repeated retained-plug history. Session Unknown produces “Confirm the stopped session” before the recurrence route. Changing the session to stopped after supported reconciliation clears the old result; running again still routes the repeated fault to service review. Stopped confirmation alone does not authorize removal, a retry or return to service.

Give the next reviewer a precise question.

Record the two sources, their original timestamps and time zones, the matching asset/session reference, what is missing, and who will resolve it. Ask the operator or vehicle manufacturer to reconcile the existing records using the exact equipment documentation. Do not overwrite the earlier note or claim that the later timestamp is automatically more reliable. Keep unnecessary personal information and credentials out of the handoff.

The assistant has one user-entered session field; it cannot compare two reports, read telemetry or establish that charging has stopped. Preserve the detail in a separate incident brief. If observations do not establish absence of danger, keep danger Unknown: the higher-priority danger gate remains in force.

No repeated stop/unlock commands, reconnects, extra-vehicle tests, force, mechanical release or protection bypass are requested. Electrical diagnosis belongs to qualified personnel. For smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress, keep people away and contact the operator and local emergency services. Do not approach for evidence.

Source check — October 30, 2026: ChargePoint's official stuck-connector guidance calls for stopped confirmation on both station and vehicle, points to the applicable vehicle manual and prohibits force/tools. Our two-report worksheet is an original way to preserve uncertainty; it is not a diagnostic rule supplied by ChargePoint. No generic waiting interval, key-fob pattern, restart or emergency-release step is adopted.

Check the unresolved-session route ↗ · Prepare a sanitized evidence handoff ↗

The plug released. Has the recurring incident been closed?

A later normal release is an observation about that event, not proof that a recurring problem has been repaired. Keep the latest outcome, previous occurrences and service disposition in separate records. This is our conservative support workflow, not a manufacturer-required test or a diagnosis.

A fictional handoff with three separate facts.

• Latest outcome: an existing operator report says charging was confirmed stopped and the plug subsequently released through the applicable normal procedure. Record the report's timestamp, time zone and source; do not repeat the action to verify it.
• History: the same identified connector has two earlier retained-plug reports. Keep their original references and wording. Do not rewrite the frequency as “First occurrence” because the latest attempt ended differently.
• Service disposition: no service assessment or return-to-use decision is documented. Record “pending operator/service review”, with an owner for that follow-up. Do not fill the gap with “fixed”, an assumed failed part or a made-up protocol code.

Map the history to the existing tool.

For this example only, use the reported stopped state, identified equipment and “Repeated on this connector” frequency. The observed condition describes the incident being reported, not a claim that the plug remains held now; put the later release in the separate incident brief. The form has no release-outcome or service-closure field and cannot verify either. Do not select “No listed danger signs observed” unless existing safe observations actually support it; otherwise leave uncertainty unresolved.

When danger and damage checks are clear and the session is confirmed stopped, repeated frequency still produces “Recurring fault: service review, not another retry.” Selecting an intermittent condition also retains this route even if frequency is mistakenly left at first occurrence. Unknown or present danger, damage/contamination and unconfirmed stopped state take priority. Changing inputs clears the previous result.

No further reconnect, reset, extra-vehicle trial or repeated unlock attempt is requested. Electrical diagnosis belongs to qualified personnel. The site operator and appropriate service team must determine the equipment-specific next action; this checklist grants no release or return-to-service permission. For smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress, keep people away and contact the operator and local emergency services. Do not approach for evidence.

Source check — October 21, 2026: ChargePoint's official stuck-connector guidance treats persistent sticking as a support issue and directs users to ChargePoint or the vehicle manufacturer. It also warns against force or tools and points to the applicable vehicle manual. We do not adopt its restart advice, key-fob patterns or mechanical-release steps. The other references below retain their earlier review dates; they were not freshly rechecked for this example.

Check the recurrence handoff ↗ · Record the later outcome in a sanitized incident brief ↗

Use the connector-lock triage assistant.

The assistant runs locally in the browser and builds a conservative ownership and evidence checklist. It does not diagnose energized equipment, decode vendor-specific errors or replace the exact vehicle and charger manuals.

Open connector-lock triage ↗

Primary sources.

ChargePoint and Open Charge Alliance references were retrieved again October 12, 2026. ABB and OSHA remain historical background from the earlier review, not newly verified sources for this identity-mapping example. Exact equipment documentation and local safety rules control the final action.

• ChargePoint — Removing a Stuck EV Connector ↗
• Open Charge Alliance — Improving Uptime Monitoring with OCPP v1.3 ↗
• ABB E-mobility — A400 CE manual, Rev. 004 ↗
• OSHA 29 CFR 1910.334 — Use of equipment ↗