99
» Sensor communication failure in zone 12: event
147
(factory standard) and
with user/zone being
012
.
» Sensor reset in zone 64: event
130
(factory standard) and with user/zone being
064
.
» Sensor tamper in zone 05: event
383
(factory standard) and with user/zone
being
005
.
» Keyboard tamper registered at address 01: event
145
(factory standard)
and with user/zone being
201
.
» Siren tamper registered at address 09: event
145
(factory standard) and
with user/zone being
309
.
» Keyboard communication failure registered at address 01: event
381
(factory standard) and with user/zone being
201
.
As can be seen in the following commands, according to the registered Contact-ID
code, the event may be blocked if congured as 000 (will not be sent to the IP
Receiver). The registration of the Contact-ID code can be done according to the
available options of Contact-ID code, or even, when registering FFF will cause the
option that is registered with this value to send to the monitoring company the
default Contact-ID code.
The following tables show the events and the respective standard Contact-ID
codes:
Events of the opening type
Zone triggering
Zone no. Event Contact-ID Code
01 to 64 Zone triggering 130
The commands relating to the Contact-ID, more specically the Programmable
Contact-ID, the communication protocol must be set to Programmable Contact-
ID, otherwise events will be sent with the standard Contact-ID. Refer to the topic
Reporting
mode, in the part explaining the Phone Protocol 1/2.
Use the table above to perform the
Contact-ID
event change command for zone
triggering described below:
901
+
Enter Enter
+ +
Zone N°
01 to 64