Charger faults rarely announce themselves on handover day. A latent defect in a lug torque, a gland seal or a protection setting sits quietly through a five-minute plug-in demo, then surfaces weeks later under full load, in rain, or when the network link drops mid-session. That is why a proper commissioning run tests the unit under load and under deliberate fault, and records the readings before anyone signs.
Key takeaways
Commissioning is three separate jobs wearing one name. Split them, give each one its own pass criteria and its own signature, and the gaps close on their own.
Feed sizing, earthing and bonding, protection device selection and discrimination, cable routing and mechanical protection. The electrical contractor owns this layer, and it is the only layer that can seriously injure someone if it is wrong.
Isolation, pre-charge and contactor behaviour, output voltage and current accuracy, thermal behaviour at rated load, and the protective functions the unit shipped with. This belongs to the charger supplier, and on many sites it is never tested beyond whatever the display happens to show.
Connectivity, heartbeat stability, transaction handling, authorization, metering and firmware configuration. The network operator or CPO integration team owns it, which in practice often means nobody on site does.
The faults that survive a plug-in demo are specific:
Write the pass criteria and the record sheet before the units arrive. On handover day the pressure runs one way: accept whatever the screen shows so the site can open. A pre-agreed sheet with numbers on it is the only thing that survives that pressure.
Then sequence the work: dead checks with the supply isolated, energize without load, load test to thermal steady state, network and metering acceptance, and finally fault rehearsal. Jumping to a load test with an unproven earth is how commissioning injuries happen.
These checks cost an hour and prevent the expensive category of fault, the kind that hides until the site is busy. All of them happen with the supply isolated.

A socket tester tells you there is a live, a neutral and an earth. It does not tell you the earth will carry fault current, and it does not tell you the feed is sound before you bolt electronics onto it. Those are two separate measurements, and both need a number written down.
Measure earth loop impedance with a proper instrument, or run a protective earth continuity test from the charger frame to the earth bar and from the earth bar to the installation earth. Record the reading. One measurement on a dry day is a data point, not a certificate: it confirms the path existed at that moment, at that soil moisture and that temperature.
Test the feed before the charger is connected, at the correct test voltage, with surge protective devices and the unit itself isolated. Testing with the electronics attached can damage arresters and input stages, and a wounded input stage frequently survives right up to the first full-load run, which is exactly when nobody is still thinking about commissioning.
Match the device to what the unit actually requires. A Type A device will not detect a smooth DC residual current, which is why some chargers call for a Type B device or an integrated DC detection function. Confirm which one this site has before you energize it, not after a trip.
Then confirm the charger’s own protective functions are enabled rather than bypassed. If you find insulation monitoring disabled, stop and write down what you found: which function was off, the setting as found against the factory default, who is responsible for it, and what has to be verified at this site before it is switched back on. An undocumented disabled function will be discovered by somebody else, months later, with no paper trail pointing back to the day it was turned off.
Treat the requirement for a properly grounded socket as the floor rather than the target. evaisun’s guide requires connection to a properly grounded electrical socket, and a commercial installation with a separately derived earth needs that continuity proven end to end, not inferred from a green lamp.
When a charger misbehaves in month eight, the argument is always the same: the site says the unit, the supplier says the supply. A baseline captured on handover day ends that argument before it starts, because both parties signed the same numbers.
Keep the instrument model and serial number on the sheet. If a dispute ever reaches a third party, the credibility of the measurement rests on the instrument as much as the reading.
A vehicle’s battery management system decides how much current it will accept. A car that takes a fraction of the cabinet’s rating proves nothing about whether the cabinet holds its own rating. A plug-in test is a compatibility check, and calling it a capacity test is how underperforming sites get signed off.
Take a depot that commissions in April and runs its first hot week in July. A unit that reached full rating on a mild afternoon has been tested, but not tested at the ambient it will actually see, and the test sheet should say which ambient was used so nobody has to guess later.

The output side is where a charger can hurt somebody who is simply trying to plug in a car. Every check below answers one question: does the unit ever present voltage where it should not, and does it ever let a connector go under load?
Verify the function is active and that it actually reports a fault. Introduce a known fault following the manufacturer’s procedure, confirm the response, then clear it and confirm the unit returns to service. Skip the injection and you finish the day with no evidence the function responds to anything at all.
A unit should detect a stuck output contactor and refuse to close, rather than closing onto a live DC bus. Confirm the detection works rather than assuming the logic exists.
With no session active, measure the connector pins and confirm the output is de-energized. A display reading stopped is not the same as a dead bus. Then exercise the connector lock actuator and the interlock that blocks unplugging under load: a lock that fails to engage is an arcing risk and a warranty claim waiting for a customer to yank the handle.
Where connector temperature sensing is fitted, confirm the sensor reads ambient before the first session. A dead sensor reports a cool connector, which disables the derating meant to protect it. On AC units, verify control pilot and proximity pilot behaviour with the vehicles actually expected on site, including the case of a cable connected but not latched.
A charger that charges is not yet a managed asset. These tests decide whether the operator can bill, control and diagnose the site without sending someone to stand in front of it.

Every scenario below will happen in service. The only decision is whether it happens first with a witness and a record sheet, or first with a customer and a support ticket.
| Scenario | What must happen | What to record |
|---|---|---|
| Mains loss and restore | Output de-energized, orderly shutdown, defined restart behaviour | Pin voltage, restart time, event in the platform log |
| Emergency stop pressed and reset | Contactors open, no restart until reset, clear local indication | Pin voltage after trip, reset procedure, who performed it |
| Residual current trip | Output isolated, fault latched and announced | Device type, trip indicator, recovery steps |
| Network loss mid-session | Session continues per local policy, transaction stored for later upload | Session state, reconciliation after reconnect |
| Enclosure opened while energized | Interlock or tamper detection responds as designed | Local alarm, platform notification, output state |
| Connector lock failure | No session start, or orderly stop, never a live release | Pin voltage, lock feedback, error code |
| Over-temperature | Derate first, then stop, with the reason logged | Derate threshold, ambient at test, recovery behaviour |
Then confirm auto-restart behaviour matches site policy: an unattended depot usually wants automatic recovery from a mains dip, while a public site may want a manual reset with an error code so a genuine fault is not silently cleared. For each scenario, start a stopwatch at the moment of the trip and log two things: how long the unit took to come back, and the path it took back, whether it restarted on its own, waited for a reset, or returned in a restricted state. A unit that needs a technician to clear a short interruption costs the operator a morning of charging.
Record who witnessed each rehearsal and when. Before the witness sheet is signed, walk the table row by row and check that a reading, a name and a time sit against every scenario.

Handover is an evidence handover. If time runs short on the day, spend what is left on five checks: protective earth continuity, a full-load thermal image of the terminals, insulation monitoring proven with a simulated fault, meter readings against a reference, and one complete fault rehearsal. Those five catch the faults that cost the most to find later.
If you are planning a rollout and want the installation, protection and test documentation that goes with the hardware, talk to evaisun’s team before the first unit ships rather than after the first fault.
The test sequence sets the duration, not the paperwork. Holding a load test to thermal steady state is usually the longest single step, because the cabinet has to soak before its real behaviour shows up. A site that finishes suspiciously fast has often skipped that hold. Budget the day around the load test and the fault rehearsals, not around the visual inspection.
Only as a compatibility check, not a capacity test. Without a load bank you can still verify earthing, insulation monitoring, connector safety, network behaviour and metering against a reference, but you cannot prove rated output or thermal performance. If no load bank is available on handover day, book one before the first month of operation ends.
No. A factory report proves the unit met its specification on the day it was tested, on the manufacturer’s supply, with the manufacturer’s instruments. It says nothing about the earth at this site, the torque applied during this installation, or the network this unit must talk to. Use it as the reference value your site readings are compared against.
US
English中国大陆
简体中文German
Deutsch
Russian
Русский
French
FrançaisSpanish
español
Portuguese
PortuguêsJapanese
日本語
Italian
Italia
Korean
한국인Subscribe the newsletter to get updated to news and promotions