OCPP In-Depth Guide

The Charge Controller family implements the OCPP standard based on the official OCPP 1.6 standard defined by the Open Charge Alliance. Download relevant documents from the Open Charge Alliance website.

• OCPP 1.6
• OCA ISO 15118 (scroll down to "Application Notes")
• Secure transfer of the Eichrecht OCPP public key via hastobe spec
• EVSE Check V3

1. Setting up the connection and verifying it

1. Basic Requirements

   • Valid ChargePointID (found under BACKEND > OCPP)
   • Working network connection (GSM, Ethernet, or WLAN)
   • OCPP backend URL (format: ws://backend:8080/OCPPJProxy/v16/)

2. Connection Verification

   • Check BACKEND > Connection Status
   • Verify heartbeat messages are being sent/received
   • Confirm transaction messages are flowing

2. Troubleshooting guide

2.1. Common connection issues

1. No Backend Connection

   • Check network connectivity (ping test)
   • Verify ChargePointID is correct
   • Confirm backend URL format
   • Check SSL certificates if using WSS

2. Connection Drops

   • Check network stability
   • Verify heartbeat interval settings
   • Monitor system logs for timeout errors

3. Authentication Failures

   • Verify basic auth credentials
   • Check authorization key format
   • Confirm OCPP version compatibility

2.2. Diagnostic Steps

1. Check real-time logs:

   • DIAGNOSTICS > OCPP Status
   • DIAGNOSTICS > System Logs

2. Verify network settings:

   • BACKEND > Connection Type
   • NETWORK > Configuration

3. Test backend communication:

   • Initiate test transaction
   • Monitor message exchange
   • Check error responses

3. Supported feature profiles

Feature profile	Features	Compliance	Info
The Charge Controller family provides mature support for the OCPP 1.6 protocol.
Some specifications leave room for propietary implementations. Where this is the case, details are outlined.

Feature profile	Features	Compliance	Info
Core	Authorize BootNotification ChangeAvailability ChangeConfiguration ClearCache DataTransfer GetConfiguration Heartbeat MeterValues RemoteStartTransaction RemoteStopTransaction Reset StartTransaction StatusNotification StopTransaction UnlockConnector	compliant	Basic Charge Station functionality comparable with OCPP 1.5 without support for firmware updates, local authorization list management and reservations.
Firmware Management	GetDiagnostics DiagnosticsStatusNotification FirmwareStatusNotification UpdateFirmware	compliant	Support for firmware update management and diagnostic log file download
Local Auth List Management	GetLocalListVersion SendLocalList	compliant	Features to manage the local authorization list in Charge Stations
Reservation	CancelReservation ReserveNow	compliant	Support for reservation of a Charge Station
Smart Charging	ClearChargingProfile GetCompositeSchedule SetChargingProfile	compliant	Support for basic Smart Charging, for instance using control pilot
Remote Trigger	TriggerMessage	compliant (proprietary implementation)	Support for remote triggering of Charge Station messages
Firmware Management	GetDiagnostics DiagnosticsStatusNotification FirmwareStatusNotification UpdateFirmware	compliant	Support for firmware update management and diagnostic log file download
Local Auth List Management	GetLocalListVersion SendLocalList	compliant	Features to manage the local authorization list in Charge Stations
Reservation	CancelReservation ReserveNow	compliant	Support for reservation of a Charge Station
Smart Charging	ClearChargingProfile GetCompositeSchedule SetChargingProfile	compliant	Support for basic Smart Charging, for instance using control pilot
Remote Trigger	TriggerMessage	compliant (proprietary implementation)	Support for remote triggering of Charge Station messages

4. Supported messages based on "Open Charge Point Protocol 1.6"

Message	"Open Charge Point Protocol 1.6" (edition 2 FINAL, 2017-09-28) chapter numbers
Authorize	Ch. 6.1 — 6.2
BootNotification	Ch. 6.3 — 6.4
CancelReservation	Ch. 6.5 — 6.6
ChangeAvailability	Ch. 6.7 — 6.8
ChangeConfiguration	Ch. 6.9 — 6.10
ClearCache	Ch. 6.11 — 6.12
ClearChargingProfile	Ch. 6.13 — 6.14
DataTransfer	Ch. 6.15 — 6.16
DiagnosticsStatusNotification	Ch. 6.17 — 6.18
FirmwareStatusNotification	Ch. 6.19 — 6.20
GetCompositeSchedule	Ch. 6.21 — 6.22
GetConfiguration	Ch. 6.23 — 6.24
GetDiagnostics	Ch. 6.25 — 6.26
GetLocalListVersion	Ch. 6.27 — 6.28
Heartbeat	Ch. 6.29 — 6.30
MeterValues	Ch. 6.31 — 6.32
RemoteStartTransaction	Ch. 6.33 — 6.34
RemoteStopTransaction	Ch. 6.35 — 6.36
ReserveNow	Ch. 6.37 — 6.38
Reset	Ch. 6.39 — 6.40
SendLocalList	Ch. 6.41 — 6.42
SetChargingProfile	Ch. 6.43 — 6.44
StartTransaction	Ch. 6.45 — 6.46
StatusNotification	Ch. 6.47 — 6.48
StopTransaction	Ch. 6.49 — 6.50
TriggerMessage	Ch. 6.51 — 6.52
UnlockConnector	Ch. 6.53 — 6.54
UpdateFirmware	Ch. 6.55 — 6.56

5. Supported messages based on "Using ISO 15118 Plug & Charge with OCPP 1.6"

Request message	"Using ISO 15118 Plug & Charge with OCPP 1.6" (v1.0, 2020-09-16) chapter numbers
Authorize	Ch. 6.1.1 — 6.1.2
CertificateSigned	Ch. 6.2.1 — 6.2.2
DeleteCertificate	Ch. 6.3.1 — 6.3.2
Get15118EVCertificate	Ch. 6.4.1 — 6.4.2
GetCertificateStatus	Ch. 6.5.1 — 6.5.2
GetInstalledCertificateIds	Ch. 6.6.1 — 6.6.2
InstallCertificate	Ch. 6.7.1 — 6.7.2
SignCertificate	Ch. 6.8.1 — 6.8.2
TriggerMessage	Ch. 6.9.1 — 6.9.2

6. List of all configuration keys and equivalent Config UI labels

OCPP key	Master-Slave scope	Reboot needed?	Info	Standard OCPP parameter?	Config UI label
RCMBDelta	Both	No	Minimum residual current change (in tenth of a milliamp) for which an OCPP status notification is sent to the backend. A value of 0 disables notifications.	No	RCMB Delta
RCMBIEC62955Mode	Individual	No	Configures the RCMB to comply with IEC62955 or IEC62752. Important note: If set to 'IEC62955 (locked)', the option 'IEC62752' will be permanently disabled and cannot be selected anymore from then on!	Yes	N/A
RCMB_STATE	Individual	No	RDC-M (RCMB) protection state\nMaximum values of last transaction\nCurrent values	No	N/A
RCMBTransactionMaxRMS	Individual	No	Largest RMS value measured while a transaction was in progress	No	Maximum RMS value of last transaction
RCMBTransactionMaxDC	Individual	No	Largest DC value measured while a transaction was in progress	No	Maximum DC value of last transaction
WeldCheck	Individual	No	Welded contactor detection. For the '230V input' with and without PE check options (if available) L1 must be connected before the contactor. In these two cases weld check is only done when the car is disconnected and not immediately on opening the contactor.	Yes	Welded contactor detection
WeldCheckInType	Individual	No	Whether the welding detection input circuit is normally closed or normally open.	Yes	Welded contactor input type
ChargePointVendor	Both	No	Mandatory, identifies the vendor of the ChargePoint.	Yes	ChargePoint Vendor
ChargePointModel	Not relevant	No	Mandatory, identifies the model of the ChargePoint. Please note that this must not match a different model of the generation of charge controllers.	Yes	ChargePoint Model
SSHAccessUsb	Individual	No	Disables SSH access to the controller via USB.	Yes	SSH Access via USB
SSHAccessWlanNetwork	Individual	No	Disables SSH access to the controller via WLAN.	Yes	SSH Access via WLAN
SSHAccessEth	Individual	No	Disables SSH access to the controller via Ethernet.	Yes	SSH Access via Ethernet
SSHAccessGsm	Individual	No	Disables SSH access to the controller via GSM.	Yes	SSH Access via GSM
InvalidRFIDFilter	Both	No	Set whether RFID tags with invalid UIDs shall be filtered out and thus not reported by the reader.	Yes	Filter Out Invalid RFIDs
RFIDEnable	Individual	No	Enables or disables the RFID reader. Allows preventing error messages if no reader is installed.	No	N/A
EnforcePwdChange	Both	No	Force change of default operator password on login.	No	Enforce Password change
EnforceStrongLoginPwds	Both	No	Force selecting a strong secure login password when changing the operator password, the installer password, or the user password.	No	Enforce strong login passwords
RFIDMode	Both	No	This parameter determines whether the RFID reader shall just be able to read RFID cards or also shall support NFC communication. If set to 'RFID only' only RFID cards can be read. If set to 'RFID/NFC hybrid' NFC communication is supported and RFID cards can be read.	Yes	RFID Mode
EnforceMasterRFID	Both	No	When changing the default operator password the setting of RFID token(s) is forced that reset the system to its operator default settings if presented for 120 seconds.	No	Enforce Master RFID
EnforceSecureRFID	Both	No	This parameter determines whether all RFID cards are accepted to start charging (off) or if only secure RFID token compliant with VDE-AR-E 2532-100 will be accepted (on).	No	Enforce using Secure RFID
ChargeBoxSerialNumber	Individual	No	Overrides the serial number of the charge controller manufacturer. Named 'ChargeBOXSerialNumber' in OCPP BootNotification. Note: It can only be set once if the value is empty! This precondition is met for re-flashed charge controllers.	Yes	Controller serial number
ChargePointSerialNumber	Master	No	Set by the charge point manufacturer, not by the controller manufacturer. Sent as 'ChargePointSerialNumber' in OCPP BootNotification. If not set, the OCPP message value is replaced by the 'ChargeBoxIdentity' value.	Yes	Manufacturer serial number
MasterRFIDtoReboot	Individual	No	RFID tag to reboot the system if presented for 30 seconds. Disable this feature by leaving this parameter empty.	No	N/A
UserInstallerPasswordCheck	Master	No		No	N/A
MasterRFIDstoReset	Individual	No	RFID tokens that reset the system to its operator default settings if presented for 120 seconds. Up to 2 (colon separated) tokens can be defined. To disable this feature leave the input field empty.	No	Factory Reset by RFID
SSHClientKey	Master	No	Key for authorizing the user 'root' of the ChargePoint to connect to server via SSH. This authorization can then be used to establish reverse tunnels using customer-specific scripts.	No	N/A
ErrorsList	Individual	No	List of errors currently present in the ChargePoint.	No	N/A
ErrorResolution	Individual	No	List of error resolutions currently present in the ChargePoint.	No	N/A
EventsList	Individual	No	List of the last events and errors with their timestamp.	No	N/A
OPKGInstallExtraOption	Both	No		No	N/A
AuthorizationInputMode	Not relevant	No	Set if the authorization input can just start or it can both start and stop a transaction. Note that Scheidt&Bachmann requires this to be set to Only start.	Yes	Authorization Input Mode
AuthorizationInputType	Not relevant	No	Set if the authorization input switch is normally open or normally closed. Note that Scheidt&Bachmann requires this to be set to Normally open.	Yes	Authorization Input Switch Type
loglevel	Both	No	Level for the logging system. For security reasons you may be asked to re-enter your credentials to download the log.	No	Log Level
loglevelcomponents	Both	No	This parameter allows to set different log levels for different software components. The string entered consists of a comma-separated list of component names and component log levels. A full list of component names is available in the Documentation view. The possible log levels are: TRACE, 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 log level VDBG for the RCMB component is: BACKEND=TRACE,RCMB=VDBG	No	N/A
GiroEEnable	Individual	No	Enables or disables the GiroCard payment via Giro-e over OCPP. Requires a Giro-e capable OCPP backend.	No	N/A
PowerLineVoltage	Individual	No	Single phase RMS voltage of the power source feeding the ChargePoint in Volts. This is used for current calculation from power values from meter.	Yes	Power source voltage
MasterSlaveMode	Not relevant	No	'Master' controller handles the backend connection and may start and stop transaction for its slave. 'Slave' controller connects to a master as its backend. Some other parameters are automatically adjusted when turning this on. IMPORTANT NOTE: supported is a setup with 1 master and 1 slave.	Yes	Master/Slave Mode
LedType	Not relevant	No	Type of LED device connected to the ChargePoint (if any).	No	LED Type
DualLedMode	Not relevant	No	Behavior for dual LED boards. When set to 'On', the dual LED board shows independent states of master and slave for the left and right LEDs. 'On Inverted' is the same as 'On' but with master showing slave state and vice versa. When set to 'Off', LEDs operate in clone mode: the left and the right LEDs show the same pattern and colors, presenting the state of the main/master device.	No	Dual LED board mode
DisplayType	Not relevant	No	Type of display connected to the ChargePoint (if any).	No	Type of Display
DisplayMode	Not relevant	No	Controls the display mode. When set to 'Master/Slave', the display shows independent states for master and slave. When set to 'Main (Master)' the display only presents the state of the main/master device.	No	Mode for Display
DisplayContentSelectorTime	Not relevant	No	If enabled the display shows charging time information.	No	Display charging time
DisplayContentSelectorEnergy	Not relevant	No	If enabled the display shows charging energy information.	No	Display energy
DisplayContentSelectorPower	Not relevant	No	If enabled the display shows charging power information.	No	Display power
PatternOnRelayK2	Not relevant	No	Behavior for the relay 2 (K2), to be used for an external indicator light such as an LED or blinking light. Use option 'On while vehicle connected' for integration with parking management system by Scheidt&Bachmann. To use two contactors in series that are to be controlled separately use option 'On while charging'.	No	HMI Pattern On Relay 2 (K2)
DisplayLanguage	Individual	No	The language of display texts on the LCD display, if available. Only has an effect if a LCD is configured.	No	Language of Display
EichrechtState	Individual	No	Eichrecht State	No	N/A
OCPPSchuko	Not relevant	No	Use auxiliary input/output to support additional Schuko Socket	Yes	Schuko Socket
EOActuatorType	Not relevant	No	Configure the connected actuator type	Yes	Actuator type
Type2ContactorLifetime	Individual	No	Maximum number of operating cycles the contactor should be allowed to perform until a replacement is necessary.	Yes	Type 2 Contactor Lifetime
Type2PlugLifetime	Individual	No	The maximum number of times the plug of the type2 socket can be plugged in safely..	Yes	Type 2 Plug Lifetime
SetType2PlugCycles	Individual	No	Use this field when the type2 socket is replaced and the counter for socket cycles must be reset to 0 for a new socket or to a number greater than 0 for a used one.	No	Set type 2 plug cycles to
Type2PlugCounter	Not relevant	No	Number of times the plug of the type2 socket was plugged in.	No	N/A
SetTypeContactorCycles	Individual	No	Use this field when the contactor is replaced and the counter for contactor cycles must be reset to 0 for a new contactor or to a number greater than 0 for a used one.	No	Set type 2 contactor cycles to
ContactorCyclesType2	Individual	No	The number of times the contactor of the type 2 socket was switching on and off.	No	N/A
ThresholdContactorCurrentUnderLoad	Individual	No	Set threshold contactor current under load (in Amperes)	Yes	Threshold Contactor Current Under Load [A]
ContactorCyclesUnderloadLimit	Individual	No	The maximum number of contactor cycles under load before receiving a system warning	Yes	Contactor Cycles Under Load Limit
SetCountContactorCyclesType2UnderLoad	Individual	No	Use this field when the contactor under load is replaced and the counter for contactor cycles must be reset to 0 for a new contactor or to a number greater than 0 for a used one.	No	Set contactor cycles under load to
GetCountContactorCyclesType2UnderLoad	Individual	No	The number of times the contactor was switching on and off under load.	No	Number of contactor cycles under load
CableAttached	Not relevant	No	Setting this to on indicates that the charger has a fixed cable attached and does NOT need to lock a cable in a socket. ATTENTION: This is safety relevant!	Yes	Fixed cable attached
CPDiodeDetection	Individual	No	Set this value to 'On' if you want to check before charging if the diode connected to the control pilot line is connected or not.	No	Detect Control Pilot Diode
LockIfAuthorized	Both	No	If 'On' is selected the socket type 2 actuator is locked only after successful authorization, otherwise already on plug-in.	No	Lock Actuator only if authorized
LockPermanently	Individual	No	If 'On' is selected the type 2 socket locking mechanism stays locked permanently once a charging cable is inserted.	No	Permanently locked cable
PauseChargingStateD	Both	No	If set to On, charging transactions are paused in case State D is detected. While state D is detected an error is reported to the user.	No	Pause/prevent charging in state D
AdcCpCalibrationCfg	Individual	No	This parameter allows to enable the ADC calibration for the control pilot line's states detection. Once calibrated, it is possible to trigger a re-calibration. Note that changes of this parameter require a reboot to take effect.	Yes	ADC calibration for CP line
CheckCarOverCurrentStopLimit	Individual	No	When the charging current reported by the OCPP meter exceeds the signaled current by this percentage, charging will be stopped.	Yes	Stop limit in (%) for 'Check for car overload'
SocketType2State	Individual	No	State of TYPE2 socket at connector 1.	No	N/A
SignaledCurrentLimit	Individual	No	Current (in Ampere) that is signaled to the vehicle via PWM.	No	N/A
HardwareCurrentLimit	Individual	No	Maximum current (in Amperes) the charge point hardware can support	Yes	Maximum Current [A]
OperatorCurrentLimit	Individual	No	Maximum current (in Amperes) that can be signaled to the vehicle for charging. If the parameter 'Installation Current Limit' exists, the 'Operator Current Limit' must be below or equal to the 'Installation Current Limit'. Otherwise, it must be below or equal to the 'Maximum Current'. It can be freely configured, even while charging. This parameter can be changed by the backend for energy management	No	Operator Current Limit [A]
FreeCharging	Both	No	Allows charging without authorization via RFID or the backend. Charging is started immediately after a vehicle is connected.	No	Free Charging
CheckCarOverCurrent	Both	No	If set to On the current consumed by the vehicle will be checked against the signaled current. If the overload is above 10% the signaled current will be decreased by 10%. If the overload is above the configured percentage limit the charging will be stopped.	No	Check for car overload
RandomRestartAfterPowerLoss	Both	No	If this feature is enabled, the restart of charging will be randomized after a power loss. In case of many chargepoints connected to the same power line, this feature avoids a high peak of energy consumption in short period of time, which can result in another blackout.	Yes	Randomize charging after power loss
PDL_Power	Master	No	PDL Power	No	PDL Power
EnergyManInputPowerLimitCfg	Individual	No	Enables energy Management from external input	Yes	Energy management from external input
ChargingScheduleAllowedChargingRateUnit	Master	Yes	List of supported quantities for use in a ChargingSchedule.	No	N/A
PhasesConnected	Individual	No	Shows how the number of phases connected to the ChargePoint is configured.	No	N/A
ASKIoverOCPPAllowedIP	Both	No	Configure a single IP address here that will be allowed to access the 'ASKI over OCPP-S' service. An empty field will allow no access!	Yes	N/A
ConnectorPhaseRotation	Both	Yes		No	N/A
ConnectorPhaseRotationIT	Individual	No		No	N/A
ConnectorSwitch3to1PhaseSupported	Master	Yes	If set the ChargePoint supports switching between 3 and 1 phases during a charging session.	Yes	N/A
SmartChargingUseDisconnectedLimit	Individual	Yes	If enabled and the ChargePoint gets disconnected from the Backend, the 'Disconnected Upper Limit [A] for SmartCharging' will be applied despite the limitations set in stored charging profiles.	Yes	N/A
ASKIoverOCPP	Master	No	Enable or disable support for receiving OCPP 1.5 SOAP 'Change Configuration Requests' for the LaMa parameter 'LaMa_ConnectionRate'. The SOAP server will listen on TCP port 13000 for connector 1. 'LaMa_ConnectionRate' can be changed in 10th of Amps.	Yes	N/A
EnergyManInputPowerCurrentLim	Individual	No	Single phase RMS current limit (in A) for energy management from external input. Range: from 6 A to 80 A. Set to 0 A to pause charging.	Yes	Current limit for energy management from external input
LaMa_ConnectionRate	Individual	No	Secret key for Mennekes EnergyManager Input	No	N/A
ConnectorPhaseRotationMaxLength	Individual	Yes	Maximum number of items in a ConnectorPhaseRotation Configuration Key.	No	N/A
ChargeProfileMaxStackLevel	Master	Yes	Max StackLevel of a ChargingProfile.	No	N/A
ChargingScheduleMaxPeriods	Master	Yes	Maximum number of periods that may be defined per ChargingSchedule.	No	N/A
MaxChargingProfilesInstalled	Master	Yes	Maximum number of Charging profiles installed at a time.	No	N/A
SmartChargingDisconnectedLimit	Individual	No	Disconnected Upper Limit applied to SmartCharging in case the ChargePoint is disconnected from the backend.	Yes	N/A
RCDRESET	Individual	No	RCD Reset	No	N/A
RCDAUTORECLOSURE	Both	No	Allows to enable the automatic reclosure of the RCD. The auxiliary relay output (on CC612: C3/4, on ICC1324: 23/24) or a dedicated output on ICC1612 is used.	Yes	RCD Auto Reclosure
RCDENABLE	Both	No	Allows to enable RCD detection. It must be Off when there is no RCD connected to the controller. If there is an opto input, it could be used (e. g. C6/5 on CC612). On ICC1324 a lost communication with primary meter because of its power loss could be used.	Yes	RCD Enable
SPDCFG	Individual	No	Allows support for Surge Protection Devices (SPD). It must be 'Off' when there is no SPD connected to the controller.	Yes	SPD Config
VentHeatingCtrlMode	Both	No	This parameter allows to enable the activation of an external fan or heater according to the housing temperature or vehicle state.	Yes	Fan or heater control configuration
WeldCheckAuxRelay	Both	No	When enabled, the auxiliary relay will be activated whenever the contactor is welded. If enabled on CC1612 the RCD test pin is not used but instead the selected Ex out output.	No	Weld check output
MonitoringRelayInput	Individual	No	Use a unique input from a monitoring relay to trigger RCD/MCB.	Yes	N/A
RCDAUTORECLOSUREDELAY	Both	No	RCD auto reclosure delay in seconds.	Yes	RCD auto reclosure delay
RCDAUTORECLOSUREATTEMPTS	Both	No	RCD auto reclosure attempts.	Yes	RCD auto reclosure attempts
VentHeatingHyst	Both	No	This delta in degree (Celsius) allows to add hysteresis to the fan or heater control. In order to switch off the fan/heater the temperature must be below/above the configured temperature threshold plus/minus this delta.	Yes	Fan or heater control hysteresis configuration
VentHeatingTempThr	Both	No	Temperature threshold necessary to start or stop the fan or heater.	Yes	Temperature threshold for fan or heater control
AmbientCpuDelta	Individual	No	Temperature delta for measurements from temperature sensor. This value should be tuned according to the thermal characteristics of the charging station.	No	Charging Station temperature delta
LocalScheduledReboots	Both	No	The local time of day used for house keeping reboots. The charge controller reboots after 30 days to ensure uninterrupted operation. Reboots only occur with no vehicle connected and no customer present. Select a full hour in the range 0 to 23.	Yes	Local time for housekeeping reboot
DaysScheduledReboots	Both	No	Number of days that is used for house keeping reboots. The charge controller reboots after the number of days to ensure uninterrupted operation. Reboots only occur with no vehicle connected and no customer present. Select a number in range [1..99].	No	Number of days for housekeeping reboot
ReducedCurrent	Individual	No	Charging current value in Ampere when temperature is above temperature threshold 1.	No	Charging current to reduce temperature [A]
ReducedCurrentPct	Individual	No	How much (in %) of signaled current should be applied to reduce temperature when temperature is above temperature threshold 1.	No	Charging current (in % of signaled current) to reduce temperature
TempDelta	Master	No	Temperature change in degrees Celsius for which a new temperature measurement report is sent to the backend system. A value of 0 switches the reporting off.	No	Temperature Report Delta
TempStopThreshold2	Individual	No	Temperature threshold necessary to stop charging.	No	Temperature threshold 2
TempReduceThreshold1	Individual	No	Temperature threshold necessary to start decreasing the current.	No	Temperature threshold 1
MaxTimePerSession	Both	No	Time limit (in h) set by the operator	No	N/A
InputOutputBackendControlledMode	Both	No	Inputs (InputOptoC65 and InputOptoC87 on CC612 or InputOpto1 and InputOpto2 on others) and output (Output1, and if present, Output2) can be controlled via a backend.	Yes	Backend controlled mode for inputs and outputs
InputChangeNotifyBackend	Both	No	Changes on inputs 1 and 2 will issue a status notification message to backend limited to not more then one message every 10 sec. Requires 'Backend controlled mode for inputs and outputs' set to 'On'.	No	Backend notification for input changes
TamperDetectionInputEnable	Individual	No	When enabled, the individual charge controller informs the backend with a status notification that the tamper detection sensor has been triggered.	Yes	Tamper detection sensor enable
DataTransferTariffUsage	Both	No	Enables the DataTransfer messages that allow to show Tariff and Total Usage Information. Beware this feature only works with backend systems that support it. If the backend system does not support it, this will prevent all authorizations from being successful.	No	DataTransfer for Tariff And Total Usage
AuthorizeRemoteTxRequests	Both	Yes	This parameter determines whether a remote request to start a transaction in the form of a RemoteStartTransaction.req message should be authorized beforehand like a local action to start a transaction. Some backends require this as OCPP specification is not clear about this. Other backends are not working if this is parameter is enabled.	Yes	Send Authorize for RemoteStart
AllowOfflineTxForUnknownId	Both	Yes	This parameter determines whether a client is allowed to charge in case its authorization cannot be processed because the backend is offline or not reachable. If set to 'On', the client is allowed to charge even if it cannot get authenticated from the ocpp whitelist nor from local whitelist. If set to ImmediatelyWhenPlugged, then charging will be allowed in case ChargePoint is offline by just plugging the car and without RFID authorization. If 'Connection Type' is 'No Backend' then this parameter is ignored.	No	If in doubt allow charging
InfoStatusNotifications	Both	No	This parameter determines whether OCPP status notifications that are meant just for informative purposes (such as a temperature report) should be sent to the backend system or not.	No	Send informative StatusNotifications
ErrorStatusNotifications	Both	No	This parameter determines whether OCPP status notifications that are meant to report and error (such as when the plug locking system is broken) should be sent to the backend system or not.	Yes	Send error StatusNotifications
UsbErrorStatusNotifications	Individual	No	This parameter determines whether USB communication errors between master and slave are reported to backend.	Yes	Send USB error StatusNotifications
StatusNotificationStrategy	Both	No	This parameter determines on which conditions the ChargePoint changes into the OCCUPIED state. In 'Occupied on Charging' occupied is signaled only when authorization is there and a cable is plugged in. In 'Occupied on 'Authorized/Plugged' the state changes to occupied already when the charger is authorized with nothing connected or when a cable/vehicle is connected but no authorization has taken place yet.	Yes	Strategy for StatusNotification state transitions
DisplayDisconnectAsError	Master	No	Parameter that determines whether an error is signaled to the user when the backend connection is interrupted.	Yes	Display backend disconnect as error
AuthorizationCacheEnabled	Master	Yes	Enables the use of the internal whitelist for storing RFID UID from the OCPP backend. If disabled, RFIDs even if reported from the backend with an expiry date are not added to an internal cache.	No	Enable OCPP whitelist
idTagLetterCase	Both	No	Parameter that makes the RFID tag management configurable to upper or lower case.	Yes	RFID Tag letter case
StopTransactionOnEVSideDisconnect	Both	Yes	When set to 'On' the Charge Point will stop a transaction when the cable is unplugged from the EV.	No	Stop Transaction On EV Side Disconnect
UnlockConnectorOnEVSideDisconnect	Both	Yes	When set to 'On' the Charge Point will unlock the cable on Charge Point side when the cable is unplugged at the EV.	No	Unlock Connector On EV Side Disconnect
ReserveConnectorZeroSupported	Master	Yes	If set to 'On' the ChargePoint supports reservations on connector 0.	No	N/A
FreeChargingMode	Both	No	Sets the OCPP behavior in free charging mode. Note that in case of a master/slave scenario the slave will be automatically configured to the same mode as used for the master.	Yes	Free Charging Mode
AllowLongOcppGetConfKeys	Both	No	Allows OCPP keys in get configuration command to be longer than 500 characters.	Yes	Allow long get configuration keys
OcppGetConfBoolIsInt	Both	No	If activated, boolean OCPP keys are returned as integer values '0' or '1' in command 'GetConfiguration'. This is for compatibility. If not activated, boolean OCPP keys are returned as boolean values 'false' or 'true' in command 'GetConfiguration' according to the OCPP standard. The command 'ChangeConfiguration' accepts both types simultaneously.	No	Integer values for boolean get configuration keys
StopTransactionOnInvalidId	Individual	Yes	Determines if the ChargePoint will stop an ongoing transaction when it receives a non-Accepted authorization status in a StartTransaction response.	No	Stop Transaction on invalid ID
ChargeBoxIdentity	Individual	No	ID that is sent to the backend and used by the backend to identify the ChargePoint.	Yes	OCPP ChargeBoxIdentity (ChargePointID)
FirmwareVersion	Individual	No	Firmware version running on the ChargePoint.	No	N/A
RCMBVersion	Individual	No	Version of the RCMB module connected to the ChargePoint.	No	N/A
SupportedFeatureProfiles	Master	Yes	List of supported Feature Profiles. Possible profile identifiers: Core, FirmwareManagement, LocalAuthListManagement, Reservation, SmartCharging and RemoteTrigger.	No	N/A
RfidTagFreeCharging	Individual	No	RFID Tag for Free Charging with OCPP Full, fixed RFID modes. Note that this RFID Tag is also used when 'If in doubt allow charging' is 'ImmediatelyWhenPlugged'	Yes	RFID Tag for Free Charging with OCPP Full, fixed RFID modes
BackendConnectionTimeout	Master	No	The time in seconds that is used for establishing an APN connection, establishing a Proxy or establishing a backend connection before a timeout will be recognized. Also determines the time period that is waited for answers from the backend for OCPP requests. Only reduce this value to a smaller value if you can assure a stable network connection. Increase the value to a larger value in case of bad network coverage. Increasing the value will result in longer user interaction delays.	Yes	Backend connection timeout
ConnectionTimeOut	Both	Yes	Interval (from successful authorization) until incipient charging session is automatically canceled due to failure of the EV user to correctly insert the charging cable connector(s) into the appropriate connector(s).	Yes	Vehicle connection timeout [s]
NumberOfConnectors	Master	Yes	Number of physical charging connectors of this Charge Point.	No	N/A
GetConfigurationMaxKeys	Master	Yes	Maximum number of requested configuration keys in a GetConfiguration.req PDU.	No	N/A
TransactionMessageAttempts	Individual	Yes	Sets how often the ChargePoint tries to submit a transaction-related message when the backend fails to process it. 0 means infinite attempts.	Yes	Number of transaction message attempts
EichrechtTransactionMessageAttempts	Individual	No	Sets how often the ChargePoint tries to submit an Eichrecht transaction-related message when the backend fails to process it. 0 means infinite attempts. -1 means that the value of the OCPP-key \"TransactionMessageAttempts\" should be used.	Yes	Number of Eichrecht transaction message attempts
TransactionMessageRetryInterval	Individual	Yes	Sets how long the ChargePoint will wait before resubmitting a transaction-related message that the backend failed to process.	Yes	Transaction message retry interval (seconds)
ResetRetries	Individual	Yes	Number of times to retry an unsuccessful reset of the ChargePoint.	Yes	Number of reset retries
OcppQueueFullAsErrorState	Both	No	When set, a full OCPP message queue will cause an error state. Charging will be terminated.	Yes	Disallow charging if OCPP queue full
LocalPreAuthorize	Master	Yes	Sets if the Charge Point, when online, will start transactions for locally authorized identifiers without requesting an Authorize.conf from the Central System.	No	Local Pre Authorize
LocalAuthorizeOffline	Master	Yes	Sets if the Charge Point, when offline, will start transactions for locally authorized identifiers.	No	Local Authorize Offline
ForceHeartbeatRequestMessages	Not relevant	No	Sets if the Charge Point should send OCPP Heartbeat request messages despite other messages being sent.	Yes	Force Heartbeat request messages
RetransmitMeterValues	Both	No	If enabled, MeterValue messages are retransmitted on errors.	No	Retransmit MeterValues
UPnPUUID	Individual	No	The UPnP UUID that this ChargePoint uses when announcing its presence on the local network. Only used if connected to a local network.	Yes	ChargePoint UPnP UUID
HeartbeatInterval	Master	Yes	The interval in seconds with which OCPP heartbeat messages are sent to the backend system. Modifying this parameter may upset the backend system (OCPP 1.6).	No	Heartbeat interval (OCPP 1.6)
StopTransactionModeUnplug	Both	No	This allows to modify the behavior of the charger at the end of a transaction. Normal unlocks and stops the transaction, when the plug is removed from the vehicle or the RFID used for authorization is used again. Stop after unplugging causes a transaction to be fully stopped only when the cable is pulled from the socket of the charging station. Only by RFID/Remote Stop only unlocks if RFID or a backend message is used for stopping the transaction. Pulling the cable out of the car will not end the transaction.	Yes	Stop Transaction Mode
SupportedFileTransferProtocols	Master	Yes	List of supported file transfer protocols: FTP, FTPS, SCP, HTTP and HTTPS	No	N/A
USBFieldEngineer	Both	No	Allow getting diagnostics and configuration of the ChargePoint via USB stick.	Yes	USB Field Engineer
USBConfigUpdate	Both	No	Allow update of the charge point configuration via USB stick.	Yes	USB Config update
USBFirmwareUpdate	Both	No	Allow update of the charge point firmware via USB stick.	Yes	USB Firmware update
LocalAuthListEnabled	Master	Yes	Selects if the Local Authorization List is enabled	No	N/A
LocalAuthListMaxLength	Master	Yes	Maximum number of identifications that can be stored in the Local Authorization List	No	N/A
SendLocalListMaxLength	Master	Yes	Maximum number of identifications that can be send in a single SendLocalList.req	No	N/A
fll	Master	No	Local whitelist of RFIDs independent of a backend connection.	No	Enable local whitelist
fllUseOcppStartStop	Both	No	Send OCPP Start/Stop transaction for authorizations from the local white list.	No	Send OCPP Start/Stop transaction
ConnectionType	Master	No	The type of data connection used to connect to the backend system. Choose 'No Backend' to disable backend communication completely. While using GSM the wallbox can be connected to LAN/WLAN at the same time.	Yes	Connection Type
DataConsumption	Master	No	Data Consumption (in bytes) for the running month.	No	Data Consumption
DataConsumptionLastMonth	Master	No	Data Consumption (in bytes) for the previous month.	No	Data Consumption Last Month
InterfacesList	Master	No	List of interfaces and their IPs	No	N/A
APN	Master	No	Access Point Name of the mobile network to be used when establishing connections to the backend system via the built-in modem.	Yes	Access Point Name (APN)
ModemNetworkSelMode	Master	No	In 'Automatic' mode the modem chooses the operator. In 'Manual' mode the operator specified in requested operator name is used. In 'Manual/Auto' mode the automatic mode is used if manual selection fails.	Yes	Network selection mode
ModemNetworkType	Master	No	The technology to be used to access the network 2G (GSM), 3G (UTRAN) or 4G (LTE). In auto mode the modem will choose the technology.	Yes	Modem Access Technology
ModemNetworkOperFmt	Master	No	Indicates if the operator name format is alphanumeric or numeric. Long alphanumeric format can be up to 16 characters and short format up to 8 characters (refer to GSM MoU SE.13).	Yes	Network operator name format
ScanNetworkOperators	Master	No	Determines whether a search for available network operators is carried out upon boot. Set the 'Scan network operators at boot' parameter to 'On', then click on 'Save & Restart'. After boot the state page will show all the available operator names. The value is automatically set to 'Off' again after boot.	Yes	Scan network operators at boot
APNUsername	Master	No	Username to be used for authenticating with the Access Point of the mobile network for connecting with the backend system.	Yes	APN Username
APNPassword	Master	No	Password to be used for authenticating with the Access Point of the mobile network for connecting with the backend system.	Yes	APN Password
Req3GNetworkOperator	Master	No	The name of the network operator to be used in manual 'Network selection mode'.	Yes	Requested Network operator
SIMPIN	Master	No	PIN number that should be used to unlock the SIM card. This number is only used if the SIM card requires a PIN number.	Yes	N/A
LASTWRONGSIMPIN	Master	No	The wrong PIN number that was used last time.	Yes	N/A
GSMPPPMTU	Master	No	Maximum transmission unit size for GSM connections (in bytes)(valid value range: 68 - 1492).	Yes	N/A
ModemNetworkState	Master	No	The current network registration mode of the modem which informs about the technology (2G, 3G, 4G) and about the registration (home network, roaming...)	No	N/A
OperatorSelectionMode	Master	No	Operator Selection Mode, Auto or Manual...	No	N/A
GSMState	Master	No	Registration state to the mobile network.	No	N/A
IMSI	Master	No	International Mobile Subscriber Identity (IMSI), a value associated with the SIM card inserted into the built-in modem. If this number is properly read the SIM card is inserted correctly and can be read by the built-in modem.	No	N/A
IMEI	Master	No	International Mobile Equipment Identification (IMEI). A number associated with the hardware of the built-in modem. If this number is present this device has a built-in modem and can properly communicate with the modem.	No	N/A
ICCID	Master	No	Integrated Circuit Card Identifier (ICCID) of the SIM card inserted into the built-in modem.	No	N/A
LAI	Master	No	Location Area Identity (LAI), composed of Mobile Country Code (MCC), Mobile Network Code (MNC) and Location Area Code (LAC).	No	N/A
Used3GNetworkOperator	Master	No	Name of the network operator the built-in modem is currently connected to.	No	N/A
AvailableNetworks	Master	No	List of network operators that are available and visible using the currently selected antenna. This value is only properly filled if requested via the 'Scan network operators at boot' configuration parameter.	No	N/A
MODEMNETSTATE	Master	No	Show at which state in the connection sequence the modem is currently operating. Show OK when connected. Additionally, APN session duration and traffic are shown.	No	N/A
ModemInfo	Master	No	Shows the modem manufacturer, model and firmware revision.	No	N/A
ModemAccessTechnology	Master	No	Shows which access technology (2G, 3G, 4G) the modem is currently using.	No	N/A
ModemLastConnError	Master	No	Reason for the last modem APN connection failure	No	N/A
RSSI	Master	No	Received Signal Strength Indicator as reported by the modem. This parameter is an indication how well the built-in modem can receive signals from the base station.	No	Received Signal Strength Indicator (RSSI)
MCC	Master	No	Mobile Country Code as determined from the SIM card. This tells you which country your SIM card comes from.	No	N/A
MNC	Master	No	Mobile Network Code as determined from the SIM card. This tells you which mobile network operator your SIM card comes from.	No	N/A
LAC	Master	No	Location Area Code as reported by the built-in modem, this value can be used to determine the location of the ChargePoint.	No	N/A
CellID	Master	No	Cell ID as reported by the built-in modem, this value can be used to determine the location of the ChargePoint more accurately.	No	N/A
GSMStateInfo	Master	No	Status of the GSM connection such as APN name, network type (LTE, EDGE), frequency/band (e.g. band 7, band 20), signal strength (RSSI) and signal quality (SINR).	No	N/A
NetworkConfigMode	Master	No	Mode for ethernet configuration to be used for the ChargePoint. 'Auto' uses DHCP to configure the ChargePoint's ethernet connection; 'Static' uses the addresses as filled in static network configuration IP; 'DHCP server' assigns a predefined DHCP configuration to other DHCP clients in the same network (range 172.16.23.100-172.16.23.254]; netmask 255.255.255.0; gateway 172.16.23.1; DNS 172.16.23.1). The DHCP server's own IP is 172.16.23.1. Any static network configuration is ignored in case of DHCP server mode. Please consider to switch the 'WAN router' on if the DHCP server is enabled.	Yes	Mode for ethernet configuration
StaticNetworkConfigAddress	Master	No	Static LAN IP of the ChargePoint.	Yes	Static network configuration IP
StaticNetworkConfigNetmask	Master	No	Netmask to use for the LAN of the ChargePoint.	Yes	Static network configuration netmask
StaticNetworkConfigDNS	Master	No	DNS server to use for the LAN of the ChargePoint.	Yes	Static network configuration DNS
SSLModeClient	Master	No	Allows to set how strict SSL authentication is, from no authentication (encryption only) to full authentication.	Yes	SSL Strictness as client
WANRouter	Master	No	Enables access from LAN interfaces to the selected WAN (GSM/Ethernet/WLAN) interface. This will also enable the DNS forwarder.	Yes	WAN router
OCPPMode	Master	No	This parameter determines whether backend communication is done using the standard OCPP JSON variant or the proprietary Binary OCPP variant of Ebee Smart Technologies. The Binary OCPP variant is working across NAT networks and therefore does not require a private APN for remote messages to arrive at the charge point. Also Binary OCPP uses much less data (factor 20 to 50) than standard OCPP. Binary OCPP however requires a Binary OCPP proxy on the backend side.	Yes	OCPP Mode
ConnSettingsFallback	Individual	No	Restores last good connection settings when failed to reconnect to the backend after a reboot.	Yes	Connection settings fallback
HostnameBinaryOCPP	Master	No	The DNS hostname or IP address of the binary ocpp proxy server for the backend system. This parameter is only used if Binary OCPP is selected for the TCP/IP mode.	Yes	Hostname (Binary OCPP)
OCPPBackendJSONURL	Master	No	The WS/WSS URL of the OCPP backend system. This URL must be the WS/JSON endpoint and begin with \"ws://\" or \"wss://\". This parameter is only used if OCPP-J 1.6 or OCPP-J 2.0 mode is used. The ChargePoint's ID gets automatically appended when connecting to the backend.	Yes	WebSockets JSON OCPP URL of the Backend
WebsocketsProxyURL	Master	No	Specify the websockets proxy to connect to in the format HOST:PORT, whereby PORT is optional and set to 80 when not specified.	Yes	Websockets proxy
HTTPBasicAuthPassword	Master	No	The password to be used for HTTP Basic Authorization. If left empty, HTTP Basic Authorization is not used.	Yes	HTTP Basic Authentication password
OcppCertificate	Master	No	Certificate used for SSL connections to the backend.	No	Certificate (OCPP)
OcppCSR	Master	No	Certificate signing request (for OCPP) in PEM format that corresponds to the private key this charge point generated upon provisioning.	No	Certificate signing request (OCPP)
OcppUserCaCertificate	Master	No	User CA Certificate (OCPP).	No	User CA Certificate (OCPP)
NetworkConfigHostname	Master	No	Network hostname used for DHCP and mDNS.	Yes	Client hostname
StaticNetworkConfigGateway	Master	No	Gateway to use for the LAN of the ChargePoint.	Yes	Static network configuration gateway
PortBinaryOCPP	Master	No	TCP port of the proxy server for binary OCPP communication with the backend.	Yes	Port number (Binary OCPP)
RegenerateOcppCertAndKey	Master	No	Trigger Regeneration of Private Key and Self Signed Certificate for OCPP.	No	N/A
TcpWatchdogTimeout	Individual	No	This is the time in seconds in which the connection to the backend can be not working until the system reboots. Set it to 0 to disable rebooting.	Yes	TCP Watchdog Timeout
NetworkConfigDHCPRetries	Master	No	DHCP request number of retries before giving up.	Yes	DHCP client request retries
NetworkConfigDHCPTimeout	Master	No	DHCP request timeout in seconds.	Yes	DHCP client request timeout
NetworkConfigDHCPDelay	Master	No	DHCP request delay between multiple requests in seconds.	Yes	DHCP client request delay
WebSocketPingInterval	Master	Yes	WebSockets keep-alive interval in seconds or 0 when unused. Using keep-alive on WebSockets layer is especially useful when using a NAT router between ChargePoint and backend. The ping-pong being sent prevents the NAT router from closing the websockets connection.	No	WebSockets keep-alive interval
OcppConStrictTls	Master	No	If 'All ciphers' is selected, all recent TLS versions will be accepted. For 'Only secure ciphers' any OCPP connection will be forced to connect only via TLS 1.2 or higher and secure ciphers. Lower versions or weak ciphers will be refused. This is the most secure option currently.	Yes	OCPP connection strictness
WLANSSID	Master	No	SSID of the WLAN the ChargePoint tries to connect to.	No	WLAN SSID
WLANPassword	Master	No	Password of the WLAN the ChargePoint connectsto. The Chargepoint automatically chooses thecorrect encryption method of the WLAN.	No	WLAN password
WLANStaticNetworkConfigAddress	Master	No	Static WLAN IP of the ChargePoint.	Yes	N/A
WLANStaticNetworkConfigNetmask	Master	No	Netmask to use for the WLAN of the ChargePoint.	Yes	N/A
WLANStaticNetworkConfigGateway	Master	No	Gateway to use for the WLAN of the ChargePoint.	Yes	N/A
WLANStaticNetworkConfigDNS	Master	No	DNS server to use for the WLAN of the ChargePoint.	Yes	N/A
WLANEnabled	Master	No	Enable or disable WLAN.	No	WLAN enabled
WLANNetworkConfigMode	Master	No	Network configuration mode for the ChargePoint's WLAN connection. Set to 'Auto' to use DHCP to configure the WLAN network connection automatically. Use 'Static' to use a static IP address to be configured below (as well as a netmask, gateway, and DNS server).	Yes	Mode for WLAN configuration
WLANNetworkConfigDHCPRetries	Master	No	Number of DHCP requests sent before giving up on the DHCP server.	No	N/A
WLANNetworkConfigDHCPTimeout	Master	No	DHCP request timeout in seconds.	No	N/A
WLANNetworkConfigDHCPDelay	Master	No	DHCP request delay (in seconds) between multiple requests .	No	N/A
TcpdumpInterface	Individual	No	The type of interface we want to dump packet data into file. Choose 'Any' to listen on any network interface.	No	Tcpdump Interface
Tcpdump	Individual	No	Switch 'tcpdump' on or off for dumping packets data at the configured interface into the log file 'packets.pcap0'. Note: 'tcpdump' will log 20 MB data at most and switch off on its own. The log data file may be retrieved via the 'Download Log Files' function. A running 'tcpdump' will be stopped before.	No	Start and stop 'tcpdump' run
Config15118	Both	No	High Level (15118 protocol) Power Line Communication configuration. If set to 'Off' 15118 communication is disabled. If set to 'On (with PlugNCharge)' 15118 communication is enabled and plug and charge is supported. If set to 'On (no PlugNCharge)' 15118 communication is enabled but plug and charge is not supported.	Yes	15118 Configuration
SeccCertExpireDate15118	Individual	No	Supply Equipment Charge Controller Certificate expiry date. This is the expiry date of the certificate for the secure TLS communication with the car via power line communication (15118 protocol).	No	SECC Certificate Expiry Date (15118 protocol)
Log15118	Both	No	Enable the creation of the '15118_log.csv' file with the input and output exi stream messages.	Yes	Extra logging
MACEVCCIDPrefix	Both	No	This prefix will be inserted in the EV's MAC address when used as authorization ID against the backend or local whitelist for autocharge.	Yes	EVCCID or EV's MAC address prefix for OCPP authorization
EVMACAddr	Individual	No	EV's MAC address.	No	EV's MAC address
autochargeid	Both	No	This ID will be used for authorization in case the EV failed to communicate with the EVSE or does not support autocharge.	Yes	Autocharge fixed ID
Autocharge	Both	No	Autocharge is an experimental and non-standard feature. Some vehicles may not work or show a charging error. The feature is improved continuously both on EVSE and EV side. Check if software updates are available to make use of improvements. If set to 'On (Fixed ID)' an autorization request will be done for the configured autocharge fixed ID in case the EV failed to communicate with the EVSE or does not support autocharge.	Yes	Autocharge
DepartureTime	Individual	No	Used to indicate when the vehicle intends to finish the charging process.	No	N/A
EAmount	Individual	No	Amount of energy reflecting the EV's estimate of how much energy is needed to fulfill the user configured charging goal for the current charging session. This might include energy for other purposes than solely charging the HV battery of an EV.	No	N/A
EVSEMaxCur	Individual	No	Value sent to the EV on Charging Status messages during the charging loop.	No	N/A
V2GEvseCertConfig	Both	No	This option allows to specify the fields of a subject name to be used for the generation of the Leaf certificate's CSR and therefore for the corresponding signed certificate.	Yes	N/A
SeccLeafSubjectCommonName	Both	No	(Comma separated) Common Name(s) of the SECC (EVSE) leaf certificate(s). The CN must be a SECCID. The field can contain optional multiple SECCIDs if necessary.	No	N/A
SeccLeafSubjectCountry	Both	No	Country of the SECC (EVSE) leaf certificate. Indicates in which country the CPO operates. Example: DE	No	N/A
SeccLeafSubjectOrganization	Both	No	Organization of the SECC (EVSE) leaf certificate. Indicates which CPO operates this EVSE. Example: Hubject GmbH	No	N/A
ConnectorEvseIds	Both	No	Comma separated EVSEIDs for OCPP connectors starting with connector 1 in one string.	Yes	N/A
CertificateStoreMaxLength	Both	Yes	Maximum number of Root/CA certificates that can be installed in the Charge Point.	Yes	N/A
CentralContractValidationAllowed	Both	Yes	If this variable is true, then the contract certificate and chain will be sent to the server for validation and authorization. Otherwise, the certificate will be validated by the Charge Point and only the certificate's OCSP information will be sent to the server.	Yes	N/A
ContractValidationOffline	Both	Yes	If this variable is true, then the Charge Point will try to validate a contract certificate when it is offline.	Yes	N/A
ISO15118PnCEnabled	Both	Yes	If this variable set to true, then the Charge Point supports ISO 15118 plug and charge messages via the DataTransfer mechanism as described in the OCA OCPP 1.6 extension document.	Yes	N/A
P15118ConStrictTls	Master	No	If 'Standard' is selected, any 15118 connection will be forced to connect only via TLS 1.2 or higher and secure ciphers according standard. Lower versions or weak ciphers will be refused. This is the most secure option currently. For 'All ciphers' all recent TLS versions and ciphers will be accepted. This should be used only to solve compatibility issues.	Yes	15118 connection strictness
P15118EVSlacReqTimeout	Both	No	This time indicates how long the EVSE should signal 5% to wait for EV SLAC requests. When this timeout expires, it is assumed the EV does not support 15118 nor autocharge and nominal PWM is signaled if already authorized. This parameter is relevant only if 15118 or Autocharge are enabled.	Yes	15118 EV detection timeout [s]
OCPPMeterType	Individual	No	Type of meter used for the charging socket and its connector. This is relevant for OCPP transactions. For Modbus/RTU meters the address must be 1.	Yes	Configuration
SecondMeterType	Master	No	Energy Management: the type of second meter used only for input to manage the current on the grid. For Modbus/RTU meters the address must be 2.	Yes	Meter configuration (Second)
OCPPViaLocalNetwork	Both	No	If 'On' is selected, the minimum value of parameter 'Meter Value Sample Interval (OCPP)' is reduced from '10' to '1'.	No	OCPP Via Local Network minimum value '1'
MeterValueSampleInterval	Both	Yes	Interval in seconds after which a new meter value is sent to the backend system during a charging transaction. Set 0 to turn off or to a value greater than or equal to 10 to turn on.	No	Meter Value Sample Interval (OCPP)
MeterValueSampleMode	Both	No	According to the mode, meter values are sent under specific circumstances. 'WholeTransaction': only while transaction is active. 'ContactorClosed': only when contactor is closed.'CurrentFlowOnly': only when current is flowing to vehicle.	No	Meter Value Sample Mode (OCPP)
ClockAlignedDataInterval	Both	Yes	Interval in seconds after which a new meter value is sent to the backend system regardless of whether a charging transaction is ongoing or not. The sending of these values is aligned with the full hour. Set it to 0 to turn off or a value of 10 or greater to turn on.	Yes	Clock aligned data interval (OCPP)
ClockAlignedMeterRandomSendDelay	Both	No	The sending of the clock aligned values are delayed for a random time between 0 and the configured value. In case of large number of chargers, this can prevent backend problems on handling many messages at the same time.	Yes	Clock aligned random sent delay in seconds (OCPP)
MeterValuesAlignedData	Both	Yes	Comma-separated list of types of meter values that should be sent as clock aligned data elements in separate meter values messages. Supported are: 'Energy.Active.Import.Register', 'Power.Active.Import', 'Current.Import', 'Current.Offered', 'Voltage', 'Soc', 'Frequency', and 'Temperature'.	No	Meter values aligned data (OCPP)
MeterValuesSampledData	Both	Yes	Comma-separated list of types of meter values that should be sent as sampled data elements in separate meter value messages. Supported are: 'Energy.Active.Import.Register', 'Power.Active.Import', 'Power.Offered', 'Current.Import', 'Current.Offered', 'Frequency', 'SoC', and 'Temperature'.	No	Meter values sampled data (OCPP)
StopTxnSampledData	Both	Yes	Not supported (included for compatibility).	No	Stop transaction sampled data (OCPP)
StopTxnAlignedData	Both	Yes	Not supported (included for compatibility).	No	Stop transaction aligned data (OCPP)
SecondMeterIPAddress	Master	No	Sets the IP address of the second meter.	Yes	IP address of second meter
SecondMeterTCPPortNumber	Master	No	Specifies the TCP port of the second meter.	Yes	Port number of second meter
MeterRestrictSecondaryTypes	Not relevant	No	Show complete list with all meter types for load management or limit list to meter models with Modbus TCP.	Yes	N/A
RestartTransAfterPowerLoss	Both	No	Enable if a transaction that was interrupted by a power loss shall be continued once the power is restored. If disabled the authorization needs to be done again by the user and a new transaction will be started. Can't be enabled if sending signed meter values is enabled.	Yes	Restart transaction after power loss
CurrentDirPrimaryL1	Individual	No	If 'Standard' is selected, positive values mean grid-to-charger and negative values mean charger-to-grid. If 'Inverted' is selected, the value reported by the primary meter will be considered to be from the charger to the grid. If set to 'Suppress-signed' the current and power value reported by the primary meter in line 1 will be considered to be from the grid to the charger.	Yes	Current flow direction of L1 of primary meter
CurrentDirPrimaryL2	Individual	No	If 'Standard' is selected, positive values mean grid-to-charger and negative values mean charger-to-grid. If 'Inverted' is selected, the value reported by the primary meter will be considered to be from the charger to the grid. If set to 'Suppress-signed' the current and power value reported by the primary meter in line 2 will be considered to be from the grid to the charger.	Yes	Current flow direction of L2 of primary meter
CurrentDirPrimaryL3	Individual	No	If 'Standard' is selected, positive values mean grid-to-charger and negative values mean charger-to-grid. If 'Inverted' is selected, the value reported by the primary meter will be considered to be from the charger to the grid. If set to 'Suppress-signed' the current and power value reported by the primary meter in line 3 will be considered to be from the grid to the charger.	Yes	Current flow direction of L3 of primary meter
CurrentDirSecondL1	Individual	No	If set to 'Inverted', the current and power value reported by the second meter in line 1 will be inverted in sign.	Yes	Current flow direction of L1 of second meter
CurrentDirSecondL2	Individual	No	If set to 'Inverted', the current and power value reported by the second meter in line 2 will be inverted in sign.	Yes	Current flow direction of L2 of second meter
CurrentDirSecondL3	Individual	No	If set to 'Inverted', the current and power value reported by the second meter in line 3 will be inverted in sign.	Yes	Current flow direction of L3 of second meter
WrittenOfferAddress	Both	No	Configures the postal address part of the written offer that the user can write to in order to request the GPL software. (Multiple lines can be separated by commas.)	No	N/A
ManufacturerURL	Master	No	Configures the uniform resource locator (URL) of the manufacturer. The manufacturer URL is used by various network services such as the SEMP interface.	No	N/A
AuthorizationInput	Not relevant	No	Input used for authorization from an external switch/relay. If triggered, an AuthorizeRequest with a fixed idtag 'input_auth' will be sent to the backend. To authorize successfully, 'input_auth' needs to be configured in the backend.	Yes	Authorization Input
RestInterfaceEnable	Both	No	This option enables the REST interface. It provides the status of the charge controller, error messages and charging session information. The interface can be used to show information on a customer-facing display of the charger. The option 'Enabled (without UID)' prevents access to user authentication information. 'Enabled (with UID)' shows user authentication information and may be used, when interfaces are protected against unauthorized access.	Yes	N/A
DlmHierarchicalMode	Master	No	If selected, this node will function as the DLM Coordinator (i.e. the \"central\" node) of the hierarchical DLM network. There can only be a single coordinator	Yes	Hierarchical Dynamic Load Management - DLM Coordinator
DlmcAddress	Master	No	This unique address identifies this controller in the hierarchical DLM network. The naming schema is hierarchy in the constraints for this hierarchical DLM network.	Yes	N/A
DlmcMqttBrokerAddress	Master	No	The IP address for the broker. On one of the controllers in the hierarchical DLM network has to be run the MQTT broker. Use the IP address of the controller where the value \"Enabled (with local MQTT broker)\" was set.	Yes	N/A
DlmcMqttBrokerPort	Master	No	The port on which this controller connects to the MQTT broker. The default is 8883.	Yes	N/A
DlmcMaximumFallbackCurrent1	Master	No	When the connection to the DLM coordinator is lost then this fallback current (L1/L2/L3) [A] is set for the DLM master	Yes	DLM master fallback current
DlmcMaximumFallbackCurrent2	Master	No	When the connection to the DLM coordinator is lost then this fallback current (L1/L2/L3) [A] is set for the DLM master	Yes	DLM master fallback current
DlmcMaximumFallbackCurrent3	Master	No	When the connection to the DLM coordinator is lost then this fallback current (L1/L2/L3) [A] is set for the DLM master	Yes	DLM master fallback current
DlmcPublishConstraints	Master	No	When enabled the constraints will be published to the MQTT broker	Yes	Publish constraints for DLM coordinator
DlmState	Individual	No	DLM State	No	N/A
DlmMode	Individual	No	Specifies the ChargePoint's role in a DLM network. There MUST be exactly one DLM Master in a DLM network managing multiple DLM-Slaves. Typically, a ChargePoint configured as DLM Master will also host an internal DLM-Slave. Note: A ChargePoint configured as standalone DLM Master will not host an internal DLM-Slave. If used for charging anyway, its power consumption will be not controlled by DLM!	Yes	Dynamic Load Management - DLM Master/Slave
DlmSolarMode_dlm	Master	No	Whether this DLM Master allows special handling of DLM-Slaves that want to use solar energy. 'Solar Surplus' will allow those slaves to charge only when there is enough solar energy available. 'Solar Charging' allows to use some amount of grid supply current(see parameter 'Maximum grid supply current') to charge the solar DLM slaves at least with their minimum charging current. With 'Grid Charging' all DLM slaves charge with the maximum available current.	No	Configure Solar Mode for DLM
DlmDiscoveryNetworkId	Master	No	Several DLM groupings might coexist in one physical LAN. In case of DLM Master-Auto-Discovery, they are distinguished by Master-Auto-Discovery Network Id.	Yes	DLM Network Id
DlmMasterIp	Master	No	DLM Master IP which is used for DLM-Slaves configured with Master-Fixed-IP. Additionally the connection port can be specified (IP[:port]).	Yes	DLM Master IP and port
DlmTimeTableScheduleRandomization	Not relevant	No	Delay the scheduled activation of a specified current limit by a random number of seconds between 0 and this. Example: assume a value of 100 is set and the time table is set to restrict the current to 6 A at 2 pm. The limit would be enforced at 14:00:00 + a random number of seconds up to 100, effectively between 14:00:00 and 14:01:39	No	N/A
DlmPhase1Limit	Master	No	Overall current limit for DLM available for distribution to EVs.	Yes	EVSE Sub-Distribution Limit (L1/L2/L3) [A]
DlmOperatorPhase1Limit	Master	No	Operator current limit for DLM available for distributionto EVs. The 'Operator EVSE Sub-Distribution Limit' is equal or smaller than the 'EVSE Sub-Distribution Limit'. It can be changed without rebooting the chargepoint. Thus a backend could use this parameter to alter the energy available for charging EVs dynamically. The backend will not be able to set a value higher than the 'EVSE Sub-Distribution Limit'.	No	Operator EVSE Sub-Distribution Limit (L1/L2/L3) [A]
DlmOperatorPhase2Limit	Master	No	Operator current limit for DLM available for distributionto EVs. The 'Operator EVSE Sub-Distribution Limit' is equal or smaller than the 'EVSE Sub-Distribution Limit'. It can be changed without rebooting the chargepoint. Thus a backend could use this parameter to alter the energy available for charging EVs dynamically. The backend will not be able to set a value higher than the 'EVSE Sub-Distribution Limit'.	No	Operator EVSE Sub-Distribution Limit (L1/L2/L3) [A]
DlmOperatorPhase3Limit	Master	No	Operator current limit for DLM available for distributionto EVs. The 'Operator EVSE Sub-Distribution Limit' is equal or smaller than the 'EVSE Sub-Distribution Limit'. It can be changed without rebooting the chargepoint. Thus a backend could use this parameter to alter the energy available for charging EVs dynamically. The backend will not be able to set a value higher than the 'EVSE Sub-Distribution Limit'.	No	Operator EVSE Sub-Distribution Limit (L1/L2/L3) [A]
DlmExtMeterMainDistributionLimitPhase1	Master	No	Current limit for DLM available for distribution to EVs and additional energy loads. This value is typically higher than the 'EVSE Sub-Distribution Limit' above. An external meter is required to detect the energy consumption of the additional load.	Yes	Main Distribution Limit (L1/L2/L3) [A]
DlmExtMeterMainDistributionLimitPhase2	Master	No	Current limit for DLM available for distribution to EVs and additional energy loads. This value is typically higher than the 'EVSE Sub-Distribution Limit' above. An external meter is required to detect the energy consumption of the additional load.	Yes	Main Distribution Limit (L1/L2/L3) [A]
DlmExtMeterMainDistributionLimitPhase3	Master	No	Current limit for DLM available for distribution to EVs and additional energy loads. This value is typically higher than the 'EVSE Sub-Distribution Limit' above. An external meter is required to detect the energy consumption of the additional load.	Yes	Main Distribution Limit (L1/L2/L3) [A]
DlmExtLoadHeadroomPhase1	Master	No	Safety margin to avoid transient overload situations. The algorithm will keep headroom towards 'Main Distribution Limit'	No	External Load Headroom (L1/L2/L3) [A]
DlmExtLoadHeadroomPhase2	Master	No	Safety margin to avoid transient overload situations. The algorithm will keep headroom towards 'Main Distribution Limit'	No	External Load Headroom (L1/L2/L3) [A]
DlmExtLoadHeadroomPhase3	Master	No	Safety margin to avoid transient overload situations. The algorithm will keep headroom towards 'Main Distribution Limit'	No	External Load Headroom (L1/L2/L3) [A]
DlmExtLoadAvgLen	Master	No	Meter values will be averaged in order to avoid transients.	Yes	External Load Averaging Length [s]
DlmDisconnectedLimit	Both	No	Current limit when disconnected from DLM network.	Yes	Disconnected Limit [A]
DlmMinCurrentRating	Both	No	Minimum current limit that charging should not go below.	Yes	Minimum Current Limit [A]
DlmSlaveSolarEnabled	Both	No	Enables additional limiting for this DLM slave to use renewable production	No	Solar Mode on this charger
DlmCurrImbalanceLim	Master	No	Maximum allowed phase imbalance. DLM will not exceed the 'Current Imbalance Limit' between phases when assigning current to EVs.	Yes	Current Imbalance Limit [A]
DlmExtMeterLoadFallbackPhase1	Master	No	In the error case, where the external meter is disconnected or fails, 'External Load Fallback' is assumed as consumption of an additional consumer. Setting to a high value will result in no current available for the EVSE sub-distribution in that particular situation. Thus, charging would stop	Yes	External Load Fallback (L1/L2/L3) [A]
DlmExtMeterLoadFallbackPhase2	Master	No	In the error case, where the external meter is disconnected or fails, 'External Load Fallback' is assumed as consumption of an additional consumer. Setting to a high value will result in no current available for the EVSE sub-distribution in that particular situation. Thus, charging would stop	Yes	External Load Fallback (L1/L2/L3) [A]
DlmExtMeterLoadFallbackPhase3	Master	No	In the error case, where the external meter is disconnected or fails, 'External Load Fallback' is assumed as consumption of an additional consumer. Setting to a high value will result in no current available for the EVSE sub-distribution in that particular situation. Thus, charging would stop	Yes	External Load Fallback (L1/L2/L3) [A]
DlmInput1CurrOffsetPhase1	Master	No	Offset added to 'EVSE Sub-Distribution Limit' case external input 1 is high. Note: currently only negative values are supported.	Yes	Ext. Input 1 Current Offset (L1/L2/L3) [A]
DlmInput1CurrOffsetPhase2	Master	No	Offset added to 'EVSE Sub-Distribution Limit' case external input 1 is high. Note: currently only negative values are supported.	Yes	Ext. Input 1 Current Offset (L1/L2/L3) [A]
DlmInput1CurrOffsetPhase3	Master	No	Offset added to 'EVSE Sub-Distribution Limit' case external input 1 is high. Note: currently only negative values are supported.	Yes	Ext. Input 1 Current Offset (L1/L2/L3) [A]
DlmInput3CurrOffsetPhase1	Master	No	Offset added to 'EVSE Sub-Distribution Limit' case meter digital input is high. Note: currently only negative values are supported.	Yes	Meter Digital Input Current Offset (L1/L2/L3) [A]
DlmInput3CurrOffsetPhase2	Master	No	Offset added to 'EVSE Sub-Distribution Limit' case meter digital input is high. Note: currently only negative values are supported.	Yes	Meter Digital Input Current Offset (L1/L2/L3) [A]
DlmInput3CurrOffsetPhase3	Master	No	Offset added to 'EVSE Sub-Distribution Limit' case meter digital input is high. Note: currently only negative values are supported.	Yes	Meter Digital Input Current Offset (L1/L2/L3) [A]
DlmExtMeterEnabled	Master	No	If enabled, an external, secondary meter allows to also consider the power consumption of additional load. The power available for charging EVs will be adjusted accordingly. Please make sure, 'Meter configuration (Second)' is configured, preferrably to a 3-phase, phase aware meter.	Yes	External Meter Support
DlmExtMeterLocation	Master	No	Specifies how the external meter is connected according to its location. Either at the grid's entry point; between an external load and the rest of the installation; or at a renewable energy source such as e.g. a solar panel.	Yes	External Meter Location
DlmCurrImbalancePreventionEnabled	Master	No	If enabled, DLM will not exceed the 'Current Imbalance Limit' configured.	Yes	Current Imbalance Prevention
DlmDisableDiscoveryBroadcast	Master	No	Disables the broadcasting of DLM Discovery beacons in the DLM master. If disabled, DLM slaves will not be able to find their DLM master automatically with the help of the DLM Master-Auto-Discovery feature.	Yes	Disable Discovery Broadcasting
DlmRecalcInterval	Master	No	The DLM algorithm will not calculate and re-assign current to its DLM slaves any faster than at this configured rate. As an exception, EVs getting ready to charge will be considered and assigned current immedeately.	No	DLM Algorithm Sample Rate
DlmPersistentSlavesCount	Master	No	Number of persistent DLM slaves registered in DLM slave database	No	Persistent DLM slave count
DlmClearPersistentSlaves	Master	No	Select 'Clear' and 'Save' to clear the database of known DLM slaves	No	Clear persistent DLM slave DB
DlmInput1CurrOffsetCfg	Master	No	Adds a configurable offset to 'EVSE Sub-Distribution Limit' based on GPI External Input 1.	Yes	External Input 1 Config
DlmInput3CurrOffsetCfg	Master	No	Adds a configurable offset to 'EVSE Sub-Distribution Limit' based on the Meter's Digital Input register.	Yes	Meter Digital Input Config
DlmInput1Polarity	Master	No	Changes the polarity of the input signal 1. \"Active high\" does not change the polarity, \"Active low\" inverts the signal.	Yes	External Input 1 Polarity
ModbusSlaveTCPConfigOnOff	Both	No	Activates the charging station's Modbus TCP Server function for connecting energy management systems via Ethernet. Through this interface control information and commands are transferred between charging station and energy manager. For detailed information on the Modbus registers, see the product documentation.	Yes	Modbus TCP Server for energy management systems
ModbusSlaveRegAddrSet	Both	No	Choose the set of register addresses that the Modbus TCP Server device will expose to its Master device	Yes	Modbus TCP Server Register Address Set
ModbusSlaveAllowStartStop	Both	No	Allows transactions to be started/stopped from a Modbus Master device via the controller's Modbus TCP Server interface.	Yes	Modbus TCP Server Allow Start/Stop Transaction
ModbusSlaveAllowUIDDisclose	Both	No	Allows sending the UID via the Ebee Modbus TCP Server protocol	Yes	Modbus TCP Server Allow UID Disclose
ModbusSlaveTCPPort	Master	No	Port number on which the Modbus TCP Server waits for incoming connections on connector 1. A second server waits on 'port + 100'. Its registers are read-only. In case a second connector is supported, the configured 'port + 1' and 'port + 101' will be used for that connector.	Yes	Modbus TCP Server Base Port
ModbusSlaveCommTimeout	Both	No	Timeout in seconds between messages with a Modbus TCP Master device	Yes	Modbus TCP Server Communication Timeout
ModbusSlaveDevAddr	Individual	No	Device address (0 to 255) to use for the Modbus TCP Server feature	Yes	Modbus TCP Server Device Address
SMAInterfaceOnOff	Master	No	The charging station can be networked with the SMA Sunny Home Manager 2.0 to charge primarily or exclusively with self-generated solar energy.	No	SEMP interface
SMAChargingMode	Master	No	This option sets the directly applicable charging mode. In surplus charging mode, the vehicle charges primarily with self-generated electricity according to the setting in Sunny Portal. In immediate charging mode, control signals from the Sunny Home Manager 2.0 are ignored and the vehicle is charged with the maximum possible current regardless of the available solar power. In Manual Configuration mode, it is also possible to specify how much energy is to be charged at least until the preset departure time. This mode also uses energy from the electricity grid if not enough self-generated electricity can be provided. The expected amount of energy can be communicated to the energy manager via the maximum demand option. In each of the modes, charging continues until the vehicle is full.	No	Charging Mode
SMACommunicationTimeout	Master	No	If the charging station cannot reach the energy manager for longer than set, the connection is considered to have failed. Possible value range: 60 s to 3600 s.	No	Time to connection failure [s]
SMACommunicationTimeoutCurrent	Master	No	If the connection to the energy manager fails, the charging current is set to the value set here. Settings between 6 A and 80 A are permissible.	No	Current in case of connection failure [A]
SMAMaxEnergyDemand	Master	No	This value sets the maximum energy demand that is reported to the Energy Manager for the charging point. This value typically represents the maximum capacity of the vehicle battery. Permissible range of values: 1 kWh to 1000 kWh.	No	Maximum energy demand [kWh]
SMAMinEnergyDemand	Master	No	This value sets the minimum amount of energy that is reported to the Energy Manager for the charge point. With manual configuration, at least the set amount of energy is charged by the preset time. Permissible value range: 0 kWh to 1000 kWh.	No	Minimum energy demand [kWh]
SMAChargeCompleteTime	Master	No	This value configures the time of day until the charging process should be completed. At least the minimum configured energy requirement should be charged by this time.	No	Scheduled departure time [hh:mm]
EEBUSConfigOnOff	Master	No	Compatible energy managers can control the charging station via the EEBus interface.	No	EEBus interface
EEBUSModuleVersion	Master	No		No	N/A
EEBUSModuleShipId	Master	No		No	N/A
EEBUSConfigCevcOnOff	Master	No	Compatible energy managers can control the charging station via the EEBus interface.	No	Coordinated Charging Mode
EEBUSFallbackCurrent	Master	No	If the connection to the energy manager fails, the charging current is set to the value set here. Settings between 6 A and 80 A are permissible.	No	N/A
EEBUSCommunicationTimeout	Master	No	If the charging station cannot reach the energy manager for longer than set, the connection is considered to have failed. If the energy manager serves to protect the main fuse from overload, a correspondingly short time is recommended. Possible value range: 4 s to 3600 s.	No	Communication Timeout [s]
EEBUSPairedCemId	Master	No	Identifier issued by the coupled energy manager for identification purposes.	No	Identifier of the coupled energy manager
EEBUSPairedCemSki	Master	No	Subject Key Identifier of the coupled energy manager for identification purposes.	No	SKI of the coupled energy manager
EEBUSPairedCemUri	Master	No		No	N/A
EEBUSPairedCemModelName	Master	No		No	N/A
EEBUSPairedCemIp	Master	No		No	N/A
EEBUSEnableKeoLogging	Master	No	Enable logging of KEO stack messages	No	N/A
EEBusLPCFailsafePowerUser	Master	No	If the connection to the energy manager fails, the failsafe power for LPC is set to the value set here.	No	Failsafe power in case of connection failure [W]
EEBusLPCFailsafePowerEnergyGuard	Individual	No	If the connection to the energy manager fails, the power is set to the value set by the energy guard.	No	Energy guard failsafe power in case of connection failure [W]
EEBusLPCFailsafeDurationMinUser	Master	No	The minimum duration that the system will remain in the LPC failsafe state if the connection to the energy manager fails. Possible value range: 7200 s to 86400 s.	No	Minimum duration for failsafe state [s]
EEBusLPCFailsafeDurationMinEnergyGuard	Individual	No	The minimum duration that the system will remain in the failsafe state if the connection to the energy manager fails. The value is set by the energy guard. Possible value range: 7200 s to 86400 s.	No	Energy guard minimum duration for LPC failsafe state [s]
HemsConfigChargingMode	Master	No	This option allows to select the charging mode used by the EEBus system.\"Mains charging\" configures the charging with mains power. The options \"Solar charging\" and \"Solar surplus charging\" configure the usage of self-produced solar power for charging. The first two options aim at optimizing the self-consumption whereas \"Solar surplus charging\" additionally configures the exclusive usage of solar surplus power for charging.	No	N/A
HemsConfigMaxEnergyDemand	Master	No	This value sets the maximum energy demand that is reported to the Energy Manager for the charging point. This value typically represents the maximum capacity of the vehicle battery. Permissible range of values: 1 kWh to 1000 kWh.	No	N/A
HemsConfigMinEnergyDemand	Master	No	This value sets the minimum amount of energy that is reported to the Energy Manager for the charge point. With manual configuration, at least the set amount of energy is charged by the preset time. Permissible value range: 0 kWh to 1000 kWh.	No	N/A
HemsConfigOptEnergyDemand	Master	No	This value sets the optimal amount of energy that is reported to the Energy Manager for the charge point. With manual configuration, at least the set amount of energy is charged by the preset time. Permissible value range: 0 kWh to 1000 kWh.	No	Optimal energy demand [kWh]
HemsConfigChargeCompleteTime	Master	No	This value configures the time of day until the charging process should be completed. At least the minimum configured energy requirement should be charged by this time.	No	N/A
HemsDeviceName	Master	No	Allows the configuration of an HEMS-specific device name for systems such as EEBus or SEMP. Please note that this value is not adopted immediately if the system in question is already coupled with an energy manager.	Yes	HEMS device name
SignedUpdates	Both	No	Enables or disables the signature verification for software updates.	Yes	N/A
BannerEnabled	Not relevant	No	A Banner SureCross DX80-PB2 gateway can be connected via the charging station's external Modbus RTU interface. Each gateway can connect up to 47 M-GAGE wireless sensors for parking space occupancy detection. The charging station connected to the gateway sends the occupancy data for all connected sensors via OCPP DataTransfer to the set backend, which may evaluate the data. Note: Modbus ID 3 must be set in the DX80 gateway configuration.	Yes	Send parking space occupancy data to backend
BannerReadAnalog	Not relevant	No	For testing and analysis purposes, raw analogue data from the parking sensor can be transmitted to the backend. As more data is transmitted, the data retrieval interval need to be increased. In normal operation, the transmission of raw data is not necessary.	Yes	Transmit additional analogue sensor values
BannerPollInterval	Not relevant	No	Specifies the interval in seconds at which the charging station retrieves sensor data from the gateway. New data can be retrieved after 20 seconds at the earliest. When retrieving raw analogue data, the interval must be at least 40 seconds. The interval should be extended if many sensors are connected and data from connected sensors is missing.	Yes	Interval to retrieve data from the gateway (s)
BannerSendInterval	Not relevant	No	Specifies the interval in seconds at which sensor data is sent to the OCPP backend. The send interval should be at least 40 seconds and must not be shorter than the data retrieval interval. Intervals between 60 and a maximum of 600 seconds are recommended.	Yes	Interval for sending data via OCPP (s)
BannerMaxNodeId	Not relevant	No	Parking sensors are integrated in the gateway with a consecutive number. The gateway has the number 0, the first sensor the number 1. Up to 47 sensors can be read via the gateway.	Yes	Number of connected parking sensors
GeolocationUpdate	Master	No	Request or update the geolocation data	No	Update geolocation data

7. OCPP-relevant configuration parameters in Config UI

Category	Parameter	Purpose	Cleaned-up Remarks
General	Connection Type	Physical connection method for OCPP Backend communication	Defines the preferred connection method, but if both Ethernet and GSM are active, Ethernet is always used automatically. If no Backend is configured, no OCPP communication occurs.
	OCPP ChargeBoxIdentity (ChargePointID)	Unique identifier for the Charge Controller	Required for proper communication with the OCPP backend.
	OCPP Mode	Defines the OCPP version and transport protocol	Always set to <Value>OCPP-J 1.6</Value>.
	WebSockets JSON OCPP URL of the Backend	URL of the OCPP central system for WebSocket	Use the format ws://backend:8080/OCPP/v16/. Do not include the ChargePointID in the URL, even if some backends suggest it.
	WebSockets proxy	Proxy server for WebSocket connections	Optional WebSocket proxy in the format HOST:PORT. If no port is given, 80 is used by default.
	WebSockets keep-alive interval	Interval for WebSocket ping messages	Value in seconds (0–10000). Use 60 seconds to help maintain connection stability. Use this if the backend connection drops unexpectedly.
Security	OCPP connection strictness	Security level for OCPP connections	Sets minimum encryption standard. Use only-secure-cyphers when possible. Set to all-cyphers if the backend doesn't support modern encryption.
	HTTP Basic Authentication password	Password for OCPP authentication	Used if required by the backend. Username is automatically set to the ChargePointID.
Connection Behavior	Force Heartbeat request messages	Whether to force sending heartbeat messages	Some backends need this to maintain a stable connection. Enable if you witness frequent disconnects.
	TCP Watchdog Timeout	Timeout for TCP connection monitoring
	Display backend disconnect as error	Whether to show disconnection as an error
StatusNotification	Send informative StatusNotifications	Whether to send informational status updates	Sends additional status info, helpful for debugging or to enhance backend insights.
	Send error StatusNotifications	Whether to send error status updates	Enables more detailed error reporting to the backend.
	Send USB error StatusNotifications	Whether to send USB-specific error updates	Controls if USB-related errors are reported to the backend.
Maintenance & UI Events	State 'unavailable' at FW update begin	Set status to unavailable during firmware updates
	Force OCPP connector state	Override connector availability state
	Send status for webui login event	Send notification when web UI is accessed	Sends an info-level status message to the backend when someone logs into the web UI.
Compatibility & Legacy	Strategy for StatusNotification	When to change connector status to Occupied	Deprecated. Legacy setting from OCPP 1.5. Can be ignored.
	Allow long get configuration keys	Support for longer configuration key names
	Integer values for boolean config keys	Use integers instead of booleans in responses
Retry & Timeout Settings	Backend connection timeout	Timeout for OCPP connection attempts
	Number of transaction message attempts	Retries for transaction messages
	Eichrecht transaction message attempts	Retries for Eichrecht-specific messages
	Disallow charging if OCPP queue full	Block charging when message queue is full
	SSL Strictness as client	SSL/TLS security level
Metering & Reporting	DataTransfer for Tariff And Total Usage	Send tariff and usage data via DataTransfer
	Meter values sampled data (OCPP)	Meter values to be sent based on sampling interval
	Meter Value Sample Interval (OCPP)	Time between meter value samples
	Meter values aligned data (OCPP)	Meter values to be sent at regular intervals
	Clock aligned data interval (OCPP)	Interval for clock-aligned meter values
	Retransmit MeterValues	Whether to retry sending meter values

8. OCPP-Relevant Configuration Parameters

Category	Parameter	Purpose	Cleaned-up Remarks
General Connectivity	Connection Type	Physical connection method for OCPP Backend communication	Defines the preferred connection method. If both Ethernet and GSM are active, Ethernet is always used automatically. If no Backend is configured, no OCPP communication occurs.
	OCPP ChargeBoxIdentity (ChargePointID)	Unique identifier for the Charge Controller	Required for proper communication with the OCPP backend.
	OCPP Mode	Defines the OCPP version and transport protocol	Always set this to OCPP-J 1.6.
	WebSockets JSON OCPP URL of the Backend	URL of the OCPP central system for WebSocket	Use the format ws://backend:8080/OCPP/v16/. Do not include the ChargePointID in the URL, even if some backends suggest it.
	WebSockets proxy	Proxy server for WebSocket connections	WebSocket proxy in the format HOST:PORT. If no port is given, 80 is used by default.
	WebSockets keep-alive interval	Interval for WebSocket ping messages	Value in seconds (0–10000). Use 60 seconds to help maintain connection stability. Use this if the backend connection drops unexpectedly. More
Security & Authentication	OCPP connection strictness	Security level for OCPP connections	Sets minimum encryption standard. Use only-secure-cyphers when possible. Set to all-cyphers if the backend doesn't support modern encryption.
	HTTP Basic Authentication password	Password for OCPP authentication	Used if required by the backend. Username is automatically set to the ChargePointID.
	Send status for webui login event	Send notification when web UI is accessed	Sends an info-level status message to the backend when someone logs into the web UI. More
	SSL Strictness as client	SSL/TLS security level	Set to Skip host check if DNS server fails and you use IP addresses in place of domain names. More
Connection Behavior	Force Heartbeat request messages	Whether to force sending heartbeat messages	Some backends need this to maintain a stable connection. Enable if you witness frequent disconnects.
	TCP Watchdog Timeout	Timeout for TCP connection monitoring	If the TCP Watchdog Timeout is reached and the Backend cannot be reached, a reboot on the Charge Controller is triggered. More
	Backend connection timeout	Timeout for OCPP connection attempts	(OCPP standard: BackendConnectionTimeout). Default: 60s. Range: 3-300s. Full behavior details
	Disallow charging if OCPP queue full	Block charging when message queue is full	Charging is blocked when the internal OCPP message queue is full. Prevents new sessions that would result in message loss — especially critical for Eichrecht compliance. More
	Display backend disconnect as error	Whether to show disconnection as an error on the HMI	Error is shown on the HMI in case a Backend is configured but connection fails.
StatusNotification Control	Send informative StatusNotifications	Whether to send informational status updates	Sends additional status info, helpful for debugging or to enhance backend insights. More
	Send error StatusNotifications	Whether to send error status updates	Enables more detailed error reporting to the backend. More
	Send USB error StatusNotifications	Whether to send USB-specific error updates	Controls if USB-related errors are reported to the backend. More
	State 'unavailable' at FW update begin	Set status to unavailable when firmware is being downloaded
Maintenance & Overrides	Force OCPP connector state	Override connector availability state	Overrides the connector availability state regardless of Backend-side state.
Compatibility & Legacy	Strategy for StatusNotification	When to change connector status to Occupied	Deprecated. Legacy setting from OCPP 1.5. Can be ignored.
	Allow long get configuration keys	Extends the max. length of configuration key values to 500+ characters	Allows more than the OCPP standard for the value length of GetConfiguration requests. Needed for proprietary certificate exchange.
	Integer values for boolean config keys	Use integers instead of booleans in responses	(Deprecated) Scoped to standard OCPP configuration key values. Behavior to output those values as integer is deprecated.
Retry Logic	Number of transaction message attempts	Retries for transaction messages	Used for all transaction-related messages except Eichrecht-bound ones. More
	Eichrecht transaction message attempts	Retries for Eichrecht-specific messages	Used only if Eichrecht is active and message is Start/Stop/MeterValues tied to a transaction. More
Metering & Reporting	DataTransfer for Tariff And Total Usage	Send tariff and usage data via DataTransfer
	Meter values sampled data (OCPP)	Meter values to be sent based on sampling interval
	Meter Value Sample Interval (OCPP)	Time between meter value samples
	Meter values aligned data (OCPP)	Meter values to be sent at regular intervals
	Clock aligned data interval (OCPP)	Interval for clock-aligned meter values
	Retransmit MeterValues	Whether to retry sending meter values	When enabled, transaction-bound MeterValues are held in the queue and retried until success or limit reached. Affects queue size and charging availability. More

9. In-Depth Explanations

9.1. Connectivity keep-alive troubleshooting

Purpose: Maintain a persistent connection with the OCPP backend.

Details:

• If your backend frequently disconnects, try enabling Force Heartbeat and/or lowering the WebSockets keep-alive interval to 60 seconds.
• This setting works alongside the TCP watchdog.
• Pings sent prevent NAT/firewall timeout issues in some networks.

9.2. Informative StatusNotifications

Controlled by: Send informative StatusNotifications (INFO_STATUS_NOTIFICATIONS)

Details:

• Sends info-level updates like:

  • Energy flow start/stop
  • Temperature readings
  • Web UI logins
  • GPIO state changes

• Useful for debugging, UI feedback, and backend analytics.

• Does not include error-level data.

Triggered Informational StatusNotifications:

• Energy Flow:

  • "Energy is flowing to vehicle"
  • "No energy flowing to vehicle"
  • "Energy flow to vehicle is unknown"

• Temperature Reports:

  • "Temperatures: CPU: [temp] RFID: [temp]"
  • "Charging paused. Temperature: +XX.X C"
  • "Signaled current reduced. Temperature: +XX.X C"
  • "Signaled current back to nominal. Temp: +XX.X C"

• Ventilation & Heating: State change notifications

• Web UI Login Events: If enabled

• GPIO State Changes: Depends on related GPIO notify setting

• Triggered by backend: "Triggered status report" via TriggerMessage

9.3. Error StatusNotifications

Controlled by: Send error StatusNotifications (ERROR_STATUS_NOTIFICATIONS)

Examples of Static Info Strings:

• "Residual current detected via sensor"
• "Vehicle signals error"
• "Vehicle diode check failed - tamper detection"
• "MCB of type 2 socket triggered"
• "RCD may be triggered (OCPP meter power loss)"
• "Contactor welded"
• "Plug locking failed"
• "Housing temperature too high - charging paused"
• "Temperature reaches safety limit - emergency stop"
• "GSM SIM card is missing"
• "USB communication errors."
• "Message queue is full"

Examples of Dynamic Info Strings:

• GSM signal strength: gsm_get_ocpp_status_info_string()
• Firmware update status: net_firmware_get_status_info_string()
• USB hotplug: usb_hotplug_progress_string()
• Phase errors: phase_monitor_get_phase_err_msg()
• Internal diagnostics: component manager, PIC24, etc.

9.4. USB error StatusNotifications

Controlled by: Send USB error StatusNotifications (USB_ERROR_STATUS_NOTIFICATIONS)

• Sends:

  • "USB communication errors."
  • "USB stick handling: Finalized - Remove USB stick"
  • "USB stick handling failed - Remove USB stick"

• Often sent together with log file diagnostics or update failures

9.5. SSL strictness and IP address use

Problem: When using IP addresses instead of domain names, TLS certificate validation fails due to hostname mismatch.

Solution:

• Set SSL Strictness as client to Skip host check
• This disables hostname validation but maintains encryption

9.6. Backend connection timeout details

Parameter: Backend connection timeout (BackendConnectionTimeout)

Default: 60s Range: 3–300s

Behavior:

• Used for:

  • APN and proxy connection timeout
  • OCPP request-response timeout

• Retries use exponential backoff:

  • Timeout doubles per failure (±20% jitter)
  • Max delay: 12h (43,200s)
  • After max: triggers reboot

• Volatile messages are discarded after timeout

• Persistent messages are retried

• Triggers backend reset via tcpip_comm_manage_generic_error(0)

9.7. TCP watchdog timeout

Parameter: TCP Watchdog Timeout

Purpose:

• Acts as a global failsafe
• If no TCP activity over a long period, reboot is triggered
• Log example: "No tcp connection for long time. Rebooting"

9.8. OCPP queue full behavior

Parameter: Disallow charging if OCPP queue full

Name: OCPP_QUEUE_FULL_AS_ERROR_STATE (OCPP: "OcppQueueFullAsErrorState") Default: OFF Type: ON/OFF option File: ocpp_logic_parameters.c:1370–1383

Purpose:

• Charging is blocked if the internal OCPP message queue is full
• Prevents starting new sessions that would generate unsent messages
• Especially important for Eichrecht-compliant operations

9.9. Queue implementation and limits

Total queue capacity:

• 350 messages maximum: Hard-coded limit (PERS_LIST_ELEM_NUM_MAX)
• 70 message threshold for StatusNotifications: If 70+ items in queue, additional StatusNotifications are suppressed (PERS_LIST_ELEM_NUM_MSG_LIMIT)

Technical Behavior:

• Before sending any new message, the system checks queue fullness

• If full:

  • A log warning is created
  • The message is discarded silently
  • If the feature is enabled: triggers error state ERR_OCPP_MSG_QUEUE_FULL
  • Error marked as pause_during_error = 1, which blocks or stops charging

Error state properties:

• OCPP Status: "Message queue is full"
• Internal Code: 01-05-006
• Recovery trigger: Queue no longer full
• Recovery behavior: Clears error and automatically resumes charging

9.10. Charging impact

• When queue is full and this setting is enabled:

  • Charging stops
  • New sessions cannot start
  • State persists until queue drains

• When disabled:

  • Queue full only suppresses new messages silently, does not affect charging

9.11. Operational Notes

• Message queue stats are not visible in the UI
• May correlate with watchdog reboots or intermittent disconnects
• When queue is full, all message types compete for limited space
• Retransmissions (like MeterValues) hold up queue until backend responds

9.12. Recommendations

• Enable only in legally constrained scenarios
• Avoid on unstable connections unless retries are optimized
• Use with infinite retry for transaction messages to prevent data loss

9.13. Transaction message retry logic

Parameter: TRANSACTION_MESSAGE_ATTEMPTS (OCPP: "TransactionMessageAttempts")

Default: 5 attempts Range: 0–5 attempts Special value: 0 = infinite retries File: ocpp_logic_parameters.c:1293-1311

Behavior:

• Applies when Eichrecht is not active

• Retries are limited to the value set in the parameter

• When retries are exhausted:

  1. Message is logged as deleted
  2. Removed from persistent queue
  3. Memory is freed
  4. No error state is triggered — message is silently dropped

Retry Interval:

• Controlled by TRANSACTION_MESSAGE_RETRY_INTERVAL (OCPP: "TransactionMessageRetryInterval")
• Default: 0 seconds
• Range: 0–1000 seconds
• Sets how long the ChargePoint waits before resubmitting a transaction-relevant message
• File: ocpp_logic_parameters.c:1334–1350

Transaction-Relevant Messages Include:

• StartTransaction
• StopTransaction
• MeterValues with transaction ID
• (Also TransactionEvent in OCPP 2.0)

9.14. Eichrecht transaction message attempts

Parameter: EICHRECHT_TRANSACTION_MESSAGE_ATTEMPTS (OCPP: "EichrechtTransactionMessageAttempts")

Default: 0 (infinite retries) Range: -1 to 5 Special values:

• 0: Infinite retries
• -1: Use value of TRANSACTION_MESSAGE_ATTEMPTS File: ocpp_logic_parameters.c:1312–1332

Applies when:

• Eichrecht is active AND

• Message is:

  • StartTransaction
  • StopTransaction
  • MeterValues with transaction ID

Priority behavior:

if (eichrecht_is_active() && ocpp_client_is_message_transaction_relevant(message, 0))
    return PS_GET(EICHRECHT_TRANSACTION_MESSAGE_ATTEMPTS, unsigned int);
return PS_GET(TRANSACTION_MESSAGE_ATTEMPTS, unsigned int);

Eichrecht active condition:

• Eichrecht-certified meter is selected (eHZ, DZG, etc.) OR
• System is in Eichrecht locked state File: eichrecht.c:216–227

Fallback logic:

• If parameter = -1 → use TRANSACTION_MESSAGE_ATTEMPTS

9.15. Retransmit MeterValues (cross-linked with queue behavior)

Parameter: Retransmit MeterValues

Purpose: Determines whether MeterValues messages are retried upon backend failure.

Behavior:

• When enabled:

  • MeterValues with transaction ID are treated as persistent
  • Retried according to transaction message attempt logic (TransactionMessageAttempts, EichrechtTransactionMessageAttempts)
  • Held in queue until successfully sent or max attempts exceeded
  • Increases queue pressure, see OCPP queue full behavior

• When disabled:

  • MeterValues are considered volatile
  • If backend is unreachable, messages are dropped immediately after timeout

Dependencies:

• Queue size: 350 message limit affects retried MeterValues
• If queue is full and OcppQueueFullAsErrorState is enabled, charging is blocked (see Queue full behavior)
• Retransmit setting only applies to transaction-bound MeterValues

Implementation:

• Retransmission logic tied to message persistence flag
• Controlled via config UI flag or internal preset
• File references: ocpp_client.c, persistent_list.c

Recommendation:

• Enable in Eichrecht or legally regulated environments
• Disable in unstable networks where queue overflow is a risk

see CANNED response on this if existing

-->