50
12.3.
Delays
For each event it is possible to define the delay with which the lock or OC will be controlled.
Additionally, a distinction is made between local (OC) and remote (local
–
connected to the
keyboard generating the event, remote
–
output of other keyboards). Delay times are also
differentiated according to the type of event. One delay time can be defined for the door open
button (aux) and the other time is defined for other events in the system. Differentiation between
“
local
”
and remote locks enables to set different opening and delay times
–
when, for example,
after using RFID, 2 door pairs have to be opened which are separated from each other.
Delay is defined by the cassette that calls the event, the opening time of each lock is determined
by the setting of satellite cassette.
12.4.
Beeper configuration
Location of beeper generation is defined analogously to the definition of open locks or OC.
By definition, a beeper is supposed to signal the occurrence of an event, so the delay times and
duration of a beeper is correlated with these events. If the opening of lock is assigned to an event,
the beeper delay and time will be taken from the parameters of lock. If the locks are not opened,
the OC settings are checked. If the OC is not activated either, then the parameters defined for
beeper are valid (time and delay). Location of beeper generation is always taken from the beeper
parameter and is independent of the open locks and OC.
12.4.1.
Beeper in delay time
By default, if the key is activated with delay, a waiting signal is generated in the keyboard. It can
be deactivated by increasing the delay time by 1000. For example, if you set the delay to 15
seconds, the waiting signal is muted by entering 1015. The delay will still be 15 seconds.
In this way, the beeper will be activated with the lock without informing about upcoming control
of the lock.
This way you can influence the beeper when opening the local key (parameter 370) and separately
the local key from the AUX button (parameter 372).
12.5.
Optimized event response for common keyboard
Due to the specific operation of bus data in KDC3900 series, it may be necessary to optimize the
response to lock button events. If such an event is called, all PBXes that have the appropriate
parameters programmed will react. In special cases, when multiple panels (e.g. 40 devices) are
connected to the bus, this may cause a blockage of bus data.
In order to limit the number of messages on the bus, it is recommended to enter AUX button in
the common satellite to only one control panel, and in the other control panels the value of
parameter x364 (assigning the AUX button to control the lock
–
local for satellite) from 128 to 0.
