The actual trouble beeps can be stopped by system/partition arming or by any entering within
trouble displaying menu (by pressing the [*][4] Keys). So, as soon as the users had
acknowledged the troubles by means of [*][4] command, the keypad trouble buzzer warnings
will stop, as there are no troubles in the system, but the corresponding trouble indicator will
still remain ON until the respective trouble condition is solved. The SYSTEM LED will still
remain to blink until all troubles will be solved.
If option of “next trouble beep stopping” was enabled by programming, it can be released just
by entering command [*][4] as follows:
§ once user entered [*][4] command, if the keypad buzzer will sound 6 confirmation
beeps, that means in the future the keypads will no longer emit intermittent beeps
upon any new trouble occurring (the intermittent beeps will not be reactivated even a
new trouble will occur);
§ once user entered [*][4] command, if the keypad buzzer will sound 3 confirmation
beeps, that means in the future the keypads will emit again intermittent beeps upon
any new trouble occurring (the intermittent beeps will be reactivated whenever a new
trouble occurs).
So, if option of “next trouble beep stopping” was enabled by programming, then any entering
within trouble displaying menu will toggle the next trouble beep emitting from activated to
deactivated and vice-versa.
If option of “next trouble beep stopping” wasn’t enabled by programming, the keypad buzzer
will sound no beeps once user enter [*][4] command, but it will still stop the actual trouble
buzzer warnings until a new trouble occurring.
Remarks:
1. Burnt fuse on AUX trouble, though it does record as LOG event (and optionally, if the digital communicator is
enabled by programming and the appropriate reporting code is programmed too, it is reported to CS), cannot
be displayed on the keypads because the keypads are powered exactly from this power supply (this trouble is
stopping the keypad powering until the fuse is replaced).
2. If any trouble condition occurs, it needs to be solved before arming to assure a proper function for system.
3. If there are alarms in the memory, the SYSTEM LED will turn blinking too; if the SYSTEM LED is blinking just
because of at least one alarm occurred, you can see the alarm memory occurred in the system since last
arming then by means of [*][5] command.
Press [#] key to exit the system trouble displaying menu.
ALARM MEMORY DISPLAYING
[*][5]
All alarms occurred in the system/partition since last arming are memorized and can be
visualized on zone LEDs.
To view the alarmed zones or the special alarms triggered from the keypad or from
phone line trouble, enter [*][5] command, while system/partition is disarmed.
Soon after starting this command by entering [*] key, all keypad LEDs will turn OFF. After
entering the key [5], the SYSTEM LED will blink and the zone LEDs that triggered
the alarm will turn ON.
To view the special alarms triggered from the keypad or from phone line trouble,
press [*].
The green LED READY will also blink, indicating the second set of alarms on the 1, 2, 3 and 4
LEDs.
Within the 2
-nd
mode of alarm visualization
- LED 1 indicates an alarm triggered from the keypad locked after to many wrong code
entering
- LED 2 indicates a keypad alarm (panic, fire, medical emergency)
- LED 3 indicates an alarm triggered from the phone line trouble and
To Next Page
Loading...
