69
Value
Description
Use local white-list
Yes:
local list of authorized users -> Enabled
No:
local list of authorized users -> Disabled
Authorization check order
Local:
ID authorization has first place on the local white-
-list. If the user does not exist locally, then in second
place backend is asked to obtain the authorization.
CS:
ID authorization is always asked to the backend.
NOTE:
This setting only applies when Charge Point is
online; otherwise the authorization is only locally.
Authorize always in offline
mode
Yes:
If user is not present locally in the local white-list
and charge point cannot ask to the backend, user is
allowed to start a new charge transaction.
No:
If user is not present locally in the local white-list
and charge point cannot ask to the backend, the user is
not allowed to start a new charge transaction.
Retry after CS internal error
Yes:
Enabled. If StatusNotification, StartNotification
or StopNotification are not received correctly by the
backend, charge point retries again to send those
requests until it is received correctly.
No:
Disabled.
NOTE: Special development must be done in backend in
order to retry the messages by charge point.
Summary of Contents for CCS
Page 1: ...Instruction Manual Raption 50 Series ...
Page 2: ......
Page 4: ......
Page 10: ...06 Raption 50 Series Instruction Manual C Dimensions Units specified in millimeters ...
Page 39: ...35 3 CONNECTOR DISABLE 4 CONNECTOR IN USE ...
Page 40: ...36 Raption 50 Series Instruction Manual 5 CONNECTOR RESERVED 6 CONNECTOR BLOCKED PER RESERVED ...
Page 41: ...37 7 CONNECTOR BLOCKED PER CHARGING ...
Page 43: ...39 ...