
P r o g r a m D e s c r i p t i o n s :
5 . 9 C o m m u n i c a t o r – R e p o r t i n g F o r m a t s
19
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.
Additional Notes on Contact ID
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].
Please refer to Appendix A for a list of Contact ID Identifiers.
Contact ID Uses Programmed/Automatic Codes . . [381]: [7]
Contact ID Partial Close Identifier is 4/5 . . . . . . . . . [018]:[4]
SIA
SIA is a specialized format that will communicate information
quickly using Frequency Shift Keying (FSK) rather than
pulses. The SIA format will automatically generate the type of
signal being transmitted, such as Burglary, Fire, Panic etc.
The two digit reporting code is used to identify the zone or
access code number.
NOTE: If the Automatic SIA option is selected, the panel will
automatically generate all zone and access code numbers,
eliminating the need to program these items.
If the
SIA Sends Automatic Reporting Codes
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 and send the
reporting code.
If the
SIA Sends Programmed Reporting Codes
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.
Please refer to Appendix A for a list of SIA identifiers.
SIA Sends Automatic Reporting Codes . . . Section [381]: [3]
Pager Format
The communication format option for either telephone number
can be programmed as
Pager
format. If an event occurs and
the
Communicator Call Direction options
direct the call to a
telephone number with the Pager Format selected, the panel
will attempt to page.
When calling a pager, extra digits will be required in order for
the format to function properly. The following is a list of Hex
digits and the functions they perform:
Hex [B] - simulates the [*] key on a touch tone telephone
Hex [C] - simulates the [#] key on a touch tone telephone
Hex [D] - forces the panel to search for dial tone
Hex [E] - two second pause
Hex [F] - marks the end of the telephone number
The panel will attempt to call the pager once. Once the appro-
priate telephone number is dialed, the panel will send the
account number and Reporting Code followed by the [#] key
(Hex [C]).
The panel has no way of confirming if the pager was called
successfully. A Failure To Communicate trouble will only be
generated if the panel detects a busy tone on all dialing
attempts, or if no dial tone is detected on all dialing attempts.
The pager format will not cause any form of ringback.
NOTE:Do not use the digit C in a reporting code when using
Pager Format. In most cases, the digit C will be interpreted as
a [#] which will terminate the page before it has finished.
NOTE:If the panel detects a busy signal, it will attempt to page
again. It will make the maximum number of attempts pro-
grammed in section [160].
NOTE:Force dialing should be disabled when using Pager format.
NOTE:When using Pager format, you must program two hex
digit E’s at the end of the telephone number
Private Line Format
The
Private Line
format allows the communication of events
directly to a user over a telephone line. When an event occurs
that the panel is programmed to communicate, the panel
seizes the line and dials the programmed telephone num-
ber(s). The panel then emits a double beep on the line every 3
seconds. This indicates to the user receiving the call that the
control panel is calling.
The user must acknowledge the call by pressing 1, 2, 4, 5, 7,
8, 0, * or # from any touchtone telephone. The panel will wait
for this acknowledgment for the duration of
Post Dial Wait for
Handshake
timer.
The panel will then indicate which zone is in alarm by sound-
ing a corresponding number of beeps (e.g three beeps for
Zone 3). The user must then press a key (1, 2, 4, 5, 7, 8, 0, * or
#) to acknowledge the alarm. If the panel has another alarm to
communicate, it will sound a corresponding number of beeps
for the new zone alarm. The user must then press a key to
acknowledge the signal. When there are no further alarms, the
panel will hang up.
NOTE: The keys 3, 6 and 9 are not valid handshakes.
NOTE: Events not received by the central station due to an
FTC will not be transmitted via the Private Line format.
Post Dial Wait for Handshake Timer . . . . . . . . . Section [161]
Scantronics and Sur-Gard 4-8-1 Formats
These are DTMF formats that send reporting codes as:
•
One 4-digit account code
•
Eight 1-digit reporting channels (event code)
•
One 1-digit status channel
The software automatically generates a code for the event
based on the programming of the call direction groups.
Channels
1
2
3
4
5
6
7
8
aaaa
x
x
x
x
x
x
x
x
i
Account
Event
Status
Code
Code
Code
When you program the reporting codes for zones and events
(programming sections [320]-[353]), program them in the for-
mat XY, where:
X= channels 1-8
Y= event code (0-9).
NOTE: If your central station uses a Scantronics 5100 receiver,
only program numbers from 1 to 6 for the event code.
Example
: If you program the zone 3 alarm reporting code as
[31], the panel will send event code 1 in channel 3. The panel
Summary of Contents for Power608
Page 4: ...ii PC5008 Wiring Diagram...
Page 50: ...46 NOTES...