Repeaters - Pima Sentinel Installation And Configuration Manual

3.11. Repeaters

Repeaters and Formats can only be programmed by PIMA. Only the
Channels can be modified by the users
A repeater can receive events from any alarm system, and relay them to the CMS in any medium -
radio, network or telephone. A repeater can be part of a chain, but have a separate log.
Up to 16 repeaters can be set in Sentry, each can be entirely separated logical repeater.
To set the repeaters' channels, do the following:
1. Double-click on Repeaters.
2. Double-click on Repeater X. A repeater can be defined with up to 4 channels: a channel can
be any medium defined in Sentry, and have up to 32 formats, and different Keepalive and
supervision accounts.
3. Double-click on Channel X. The properties of the Channels window are:
Property Details
Channel The physical channel
Station Phone Set the destination phone number (that is, Sentry's Repeater IN), when the
Number SENTINEL is in Line mode and the repeater is set as Out
Test Time Set the interval in min. for the channel's supervision. Range: 0-9999
0: disable supervision


Account Set the account no. for PimaGuard life signals and fault reports.
If repeater OUT is in use and Sentry's fault account is routed to this
repeater's channel, the account no. will be replaced with the channel's
account no. See the next section for limitations.
In Repeater IN there is no Restore event after sending a life
signal, when the Test time expires without receiving any event
When the repeater is in OUT mode, the channels backup one another
•
by their order: if Channel 1 becomes faulty, the event buffer is
routed to Channel 2, and so on, in a loop. When Channel 1 is
restored, the events are routed back to it.
When the repeater is in IN mode, events are accepted from all the
•
channels without any priority.
In Repeater OUT: life signal is sent (with the account no.) if no other
event was sent during Test Time
In Repeater IN: if no event is received during Test Time, a fault event is
sent (see the Fault Codes appendix, on page 41)
Make sure the account no. is unique and not in
use by any of the control panels
PimaGuard
33