Menu Item: "Hems; Menu Item: „Authorization - Webasto Live Konfigurationsanleitung

6 | Configuration menu
Defines whether or not OCPP status messages sent for informa-
tional purposes (such as a temperature report) should be sent to
the backend system.
"Send error StatusNotifications"
Defines whether or not OCPP status messages that contain an
error message (such as a broken charging cable receptacle)
should be sent to the backend system.
"Strategy for StatusNotification state transitions"
Defines under which conditions the charging station changes to
the "occupied" status.
In the "Occupied on Charging" status, an occupied signal is sent
only if authorisation is present and a cable is connected.
In the "Occupied on Authorized/Plugged" status, the "occupied"
status already changes
– when the charging station is authorised and no cable is
connected, or
– when a cable/vehicle is connected but authorisation has
not yet taken place.
„Allow long get configuration keys"
OCPP keys can have more than 500 characters in configuration
mode ("GetConfiguration").
„Disallow charging if OCPP queue full"
When this parameter is activated, an error is generated if the
queue for OCPP messages is full. The charging process is can-
celled.
After entering all relevant data, click on „Save" and then on
„Restart".
6.3.2 Subitem „General"
„Restart Transaction after power loss"
After a power failure, the Webasto Live has the possibility of
continuing with a charging process using the same authentica-
tion parameters and transmitting these to the backend again.
Default value: "On"
„Backend Connection Timeout"
This parameter specifies the time in seconds that a Webasto
Live waits for messages from the backend before requesting the
message again. This parameter also defines the time a Webasto
Live waits for dialling into the mobile phone network and estab-
lishing the connection to the backend.
NOTE
We recommend increasing this parameter in areas with
poor mobile phone reception.
NOTE
Setting a too high value results in a long waiting time
until the charging station implements commands from
the backend. This can lead to delays in operation of the
charging station.
Default value: 60
„SSL Strictness as client"
The Webasto Live enables secure communication to a backend
using SSL in multiple levels. Not every backend supports or
needs this parameter to be changed.
In order to use the Webasto backend, the predefined values
must not be changed. Request the parameter relevant for you
from your backend operator.
Default value: "Normal SSL Auth"
"TCP Watchdog Timeout"
10 / 19
The Webasto Live can reboot a system automatically if a long
period passes without a connection to the backend. The char-
ging station establishes a new connection to the backend after
a reboot.
u
Set the parameter to the value 0 to deactivate this function.
Default value: 0
„Display backend disconnect as error"
If this parameter is activated, the LED status bar indicates to the
user of the charging station whether an error has occurred in
the connection to the backend. The corresponding LED code
can be found in the installation and operating instructions.
Default value: „Off"
6.4

Menu item: "HEMS"

"Modbus TCP Server"
Changes the charging station to a Modbus slave. As a result
parameters can be read and written with the Modbus protocol.
See the documentation of the Modbus manufacturer for de-
tailed register information.
6.5 Menu item: „Authorization"
6.5.1 Subitem „Free Charging"
This menu item can be used to configure the Webasto Live so
that charging processes can be started without user authentica-
tion.
Default value: „Off"
Both of the supplied RFID transponders are entered in the local
access list when delivered and can be used to activate the char-
ging station.
When this mode is switched on ("On"), the following options
are available:
n Mode 1: "No OCPP"
No OCPP messages are sent to the backend. No authentication
is needed to start the charging process. The charging process
starts as soon as the Webasto Live is connected to the vehicle.
NOTE
It is not possible to end an active charging process from
the backend, because all "Remote Stop" messages are
declined due to a missing "Transaction ID".
n Mode 2: „With OCPP status notif without auth"
No authentication is needed to start the charging process. The
charging process starts as soon as the Webasto Live is connec-
ted to the vehicle. Only OCPP status messages are sent to the
backend (e.g. charging station occupied). No "Start transaction"
or "Stop transaction" messages are sent to the backend.
NOTE
It is not possible to end an active charging process from
the backend, because all "Remote Stop" messages are
declined due to a missing "Transaction ID".
n Mode 3: „With OCPP status notif with auth"
Authentication is required via RFID to start the charging process.
Only OCPP status messages are sent to the backend (e.g. char-
ging station occupied). No "Start transaction" or "Stop transac-
tion" messages are sent to the backend.
NOTE
It is not possible to end an active charging process from
the backend, because all "Remote Stop" messages are
declined due to a missing "Transaction ID".
n Mode 4: „With OCPP Full fixed RFID with auth"
5110490B Configuration Instructions Webasto Live