Bosch 7412 G User Manual

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 11
Bosch Security Systems | 1/04 | 47775E
2.0 9000MAIN
Use this programming module to define the
operating characteristics that affect panel-wide
functions. There are nine programming categories in
this module: Phone, Phone Parameters, Routing,
Enhanced Communications, Area Parameters,
Command Center, User Interface, Function List, and
Relay Parameters.
2.1 Phone
The control panel can dial up to four different
telephone numbers when sending event reports. All
telephone numbers use the same receiver format.
Event report routing and communication protocols
are discussed in Section 2.3 Routing.
Phone 1
Default:Blank
Selection:Up to 24 characters (do not enter
[SPACE])
0 to 9 Numbers 0 through 9
C 3-second pause
D 7-second dial-tone detect.
# or * Used for the same purpose as pressing
this key on a telephone keypad when
manually dialing. For example, an
asterisk (*) may be needed to access
your long distance service. Do not use
these characters when pulse dialing.
Blank Control panel dials no phone number.
Programming this item Blank does not
disable phone routing. To disable
reporting to this phone, see Section 2.3
Routing.
This is the telephone number the control panel dials
to contact the central station receiver when sending
event reports. This number is Phone 1 referred to in
the prompts in Section 2.3 Routing.The control panel is pre-programmed with a
7-second dial tone detect period. When a dial tone is
detected or the waiting period ends, the control
panel begins to dial. To extend the dial tone detect
period, place a D before the phone number. To
insert a pause during or after dialing, use C in the
number sequence. For example, if the control panel
hangs up before it hears the Modem IIIa
2 Ack tone
from the D6500/D6600, program extra Cs after the
phone number. The control panel waits on line for
three extra seconds for each C programmed.
Enter up to 24 of the following characters to define
dialing characteristics.
0101
0101
0101Using both phone data entry lines: The first
line of the phone number data entry line
must be filled (twelve characters) before
you press [ENTER] to move on to the
second line. If you enter characters on the
second line, and there are less than twelve
characters on the first line, the second line
clears when you press [ENTER].
Phone 2
Default:Blank
Selection:Up to 24 characters (do not enter
[SPACE])
See explanation of Phone 1. This number is Phone
2, referred to in the prompts in Section 2.3 Routing.
Phone 3
Default:Blank
Selection:Up to 24 characters (do not enter
[SPACE])
See explanation of Phone 1. This number is Phone
3, referred to in the prompts in Section 2.3 Routing.
Phone 4
Default:Blank
Selection:Up to 24 characters (do not enter
[SPACE])
See explanation of Phone 1. This number is Phone
4, referred to in the prompts in Section 2.3 Routing. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 12
Bosch Security Systems | 1/04 | 47775E
2.2 Phone Parameters
The program items in this category describe panel-
wide characteristics for telephone dialing, receiver
format, and supervision.
Modem Format
Default:Yes
Selection:Yes or No
Yes
Radionics’ Modem IIIa2
Communication Format: Reports
identify points as 001 through 247 and
passcode User ID codes as 000 through
249 at the D6500/D6600 Receiver
(unless 
Point/User Flag is
programmed Yes; see the 
Point/User
Flag
 prompt in this section). When
reporting point events, Radionics’
Modem IIIa
2 Communication Format
also sends point text to the
D6500/D6600 as programmed in Point
Assignments.
No
BFSK (2300 Hz or 1400 Hz
acknowledgment tone).
Central Station Receiver Format for
Transmission of Reports: Modem format provides
many reporting advantages over the BFSK format.
See the D6500/D6600 Report Directory for more
information about the effect of reporting formats.
Modem Format must be set to Yes when
sending events over a network to a D6600
receiver (NetCom).
0101
0101
0101If Modem Format is No, be sure to assign
a number to identify Duress Reports in
BFSK Duress Code in this programming
section.
Point/User Flag
Default:Yes
Selection:Yes or No
Yes The control panel sends a flag with
each report telling the D6500/D6600 to
convert point numbers and User ID
numbers to COMEX format. The
conversions are shown in Table 6 and
Table 7. No matter how the
D6500/D6600 is programmed for
output to the computer system, points
and User ID numbers are converted
when this item is Yes. (See the D6600
Communications Receiver/Gateway
Computer Interface Manual, Appendix C,
Numbered Table and Note 1.)
No The control panel does not send the
flag. The D6500/D6600 outputs point
numbers as 001 to 247 (rather than 100
to 732) and User ID numbers as 000 to
249 (rather than 000 to F08), as
indicated in Table 6 and Table 7.
This program item determines how point and User
ID numbers are presented at the D6500/D6600
display, printer, and computer RS-232 output.
When 
Modem Format is Yes, the control panel
sends expanded Radionics’ Modem IIIa2
Communication Format reports to the
D6500/D6600. If your central station data files are
not set up for point and User ID number reporting,
you can use this program item to convert these
numbers to COMEX Reports.
When 
Modem Format is Yes, the control panel
sends expanded Radionics’ Modem IIIa2
Communication Format Reports to the receiver.
Point/User Flag affects Radionics’ Modem IIIa2
Communication Format data as shown in Table 6.
The Bosch Security Systems D6500/D6600 Receiver
adds the leading zero in the User ID number with
Point/User Flag programmed No. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 13
Bosch Security Systems | 1/04 | 47775E
Table 6: Modem IIIa2 Communication Format
Data - User ID Numbers
Point/User Flag
NOPoint/User Flag
YES
000000
001 to 005 001 to 005
006 to 013601 to 608
014 to 021 701 to 708
022 to 029801 to 808
030 to 037 B01 to B08
038 to 045C01 to C08
046 to 053 D01 to D08
054 to 061E01 to E08
062 to 069 F01 to F08
070 to 249000
Table 7: Modem IIIa2 Communication Format
Data – Point Numbers
Point/User Flag
NOPoint/User Flag
YES
001 to 008100 to 800
009 to 024 101 to 116
025 to 040201 to 216
041 to 056 301 to 316
057 to 072401 to 416
073 to 088 501 to 516
089 to 104601 to 616
105 to 120 701 to 716
121 to 136801 to 816
153 to 168 217 to 232
169 to 184317 to 332
185 to 200 417 to 432
201 to 216517 to 532
217 to 232 617 to 632
233 – 247717 to 731
Independent Zone Control Notice: When using
Independent Zone Controls (IZC) to send
Opening/Closing Reports by point, do not duplicate
reporting independent point numbers with User ID
Reports (see Section 3.1 Passcode/Token Worksheet). For
example: If an IZC is connected to Point 8, User ID
8 should not be used.D6000:Opening/Closing User ID numbers are
identified at the receiver as ZONEs (same
identification as independent points).
Table 8: Zones
User ID Number Zone
1B
2C
3D
4E
5F
66
77
88
911
92 2
933
94 4
955
96 0
D6500/D6600 Receiving BFSK Format:
Opening/closing User ID numbers are identified at
the receiver as ZN (same identification as
independent points). The ZN numbers are based on
the tens digit of the User ID number. This only
applies for Users 000 through 099. Users 100
through 249 do not report in BFSK format.
DTMF Dialing
Default:Yes
Selection:Yes or No
Yes Dials the programmed phone
number(s) using DTMF.
No Pulse dialing only.
Use dual-tone multi-frequency (DTMF) to dial the
central station receiver phone number(s) for event
reports, and/or the RPS. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 14
Bosch Security Systems | 1/04 | 47775E
Phone Supv Time
Default:Blank
Selection:Blank or 10 to 240
Blank No phone line supervision.
10 to 240 Enter the number of seconds (in 10
second increments) you wish to
supervise the phone line. After a faulted
phone line restores, it takes the same
amount of time to initiate restoral
responses.
Phone line trouble responses: Command centers
display SERVC PH LINE # to indicate which
phone line failed. The command center initiates a
trouble tone if 
Buzz on Fail is Yes and CC Trouble
Tone
 is Yes.
With dual phone lines (using the D928 Module), the
restored phone line handles all messages regardless
of the phone line’s number.
Phone, Trouble, and Restoral Events report when
they occur. They report also when a Diagnostic
Report is initiated from a command center or by a
Sked.
Alarm On Fail
Default:No
Selection:Yes or No
Yes Generate alarm responses when a
phone line fails.
No Phone failures report as trouble
responses for Area 1 and/or the
account number for Area 1.
0101
0101
0101
Phone Supv Time must be programmed to
use this feature.
Phone Failure Alarm Responses: The
Alarm Bell relay for Area 1 activates. All
Phone Event messages report as Area 1
and/or the account number for Area 1.
Buzz on Fail
Default:No
Selection:Yes or No
Yes Generate panel-wide trouble tones and
display PHONE FAIL # at command
centers when a Phone Fail Event
occurs.
No Does not generate trouble tones at
command centers when a Phone Fail
Event occurs. PHONE FAIL # still
displays.
0101
0101
0101
Phone Supv Time must be programmed to
use this feature.
De-selecting individual command
centers for panel-wide trouble tones:
Panel-wide trouble tones for programming
CC can turn off individual command
centers (based on their CC # 1 through 8)
# Trouble Tone in Command Center
Parameters as No.
Two Phone Lines
Default:No
Selection:Yes or No
Yes The D928 Dual Phone Line Module is
installed. The LEDs on the D928 light
to indicate primary or secondary line
trouble and COMM FAIL.
No No D928 Dual Phone Line Module.
Use this program item when a D928 Dual Phone
Line Module is connected to the control panel. Both
lines must operate the same; either ground start or
loop start.
0101
0101
0101
IMPORTANT! Program Phone Supv Time
when using two phone lines.
NFPA standards prohibit the use of ground
start phone lines in systems monitoring
Fire points. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 15
Bosch Security Systems | 1/04 | 47775E
BFSK Duress Code
Default:0
Selection:0 to 9
If Duress Enable in Area Parameters is Yes and
Modem Format in Phone Parameters is No, you
must program a number to identify Duress Reports
at the central station.
Expand Test Rpt
Default:No
Selection:Yes or No
Yes Report events listed in Routing Group
Test Reports report to the central
station if they are off-normal.
No Does not report off-normal conditions
for the events listed in the Routing
Group Test Reports at test time.
Use this program item to add system event
information to scheduled Test Reports. Test Reports
are set up as scheduled events. See Section 5.2 Skeds.
This parameter is related only to Sked
Function Code 9 (Test Report) and
whether this Sked transmits Expanded
Test Report information or not. It does not
have any bearing on Sked Function Codes
28 (Expanded Off-Normal Test Report)
and 29 (Non-Expanded Off-Normal Test
Report).
Ground Start
Default:Long
Selection:Long or Short
Long Standard duration of ground. Use this
setting for most ground start telephone
systems. The duration is 700
milliseconds.
Short Shorter duration of ground. Use this
setting for telephone systems where
specified. The duration is 250
milliseconds.
Some newer ground start telephone exchange
switches require a shorter amount of time to initiate
dial tone. If the control panel cannot initiate a dial
tone on the ground start line with the default (long)
setting, try the short setting.Press the [SPACE] bar to scroll through the
selections. Press [ENTER] when the correct selection
appears in the display.
Use this program item only when the control
panel is connected to ground start
telephone lines. Ground start is not allowed
on UL Listed systems.
2.3 Routing
Use routing to select full or partial groups of events
which report to up to four different destinations.
Routing includes choosing the most important
destination (route number), the events reported to a
single or multiple destination, and if the events fail,
selecting a backup destination.
2.3.1 Called Party Disconnect
Telephone companies provide called party
disconnect to allow the called party to terminate a
call. The called party must go on hook (hang up) for
a fixed interval before a dial tone is available for a
new call. This interval varies with telephone
company equipment. D9412G/D7412G firmware
allows for called party disconnect by adding a 35
second on hook interval to the dial tone detect
function. If the control panel does not detect a dial
tone in 7 seconds, it puts the phone line on hook for
35 seconds to activate called party disconnect, goes
off hook and begins a 7-second dial tone detect. If
no dial tone is detected, the control panel dials the
number anyway. Each time the number is dialed,
the control panel records this as an attempt. After
ten attempts, the control panel goes into
communications failure and Comm Fail Route #
displays on the command centers.
2.3.2 Route Number Groups: Which Has the
Highest Priority?
To program a group, first choose a route number.
The lower the route number, the higher priority that
group has (for example, events reported for Route 1
have a higher priority than Routes 2, 3, or 4 if each
group tries to send a message at the same time). This
becomes important when programming duplicate
reports or choosing the events you want to ensure
report first regardless of the number of events that
need to report to multiple groups. Route 1 group
primary device is the first destination the control
panel attempts to dial if an event in that group must
be reported. If the control panel is idle, any event
generated for any group initiates a dialing sequence. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 16
Bosch Security Systems | 1/04 | 47775E
2.3.3 Programming a Primary and Backup
Destination
Each route number has an 
R# Primary Device and
an 
R# Backup Device. In typical applications
where two phone numbers are programmed, the 
R#
Primary Device
 destination is the phone number
the route group attempts to dial first. If the
 R#
Primary Device
 destination fails to connect to the
central station receiver after two dialing attempts, the
R# Backup Device destination is dialed. In
addition, the control panel can be programmed so
the 
R# Primary Device and/or the R# Backup
Device
 can be an SDI device, such as a D9133TTL-
E Network Interface Module. The control panel can
also be programmed to make only one attempt for
the 
R# Primary Device before attempting to send
events using the 
R# Backup Device.
2.3.4 Enhanced Routing
In previous versions, only Phone numbers 1 through
4 could be programmed for the Primary and Backup
Destinations. The D9412G/D7412G allow events to
be transmitted to up to four additional SDI Paths.
The D9133TTL-E Network Interface Module (with
Ethernet) connects directly to the SDI Bus and
occupies SDI Address 88. For additional information
regarding the specific programming requirements for
enhanced communications, see Sections 2.4 Enhanced
Routing and 6.5 Enhanced Communications.
2.3.5 Programming a Duplicate Report
To allow an event within a group to report to
multiple groups, the event should be Yes for each
route number available. For instance, programming
Fire Alarms for Route Group 1 and Route Group 2
results in the fire alarms first reporting to Route
Group 1 followed by a duplicate report to Route
Group 2.2.3.6 Routing Destination Communication
Failures
When the 
R# Primary Device fails to connect with
the central station after one or two attempts (see
RG# 1 Attempt in Section 6.6.1 Route Group
Attempts), the 
R# Backup Device phone number or
SDI Path is attempted. The central station receives
the original event with a COMM FAIL PHONE# =
(1, 2, 3, or 4) if the 
R# Primary Device destination
is a phone number. If the 
R# Primary Device is an
SDI Path, the central station receives the original
event with A COMM FAIL RG# SDI## (SDI Path
1 = 88, SDI Path 2 = 89, SDI Path 3 = 90, SDI Path
4 = 91). When all attempts to both the 
R# Primary
Device
 and R# Backup Device fail, a Comm Fail
RG# Event is generated. Comm Restore Events are
not generated.
2.3.7 Message Prioritization within a Route
Number
The D9412G/D7412G Control Panels meet the
digital reporting requirements for UL 864. Fire
Alarm Events have the highest priority and are
reported first for each group. The next highest
priority events are in the following order: panic,
duress, medical, intrusion alarm, supervisory, and all
troubles and restorals.
0101
0101
0101To comply with NFPA and UL864, you
must program Route 1 to report only Fire
Alarm Events to ensure the fastest
reporting time.
2.3.8 Dialing Attempts
The D9412G/D7412G Control Panels have a
prompt called 
RG# 1 Attempt (see Section 6.6.1
Route Group Attempts.).
If this item is set to No, the control panel first makes
up to six attempts to make contact using the primary
device within a route group. If unsuccessful, it makes
up to four attempts to make contact using the
backup device before initiating a Comm Fail Report.
When only one destination is programmed, the
control panel makes ten attempts to contact that
destination. Each group takes approximately 10
minutes to go into Comm Fail.
If this item is set to Yes, the control panel only
makes one attempt (instead of two) to contact the
primary device before attempting to contact the
backup device. The route group still makes a total of
ten attempts; however, the 
R# Primary Device
makes five attempts and then the R# Backup
Device
 makes five attempts. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 17
Bosch Security Systems | 1/04 | 47775E
Route #
Default:1
Selection:1 to 4
1 First group sent
2 Second group sent
3 Third group sent
4 Fourth group sent
Enter the number specifying the route group to
program. The route represents the group you wish to
send a group of reports. The groups are prioritized. 1
is the first group to report and 4 is the last group to
report. Each group has a primary and a backup
device. The primary device is the first (most
important) destination used to reach the
programmed route within this group. The backup
device is used if the primary device fails.
 R# Primary Device
Default:Blank
Selection:Blank, 1 to 4
1 Phone 1 or SDI Path 1 is this group’s
primary destination.
2 Phone 2 or SDI Path 2 is this group’s
primary destination.
3 Phone 3 or SDI Path 3 is this group’s
primary destination.
4 Phone 4 or SDI Path 4 is this group’s
primary destination.
Enter the number specifying the primary device.
R# Backup Device
Default:Blank
Selection:Blank, 1 to 4
1 Phone 1 or SDI Path 1 is this group’s
backup destination if the primary
destination fails.
2
Phone 2 or SDI Path 2 is this group’s
backup destination if the primary
destination fails.
3 Phone 3 or SDI Path 3 is this group’s
backup destination if the primary
destination fails.
4 Phone 4 or SDI Path 4 is this group’s
backup destination if the primary
destination fails.
Enter the number specifying the backup device. The
backup device is used when the primary device fails
to reach the programmed destination.
View Events?
Default:No
Selection:Yes or No
Yes
Access each routing group and
program individual events for this
route group only (D5200).
No
Continue programming without
viewing individual groups.
The D5200 Programmer reveals the following sub-
prompts. Leaving 
View Events? as No allows the
user to ignore a large area of programming that
might not need to be changed. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 18
Bosch Security Systems | 1/04 | 47775E
Fire Reports
Selecting Yes enables a report to be sent when the
event occurs.
Table 9: Diagnostic Reports
Report Selections Description
R# Fire AlarmYes, NoReports Fire Event.
R# Fire Restore
(Alarm)Yes, NoReports fire restoral
from alarm.
R# Fire MissingYes, NoReports missing Fire
point.
R# Fire Trouble
Yes, NoReports fire trouble.
R# Fire
Supervis
Yes, NoReports fire
supervision.
R# Fire Restore
(T/M/S)Yes, NoReports fire restoral
from trouble,
missing, or bypass.
R# Fire CancelYes, NoReports canceled
fire alarm.
R# Fire Sup
MissYes, NoReport fire
supervisory missing.
R# Fire Supv
Rest*Yes, NoReports restorals
from Fire
Supervision.
*  This event is not reported when using BFSK format.
Burglar Reports
Selecting Yes enables sending a report when the
event occurs.
Table 10: Burglar Reports
Report Selections Description
R# AlarmYes, NoReport Burglar Alarm
Event.
R# Burg
RestoreYes, NoReports non-fire
restoral from trouble,
missing, or
supervisory.
R# DuressYes, NoDuress Report.
R# Missing
AlarmYes, NoReports missing
Alarm point.
R# Usr Code
Tmpr
Yes, NoReports user code
tamper.
R# Trouble Rpt
Yes, NoReports Trouble
Event.
R# Missing TrblYes, NoReports Missing
Trouble Event.
R# Non Fire
SuprvYes, NoReports Non-fire
Supervision Event.
R# Pt Bus FailYes, NoReports point bus
failure.
R# Pt Bus Rstl
Yes, NoReports restoral of
point bus after failure.
R# Non Fire
Cncl
Yes, NoReports canceled
non-fire alarm.
R# Alarm
RestoreYes, NoReports non-fire
restoral from alarm.
R# Sup MissingYes, NoReports supervisory
missing.
R# Unverfied
Evt†*Yes, NoReports Unverified
Events for Cross
points.
† This event is not reported when using BFSK format.
*  This event does not produce a corresponding Restoral
Event.
0101
0101
0101The Unverified Event is transmitted when a
single point programmed in Cross Point
Group faults into an alarm condition then
restores before the Cross Point Time
elapses. This event encompasses both
Fire and Non-fire points. It is not, however,
related to the Verify Time used for smoke
detectors. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 19
Bosch Security Systems | 1/04 | 47775E
Restoral Reports are not sent if the
control panel is reset after a point is
bypassed and then the point is
unbypassed. This is true for both Fire and
Non-fire points.
The 9000 Series Control Panels log a
Ground Fault Event as Trouble Point 256.
User Reports
Selecting Yes enables a report to be sent when the
event occurs.
Table 11: User Reports
Report Selections Description
R# Point
Bypass
Yes, NoReports Point
Bypass Event.
R# Forced
PointYes, NoReports Forced
Point Event.
R# Point OpenYes, NoReports Point
Opening Event.
R# Point Close
Yes, NoReports Point
Closing Event.
R# Forced ArmYes, NoReports point forced
armed.
R# Fail To
OpenYes, NoReports Fail to
Open Event.
R# Fail To
Close
Yes, NoReports Fail to
Close Event.
R# Ext Clos Tm
Yes, NoReports Extend
Close Time Event.
R# Opening
Rpt
Yes, NoReports Opening
Events.
R# Forced
CloseYes, NoReports Point
Forced Close Event
R# Closing RptYes, NoReports Closing
Events.
R# FC Perim
InstYes, NoReports Forced
Close Perimeter
Instant Armed Event.
R# FC Perim
Delay
Yes, NoReports Forced
Close Perimeter
Delay Armed Event.
R# Perim Inst
ArmYes, NoReports Perimeter
Instant Armed Event.
R# Perim Delay
Arm
Yes, NoReports Perimeter
Delay Armed Event.
R# Send User
TextYes, NoReports user text. 
						

							D9412G/D7412G | Program Entry Guide | 2.0 9000MAINEN | 20
Bosch Security Systems | 1/04 | 47775E
Test Reports
0101
0101
0101To send a single Test Report (R# Test
Report), enable Sked Function Code #9
(Test Report) in the Skeds section of the
program.
To expand this Test Report to include any
off-normal point condition or other off-
normal conditions of events listed in Diag
Reports as a Non-status Event following a
Test Report, Expand Test Rpt in Section
2.2 Phone Parameters must be
programmed Yes.
Events R# Log Threshold, R# Log
Overflow, and R# RAM Fail are added to
the reports sent with Expanded Test
Reports if they are enabled in RAM Reports
and Expand Test Rpt is also enabled.
To initiate a Status Report, which includes
all R# S: ____ Events as a Status Event (as
opposed to a Non-status Event), Sked
Function Code #10 must be enabled in the
Skeds section of the program.
Reporting off-normal conditions as a Status
Report following a Test Report is required
by some automation systems. Reporting off-
normal conditions as a Non-status Report,
which follows a Test Report, is required for
other automation systems.
An off-normal condition is any point which is
missing, trouble, supervisory, or in alarm (as
opposed to normal). Also, points not
cleared at the command center report as
off-normal.
Control Panels with Firmware version 6.30
or higher can generate an Expanded Off-
Normal Test Report by using Sked Function
Code 28 or a Non-Expanded Off-Normal
Test Report using Sked Function Code 29.
To generate this event, one or more points
must be in an off-normal state at the time
the Sked executes. Expanded Off-Normal
Test Reports include the Off Normal Test
Report Event as well as events for any
points that are in an off-normal state at the
time the report is generated. Non-Expanded
Off-Normal Test Report Events are only
sent when a point is in the off-normal state
but only sends the Off Normal Test Report
Event.
Table 12: Test Reports
Report Selections Description
R# S: AlarmYes, NoStatus Alarm Report
R# S: Trouble
Yes, NoStatus Trouble
Report
R# S:
Supervised
Yes, NoStatus Supervised
Report
R# Status
ReportYes, NoStatus Report
R# S: OpenYes, NoStatus Open Report
R# S: Close
Yes, NoStatus Close Report
R# Test ReportYes, NoTest Report
R# S: Perim
InstYes, NoStatus Perimeter
Instant Arm Report
R# S: Perim
Delay
Yes, NoStatus Perimeter
Delay Arm Report
R# S: Fire Supv
Yes, NoStatus Fire
Supervision Report
R# S: Fire
Alarm
Yes, NoStatus Fire Alarm
Report
R# S: Fire Trbl
Yes, NoStatus Fire Trouble
Report
R# S: Msng
Fire
Yes, NoStatus Fire Missing
Report
R# S:
MsngBurgTrYes, NoStatus Burg Missing
Trouble Report
R# S:
MsngBurgAl
Yes, NoStatus Burg Missing
Alarm Report
R# S:
FireSpMsngYes, NoStatus Fire
Supervision Missing
Report
R# S:
SuperMsng
Yes, NoStatus Non-fire
Supervision Missing
Report
R# S:
DrLeftOpenYes, NoStatus Door Left
Open Report
 Diag Reports
Selecting Yes enables sending a report when the
event occurs. If the off-normal state of the following
events (indicated with an *) still exist, they report
when a Test Report (see the 
Test Reports sub-
prompt in Section 2.3.8 Dialing Attempts) is initiated
and Expanded Test Rpt is programmed Yes.