RDU Mk2 Installation & Programming Manual
Document No: LT0499
Programming Part 1
Page 6-30
8 April 2015
Issue 1.02
Local
Setting local enabled means that when the trial evac keyswitch is operated at the RDU, the
bells relay (if any) at the RDU will be energised (regardless of isolation). During scan fail,
the trial evac keyswitch will always work locally even if local is disabled.
Follow
In future, some versions of FIP may transmit a “trial evac” state to an RDU. Setting follow
enabled at the RDU means that when the trial evac state received from the FIP is asserted,
the RDU bells relay will be energised, regardless of isolation. There is no current version of
FIP software which transmits the trial evac state to an RDU but future releases may do so.
During scan fail, the last known FIP trial evac state can be overridden by bells isolate at the
RDU.
For a non-maf RDU, setting follow or local true is meaningless because there is no bells
relay at the RDU, but setting pass-on true allows the non-maf RDU to send the state of its
trial evac input to the FIP.
6.4.4.4
MCP Manual Callpoint
The MCP can be enabled or disabled. If the MCP is enabled, it will be monitored for alarm
and fault which will be sent to the FIP when they occur.
NOTE
the MCP cannot be used in
New Zealand mode.
6.4.4.5
Brigade Test
If this option is enabled, the RDU keypad can be used to send a Brigade Test command to
the FIP.
6.4.4.6
All Zones Isolated
By default, the Standby relay will de-energise if all MAF mapped zones are isolated. This
may be disabled if allowed by the local Fire Brigade.
6.4.4.7
Printer setup
The printer setup menu options are:
1:Lines per page; 2:Baud Rate; 3:Print relay controls; >
Option 1:Lines per page, determines how often a new page/page heading is printed and
Option 2:Baud rate, allows the baud rate of the printer serial port to be set.
Option 3 allows the enabling/disabling of the logging of relay control (activate/deactivate)
events.
The right arrow key gives a further menu:
1:Event printer enable/disable; 2:Select print evt; 3:Select history evt
Option 1 allows event printing to be enabled or disabled. When event printing is disabled no
events at all are printed and the size of the history queue is doubled if history is stored in
RAM rather than non-volatile flash memory.
Options 2 and 3 allow the selection of which types of events are to be printed and logged to
history. There are six different types which can be individually enabled or disabled, and
these are shown as:
1:Zone 2:System 3:Sys run 4:Cct 5:Pnt 6:Relay