Wait For Dial Tone; Call Routing; Call Attempts; Communication Fault - Bosch FPT-DACT Operations & Installation Manual

Fire communicator
Table of Contents

Advertisement

FPT-DACT | Operation & Installation Guide | 4.0 System Operation
The yellow telephone line LED indicates there is active
communication and shows line fault conditions. The
LED(s) flashes once every second during active
communication. The LED(s) lights steadily for a line
fault condition.
4. 1 .3

Wait for Dial Tone

When enabled, the Wait for Dial Tone feature verifies a
dial tone is present before dialing. When there is no dial
tone present after 7 sec, the FPT-DACT hangs up and
tries again after a 30-sec wait. When no dial tone is
detected on the second try, the FPT-DACT dials again.
When this feature is not enabled, the FPT-DACT waits
7 sec after disconnecting and then re-dials whether or
not a dial tone is present.
4. 1 .4

Call Routing

Each type of event (non-supervisory alarms, supervisory
alarms, alarm restorals, supervisory restorals, test and
trouble, and trouble restorals) can be programmed with
a different call routing. For example, the alarm messages
can be set for Phone 2 backup while supervisory
restorals are sent to Phone 2 only.
Phone 2 Backup is the default and
recommended setting for all event types.
Changing this setting can cause messages
to transmit to the central station.
Each event is routed through the telephone to the
central station one of four ways:
1. PHONE 1 Only: Only uses Phone Number 1.
2. PHONE 2 Only: Only uses Phone Number 2.
3. PHON 1 AND 2: Uses both Phone Number 1 and
Phone Number 2.
4. PHN 2 BACKUP: Primarily uses Phone Number 1
with Phone Number 2 as a backup if
communication cannot be established with Phone
Number 1. PHN 2 BACKUP is the default setting
for the FPT-DACT.
See Appendix E on page 55 for more information about
report steering.
Use the default setting of Phone 1 with
Phone 2 as a backup. If this setting changes,
the telephone lines used also change and
the messages might not transmit to the
central station. Table 4 on page 7 does not
apply to the PHONE 1 ONLY and PHONE 2
ONLY route settings.
4. 1 .5

Call Attempts

When an event must be communicated to the central
station, the FPT-DACT makes up to ten attempts to
communicate with the central station until the call is
answered.
1/05 | F01U002505B
Table 5 on page 19 shows the procedure the FPT-DACT
follows in attempting to communicate with the central
station when it is programmed to use Phone 2 Backup
(default) or Phones 1 and 2.
4. 1 .6

Communication Fault

When a report must be transmitted to the central station,
the FPT-DACT makes up to ten attempts to
communicate (see Table 5). If after ten attempts the FPT-
DACT does not connect successfully, a communication
failure occurs and a Comm Fault Report is generated.
Then, the FPT-DACT makes up to ten attempts to
communicate the Comm Fault to the central station. If
the FPT-DACT does not succeed, the original report
and the Comm Fault Report clear from the FPT-
DACT's buffer.
The total time from the first sequence of attempts to a
communications failure is approximately 15 min. This
varies depending on how [Ack Wait time] is
programmed. A Comm Fault Restoral Report transmits
when communication restores after a communications
failure.
4. 1 .7

Programming Fault

Programming faults indicate if specific telephone
programming items are not completed.
A programming fault generates when:
Both account numbers are not changed from their
default values of 0000.
No telephone number is programmed.
A report is routed to Phone Number 1 and either
Account Number 1 is 0000 or Phone Number 1 is
invalid.
A report is routed to Phone Number 2 and either
Account Number 2 is 0000 or Phone Number 2 is
invalid.
A report is routed to Phone Numbers 1 and 2 or to
Phone 1 with Phone 2 as backup. At least one of the
account numbers is 0000 or one of the telephone
numbers is invalid.
4. 1 .8

Lost Data and Limited Reports

A Data Lost Report generates when an event cannot
transmit to the central station. This occurs when the:
Reporting buffer contains the maximum of 32 events
and another event occurs. The lowest priority event
in the report buffer is deleted and replaced by Data
Lost unless the report is already a Data Lost Report.
If the new event has a higher priority than an event
already in the report buffer, the lower priority event
is discarded and replaced with the higher priority
event. When the buffer is full, the lowest priority
event is discarded when a new event occurs. The
Data Lost Report is the last event sent, emptying the
EN | 20

Advertisement

Table of Contents
loading

Table of Contents