Home / Technical configuration / Charging Station Diagnostics & Maintenance / Manufacturer error codes / Circontrol error codes
Circontrol error codes
This page covers Circontrol eNext Park (including eNext Park T Two), eVolve Smart and Post eVolve Smart chargers, the earlier Wallbox eNext / eNext Elite generation and the Raption 50 Gen2 fast charger. It gives the light blink sequences, the Raption error codes and its backend connection messages. The eNext Park S variant is not named in the Circontrol manuals: it is assumed to follow the eNext Park.
Where to read the code: in Chargekeeper, charging station list, connector details,
Information column (or the list of sessions in progress, Information column). It shows
"OCPP code - manufacturer code - information". See Manufacturer error codes.
How Circontrol reports its errors
- No Circontrol document states what the chargers send to the backend (OCPP code, manufacturer code, information field), nor any mapping to OCPP codes. The tables on this page therefore have no OCPP code column.
- On eNext Park and eVolve Smart chargers, diagnosis goes through the light: a sequence of red blinks, on each connector's light bar (each connector has its own). The installation manual only gives the basic colour code: green available, blue charging, red fault (eNext Park T Two: blinking blue = paused, red = fault or disabled).
- Warning: the same number of blinks does not mean the same thing on an eNext Park and on an earlier Wallbox eNext / eNext Elite. For example, 3 red blinks signal a proximity error on the eNext Park, but no voltage on the earlier eNext; 12 blinks mean too low a temperature on one, a welded contact on the other. Identify the charger generation before reading a table.
- On the Raption 50 Gen2, the code is read on the touchscreen (press the faulted connector, then the 'Information' button) or in the charger's log files, under 'Vector of Error Flags Objects'.
eNext Park, eVolve Smart and Post eVolve Smart — light sequences
Numbering of the eNext Park & eVolve Smart user manual (items 1 to 12). From item 5 onwards, the number of blinks no longer matches the item number, and there is no 5-blink sequence.
| Signal | Meaning | What to do |
|---|---|---|
| Red, continuous flashing | Item 1 'D state error': the vehicle signals state D (ventilation request, typical of some old EVs with gassing batteries) | Check the vehicle; the car park may need external ventilation; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 2 red blinks | Item 2 'E state error': communication fault between the vehicle and the charger | Unplug and retry, try another vehicle or cable; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 3 red blinks | Item 3 'Proximity error': proximity line shorted to earth while the vehicle is connected | Try another cable; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 4 red blinks | Item 4 'Negative PWM voltage error': the pilot PWM signal exchanged with the vehicle is negative or invalid | Unplug, wait for green, replug; try another vehicle; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 6 red blinks | Item 5 'Non-current selection error (DIP switch)': the on-board current limit setting does not match the hardware | Have the installer check the current-limit DIP switch setting; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 7 red blinks | Item 6 'Welded contact error': an internal short-circuit (welded contactor) has been detected | Contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 8 red blinks | Item 7 'Locking system error': the connector lock failed, e.g. plug not fully inserted in the socket outlet | Reinsert the plug fully and retry; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 9 red blinks | Item 8 'Communication error': internal communication fault (the manual does not say between which components) | Contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 10 red blinks | Item 9 'No input voltage error': no supply voltage reaches the Mode 3 board | Check that the upstream breakers and RCDs are armed; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
| 11 red blinks | Item 10 'Maximum temperature error': internal temperature too high; charging resumes by itself once back in range | Wait for the unit to cool down; check exposure and ventilation if it recurs |
| 12 red blinks | Item 11 'Minimum temperature error': internal temperature too low; charging resumes by itself once back in range | Wait for the temperature to rise |
| Fixed (steady) light bar (colour not stated) | Item 12 'Tamper error': enclosure opened, or tamper switch not in maintenance position | Have the installer close the unit properly or reset the tamper switch; contact Circontrol technical support or the installer (the manual states technical assistance is required) |
Other models: Raption 50 Gen2 — error codes
Each code is a power of two, in hexadecimal (decimal value in brackets). A value missing from the table is probably the sum of several active faults (to be confirmed). Check in this order: socket, then plug, then charger.
Procedure for all codes: read the code (current and historical flags) with the 'Information' button or in the log files, note the serial number and firmware version, and send it all to Circontrol post-sales support (ps-support@circontrol.com).
DC-side errors (CCS2 / CHAdeMO connectors, power modules) are only decoded by a Circontrol tool reserved for partners; they are not listed here.
Charger level (general fault)
The code-to-label pairing in this table was read from a text extraction of the manual and still has to be checked against the original document: the meanings are therefore marked (to be confirmed).
| Code | Meaning | What to do |
|---|---|---|
0x1 (1) |
Invalid configuration (to be confirmed) | See procedure above |
0x2 (2) |
RFID reader fault (to be confirmed) | See procedure above |
0x4 (4) |
Display fault (to be confirmed) | See procedure above |
0x8 (8) |
Tamper fault (enclosure) (to be confirmed) | See procedure above |
0x10 (16) |
The charger is tilted (to be confirmed) | See procedure above |
0x20 (32) |
Power supply dropped out (to be confirmed) | See procedure above |
0x40 (64) |
Residual-current device (RCD) dropped out (to be confirmed) | See procedure above |
0x80 (128) |
Temperature out of range (to be confirmed) | See procedure above |
0x100 (256) |
Other, undefined error (to be confirmed) | See procedure above |
0x200 (512) |
One or more configured internal devices are not communicating (to be confirmed) | See procedure above |
0x400 (1024) |
An installed device does not match the configuration (to be confirmed) | See procedure above |
0x800 (2048) |
Wrong device version (firmware or hardware) (to be confirmed) | See procedure above |
0x1000 (4096) |
Protective earth (PE) error (to be confirmed) | See procedure above |
0x2000 (8192) |
Charger miniature circuit breaker (MCB) tripped (to be confirmed) | See procedure above |
0x4000 (16384) |
The charger is offline (to be confirmed) | See procedure above |
Plug level (one plug and all its sockets)
| Code | Meaning | What to do |
|---|---|---|
0x1 (1) |
Invalid configuration | See procedure above |
0x2 (2) |
A charger-level error makes this plug inoperative: check the charger-level code | See procedure above |
0x4 (4) |
User interface error | See procedure above |
0x8 (8) |
Lock error | See procedure above |
0x10 (16) |
Power supply dropped | See procedure above |
0x20 (32) |
RCD tripped | See procedure above |
0x40 (64) |
Contactor failed | See procedure above |
0x80 (128) |
Meter failed | See procedure above |
0x100 (256) |
Emergency stop button pressed | Check whether the emergency stop button has been pressed and release it; see procedure above |
0x200 (512) |
Temperature out of range | See procedure above |
0x400 (1024) |
Communication with the vehicle failed | See procedure above |
0x800 (2048) |
Proximity pin error (Mode 3 / AC) | See procedure above |
0x1000 (4096) |
Other, undefined error | See procedure above |
0x2000 (8192) |
One or more devices of the socket are not communicating | See procedure above |
0x4000 (16384) |
Current consumption exceeded (overcurrent) | See procedure above |
0x8000 (32768) |
MCB tripped | See procedure above |
0x10000 (65536) |
Voltage out of range | See procedure above |
0x20000 (131072) |
All sockets of the plug are in error, plug inoperative: check the socket codes | See procedure above |
0x40000 (262144) |
Tamper error | See procedure above |
Socket level (one socket; the plug may stay available)
| Code | Meaning | What to do |
|---|---|---|
0x1 (1) |
Invalid configuration | See procedure above |
0x2 (2) |
A plug-level error makes this socket inoperative: check the plug code | See procedure above |
0x4 (4) |
User interface error | See procedure above |
0x8 (8) |
Lock error | See procedure above |
0x10 (16) |
Power supply dropped | See procedure above |
0x20 (32) |
RCD tripped | See procedure above |
0x40 (64) |
Contactor failed | See procedure above |
0x80 (128) |
Meter failed | See procedure above |
0x100 (256) |
Emergency stop button pressed | Check whether the emergency stop button has been pressed and release it; see procedure above |
0x200 (512) |
Temperature out of range | See procedure above |
0x400 (1024) |
Communication with the vehicle failed | See procedure above |
0x800 (2048) |
Proximity pin error (Mode 3 / AC) | See procedure above |
0x1000 (4096) |
Other, undefined error | See procedure above |
0x2000 (8192) |
One or more devices of the socket are not communicating | See procedure above |
0x4000 (16384) |
Current consumption exceeded (overcurrent) | See procedure above |
0x8000 (32768) |
MCB tripped | See procedure above |
0x10000 (65536) |
Voltage out of range | See procedure above |
Other models: Raption and eVolve — backend connection messages
Text messages describing a failure of the charger to connect to the OCPP backend (Raption 50 Gen2, eVolve Master, eVolve Smart, Wallbox Smart). The manual does not say where they are displayed; by nature, they never reach the backend. Settings are changed on the charger's setup page (http://<ip>:8080/html/setup.html).
| Message | Meaning | What to do |
|---|---|---|
Connect failed in tcp_connect |
OCPP 1.5: the charger cannot open the TCP connection to the Central System | Check the OCPP URL; check DHCP (Raption, eVolve Master) or the modem APN / static IP (eVolve, Wallbox Smart), then reboot |
bind failed in soap_bind / Error 28 |
OCPP 1.5: the configured OCPP listening port clashes with a port reserved by the unit | Configure another listening port |
Can not get charge device name |
OCPP 1.5: the charger's internal application is corrupted, missing or not installed | Upload the file provided by Circontrol post-sales via the 'Configuration update' page |
Notifying Boot - 200 |
Boot notification not accepted: the Central System does not recognise the charger | Declare the charger in the CSMS; check the Charge Point ID in the OCPP settings |
Notifying Boot - -1 |
Boot notification not delivered completely: a network filter on message size (SIM provider or CSMS) truncates messages | Lower the MTU from 1500 to 1000-1200 bytes (router or SIM provider) |
HTTP/1.1 404 Not Found |
The charger reaches the Central System but the login path is wrong | Review the Central System URL |
SSL/TLS error |
TLS handshake fails on an HTTPS / WSS Central System URL | Upload the correct certificate |
Getting valid public ID timeout |
The charger cannot obtain its public address in time | Check the modem's blocked-IP list; check the Public Address Manager setting and SIM activation with the provider |
No Data, get host by name failed in tcp_connect() |
The charger cannot resolve the Central System host name | Enable DNS protection on the Teltonika router, check DHCP, reboot (Raption, eVolve Master); check the modem APN, or static IP with correct gateway / DNS (eVolve, Wallbox Smart) |
CS Connection FAILED. Fail reason: Underlying Transport Error |
OCPP 1.6: the charger cannot resolve the Central System host name | Check the OCPP URL; same network checks as for the DNS error above |
CS Connection FAILED. Fail reason: Timer Expired |
OCPP 1.6: host name resolved but the Central System cannot be reached | Check DHCP (Raption, eVolve Master) or the modem APN / static IP (eVolve, Wallbox Smart), reboot |
CS Connection FAILED. Fail reason: Invalid HTTP status |
OCPP 1.6: the Central System is reached but rejects the Charge Point ID | Ask the CSMS operator to add the charger; check the Charge Point ID in the OCPP settings |
Lights and display — earlier Wallbox eNext / eNext Elite generation
Red = errors, yellow = temperature. The same error number, its description and its solution are shown in the 'HiCharger' Bluetooth app. Numbering differs from the eNext Park: do not mix the two tables.
| Signal | Meaning | What to do |
|---|---|---|
| 3 red blinks | Low voltage: no voltage detected in the power circuit (also shown after a DC-leak trip once the leak detector has reset, until protections are rearmed) | Make sure all protections are armed |
| 5 red blinks | Electric protection: the unit's electrical protections have tripped | Rearm the protections; contact support if it repeats |
| 6 red blinks | Current leak: a leakage current has been detected (6 mA DC leak detector included) | Unplug the vehicle; on three-phase units, rearm the protections; contact support if it repeats |
| 11 red blinks | Connector lock: the connector locking mechanism failed | Repeat the operation; contact support if it persists |
| 12 red blinks | Welded contact: an internal short-circuit (welded contactor) has been detected; the trip coil opens the protections | Unplug the vehicle, restart the unit and retry; contact support if it persists |
| 14 red blinks | Damaged cable: the cable plugged into the charger is detected as damaged | Try another cable; contact support if it persists |
| 15 red blinks | Negative PWM: the vehicle's response on the pilot signal is invalid | Unplug, wait for green lights, replug; contact support if it persists |
| 16 red blinks | E status: communication error between the vehicle and the charger | Try another cable; contact support if it persists |
| 17 red blinks | D status: the vehicle requests ventilation | Contact technical support |
| 18 red blinks | Maintenance required (relays): some internal components (relays) need maintenance | Contact technical support |
| 7 yellow blinks | High temperature: charger interior too hot to charge | Wait until the temperature returns to normal and retry |
| 8 yellow blinks | Low temperature: charger interior too cold to charge | Wait until the temperature returns to normal and retry |
Sources
- eNext Park & eVolve Smart Series – User Manual (EN) (M460J10-03-25A, 2025-01) — https://circontrol.com/usermanual/manual-enextpark-fr.pdf
- eNext Park eVolve Smart – User manual (FR) (M460J10-02-25A, 2025-03) — https://circontrol.com/usermanual/manual-evolve-enext-fr.pdf
- eNext Park – Installation Manual (v2.2, 2024-06) — https://circontrol.com/usermanual/manual-enextpark-eng.pdf
- Wallbox eNext – User Manual V2 (April 2020 edition, copy hosted by a distributor) — https://cdn.shopify.com/s/files/1/0346/6297/3576/files/E-Next_User_Manual_V2_April_Edition_2020_Manual.pdf
- Wallbox eNext Series – Installation Manual (v3.8, 2021, copy hosted by the distributor ChargeStar) — https://www.chargestar.com.au/wp-content/uploads/2021/09/CC-EN-WB_eNext_Series-Installation_Manual-3.8.pdf
- Raption 50 Gen2 Series – Service Manual, 'Troubleshooting & Errors' chapter (ManualsLib copy) — https://www.manualslib.com/manual/2355133/Circontrol-Raption-50-Gen2-Series.html?page=60
- Raption error decoder tool (Circontrol 'Expert Area', partner access, provided by the post-sales team)
