Tyco F3200 Smoke Alarm User Manual


 
F3200 Installation & Programming Manual Document No: LT0122
Configuring a FIP
Page 5-2 5 July 2001 Issue 2.7
5.1 GENERAL
An F3200 FIP is configured to suit a particular customer's requirements by:
Fitting and connecting the required pcb modules;
adding appropriate battery test resistors when necessary;
adjusting or removing links on the pcbs;
programming the FIP.
The detectors, manual call points (MCPs), warning devices, ancillary equipment and field
wiring that are connected to the FIP must match the FIP configuration.
The FIP configuration data, which is entered during programming, is stored in the non-
volatile memory database. The database may be saved to a computer for backup storage,
or reloaded from a computer.
All programmable options have a default option for the most likely usage. That is, for many
applications, no programming other than entry of site and zone names will be necessary.
Programming is described in detail in Chapters 6, 7, 11 and 12. The rest of this chapter
describes configuration of the hardware.
5.2 MODULE CONFIGURATION
The required modules are fitted to the F3200 as described in Section 2.3.2. Note that 8 way
modules are connected Bus Out to Bus In with all 8 Zone Modules preceding any 8 Relay
Modules. (Refer also to Section 8.1.3).
The F3200 does various self-tests on start up and includes checking to see what modules
are present (including 16 Zone LED Display Bds). It displays the results on the LCD. If the
modules present do not agree with the programmed database then the FIP annunciates this
and remains inactive.
E2 Initialisation causes the Controller/Display to accept the modules found as present and
stores this configuration in the database. E2 Initialisation also clears all other data
programmed in the database. Refer to Section 6.3.1.
Where it is desired to add a module to an existing system this can be done by programming
the Module Configuration through the keyboard (see Section 7.1).
For servicing, modules can be temporarily removed as detailed in Section 10.2 of the
Operator's Manual. This temporary configuration is not stored in the database.