Skip to main content
Version: 5.32

Servicing & Troubleshooting

1. Diagnosing

Errors can be diagnosed using the LEDs on the user interface (RFID105/110/117) as well as through the Config UI of the Charge Controller.

  1. Log in to the Config UI using the Operator Login Credentials.
  2. Under DOCUMENTATION > Errors you'll find the list of possible Error activation messages.
info

Error activation message is the message that is sent when the error occurred. Error resolution message (if any) is sent when the error is corrected.

2. Logs

Log files serve as the primary data source for network observability, representing computer-generated data files that capture valuable information about usage patterns, activities, and operations within an operating system, application, server, or other networked devices, providing insights into the performance and optimization of resources.

2.1. Settings

The Log Level determines the amount of information provided by the logs.

ScopeLocation in Config UIFieldValueContents
OperatorSystem > GeneralLog Level LOG_LEVEL_DBGrecommended in most cases
LOG_LEVEL_INFOProvides less information thanLOG_LEVEL_DBG

2.2. Log level by component

In addition to the Log Level , you can change the Log Level by component to suit your logging needs. For setting the Log Level by component:

  1. Log in to the Config UI using the Operator Login Credentials
  2. Under SYSTEM > General set the Log Level by component
  3. At the bottom of the Config UI, click , then click to apply the changes

This parameter allows to set different log levels for different software components. The string consists of a comma separated list of component names and component log levels. See the Config UI > DOCUMENTATION page for an extensive list of component names. The possible log level are:

ModeInfo
TRACELog everything
VDBG
DBG
INFO
WARN
ERR
USER_INFO
USER_WARN
USER_ERR

For example, the string to set log level TRACE for the BACKEND component and VDBG for the RCMB component looks like so:

BACKEND=TRACE,RCMB=VDBG
info

Get in touch with your support agent for guidance on your technical errors. The agent will inform you on which logging configuration to set for your case.

2.3. Download logs

ScopeLocation in Config UIFieldValueContents
OperatorDIAGNOSTICS > LogsDownload DiagnosticsDownloadDownloads the logs and setting files as a zip file
Download Diagnostics 2DownloadIf applicable: Downloads the logs and setting files of the Slave Controller as a zip file
caution

This operation may take a few minutes depending on the size of the logs. Don't refresh or leave the page until the download is complete.

2.4. Log encryption

See here.

3. Loggable components

ComponentInternal name (use this when setting the log level)Info
DEFAULT
LOGGING
Dynamic Load ManagementDLM
PIC24For (Mennekes) HMI
SLAC
General Purpose Input OutputGPIO
MONITORING
QCA700X_FLASH
The AC/DC sensitive residual currentmonitoring module RCMB104RCMB
Electrical MeterMETER
METER_EHZ
METER_S0
METER_INTERNAL
METER_MODBUS
SQL
RFID moduleRFID
LOG_FILE
TimeSYSCLOCK
Type 2 Charging Socket StateSOCKETTYPE2
Schuko wallplugSCHUKO
OCPP communicationOCPP
GSM communicationGSM
ISO 15118P15118
Vehicle state (is the car connected?, are the doors closed?, temperature, ...)VEHICLEIF
ASN1
Humidity sensorHUMIDITY_SENSOR
NOR_STORE
ETHREAD
EEVT
MK_PIC24
TIMER_POOL
Component ManagerCOMPONENT_MGR
PlugPLUG
I2C communication (RFID)I2C
Auth input I/O stateAUTH_INPUT
HW_VARIANT_MGR
Legacy Config UIWEB_INTERFACE
Config UIWEB_INTERFACE_NG
STM32_EO
EichrechtEICHRECHT
Home Energy Management SystemHEMS
OCPP BackendBACKEND
ERROR_HANDLING
HMIHMI
Master and Slave informationMASTER_SLAVE
PROTOCOLS
PARAMETERS
WEBDATA
TimeNTP
Modbus relatedMODBUS_RTU
Modbus relatedMODBUS_DEVICE
Time relatedTIMEZONE
Fast Charging through DCCCS_MODE4
USB hotplugging statusUSB_HOTPLUG
USBLIB_MOD
Metering (DC)METER_DC_DZG
HMISTM32_HMI
Master-Slave CommunicationMS_COMM
SU CommunicationSU_COMM
WebSocket ServerWS_SERVER
Energy ManagerENERGY_MAN
ALL