Table of Contents
Advertisement
Kidde Gemini II System
municating with a device which has been de-regis-
tered but still connected. In this case, the MCP will
send a message to the device causing it to remain
de-registered.
5. The MCP sends a message to all devices requesting
them to re-send their events (alarms, supervisory and
troubles). The devices will send any events that they
have stored in their "Local Active Event Lists" when
they are later polled by the MCP. These events are
added to the MCP's "System Active Event List" and
stored in the "System Event Log."
If an RHU is reset the following happens:
1. The RHU sends a message informing the MCP that it
has reset. This is recorded in the MCP "System Event
Log."
2. The MCP clears its "System Active Event List" of any
alarms, supervisory or trouble events that were cre-
ated by the RHU which has been reset.
3. The RHU clears its own "Local Active Event List."
4. The RHU generates any alarm, supervisory or trouble
event that it detects. These events are reported to the
MCP as the MCP subsequently polls the RHU for its
status. They are added to the MCP's "System Active
Event List" and stored in the MCP "System Event Log."
Each RHU has a RESET button on its Display Panel. Press-
ing and holding this button for more than one second will
cause the RHU to reset. The sequence of actions that oc-
cur are the same as shown above, when the RHU is reset
using the RESET button on the MCP.
At the MCP and RHU, reset is disabled when the unit is in
the period of pre-release delay, when its agent release out-
put is active or if it is in Walk Test. However, if there is an
active abort state for the unit selected for reset, then reset
is active. Reset is also active if the release is selected to be
on-until-reset.
2-12
EVENT MESSAGES
Below is a list of event, alarm and trouble messages and
their meaning.
Messages originate in the Main Control Panel, Remote Haz-
ard Unit or Remote Display Unit.
Event Message
Explanation
24hr resound
An alarm which was acknowledged
and silenced more than 24 hours ago
has activated the buzzer since the con-
dition which caused the alarm still ex-
ists.
24v Low FLT
Low voltage detected on the 24 Vdc
circuit.
Abort event
Abort input received indicating that
someone activated an abort switch.
06-235975-001
Abort IP FLT
Abort IP ISO
Abt. Invalid
AbortIsoFAIL
Alarm IP ISO
ALARM Zone 1
ALARM Zone 2
Alrm Rel ISO
Bat Low FLT
Comms error
Config FAIL
DetIPIsoFAIL
Ground FLT
Hard reset
In Walktest
Isolate FAIL
Man Rel FLT
Man Rel ISO
MANUAL PULL
MRel IsoFAIL
NameTag FAIL
OpRelDatFAIL
Opt RelayFLT
Opt Rels ISO
2-8
firealarmresources.com
Fault on the abort input circuit.
Abort input has been isolated by the
operator.
Abort input was received, but there
was no alarm and therefore release
outputs were not activated.
Abort isolation failed.
Zone detectors have been isolated by
the operator.
Zone 1 detectors activated on initiat-
ing circuit 1.
Zone 2 detectors activated on initiat-
ing circuit 2.
MCP alarm relay has been isolated.
Battery low voltage detected (voltage
is below 18.6 V). Batteries may be
faulty or placed in reversed when in-
stalled. This condition is cleared by
reconnecting to AC main power.
Communications error.
The operator has changed the configu-
ration parameters for a Remote Haz-
ard Unit at the Main Control Panel, but
the Main Control Panel cannot send
the new parameters to the Remote
Hazard Unit.
Detector input isolation failed.
Ground voltage was detected.
CPU Reset
Walk Test in progress
Failure to isolate part of a Remote Dis-
play Unit
Fault on the manual release input
Manual release input has been iso-
lated.
Manual release input was received in-
dicating a manual pull station was ac-
tivated by someone.
Manual release isolation failure.
The operator entered a new name tag,
but it could not be updated.
Failure to update RHU with optional
relay data.
Fault on the optional relay circuit.
Optional relay circuit has been isolated
by the operator.
November 2002
Advertisement
Table of Contents
