When an EV charger stops working, the visible problem rarely tells the whole story. A failed charging session, an error message, lost connectivity or a charger that appears online but will not start charging are symptoms. The underlying cause may be in the charger itself, the electrical supply, communications, configuration, the backend system or the interaction with the vehicle.
Effective diagnostics therefore does not start by replacing a component. It starts by isolating the fault.
Within professional EV charger maintenance, the objective is not simply to bring equipment temporarily back online. It is to determine what caused the problem, what intervention is required and whether the charging point can actually perform its intended function after the intervention.
What Does an EV Charger Fault Actually Mean?
From the driver's perspective, the problem is usually straightforward: the vehicle will not charge.
Technically, however, a complete charging session depends on a wider system.
That system may include the charging equipment, electrical supply infrastructure, protective devices, cable and connector, communications, local software, the backend or CSMS, identification and authorisation mechanisms, and the vehicle itself.
It is therefore useful to distinguish between three things:
Symptom — what the driver or operator observes.
Error or event — information recorded by the charger or another system.
Root cause — the technical issue that produced the observed result.
They are not necessarily the same.
An error code can provide an important diagnostic direction, but it should not automatically be treated as a confirmed root cause.
One Failed Charging Session Does Not Automatically Mean the Charger Is Faulty
If one vehicle fails to start a charging session, that alone does not prove that the charger has failed.
The problem could be associated with vehicle-to-charger communication, user identification, the backend service, the cable or connector, local configuration, an electrical supply issue or a specific combination of vehicle and charging equipment.
Good troubleshooting therefore looks for context and repeatability.
Does the same vehicle charge at another charging point? Can other vehicles use the affected charger? Is the problem limited to one connector or does it affect the whole charger? Did it begin after a configuration or software change? Are there corresponding events in the backend?
Each answer helps narrow the area in which the fault should be investigated.
Diagnostics Starts with Data
A significant amount of context can often be collected before an engineer visits the site.
Depending on the charging equipment and management system, this may include current and historical status information, timestamps, error codes, system events, transaction history, communication status, diagnostic logs and information about recent configuration or software changes.
This information can answer important questions.
When did the fault first occur? Is it intermittent or repeatable? Does it affect every connector? Did the charger lose communications? Was there a sequence of events immediately before the failure? Was anything changed before the issue appeared?
Remote diagnostics does not replace an on-site technical inspection. It can make that inspection more focused by providing better information before the engineer arrives.
What Can Be Diagnosed Remotely?
With connected EV charging infrastructure, part of the diagnostic process can take place without a physical site visit.
Depending on the charging equipment, backend platform, protocol version and specific implementation, operators may have access to charger statuses, error conditions, operational events, diagnostic logs and certain configuration parameters.
OCPP is one of the protocols used for communication between charging stations and central management systems. Different OCPP versions provide different monitoring, diagnostic and management capabilities, while the functions actually available also depend on the specific implementation.
Remote investigation may, for example, establish that a charger has lost its connection to the central system, that a particular connector has entered an error state or that a fault appeared immediately after a particular system event.
There is, however, an important limitation:
“Online” does not necessarily mean “operational.”
A communication connection demonstrates that certain parts of the system can exchange information. It does not by itself prove that the charging point can successfully authorise a user, communicate with a vehicle and deliver power.
When Remote Diagnostics Is Not Enough
Some faults cannot be reliably isolated from backend data alone.
Physical damage to cables or connectors, electrical faults, connection issues, power components, protective devices, cooling systems in applicable DC equipment and other hardware failures may require an on-site technical inspection.
The same applies when remote information identifies a general symptom but does not provide enough evidence to determine the underlying cause with sufficient confidence.
In these situations, remote diagnostics should prepare the site visit rather than replace it.
How On-Site Fault Diagnostics Works
There is no universal diagnostic procedure that applies identically to every EV charger.
The required checks depend on the manufacturer, model, equipment architecture, whether the system is AC or DC, the reported fault and the applicable service documentation.
The underlying process, however, is consistent.
The equipment must first be placed in an appropriate condition for safe technical work. The visible condition and known symptoms can then be examined alongside the available diagnostic information and the relevant subsystems. Where necessary and permitted, appropriate electrical and functional checks are performed.
The objective is to progressively narrow the fault domain until a specific cause, or a sufficiently clear corrective action, can be established.
Service procedures and qualification requirements can be manufacturer- and equipment-specific. Technical intervention should therefore follow the applicable documentation and requirements rather than a universal checklist applied mechanically to every charger.
Where Is the Fault Usually Investigated?
It is useful to troubleshoot EV charging systems by subsystem rather than treating every incident as the same generic “charger failure.”
Electrical Supply and Infrastructure
The fault may exist outside the charger itself — for example in the electrical supply, protection or another part of the upstream infrastructure.
This is one reason why the charger and the electrical system behind it should not be treated as completely separate systems.
Cables and Connectors
Mechanical wear, contamination, damage or issues with contact elements can affect normal charging operation.
The correct inspection and permissible repair depend on the design and requirements of the specific equipment.
Communications
Loss or instability of connectivity can affect remote management, authorisation, reporting or the visibility of the charging point in the backend system.
A communication fault and a charging fault, however, are not necessarily the same thing.
Backend and Authorisation
In some cases the charging equipment may technically be capable of delivering power, while a session fails because of identification, the authorisation workflow or another dependency on the central system.
Configuration, Software and Firmware
Incorrect configuration, incompatible settings or an issue following a change can produce behaviour that resembles a hardware fault.
Software interventions also need to be controlled.
“A firmware update is available” does not automatically mean “install it now.”
A change should have a technical reason and follow an appropriate procedure for the equipment involved.
Power Electronics and Cooling
DC charging systems may involve faults associated with power modules, thermal management or cooling components where these form part of the specific architecture.
Remote symptoms often need to be correlated with physical inspection and manufacturer-specific diagnostics.
Vehicle–Charger Interaction
Not every problem can be reproduced with every vehicle.
Where an issue occurs only with a particular vehicle or under a particular combination of conditions, the diagnostic process needs to account for that dependency as well.
A Restart Is Not a Diagnosis
A remote or local restart is a useful operational tool and can restore service in certain situations.
But there is an important difference between restoring service and identifying the cause.
If restarting the charger restores operation, it demonstrates that service has been restored. It does not prove why the problem occurred.
For an isolated incident, that may be an appropriate operational response. For a recurring issue, however, the history needs to be investigated.
If a charging point regularly needs to be restarted, the restart gradually stops being the solution and becomes part of the symptom.
From Fault Diagnostics to Corrective Maintenance
Once the fault has been isolated, the appropriate corrective action can be determined.
That does not always mean replacing a physical component.
Depending on the root cause, the intervention may involve correcting configuration, restoring communications, a controlled software or firmware intervention, electrical repair, replacement of a cable, connector or another component, or work elsewhere in the system.
Certain equipment and components may also be subject to manufacturer-specific service procedures, restrictions or qualification requirements.
The right question is therefore not simply, “What can we replace?” but “What is the identified cause, and what intervention is appropriate for it?”
Spare Parts Are Part of Recovery Time
Diagnostic time and total service-restoration time are not the same thing.
The root cause may be identified relatively quickly while the repair itself depends on component availability, logistics, site access, required qualifications or manufacturer procedures.
This distinction becomes particularly important for business-critical charging infrastructure.
An effective maintenance operation therefore requires more than the technical ability to diagnose a fault. It also requires an escalation process, spare-parts management, on-site intervention where necessary and follow-through until the charging service has been restored.
When Is an EV Charger Repair Actually Complete?
Replacing a failed component is not the final step.
After the technical intervention, the system should be checked to confirm that it has genuinely returned to normal operation.
Depending on the case, this may include checking equipment status, confirming that the relevant error condition is no longer active, carrying out functional testing and, where appropriate, completing a test charging session.
“The charger is online” and “the charger can successfully charge a vehicle” are two different checks.
Closing the repair should also leave a clear technical record: what the reported problem was, what was found, what intervention was performed and how successful operation was verified.
That information matters not only for the current incident but also for the next one.
Why Fault History Matters
A single failure may appear random. A sequence of similar failures becomes useful technical information.
If the same connector repeatedly enters an error state, communications fail under particular conditions or the same intervention is required at short intervals, the history may reveal a pattern that is not visible when each incident is treated in isolation.
Diagnostic and repair records therefore contribute to preventive maintenance rather than serving merely as an administrative archive.
They allow future maintenance decisions to be informed by the history of the actual equipment.
Diagnostics, Repair and Uptime
The objective of technical maintenance is not to promise that failures will never occur.
It is to operate and support the infrastructure so that problems can be detected, isolated, prioritised and resolved through an organised process.
Operational reliability depends on the whole chain: incident detection, remote diagnostics, deciding whether on-site intervention is required, obtaining parts, carrying out the repair, functional testing and documenting the result.
Diagnostics and repair are therefore part of reliability management, not isolated emergency activities.
Diagnostics as Part of the Charging Infrastructure Lifecycle
When charging infrastructure is managed as a system, preventive and corrective maintenance are not separate worlds.
Remote monitoring can provide early information about an issue. Diagnostics identifies where the cause should be investigated. On-site intervention confirms or supplements the remote evidence. Corrective maintenance restores functionality. The resulting service history feeds back into future maintenance decisions.
This is the lifecycle logic behind Qerra Care — connecting monitoring, diagnostics, technical response and infrastructure history within the agreed scope of service.
For existing charging infrastructure installed by another provider, the ability to take over technical maintenance is determined following a technical assessment of the equipment and system.
The real end of a repair is not when the engineer closes the job. It is when we know what failed, what was done and that the charging function has been restored.
Frequently Asked Questions
Can an EV charger be diagnosed remotely?
Part of the diagnostic process can be performed remotely where the charging equipment and management system provide the necessary statuses, events, logs and other diagnostic information. Actual capabilities depend on the charger, backend platform, protocol version and implementation. Hardware and electrical faults often require on-site inspection.
What does it mean if an EV charger is online but not charging?
Online status generally indicates that a communication path is available to a particular system. It does not prove that the complete charging process is working. The cause may involve the connector, vehicle, authorisation, configuration, electrical system, hardware or another part of the charging environment.
When is an on-site engineer required?
An on-site visit is required when the fault cannot be reliably isolated remotely or when physical, electrical or other technical inspections and repair work are necessary. The exact procedure depends on the equipment and the nature of the fault.
Can restarting an EV charger be considered a repair?
A restart may restore operation for certain operational issues, but it does not by itself demonstrate that the underlying cause has been identified and corrected. Recurring incidents require further investigation.
How long does an EV charger repair take?
There is no universal repair time. It depends on the type of fault, the ability to diagnose it remotely, whether an on-site visit is required, spare-parts availability, site access and the requirements of the specific equipment. Under a contracted maintenance service, response and diagnostic times may be defined through an SLA.
Can an EV charger installed by another company be repaired?
In many cases this may be possible, but it should not be assumed automatically. The equipment model and condition, available documentation, access to the required systems and serviceability of the equipment need to be assessed. At Qerra, taking over existing charging infrastructure for technical maintenance is subject to a technical assessment.
Need technical support for your EV charging infrastructure?
Qerra Care brings together monitoring, diagnostics, technical response and EV charging infrastructure maintenance within the agreed service scope.