35
If even after the 8 attempts the 2
-nd
central station doesn’t answer (the control panel failed to report the events to CS2), then the control panel will record a “CS2 communication failed” event into
the 800-event LOG and a specific reporting code into the CS2 85-event internal buffer, too. Upon a new reportable event occurring, if the communication with CS2 is established, the entire list
from CS internal buffer, the old reporting codes, the new reporting codes and the failed communication reporting code, which is already in the list, will be reported together to the CS2. In the
same time, if an event of “CS2 communication failed” occurred in the system, the specific reporting code will be recorded into the CS1 85-event internal buffer and will be transmitted to CS1, too.
This trouble condition will turn the SYSTEM LED blinking and the zone 3 LED ON, within system trouble displaying menu - [*][4] command. If this trouble condition occurred for first time, then the
keypad trouble buzzer warnings will be activated, too, and the keypad will emit intermittent beeps, at every 8 seconds, until the users will acknowledge the trouble by means of [*][4] command,
or until system/partition arming. 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, (and the zone 3 LED will still remain ON within system trouble displaying menu) until a successful transmitting to both CS1 and CS2.
So, if both phone numbers are programmed in [074] and [075] sections and none of them answers, then the calling sequence is the following:
- [25 seconds: CS1 phone number dialing and waiting for handshake][pause of 32 seconds][25 seconds: CS1 phone number dialing and waiting for handshake][pause of 32
seconds]... and so on up to 8 times for 1
-st
CS phone number and then
- [25 seconds: CS2 phone number dialing and waiting for handshake][pause of 32 seconds][25 seconds: CS2 phone number dialing and waiting for handshake][pause of 32
seconds]... and so on up to 8 times for 2
-nd
CS phone number.
4. Within “zone restore” denomination there is an event which is referring to the recording moment into the 800-event LOG and to the reporting moment to CS, as follows:
For audible zones which triggered the alarm and then their loops ”closed back”, the “zone restore event” can be set to occur either
upon zone closure or upon bell cut-off;
For audible zones which triggered the alarm and their loops remain “open” even after the bell cut-off, the “zone restore event” will occur upon zone closure, regardless of “zone
restore” option programming.
For all silent zones the “zone restore event” will occur only upon zone closure, regardless of “zone restore” option programming.
“Report only first zone alarm” is a function of the zone restores option, too. If the “zone restore event” is set to occur upon bell cut-off and this option is set as enabled, then, for any
audible zone the control panel will consider only first zone violation, which triggers the siren timer (once the zone made the alarm sound and then its loop “closes” and “opens” for several
times, it will no longer record alarms into the 800-event LOG and/or into the first 9 alarm memory while siren is sounding).
4.1 Considering that during one siren activation period only first violation of each “audible zone” will trigger the siren timer, for any zone which allows auto shutdown, during the same
arming period (or during the same disarming period for 24h zones), there are 2 situations regarding the zone restore events and auto shutdown:
if “zone restore event” is set to occur upon zone closure, then the maximum alarm number which can be recorded by such a zone, will be equal with “swinger shutdown
counter”, even though these alarms occur during one “siren activation period” or that zone itself will trigger the siren timer for more times, when it gets violated.
If “zone restore event” is set to occur upon bell cut-off, then the maximum number of “siren timer triggering” which can be performed by such a zone will be equal with
“swinger shutdown counter”. Please note that if “report only first zone alarm” is disabled, too, such a zone may record more alarms than “swinger shutdown counter”; this is
possible because once the zone made the alarm sound and then its loop “closes” and “opens” for several times it will keep recording alarms into the 800-event LOG and/or into the first 9
alarm memory while siren is sounding, but zone restore event will occur only upon bell cut-off.
This is happening because the panel is counting the zone restore events for any zone which allows auto shutdown and the zone will bypass from swinger only after the
number of zone restorations gets to the “swinger shutdown counter”.
Section [033] – Split Reporting Options for CS1&CS2
Where CS1 is the first “central monitoring station” and CS2 is the second “central monitoring station” to which the control panel transmits the events occurred in the system.
When the panel is being within “main programming menu”, in order to establish the events to be transmitted to CS1&CS2 in case of split reporting, select section [033].
The 1 to 8 options will be displayed according to the table below:
Key
pressed to
toggle
option
KP-126Pz / KP-164Pz (LED
keypads)
Description
KP16LCD / KP16LCDL (LCD keypads)
Zone
LED
ON OFF 1
st
line message
2
nd
line message
Enabled Disabled
[1] 1
* enabled disabled
*
Reports alarms, restorations, ambush and panics to CS1
AlResAmbPanCS1 Enable k1 Disable k1
[2] 2
* enabled disabled
*
Reports arming, disarming and bypassing to CS1
ArmDisByssCS1 Enable k2 Disable k2
To Next Page
Loading...