Page 16
•
Card 4 gets lost
– Delete it
using the card 2
, which is available, and using the procedure
from
chapter 6.7.3
– Read
+ (inserting) programming card
, then
5x + (inserting)
programming card
again, then
card 2
, and finally
+ (inserting) programming card
again.
Register the change in your table
.
Pic.5 g): Deleting card 4 using the card 2, table after deleting card 4
•
It is necessary to
add another card
(card 6). We proceed with the procedure from
chapter 6.7.1
again.
1
– Read
+ (inserting) programming card
, read
cards 1-5
, after 15
s the programming mode is exited.
Register the change in your table
.
Pic. 5 h): Table after inserting card 6
A new card is always inserted at the position after the last inserted card. In case of deleting
all cards using the procedure described in
chapter 6.7.4
, it is necessary to create a new filing
table.
6.8 ID expiration function
This function is implemented since the FW version 5.0.
It is possible to set an
Expiration date
for every
ID
stored in the module. When the date
occurs, the ID becomes invalid (expired). The expiration evaluation is performed on every
date change in the module’s RTC and when the access rights are downloaded.
6.9 ID with Alarm flag function
This function is implemented since the FW version 5.0.
It is possible so set an
Alarm
– ID flag
for every
ID
stored in the module. When the ID is read,
relevant alarm is raised (and the alarm output is switched for preset time).
position
card
1
card 1
2
card 2 (available)
3
card 3
4
card 4 (lost)
5
card 5
position
card
1
card 1
2
card 2
3
card 3
4
card 4
5
card 5
position
card
1
card 1
2
card 2
3
card 3
4
card 4
5
card 5
6
card 6
