background image

Page 9

Items accessible to Level  II only

ITEM

Number

Access
Level

Menu Category

Menu Label

Description

30

II

Account (#1)

Account ID #1

Assign 4-6 numeric Account ID to be identified with Account #1
monitoring station receiver. 

31

II

Account (#1)

Dial-Prefix #1

(OPTIONAL) Set up-to-8-digits to be first dialed by UDACT when
attempting to call Account #1 monitoring station receiver.

32

II

Account (#1)

Local Number #1

Set up-to-8-digits to be dialed (after Dial-Prefix #1 digits) by UDACT when
attempting to call Account #1 monitoring station receiver.

33

II

Account (#1)

Report Format #1
Default Contact ID

Choose report format (Contact ID or SIA) to be generated by UDACT when
reporting with Account #1 monitoring station receiver.

40

II

Account (#2)

Account ID #2

Assign 4-6 numeric Account ID to be identified with Account #1
monitoring station receiver

41

II

Account (#2)

Dial-Prefix #2

(OPTIONAL) Set up-to-8-digits to be first dialed by UDACT when
attempting to call Account #2 monitoring station receiver.

42

II

Account (#2)

Local Number #2

Set up-to-8-digits to be dialed (after Dial-Prefix #2 digits) by UDACT when
attempting to call Account #2 monitoring station receiver.

43

II

Account (#2)

Report Format #2
Default Contact ID

Choose report format (Contact ID or SIA) to be generated by UDACT when
reporting with Account #2 monitoring station receiver.

50

II

Report Priority

<ALARM> Events

Default is Account 1

Choose which Account # (1 or 2) will be the 

first

 to be 

attempted

 to be

reached by the UDACT, when an ALARM event is to be reported. This is
designated as the “primary

 account and the other will become the

“secondary”. If the UDACT cannot report to the primary, it will then

attempt

 to report to the secondary. This cycle will 

normally

 continue until

the event is eventually sent or the <MAXIMUM Attempts> has been
achieved.

51

II

Report Priority

<TROUBLE> Events
Default is Account 1

Choose which Account # (1 or 2) will be the 

first

 to be 

attempted

 to be

reached by the UDACT, when a TROUBLE event is to be reported. (See
ITEM 50 for a description of the UDACT report-attempt operation).

52

II

Report Priority

<SUPVSRY> Events
Default is Account 1

Choose which Account # (1 or 2) will be the 

first

 to be 

attempted

 to be

reached by the UDACT, when a SUPERVISORY event is to be reported.
(See ITEM 50 for a description of the UDACT report-attempt operation).

53

II

Event Logging

Ignore <SUPVSRY>
Events 
Default is Non-
Addressable Panel

This selection allows the overriding of the “normal’ reporting of the
supervisory events when set to 1.  The UDACT will report supervisory
events when set to 2.  

54

II

Event Logging

Fire Alarm Protocol
Selection

Select FA for CONVENTIONAL Fire Alarm or FX for ADDRESSABLE
Fire Alarm.

55

II

Report Priority

Max. Attempts

Range is 5 to 10,
Default is 6 Attempts 

Set the “normal” upper limit for UDACT attempts (call-attempt pairs) to
report to monitoring station receivers. One  attempt is registered when the
UDACT tries to access 

both (i.e. the pair of)

 “primary” and “secondary”

Accounts #’s. (See ITEM 50 for a description of the UDACT report-attempt
operation). After this count has been exceed, the UDACT will assert the
TROUBLE-SEND signal (and BUZZER) to the connected Fire-Panel. Only
a UDACT power reset will remove this condition.

60

II

Phone Line (1/2)

Dial-type Line 1

Configure Line 1 for DTMF (Tone) or Rotary (Pulse) dialling. 

61

II

Phone Line (1/2)

Dial-type Line 2

Configure Line 2 for DTMF (Tone) or Rotary (Pulse) dialling. 

62

II

Configuration

Reboot UDACT

Reset entire UDACT (configuration is not affected).

63

II

Phone Line(1&2)

Deaf Dialling
Default dial tone(1)

To wait and listen for dial tone select 1 (default) or Ignore Dial Tone for use
with “Mobile Radio Telephone” select 2 

NOTE:  All configurable items have default values assigned by the “Restore-to-Default” operation. All items must have a (non-zero) value assigned

unless specifically identified as OPTIONAL within the table(s) above.

firealarmresources.com

Summary of Contents for UDACT-9000

Page 1: ...UDACT 9000 Digital Communicators Installation and Operation Manual 2001 by Potter Electric Signal Company September 2001 firealarmresources com...

Page 2: ...and Dimensions Page 3 Connections and Settings Page 3 Field Wiring Page 4 Power Up Procedures Page 5 System Configuration and Operation Page 8 Reporting Formats Page 10 Compatible Fire Alarm Control...

Page 3: ...arm Supervisory and Trouble information on two telephone lines when connected to a Potter Fire Alarm Control Panel FACP such as the PFC 9000 The UDACT 9000 continuously supervises the state of each of...

Page 4: ...for Fire Protective Signalling Systems and applicable section of Standard 1635 Digital Alarm Communicator System Units These Communicators comply with the National Fire Protection Association NFPA per...

Page 5: ...he Chassis Earth Ground Mounting Lug and to connect the Earth Ground Wire Lugs from the Main Chassis to the ground screw on the Backbox UDACT 9000 MAIN BOARD There are no user configurable jumpers on...

Page 6: ...the first Telephone Line via the required RJ31X Connector Line 2 Input Tip Ring To the second Telephone Line via the required RJ31X Connector Line 2 Output Tip Ring To an optional Premise Telephone o...

Page 7: ...7 Enter the passcode 2222222 for installer Enter 2 digit ITEM number to configure To scroll down list of items press or to scroll up 8 When you try to enter a 2 digit number the following screen will...

Page 8: ...Alarm Protocol by entering 54 Item number the following screen will appear 1 FA type 2 FX type UDACT type _ Press when done or to cancel Select FX by typing 2 if the Fire Alarm used is a PFC 9000 Sele...

Page 9: ...cator Reporting event Date Time The next screen is Digital Communicator Waiting for KISS Date Time If the screen stays in the Waiting for KISS mode then you should contact our Tech Support otherwise w...

Page 10: ...I II Event Logging Flush all events Terminate any in progress event reporting Remove report pending trigger i e cancel attempts to report queued events and Force event queue FIFO to empty state i e er...

Page 11: ...s Account 1 Choose which Account 1 or 2 will be the first to be attempted to be reached by the UDACT when a TROUBLE event is to be reported See ITEM 50 for a description of the UDACT report attempt op...

Page 12: ...nput circuit number For example Loop 1 address 1 will not report to the Central Station as Circuit 1 These input circuit numbers are unique and within the fire panel are automatically numbered sequent...

Page 13: ...tact Zone Fire Alarm Alarm New event 1 110 0 NNN Zone Fire Alarm restored Alarm Restore 3 110 0 NNN Zone Trouble detected Trouble New event 1 300 0 NNN Zone Trouble restored Trouble Restore 3 300 0 NN...

Page 14: ...arm New event WA NN Waterflow alarm restored Alarm Restore WH NN General Alarm Alarm New event QA NN General Alarm restored Alarm Restore QH NN Indicating Zone Trouble Trouble New event UT NN Indicati...

Page 15: ...P M Transmits user configurable Zoned Alarm Supervisory and Trouble status to a Central Monitoring Station using either Ademco Contact ID or SIA DCS Protocols M User configurable using the CFG 5000 Co...

Page 16: ...ible to repair or replace equipment which has been repaired by others abused improperly installed altered or otherwise misused or damaged in any way Unless previously contracted by Potter Potter will...

Page 17: ...TYPE EQUIVALENT CODE ALARM 1 SUPERVISORY LATCHING 2 SUPERVISORY NON LATCHING 3 WATERFLOW 4 GENERAL ALARM 5 TROUBLE 6 OUTPUT CIRCUIT TYPE SILENCEABLE SIGNAL CIRCUIT 8 NONSILENCEABLE SIGNAL CIRCUIT 9 S...

Page 18: ...____________________ Reporting Format 9 Contact ID 9 SIA ___________________________________________________________________________________________ Account 2 Identification max 6 digits _ _ _ _ _ _ A...

Reviews: