DSC pc1565 - Communicator Formats and Downloading; 5.9 Reporting Formats

Program De sc rip tio ns : 5.9 Communicator – Reporting Formats

The )XQFWLRQ.H\V5HTXLUH &RGH option must be selected
(section [015], option 4 OFF) in order for wireless keys to be
identified for arming. Disarming will always be logged by
access code, if one is programmed for the Key, regardless of
this option.
Wireless Maintenance
The panel will transmit a :LUHOHVV'HYLFH/RZ%DWWHU\$ODUP
reporting code if a low battery condition is indicated by a
detector. Transmission and logging to the event buffer of the
trouble will be delayed by the number of days programmed
for =RQH /RZ %DWWHU\ 7UDQVPLVVLRQ 'HOD\. The :LUHOHVV
'HYLFH/RZ%DWWHU\5HVWRUDO reporting code will be transmit-
ted when the problem is corrected. The specific zone that
caused the trouble will be recorded in the event buffer.
127( 7KHUHVWRUDOZLOOQRWEHWUDQVPLWWHGXQWLODOOGHWHFWRUV
LQGLFDWHJRRGEDWWHU\FRQGLWLRQV
Wireless Maintenance Reporting Codes . . . . . Section [353]
Zone Low Battery Transmission Delay . . . . . . . Section [370]
AC Failure Trouble Alarm Code
To prevent the panel from transmitting an $&)DLOXUH7URXEOH
$ODUP reporting code during short power outages, the panel
will not send the signal unless AC power is lost for the amount
of minutes programmed for the $&)DLOXUH&RPPXQLFDWLRQ
'HOD\. The $& )DLOXUH 7URXEOH 5HVWRUDl reporting code fol-
lows the AC failure communication delay as well.
127(,I$&)DLOXUH&RPPXQLFDWLRQV'HOD\LVSURJUDPPHGDV
³´WKHQWKH$&IDLOXUHWUDQVPLVVLRQZLOOEHLPPHGLDWH
AC Failure Communication Delay . . . . . . . . . . Section [370]
5.9 Communicator – Reporting Formats
Each communication telephone number can be programmed
to report using any one of ten formats available. Two 20 BPS
pulse formats and two 10 BPS formats are supported, in addi-
tion to Contact ID, SIA, Pager, Private Line, Scantronics 4-8-1
and Sur-Gard 4-8-1 formats.
The &RPPXQLFDWRU &DOO 'LUHFWLRQ options can be used to
disable the reporting of events such as Openings and Clos-
ings.
127('RQRWSURJUDPWKHQGWHOHSKRQHQXPEHUWRXVH&RQ
WDFW ,' RU 6,$ UHSRUWLQJ FRGH IRUPDWV VHFWLRQ >@ LI $XWR
PDWLFUHSRUWLQJFRGHVDUHVHOHFWHGIRUHLWKHU&RQWDFW,'RU6,$
VHFWLRQ>@
Communicator Format Options . . . . . . . . . . . . Section [360]
Communicator Call Directions . . . . . . . Section [361] to [368]
The following is a description of each reporting format:
Pulse Formats
Depending on which pulse format is selected, the panel will
communicate using the following specifications:
• 3/1, 3/2, 4/1 or 4/2
• 1400 or 2300 Hz handshake
• 10 or 20 bits per second
• non-extended
With the +]+DQGVKDNH option enabled, the communica-
tor will respond to 1600Hz handshakes when using the report-
ing Communication Formats 01 and 02 only. When the
Standard Handshake option is enabled, the communicator will
respond to the handshake specified by the BPS format
(1400Hz or 2300Hz).
$GGLWLRQDO1RWHVRQ3XOVH)RUPDWV
1. The digit ‘0’ will send no pulses and is used as a filler digit.
2. When programming account numbers, enter four digits.
When programming a three digit account number, the
fourth digit must be programmed as ‘0’.
• 3 digit account number [123] - program [1230]
3. If an account number has a ‘0’ in it, substitute a HEX digit
‘A’ for the ‘0’. For example:
• 3 digit account number [502] - program [5A20]
• 4 digit account number [4079] - program [4A79]
4. Reporting codes are two digits. When programming sin-
gle-digit Reporting Codes, the second digit must be pro-
grammed as a ‘0’. If a ‘0’ is to be transmitted, substitute
HEX digit ‘A’. For example:
• 1 digit Reporting Code [3] - program [30]
• 2 digit Reporting Code [30] - program [3A]
5. To prevent the panel from reporting an event, the reporting
code should be programmed as [00] or [FF].
1600Hz/Standard Handshake . . . . . . . . . . .Section [702]: [4]
Contact ID
Contact ID is a specialized format that will communicate infor-
mation using tones rather than pulses. This format allows more
information to be sent faster than other formats. For example,
in addition to reporting an alarm in zone one, the Contact ID
format will also report the type of alarm, such as an Entry/Exit
alarm.
If the &RQWDFW ,' XVHV 3URJUDPPHG 5HSRUWLQJ &RGHV
option is enabled, a two digit number from Appendix A must
be entered in programming sections [320] to [353] for each
event to be transmitted. The two digit number determines the
type of alarm. The panel will automatically generate all other
information, including the zone number.
If the &RQWDFW,'XVHV$XWRPDWLF5HSRUWLQJ&RGHV option is
enabled, the panel will operate as follows:
1. If an event’s reporting code is programmed as [00], the
panel will not attempt to call the central station.
2. If the reporting code for an event is programmed as any-
thing from [01] to [FF], the panel will automatically gener-
ate the zone or access code number. See Appendix A for a
list of the codes which will be transmitted.
127(,IWKH$XWRPDWLF&RQWDFW,'RSWLRQLVVHOHFWHGWKHSDQHO
ZLOODXWRPDWLFDOO\JHQHUDWHDOO]RQHDQGDFFHVVFRGHQXPEHUV
HOLPLQDWLQJWKHQHHGWRSURJUDPWKHVHLWHPV
If the &RQWDFW ,' XVHV 3URJUDPPHG 5HSRUWLQJ &RGHV
option is enabled, the panel will operate as follows:
1. If an event’s reporting code is programmed as [00] or [FF],
the panel will not attempt to call central station.
2. If the reporting code for an event is programmed as any-
thing from [01] to [FE], the panel will send the programmed
reporting code.
$GGLWLRQDO1RWHVRQ&RQWDFW,'
1. Account numbers must be four digits.
2. All reporting codes must be two digits.
3. Substitute the HEX digit ‘A’ for the ‘0’.
4. To prevent the panel from reporting an event, the reporting
code should be programmed as [00].
5. To change the Contact ID Partial Close Identifier from (4) to
(5), change the programming in section [018]: [4].