181 Kaba Ilco Lodging Access Control System
Chapter 7: Auditing
In the event of suspected illicit entry to a room or use of the FDU, the audit trails can be
read by following the instructions in this chapter. In addition, the lock audit is useful for
verifying the lock firmware version, addresses and battery voltage (Generation E-760,
770, and 710-II locks only), if the lock appears to be malfunctioning.
According to the privileges of the user, the audit options available will vary as shown in
the following table:
User Type of audits that can be exported.
General Manager Lock and FDU audits
Master Lock audits
Programming Lock audits
All others None
Table 7: Users with audit transfer abilities
7.1 Auditing a Lock
The lock audit is stored in non-volatile memory, and cannot be erased by disconnecting
the batteries, or by any programming function. Locks store the most recent 350 entries in
FIFO (First-In-First-Out) format, with the following information:
x Lock firmware version
x Type of lock
x Lock adresses
x Data for each recorded entry
o Keycard level
o Issuer’s Authorization number
o ID (serial) number
o Date and time of entry
Generation E-760 & 770 locks store the most recent 200 audit entries.
Example of a 760K lock audit:
The first screen displayed by the FDU when showing a lock audit contains information
about the lock type, PCB, firmware version and addresses.
To Next Page
Loading...
