Circutor URBAN - OCPP 1.6 Authorization Settings Explained

URBAN - URBAN WB
Instruction Manual
56
Value Description
Authorization
cache enabled
YES: maintain a local list of all presented identifiers that have been
successfully authorized by the Central System.
NO: authorization for presented identifiers is requested directly to
the Central System
Authorize remote
Tx requests
YES: the Charge Point asks for authorization when the Central Sys-
tem sends a remote start
NO: the Charge Point starts the Charge Transaction when the Central
System sends a remote start
Local pre-
-authorize
YES: Charge Point looks for locally-authorized identifiers without
waiting for the Central System authorization.
NO: Charge Point requests authorization for presented identifiers to
the Central System.
Allow offline Tx
for unknown Id
YES: during oine period unknown identifiers are allowed to start
charging
NO: during oine period unknown identifiers are NOT allowed to
start charging
Local authorize
off-line
YES: during oine period locally-authorized identifiers are allowed
to start charging
NO: during oine period locally-authorized identifiers are NOT al-
lowed to start charging
Stop transaction
on invalid Id
YES: stop existing Charge Transaction after response from Central
System when user is blocked, expired or invalid.
NO: Charge Transaction does not stop even if backend rejects the
user.