Symptom, operating context and diagnostic scope
Useful for: Fleet teams documenting range, battery, no-charge or interrupted-charge complaints for qualified EV service
A failed charge session can originate in the vehicle, battery controls, connector, charger, network, site power or environmental condition. The handover should preserve enough context for qualified diagnosis.
UNECE R100 addresses electric-powertrain and rechargeable-energy-storage safety where adopted. It does not prove that a specific vehicle has an approval or authorize service work.
Diagnostic inputs
Record these symptoms, conditions and service facts before parts are changed or a repair is approved:
- 01Vehicle, battery and software identity
- 02State of charge, warnings and diagnostic codes
- 03Charger, cable, connector and site-power details
- 04Charge-session start, stop and interruption record
- 05Ambient, battery and recent damage conditions
- 06Qualified isolation, repair and return-to-service process
Diagnostic decision matrix
Work through every row to separate symptoms from causes and define the evidence required before returning the vehicle to service.
Scroll horizontally to view all columns.
| Decision factor | What to choose or check | Limit or condition |
|---|---|---|
| Immediate safety | Follow OEM isolation, parking and emergency instructions for the observed condition. | Do not touch, move or charge a damaged vehicle without authorization. |
| Fault context | Capture codes and conditions before clearing or disconnecting where safe. | A cleared warning can remove evidence without correcting the cause. |
| System split | Test vehicle, connector, charger, communication and site power through approved methods. | One successful charger session does not identify every intermittent fault. |
| Return to service | Require documented repair, inspection and approved verification. | Charging once after reset is not necessarily a complete safety release. |
From symptom to verified corrective action
Preserve the symptom, isolate the affected system and confirm the result with a repeatable check instead of replacing parts by assumption.
- 01Describe the symptom
Commercial electric vehicle battery and charging-fault handover
- 02Record operating conditions
Vehicle, battery and software identity; State of charge, warnings and diagnostic codes
- 03Isolate the affected system
Immediate safety and Fault context must both pass.
- 04Verify corrective evidence
Vehicle, battery and software identity record; Fault-code and charge-session capture
Diagnostic evidence checklist
Ask for evidence that is traceable to the selected model, configuration, vehicle or project scope. A record from another project is context, not verification.
- Vehicle, battery and software identity record
- Fault-code and charge-session capture
- Qualified isolation and diagnostic report
- Repair, verification and return-to-service approval
Diagnostic failure modes
Clearing codes before capture
Better diagnostic control: Preserve the fault and operating context for qualified diagnosis.
Assuming the charger is faulty
Better diagnostic control: Separate vehicle, connector, charger, network and site power.
Opening the battery for inspection
Better diagnostic control: Use only trained, authorized high-voltage service and OEM procedures.
Limitations
- This page is not a high-voltage diagnostic, repair or emergency-response procedure.
- Qualified EV technicians, OEM instructions and applicable approval rules control service.
- Remove the vehicle or charger from service for damage, overheating, smoke, water exposure, insulation fault, exposed conductors or unresolved safety codes.
Evidence scope and technical basis
Each source is limited to what it can support. This makes the evidence chain readable to buyers, search engines and AI systems without turning a general source into a project claim.
Supports: Controls the project-input, quotation, approval and inspection workflow described in this guide.
Does not establish: It does not replace the signed quotation, approved specification, selected OEM documents or unit-linked project records.
Supports: Provides public checklists and worksheets; the signed project documents remain controlling.
Does not establish: It does not replace the signed quotation, approved specification, selected OEM documents or unit-linked project records.
Supports: Defines the relevant product family and published configuration boundaries. Project-specific ratings require the selected OEM documents.
Does not establish: It does not replace the signed quotation, approved specification, selected OEM documents or unit-linked project records.
Supports: Primary public guidance supporting route, dwell-time, charging-plan, procurement and infrastructure inputs. U.S. programs and examples are not global requirements.
Does not establish: It is authority, jurisdiction or subject specific and does not approve the selected vehicle for another destination or project.
Supports: Primary international regulation reference for electric-powertrain and rechargeable-energy-storage safety where adopted. Applicability and approval status must be confirmed for the vehicle and destination.
Does not establish: It is authority, jurisdiction or subject specific and does not approve the selected vehicle for another destination or project.