Skip to main content

Parameters

Version-aware parameter reference and filterable settings table.

v5.33.5
Applies to
operatorsmanufacturers
UpdatedSep 10, 2026

Parameters

1 Parameters reference

Use the table below to browse the available settings parameters across supported controller versions. The data is currently backed by the extended settings payload and will be expanded with version-specific files over time.

Showing 142 parameters for Latest (extended). The table is now version-aware and can be expanded with version-specific data files later.

KeyLabelSectionGroupDescriptionTypeDefaultMode
WebUINetworkUserEnabled_networkAllow 'user' to configure networkNetworkConfigIf switched 'On' the 'user' account is able to configure parameter in this group 'Network'. If 'Off' this group 'Network' is invisible for 'user' account.enum1rw
ConfigUserEnabled_networkConfigUserEnabled_networkNetworkConfigenum1ro
WebUIEnabledGSM_modemShow Modem ConfigurationNetworkGSMShow or hide the modem configuration.enum0rw
APN_modemAccess Point Name (APN)NetworkGSMAccess Point Name of the mobile network to be used when establishing connections to the backend system via the built-in modem.stringrw
APNUsername_modemAPN UsernameNetworkGSMUsername to be used for authenticating with the Access Point of the mobile network for connecting with the backend system.stringrw
APNPassword_modemAPN PasswordNetworkGSMPassword to be used for authenticating with the Access Point of the mobile network for connecting with the backend system.passwordrw
SIMCardPinNumber_modemSIM PINNetworkGSMPIN number that should be used to unlock the SIM card. This number is only used if the SIM card requires a PIN number.passwordrw
NetworkOperSelMode_modemNetwork selection modeNetworkGSMIn Automatic mode the modem chooses the operator. In manual mode the operator specified in requested operator name is used. In Manual/Auto, if manual selection fails, automatic mode is used.enum0rw
NetworkType_modemModem Access TechnologyNetworkGSMThe technology to be used to access the network 2G (GSM), 3G (UTRAN) or 4G (LTE). In auto mode the modem will choose the technology.enum0rw
ReqNetworkOperator_modemRequested Network operatorNetworkGSMThe name of the network operator to be used in manual 'Network selection mode'.stringrw
NetworkOperNameFormat_modemNetwork operator name formatNetworkGSMIndicates 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).enum1rw
WANRouter_tcpipWAN routerNetworkGSMEnables access from LAN interfaces (Ethernet/WLAN/USB) to WAN (GSM) interface. This will also enable the DNS forwarder.enum0rw
GSM_PPP_MTU_modemMTUNetworkGSMMaximum transmission unit size for GSM connections (in bytes)(valid value range: 68 - 1492).stringrw
WebUIEnabledLAN_tcpipShow LAN ConfigurationNetworkLANShow or hide the LAN configuration.enum0rw
NetworkConfig_mode_tcpipMode for ethernet configurationNetworkLANMode 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.enum0rw
NetworkConfigStaticAddress_tcpipStatic network configuration IPNetworkLANStatic LAN IP of the ChargePoint.string192.168.0.100rw
NetworkConfigStaticNetmask_tcpipStatic network configuration netmaskNetworkLANNetmask to use for the LAN of the ChargePoint.string255.255.255.0rw
NetworkConfigStaticGateway_tcpipStatic network configuration gatewayNetworkLANGateway to use for the LAN of the ChargePoint.string192.168.0.1rw
NetworkConfigStaticDNS_tcpipStatic network configuration DNSNetworkLANDNS server to use for the LAN of the ChargePoint.string8.8.8.8rw
NetworkConfigDHCPRetries_tcpipDHCP client request retriesNetworkLANDHCP request number of retries before giving up.int10rw
NetworkConfigDHCPTimeout_tcpipDHCP client request timeoutNetworkLANDHCP request timeout in seconds.int10rw
NetworkConfigDHCPDelay_tcpipDHCP client request delayNetworkLANDHCP request delay between multiple requests in seconds.int10rw
NetworkConfigHostname_tcpipClient hostnameNetworkLANNetwork hostname used for DHCP and mDNS.stringrw
EthernetSpanningTree_lanSpanning Tree ProtocolNetworkLANEnable this to allow detection and handling of loops in the ethernet network link topology. If a loop is detected the charge controller will disable communication on one of its two ethernet ports to prevent network disturbances. Similarly the communication on this port will be reactivated when the loop is gone.enum1rw
USBShowHideConfiguration_dlShow USB ConfigurationNetworkUSBShow or hide the USB configuration.enum0rw
USBAdditionalIP_dlStatic USB network configuration additional IPNetworkUSBAssigns an additional fixed IP to the usb device interface of the ChargePoint. This allows grouping multiple ChargePoint in one USB network. The subnet is fixed at 24 bits 255.255.255.0stringrw
USBAdditionalGW_dlStatic USB network configuration gatewayNetworkUSBAssigns a gateway to the usb device interface of the ChargePoint. Note: please be careful when setting a gateway here, as might conflict with a gateway set in the AN or Ethernet configuration sections.stringrw
USBAdditionalDNS_dlStatic USB network configuration DNSNetworkUSBAssigns an additional DNS server to the ChargePoint in case USB is used as backend connection path.stringrw
Enabled_wlanWLAN enabledNetworkWLANEnable or disable WLAN.enum1rw
WLANSSID_wlanWLAN SSIDNetworkWLANSSID of the WLAN the ChargePoint tries to connect to.stringrw
WLANPassword_wlanWLAN passwordNetworkWLANPassword of the WLAN the ChargePoint connects to. The Chargepoint automatically chooses the correct encryption method of the WLAN.passwordrw
NetworkConfig_mode_wlanMode for WLAN configurationNetworkWLANNetwork 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).enum0rw
NetworkConfigStaticAddress_wlanStatic network configuration IPNetworkWLANStatic WLAN IP of the ChargePoint.string192.168.1.100rw
NetworkConfigStaticNetmask_wlanStatic network configuration netmaskNetworkWLANNetmask to use for the WLAN of the ChargePoint.string255.255.255.0rw
NetworkConfigStaticGateway_wlanStatic network configuration gatewayNetworkWLANGateway to use for the WLAN of the ChargePoint.string192.168.1.1rw
NetworkConfigStaticDNS_wlanStatic network configuration DNSNetworkWLANDNS server to use for the WLAN of the ChargePoint.string8.8.8.8rw
NetworkConfigDHCPRetries_wlanDHCP client request retriesNetworkWLANNumber of DHCP requests sent before giving up on the DHCP server.int10rw
NetworkConfigDHCPTimeout_wlanDHCP client request timeoutNetworkWLANDHCP request timeout in seconds.int10rw
NetworkConfigDHCPDelay_wlanDHCP client request delayNetworkWLANDHCP request delay (in seconds) between multiple requests .int10rw
ChargePointID_ocppOCPP ChargeBoxIdentity (ChargePointID)BackendOCPPID that is sent to the backend and used by the backend to identify the ChargePoint.string+49*839*00000000001rw
EvseID_ocppEVSE IdentityBackendOCPPThe 'EVSE Identity' can be used to differentiate a technical ID in the backend from the ID that is presented to the user. If set, the 'EVSE Identity' will be used for ISO 15118 certificate signing requests. When left empty, the ISO 15118 name of the EVSE will be derived from the 'ChargeBoxIdentity'.stringrw
TCP_IP_MODE_V2_tcpipOCPP ModeBackendOCPPThis 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.enum0rw
JsonOCPPBackendURL_tcpipWebSockets JSON OCPP URL of the BackendBackendOCPPThe 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.stringws://127.0.0.1:8081/CentralSystemServicerw
WebsocketsProxyURL_tcpipWebsockets proxyBackendOCPPSpecify the websockets proxy to connect to in the format HOST:PORT, whereby PORT is optional and set to 80 when not specified.stringrw
WebSocketsKeepAliveInterval_tcpipWebSockets keep-alive intervalBackendOCPPWebSockets 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.int0rw
OCPPConStrictTls_tcpipOCPP connection strictnessBackendOCPPIf '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. enum0rw
HTTPBasicAuthPassword_tcpipHTTP Basic Authentication passwordBackendOCPPThe password to be used for HTTP Basic Authorization. If left empty, HTTP Basic Authorization is not used.passwordrw
ForceHeartBeat_ocppForce Heartbeat request messagesBackendOCPPSets if the Charge Point should send OCPP Heartbeat request messages despite other messages being sent.enum1rw
InfoStatusNotifications_ocppSend informative StatusNotificationsBackendOCPPThis 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.enum1rw
ErrorStatusNotifications_ocppSend error StatusNotificationsBackendOCPPThis 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.enum1rw
UsbErrorStatusNotifications_ocppSend USB error StatusNotificationsBackendOCPPThis parameter determines whether USB communication errors between master and slave are reported to backend.enum0rw
StatusNotificationStrategy_ocppStrategy for StatusNotification state transitionsBackendOCPPThis 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.enum1rw
AllowLongOcppGetConfKeys_ocppAllow long get configuration keysBackendOCPPAllows OCPP keys in get configuration command to be longer than 500 characters.enum0rw
OcppGetConfBoolIsInt_ocppInteger values for boolean get configuration keysBackendOCPPIf 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.enum1rw
OcppQueueFullAsErrorState_ocppDisallow charging if OCPP queue fullBackendOCPPWhen set, a full OCPP message queue will cause an error state. Charging will be terminated.enum0rw
UnavailAtFwUpdateBegin_customState 'unavailable' at FW update beginBackendOCPPIf 'On' set CP state to 'unavailable' at the begin of the FW update, immediately after the update request. If 'Off' set CP state to 'unavailable' at the begin of the installing process, after download and any update delay timer.enum1rw
ForceFwUpdateMaster_msForce firmware update on masterBackendOCPPIf 'On' the firmware update will be installed on master even if not all slaves could download it and their update failed. If 'Off' the firmware update will only be installed on master if all slaves have successfully downloaded it.enum0rw
ForceStateAvail_ocppForce OCPP connector state to available/unavailableBackendOCPPForce the OCPP connector state to change to available/unavailable. This overrides the actual state set by the backend.enum0rw
FreeCharging_vehicleifFree ChargingAuthorizationFree ChargingAllows charging without authorization via RFID or the backend. Charging is started immediately after a vehicle is connected.enum0rw
FreeChargingMode_ocppFree Charging ModeAuthorizationFree ChargingSets 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.enum0rw
RfidTagFreeCharging_ocppRFID Tag for Free Charging with OCPP Full, fixed rfid modesAuthorizationFree ChargingRFID Tag for Free Charging with OCPP Full, fixed RFID modes. Note this RFID Tag is also used when 'If in doubt allow charging' is 'ImmediatelyWhenPlugged'stringfreechargingrw
RfidTagFreeChargingConnector2_ocppRFID Tag for Free Charging with OCPP Full, fixed rfid modes (Connector 2)AuthorizationFree ChargingRFID Tag for Free Charging with OCPP Full, fixed RFID modes. (Connector 2)stringrw
IfInDoubtAllowCharging_ocppIf in doubt allow chargingAuthorizationFree ChargingThis 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. enum0rw
FllCfg_fllEnable local whitelistAuthorizationRFID WhitelistsLocal whitelist of RFIDs independent of a backend connection.enum0rw
UseCache_ocppEnable OCPP whitelistAuthorizationRFID WhitelistsEnables 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.enum1rw
CacheExpiryOption_cacheOCPP whitelist expiry modeAuthorizationRFID WhitelistsThe assumed expiry date of cache entries when OCPP expiry-date has not been set explicitly by the backend. The default setting for such cache entries is the largest allowable system time: 2038enum0rw
LocalPreAuthorize_ocppLocal Pre AuthorizeAuthorizationRFID WhitelistsSets if the Charge Point, when online, will start transactions for locally authorized identifiers without requesting an Authorize.conf from the Central System.enum1rw
LocalAuthorizeOffline_ocppLocal Authorize OfflineAuthorizationRFID WhitelistsSets if the Charge Point, when offline, will start transactions for locally authorized identifiers.enum1rw
OperatorCurrentLimit_vehicleifOperator Current Limit [A]Load ManagementLocalMaximum current (in ampere) 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 managementint16rw
MonitoringSessionEnergy_monMax Energy per session [kWh]Load ManagementLocalEnergy limit (in kWh) set by the operatorint0rw
MonitoringSessionTime_monMax Time per session [h]Load ManagementLocalTime limit (in h) set by the operatorint0rw
PowerLimiterMode_energymanPower Limiter ModeLoad ManagementLocalPower limiter can be set to the Austrian slow-charging mode or manual configuration conservative mode or manual configuration progressive mode. Identical behaviour on a 2-socket station (master/slave). The mode applies per charge point.enum0rw
PowerLimit_energymanPower limit [W]Load ManagementLocalSet power limit (in Watt). Identical behaviour on a 2-socket station (master/slave). The limit applies per charge point. Range: from 4140W to 43000W.int22000rw
InputPowerLimit_energymanEnergy management from external inputLoad ManagementLocalEnables energy Management from external inputenum0rw
InputCurrentLimit_energymanCurrent limit for energy management from external inputLoad ManagementLocalSingle phase RMS current limit (in A) for energy management from external input. Range: from 6A to 80 A. Set to 0A to pause charging.int16rw
SmartChargingUseDisconnectedLimit_energymanEnable Disconnected Upper Limit for SmartChargingLoad ManagementLocalIf 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.enum0rw
SmartChargingDisconnectedLimit_energymanDisconnected Upper Limit [A] for SmartChargingLoad ManagementLocalDisconnected Upper Limit applied to SmartCharging in case the ChargePoint is disconnected from the backend.int16rw
DeleteAllSmChrgProfilesButton_customDelete all Smart Charging profilesLoad ManagementLocalDelete all Smart Charging profiles from controller. This is useful to remove old data from controller after you changed the load balancing system.action
SempGatewayConfigOnOff_semp_gatewaySEMP interfaceLoad ManagementSMA Sunny Home Manager InterfaceThe charging station can be networked with the SMA Sunny Home Manager 2.0 to charge primarily or exclusively with self-generated solar energy.enum0rw
SempGatewayChargingMode_semp_gatewayCharging ModeLoad ManagementSMA Sunny Home Manager InterfaceThis 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.enum0rw
SempGatewayFallbackCurrent_semp_gatewayCurrent in case of connection failure [A]Load ManagementSMA Sunny Home Manager InterfaceIf the connection to the energy manager fails, the charging current is set to the value set here. Settings between 6A and 80A are permissible.int6rw
SempGatewayCommunicationTimeout_semp_gatewayTime to connection failure [s]Load ManagementSMA Sunny Home Manager InterfaceIf the charging station cannot reach the energy manager for longer than set, the connection is considered to have failed. Possible value range: 60s to 3600s.int600rw
SempGatewayMaxEnergyDemand_semp_gatewayMaximum energy demand [kWh]Load ManagementSMA Sunny Home Manager InterfaceThis 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.int30rw
SempGatewayMinEnergyDemand_semp_gatewayMinimum energy demand [kWh]Load ManagementSMA Sunny Home Manager InterfaceThis 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.int5rw
SempGatewayMaxChargingTime_semp_gatewayScheduled departure time [hh:mm]Load ManagementSMA Sunny Home Manager InterfaceThis 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.string08:00rw
EEBUSConfigOnOff_eebusEEBus interfaceLoad ManagementEEBUSCompatible energy managers can control the charging station via the EEBus interface.enum0rw
ChargingMode_hemsCharging ModeLoad ManagementEEBUSThis 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" configures the usage of self produced solar power for charging. Both options aims to optimize the self-consumption whereas "Solar surplus charging" configures additionally the exclusive use of solar surplus power for charging.enum0rw
EEBUSConfigCevcOnOff_eebusCoordinated Charging ModeLoad ManagementEEBUSCompatible energy managers can control the charging station via the EEBus interface.enum0rw
MaxEnergyDemand_hemsMaximum energy demand [kWh]Load ManagementEEBUSThis 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.int30rw
OptEnergyDemand_hemsOptimal energy demand [kWh]Load ManagementEEBUSThis 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.int8rw
MinEnergyDemand_hemsMinimum energy demand [kWh]Load ManagementEEBUSThis 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.int5rw
MaxChargingTime_hemsScheduled departure time [hh:mm]Load ManagementEEBUSThis 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.string08:00rw
EEBUSFallbackCurrent_eebusCurrent in case of connection failure [A]Load ManagementEEBUSIf the connection to the energy manager fails, the charging current is set to the value set here. Settings between 6A and 80A are permissible.int6rw
EEBUSCommunicationTimeout_eebusCommunication Timeout [s]Load ManagementEEBUSIf 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: 4s to 3600s.int4rw
EEBusLPCFailsafePowerUser_eebusFailsafe power in case of connection failure [W]Load ManagementEEBUSIf the connection to the energy manager fails, the failsafe power for LPC is set to the value set here.int11040rw
EEBusLPCFailsafeDurationMinUser_eebusMinimum duration for failsafe state [s]Load ManagementEEBUSThe minimum duration that the system will remain in the LPC failsafe state if the connection to the energy manager fails. Possible value range: 7200s to 86400s.int7200rw
EEBUSCoupledEnergyManager_eebusConnect or disconnect the energy managerLoad ManagementEEBUSCouple energy manager activates the EEBUS coupling process. The coupling must also be activated on energy manager side.string{"model": "", "ski": "", "ip": "", "shipId": "", "coupled": 0}rw
DlmMode_dlmDynamic Load Management - DLM Master/SlaveLoad ManagementDynamic Load ManagementSpecifies 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!enum0rw
DlmDiscoveryNetworkId_dlmDLM Network IdLoad ManagementDynamic Load ManagementSeveral DLM groupings might coexist in one physical LAN. In case of DLM Master-Auto-Discovery, they are distinguished by Master-Auto-Discovery Network Id.int0rw
DlmDiscoveryDisableBroadcast_dlmDisable Discovery BroadcastingLoad ManagementDynamic Load ManagementDisables 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.enum0rw
DlmSolarMode_dlmConfigure Solar Mode for DLMLoad ManagementDynamic Load ManagementWhether this DLM Master allows special handling of DLM-Slaves that want to use solar energy. 'Solar Surplus' will allow those slaves to charge only when there is enough solar energy available. 'Solar Charging' allows to use some amount of grid supply current(see parameter 'Maximum grid supply current') to charge the solar DLM slaves at least with their minimum charging current. With 'Grid Charging' all DLM slaves charge with the maximum available current.enum0rw
DlmAlgoSampleRate_dlmDLM Algorithm Sample RateLoad ManagementDynamic Load ManagementThe DLM algorithm will not calculate and re-assign current to it's DLM slaves any faster than at this configured rate. As an exception, EVs getting ready to charge will be considered and assigned current immedeately.enum30rw
DlmClearPersistentSlavesButton_dlmClear persistent DLM slave DBLoad ManagementDynamic Load ManagementImmediately clears the database of known DLM slavesaction
DlmSlaveEnableSolar_dlmSolar Mode on this chargerLoad ManagementDynamic Load ManagementEnables additional limiting for this DLM-Slave to use renewable productionenum0rw
DlmSlaveEnableSolarUser_dlmUser is allowed to switch the SolarMode on this chargerLoad ManagementDynamic Load ManagementIf the role 'operator' set 'yes', the role 'user' should see the parameter on the page 'load management' and have the permission to set the 'Solar Mode on this charger' to either 'on' or 'off'.enum0rw
DlmMinCurrentRating_dlmMinimum Current Limit [A]Load ManagementDynamic Load ManagementMinimum current limit that charging should not go below.int6rw
DlmDisconnectedLimit_dlmDisconnected Limit [A]Load ManagementDynamic Load ManagementCurrent limit when disconnected from DLM network.int6rw
DlmMasterIp_dlmDLM Master IP and portLoad ManagementDynamic Load ManagementDLM Master IP which is used for DLM-Slaves configured with Master-Fixed-IP. Additionally the connection port can be specified (IP[:port]).stringrw
DlmPhaseLimit_dlmEVSE Sub-Distribution Limit (L1/L2/L3) [A]Load ManagementDynamic Load ManagementOverall current limit for DLM available for distribution to EVs.triple16rw
DlmOperatorLimit_dlmOperator EVSE Sub-Distribution Limit (L1/L2/L3) [A]Load ManagementDynamic Load ManagementOperator 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'.triple16rw
DlmInput1CurrOffsetConfig_dlmExternal Input 1 ConfigLoad ManagementDynamic Load ManagementAdds a configurable offset to 'EVSE Sub-Distribution Limit' based on GPI External Input 1.enum0rw
DlmInput1Polarity_dlmExternal Input 1 PolarityLoad ManagementDynamic Load ManagementChanges the polarity of the input signal 1. "Active high" does not change the polarity, "Active low" inverts the signal.enum0rw
DlmInput1OffsetPhase_dlmExt. Input 1 Current Offset (L1/L2/L3) [A]Load ManagementDynamic Load ManagementOffset added to 'EVSE Sub-Distribution Limit' case external input 1 is high. Note: currently only negative values are supported.triple0rw
DlmInput2CurrOffsetConfig_dlmExternal Input 2 ConfigLoad ManagementDynamic Load ManagementAdds a configurable offset to 'EVSE Sub-Distribution Limit' based on GPI External Input 2.enum0rw
DlmInput2Polarity_dlmExternal Input 2 PolarityLoad ManagementDynamic Load ManagementChanges the polarity of the input signal 2. "Active high" does not change the polarity, "Active low" inverts the signal.enum0rw
DlmInput2OffsetPhase_dlmExt. Input 2 Current Offset (L1/L2/L3) [A]Load ManagementDynamic Load ManagementOffset added to 'EVSE Sub-Distribution Limit' case external input 2 is high. Note: currently only negative values are supported.triple0rw
DlmExternalMeterEnabled_dlmExternal Meter SupportLoad ManagementDynamic Load ManagementIf 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.enum0rw
ConfigSecond_meterMeter configuration (Second)Load ManagementDynamic Load ManagementEnergy 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.enum3rw
DlmInput3CurrOffsetConfig_dlmMeter Digital Input ConfigLoad ManagementDynamic Load ManagementAdds a configurable offset to 'EVSE Sub-Distribution Limit' based on the Meter's Digital Input register.enum0rw
DlmInput3OffsetPhase_dlmMeter Digital Input Current Offset (L1/L2/L3) [A]Load ManagementDynamic Load ManagementOffset added to 'EVSE Sub-Distribution Limit' case meter digital input is high. Note: currently only negative values are supported.triple0rw
SecondMeterIPAddress_meterIP address of second meterLoad ManagementDynamic Load ManagementSets the IP address of the second meter.stringrw
SecondMeterTCPPortNumber_meterPort number of second meterLoad ManagementDynamic Load ManagementSpecifies the TCP port of the second meter.int502rw
SecondMeterModbusAddr_meterModbus address of second meterLoad ManagementDynamic Load ManagementSecondary meters use a default address of '2'. If both meters share a RTU bus then their addresses must be different.int2rw
S0MeterPulsesPerKWhSecond_meterPulses per kWh (Second S0 meter)Load ManagementDynamic Load ManagementEnergy Management: Second S0 Meter Pulses per kWh.int1000rw
CurrentDirSecondL1_meterCurrent flow direction of L1 of second meterLoad ManagementDynamic Load ManagementIf set to 'Inverted', the current and power value reported by the second meter in line 1 will be inverted in sign.enum0rw
CurrentDirSecondL2_meterCurrent flow direction of L2 of second meterLoad ManagementDynamic Load ManagementIf set to 'Inverted', the current and power value reported by the second meter in line 2 will be inverted in sign.enum0rw
CurrentDirSecondL3_meterCurrent flow direction of L3 of second meterLoad ManagementDynamic Load ManagementIf set to 'Inverted', the current and power value reported by the second meter in line 3 will be inverted in sign.enum0rw
DlmExternalMeterMainDistLimit_dlmMain Distribution Limit (L1/L2/L3) [A]Load ManagementDynamic Load ManagementCurrent 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.triple100rw
DlmExternalLoadHeadroom_dlmExternal Load Headroom (L1/L2/L3) [A]Load ManagementDynamic Load ManagementSafety margin to avoid transient overload situations. The algorithm will keep headroom towards 'Main Distribution Limit'triple0rw
DlmExternalLoadFallback_dlmExternal Load Fallback (L1/L2/L3) [A]Load ManagementDynamic Load ManagementIn 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 stoptriple9999rw
DlmExternalMeterLocation_dlmExternal Meter LocationLoad ManagementDynamic Load ManagementSpecifies how the external meter is connected according to its location. Either at the grid's entry point; between an external load and the rest of the installation; or at a renewable energy source such as e.g. a solar panel. It is also possible to locate the site of the external meter on the EVSE sub-distribution point (which means all DLM slaves) and a renewable energy source without external load.enum0rw
DlmExternalEnergyType_dlmExternal Energy TypeLoad ManagementDynamic Load ManagementSpecifies the type of energy connected to installation. Either a consumer of electricity or a producer of renewable energy such as a solar array.enum0rw
DlmExternalLoadAvgLen_dlmExternal Load Averaging Length [sec]Load ManagementDynamic Load ManagementMeter values will be averaged in order to avoid transients.int5rw
DlmCurrImbalanceLimitEnabled_dlmCurrent Imbalance PreventionLoad ManagementDynamic Load ManagementIf enabled, DLM will not exceed the 'Current Imbalance Limit' configured.enum0rw
DlmCurrImbalanceLimit_dlmCurrent Imbalance Limit [A]Load ManagementDynamic Load ManagementMaximum allowed phase imbalance. DLM will not exceed the 'Current Imbalance Limit' between phases when assigning current to EVs.int20rw
DlmITNetworkEnabled_dlmIT NetworkLoad ManagementDynamic Load ManagementSet to 'On', if your power distribution system is IT (isolé-terre). If set to 'On', the DLM Master will only accept DLM Slaves, whose phase rotation is set to 'Single-phase system (IT earthing)'. If set to 'Off', the DLM Master will only accept DLM Slaves, whose phase rotation is not set to 'Single-phase system (IT earthing)'. Connection attempts of DLM Slaves configured differently will be denied.enum0rw
DlmTimeTableEnabled_dlmMaximum Current SchedulerLoad ManagementDynamic Load ManagementIf enabled, DLM will not exceed the limit configured in the time tables. Each entry set specifies the maximum allowed current for each phase which is applied at the selected hour. Each entry is valid until another applicable entry replaces it. NOTE: All time values use the UTC time zone. Example: Two entries: (5am: 10/10/10Amp) and (10am: 20/20/20Amp) would apply a maximum of 10Amp starting at 5am UTC and would apply until 9:59:59am UTC. At 10am UTC the maximum would be set to 20Amp and be valid until 4:59:59am UTC the next day.enum0rw
DlmTimeTableTable_dlmDLM Time TableLoad ManagementDynamic Load Managementtable
UserPwdPlain_customUser PasswordSystemPasswordSet a new login password of the web interface for the 'user' user.doubleEntryPasswordgreen_zonerw
InstallerPwdPlain_customInstaller PasswordSystemPasswordSet a new login password of the web interface for the 'installer' user.doubleEntryPasswordblue_zonerw
OperatorPwdPlain_customOperator PasswordSystemPasswordSet a new login password of the web interface for the 'operator' user. If using secure login passwords is enforced, the new password has to fulfill these requirements: The minimum length is 8 characters. The password has to contain at least one character each from the following character groups: lowercase letters a..z, uppercase letters A..Z, digits 0..9, special characters. It shall not be possible to crack the password easily by repeated guessing.doubleEntryPasswordyellow_zonerw
WebUIPublicKey_customWebUIPublicKey_customSystemPasswordstring-----BEGIN PUBLIC KEY----- MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9V0ZHPh6hnAuf2MZ5RU0W+NnP eaHIlsGx6YW8hvz0WRmybGO3fFJS0ZUo16G2dWb0NxIBbRjN8ZERvjH7wbnIBj6c ISAxp/xvWWTq1VNt+4qDCVDvwJfdEdYBSroEYhunxThpuMo/oxyFmJZmMBIY/Tap wvp/DB0CYBKI2XGhjQIDAQAB -----END PUBLIC KEY----- rw