EQUIPMENT: MX

PUBLICATION: 17A-04-FF4
ISSUE No. & DATE: 1 9/03

DOCUMENT CONTROL NUMBER /

MX ADDRESSABLE FIRE CONTROLLERS

FAULT FINDING INFORMATION

1. OVERVIEW 2. PSEUDO POINTS IN MX
This document gives a list of the fault states possible from an This section details the pseudo points in MX Version 4. The
MX panel using Version 4.0 firmware. label and group assignments relate to the UK EN54 template.
Faults are reported on the MX panel in two distinct ways.
• Using specific points used solely for fault 2.1 POINT SECTION – LOCAL I/O
reporting
When reported on the user interface or via printers, the
• Setting a ‘standard’ point into a fault state output format used for Local I/O pseudo points is:
‘Pn’ where n is the point number.
1.1 FAULT REPORTING, PSEUDO, POINTS
Within each point section there are 'pseudo' points, these points Address Pseudo Point 1
are activated when a monitored event occurs. Depending on the Label Data Packet Error
firmware driver they may be cleared after a predetermined time, Use Not used in version 4
or they may only clear when the monitored condition clears. Assigned Group 104 - Gen. Purpose Fault I/P
These conditions are reported by activating the assigned group.

Address Pseudo Point 2

1.2 PLACING STANDARD POINTS INTO Label FIFO Full
FAULT Use Not used in version 4
Assigned Group 104 - Gen. Purpose Fault I/P
The system can also report faults on other points in the system,
this it does by placing that point into a special fault condition,
this is different from standard point activation.
Address Pseudo Point 3
The software driver can place a point into different faults Label EA FIFO Full
depending on the device being monitored. Use Not used in version 4
Examples include ‘NO RESPONSE’ and ‘RELAY STUCK’. Assigned Group 104 - Gen. Purpose Fault I/P

The group processing used in the reporting of these faults is

visible to the user in MX Consys, the assignment of fault state Address Pseudo Point 4
to the associated group is not alterable. Label LNET Data Path Flt
Use Not used in version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 5

Label LNET Module Flt
Use Not used in version 4
Assigned Group 104 - Gen. Purpose Fault I/P

© 2003 Tyco Safety Products PAGE 1 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

Address Pseudo Point 6

Label Configuration Store
Use Panel configuration is stored in Flash chips, the data is covered by a checksum.
The panel regularly calculates the checksum and compares it to that stored, if
different this point is activated. The panel will also start a shutdown procedure
which will result in it restarting and locking into a ‘safe state’. It is considered
unsafe to use a configuration that is known to be bad.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 7

Label Slave Busy Local IO
Use This fault is raised if the SPI channel is held busy by the slave processor (in this
case the Local I/O) for more than a second.
It is cleared when communication resumes.
Assigned Group 395 - Loop Fault I/P

Address Pseudo Point 8 to 15

Label Slave Busy Chan A….. Slave Busy Chan H
Use As pseudo point 7 above but used to monitor the loop SPI channels.
This fault is also raised if the slave, loop card, is not fitted.
Assigned Group 395 - Loop Fault

Address Pseudo Point 16

Label Bad Packet Local IO
Use Not used in version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 17 to 24

Label Bad Packet Chan A …. Bad Packet Chan H
Use Not used in version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 25

Label FIM Bad Packet
Use The main CPU communicates to the local I/O processor located on the FIM using
data packets on an SPI link. If three consecutive bad packets are received corrupt
this fault is raised.
The fault is self clearing after 10 seconds.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 26

Label FIM Fault
Use The Local IO chip regularly sends a health status regarding itself to the main
processor. If this status indicates a fault has been detected this point is activated.
It is cleared if the heath report indicates OK.

The states monitored are the RAM and the firmware checksum.
Assigned Group 104 - Gen. Purpose Fault I/P

PAGE 2 of 16
 EQUIPMENT:
MX
17A-04-FF4
PUBLICATION:
1 9/03
ISSUE No. & DATE:

Address Pseudo Point 27

Label MP ROM Fail
Use The firmware checks its own checksum regularly, if different to the values stored
within the firmware chip this fault is raised.
The firmware is then processed to place itself into a ‘safe state’, this involves
restarting in a ‘locked’ state. It is not deemed safe to use firmware known to be
corrupt.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 28

Label MP System RAM
Use The panel regularly checks each byte of RAM with fixed sequences to check each
bit can be written to and read independently.
If faults are detected this fault is raised and the system is placed into the 'safe state'
as described above.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 29

Label MP Clock
Use This point is not used for fault reporting it is used in the process of changing the
current time within the panel.
Assigned Group 165 - System Clock Update

Address Pseudo Point 30

Label Monitor Point
Use Not used in Version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 31

Label Battery Low
Use If the battery is present but the reported voltage has dropped below a threshold
value, this point is activated.
The fault is cleared once the voltage is greater than the threshold.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 32

Label RBus Circuit Fault
Use The Remote Bus (RBus) connections on the FIM are split between RBus 0 and
non-zero nodes.
If faults are detected on all nodes other than zero, a relay on the FIM is tripped to
isolate (protect) RBus 0 communications. If this happens this point is activated.
The relay is only put to its normal state on Fire Reset.
Assigned Group 196 - Comms Fault I/P

© 2003 Tyco Safety Products PAGE 3 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

Address Pseudo Point 33

Label Stack Overflow
Use If the firmware monitoring process discovers that one or more of the task stacks is
near the full condition the fault point is activated.
This fault is not cleared.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 34

Label System Heap Error
Use If the area of RAM within the panel used for system ‘heap’ is found to be corrupt,
this point is activated.
The point is not cleared.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 35

Label Unsupervised Panel
Use Not used in Version 4.
The fault is now raised using a different set of points to allow panel number
reporting.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 36

Label RUI Connection
Use The point is set when MX Remote (Remote User Interface) starts communication
and cleared when communication ceases. The end to communication can be
because the use MX Remote was finished or there was a problem in the
communication channel.
Assigned Group 312 - Remote Connect I/P

Address Pseudo Point 37

Label Undefined
Use Not used in version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 38

Label Undefined
Use Not used in version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 39

Label RBUS Firmware
Use Not used in Version 4
The fault is now raised on the particular RBus node, not as a general fault.
Assigned Group 104 - Gen. Purpose Fault I/P

PAGE 4 of 16
 EQUIPMENT:
MX
17A-04-FF4
PUBLICATION:
1 9/03
ISSUE No. & DATE:

Address Pseudo Point 40

Label Local I/O F/W
Use The compatibility between the firmware on the Local I/O chip and the main
firmware is checked. If not compatible the fault is raised.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 41

Label Undefined
Use Not used in Version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 42

Label Delay Pool Full
Use Not used in Version 4
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 43

Label Walktest Sounders
Use Sounders are walktested using standard point commands as directed from the User
Interface.
This point is set and cleared surrounding that walktest to place a record into the
panel log.
Assigned Group 322 - WalkTest Sounders I/P

Address Pseudo Point 44

Label Inhibit Sound LED
Use The system monitors the isolate status of sounder devices.
If all sounders are isolated this point is set, once one sounder is available the point
is cleared.
The activation of this point inhibits the activation of the sounder LED.
The goal is not to indicate on the front panel that sounders are active, when the
system knows they are all isolated.
Assigned Group 351 - Inhibit Sounders Active LED

Address Pseudo Point 45

Label Commissioning
Use The system monitors the commissioning states. If any are active this point is
raised.
Assigned Group 419 – Commission Mode I/P

© 2003 Tyco Safety Products PAGE 5 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

2.2 POINT SECTION – RBUS NODE PSEUDO POINTS

When reported on the user interface or via printers, the output format used for faults reported from an RBus node points is
‘RBnn.Pmm’
where nn is the node number 0-15 and mm is the point on that node 1-8.

Note:
1) This section refers to faults reported from a node, not the higher level monitoring which detects presence of
absence of complete nodes.
2) Some personalities will not have some of these faults configured.

Address Pseudo Point 1

Label MPIM Display Fail
Use If configured as an OCM the MPM firmware monitors the link to the LCD module.
If a problem is found this point is set.
Assigned Group 189 - System Display Fault I/P

Address Pseudo Point 2

Label MPIM ROM Fail
Use The MPIM regularly checks the checksum on the firmware held in ROM. If the
value calculated differs from that stored in the ROM this point is activated.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 3

Label MPIM RAM Fail
Use The MPIM regularly checks each RAM byte with fixed bit patterns. If read or
write problems are encountered this point is activated.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 4

Label N/A
Use Not used in Version 4
Assigned Group None

Address Pseudo Point 5

Label Printer Comms
Use The fault is only reported from PIBs.
IF data is sent to the PIB and the printer is offline the fault is raised. The fault is
cleared when the queued data can be sent.
Assigned Group 354 – Printer Offline I/P

Address Pseudo Point 6

Label Bad packet
Use This point is activated if the MPIM received an RBus packet that has a valid
checksum but can not be handled. For example a print request to an OCM.
Assigned Group 104 - Gen. Purpose Fault I/P

PAGE 6 of 16
 EQUIPMENT:
MX
17A-04-FF4
PUBLICATION:
1 9/03
ISSUE No. & DATE:

Address Pseudo Point 7

Label MultiCast Seq Err
Use Much of the LCD information is transferred with a system called ‘multi-cast’, this
allows the same information to be sent to multiple RBUS units with a single data
packet.
If sequence identifier in a packet indicates a packet has been lost, this fault is
raised. It will be automatically cleared by the MPIM within 60 seconds.
Assigned Group 104 - Gen. Purpose Fault I/P

Address Pseudo Point 8

Label Char CHIP CS
Use 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 that stored within
the device, this fault is raised.
Assigned Group 104 - Gen. Purpose Fault I/P

2.3 POINT SECTION – RBUS NODE FAULTS

When reported on the user interface or via printers, the output format used for faults reported from an RBus node faults are:
‘RBnn’
where nn is the node number 0 - 15.

Note:
1) This section refers to faults regarding presence or absence of complete nodes, It is NOT an indication of
faults held by the node but the node itself.
2) This set of points are exceptions to the normal address where the first point address is ‘One’ instead here
as the RBUS units can be addressed from 0-15 the first address is ‘Zero’

Address Pseudo Point 0 - 15

Label RBUS Fault
Use Used by RBUS / COMMS driver to indicate loss of configured nodes / presence of
un-configured nodes and other fault states such as firmware incompatible.
Assigned Group 139 – No response I/P
301 – Firmware Incompatible IP
386 – Character Set Chip Invalid
140 – Unconfigured device I/P

2.4 POINT SECTION – NETWORK CARD FAULTS

When reported on the user interface or via printers, the output format used for faults reported from Network Card Fault points
are:
‘TLI Pnn’
where nn is the point number 01-11

Note: This section refers to faults assigned to the network card. The configuration is controlled by the use of the
options in the ‘Network Card’ dialog within Consys

© 2003 Tyco Safety Products PAGE 7 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

Points 1 to 8 are used for TLI800 card

Points 9-11 are for the Filnet Card

Address Pseudo Point 1

Label Net Card Common
Use The Common fault is the ‘OR’ of all the other faults. The common fault condition
becomes true if any of the other fault conditions are true. In practice, it is
unnecessary to have a common fault message in addition to a detailed message. In
these circumstances the Common fault should be disabled.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 2

Label Net Card Left
Use The Port Left Connection fault is raised when the TLI800 Network Interface
Module detects a short or open circuit condition on its left network port wiring.
The fault may be disabled if the network is wired as a spur and the node is at the
end of the spur.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 3

Label Net Card Right
Use The Port Right Connection fault is raised when the TLI800 Network Interface
Module detects a short or open circuit condition on its right network port wiring.
The fault may be disabled if the network is wired as a spur and the node is at the
end of the spur.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 4

Label Net Card Ground
Use The Network Ground fault is raised when the TLI800 Network Interlace Module
detects a ground fault condition on the network.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 5

Label Net Card Data Trans
Use Data Transfer faults are generated on Node to Node transfers that do NOT receive
acknowledgements from the destination panel. This option should always be
enabled.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 6

Label Net Card Ring Cont
Use The Ring Continuity fault is raised when a transmitting panel does not receive its
transmitted message back on its opposite channel in the required time. This option
should only be enabled for ring topologies.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 7

Label Net Card Comms Fail
Use The Net Comms Failure fault is raised when a network card detects that it cannot
communicate with other network cards. This option should always be enabled.
Assigned Group 104 – General Purpose Fault I/P

PAGE 8 of 16
 EQUIPMENT:
MX
17A-04-FF4
PUBLICATION:
1 9/03
ISSUE No. & DATE:

Address Pseudo Point 8

Label Net Card F/W Incompatible
Use Indicates the network card is incompatible with the panel firmware.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 9 FILNET ONLY

Label Net Card Short_Cct
Use Indicates the network card detected a short circuit on the network.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 10 FILNET ONLY

Label Net Card Open_Cct
Use Indicates the network card detected an open circuit on the network.
Assigned Group 104 – General Purpose Fault I/P

Address Pseudo Point 11 FILNET ONLY

Label Net Card Emergency
Use Indicates that the network emergency mode is in fault.
Assigned Group 104 – General Purpose Fault I/P

2.5 POINT SECTION – NETWORK NODE FAULTS

When reported on the user interface or via printers, the output format used for faults reported from an RBus node points are:
‘Net nnn’
where nnn is the panel node number e.g. 001 - 099

Note: This section refers to faults regarding presence or absence of panel nodes

Address Pseudo Point 1 – 99

Label Network Node
Use Used by supervisor panel to indicate which panels are not responding to
supervison or if being supervised reporting lack of supervision.
Assigned Group 104 – General Purpose Fault I/P

2.6 POINT SECTION – COM1 FAULTS

When reported on the user interface or via printers, the output format used for faults reported from COM1 are:
‘COM1’

Note: This section refers a fault regarding presence of absence of a printer connected to COM1

Address Pseudo Point 1

Label Printer Comms
Use If a printer is configured and is not connected to the panel then this monitor point
will be activated.
Assigned Group 354 – Printer Offline I/P

© 2003 Tyco Safety Products PAGE 9 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

2.7 POINT SECTION – COM2 FAULTS

When reported on the user interface or via printers, the output format used for faults reported from COM2 are
‘COM2’

Note: This section refers to faults regarding COM2 which is the configuration or MX remote port.

Address Pseudo Point 1

Label Comms Fault
Use Will give fault if packet Retries exceed maximum (100).
Assigned Group 104 – General Purpose Fault I/P

2.8 POINT SECTION – COM3 FAULTS

When reported on the user interface or via printers, the output format used for faults reported from COM3 are:
‘COM3’

Note: This section refers to faults regarding COM3 which is used to connect to the network card

Address Pseudo Point 1

Label Comms Fault
Use Will give fault if packet Retries exceed maximum (100).
Assigned Group 104 – General Purpose Fault I/P

PAGE 10 of 16
 EQUIPMENT:
MX
17A-04-FF4
PUBLICATION:
1 9/03
ISSUE No. & DATE:

3. GENERAL FAULT OVERVIEW

The table below lists the fault states possible for standard points within MX. The group assignments are those assigned in the
UK EN54 Version 4.0 template.

Fault State Use within MX Version 4 Current group and logged

description

Loop Shutdown This fault is raised on the loop pseudo point 136
if the loop is shutdown. LOOP FAULT SHUTDOWN

Ground Fault Raised by the APM800. 137

GROUND FAULT
This indicates an earth fault either in PSU or
in a connected boards.

Noisy Device Not used in Version 4.0. 138

NOISY DEVICE

No Response This is a general fault state used by all the 139

point drivers. NO RESPONSE
It is raised if a configured device does not
response to a poll.
The device could be on the loop, an RBus
unit, or a panel not responding to network
supervision.
Unconfigured Device This is a general fault state used by all the 140
point drivers. UNCONFIGURED DEVICE
It is raised if a device responds to a poll that
is not configured.
The device could be on the loop, an RBus
unit, or a panel not responding to network
supervision.

High ID Current Not used in Version 4.0. 141

HIGH IDENT CURRENT

Low ID Current Not used in Version 4.0. 142

LOW IDENT CURRENT

Invalid Device Ident Used if configured device answers with 180

wrong ID. IDENT FAULT

Multiple Devices Used on the MX Digital loop driver to 181

indicate more than one device is replying to MULTIPLE DEVICES
the polled address.

Device Fault Used on the MX Digital loop driver for non- 143
specific faults. The device is present and DEVICE FAULT
replying, but the reply indicates a device
error. This is the catchall where a more
meaningful fault can not be raised.

Invalid Condition Not used in Version 4.0. 144

INVALID CONDITION

© 2003 Tyco Safety Products PAGE 11 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

Fault State Use within MX Version 4 Current group and logged

description

Low Long Term Average This fault is currently valid for the 8xxI and 145
8xxPH/PHEx, 801F/FEx devices. LO L.TERM AVG FAULT
It indicates the device is dirty and requires
changing.

High Long Term Average This fault is valid for 8xxI and 8xxPH/ 146
PHEx devices and indicates the device is HI T.TERM AVG FAULT
dirty and requires changing.

Loop Open Circuit Raised on the loop pseudo point if it is 147

found to be ‘Open Circuit’ due to open loop LOOP O/C FAULT
polling.

Loop Short Circuit Raised on the loop pseudo point if the AVR 148
processor detects higher than expected loop LOOP S/C FAULT
current.

Relay/Sounder Stuck Used on the SNM800 and the DIO800, 149

SIO800 devices. RELAY OR SDR STUCK
Relay cannot be switched to the state which
is required by the firmware.

Callpoint Short Circuit Not used in Version 4.0. 182

CALLPNT WIRING S/C

Callpoint Open Circuit Not used in Version 4.0. 183

CALLPNT WIRING O/C

Detector Wiring Fault Not used in Version 4.0. 150

DETECTOR WIRING FLT

Power Open Circuit This fault is used for the BDM800 and will 151
be raised if the device detects a supply open POWER WIRING OPEN
circuit.

Power Short Circuit This fault is used for the BDM800 and will 184
be raised if the device detects a supply short POWER WIRING SHORT
circuit.

Contact Open Circuit Raised on the MIM800 and SIO800 devices 185
if the supervised input is open. CONTACT WIRING OPEN

Contact Short Circuit Raised on the MIM800 and SIO800 devices 186
if the supervised input is shorted. CONTACT WIRING SHRT

Battery Fault Raised on the APM800, if the connection 152

between battery and PSU is in fault (below BATTERY FAULT
defined voltage).

Charger Fault Raised on the APM800 if the battery 153

connected to the PSU cannot be charged. CHARGER FAULT

PSU Fault Raised on the APM800 and the DIO800 154

devices if the auxiliary voltage is not in a AUX CHARGER FAULT
valid range.

PAGE 12 of 16
 EQUIPMENT:
MX
17A-04-FF4
PUBLICATION:
1 9/03
ISSUE No. & DATE:

Fault State Use within MX Version 4 Current group and logged

description

Mains Fault Raised on the APM800 if there is no mains 155

voltage on PSU, it is operating with battery. MAINS FAULT

Battery Critical Raised on the APM800. 157

BATTERY CRITICAL
This is raised at a higher voltage level that
the ‘Battery Fault’.

Sounder Fault Used to report faults on the LPS800, 158

SNM800 and with the sounder circuits on SOUNDER FAULT
the FIM.
A reason could be that the auxiliary voltage
is not present for the loop device.

Sounder Open Circuit Used to report faults on the LPS800 and 159
SNM800 if the supervised output is open. SOUNDER LINE OPEN

Sounder Short Circuit Used to report faults on the LPS800 and 187
SNM800 if the supervised output is shorted. SOUNDER LINE SHORT

Sounder EOL Fault Not used in Version 4.0. 188

SOUNDER EOL FAULT

LCD Display Failure Not used in Version 4.0. 189

LCD FAULT

Relay Coil Fault Used for fault reporting on the two sounder 160
circuits and the alarm relay on the FIM. RELAY COIL FAULT
Wiring Fault - Short Circuit This fault applies to CIM800, DIM800, 161
DIO800, GAR800, GARA800 and WIRING S/C FAULT
BDM800 devices and indicates the
supervised input is shorted.

Wiring Fault - Open Circuit As above, indicating the supervised input is 162
open. WIRING O/C FAULT

Airflow Fault Not used in Version 4.0. 163

AIRFLOW FAULT

Earth Contact Fault Not used in Version 4.0. 164

EARTH CONTACT FAULT
Detector Condition Low This fault can be raised on 8xxI and 8xxPH 190
/ PHEx devices. DET LTA LO WARNING
This condition is raised before the device
raises Low LTA.

Detector Condition High As above. 191

DET LTA HI WARNING
This condition is raised before the device
raises High LTA.

System Release Line Short Used by the LAV800, it indicates the 202
Circuit supervised output is shorted. RELEASE LINE SHORT

© 2003 Tyco Safety Products PAGE 13 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

Fault State Use within MX Version 4 Current group and logged

description

System Release Line Open Used by the LAV800, it indicates the 201
circuit supervised output is open. RELEASE LINE OPEN

System Release Line Stuck Used by the LAV800. It indicates the relay 203
cannot switch to the state which is required RELEASE RELAY STUCK
by the firmware.

No Network Supervision Raised if a networked panel fails to receive 208

the regular supervision poll. NET NO SUPERVISION

No Response From Sounder LPS800 and SNM800 (if configured as DC 285

sounders or AC speakers). SOUNDER NO RESPONSE
This fault is not raised when the device not
responding has a sounder base.

No response from Door This fault is raised by RIM800 and 286

Control SNM800 units if configured as door control DOOR CTRL NO RESPNS
units and not responding to polls.

Fault in Door Control Raised on an SNM800 if configured as door 287

control. DOOR CTRL FAULT
The Auxiliary voltage is not present.

Door Control Line Open Raised on an SNM800 if configured as door 288

control if the supervised output is open. DOOR CTRL OPEN CCT

Short Circuit in Door Control Raised on an SNM800 if configured as door 289

line control if supervised output is shorted. DOOR CTRL SHORT CCT

Door Control Stuck If the monitored contact is stuck on a 290

RIM800 or SNM800. DOOR CTRL STUCK
The relay cannot be switched in the state
which is required by the firmware.

No Response from Raised on an SNM800 if configured as 291

Extinguishing Control Extinguishing control. EXT. CTRL NO RESPNS

Fault in Extinguishing Raised on the LAV800 and SNM800 (if 292

Control configured as an Extinguishing Control EXT. CTRL FAULT
unit).
The Auxiliary voltage is not present.

Extinguishing Control Line Raised on an SNM800 if configured as 293

Open Extinguishing control. EXT. CTRL OPEN CCT
If supervised output is open.

Short Circuit in Extinguisher Raised on an SNM800 if configured as 294

Control line Extinguishing control. EXT. CTRL SHORT CCT
The supervised output is shorted.

Extinguishing Control Stuck Raised on an SNM800 if configured as 295

Extinguishing control. EXT. CTRL STUCK
The relay cannot be switched in the state
which is required by the firmware.

PAGE 14 of 16
 EQUIPMENT:
MX
17A-04-FF4
PUBLICATION:
1 9/03
ISSUE No. & DATE:

Fault State Use within MX Version 4 Current group and logged

description

No response from Alarm RIM800 and SNM800 if configured as 296

Control alarm control units. ALARM CTRL NO RESP

Fault in Alarm Control Raised on an SNM800 if configured as 297

Alarm Control. ALARM CTRL FAULT
The Auxiliary voltage is not present.

Alarm Control Line Open Raised on an SNM800 if configured as 298

Alarm Control and the supervised output is ALARM CTRL OPEN CCT
open.

Short Circuit in Alarm Raised on an SNM800 if configured as 299

Control line Alarm Control and the supervised output is ALARM CTRL SHRT CCT
shorted.

Alarm Control Stuck Raised on RIM and SNM800 devices. 300

ALARM CTRL STUCK
It indicates the relay cannot be switched in
the state which is required by the firmware.

Firmware Incompatible Loop firmware not able to provide features 301

required. F/W INCOMPATIBLE
Raised on an RBus channel if not
compatible due to changes in packet format.
All MPIM f/w released up to the time of
V4.0 panel firmware are compatible with
major features.

Fault with supervised input If the supervised input on the FIM becomes 143
faulty. DEVICE FAULT

Lost External Power Supply Reported by the DIM if it has problems with 326
its external power source. EXT PSU LOST

Detector Power Up Used on devices with a base:. 353

DETECTOR POWER UP
If one device was removed and re-inserted
again. Fault will be cleared after
initialisation of the device.

Calibration Fault Raised on the 8xxCH/CHEx, 8xxPH/PHEx, 383

801F/FEx devices if the calibration value, CALIBRATION FAULT
stored by the factory, are invalid.
The device cannot be used.

Invalid character set Raised by the panel if the OCM does not 386
contain a character set chip which supports WRONG CHAR SET CHIP
the codepage the panel wishes to use.
System Extinguishing Fault The control line used to control or monitor 388
extinguishing equipment is in fault. SYS EXTINGUISH. FLT

Loop Loading Fault The load on the loop has passed a threshold. 389
The loop is still working but the system may LOOP LOADING FAULT
not have the current to handle further large
scale point activations.

© 2003 Tyco Safety Products PAGE 15 of 16

Registered Office: First Floor North Building Walden Court Parsonage Lane Bishop’s Stortford Herts CM23 5DB
MX
17A-04-FF4
1 9/03

Fault State Use within MX Version 4 Current group and logged

description

Device not supported Not used in Version 4.0. 392

DEV. NOT SUPPORTED

Late Poll There is a background monitor of loop point 420

polling. LATE POLL
This process checks when a device is
polled, how long it has been since its last
poll. If that time is outside a tight time scale
this fault is raised.
This fault will clear when polling is within
expected parameters.
It is not expected this fault will ever be
announced, it is a required background
process for approvals.

Polling Error This fault is linked to the ‘Late Poll’ fault 421
described above. POLLING ERROR
The background monitor also scans the last
poll time of all points. If a point has not
been polled within a time window this fault
is raised.
It is not expected this fault will ever be
announced, it is a required background
process for approvals.
Window Fault The S271I+ and S271F+ devices can 433
monitor the state of their ‘window’. If this WINDOW FAULT
is found to be dirty and requires cleaning,
this fault is raised.
It is expected that dealing with this fault
will not require Tyco level service and can
be handled by the end user.

Beam Fault Beam Detector Module has detected the 448

FIRERAY (Beam detector) has raised a BEAM FAULT
fault.

Wrong Device Code Not used in Version 4.0. 449

WRONG DEVICE CODE

JM/mm

11th September 2003

PAGE 16 of 16