Professional Documents
Culture Documents
Addressable
Fire Alarm
Control Panels
Firmware version 24
Doc. version 1
14. October 2015
Tyco Fire & Security GmbH, Victor von Bruns-Strasse 21, 8212 Neuhausen am Rheinfall, Switzerland, 2015
Contents subject to change without notice.
All rights to this documentation, including the contents of the online help, are reserved, in particular but not limited
to the rights of copying, distribution and translation.
No portion of this documentation, including the online help, may be reproduced, edited, copied or distributed in any
form without prior written authorization from Tyco Fire & Security GmbH
FIRECLASS Fire Alarm Control Panels Contents
Contents
1 Overview ...........................................................................................................4
1.1 Fault Reporting, pseudo, points ..................................................................................... 4
1.2 Placing standard points into Fault ................................................................................. 4
1 Overview
This document gives a list of the possible fault states There are pseudo points within each point region, for
from FIRECLASS panels using Version 24 firmware. example, the Field Interface Module (FIM) pseudo
Faults are reported on the FIRECLASS panel in two points and the RBUS pseudo points. Each region has a
distinct ways: section below.
Using specific points used solely for fault reporting.
Setting a 'standard' point into a fault state.
1.2 Placing standard points
into Fault
1.1 Fault Reporting, pseudo, The system can also report faults on other points in the
points system. It does this by placing that point into a special
fault condition. This is different from standard point acti-
Pseudo points are activated when a monitored event
vation.
occurs. Depending on the firmware driver, they may be
cleared after a predetermined time, or they may only The software driver can place a point into different faults
clear when the monitored condition clears. These depending on the device being monitored.
conditions are reported by activating the processing Examples include 'NO RESPONSE' and 'RELAY
assigned to the point. STUCK'.
The Cause linked to the fault state is not visible to the
FIRECLASS Express user.
2 Pseudo Points
The configuration may be too complex for the panel to deal with.
The states monitored are the RAM and the firmware checksum.
Table 1: FIM Local I/O Pseudo Points
RBnn.Pmm
If the sequence identifier in a packet indicates a packet has been lost, this
fault is raised. It is automatically cleared within 60 seconds.
7 Char CHIP CSum Err The MPM, if configured as an OCM, performs a checksum on the data in
the character set EEPROM. If the calculated value does not match the value
stored within the device, this fault is raised.
Table 2: RBUS Node Pseudo Points
RBnn
TLI Pnn
2.5 Network Node Pseudo This section refers to faults regarding the
presence or absence of panel nodes.
Points
When reported on the user interface or via printers, the
output format used for faults reported from network
node points is:
Net nnn
COM1
COM2
COM3
4 System Fault
Company stamp