An EV charging site actually needs two maintenance calendars running in parallel, not one. The charger itself needs periodic electrical re-verification and physical inspection, at a frequency driven by how hard it's actually used and how exposed it is to the elements, not a single generic date on a calendar. The test instrument used to verify it, an FEV300, FEV350 or FEV500, needs its own maintenance regime entirely: calibration currency, battery health, connector wear from constant mating cycles, and firmware currency, none of which the charger's own maintenance schedule touches at all.
Why the test instrument itself needs a tighter regime than typical electrical test gear
Test equipment used for EV charging inspection lives a harder life than most instruments in a technician's kit. Constant connector mating: every test cycle involves physically mating and unmating a Type 1, Type 2 or CCS2 connector, sometimes dozens of times in a single site visit, genuine mechanical wear on the instrument's own connector, not just the charger's. Field battery operation: the Fluke FEV500 runs on a removable lithium-ion battery pack (10.8 V, 6.8 Ah), rated for up to 10 hours of runtime and around 3 hours to recharge via a 65 W USB-C PD supply, and like any lithium-ion pack, capacity and reliable runtime degrade with charge cycles and age, mattering directly for a technician relying on it to complete a full day of site testing. Outdoor and semi-exposed working conditions: much of this testing happens at outdoor or semi-exposed car park charging points in Singapore's heat and humidity, and while the FEV500 carries an IP54 rating with its lid closed, that is not a substitute for keeping the unit, particularly its USB-C port cover and connector interfaces, clean and dry between uses. Firmware currency affects protocol compatibility: CCS2 digital communication testing (SLAC, ISO 15118, DIN SPEC 70121) is a live, evolving protocol space as station manufacturers update their own firmware, so keeping the FEV500's firmware current can directly affect whether it correctly negotiates with newer station firmware during testing.
Test instrument maintenance, by frequency
| Frequency | Task | Why |
|---|---|---|
| Every use, before testing | Zero the test leads (FEV500 continuity measurement) via SENSE ZERO ADJ | Test lead resistance, even a fraction of an ohm, can distort a low-resistance RLO reading |
| Every use, before testing | Visual check of connector, PE Pre-Test sensor and cable for damage or wear | A damaged or contaminated test connector can produce a false result |
| Every use | Confirm battery charge level suits the planned site scope | Running out mid-sequence forces an incomplete visit and a repeat trip |
| Weekly to monthly | Check firmware version against Fluke's downloads page | Keeps protocol testing (SLAC, ISO 15118, DIN SPEC 70121) aligned with current station firmware |
| Ongoing | Keep the USB-C port cover, connector housings and vents clean and dry | IP54 protects against a defined ingress level with the lid closed; it doesn't replace physical upkeep |
| Per your quality programme, typically annually | SAC-SINGLAS accredited calibration with a traceable certificate | An expired certificate invalidates the defensibility of every result in an audit |
| As battery performance visibly degrades | Replace the removable battery pack per manufacturer guidance | Runtime shortfall found mid-visit is a scheduling problem, not just a battery one |
| End of instrument life | Delete personal/project data and remove batteries for separate disposal | Protects client data and follows correct battery disposal practice |
Why charger-side maintenance can't run on a single calendar date either
The same logic that argues against a one-size-fits-all instrument schedule applies even more strongly to the charging stations themselves, because two chargers of the identical model can experience wildly different real-world duty cycles. Consider two Type 2 AC chargers, electrically identical at commissioning: one in a public shopping centre car park seeing fifteen to twenty sessions a day from a rotating cast of vehicles, and one in a private condominium reserved bay seeing one or two sessions a day from the same resident's vehicle. The public unit accumulates connector mating cycles, thermal cycling and user-handling exposure far faster than the private one, despite identical installation dates and specification. This is the practical argument for a risk-based re-test interval driven by actual usage intensity and environmental exposure rather than a single fixed calendar date, set in consultation with the charger manufacturer's own operation and maintenance guidance and your facility's quality programme.
What Charger-Side Preventive Maintenance Should Actually Cover
Connector and cable physical inspection: checking for bent pins, worn locking mechanisms and cable jacket damage (see our guide to connector types and common faults), ideally on a cadence reflecting actual mating-cycle frequency. Periodic electrical re-verification: earth fault loop impedance, insulation resistance, and RCD/RDC-DD or IMD trip performance, at intervals reflecting the degradation risks discussed in our guides to loop impedance testing and insulation resistance testing, both flagging outdoor exposure and sustained current draw as accelerants a one-off commissioning test won't catch later. Thermal and cooling checks on DC fast chargers: DC power conversion generates real heat the station's cooling system must manage continuously, so fans, vents and thermal cutoffs are a legitimate maintenance item. Firmware currency on the charger itself: distinct from the test instrument's firmware, this matters under Singapore's SS 722 Part 3 DC charging requirements, which call for stricter temperature control and cable insulation integrity checks than TR25. Emergency isolation switch verification: confirming the SCDF Fire Code-mandated switch within 15 metres remains accessible, correctly labelled and functional, a fire-safety item separate from the electrical test programme above.
A Simple Maintenance Log Worth Actually Keeping
Most gaps in an EV charging maintenance programme don't come from anyone deciding to skip a task, they come from nobody consistently recording that it happened, so a battery replaced eighteen months ago looks indistinguishable from one untouched since commissioning. A workable log captures, for each instrument, serial number, current firmware version and date last checked, calibration certificate number and expiry date, an estimate of battery cycle count or age, and the date of the last connector/cable inspection; for each charging station, the date and result of the last full electrical re-test, the last physical inspection, the station's firmware version, and confirmation the emergency isolation switch was found functional. Neither log needs to be elaborate, but it needs an owner actually accountable for keeping it current.
Consider a technician arriving at a multi-bay site for a scheduled re-test, only to find the FEV500's battery, last swapped an unknown time ago, delivers barely three hours of runtime instead of the roughly ten a healthy pack should provide. Without a log showing when the pack was last replaced, there's no way to tell whether this is normal degradation or a pack already marginal at the last visit, and the consequence is concrete: a one-afternoon site visit now needs a second trip. The failure mode we see most often isn't a missed test, it's conflating the two programmes into one undocumented routine where neither the charger's nor the instrument's maintenance is clearly owned. A simple, separate log for each, with results captured through TruTest's reporting workflow (see our TruTest software workflow guide) rather than loose paper notes, is what actually survives an audit or insurance claim review years later.