FireClass FC-P-S Service And Maintenance Manual page 26

5.4 Psuedo Points In FireClass
Field
Address
Label
Use
Table 10: Psuedo Point 6 -Details
Field
Address
Label
Use
Table 11: Psuedo Point 7 -Details
Field
Address
Label
Use
Table 12: Psuedo Point 8-15 -Details
26
Description
Pseudo Point 6
Configuration Store
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.
Description
Pseudo Point 7
FIM Comms Failed
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.
Description
Pseudo Point 8 to 15
Loop A Failed..... Loop H
Failed
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.
FireClass Fire detection system FireClass Panels
Field
Address
Label
Use
Table 13: Psuedo Point 25 -Details
Field
Address
Label
Use
Table 14: Psuedo Point 26 -Details
Field
Address
Label
Use
Table 15: Psuedo Point 27 -Details
Service and Maintenance Doc. version1
Description
Pseudo Point 25
FIM Bad Packet
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.
Description
Pseudo Point 26
FIM Fault
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.
Description
Pseudo Point 27
MP ROM Fail
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.