Menu Item: Authorization; Free Charging; Free Charging Mode „On; Free Charging Mode „Off - Webasto Live Configuration Instructions

9

Menu item: Authorization

9.1

Free Charging

The Webasto Live can be configured using "Free Charging" so that charging processes can be started by the user without authentica-
tion.
"Free Charging" is deactivated by default (parameter: "Off"). Both of the supplied RFID transponders are entered in the local access list
when delivered and can be used to activate the charging station.
Since it may nevertheless be required for invoicing purposes to transmit charging processes to a back end, different parameters can be
configured (e.g. for invoicing the processes of a company car).
9.2 Free Charging Mode „On"
Free Charging Mode – Behaviour of the charging station and parameters transmitted for charging processes without au-
thentication
Modus 1: „No OCPP"
No OCPP messages are sent to the back end. 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 back end, because all "Remote Stop" messag-
es are declined due to a missing "Transaction ID".
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 connected to the
vehicle. Only OCPP status messages are sent to the back end (e.g. charging point occupied). No "Start transaction" or "Stop transaction"
messages are sent to the back end.
NOTE
It is not possible to end an active charging process
from the back end, because all "Remote Stop" messag-
es are declined due to a missing "Transaction ID".
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 back end (e.g. charging
point occupied). No "Start transaction" or "Stop transaction" messages are sent to the back end.
NOTE
It is not possible to end an active charging process
from the back end, because all "Remote Stop" messag-
es are declined due to a missing "Transaction ID".
Mode 4: "With OCPP Full fixed RFID with auth"
Authentication is required via RFID to start the charging process. OCPP status messages (e.g. charging point occupied) as well as "Start
transaction" and "Stop transaction" are sent to the back end. The transmitted "Transaction ID" can be specified on the operator screen
under the "RFID Tag for Free Charging with OCPP Full, fixed rfid modes" menu item. "Remote Stop" messages are accepted for the cor-
rect "Transaction ID". The charging process can only be stopped locally by the same RFID media that started the charging process.
Mode 5: "With OCPP Full fixed RFID without auth"
Authentication is not required via RFID to start the charging process. The charging process starts as soon as the Webasto Live is con-
nected to the vehicle. OCPP status messages (e.g. charging point occupied) as well as "Start transaction" and "Stop transaction" are sent
to the back end. The transmitted "Transaction ID" can be specified on the operator screen under the "RFID Tag for Free Charging with
OCPP Full, fixed rfid modes" menu item. "Remote Stop" messages are accepted for the correct "Transaction ID". The charging process is
ended when the vehicle changes to charging status A or the cable is removed.
Mode 6: "With OCPP Full any RFID"
Authentication is required via RFID to start the charging process. OCPP status messages (e.g. charging point occupied) as well as "Start
transaction" and "Stop transaction" are sent to the back end. The transmitted "Transaction ID" is the ID of the currently used RFID me-
dia. "Remote Stop" messages are accepted for the correct "Transaction ID". The charging process can only be stopped locally by the
same RFID media that started the charging process.
9.3 Free Charging Mode „Off"
If in doubt allow charging – In case of doubt allow charging
With this parameter you can configure how the Webasto Live should behave when authentication of the user is not possible due to no
communication or a lost connection to the back end. Authorisation of the user is allowed temporarily until the parameters can be
15