Why does my DC fast charger show error code 102 and refuse to start a charging session?
Error code 102 on a DC fast charger typically means a communication fault between the charger and the vehicle or a ground‑monitor…
See the fixFix Library
Practical, step-by-step fixes for ev fleet & charging infrastructure problems — 78 published so far.
Error code 102 on a DC fast charger typically means a communication fault between the charger and the vehicle or a ground‑monitor…
See the fixError code 104 on a DC fast charger typically means a communication failure between the charger and the vehicle's battery management system,…
See the fixYour DC fast charger likely stops at 80% because the vehicle's battery management system limits charge rate to protect battery health, and…
See the fixYour DC fast charger throttles speed because the battery management system limits charge rate as the battery warms up or reaches higher…
See the fixYour fleet EV charger trips the breaker because the circuit is overloaded, the breaker is worn out, or there's a ground fault…
See the fixYour fleet EV charging station trips the breaker because the circuit is overloaded, the breaker is worn out, or there's a ground…
See the fixA 'communication error' on a DC fast charger usually means the charger can't handshake with the vehicle or the network backend —…
See the fixYour DC fast charger trips the 480V breaker during peak hours because the combined load of multiple chargers plus site demand exceeds…
See the fixYour DC fast charger throttles because its liquid-cooled cables or power modules overheat, triggering thermal protection that reduces output to protect hardware.…
See the fixYour Level 2 charger is likely tripping the breaker because it's drawing more current than the circuit is rated for, or the…
See the fixYour Level 2 charger trips the breaker most often because the circuit is overloaded, the breaker is undersized, or there's a ground…
See the fixYour charger is likely throttling output due to high cabinet temperature, a utility demand response signal, or a firmware limit set below…
See the fix