Common EV Charger Installation Faults Caught by Testing

Why these faults are usually invisible without the right test

An EV charger that looks correctly installed, is properly labelled, and shows the expected voltage on a basic check can still fail to charge a real vehicle safely or at all. This is because the faults that actually cause problems in the field are almost never visible defects; they are electrical or protocol-level issues that only manifest when the charger's full sequence, control pilot signalling, protective device operation, and (for DC) digital communication, is actually exercised. This is the entire rationale for a defined commissioning test sequence rather than a visual inspection and a spot voltage check.

Control pilot signal faults

The control pilot (CP) circuit, explained in detail in our IEC 61851-1 guide, is where a surprising share of real-world faults originate. Common issues an analyzer's CP waveform capture will surface include: an incorrect duty cycle being generated (telling a vehicle it can draw more or less current than the circuit actually supports), a distorted or noisy PWM waveform caused by poor wiring or electromagnetic interference from nearby equipment, and incorrect handling of the state transitions between "vehicle connected" and "charging," which can cause some vehicle models to refuse to charge even though others tolerate the same fault. Because different vehicle manufacturers implement their CP state-machine logic with slightly different tolerances, a charger that "works fine" with one test vehicle can still have a marginal CP fault that only some other vehicle models will refuse to accept, which is exactly why an instrument-based pass/fail test against the IEC 61851-1 tolerance, rather than a single real-vehicle trial, is the reliable way to confirm compliance.

Missing or incorrect residual current protection

As covered in detail in our RCD and RDC-DD testing guide, one of the more consequential and easy-to-miss installation gaps is fitting a standard Type A RCD on an EV charging circuit without genuine RDC-DD (smooth DC leakage) protection, whether as a stand-alone module or via a Type B RCD. This installation will pass a routine AC-only RCD trip test performed with a general-purpose tester, because that test never exercises the DC leakage fault path the RDC-DD exists to catch. Only a combined test, such as the one built into the Fluke FEV350, actually verifies both protective functions and reveals this specific gap.

Earth continuity and insulation faults from installation workmanship

A meaningful share of faults caught during commissioning trace back to installation workmanship rather than the charger hardware itself: a poorly torqued earth terminal, cable insulation nicked during pulling or termination, or a protective conductor resistance exceeding the maximum allowed by SS 638 (0.5 Ω for Mode 3 installations, measured between the charger's protective earth terminal and the distribution board's main earthing terminal). These faults are exactly what earth continuity and insulation resistance testing, whether via a connected multifunction tester on an FEV350 job or the dedicated DC-side tests on an FEV500, are designed to catch before the charger is energised for use.

DC fast charger communication failures

DC fast (CCS2) chargers introduce an entirely separate fault category that has no AC equivalent: failures in the digital communication handshake. A charger can pass every electrical safety test and still fail to reliably pair with certain vehicle models over SLAC, or fail partway through the ISO 15118 or DIN SPEC 70121 negotiation, which in the field shows up as a charger that "works with some cars but not others," a frustrating and hard-to-diagnose symptom without the right tool. The Fluke FEV500's ability to complete the full digital protocol exchange, and to simulate error and fault conditions deliberately, is what lets a technician isolate whether a reported fault sits in the charger's communication stack, its power electronics, or elsewhere, rather than guessing based on which specific vehicles have reported problems.

Connector and cable wear faults that develop after commissioning

Not every fault is present at first installation; a meaningful share develops over months of use and shows up only during periodic re-testing rather than initial commissioning. Charging connector pins wear with repeated insertion cycles, and a worn or slightly bent pin can introduce intermittent contact resistance that a technician cannot detect by visual inspection alone but that a proximity pilot or control pilot signal test will flag as marginal or unstable. Cable insulation, particularly on connectors handling frequent outdoor exposure to Singapore's heat, humidity, and UV, can degrade gradually, and a charger that passed its insulation resistance test comfortably at commissioning can drift toward the acceptance threshold over a year or two of service. This is the practical argument for periodic re-testing on a defined interval, not just a one-time commissioning check, since several of the fault categories in this guide are as likely to develop after a charger has been in reliable service for a period as they are to be present on day one.

Distinguishing installation faults from design or component faults

When a fault is found, the practical next question is whether it originates in the installation itself or in the charger's own hardware or firmware, since the fix and the responsible party differ significantly between the two. Faults that are almost always installation-related include earth continuity failures, insulation faults from cable damage during pulling or termination, incorrect proximity pilot cable coding for the specific cable actually fitted, and an RCD or RDC-DD module of the wrong type specified or wired incorrectly. Faults more likely to trace back to the charger unit itself include a control pilot circuit generating an incorrect duty cycle consistently across multiple installations of the same charger model, or a DC fast charger's communication stack failing the same protocol negotiation step across different sites. A useful diagnostic habit: when a fault appears identically across multiple installations of the same charger model from the same manufacturer, suspect the unit or its firmware; when a fault appears in only one installation among several otherwise-identical units, suspect the site-specific installation work.

Faults specific to multi-charger sites with dynamic load management

Sites with several chargers sharing a limited electrical supply, common in Singapore carparks and commercial developments, often deploy dynamic load management (DLM) systems that redistribute available current across active charging sessions. This introduces a fault category with no single-charger equivalent: a DLM system that fails to correctly reduce a charger's available current when other chargers on the same circuit become active, which either trips an upstream protective device under combined peak load or, less obviously, delivers current to one charger that exceeds what the shared supply was actually designed to carry once other sessions start. Verifying DLM behaviour requires testing multiple chargers under simultaneous load, confirming the current allocation logic actually responds as configured rather than simply confirming each charger passes its individual commissioning test in isolation. This is a common gap in commissioning practice: individual chargers on a DLM-managed site can each pass their own standalone test sequence while the shared system as a whole has never actually been verified under realistic combined load.

Environmental ingress and pest-related faults in Singapore's climate

Beyond the electrical and protocol fault categories covered above, Singapore's outdoor and semi-exposed EV charger installations face a category of faults driven directly by the local environment that is less common in temperate-climate installations. Moisture ingress through cable gland seals that were not correctly torqued or sized during installation is a recurring finding, made worse by Singapore's combination of heavy rainfall and high ambient humidity that keeps ingress points wet for extended periods rather than drying quickly between rain events. Less commonly discussed but genuinely observed in the field: insect and small pest ingress into charger enclosures through inadequately sealed cable entries or ventilation openings, which can cause insulation damage or short circuits inside the enclosure over time, an issue effectively unique to tropical climates and rarely anticipated in electrical designs originating from temperate markets. Both failure modes are why enclosure IP rating and, just as importantly, correct installation of every cable gland and enclosure seal to that rating's actual specification, not just fitting an IP-rated enclosure and assuming the rating is automatically preserved, deserves explicit verification during commissioning rather than being assumed from the equipment's datasheet alone.

Grounding system mismatch: a design-stage fault that surfaces at testing

Singapore's electrical installations predominantly use a TN-S or TN-C-S earthing arrangement, but EV charger equipment, particularly imported units originally designed for markets using different earthing conventions (TT or IT systems common in parts of Europe and elsewhere), occasionally arrives with default protective device configurations or internal earthing assumptions that do not correctly match a TN-S installation without deliberate configuration during commissioning. This can manifest as an RCD that behaves unexpectedly under a specific fault condition, or an earth fault loop impedance reading that looks anomalous relative to what the installation's actual earthing arrangement should produce, not because the installation is wrong but because the charger's internal protective logic was configured for an assumption that does not match the actual system it has been installed into. Confirming a charger's earthing system compatibility and any required configuration setting against Singapore's actual TN-S environment, rather than assuming default factory configuration is automatically correct, is a design-stage check that, when missed, surfaces later as a confusing and hard-to-diagnose test result during commissioning.

Distinguishing a charger-side fault from a vehicle-side quirk

When a charger reports an intermittent fault only with certain vehicles, or a driver reports an inconsistent charging experience, the diagnostic challenge is separating a genuine charger-side fault from a vehicle-specific implementation quirk that the charger is correctly, if inconveniently, responding to. The practical diagnostic approach is running the full instrumented test sequence (control pilot waveform analysis for AC, or the full SLAC/ISO 15118 protocol exchange for DC) independent of any specific vehicle, since a charger that passes cleanly against the IEC 61851-1 or ISO 15118 standard tolerances, tested with an analyzer rather than a real vehicle, has demonstrated standards compliance regardless of how any individual vehicle subsequently behaves. Where the charger passes this standards-based test but a specific vehicle model still reports a problem, the fault more likely traces to that vehicle's own onboard charging controller implementation, worth documenting as a known vehicle-specific compatibility note rather than continuing to treat it as an unresolved charger fault. This distinction matters practically because it determines whether further troubleshooting effort should go into the charger installation (if it fails the standards-based test) or into liaising with the vehicle manufacturer or simply documenting a known compatibility limitation (if the charger genuinely passes standards-compliant instrumented testing).

Why documentation and re-test after a fix matters

When a fault is identified and corrected, whether a rewired earth connection, a replaced RCD module, or a firmware update addressing a control pilot issue, the fix itself should be followed by a full re-test of the affected function, not just a visual confirmation the physical work was done. A rewired earth terminal that looks correctly connected can still carry a resistance above the SS 638 threshold if a strand of the conductor was damaged during the rework; a firmware update addressing one control pilot issue occasionally introduces a different regression that only shows up under the same instrumented waveform test that caught the original fault. Recording both the original fault finding and the post-fix re-test result in the charger's commissioning file gives the facility a genuine audit trail, one that matters considerably if the same or a related fault recurs later and a facilities team needs to establish whether it is a new issue or a repeat of something previously addressed.

Building a fault pattern library across a growing charger fleet

For a testing contractor or charge point operator servicing many sites over time, deliberately tracking which fault categories recur, by charger manufacturer and model, by installer, and by site type, turns individual fault findings into genuinely useful predictive information rather than isolated incidents each addressed in isolation. A specific charger model showing a control pilot duty cycle fault across several unrelated installations points toward a firmware or hardware issue worth raising directly with the manufacturer rather than continuing to treat each occurrence as a fresh, unrelated installation problem. An installer whose sites disproportionately show earth continuity or insulation faults relative to other installers working with the same equipment points toward a workmanship pattern worth addressing through training or closer quality oversight on that installer's future work, rather than assuming each finding is an independent, unrelated event. Building this kind of simple pattern tracking, even as a basic spreadsheet cross-referencing fault type against charger model and installer, is a low-effort practice that meaningfully improves a testing organisation's ability to catch systemic issues early, well before they accumulate into a larger, more expensive problem across an entire fleet.

The instrument used to find the fault matters as much as the fault itself

A finding is only as credible as the instrument that produced it, a point easy to overlook when the focus is naturally on the fault rather than the tool that caught it. A control pilot duty cycle deviation reported by an uncalibrated or poorly maintained analyzer is itself an unverified claim, and a facilities team disputing a reported fault is entitled to ask whether the testing instrument's own calibration was current at the time. This is precisely why our companion guide on EV charging test equipment calibration treats the analyzer's own accreditation as inseparable from the credibility of every fault finding it produces; a fault-finding process built on an uncalibrated instrument is not meaningfully more trustworthy than skipping instrumented testing altogether; it simply looks more rigorous on the surface while carrying the same underlying uncertainty.