Inicio / Configuración técnica / Charging Station Diagnostics & Maintenance / Manufacturer error codes / IES Synergy error codes
IES Synergy error codes
Este artículo aún no está disponible en Español. Se muestra la versión en English.
This page covers the IES Synergy Keywatt chargers present in the fleets: Keywatt 50 / 50X (Keywatt S50 / 50x Station), Wallbox G3 / G3X (Keywatt 24 Wallbox) and Station 24k (Keywatt 24 Station), as well as the Keywatt S120 / S150 / S180 and 50 Station Bus. It gives the codes documented by IES, then the codes seen on our chargers and the messages shown on the screen.
Where to read the code: in Chargekeeper, charging station list, connector details, Information column (or the active sessions list, Information column). It shows “OCPP code - vendor code - information”. See Manufacturer error codes.
How IES reports its errors
- The vendor code (
vendorErrorCode) holds a module prefix followed by a hexadecimal value, for exampleCCU:0x00000002(Context:0x00),CCU:0x0000003b(Context:0x86),AC:0x00020010,DCMETER:0x00054000,DCMETER_WRN:0x00060002orOCPP:0x0003f100. - The information field holds a readable text, for example “External emergency stop.”.
- With no fault, the charger sends the code
0x00with a state in the information field (“Waiting plugged”, “Finishing”, “Vehicle plugged”, “Cancel charge”, “Suspended EV”, “Booting”…). This value means “no fault”. - For
CCU:0x000000NNcodes, the last byteNNwould match the code shown on the screen0xNN(to be confirmed): for exampleCCU:0x00000002arrives with the information “External emergency stop.”, which matches screen code0x02(emergency stop). The match is not systematic: overheating, for example, arrives asCCU:0x00000050, while the screen shows it as0x0Aor0x86. - IES does not publicly document the
(Context:0xYY)suffix, nor theAC:,DCMETER:,DCMETER_WRN:andOCPP:prefixes. The user manuals only list the codes a driver can act on; the others are described in the IES maintenance manual, which is not published.
Keywatt 50 / 50X, Wallbox G3 / G3X, Station 24 — codes sent to the supervision
Codes shown on the touch screen as “Error occurred: 0xNN” and printed in every recent Keywatt manual (S50, 24 Wallbox G3 / G3X, 24 Station, S120 to S180, 50 Station Bus). Several codes are listed together for the same message; the manual does not say what sets them apart. Codes 0x07, 0x29, 0x11, 0x14 and 0x19 concern the CHAdeMO connector only.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
0x02 |
Emergency stop triggered: the session is stopped (listed together with 0x03, 0x81 for the same message). | Unplug the vehicle. Release the emergency button by turning it clockwise until it pops out; the charger runs a self-test and becomes available again. If the button was not pressed, have the maintenance partner check the emergency-stop circuit. | OtherError |
0x03 |
Emergency stop triggered: the session is stopped (listed together with 0x02, 0x81 for the same message). | Unplug the vehicle. Release the emergency button by turning it clockwise until it pops out; the charger runs a self-test and becomes available again. If the button was not pressed, have the maintenance partner check the emergency-stop circuit. | — |
0x81 |
Emergency stop triggered: the session is stopped (listed together with 0x02, 0x03 for the same message). | Unplug the vehicle. Release the emergency button by turning it clockwise until it pops out; the charger runs a self-test and becomes available again. If the button was not pressed, have the maintenance partner check the emergency-stop circuit. | — |
0x0A |
The charging station is overheating (listed together with 0x86 for the same message). | Unplug the vehicle. Check that no air inlet or outlet is blocked and clean it. If it recurs, contact IES support or the maintenance partner. | — |
0x86 |
The charging station is overheating (listed together with 0x0A for the same message). | Unplug the vehicle. Check that no air inlet or outlet is blocked and clean it. If it recurs, contact IES support or the maintenance partner. | — |
0x51 |
Communication with the vehicle was lost during the session. | Unplug the vehicle and start a new session. If it happens with several vehicles, contact support. | — |
0x07 |
CHAdeMO: communication with the vehicle was lost (listed with 0x07, 0x29 and 0x51). | Unplug the vehicle and press X on the screen, then retry. | — |
0x29 |
CHAdeMO: communication with the vehicle was lost (listed with 0x07, 0x29 and 0x51). | Unplug the vehicle and press X on the screen, then retry. | — |
0x22 |
Connector could not be locked on the vehicle inlet (listed together with 0x33). | Plug again, keeping the connector pressed against the vehicle until the charge has started. If it persists, contact the maintenance partner (locking device). | — |
0x33 |
Connector could not be locked on the vehicle inlet (listed together with 0x22). | Plug again, keeping the connector pressed against the vehicle until the charge has started. If it persists, contact the maintenance partner (locking device). | — |
0x3A |
Vehicle battery is not compatible with this charger (CCS / AC). | Unplug the vehicle; use another charger suited to the vehicle. | — |
0x11 |
CHAdeMO: vehicle battery is not compatible with this charger. | Unplug the vehicle and press X; use another charger. | — |
0x32 |
Vehicle gear selector is not in the parking position (CCS / AC). | Unplug, put the vehicle in park, then plug in again. | — |
0x14 |
CHAdeMO: vehicle gear selector is not in the parking position. | Unplug, press X, put the vehicle in park and retry. | — |
0x15 |
The vehicle itself reported an error and the charge stopped. | Read the message shown in the vehicle. Unplug the vehicle (CHAdeMO: press X once unplugged). | — |
0x31 |
Vehicle battery temperature too high (CCS / AC). | Unplug the vehicle and let the battery cool down before retrying. | — |
0x19 |
CHAdeMO: vehicle battery temperature too high. | Unplug, press X, let the battery cool down before retrying. | — |
0x46 |
Link lost between the touch screen (HMI) and the charger electronics. On the newer DC chargers, this code arrives with the information “Error connecting to PowerUnit.”: meaning to be confirmed with IES. | Unplug the vehicle. If it repeats, reboot the station remotely and contact IES support. | InternalError |
Fault messages of the 50 kW DC chargers — Keywatt 50 Cube and 50 kW CHBRN charger
Fault names shown by the previous-generation 50 kW DC chargers (Keywatt 50 Cube, 50 kW charger CHBRN011436 / CHBRN012230), absent from our fleets. They describe the same architecture (CCU and power supervisor, “PSU”) as the current Keywatt DC chargers. Some labels received from our chargers look like them, but no source links these names to a vendor code value.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
EXT_Emergency_Stop |
Emergency-stop push button activated. | Release the emergency button and let the charger restart. | — |
ERR Vout_at_start |
Unexpected voltage present on the DC output when the charger starts. | Contact the maintenance partner. | — |
Out_Pwr_Switch_Fail. |
DC output contactor is defective. | Contact the maintenance partner. | — |
Can_Data_invalid |
Vehicle sent invalid CAN data, or did not update its current request when charging started. | Retry; if vehicle-specific, check the vehicle. | — |
Can_Frame_absent |
No CAN communication with the vehicle. | Re-plug and retry; check the connector and cable. | — |
ShortCircuit |
Output current too high: above the maximum, or above 5 A during the insulation test. | Contact the maintenance partner. | — |
OverVoltage |
Charger output voltage above its maximum limit. | Contact the maintenance partner. | OverVoltage |
ChargerOverHeating |
Power modules reached their maximum operating temperature (cooling problem). | Check the air vents and fans; contact the maintenance partner if it recurs. | — |
Over Limit I |
Vehicle asks for more current than allowed by the start-of-charge calculation. | Retry; if vehicle-specific, check the vehicle. | — |
PSU Absent |
Power supervisor does not respond (internal fault). | Contact the maintenance partner. | InternalError |
PSU Timeout Change |
Power supervisor timed out during a state change (internal fault). | Contact the maintenance partner. | — |
PSU bad state |
Power supervisor entered an inconsistent state (internal fault). | Contact the maintenance partner. | — |
Connector_Lock |
CHAdeMO plug locking coil is defective. | Contact the maintenance partner. | — |
BatteryIncompatib. |
Vehicle battery voltage range not suitable for the charger. | Use another charger. | — |
BatteryMalfunction |
Vehicle battery fault: no CAN at start, wrong current/voltage data, or abnormal start voltage. | Check the vehicle. | — |
ChargingStopCtl |
Charge start refused by the vehicle (CAN or physical I/O line). | Check the vehicle state and retry. | — |
VehicleShiftPosition |
Vehicle gear selector not in neutral/park. | Put the vehicle in park and retry. | — |
VehicleOtherFaults |
Fault reported by the vehicle. | Check the vehicle's own diagnostics. | — |
BatteryOverVoltage |
Vehicle detected an over-voltage. | Check the vehicle; contact the maintenance partner if repeated. | — |
BatteryUnderVoltage |
Vehicle detected a voltage that is too low. | Check the vehicle. | — |
BatteryCurrentDiff. |
Vehicle found a mismatch between its current measurement and the charger's CAN data. | Retry; contact the maintenance partner if repeated. | — |
HighBatteryTemp. |
Vehicle detected battery overheating. | Let the battery cool down before retrying. | — |
VoltageDifferential |
Vehicle found a mismatch between its voltage measurement and the charger's CAN data. | Retry; contact the maintenance partner if repeated. | — |
InsulationFailure |
Earth-fault (insulation) current detected by the charger. | Take the connector out of service and contact the maintenance partner. | InternalError |
ChargerMalfunction |
Charge stopped by the power supervisor after an output over-voltage, or by the STOP/OFF button. | If not a manual stop, contact the maintenance partner. | — |
PSU ERROR ARU |
Software emergency stop requested by the power supervisor (internal). | Contact the maintenance partner. | — |
PSU Modules COM |
Communication lost with the power modules (internal). | Contact the maintenance partner. | — |
PSU CCU COM |
Communication interrupted between the power supervisor and the CCU (internal). | Contact the maintenance partner. | — |
PSU OVERVOLTAGE |
Over-voltage detected by the power supervisor (internal). | Contact the maintenance partner. | — |
PSU OVERHEATING |
Overheating detected by the power supervisor (internal). | Check ventilation; contact the maintenance partner. | — |
PSU COHERENCY |
Consistency error detected by the power supervisor (internal). | Contact the maintenance partner. | — |
PSU INSULATION |
Earth fault detected by the power supervisor (internal). | Contact the maintenance partner. | — |
PSU LIMIT Vmax |
Output voltage exceeded its limit by more than 5 V (power supervisor). | Contact the maintenance partner. | — |
PSU SHORT CIRCUIT |
Output short circuit detected by the power supervisor (internal). | Contact the maintenance partner. | — |
PSU Bad Vred |
Input (grid-side) voltage out of range, detected by the power supervisor. | Have the supply voltage checked by a qualified electrician; contact the maintenance partner. | — |
OverCurrent |
Output current above the maximum value. | Contact the maintenance partner if repeated. | OverCurrentFailure |
ERR EV Charge Status Not Ready |
Vehicle requests a charge while reporting a not-ready status. | Re-plug and retry. | — |
ERR Bad Pilot State during charge |
Control pilot left state C during the charge. | Re-plug and retry; check the cable. | — |
EV bad pilot state at start |
Control pilot not in state A or B at session start. | Re-plug and retry. | — |
Error EV Not Ready |
Vehicle 'ready' flag not set. | Retry. | — |
Error Timeout : EV Session Setup Request not received |
Vehicle did not send the session setup request within 20 s. | Re-plug and retry. | — |
Error Timeout : EV Ready to Charge State not received |
Vehicle did not signal ready-to-charge within 40 s. | Re-plug and retry. | — |
Error No message or Client Disconnected |
Vehicle detected as present but it sends no request. | Re-plug and retry. | — |
Codes seen on our chargers, not documented by IES
These codes were received from chargers supervised by Chargekeeper but do not appear in the manufacturer's public documentation. The label is the one sent by the charger itself.
Chargers concerned: keywatt 50 CCS, keywatt 50 AC CCS, keywatt 50X dual, wallbox G3 CCS AC, wallbox G3X dual, wallbox G3X tri, station 24k, KS120 2xCCS, KM100 2xCCS and KM200 2xCCS (model names sent by the chargers). The same code can arrive with several (Context:…) suffixes: each form received has its own row.
| Code | Label sent by the charger | OCPP code |
|---|---|---|
AC:0x00020000 |
“No error.” | — |
AC:0x00020002 |
“AC warnings raised : POWER METER ABNORMAL” | GroundFailure |
AC:0x00020010 |
“AC warnings raised : OVERCURRENT” | OverCurrentFailure |
AC:0x00020020 |
“AC warnings raised : CONNECTOR FAILURE” | OtherError |
AC:0x00020040 |
“AC warnings raised : EMERGENCY STOP” | OtherError |
AC:0x00020400 |
“AC warnings raised : LOCK BREAKDOWN” | ConnectorLockFailure |
AC:0x00020420 |
“AC warnings raised : CONNECTOR FAILURE, LOCK BREAK” | OtherError |
AC:0x00022000 |
“AC warnings raised : COMMUNICATION INTERRUPTION” | InternalError |
CCU:0x00000000 |
“Insulation warning is over.” | — |
CCU:0x0000001f(Context:0x00) |
“CCS: Vehicle bad pilot state.” | EVCommunicationError |
CCU:0x0000001f(Context:0x86) |
“CCS: Vehicle bad pilot state.” | EVCommunicationError |
CCU:0x0000001f(Context:0x87) |
“CCS: Vehicle bad pilot state.” | EVCommunicationError |
CCU:0x0000001f(Context:0x8b) |
“CCS: Vehicle bad pilot state.” | EVCommunicationError |
CCU:0x00000023(Context:0x00) |
“CCS: PEV incoherent pilot state during charge” | EVCommunicationError |
CCU:0x00000023(Context:0x88) |
“CCS: PEV incoherent pilot state during charge” | EVCommunicationError |
CCU:0x00000023(Context:0x89) |
“CCS: PEV incoherent pilot state during charge” | EVCommunicationError |
CCU:0x00000023(Context:0x8a) |
“CCS: PEV incoherent pilot state during charge” | EVCommunicationError |
CCU:0x00000023(Context:0x8b) |
“CCS: PEV incoherent pilot state during charge” | EVCommunicationError |
CCU:0x00000028(Context:0x07) |
“No module.” | InternalError |
CCU:0x00000028(Context:0x89) |
“No module.” | InternalError |
CCU:0x0000003b(Context:0x00) |
“CCS: TCP Connection lost with client” | EVCommunicationError |
CCU:0x0000003b(Context:0x85) |
“CCS: TCP Connection lost with client” | EVCommunicationError |
CCU:0x0000003b(Context:0x86) |
“CCS: TCP Connection lost with client” | EVCommunicationError |
CCU:0x0000003b(Context:0x87) |
“CCS: TCP Connection lost with client” | EVCommunicationError |
CCU:0x0000003b(Context:0x89) |
“CCS: TCP Connection lost with client” | EVCommunicationError |
CCU:0x0000003b(Context:0x8c) |
“CCS: TCP Connection lost with client” | EVCommunicationError |
CCU:0x0000003c(Context:0x00) |
“Error SLAC timeout.” | EVCommunicationError |
CCU:0x0000003c(Context:0x82) |
“Error SLAC timeout.” | EVCommunicationError |
CCU:0x0000003f(Context:0x00) |
“CCS: PLC no link.” | EVCommunicationError |
CCU:0x0000003f(Context:0x82) |
“CCS: PLC no link.” | EVCommunicationError |
CCU:0x0000003f(Context:0x85) |
“CCS: PLC no link.” | EVCommunicationError |
CCU:0x0000003f(Context:0x86) |
“CCS: PLC no link.” | EVCommunicationError |
CCU:0x0000003f(Context:0x87) |
“CCS: PLC no link.” | EVCommunicationError |
CCU:0x0000003f(Context:0x8c) |
“CCS: PLC no link.” | EVCommunicationError |
CCU:0x00000042(Context:0x00) |
“CCS: Vehicle plugged after Ext. Emergency” | EVCommunicationError |
CCU:0x00000044(Context:0x00) |
“CCS: V2G sequence error.” | EVCommunicationError |
CCU:0x00000044(Context:0x86) |
“CCS: V2G sequence error.” | EVCommunicationError |
CCU:0x00000044(Context:0x87) |
“CCS: V2G sequence error.” | EVCommunicationError |
CCU:0x00000044(Context:0x8c) |
“CCS: V2G sequence error.” | EVCommunicationError |
CCU:0x00000044(Context:0x8d) |
“CCS: V2G sequence error.” | EVCommunicationError |
CCU:0x00000045(Context:0x00) |
“CCS: V2G request error.” | EVCommunicationError |
CCU:0x00000050(Context:0x00) |
“Over heating.” | HighTemperature |
CCU:0x00000055(Context:0x00) |
“CCS: Connector failure. T° sensor not connected.” | ConnectorLockFailure |
CCU:0x0000005a(Context:0x00) |
“No message received from EV during 60s.” | EVCommunicationError |
CCU:0x0000005a(Context:0x82) |
“No message received from EV during 60s.” | EVCommunicationError |
CCU:0x0000005a(Context:0x86) |
“No message received from EV during 60s.” | EVCommunicationError |
CCU:0x0000005a(Context:0x87) |
“No message received from EV during 60s.” | EVCommunicationError |
CCU:0x0000005b(Context:0x00) |
“EV does not setup the session after SLAC.” | EVCommunicationError |
CCU:0x0000005b(Context:0x83) |
“EV does not setup the session after SLAC.” | EVCommunicationError |
CCU:0x00000084(Context:0x00) |
“No module.” | InternalError |
CCU:0x00000087(Context:0x00) |
“Voltage for imd measurement not reached.” | InternalError |
CCU:0x00000088(Context:0x00) |
“Insulation failure M.” | InternalError |
CCU:0x0000008c(Context:0x88) |
“PSU ins controller failed.” | InternalError |
CCU:0x0000008d(Context:0x00) |
“PSU dVred.” | InternalError |
CCU:0x000000bf(Context:0x00) |
— | OtherError |
CCU:0x000000e0(Context:0x00) |
“OSBX: absent or failed.” | InternalError |
CCU:0x000000e4(Context:0x00) |
“OSBX: abnormal voltage difference.” | InternalError |
CCU:0x000000ff(Context:0x00) |
“UNDEFINED” | OtherError |
CCU:0x000000ff(Context:0x81) |
“UNDEFINED” | OtherError |
CCU:0x00000100(Context:0x82) |
— | OtherError |
CCU:0x000100bf(Context:0x80) |
— | OtherError |
CCU:0x000100bf(Context:0x81) |
— | OtherError |
CCU:0x000100bf(Context:0x88) |
— | OtherError |
CCU:0x000100bf(Context:0x8b) |
— | OtherError |
CCU:0x000100bf(Context:0x8c) |
— | OtherError |
CCU:0x000100bf(Context:0x8f) |
— | OtherError |
CCU:0x000100bf(Context:0x90) |
— | OtherError |
CCU:0x0006009b(Context:0x81) |
— | OtherError |
DCMETER:0x00050000 |
“DC meter unavailable warning is rising.” | — |
DCMETER:0x00050800 |
“DC meter unavailable warning is over.” | — |
DCMETER:0x00054000 |
“DC meter unavailable warning is rising.” | — |
DCMETER_WARN:0x00060002 |
“DC meter voltage inputs inverted warning is rising” | — |
DCMETER_WRN:0x00060002 |
“DC meter voltage inputs inverted warning is rising” | — |
MCU:0x00010028 |
“Module is absent or in failure.” | InternalError |
OCPP:0x0003f100 |
“Power loss detection” | OtherError |
OCPP:0x0003ff12 |
“Door opening detected” | OtherError |
OCPP:0x0003ff13 |
“ACMB connection lost warning is rising.” | — |
LEDs and screen
Text messages, without a code, shown on the touch screen at start-up or during a session (Keywatt S50 / 50x Station, Keywatt 24 Station, Keywatt S120 / S150 / S180). The manual does not say whether they are also sent in the information field.
| Signal | Meaning | What to do |
|---|---|---|
Error connecting server. |
Start-up stopped because the backend (CSMS) refused the connection. | Check the charge point identity and the OCPP endpoint configured on the CSMS side. Contact IES support. |
Error connecting to RFID reader. |
Start-up stopped because the RFID reader does not respond. | Contact IES support. |
Error connecting to Communication Control Unit. |
Start-up stopped because the communication control unit (CCU) board does not respond. | Contact IES support. |
Error connecting to AC Unit. |
Start-up stopped because the AC power-share board does not respond. | Contact IES support. |
AC contactor failed. |
AC contactor failure detected at start-up. | Unplug any connected vehicle. Contact IES support. |
Charger inoperative. |
The backend has set the charger to refuse charging (out of service). | Check the availability requested from the CSMS and set it back to operative if intended. |
Authorization failed! |
The backend rejected the user's identification. | Check the badge status and access rights in the CSMS. |
Charger offline. Set up to refuse offline charging. |
Charger has no backend connection and is configured not to allow offline charging. | Check the charger's network connectivity. Review the offline-charging setting if offline sessions are wanted. |
Error timeout. Please unplug your vehicle then identify. |
User identified but the session timed out before it started. | Unplug the vehicle, then identify again. |
Error updating. DO NOT CHARGE HERE. |
Firmware update failed; the charger must not be used. | Contact IES support to redo the update. |
Station shut down. Please reboot. |
Charging station has shut down and needs a restart. | Contact IES support to restart the station. |
Station rebooted. Please unplug your vehicle. |
The station restarted while a session was running. | Unplug the vehicle and start a new session. |
Warning: insulation failure. |
Insulation fault detected on the charging cable. | Take the connector out of service and contact IES support. |
Sources
- IES Synergy – User Manual Keywatt S50 Station (Keywatt 50x Station) (DUM019665-EN_V001c, 2023-10) — link
- IES Synergy – User Manual Keywatt 24 Wallbox (G3 / G3X) (DUM016055-EN_V003d) — link
- IES Synergy – User Manual Keywatt 24 Wallbox G3X V3 (DUM020403-EN_V001a) — link
- IES Synergy – User Manual Keywatt 24 Station (DUM3017446-EN_V001b) — link
- IES Synergy – User Manual Keywatt S120 / S150 / S180 (DUM4021418-EN_V001a, 2023-10) — link
- IES Synergy – User Manual Keywatt 50 Station Bus (DUM017749-EN_V001b) — link
- IES Synergy – User Manual Keywatt 50 Cube (DUM1017795-EN_V001b) — link
- IES Synergy – Charging Station 50 kW (CHBRN011436 & CHBRN012230), Instruction manual (DUM018129-EN_V001) — link
- IES Synergy Help Center — link
