6. Allocating locking authorisations
6.1 Allocating locking
authorisations –
normal user keys
6.2 Allocating locking
authorisations –
privileged user
keys
NOTE
Malfunction due to outdated Dialock firmware.
To ensure that the current Dialock firmware is running on the terminal, the
device has to be flashed (programmed) using the mobile programming unit
(MDU) during start-up. In case of questions concerning the firmware version
or the procedure please contact Häfele.
The work operations must be carried out within a short time window.
The following therefore applies:
• Study every work operation and have the keys that are needed at the ready
before commencing with initial start-up.
• Perform the work operations quickly and without interruptions.
For safety reasons, the initial start-up can only take place within 5 seconds after
the battery was inserted.
If this time window is missed, the initial start-up can be started again by removing
the battery and inserting it again.
For step-by-step instructions "Start-up" see illustrations
starting on page 52.
If errors have occurred:
• Repeat process.
NOTE
Warning of abuse!
Unauthorised persons can gain access to lockers using the programming,
erasing and privileged keys.
> Only personnel who are authorised by the operator may allocate
locking authorisations! Take care when allocating locking
authorisations to avoid overlapping or mistakes.
> Keep programming, erasing and privileged keys in a safe place
and protect from abuse.
The normal user keys have the locking authorisation for a locker with a fixed
allocation.
For step-by-step instructions "Allocating locking
authorisations – normal user keys" see illustrations starting
on page 53.
The privileged user keys have the same rights as the normal user keys, but can also
be used by privileged persons to configure the relevant locker lock in combination
with the MDU.
For step-by-step instructions "Allocating locking
authorisations – privileged user keys" see illustrations
starting on page 54.
17