EST3 Installation and Service Manual

Installation

5.30

details, activation of a dialer test signal, etc., are all a part of the information that is downloaded into the nonvolatile memory of the 3-MODCOM by the SDU.

The 3-MODCOM electronically dials receivers in the central monitoring station (CMS) using either pulse or tone dialing, as specified during configuration. The module dials the stored CMS telephone number using the same digits that would be used if a person were dialing from the premises with an ordinary telephone.

Each time the 3-MODCOM sends test messages to the CMS, it indicates whether the system is in a normal or abnormal state.

You can select which system states (such as alarm, trouble, or

monitor) represent an abnormal condition. This prevents the 3-

MODCOM from reporting an abnormal condition when the system is in a state that occurs frequently as part of normal system operation.

There are provisions for programming a periodic test transmission to the CMS station on a one-minute to 45-day basis.

A daily test signal is primarily intended for certified installations, and is mandatory for all fire alarm installations.

The 3-MODCOM sends messages in order of their priority.

Messages may include device and user ID information regarding events, such as openings, closings, alarms, and tamper or trouble events. The module waits for acknowledgement that each message sent has been received. .Where necessary, the 3-

MODCOM can be configured to begin dialing without waiting for a dial tone. This option is used in areas where the telephone line has an absent or erratic dial tone.

Failover operation

You can create dynamic failover operation for 3-MODCOMs.

By dynamic failover we mean that in the event of a communication failure or device trouble, the system switches from accounts on one 3-MODCOM to matching accounts on another 3-MODCOM.

Failover operation results in a system that is resistant to trouble arising from telephone lines, 3-MODCOMs, or the CPU module.

The operation can be limited to a single panel, or can span two or more panels anywhere in a network.

In systems with a single 3-MODCOM you can include a second

3-MODCOM that acts as a redundant unit. In systems with two or more 3-MODCOMs, you can program the system so that the units back up each other, while still handling their normal traffic.

Failover operates by enabling and disabling various accounts defined for the project. On detection of a fault or trouble, project

EST3 Installation and Service Manual

Installation rules disable accounts on the failed 3-MODCOM and enable matching accounts on the backup 3-MODCOM.

When a 3-MODCOM acts as a backup it still provides line supervision. Only the backup accounts are disabled. Further, backup units should conduct their own dialer tests, using unique accounts that identify the 3-MODCOM. Even when not in use, a backup unit should generate a trouble event if it cannot contact the assigned receiver.

Because of the way rules are processed, when the primary

3-MODCOM comes out of trouble, the accounts are automatically switched back to their normal state. Messages already queued for transmission in the backup unit will still be sent, even after backup accounts are disabled. Only new messages will be routed differently. This means that device activation and restoral messages sent to the CMS will still be properly paired.

Failover operation is created by specific configuration and programming steps. These are outlined below.

Configuration requirements

• For each primary 3-MODCOM add (or select) a backup

3-MODCOM in the same panel or in a different panel according to the scope of failover operation you need

• Configure the primary and backup 3-MODCOMs identically except for their labels and the labels of the accounts

• Label the accounts so that it’s easy to recognize the

3-MODCOM in which they are used

• Make sure each 3-MODCOM uses a unique account for dialer tests

Programming requirements

• Create message rules that send identical messages to both accounts

• On system startup, disable the accounts on the backup

3-MODCOM

• On activation of a panel comm fault, line fault, or LRM comm fault, disable the primary accounts and enable the backup accounts

ACDB requirements

Additional steps are required when the project includes reporting to a CMS that requires translation from a Cardholder ID to a cardholder name. In this situation, the ACDB user must enter a

User ID (name) for both CMS Accounts (the primary and backup accounts).

EST3 Installation and Service Manual 5.31