Fault detection is the capability of an EV charger, charging site, or charging network to identify abnormal conditions—electrical, mechanical, thermal, or software-related—so the system can protect safety, maintain reliability, and trigger corrective actions. Effective fault detection is essential for uptime, safe operation, and fast maintenance response.
What Is Fault Detection?
Fault detection is the process of monitoring signals and system states to recognize when something is wrong.
– Detects faults in the charger (power electronics, contactors, sensors, firmware)
– Detects faults in the electrical installation (earthing issues, protection trips, supply problems)
– Detects faults in communication and backend integration (OCPP errors, connectivity loss)
– Detects user-facing failures (authentication errors, payment failures, connector issues)
Fault detection includes both real-time protection (stop charging immediately) and diagnostic detection (log and report issues for maintenance).
Why Fault Detection Matters in EV Charging
– Protects users and vehicles through safe shutdown and fail-safe operation
– Reduces downtime by enabling quicker troubleshooting and repair
– Prevents repeated failed sessions that damage customer experience and trust
– Lowers service cost through accurate root-cause identification and fewer unnecessary site visits
– Enables proactive maintenance by catching degradation early (fans, connectors, insulation)
– Supports warranty workflows with evidence (logs, timestamps, fault codes)
Types of Faults Commonly Detected
Electrical Protection Faults
– Ground fault / earth leakage detected
– Overcurrent and short-circuit events (often via protective devices or internal sensing)
– Over/undervoltage, phase loss, or supply instability
– Insulation resistance issues or abnormal leakage behavior
– Incorrect wiring conditions (polarity/phase issues where applicable)
Thermal Faults
– Overtemperature in power electronics, contactors, or internal hotspots
– Connector or cable overheating (temperature sensors, derating thresholds)
– Fan failure or reduced airflow leading to rising temperatures
– Environmental issues affecting thermal performance (blocked vents, dust)
Mechanical and Interface Faults
– Connector lock failures and plug detection errors
– Socket shutter issues (where applicable)
– Service door tamper events (if monitored)
– Physical impact or enclosure integrity issues (site-dependent sensors)
Communication and Backend Faults
– Loss of CPMS connectivity (network, SIM, router, firewall)
– OCPP handshake failures, authorization errors, message timeouts
– Clock/time sync errors affecting logs and receipts
– Configuration push failures and inconsistent parameter states
Payment and Authentication Faults
– RFID read failures or invalid credentials
– EMV terminal faults, declined authorizations, payment timeouts
– Roaming authorization failures and settlement data errors
– User workflow failures (app start issues, QR flow interruptions)
How Fault Detection Works
Fault detection relies on layered monitoring and logic.
– Sensors and measurements: voltage, current, temperature, insulation, fan RPM
– State monitoring: contactor status, connector state, lock state, relay feedback
– Thresholds and rules: trip points, derating curves, timeout rules
– Watchdog and self-tests: detect firmware crashes or abnormal behavior
– Event logging: fault codes, timestamps, severity levels, context values
– Remote reporting: send fault status to CPMS for alerts, dashboards, and ticketing
Fault Detection Outcomes
When a fault is detected, systems typically respond in one of these ways:
– Immediate shutdown for safety-critical faults (ground fault, severe overcurrent, critical overtemperature)
– Derating for thermal or partial failures (reduced power to stay safe)
– Retry and recovery for transient issues (communication dropouts, temporary supply dips)
– Lockout until manual inspection for serious faults or repeated events
– Alerting via CPMS: ticket creation, maintenance dispatch, SLA escalation
Best Practices for Reliable Fault Detection
– Use clear, standardized fault codes with severity levels and recommended actions
– Include context in logs (measurements, states, last commands) to enable remote diagnosis
– Differentiate transient vs persistent faults to avoid nuisance downtime
– Validate sensors and use plausibility checks to reduce false positives
– Integrate alerts with maintenance workflows (SLA, spare parts, technician dispatch)
– Use commissioning checklists to ensure protective devices and sensors behave correctly
– Track recurring fault patterns to improve product design and site installation standards
Common Issues to Avoid
– Too-sensitive thresholds that cause nuisance trips and customer frustration
– Fault codes that are generic (“error”) without actionable detail
– Missing time synchronization leading to unusable logs and difficult investigations
– Poor connectivity that prevents fault reporting to the backend
– No correlation between site events (breaker trips) and charger logs, slowing root-cause analysis
Limitations to Consider
– Fault detection depends on sensor quality and correct calibration/placement
– Some site-level issues require external measurements (power quality, earthing resistance) beyond the charger
– Roaming and payment ecosystems can hide root cause if data exchange is incomplete
– Overly aggressive auto-recovery can mask underlying safety issues; lockout rules are still needed
– True predictive maintenance requires historical data and analytics, not only real-time detection
Related Glossary Terms
Charger Diagnostics
Fault Recovery
Fail-Safe Operation
Electrical Commissioning
Charging Uptime
OCPP
Ground Fault Protection
Overcurrent Protection