Initialising the database, Accessing the database, Verifying the database -13 – Tyco F3200 User Manual

Page 79

Advertising
background image

Document No: LT0122

F3200 Installation & Programming Manual

Programming

Issue 2.7

5 July 2001

Page 6-13

6.3 INITIALISING,

ACCESSING,

DE-ACCESSING,

PRINTING, SAVING, LOADING & VERIFYING THE
DATABASE

6.3.1 INITIALISING

THE

DATABASE

The E2 INIT (initialisation) sequence causes the FIP to accept the module configuration

found and store this in its database. Note that this also sets all other parameters to the

default option and erases all other programmable data in the database e.g. zone names,

output logic equations. It should, therefore, only be done on an unprogrammed system.

Whenever the panel is powered up or down, Lk7 should always be in the write protect

position.

Steps

1.

Fit the minijump on the DATABASE link, Lk7 (top right of Controller/Display) in the

WRITE PROTECT position, (i.e. NOT write enabled).

2.

With the batteries disconnected, turn the FIP mains power off.

3.

Short circuit pins SW1 (top centre of Controller/Display) with the minijump, then turn

the power on.

4.

When the start up sequence is completed the LCD prompts you to write enable the

database by moving Lk7 to the write enable position.

Move Lk7 to the write enable position.

You will then be prompted on the LCD to remove SW1 and press "ACK".

Remove the minijump from SW1 (place it on one pin only), and press "ACK" to

complete the sequence, or "CLEAR-ESC" to abort it.

6.3.2

ACCESSING THE DATABASE

When programming the database the DATABASE link (Lk7 on Controller/Display) must be

in the WRITE ENABLE position. At all other times it must be in the WRITE PROTECT
position.

With Lk7 on the Controller in the WRITE ENABLE position, selecting "Program Data" from

the SET menu prompts for entry of the 6 digit access code. The default access code is 0 0 0

0 0 0.

When access has been granted, the Program data menu is displayed and a new access

code can be entered (option 1, refer to Section 6.4.2).

The access code for the FIP should be recorded in the FIP contract file to enable future

reconfiguration. Where multiple users have individual codes then they should have a system

for remembering their own code.

Advertising