Skip to main content
v5.32
operator
manufacturer
Last updated

OCPP key meanings

1. OCPPMeterType

IDMeter
73eHZ Meter via USB
75eHZ-B Meter via USB
6Modbus Meter ABB
47Modbus ABB EV3
44Modbus Berg B23
43Modbus Berg BME 461
19Modbus TQ EM300-LR
41Modbus TQ EM410/EM420
25Modbus TQ EM300-LR (TCP)
42Modbus TQ EM410/EM420 (TCP)
81Modbus IPD Control (TCP)
86Modbus Meter Carlo Gavazzi EM111/112
20Modbus Meter Carlo Gavazzi EM200
29Modbus Meter Carlo Gavazzi EM210
21Modbus Meter Carlo Gavazzi EM340
37Modbus DZG DVH4013
7Modbus Meter Eastron SDM630
58Modbus Eastron SDM230
8Modbus Eastron SDM120_220
39Modbus Eastron SDM72D
68Modbus Eastron SDM72D-M-V2
32Modbus ECS M3PRO
54Modbus ECS M3PRO (TCP)
13Modbus Meter Finder
12Modbus Meter Garo EM270
10Modbus Meter Garo GNM1D
9Modbus Meter Garo GNM3D
22Modbus Meter Garo GNM3T
28Modbus Meter Garo GNM3TD
11Modbus Meter Garo GM3T
80Modbus Meter Garo GMI3D-LP
38Modbus Gossen Metrawatt EM2289
27Modbus Hager ECR380D
23Modbus IME CE4DMID31
87Modbus IME CE4DF3DTMID
15Modbus Inepro PRO1_2
16Modbus Inepro PRO380
84Modbus Wago 879-3000
40Modbus Iskra WM3M6
78Modbus Iskra IE38M
79Modbus Meter Finder 7M38
33Modbus Janitza UMG 512/96 PRO
34Modbus Janitza UMG 512/96 PRO (TCP)
85Modbus Janitza UMG 604 PRO (TCP)
35Modbus Janitza UMG 605 PRO
36Modbus Janitza UMG 605 PRO (TCP)
64Modbus NZR EcoCount S85/SL85
17Modbus Optec
45Modbus Phoenix Contact EEM-EM357
30Modbus Phoenix Contact EEM-MB371 (TCP)
14Modbus Saia ALE3
83Modbus Schneider Generic (TCP)
82Modbus Schneider Generic
31Modbus Schneider iEM3555
26Modbus Siemens 7KM2200 (TCP)
24Modbus Siemens 7KT1666
49Modbus YTL DTS353F
50EV Optimizer
53Modbus SELEC EM2M-1P-C-100A
55Modbus Lovato DMED 301
56Modbus Eetarp GEM630
57Modbus Eetarp GEM230
65Modbus DZG DWH4113
66Modbus ABB D1M
67Modbus ABB D1M (TCP)
60ER Eastron SDM630-EV
61ER NZR EcoCount SL+SC 85
63ER NZR EcoCount SL+S 85
62ER Iskra WM3M4C
69ER EMH iML
1S0 Meter 'Opto 1 In'
72Modbus Eichrecht
3No Meter

2. SecondMeterType

IDMeter
77WiMOD IR Reader USB stick
6Modbus Meter ABB
47Modbus ABB EV3
44Modbus Berg B23
43Modbus Berg BME 461
19Modbus TQ EM300-LR
25Modbus TQ EM300-LR (TCP)
41Modbus TQ EM410/EM420
42Modbus TQ EM410/EM420 (TCP)
81Modbus IPD Control (TCP)
86Modbus Meter Carlo Gavazzi EM111/112
20Modbus Meter Carlo Gavazzi EM200
29Modbus Meter Carlo Gavazzi EM210
21Modbus Meter Carlo Gavazzi EM340
7Modbus Meter Eastron SDM630
58Modbus Eastron SDM230
8Modbus Eastron SDM120_220
39Modbus Eastron SDM72D
68Modbus Eastron SDM72D-M-V2
32Modbus ECS M3PRO
54Modbus ECS M3PRO (TCP)
13Modbus Meter Finder
12Modbus Meter Garo EM270
10Modbus Meter Garo GNM1D
9Modbus Meter Garo GNM3D
22Modbus Meter Garo GNM3T
28Modbus Meter Garo GNM3TD
11Modbus Meter Garo GM3T
80Modbus Meter Garo GMI3D-LP
27Modbus Hager ECR380D
23Modbus IME CE4DMID31
87Modbus IME CE4DF3DTMID
15Modbus Inepro PRO1_2
16Modbus Inepro PRO380
84Modbus Wago 879-3000
40Modbus Iskra WM3M6
78Modbus Iskra IE38M
79Modbus Meter Finder 7M38
33Modbus Janitza UMG 512/96 PRO
34Modbus Janitza UMG 512/96 PRO (TCP)
85Modbus Janitza UMG 604 PRO (TCP)
35Modbus Janitza UMG 605 PRO
36Modbus Janitza UMG 605 PRO (TCP)
64Modbus NZR EcoCount S85/SL85
17Modbus Optec
45Modbus Phoenix Contact EEM-EM357
30Modbus Phoenix Contact EEM-MB371 (TCP)
14Modbus Saia ALE3
83Modbus Schneider Generic (TCP)
82Modbus Schneider Generic
31Modbus Schneider iEM3555
26Modbus Siemens 7KM2200 (TCP)
24Modbus Siemens 7KT1666
49Modbus YTL DTS353F
51Modbus Sunspec Meter
52Modbus Sunspec Meter (TCP)
50EV Optimizer
53Modbus SELEC EM2M-1P-C-100A
55Modbus Lovato DMED 301
56Modbus Eetarp GEM630
57Modbus Eetarp GEM230
59Modbus Temco Controls SPM1-XX0-AC
88SMA Commercial Energy Meter (TCP)
66Modbus ABB D1M
67Modbus ABB D1M (TCP)
1S0 Meter 'Opto 1 In'
3No Meter

3. Errors

Description: This section provides details for the Errors tab extracted from the documentation HTML.

OCPP Error codeError activation messageError resolution messageTransaction and charging is stoppedNotesCorrective actions
groundFailureResidual current detected via sensorResidual current situation resolvedYesInternal RCMB device (yellow coil). This detects also DC residual current.The safety mechanism is reset to its original state every time the cable is unplugged from the chargepoint. Otherwise the error is automatically reset after a delay of 10 seconds if the EV was unplugged. In case the RCMB version is older than or equal to D0469, the delay is 15 minutes. If the problem persists, please check the yellow current transformer (coil) and its connection.
mode3ErrorVehicle signals errorVehicle error resolvedNoMode3 errors.Disconnect EV and try again. If that doesn’t help, follow EV’s instructions.
mode3ErrorVehicle diode check failed - tamper detectionVehicle with diode problem disconnectedYesMode3 errors.Disconnect EV and try again. If that doesn’t help, follow EV’s instructions.
overCurrentFailureMCB of type 2 socket triggeredMCB type 2 reconnectedYesMCB needs to be re-armed, requires a maintenance visit.
overCurrentFailureMCB of domestic socket triggeredMCB domestic socket reconnectedYesMCB needs to be re-armed, requires a maintenance visit.
groundFailureRCD triggeredRCD reconnectedYesExternal RCD Device.Up to a certain point this will be corrected automatically.
groundFailureRCD may be triggered (OCPP meter power loss)RCD may be reconnected (OCPP meter recovered)YesExternal RCD Device.Up to a certain point this will be corrected automatically.
otherErrorSurge Protection Device (SPD) tripped. Replace.Surge Protection Device (SPD) issue solvedNoExternal SPD Device.Surge Protection Devices (SPD) needs to be replaced.
powerSwitchFailureContactor weldedContactor weld resolvedYesVery likely requires a maintenance visit with high priority as it is an indication there might now be a not properly disconnected socket while no plug is inserted.
connectorLockFailurePlug locking failedNoTypically caused by not fully inserted plugs, unplugging and attempting to plug again in most cases resolves the problem.
connectorLockFailureType 2 actuator stuck, cannot unlockType 2 locking actuator recoveredYesA mechanical problem may require a maintenance visit. An Unlock Connector or Hard Reset triggers another attempt to unlock.
connectorLockFailureCould not detect type 2 locking actuatorType 2 locking actuator detectedYesA mechanical problem may require a maintenance visit. A Hard Reset triggers another attempt to redetect the actuator type.
powerMeterFailureOCPP meter not communicatingOCPP meter communication recoveredYes
powerMeterFailureExternal meter not communicatingExternal meter communication recoveredNo
noErrorMeter eichrecht not supportedMeter eichrecht supportedNoMeter eichrecht not supported, connecting the Eichrecht meter is necessary for OCMF generation.Check if meter supports eichrecht (public key should be displayed in state page).
readerFailureRFID reader not communicatingRFID reader recoveredNo
highTemperatureCannot read temperature sensorTemp sensor recoveredNo
highTemperatureCannot read critical temperature sensorCritical temp sensor recoveredYes
otherErrorVoltage drop on HMICP detectedVoltage drop on HMICP recoveredNo
otherErrorLight sensor on HMICP failureLight sensor on HMICP failure solvedNo
otherErrorTemperature sensor on HMICP failureTemperature sensor on HMICP failure solvedNo
otherErrorHumidity sensor on HMICP failureHumidity sensor on HMICP failure solvedNo
otherErrorGyroscope sensor on HMICP failureGyroscope sensor on HMICP failure solvedNo
otherErrorShock sensor on HMICP failureShock sensor on HMICP failure solvedNo
otherErrorCommunication with HMICP failedCommunication with HMICP failure solvedNo
otherErrorHMICP controller failedHMICP controller failure solvedNo
highTemperatureHousing temperature too high - charging pausedHousing temp. below critical - charging resumedNo
noErrorHousing temp. approaching limit - current reducedHousing temp. back to normal - current restoredNo
highTemperatureDC wallbox temperature too high - charging pausedDC wallbox temperature below criticalNo
highTemperatureRelay temperature too high - charging pausedRelay temp. below critical - charging resumedNo
noErrorRelay temp. approaching limit - current reducedRelay temp. back to normal - current restoredNo
otherErrorTemperature reaches safety limit - emergency stopTemperature below safety limit - resumeYes
weakSignalSignalWeak:0///0SignalGood:0///0NoLow RSSI limit is 12 and high limit is 14.
otherErrorGSM SIM card is missingGSM SIM card insertedNoGSM SIM card is missing.Insert a SIM card in the dedicated slot.
otherErrorFW Update in progressFW Update finishedYesFW update command issued while update is already in progress.Try again after first command was processed. Otherwise carry out a hard reset.
otherErrorFW/USB Update failure deletedNoFirmware update failed.Try again.
noErrorUSB communication errors.USB communication working properly.NoUSB communication errors.Wait until application recovers from this error.
otherErrorThe ChargePoint is tilted.The ChargePoint no longer is tilted.YesThe ChargePoint has been tilted.A physical inspection and maintenance is required at the ChargePoint location.
otherErrorPossible CP and PR wiring issue.Possible CP and PR wiring issue is solved.YesA car is detected but no cable is detected.Check the wiring of CP and PR cables, they may be swapped or the plug may be broken.
otherErrorPR disconnected while car is connected.PR disconnection issue is solved.NoThe proximity cable is disconnected while the car is pluggedCheck the plug and socket PR contact, it may be defect. Check the internal PR wiring of the charging station and the charging cable.
otherErrorOCPP Master and Slave have different SW version.OCPP Master and Slave have same SW version.NoThe master and slave have different SW versions.Maybe the firmware update has failed or a manual update was performed incorrectly.Check what is the expected FW version and update firmware.
otherErrorRCMB measurement out of range.YesThe current transformer on the Chargepoint has a defect if this condition persists.Replace the current transformer on the ChargePoint.
otherErrorCar current is higher than expected.Car is charging at nominal current.NoThe car is charging with SOCKET_TYPE2_CURR_OVERLOAD_THRESHOLD_1% more than expected according to the signaled current. The charge point will try to solve it by decreasing the signaled currentCheck the car.
otherErrorCar current overload, charging stopped.Car is charging at nominal current again.YesThe car is charging with a too high current. Charging will be stoppedCheck the car.
connectorLockFailureActuator unlocked while chargingYesFor some reason the actuator was unplugged during charging.Verify the actuator and actuator wiring
otherErrorThe chargepoint was previously tiltedChargepoint tilted issue deletedYesThe chargepoint was previously tilted.It is not allowed to charge until the charge point is rebooted.
otherErrorNot all DLM Slaves connectedAll DLM Slaves are connected againNoSome DLM slaves are disconnected from DLM master.Reconnect the DLM slaves to the DLM master again.
otherErrorDLM Slave disconnected and not chargingDLM Slave is connected againNoThe DLM slave is disconnected from DLM master and its DisconnectedLimit is set to zero.Reconnect the DLM slave to the DLM master again or increase its DisconnectedLimit.
otherErrorUSB stick handling finishedYesUSB stick is inserted and is being handled.Wait until all operations have finished.
otherErrorPhase rotation failure.Phase rotation direction normal.YesA different phase rotation dir. has been detected from the option selected in the configuration. Phases have either been incorrectly installed, or misconfigured.Configuration has to be changed consistently according to detected phase rotation dir., or the phases have to be correctly installed. A physical inspection and maintenance may be required at the chargepoint location.
underVoltageThere is no power on mains.Grid power restored.YesNo power on mains has been detected.A physical inspection and maintenance is required at the chargepoint location.
otherErrorFailed init:NoA component or set of components failed to initialize correctly.An inspection and maintenance is required for the chargepoint, issue probably has to be escalated to be handled by a support engineer.
otherErrorState D detected, charging is pausedCar no longer in state D, charging is resumedNoCharging is paused because state D is detected.Check the reason why car goes to state D.
underVoltageLow voltage detected, charging is pausedNormal voltage detected, charging is resumedNoCharging is paused because low voltage is detected. Charging will resume one minute after the electric grid stabilizesWait until the electric grid stabilizes.
overVoltageHigh voltage detected, charging is pausedNormal voltage detected, charging is resumedNoCharging is paused because high voltage is detected. Charging will resume one minute after the electric grid stabilizesWait until the electric grid stabilizes.
otherErrorLow frequency detected, charging is pausedNormal frequency detected, charging is resumedNoCharging is paused because low frequency is detected. Charging will resume one minute after the electric grid stabilizesWait until the electric grid stabilizes.
overCurrentFailureRCD-MCB triggered from unique inputRCD-MCB from unique input reconnectedYesRCD-MCB needs to be re-armed.
noErrorUSB stick handling: Finalized - Remove USB stickUSB stick removedNoUSB stick is still inserted while all previous operations completed successfully.Remove the USB stick.
noErrorUSB stick handling failed - Remove USB stickUSB stick removedNoUSB stick is still inserted while there were errors with previous operations.Remove the USB stick and retry.
noErrorSocket type 2 plug lifetime exceededNoSocket type 2 plug should be replaced.
connectorLockFailureActuator emergency opener faultedActuator emergency opener failure solvedYesA mechanical problem may require a maintenance visit.
groundFailureGround check (PE) failedGround check (PE) failure solvedNoA wiring problem may require a maintenance visit.
underVoltageL1 voltage is missingL1 voltage is not missing (contactor opened)NoL1 line is not energized when it should since the contactor is closedVerify that the charger wiring is correctand that no RCD or MCB protection is active.
underVoltageNoError occurs if issued power line is either not connected or the varistor at this line is defective.Check varistor fault or mains outage.
otherErrorMessage queue is fullMessage queue works againYesError occurs when the parameter "OcppQueueFullAsErrorState" was set by the operator and the OCPP message queue is full and cannot store further items.Check the connection to the OCPP backend.
otherErrorInternal communication errorInternal communication error resolvedYesUnexpected internal SW communication error.A system reboot is required.
otherErrorOCPP meter failureOCPP meter failure resolvedYesOCPP meter reported a failure in the power line supply.Check the power lines voltage, frequency and current.
internalError15118 module failure15118 module failure resolvedNo15118 module failed to initialize.Reboot the chargepoint or check for hardware issues.
internalErrorQCA7000 initialization failureQCA7000 initialization failure resolvedNoQCA7000 initialization failure.Reboot the chargepoint or check for hardware issues.
weakSignaleth interface had 0 link up-down sequences.Too many eth link up-down sequences resolvedNoEthernet interface is having frequent disconnection and connections.Verify the LAN network settings and state.
noErrorSocket type 2 contactor lifetime exceededNoSocket type 2 contactor should be replaced.
underVoltageContactor not closedContactor error solvedNoContactor or main relay has failed to close or it opened during chargingVerify that the charger wiring is correctand that the relay is in good condition.
otherErrorCP ADC calibration aborted. (Value out of range)CP ADC calibration failure solvedNoCP ADC calibration was aborted due to an out of range ADC value.The board might need an inspection by a technician.
otherErrorWLAN SSID or PSK is incorrectly configuredWLAN SSID and PSK are now correctly configuredNoWLAN was enabled but the SSID or the PSK was wrong.Verify that WLAN SSID and the PSK was set correctly.
otherErrorFan defect, ventilation could not be startedFan ventilation functionality recoveredYes
otherErrorShock detectedShock is not longer detectedYes
otherErrorTilt detectedTilt is not longer detectedYes
otherErrorHumidity is too highHumidity is back to normalNo
otherErrorHMI180 temperature too lowHMI180 temperature back to normalNo
otherErrorHMI180 USB errorHMI180 USB error solvedNo
otherErrorHMI180 USB communication errorHMI180 USB communication error solvedYes
otherErrorPhytec temperature too highPhytec temperature back to normalYes
otherErrorPhytec LCD temperature too highPhytec LCD temperature back to normalYes
otherErrorPhytec LCD temperature too lowPhytec LCD temperature back to normalNo
otherErrorHMI180 Phytec communication errorHMI180 Phytec communication error solvedNo
otherErrorLED ring temperature too highLED ring temperature back to normalNo
otherErrorLED ring temperature too lowLED ring temperature back to normalNo
otherErrorLED group failureLED group failure solvedNo
otherErrorPayter temperature too highPayter temperature back to normalNo
otherErrorPayter temperature too lowPayter temperature back to normalNo
otherErrorPayter communication errorPayter communication error solvedNo
otherErrorWIFI module communication errorWIFI module communication error solvedNo
otherErrorWIFI temperature too highWIFI temperature back to normalNo
noErrorThreshold contactor cycles under load exceededThreshold contactor cycles exceeded solvedNoSocket type 2 contactor should be replaced.
otherErrorMeter is 1-phase, but system setting is 3-phase.Meter is 1-ph, but sys setting is 3-ph resolved.NoMeter is 1-phase, but system is 3-phase.Change the installation setting to 1-phase.
noErrorAuthorization failed.No
otherErrorFirmware update failed.NoFirmware update failed (internet connection?).Retry or perform a manual update.
resetFailureUnintended Reset - Power Outage?No
resetFailureTerminated transaction after reset! Power Outage?NoChargePoint rebooted while a transaction (charging) was active. Transaction was implicitely terminated.Restart the transaction.
otherErrorSlave is unavailable (disconnected from Master).NoA Slave disconnected from the master.Replace cable, repair connection, and wait until slave reconnects to master.
otherErrorDiagnostics failed.NoDiagnostics failed (internet connection?).Retry.
groundFailureRCMB error.No
evCommunicationError15118 communication error (exi decoder)No15118 communication failed
evCommunicationError15118 communication error (exi encoder)No15118 communication failed
evCommunicationError15118 communication error (TLS cert)No15118 communication failed
evCommunicationError15118 communication error (V2G session id)No15118 communication failed
evCommunicationError15118 communication error (TCP)No15118 communication failed
otherError15118 authorization failedNo15118 authorization for PnC failed. The signature validation failedInstall a valid certificate in the car and the correct root CA in the chargepoint
otherError15118 authentication failedNo15118 authentication for PnC failedInstall a valid certificate in the car and the correct root CA in the chargepoint
otherError15118 certificate installation failedNo15118 Certificate Installation failedVerify that car and backend are handling the certificates properly
noErrorSystem not yet ready.No

4. OCPP Keys

Description: This section provides details for the OCPP Keys tab extracted from the documentation HTML.

Key NameMaster/Slave ScopeOCPP standardDescriptionReboot RequiredAccessibilityTypeRange, Default or example
RCMBDeltaBothNoMinimum 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.NoR/Wuint[0..999] Def: 0
RCMBIEC62955ModeIndividualNoConfigures 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!YesREnum(0) IEC 62752
(1) IEC 62955
(2) IEC 62955 (locked)
Def: IEC 62955
RCMB_STATEIndividualNoRDC-M (RCMB) protection state
Maximum values of last transaction
Current values
NoRStringDef: "DC: OK, RDC-M (RCMB) Device Status (IEC 62955): OK
Last transactio..."
RCMBTransactionMaxRMSIndividualNoLargest RMS value measured while a transaction was in progressNoRStringDef: " 0.0"
RCMBTransactionMaxDCIndividualNoLargest DC value measured while a transaction was in progressNoRStringDef: " 0.0"
WeldCheckIndividualNoWelded 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.YesREnum(0) Disable
(1) Enabled 'Opto 1 In'
(3) Enable via weld check input 230V WITHOUT PE check
(4) Enable via weld check input 230V WITH PE check
Def: Disable
WeldCheckInTypeIndividualNoWhether the welding detection input circuit is normally closed or normally open.YesREnum(0) Normally open
(1) Normally closed
Def: Normally open
ChargePointVendorBothNoMandatory, identifies the vendor of the ChargePoint.YesRStringDef: "Bender GmbH Co. KG"
ChargePointModelNot relevantNoMandatory, identifies the model of the ChargePoint. Please note that this must not match a different model of the generation of charge controllers.YesRStringDef: "CC613_ELM4PR_M"
SSHAccessUsbIndividualNoDisables SSH access to the controller via USB.YesREnum(0) Off
(1) On
Def: On
SSHAccessWlanNetworkIndividualNoDisables SSH access to the controller via WLAN.YesREnum(0) Off
(1) On
Def: On
SSHAccessEthIndividualNoDisables SSH access to the controller via Ethernet.YesREnum(0) Off
(1) On
Def: On
SSHAccessGsmIndividualNoDisables SSH access to the controller via GSM.YesREnum(0) Off
(1) On
Def: On
InvalidRFIDFilterBothNoSet whether RFID tags with invalid UIDs shall be filtered out and thus not reported by the reader.YesR/WEnum(0) Off
(1) On
Def: On
RFIDEnableIndividualNoEnables or disables the RFID reader. Allows preventing error messages if no reader is installed.NoREnum(0) Off
(1) On
Def: On
EnforcePwdChangeBothNoForce change of default operator password on login.NoREnum(0) Off
(1) On
Def: Off
EnforceStrongLoginPwdsBothNoForce selecting a strong secure login password when changing the operator password, the installer password, or the user password.NoREnum(0) Off
(1) On
Def: Off
RFIDModeBothNoThis 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.YesREnum(0) RFID only
(1) RFID/NFC hybrid
Def: RFID only
EnforceMasterRFIDBothNoWhen 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.NoREnum(0) Off
(1) On
Def: Off
EnforceSecureRFIDBothNoThis 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).NoR/WEnum(0) Off
(1) On
Def: Off
ChargeBoxSerialNumberIndividualNoOverrides 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.YesRStringDef: "Not Set"
ChargePointSerialNumberMasterNoSet 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.YesRStringDef: "Not Set"
MasterRFIDtoRebootIndividualNoRFID tag to reboot the system if presented for 30 seconds. Disable this feature by leaving this parameter empty.NoR/WStringDef: ""
UserInstallerPasswordCheckMasterNoNoR/Wuint[0..4294967295] Def: 1
MasterRFIDstoResetIndividualNoRFID 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.NoR/WStringDef: ""
SSHClientKeyMasterNoKey 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.NoRStringDef: "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCNqOyR/bAsG3s/rcj1ub+Zbeyds7DEP..."
ErrorsListIndividualNoList of errors currently present in the ChargePoint.NoRStringDef: "No errors"
ErrorResolutionIndividualNoList of error resolutions currently present in the ChargePoint.NoRStringDef: "Error resolution will be displayed for every active error."
EventsListIndividualNoList of the last events and errors with their timestamp.NoRStringDef: "No events"
OPKGInstallExtraOptionBothNoNoR/WStringDef: ""
AuthorizationInputModeNot relevantNoSet 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.YesREnum(0) Only start
(1) Start and stop
(2) Only stop
(3) Charging while active
Def: Only start
AuthorizationInputTypeNot relevantNoSet if the authorization input switch is normally open or normally closed. Note that Scheidt&Bachmann requires this to be set to Normally open.YesREnum(0) Normally open
(1) Normally closed
Def: Normally open
loglevelBothNoLevel for the logging system. For security reasons you may be asked to re-enter your credentials to download the log.NoR/WEnum(0) LOG_LEVEL_NONE
(1) LOG_LEVEL_USER_ERR
(2) LOG_LEVEL_USER_WARN
(3) LOG_LEVEL_USER_INFO
(4) LOG_LEVEL_ERR
(5) LOG_LEVEL_WARN
(6) LOG_LEVEL_INFO
(7) LOG_LEVEL_DBG
(8) LOG_LEVEL_VDBG
(9) LOG_LEVEL_TRACE
Def: LOG_LEVEL_DBG
loglevelcomponentsBothNoThis 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=VDBGNoR/WStringDef: ""
GiroEEnableIndividualNoEnables or disables the GiroCard payment via Giro-e over OCPP. Requires a Giro-e capable OCPP backend.NoR/WEnum(0) Off
(1) On
Def: Off
PowerLineVoltageIndividualNoSingle phase RMS voltage of the power source feeding the ChargePoint in Volts. This is used for current calculation from power values from meter.YesR/Wuint[186..274] Def: 230
MasterSlaveModeNot relevantNo'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.YesREnum(0) Off
(1) Master
(2) Slave
Def: Off
LedTypeNot relevantNoType of LED device connected to the ChargePoint (if any).NoREnum(0) LED (default)
(1) LED ring device
(2) LED ring device with RFID always shown
(3) LED ring with free charging
(7) No LED
Def: LED (default)
DualLedModeNot relevantNoBehavior 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.NoREnum(0) Off
(1) On
(2) On Inverted
Def: Off
DisplayTypeNot relevantNoType of display connected to the ChargePoint (if any).NoREnum(0) Display not configured
(1) Display not in use
(2) Bender LCD-Module DPM2x16FP
Def: Display not configured
DisplayModeNot relevantNoControls 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.NoREnum(0) Main (Master)
(1) Master/Slave
Def: Main (Master)
DisplayContentSelectorTimeNot relevantNoIf enabled the display shows charging time information.NoREnum(0) Off
(1) On
Def: On
DisplayContentSelectorEnergyNot relevantNoIf enabled the display shows charging energy information.NoREnum(0) Off
(1) On
Def: On
DisplayContentSelectorPowerNot relevantNoIf enabled the display shows charging power information.NoREnum(0) Off
(1) On
Def: Off
PatternOnRelayK2Not relevantNoBehavior 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'.NoREnum(0) Disable
(1) On while charging
(2) Off while charging
(3) On while vehicle connected (S&B)
(4) Off while vehicle connected
(5) Blink pattern 1
(6) On while Inoperative
(7) On while Authorized
(8) On while Faulted
Def: Disable
DisplayLanguageIndividualNoThe language of display texts on the LCD display, if available. Only has an effect if a LCD is configured.NoR/WEnum(0) English
(1) Deutsch/German
(2) Italiano/Italian
(3) Slovenský/Slovak
(4) Multi-Language EN-DE-FR-NL
(5) SR Multi-Language EN-DE-FR-IT
Def: Multi-Language EN-DE-FR-NL
EichrechtStateIndividualNoEichrecht StateNoRStringDef: "System without Eichrecht"
OCPPSchukoNot relevantNoUse auxiliary input/output to support additional Schuko SocketYesREnum(0) Disable
(1) Enable 'Opto 1 In'
Def: Disable
EOActuatorTypeNot relevantNoConfigure the connected actuator typeYesREnum(0) Mennekes Standard
(2) Phoenix
(3) Kuester Gen2
Def: Mennekes Standard
Type2ContactorLifetimeIndividualNoMaximum number of operating cycles the contactor should be allowed to perform until a replacement is necessary.YesRuint[0..100000000] Def: 10000000
Type2PlugLifetimeIndividualNoThe maximum number of times the plug of the type2 socket can be plugged in safely..YesRuint[0..10000000] Def: 50000
SetType2PlugCyclesIndividualNoUse 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.NoR/WStringDef: ""
Type2PlugCounterNot relevantNoNumber of times the plug of the type2 socket was plugged in.NoRStringDef: "39/50,000"
SetTypeContactorCyclesIndividualNoUse 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.NoR/WStringDef: ""
ContactorCyclesType2IndividualNoThe number of times the contactor of the type 2 socket was switching on and off.NoRStringDef: "7/10,000,000"
ThresholdContactorCurrentUnderLoadIndividualNoSet threshold contactor current under load (in Amperes)YesRuint[6..80] Def: 6
ContactorCyclesUnderloadLimitIndividualNoThe maximum number of contactor cycles under load before receiving a system warningYesRuint[0..50000] Def: 6000
SetCountContactorCyclesType2UnderLoadIndividualNoUse 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.NoR/WStringDef: ""
GetCountContactorCyclesType2UnderLoadIndividualNoThe number of times the contactor was switching on and off under load.NoRStringDef: "0/6,000"
CableAttachedNot relevantNoSetting 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!YesREnum(0) Off
(1) On
Def: Off
CPDiodeDetectionIndividualNoSet this value to 'On' if you want to check before charging if the diode connected to the control pilot line is connected or not.NoR/WEnum(0) Off
(1) On
Def: On
PauseChargingStateDBothNoIf 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.NoR/WEnum(0) Off
(1) On
Def: Off
AdcCpCalibrationCfgIndividualNoThis 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.YesR/WEnum(0) Off
(1) On
(2) Recalibrate
Def: Off
CheckCarOverCurrentStopLimitBothNoWhen the charging current reported by the OCPP meter exceeds the signaled current by this percentage, charging will be stopped.YesR/Wuint[10..100] Def: 30
SocketType2StateIndividualNoState of TYPE2 socket at connector 1.NoRStringDef: "(A) Vehicle not connected
Cable attached
AMCC: (-/-/-)"
SignaledCurrentLimitIndividualNoCurrent (in Ampere) that is signaled to the vehicle via PWM.NoRStringDef: "0 A"
HardwareCurrentLimitIndividualNoMaximum current (in Amperes) the charge point hardware can supportYesRint[0..80] Def: 16
InstallationCurrentLimitIndividualNoThe 'Installation Current Limit' is the upper limit of the 'Operator Current Limit'. It must be below or equal to the 'Maximum Current' of the charge point. This parameter cannot be changed by the backend.YesRint[0..80] Def: 16
OperatorCurrentLimitIndividualNoMaximum 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 managementNoR/Wint[0..80] Def: 16
FreeChargingBothNoAllows charging without authorization via RFID or the backend. Charging is started immediately after a vehicle is connected.NoR/WEnum(0) Off
(1) On
Def: Off
CheckCarOverCurrentBothNoIf 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.NoR/WEnum(0) Off
(1) On
Def: On
RandomRestartAfterPowerLossBothNoIf 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.YesR/WEnum(0) Off
(1) On
Def: Off
PDL_PowerMasterNoPDL PowerNoR/WStringDef: ""
EnergyManInputPowerLimitCfgIndividualNoEnables energy Management from external inputYesR/WEnum(0) Disable
(1) Enable 'Opto 1 In'
Def: Disable
ChargingScheduleAllowedChargingRateUnitMasterYesList of supported quantities for use in a ChargingSchedule.NoRStringDef: "Current"
PhasesConnectedIndividualNoShows how the number of phases connected to the ChargePoint is configured.NoRStringDef: "Three-phase system"
ASKIoverOCPPAllowedIPBothNoConfigure a single IP address here that will be allowed to access the 'ASKI over OCPP-S' service. An empty field will allow no access!YesR/WStringDef: ""
ConnectorPhaseRotationBothYesNoR/WStringDef: "1.RST"
ConnectorPhaseRotationITIndividualNoNoR/WStringDef: "L1-L2"
ConnectorSwitch3to1PhaseSupportedMasterYesIf set the ChargePoint supports switching between 3 and 1 phases during a charging session.YesRbool[0..1] Def: Off
SmartChargingUseDisconnectedLimitIndividualYesIf 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.YesR/WEnum(0) Off
(1) On
Def: Off
ASKIoverOCPPMasterNoEnable 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.YesR/WEnum(0) Off
(1) On
Def: Off
EnergyManInputPowerCurrentLimIndividualNoSingle 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.YesR/Wuint[0..80] Def: 16
LaMa_ConnectionRateIndividualNoSecret key for Mennekes EnergyManager InputNoR/Wuint[0..100000] Def: 16
ConnectorPhaseRotationMaxLengthIndividualYesMaximum number of items in a ConnectorPhaseRotation Configuration Key.NoRuint[0..0] Def: 3
ChargeProfileMaxStackLevelMasterYesMax StackLevel of a ChargingProfile.NoRuint[0..0] Def: 255
ChargingScheduleMaxPeriodsMasterYesMaximum number of periods that may be defined per ChargingSchedule.NoRuint[0..0] Def: 255
MaxChargingProfilesInstalledMasterYesMaximum number of Charging profiles installed at a time.NoRuint[0..0] Def: 255
SmartChargingDisconnectedLimitIndividualNoDisconnected Upper Limit applied to SmartCharging in case the ChargePoint is disconnected from the backend.YesR/Wuint[0..999] Def: 16
RCDRESETIndividualNoRCD ResetNoR/WEnum(0) Off
(1) On
Def: Off
RCDAUTORECLOSUREBothNoAllows 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.YesR/WEnum(0) Off
(1) On
Def: Off
RCDENABLEBothNoAllows 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.YesR/WEnum(0) Off
(1) Opto input
Def: Off
SPDCFGIndividualNoAllows support for Surge Protection Devices (SPD). It must be 'Off' when there is no SPD connected to the controller.YesR/WEnum(0) Off
(1) On OPTO C6/5 (Normally closed)
(2) On OPTO C6/5 (Normally open)
Def: Off
VentHeatingCtrlModeBothNoThis parameter allows to enable the activation of an external fan or heater according to the housing temperature or vehicle state.YesR/WEnum(0) Off
(1) Status D (Ventilation Required by vehicle)
(2) Charging (Ventilation)
(3) Above threshold and charging (Ventilation)
(4) Above threshold (Ventilation)
(5) Below threshold (Heating)
Def: Off
WeldCheckAuxRelayBothNoWhen 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.NoR/WEnum(0) Off
(1) Relais 13/14
Def: Off
MonitoringRelayInputIndividualNoUse a unique input from a monitoring relay to trigger RCD/MCB.YesR/WEnum(0) Disable
(2) Enable 'Opto 1 In'
(3) Via meter
Def: Disable
RCDAUTORECLOSUREDELAYBothNoRCD auto reclosure delay in seconds.YesR/Wuint[30..1800] Def: 900
RCDAUTORECLOSUREATTEMPTSBothNoRCD auto reclosure attempts.YesR/Wuint[1..10] Def: 3
VentHeatingHystBothNoThis 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.YesRuint[0..25] Def: 4
VentHeatingTempThrBothNoTemperature threshold necessary to start or stop the fan or heater.YesRint[-40..100] Def: 85
AmbientCpuDeltaIndividualNoTemperature delta for measurements from temperature sensor. This value should be tuned according to the thermal characteristics of the charging station.NoRuint[0..150] Def: 23
LocalScheduledRebootsBothNoThe 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.YesR/Wuint[0..23] Def: 0
DaysScheduledRebootsBothNoNumber 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].NoR/Wuint[1..30] Def: 30
ReducedCurrentIndividualNoCharging current value in Ampere when temperature is above temperature threshold 1.NoRuint[6..80] Def: 16
ReducedCurrentPctIndividualNoHow much (in %) of signaled current should be applied to reduce temperature when temperature is above temperature threshold 1.NoRuint[0..100] Def: 100
TempDeltaMasterNoTemperature 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.NoRint[0..50] Def: 5
TempStopThreshold2IndividualNoTemperature threshold necessary to stop charging.NoRint[40..100] Def: 85
TempReduceThreshold1IndividualNoTemperature threshold necessary to start decreasing the current.NoRint[40..100] Def: 85
MaxTimePerSessionBothNoTime limit of the session. When Max Time limit is reached, the session is terminated and connector will be unlocked. If Backend is connected, and Time limit is reached, the transaction of the session is sent to backend with status 'SuspendedEV' followed by 'Finishing'. '0' corresponds to 'No limit'.NoR/Wuint[0..24] Def: 0
InputOutputBackendControlledModeBothNoInputs (InputOptoC65 and InputOptoC87 on CC612 or InputOpto1 and InputOpto2 on others) and output (Output1, and if present, Output2) can be controlled via a backend.YesREnum(0) Off
(1) On
Def: Off
InputChangeNotifyBackendBothNoChanges 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'.NoREnum(0) Off
(1) On
Def: Off
TamperDetectionInputEnableIndividualNoWhen enabled, the individual charge controller informs the backend with a status notification that the tamper detection sensor has been triggered.YesREnum(0) Off
(1) On Opto1 In (Normally closed)
(2) On Opto1 In (Normally open)
Def: Off
DataTransferTariffUsageBothNoEnables 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.NoR/WEnum(0) Off
(1) On
Def: Off
AuthorizeRemoteTxRequestsBothYesThis 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.YesR/Wbool[0..1] Def: On
AllowOfflineTxForUnknownIdBothYesThis 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.NoR/WEnum(0) Off
(1) On
(2) ImmediatelyWhenPlugged
Def: Off
InfoStatusNotificationsBothNoThis 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.NoR/WEnum(0) Off
(1) On
Def: On
ErrorStatusNotificationsBothNoThis 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.YesR/WEnum(0) Off
(1) On
Def: On
UsbErrorStatusNotificationsIndividualNoThis parameter determines whether USB communication errors between master and slave are reported to backend.YesR/WEnum(0) Off
(1) On
Def: Off
StatusNotificationStrategyBothNoThis 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.YesR/WEnum(0) Occupied on Authorized/Plugged
(1) Occupied on Charging
Def: Occupied on Charging
DisplayDisconnectAsErrorMasterNoParameter that determines whether an error is signaled to the user when the backend connection is interrupted.YesR/WEnum(0) Off
(1) On
Def: Off
AuthorizationCacheEnabledMasterYesEnables 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.NoR/Wbool[0..1] Def: On
idTagLetterCaseBothNoParameter that makes the RFID tag management configurable to upper or lower case.YesR/WEnum(0) Lower Case
(1) Upper Case
(2) Lower Case Reversed Byte Order
(3) Upper Case Reversed Byte Order
Def: Lower Case
StopTransactionOnEVSideDisconnectBothYesWhen set to 'On' the Charge Point will stop a transaction when the cable is unplugged from the EV.NoRbool[0..1] Def: On
UnlockConnectorOnEVSideDisconnectBothYesWhen set to 'On' the Charge Point will unlock the cable on Charge Point side when the cable is unplugged at the EV.NoRbool[0..1] Def: On
ReserveConnectorZeroSupportedMasterYesIf set to 'On' the ChargePoint supports reservations on connector 0.NoRbool[0..1] Def: On
FreeChargingModeBothNoSets 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.YesR/WEnum(0) No OCPP
(1) With OCPP status notif without auth
(2) With OCPP status notif with auth
(3) With OCPP Full fixed RFID with auth
(4) With OCPP Full fixed RFID without auth
(5) With OCPP Full any RFID
Def: No OCPP
AllowLongOcppGetConfKeysBothNoAllows OCPP keys in get configuration command to be longer than 500 characters.YesR/WEnum(0) Off
(1) On
Def: Off
OcppGetConfBoolIsIntBothNoIf 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.NoR/Wbool[0..1] Def: Off
StopTransactionOnInvalidIdIndividualYesDetermines if the ChargePoint will stop an ongoing transaction when it receives a non-Accepted authorization status in a StartTransaction response.NoR/Wbool[0..1] Def: On
ChargeBoxIdentityIndividualNoID that is sent to the backend and used by the backend to identify the ChargePoint.YesR/WStringDef: "+4983900000000001"
FirmwareVersionIndividualNoFirmware version running on the ChargePoint.NoRStringDef: "5.33.5-21150"
RCMBVersionIndividualNoVersion of the RCMB module connected to the ChargePoint.NoRStringDef: "D0660, V2.01"
SupportedFeatureProfilesMasterYesList of supported Feature Profiles. Possible profile identifiers: Core, FirmwareManagement, LocalAuthListManagement, Reservation, SmartCharging and RemoteTrigger.NoRStringDef: "Core,FirmwareManagement,LocalAuthListManagement,Reservation,SmartChar..."
RfidTagFreeChargingIndividualNoRFID 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'YesR/WStringDef: "freecharging"
BackendConnectionTimeoutMasterNoThe 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.YesR/Wuint[3..300] Def: 60
ConnectionTimeOutBothYesInterval (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).YesR/Wuint[4..300] Def: 45
NumberOfConnectorsMasterYesNumber of physical charging connectors of this Charge Point.NoRuint[0..0] Def: 1
GetConfigurationMaxKeysMasterYesMaximum number of requested configuration keys in a GetConfiguration.req PDU.NoRuint[0..0] Def: 352
TransactionMessageAttemptsIndividualYesSets how often the ChargePoint tries to submit a transaction-related message when the backend fails to process it. 0 means infinite attempts.YesR/Wuint[0..5] Def: 5
EichrechtTransactionMessageAttemptsIndividualNoSets 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.YesR/Wint[-1..5] Def: 0
TransactionMessageRetryIntervalIndividualYesSets how long the ChargePoint will wait before resubmitting a transaction-related message that the backend failed to process.YesR/Wuint[0..1000] Def: 0
ResetRetriesIndividualYesNumber of times to retry an unsuccessful reset of the ChargePoint.YesR/Wuint[0..100] Def: 100
OcppQueueFullAsErrorStateBothNoWhen set, a full OCPP message queue will cause an error state. Charging will be terminated.YesR/WEnum(0) Off
(1) On
Def: Off
LocalPreAuthorizeMasterYesSets if the Charge Point, when online, will start transactions for locally authorized identifiers without requesting an Authorize.conf from the Central System.NoR/Wbool[0..1] Def: On
LocalAuthorizeOfflineMasterYesSets if the Charge Point, when offline, will start transactions for locally authorized identifiers.NoR/Wbool[0..1] Def: On
ForceHeartbeatRequestMessagesNot relevantNoSets if the Charge Point should send OCPP Heartbeat request messages despite other messages being sent.YesR/WEnum(0) Off
(1) On
Def: On
RetransmitMeterValuesBothNoIf enabled, MeterValue messages are retransmitted on errors.NoR/WEnum(0) Off
(1) On
Def: On
UPnPUUIDIndividualNoThe UPnP UUID that this ChargePoint uses when announcing its presence on the local network. Only used if connected to a local network.YesRStringDef: "12b3074f-5f49-4368-b4d7-fe2ae0663b1c"
HeartbeatIntervalMasterYesThe 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).NoR/Wint[10..86400] Def: 240
StopTransactionModeUnplugBothNoThis 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.YesR/WEnum(0) Normal
(1) Stop only by unplugging
(2) Unlock only by RFID/RemoteStop
(3) Normal + Mode D
Def: Normal
SupportedFileTransferProtocolsMasterYesList of supported file transfer protocols: FTP, FTPS, SCP, HTTP and HTTPSNoRStringDef: "FTP, FTPS, SCP, HTTP, HTTPS"
LightIntensityBothYesValue range is 0 to 100NoR/Wuint[0..100] Def: 100
StatusNotificationWebuiLoginBothNoStatus notification will be sent to backend in case of login success/failure for webui.NoR/WEnum(0) Off
(1) On
Def: Off
USBFieldEngineerBothNoAllow getting diagnostics and configuration of the ChargePoint via USB stick.YesR/WEnum(0) Off
(1) On
Def: On
USBConfigUpdateBothNoAllow update of the charge point configuration via USB stick.YesR/WEnum(0) Off
(1) On
Def: On
USBFirmwareUpdateBothNoAllow update of the charge point firmware via USB stick.YesR/WEnum(0) Off
(1) On
Def: On
LocalAuthListEnabledMasterYesSelects if the Local Authorization List is enabledNoR/Wbool[0..1] Def: Off
LocalAuthListMaxLengthMasterYesMaximum number of identifications that can be stored in the Local Authorization ListNoRuint[0..1000000] Def: 1000000
SendLocalListMaxLengthMasterYesMaximum number of identifications that can be send in a single SendLocalList.reqNoR/Wuint[0..45000] Def: 45000
fllMasterNoLocal whitelist of RFIDs independent of a backend connection.NoR/WEnum(0) Off
(1) On
Def: Off
fllUseOcppStartStopBothNoSend OCPP Start/Stop transaction for authorizations from the local white list.NoR/WEnum(0) Off
(1) On
Def: On
ConnectionTypeMasterNoThe 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.YesR/WEnum(0) No Backend
(1) GSM
(2) Ethernet
(3) USB
(4) WLAN
Def: No Backend
DataConsumptionMasterNoData Consumption (in bytes) for the running month.NoR/Wuint[0..9223372036854775807] Def: 0
DataConsumptionLastMonthMasterNoData Consumption (in bytes) for the previous month.NoR/Wuint[0..9223372036854775807] Def: 0
InterfacesListMasterNoList of interfaces and their IPsNoRStringDef: "eth0: [E0:AE:B2:02:E9:8F] IP: 10.13.208.20 (ocpp)"
APNMasterNoAccess Point Name of the mobile network to be used when establishing connections to the backend system via the built-in modem.YesR/WStringDef: ""
ModemNetworkSelModeMasterNoIn '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.YesR/WEnum(0) Auto
(1) Manual
(2) Manual/Auto
Def: Auto
ModemNetworkTypeMasterNoThe technology to be used to access the network 2G (GSM), 3G (UTRAN) or 4G (LTE). In auto mode the modem will choose the technology.YesR/WEnum(0) Auto
(1) 2G
(2) 3G
(3) 4G
Def: Auto
ModemNetworkOperFmtMasterNoIndicates 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).YesR/WEnum(0) Alphanumeric Long
(1) Alphanumeric Short
(2) Numeric
Def: Alphanumeric Short
ScanNetworkOperatorsMasterNoDetermines 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.YesR/WEnum(0) Off
(1) On
Def: Off
APNUsernameMasterNoUsername to be used for authenticating with the Access Point of the mobile network for connecting with the backend system.YesR/WStringDef: ""
APNPasswordMasterNoPassword to be used for authenticating with the Access Point of the mobile network for connecting with the backend system.YesR/WStringDef: ""
Req3GNetworkOperatorMasterNoThe name of the network operator to be used in manual 'Network selection mode'.YesR/WStringDef: ""
SIMPINMasterNoPIN number that should be used to unlock the SIM card. This number is only used if the SIM card requires a PIN number.YesR/WStringDef: ""
LASTWRONGSIMPINMasterNoThe wrong PIN number that was used last time.YesR/WStringDef: ""
GSMPPPMTUMasterNoMaximum transmission unit size for GSM connections (in bytes)(valid value range: 68 - 1492).YesR/WStringDef: ""
ModemNetworkStateMasterNoThe current network registration mode of the modem which informs about the technology (2G, 3G, 4G) and about the registration (home network, roaming...)NoREnum(0) Disable
(1) Enable
(2) Enable with location
(3) Not Available
Def: Not Available
OperatorSelectionModeMasterNoOperator Selection Mode, Auto or Manual...NoREnum(0) Automatic
(1) Manual
(2) Deregister from network
(3) Set Only
(4) Manual/Automatic
(5) Not Available
Def: Not Available
GSMStateMasterNoRegistration state to the mobile network.NoREnum(0) Not Registered and Not Searching
(1) Registered at Home Network
(2) Not Registered and Searching
(3) Registration Denied
(4) Unknown
(5) Registered (Roaming)
(6) Not Available
Def: Not Available
IMSIMasterNoInternational 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.NoRStringDef: ""
IMEIMasterNoInternational 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.NoRStringDef: ""
ICCIDMasterNoIntegrated Circuit Card Identifier (ICCID) of the SIM card inserted into the built-in modem.NoRStringDef: ""
LAIMasterNoLocation Area Identity (LAI), composed of Mobile Country Code (MCC), Mobile Network Code (MNC) and Location Area Code (LAC).NoRStringDef: ""
Used3GNetworkOperatorMasterNoName of the network operator the built-in modem is currently connected to.NoRStringDef: ""
AvailableNetworksMasterNoList 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.NoRStringDef: ""
MODEMNETSTATEMasterNoShow at which state in the connection sequence the modem is currently operating. Show OK when connected. Additionally, APN session duration and traffic are shown.NoRStringDef: "Not available"
ModemInfoMasterNoShows the modem manufacturer, model and firmware revision.NoRStringDef: "Not available"
ModemAccessTechnologyMasterNoShows which access technology (2G, 3G, 4G) the modem is currently using.NoRStringDef: ""
ModemLastConnErrorMasterNoReason for the last modem APN connection failureNoRStringDef: ""
RSSIMasterNoReceived 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.NoRStringDef: "0 (Extremely low)"
MCCMasterNoMobile Country Code as determined from the SIM card. This tells you which country your SIM card comes from.NoRuint[0..0] Def: 4294967295
MNCMasterNoMobile Network Code as determined from the SIM card. This tells you which mobile network operator your SIM card comes from.NoRuint[0..0] Def: 4294967295
LACMasterNoLocation Area Code as reported by the built-in modem, this value can be used to determine the location of the ChargePoint.NoRuint[0..0] Def: 4294967295
CellIDMasterNoCell ID as reported by the built-in modem, this value can be used to determine the location of the ChargePoint more accurately.NoRuint[0..0] Def: 4294967295
GSMStateInfoMasterNoStatus 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).NoRStringDef: "Unknown APN (Not Available
NetworkConfigModeMasterNoMode 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.YesR/WEnum(0) Auto (DHCP client)
(1) Static
(2) DHCP server
Def: Auto (DHCP client)
StaticNetworkConfigAddressMasterNoStatic LAN IP of the ChargePoint.YesR/WStringDef: "192.168.0.100"
StaticNetworkConfigNetmaskMasterNoNetmask to use for the LAN of the ChargePoint.YesR/WStringDef: "255.255.255.0"
StaticNetworkConfigDNSMasterNoDNS server to use for the LAN of the ChargePoint.YesR/WStringDef: "8.8.8.8"
SSLModeClientMasterNoAllows to set how strict SSL authentication is, from no authentication (encryption only) to full authentication.YesR/WEnum(0) Normal SSL Auth
(1) Allow expired certificate
(2) Skip host check
(3) Allow expired certificate and skip host check
(4) Encrypt only - No authentication
Def: Encrypt only - No authentication
WANRouterInterfaceMasterNoSelects the WAN (GSM/Ethernet/WLAN) interface.YesR/WEnum(0) GSM
Def: GSM
WANRouterMasterNoEnables access from LAN interfaces to the selected WAN (GSM/Ethernet/WLAN) interface. This will also enable the DNS forwarder.YesR/WEnum(0) Off
(1) On
Def: Off
OCPPModeMasterNoThis 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.YesR/WEnum(0) OCPP-J 1.6
(2) OCPP-B 1.5
(3) OCPP-B 1.6
Def: OCPP-J 1.6
ConnSettingsFallbackIndividualNoRestores last good connection settings when failed to reconnect to the backend after a reboot.YesR/WEnum(0) Off
(1) On
Def: Off
HostnameBinaryOCPPMasterNoThe 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.YesR/WStringDef: "be.elinc.de"
OCPPBackendJSONURLMasterNoThe 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.YesR/WStringDef: "ws://be.elinc.de:8080/OCPPJProxyQA/v16/"
WebsocketsProxyURLMasterNoSpecify the websockets proxy to connect to in the format HOST:PORT, whereby PORT is optional and set to 80 when not specified.YesR/WStringDef: ""
HTTPBasicAuthPasswordMasterNoThe password to be used for HTTP Basic Authorization. If left empty, HTTP Basic Authorization is not used.YesR/WStringDef: ""
OcppCertificateMasterNoCertificate used for SSL connections to the backend.NoR/WStringDef: ""
OcppCSRMasterNoCertificate signing request (for OCPP) in PEM format that corresponds to the private key this charge point generated upon provisioning.NoRStringDef: "-----BEGIN CERTIFICATE REQUEST-----MIIBFjCBvAIBAjBaMRAwDgYDVQQDDAdaW..."
OcppUserCaCertificateMasterNoUser CA Certificate (OCPP).NoR/WStringDef: ""
NetworkConfigHostnameMasterNoNetwork hostname used for DHCP and mDNS.YesR/WStringDef: ""
StaticNetworkConfigGatewayMasterNoGateway to use for the LAN of the ChargePoint.YesR/WStringDef: "192.168.0.1"
PortBinaryOCPPMasterNoTCP port of the proxy server for binary OCPP communication with the backend.YesR/Wuint[1..65535] Def: 444
RegenerateOcppCertAndKeyMasterNoTrigger Regeneration of Private Key and Self Signed Certificate for OCPP.NoR/WStringDef: ""
TcpWatchdogTimeoutIndividualNoThis 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.YesR/Wuint[0..100000] Def: 10800
NetworkConfigDHCPRetriesMasterNoDHCP request number of retries before giving up.YesR/Wuint[0..100000] Def: 10
NetworkConfigDHCPTimeoutMasterNoDHCP request timeout in seconds.YesR/Wuint[0..100000] Def: 10
NetworkConfigDHCPDelayMasterNoDHCP request delay between multiple requests in seconds.YesR/Wuint[0..100000] Def: 10
WebSocketPingIntervalMasterYesWebSockets 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.NoR/Wuint[0..100000] Def: 0
OcppConStrictTlsMasterNoIf '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.YesR/WEnum(0) All ciphers
(1) Only secure ciphers
Def: All ciphers
WLANSSIDMasterNoSSID of the WLAN the ChargePoint tries to connect to.NoR/WStringDef: ""
WLANPasswordMasterNoPassword of the WLAN the ChargePoint connectsto. The Chargepoint automatically chooses thecorrect encryption method of the WLAN.NoR/WStringDef: ""
WLANStaticNetworkConfigAddressMasterNoStatic WLAN IP of the ChargePoint.YesR/WStringDef: "192.168.1.100"
WLANStaticNetworkConfigNetmaskMasterNoNetmask to use for the WLAN of the ChargePoint.YesR/WStringDef: "255.255.255.0"
WLANStaticNetworkConfigGatewayMasterNoGateway to use for the WLAN of the ChargePoint.YesR/WStringDef: "192.168.1.1"
WLANStaticNetworkConfigDNSMasterNoDNS server to use for the WLAN of the ChargePoint.YesR/WStringDef: "8.8.8.8"
WLANEnabledMasterNoEnable or disable WLAN.NoR/WEnum(0) Off
(1) On
Def: On
WLANNetworkConfigModeMasterNoNetwork 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).YesR/WEnum(0) Auto (DHCP client)
(1) Static
Def: Auto (DHCP client)
WLANNetworkConfigDHCPRetriesMasterNoNumber of DHCP requests sent before giving up on the DHCP server.NoR/Wuint[0..100000] Def: 10
WLANNetworkConfigDHCPTimeoutMasterNoDHCP request timeout in seconds.NoR/Wuint[0..100000] Def: 10
WLANNetworkConfigDHCPDelayMasterNoDHCP request delay (in seconds) between multiple requests .NoR/Wuint[0..100000] Def: 10
TcpdumpInterfaceIndividualNoThe type of interface we want to dump packet data into file. Choose 'Any' to listen on any network interface.NoR/WEnum(1) Backend Host
(0) Any
(3) GSM
(2) Ethernet
(4) USB
(5) WLAN
Def: Any
TcpdumpIndividualNoSwitch '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.NoR/WEnum(0) Off
(1) On
Def: Off
Config15118BothNoHigh 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. Configuration is only possible if output used for phase switching relay is set to 'Off'.YesR/WEnum(0) Off
(1) On (with PlugNCharge)
(2) On (no PlugNCharge)
Def: Off
SeccCertExpireDate15118IndividualNoSupply 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).NoRStringDef: "Not Available"
Log15118BothNoEnable the creation of the '15118_log.csv' file with the input and output exi stream messages.YesR/WEnum(0) Off
(1) On
Def: Off
MACEVCCIDPrefixBothNoThis prefix will be inserted in the EV's MAC address when used as authorization ID against the backend or local whitelist for autocharge.YesR/WStringDef: ""
EVMACAddrIndividualNoEV's MAC address.NoRStringDef: ""
autochargeidBothNoThis ID will be used for authorization in case the EV failed to communicate with the EVSE or does not support autocharge.YesR/WStringDef: "autochargeid"
AutochargeBothNoAutocharge 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.YesR/WEnum(0) Off
(1) On
(2) On (Fixed ID)
Def: Off
DepartureTimeIndividualNoUsed to indicate when the vehicle intends to finish the charging process.NoRStringDef: "Not Available"
EAmountIndividualNoAmount 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.NoRStringDef: "Not Available"
EVSEMaxCurIndividualNoValue sent to the EV on Charging Status messages during the charging loop.NoRStringDef: "Not Available"
SeccLeafSubjectCommonNameBothNoCommon Name of the SECC leaf certificate(s). It must be a SECCID.NoR/WStringDef: "DE-EBE-S-CHANGEME0000000000000000000000000000001"
SeccLeafSubjectCountryBothNoCountry of the SECC (EVSE) leaf certificate. Indicates in which country the CPO operates. Example: DENoR/WStringDef: "DE"
SeccLeafSubjectOrganizationBothNoOrganization of the SECC (EVSE) leaf certificate. Indicates which CPO operates this EVSE. Example: Hubject GmbHNoR/WStringDef: "Bender GmbH Co. KG"
ConnectorEvseIdsBothNoComma separated EVSEIDs for OCPP connectors starting with connector 1 in one string.YesR/WStringDef: ""
CertificateStoreMaxLengthBothYesMaximum number of Root/CA certificates that can be installed in the Charge Point.YesRuint[0..50] Def: 50
CentralContractValidationAllowedBothYesIf 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.YesR/Wbool[0..1] Def: On
ContractValidationOfflineBothYesIf this variable is true, then the Charge Point will try to validate a contract certificate when it is offline.YesR/Wbool[0..1] Def: On
ISO15118PnCEnabledBothYesIf 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.NoR/Wbool[0..1] Def: Off
P15118ConStrictTlsMasterNoIf '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.YesR/WEnum(0) All ciphers
(1) Standard
Def: Standard
P15118EVSlacReqTimeoutBothNoThis 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.YesR/Wint[1..50] Def: 7
OCPPMeterTypeIndividualNoType 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.YesREnum(73) eHZ Meter via USB
(75) eHZ-B Meter via USB
(6) Modbus Meter ABB
(47) Modbus ABB EV3
(44) Modbus Berg B23
(43) Modbus Berg BME 461
(19) Modbus TQ EM300-LR
(41) Modbus TQ EM410/EM420
(25) Modbus TQ EM300-LR (TCP)
(42) Modbus TQ EM410/EM420 (TCP)
(81) Modbus IPD Control (TCP)
(86) Modbus Meter Carlo Gavazzi EM111/112
(20) Modbus Meter Carlo Gavazzi EM200
(29) Modbus Meter Carlo Gavazzi EM210
(21) Modbus Meter Carlo Gavazzi EM340
(37) Modbus DZG DVH4013
(7) Modbus Meter Eastron SDM630
(58) Modbus Eastron SDM230
(8) Modbus Eastron SDM120_220
(39) Modbus Eastron SDM72D
(68) Modbus Eastron SDM72D-M-V2
(32) Modbus ECS M3PRO
(54) Modbus ECS M3PRO (TCP)
(13) Modbus Meter Finder
(12) Modbus Meter Garo EM270
(10) Modbus Meter Garo GNM1D
(9) Modbus Meter Garo GNM3D
(22) Modbus Meter Garo GNM3T
(28) Modbus Meter Garo GNM3TD
(11) Modbus Meter Garo GM3T
(80) Modbus Meter Garo GMI3D-LP
(38) Modbus Gossen Metrawatt EM2289
(27) Modbus Hager ECR380D
(23) Modbus IME CE4DMID31
(87) Modbus IME CE4DF3DTMID
(15) Modbus Inepro PRO1_2
(16) Modbus Inepro PRO380
(84) Modbus Wago 879-3000
(40) Modbus Iskra WM3M6
(78) Modbus Iskra IE38M
(79) Modbus Meter Finder 7M38
(33) Modbus Janitza UMG 512/96 PRO
(34) Modbus Janitza UMG 512/96 PRO (TCP)
(85) Modbus Janitza UMG 604 PRO (TCP)
(35) Modbus Janitza UMG 605 PRO
(36) Modbus Janitza UMG 605 PRO (TCP)
(64) Modbus NZR EcoCount S85/SL85
(17) Modbus Optec
(45) Modbus Phoenix Contact EEM-EM357
(30) Modbus Phoenix Contact EEM-MB371 (TCP)
(14) Modbus Saia ALE3
(83) Modbus Schneider Generic (TCP)
(82) Modbus Schneider Generic
(31) Modbus Schneider iEM3555
(26) Modbus Siemens 7KM2200 (TCP)
(24) Modbus Siemens 7KT1666
(49) Modbus YTL DTS353F
(50) EV Optimizer
(53) Modbus SELEC EM2M-1P-C-100A
(55) Modbus Lovato DMED 301
(56) Modbus Eetarp GEM630
(57) Modbus Eetarp GEM230
(65) Modbus DZG DWH4113
(66) Modbus ABB D1M
(67) Modbus ABB D1M (TCP)
(60) ER Eastron SDM630-EV
(61) ER NZR EcoCount SL+SC 85
(63) ER NZR EcoCount SL+S 85
(62) ER Iskra WM3M4C
(69) ER EMH iML
(1) S0 Meter 'Opto 1 In'
(72) Modbus Eichrecht
(3) No Meter
Def: No Meter
SecondMeterTypeMasterNoEnergy 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.YesR/WEnum(77) WiMOD IR Reader USB stick
(6) Modbus Meter ABB
(47) Modbus ABB EV3
(44) Modbus Berg B23
(43) Modbus Berg BME 461
(19) Modbus TQ EM300-LR
(25) Modbus TQ EM300-LR (TCP)
(41) Modbus TQ EM410/EM420
(42) Modbus TQ EM410/EM420 (TCP)
(81) Modbus IPD Control (TCP)
(86) Modbus Meter Carlo Gavazzi EM111/112
(20) Modbus Meter Carlo Gavazzi EM200
(29) Modbus Meter Carlo Gavazzi EM210
(21) Modbus Meter Carlo Gavazzi EM340
(7) Modbus Meter Eastron SDM630
(58) Modbus Eastron SDM230
(8) Modbus Eastron SDM120_220
(39) Modbus Eastron SDM72D
(68) Modbus Eastron SDM72D-M-V2
(32) Modbus ECS M3PRO
(54) Modbus ECS M3PRO (TCP)
(13) Modbus Meter Finder
(12) Modbus Meter Garo EM270
(10) Modbus Meter Garo GNM1D
(9) Modbus Meter Garo GNM3D
(22) Modbus Meter Garo GNM3T
(28) Modbus Meter Garo GNM3TD
(11) Modbus Meter Garo GM3T
(80) Modbus Meter Garo GMI3D-LP
(27) Modbus Hager ECR380D
(23) Modbus IME CE4DMID31
(87) Modbus IME CE4DF3DTMID
(15) Modbus Inepro PRO1_2
(16) Modbus Inepro PRO380
(84) Modbus Wago 879-3000
(40) Modbus Iskra WM3M6
(78) Modbus Iskra IE38M
(79) Modbus Meter Finder 7M38
(33) Modbus Janitza UMG 512/96 PRO
(34) Modbus Janitza UMG 512/96 PRO (TCP)
(85) Modbus Janitza UMG 604 PRO (TCP)
(35) Modbus Janitza UMG 605 PRO
(36) Modbus Janitza UMG 605 PRO (TCP)
(64) Modbus NZR EcoCount S85/SL85
(17) Modbus Optec
(45) Modbus Phoenix Contact EEM-EM357
(30) Modbus Phoenix Contact EEM-MB371 (TCP)
(14) Modbus Saia ALE3
(83) Modbus Schneider Generic (TCP)
(82) Modbus Schneider Generic
(31) Modbus Schneider iEM3555
(26) Modbus Siemens 7KM2200 (TCP)
(24) Modbus Siemens 7KT1666
(49) Modbus YTL DTS353F
(51) Modbus Sunspec Meter
(52) Modbus Sunspec Meter (TCP)
(50) EV Optimizer
(53) Modbus SELEC EM2M-1P-C-100A
(55) Modbus Lovato DMED 301
(56) Modbus Eetarp GEM630
(57) Modbus Eetarp GEM230
(59) Modbus Temco Controls SPM1-XX0-AC
(88) SMA Commercial Energy Meter (TCP)
(66) Modbus ABB D1M
(67) Modbus ABB D1M (TCP)
(1) S0 Meter 'Opto 1 In'
(3) No Meter
Def: No Meter
OCPPViaLocalNetworkBothNoIf 'On' is selected, the minimum value of parameter 'Meter Value Sample Interval (OCPP)' is reduced from '10' to '1'.NoR/WEnum(0) Off
(1) On
Def: Off
MeterValueSampleIntervalBothYesInterval 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.NoR/Wuint[0..99999] Def: 0
MeterValueSampleModeBothNoAccording 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.NoR/WEnum(0) Whole transaction
(1) Contactor closed
(2) Current flow only
Def: Whole transaction
ClockAlignedDataIntervalBothYesInterval 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.YesR/Wuint[0..4294967295] Def: 0
ClockAlignedMeterRandomSendDelayBothNoThe 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.YesR/Wuint[0..4294967295] Def: 10
MeterValuesAlignedDataBothYesComma-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'.NoR/WStringDef: "Energy.Active.Import.Register"
MeterValuesSampledDataBothYesComma-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'.NoR/WStringDef: "Energy.Active.Import.Register"
StopTxnSampledDataBothYesNot supported (included for compatibility).NoR/WStringDef: ""
StopTxnAlignedDataBothYesNot supported (included for compatibility).NoR/WStringDef: ""
SecondMeterIPAddressMasterNoSets the IP address of the second meter.YesR/WStringDef: ""
SecondMeterTCPPortNumberMasterNoSpecifies the TCP port of the second meter.YesR/Wuint[0..65535] Def: 502
MeterRestrictSecondaryTypesNot relevantNoShow complete list with all meter types for load management or limit list to meter models with Modbus TCP.YesREnum(0) All meter types
(1) Modbus TCP meters only
Def: All meter types
RestartTransAfterPowerLossBothNoEnable 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.YesR/WEnum(0) Off
(1) On
(2) On (BYES specific)
Def: Off
CurrentDirSecondL1IndividualNoIf set to 'Inverted', the current and power value reported by the second meter in line 1 will be inverted in sign.YesR/WEnum(0) Standard
(1) Inverted
(2) Suppress-signed
Def: Standard
CurrentDirSecondL2IndividualNoIf set to 'Inverted', the current and power value reported by the second meter in line 2 will be inverted in sign.YesR/WEnum(0) Standard
(1) Inverted
(2) Suppress-signed
Def: Standard
CurrentDirSecondL3IndividualNoIf set to 'Inverted', the current and power value reported by the second meter in line 3 will be inverted in sign.YesR/WEnum(0) Standard
(1) Inverted
(2) Suppress-signed
Def: Standard
WrittenOfferAddressBothNoConfigures 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.)NoRStringDef: "Ebee Smart Technologies GmbH, Torgauer Str. 12-15 (Haus 4), 10829 Ber..."
ManufacturerURLMasterNoConfigures the uniform resource locator (URL) of the manufacturer. The manufacturer URL is used by various network services such as the SEMP interface.NoRStringDef: "https://www.bender.de"
AuthorizationInputNot relevantNoInput 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.YesREnum(0) Disable
(1) Enable 'Opto 1 In'
Def: Disable
RestInterfaceEnableBothNoThis 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.YesR/WEnum(0) Disabled
(1) Enabled (with UID)
(2) Enabled (without UID)
Def: Disabled
DlmHierarchicalModeMasterNoIf 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 coordinatorYesR/WEnum(0) Disabled
(1) Enabled (with local MQTT broker)
(2) Enabled (with remote MQTT broker)
Def: Disabled
DlmcAddressMasterNoThis unique address identifies this controller in the hierarchical DLM network. The schema has to be the equivalent to the hierarchy in the constraints for this hierarchical DLM network.YesR/WStringDef: ""
DlmcMqttBrokerAddressMasterNoThe 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.YesR/WStringDef: ""
DlmcMqttBrokerPortMasterNoThe port on which this controller connects to the MQTT broker. The default is 8883.YesR/Wuint[1024..65535] Def: 8883
DlmcMaximumFallbackCurrent1
DlmcMaximumFallbackCurrent2
DlmcMaximumFallbackCurrent3
MasterNoWhen the connection to the DLM coordinator is lost then this fallback current (L1/L2/L3) [A] is set for the DLM masterYesR/WTriple[0..10000] Def: 20:20:20
DlmcPublishConstraintsMasterNoWhen enabled the constraints will be published to the MQTT brokerYesR/WEnum(0) Off
(1) On
Def: Off
DlmStateIndividualNoDLM StateNoRStringDef: "Disabled"
DlmModeIndividualNoSpecifies 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!YesR/WEnum(0) Disabled
(1) DLM Master (With internal DLM-Slave)
(2) DLM Master (Standalone)
(3) DLM Slave (Master-Auto-Discovery)
(4) DLM Slave (Master-Fixed-IP)
Def: Disabled
DlmSolarMode_dlmMasterNoThis DLM feature allows EVs on a group of DLM clients to be charged with excess PV power. Activate solar mode on one or more participating DLM clients. The function requires a meter at the grid connection point or at the solar inverter. In 'PV surplus' mode, the EV is charged when there is enough surplus power to charge at the defined minimum current. EVs in this mode charge mostly without energy from the grid. The 'PV surplus + grid support' mode uses a defined power contribution from the grid to enable charging when PV production is insufficient. This allows the vehicle to be charged primarily with self-produced energy.NoR/WEnum(0) DLM standard
(1) PV surplus
(3) PV surplus + grid support
Def: DLM standard
DlmDiscoveryNetworkIdMasterNoSeveral DLM groupings might coexist in one physical LAN. In case of DLM Master-Auto-Discovery, they are distinguished by Master-Auto-Discovery Network Id.YesR/Wuint[0..255] Def: 0
DlmMasterIpMasterNoDLM Master IP which is used for DLM-Slaves configured with Master-Fixed-IP. Additionally the connection port can be specified (IP[:port]).YesR/WStringDef: ""
DlmTimeTableScheduleRandomizationNot relevantNoDelay 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:39NoR/Wuint[0..1800] Def: 0
DlmPhase1Limit
DlmPhase2Limit
DlmPhase3Limit
MasterNoOverall current limit for DLM available for distribution to EVs.YesR/WTriple[0..10000] Def: 16:16:16
DlmOperatorPhase1Limit
DlmOperatorPhase2Limit
DlmOperatorPhase3Limit
MasterNoOperator 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'.NoR/WTriple[0..10000] Def: 16:16:16
DlmExtMeterMainDistributionLimitPhase1
DlmExtMeterMainDistributionLimitPhase2
DlmExtMeterMainDistributionLimitPhase3
MasterNoCurrent 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.YesR/WTriple[0..10000] Def: 100💯100
DlmExtLoadHeadroomPhase1
DlmExtLoadHeadroomPhase2
DlmExtLoadHeadroomPhase3
MasterNoSafety margin to avoid transient overload situations. The algorithm will keep headroom towards 'Main Distribution Limit'NoR/WTriple[0..10000] Def: 0:0:0
DlmExtLoadAvgLenMasterNoMeter values will be averaged in order to avoid transients.YesR/Wuint[2..3600] Def: 5
DlmDisconnectedLimitBothNoCurrent limit when disconnected from DLM network.YesR/Wuint[0..100] Def: 6
DlmMinCurrentRatingBothNoMinimum current limit that charging should not go below.YesR/Wuint[6..100] Def: 6
DlmSlaveSolarEnabledBothNoThis parameter is used to signal to the DLM master that the charging station is participating in solar charging. The DLM master then checks whether there is sufficient excess PV power in the current solar charging mode to charge the vehicles connected to the station. Participation in solar charging can be terminated during a charging process if desired (setting: “Off”). In this case, the normal DLM algorithm is applied.NoR/WEnum(0) Off
(1) On
Def: Off
DlmCurrImbalanceLimMasterNoMaximum allowed phase imbalance. DLM will not exceed the 'Current Imbalance Limit' between phases when assigning current to EVs.YesR/Wuint[0..255] Def: 20
DlmExtMeterLoadFallbackPhase1
DlmExtMeterLoadFallbackPhase2
DlmExtMeterLoadFallbackPhase3
MasterNoIn 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 stopYesR/WTriple[0..10000] Def: 9999:9999:9999
DlmInput1CurrOffsetPhase1
DlmInput1CurrOffsetPhase2
DlmInput1CurrOffsetPhase3
MasterNoOffset added to 'EVSE Sub-Distribution Limit' case external input 1 is high. Note: currently only negative values are supported.YesR/WTriple[-10000..0] Def: 0:0:0
DlmInput3CurrOffsetPhase1
DlmInput3CurrOffsetPhase2
DlmInput3CurrOffsetPhase3
MasterNoOffset added to 'EVSE Sub-Distribution Limit' case meter digital input is high. Note: currently only negative values are supported.YesR/WTriple[-10000..0] Def: 0:0:0
DlmExtMeterEnabledMasterNoIf 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.YesR/WEnum(0) Off
(1) On
Def: Off
DlmExtMeterLocationMasterNoSpecifies how the external meter is connected depending on its location. Either at the grid entry point, between an external load and the rest of the installation, or to a renewable energy source such as a solar panel.YesR/WEnum(0) Grid
(1) External Load
(2) Renewable Production
Def: Grid
DlmCurrImbalancePreventionEnabledMasterNoIf enabled, DLM will not exceed the 'Current Imbalance Limit' configured.YesR/WEnum(0) Off
(1) On
Def: Off
DlmDisableDiscoveryBroadcastMasterNoDisables 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.YesR/WEnum(0) Off
(1) On
Def: Off
DlmRecalcIntervalMasterNoThe 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.NoR/WEnum(1) 1 sec
(2) 2 sec
(5) 5 sec
(15) 15 sec
(30) 30 sec
(60) 1 min
(600) 10 min
(999) 15 min
Def: 30 sec
DlmPersistentSlavesCountMasterNoNumber of persistent DLM slaves registered in DLM slave databaseNoRuint[0..0] Def: 0
DlmClearPersistentSlavesMasterNoSelect 'Clear' and 'Save' to clear the database of known DLM slavesNoR/WEnum(0) -
(1) Clear
Def: -
DlmInput1CurrOffsetCfgMasterNoAdds a configurable offset to 'EVSE Sub-Distribution Limit' based on GPI External Input 1.YesR/WEnum(0) Disable
(1) Enable 'Opto 1 In'
Def: Disable
DlmInput3CurrOffsetCfgMasterNoAdds a configurable offset to 'EVSE Sub-Distribution Limit' based on the Meter's Digital Input register.YesR/WEnum(0) Off
(1) On
Def: Off
DlmInput1PolarityMasterNoChanges the polarity of the input signal 1. "Active high" does not change the polarity, "Active low" inverts the signal.YesR/WEnum(0) Active high
(1) Active low
Def: Active high
ModbusSlaveTCPConfigOnOffBothNoActivates 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.YesR/WEnum(0) Off
(1) On
Def: Off
ModbusSlaveRegAddrSetBothNoChoose the set of register addresses that the Modbus TCP Server device will expose to its Master deviceYesR/WEnum(0) Phoenix
(1) TQ-DM100
(2) Open Modbus Charge Control Interface (OMCCI)
Def: TQ-DM100
ModbusSlaveAllowStartStopBothNoAllows transactions to be started/stopped from a Modbus Master device via the controller's Modbus TCP Server interface.YesR/WEnum(0) Off
(1) On
Def: Off
ModbusSlaveAllowUIDDiscloseBothNoAllows sending the UID via the Ebee Modbus TCP Server protocolYesR/WEnum(0) Off
(1) On
Def: Off
ModbusSlaveTCPPortMasterNoPort 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.YesR/Wuint[0..65434] Def: 502
ModbusSlaveCommTimeoutBothNoTimeout in seconds between messages with a Modbus TCP Master deviceYesR/Wuint[1..2147483647] Def: 1200
ModbusSlaveDevAddrIndividualNoDevice address (0 to 255) to use for the Modbus TCP Server featureYesR/Wuint[0..255] Def: 10
SMAInterfaceOnOffMasterNoThe charging station can be networked with the SMA Sunny Home Manager 2.0 to charge primarily or exclusively with self-generated solar energy.NoR/WEnum(0) Off
(1) On
Def: Off
SMAChargingModeMasterNoThis 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.NoR/WEnum(0) Manual configuration
(1) Immediate charging
(2) Surplus charging
Def: Manual configuration
SMACommunicationTimeoutMasterNoIf 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.NoR/Wuint[60..3600] Def: 600
SMACommunicationTimeoutCurrentMasterNoIf 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.NoR/Wuint[6..80] Def: 6
SMAMaxEnergyDemandMasterNoThis 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.NoR/Wuint[1..1000] Def: 30
SMAMinEnergyDemandMasterNoThis 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.NoR/Wuint[0..1000] Def: 5
SMAChargeCompleteTimeMasterNoThis 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.NoR/WStringDef: "08:00"
EEBUSConfigOnOffMasterNoCompatible energy managers can control the charging station via the EEBus interface.NoR/WEnum(0) Off
(1) On
Def: Off
EEBUSModuleVersionMasterNoNoR/Wuint[0..4294967295] Def: 0
EEBUSModuleShipIdMasterNoNoR/WStringDef: ""
EEBUSConfigCevcOnOffMasterNoCompatible energy managers can control the charging station via the EEBus interface.NoR/WEnum(0) Off
(1) On
Def: Off
EEBUSFallbackCurrentMasterNoIf 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.NoR/Wuint[6..80] Def: 6
EEBUSCommunicationTimeoutMasterNoIf 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.NoR/Wint[4..3600] Def: 4
EEBUSPairedCemIdMasterNoIdentifier issued by the coupled energy manager for identification purposes.NoR/WStringDef: ""
EEBUSPairedCemSkiMasterNoSubject Key Identifier of the coupled energy manager for identification purposes.NoR/WStringDef: ""
EEBUSPairedCemUriMasterNoNoR/WStringDef: ""
EEBUSPairedCemModelNameMasterNoNoR/WStringDef: ""
EEBUSPairedCemIpMasterNoNoR/WStringDef: ""
EEBUSEnableKeoLoggingMasterNoEnable logging of KEO stack messagesNoR/WEnum(0) Off
(1) On
Def: Off
EEBusLPCFailsafePowerUserMasterNoIf the connection to the energy manager fails, the failsafe power for LPC is set to the value set here.NoR/Wuint[0..66000] Def: 11040
EEBusLPCFailsafePowerEnergyGuardIndividualNoIf the connection to the energy manager fails, the power is set to the value set by the energy guard.NoR/Wuint[0..66000] Def: 11040
EEBusLPCFailsafeDurationMinUserMasterNoThe 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.NoR/Wuint[7200..86400] Def: 7200
EEBusLPCFailsafeDurationMinEnergyGuardIndividualNoThe 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.NoR/Wuint[7200..86400] Def: 7200
HemsConfigChargingModeMasterNoThis 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.NoR/WEnum(0) Mains charging
(1) Solar charging
(2) Solar surplus charging
Def: Mains charging
HemsConfigMaxEnergyDemandMasterNoThis 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.NoR/Wuint[1..1000] Def: 30
HemsConfigMinEnergyDemandMasterNoThis 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.NoR/Wuint[0..1000] Def: 5
HemsConfigOptEnergyDemandMasterNoThis 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.NoR/Wuint[0..1000] Def: 8
HemsConfigChargeCompleteTimeMasterNoThis 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.NoR/WStringDef: "08:00"
HemsDeviceNameMasterNoAllows 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.YesR/WStringDef: "CC613_ELM4PR_M"
SignedUpdatesBothNoEnables or disables the signature verification for software updates.YesR/WEnum(0) Off
(1) On
Def: Off
BannerEnabledNot relevantNoA 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.YesR/WEnum(0) Off
(1) On
Def: Off
BannerReadAnalogNot relevantNoFor 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.YesR/WEnum(0) Off
(1) On
Def: Off
BannerPollIntervalNot relevantNoSpecifies 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.YesR/Wuint[0..4294967295] Def: 20
BannerSendIntervalNot relevantNoSpecifies 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.YesR/Wuint[0..4294967295] Def: 60
BannerMaxNodeIdNot relevantNoParking 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.YesR/Wuint[0..47] Def: 0
GeolocationUpdateMasterNoRequest or update the geolocation dataNoWButton

5. OCPP Keys Mapping

Description: This section provides details for the OCPP Keys Mapping tab extracted from the documentation HTML.

Web page key nameMaster/Slave ScopeReboot RequiredOCPP Keys NameOCPP StandardConfiguration File Name
RCMB DeltaBothNoRCMBDeltaNoRCMBThreshold_rcmb
Maximum RMS value of last transactionIndividualNoRCMBTransactionMaxRMSNoRCMBTransactionMaxRMS_rcmb
Maximum DC value of last transactionIndividualNoRCMBTransactionMaxDCNoRCMBTransactionMaxDC_rcmb
Welded contactor detectionIndividualYesWeldCheckNoWeldCheck_rcmb
Welded contactor input typeIndividualYesWeldCheckInTypeNoWeldCheckInType_rcmb
Time zoneBothYesNoEbeeAppTimezone_custom
ChargePoint VendorBothYesChargePointVendorNoChargePointVendor_branding
ChargePoint ModelNot relevantYesChargePointModelNoChargePointModel_branding
SSH Access via USBIndividualYesSSHAccessUsbNoSSHAccessUsb_custom
SSH Access via WLANIndividualYesSSHAccessWlanNetworkNoSSHAccessWlanNetwork_custom
SSH Access via EthernetIndividualYesSSHAccessEthNoSSHAccessEthernet_custom
SSH Access via GSMIndividualYesSSHAccessGsmNoSSHAccessGsm_custom
Filter Out Invalid RFIDsBothYesInvalidRFIDFilterNoInvalidRFIDFilter_custom
Enforce Password changeBothNoEnforcePwdChangeNoEnforcePwdChange_custom
Enforce strong login passwordsBothNoEnforceStrongLoginPwdsNoEnforceStrongLoginPwds_custom
RFID ModeBothYesRFIDModeNoRFIDMode_custom
Enforce Master RFIDBothNoEnforceMasterRFIDNoEnforceMasterRFID_custom
Enforce using Secure RFIDBothNoEnforceSecureRFIDNoEnforceSecureRFID_custom
Controller serial numberIndividualYesChargeBoxSerialNumberNoSerialNumber_custom
Manufacturer serial numberMasterYesChargePointSerialNumberNoSerialNumberManufacturer_custom
User PasswordBothNoNoUserPwdPlain_custom
Installer PasswordBothNoNoInstallerPwdPlain_custom
Operator PasswordBothNoNoOperatorPwdPlain_custom
Manufacturer PasswordNot relevantNoNoManufacturerPwdPlain_custom
Factory Reset by RFIDIndividualNoMasterRFIDstoResetNoResetToDefaultsRFID_custom
Reset Password PUKIndividualNoNoResetPasswordPUK_custom
State page password protectionBothYesNoStatePageLock_custom
Authorization Input ModeNot relevantYesAuthorizationInputModeNoAuthorizationInputMode_custom
Authorization Input Switch TypeNot relevantYesAuthorizationInputTypeNoAuthorizationInputType_custom
Log LevelBothNologlevelNoLogLevel_custom
State 'unavailable' at FW update beginBothNoNoUnavailAtFwUpdateBegin_custom
Restore timeNot relevantYesNoRestoreTime_custom
Power source voltageIndividualYesPowerLineVoltageNoPowerSourceVoltage_custom
High frequency react threshold (mHz)BothYesNoFrequencyMonitorReactHigh_custom
Current at normal grid frequency (A)BothYesNoFreqMonNormalCurrent_custom
Low frequency react threshold (mHz)BothYesNoFrequencyMonitorReactLow_custom
Current at low grid frequency (A)BothYesNoFreqMonLowCurrent_custom
Low frequency stop threshold (mHz)BothYesNoFrequencyMonitorStopLow_custom
Frequency load management randomization (s)BothYesNoFreqLoadManagamentRandomization_custom
Master/Slave ModeNot relevantYesMasterSlaveModeNoMasterSlaveMode_ms
Email notification in case of errorsMasterYesNoEmailEnabled_mail
Email provider account usernameMasterYesNoEmailUsername_mail
Email provider account passwordMasterYesNoEmailPassword_mail
SMTP server and portMasterYesNoEmailServerPort_mail
SMTP connection securityMasterNoNoEmailConnSecurity_mail
Location of charge point in outgoing emailsMasterYesNoEmailCpLocation_mail
'From:' address in outgoing emailsMasterYesNoEmailFromAddress_mail
'To:' address(es) in outgoing emailsMasterYesNoEmailToAddress_mail
Send test emailMasterNoNoEmailTestSend_mail
Resend last email session reportMasterNoNoEmailSessionReportResend_mail
Send email session reportBothNoNoEmailSessionReport_mail
Session report formatBothNoNoEmailAttachmentType_mail
Manufacturer specific mail serverMasterYesNoManufacturerSpecificMailServer_mail
LED TypeNot relevantNoLedTypeNoLedType_hmi
Dual LED board modeNot relevantNoDualLedModeNoDualLedMode_hmi
Type of DisplayNot relevantNoDisplayTypeNoDisplayType_hmi
Mode for DisplayNot relevantNoDisplayModeNoDisplayMode_hmi
Display charging timeNot relevantNoDisplayContentSelectorTimeNoDisplayContentSelectorTime_hmi
Display energyNot relevantNoDisplayContentSelectorEnergyNoDisplayContentSelectorEnergy_hmi
Display powerNot relevantNoDisplayContentSelectorPowerNoDisplayContentSelectorPower_hmi
HMI Pattern On Relay 2 (K2)Not relevantNoPatternOnRelayK2NoHMIPatternOnRelayK2_V2_hmi
Language of DisplayIndividualNoDisplayLanguageNoDisplayLanguage_hmi
CC613 Buzzer TestIndividualNoNoCC613BuzzerTest_hmi
Schuko SocketNot relevantYesOCPPSchukoNoSchuko_vehicleif
Actuator typeNot relevantYesEOActuatorTypeNoEO_ActuatorType_vehicleif
Type 2 Contactor LifetimeIndividualYesType2ContactorLifetimeNoType2ContactorLifetime_vehicleif
Type 2 Plug LifetimeIndividualYesType2PlugLifetimeNoType2PlugLifetime_vehicleif
Type 2 Plug CyclesIndividualNoNoType2PlugCounter_vehicleif
Set type 2 plug cycles toIndividualNoSetType2PlugCyclesNoType2PlugCounterWeb_vehicleif
Type 2 Plug CyclesNot relevantNoType2PlugCounterNoType2PlugCounterRO_vehicleif
Contactor Cycles Type2IndividualNoNoType2NumberContactorCycles_vehicleif
Set type 2 contactor cycles toIndividualNoSetTypeContactorCyclesNoType2NumberContactorCyclesWeb_vehicleif
Contactor Cycles Type2IndividualNoContactorCyclesType2NoType2NumberContactorCyclesRO_vehicleif
Threshold Contactor Current Under Load [A]IndividualYesThresholdContactorCurrentUnderLoadNoThresholdContactorCurrentUnderLoad_vehicleif
Contactor Cycles Under Load LimitIndividualYesContactorCyclesUnderloadLimitNoContactorCyclesUnderLoadLimit_vehicleif
Contactor Cycles Under LoadIndividualNoNoResetCountforContactorCyclesUnderloadTo_vehicleif
Set contactor cycles under load toIndividualNoSetCountContactorCyclesType2UnderLoadNoType2NumberContactorCyclesUnderLoadWeb_vehicleif
Number of contactor cycles under loadIndividualNoGetCountContactorCyclesType2UnderLoadNoCountContactorCyclesType2UnderLoad_vehicleif
ADC CP line calibration reference valueIndividualNoNoAdcCpCalibrationVal_vehicleif
ADC CP line calibration reference value for 5%IndividualNoNoAdcCpCal5PerCentVal_vehicleif
Fixed cable attachedNot relevantYesCableAttachedNoCableAttached_vehicleif
Detect Control Pilot DiodeIndividualNoCPDiodeDetectionNoDetectCPDiode_vehicleif
Pause/prevent charging in state DBothNoPauseChargingStateDNoPauseChargingStateD_vehicleif
ADC calibration for CP lineIndividualYesAdcCpCalibrationCfgNoAdcCpCalibrationCfg_vehicleif
Stop limit in (%) for 'Check for car overload'BothYesCheckCarOverCurrentStopLimitNoCheckCarOverCurrentStopLimit_vehicleif
Maximum Current [A]IndividualYesHardwareCurrentLimitNoHardwareCurrentLimit_vehicleif
Installation Current Limit [A]IndividualYesInstallationCurrentLimitNoInstallationCurrentLimit_vehicleif
Operator Current Limit [A]IndividualNoOperatorCurrentLimitNoOperatorCurrentLimit_vehicleif
Free ChargingBothNoFreeChargingNoFreeCharging_vehicleif
Check for car overloadBothNoCheckCarOverCurrentNoCheckCarOverLoad_vehicleif
Randomize charging after power lossBothYesRandomRestartAfterPowerLossNoRandomRestartAfterPowerLoss_vehicleif
Type of phase switching relay (NO/NC)IndividualYesNoPhaseSwitchingContactorType_vehicleif
Use phase switching relay (1ph <> 3ph)IndividualYesNoPhaseSwitchingOutput_vehicleif
PDL PowerMasterNoPDL_PowerNoPDLPower_vehicleif
Delay status updateBothNoNoDelayStatusUpdateStartTrans_vehicleif
Phases connected to the ChargePointIndividualYesNoPhasesNumber_custom
Energy management from external inputIndividualYesEnergyManInputPowerLimitCfgNoInputPowerLimit_energyman
Phase rotation of the ChargePointIndividualYesNoPhaseRotationInternal_energyman
Phase rotation of the single phase IT ChargePointIndividualYesNoPhaseRotationITInternal_energyman
Current limit for energy management from external inputIndividualYesEnergyManInputPowerCurrentLimNoInputCurrentLimit_energyman
HawkBit clientNot relevantYesNoHawkBitEnableConfiguration_hawkbit
HawkBit server base URLNot relevantYesNoHawkBitBaseUrl_hawkbit
HawkBit client controller IDNot relevantYesNoHawkBitControllerId_hawkbit
HawkBit client tenant IDNot relevantYesNoHawkBitTenantId_hawkbit
HawkBit client authorization tokenNot relevantYesNoHawkBitAuthToken_hawkbit
HawkBit client force HTTPSNot relevantNoNoHawkBitForceHttps_hawkbit
RCD Auto ReclosureBothYesRCDAUTORECLOSURENoRcdAutoReclosure_mon
RCD EnableBothYesRCDENABLENoRcdEnable_mon
SPD ConfigIndividualYesSPDCFGNoSPDConfig_mon
Fan or heater control configurationBothYesVentHeatingCtrlModeNoVentHeatingTempCtrlMode_mon
Weld check outputBothNoWeldCheckAuxRelayNoWeldCheckAuxRelay_mon
RCD auto reclosure delayBothYesRCDAUTORECLOSUREDELAYNoRcdAutoReclosureDelay_mon
RCD auto reclosure attemptsBothYesRCDAUTORECLOSUREATTEMPTSNoRcdAutoReclosureAttempts_mon
Fan or heater control hysteresis configurationBothYesVentHeatingHystNoVentHeatingHyst_mon
Temperature threshold for fan or heater controlBothYesVentHeatingTempThrNoVentHeatingTempThr_mon
Charging Station temperature deltaIndividualNoAmbientCpuDeltaNoTempControlAmbientCpuDelta_mon
Local time for housekeeping rebootBothYesLocalScheduledRebootsNoLocalTimeToReboot_mon
Number of days for housekeeping rebootBothNoDaysScheduledRebootsNoDaysToReboot_mon
Charging current to reduce temperature [A]IndividualNoReducedCurrentNoTempControlReducedCurrent_custom
Charging current (in % of signaled current) to reduce temperatureIndividualNoReducedCurrentPctNoTempControlReducedPercentage_custom
Temperature Report DeltaMasterNoTempDeltaNoTempDelta_mon
Temperature threshold 2IndividualNoTempStopThreshold2NoTempControlStopThr_mon
Temperature threshold 1IndividualNoTempReduceThreshold1NoTempControlReduceThr_mon
WLAN connection statusMasterNoNoWlanConnectionStatus_mon
Backend controlled mode for inputs and outputsBothYesInputOutputBackendControlledModeNoInOutputBackendControlled_iom
Backend notification for input changesBothNoInputChangeNotifyBackendNoInputChangeNotifyBackend_iom
Tamper detection sensor enableIndividualYesTamperDetectionInputEnableNoTamperDetectionInputEnable_tam
DataTransfer for Tariff And Total UsageBothNoDataTransferTariffUsageNoTariffAndUsageDataTransfer_ocpp
Ignore OCPP ParentIDBothYesNoIgnoreParentId_ocpp
Send Authorize for RemoteStartBothYesAuthorizeRemoteTxRequestsYesAuthorizeRemoteStarts_ocpp
If in doubt allow chargingBothNoAllowOfflineTxForUnknownIdYesIfInDoubtAllowCharging_ocpp
Send informative StatusNotificationsBothNoInfoStatusNotificationsNoInfoStatusNotifications_ocpp
Send error StatusNotificationsBothYesErrorStatusNotificationsNoErrorStatusNotifications_ocpp
Send USB error StatusNotificationsIndividualYesUsbErrorStatusNotificationsNoUsbErrorStatusNotifications_ocpp
Strategy for StatusNotification state transitionsBothYesStatusNotificationStrategyNoStatusNotificationStrategy_ocpp
Display backend disconnect as errorMasterYesDisplayDisconnectAsErrorNoDisconnectAsError_ocpp
Enable OCPP whitelistMasterNoAuthorizationCacheEnabledYesUseCache_ocpp
RFID Tag letter caseBothYesidTagLetterCaseNoOCPPIDTagLetterCase_ocpp
Stop Transaction On EV Side DisconnectBothNoStopTransactionOnEVSideDisconnectYesStopTransactionOnEVSideDisconnect_ocpp
Unlock Connector On EV Side DisconnectBothNoUnlockConnectorOnEVSideDisconnectYesUnlockConnectorOnEVSideDisconnect_ocpp
Free Charging ModeBothYesFreeChargingModeNoFreeChargingMode_ocpp
Allow long get configuration keysBothYesAllowLongOcppGetConfKeysNoAllowLongOcppGetConfKeys_ocpp
Integer values for boolean get configuration keysBothNoOcppGetConfBoolIsIntNoOcppGetConfBoolIsInt_ocpp
Stop Transaction on invalid IDIndividualNoStopTransactionOnInvalidIdYesStopTransactionOnInvalidId_ocpp
OCPP ChargeBoxIdentity (ChargePointID)IndividualYesChargeBoxIdentityNoChargePointID_ocpp
RFID Tag for Free Charging with OCPP Full, fixed RFID modesIndividualYesRfidTagFreeChargingNoRfidTagFreeCharging_ocpp
Backend connection timeoutMasterYesBackendConnectionTimeoutNoConnectionTimeOut_ocpp
Vehicle connection timeout [s]BothYesConnectionTimeOutYesVehicleConnectionTimeout_ocpp
Number of transaction message attemptsIndividualYesTransactionMessageAttemptsYesTransactionMessageAttempts_ocpp
Number of Eichrecht transaction message attemptsIndividualYesEichrechtTransactionMessageAttemptsNoEichrechtTransactionMessageAttempts_ocpp
Transaction message retry interval (seconds)IndividualYesTransactionMessageRetryIntervalYesTransactionMessageRetryInterval_ocpp
Number of reset retriesIndividualYesResetRetriesYesResetRetries_ocpp
Disallow charging if OCPP queue fullBothYesOcppQueueFullAsErrorStateNoOcppQueueFullAsErrorState_ocpp
Local Pre AuthorizeMasterNoLocalPreAuthorizeYesLocalPreAuthorize_ocpp
Local Authorize OfflineMasterNoLocalAuthorizeOfflineYesLocalAuthorizeOffline_ocpp
Force OCPP connector state to available/unavailableBothNoNoForceStateAvail_ocpp
Force Heartbeat request messagesNot relevantYesForceHeartbeatRequestMessagesNoForceHeartBeat_ocpp
Retransmit MeterValuesBothNoRetransmitMeterValuesNoRetransmitMeterValues_ocpp
ChargePoint UPnP UUIDIndividualYesUPnPUUIDNoChargePointUUID_ocpp
Heartbeat interval (OCPP 1.6)MasterNoHeartbeatIntervalYesHeartBeatInterval_ocpp
Stop Transaction ModeBothYesStopTransactionModeUnplugNoStopTransactionMode_ocpp
Hmi led light intensity controlBothNoLightIntensityYesLightIntensity_ocpp
Send status notification to the backend for webui login eventBothNoStatusNotificationWebuiLoginNoStatusNotificationWebuiLogin_ocpp
USB Field EngineerBothYesUSBFieldEngineerNoUsbFieldEngineer_usbhotplug
USB Config updateBothYesUSBConfigUpdateNoUsbConfigUpdate_usbhotplug
USB Firmware updateBothYesUSBFirmwareUpdateNoUsbFirmwareUpdate_usbhotplug
USB script executionNot relevantYesNoUsbScriptExec_usbhotplug
USB Installer PasswordNot relevantNoNoUsbInstallerPasswordPlain_usbhotplug
Average energy per sessionIndividualNoNoAveragekWh_sql
Average duration per sessionIndividualNoNoAverageTransactionDurationStr_sql
Average duration per sessionIndividualNoNoAverageTransactionDuration_sql
Average duration per sessionIndividualNoNoAverageTransactionDurationSeconds_sql
Total Charging SessionsIndividualNoNoTransactionsInDatabase_sql
This month's transaction countIndividualNoNoTransactionsThisMonth_sql
This month's kWh consumptionIndividualNoNoTotalkWhThisMonth_sql
OCPP whitelist learning modeMasterNoNoCacheFillMode_cache
OCPP whitelist expiry modeMasterYesNoCacheExpiryOption_cache
Enable OCPP whitelistMasterNoLocalAuthListEnabledYesLocalAuthListEnabled_cache
OCPP whitelist version numberMasterNoNoCacheVersion_cache
Local whitelist learning modeMasterNoNoFLLFillMode_fll
Enable local whitelistMasterNofllNoFllCfg_fll
Send OCPP Start/Stop transactionBothNofllUseOcppStartStopNoFLLUseOcppStartStop_fll
Connection TypeMasterYesConnectionTypeNoType_dl
Static USB network configuration additional IPNot relevantNoNoUSBAdditionalIP_dl
Static USB network configuration gatewayNot relevantNoNoUSBAdditionalGW_dl
Static USB network configuration DNSIndividualNoNoUSBAdditionalDNS_dl
Data ConsumptionMasterNoDataConsumptionNoDataConsumption_dl
Data Consumption Last MonthMasterNoDataConsumptionLastMonthNoDataConsumptionLastMonth_dl
Access Point Name (APN)MasterYesAPNNoAPN_modem
Network selection modeMasterYesModemNetworkSelModeNoNetworkOperSelMode_modem
Modem Access TechnologyMasterYesModemNetworkTypeNoNetworkType_modem
Network operator name formatMasterYesModemNetworkOperFmtNoNetworkOperNameFormat_modem
Scan network operators at bootMasterYesScanNetworkOperatorsNoScanNetworkOps_modem
APN UsernameMasterYesAPNUsernameNoAPNUsername_modem
APN PasswordMasterYesAPNPasswordNoAPNPassword_modem
Requested Network operatorMasterYesReq3GNetworkOperatorNoReqNetworkOperator_modem
Received Signal Strength Indicator (RSSI)MasterNoRSSINoRSSI_modem
Mode for ethernet configurationMasterYesNetworkConfigModeNoNetworkConfig_mode_tcpip
Static network configuration IPMasterYesStaticNetworkConfigAddressNoNetworkConfigStaticAddress_tcpip
Static network configuration netmaskMasterYesStaticNetworkConfigNetmaskNoNetworkConfigStaticNetmask_tcpip
Static network configuration DNSMasterYesStaticNetworkConfigDNSNoNetworkConfigStaticDNS_tcpip
SSL Strictness as clientMasterYesSSLModeClientNoSSLAuthMode_tcpip
WAN router interfaceMasterYesWANRouterInterfaceNoWANRouterInterface_tcpip
WAN routerMasterYesWANRouterNoWANRouter_tcpip
OCPP ModeMasterYesOCPPModeNoTCP_IP_MODE_V2_tcpip
Connection settings fallbackIndividualYesConnSettingsFallbackNoConnectionSettingsFallback_tcpip
Hostname (Binary OCPP)MasterYesHostnameBinaryOCPPNoBinaryOCPPHostname_tcpip
WebSockets JSON OCPP URL of the BackendMasterYesOCPPBackendJSONURLNoJsonOCPPBackendURL_tcpip
Websockets proxyMasterYesWebsocketsProxyURLNoWebsocketsProxyURL_tcpip
HTTP Basic Authentication passwordMasterYesHTTPBasicAuthPasswordNoHTTPBasicAuthPassword_tcpip
Certificate (OCPP)MasterNoOcppCertificateNoOcppCertificate_tcpip
Certificate signing request (OCPP)MasterNoOcppCSRNoOcppCertificateSigningRequest_tcpip
User CA Certificate (OCPP)MasterNoOcppUserCaCertificateNoOcppUserCaCertificate_tcpip
Connection Type (Backend)MasterNoNoBackendConnectionType_tcpip
Client hostnameMasterYesNetworkConfigHostnameNoNetworkConfigHostname_tcpip
Static network configuration gatewayMasterYesStaticNetworkConfigGatewayNoNetworkConfigStaticGateway_tcpip
Port number (Binary OCPP)MasterYesPortBinaryOCPPNoBinaryOCPPPort_tcpip
TCP Watchdog TimeoutIndividualYesTcpWatchdogTimeoutNoTcpWatchdogTimeout_tcpip
DHCP client request retriesMasterYesNetworkConfigDHCPRetriesNoNetworkConfigDHCPRetries_tcpip
DHCP client request timeoutMasterYesNetworkConfigDHCPTimeoutNoNetworkConfigDHCPTimeout_tcpip
DHCP client request delayMasterYesNetworkConfigDHCPDelayNoNetworkConfigDHCPDelay_tcpip
WebSockets keep-alive intervalMasterNoWebSocketPingIntervalYesWebSocketsKeepAliveInterval_tcpip
OCPP connection strictnessMasterYesOcppConStrictTlsNoOCPPConStrictTls_tcpip
WLAN SSIDMasterNoWLANSSIDNoWLANSSID_wlan
WLAN passwordMasterNoWLANPasswordNoWLANPassword_wlan
Static network configuration IPMasterYesWLANStaticNetworkConfigAddressNoNetworkConfigStaticAddress_wlan
Static network configuration netmaskMasterYesWLANStaticNetworkConfigNetmaskNoNetworkConfigStaticNetmask_wlan
Static network configuration gatewayMasterYesWLANStaticNetworkConfigGatewayNoNetworkConfigStaticGateway_wlan
Static network configuration DNSMasterYesWLANStaticNetworkConfigDNSNoNetworkConfigStaticDNS_wlan
WLAN enabledMasterNoWLANEnabledNoEnabled_wlan
Mode for WLAN configurationMasterYesWLANNetworkConfigModeNoNetworkConfig_mode_wlan
DHCP client request retriesMasterNoWLANNetworkConfigDHCPRetriesNoNetworkConfigDHCPRetries_wlan
DHCP client request timeoutMasterNoWLANNetworkConfigDHCPTimeoutNoNetworkConfigDHCPTimeout_wlan
DHCP client request delayMasterNoWLANNetworkConfigDHCPDelayNoNetworkConfigDHCPDelay_wlan
Tcpdump InterfaceIndividualNoTcpdumpInterfaceNoTcpdumpInterface_diag
Start and stop 'tcpdump' runIndividualNoTcpdumpNoTcpdump_diag
15118 ConfigurationBothYesConfig15118NoHlcConfig_15118
SECC Certificate Expiry Date (15118 protocol)IndividualNoSeccCertExpireDate15118NoSeccCertExpireDate_15118
Extra loggingBothYesLog15118NoHlcLogging_15118
EVCCID or EV's MAC address prefix for OCPP authorizationBothYesMACEVCCIDPrefixNoMACEVCCIDPrefix_15118
EV's MAC addressIndividualNoEVMACAddrNoEVMACAddr_15118
Autocharge fixed IDBothYesautochargeidNoAutochargeFixedID_15118
AutochargeBothYesAutochargeNoAutochargeConfig_15118
Retrieve OCSP certificate statusBothYesNoCheckOCSPCertStatus_15118
15118 connection strictnessMasterYesP15118ConStrictTlsNoP15118ConStrictTls_15118
15118 EV detection timeout [s]BothYesP15118EVSlacReqTimeoutNoP15118EVSlacReqTimeout_15118
ConfigurationIndividualYesOCPPMeterTypeNoConfig_meter
Meter configuration (Second)MasterYesSecondMeterTypeNoConfigSecond_meter
Baud Rate for Modbus/RTUIndividualYesNoMeterModbusRTUBaud_meter
Baud Rate for Modbus/RTU (second bus)IndividualYesNoMeterModbusRTUBaudSecond_meter
Parity for Modbus/RTUIndividualYesNoMeterModbusRTUParity_meter
Parity for Modbus/RTU (second bus)IndividualYesNoMeterModbusRTUParitySecond_meter
Stop bits for Modbus/RTUIndividualYesNoMeterModbusRTUStop_meter
Stop bits for Modbus/RTU (second bus)IndividualYesNoMeterModbusRTUStopSecond_meter
Modbus timeout [s] for Modbus/RTUIndividualNoNoMeterModbusTimeout_meter
Modbus polling frequency [ms]IndividualNoNoMeterModbusPollingFrequency_meter
Modbus address of OCPP meterIndividualYesNoOcppMeterModbusAddr_meter
Modbus address of second meterIndividualYesNoSecondMeterModbusAddr_meter
OCPP Via Local Network minimum value '1'BothNoOCPPViaLocalNetworkNoOCPPViaLocalNetwork_meter
Meter Value Sample Interval (OCPP)BothNoMeterValueSampleIntervalYesMeterValueSampleInterval_meter
Meter Value Sample Mode (OCPP)BothNoMeterValueSampleModeNoMeterValueSampleMode_meter
Clock aligned data interval (OCPP)BothYesClockAlignedDataIntervalYesClockAlignedDataInterval_meter
Clock aligned random sent delay in seconds (OCPP)BothYesClockAlignedMeterRandomSendDelayNoClockAlignedMeterRandomSendDelay_meter
Meter values aligned data (OCPP)BothNoMeterValuesAlignedDataYesMeterValuesAlignedData_meter
Meter values sampled data (OCPP)BothNoMeterValuesSampledDataYesMeterValuesSampledData_meter
Stop transaction sampled data (OCPP)BothNoStopTxnSampledDataYesStopTxnSampledData_meter
Stop transaction aligned data (OCPP)BothNoStopTxnAlignedDataYesStopTxnAlignedData_meter
IP address of OCPP meterIndividualYesNoOcppMeterIPAddress_meter
IP address of second meterMasterYesSecondMeterIPAddressNoSecondMeterIPAddress_meter
Port number of second meterMasterYesSecondMeterTCPPortNumberNoSecondMeterTCPPortNumber_meter
Pulses per kWh (S0 meter)Not relevantNoNoS0MeterPulsesPerKWh_meter
Pulses per kWh (Second S0 meter)Not relevantNoNoS0MeterPulsesPerKWhSecond_meter
Restart transaction after power lossBothYesRestartTransAfterPowerLossNoRestartAfterPowerLoss_meter
Current flow direction of L1 of second meterIndividualYesCurrentDirSecondL1NoCurrentDirSecondL1_meter
Current flow direction of L2 of second meterIndividualYesCurrentDirSecondL2NoCurrentDirSecondL2_meter
Current flow direction of L3 of second meterIndividualYesCurrentDirSecondL3NoCurrentDirSecondL3_meter
Line loss switchIndividualNoNoMeterLineLossSwitch_meter
Line loss percentageIndividualNoNoLineLossPercentage_meter
Charging cable nameIndividualNoNoChargingCableName_meter
Charging cable contact resistance (mOhm)IndividualNoNoCableContactResistance_meter
Lock charging cable contact resistanceIndividualNoNoLockContactResistance_meter
Charging cable resistance (mOhm)IndividualYesNoChargingCableResistance_meter
Cable loss energy configurationIndividualYesNoCableLossEnergyConfig_meter
Line loss resistance (Ohm)IndividualNoNoLineLossResistance_meter
Mode selectionIndividualNoNoEREastronModeSelect_meter
Enable HTTPSBothYesNoEnableHTTPS_encryption
Authorization InputNot relevantYesAuthorizationInputNoAUTHORIZATION_INPUT_custom
Custom web configuration titleNot relevantYesNoWebUICustomTitle_web
Append manufacturer serial to configuration titleNot relevantYesNoWebUITitleSerial_web
Hierarchical Dynamic Load Management - DLM CoordinatorMasterYesDlmHierarchicalModeNoDlmCMode_dlmc
DLM master fallback currentMasterYesDlmcMaximumFallbackCurrent1
DlmcMaximumFallbackCurrent2
DlmcMaximumFallbackCurrent3
NoDlmcMaximumFallbackCurrent_dlmc
Publish constraints for DLM coordinatorMasterYesDlmcPublishConstraintsNoDlmcPublishConstraints_dlmc
Dynamic Load Management - DLM Master/SlaveIndividualYesDlmModeNoDlmMode_dlm
Configure solar charging modeMasterNoDlmSolarMode_dlmNoDlmSolarMode_dlm
DLM Network IdMasterYesDlmDiscoveryNetworkIdNoDlmDiscoveryNetworkId_dlm
DLM Master IP and portMasterYesDlmMasterIpNoDlmMasterIp_dlm
EVSE Sub-Distribution Limit (L1/L2/L3) [A]MasterYesDlmPhase1Limit
DlmPhase2Limit
DlmPhase3Limit
NoDlmPhaseLimit_dlm
Operator EVSE Sub-Distribution Limit (L1/L2/L3) [A]MasterNoDlmOperatorPhase1Limit
DlmOperatorPhase2Limit
DlmOperatorPhase3Limit
NoDlmOperatorLimit_dlm
Main Distribution Limit (L1/L2/L3) [A]MasterYesDlmExtMeterMainDistributionLimitPhase1
DlmExtMeterMainDistributionLimitPhase2
DlmExtMeterMainDistributionLimitPhase3
NoDlmExternalMeterMainDistLimit_dlm
External Load Headroom (L1/L2/L3) [A]MasterNoDlmExtLoadHeadroomPhase1
DlmExtLoadHeadroomPhase2
DlmExtLoadHeadroomPhase3
NoDlmExternalLoadHeadroom_dlm
External Load Averaging Length [s]MasterYesDlmExtLoadAvgLenNoDlmExternalLoadAvgLen_dlm
Disconnected Limit [A]BothYesDlmDisconnectedLimitNoDlmDisconnectedLimit_dlm
Minimum Current Limit [A]BothYesDlmMinCurrentRatingNoDlmMinCurrentRating_dlm
Use solar mode on this chargerBothNoDlmSlaveSolarEnabledNoDlmSlaveEnableSolar_dlm
Solar Mode on this chargerNot relevantNoNoDlmHemsChargingMode_dlm
Current Imbalance Limit [A]MasterYesDlmCurrImbalanceLimNoDlmCurrImbalanceLimit_dlm
External Load Fallback (L1/L2/L3) [A]MasterYesDlmExtMeterLoadFallbackPhase1
DlmExtMeterLoadFallbackPhase2
DlmExtMeterLoadFallbackPhase3
NoDlmExternalLoadFallback_dlm
Ext. Input 1 Current Offset (L1/L2/L3) [A]MasterYesDlmInput1CurrOffsetPhase1
DlmInput1CurrOffsetPhase2
DlmInput1CurrOffsetPhase3
NoDlmInput1OffsetPhase_dlm
Meter Digital Input Current Offset (L1/L2/L3) [A]MasterYesDlmInput3CurrOffsetPhase1
DlmInput3CurrOffsetPhase2
DlmInput3CurrOffsetPhase3
NoDlmInput3OffsetPhase_dlm
Charging LogMasterYesNoDlmChargingLog_dlm
External Meter LogMasterYesNoDlmExternalMeterLog_dlm
DLM LogMasterNoNoDlmDlmLog_dlm
External Meter SupportMasterYesDlmExtMeterEnabledNoDlmExternalMeterEnabled_dlm
External Meter LocationMasterYesDlmExtMeterLocationNoDlmExternalMeterLocation_dlm
Current Imbalance PreventionMasterYesDlmCurrImbalancePreventionEnabledNoDlmCurrImbalanceLimitEnabled_dlm
Disable Discovery BroadcastingMasterYesDlmDisableDiscoveryBroadcastNoDlmDiscoveryDisableBroadcast_dlm
Maximum Current SchedulerMasterYesNoDlmTimeTableEnabled_dlm
DLM Algorithm Sample RateMasterNoDlmRecalcIntervalNoDlmAlgoSampleRate_dlm
IT NetworkMasterYesNoDlmITNetworkEnabled_dlm
Persistent DLM slave countMasterNoDlmPersistentSlavesCountNoDlmPersistentSlavesCount_dlm
Clear persistent DLM slave DBMasterNoDlmClearPersistentSlavesNoDlmClearPersistentSlaves_dlm
External Input 1 ConfigMasterYesDlmInput1CurrOffsetCfgNoDlmInput1CurrOffsetConfig_dlm
Meter Digital Input ConfigMasterYesDlmInput3CurrOffsetCfgNoDlmInput3CurrOffsetConfig_dlm
External Input 1 PolarityMasterYesDlmInput1PolarityNoDlmInput1Polarity_dlm
Maximum grid support current [A]MasterNoNoDlmSolarMaximumGridSupplyCurrent_dlm
PV surplus monitoring time to resume charging [s]MasterNoNoDlmSolarEvseSuspendedHoldTime_dlm
Solar DLM external meter power offsetMasterNoNoDlmSolarExternalMeterOffset_dlm
Show "DLM override" button in dashboardNot relevantYesNoDlmShowOverrideButtonOnDashboard_dlm
Hold time after 1ph<>3ph state switching [s]MasterNoNoDlmPhaseSwitchingHoldTime_dlm
Solar mode pauseMasterNoNoDlmSolarModePausingEnable_dlm
Start time of the solar mode pauseMasterNoNoDlmSolarModePausingStartTime_dlm
End time of the solar mode pauseMasterNoNoDlmSolarModePausingEndTime_dlm
Modbus TCP Server for energy management systemsBothYesModbusSlaveTCPConfigOnOffNoTCPConfigOnOff_modbus_slave
Modbus TCP Server Register Address SetBothYesModbusSlaveRegAddrSetNoRegAddrSet_modbus_slave
Modbus TCP Server Allow Start/Stop TransactionBothYesModbusSlaveAllowStartStopNoAllowStartStop_modbus_slave
Modbus TCP Server Allow UID DiscloseBothYesModbusSlaveAllowUIDDiscloseNoAllowUIDDisclose_modbus_slave
Modbus TCP Server Base PortMasterYesModbusSlaveTCPPortNoTCPPortNumber_modbus_slave
Modbus TCP Server Communication TimeoutBothYesModbusSlaveCommTimeoutNoCommTimeout_modbus_slave
Modbus TCP Server Device AddressIndividualYesModbusSlaveDevAddrNoSlaveDeviceAddress_modbus_slave
SEMP interfaceMasterNoSMAInterfaceOnOffNoSempGatewayConfigOnOff_semp_gateway
Charging ModeMasterNoSMAChargingModeNoSempGatewayChargingMode_semp_gateway
Time to connection failure [s]MasterNoSMACommunicationTimeoutNoSempGatewayCommunicationTimeout_semp_gateway
Current in case of connection failure [A]MasterNoSMACommunicationTimeoutCurrentNoSempGatewayFallbackCurrent_semp_gateway
Maximum energy demand [kWh]MasterNoSMAMaxEnergyDemandNoSempGatewayMaxEnergyDemand_semp_gateway
Minimum energy demand [kWh]MasterNoSMAMinEnergyDemandNoSempGatewayMinEnergyDemand_semp_gateway
Scheduled departure time [hh:mm]MasterNoSMAChargeCompleteTimeNoSempGatewayMaxChargingTime_semp_gateway
EEBus interfaceMasterNoEEBUSConfigOnOffNoEEBUSConfigOnOff_eebus
Coordinated Charging ModeMasterNoEEBUSConfigCevcOnOffNoEEBUSConfigCevcOnOff_eebus
Current in case of connection failure [A]MasterNoEEBUSFallbackCurrentNoEEBUSFallbackCurrent_eebus
Communication Timeout [s]MasterNoEEBUSCommunicationTimeoutNoEEBUSCommunicationTimeout_eebus
Connect or disconnect the energy managerMasterNoNoEEBUSCoupledEnergyManager_eebus
Connect or disconnect the energy manager (used for REST API)MasterNoNoEEBUSPairingActionSelector_eebus
Connect or disconnect the energy managerMasterNoNoEEBUSPairingActionSelectorLegacy_eebus
Identifier of the coupled energy managerMasterNoEEBUSPairedCemIdNoEEBUSPairedCemIdentification_eebus
SKI of the coupled energy managerMasterNoEEBUSPairedCemSkiNoEEBUSPairedCemSki_eebus
Coupling status of the energy managerMasterNoNoEEBUSPairingStatus_eebus
Charging SummaryMasterNoNoEEBUSChargingSummary_eebus
EEBus stack versionMasterNoNoEEBusStackVersion_eebus
Failsafe power in case of connection failure [W]MasterNoEEBusLPCFailsafePowerUserNoEEBusLPCFailsafePowerUser_eebus
Energy guard failsafe power in case of connection failure [W]IndividualNoEEBusLPCFailsafePowerEnergyGuardNoEEBusLPCFailsafePowerEnergyGuard_eebus
Minimum duration for failsafe state [s]MasterNoEEBusLPCFailsafeDurationMinUserNoEEBusLPCFailsafeDurationMinUser_eebus
Energy guard minimum duration for LPC failsafe state [s]IndividualNoEEBusLPCFailsafeDurationMinEnergyGuardNoEEBusLPCFailsafeDurationMinEnergyGuard_eebus
Fail-safe currentIndividualYesNoFailSafeCurrent_hems
HEMS Current LimitIndividualYesNoCurrentLimit_hems
Charging ModeMasterNoHemsConfigChargingModeNoChargingMode_hems
Maximum energy demand [kWh]MasterNoHemsConfigMaxEnergyDemandNoMaxEnergyDemand_hems
Minimum energy demand [kWh]MasterNoHemsConfigMinEnergyDemandNoMinEnergyDemand_hems
Optimal energy demand [kWh]MasterNoHemsConfigOptEnergyDemandNoOptEnergyDemand_hems
Scheduled departure time [hh:mm]MasterNoHemsConfigChargeCompleteTimeNoMaxChargingTime_hems
HEMS device nameMasterYesHemsDeviceNameNoDeviceName_hems
Send parking space occupancy data to backendNot relevantYesBannerEnabledNoBannerEnabled_banner
Transmit additional analogue sensor valuesNot relevantYesBannerReadAnalogNoBannerReadAnalog_banner
Interval to retrieve data from the gateway (s)Not relevantYesBannerPollIntervalNoBannerPollInterval_banner
Interval for sending data via OCPP (s)Not relevantYesBannerSendIntervalNoBannerSendInterval_banner
Number of connected parking sensorsNot relevantYesBannerMaxNodeIdNoBannerMaxNodeId_banner
Update geolocation dataMasterNoGeolocationUpdateNoUpdateGeolocationButton_custom
Delete all Smart Charging profilesMasterYesNot AvailableNoDeleteAllSmChrgProfilesButton_custom
EEBUSStartPairingButtonMasterNoNot AvailableNoEEBUSStartPairingButton_eebus
EEBUSClearPairingButtonMasterNoNot AvailableNoEEBUSClearPairingButton_eebus
StartIndividualNoNot AvailableNoStartChargeViaWebInterface_webcharging
StopIndividualNoNot AvailableNoStopChargeViaWebInterface_webcharging
Start (Connector 2)IndividualNoNot AvailableNoStartChargeViaWebInterface_webcharging_2
Stop (Connector 2)IndividualNoNot AvailableNoStopChargeViaWebInterface_webcharging_2

6. OCPP REST

Description: This section provides details for the OCPP REST tab extracted from the documentation HTML.

Key nameKey values or example
conn_stateno_vehicle_connected
vehicle_connected_schuko
vehicle_charging_schuko
vehicle_connected_type2
vehicle_charging_type2
vehicle_connector_error
auth_statenot_authorized_for_charging
wait_for_auth
authorized_for_charging
auth_timeout
auth_uide.g: 046e453af012ca3
time_since_charging_starte.g: 2127
meter_whe.g: 426416
power_we.g: 3600
transaction_whe.g: 13500
display_texte.g: <tariffInfoResponse>
<tariffEntry>
<chargeMode>
<maxPower>3.7</maxPower>
<currentType>AC</currentType> </chargeMode>
<hourPrice>60</hourPrice>
</tariffEntry>
<tariffEntry>
<chargeMode>
<maxPower>8.0</maxPower>
<currentType>AC</currentType>
</chargeMode>
<hourPrice>120</hourPrice>
</tariffEntry>
<tariffEntry>
<chargeMode>
<maxPower>22.0</maxPower>
<currentType>AC</currentType>
</chargeMode>
<hourPrice>300</hourPrice>
</tariffEntry></tariffInfoResponse>
cp_ide.g: +4983900000000001
ocpp_stateavailable
occupied
reserved
unavailable
faulted
preparing
charging
suspendedevse
suspendedev
finishing
type2_statea
b
c
d
e
type2_proximityno_cable
13
20
32
63
cable_attached
short_circuit
sig_currente.g: 16
schuko_stateidle
connected
power_on
backend_conn_statenot_connected
connecting
connecting_proxy_ok
connected
not_reacheable
rejected
pending
free_chargingoff
on
slave_stateavailable
occupied
reserved
unavailable
faulted
preparing
charging
suspendedevse
suspendedev
finishing
ocpp_meter_cfgehz_meter_rs232
s0_meter_opto_1
s0_meter_opto_2
no_meter
s0_meter_dedicated_input
internal_meter
modbus_meter_abb
modbus_meter_eastron_sdm630
modbus_meter_eastron_sdm120_220
modbus_meter_garo_gnm3d
modbus_meter_garo_gnm1d
modbus_meter_garo_gm3t
modbus_meter_garo_EM270
modbus_meter_finder
modbus_meter_saia_ale3
modbus_meter_inepro_pro1_2
modbus_meter_inepro_pro380
modbus_meter_optec
ocpp_meter_seriale.g: 65465484ds
current_ae.g: 14.0,14.5,14.1
energy_man_currente.g: 12
ambient_tempe.g: +25.30
firmware_vere.g: 5.33.5-21150
cc_serial_ne.g: 1703512493/b94060007
manuf_serial_ne.g: 1703512493
con_cycles_schukoe.g: 560
con_cycles_type2e.g: 1450
max_currente.g: 32
rcmb_state
triggered
okay
rcmb_maxe.g: 0.0, 0.0
rcmb_valuese.g: 0.0, 0.0
cable_attachedoff
on
schuko_cfgdisable
enable
rcd_statedisable
triggered
okay
mcb_type2_statedisable
triggered
okay
mcb_schuko_statedisable
triggered
okay
cp_vendore.g: Bender GmbH Co. KG
errorse.g: plug_locking_failed;;rfid_reader_not_communicating
cp_modele.g: CC612_2M3PR
voltage_ve.g: 230,230,230
wlan_statewlan_disconnected
wlan_connected

7. Modbus Slave Registers

Description: This section provides details for the Modbus Slave Registers tab extracted from the documentation HTML.

Reg. TypeAddressNameR/WNr. Regs.Description
Holding1000Charge Point StateR1
Holding1001Charge StateR1
Holding1002EVSE StateR1
Holding1004Cable StateR1
Holding1006EVSE Error CodeR1
Holding1008Current L1R1Returns the current of phase 1 of the ocpp meter in mA.
Holding1010Current L2R1Returns the current of phase 2 of the ocpp meter in mA.
Holding1012Current L3R1Returns the current of phase 3 of the ocpp meter in mA.
Holding1020Active PowerR2
Holding1024Active Power L1R2
Holding1028Active Power L2R2
Holding1032Active Power L3R2
Holding1036EnergyR2
Holding1100Hardware current limitR1
Holding1102Minimum current limitR1
Holding1104Max. Current from EVSER1
Holding1106Max. Current from CableR1
Holding1108Max. Current from EVR1
Holding1200User priorityR1
Holding1300EV Battery State (% 0-100)R1Returns an estimate of the SoC
Holding1302EV Battery Capacity (Wh)R2Returns an estimate of the EV Battery Capacity
Holding1400Schedule TypeR1
Holding1402Required Energy (Wh)R2
Holding1406Required Battery State (% 0-100)R1
Holding1408Scheduled Time (hhmmss)R2
Holding1412Scheduled Date (yymmdd)R2
Holding1502Charged Energy (Wh)R1Sum of charged energy for the current session
Holding1504Start Time (hhmmss)R2Start time of charging process
Holding1508Charging Time (seconds)R2Duration since beginning of charge
Holding1512End Time (hhmmss)R2End time of charging process
Holding1600User IDR2User ID (OCPP IdTag) from the current session. Bytes 0 to 3.
Holding1602User IDR2User ID (OCPP IdTag) from the current session. Bytes 4 to 7.
Holding1604User IDR2User ID (OCPP IdTag) from the current session. Bytes 8 to 11.
Holding1606User IDR2User ID (OCPP IdTag) from the current session. Bytes 12 to 15.
Holding1608User IDR2User ID (OCPP IdTag) from the current session. Bytes 16 to 19.
Holding162015118 Smart vehicle detectedR1Returns 1 if an EV currently connected is a smart vehicle, or 0 if no EV connected or it is not a smart vehicle
Holding2000Safe Current (Amps.)R/W1Max. charge current under communication failure
Holding2002Comm. Timeout (seconds)R/W1Communication timeout
Holding5000Charge Power (W)W2
Holding5004Charge Current (A)W1
Holding5006Charge Control1Unimplemented
Holding5008Charge Release1Unimplemented
Holding5900Free ChargingR/W1Unimplemented
Holding5902Free Charging ModeR/W1Unimplemented
Holding6000Life BitR/W10/1 Toggle-Bit

8. Logging Components

Description: This section provides details for the Logging Components tab extracted from the documentation HTML.

Component numberComponent name
0DEFAULT
1LOGGING
2DLM
3PIC24
4SLAC
5GPIO
6MONITORING
7QCA700X_FLASH
8RCMB
9METER
10METER_EHZ
11METER_S0
12METER_INTERNAL
13METER_MODBUS
14SQL
15RFID
16LOG_FILE
17SYSCLOCK
18SOCKETTYPE2
19SCHUKO
20OCPP
21GSM
22P15118
23VEHICLEIF
24ASN1
25HUMIDITY_SENSOR
26NOR_STORE
27ETHREAD
28EEVT
29MK_PIC24
30TIMER_POOL
31COMPONENT_MGR
32PLUG
33I2C
34AUTH_INPUT
35HW_VARIANT_MGR
36WEB_INTERFACE
37WEB_INTERFACE_NG
38STM32_EO
39EICHRECHT
40HEMS
41BACKEND
42ERROR_HANDLING
43HMI
44MASTER_SLAVE
45PROTOCOLS
46PARAMETERS
47WEBDATA
48NTP
49MODBUS_RTU
50MODBUS_DEVICE
51TIMEZONE
52CCS_MODE4
53USB_HOTPLUG
54USBLIB_MOD
55METER_DC_DZG
56STM32_HMI
57MS_COMM
58SU_COMM
59WS_SERVER
60ENERGY_MAN
61ALL