Kidde Fire Systems VEGA LT TM0081 User Manual
TM0081
Page 49 of 51
Issue 1.01
15. FAULT
DIAGNOSIS
Main Panel Messages
Message
Possible Cause
Action
Fail Safe Alarm
The MBLC card has detected a fire alarm
condition but is unable to transmit the alarm
data to the MCP card. The MBLC operates a
hardwired fail safe line connected to the MCP
to indicate the Fail Safe Alarm.
Note: Under fail safe operation the MBLC
directly operates its own sounder and relay
outputs.
condition but is unable to transmit the alarm
data to the MCP card. The MBLC operates a
hardwired fail safe line connected to the MCP
to indicate the Fail Safe Alarm.
Note: Under fail safe operation the MBLC
directly operates its own sounder and relay
outputs.
Reset the system.
If problem persists contact Technical Help
Line for further information.
If problem persists contact Technical Help
Line for further information.
Logon fault
Device(s) found or lost on the loop(s) that
does not match the previously stored device
database. New devices added or removed
during commissioning. Faulty device, bad
loop connection or faulty loop card.
does not match the previously stored device
database. New devices added or removed
during commissioning. Faulty device, bad
loop connection or faulty loop card.
Replace faulty device or loop card. Check
external loop wiring. Check loop
configuration against as fitted installation
drawings. Refer section 10.4 and 10.5.
external loop wiring. Check loop
configuration against as fitted installation
drawings. Refer section 10.4 and 10.5.
Config fault
The actual devices attached to the detection
loop and logged onto the control panel do not
match the uploaded VIPER site file. OR
Operator has incorrectly changed a device
type in the Viper site file OR has added a
device that has not been logged onto the
detection loop.
loop and logged onto the control panel do not
match the uploaded VIPER site file. OR
Operator has incorrectly changed a device
type in the Viper site file OR has added a
device that has not been logged onto the
detection loop.
Check the Viper site file against the control
panel loop listing. The device types in Viper
should match the actual devices attached to
the detection loop.
panel loop listing. The device types in Viper
should match the actual devices attached to
the detection loop.
BLC * re-init,
Repeater * re-init,
Repeater * re-init,
The MBLC or Repeater panel at the address
* indicated has transmitted a message to the
MCP indicating that it is waiting to be
initialised.
The processor-reset button on the MBLC or
Repeater panel has been pressed.
The software on that MBLC or Repeater
panel has dropped out of program.
* indicated has transmitted a message to the
MCP indicating that it is waiting to be
initialised.
The processor-reset button on the MBLC or
Repeater panel has been pressed.
The software on that MBLC or Repeater
panel has dropped out of program.
Switch off the control panel or repeater
panel and check connections to internal
circuit boards.
panel and check connections to internal
circuit boards.
Repeater *
comms failure
comms failure
The Repeater panel at that address *
indicated is not replying to messages from
the main panel.
Faulty communications device or faulty board
located within the panel.
indicated is not replying to messages from
the main panel.
Faulty communications device or faulty board
located within the panel.
Check communication cable wiring.
Check Repeater panel address switch
settings.
Replace faulty boards.
Check Repeater panel address switch
settings.
Replace faulty boards.
Repeater
Sounder fault
Sounder fault
The Repeater panel has reported a sounder
short or open circuit fault on its external
wiring.
Note: The panel also reports a repeater
sounder fault during communications fault
with the Repeater panel.
short or open circuit fault on its external
wiring.
Note: The panel also reports a repeater
sounder fault during communications fault
with the Repeater panel.
Check sounder circuit wiring.
Check communication cable wiring.
Check communication cable wiring.
Alarm during
autolearn re-learn
loop
autolearn re-learn
loop
During the autolearn process an alarm
occurred on a different detection loop. The
autolearn process was halted and did not
complete successfully.
occurred on a different detection loop. The
autolearn process was halted and did not
complete successfully.
Re-learn the specified detection loop.
Interrupt Fault –
Apollo only
Apollo only
The device alarm interrupt flag has been
raised on a detection loop, which has not
been maintained for enough consecutive
scans to generate an alarm condition. If this
occurs 5 times on the same loop by any
device within a 24 hour period the Interrupt
Fault is raised. Possible cause noise induced
on detection loop.
raised on a detection loop, which has not
been maintained for enough consecutive
scans to generate an alarm condition. If this
occurs 5 times on the same loop by any
device within a 24 hour period the Interrupt
Fault is raised. Possible cause noise induced
on detection loop.
Check for faulty device located on the
detection loop.
Check loop cabling for induced noise.
If problem persists contact Technical Help
Line for further information.
detection loop.
Check loop cabling for induced noise.
If problem persists contact Technical Help
Line for further information.
Sync fault –
Apollo only
Apollo only
Faulty MBLC card
Replace MBLC card.