Installation and programming manual
Options and programming methods
61
•
Blinker
: generates an intermittent signal (0.5 sec ON and 0.5 sec OFF) when the
output activates - can be employed in direct control of a visual signaling device (e.g.
flasher).
•
ON afterRestoral
: the output does not restore-to-standby (reset) when the
trigger-event clears. This option is useful in situations that require a trigger event for
output activation and a reset event for its deactivation.
This option applies to “Bistable” outputs only. If it is enabled for a bistable output
with reset-event configuration, it will deactivate the output instead of activating it
(refer to
paragraph 6-11 Events
).
This option is useful in situations that require the output to reveal event “memory”
(event signaling which continues even after the event clears). In this case, the
output is deactivated by a different event which restores it directly to standby
(resets the output).
For example:
•• O.C. Output 1 is configured as "ON afterRestoral"
•• the activation of “Mains failure” event is programmed to trigger O.C. Output 1
•• the restoral (reset) of "Valid code"event is programmed to trigger O.C. Output 1
In the event of Mains failure, O.C. Output 1 will activate but will not restore to
standby (reset) when the Mains failure condition clears. It will restore to standby
(reset) only when “CODE 1” is entered a keypad and generates a “Valid code” for the
“CODE 1” event.
•
Switching
- each time you execute an “activate output” command, the output will
switch status. Therefore, if it is deactivated it will activate and vice versa.
However, each time you execute a “deactivate output” command, the output will
always deactivate.
If you wish to manage this feature through a shortcut, you must use the “Activate
outputs” shortcut.
Monostable time
This parameter applies to “Monostable” outputs only. This interval can be expressed in
seconds or minutes (see “info” box).
When a “Monostable” output receives an activation signal, it will remain active (On) for
the programmed time, regardless of the status of the trigger-event. In some cases,
“Monostable” outputs can be forced to standby before the programmed monostable
time runs out.
Use keys
and
and the number keys to set the times.
Via PC
Programming zones via the SmartLeague application is accomplished by the selection
and programming of the terminal configured as output, described in
paragraph 6-6
Terminals
.
6-9
Walk test
This section provides a quick and easy way of testing all the configured inputs.
After initializing the Walk test, all you need to do is walk through the protected
partitions and then check the detection capacity of the inputs via the system
keypad or SmartLeague software application.
Via Keypad
Type-in the code
(Installer)
, PROGRAMMING Walk test
.
On access this section, the full list of configured zones appears on the screen.
As these input zones are violated by the operator carrying out the walk test,
they will be cleared from the list and the keypad will emit a long beep.
You can consider the outcome of test positive when there are no zones left on
the list.
Via PC
Select “Check control panel - Monitoring - Walk test” option from the menu bar.
The display will show a list of all the configured zones and the start test button.
Once you press the test button, the violated zones will be marked by a red dot.
If this value is
expressed in
minutes, there is
an error margin of
1 minute (for example, if
you set 5 minutes, the
period can vary between 4
and 5 minutes).
PROGRAMMING
Zones
Outputs
Walk test
Walk test
Panel T01
Panel T02
Panel T03
