0% found this document useful (0 votes)
10K views2,363 pages

EN - HYC - XX - MAN - OCPP Error Codes Software Version 2.2.x

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10K views2,363 pages

EN - HYC - XX - MAN - OCPP Error Codes Software Version 2.2.x

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 2363

ERROR CODES SOFTWARE VERSION 2.2.

DATE

9/9/2024

errorCode ocppName
0 No Error
1 PLC Error

2 SLAC Error
3 SLAC interrupted

4 Link Error
5 Link Error

6 SDP Error
7 SDP Error

8 TCP Error
9 TCP Error
10 TCP Error
11 TCP Error

12 TCP Error

13 TCP Error

14 V2G Error

15 Lock Fault

16 Lock Fault

17 Lock Fault

18 Isolation Fault
19 Stack Error

20 Cable Error

23 Authorization Timeout
24 Isolation Fault
25 Isolation Fault
26 Isolation Fault

27 Isolation Fault
28 Isolation Fault

29 Isolation Fault

30 Cooler Error
31 Cooler Error
32 Cooler Error
33 Cooler Error
34 Cooler Error
36 Cooler Error
39 Surge Arrester Error
40 ISO Selftest Cable Plugged
41 Meter Pairing Error
42 Meter Eichlog full
43 Meter communication Error
44 Meter fatal Error
45 Meter full charging Error
46 Meter no pairing Error
47 Meter latest start charge refused
Error
50 EV Error voltage present

51 EV Error other
52 EV Wrong voltage requested
53 EV Wrong CP state
54 EV Wrong precharge voltage
55 EV No current flow
60 Cable communication Error
61 Cable leakage Error
62 Cable temphigh Error
63 Cable tempDelta Error
64 Cable tempSensorDc Error
65 Cable tempSensorHousing Error
66 Cable HW fault Error
67 Cable critical lever Error
70 CHAdeMo timeout 1 Error
71 CHAdeMo timeout 3 Error

72 CHAdeMo timeout 5 Error

73 CHAdeMo timeout 6 Error

74 CHAdeMo timeout 9 Error

75 CHAdeMo timeout 11 Error


76 CHAdeMo timeout 14 Error

77 CHAdeMo timeout 15 Error

78 CHAdeMo can timeout Error

79 CHAdeMo vehicle normal stop Error

80 CHAdeMO vehicle fault flags


voltage Error

81 CHAdeMO vehicle fault flags


current Error
82 CHAdeMO vehicle fault flags
temperature Error
83 CHAdeMO vehicle fault flags
charging system Error
84 CHAdeMO vehicle fault flags shift
position Error
90 GBT wrong protocol version Error
91 GBT BRM timeout Error
92 GBT BCP timeout Error
93 GBT BRO 00 timeout Error
94 GBT BRO AA timeout Error
95 GBT BCS timeout Error
96 GBT BCL timeout Error
97 GBT BSM timeout Error
100 Stack duplicate Error
101 Stack allocation timeout

150 Output disabled iso fault


151 Output disabled iso fault persistent

152 Output disabled iso warning count

160 Output relay plus welded


161 Output relay minus welded
162 Partitioning relay welded

170 Serial_Port_Open
171 Serial_Port_Configure
172 Serial_Port_Rs485
173 Serial_Port_Poll_Error
174 Serial_Port_Unexpected_Poll_Even
t
175 Serial_Port_Timeout
176 Serial_Port_Write_Error
177 Serial_Port_Read_Error
180 DzgMeteringBus_Timeout
190 DzgProtocol_Fewer_Bytes_Than_M
inimum
191 DzgProtocol_Fewer_Bytes_Than_F
rame_Element_Length
192 DzgProtocol_Trailing_Bytes_Detect
ed
193 DzgProtocol_Checksum_Mismatch

194 DzgProtocol_Request_Response_
Mismatch
195 DzgProtocol_Payload_Error
196 Authorization_Failed
197 Sequence_Error
198 EmergencyStopCP_Unplug
199 EmergencyStopCP_CPError
200 EmergencyStopCP_BeforeCharging
Loop
201 EmergencyStopCP_DuringCharging
Loop
202 EmergencyStopCP_AfterChargingL
oop
203 EmergencyStopCP_Other
204 EmergencyStopPP_ContinuityLoss

207 EmergencyStopCP_WrongTeardow
nOrderOnUserStop
208 EmergencyStopCP_PrematureUnpl
ugAfterChargingLoop
220 SLAC_Timeout_ParamReq_AfterPl
ugin
221 SLAC_Timeout_ParamReq_AfterEv
Restart
222 SLAC_Timeout_ParamReq_AfterEv
seRestart

223 SLAC_Timeout_ParamReq_Other

224 SLAC_Timeout_StartAttnCharInd

225 SLAC_Timeout_AttnCharRsp
226 SLAC_Timeout_ValidateReq

227 SLAC_Timeout_MatchReq
228 SLAC_Error_Other
1000 Door Closed
1001 Door Opened
1002 Emergency StopButton Disengaged

1003 Emergency StopButton Engaged


1004 Uncontrolled Reboot
OFTWARE VERSION 2.2.x

hyperlogName
NoError
PLC_Error

DEPRECATED__SLAC_Timeout
SLAC_Interrupted

Link_Timeout
Link_Interrupted

SDP_Timeout
SDP_Interrupted

TCP_AcceptError
TCP_EmptyPacket
TCP_Error
TCP_POLLERR

TCP_POLLHUP

TCP_POLLRDHUP

V2G_Error

Lock_Fault

Lock_OpenLoad

Lock_Overcurrent

ISO_Fault
Stack_Error

Cable_Error_unknown

Authorization_Timeout
ISO_Fault_Check
ISO_Fault_Charging
Discharge_Slow

Output_Voltage_Low
ISO_Warning_Check

ISO_Warning_Charging

Cooler_Error_Level
Cooler_Error_Communication
Cooler_Error_Fan1
Cooler_Error_Fan2
Cooler_Error_Temp_Sensor
Cooler_Error_Level_Sensor
Surge_Arrester_Error
ISO_Selftest_Cable_Plugged
Meter_Error_Pairing
Meter_Error_Eichlog_Full
Meter_Error_Communication
Meter_Error_Fatal
Meter_Error_Charging_Full
Meter_Error_No_Pairing_Executed
Meter_Error_Latest_Start_Charge_Refused

EV_Error_VoltagePresent

EV_Error_Other
EV_Error_WrongVoltageReq
EV_Error_WrongCPState
EV_Error_WrongVoltagePrecharge
EV_Error_NoCurrentFlow
Cable_Error_Communication
Cable_Error_Leakage
Cable_Error_TempHigh
Cable_Error_TempDelta
Cable_Error_TempSensorDc
Cable_Error_TempSensorHousing
Cable_Error_HW_Fault
Cable_Error_CriticalLevel
CHAdeMO_Error_Timeout1
CHAdeMO_Error_Timeout3

CHAdeMO_Error_Timeout5

CHAdeMO_Error_Timeout6

CHAdeMO_Error_Timeout9

CHAdeMO_Error_Timeout11
CHAdeMO_Error_Timeout14

CHAdeMO_Error_Timeout15

CHAdeMO_Error_Timeout_CAN

CHAdeMO_Error_VehicleNormalStop

CHAdeMO_Error_VehicleFaultFlags_Voltage

CHAdeMO_Error_VehicleFaultFlags_Current

CHAdeMO_Error_VehicleFaultFlags_Temperature

CHAdeMO_Error_VehicleFaultFlags_ChargingSystem

CHAdeMO_Error_VehicleFaultFlags_ShiftPosition

GBT_Error_WrongProtocolVersion
GBT_Error_BRM_Timeout
GBT_Error_BCP_Timeout
GBT_Error_BRO_00_Timeout
GBT_Error_BRO_AA_Timeout
GBT_Error_BCS_Timeout
GBT_Error_BCL_Timeout
GBT_Error_BSM_Timeout
Stack_Error_Duplicate
Stack_Allocation_Timeout

Output_Disabled_IsoFault
Output_Disabled_IsoFaultPersistent

Output_Disabled_IsoWarningCount

Output_Relay_Plus_Welded
Output_Relay_Minus_Welded
Partitioning_Relay_Welded

Serial_Port_Open
Serial_Port_Configure
Serial_Port_Rs485
Serial_Port_Poll_Error
Serial_Port_Unexpected_Poll_Event

Serial_Port_Timeout
Serial_Port_Write_Error
Serial_Port_Read_Error
DzgMeteringBus_Timeout
DzgProtocol_Fewer_Bytes_Than_Minimum

DzgProtocol_Fewer_Bytes_Than_Frame_Element_Length

DzgProtocol_Trailing_Bytes_Detected

DzgProtocol_Checksum_Mismatch

DzgProtocol_Request_Response_Mismatch

DzgProtocol_Payload_Error
Authorization_Failed
Sequence_Error
EmergencyStopCP_Unplug
EmergencyStopCP_CPError
EmergencyStopCP_BeforeChargingLoop

EmergencyStopCP_DuringChargingLoop

EmergencyStopCP_AfterChargingLoop

EmergencyStopCP_Other
EmergencyStopPP_ContinuityLoss

EmergencyStopCP_WrongTeardownOrderOnUserStop

EmergencyStopCP_PrematureUnplugAfterChargingLoop

SLAC_Timeout_ParamReq_AfterPlugin

SLAC_Timeout_ParamReq_AfterEvRestart
SLAC_Timeout_ParamReq_AfterEvseRestart

SLAC_Timeout_ParamReq_Other

SLAC_Timeout_StartAttnCharInd

SLAC_Timeout_AttnCharRsp
SLAC_Timeout_ValidateReq

SLAC_Timeout_MatchReq
SLAC_Error_Other
Door Closed
Door Opened
Emergency StopButton Disengaged

Emergency StopButton Engaged


Uncontrolled Reboot
COMPANY

Alpitronic GmbH | Srl. Bozner-Boden-Mitterweg 33 | Via di Mezzo ai Piani 33. I-39100 Bozen | Bolzano

descriptionDetailed
No error.
Communication failure with powerline modem of CCS connector, Powerline modem does
not respond or communication gets interrupted
Timeout while waiting for SLAC match
Connection interrupted while waiting for SLAC match,Cable disconnect has been
detected. Loose connection / Charge cable may not be plugged in correctly
Timeout while waiting for GPhy LINK after SLAC match
Connection interrupted while waiting for GPhy LINK after SLAC match, Loose connection
/ Charge cable may not be plugged in correctly
Timeout waiting for SECCDiscover request from EV
Cable disconnect detected while waiting for SECCDiscover request, Loose connection /
Charge cable may not be plugged in correctly
TCP socket to EV failed
TCP socket to EV failed
TCP socket to EV failed
POLLERR flag active while reading TCP socket. Usually indicating a Reset-flag (RST -
0x04) sent by the EV. Reset, indicates a harsh shutdown. Usually to be used in case of
errors
POLLHUP flag active. Connection terminated by local low-level socket handling. Usually
due to an internal socket handling error
POLLRDHUP flag active. Usually indicating a Finish-flag (FIN - 0x01) sent by the EV.
Finish indicates a intended termination of the socket, connection in a good case
scenario. However, FIN is often used instead of RST, even in error scenarios
V2G Sequence error, The received V2G message is not allowed during the current state

A lock fault was reported by the EV (CCS: Field: EVError, CHAdeMO: control signal on
cable, monitored and mapped on a CAN signal by CTRL_IO). Charge cable may not be
plugged in correctly / Failure of the locking actuator
Locking circuit detected no current flow. Locking actuator not connected properly to
CTRL_IO board (KF3) / Failure of the locking actuator
Locking circuit detected a high current flow, exceeding the permitted limits. Charge cable
may not be plugged in correctly / Failure of the locking actuator
The RCD device reported an error, Residual current device (RCD) tripped
Power general stack error was diagnosed. Log files have to be analyzed for further
details, At least one Powerstack is in Fault-state. Check individual errors - if available
Cable cooling unit error, Cable not properly connected to CTRL_IO board (KF3) / Cable
damaged
The customer did not authenticate in time
An isolation fault was detected during isolation check
An isolation fault was detected during an ongoing power transfer
Overall timeout of 20s for CH_SUB_03 (insulation/latch check) and the subsequent
output voltage descent was exceeded
Output voltage too low to perform isolation check
An isolation warning was detected during isolation check, Isolation resistance dropped
below warning threshold
An isolation warning was detected during an ongoing power transfer, Isolation resistance
dropped below warning threshold
Cable cooling unit: coolant level low
Communication with cable cooling unit failed
Cable cooling unit: Fan 1 defect
Cable cooling unit: Fan 2 defect
Cable cooling unit: temperature sensor failed
Cable cooling unit: coolant level sensor failed
Surge arrester device indicated a fault state
A connector was re-plugged into the EV during an ongoing isolation self test
Pairing with meter failed
Meter log is full
Communication with meter failed. In case of TYPE 2: RCD Tripped
Meter reported fatal error
Meter charge log full
Meter is not paired with SECC
Error while trying to start a metering session

Voltage > 60 V Measuresd at charging connector before charging session has been
initialized
The EV has communicated an error
The EV requested an abnormal (out of bounds) target voltage
The EV requested power delivery, but it´s CP state is not C or D
The EV requested an abnormal (out of bounds) target voltage
No current flow to EV
CAN timeout for cable-related message
Leakage of cooling liquid detected
Any of the measured temperature is too high
Temperature delta between DC+ and DC- too high
Summarized temperature status
Housing temperature status
Cable Good signal reported (non-critical) error, not covered by the errors above
Cable Good signal reported critical error
Timeout of 120s expired while waiting for vehicle CAN communication being initiated by
the EV
Timeout of 8s expired while waiting for activation of both redundant enable charging
signals by the EV
EV contactors weren't closed within 4s after activating switch d2 (charge sequence
signal 2)
Precharge and closing of charging station output contactors wasn't completed within 4s
after closing of EV contactors
EV failed to reset the Vehicle charge permission(opto coupler j) within 4s after the
transmission of an active chargingstop control-flag
EV contactor welding detection not completed within 10s
After completion of the welding detection and deactivation of j1 and j2, an unenergized
state wasn't detected within 4s(CHAdeMO version < v1.1 → 6s)
The EV didn't stop transmitting its CAN messages within 2.5s (3s for CHAdeMO version
< v1.1>)
Either of the CAN messages expected from the vehicle wasn't received in time (timeout:
400ms), while monitoring routine (CH_SUB_06) was active
Vehicle set the Normal stop request beforecharging-flag (CAN message 102)

over voltage-flag / under voltage-flag was set by EV (CAN message 0x102), indicating,
that measured battery voltage exceeded / fell below the upper / lower voltage limit
(defined by EV). Furthermore, this error can indicate an unacceptable deviation between
measured battery voltage (EV measurement) and reported output present current
(charging station measurement).

current deviation-flag was set by EV (CAN message 0x102)

High battery temperature-flag was set by EV (CAN message 0x102). This flag is set,
when the battery temperature exceeded a predefined temperature limit.
The EV detected either a vehicle error or a charging station error

The gear lever isn't set to parking

GB/T protocol version error


GB/T BRM timeout
GB/T BCP timeout
GB/T BRO timeout
GB/T BRO timeout
GB/T BCS timeout
GB/T BCL timeout
GB/T BSM timeout
Power module configuration error
Stacks weren't allocated to a connector in time. The stack allocation usually takes place
between authorization and isolation check
Connector will be locked from now on, due to a confirmed isolation fault
The connector is locked persistently (i.e., even after service restart due to a previous
locking condition (Output_Disabled_IsoFault, Output_Disabled_IsoFault Persistent)
Connector will be locked from now on, due to a high number of isolation warnings during
previous isolation checks
A welded DC+ contactor was diagnosed during output contactor welding check
A welded DC- contactor was diagnosed during output contactor welding check
A welded bridge relay (stack interconnection) was diagnosed during stack deallocation

Could not open serial port


Error while configuring serial port
Error while configuring serial port for RS485 mode
Serial port error while polling
Serial port error while polling

Timeout while waiting for serial port data


Error while trying to write data to serial port
Error while trying to read data from serial port
Timeout on the DZG metering bus: no data received
DZG protocol error - Error constructing frame from bytes: too few bytes

DZG protocol error - Error constructing frame from bytes: fewer bytes in frame than
claimed by frame element length
DZG protocol error - Error constructing frame from bytes: trailing bytes detected

DZG protocol error - Error constructing frame from bytes: checksum mismatch

DZG protocol error - Received structurally mismatching frame in read attempt loop

DZG protocol error - Generic error while parsing meter message


Plug and Charge authorization declined by backend
EV sent a message which was not expected at that time
Unexpected CP state transition (X → A) indicating an unplug event
Unexpected CP state transition (X → E|F) indicating an error state
Unexpected CP state transition before charging loop(C → B) indicating an EV-initiated
emergency stop
Unexpected CP state transition during charging loop(C → B) indicating an EV-initiated
emergency stop
Unexpected CP state transition after charging loop(C → B) indicating an EV-initiated
emergency stop
Other errors related to unexpected CP states, not covered by the error codes above
(CCS1) Unexpected PP state transition to unconnected during ongoing TCP
communication
Emergency stop activated due to incorrect teardown order during user-initiated stop

Emergency stop triggered due to premature unplugging during the charging loop

EV didn't initiate SLAC (by sending CM_SLAC_PARM.REQ) after cable was plugged in

EV didn't initiate SLAC (by sending CM_SLAC_PARM.REQ) after a restart initiated by


the EV (e.g.: by sending a BCB-toggle after a terminated session)
EV didn't initiate SLAC (by sending CM_SLAC_PARM.REQ) after a restart initiated by
the charger (e.g.: by sending a B1-B2-toggle / BEB-toggle / BFB-toggle after a
terminated session)
EV didn't initiate SLAC (by sending CM_SLAC_PARM.REQ) in other cases, not covered
by the more specific error codes mentioned above
EV didn't send CM_START_ATTEN_CHAR.IND afer CM_SLAC_PARM.REQ was
exchanged
EV didn't reply to CM_ATTEN_CHAR.IND by sending CM_ATTEN_CHAR.RSP
EV didn't send a valid CM_VALIDATE.REQ (step 2) after CM_VALIDATE (step 1) was
exchanged
EV didn't send CM_SLAC_MATCH.REQ after CM_ATTEN_CHAR was exchanged
Other SLAC errors not covered by more specific SLAC-related error codes
Closed signal from door contact switch, All doors of the charger have been closed
Open signal from door contact switch, At least one door of the charger got opened
Emergency stop button has been disengaged

Emergency stop button has been engaged.


Charger has experienced a reboot without undergoing proper shutdown procedures
I-39100 Bozen | Bolzano

solveActions

Reconnect vehicle
Soft reset
Hard reset vehicle
Reconnect
Move EV vehicle
Reconnect
Move EV
Hard reset vehicle
Reconnect
Move EV vehicle
Reconnect
Move EV
Hard reset vehicle
Reconnect
Move EV vehicle
Reconnect
Move EV
Hard reset vehicle
Reconnect
Move EV vehicle
Reconnect
Move EV vehicle
Reconnect
Move EV vehicle
Reconnect
Move EV
Hard reset
Fault analysis through alpitronic
Reconnect vehicle
Move EV
Hard reset vehicle
Reconnect
Move EV
Hard reset
Fault analysis through alpitronic
Reconnect vehicle
Move EV
Hard reset vehicle / Resend connector unlock command via Backend
Reconnect
Soft reset
Hard reset
Fault analysis through alpitronic
Reconnect vehicle / Resend connector unlock command via Backend
Soft reset
Hard reset vehicle / Resend connector unlock command via Backend
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Reconnect vehicle
Hard reset
Try
Harddifferent
reset vehicle
Fault analysis through alpitronic
Technician on site
Reconnect vehicle
Reconnect vehicle
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Hard
No reset action required
further

No further action required

Fault analysis through alpitronic


Technician on through
Fault analysis site alpitronic
Technician
Fault on through
analysis site alpitronic
Technician on site
Fault analysis through alpitronic
Technician on through
Fault analysis site alpitronic
Technician
Fault on through
analysis site alpitronic
Technician on site

Reconnect vehicle
Soft reset on site
Technician
Reconnect vehicle
Soft reset on site
Technician
Technician on site
Technician on site

Reconnect vehicle
Soft reset
Hard reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset
Hard reset
Fault analysis
Technician on through
site alpitronic
Reconnect vehicle
Reconnect vehicle
Fault analysis
Reconnect through alpitronic
vehicle
Fault analysis through alpitronic
Reconnect vehicle
Fault analysis through alpitronic

Reconnect vehicle
Soft reset
Hard reset
Reconnect vehicle
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset
Fault analysis through alpitronic
Technician on site

Reconnect vehicle
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset
Hard reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft reset vehicle
Reconnect
Soft
Faultreset
analysis through alpitronic
Technician on site

Fault analysis through alpitronic


Technician on through
Fault analysis site alpitronic
Technician on site
Fault analysis through alpitronic
Technician on site
No further action required
Close all service doors
No further action required

Disengage emergency stop button


severity
Info
Error

Error
Equipment Down

Error
Error

Error
Error

Error
Error
Error
Error

Error

Error

Error

Error

Error

Error

Critical Warning
Critical Warning

Error

Info
Error
Error
Error

Error
Critical Warning

Critical Warning

Critical Warning
Critical Warning
Critical Warning
Critical Warning
Critical Warning
Critical Warning
Error
Error
Error
Equipment Down
Error
Equipment Down
Equipment Down
Equipment Down
Error

Error

Error
Error
Error
Error
Error
Error
Equipment Down
Error
Error
Error
Error
Error
Error
Error
Error

Error

Error

Error

Error
Error

Error

Error

Error

Error

Error

Error

Error

Error

Error
Error
Error
Error
Error
Error
Error
Error
Error
Error

Equipment Down
Equipment Down

Equipment Down

Error
Error
Error

Error
Error
Error
Error
Error

Error
Error
Error
Error
Error

Error

Error

Error

Error

Error
Error
Error
Error
Error
Error

Error

Error

Error
Error

Error

Error

Error

Error
Error

Error

Error

Error
Error

Error
Error
Error
Error
Error

Error
Error

You might also like