GIGA-TMS TR4020, Руководство пользователя

Страница: 28 / 161

C.6. Using the TR40xx as an Access Control Terminal
We receive a lot of questions regarding whether or not the TR40xx can be used as an Access Control
Terminal. Some Users take the fact that the TR40xx has an electric lock control relay (see Bell and Lock
control relays ) as an indication of the Terminal’s ability to perform an Access Control Function. This Section
will attempt to clarify this point.
The TR40xx is not an Access Control Terminal. It doesn’t have an internal User database and, by
default, accepts and activates the door lock on any ID-card read. The Lock relay was originally built into the
Terminal for a different reason: some of our customers wanted to use the Time Recorder in conjunction with
a turnstiles. This is normally done to enforce the “clocking” i.e. make sure that the person won’t be able to
access or exit the facility without registering first.
Later, we have extended the TR40xx firmware to provide a limited Access Control functionality. This
was done by implementing a new Prefix to match Setting. When the prefix is set, the TR40xx will only accept
(add the record and activate the lock) the User ID-cards with an ID-code that starts from a matching
sequence of digits.
Basically, this allows you to choose a single prefix combination for your facility (organization) and issue
ID-cards that have a common part (prefix), and a User ID. For example, you might choose the prefix to be
“1234” and issue sequential User IDs like “001”, “002”, etc. Then you will have ID-cards with codes like
“1234001”, “1234002”, etc. If you pre-program the TR40xx’s
Prefix to match to “1234”, then the Terminal will
only accept the cards with the ID-codes starting from ”1234”. All other cards will be rejected- and that means
that access won’t be granted too.
Further, you can hide the prefix from appearing in the Time and Attendance database by Using the
From character and Number of characters Settings. This way you can keep the prefix confidential.
This Access Control implementation is very simple, of course, and is only fit for low-security
applications. Plus, you cannot control User access rights individually. On the positive side, you don’t have to
maintain the User database- all you need to do is issue the Cards with the correct prefix.