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 of the instruments in a technician's kit, for reasons specific to what it's actually doing:
- 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 across multiple bays. That is 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. Like any lithium-ion pack, capacity and reliable runtime degrade with charge cycles and age, which matters directly for a technician relying on it to complete a full day of site testing without running out mid-sequence.
- 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. The FEV500 carries an IP54 rating with its lid closed, which is a real, useful protection level, but it is not a substitute for keeping the unit, and particularly its USB-C port cover and connector interfaces, genuinely clean and dry between uses.
- Firmware currency affects protocol compatibility. Because CCS2 digital communication testing (SLAC, ISO 15118, DIN SPEC 70121) is a live, evolving protocol space as charging station manufacturers update their own firmware, keeping the FEV500's own firmware current is not a cosmetic housekeeping task, it can directly affect whether the instrument 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) using the SENSE ZERO ADJ socket, per the instrument's documented zeroing procedure | Test lead resistance, even a fraction of an ohm, is enough to distort a low-resistance RLO continuity reading if not compensated for at the start of each test cycle |
| Every use, before testing | Visual check of the connector, PE Pre-Test sensor, and cable for damage, contamination or wear | A damaged or contaminated test connector can produce a false result before the charging station is even the variable being measured |
| Every use | Confirm battery charge level is sufficient for the planned site scope (FEV500) | Running out of charge mid-sequence on a multi-bay site forces an incomplete visit and a repeat trip |
| Weekly to monthly, depending on use intensity | Check firmware version against the latest available on Fluke's software downloads page | Keeps digital protocol testing (SLAC, ISO 15118, DIN SPEC 70121) aligned with current station firmware behaviour in the field |
| Ongoing | Keep the USB-C port cover, connector housings and vents genuinely clean and dry, particularly after outdoor use | The IP54 rating protects against a defined level of dust and water ingress with the lid closed; it does not eliminate the value of basic physical upkeep |
| Per your quality programme, typically annually | SAC-SINGLAS accredited calibration with a traceable certificate | An expired or non-traceable calibration certificate invalidates the defensibility of every test result the instrument has produced since, in an audit context |
| As battery performance visibly degrades | Replace the removable battery pack per the manufacturer's guidance for the specific pack | Runtime shortfall discovered mid-site-visit is a productivity and scheduling problem, not just a battery problem |
| End of instrument life | Delete personal/project data from the instrument and remove batteries for separate disposal before decommissioning, per the manufacturer's documented disposal guidance | Protects client project data and follows correct battery disposal practice rather than treating the unit as generic e-waste |
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 installed in a public shopping centre car park seeing fifteen to twenty charging sessions a day from a rotating cast of vehicles and connectors, and one installed 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 from sustained charging sessions, and exposure to a much wider range of user handling far faster than the private one, even though both were installed on the same day to the same 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 applied uniformly across a portfolio of charging points. A high-traffic public DC fast charger, exposed to weather and heavy daily connector cycling, reasonably warrants more frequent periodic electrical verification (loop impedance, insulation resistance, RCD/IMD function) than a low-traffic private AC point in a sheltered car park. Set your specific interval in consultation with the charger manufacturer's own operation and maintenance guidance and your facility's quality programme, rather than relying on a generic industry rule of thumb; what matters is that the interval is actually driven by that station's real usage and exposure profile, not an arbitrary date copied from an unrelated asset class.
What charger-side preventive maintenance should actually cover
- Connector and cable physical inspection: checking for the bent pins, worn locking mechanisms and cable jacket damage described in our guide to connector types and common faults, ideally on a cadence that reflects actual mating-cycle frequency rather than a fixed calendar.
- Periodic electrical re-verification: earth fault loop impedance, insulation resistance, and RCD/RDC-DD (or IMD, for DC stations) trip performance, re-checked at intervals reflecting the degradation risks discussed in our guides to loop impedance testing at EV charging points and insulation resistance testing for EV charging circuits, both of which flag outdoor exposure and sustained current draw as accelerants of gradual electrical degradation that a one-off commissioning test won't catch later.
- Thermal and cooling system checks on DC fast chargers: DC power conversion generates real heat that the station's own cooling system needs to manage continuously; a station's fans, vents and thermal cutoffs are a legitimate preventive maintenance item, not just an electrical safety one.
- Firmware and software currency on the charger itself: distinct from the test instrument's own firmware, keeping the charging station's own firmware current matters increasingly under Singapore's SS 722 Part 3 DC charging requirements, which call for stricter temperature control and cable insulation integrity checks than the previous TR25 revision, some of which are implemented in charger firmware rather than purely in hardware.
- Emergency isolation switch verification: confirming the SCDF Fire Code-mandated emergency isolation shut-off switch within 15 metres of the charging station remains accessible, correctly labelled, and functional, a fire-safety maintenance item entirely 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, from a distance, indistinguishable from one nobody has touched since commissioning. A workable log doesn't need to be elaborate, but it does need to capture, for each instrument, at minimum: the instrument's serial number, current firmware version and the date it was last checked against Fluke's software downloads page, the calibration certificate number and expiry date, an estimate of battery cycle count or age (particularly for the FEV500's removable pack), and the date and outcome of the last connector/cable physical inspection. For each charging station under your care, the equivalent log tracks: date and result of the last full electrical re-test (loop impedance, insulation resistance, RCD/IMD trip performance), date of the last physical connector and cable inspection, firmware version on the station itself, and confirmation the emergency isolation switch was checked and found accessible and functional. Neither log needs to live anywhere fancier than a shared spreadsheet, but it needs an owner who is actually accountable for keeping it current, not a folder everyone assumes someone else is updating.
A worked scenario: what happens when this slips
Consider a technician arriving at a multi-bay commercial site for a scheduled periodic re-test, only to find the FEV500's battery, last swapped an unknown amount of time ago, delivers barely three hours of runtime instead of the roughly ten hours a healthy pack should provide. Without a maintenance log showing when the pack was last replaced, there's no way to tell whether this is normal end-of-life degradation or a symptom of a pack that was already marginal at the last visit and has simply crossed a threshold since. The practical consequence is concrete: a multi-bay site visit that should have taken one afternoon now needs a second trip, because the instrument ran out of charge partway through, a scheduling and cost problem that traces directly back to a maintenance gap rather than to anything wrong with the charging stations being tested. The fix isn't complicated, log the pack's install date and check runtime against the manufacturer's expected figure at each use, but it only works if it's actually done consistently rather than left to memory.
Keeping the two programmes honestly documented, and honestly separate
The practical failure mode we see most often isn't a missed test, it's conflating the two programmes into one undocumented "someone should probably check on this" routine, where neither the charger nor the test instrument's own maintenance is clearly owned. Keeping a simple, separate log for each, instrument calibration and firmware history on one side, charger electrical re-test and physical inspection history on the other, 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 an insurance claim review months or years later.