Page 17
Individual signals function in
WIEGAND output
operating mode is described in
table 17
.
W
ieg
a
nd
Input 1
Beeper control (0 V active)
Input 2
Control of icon 4 at the display (see
tab. 4
, 0 V active)
Output 1 (relay)
Tamper signaling; it follows the alarm state of tamper sensors
(tamper signal = relay switched on)
3)
Table 17: Signal function in WIEGAND operating mode
Since the
FW version 5.09
the reading synchronization of a
couple of TECHFASS readers
is
implemented, enabling to
cancel the mutual disturbance
of the modules. The reader module
offers the
Wiegand data interface
synchronization
in
MASTER
mode.
6.6.2 Wiegand input (external reader)
The terminal can be configured into a mode of controlling the door from both sides (
entry
reader mode
) or into a mode, where the reading of IDs is provided by an external reader only
(
external reader mode
).
In the
entry reader mode
an identification at an external reader connected via the
WIEGAND
interface
acquires a
reason code 255
, the terminal own reader operates standardly, the
reason codes are acquired according to a reason icon selected at the display.
Since the
FW version 5.09
the reading synchronization of a
couple of TECHFASS readers
is
implemented, enabling to
cancel the mutual disturbance
of the modules. The reader module
offers the
Wiegand data interface
synchronization
in
SLAVE
mode.
In the
external reader mode
the terminal own reader is disabled. The ID media reading is
provided by an external reader, which is connected to the terminal with the
WIEGAND
interface
. The code of the reason selected at the terminal display is assigned directly to the
identification event raised at the external reader.
The acoustic signalization of the events raised at the external reader is announced directly
at the external device itself
– the signal for the beeper control is present at the cable 1 (see
tab. 6
).
The
WIEGAND input
and
WIEGAND output
operating modes are mutually exclusive.
6.7 Module advanced function
If the advanced function is selected, the door lock release is caused only when an ID medium
is read at the entry reader. Reading an ID medium at the terminal embedded reader saves
an event in the memory, but does not release the door lock.
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.
