RDU Mk2 Installation & Programming Manual
Document No: LT0499
Programming Part 1
Page 6-16
8 April 2015
Issue 1.02
WARNING
If the RDU protocol is set different to the FIP protocol, this can be detected since an
incorrect RDU reply format will cause the FIP to generate scan fail for the RDU. A problem
arises when the RDU is programmed as mimic only. In this case the FIP is not expecting a
reply from the RDU so will not generate scan fail even though the RDU protocol is incorrect.
Similarly the RDU rejects all messages received from the master FIP because it cannot
interpret them, but does not show FIP Comms Failure as the messages are valid (just the
wrong protocol).
In this situation the RDU will not show the true zone status present at the FIP. Every zone at
the RDU will show normal regardless of the FIP zone status.
6.4.1.5
Keypad Type
The keypad parameter allows the keypad type to be selected as AS4428.1 or AS1603.4 to
match the physical keypad. On initialisation, the keypad type will be set as 4428.1. The
4428.1 keypad has Warning System Isolate, External Bell Isolate and AIF mode keys that
the 1603.4 keypad does not. The 1603.4 keypad has Bells Isol and Brigade Test keys that
the 4428.1 keypad does not.
6.4.1.6
Legacy Bells
The Legacy Bells option can be set to one of:
1:Warning System 2:External Bell 3:None
The Legacy Bells parameter is provided to allow AS4428.1 operation to be mixed with
AS1603.4 operation, when this is necessary. AS4428.1 systems have a Warning System
and an External Bell. AS1603.4 systems have only Bells. The Legacy Bells setting
determines whether Warning System isolate, External Bell isolate or neither, map to Bells
isolate. If set to "none", then neither the Warning System nor the External Bell map to Bells
isolate.
The RDU has an FF Mode parameter (refer section 6.4.1.1) that can be set to either
AS4428.1 mode or AS1603.4 mode. The RDU also has a "keypad type" parameter (refer
section 6.4.1.5) that is set according to whether the RDU keypad type is AS4428.1 or
AS1603.4. If the RDU FF Mode doesn't match the RDU keypad type or doesn't match the
type of FIP, the Legacy Bells parameter can be used to map Bells isolate. In general, the
RDU FF Mode should be set the same as the RDU keypad type but any combination is
allowed as listed below. For the purposes of the Legacy Bells setting at the RDU, an MX1
FIP behaves like an AS1603.4 FIP and effectively sends and receives "Bells isolate" states
to the RDU. MX1 maps "Bells isolate" to its "Alarm Devices" disable state.
1.
RDU FF Mode is AS4428.1, RDU keypad is AS4428.1
If the FIP type is also AS4428.1, the Legacy Bells parameter should be set to "none". If
the FIP type is AS1603.4 or is an MX1 panel, the Legacy Bells parameter can be used to
map FIP Bells isolate ("Alarm Devices disable" on MX1) to either Warning System isolate
or External Bell isolate at the RDU.
For example, if Legacy Bells is set to "Warning System" then the Warning System isolate
LED at the RDU indicates the state of FIP Bells Isolate, and the Warning System isolate
key at the RDU can be used to isolate and de-isolate the FIP Bells. Whether the RDU is
allowed to send isolate/de-isolate commands to the FIP is determined by the "pass-
on/follow" parameters associated with the Warning System (if Legacy Bells is set to
Warning System) - refer to section 6.4.4.3.1.