Document No: LT0499
RDU Mk2 Installation & Programming Manual
Programming Part 2
Issue 1.02
8 April 2015
Page 7-25
7.6
CONVERTING AN RDU Mk1 DATABASE TO RDU Mk2
7.6.1
USING THE DATABASE CONVERSION UTILITY
A database that was originally created by RDU Mk1 software can be used in an RDU
running Mk2 software but it must first be converted to a form that can be used with RDU Mk2
software. Also, RDU Mk2 software can be installed in an RDU that was previously running
RDU Mk1 software (if the hardware is not too old) and if it is desired to use the existing Mk1
database with the Mk2 software, then the database must first be saved to a computer where
the database conversion utility can be used to convert it to RDU Mk2 format. The database
conversion utility is available on the Tyco website as software SF0425.
The database conversion utility runs on a PC and reads a database file ("S2/S8 format") that
has been captured from RDU Mk1 software and generates a database file ("S2/S8 format")
that can be loaded into an RDU Mk2. The command line used to run the database converter
is : RDU_DatabaseConverter.exe input_filename output_filename 4428
The 4428 parameter at the end is optional, and if it is present the output database file will
have AS4428.1 operation selected, otherwise AS1603.4 operation is selected. An RDU Mk1
database is always AS1603.4 type so if the 4428 parameter is present, some translation is
done by the database converter to convert the AS1603.4 database to AS4428.1 operation.
The automatic translation may not always be desirable, in which case the "4428" option can
be left off and AS4428 operation configured manually after the database has been loaded
into the panel. The automatic conversion that occurs when the database is converted to
AS4428 mode is as follows.
1. FF Mode is selected as AS4428. Refer to section 6.4.1.1.
2. The keypad type is selected as AS4428. Refer to section 6.4.1.5.
3. The mapping of zones to ANC1, ANC2, ANC3 is converted to a mapping to ANC1,
Warning System and External Bell respectively. I.e., zones which were previously
mapped to ANC2 become mapped to the Warning System and zones which were
previously mapped to ANC3 become mapped to the External Bell.
Refer to the following section 7.6.3 for more information on the changes that need to be
made when converting to AS4428.1 compliance. If the RDU is to be fully AS4428.1
compliant then it must have separate relay outputs for the Warning System and External Bell
if these are provided. The ancillary 3 relay is most suitable for the Warning System because
it supports wiring to multiple circuits of alerting devices.
7.6.2
DIFFERENCES BETWEEN RDU MK1 AND RDU MK2 PROGRAMMING OPTIONS
In addition to the changes listed in the previous section when AS4428 operation is selected,
there are some other differences between RDU Mk1 and RDU Mk2 programming options.
The following is a list of the 1603 RDU parameters that do not have an obvious counterpart
in RDU Mk2 and how they are converted.
1. Custom mode.
The 1603 RDU Mk1 had a "mode parameter" that could be set to one of [non LCD
mimic, non LCD, type 2 mimic, type 2, type 3 mimic, type 3, custom]. If the "mode
parameter" was set to custom, then a number of additional custom mode parameters
could be programmed. RDU Mk2 does not have a mode parameter and all of the RDU
Mk1 custom mode parameters can be programmed at any time, regardless of other
mode settings. These include mimic/ non-mimic operation, FF type 2/3 selection, buzzer
options and FF alarm input source type.