5.4 Psuedo Points In FireClass
FireClass Fire detection system FireClass Panels
26
Service and Maintenance Doc.
version1
Field
Description
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.
Table 10: Psuedo Point 6 -Details
Field
Description
Address
Pseudo Point 7
Label
FIM Comms Failed
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.
Table 11: Psuedo Point 7 -Details
Field
Description
Address
Pseudo Point 8 to 15
Label
Loop A Failed….. Loop H
Failed
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.
Table 12: Psuedo Point 8-15 -Details
Field
Description
Address
Pseudo Point 25
Label
FIM Bad Packet
Use
The main CPU communi-
cates to the local I/O proces-
sor 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.
Table 13: Psuedo Point 25 -Details
Field
Description
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.
Table 14: Psuedo Point 26 -Details
Field
Description
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 then proceeds
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.
Table 15: Psuedo Point 27 -Details
