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

FireClass Fire detection system FireClass Panels
Field
Address
Label
Use
Table 16: Psuedo Point 28 -Details
Field
Address
Label
Use
Table 17: Psuedo Point 29 -Details
Field
Address
Label
Use
Table 18: Psuedo Point 31 -Details
Service and Maintenance Doc. version 1
Description
Pseudo Point 28
MP System RAM
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.
Description
Pseudo Point 29
MP Clock
This point is not used for fault
reporting it is used in the
process of changing the
current time within the panel.
Description
Pseudo Point 31
Battery Low
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.
Field
Address
Label
Use
Table 19: Psuedo Point 32 -Details
Field
Address
Label
Use
Table 20: Psuedo Point 33 -Details
Field
Address
Label
Use
Table 21: Psuedo Point 34 -Details
Field
Address
Label
Use
Table 22: Psuedo Point 40-Details
5.4 Psuedo Points In FireClass
Description
Pseudo Point 32
RBus Circuit Fault
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 hap-
pens this point is activated.
The relay is only put to its
normal state on Fire Reset.
Description
Pseudo Point 33
Stack Overflow
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.
Description
Pseudo Point 34
System Heap Error
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.
Description
Pseudo Point 40
Local I/O F/W
The compatibility between
the firmware on the Local I/O
chip and the main firmware is
checked. If not compatible
the fault is raised.
27