PowerSeries Pro Installation Guide
[001] – Installer code
[002] – Master code
[003] – Maintenance code
Access codes are either 4, 6 or 8 digits in length, depending on the setting
of programming section [041]. Duplicate codes are not valid.
Communication paths
The path of communication between the alarm panel and the central station
must be established through either the alarm panel’s on-board Public
Switched Telephone Network (PSTN) connection (Ethernet) or through
the alternate communicator if equipped.
Alternate communicator setup
The alternate communicator is an ethernet or optional cellular
communications device that can be used as a backup to the PSTN
connection or as a primary means of communication between the alarm
panel and the central monitoring station. The alternate communicator
communicates via 2G, 3G, LTE or Ethernet.
The following configuration steps are required to set up the alternate
communicator:
l
Install the optional cellular alternate communicator to the alarm
panel
l
Enroll the alternate cellular communicator with Connect 24 (North
America only)
l
Set the communication path: [300]
l
Enable the alternate communicator: [383] option 3 for Ethernet,
and [383] option 4 for cellular.
l
The Ethernet or Cellular receivers IP and Port: [851]
l
Enable event reporting: [307]/[308]
l
Program communication delay timer: [377]
l
Program DLS access: [401] option 07
Refer to Section 5: Programming for details.
[300] Panel/Receiver Communication Paths
This section is used to select the path of communications between the
alarm system and the central station.
Testing the system
Installer Walk Test
Walk test enables the installer to test the operation of each detector by
tripping zones, causing an actual alarm. Enter section [901] to initiate a
walk test. When a zone is tripped, all system sirens emit a tone to indicate
that the zone is working correctly.
After 15 minutes without zone activity, the walk test terminates
automatically. To manually exit walk test mode, enter [901] again.
Viewing the event buffer
The event buffer contains logs of events that have occurred on the alarm
system beginning with the most recent. The capacity of the event buffer is
scalable and can hold 500/1000 events (depending on panel model) before
rolling over. The buffer displays events according to their time stamp,
beginning with the most recent. The event buffer can be uploaded using
DLS.
Each event displays the time and date, a description of the event, the zone
label, access code number or any other pertinent information. To view the
event buffer, press [*][6][Master Code][*].
Troubleshooting
LCD programmable-message keypad:
l
Press [*][2] followed by access code if required to view a trouble
condition
l
The trouble light flashes and the LCD displays the first trouble
condition
l
Use the arrow keys to scroll through all trouble conditions present
on the system
Note:
When additional information is available for a specific trouble
condition, a [*] is displayed. Press the [*] key to view the additional
information.
[*][2] Trouble Display
This feature is used to view system troubles. If a trouble is present, the
keypad Trouble indicator illuminates and an audible indication is emitted
(two short beeps every 10 seconds, except while in AC failure). Silence
the audible indicator by pressing [#].
Troubles may be viewed while the system is armed or disarmed. The
system may be programmed to show all troubles while armed or only fire
troubles.
The system can be configured to require a user code to view [*][2] system
troubles. See section [023] option 5.
To view trouble conditions:
l
Press [*][2] to enter the Trouble menu.
l
On an LCD keypad, scroll to a trouble type then press [*] to view
the specific trouble. The zone name and trouble condition for each
trouble are displayed on the screen.
Note:
The trouble beeps generated by fire trouble are only silenced after
[*][2]trouble menu is exited. A keypress in the keypad will not silence the
fire trouble beeps. For UL installations, set the value in section [023] bit 5
access code required for [*][2] to enabled.
Table 1-8 : Trouble Indications
Trouble 01
–
Service Required:
[01]
Bell Circuit Trouble: The bell circuit is open
[02]
RF Jam: The HSM2HOSTx has detected an RF Jam condition
[03]
Loss of Clock: System time and date require programming.
[04]
Output 1 Fault: An HSM2204 module has detected an open condition on output
#1.
[05]
Warm Start: Warm restart has occured.
[06]
USB Wi-Fi Connected: USB Wi-Fi adapter is detected
[07]
Power Unit Failure (System): Failure detected with internal power unit.
[08]
Failure detected with internal power unit (HSM3204CX Corbus Repeater)
[09]
Failure detected with internal power unit (HSM3350 3 A Power Supply)
[10]
Overcurrent Trouble: If the total current of the panel internal components and all
outputs exceeds a threshold of 2.1 A for a period longer than 5 minutes, an
overcurrent trouble is generated. When the current goes below a 2.0 A threshold, the
trouble restores. Do not exceed 2A combined between AUX and Corbus.
Note:
Total current does not include bell current or battery charging.
Trouble 02 – Battery Trouble:
[01]
Panel Low Battery Trouble: The battery voltage is low.
[02]
Panel No Battery: No battery connected to alarm controller.
[04]
HSM2204 01 - 04 Low Battery: An HSM2204 has a low battery voltage.
[05]
HSM2204 01 - 04 No Battery: No battery connected to HSM2204.
[07]
HSM2300 01 - 04 Low Battery: An HSM2300 has a low low battery voltage.
[08]
HSM2300 01 - 04 No Battery: No battery connected to HSM2300.
[10]
HSM3204CX Low Battery: A Corbus repeater has a low battery voltage.
[11]
HSM3204CX No Battery: No battery connected to corbus repeater.
[13]
HSM3350 Low Battery 1: A 3 A power supply module has a low battery voltage.
[14]
HSM3350 Low Battery 2: A 3 A power supply module has a low battery voltage.
[15]
HSM3350 No Battery 1: No battery connected to 3A power supply module.
[16]
HSM3350 No Battery 2: No battery connected to 3A power supply module.
- 10 -
