Fire Safety

MDACT
Digital Alarm Communicator/Transmitter
Programming Manual

Siemens Building Technologies, Inc. Siemens Building Technologies, Ltd.

8 Fernwood Road 2 Kenview Boulevard
Florham Park, New Jersey 07932 Brampton, Ontario L6T 5E4 CN

P/N 315-099378-2
 This page is intentionally blank.

Page 2 MDACT Programming Manual

 Contents

Contents

1.0 MDACT Operation ......................................................................................................................................................... 5

1.1 Communicator Operation ............................................................................................................................................... 5
1.2 Keypad Operation ........................................................................................................................................................... 9
1.3 Modes of Operation: Program, Status, History, Test and Reset ................................................................................... 13

2.0 How to Program .......................................................................................................................................................... 17

2.1 Keypad Programming ................................................................................................................................................... 17
2.2 Programming Key Sequences ...................................................................................................................................... 17
2.3 Connecting the Keypad ................................................................................................................................................ 19

3.0 Program Menu Tree .................................................................................................................................................... 21

4.0 Specific Programming Instructions .......................................................................................................................... 25

4.1 Prog Time ..................................................................................................................................................................... 25
4.2 Prog Timers .................................................................................................................................................................. 27
4.3 Program Inputs ............................................................................................................................................................. 28
4.4 Prog Relay .................................................................................................................................................................... 29
4.5 Prog Acc’nts .................................................................................................................................................................. 30
4.6 Prog Formats ................................................................................................................................................................ 35
4.7 Prog Defaults ................................................................................................................................................................ 36
4.8 Slave Connctn .............................................................................................................................................................. 37

Appendix A: MDACT Troubleshooting .................................................................................................................................... 39

Appendix B: Compatibilities .................................................................................................................................................... 41
Appendix C: Reporting Summary for Fire Communicator .................................................................................................... 43
Appendix D: Programming Defaults List ................................................................................................................................ 45
Appendix E: Report Routing .................................................................................................................................................... 47
Index ........................................................................................................................................................................................... 49

MDACT Programming Manual Page 3

Contents

Figures

Figure 1: Connecting a Keypad to the MDACT ............................................................................................................................ 9

Figure 2: DCT-P Keypad Key Descriptions ................................................................................................................................. 10
Figure 3: Additional Functions of the [Drill], [Disable] and [Reset] Keys. ................................................................................... 11
Figure 4: Scrolling Main Menu .................................................................................................................................................... 11
Figure 5: Exclusive Keys ............................................................................................................................................................. 11
Figure 6: Shared Keys ................................................................................................................................................................ 12
Figure 7: Sub-menu Items .......................................................................................................................................................... 12
Figure 8: Event History Example ................................................................................................................................................ 13
Figure 9: Programming Key Sequence for System Date ............................................................................................................ 17
Figure 10: Programming Key Sequence Diagram ...................................................................................................................... 18
Figure 11: Connecting a Keypad to the MDACT ......................................................................................................................... 19

Tables

Table 1: Report Routing with Primary and Alternate Phone Number, Phone 2 Backup .............................................................. 6
Table 2: Event History Abbreviations .......................................................................................................................................... 14
Table 3: SYS TROUBLE LED Indications ................................................................................................................................... 40
Table 4: MDACT UL Listed Compatibility .................................................................................................................................... 41

Page 4 MDACT Programming Manual

 System Operation

1.0 MDACT Operation

1.1 Communicator Operation
The MDACT contains an integrated communicator that sends reports to a monitoring station. Operation of the
communicator is fully automatic.
When events occur, the communicator sends corresponding reports to the monitoring station in priority order according
to NFPA requirements. Fire and waterflow alarms are sent first, followed by supervisory alarms and trouble reports and,
finally, all other reports.
Note: Priority sorting of events sent to a monitoring station may cause the message sequence to imply that a point has been
restored when it actually has not. For example, the sequence “alarm”, “restore”, “alarm” would be transmitted as “alarm”,
“alarm”, “restore” when priority sorting is applied.
1.1.1 Phone Line and Phone Number Selection
Note: To comply with UL and NFPA standards, you must program both a primary and alternate phone number. The numbers
must be different.
The MDACT can report to two (2) phone numbers with full single, double and back-up reporting. It communicates in
Contact ID and SIA formats.
To ensure the delivery of critical reports, the MDACT has two phone lines and two phone numbers that can be used for
reporting. Reports can be “steered” to one or both of the two phone numbers using the report steering feature in the
dialer programming. Account Number 1 is used with Phone Number 1 and Account Number 2 is used with Phone
Number 2.
Note: Except for test reports, the MDACT automatically selects the phone line to be used.
Report routing is conducted as follows:
• Reporting starts using Phone Number 1 on Phone Line 1, unless the line monitor shows it to be bad at the start of
reporting. If the report is not successful attempting to use Phone Number 1 on Phone Line 1, the MDACT will
automatically switch and use Phone Number 2 on Phone Line 1.
• If the report is still unsuccessful using either phone number on Phone Line 1, then the MDACT will try to send the
report on Phone Line 2 using Phone Number 1 first, then Phone Number 2 if necessary.
See Table 1 for the complete report routing pattern.
The one exception to this is when test reports (manual or automatic) are sent. Test reports are sent to alternating phone
lines regardless of phone monitor or initial failure to report. This allows both phone lines to be tested if the user sends
two manual test reports. The first report will use one line and the second will use the other line. Automatic test will
automatically alternate phone lines; manual test requires the user to determine which phone line is used for testing
purposes (Phone 1, Phone 2 or alternating phone lines).
Note: Since the MDACT automatically selects which line is to be used, both phone lines must use the same dialing sequences
for reporting. For example, a phone line which requires a “9” to be dialed for an outside line cannot be paired with a line
that does not require a “9”. In any case, PBX lines and ground start phone lines do not comply with NFPA requirements
for digital communication.

MDACT Programming Manual Page 5

System Operation
1.1.2 Telephone Line Supervision
The MDACT monitors the Primary and Alternate telephone lines while the communicator is idle by “sniffing” the line for
trouble. The total time for trouble indication is 36 seconds.
Each line is “sniffed” every 12 seconds. If a trouble still exists after three samples (36 seconds), the MDACT sends a
trouble report and turns on the yellow phone line LED and System Trouble Relay.
The yellow Phone Line LEDs indicate active communication and show line fault conditions. The LED(s) will flash once
every second during active communication and will be on steady for a line fault condition.
1.1.3 Wait for Dial Tone
When enabled, the Wait for Dial Tone feature ensures a dial tone is present before dialing. If no dial tone is present after
seven seconds, the MDACT hangs up and tries again after a 30-second wait. If no dial tone is detected on the second
try, the MDACT will dial anyway.
If this feature is not enabled, then the MDACT will wait seven seconds after going off-hook, and then dial whether or not
a dial tone is present.
1.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, alarm messages can be set for
Phone 2 Backup while supervisory restorals are sent to Phone 2 only.
Note: Phone 2 Backup is the default setting for all event types and is the recommended setting. Changing this setting may
result in messages not being communicated to the central station.
Each event can be routed through the phone in one of four possible ways:
• PHONE 1 Only: events are sent to the central station using only Phone Number 1.
• PHONE 2 Only: events are sent to the central station using only Phone Number 2.
• PHON 1 AND 2: events are sent to the central station using both Phone Number 1 and Phone Number 2.
• PHN 2 BACKUP: events are sent to the central station primarily using Phone Number 1 with Phone Number 2 used
as a backup in case communication cannot be established with Phone Number 1. This is the default setting for the
dialer.
See Appendix E for more information regarding report steering.
Note: SIEMENS Fire Safety recommends using the default setting of Phone 1 with Phone 2 as backup. If this setting is
changed, the phone lines used will change and messages may not be sent to the central station. Also note that Table 1
does not apply to the “PHONE 1 ONLY” and “PHONE 2 ONLY” route settings.
1.1.5 Call Attempts
When an event must be communicated to the central station, the dialer will make one attempt at communication. If that
attempt is not successful (call is not answered/acknowledged), the dialer then goes into a series of attempts. It will
attempt communication with the central station 10 times. Table 1 shows the procedure the dialer will follow for attempting
to communicate with the central station when it is programmed to use Phone 2 Backup (default) or Phone 1 and 2.

Attempt Primary Phone Line (Phone 1) Secondary Phone Line (Phone 2)

1 1st phone number

2 2nd phone number

3 1st phone number

4 2nd phone number

5 2nd phone number

6 1st phone number

7 1st phone number

8 2nd phone number

9 2nd phone number

10 1st phone number

Table 1: Report Routing with Primary and Alternate Phone Number, Phone 2 Backup

Page 6 MDACT Programming Manual

 System Operation
1.1.6 Communication Fault
When a report must be transmitted to the central station, the MDACT will attempt communication. If the attempt is not
acknowledged, the dialer will make nine more attempts (see Table 1). If, after 10 attempts, the dialer has not made a
successful connection, a communication failure occurs and a COMM FAULT report is generated.
The dialer will then attempt to communicate the COMM FAULT to the central station. If it is unsuccessful on the first
attempt, it will proceed to make nine more attempts for a total of 10 attempts. If the dialer is not successful after 10
attempts at communicating the COMM FAULT report, the original report and the COMM FAULT are cleared from the
dialer’s buffer.
The total time from the first sequence of attempts to communicate a failure is approximately 15 minutes (depending on
programming of ACK WAIT time). A COMM FAULT RESTORAL report is transmitted when communication is restored
after a communications failure.
1.1.7 Programming Fault
Programming faults are used to indicate if specific phone programming items have not been completed.
A programming fault is generated if:
• Both account numbers are not changed from their default values (0000).
• Neither phone 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 Number 1 and 2 or to Phone 1 with Phone 2 as backup and at least one of the account
numbers is “0000” or one of the phone numbers is invalid.
1.1.8 Lost Data
A DATA LOST report is generated when an event cannot be transmitted to the central station. This can occur during two
possible situations:
• If the reporting buffer contains the maximum 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, then 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, thus emptying the report buffer. If the buffer fills again, another
DATA LOST report is sent.
• If the MDACT has sent 99 trouble reports in a 24-hour period and another trouble report is generated, that report will
be changed to a DATA LOST report. The DATA LOST report tells the central station that the 100-event limit for trouble
messages has been reached.
DATA LOST reports are entered into the history buffer.
1.1.9 Limited Reports
To reduce the number of reports that are sent to the central station, the MDACT will only transmit 100 trouble reports in
a 24-hour period. If the MDACT communicates 99 trouble reports to the central station within a 24-hour period, when
the next trouble report is generated, it is changed to a DATA LOST report that is sent to the central station.
The trouble report counter may be reset to allow more trouble reports to be sent to the central station. A Manual Test
Report will reset the counter to zero. The counter will always be reset at 9:00 a.m. regardless of when it is manually
reset.
1.1.10 Communications Tests
The MDACT can perform two types of communications tests: Auto Test and Manual Test. These tests verify the MDACT’s
operation and its ability to transmit a report over the phone line to a receiver. The Auto Test occurs automatically at a
fixed frequency set by the installer. The Manual Test occurs when initiated by the user.

MDACT Programming Manual Page 7

System Operation
1.1.10.1 Auto Test
Auto Test is an automatic test used to verify proper operation of each phone line connected to the MDACT. The
programmable parameters for Auto Test are set at the DCT-P Keypad (see Section 4.1.2 2: AUTO TEST).
The time ( in 24-hour military format) when automatic testing begins, and the testing frequency interval, are established
from the DCT-P Keypad.
The frequency at which the automatic test reports are sent (or, how often the reports are sent) can be set to one of the
following selections: every 6 hours, every 12 hours, every 24 hours, every 7 days or every 28 days. For example, if the
test time is set to 2300 (11:00 PM), and the test frequency is set for every 24 hours, then automatic testing will begin at
2300 hours and repeat every 24 hours. There is also a “DISABLED” selection to turn off automatic testing.
Note: Setting Auto Test to either 7 days, 28 days or DISABLED is not compliant with Underwriters Laboratories, Inc.

A power cycle will default the system time to “0000.” The system time should be set up again after a power
cycle.

The Auto Test report is sent even if the maximum number of trouble reports to be sent in a 24-hour period (100) has
been exceeded. If the report queue is currently full of reports to be sent, a “DATA LOST” report is sent unless one is
already in the queue. If this is the case, then the Auto Test report is not sent.
Every time an Auto Test report is sent, the phone line that is used alternates. For example, if the first report uses Phone
Line 1, the second report will use Phone Line 2. The third report will use Phone Line 1.
Note: Sending a Manual Test report does not affect the alternating phone line sequence of the Auto Test report.
Unless it successfully sends the report initially, the MDACT will attempt to send the Auto Test report a maximum of 10
times which, consequently, may take up to 15 minutes to complete. The reports are re-prioritized on each phone call
attempt. If a higher priority event occurs while attempting an Auto Test, the higher priority event is sent on the following
phone call.
If the MDACT fails to send the Auto Test report in 10 tries, a COMM FAULT report is sent. The MDACT sends the COMM
FAULT using its normal report routing. When it is time for the next Auto Test attempt, it will be conducted on the
alternate phone line, not the failing phone line.
When it is time to send a report, the MDACT checks its status. If any alarms, troubles or system faults are present, the
MDACT sends the Off Normal at Test report instead. If all conditions are normal, the MDACT sends the Auto Test report.
1.1.10.2 Manual Test
A Manual Communications Test is initiated by the user from the DCT-P Keypad (see Section 1.3.4 “Test Mode”). When
a Manual Test is initiated, the user is prompted to select a phone line (Line 1 or Line 2). After a phone line is selected,
a Manual Test report is sent to the receiver using the specified phone line.
When the Manual Test report is successfully inserted in the report queue, the DCT-P Keypad display will show the
following message, “COMMUNICATOR INITIALIZING...” until the MDACT starts its first attempt to transmit the report.
When the Manual Test report is being sent, the DCT-P Keypad’s display is updated to show the phone line being used
and the transmission attempt that is currently being made. The message, “COMMUNICATOR LINE 1, TRY 1” indicates
that Phone Line 1 is being used on Transmission Attempt #1. After the report has been successfully transmitted, the
DCT-P Keypad’s display is updated to show the following message, “COMMUNICATOR PASSED.” The keypad then
emits a brief tone, and the rotating Test Menu returns to the keypad’s LCD display after displaying the message for two
seconds.
Unless it successfully sends the report initially, the MDACT will attempt to send a Manual Test report twice, which may
take up to three minutes. The reports are re-prioritized on each phone call attempt. If a higher priority event occurs while
attempting a Manual Test, the higher priority event is sent on the following phone call.
Note: See Appendix A: MDACT Troubleshooting for information on error messages or messages that indicate non-normal
operating conditions.

Page 8 MDACT Programming Manual

 System Operation

1.2 Keypad Operation

1.2.1 Understanding the DCT-P LCD Remote Keypad
The DCT-P LCD Remote Keypad is an alphanumeric LCD keypad used for programming and debugging purposes only
when connected to the MDACT. The DCT-P has a two-line by 16-character display to provide information on various
dialer programming functions. In most instances, the first line displays general system status information, while the
second line describes the specific programming menus and prompts.
See Figure 1 to connect the DCT-P to the MDACT.

MDACT Fire Communicator

LINE 1

LINE 2

SYS TROUBLE

HEARTBEAT

+ + - - AB 1 2 3 4 5 KEYPAD NC C NO
DCT-P
Terminal Strip KEYPAD

+12 VDC RED

Com BLACK
Data In GREEN
Data Out YELLOW

Figure 1: Connecting a Keypad to the MDACT

MDACT Programming Manual Page 9

System Operation
See Figure 2 for a description of DCT-P Keypad key functions.

Alarm
First Line Silenced SYSTEM NORMAL
Second Line Power 0: PROGRAM
Trouble
J
Silence

L
H 1 2 3 Reset
K
I 4 5 6 Drill
D
7 8 9 Disable
E
#
C *
Clear
0
Program Command Test
F
History
G

A
B
Figure 2: DCT-P Keypad Key Descriptions
A) [0/Program] Key: Enters the Programming Mode menu when pressed. See Section 4.0 “Specific Programming
Instructions” for step-by-step programming instructions.
B) [#/Command] Key: Accepts programming entries into MDACT. This key must be pressed after every programming
entry.
C) [*/Clear] Key: Use this key to back out of any programming menu without making any changes. To return to the
“SYSTEM NORMAL” display, press the [*/Clear] key until “SYSTEM NORMAL” is displayed across the first line.
D) [Drill] Key: Advances to the next programmable feature or character position. See Figure 3.
E) [Disable] Key: Moves back to the previous programmable feature or character position. See Figure 3.
F) [Test] Key: Pressing the [Test] key enters Test Mode. Pressing the [Test] key when entering a phone number pulls
up three phone control code options. See Section 1.3.4 “Test Mode” for more information.
G) [History] Key: Pressing the [History] key enters History Mode. See Section 1.3.3 “History” for more information.
H) [1] Key: Increases the DCT-P’s sounder volume. Press and hold the [*/Clear] key first, and then press the [1] key
to adjust the volume.
I) [4] Key: Decreases the DCT-P’s sounder volume. Press and hold the [*/Clear] key first, and then press the [4] key
to adjust the volume.
J) [3] Key: Increases the DCT-P’s backlight intensity. Press and hold the [*/Clear] key first, and then press the [3] key
to adjust the backlight intensity.
K) [6] Key: Decreases the DCT-P’s backlight intensity. Press and hold the [*/Clear] key first, and then press the [6]
key to adjust the backlight intensity.
L) [Reset] Key: Initiates a manual reset of the MDACT. See Section 1.3.5 “Reset” for more information. Clears the
character selected by the cursor when pressed. See Figure 3.

Page 10 MDACT Programming Manual

 System Operation

Press [Drill] to advance cursor to next position.

PHN NMBR 1: 5551 Drill

PHN NMBR 1: 5551
234????????????? 234?????????????

Press [Disable] to move cursor back one position.

PHN NMBR 1: 5551 Disable

PHN NMBR 1: 5551
234????????????? 234?????????????

Press [Reset] to clear character currently selected.

PHN NMBR 1: 5551 Reset

PHN NMBR 1: 5?51
234????????????? 234?????????????
Figure 3: Additional Functions of the [Drill], [Disable] and [Reset] Keys.
1.2.2 Scrolling Menus
When properly connected to the MDACT, the DCT-P will display along its second line a scrolling menu of possible user
actions. This scrolling menu is the MDACT’s Main Menu. The scrolling menu items flash one at a time at 1-second
intervals through the list and then start over. When operating normally, “SYSTEM NORMAL” is displayed along the first
line on the DCT-P LCD.

SYSTEM NORMAL
0: PROGRAM
1: STATUS
2: HISTORY
3: TEST
4: RESET
Figure 4: Scrolling Main Menu
The Programming Menu and Test Menu options also flash across the second line one at a time at 1-second intervals.
The speed of the display rate can be adjusted. See Section 4.2.2 “2:DISPLAY RATE” for more information.
1.2.3 Selecting Menu Items
Depending on what menu level you are at (menu, sub-menu, sub-sub-menu, etc.), there are three ways to select an
item:
• Exclusive Keys: In the Main Menu, TEST and HISTORY have an exclusive key on the DCT-P Keypad. To select one
of these menu items, you may select the item from the Main Menu by pressing the corresponding key or by pressing
the exclusive function key. For example, TEST is the third choice in the Main Menu. Pressing either the [3] from the
Main Menu or pressing the [Test] key will call up the Test Mode Menu. See Figure 5.

SYSTEM NORMAL
Test
3: TEST
OR Press the [TEST] key
Press the [3] key
from the Main Menu on the DCT-P Keypad
Figure 5: Exclusive Keys
• Shared Keys: The [Program], [Clear] and [Command] keys are not exclusive, but shared with other characters.

MDACT Programming Manual Page 11

System Operation
The character sharing the corresponding key is displayed on the same key. These keys are the [*/Clear], [0/Program]
and [#/Command] keys. To select one of these items, press the shared key. For example, The [Program] key is also
the [0] key. If an asterisk (*) is required, press the [*/Clear] key to enter this character.

SYSTEM NORMAL
0
0: PROGRAM Program

Enter the Programming Mode by pressing the [0/Program] key.

*
Clear

Press the [*/Clear] key to enter an asterisk (*).

Figure 6: Shared Keys
• Sub-menu Items: The corresponding key to a sub-menu item may be displayed in the second line preceeding a
dash. Press the corresponding key to select that item. For example, press the [1] key to select PROG TIME from the
Programming Mode menu.

PROG MODES
1: PROG TIME 1
Corresponding Key
Figure 7: Sub-menu Items
Note: When a scrolling menu is active, it is not necessary to wait for the desired menu item to appear before making your
selection. Any item on the current menu rotation can be selected at any time.

Page 12 MDACT Programming Manual

 System Operation
1.3 Modes of Operation
The MDACT has five modes of operation: PROGRAM, STATUS, HISTORY, TEST and RESET. Each of these modes
appear as selections on the MDACT’s Main Menu.
SYSTEM NORMAL
0- PROGRAM
1- STATUS
2- HISTORY
3- TEST
4- RESET
1.3.1 0-PROGRAM
When the DCT-P LCD Remote Keypad is connected to the MDACT, the Main Menu will appear shortly after keypad
start-up. See Section 4.0 “Programming” for step-by-step programming instructions.
1.3.2 1-STATUS
When the Status Mode is selected, the top line shows the highest priority off-normal condition. The second line shows
each off-normal condition sequentially.
Pressing the [*/Clear] key terminates Status Mode and returns the display to Main Menu.
1.3.3 2-HISTORY

The history buffer is cleared when the system loses all power.

The HISTORY option is a list of system events that have occurred. HISTORY can be selected from the Main Menu by
pressing the [2] key, or by pressing the [History] key.
Up to 100 events can be stored in the history buffer.
Once you enter the History Mode, the most recent system event will be displayed on the top line of the DCT-P’s LCD.
The time and date will appear on the second line. As a reminder, the bottom line will toggle every four seconds between
the time/date that the event occurred and the keys to use to navigate through the history buffer.
The following keys are used on the DCT-P Keypad to navigate through the history buffer:
• [Disable]: moves to older events in the history buffer.
• [Drill]: moves to newer events in the history buffer.
• [*/Clear]: terminates History Mode and returns the display to the Main Menu.

Total # of
stored events 037/037 KEYPD:IN
Event # Event NXT-DRL/PRV-DIS
037/037 KEYPD:IN
02:51 010100 Press [Drill] to Press [Disable]
advance to the to display the
Time next event. previous event.
Month Year
Day
Figure 8: Event History Example

MDACT Programming Manual Page 13

System Operation
Table 2 lists the event history abbreviations.

Abbreviation Meaning Abbreviation Meaning

A, ALRM Alarm OFFNORM Off Normal at Test

AUTOTST Auto Test PGMG:FLT Trouble Programming

ARST Alarm Restore PH1 Phone Line 1

BATT:LOW Battery Low PH2 Phone Line 2

BAT:RSTR Battery Restore RS, RST, RSTR Restore

COMM Communication S Supervisory

DATALOST Data Lost SYSFLT:F Trouble Input

EE2 EEPROM SYSFLT:R Trouble Input Restore

F Fire SYS:RSET System Reset

FAIL Failure SYSRST System Restore

FLT Fault SYSTRB System Trouble

KEYPD: IN Keypad Installed WDOG:RST Automatic CPU Reset (Watchdog)

KEYPD: RS Keypad Removed TRBL Trouble

M Monitor TRST Trouble Restore

MANULTST Manual Test W Waterflow Alarm

Table 2: Event History Abbreviations

1.3.4 3-TEST
Note: Do not select 2: TEST TONES. This selection is for factory testing only.
Selecting Test Mode brings up the following test items:
TEST MODES
1: TEST COMM
2: TEST TONES
1.3.4.1 TEST COMM
Programming Key Sequence: [3]-TEST, [1]-TEST COMM
Description: Selecting TEST COMM allows you to initiate a manual communications test.
Procedure:
1) From the Main Menu, press [3] for TEST. The TEST MODES window (above) will display.
2) Press [1] to select TEST COMM. The following window will display:
SEL PHONE LINE
1: LINE 1
2: LINE 2
3: ALTERNATE

Page 14 MDACT Programming Manual

 System Operation
Note: Alternate uses the phone line not used in the previous comm test.
3) Select the appropriate line to be tested (Line 1 or Line 2). Once a line is selected, a manual communications test
is initiated and the following window will display:
COMMUNICATOR
LINE 1, TRY 1
The bottom line indicates the line on which the manual communications test has been initiated and the current attempt
(try). The MDACT will attempt a maximum of two tries before declaring a failure. If a failure has been declared, the
following window will display:
COMMUNICATOR
FAILED
This message will display briefly, and then the LCD will return to the TEST MODES menu.
If the manual communications test passes, the following window will display:
COMMUNICATOR
PASSED
This message will display briefly, and then the LCD will return to the TEST MODES menu.
Note: For more information regarding the types of communications tests the MDACT can perform, see Section 1.1.10
Communications Tests.
1.3.5 4-RESET
There are four ways the MDACT can be manually reset:
Note: Resetting the Dialer does not reset the MXL System.
1) On the DCT-P LCD Remote Keypad, pressing the [4] key to select RESET from the Main Menu, or pressing the
[Reset] key will reset the MDACT only if there are off-normal conditions present. An OPEN RESET report with a
User ID parameter of 99 is sent when using this way to reset the MDACT.
2) Exiting the Test Mode will reset the MDACT. An OPEN RESET report with a User ID parameter of 99 is sent when
using this way to reset the MDACT.
3) Exiting the Programming Mode will reset the MDACT. An OPEN RESET report with a User ID parameter of 01 is
sent when using this way to reset the MDACT.
4) Powering up the MDACT will reset it, but no OPEN RESET report is sent.

MDACT Programming Manual Page 15

System Operation

This page is intentionally blank.

Page 16 MDACT Programming Manual

 How to Program

2.0 How to Program

2.1 Keypad Programming
All programming for the MDACT is done via the DCT-P LCD Remote Keypad. To properly program the MDACT, two
keys the [#Command] and [*/Clear] keys must always be pressed in addition to the key(s) necessary for making
specific programming entries.
• [#/Command] Key: This key must be pressed to accept an entry into the MDACT.
• [*/Clear] Key: This key must be pressed after the the [#Command] key is pressed to return to the sub-menu/menu
selections.
See Figure 9 for the complete programming key sequence for setting the MDACT’s operational date.
0
1 1 ENTER DATE #
Command
*
Program Clear
MMDDYY: 010100
Press to enter Press to enter Press to select Press to accept Press to move to
SYSTEM for Enter the current entry into system next menu item or to
Programming PROG TIME date using keypad
Mode Menu submenu system date/time backtrack through
keys 0-9 menu(s)
Figure 9: Programming Key Sequence for System Date
Note: Once you have entered the Programming Menu (Level 2), it is no longer necessary to press [0] to re-enter the
Programming Menu. If you press [0] while already in the Programming Menu, the keypad will emit a three-beep error
tone.

When Programming Mode is entered, all monitoring will cease. The MDACT will not process input point events
or supervise the phone lines. Central Station communication is disabled.

2.2 Programming Key Sequences

2.2.1 Understanding Programming Key Sequences
A programming key sequence is a list of keys to push to get to the desired level option. Its purpose is to reduce
repetition and provide quick instructions when programming the MDACT.
• Level 1: Level 1 in the system is the Main Menu. For all system programming, <PROG/0> will be your Main Menu
choice. Therefore, the first number in the key sequence is “0”. The Main Menu selections consist of four options:
- PROGRAM
- STATUS
- HISTORY
- TEST
- RESET
• Level 2: Level 2 is the Programming Mode Menu. It represents the second number in the key sequence. There are
seven programming options:
- PROG TIME
- PROG TIMERS
- PROG INPUTS
- PROG RELAY
- PROG ACC’NTS
- PROG FORMATS
- PROG DEFLTS
• Level 3: Level 3 provides the third set of options that branch from Level 2 (see Figure 11). The third number in the key
sequence represents the option chosen in Level 3.
• Level 4: Level 4 is comprised of keypad prompts that supply instructions specific to the selected menu item.
Note: Not all programming menus will extend to Level 4. If a menu does not reach Level 4, the instructional prompts will
appear on the last (highest) menu level.

MDACT Programming Manual Page 17

How to Program

LEVEL 1 LEVEL 2 LEVEL 3 LEVEL 4

(MAIN MENU)
1: SYSTEM
[1]: SYSTEM

[1]: PROG TIME

[0]: PROGRAM

1st key in shortcut. 2nd key in shortcut. 3rd key in shortcut. Follow the keypad
prompts to make
From the Main Menu From the Programming Menu From the PROG TIME settings for this
(Level 1), press [0] to (Level 2), press [1] to enter the submenu (Level 3), selection. Press [#] to
enter the Programming PROG TIME submenu. press [1] to select 1: confirm the setting.
Menu (Level 2). SYSTEM (Level 4).

Figure 10: Programming Key Sequence Diagram

The example above is the programming key sequence to enter system settings such as the date and time. Once you
have entered the key sequence, follow the procedural description of the specific function you are programming.
Note: Once you have entered the Programming Menu (Level 2), it is no longer necessary to press [0] to re-enter the Programming
Menu. If you press [0] while already in the Programming Menu, the keypad will emit a three-beep error tone.

Page 18 MDACT Programming Manual

 How to Program
2.3 Connecting the Keypad
Note: The DCT-P LCD Remote Keypad is used strictly for programming and debugging purposes only.
A DCT-P LCD Remote Keypad can be used to operate the MDACT Communicator. Plug the molex connector from the
DCT-P onto the connector pins on the MDACT board as shown in Figure 11.
Use the following steps when programming the MDACT from the DCT-P:
1) Set the DCT-P’s address between 1 and 15.
2) Use the wire connector supplied with the MDACT to connect the DCT-P to the MDACT. See Figure 11.
3) Program the MDACT as explained in the programming section of this manual.
Note: If there is no keypad activity for three minutes, the keypad is disabled. The keypad’s buzzer sounds and a “SYSTEM
FAULT” message will appear on the keypad. Disconnect the keypad from the MDACT by removing the wire harness
plug from the MDACT’s keypad pins, then reconnect the wire plug harness to re-enable the keypad.

MDACT Fire Communicator

LINE 1

LINE 2

SYS TROUBLE

HEARTBEAT

+ + - - AB 1 2 3 4 5 KEYPAD NC C NO
DCT-P
Terminal Strip KEYPAD

+12 VDC RED

Com BLACK
Data In GREEN
Data Out YELLOW

Figure 11: Connecting a Keypad to the MCACT

MDACT Programming Manual Page 19

How to Program

This page is intentionally blank.

Page 20 MDACT Programming Manual

 Program Menu Tree

3.0 Program Menu Tree

Level 2 (Programming Menu) Level 3 Level 4 Level 5

1: SYSTEM
1: TEST TIME
1: PROG TIME 2: AUTO TEST TEST FREQ (__)
2: TEST FREQUENCY
3: DAYLIGHT SAV 1: 6 HOURS
2: 12 HOURS
3: 24 HOURS

Note: Setting Auto Test to either 7 days, 28 days 4: 7 DAYS

or DISABLED is not compliant with 5: 28 DAYS
Underwriters Laboratories, Inc.
1: AC FAIL DLY 1: WAIT FOR DC
2: PROG TIMERS
2: DISPLAY RATE 2: WAIT DLY TIME

Note: MDACT will prompt for specific input point to be programmed.

1: CONFIGURE 1: FIRE N/A

3: PROG INPUTS
2: WATERFLOW N/A
3: SUPERVISORY N/A
4: MONITOR N/A
5: SYS FAULT N/A
6: AC FAILURE N/A
7: LOW BATTERY N/A
MUST BE SET TO NO (0)
2: SUPERVISED FOR ALL 5 INPUTS

Note: Use [Drill] to move to the next point

and [Disable] to move to the
previous point.

4: PROG RELAY N/A

1: NUMBER 1
1: ACCOUNT NUMS
5: PROG ACC’NTS 2: NUMBER 2

1: PHONE #1
2: PHONE NUMS 2: PHONE #2

1: PHONE 1 FORMAT 1: 4/2 REPORT N/A

2: SIA 110, RPRT
Note: This feature is not
3: CONTACT ID
3: PHONE CONTROL supported by the
MDACT and has not 4: SIA 300, RPRT
been evaluated by
UL.

2-PHONE 2 FORMAT Same as Phone 1

5: PROG ACCTS continued on next page.

MDACT Programming Manual Page 21

Program Menu Tree
Level 2 Level 3 Level 4 Level 5 Level 6
(Programming
Menu)

5: PROG 3: PHONE
N/A Note: This feature is not supported by the MDACT
ACC’NTS CONTROL
and has not been evaluated by UL.

1: NONSUP 1: PHONE 1 ONLY

4: RPT
ALRM
STEERING 2: PHONE 2 ONLY
3: PHON 1 AND 2
4: PHONE 2 BACKUP

2: SUPVSY Same as NONSUP ALRM

ALRM

3: ALM RSTR,
RST Same as NONSUP ALRM

4: SUPVSY Same as NONSUP ALRM

RSTR

5: TESTS Same as NONSUP ALRM

6: TBL, TBL Same as NONSUP ALRM

RSTR

5: LINE
1: LINE #1 1: DIALING TYPE 1: PULSE ONLY
CONTROL
2: MONITOR LINE 2: TONE/PULSE
3: WAIT DIALTONE 3: TONE ONLY
2: LINE #2
Same as LINE #1

6: ACK WAIT TIME

Page 22 MDACT Programming Manual

 Program Menu Tree
Level 2 (Programming Menu) Level 3 Level 4 Level 5

6: PROG FORMATS N/A Note: This feature is not supported by the MDACT
and has not been evaluated by UL.

7: PROG DEFLTS 1: CLEAR HISTRY

2: DEFAULT ALL EE
3: DEFLT 4/2 CDES N/A Note: This feature is not supported by the MDACT
and has not been evaluated by UL.

8: SLAVE CONNECTN 1: BUS ADDRESS NEW ADDRESS 133

2: SUPERVISE BUS YES (1)/NO(0) YES (1)

MDACT Programming Manual Page 23

Program Menu Tree

Notes:

Page 24 MDACT Programming Manual

 Programming

4.0 Specific Programming Instructions

The MDACT uses scrolling menus to display menu choices. The Main Menu appears as follows:
SYSTEM NORMAL
0: PROGRAM
1: STATUS
2: HISTORY
3: TEST
4: RESET
To enter the Programming Menu, press the [0] key. The Programming Menu appears as follows:
1: PROG TIME
2: PROG TIMERS
3: PROG INPUTS
4: PROG RELAY
5: PROG ACC’NTS
6: PROG FORMATS
7: PROG DEFLTS
Note: Once you have entered the Programming Menu (Level 2), it is no longer necessary to press [0] to re-enter the Programming
Menu. If you press [0] while already in the Programming Menu, the keypad will emit a three-beep error tone.

4.1 PROG TIME

DATE/TIME
1: SYSTEM
2: AUTO TEST
3: DAYLIGHT SAV
Description: The PROG TIME feature provides programming options for setting the system’s date and time, establishing
automatic testing times and adhering to daylight savings.
Programming Procedure:
1) From the Programming Menu, press [1] for PROG TIME. The above window will display. See the following sections
for PROG TIME programming options.
4.1.1 1: SYSTEM
Programming Key Sequence: [0]-PROGRAM, [1]-PROG TIME, [1]-SYSTEM
Description: Selecting 1:SYSTEM allows you to set the current date and time for system operations.
Programming Procedure:
1) From the PROG TIME submenu, press [1] for SYSTEM. The following window will appear:
ENTER DATE
MMDDYY: __________
2) Enter the date followed by [#/Command] to accept the entry.
3) Press [*/Clear] to move to the next feature.
ENTER TIME
HHMM: __________
4) Enter the time in 24-hour format followed by [#/Command] to accept the entry.
5) Press [*/Clear] to return to the PROG TIME (DATE/TIME) scrolling menu. The keypad will display the entries made
before returning to the PROG TIME menu.

MDACT Programming Manual Page 25

Programming
4.1.2 2: AUTO TEST
AUTOMATIC TEST
1: TEST TIME
2: TEST FREQUENCY
Programming Key Sequence: [0]-PROGRAM, [1]-PROG TIME, [2]-AUTO TEST
Description: AUTO TEST allows you to set the time when the auto test is sent and how often the automatic test occurs.
Programming Procedure:
1) From the PROG TIME submenu, press [2] for AUTO TEST. The above window will appear. See the following
sections for AUTO TEST programming options.
4.1.2.1 1: TEST TIME
Programming Key Sequence: [0]-PROGRAM, [1]-PROG TIME, [2]-AUTO TEST, [1]-TEST TIME
Description: 1: TEST TIME allows you to program the time of day at which automatic tests occur and uses a 24-hour
clock (for example, enter 2300 for 11:00 PM).
Programming Procedure:
1) From the AUTO TEST submenu, press [1] for TEST TIME. The following window will appear:
AUTO TEST TIME
HHMM: __________
2) Enter the time in 24-hour format followed by the [#/Command] key.
3) Press the [*/Clear] key to return to the AUTO TEST submenu.
4.1.2.2 2: TEST FREQUENCY
Programming Key Sequence: [0]-PROGRAM, [1]-PROG TIME, [2]-AUTO TEST, [2]-TEST FREQUENCY
Description: This feature allows you to program how often the automatic test reports are sent. The first test will be sent
when the system time matches the next programmed test time. Subsequent reports will be sent to the selected interval.
Programming Procedure:
1) From the AUTO TEST submenu, press [2] for TEST FREQUENCY. The following window will appear:
AUTO FREQ (_)
1: 6 HOURS
2: 12 HOURS
3: 24 HOURS
4: 7 DAYS
5: 28 DAYS
6: DISABLED This item is not currently supported.
2) Press the number key that corresponds to your selection followed by the [#/Command] key. The revised setting is
displayed in parentheses on the first line.
3) After you have programmed the test frequency, press the [*/Clear] key to return to the AUTO TEST submenu.

Page 26 MDACT Programming Manual

 Programming
4.1.3 3: DAYLIGHT SAV
Programming Key Sequence: [0]-PROGRAM, [1]-PROG TIME, [3]-DAYLIGHT SAV
Description: DAYLIGHT SAV enables automatic adjustment of system time for daylight savings. The dates for the
adjustment are pre-programed into the system.
Programming Procedure:
1) From the PROG TIME submenu, press [3] for DAYLIGHT SAV. The following window will appear:
DAYLIGHT SAVING?
NO: YES (1)/NO (0)
2) The current setting precedes the colon (:) in the second line. Press [1] to set DAYLIGHT SAV to YES. Press [0] to
set it to NO.
3) Press the [#/Command] key to confirm your selection.
4) After you have programmed this feature, press the [*/Clear] key to return to the PROG TIME submenu.
4.2 PROG TIMERS
PROG TIMERS
1: AC FAIL DLY
2: DISPLAY RATE
Description: The PROG TIMERS feature allows the user to set time-related parameters for AC Fail Delay and Display
Rate.
Programming Procedure:
1) From the Programming Menu, press [1] for PROG TIME. The above window will display. See the following sections
for PROG TIME programming options.
4.2.1 1: AC FAIL DLY
AC FAIL DLY (__)
1: WAIT FOR DC
2: WAIT DLY TIME
Programming Key Sequence: [0]-PROGRAM, [2]-PROG TIMERS, [1]-AC FAIL DLY
Description: This feature sets the number of hours the MDACT will wait after an AC failure is signaled before sending
an AC Failure report.
4.2.1.1 1: WAIT FOR DC
Programming Key Sequence: [0]-PROGRAM, [2]-PROG TIMERS, [1]-AC FAIL DLY, [1]-WAIT FOR DC
Description: Two input points must be programmed with one set for AC Fail and the other for Low Battery. Once an AC
Fail signal is received on the AC Fail input, the MDACT will wait for a low battery signal. The “Wait for DC” function
causes the dialer to wait and send the AC FAIL and LOW BATT reports simultaneously. The current setting is displayed
in parentheses on the first line.
Note: If a Low Battery input activates followed by an AC Fail input activating, the AC Fail report is sent immediately.
Programming Procedure:
1) Press [1] if you want to WAIT for DC followed by [#/Command]. The setting in parentheses will reflect the setting.
2) After you have programmed WAIT for DC, press the [*/Clear] key to return to the PROG TIMERS submenu.

MDACT Programming Manual Page 27

Programming
4.2.1.2 2: WAIT DLY TIME
Programming Key Sequence: [0]-PROGRAM, [2]-PROG TIMERS, [1]-AC FAIL DLY, [2]-WAIT DLY TIME
Description: WAIT DLY TIME allows you to select how long to wait after an AC Fail signal is received before reporting
the event over the phone line.
Refer to NFPA 72 Section 1-5.8.6.3 “The primary power failure trouble signal for the DACT shall not be transmitted until
the actual battery capacity is depleted by at least 25 percent, but by not more than 50 percent” when determining the
WAIT DLY TIME.
Note: Anytime AC Fail and Low Battery events are both present, the AC Fail event is reported regardless of any wait time.
Note: Programming “WAIT DLY TIME” for “00” will allow the MDACT to send an AC Fail report without any delay.
Programming Procedure:
1) From the AC FAIL DLY submenu, press [2] for WAIT DLY TIME followed by [#/Command]. The following window
will appear:
AC FAIL DLY (__)
(00-24 HRS): _____
2) The current setting is displayed in parentheses on the first line. Enter the time and press the [#/Command] key.
3) After you have programmed the WAIT DLY TIME option, press the [*/Clear] key to return to the PROG TIMERS
submenu.
4.2.2 2: DISPLAY RATE
Programming Key Sequence: [0]-PROGRAM, [2]-PROG TIMERS, [2]-DISPLAY RATE
Description: This feature allows you to set the speed at which the lines of the menus are updated on the LCD (in units
of ¼ sec.).
Programming Procedure:
1) From the PROG TIMERS submenu, press [2] for DISPLAY RATE. The following window will appear:
DSPLY RATE (__)
.25 X (1-16): _____
2) The current setting is displayed in parentheses on the first line. Enter the desired value and press the [#/Command]
key.
3) After you have programmed the display rate, press the [*/Clear] key to return to the PROG TIMERS submenu.
4.3 Program Inputs
POINT NUMBER
(1-5): ___
Description: This feature allows you to program the five available inputs.
Programming Procedure:
1) Enter the point number you wish to program and press the [#/Command] key. Once you have entered the point
number, the display will scroll through the following PROG INPUT options:
PROG POINT (___)
1: CONFIGURE
2: SUPERVISED
Press the number key that corresponds to your selection.
Pressing the [Drill] button will send you to the next point. For example, if you are programming Point 2 and you press
[Drill], you will be sent to the setting for Point 3.
Pressing the [Disable] button will return you to the previous point. For example, if you are programming Point 2 and you
press [Disable], you will be sent to the setting for Point 1.

Page 28 MDACT Programming Manual

 Programming
4.3.1 1: CONFIGURE
Note: The Configure Menu is not applicable to MDACT operation.
ACTVTN TYPE (___)
1: FIRE N/A
2: WATERFLOW N/A
3: SUPERVISORY N/A
4: MONITOR N/A
5: SYS FAULT N/A
6: AC FAILURE N/A
7: LOW BATTERY N/A

Note: Press the [*/Clear] key to return to the PROG INPUTS submenu.

4.3.2 2: SUPERVISED
Programming Key Sequence: [0]-PROGRAM, [3]-PROG INPUTS, [2]-SUPERVISED
Description: This option enables supervision for the connection between the five inputs and the FACP.

Programming Procedure:
1) From the PROG INPUTS submenu, press [2] to select SUPERVISED. The following window will appear:
SUPERVISED? (___) ALL INPUTS MUST BE SET TO NO (0)
NO: YES (1)/NO (0)
The parentheses on the first line indicate the point that is currently being programmed. The current setting for the
SUPERVISED option is displayed at the beginning of the second line.
2) Press the number key that corresponds to your selection. To confirm your selection, press the [#/Command] key.
3) To return to the PROG INPUTS submneu, press the [*/Clear] key.
Note: An input configured for System Fault is always supervised and cannot be changed.
4.4 PROG RELAY
RELAY (______)
1: RELEAS ON TRBL N/A
2: ACTIV GND STRT N/A
Note: Press the [*/Clear] key to return to the Programming Menu.

MDACT Programming Manual Page 29

Programming

4.5 PROG ACC’NTS

PROG ACC’NTS
1: ACCOUNT NUMS
2: PHONE NUMS
3: PHONE CONTROL
4: RPT STEERING
5: LINE CONTROL
6: ACK WAIT TIME
Description: This feature allows you to program parameters for event reporting.
Programming Procedure:
1) From the Programming Menu, press [5] to select PROG ACC’NTS.
2) Press the number key that corresponds to your selection. See the following sections for account programming
information.
4.5.1 1: ACCOUNT NUMBERS
Programming Key Sequence:[0]-PROGRAM, [5]-PROG ACC’NTS, [1]-ACCOUNT NUMS
Description: The account numbers identify the MDACT when it reports to the central station.
Programming Procedure:
1) From the PROG ACC’NTS submenu, press [1] for ACCOUNT NUMS. The following window will display:
ACCOUNT NUMS
1: NUMBER 1
2: NUMBER 2
2) Press the number that corresponds with the account number you wish to set. The following window will then
display:
ACCOUNT #1: 0000
NEW NUMBER: 0000
3) The existing number is shown on the top line. Hexadecimal digits A through F can be accessed for entry by
pressing the [Test] key. Press [1] for A, [2] for B, [3] for C, [4] for D, [5] for E and [6] for F.
4) Enter the new number on the second line and press the [#] key to confirm your entry. Press the [*/Clear] key to
return to the PROG ACC’NTS submenu.
5) Program Account Number 2 using the same procedure.
Note: “0000” is not a valid account number. At least one digit must be non-zero.

Page 30 MDACT Programming Manual

 Programming
4.5.2 2: PHONE NUMS
Programming Key Sequence:[0]-PROGRAM, [5]-PROG ACC’NTS, [2]-PHONE NUMS
Description: The system can be programmed with two reporting phone numbers. Phone Number 1 is used with Account
Number 1; Phone Number 2 is used with Account Number 2. Remote programming occurs on Phone Line 1 using
Phone Number 3.
• PHONE #1: Phone Number 1
• PHONE #2: Phone Number 2
• PHONE #3: Not available at this time (reserved for future use).

For compliance with UL and NFPA standards, both phone numbers must be used.

Programming Procedure:
1) From the PROG ACC’NTS submenu, press [2] for PHONE NUMS. The following window will display:
PHONE NUMS
1- PHONE #1
2- PHONE #2
3- PHONE #3 This item is not currently supported.
2) Press the number key that corresponds with the phone number you wish to configure (example is Phone #1). The
following window will appear:
PHN NMBR 1: ????
????????????????
3) Enter the phone number. Press [Drill] and [Disable] to move between digits. Press the [#/Command] key when
the entry is complete. Press [*/Clear] to return to the PROG ACC’NTS submenu.
Note: Before exiting the Phone Numbers programming submenu, see the following information regarding special control
characters for phone numbers.
Several special control characters can be included in the phone number by pressing the [TEST] key:
PHONE CONTROL CODE
1: * CODE
2: # CODE
3: /3 SEC DELAY
• * CODE: Press the [TEST] key, and then press the [1] key for Touch Tone “*” action.
• # CODE: Press the [TEST] key, and then press the [2] key for Touch Tone “#” action.
• /3 SEC DELAY: Press the [TEST] key, and then press the [3] key for a three-second delay.

MDACT Programming Manual Page 31

Programming
4.5.3 3: PHONE CONTROL
Programming Key Sequence:[0]-PROGRAM, [5]-PROG ACC’NTS, [3]-PHONE CONTROL
Description: There are features associated with each phone number. See below for information on these features.
Programming Procedure:
1) From the PROG ACC’NTS submenu, press [3] for PHONE CONTROL. The following window will display:
PHONE CONTROL
1: PHONE 1 FORMAT
2: PHONE 2 FORMAT
3: PHONE 1 TONE N/A Note: This feature is not supported by the MDACT
4: PHONE 2 TONE N/A and has not been evaluated by UL.
2) Press the number key (1 or 2 for Phone Format) that corresponds with the phone you wish to configure (example
is Phone #1). The following window will appear:
PHONE FORMAT (__)
1: 4/2 REPORT N/A Note: This feature is not supported by the MDACT
2: SIA 110, RPRT and has not been evaluated by UL.
3: CONTACT ID
4: SIA 300, RPRT
3) Press the number key that corresponds to your selection (the current setting is displayed in parentheses on the first
line). Press the [#/Command] key to confirm your selection. Press the [*/Clear] key to return to the PHONE
CONTROL submenu.
4) Use the Phone 1 Format instructions when setting Phone 2 Format.
5) To configure the tone setting, press [3] from the PHONE CONTROL submenu (example is Phone #1). The following
window will appear:
TONE (_____) Acknowledge Tone
1: 19D, 14A, 10PS
2: 18D, 23A, 10PS
XXD, XXA, XXPS
3: 19D, 14A, 20PS
4: 18D, 23A, 20PS Data Frequency Pulses per Second
5: 19D, 14A, 40PS
6: 18D, 23A, 40PS
6) Press the number key that corresponds to your selection (the current setting is displayed in parentheses on the first
line). Press the [#/Command] key to confirm your selection. Press the [*/Clear] key to return to the PHONE
CONTROL submenu. Use the Phone 1 Tone instructions when setting Phone 2 Tone.

Page 32 MDACT Programming Manual

 Programming
4.5.4 4: RPT STEERING
Programming Key Sequence:[0]-PROGRAM, [5]-PROG ACC’NTS, [4]-RPT STEERING
Description: Different classes of reports can be directed to different phone numbers. Non-supervisory alarms include
fire alarms, waterflow alarms and monitor alarms. Supervisory alarms come from points configured as a supervisory
type. Non-supervisory restorals include fire, waterflow and monitor restorals. Supervisory restorals come only from
points configured as a supervisory type. Trouble reports include all point and system troubles and restorals. Tests
include auto tests, manual tests and off-normal at test reports.
Note: See Appendix E for the appropriate routing of each report.
Programming Procedure:
1) From the PROG ACC’NTS submenu, press [4] for RPT STEERING. The following window will display:
REPORT STEERING
1: NONSUP ALRM
2: SUPVSY ALRM
3: ALM RSTR, RST
4: SUPVSY RSTR
5: TESTS
6: TBL, TBL RSTR
2) Press the number key that corresponds to your selection. The following window will display (with varying headings,
depending on your choice. In this example, non-supervisory alarm is selected):
NONSUP ALRM (__)
1- PHONE 1 ONLY
2- PHONE 2 ONLY
3- PHON 1 AND 2
4- PHN 2 BACKUP

• PHONE 1 ONLY: Report sent to Phone #1 only.

• PHONE 2 ONLY: Report sent to Phone #2 only.
• PHONE 1 AND 2: Report sent to Phones #1 and #2.
• PHONE 2 BACKUP: Report sent to Phone #1, then to Phone #2 if Phone #1 fails. The MDACT tries Phone Number
1 first. If it fails, then Phone Number 2 is tried.
3) Press the number key that corresponds with your selection followed by the [#/Command] key. Press the [*/Clear]
key to return to the RPT STEERING submenu.
Note: Report Steering menu choices 2 - 6 will display the same menu options as Report Steering choice #1: NONSUP ALRM.
Use the instructions for NONSUP ALRM when setting Report Steering menu choices 2 - 6.

MDACT Programming Manual Page 33

Programming
4.5.5 5: LINE CONTROL
Programming Key Sequence:[0]-PROGRAM, [5]-PROG ACC’NTS, [5]-LINE CONTROL
Description: This allows you to set the dialing type and line supervision for each phone line.
Programming Procedure:
1) From the PROG ACC’NTS submenu, press [5] for LINE CONTROL. The following window will display:
LINE CONTROL
1: LINE #1
2: LINE #2
2) Press the number key that corresponds with the line you wish to configure (example is Line #1). The following
window will display:
LINE 1 CONTROL
1: DIALING TYPE
2: MONITOR LINE
3: WAIT DIALTONE
Dialing Type: Determines which format the MDACT will use for dialing on each phone line. Tone/Pulse will first try tone
dialing and then pulse dialing if tone dialing fails.
Monitor Line: Supervises phone line integrity.
Note: For UL installations, both phone lines must be used, enabled and supervised.
Wait Dialtone: If set to YES, the MDACT starts dialing when it receives a dial tone. If set to NO, the MDACT waits seven
seconds before dialing.
3) Press [1] for DIALING TYPE. The following window will display:
DIAL #1 (_____)
1: PULSE ONLY
2: TONE/PULSE
3: TONE ONLY
4) Press the number key that corresponds with your selection followed by the [#/Command] key. Press the [*/Clear]
key to return to the LINE CONTROL submenu.
5) From the LINE CONTROL submenu, press [2] for MONITOR LINE. The following window will display:
MONITOR LINE #1
YES: YES (1)/NO (0)
6) The current selection precedes the colon (:) on the second line. Press the number key that corresponds with your
selection followed by the [#/Command] key. Press the [*/Clear] key to return to the LINE CONTROL submenu.
7) From the LINE CONTROL submenu, press [3] for WAIT DIALTONE. The following window will display:
WAIT DIALTONE #1
YES: YES (1)/NO (0)
8) The current selection precedes the colon (:) on the second line. Press the number key that corresponds with your
selection followed by the [#/Command] key. Press the [*/Clear] key to return to the LINE CONTROL submenu.
Use these steps when configuring Line #2.

Page 34 MDACT Programming Manual

 Programming
4.5.6 6: ACK WAIT TIME
Programming Key Sequence:[0]-PROGRAM, [5]-PROG ACC’NTS, [6]-ACK WAIT TIME
Description: After the MDACT dials the phone number, it waits for the receiver to answer the phone and send the
proper handshake tones. If the handshake is not detected, the MDACT hangs up. This parameter sets how long the
MDACT waits before hanging up.
Programming Procedure:
1) From the PROG ACC’NTS submenu, press [6] for ACK WAIT TIME. The following window will display:
ACK WAIT TIME (___)
(20-90 secs): ___
2) Enter a value between 20 and 90 for the ACK WAIT TIME and then press the [#/Command] key. The default value
is 45 seconds. Press the [*/Clear] key to return to the PROG ACC’NTS menu.
4.6 PROG FORMATS
PROG FORMATS
1: 4/2 POINT RPT N/A Note: This feature is not supported by the MDACT
2: 4/2 RPT CODES N/A and has not been evaluated by UL.
3: SIA SILENC RPT N/A

MDACT Programming Manual Page 35

Programming

4.7 PROG DEFAULTS

PROG DEFLTS
1: CLEAR HISTORY
2: DEFAULT ALL EE
3: DEFLT 4/2 CDES N/A Note: This feature is not supported by the MDACT and has
not been evaluated by UL.
Description: This feature is used to clear the history logger, reset the MDACT to its default EEPROM settings and to
use default reporting codes.
4.7.1 1: CLEAR HISTORY
Programming Key Sequence: [0]-PROGRAM, [7]-PROG DEFLTS, [1]-CLEAR HISTORY
Description: It is possible to clear some or all of the history records in the system using this menu item.
Programming Procedure:
1) From the PROG DEFAULTS submenu, press [1] for CLEAR HISTORY. The following window will display:
HIST ITEMS= _____
DEL OLDEST 000
2) The number on the first line indicates the total number of records stored in the history logger. Enter the number of
history records you wish to delete and press the [#/Command] key. The number of events are erased and the
MDACT returns to the PROG DEFAULTS menu.
4.7.2 2: DEFAULT ALL EE
Programming Key Sequence: [0]-PROGRAM, [7]-PROG DEFLTS, [2]-DEFAULT ALL EE
Description: It is possible to set the MDACT back to the original factory programming configuration with this option.

All programming, including point configurations and option selections, will be lost when this operation is

performed.

Note: Date/Time settings are not affected when defaulting the MDACT.
Programming Procedure:
1) From the PROG DEFAULTS submenu, press [2] for DEFAULT ALL EE. The following window will display:
DEFAULT EE?
NO: YES (1)/NO (0)
2) The entry preceding the colon (:) on the second line indicates the current setting. To restore the MDACT to its
factory settings, press [1] followed by [#/Command]. When the [*/Clear] key is pressed, the following window will
display:
SETTING EEPROM
TO DEFAULT...

When the operation is complete, the PROG DEFAULTS submenu will reappear.

Page 36 MDACT Programming Manual

 Programming

4.8 SLAVE CONNECTN

SLAVE CONNECTN
1: BUS ADDRESS
2: SUPERVISE BUS
4.8.1 1: BUS ADDRESS
Shortcut: [8]-SLAVE CONNECTN, [1]-BUS ADDRESS
Description: This feature sets the dialer bus address.
Programming Procedure:
1) From the SLAV CONNECTN submenu, press [1] for BUS ADDRESS. The following window will display:
BUS ADDRESS (_____)
NEW ADDRESS:
2) The current setting is displayed in parantheses on the first line. Enter in the desired setting on the second line and
press the [#] key. To return to the SLAVE CONNECTN submenu, press the [*/Clear] key.
4.8.2 2: SUPERVISE BUS
Shortcut: [8]-SLAVE CONNECTN, [2]-SUPERVISE BUS
Programming Key Sequence: [0]-PROGRAM, [7]-PROG DEFLTS, [2]-DEFAULT ALL EE
Description: This feature enables the dialer bus supervision.
Programming Procedure:
1) From the SLAV CONNECTN submenu, press [2] for SUPERVISE BUS. The following window will display:
SUPERVISE BUS
NO:YES (1)/NO (0)
2) The current setting is displayed in preceding the colon (:) on the second line. Press the number key that corresponds
with your selection followed by the the [#] key. To return to the SLAVE CONNECTN submenu, press the [*/Clear]
key.

MDACT Programming Manual Page 37

Programming

This page is intentionally blank.

Page 38 MDACT Programming Manual

 Appendix A

Appendix A: MDACT Troubleshooting

The following troubleshooting section is not intended for use as an acceptance testing procedure. The following
information is provided as a general guide to determine, recognize and resolve a system problem upon installation,
maintenance and during normal standby.
MDACT Onboard LEDs
The dialer portion of the MDACT has four onboard LEDs that indicate various system conditions.
• LINE 1 LED: This LED will blink if a report is being sent out on Line 1. If a line fault condition occurs on Line 1, this
LED will be steady-on in conjunction with the SYS TROUBLE LED. Check for the following if the Line 1 LED is
steady-on:
1) Use a voltmeter to measure the voltage present across each phone line (Tip to Ring) while the phone line is idle.

The voltage present during ringing for an incoming call can be over 100 VAC.

• The standby telco “battery” voltage is typically in the range of 30 VDC to 50 VDC, but any voltage over 6 VDC
will be accepted by the MDACT.
• The polarity of the voltage does not matter.
2) Check for other devices that may use the phone line, such as fax machines, credit card verifiers or PBX systems.
• NFPA 72 requires a dedicated phone line for fire reporting.
• If the devices sharing the phone line cannot be removed, make sure they are wired so that the MDACT’s line
seizure relay will disconnect them when needed.
• Measure the line voltage while these devices are in use. Make sure that it remains above 6 V.
3) Check for intermittent faults on the phone line.
• Make a test call and see that the line is free of distortion and noise.
• Temporarily swap Lines 1 and 2 on the MDACT and see if the problem indication moves to the MDACT’s
other phone line channel, in which case the phone line is causing the problem rather than the line monitor.
• Confirm that the fault message is “PHONE FAULT” and not “COMM FAULT.”
• If only one phone number is available for reporting, set report steering for all events to “PHONE 1 ONLY.”
• “COMM FAULT” may also be caused if one of the phone lines has telco battery voltage, but will not complete
a call. Make test calls to the receiver(s) on both phone lines, listening for the receiver ACK tone.
4) Make sure that two phone lines are available.
• NFPA 72 requires that the auto test report be sent on a different phone line each time it is sent. If only one
phone line is connected to the MDACT, a “COMM FAULT” will be generated on every other test call.
• LINE 2 LED: This LED will blink if a report is being sent out on Line 2. If a line fault condition occurs on Line 2, this
LED will be steady-on in conjunction with the System Trouble LED. If the LINE 2 LED is steady-on, see the four steps
listed above for LINE 1 LED.
• HEARTBEAT LED: This LED will blink if the MDACT is functioning properly. This LED will not light at all if the MDACT
is not functioning properly. If this is the case, check the following:
• Check the MDACT’s main power. Be sure that the factory-connected interconnect ribbon cable between the two
boards has not been dislodged.

MDACT Programming Manual Page 39

Appendix A
• SYS TROUBLE LED: This LED is off if the MDACT is operating properly. It will be steady-on for any MDACT system
trouble. It also operates in conjunction with the MDACT’s onboard trouble relay. Depending on the number of times
the SYS TROUBLE LED blinks, a different trouble condition is indicated. See Table 3.

Number of Blinks Trouble Condition Indicated Description of Trouble Condition

The internal RAM has failed. May occur at any time. When this
problem occurs, the MDACT w ill continuously cycle through its
2 Internal RAM Test Failure start-up routine. Each time the start-up routine occurs, the SY S
TROUBLE LED w ill blink tw o times. Contact Siemens Building
Technologies Technical Support at (800) 248-7976 immediately.

The external RAM has failed. May occur at any time. When this
problem occurs, the MDACT w ill continuously cycle through its
3 External RAM Test Failure start-up routine. Each time the start-up routine occurs, the SY S
TROUBLE LED w ill blink three times. Contact Siemens Building
TechnologiesTechnical Support at (800) 248-7976 immediately.

The ROM checksum has failed. May occur at any time. When this
problem occurs, the MDACT w ill continuously cycle through its
4 ROM Checksum Failure start-up routine. Each time the start-up routine occurs, the SY S
TROUBLE LED w ill blink four times. Contact Siemens Building
Technologies Technical Support at (800) 248-7976 immediately.

An EEPROM test is performed every 10 minutes. If the checksum

fails, the MDACT w ill automatically default. The SY S TROUBLE
LED w ill be lit and "trouble Programming" w ill appear on the
5 EEPROM Checksum Failure
keypad. All configuration settings must be reprogrammed. If this
reoccurs often, contact Siemens Building Technologies Technical
Support at (800) 248-7976 immediately.
Table 3: SYS TROUBLE LED Indications
Note: The MDACT considers the connection of the DCT-P Keypad as an off-normal condition.

Manual Test Report Failure

If the MDACT fails to send the Manual Test report in two attempts, or the [*/Clear] key is pressed, the report transmission
is aborted. A COMM FAULT message, however, is not sent. The DCT-P Keypad emits a three-beep tone and displays
the following message, “COMMUNICATOR FAILED.” After two seconds, the keypad display is updated to show the
following message, “CLEARING ALL REPORTS!!” Any report, including the Manual Test report, in the report queue is
deleted. After two seconds, the rotating Test Menu is displayed.
Reports in Queue
If there are any reports in the queue, the DCT-P Keypad displays the following message, “REPORTS IN QUEUE
PLEASE WAIT.” The MDACT then waits for these reports to be sent. If the [*/Clear] key is pressed on the DCT-P
Keypad, the wait is terminated, the DCT-P Keypad emits a three-beep tone and the keypad’s LCD display shows the
following message, “ERROR DURING COMM TEST.” The rotating Test Menu will return to the keypad’s LCD display
after displaying the message for two seconds.
When the report queue is empty, the MDACT prompts the user to select the phone line to be used (Line 1 or Line 2) or
to alternate the phone lines (see Section 1.3.4.1 TEST COMM for more information). If the third option, Alternate, is
selected, the phone line is switched from the phone line used in the last Manual Test report, regardless of whether it was
specified by line number or by Alternate. Pressing the [*/Clear] key instead of a selection key causes the phone line to
alternate. Sending an Auto Test does not affect the phone line sequence of the Manual Test report. When the line
selection is complete, the Manual Test report is inserted in the report queue.
If the report queue is currently full of reports to be sent, a “DATA LOST” report is sent unless one is already in the queue.
If this is the case, then the Manual Test report is not sent. The Manual Test report is inserted in the History Log
regardless of whether or not the report was added to the report queue.
“ERROR DURING COMM TEST” Message
When a Manual Test is requested, the MDACT checks to see that at least one phone line is good. If this condition is not
met, the DCT-P Keypad emits a three-beep tone and displays the following message, “ERROR DURING COMM TEST.”
The rotating Test Menu will return to the keypad’s LCD display after displaying the message for two seconds.

Page 40 MDACT Programming Manual

 Appendix B

Appendix B: Compatibilities
The following receivers and panels have been proven to be compatible with the MDACT under the method required by
Underwriters Laboratories. Receivers that are not listed as compatible should not be used with the MDACT.

Available Reporting Formats

• Contact ID (CID): Is the preferred reporting format. It provides a four digit account code followed by a three digit event
code, a two digit group number, and a three digit contact number, all of which are used to provide specific point
identification.
• SIA: Security Industry Association (SIA) Digital Communication Standard. The DACT provides level 1 compatibility
which includes tonal acknowledge, basic reports only, and fixed reporting codes.

Compatible Receivers (q = Available)

Osborne/Hoffman Silent
Report Radionics Radionics Sur-gard Ademco
Quick Alert Model Knight
Format D6500 D6600 SG-SLR 685
II SK9000

Contact ID q q q q q
SIA 300 q q q
SIA 110 q q q

Table 4: MDACT UL Listed Compatibility

MDACT Programming Manual Page 41

Appendix B

This page is intentionally blank.

Page 42 MDACT Programming Manual

 Appendix C

Appendix C: Reporting Summary for Fire Communicator

POINT-RELEAT ED EVENT S

Report SIA Contact ID Contact ID

SIA Code
Description Description Code Description

Point Fire Alarm FA pppp Fire Alarm 1 110 aa ppp Fire Alarm

Point Waterflow Alarm SA pppp Sprinkler Alarm 1 113 aa ppp Waterflow

Point Supervisory Alarm SS pppp Sprinkler Supervisory 1 200 aa ppp Fire Supervisory

Point Monitor Alarm UA pppp Untyped Zone Alarm 1 140 aa ppp General Alarm

Point Fire Trouble FT pppp Fire Trouble 1 373 aa ppp Fire Trouble

Point Waterflow Trouble ST pppp Sprinkler Trouble 1 373 aa ppp Fire Trouble

Point Supervisory Trouble ST pppp Sprinkler Trouble 1 373 aa ppp Fire Trouble

Point Monitor Trouble UT pppp Untyped Zone Trouble 1 373 aa ppp Fire Trouble

Point Fire Alarm Restore FR pppp Fire Restoral 3 110 aa ppp Fire Alarm

Point Waterflow Restore SH pppp Sprinkler Alarm Restore 3 113 aa ppp Waterflow

Point Supervisory Restore SR pppp Sprinkler Restoral 3 200 aa ppp Fire Supervisory

Point Monitor Restore UR pppp Untyped Zone Restoral 3 140 aa ppp General Alarm

Point Fire Trouble Restore FJ pppp Fire Trouble Restore 3 373 aa ppp Fire Trouble

Point Waterflow Trouble Restore SJ pppp Sprinkler Trouble Restore 3 373 aa ppp Fire Trouble
Point Supervisory Trouble
SJ pppp Sprinkler Trouble Restore 3 373 aa ppp Fire Trouble
Restore
Point Monitor Trouble Restore UJ pppp Untyped Trouble Restore 3 373 aa ppp Fire Trouble

Notes:
• Some codes are used for more than one event type.
• For SIA, no area is reported.
• For Contact ID, the area is 0.
• The point is reported as Points 1-5 corresponding to the five inputs.
• ppp, pppp: point number (SIA can be 1-4 digits)
• a, aa, aaaa: area number (SIA can be 1-4 digits)
• iii, iiii: user ID (SIA can be 1-4 digits)
• nn, nnn, nnnn: condition parameter (SIA can be 1-4 digits)

MDACT Programming Manual Page 43

Appendix C

N ON -POIN T-R ELEATED EVEN TS

R eport SIA SIA C ontact ID C ontact ID

D escription C ode D escription C ode D escription

Open Reset OR i i i D i sarm From Alarm 1 401 aa i i i O/C By User

Low Battery YT System Battery Trouble 1 302 aa 000 Low System Battery

Low Battery Restore YR System Battery Restoral 3 302 aa 000 Low System Battery

A C F ai l AT AC Trouble 1 301 aa 000 A C L o ss

AC Fai l Restore AR AC Restoral 3 301 aa 000 A C L o ss

Auto Test RP Automati c Test 1 602 aa 000 Peri odi c Test Report

Off Normal At Test YX Servi ce Requi red 6 300 aa 000 System Trouble

Phone 1 Trouble LT 1 Phone Li ne Trouble 1 351 aa 000 Telco 1 Fault

Phone 1 Restore LR 1 Phone Li ne Restoral 3 351 aa 000 Telco 1 Fault

Phone 2 Trouble LT 2 Phone Li ne Trouble 1 352 aa 000 Telco 2 Fault

Phone 2 Restore LR 2 Phone Li ne Restoral 3 352 aa 000 Telco 2 Fault

Manual Test RX Manual Test 1 601 aa 000 Manual Tri gger Test

D ata Lost RT D ata Lost 1 354 aa 000 Fai l to C ommuni cate

EEPROM Fai lure IA 4 Equi pment Fai lure C ondi ti on 1 307 aa 000 Self-test Fai lure

Trouble Input IA 2 Equi pment Fai lure C ondi ti on 1 300 aa 002 System Trouble

Trouble Input Restore IR 2 Equi pment Fai l - Restoral 3 300 aa 002 System Trouble

System Trouble Keypad IA 5 Equi pment Fai lure C ondi ti on 1 300 aa 005 System Trouble

System Restore Keypad IR 5 Equi pment Fai l - Restoral 3 300 aa 005 System Trouble

System Trouble C omm Fault IA 6 Equi pment Fai lure C ondi ti on 1 300 aa 006 System Trouble

System Restore C omm Fault IR 6 Equi pment Fai l - Restoral 3 300 aa 006 System Trouble

System Trouble Programmi ng IA 11 Equi pment Fai lure C ondi ti on 1 300 aa 011 System Trouble

System Restore Programmi ng IR 11 Equi pment Fai l - Restoral 3 300 aa 011 System Trouble

Notes:
• Some codes are used for more than one event type.
• For SIA, no area is reported.
• For Contact ID, the area is 0.
• The point is reported as Points 1-5 corresponding to the five inputs.
• ppp, pppp: point number (SIA can be 1-4 digits)
• a, aa, aaaa: area number (SIA can be 1-4 digits)
• iii, iiii: user ID (SIA can be 1-4 digits)
• nn, nnn, nnnn: condition parameter (SIA can be 1-4 digits)

Page 44 MDACT Programming Manual

 Appendix D

Appendix D: Programming Defaults List

The following is a list of all the programming defaults for the MDACT. Use the MDACT Program Record
Sheet (P/N 315-099365) to record programming entries.
Program Time
• System Date*: 01 01 00
• System Time*: 0000
* Once the user has entered the system date and
time, defaulting the MDACT will not reset the system
date and time. Time is not stored and will be lost on
power failure.
Auto Test
• Auto Test Time: 0400
• Auto Test Frequency: 24 hrs
Daylight Savings: NO
Timers
• AC Fail Delay: 6 hrs
• Display Rate: 1 second
Program Inputs (Configure)
• Point 1: N/A
• Point 2: N/A
• Point 3: N/A
• Point 4: N/A
• Point 5: N/A
Program Inputs (Supervised)
• Point 1: NO
• Point 2: NO
• Point 3: NO
• Point 4: NO
• Point 5: NO
Configure Relay: N/A
Program Accounts
• Account #1: 1234
• Account #2: 2345
Phone Numbers
• Phone #1: 1234567
• Phone #2: 2345678
Phone Control
• Phone #1 Format: SIA 300
• Phone #2 Format: SIA 300
• Phone #1 Tone: 19D, 14A, 10PS
• Phone #2 Tone: 19D, 14A, 10PS
Report Steering
• Non-SUP Alarm: Phone 2 Backup
• Supervisory Alarm: Phone 2 Backup
• Alarm Restor, Reset: Phone 2 Backup
• Supervisory Restore: Phone 2 Backup
• Tests: Phone 2 Backup
• Trbl, Trbl Restore: Phone 2 Backup

MDACT Programming Manual Page 45

Appendix D

Line Control
• Line 1 Dialing Type: Tone/Pulse
• Line 2 Dialing Type: Tone/Pulse
• Line 1 Monitor Line: YES
• Line 2 Monitor Line: YES
• Line 1 Wait Dial Tone: YES
• Line 2 Wait Dial Tone: YES
ACK WAIT TIME: 45 seconds
Program Formats (4/2 Point Rpt) N/A Note: This feature is not supported by the
• Fire Alarm Digit 1: 0 N/A MDACT and has not been evaluated
by UL.
• Fire Rstrl Digit 1: 3 N/A
• Waterflow Digit 1: 0 N/A
• Supervise Digit 1: 0 N/A
• Trouble Digit 1: 6 N/A
• Trbl Rstrl Digit 1: 3 N/A
• Monitor Digit 1: 0 N/A
• Zone 1 Digit 1: 1 N/A
• Zone 2 Digit 1: 2 N/A
• Zone 3 Digit 1: 3 N/A
• Zone 4 Digit 1: 4 N/A
• Zone 5 Digit 1: 5 N/A
Program Formats (4/2 Rpt Codes Group 1) N/A Note: This feature is not supported by the
• Open Reset: 9F N/A MDACT and has not been evaluated
by UL.
• Low Batt: F9 N/A
• Low Batt Rstrl: E9 N/A
• AC Fail: F8 N/A
Program Formats (4/2 Rpt Codes Group 2) N/A Note: This feature is not supported by the
• AC Fail Rst: E8 N/A MDACT and has not been evaluated
• Auto Tst Rpt: EE by UL.
N/A
• Off Norm Tst: FD N/A
• Phone 1 Trbl: FB N/A
• Phone 1 Trbl Rstrl: EB N/A
• Phone 2 Trbl: FC N/A
• Phone 2 Trbl Rstrl: EC N/A
Program Formats (4/2 Rpt Codes Group 3) N/A Note: This feature is not supported by the
• Man Tst Rpt: FE N/A MDACT and has not been evaluated
by UL.
• Data Lost: FF N/A
• EEPROM Fail: FD N/A
• Trbl Input Rpt: FD N/A
Program Formats (4/2 Rpt Codes Group 4) N/A Note: This feature is not supported by the
• Trbl Input Rtrl: ED N/A MDACT and has not been evaluated
by UL.
• Analog Servc: FD N/A
Program Formats (4/2 Rpt Codes Group 5) N/A Note: This feature is not supported by the
• Rmt Prg Fail: FD N/A MDACT and has not been evaluated
by UL.
Slave Connection
• Bus Address: 133
• Supervise Bus: YES

Page 46 MDACT Programming Manual

 Appendix E

Appendix E: Report Routing

The information in Appendix E shows the mapping of point-related and non-point-related events to their respective
report routing group, lists the priority level of each event and identifies the reporting limit for specific types of events.

POINT-RELATED EVENTS

Report Description Report Routing Report Priority

Point Fire Alarm NONSUP ALRM 0

Point Waterflow Alarm NONSUP ALRM 0

Point Supervisory Alarm SUPVSY ALRM 3

Point Monitor Alarm NONSUP ALRM 3

Point Fire Trouble* TBL, TBL RSTR 3

Point Waterflow Trouble* TBL, TBL RSTR 3

Point Supervisory Trouble* TBL, TBL RSTR 3

Point Monitor Trouble* TBL, TBL RSTR 3

Point Fire Alarm Restore ALM RSTR, RST 4

Point Waterflow Restore ALM RSTR, RST 4

Point Supervisory Restore SUPVSY RSTR 4

Point Monitor Restore ALM RSTR, RST 4

Point Fire Trouble Restore* TBL, TBL RSTR 4

Point Waterflow Trouble Restore* TBL, TBL RSTR 4

Point Supervisory Trouble Restore* TBL, TBL RSTR 4

Point Monitor Trouble Restore* TBL, TBL RSTR 4

* These events will be limited to a total of 100 reports sent out in a 24-hour period. If this limit is exceeded, the 100th
event will be replaced with a DATA LOST report.

MDACT Programming Manual Page 47

Appendix E

NON-POINT-RELATED EVENTS

Report Description Report Routing Report Priority

Open Reset ALM RSTR, RST 4

Low Battery* TBL, TBL RSTR 3

Low Battery Restore* TBL, TBL RSTR 3

AC Fail* TBL, TBL RSTR 3

AC Fail Restore* TBL, TBL RSTR 3

Auto Test TESTS 4

Off Normal At Test TESTS 4

Phone 1 Trouble* TBL, TBL RSTR 3

Phone 2 Trouble* TBL, TBL RSTR 3

Phone 2 Trouble* TBL, TBL RSTR 3

Phone 2 Restore* TBL, TBL RSTR 3

Manual Test‡ TESTS 4

Data Lost TBL, TBL RSTR 6

EEPROM Failure* TBL, TBL RSTR 3

Trouble Input* TBL, TBL RSTR 3

Trouble Input Restore* TBL, TBL RSTR 3

SystemTrouble Keypad* TBL, TBL RSTR 3

System Restore Keypad* TBL, TBL RSTR 3

System Trouble Comm Fault* TBL, TBL RSTR 3

System Restore Comm Fault* TBL, TBL RSTR 3

System Trouble Programming* TBL, TBL RSTR 3

System Restore Programming* TBL, TBL RSTR 3

* These events will be limited to a total of 100 reports sent out in a 24-hour period. If this limit is exceeded, the 100th
event will be replaced with a DATA LOST report.
‡
Resets count of limited reports and 100 additional reports can be sent.

Page 48 MDACT Programming Manual

 Index

Index
A M R
AC Fail Delay 27 Modes of Operation 13 Report Steering 33
Wait Delay Time 28 Phone 1 and 2 33
Wait for DC 27 P Phone 1 Only 33
Account Numbers 30 Phone 2 Backup 33
Phone 1 and 2 33
Account Programming 30 Phone 2 Only 33
Phone 1 Only 33
Auto Test 26 Reports
Phone 2 Backup 33 Comm Fault 7
Auto Test Frequency 26
Phone 2 Only 33 Data Lost 7
Auto Test Time 26
Phone Control 32 Reset 15
C Phone Line Selection 5
Phone Number Selection 5
S
Call Routing 6 Phone Numbers 31 Scrolling Menus 11
Clear History 36 Program Accounts 30 Selecting Menu Items 11
Communication Fault 7 Program Defaults Shared Keys 11
Communicator Operation 5 Clear History 36, 37 Slave Connctn 37
Compatibilities 41 Default EE 36, 37
Sub-menu Items 12
Connections Program Formats 35
Keypad 19 Program Inputs 28
Configuration 29 T
D Supervised 28
Program Menu Tree 21 Telephone Line Supervision 6
Date 25
Program Relay 28 Time 25
Daylight Savings Time 27
Default EE 36 Program Time 25
U
Display Rate 28 Program Timers 27
AC Fail Delay 27 Understanding the DCT-P LCD Remote
E Display Rate 28 Keypad 9
Programming 25
Exclusive Keys 11 Account Numbers 30 W
Accounts 30
F Wait Delay Time 28
Clear History 36
Date 25 Wait for DC 27
Factory Default Settings 36
Default EE 36
I Keypad 17
Line Control 34
Inputs Phone Control 32
Programming 28 Phone Numbers 31
Configuration 29 Program Defaults 36
Supervised 29 Program Formats 35
Report Steering 33
K Shortcuts 17
Level 1 17
Keypad Programming 17
Level 2 17
L Level 3 17
Level 4 17
Limited Reports 7 Slave Connctn 37
Line Control 34 Time 25
Lost Data 7 Timers 27
Programming Defaults 36

MDACT Programming Manual Page 49

Siemens Building Technologies, Inc. Siemens Building Technologies, Ltd.
8 Fernwood Road 2 Kenview Boulevard
Florham Park, New Jersey 07932 Brampton, Ontario L6T 5E4 CN

P/N 315-099378-2