EasyManua.ls Logo

FireClass FC32-1 - RBUS Node Specific Faults

FireClass FC32-1
24 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
8 Fault Finding Guide Doc. version 2
2.2 RBUS Node Pseudo Points FIRECLASS Fire Alarm Control Panels
2.2 RBUS Node Pseudo Points
When reported on the user interface or via printers, the
output format used for faults reported from RBus node
points is:
‘RBnn.Pmm’
Where nn is the node number 0–15 and mm is the
point on that node, 1–8.
This section refers to faults reported from a
node, not the higher level monitoring which
detects the presence or absence of complete
nodes.
Some configurations will not have some of
these faults set up.
Point
Address
Label Use
1 MPIM Display Fail If configured as a display module, the firmware monitors the link to the LCD
module. If a problem is found, this point is set.
2 MPIM ROM Fail The MPM regularly checks the checksum on the firmware held in ROM. If
the value calculated differs from the value stored in the ROM, this point is
activated.
3 MPIM RAM Fail The MPIM regularly checks each RAM byte with fixed bit patterns. If it
encounters read or write problems, this point is activated.
4 N/A Not used
5 N/A Not used
6 Bad packet Bad packet
7 MultiCast Seq Err 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 the sequence identifier in a packet indicates a packet has been lost, this
fault is raised. It is automatically cleared within 60 seconds.
8 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

Related product manuals