FXUP
- USER MANUAL -
090010932
[email protected]
elmospa.com
6
Examples
(Acknowledgement time: 200 s; Inspection time: 400 s; Short time: 100 s):
Short time is Off:
An alarm event is generated by a non-call-point device from an enabled zone: the countdown starts at 200 s.
A non-call-point device generates another alarm event: the timer keeps going.
The operator presses Evacuate: the countdown starts again from 400 s.
Someone hits a manual call point: outputs immediately activate.
Short time is On:
Someone hits a call point: the countdown starts from 100 s.
The operator presses Evacuate: the countdown starts again from 400 s.
During inspection time, before the countdown reaches 100, a new alarm event is generated: the countdown drops to 100 s.
Short time is On:
An alarm event is generated by a non-call-point device from an enabled zone: the countdown starts at 200 s.
During acknowledgement time, before the timer reaches 100, a new alarm event is generated: the timer drops to 100 s.
The operator presses Evacuate: the countdown starts again from 400 s.
During inspection time, before the countdown reaches 100, a new alarm event is generated: the countdown drops to 100 s.
4.1.4 System events
The Display and Print menus both let you see a list of system events. These events, listed in the
s
ystem
events
table
(
chap
.
7)
, are generated by some conditions such as the following:
• a signal from a loop device (e.g. Gas leak);
• specific events in the usage and programming screens (e.g. Zone disabled or Password access);
• pressing some buttons on the panel (e.g. Sounders alarm, generated by the evacuate procedure);
• a different system event is generated (e.g. Sounders alarm generates a Fire event).
Some specific system events can be used to activate outputs (e.g. by default, the Fire event activates all bell outputs, the
relay 2 output and every output of the loop).
4.2 Main screen
When no system messages are shown, the main screen of the unit shows the date and time,
the 5-digit ID used by GLOBALPRO to identify the unit and the other data shown on the right.
The star in the third row is only shown if some outputs have been manually activated from the
o
utputs
activation
(
chap
. 5.5)
menu.
When this screen is visible, any keypad button except Evacuate and Silence Buzzer lead to a
password request to get into the user menu. Evacuate leads to a password request to activate
the
e
vacuate
pRoceDuRe
(
chap
. 4.5)
.
LU 06/07/15 10:10:24
00000 Cust._Name
Installer_Name__ *
Telephone_Number
4.3 Unit screens system messages
When there are active alarm or fault events, the main screen changes to show some which
loop, address and zone generated those events.
• The first line holds the
loop
L, the
system event
that caused the fault or alarm message
and the involved
zone
.
• The second line contains the name and number of the
address
that generated the event.
• The third line hosts the name of the affected
zone
and the number of the
last chronologically
zone affected by alarms
.
• The last row shows the
total number of alarm affected zones
T and the
current/total
message number
for faults or for alarms. Use -> and <- to browse messages.
L1-DEVICE FAULT Z004
ADDRESS TEXT -A013
ZONE TEXT -Z007
ESC -> <- 02/03
L1-FIRE Z001
ADDRESS TEXT -A003
ZONE TEXT -Z007
ESC ->T004<- 03/07
The existing standards mandate absolute priority for alarm messages, included hiding all other messages while alarm
messages are present. To see these other messages, browse to the
v
ista
»
m
essages
cleaReD
(
chap
. 5.3.1)
menu.
While system message screens are active, press ESC to access the usage and programming menus.
