Home / Configurazione tecnica / Charging Station Diagnostics & Maintenance / Manufacturer error codes / Mennekes error codes
Mennekes error codes
Questo articolo non è ancora disponibile in Italiano. Viene mostrata la versione in English.
This page covers MENNEKES AMTRON Professional, AMTRON Charge Control and AMEDIO Professional chargers, fitted with Bender CC612 and ICC1622 charge controllers (firmware 5.x), as well as AMTRON Xtra, Trend and Premium wallboxes (HCC3 controller). It lists the controller's error messages, the messages received from our chargers and how to read the lights.
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 Mennekes reports its errors
Mennekes chargers with a Bender controller (CC612, ICC1622) never send a manufacturer code (vendorErrorCode). The error arrives as text, in the information field, with a standard OCPP code. Example: status Faulted, OCPP code OverCurrentFailure, information "RCD-MCB triggered from unique input".
- So look up the text of the Information column in the tables below. The OCPP code column gives the code the charger actually sends with that message, as received from chargers supervised by Chargekeeper.
- The text can change with the firmware version: the MENNEKES list refers to firmware 5.12.0 and only covers the most common messages.
- The full list, with corrective actions, is on each charger: web interface, 'Documentation' > 'Errors Documentation' (operator login). Active errors are shown under 'State' > 'Errors list', or remotely with GetConfiguration, keys
ErrorsListandEventsList. - Not every text is a fault: "Authorization failed." arrives with OCPP code
NoError, it is a refused badge.
AMTRON Professional and AMTRON Charge Control (Bender CC612 / ICC1622 controllers) — messages sent to the backend
| Message | Meaning | What to do | OCPP code |
|---|---|---|---|
RCD-MCB triggered from unique input |
The monitoring input wired to the phase-sequence relay, RCD or circuit breaker reports an abnormal state: no supply voltage, anti-clockwise rotating field, under- or over-voltage, lost phase, loose terminal or broken wire, RCD or breaker tripped, faulty controller input | Re-arm the RCD or breaker with the multi-function button if the charger has one; have a qualified electrician check the supply and the phase rotation; if it persists, contact MENNEKES support (controller replacement) | OverCurrentFailure |
Contactor welded |
The contactor's auxiliary (mirror) contact feedback does not match what the controller commands: the contactor may be stuck closed | Power the charger off for 3 minutes and restart it; if it persists, call in a qualified electrician (check or replace the contactor, auxiliary contact or controller) | PowerSwitchFailure |
Housing temperature approaching limit - charging current reduced |
Inside temperature between 50 °C and 55 °C: the charger lowers the charging current | Let the charger cool down; if it recurs, check sun exposure and ventilation | OtherError |
Housing temperature too high - charging paused |
Inside temperature above 55 °C: charging is paused until it cools down | Let the charger cool down; if it appears at normal temperature, suspect the temperature sensor and escalate to support | HighTemperature |
Possible CP and PR wiring issue |
The controller suspects a wiring problem on the Control Pilot / Proximity lines: faulty charging cable or CP and PR wired incorrectly | Try another charging cable; have a qualified electrician check the CP/PR wiring | — |
Vehicle signals error |
The vehicle reports an error (IEC 61851 state E) or no valid cable is detected (CP line short-circuited, invalid CP signal, PP resistance not detected) | Unplug and retry, try another cable or another vehicle; run a function test with the MENNEKES test box; if only one vehicle is affected, refer the driver to a garage | EVCommunicationError |
State D detected, charging is paused |
The vehicle requests state D (charging with ventilation), which the charger does not accept, or the CP signal level is out of range | Check the cable and connectors; have a qualified electrician measure the CP signal (12 V DC in state A); if it persists with several vehicles, escalate to support (controller replacement) | — |
RFID reader not communicating |
The controller has lost contact with the RFID reader (loose or faulty connection) | Restart the charger; have a qualified electrician check the connection between the controller and the RFID reader | ReaderFailure |
Residual current detected via sensor |
The built-in residual current sensor measured a leakage current, on the vehicle side or in the installation, and stopped the charge | Unplug: the protection resets when the plug is removed, or by itself after about 15 minutes; if it recurs, have a qualified electrician check the current transformer and its connection | GroundFailure |
The current transformer has a defect |
The residual current measuring transformer appears faulty, or its connection to the controller is bad | Have a qualified electrician check the connection between the controller and the transformer; contact MENNEKES support | — |
Diagnostic failed |
The diagnostics file requested by the backend could not be uploaded (backend connection, SIM card, mobile reception) | Check the backend connection and the upload URL; check the SIM card and mobile signal; retry GetDiagnostics | — |
Signal Weak |
The connection to the backend is weak or missing (mobile reception, SIM card, backend unreachable) | Check the SIM card and mobile signal (antenna); check the backend connection | — |
Not all DLM Slaves connected |
The dynamic load management (DLM) master cannot reach every slave charger: network disruption between them | Check the local network and cabling between the chargers; check that each slave is powered and online | — |
FW Update in progress |
A firmware update is running | Wait for the update to complete | — |
Firmware update failed |
The firmware update could not be carried out (download or installation failure) | Download the firmware again; restart the update | — |
Bender controllers — internal error states
Internal identifiers of the Bender firmware (ERR_*), read through the controller's Modbus TCP API (registers 105 to 112, 'Error Codes 1-4'). Chargekeeper does not receive these identifiers: it receives the message text. This table is useful when an installer reads the controller over Modbus.
| Code | Meaning | What to do | OCPP code |
|---|---|---|---|
ERR_RCMB_TRIGGERED |
Residual current seen by the built-in sensor (mask 0x01) | See "Residual current detected via sensor" | — |
ERR_VEHICLE_STATE_E |
The vehicle reports an error state (mask 0x02) | See "Vehicle signals error" | — |
ERR_MODE3_DIODE_CHECK |
The vehicle diode check on the CP line failed, treated as possible tampering (mask 0x04) | Try another cable or vehicle; escalate to support if all vehicles are affected | — |
ERR_MCB_TYPE2_TRIGGERED |
The circuit breaker of the Type 2 outlet has tripped (mask 0x08) | Re-arm the breaker; call in a qualified electrician if it trips again | — |
ERR_MCB_SCHUKO_TRIGGERED |
The circuit breaker of the domestic (Schuko) outlet has tripped (mask 0x10) | Re-arm the breaker; call in a qualified electrician if it trips again | — |
ERR_RCD_TRIGGERED |
The residual current device has tripped (mask 0x20) | Re-arm the RCD (multi-function button on AMTRON variants with a built-in RCD); call in a qualified electrician if it trips again | — |
ERR_CONTACTOR_WELD |
Contactor detected as welded (mask 0x40) | See "Contactor welded" | — |
ERR_BACKEND_DISCONNECTED |
No connection to the OCPP backend (mask 0x80) | Check the network or SIM card, and the OCPP URL | — |
ERR_ACTUATOR_LOCKING_FAILED |
The plug could not be locked in the socket: plug not fully inserted, foreign object or faulty actuator (mask 0x100) | Re-insert the plug fully and retry; escalate to support if repeated | — |
ERR_ACTUATOR_LOCKING_WITHOUT_PLUG_FAILED |
Locking test without a plug inserted failed (mask 0x200) | Restart the charger; escalate to support if it persists | — |
ERR_ACTUATOR_STUCK |
The locking actuator is stuck and cannot release the plug (mask 0x400) | Try UnlockConnector remotely; otherwise, manual emergency unlock by a qualified electrician (AMTRON Professional manual, § 9.3) | — |
ERR_ACTUATOR_DETECTION_FAILED |
The controller cannot detect the locking actuator, disconnected or faulty (mask 0x800) | Escalate to support: the 'Redetect actuator' function on the manufacturer tab is for the manufacturer or installer | — |
ERR_FW_UPDATE_RUNNING |
Firmware update in progress (mask 0x1000) | Wait | — |
ERR_TILT |
The charger is tilted: knocked over or mounted out of level (mask 0x2000) | Inspect the charger on site for impact damage | — |
ERR_WRONG_CP_PR_WIRING |
Wiring problem suspected on the CP / PR lines (mask 0x4000) | See "Possible CP and PR wiring issue" | — |
ERR_TYPE2_OVERLOAD_THR_2 |
The vehicle draws more current than allowed; charging stopped (mask 0x8000) | Retry; if it repeats with one vehicle, refer the driver to a garage | — |
ERR_ACTUATOR_UNLOCKED_WHILE_CHARGING |
The plug lock opened during charging (mask 0x10000). Received by the backend as the text "Actuator unlocked while charging" | Escalate to support | ConnectorLockFailure |
ERR_TILT_PREVENT_CHARGING_UNTIL_REBOOT |
The charger was tilted and stays blocked until it is rebooted (mask 0x20000) | Inspect the charger on site, then reboot it | — |
ERR_PIC24 |
Fault of the controller's PIC24 co-processor (mask 0x40000) | Restart the charger; escalate to MENNEKES support | — |
ERR_USB_STICK_HANDLING |
A USB stick is being processed (configuration, field engineer) (mask 0x80000) | Wait for completion and remove the stick | — |
ERR_INCORRECT_PHASE_INSTALLATION |
Wrong phase rotation detected (anti-clockwise rotating field) (mask 0x100000) | Have a qualified electrician correct the phase order | — |
ERR_NO_POWER |
No mains voltage detected: supply cut or upstream protection tripped (mask 0x200000) | Check the upstream breakers and the supply | — |
ERR_METER_SECOND_NOT_COMMUNICATING |
The second energy meter does not respond (mask 0x400000) | Restart the charger; escalate to support | — |
ERR_MONITORING_RELAY_INPUT_TRIGGERED |
The combined RCD/MCB monitoring input has triggered (mask 0x800000) | See "RCD-MCB triggered from unique input" | — |
ERR_STATE_D |
Charging paused because the vehicle signals state D (mask 0x1000000) | See "State D detected, charging is paused" | — |
DC_ERR_DOOR_OPEN |
Door of a DC wallbox is open, DC products only (mask 0x2000000) | Close the door | — |
ERR_RCD_MAYBE_TRIGGERED |
RCD probably tripped, deduced from the loss of power on the primary meter (mask 0x4000000) | Check and re-arm the RCD | — |
Bender controllers — events
One-off events of the Bender firmware (ERR_EVENT_*: failed update, unintended reset, authorization failure…), read through the Modbus TCP API (registers 158 to 165, 'Error Events 1-4'). They are not persistent states.
| Code | Meaning | What to do |
|---|---|---|
ERR_EVENT_REBOOT_IN_PROGRESS |
A reboot of the charger was requested (mask 0x04) | — |
ERR_EVENT_AUTHORIZATION_FAILED |
An authorization attempt was rejected: unknown or blocked badge (mask 0x08). Received by the backend as the text "Authorization failed." with OCPP code NoError: an event, not a fault | Check the badge in Chargekeeper |
ERR_EVENT_AUTHORIZATION_FAILED_NO_STATUSNOTIF |
Authorization rejected locally, without notifying the OCPP backend (mask 0x10) | Check the local authorization list and settings |
ERR_EVENT_FW_UPDATE_FAILURE |
Firmware update failed, possibly for lack of internet connection (mask 0x40) | Retry the update |
ERR_EVENT_FW_UPDATE_PACKAGE_MANAGER_FAULT |
Firmware update refused by the package manager: incompatible or invalid package (mask 0x100) | Check that the firmware file matches the controller; escalate to support |
ERR_EVENT_MONITORING_UNINTENDED_RESET |
Unexpected restart, probably a power cut (mask 0x200) | Check supply stability if it repeats |
ERR_EVENT_TRANSACTION_STOPPED_AFTER_RESET |
A charging session was closed implicitly because the charger rebooted during it (mask 0x400) | Check the end of the session in Chargekeeper |
ERR_EVENT_SLAVE_DISCONNECTED |
A slave charger lost its link to the master (mask 0x800) | Check the master–slave cabling or network |
ERR_EVENT_DIAGNOSTICS_FAILURE |
Diagnostics upload failed, possibly for lack of internet connection (mask 0x1000) | See "Diagnostic failed" |
ERR_EVENT_RCMB_ERROR |
Error of the residual current monitoring module (mask 0x2000) | Escalate to support |
ERR_EVENT_15118_COMMUNICATION_FAILURE |
The ISO 15118 TCP/TLS link with the vehicle failed (mask 0x8000) | Retry; fall back to RFID or app authorization |
ERR_EVENT_15118_AUTHORIZATION_FAILURE |
Plug & Charge authorization failed: signature check rejected (mask 0x10000) | Check the Plug & Charge certificates |
ERR_EVENT_15118_AUTHENTICATION_FAILURE |
Plug & Charge authentication failed (mask 0x20000) | Check the Plug & Charge certificates |
ERR_EVENT_15118_CERT_INSTALLATION_FAILURE |
Installing an ISO 15118 certificate failed (mask 0x40000) | Retry; check the certificate infrastructure (PKI) setup |
ERR_EVENT_15118_DEPARTURE_TIME |
The vehicle sent a departure time over ISO 15118 (mask 0x80000) | — |
ERR_EVENT_15118_EAMOUNT |
The vehicle sent a requested energy amount over ISO 15118 (mask 0x100000) | — |
ERR_EVENT_15118_V2G_SEQUENCE_TIMEOUT |
The ISO 15118 message sequence timed out (mask 0x200000) | Retry the session |
ERR_EVENT_15118_V2G_SEQUENCE_ERROR |
ISO 15118 message sequence error (mask 0x400000) | Retry the session |
ERR_EVENT_15118_DC_CABLE_CHECK |
DC cable check error: vehicle not in state C/D; DC products only (mask 0x800000) | — |
ERR_EVENT_15118_DC_POWER_STOP |
DC power stop error: vehicle not in state B; DC products only (mask 0x1000000) | — |
ERR_EVENT_15118_DC_ISOLATION_FAULT |
DC cable insulation fault; DC products only (mask 0x2000000) | Escalate to support |
ERR_EVENT_15118_DC_UNEXPECTED_CP_STATE |
Unexpected CP state during a DC session; DC products only (mask 0x4000000) | — |
ERR_EVENT_15118_DC_EVSE_INITIATED_SHUTDOWN |
Normal shutdown initiated by the charger (mask 0x8000000) | — |
ERR_EVENT_GENERIC_INFORM |
Generic informational event (mask 0x10000000) | — |
ERR_EVENT_IDTAG_ADDED_OK |
A badge was added to the local authorization list (mask 0x20000000) | — |
ERR_EVENT_IDTAG_ADDED_FAILURE |
Adding a badge to the local authorization list failed (mask 0x40000000) | Retry adding the badge |
ERR_EVENT_SYSTEM_NOT_READY |
The system has not finished starting (mask 0x80000000) | Wait for start-up to complete |
Codes received from our chargers, not documented by Mennekes
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.
On Mennekes chargers, the code is the text itself, sent in the information field.
| Code | Label sent by the charger | OCPP code |
|---|---|---|
| (text) | "Performing periodical housekeeping reboot" | OtherError |
| (text) | "Unintended Reset - Power Outage?" | ResetFailure |
| (text) | "Plug locking failed" | ConnectorLockFailure |
| (text) | "Car current is 10% more than expected." | OtherError |
| (text) | "OCPP meter not communicating" | PowerMeterFailure |
| (text) | "eth interface had 5 link up-down sequences." | WeakSignal |
| (text) | "Failed init: Tilt sensor" | OtherError |
| (text) | "External meter not communicating" | PowerMeterFailure |
| (text) | "eth interface had 6 link up-down sequences." | WeakSignal |
| (text) | "DLM Slave disconnected and not charging" | OtherError |
| (text) | "Terminated transaction after reset! Power Outage?" | ResetFailure |
| (text) | "eth interface had 7 link up-down sequences." | WeakSignal |
| (text) | "Type 2 actuator stuck, cannot unlock" | ConnectorLockFailure |
| (text) | "Car current overload, charging stopped." | OtherError |
| (text) | "eth interface had 8 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 45 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 69 link up-down sequences." | WeakSignal |
| (text) | "Contactor not closed" | UnderVoltage |
| (text) | "eth interface had 9 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 89 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 91 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 114 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 88 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 42 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 64 link up-down sequences." | WeakSignal |
| (text) | "Relay temperature too high - charging current(...)" | OtherError |
| (text) | "eth interface had 68 link up-down sequences." | WeakSignal |
| (text) | "eth interface had 116 link up-down sequences." | WeakSignal |
Other models: AMTRON Xtra, Trend and Premium (HCC3 controller)
Numbered codes shown in the service interface ('Production settings' > 'HCC3 error code') and in the MENNEKES Charge APP ('Configure Wallbox' > 'Wallbox information' > 'Current error code'); the red 'Error' light is lit or flashing. The MENNEKES document does not say whether these codes reach an OCPP backend.
| Code | Meaning | What to do |
|---|---|---|
10 |
Installation fault: supply / phase-sequence monitoring does not report the expected state (no supply, wrong rotating field, under-voltage, lost phase, loose terminal or broken wire, RCD or breaker tripped, faulty controller input) | Acknowledge with the multi-function button; have a qualified electrician check the supply; escalate to support (controller replacement) |
11 |
Controller fault | Power the charger off for 3 minutes and restart it; escalate to support (controller replacement) |
12 |
Misconfiguration: state D vehicle refused, CP out of range, or external temperature sensor faulty or missing | Run a function test with the MENNEKES test box; check the configuration in the service interface; check cables and connectors |
13 |
Overtemperature: housing above 60 °C (or faulty temperature sensor) | Let the charger cool down |
14 |
Inconsistent feedback from the contactor's auxiliary (mirror) contact (loose terminal, broken wire, sticking contactor, faulty controller input) | Power the charger off for 3 minutes and restart it; have a qualified electrician check the contactor and its auxiliary contact |
15 |
Device time invalid: the system clock must be synchronised (first start-up or power cut longer than 4 hours) | Connect with the MENNEKES Charge APP (automatic sync) or set the time in the service interface |
16 |
Connection error with the Home Manager (energy manager): the two devices are not on the same network | Check both configurations and the network layout |
30 |
Device start-up failed | Power the charger off for 3 minutes and restart it |
31 |
Internal self-test not passed (locking actuator blocked or faulty, loose cables or connectors, badly inserted charging cable) | Check that the actuator locks and unlocks fully; escalate to support (actuator replacement) |
32 |
No connection between the HMI board and the controller | Have a qualified electrician check this connection |
50 |
The charging plug could not be locked: badly plugged cable or foreign object in the socket | Insert the plug fully; check for foreign objects |
51 |
Wrong cable: its cross-section does not match the current configured on the charger | Use a suitable cable |
52 |
Faulty cable or invalid CP/PP signals (CP in D, E or out of range, CP/PP miswired, CP short-circuit, PP resistance not detected) | Try another cable; have a qualified electrician measure the CP signal (12 V DC in state A) |
100 |
No communication with the ACU (SCU mode only): RS-485 link down, or HCC3 not in SCU mode or not registered in the ACU | Check SCU mode and the ACU configuration ('Search SCU'); check the RS-485 bus; power the charger off for 3 minutes and restart it |
101 |
Charger not polled by the ACU (SCU mode only) | Same as code 100 |
102 |
Charger in maintenance mode (SCU mode only) | Check 'SCU-Setup' > 'Setup' > 'Test' in the ACU |
103 |
Charging point disabled in the ACU (SCU mode only) | Untick 'SCU Unavailable' in the ACU web interface |
255 |
Unknown error | Power the charger off for 3 minutes and restart it |
Lights and display
| Signal | Meaning | What to do |
|---|---|---|
| CC612 controller 'Alarm' LED red (inside the housing) | Controller system error: steady red (standard firmware) or fast-blinking red (Eichrecht firmware) | Read the 'Errors list' in the web interface, or the ErrorsList key with GetConfiguration over OCPP |
| Red 'Fault' symbol, steady or flashing, on the AMTRON LED panel | An error prevents charging: wrong or faulty cable, RCD or breaker tripped (variants with built-in protection), anti-clockwise rotating field, controller connectors not fully inserted | Stop the session, unplug, check the cable, replug and retry; re-arm the RCD or breaker with the multi-function button; read the error message in the web interface; contact the service partner if it persists |
Sources
- Troubleshooting – AMTRON Professional (error messages and solution approaches) (v01, 2022-12-13, firmware 5.12.0) — https://www.mennekes.org/fileadmin/MEN-Deutschland/emobility/01_documents/04_installer/Troubleshooting_AMTRON_Professional_v01_2022-12-13_en.pdf
- Troubleshooting – AMTRON Xtra, Trend, Premium (with HCC3) (v01, 2022-12-13) — https://mennekes.org/fileadmin/MEN-Deutschland/emobility/01_documents/04_installer/Troubleshooting_AMTRON_HCC3_v01_2022-12-13_en.pdf
- AMTRON Professional(+) (E) 7.4 / 22 (PnC) – Operating and installation manual (1028500DS-5 v00, 2022-09) — https://www.MENNEKES.de/fileadmin/MEN-Deutschland/emobility/04_software/03_amtron_professional/1028500DS-5_BA-IA_AMTRON_Professional____E_7_4-22_PnC__v00_2022-09-01.pdf
- AMTRON Charge Control – Betriebs- und Installationsanleitung (1038400DS-1 v00, 2022-02, copy hosted by a distributor) — https://memodo.de/mwdownloads/42773e399440537db425a7c9820ee211
- Bender CC612 charge controller – Manual (CC612(4G)_D00325_07_M_XXEN/10.2022) — https://www.bender.de/fileadmin/content/Products/m/e/CC612(4G)_D00325_M_XXEN.pdf
- Bender Controller Software Docs – Modbus TCP API (v5.38.2) — https://www.bender.de/docs/charge-controller/APIs/Modbus-API/
- Bender Controller Software Docs – Servicing & Troubleshooting (v5.38.2) — https://www.bender.de/docs/charge-controller/Servicing-and-Troubleshooting/
- Bender Controller Software Docs – OCPP parameter reference table (v5.38.2) — https://www.bender.de/docs/charge-controller/OCPP/Reference/ocpp-parameter-table/
- Bender Controller Software Docs – REST API reference (v5.38.2) — https://www.bender.de/docs/charge-controller/APIs/REST-API/rest-api-reference/
- Bender Controller Software Docs – CC612 LED indicators (v5.38.2) — https://www.bender.de/docs/charge-controller/LED-Signals/charge-controller/cc612/
- Bender Controller Software Docs – ICC13xx/ICC1624 LED indicators (v5.38.2) — https://www.bender.de/docs/charge-controller/LED-Signals/charge-controller/icc/
- Web interface of each charger, 'Documentation' > 'Errors Documentation' (operator login)
