Inicio / Configuración técnica / Charging Station Diagnostics & Maintenance / Manufacturer error codes / Schneider Electric error codes
Schneider Electric error codes
Este artículo aún no está disponible en Español. Se muestra la versión en English.
This page covers the Schneider Electric chargers found in the fleets supervised by Chargekeeper: EVlink Pro AC, EVlink Smart Wallbox, SE Charge Pro and EVlink Pro DC. For each manufacturer code it gives the meaning, what you can do and the associated OCPP code. The EVlink DC 24 kW is at the end of the page, under "Other models".
Where to read the code: in Chargekeeper, charging station list, connector details, Information column (or the list of ongoing sessions, Information column). It shows "OCPP code - manufacturer code - information". See Manufacturer error codes.
How Schneider Electric reports errors
Schneider Electric chargers send their code in the manufacturer code field (vendorErrorCode) of the OCPP StatusNotification message. The format depends on the model:
- EVlink Pro AC: a "group.detail" code, for example
10.1or11.0. The station often adds an English label in the information field (for example "Plug Presence (PP) conformity" with10.1). - The value
0.0is not a fault. The EVlink Pro AC sends it permanently when everything is fine: ignore it. - EVlink Smart Wallbox: a plain number, for example
25. It is the number of event "Evt#25" in the Schneider Electric troubleshooting guide. - EVlink Pro DC (EVD… references): a hexadecimal code, for example
0x200202. The station sometimes writes it in lower case (0x10020f). - SE Charge Pro: a hexadecimal code, for example
0x30000D. Schneider Electric does not publish the list of these codes; see the dedicated section.
The OCPP code actually sent may differ from the documented one: in that case the tables show both.
EVlink Pro AC — codes sent to the supervision
Main source: the EVlink Pro AC OCPP connectivity guide (2026). Codes 1.0, 1.2, 2.5, 17.1 and 18.1 only appear in the 2023 troubleshooting guide, which numbered some codes differently; the 2026 OCPP guide no longer lists them. The code is also shown in the eSetup installer app.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
1.0 |
Rated capacity setting out of range: the configuration DIP switch is set wrongly | Check in eSetup that the configuration does not allow derating. Have the installer check the DIP switch against installation guide NNZ1940301. | — |
1.1 |
Firmware older than the version the station expects (downgrade detected) | Check the installed software version and update it. | OtherError |
1.2 |
Software older than expected (downgrade detected) | Check the installed software version and update it. | — |
2.0 |
Main board (station electronics) fault | Export the diagnostic report from eSetup before any intervention. If a cable is plugged, unplug it and restart the station. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
2.1 |
Physical derating setting invalid, or changed during a charge | Have the installer set the DIP switch per installation guide NNZ1940301. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
2.2 |
6 mA DC leakage detection module missing | Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
2.3 |
ISO 15118 communication module missing | Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
2.4 |
Temperature sensor fault (Eichrecht-certified references only) | Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
2.5 |
Temperature sensor fault (Eichrecht references) — numbering of the 2023 troubleshooting guide | Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | — |
3.0 |
Upstream protection tripped (MNx release) or contactor state mismatch | For stations with an MR part number, check the fault type in eSetup. Have a qualified electrician check whether the MNx has tripped and the contactor state. Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | OverCurrentFailure |
4.0 |
Internal fault of the RDC-DD (6 mA DC leakage) measurement board | Unplug the EV. Power-cycle the station. If the code persists, take the station out of service and contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
5.0 |
DC leakage current above 6 mA detected | If it happened during a charge, unplug the EV. Check that the station light returns to green. Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | OtherError |
6.0 |
Supply voltage problem: phase synchronisation, voltage or frequency out of range | With embedded RCD: check in eSetup that the phase connection is set to three-phase. Without embedded RCD: check it is set to single-phase. | InternalError |
6.1 |
Internal metering board reports at least one fault | Switch the station off and on. If the code persists, the station has to be replaced. | InternalError |
7.0 |
Lost Modbus communication with the metering power meter (internal or external) after 3 failed attempts | Check whether the MID meter display shows information. Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError (actually sent: PowerMeterFailure) |
7.1 |
Metering dataset error, e.g. signature verification failed | Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
8.0 |
Bluetooth processor problem: communication lost or update impossible | Check the se.com FAQ for this issue. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | InternalError |
9.0 |
Lost communication with the RFID/NFC badge reader | Restart the station. Present a badge to the reader. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | ReaderFailure |
10.0 |
Control Pilot (CP) communication fault with the vehicle | If an EV simulator is available, test the station with it: if the code disappears, try another cable or vehicle. Otherwise unplug and replug the cable. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | EVCommunicationError |
10.1 |
Plug Presence (PP) resistor value wrong: cable not recognised | If an EV simulator is available, test the station with it: if the code disappears, try another cable or vehicle. Otherwise unplug and replug the cable. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | EVCommunicationError |
10.2 |
Short-circuit on the Control Pilot wire | If an EV simulator is available, test the station with it: if the code disappears, try another cable or vehicle. Otherwise unplug and replug the cable. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | EVCommunicationError |
11.0 |
Cable lock/unlock failure on the socket | If no cable is plugged: restart the station. If a cable is plugged: unplug and replug it, then try another cable. If the code persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | ConnectorLockFailure |
12.0 |
Contactor not in the commanded state (welded closed or stuck open) | Turn the station off and have a qualified technician check that the contactor opens and closes. Contact Schneider Electric field service; the station may need replacement. | InternalError |
13.0 |
Three-phase charging requested while not allowed in simplified Mode 3 | Inform the user the vehicle is not compatible with this charging mode. | OtherError |
14.0 |
Vehicle draws more current than allowed (overcurrent/overload) | Try the station with another vehicle: if the code disappears the first vehicle is the cause. If it persists, contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | OverCurrentFailure |
15.0 |
Vehicle requests ventilation (battery gas risk), which the station does not support | Inform the user the vehicle is not compatible with this station. | OtherError |
16.0 |
Lost communication with the EcoStruxure EV Charging Expert (local load manager) | Check that the EV Charging Expert is powered, and check its dashboard. Check the network between the Charging Expert and the station. | OtherError |
17.0 |
Supervision (OCPP) communication or configuration problem | Check the Ethernet link and ping the station IP. Check the supervision (OCPP) settings and modem settings. Export the diagnostic report from eSetup before any intervention. Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | OtherError (actually sent: InternalError) |
17.1 |
Connection to the CPO backend lost while the station itself is not in error; offline charging still allowed | Check that the modem, router and switch are powered. Check the IT infrastructure. With a wireless modem, check the signal strength. | — |
18.0 |
Dynamic energy management: lost communication with the external TIC (Linky) or Modbus metering device | Check the TIC communication LED; if it is off, have a qualified electrician check the TIC wires to the Linky meter. For a Modbus meter: check the communication parameters, and have a qualified electrician check the wiring. | OtherError |
18.1 |
Dynamic energy management: lost communication with the external Modbus meter (2023 troubleshooting guide numbering) | Check the communication parameters with the meter. Have a qualified electrician check the external wiring. Have the external meter replaced if faulty. | — |
19.0 |
Station temperature outside the allowed range (Eichrecht references only) | Contact Schneider Electric Customer Care with the station serial number and a diagnostic report. | OtherError |
EVlink Smart Wallbox (and EVlink Parking / City) — codes sent to the supervision
The Smart Wallbox sends the event number alone (for example 25). It matches event "Evt#N" of the Schneider Electric troubleshooting guide, shown in brackets. This guide is shared by the EVlink Parking, City and Smart Wallbox: rows marked "Parking / City" do not apply to the Smart Wallbox. Numbers 2, 23, 26 to 28 and 32 are not documented.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
1 (Evt#1) |
RFID reader communication lost (reader disconnected or faulty) | Have the installer check the reader wiring; check its LEDs and the software version in the web server update tab. | ReaderFailure |
3 (Evt#3) |
Cannot reach the master board (internal communication) — Parking/City | Have the installer check the Ethernet link between the two boards and their LEDs; reboot; if it persists, factory reset each side. | OtherError |
4 (Evt#4) |
Socket lock state mismatch (socket/flap lock sensor) | Inspect the socket and shutter, remove foreign bodies, reinsert the plug. | ConnectorLockFailure |
5 (Evt#5) |
Contactor state mismatch | Have a qualified electrician check the contactor and its auxiliary contacts; if it is stuck, the vehicle's on-board charger may be short-circuited. | — |
6 (Evt#6) |
Surge arrester fault — Parking/City | Have a qualified electrician check the cartridges, the shunt (if no arrester) and the connectors. | — |
7 (Evt#7) |
Anti-intrusion: door open or door contact faulty — Parking/City | Do not press the blinking green button (it starts a factory reset); have the installer check the door contact, bracket and cables. | — |
8 (Evt#8) |
Software configuration file missing, damaged or already open | Save the configuration in the commissioning tool before any change; re-import a backup or factory reset and recommission. | — |
9 (Evt#9) |
Wrong value in EEPROM (hardware configuration) | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. | — |
10 (Evt#10) |
Flap not locked: inductive sensor mismatch — Parking/City | Clear the flap area, close it firmly, have the installer check the sensor position. | — |
11 (Evt#11) |
Upstream protection feedback wrong (breaker, MNx, RCD) | Check the protective devices; have a qualified electrician check the OF/MNx wiring and connectors. | — |
12 (Evt#12) |
Lost communication with the iEM3xxx energy meter | Have a qualified electrician check the meter wiring and supply; compare the settings with the commissioning guide. | — |
13 (Evt#13) |
Lost communication with an external (third-party) RFID reader | Check the external reader LEDs and connections; reboot the reader then the station. | — |
14 (Evt#14) |
Plug/unplug process: socket or vehicle not connected within one minute (City: domestic and T2/T3 used on the same side) | Inspect cables and sockets, check that the vehicle locks the cable, reinsert connectors. | OtherError |
15 (Evt#15) |
Single-phase station wired three-phase — Parking/City | On a 7 kW single-phase unit, have a qualified electrician disconnect phases 2 and 3. | — |
16 (Evt#16) |
Lost communication with the cluster manager (PLC) — clustered stations only | Check the Ethernet cable to the PLC and its status LEDs; reset the PLC cabinet and the stations. | — |
17 (Evt#17) |
Control Pilot signal non-conforming with a Mode 3 vehicle | Try another cable, then another vehicle or simulator. | EVCommunicationError |
18 (Evt#18) |
Plug Presence (PP) resistor value wrong | Try another cable, then another vehicle or simulator. | OtherError |
19 (Evt#19) |
Charge stopped because the cable was disconnected on the vehicle side during charge | Stop the charge from the vehicle before unplugging; try another cable or vehicle. | — |
20 (Evt#20) |
Short-circuit on the Control Pilot wire | Try another cable, then another vehicle or simulator. | OtherError |
21 (Evt#21) |
Overcurrent drawn by the vehicle | Try another vehicle. | OverCurrentFailure |
22 (Evt#22) |
Vehicle requests ventilation (old battery tech) while station configured indoor | Vehicle not supported by this installation. | — |
24 (Evt#24) |
No modem communication or RSSI below 10 | Check the modem cable, power and LEDs; reset modem and station; reposition the antenna (RSSI must exceed 10). | — |
25 (Evt#25) |
Energy reserve too low to lock/unlock the socket — Smart Wallbox; clears after a few seconds | Reinsert the plug properly and wait for the reserve to recover. | OtherError |
29 (Evt#29) |
Lost communication with the remote energy manager (Modbus Ethernet) | Check the local supervision and Modbus Ethernet link; reboot the whole system. | — |
30 (Evt#30) |
Supervision (OCPP) communication or rights problem | Export the maintenance report; check modem/antenna (RSSI > 10); check with the backend that the station identity is registered. | — |
31 (Evt#31) |
Lost communication with the NTP time server | Check the NTP settings in the commissioning tool and the network (cable, firewall). | — |
SE Charge Pro — codes seen on our stations, not documented by Schneider Electric
Schneider Electric does not publish an error code list for the SE Charge Pro: its installation and commissioning guides only describe the LEDs (see "LEDs and display").
These codes were received from stations supervised by Chargekeeper but do not appear in the manufacturer's public documentation. The label is the one sent by the station itself.
| Code | Label sent by the station | OCPP code |
|---|---|---|
0x100008 |
"WeakSignal" | WeakSignal |
0x100205 |
"Lock / Unlock cable Failure" | ConnectorLockFailure |
0x300002 |
"Internal Power Meter communication loss" | InternalError |
0x300009 |
"Supervision (OCPP) issue" | OtherError |
0x30000B |
"DEM communication loss : TIC" | OtherError |
0x30000D |
"DEM communication loss : Peak controller" | OtherError |
0x300010 |
"RDC DD (6mA) measurement board error" | InternalError |
EVlink Pro DC — codes sent to the supervision
Source: the EVlink Pro DC OCPP connectivity guide, which gives the OCPP code sent for each code (DTC). On a fault, the station also shows a message on its screen. Schneider Electric gives no per-code action: if a fault persists, contact Schneider Electric Customer Care.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
0x100005 |
Card reader communication failure | — | ReaderFailure |
0x100007 |
Insulation warning | — | OtherError |
0x100009 |
SD card of the terminal abnormal | — | InternalError |
0x10000C |
SECC (charging communication controller) socket connection fault | — | OtherError |
0x10000F |
Environment detection board offline | — | OtherError |
0x100101 |
Terminal (dispenser) over-temperature | — | HighTemperature |
0x100102 |
Cable connector over-temperature | — | InternalError |
0x100202 |
Emergency stop pressed on the terminal | — | InternalError |
0x100205 |
Vehicle connector lock control error | — | ConnectorLockFailure |
0x100206 |
Ground (earth) fault | — | GroundFailure |
0x100207 |
Insulation monitoring board fault | — | InternalError |
0x100208 |
Output relay control fault | — | InternalError |
0x10020A |
Insulation fault | — | OtherError |
0x10020B |
Water level fault in the power cabinet | — | OtherError |
0x10020C |
Terminal door open | — | OtherError |
0x10020D |
Humidity too high | — | OtherError |
0x10020E |
Tilt sensor triggered (cabinet tilted, e.g. vehicle impact): output cut and session stopped, indicator red | — | OtherError |
0x10020F |
Energy meter fault | — | PowerMeterFailure |
0x100210 |
Communication fault with a sub-board | — | InternalError |
0x100211 |
Power loss | — | InternalError (actually sent: OtherError) |
0x100212 |
Communication fault with the power cabinet | — | InternalError |
0x100213 |
Overcurrent | — | OverCurrentFailure |
0x100214 |
Output overvoltage | — | InternalError |
0x100216 |
PLC (powerline vehicle communication) board offline | — | InternalError (actually sent: OtherError) |
0x200001 |
Power module communication fault | — | InternalError |
0x200002 |
Power module fault | — | InternalError (actually sent: OtherError) |
0x200003 |
Power distribution unit (PDU) relay control fault | — | InternalError |
0x200004 |
Power distribution unit (PDU) communication fault | — | InternalError (actually sent: OtherError) |
0x200008 |
Surge protection alarm | — | OtherError |
0x200101 |
Power module over-temperature | — | InternalError |
0x200102 |
Power distribution unit (PDU) over-temperature | — | InternalError |
0x200103 |
Power cabinet fan controller communication alarm | — | InternalError |
0x200104 |
Power cabinet fan failure | — | InternalError |
0x200202 |
Emergency stop pressed on the power cabinet | — | InternalError (actually sent: OtherError) |
0x200203 |
Water level fault in the power cabinet | — | OtherError |
0x200204 |
Power cabinet door open | — | OtherError |
0x200206 |
Input (mains) overvoltage | — | OverVoltage |
0x200207 |
Input relay control fault | — | PowerSwitchFailure |
0x200208 |
Input (mains) undervoltage | — | UnderVoltage |
0x200209 |
Circuit breaker tripped | — | OtherError |
0x20020B |
Tilt sensor alarm (power cabinet) | — | OtherError |
0x20020C |
Fuse blown | — | OtherError |
0xC00000 |
Power control fan fault | — | InternalError |
Other codes seen on our stations, not documented by Schneider Electric
These codes were received from stations supervised by Chargekeeper but do not appear in the manufacturer's public documentation. The label is the one sent by the station itself.
EVlink Pro DC (EVD… references)
Several of these codes arrive at the end of a session with a label describing why it stopped (for example "EV charge complete").
| Code | Label sent by the station | OCPP code |
|---|---|---|
0x100222 |
— | — |
0x10029a |
"Idle DC Output Over-Voltage" | OtherError |
0xa0000a |
"Inuslation fault" | — |
0xa0000b |
"Meter data error" | — |
0xa00014 |
"Precharge over-time" | — |
0xa00101 |
"EV disconnected" | OtherError |
0xa00102 |
"EV communication interrupted" | OtherError |
0xa00103 |
"EV Comm Itr (ParaDisReq not recv from EV)" | — |
0xa00104 |
"EV Comm Itr (CabCheckReq not rev from EV)" | — |
0xa00105 |
"Charge parameters dismatch" | — |
0xa00106 |
"EV charge complete" | OtherError |
0xa00110 |
"EV initial communication not received" | OtherError |
0xa00114 |
"EV actively stops charging(CP C to B)" | OtherError |
0xa00203 |
"Remotely stop" | OtherError |
0xa00207 |
"Output over-voltage fault" | OverVoltage |
0xa00209 |
"Output over-current fault" | — |
0xa0020c |
"Card stop" | OtherError |
0xb00001 |
"EmergencyStop" | OtherError |
0xb00003 |
"Power cabinet door open" | OtherError |
0xb00009 |
"Power policy fault" | OtherError |
0xb0000a |
"Power switch overtime fault" | — |
0xb00200 |
"Power supply module failure" | OtherError |
EVlink Smart Wallbox
| Code | Label sent by the station | OCPP code |
|---|---|---|
force |
— | OtherError, EVCommunicationError |
Model not reported by the station
These codes were received from Schneider Electric stations whose model was not known. They carry the same number as an EVlink Pro AC code (see above).
| Code | Label sent by the station | OCPP code |
|---|
Other models
EVlink DC 24 kW — DC part
Older model, not present in the fleets supervised by Chargekeeper. The source does not say where the code is shown. GB = GB/T, Combo = CCS.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
0x00 |
No error | — | — |
0x01 |
Internal power supervision problem | — | — |
0x02 |
External emergency stop button pressed | — | — |
0x03 |
Emergency stop triggered by internal anomaly detection | — | — |
0x04 |
Abnormal output voltage at charger power-up | — | — |
0x05 |
Output relay failure found during start self-check | — | — |
0x06 |
Inconsistent value in a CAN frame (CHAdeMO) | — | — |
0x07 |
CAN communication with the vehicle stopped | — | — |
0x08 |
Output overcurrent | — | — |
0x09 |
Output voltage above limit | — | — |
0x0A |
Charger overheating | — | — |
0x0B |
Vehicle requests more current than allowed (CHAdeMO) | — | — |
0x0C |
Power supervisor not responding | — | — |
0x0D |
Power supervisor stuck while changing mode | — | — |
0x0E |
Power supervisor in an inconsistent state | — | — |
0x0F |
Abnormal internal voltage at start | — | — |
0x10 |
Connector locking problem | — | — |
0x11 |
Battery characteristics incompatible with the charger (CHAdeMO) | — | — |
0x12 |
Battery inconsistent or not responding (CHAdeMO) | — | — |
0x13 |
Charging stopped on request of an external user (CHAdeMO) | — | — |
0x14 |
Vehicle shift-position fault flag (CHAdeMO CAN) | — | — |
0x15 |
Other vehicle fault flag (CHAdeMO CAN) | — | — |
0x16 |
Battery overvoltage flag (CHAdeMO CAN) | — | — |
0x17 |
Battery undervoltage flag | — | — |
0x18 |
Battery current deviation flag (CHAdeMO CAN) | — | — |
0x19 |
High battery temperature flag (CHAdeMO CAN) | — | — |
0x1A |
Voltage deviation flag (CHAdeMO CAN) | — | — |
0x1B |
Insulation test failed | — | — |
0x1C |
Charger internal problem (CHAdeMO) | — | — |
0x1D |
Voltage limit reached (CHAdeMO) | — | — |
0x1E |
Charge ended by user action | — | — |
0x1F |
Vehicle pilot state inconsistent (Combo) | — | — |
0x20 |
Internal voltage takes more than 2 minutes to fall below minimum after charge (CHAdeMO/GB) | — | — |
0x23 |
Vehicle pilot state inconsistent during charge | — | — |
0x25 |
Vehicle not ready to charge (Combo) | — | — |
0x28 |
No power module active | — | — |
0x29 |
No CAN frame received from the vehicle (CHAdeMO) | — | — |
0x31 |
Battery too hot or too cold to accept charge (Combo) | — | — |
0x32 |
Vehicle not in Park position (Combo) | — | — |
0x33 |
Vehicle reports connector lock fault (not locked or cannot unlock) (Combo) | — | — |
0x34 |
Non-recoverable fault of the vehicle battery system (Combo) | — | — |
0x35 |
Vehicle stopped because the station could not deliver the requested current (Combo) | — | — |
0x36 |
Vehicle stopped: battery voltage outside its normal range (Combo) | — | — |
0x37 |
Vehicle stopped sending data (Combo) | — | — |
0x38 |
Vehicle did not answer session setup (Combo) | — | — |
0x39 |
Vehicle did not reach ready-to-charge state (Combo) | — | — |
0x3A |
Vehicle judged the station incompatible (Combo) | — | — |
0x3B |
Connection with the vehicle lost (Combo) | — | — |
0x3C |
SLAC (PLC association) procedure failed (Combo) | — | — |
0x3D |
Ethernet negotiation failure | — | — |
0x3E |
Ethernet link failure | — | — |
0x3F |
PLC link lost (Combo) | — | — |
0x40 |
CHAdeMO protocol version not supported | — | — |
0x44 |
Vehicle did not follow the communication sequence (Combo) | — | — |
0x45 |
Incorrect data value in a vehicle request (Combo) | — | — |
0x46 |
Keep-alive frame not received (HMI timeout) | — | — |
0x47 |
CHAdeMO charge ended: time limit reached | — | — |
0x48 |
CHAdeMO vehicle dropped the physical charge-enable signal during charge | — | — |
0x49 |
CHAdeMO vehicle cleared the charge-enable flag during charge | — | — |
0x50 |
CCS connector temperature too high | — | — |
0x51 |
CAN frame not received (GB/T) | — | — |
0x52 |
CCS1 connector button pressed during charge, or proximity disconnected | — | — |
0x53 |
Vehicle sent a wrong or unreadable parameter (Combo) | — | — |
0x54 |
Vehicle sent a badly formatted V2G frame (Combo) | — | — |
0x55 |
Connector temperature sensor not connected | — | — |
0x56 |
Voltage difference across the output relay too high (Combo) | — | — |
0x57 |
PLC chipset malfunction (Combo) | — | — |
0x60 |
Depends on standard: dual junction relay error (Combo/CHAdeMO) or informative charge stop by the vehicle (GB/T) | — | — |
0x61 |
Informative: target state of charge reached (GB/T) | — | — |
0x62 |
Informative: total voltage set-point reached (GB/T) | — | — |
0x63 |
Informative: cell voltage set-point reached (GB/T) | — | — |
0x64 |
Insulation fault detected (GB/T) | — | — |
0x65 |
Output connector overheated (GB/T) | — | — |
0x66 |
Vehicle BMS element or output connector overheated (GB/T) | — | — |
0x67 |
Charger connection fault (GB/T) | — | — |
0x68 |
Battery pack temperature too high (GB/T) | — | — |
0x69 |
Other vehicle faults (GB/T) | — | — |
0x6A |
Current above the requested value (GB/T) | — | — |
0x6B |
Abnormal voltage (GB/T) | — | — |
0x6C |
Vehicle not ready to charge (GB/T) | — | — |
0x70 |
GB/T BHM frame missing or timed out | — | — |
0x71 |
GB/T BRM frame missing or timed out | — | — |
0x72 |
GB/T BCP frame missing or timed out | — | — |
0x73 |
GB/T BRO frame missing or timed out | — | — |
0x74 |
GB/T BCL frame missing or timed out | — | — |
0x75 |
GB/T BCS frame not received | — | — |
0x76 |
GB/T BCS frame timed out | — | — |
0x77 |
Vehicle high-voltage relay fault (GB/T) | — | — |
0x78 |
GB/T communication timeout (BCS) | — | — |
0x79 |
Vehicle reports high-voltage relay fault (GB/T) | — | — |
0x7A |
Single battery cell voltage too high (GB/T) | — | — |
0x7B |
Single battery cell voltage too low (GB/T) | — | — |
0x7C |
Vehicle battery state of charge too high (GB/T) | — | — |
0x7D |
Vehicle battery state of charge too low (GB/T) | — | — |
0x7E |
Battery charging overcurrent (GB/T) | — | — |
0x7F |
Battery over-temperature (GB/T) | — | — |
0x80 |
Unknown failure reported by the power supervisor | — | — |
0x81 |
Emergency stop detected by the power supervisor | — | — |
0x82 |
Communication failure with the power modules | — | — |
0x83 |
Communication failure between CCU and power supervisor | — | — |
0x84 |
No power module available | — | — |
0x85 |
Overvoltage detected by the power supervisor | — | — |
0x86 |
Charger overheating (power supervisor) | — | — |
0x87 |
Data consistency failure | — | — |
0x88 |
Insulation test failed (power supervisor) | — | — |
0x89 |
Output voltage limit reached | — | — |
0x8A |
Short circuit at the output | — | — |
0x8B |
Rectified voltage (Vred) outside min/max limits | — | — |
0x8C |
Insulation controller malfunction | — | — |
0x8D |
Rectified voltage changing too fast | — | — |
0x8E |
Power board not compatible | — | — |
0xA0 |
Error while reprogramming the power supervisor or power modules | — | — |
0xB0 |
Stuck in bootloader: no valid application in flash | — | — |
0xB1 |
Application in flash cannot boot; reprogramming needed | — | — |
0xC0 |
Self-check: control pilot negative voltage generator failed | — | — |
0xC1 |
Self-check: internal pre-charge did not reach target voltage | — | — |
0xC2 |
Self-check: output pre-charge did not reach target voltage | — | — |
0xC3 |
Self-check: output voltage wrong after output relay closed | — | — |
0xC4 |
Self-check: insulation fault during pre-charge or after output connection | — | — |
0xC5 |
Self-check: at least one power module present but not active | — | — |
0xC6 |
Self-check: power module 1 output voltage off target | — | — |
0xC7 |
Self-check: power module 2 output voltage off target | — | — |
0xC8 |
Self-check: power module 3 output voltage off target | — | — |
0xC9 |
Self-check: power module 4 output voltage off target | — | — |
0xCA |
Self-check: power module 5 output voltage off target | — | — |
0xCB |
Self-check: power module 6 output voltage off target | — | — |
0xCC |
Self-check: output voltage stays high after modules stopped and output disconnected | — | — |
0xCD |
Self-check: voltage present on output while output and pre-charge relays are open | — | — |
0xCE |
Self-check: no power module present at initialisation | — | — |
0xCF |
Self-check: power modules present but all failed | — | — |
0xD0 |
Self-check: PLC chipset missing, CCS mode unavailable | — | — |
0xE0 |
OSBX module missing or failed | — | — |
0xE1 |
Voltage detected on both OSBX outputs | — | — |
0xE2 |
OSBX temperature too high | — | — |
0xE3 |
OSBX fan not working properly | — | — |
0xE4 |
Voltage between OSBX input and output too high | — | — |
0xE5 |
Insulation failure detected by OSBX (CHAdeMO) | — | — |
0xFF |
Unknown error | — | — |
EVlink DC 24 kW — AC part
These values can add up in a single code. All of them are internal errors.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
0x2 |
AC side: power meter error | Internal error: contact after-sales service. | — |
0x4 |
AC side: over-temperature error | Internal error: contact after-sales service. | — |
0x8 |
AC side: overvoltage error | Internal error: contact after-sales service. | — |
0x10 |
AC side: overcurrent error | Internal error: contact after-sales service. | — |
0x20 |
AC side: connector error | Internal error: contact after-sales service. | — |
0x40 |
AC side: emergency stop error | Internal error: contact after-sales service. | — |
0x80 |
AC side: motherboard error | Internal error: contact after-sales service. | — |
0x400 |
AC side: lock error | Internal error: contact after-sales service. | — |
0x800 |
AC side: low voltage error | Internal error: contact after-sales service. | — |
0x2000 |
AC side: communication error | Internal error: contact after-sales service. | — |
0x4000 |
AC side: contactor error | Internal error: contact after-sales service. | — |
0x8000 |
AC side: EV diode (pilot) error | Internal error: contact after-sales service. | — |
0x10000 |
AC side: "dx" error | Internal error: contact after-sales service. | — |
LEDs and display
EVlink Pro AC
A red light means the charge is stopped. Warnings do not turn the light red.
| Signal | Meaning | What to do |
|---|---|---|
| Red light, 1 flash every 10 s | Internal error | Unplug the EV and power-cycle the station. If still red, stop using the station, export the diagnostic report via eSetup and contact Schneider Electric Customer Care. |
| Red light, 2 flashes every 10 s | Communication error with the vehicle | Unplug and replug the cable. Try another cable, vehicle or EV simulator. If it persists, export the diagnostic report and contact Schneider Electric Customer Care. |
| Red light, 3 flashes every 10 s | Communication error with the power meter (internal or external) | Internal meter: contact Schneider Electric Customer Care. External meter: have the installer check its connection, activity and configuration, and the Panel Server if used. Give Customer Care the meter reference and station serial number. |
| Red light, 4 flashes every 10 s | OCPP / supervision communication error | Check the EV Charging Expert if present. Check the modem and its signal strength. Check the network path. Export the diagnostic report and contact Schneider Electric Customer Care. |
EVlink Parking / City / Smart Wallbox — troubleshooting mode
Troubleshooting mode is only available when the socket indicator is steady red: press the stop button (Parking / City: on the faulty side). Codes are replayed in chronological order, separated by pauses. One blink count can cover several faults.
| Signal | Meaning | What to do |
|---|---|---|
| 1 blink | Surge arrester fault (cartridge faulty or badly seated, status connector unplugged or wire broken) — Parking / City | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
| 2 blinks | Socket or flap lock fault: lock sensor state does not match (Parking / City / Smart Wallbox) or flap inductive sensor mismatch (Parking / City) | Inspect the connector and socket; remove any foreign body. Reinsert the plug fully. Close the flap firmly. |
| 3 blinks | Cannot reach the master board (Parking / City) or energy reserve too low to drive the socket lock (Smart Wallbox) | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
| 4 blinks | Contactor state mismatch, or wrong feedback from protection input 1 (socket breaker, RCD) | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
| 5 blinks | Communication loss: cluster manager, modem (RSSI below 10), OCPP supervision, or NTP server | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
| 6 blinks | Lost communication with the RFID reader or with the iEM3xxx energy meter | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
| 7 blinks | Wrong number of phases (single-phase station wired three-phase, Parking / City) or overcurrent from the vehicle | For overcurrent: try another vehicle. For phase mismatch: contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
| 8 blinks | Vehicle / cable problem: external reader link lost, plug not connected within one minute, CP fault, wrong PP value, CP short-circuit, or cable pulled out during charge | Inspect cables and sockets, remove foreign bodies, reinsert connectors. Try another cable, then another vehicle or simulator. Stop the charge from the vehicle before unplugging. |
| 9 blinks | Anti-intrusion fault: door open or door contact faulty (Parking / City) | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
| 10 blinks | Configuration file missing, damaged or already open | Contact Schneider Electric Customer Care with the commercial reference and serial number from the product label. |
EVlink Smart Wallbox — user view
After a 5-second press on the push-button.
| Signal | Meaning | What to do |
|---|---|---|
| Steady red, 2 flashes | Station or charging cable | Unplug and replug the cable. Try another cable; if that fixes it, contact the cable supplier. Otherwise contact the installer or Schneider Electric Customer Care. |
| Steady red, 5 flashes | Charging station | Power-cycle the station. If it persists, contact the installer or Schneider Electric Customer Care. |
| Steady red, 6 flashes | Charging station | Contact the installer or Schneider Electric Customer Care. |
| Steady red, 7 flashes | Electric vehicle | Contact the vehicle dealer. |
| Steady red, 8 flashes | Charging cable | Unplug and replug the cable. Try another cable; if that fixes it, contact the cable supplier. Otherwise contact the installer or Schneider Electric Customer Care. |
| Steady red, 10 flashes | Charging station | Contact the installer or Schneider Electric Customer Care. |
SE Charge Pro
| Signal | Meaning | What to do |
|---|---|---|
| Front LED solid red | Any error other than DC leakage: electrical safety, internal, vehicle communication, power meter communication or OCPP communication | — |
| Front LED blinking red (2 Hz, permanent) | DC leakage above 6 mA (RDC-DD trip) | — |
| Front LED orange breathing | Connection to the supervision platform failed during commissioning | — |
| Front LED orange blinking (2 Hz) | eSetup pairing failed (5 s) or authentication failed (2 s) | — |
| Side LED blinking red | Anti-tripping module pairing failed, PLC bandwidth overload, TIC link lost, or external meter (PowerTag, Resi9, P1…) link lost | — |
Sources
- EVlink Pro AC Charging Stations – Troubleshooting Guide (DOCA0282EN-00, 2023-07) — https://www.se.com/be/en/download/document/DOCA0282EN/
- EVlink Pro AC – OCPP Protocol Connectivity Guide (GEX1969200-12 (firmware 2.1.0), 2026-06) — https://download.se.com/files?p_Doc_Ref=GEX1969200
- EVlink Pro AC – Modbus Connectivity Guide (GEX1969300-06, 2026-03) — https://download.se.com/files?p_Doc_Ref=GEX1969300
- EVlink Troubleshooting guide (EVlink Parking, EVlink City, EVlink Smart Wallbox) (DOCA0117EN-01, 2022-06) — https://www.se.com/au/en/download/document/DOCA0117EN/
- EVlink Smart Wallbox – User guide (NHA95096-06, 2022-01) — https://www.se.com/au/en/download/document/NHA95096/
- Schneider Charge Pro – Installation Guide (BRU2882901-07 (EN), 2026-06) — https://www.se.com/hk/en/download/document/BRU2882901/
- EVlink Pro DC – OCPP Protocol Connectivity Guide (DOCA0311EN_IEC-03, 2026-02) — https://download.se.com/files?p_Doc_Ref=DOCA0311EN
- EVlink Pro DC 180 / 150 / 120 – Installation Guide (GEX4300800-06_EN, 2026-08) — https://download.se.com/files?p_Doc_Ref=GEX4300800
- Error Codes – charging station EVlink DC 24 kW (NNZ22837, 2020) — https://www.se.com/be/en/download/document/NNZ22837/
