FS20

Fire detection system

Commissioning
Maintenance
Troubleshooting
MP5

009052_q_en_-- Building Technologies

2014-01-15 Control Products and Systems
 Legal notice

Legal notice
Technical specifications and availability subject to change without notice.
© 2006-2014 Copyright by Siemens Switzerland Ltd

Transmittal, reproduction, dissemination and/or editing of this document as well as

utilization of its contents and communication thereof to others without express
authorization are prohibited. Offenders will be held liable for payment of damages.
All rights created by patent grant or registration of a utility model or design patent
are reserved.

Issued by:
Siemens Switzerland Ltd.
Infrastructure & Cities Sector
Building Technologies Division
International Headquarters
Gubelstrasse 22
CH-6301 Zug
Tel. +41 41 724-2424
www.siemens.com/buildingtechnologies

Edition: 2014-01-15
Document ID: 009052_q_en_--

2
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Table of contents

1 About this document ......................................................................................9

1.1 Applicable documents..................................................................................... 11
1.2 Download center.............................................................................................11
1.3 Technical terms .............................................................................................. 12
1.4 History of changes .......................................................................................... 12
2 Safety ............................................................................................................ 14
2.1 Safety instructions .......................................................................................... 14
2.2 Safety regulations for the method of operation ................................................ 16
2.3 Standards and directives complied with ..........................................................18
2.3.1 CPR conformity and firmware version ..............................................18
2.4 Release Notes ................................................................................................ 18
3 Mounting / Installation .................................................................................. 19
3.1 Installing and checking the detector line .......................................................... 19
3.1.1 Installing devices with serial number ................................................ 19
3.1.2 Installing devices according to the wiring sequence .......................... 19
3.1.3 Checking the detector line ................................................................ 20
3.2 Mount and install 'Station' ............................................................................... 20
4 Commissioning – overview .......................................................................... 21
4.1 Commissioning variants .................................................................................. 21
4.2 Definition of terms........................................................................................... 22
4.3 Standard gateway ........................................................................................... 23
4.4 Brief instructions on operating the 'Station' ...................................................... 23
4.5 License ........................................................................................................... 24
5 Connectivity and communication with 'Station'.......................................... 25
5.1 Connecting the PC to the station..................................................................... 25
5.2 Disconnecting PC from the 'Station' ................................................................ 25
5.3 Loading data to the 'Station' ............................................................................ 26
5.4 Initializing 'Station' .......................................................................................... 26
5.5 Loading configuration from the PC to the 'Station' ........................................... 28
5.6 Loading configuration from the 'Station' to the PC ........................................... 30
5.7 Creating a back-up of the 'Site' configuration................................................... 30
5.8 Setting Windows firewall ................................................................................. 32
5.8.1 Windows XP .................................................................................... 32
5.8.2 Windows 7 ....................................................................................... 32
6 General commissioning steps ..................................................................... 34
6.1 Preparing 'Station' for commissioning.............................................................. 34
6.2 Preparing 'Station' for commissioning – without BDV installation ..................... 35
6.3 Auto-configuring 'Station' ................................................................................ 35
6.4 Auto-configuring the detector line.................................................................... 36
6.5 Loading automatically created configuration to the PC .................................... 36
6.6 Adapting configuration .................................................................................... 37

3
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 6.7 Switch on detector line.................................................................................... 37
6.8 Switching off the detector line ......................................................................... 37
6.9 Restarting the detector line ............................................................................. 37
6.10 Read in devices on detector line ..................................................................... 38
6.11 Switching off 'Zone'......................................................................................... 38
6.12 Switching on 'Zone'......................................................................................... 38
6.13 Detaching the device ...................................................................................... 38
6.14 Delete the device on Person Machine Interface .............................................. 39
6.15 Remove the elements ..................................................................................... 39
6.16 Switching on test mode................................................................................... 39
6.17 Switch on normal operation ............................................................................ 40
6.18 Rectify localization errors ................................................................................ 41
6.19 Checking 'Site' function................................................................................... 41
6.20 Completion work ............................................................................................. 41
7 A - Commissioning stand-alone 'Station' without PC ................................. 42
7.1 Configuring the power supply.......................................................................... 43
7.2 Entering customer texts using the Person Machine Interface .......................... 43
7.3 Setting detector parameter sets ...................................................................... 44
8 B1 - Commissioning stand-alone 'Station' with PC, without pre-
configuration ................................................................................................ 45
9 B2 - Commissioning stand-alone 'Station' with PC, with
pre-configuration .......................................................................................... 46
10 C- Commissioning networked 'Stations' ..................................................... 47
11 Commissioning FC2080 ............................................................................... 48
12 Commissioning FG2020 ............................................................................... 49
13 Adding a 'Station' to an existing 'Site' ......................................................... 50
14 Commissioning Ethernet switch (MM) FN2008-A1 ...................................... 51
14.1 Install Primary Setup Tool ............................................................................... 52
14.2 Assign IP address........................................................................................... 52
14.3 Configure FN2008-A1 using Internet browser ................................................. 53
15 Commissioning safety module (firewall) FN2009-A1 .................................. 54
15.1 Installing Security Configuration Tool .............................................................. 55
15.2 Selecting type and entering MAC address ...................................................... 55
15.3 Entering network settings................................................................................ 56
15.4 Creating IP service definitions......................................................................... 59
15.5 Creating firewall rules ..................................................................................... 60
16 Merging two 'Sites' ....................................................................................... 62
16.1 Adding 'Site' B to 'Site' A ................................................................................. 63
16.2 Connecting 'Sites' physically to one another.................................................... 64
17 Changing and expanding the FDnet/C-NET detector line ........................... 65
17.1 Extending the detector line to include additional devices ................................. 65
17.1.1 Mount and wire new devices ............................................................ 65
17.1.2 Configure a new device.................................................................... 66
17.2 Replacing stationary devices of the same type................................................ 66

4
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 17.3 Permanently removing stationary devices ....................................................... 67
17.4 Removing or replacing non-stationary devices ................................................ 67
17.4.1 Temporarily removing an individual non-stationary device ................ 67
17.4.2 Temporarily removing multiple non-stationary devices...................... 68
17.4.3 Permanently removing non-stationary devices ................................. 68
17.4.4 Replacing non-stationary devices of the same type .......................... 69
17.4.5 Replacing a device........................................................................... 69
17.4.6 Replacing non-stationary devices of different types .......................... 69
17.4.6.1 Replacing a device in the 'Zone' ....................................................... 70
17.5 Replacing 'Manual call point' of the same type ................................................ 70
17.5.1 Switching on the replace mode ........................................................71
17.5.2 Switching off replace mode .............................................................. 71
17.5.3 Testing 'Manual call point' ................................................................ 71
17.6 Convert two stubs into a loop .......................................................................... 72
17.7 Connecting a sub-stub to a loop...................................................................... 72
18 Commissioning the control panel with MS9i detector lines ....................... 73
19 Commissioning control panel with collective detector lines...................... 74
19.1 Pre-configuration ............................................................................................ 74
19.2 Reference measurement with EOL 4k7 and 3k3 .............................................75
19.3 Possible error messages ................................................................................ 75
19.3.1 'Line Fault' error message ................................................................ 76
19.4 Troubleshooting procedure ............................................................................. 76
19.4.1 Checking the collective detector line ................................................ 76
19.4.2 Checking line resistance .................................................................. 77
19.4.3 Checking the line continuity.............................................................. 77
19.4.4 Measuring insulation values ............................................................. 77
19.4.5 Commissioning the collective detector line step-by-step ................... 78
20 Commissioning of control panel with AnalogPLUS detector line ..............79
21 Changing and expanding the AnalogPLUS detector line ...........................80
21.1 Adding a device to the detector line ................................................................ 80
21.2 Replacing a device with one of a different type................................................ 80
21.3 Removing a device for good ...........................................................................81
21.4 Replacing a non-stationary device of the same type........................................ 81
21.5 Replacing multiple non-stationary devices of the same type with a line restart . 81
21.6 Replacing a stationary device and I/O module.................................................82
21.7 Converting a stub or loop ................................................................................ 82
21.8 Querying the number of devices on the detector line ....................................... 82
21.9 Readdressing devices .................................................................................... 83
22 Commissioning of control panel with interactive detector line.................. 84
22.1 Commissioning of interactive detector line for AlgoRex data migration ............ 84
23 Changing and expanding the interactive detector line ............................... 86
23.1 Adding a device to the detector line ................................................................ 86
23.2 Replacing a device with one of a different type................................................ 86
23.3 Removing a device for good ...........................................................................86
23.4 Replacing a non-stationary device of the same type........................................ 87

5
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 23.5 Replacing an I/O module ................................................................................ 87
23.6 Replacing stationary manual call points of the same type ................................ 88
23.7 Converting a stub or loop ................................................................................ 88
23.8 Locating wire breaks....................................................................................... 89
24 Commissioning the sounder base FDSB291............................................... 90
25 Commissioning the fire brigade periphery module FCI2001-D1................. 91
26 Commissioning I/O card (remote transmission) FCI2007-A1 and I/O card
(horn/monitored) FCI2009-A1 ....................................................................... 92
27 Testing detectors.......................................................................................... 93
27.1 Activate the detector ....................................................................................... 93
27.2 Testing logged test activations ........................................................................ 93
28 Testing detector with detector exchanger and tester or intelligent detector
tester ............................................................................................................. 94
29 Updating the firmware of the 'Station' ......................................................... 95
29.1 Preparation and security ................................................................................. 95
29.2 Updating the firmware of the main CPU and the additional CPUs – Overview . 96
29.2.1 Standalone station and SAFEDLINK station ..................................... 96
29.2.2 Router station and Ethernet station .................................................. 97
29.2.3 Modular station with CPU card ......................................................... 98
29.2.4 Updating several 'Stations' simultaneously ....................................... 98
29.3 Updating the firmware of the additional CPUs only – Overview ....................... 99
29.3.1 Standalone station and SAFEDLINK station ..................................... 99
29.3.2 Router station and Ethernet station ................................................ 100
29.4 Update only the BDV .................................................................................... 100
29.4.1 Standalone station and SAFEDLINK station ................................... 100
29.4.2 Router station and Ethernet station ................................................ 101
29.5 Converting the configuration ......................................................................... 101
29.6 Updating the firmware of the main CPU and the additional CPUs.................. 102
29.6.1 PMI & mainboard FCM2004 ........................................................... 102
29.6.2 PMI & mainboard FCM2027 ........................................................... 104
29.6.3 CPU card FCC2004 ....................................................................... 106
29.7 Update the firmware of the additional CPUs .................................................. 108
29.8 Testing the firmware version of the additional CPUs ..................................... 110
29.9 Creating diagnosis report .............................................................................. 111
30 Updating the firmware of the peripheral devices ...................................... 112
30.1 Updating the firmware of the MCL-USB adapter FDUZ221............................ 112
30.2 Updating the firmware of the floor repeater terminal FT2010 ......................... 114
30.3 Updating the firmware of the floor repeater display FT2011........................... 116
30.4 Updating firmware of mimic display driver FT2001-A1 ................................... 118
30.5 Updating the firmware of the radio gateway FDCW221 ................................. 120
30.6 Updating the firmware of the radio gateway FDCW241 ................................. 122
30.7 Updating the firmware of the service device FDUD29x .................................. 122
30.8 Updating firmware on the line tester FDUL221 .............................................. 124
30.9 Updating firmware on the line tester with serial interface FDUL221 ............... 126
31 Commissioning external printer ................................................................ 128

6
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 32 Maintenance................................................................................................ 131
32.1 General ........................................................................................................ 131
32.2 Spare parts................................................................................................... 131
32.3 Testing and measuring instruments ..............................................................132
32.4 Preparatory work .......................................................................................... 132
32.5 Test system data .......................................................................................... 133
32.6 Testing the 'Station' ...................................................................................... 133
32.7 Check the power supply................................................................................134
32.8 Testing the printer......................................................................................... 135
32.9 Checking 'Site' function ................................................................................. 135
32.10 Intervals for testing the system function ........................................................ 135
32.11 Completion work ........................................................................................... 137
33 Repair .......................................................................................................... 138
33.1 Disconnecting 'Station' from the power supply ............................................... 138
33.2 Spare parts................................................................................................... 138
33.3 Fault messages on the Person Machine Interface ......................................... 139
33.4 Fault indicators on components ....................................................................141
33.5 Communication problems in networked systems ........................................... 141
33.6 Non-stationary devices of the same type have been swapped over ............... 142
33.7 Error message 'Topology is invalid' ............................................................... 143
33.8 Error message 'Too many devices' ............................................................... 144
33.9 Restart 'Station' ............................................................................................ 144
33.10 Restoring factory setting on the 'Station' ....................................................... 146
Index............................................................................................................ 149

7
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 About this document
1 Applicable documents

8
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 About this document
Applicable documents
1

1 About this document

Goal and purpose
This document provides information and work steps for installing, commissioning,
maintaining and repairing the fire detection system FS20. More information can be
found in the corresponding documents under 'Applicable documents'.

To understand this document, you must have complete knowledge of document

008836. See chapter 'Applicable documents'.

Scope
The information contained in this document is valid for market package MP5.

Target groups
The information in this document is intended for the following target groups:

Target group Activity Qualification

Installation personnel Assembles and installs the product Has received specialist training in the area
components at the place of of building installation technology or
installation. electrical installations.
Carries out a performance check
following installation.
Commissioning personnel Configure the product at the place of Has obtained suitable specialist training for
installation according to customer- the function and for the products.
specific requirements. Has attended the training courses for
Check the product operability and commissioning personnel.
release the product for use by the
operator.
Searches for and corrects
malfunctions.
Maintenance personnel Carries out all maintenance work. Has obtained suitable specialist training for
Checks that the products are in the function and for the products.
perfect working order.
Searches for and corrects
malfunctions.

Reference document and source language

The source language of this document is German (de).
The reference version of this document is the international version in English.
The international version is not localized.
The reference document has the following designation:
ID_x_en_--
x = version, en = English, -- = international

9
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 About this document
1 Applicable documents

Document identification
The document ID is structured as follows:

ID code Examples

ID_ModificationIndex_Language_COUNTRY A6V10215123_a_de_DE
-- = multilingual or international A6V10215123_a_en_--
A6V10315123_a_--_--

Date format
The date format in the document corresponds to the recommendation of
international standard ISO 8601 (format YYYY-MM-DD).

Conventions for text marking

Markups
Special markups are shown in this document as follows:

Requirement for a behavior instruction

1. Behavior instruction with at least two operation sequences

2.

– Version, option, or detailed information for a behavior instruction

Intermediate result of a behavior instruction

End result of a behavior instruction

Numbered lists and behavior instructions with an operation

sequence

X] Reference to a page number

'Text' Quotation, reproduced identically

<Key> Identification of keys

Supplementary information and tips

The 'i' symbol identifies supplementary information and tips for an easier way of
working.

10
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 About this document
Applicable documents
1

1.1 Applicable documents

Document ID Title

007004 Automatic Fire Detector, Technical Manual

007227 FDUD292 Detector Exchanger and Tester, Operation
008164 FD20 Sinteso Detector System, Equipment Overview
008250 FDUL221 Line Tester, Operation
008331 List of compatibility
008723 FD20 Detector system, Table of contents
008836 FS20 Fire Detection System, System Description
008837 FS20 Fire Detection System, Product Data
008838 Fx20xx, Fire Control Panel / Fire Terminal, Operation
008843 FS20 Fire Detection System, Planning
008851 FS20 Fire Detection System, Mounting / Installation
008860 FT201x Floor Repeater Terminal / Floor Repeater Display, Installation
009078 FS20 Fire Detection System, Configuration
009310 FT2010 Floor Repeater Terminal, Operation
009311 FT2011 Floor Repeater Display, Operation
009690 FS20 Fire Detection System, Components / Spare Parts / Repair Parts
009718 FDUD293 Intelligent Detector Tester, Operation
009771 Open-source software (OSS) licenses
009854 FDUZ221 MCL-USB adapter, Installation
009865 FDCW221, DOW1171, SMF121, SMF6120, Technical Manual
A6V10224853 FS20/FS720 Fire Detection System, External Printer, Application Note
A6V10227639 FDCW241 radio gateway, technical manual
A6V10244961 FS20 Fire Detection System, Site Conversion
A6V10380629 FT2080 fire terminal (Touch), operation

1.2 Download center

You can download various types of documents, such as data sheets, installation
instructions, and license texts via the following Internet address:
http://siemens.com/bt/download
Enter the document ID in the 'Find by keywords' input box.

You will also find information about search variants and links to mobile
applications (apps) for various systems on the home page.

11
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 About this document
1 Technical terms

1.3 Technical terms

Term Explanation

BDV Base data variant

ES Product version
FDnet Addressed detector line
FW Firmware
MCL Maintenance and commissioning link
'MCP' Abbreviation for 'Manual call point'

You will find additional technical terms and their explanation in document 008836,
in the chapter 'Glossary'. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

1.4 History of changes

The reference document's version applies to all languages into which the reference
document is translated.

The first edition of a language version or a country variant may, for example, be
version 'd' instead of 'a' if the reference document is already this version.

The table below shows this document's history of changes:

Version Edition date Brief description

q 2014-01-13 FDUZ227 added to various chapters: May be used instead of FDUZ221

p 2013-11-14 Edition for MP5
Change to date format according to ISO 8601
New:
Standard gateway pre-configured for stand-alone stations
'Commissioning' - 'Overview': FT2080 added
'Brief instructions on operating the station': Operation for FT2080
'Fault messages on the Person Machine Interface': Fault messages on the FT2080
'Commissioning of control panel with AnalogPLUS detector line'
'Changing and expanding the AnalogPLUS detector line'
'Commissioning of control panel with interactive detector line'
'Commissioning of interactive detector line for AlgoRex data migration'
'Changing and expanding the interactive detector line'
Revised:
Firmware update updated
Replacing a device without SintesoWorks
Chapters 'Removing or replacing non-stationary devices' and 'Changing and expanding the
detector line' have been combined into one new chapter called 'Changing and expanding
the FDnet/C-NET detector line'
Firmware update FDCW241
CPR replaces CPD: The Construction Products Regulation (CPR 305/2011) replaces the
previous Construction Products Directive (CPD 89/106).
Chapters 'B1 - Commissioning stand-alone 'Station' with PC, without pre-configuration' and
'B2 - Commissioning stand-alone 'Station' with PC, with pre-configuration': only applicable
to FDnet detector lines
'Definition of terms' chapter revised

12
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 About this document
History of changes
1

Version Edition date Brief description

o 2013-01 Chapter 'Setting Windows firewall' updated for Windows 7

n 2012-06 Addition to chapter 'Setting Windows firewall', for Windows 7
m 2012-05 Edition for MP-EN 4.0
New: Revised:
Updating the firmware of the main CPU Creating diagnosis report
and additional CPUs in a single step Restart the station
Updating the firmware of a modular Commissioning the sounder base FDSB291
station with CPU card(s)
Checking 'Site' function
Updating several 'Stations'
simultaneously Restoring factory settings
Update the firmware of the additional Addition to chapter 'Possible error messages',
CPUs via GAP for collective detector lines
Commissioning FC2080 Checking the detector line
Commissioning FG2020 Testing detector with detector exchanger and
tester or intelligent detector tester
Create a back-up of the'Site'
configuration Replacing non-stationary devices of different
types
Replacing FDnet device: 20 s wait time
instead of 40 s
Updating the firmware of the peripheral
devices: Resetting the line card no
longer necessary
Updating the firmware of the radio
gateway FDCW241
Commissioning of I/O card (remote
transmission) FCI2007-A1 and I/O card
(horn/monitored) FCI2009-A1
l 2010-07 Revised chapters: "Loading configuration from the PC to the 'Station'", "Updating the
firmware of the 'Station'"
k 2010-05 Edition for MP3.0:
History of changes redefined and standardized
Ethernet switch (MM) FN2008-A1 and safety module (firewall) FN2009-A1 added
"Merging two sites" chapter added
Chapter on 'Site' conversion removed. Reference to doc. A6V10244961 'Site conversion'
added.
Revised chapters: "Updating 'Station' firmware", "Restarting 'Station'", "Restoring 'Station'
to factory setting"
j 2009-10 Chapter 15 and 16: Commissioning steps revised
i 2009-04 Modifications for MP2.1
h 2009-02 "Commissioning control panel with collective lines" chapter revised
Chapter: "Updating the firmware of the peripheral devices (FT2010, FT2011, FDCW221)"
revised
New chapter: "Updating firmware of mimic display driver"
g 2009-01 Modifications for MP2.1
f 2008-08 Modifications for MP2.1
e 2008-07 Modification for MP1.3 and MP2.1
d 2007-09 Modifications for MP1.2 (Firmware update)
c 2007-08 Modifications for MP1.2 and new document structure
b 2006-11 Modifications for MP1.1
a 2006-10 First edition

13
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Safety
2 Safety instructions

2 Safety

2.1 Safety instructions

The safety notices must be observed in order to protect people and property.
The safety notices in this document contain the following elements:
Symbol for danger
Signal word
Nature and origin of the danger
Consequences if the danger occurs
Measures or prohibitions for danger avoidance

Symbol for danger

This is the symbol for danger. It warns of risks of injury.

Follow all measures identified by this symbol to avoid injury or death.

Additional danger symbols

These symbols indicate general dangers, the type of danger or possible
consequences, measures and prohibitions, examples of which are shown in the
following table:

General danger Explosive atmosphere

Voltage/electric shock Laser light

Battery Heat

Signal word
The signal word classifies the danger as defined in the following table:

Signal word Danger level

DANGER DANGER identifies a dangerous situation, which will result directly in death or
serious injury if you do not avoid this situation.

WARNING WARNING identifies a dangerous situation, which may result in death or serious
injury if you do not avoid this situation.

CAUTION CAUTION identifies a dangerous situation, which could result in slight to

moderately serious injury if you do not avoid this situation.

NOTICE NOTICE identifies possible damage to property that may result from non-
observance.

14
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Safety
Safety instructions
2

How risk of injury is presented

Information about the risk of injury is shown as follows:

WARNING

Nature and origin of the danger

Consequences if the danger occurs
Measures / prohibitions for danger avoidance

How possible damage to property is presented

Information about possible damage to property is shown as follows:

NOTICE

Nature and origin of the danger

Consequences if the danger occurs
Measures / prohibitions for danger avoidance

15
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Safety
2 Safety regulations for the method of operation

2.2 Safety regulations for the method of operation

National standards, regulations and legislation
Siemens products are developed and produced in compliance with the relevant
European and international safety standards. Should additional national or local
safety standards or legislation concerning the planning, assembly, installation,
operation or disposal of the product apply at the place of operation, then these
must also be taken into account together with the safety regulations in the product
documentation.

Electrical installations

WARNING

Electrical voltage
Electric shock
Work on electrical installations may only be carried out by qualified
electricians or by instructed persons working under the guidance and
supervision of a qualified electrician, in accordance with the electrotechnical
regulations.

Wherever possible disconnect products from the power supply when carrying
out commissioning, maintenance or repair work on them.
Lock volt-free areas to prevent them being switched back on again by mistake.
Label the connection terminals with external external voltage using a
'DANGER External voltage' sign.
Route mains connections to products separately and fuse them with their own,
clearly marked fuse.
Fit an easily accessible disconnecting device in accordance with IEC 60950-1
outside the installation.
Produce earthing as stated in local safety regulations.

Assembly, installation, commissioning and maintenance

If you require tools such as a ladder, these must be safe and must be intended
for the work in hand.
When starting the fire control panel ensure that unstable conditions cannot
arise.
Ensure that all points listed in the 'Testing the product operability' section below
are observed.
You may only set controls to normal function when the product operability has
been completely tested and the system has been handed over to the customer.

16
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Safety
Safety regulations for the method of operation
2

Testing the product operability

Prevent the remote transmission from triggering erroneously.
If testing building installations or activating devices from third-party companies,
you must collaborate with the people appointed.
The activation of fire control installations for test purposes must not cause
injury to anyone or damage to the building installations. The following
instructions must be observed:
– Use the correct potential for activation; this is generally the potential of the
building installation.
– Only check controls up to the interface (relay with blocking option).
– Make sure that only the controls to be tested are activated.
Inform people before testing the alarm devices and allow for possible panic
responses.
Inform people about any noise or mist which may be produced.
Before testing the remote transmission, inform the corresponding alarm and
fault signal receiving stations.

Modifications to the system design and the products

Modifications to the system and to individual products may lead to faults,
malfunctioning and safety risks. Written confirmation must be obtained from
Siemens and the corresponding safety bodies for modifications or additions.

Modules and spare parts

Components and spare parts must comply with the technical specifications
defined by Siemens. Only use products specified or recommended by
Siemens.
Only use fuses with the specified fuse characteristics.
Wrong battery types and improper battery changing lead to a risk of explosion.
Only use the same battery type or an equivalent battery type recommended by
Siemens.
Batteries must be disposed of in an environmentally friendly manner. Observe
national guidelines and regulations.

Disregard of the safety regulations

Before they are delivered, Siemens products are tested to ensure they function
correctly when used properly. Siemens disclaims all liability for damage or injuries
caused by the incorrect application of the instructions or the disregard of danger
warnings contained in the documentation. This applies in particular to the following
damage:
Personal injuries or damage to property caused by improper use and incorrect
application
Personal injuries or damage to property caused by disregarding safety
instructions in the documentation or on the product
Personal injury or damage to property caused by poor maintenance or lack of
maintenance

17
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Safety
2 Standards and directives complied with

2.3 Standards and directives complied with

A list of the standards and directives complied with is available from your Siemens
contact.

2.3.1 CPR conformity and firmware version

In order to satisfy Ordinance No. 305/2011 (the Construction Products Regulation –
CPR), the firmware of a newly installed fire detection installation must be current
market package version MP5 or higher.

NOTICE

Firmware version of a newly installed fire detection installation not updated

No CPR conformity
Compare the firmware version of a newly installed fire detection installation
with the firmware version MP5.
Update the firmware if necessary.

2.4 Release Notes

Limitations to the configuration or use of devices in a fire detection installation with
a particular firmware version are possible.

WARNING

Limited or non-existent fire detection

Personal injury and damage to property in the event of a fire.
Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.

NOTICE

Incorrect planning and/or configuration

Important standards and specifications are not satisfied.
Fire detection installation is not accepted for commissioning.
Additional expense resulting from necessary new planning and/or configuration.
Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.

18
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Mounting / Installation
Installing and checking the detector line
3

3 Mounting / Installation

3.1 Installing and checking the detector line

Most FDnet devices are installed on a base and can be changed with ease.
The bases of non-stationary FDnet devices and stationary FDnet devices must be
installed and uninstalled when the FDnet detector line is switched off and
disconnected from the power supply.

Prerequisites
The FDnet detector line is not connected to the control panel and is
disconnected from the power supply when the FDnet devices are being
installed, wired and inserted.
The FDnet detector line is tested with the line tester FDUL221.
The control panel is commissioned by the commissioning personnel.

3.1.1 Installing devices with serial number

Before inserting or connecting an FDnet device, stick the serial number on the
layout plan. The adhesive strip with the serial number can be found on the bottom
of the device.

1. Install and wire the FDnet devices and stick the serial number for each device
on the layout plan.
2. Install the detector dust caps on the optical point detector if necessary.
3. Install the designation plate if necessary.

3.1.2 Installing devices according to the wiring sequence

1. Install and wire the FDnet devices and document the wiring sequence in the
layout plan.
2. Install the detector dust caps on the optical point detector if necessary.
3. Install the designation plate if necessary.

19
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Mounting / Installation
3 Mount and install 'Station'

3.1.3 Checking the detector line

NOTICE

Simultaneous connection of line tester and FDnet detector line to the control
panel
Damage to line tester or control panel
Do not connect the line tester and the FDnet detector line to the control panel
at the same time.

Acceptance test
The FDnet detector line is not connected to the control panel.
1. Connect the line tester FDUL221 to the newly installed FDnet detector line.
2. Test the FDnet detector line for short-circuits, open lines and earth faults.
3. Check the number of the devices on the FDnet detector line using the display
on the line tester.
4. Check the branch-off position of the stubs and the number of devices at the
stubs.
5. Check the type of all FDnet devices.
6. Remedy any errors you notice and carry out the acceptance test again.

You will find information on the line tester in document 008250. See chapter
'Applicable documents'.

Error when reading in the devices

If there are too many devices on the FDnet detector line for them all to be
displayed on the line tester, a message to this effect is displayed. Proceed as
follows should this happen:
Read in the devices from both sides of the loop. To do this, change over the
detector line cables as follows:
- Connect the feed line of the detector line to connection socket B.
- Connect the return line of the detector line to connection socket A.
The devices are read in from the other side of the loop. This allows the devices
which previously couldn't be read in to be displayed.

3.2 Mount and install 'Station'

1. Mount and install the 'Station' according to the information in document
008851. See chapter 'Applicable documents'.
2. Insert the cables for the detector lines and the mains supply into the housing
but do not yet connect the the cables.
3. Insert the batteries but do not yet connect them.

You will find information about mounting and installation of 'Stations' components
in the 008851 document. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

20
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning – overview
Commissioning variants
4

4 Commissioning – overview
The 'Stations' on the FCnet, such as control panels FC2020/FC2040 and fire
terminals FT2040 and FT2080, are connected to the power supply and
commissioned by the installation and commissioning personnel.
Networked 'Stations' must only be commissioned with SintesoWorks.
Standalone control panels can be commissioned with or without SintesoWorks.

NOTICE

Alternative commissioning procedure

Faults during operation
Only the procedures described in this document are permitted.

4.1 Commissioning variants

In order to satisfy Ordinance No. 305/2011 (the Construction Products Regulation –
CPR), the firmware of a newly installed fire detection installation must be current
market package version MP5 or higher.

NOTICE

Firmware version of a newly installed fire detection installation not updated

No CPR conformity
Compare the firmware version of a newly installed fire detection installation
with the firmware version MP5.
Update the firmware if necessary.

The table below provides an overview of the procedure for commissioning the
'Stations'. The letters A, B1, B2 and C refer to the detailed descriptions in the
following chapters.

Standalone control panel Networked 'Stations'

Without No pre- A Not possible.

SintesoWorks configuration Auto-configuration
possible
Adaptations on the Person Machine
Interface
With Without pre- B1 C
SintesoWorks configuration Auto-configuration Initialize the 'Stations' for networking
Adaptations in SintesoWorks Read in the FDnet devices by line
With pre- B2 Assign the logical elements in
configuration SintesoWorks
Read in the devices by line
Assign the logical elements in
SintesoWorks

Commissioning variants

21
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning – overview
4 Definition of terms

4.2 Definition of terms

Auto-configuration Auto-configuration is performed using a command on the Person Machine Interface. In this
process, the FDnet devices are read in and a configuration created.
There are two types of auto-configuration.
Auto-configuration of an individual FDnet detector line
Auto-configuration of 'Station'
Auto-configuration results in the following:
One 'FDnet' is created for each Section detector line.
One 'Sensor' is created for each 'Channel' 'Automatic detectors' ('Manual call points' and
'Zone').
One 'Input' is created for each 'Channel' 'Technical zone'.
For all 'Output' channels and for each FDnet detector line, one 'Control' is created.
One 'Control' is created for each alarm sounder.
External alarm indicators are not auto-configured.
Each 'Section' and each 'Zone' contains customer text, such as detector line no., zone no.,
and serial number of the device.

Detailed information about the result of auto-configuration can be found in the 'List of
compatibility'.

Pre-configuration The logical elements incl. customer texts are created in SintesoWorks prior to commissioning:
In the 'Detection' task card up to and including 'Zone' level
In the 'Control' task card up to and including 'Control' level ('Fire control', 'Evac control',
'Counter control')
In addition, the logical elements can subsequently be assigned as far as possible for alarming
and control.
Logical channels can be preconfigured. This makes sense if customer texts are to be
configured down to this level.

Read in by line The FDnet detector line can be read in by sending a command via the Person Machine
Interface. During this process, the devices are listed without generating sections and zones i.e.
no corresponding logical elements are created in the 'Detection tree' and 'Control tree'.

Adaptations The following procedures are examples of adaptations:

Entering customer text for logical elements
Changing detector parameter sets
Configuring alarm devices
Configuring 'Controls'
Configuring the power supply

Non-stationary devices Point detectors installed on a base apart from radio detectors.

Stationary devices All devices apart from point detectors, e.g.:

Manual call point
Radio detector
Input/output modules
Alarm sounder
Line separator
Radio gateway
Floor repeater terminal
Floor repeater display
Mimic display driver

22
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning – overview
Standard gateway
4

4.3 Standard gateway

The standard gateway address of the station is pre-configured as
192.168.200.254. When using a router, an address does not need to be set at the
station. Following startup, the station automatically connects to the router. A tool is
not required to establish a remote connection.

station Router
IP address: 192.168.200.1 192.168.200.254
Subnet mask: 255.255.255.0 255.255.255.0
Standard gateway: 192.168.200.254

4.4 Brief instructions on operating the 'Station'

Fire control panel FC20xx / Fire terminal FT2040
Buttons Description

Opens the main menu

= <MENU>

> and < > Navigation buttons for selecting the next or previous entry in
a list
> and < > Navigation buttons for changing to a higher or lower level in
the hierarchy
Opens or runs a selected entry or menu item
ok = <ok>

Cancels all operating procedures and closes an open list or

C = <C> an open window
<1> to <9> Buttons on the keypad to enter:
PIN
Shortcut
Address
Parameter
Customer text

You will find detailed instructions for operating the 'Stations' in document 008838.
See chapter 'Applicable documents'.

23
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning – overview
4 License

Fire terminal (Touch) FT2080

Buttons Description

Opens the 'Main menu'

Opens the topology

and Navigation buttons for changing to a higher or lower level in

the hierarchy
Opens the 'Select command' dialog window

Command execution OK

Command execution not OK

Valid setting of a menu

Current position in the topology
Selected filter setting
Performing search

Navigation buttons to scroll between pages

and

You will find detailed instructions for operating the 'FT2080' in document
A6V10380629. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

4.5 License
When the data is first loaded from the PC to the 'Station', the 'Station' receives the
license from SintesoWorks. Communication between the 'Station' and
SintesoWorks is then only possible with a valid license.

24
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
Connecting the PC to the station
5

5 Connectivity and communication with 'Station'

A PC does not have to be directly connected to a 'Station' to be able to
communicate with a 'Station' in the 'Site'. The PC can be connected to any place in
the Ethernet.
Detailed information about the connection variants can be found in the
'Establishing connection from PC to FS20 network' chapter in document 009078.
See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

5.1 Connecting the PC to the station

For most commissioning, maintenance and repair work a PC with installed
SintesoWorks is required. The figure below shows the connection between the PC
and 'Station'.

Rear panel of operating unit and PC

LAN Ethernet connection

1 Cable, type CAT 5 or CAT 7, crossover, max. 100 m

5.2 Disconnecting PC from the 'Station'

As the IP address is bound to the MAC address while there is a connection
between the PC and the 'Station' and as it remains in the cache even in the case of
a short break in the connection of 2 min., you must observe the following
instructions.

NOTICE

Incorrect disconnection of 'Station'

Establishing a connection to other 'Station' is not possible
Disconnect the PC from the 'Station' as described in the following instructions.

The connection between the PC and the 'Station' must be disconnected as follows:
1. Select 'Commissioning' > 'Disconnect' in SintesoWorks.
2. Disconnect the cable connection between PC and 'Station'.
3. Wait 2 min. before you establish a connection to another 'Station'.

25
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
5 Loading data to the 'Station'

5.3 Loading data to the 'Station'

Data is loaded from SintesoWorks to the 'Station' when the following commands
are performed.
'Initialize station'
'Download site'

If you use a number of network cards on the PC, observe the information in the
chapter 'IP settings for several network cards' in document 009078. See chapter
'Applicable documents'.

The table below shows which data is overwritten in the station 'Station'.

Command Overwrites the Sets the address Overwrites the

BDV of the 'Station' configuration

'Initialize station' 1 Yes Yes Yes

'Download site' Yes No Yes 2

1 Command is only performed for the 'Station' that is connected to the PC via LAN.
2 The configuration of all 'Stations' in the 'Site' can be overwritten as an option.

See also
Initializing 'Station' [ 26]
Loading configuration from the PC to the 'Station' [ 28]

5.4 Initializing 'Station'

Each 'Station' in a fire detection system with several networked 'Stations' must
have a unique address.
Once a 'Station' has been started for the first time or once the firmware on the
main CPU has been updated, a 'Station' has the address '1'. Networked
'Stations' must therefore all be initialized.
If two 'Sites' are merged to form one 'Site', the 'Stations' with the same
addresses in the added 'Site' must each be given a new address.
The 'Initialize station' procedure issues the 'Station' an address within the 'Site'
according to the configuration in SintesoWorks.

A standalone 'Station' does not have to be initialized.

If you use a number of network cards on the PC, observe the information in the
chapter 'IP settings for several network cards' in document 009078. See chapter
'Applicable documents'.

26
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
Initializing 'Station'
5

'Initialize 'Station'

NOTICE

Connection module (card cage) FCA2006-A1 defective or installed incorrectly

Control panels identified incorrectly, e.g. FC2060 identified as FC2040.
Check that the connection module (card cage) FCA2006-A1 is installed
correctly.

The PC is connected locally to the 'Station'.

1. Highlight the 'Station' you want to initialize in the 'Hardware tree'.
2. Select the 'Commissioning' > 'Initialize station' menu item.
The following window is opened:

3. Click on 'Start'.
The following window is opened:

4. Press <MENU> on the 'Station' and enter a valid PIN.

5. Click on 'OK' in the 'Set access level' window.
The 'Station' is initialized.
The 'Station' is restarted.
After a few minutes, the 'Buzzer' sounds twice.
6. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.

See also
Loading data to the 'Station' [ 26]

27
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
5 Loading configuration from the PC to the 'Station'

5.5 Loading configuration from the PC to the 'Station'

You can use the 'Download site' function to load the configuration of one 'Site' from
the SintesoWorks on the PC into the 'Station'.

NOTICE

Different network configuration in 'SintesoWorks' and networked 'Site'

When the selection displayed for 'Download site' is manually modified, in special
cases1 it may be necessary to reset a 'Station' to the factory setting as well as a
'Initialize station'.
Do not modify the selection displayed for 'Download site' in normal cases.
Check the sequence when loading different configuration states in special
cases 1.
After any change of the network configuration, make sure that all 'Stations' in
the 'Site' for the 'Download site' procedure are selected and can be accessed.
Temporarily update non-accessible 'Stations' to the latest status of the global
network configuration prior to integration in the network.

If you use a number of network cards on the PC, observe the information in the
chapter 'IP settings for several network cards' in document 009078. See chapter
'Applicable documents'.

The 'Site' is opened in SintesoWorks.

The PC is connected to the 'Station'.
Networked 'Stations' are initialized.
'Station' and SintesoWorks have the same 'Site' ID.
'Station' and SintesoWorks are in the same organizational unit.
1. Select 'Commissioning' > 'Download site'.
The 'Download site' and 'Connect' windows are opened.

2. Select 'Connect' in the window and click on 'OK'.

The 'Stations' are listed in the 'Download site' window.
3. Select the 'Stations' whose configuration you would like to load from
'SintesoWorks' to the 'Stations' and click on 'Start'.
The 'Set access level' window may be opened with the 'Set the station to
access level 3' prompt. Press <MENU> on the 'Station', enter the PIN and
press <ok>.

28
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
Loading configuration from the PC to the 'Station'
5

4. Click on 'OK' in the 'Set access level' window.

The 'Action confirmation' window opens.
5. Click on 'Yes'.
The configuration is loaded to the 'Station'.
The advancement status is displayed in the 'Download site' window.
The 'Station' restarts.
After a few minutes, the 'Buzzer' sounds twice.
6. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.

1 Examples of special cases:

A 'Station' will be added to a networked 'Site' and a new network configuration
will be loaded upon initialization of this 'Station', different from the global
network configuration of the connected 'Site'.
During the 'Download site' procedure a 'Station' is temporarily not accessible.
Both examples can result in the 'Station' no longer starting after the 'Download site'
procedure and the above actions having to be carried out.

See also
Loading data to the 'Station' [ 26]

29
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
5 Loading configuration from the 'Station' to the PC

5.6 Loading configuration from the 'Station' to the PC

The 'Upload site' function can be used to load the configuration of a 'Site' to
SintesoWorks on the PC.
The 'Site' is opened in SintesoWorks.
The PC is connected to the 'Station'.
'Station' and SintesoWorks have the same 'Site' ID.
'Station' and SintesoWorks are in the same organizational unit.
1. Select 'Commissioning' > 'Upload site'.
The 'Upload site' and 'Connect' windows are opened.

2. Select 'Connect' in the window and click on 'OK'.

The 'Stations' are listed in the 'Upload site' window.
3. Select the 'Stations' whose configuration you would like to load to
SintesoWorks and click on 'Start'.
The 'Action confirmation' window opens.
4. Click on 'Yes'.
The configuration is loaded to the PC.
The advancement status is displayed in the 'Upload site' window.

5.7 Creating a back-up of the 'Site' configuration

With the 'Create backup embedded configuration' function, you can create a back-
up file of the 'Site' configuration.
The following conditions must be satisfied for a complete back-up:
All of the 'Stations' in the 'Site' must be networked and commissioned.
The 'Site' IDs for all 'Stations' must match the 'Site' ID for the 'Site' loaded in
SintesoWorks.
The BDVs for all 'Stations' must be compatible with the BDV for the 'Site'
loaded in SintesoWorks.
– The BDVs are compatible when the major version and the minor version
are identical. The bugfix version is not relevant for the compatibility.
The country codes of the BDVs for all 'Stations' must match the BDV for the
'Site' loaded in SintesoWorks.

You will find Information about BDV names and versions in document 009078.
See chapter 'Applicable documents'.

If the above-mentioned conditions are not satisfied, a corresponding message is

displayed and an incomplete back-up file created. In this instance, 'incomplete' is
added to the file name of the back-up file.

30
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
Creating a back-up of the 'Site' configuration
5

Creating a back-up
The 'Site' is opened in SintesoWorks.
The PC is connected to a 'Station'.
1. Select 'Commissioning' > 'Create backup embedded configuration'.
The 'Create backup embedded configuration' and 'Connect' windows are
opened.

2. Select 'Connect' in the window and click on 'OK'.

The 'Site' configuration is loaded to the PC and saved as a back-up file.
The advancement status is displayed in the 'Create backup embedded
configuration' window.

Back-up file
The back-up file is saved in the following directory as standard:
C:\Documents and Settings\All Users\Application Data\Siemens\FX2030
The back-up file has the following name:
<'Site' name>_<back-up counter>(_incomplete).fsc
Example: Test_Site_007_incomplete.fsc
– 'Site' name: Name of the 'Site'.
– Back-up counter: Three-digit number that is automatically assigned to each
back-up.
– 'incomplete': If it was not possible to create a complete back-up,
'incomplete' is added to the file name.
A maximum of ten 'Site' back-up files are saved. If more than ten back-up files
are created, the oldest file is automatically deleted.

In the pre-settings, you can define that a back-up file is created automatically
each time a configuration is loaded from the PC to the 'Station' using the
'Download site' command. To do this, select 'Options' > 'Preferences' >
'Commissioning preferences'.

31
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
5 Setting Windows firewall

5.8 Setting Windows firewall

The aim of the settings is to establish a functioning Ethernet connection between
the FXS2002 engineering tool on the PC and FS20 control panels.
The Windows firewall may prevent the PC connecting to the 'Station'. In this case,
the firewall must be switched off in Windows XP or firewall rules set in Windows 7
when working with the fire detection installation.
To do this, proceed as follows:

You must have administrator rights to make the following settings.

5.8.1 Windows XP
You have administrator rights on your PC
1. Open the Windows start menu.
2. Select 'Settings' > 'Control panel' > 'Administrative Tools' > 'Services'.
3. Right-click on 'Windows Firewall/Internet Connection Sharing (ICS)' in the new
window.
4. Select 'All Tasks' > 'Exit' in the context menu.
5. Once the work is complete, reactivate the firewall. To do this, proceed as
described above but select 'All Tasks' > 'Start' in the context menu.

NOTICE

Security vulnerability in operating system due to deactivated firewall

Unauthorized access to your PC
Activate the firewall after the firmware update.

5.8.2 Windows 7

There are different ways of adjusting the firewall rules in Windows 7. The
following settings apply for Siemens PCs which use group guidelines controlled
by the domain.

Make the following settings for the Windows 7 firewall:

You have administrator rights on your PC.
The PC is connected to the Siemens intranet.
1. Open the Windows start menu.
2. Select 'Control Panel' > 'All Control Panel Items' > 'Administrative Tools' >
'Local Security Policy' > 'Windows Firewall with Advanced Security'.
3. Expand the menu.
4. Right-click 'Inbound Rules' > 'New Rules'
This opens the 'New Inbound Rule Wizard'.

32
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Connectivity and communication with 'Station'
Setting Windows firewall
5

5. Select 'Rule Type' and activate 'Program'.

6. Click 'Next >' to confirm and enter the program path to 'F-FXS2002.exe'.
- Example: C:\Program Files (x86)\Siemens\F-FX2030\XL_en_1-V5.0
- NOTICE! Remember to enter/add the new path if the version changes.
7. Click 'Next >' to confirm and then confirm the default setting 'Allow the
connection' in the next step ('Action').
8. In the next step 'Profile', remove the check mark from the 'Domain' checkbox.
The 'Private' and 'Public' checkboxes are checked.
9. Click 'Next >' to confirm and enter an appropriate name in the next step
('Name'), such as 'FS20 application'.
10. Click 'Finish' to complete the process.
A 'New Rule' has now been set and appears in the 'Inbound Rules' list.
It is necessary to make additional settings for the new rule:
1. Right-click the new rule and select 'Properties'.
2. Select the 'General' tab in the 'Rule Name Properties' window.
3. Set the following values:
4. 'General': 'Activated'
5. 'Action': 'Allow connection'
6. Select the 'Protocol and Ports' tab.
7. Set the following values:
- 'Protocol type': 'UDP'
- 'Local port': 'Specific Ports', and enter the value range '50067-50070' in the
box.
- 'Remote port': 'All Ports'
8. Confirm with 'OK'.
The new firewall rule is now configured.

NOTICE

Security vulnerability in operating system due to open ports

Unauthorized access to your PC
Deactivate the firewall rule configured above after the firmware update.

33
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
6 Preparing 'Station' for commissioning

6 General commissioning steps

The following chapters contain general commissioning steps that are referred to in
several chapters.

6.1 Preparing 'Station' for commissioning

1. Connect the cables for the detector lines and the periphery devices.
2. Connect the power supply (mains and batteries).
The 'Station' starts and reads in the internal hardware.
During start-up, the 'FAULT' LED flashes and the display shows the
progress.
During start-up, the firmware version F-FXS2001 is displayed.
3. Wait until the display indicates the selection of the BDV.
4. Press the 'Install' softkey and confirm with the 'Yes' softkey.
The 'Station' restarts.
During this process, the 'FAULT' LED flashes and the display shows the
progress.
5. Wait until only the green 'System On' LED lights up, the display shows the
normal condition and the 'Station' can be operated.
6. Press <MENU> and select the 'Login/logout' menu item.
You are prompted to enter a PIN.
7. Enter the PIN and confirm with <ok>.
The 'User successfully logged in' message is displayed.
The main menu is shown on the display.
8. Check the firmware of the 'Station' to ensure that it is up to date. To do this
select the 'Topology' > 'Hardware tree' > 'Station' > 'More Options' > 'Show
details' menu items.
The 'Station' version and configuration data are displayed.
9. Update the firmware if necessary.
10. Enter the date and time. To do this, select the 'Settings/administration' >
'System commands' > 'Set system time' menu items.

Additional messages may be displayed depending on the configuration of the

'Station'.

34
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
Preparing 'Station' for commissioning – without BDV installation
6

6.2 Preparing 'Station' for commissioning – without BDV

installation
1. Connect the cables for the detector lines and the periphery devices.
2. Connect the power supply (mains and batteries).
The 'Station' starts and reads in the internal hardware.
During start-up, the 'FAULT' LED flashes and the display shows the
progress.
During start-up, the firmware version F-FXS2001 is displayed.
3. Wait until the display indicates the selection of the BDV.
The 'Station' is prepared for commissioning.

It is not necessary to install the BDV for the further procedure. This saves having
to restart the 'Station'.

6.3 Auto-configuring 'Station'

1. Select 'Topology' > 'Hardware tree' > 'Station' in the main menu.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Auto-configure station' command.
The 'Station' is auto-configured.
The following message is shown following successful auto-configuration:
'Command executed'

You will find detailed information on the result of the auto-configuration in the 'List
of compatibility'. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

35
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
6 Auto-configuring the detector line

6.4 Auto-configuring the detector line

NOTICE

Incorrect order for reading in a loop, no isolation of second 'Line'

Error when reading in a loop
The FDnet detector lines are detected as stubs during the first system start-up,
e.g. 'Line' 11, 'Line' 12 (2-digit line number), even if they are connected as a loop.
Before you proceed to reading in the first 'Line', you must isolate the second
'Line'.
To read in a loop, always select the first 'Line', in this case the 'Line' 11. The
'Line' 12 is then read in automatically and a loop is displayed with a 1-digit line
number, in this case as 'Line' 1.
Proceed in the same way from 'Line' 21/22 (loop 2) to 'Line' 41/42 (loop 4).

1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Auto-configure line' command.
The 'FDnet' detector line is auto-configured.
The following message is shown following successful auto-configuration:
'Command executed'

You will find detailed information on the result of the auto-configuration in the 'List
of compatibility'. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

6.5 Loading automatically created configuration to the

PC
1. Select the 'File' > 'New site' menu item.
The 'Create new site' window opens.
2. Select the 'Upload from station(s)' option field.
3. Click on 'Next'.
The 'Create site by uploading from station(s)' and 'Connect' windows are
opened.
4. In the window, 'Connect' select 'Local connection' and then click on 'OK'.
The configuration is loaded to 'SintesoWorks'.
The advancement status is displayed in the 'Create site by uploading from
station(s)' window.
The 'Site properties' window is opened after loading.
5. Change the entries if required and click on 'OK'.
The 'New site confirmation' window opens.
6. Click on 'Yes'.
The 'Site' is opened in SintesoWorks.

36
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
Adapting configuration
6

6.6 Adapting configuration

Adapt the configuration in the 'Site' in SintesoWorks e.g.:
Changing customer texts
Setting the properties and the parameter sets
Changing allocation of 'Zones' and 'Sections'
Configuring controls
Configuring the operating and display units
Configuring the network

You will find information about configuring a 'Site' in document 009078. See
chapter 'Applicable documents'.

See also
Applicable documents [ 11]

6.7 Switch on detector line

1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Detector line ON' command.
The yellow 'ISOLATION' LED goes out.
The detector line is switched on.

6.8 Switching off the detector line

1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Detector line OFF' command.
The yellow 'ISOLATION' LED lights up.
The detector line is switched off.

6.9 Restarting the detector line

1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Restart line' command.
The FDnet detector line is restarted.
The following message is displayed following restart: 'Command executed'.

37
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
6 Read in devices on detector line

6.10 Read in devices on detector line

NOTICE

Incorrect order for reading in a loop

Error when reading in a loop.
The FDnet detector lines are detected as stubs during the first system start-up,
e.g. 'Line' 11, 'Line' 12 (2-digit line number), even if they are connected as a loop.
Always select the first 'Line' to read in a loop, in this case, 'Line' 11. 'Line' 12
is then read in automatically.
After reading in, a loop is indicated with a 1-digit line number, in this case, as
'Line' 1.
Proceed in the same way from 'Line' 21/22 (loop 2) to 'Line' 41/42 (loop 4).

1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Read in installed devices' command.
The FDnet devices are read in.
The following message is shown following successful reading in:
'Command executed'

6.11 Switching off 'Zone'

1. Select 'Topology' > 'Detection tree' > 'Area' > 'Section' > 'Zone' in the main
menu.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Off' command.
The yellow 'ISOLATION' LED lights up.
The 'Zone' is switched off.

6.12 Switching on 'Zone'

1. Select 'Topology' > 'Detection tree' > 'Area' > 'Section' > 'Zone' in the main
menu.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'On' command.
The yellow 'ISOLATION' LED goes out.
The 'Zone' is switched on.

6.13 Detaching the device

If you want to remove a device for good, uninstall the device – and, if necessary,
the base – and connect the wires of the detector line.
You will find more information about installing and uninstalling in the
documentation for the corresponding device.

38
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
Delete the device on Person Machine Interface
6

6.14 Delete the device on Person Machine Interface

1. Mark the corresponding device fault message.
2. Press the 'More Options' softkey.
3. Select the 'Show topology' menu item.
The logical channel is displayed. For some devices, 'Device' is displayed
directly.
4. Press the 'More Options' softkey.
5. Select the 'Jump to link' menu item.
The physical channel is displayed.
6. Press the 'Upper level' softkey.
'Device' is displayed.
7. Press the 'More Options' softkey.
8. Select the 'Execute commands' menu item.
9. Select the 'Remove/delete device' command.
The control panel deletes the physical representation of the removed device.
The logical channel element remains in the 'Zone'.

6.15 Remove the elements

If you have uninstalled an FDnet device for good, the corresponding elements, e.g.
the 'Zone' must be removed from the logical structure trees in SintesoWorks. You
can search for elements using the 'Find' function.
You will find more information in document 009078. See chapter 'Applicable
documents'.

See also
Applicable documents [ 11]

6.16 Switching on test mode

1. Select 'Topology' > 'Detection tree' in the main menu.
2. Select the element you want to switch to test mode: 'Area', 'Section', or 'Zone'
3. Press the 'More Options' softkey and select 'Execute commands'.
4. Select a command from the following table.
The yellow 'DETECTOR TEST' LED lights up.
The element is in test mode.

Element Command

Area 'Non-MCP zones det.test'

'MCP zones det.test'
Section 'Non-MCP zones det.test'
'MCP zones det.test'
Zone 'Detector test'

39
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
6 Switch on normal operation

6.17 Switch on normal operation

There is a shortened procedure for switching individual 'Zones' to normal
operation. The procedure is described in the following section: 'Switching 'Zone' to
normal operation'

Switching 'Area', 'Section' or 'Zone' to normal operation

1. Select 'Topology' > 'Detection tree' in the main menu.
2. Select the element you want to switch to normal operation: 'Area', 'Section' or
'Zone'
3. Press the 'More Options' softkey and select 'Execute commands'.
4. Select a command from the following table.
The element is switched to normal operation.
The yellow 'DETECTOR TEST' LED goes out.

Element Command

Area 'Non-MCP zones det.test END'

'MCP zones det.test END'
Section 'Non-MCP zones det.test END'
'MCP zones det.test END'
Zone 'Detector test END'

Commands under 'Execute commands'

You can also switch to normal operation at superordinate level for the command
in question. Test mode can also be exited in the 'Zone', 'Section', or 'Area', for
example.

Switching 'Zone' to normal operation

There is a shortened procedure for switching individual 'Zones' to normal operation:
1. Select 'Message summary' > 'Test message' in the main menu.
2. Select the displayed 'Zone' in test mode and press the 'Execute Commands'
softkey.
3. Select the 'Detector test END' command.
The 'Zone' is switched to normal operation.
The yellow 'DETECTOR TEST' LED goes out.

40
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 General commissioning steps
Rectify localization errors
6

6.18 Rectify localization errors

1. Use 'Topology' > 'Hardware tree' > 'Station' > 'Line card' > 'Detector line' to
select the corresponding detector line in the main menu.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Accept replaced devices' command.
The fault messages are no longer displayed.

If devices are missing or the device types do not correspond to the FDnet
topology, error messages will continue to be displayed.

6.19 Checking 'Site' function

Test the functions of the 'Site' in the various test modes:
You will find information about testing a 'Site' in the chapter 'Testing' in document
008838. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

6.20 Completion work

1. Check the time and date and reset these. To do this, select
'Settings/administration' > 'System commands' > 'Set system time' in the main
menu.
2. Set the PIN for access levels 1, 2.1, 2.2, and 3. To do this, select
'Settings/administration' > 'LED test' in the main menu.
3. Fit the housing cover.
4. Label the installation plate, which should be outside on the housing, with the
site number and the date of commissioning.
- To do this, use a solvent-resistant pen.

41
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 A - Commissioning stand-alone 'Station' without PC
7 Completion work

7 A - Commissioning stand-alone 'Station'

without PC
The procedure in this chapter is only valid for standalone 'Stations'.

In this commissioning variant, a 'Station' without a PC and a SintesoWorks are

commissioned.

Prerequisites
The detector lines and FDnet devices are installed.
The acceptance test has been carried out for the detector lines.
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not connected.

You will find additional information about the individual steps on the specified
pages.

Commissioning
1. If necessary, configure the power supply. Link [ 43]
2. Prepare the 'Station' for commissioning. Link [ 34]
3. Perform auto-configuration:
- 'Auto-configure 'Station' Link [ 35]
OR
- Auto-configure detector lines individually Link [ 36]
4. Adapt the auto-configuration in the Person Machine Interface, e.g.:
- Changing customer texts. Link [ 43]
- Setting parameter sets of the FDnet devices. Link [ 44]
5. Test the function of the 'Site' and remedy the problems, if any. Link [ 41]
6. Perform the completion tasks. Link [ 41]

42
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 A - Commissioning stand-alone 'Station' without PC
Configuring the power supply
7

7.1 Configuring the power supply

If the 'Station' is equipped with a power supply and batteries, the power supply
does not have to be configured. In all other cases the power supply must be
configured. This may be done by wiring accordingly.
The following table shows the cases in which the monitoring signals of the power
supply must be re-wired.

Operation mode Connector on Connect with

periphery board

Operation without X1 / pin 1 '#BATT' X1 / pin 4 #COMMON

batteries
Operation without power X1 / pin 1 '#BATT' X1 / pin 4 #COMMON
supply unit
X1 / pin 2 '#CONV' X1 / pin 4 #COMMON
X1 / pin 3 '#MAINS' X1 / pin 4 #COMMON

Configuring the power supply

You will find the pin assignments in document 008837. See chapter 'Applicable
documents'.

See also
Applicable documents [ 11]

7.2 Entering customer texts using the Person Machine

Interface
1. Select 'Topology' > 'Detection tree' > 'Area' > 'Section' > 'Zone' in the main
menu.
2. Select the element you want to label with a customer text.
3. Press the 'More Options' softkey and select 'Execute commands'.
4. Select the 'Set customer text' command.
5. Enter the customer text using the numeric keypad.
6. Press <ok> to save the customer text. There is no need to restart the Station.

Showing the customer text on the display

All elements apart from 'Zone':
If a message associated with an element appears, the corresponding customer
text is displayed. If no customer text is assigned to this element, the customer
text of the next superordinate element, e.g. 'Detector' > 'Line' > 'Line card',
appears.
'Zone' element:
If an alarm message for a 'Zone' appears, the customer text of the detector
(sensor) is displayed. The customer text of the 'Zone' appears if no customer
text is assigned to the 'Detector'. The customer text of the next superordinate
element ('Detector' > 'Zone' > 'Section' > 'Area') appears if no customer text is
assigned to the 'Zone' either.

43
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 A - Commissioning stand-alone 'Station' without PC
7 Setting detector parameter sets

7.3 Setting detector parameter sets

1. Select 'Topology' > 'Detection tree' > 'Area' > 'Section' > 'Zone' > 'Detect.' in the
main menu.
2. Press the 'More Options' softkey.
3. Select 'Execute commands'.
4. Select the corresponding command:
- 'Select PS MANNED'
- 'Select PS UNMANNED'
- 'Select PS'
5. Select the desired parameter set.
The following message is displayed: 'Command executed'

44
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 B1 - Commissioning stand-alone 'Station' with PC, without pre-configuration
8

8 B1 - Commissioning stand-alone 'Station' with

PC, without pre-configuration
First auto-configure the 'Station' in this commissioning variant. Then adapt the
auto-configuration manually in SintesoWorks.

The procedure in this chapter applies exclusively to standalone 'Stations' and is

only valid forFDnet detector lines.

Prerequisites
The detector lines and FDnet devices are installed.
The acceptance test has been carried out for the detector lines.
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The current firmware and BDV are available on the PC.

You will find additional information about the individual steps on the specified
pages.

Commissioning
1. Prepare the 'Station' for commissioning. Link [ 34]
2. Perform auto-configuration:
- Auto-configure 'Station'. Link [ 35]
OR
- Auto-configure detector lines individually. Link [ 36]
3. Connect the PC to the 'Station'. Link [ 25]
4. Load the automatically created configuration to the PC. Link [ 36]
5. Adapt the configuration in SintesoWorks. Link [ 37]
6. Load the configuration from the PC to the 'Station'. Link [ 28]
7. Test the function of the 'Site'. Link [ 41]
8. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
9. Disconnect the PC from the 'Station'. Link [ 25]
10. Perform the completion tasks. Link [ 41]

45
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 B2 - Commissioning stand-alone 'Station' with PC, with pre-configuration
9

9 B2 - Commissioning stand-alone 'Station' with

PC, with pre-configuration
The procedure in this chapter is only valid for FDnet detector lines.

In this commissioning variant, in,SintesoWorks, first manually configure a 'Site' up

to 'Line' level. Then read in the FDnet devices and adapt the configuration
manually in SintesoWorks.

Prerequisites
The detector lines and FDnet devices are installed.
The acceptance test has been carried out for the detector lines.
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The current firmware and BDV are available on the PC.

You will find additional information about the individual steps on the specified
pages.

Commissioning
1. In SintesoWorks create a 'Site' and configure it manually to the 'Zone' level.
2. Prepare the 'Station' for commissioning - without BDV installation. Link [ 35]
3. Connect the PC to the 'Station'. Link [ 25]
4. Load the configuration from the PC to the 'Station'. Link [ 28]
5. Read-in the FDnet devices. Link [ 38]
6. Load the configuration from the 'Station' to the PC. Link [ 30]
7. Adapt the configuration in SintesoWorks. Link [ 37]
8. Load the configuration from the PC to the 'Station'. Link [ 28]
9. Test the function of the 'Site'. Link [ 41]
10. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
11. Disconnect the PC from the 'Station'. Link [ 25]
12. Perform the completion tasks. Link [ 41]

46
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 C- Commissioning networked 'Stations'
10

10 C- Commissioning networked 'Stations'

NOTICE

Commissioning as standalone 'Station'

Commissioned as standalone'Station', Stations' cannot be combined to form a
networked 'Site' later on.
Initialize networked 'Stations' using a network address right from the start.

Prerequisites
The detector lines and FDnet devices are installed.
The acceptance test has been carried out for the detector lines.
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The current firmware and BDV are available on the PC.

You will find additional information about the individual steps on the specified
pages.

Commissioning
1. Create a 'Site' and the 'Stations' in SintesoWorks and pre-configure, if required.
2. Prepare each 'Station' individually for commissioning - without BDV installation.
Link [ 35]
3. Connect the PC to each 'Station' individually. Link [ 25]
4. Initialize each 'Station' individually. Link [ 26]
5. Read-in the FDnet devices for all 'Stations'. Link [ 38]
6. Load the configuration from the 'Station' to the PC. Link [ 30]
7. Adapt the configuration in SintesoWorks. Link [ 37]
8. Load the configuration from the PC to the 'Station'. Link [ 28]
9. Test the function of the 'Site'. Link [ 41]
10. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
11. Disconnect the PC from the 'Station'. Link [ 25]
12. Perform the completion tasks. Link [ 41]

47
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning FC2080
11

11 Commissioning FC2080
Because of the fact that the FC2080 fire control panel has no integrated operating
unit, you must configure at least one operating unit within the 'Site' in such a way
that it has a visibility of the FC2080.

Commissioning
1. Create a 'Site' and the 'Stations' in SintesoWorks and pre-configure, if required.
2. Configure the visibility of the FC2080 in SintesoWorks. You will find information
on this in the following chapter.
3. Follow the commissioning steps in chapter 'C- Commissioning networked
'Stations' [ 47]'.

Configuring visibility on FC2080

Configuring visibility on FC2080

The 'FC2080' element is present in the structure tree.

The 'Stations' that are to have a visibility of the FC2080 are present in the
structure tree.
1. Select the 'Operation' task card.
2. In the tree view, open the 'Station' that is to have a visibility of the FC2080.
3. Open the 'PMI' window and highlight the 'Standard visibility' element.
4. In the menu bar, click on 'Assign'.
The 'Assign dialog' window opens.
5. Select the desired visibility on the left in the window.
6. On the right in the window, select the 'FC2080' element.
7. Click on 'Assign'.
The visibility on the FC2080 is configured.

48
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning FG2020
12

12 Commissioning FG2020
Because of the fact that the FG2020 has no integrated operating unit, you must
configure at least one operating unit of the 'Site' in such a way that it has a visibility
of the FG2020.

Commissioning
1. Create a 'Site' and the 'Stations' in SintesoWorks and pre-configure, if required.
2. Configure the visibility of the FG2020 in SintesoWorks. You will find information
on this in the following chapter.
3. Follow the commissioning steps in chapter 'C- Commissioning networked
'Stations' [ 47]'.

Configuring visibility on FG2020

Assigning a visibility

The 'FG2020' element is created.

The 'Stations' that are to have visibility of the SIGMASYS control panel are
created.
1. Select the 'Operation' task card.
2. In the tree view, open the 'Station' that is to have visibility of the SIGMASYS
control panel.
3. Open the 'PMI' window and highlight the 'Standard visibility' element.
4. In the menu bar, click on 'Assign'.
The 'Assign dialog' window opens.
5. Select the desired visibility on the left in the window.
6. On the right in the window, select the corresponding element.
7. Click on 'Assign'.
The element is assigned with 'Standard visibility'.

49
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Adding a 'Station' to an existing 'Site'
13

13 Adding a 'Station' to an existing 'Site'

Prerequisites
The detector lines and FDnet devices are installed.
The acceptance test has been carried out for the detector lines.
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The current firmware and BDV are available on the PC.

You will find additional information about the individual steps on the specified
pages.

Commissioning
1. In SintesoWorks, create the 'Station' to be integrated and configure it, if
required.
2. Prepare the 'Station' for commissioning - without BDV installation. Link [ 35]
3. Connect the PC to the 'Station'. Link [ 25]
4. Initialize the 'Station'. Link [ 26]
5. Read-in the FDnet devices. Link [ 38]
6. Load the configuration from the 'Station' to the PC. Link [ 30]
7. Adapt the configuration in SintesoWorks. Link [ 37]
8. Load the configuration from the PC to the 'Station'. Link [ 28]
9. Test the function of the 'Site'. Link [ 41]
10. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
11. Disconnect the PC from the 'Station'. Link [ 25]
12. Perform the completion tasks. Link [ 41]

50
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning Ethernet switch (MM) FN2008-A1
Setting detector parameter sets
14

14 Commissioning Ethernet switch (MM)

FN2008-A1
This description focuses on correctly integrating the 'Ethernet switch (MM)
FN2008-A1' in the fire detection installation. More information about the product
can be found on the data carrier in the scope of supply and at the following
address: http://support.automation.siemens.com (Manufacturer designation:
Scalance X204-2)

NOTICE

Alternate products for 'Ethernet switch (MM) FN2008-A1'

No compliance with EN 54
For an EN-54-compliant fire detection installation, you must use the permitted
'Ethernet switch (MM) FN2008-A1'.

The 'Ethernet switch (MM) FN2008-A1' is a class A equipment and may cause
radio interference in residential areas. If interference does occur, observe the
relevant information in document 008851. See chapter 'Applicable documents'.

Commissioning
1. Install the 'Primary Setup Tool' software. Link [ 52]
2. Assign the IP address. Link [ 52]
3. Configure FN2008-A1 using the Internet browser Link [ 53]
4. In SintesoWorks, create the links you want e.g. for the following monitoring
functions in a 'Technical zone'.
- Redundant power
- Display error contact

You will find detailed instructions on creating a link in document 009078 See
chapter 'Applicable documents'.

The FN2008-A1 has no IP address in the factory setting. You must manually
assign the IP address.

51
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning Ethernet switch (MM) FN2008-A1
14 Install Primary Setup Tool

14.1 Install Primary Setup Tool

The 'Primary Setup Tool' software is included in the scope of supply for the
FN2008-A1.

Start 'Primary Setup Tool' installation.

Primary Setup Tool is installed.
The DLC and PROFINET RT protocols are installed.
Primary Setup Tool recognizes one or more connected FN2008-A1 without IP
address via the DLC protocol.

The FN2008-A1 is displayed as X204-2 in the Primary Setup Tool.

14.2 Assign IP address

The FN2008-A1 is displayed as X204-2 in the Primary Setup Tool.

Primary Setup Tool is installed on the PC.

Several FN2008-A1 are physically linked in the system.
1. Connect the PC to any available FN2008-A1 port P1...P4 using a network
cable.
2. Start the Primary Setup Tool via 'Start' > 'Programs' > 'Simatic'.
Primary Setup Tool lists one or more FN2008-A1 (X204-2).
3. Select each FN2008-A1 one after the other and issue a unique IP address
(192.168.1.xxx) to each FN2008-A1.
4. Click on the connected FN2008-A1 in the tree view and select the 'Load' menu
item.
The assigned IP address is saved to the FN2008-A1.
5. Repeat the 'Load' process for each FN2008-A1.
Each FN2008-A1 in the system has an individual IP address.

52
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning Ethernet switch (MM) FN2008-A1
Configure FN2008-A1 using Internet browser
14

14.3 Configure FN2008-A1 using Internet browser

A configuration is available via the localization manager. We recommend using
the configuration and if necessary making system-specific adaptations.

NOTICE

Incorrect settings of the ports

Malfunction
The factory setting 'auto-negotiation' for the ports may not be changed.

1. Open the Internet browser and enter the FN2008-A1's address in the address
field.
The login window opens.
2. Login:
- User name = 'admin'
- Password = 'admin'
3. Select 'System' > 'Passwords' in the tree view and set a new password for the
following fields:
- 'New User Password'
- 'New Admin Password'
4. Confirm the entered password with 'Confirmation'.
5. Click 'Set Values'.
6. Select 'X204-2' > 'Ring' in the tree view and check the 'Enable ring redundancy'
checkbox.
- Select the 'Automatic Redundancy Detection' redundancy mode.
7. Select 'X204-2' > 'Fault Mask' in the tree view and check the
'Enable Link Down Monitoring' checkbox for each connected port:
- Port 5 and 6 = Ring
- Port 1 = The connected 'Station'
- Port 2 to 4 only if more stations 'Stations' are connected
FN2008-A1 is configured.

53
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
15 Configure FN2008-A1 using Internet browser

15 Commissioning safety module (firewall)

FN2009-A1
This description focuses on correctly configuring and integrating the 'Security
module (firewall) FN2009-A1' in the fire detection installation. More information
about the product can be found on the data carrier in the scope of supply and at
the following address: http://support.automation.siemens.com (Manufacturer
designation: Scalance S612)

A configuration is available via the localization manager. We recommend using

the configuration and if necessary making system-specific adaptations.

Commissioning
1. Install the 'Security Configuration Tool' software. Link [ 55]
2. Select the type and enter the MAC address. Link [ 55]
3. Enter the network settings. Link [ 56]
- Load configuration.
4. Create IP service definitions. Link [ 59]
5. Create firewall rules. Link [ 60]
- Load configuration.

The 'Security module (firewall) FN2009-A1' is a class A equipment and may

cause radio interference in residential areas. If interference does occur, observe
the relevant information in document 008851. See chapter 'Applicable
documents'.

The FN2009-A1 has no IP address in the factory setting. You must manually
assign the IP address.

NOTICE

FN2009-A1 is not in the factory setting and already has an IP address

It is not possible to upload a new configuration
Press the Reset button on the live FN2009-A1.

54
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
Installing Security Configuration Tool
15

15.1 Installing Security Configuration Tool

The 'Security Configuration Tool' software is included in the scope of supply for
the FN2009-A1.

Install the 'Security Configuration Tool' software.

The software is installed in the standard path 'SIMATIC' > 'SCALANCE' >
'Security' > 'Security Configuration Tool'.
FN2009-A1 can be configured.

The FN2009-A1 is displayed as S612V2 in the Security Configuration Tool.

15.2 Selecting type and entering MAC address

The corresponding MAC address can be found on the front of the FN2009-A1.
The FN2009-A1 is type S612V2.

Preparation
The PC is connected to FN2009-A1.
'Security Configuration Tool' is started.
1. Create a new project using the 'Project' > 'New' menu and enter the
administrative project data, 'User name' and 'Password'.
2. Save the new project.
3. Select 'View' > 'Advanced Mode'.
More entry masks for required settings can be viewed.

Selecting type
1. Highlight the field below the 'Type' designation.
The button for the dropdown list field is displayed.

2. Select 'S612V2'.
Type is selected.

55
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
15 Entering network settings

Entering MAC address

The MAC address is known.
1. Double-click on the field below the 'MAC Address' designation.
The MAC address can be edited.

2. Enter the MAC address for the FN2009-A1.

MAC address is entered.

15.3 Entering network settings

The network topology is known.
'Advanced Mode' is selected.
Enter the network settings in the following order:
- External IP address 'IP Address ext.'
- Routing mode 'Routing Mode'
- Router network data 'Router'
- Load the network settings to FN2009-A1.

Entering external IP address, 'IP Address ext.'

1. Double-click on the field below the 'IP Address ext.' designation.
The external IP address for the FN2009-A1 can be edited.
2. Enter the following IP address: 10.169.29.80.

Entering routing mode, 'Routing Mode'

The following settings apply for the planned network access to GAP with activated
DHCP server.
'192.168.201.X' must be changed accordingly for network access to the standby
router or with IP address details.

'Module 1' is highlighted in the 'View' window.

1. Press <F4> on the keyboard or open the 'Edit' > 'Properties' menu.
The 'Module Properties' window is displayed:

56
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
Entering network settings
15

2. Select the 'Routing Mode' tab.

The following entry mask is displayed:

3. Check the 'Routing active' checkbox.

4. Enter the following 'internal module IP address': 192.168.201.2.
5. Confirm input with 'OK'.
'Internal sub-net mask' is automatically created.
'Routing Mode' is active.

57
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
15 Entering network settings

Entering router network data, 'Router'

The following settings apply for the planned network access to GAP with activated
DHCP server.

1. Open the 'Module Properties' window again.

The 'Network' tab is displayed.
2. Click on 'Add Router'.
The 'Sub-net Mask' '255.255.255.0' is already entered.
3. Correct the 'Sub-net Mask' from '255.255.255.0' to '255.255.0.0'.
4. Enter the following network data:
- 'Router IP': 192.168.201.1
- 'Network ID': 192.168.0.0
5. Confirm input with 'OK'.
The router network data is entered.

Load the network settings to FN2009-A1.

MAC address is entered.
IP addresses are entered.
1. Highlight the FN2009-A1 module in the project.
2. Select the 'Transfer > 'To Module' menu.
The network settings are loaded to FN2009-A1.
Network settings are entered.

58
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
Creating IP service definitions
15

15.4 Creating IP service definitions

NOTICE

Different BACnet port settings in FN2009-A1 and SintesoWorks

No communication possible
Configure the same BACnet port in FN2009-A1 and SintesoWorks.

1. Open the 'Options' > 'IP Service Definitions' menu.

The 'IP Service Definitions' window is opened.

2. Select the 'IP Services' tab.

3. Click on 'Add IP Service'.
One row can be edited for one IP service.
4. Enter the two IP services required as shown in the figure above:
- 'Name': Tool, 'Protocol': udp, 'Source Port': *, 'Target Port': 51000
- 'Name': BACnet, 'Protocol': udp, 'Source Port': *, 'Target Port': 47808
Required IP services are created.
5. Select the 'ICMP' tab.
6. Click on 'Add ICMP Service'.
One row can be edited for one ICMP service.
7. Enter the two optional ICMP services required as shown in the figure below:
- 'Name': ICMP0, 'Type': Echo Request, 'Code': No code
- 'Name': ICMP1, 'Type': Echo Reply, 'Code': No code
Optional IP services are created.

59
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
15 Creating firewall rules

8. Confirm input with 'OK'.

'IP Service Definitions' are created.

15.5 Creating firewall rules

IP service definitions are created.
The network addresses are known.
1. Right-click on the module for which you want to create firewall rules.

2. Select 'Properties…'.
The 'Module Properties' window for the selected module is displayed:

60
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning safety module (firewall) FN2009-A1
Creating firewall rules
15

3. Select the 'Firewall Settings' tab.

The following window is displayed without entries:

4. Click on 'Add Rule' for each firewall rule you would like to create.
5. Select the corresponding settings and IP services from the dropdown list fields.
6. Enter the required IP addresses.
7. Confirm input with 'OK'.
The firewall rules are created.

Loading the firewall rules to FN2009-A1

The firewall rules are created.
1. Highlight the FN2009-A1 module in the project.
2. Select the 'Transfer > 'To Module' menu item.
The firewall rules are loaded to FN2009-A1.

61
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Merging two 'Sites'
16 Creating firewall rules

16 Merging two 'Sites'

You can merge two 'Sites' to form one 'Site'.

Prerequisites
Both 'Sites' are in the same organizational unit.
Both 'Sites' have the same firmware version and BDV version (version 32 or
higher)
Both 'Sites' have one network.
Both 'Sites' combined have at most the allowed number of 'Stations' for a 'Site'.
Both 'Sites' combined have at most the allowed number of SAFEDLINK sub-
nets for a 'Site'.
Wiring between the two 'Sites' is prepared:
– The 'Ethernet switch (MM) FN2008-A1' is installed in the 'Stations' intended
as router station and connected to an optical network (FCnet/LAN).
– Large SAFEDLINK sub-nets are in the original state and not yet divided.
– Ethernet sub-net are in the original state.

You will find additional information about the individual steps on the specified
pages.

Commissioning
1. Add Site' B to 'Site' A. Link [ 63]
2. Initialize all 'Stations' that have a new address. Link [ 26]
3. Load the configuration of all 'Stations' in 'Site' A from the PC to the 'Station'.
Link [ 28]
4. Connect the 'Sites' physically to one another. Link [ 64]
5. Load the configuration of the merged 'Site' from the 'Station' to the PC. Link
30]
6. Adapt the configuration in SintesoWorks. Link [ 37]
7. Load the configuration from the PC to the 'Station'. Link [ 28]
8. Test the function of the 'Site'. Link [ 41]
9. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]

62
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Merging two 'Sites'
Adding 'Site' B to 'Site' A
16

16.1 Adding 'Site' B to 'Site' A

'Site' A is opened in SintesoWorks.
1. In the 'Edit' menu, select the 'Merge sites' menu item.
The following window is opened:

A
B

2. Enter the path and name of 'Site' B that you would like to merge with 'Site' A.
3. Enter the path and name of the new merged 'Site'.
4. Click on 'Next'.
The conditions for merging are checked.
The results are listed in the window below:

5. Click on 'Next' if 'ok' is everywhere in the 'Result' column. If 'ok' is not

everywhere, click on 'Cancel' and ensure that all the conditions that are listed in
the 'Check' column are satisfied.
SintesoWorks checks whether there are address conflicts at 'Stations'
levels and suggests a possible new address.

63
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Merging two 'Sites'
16 Connecting 'Sites' physically to one another

6. Check the suggested addresses for the 'Stations' in 'Site' B and adapt them if
necessary. The 'New address' column can be edited.
7. Check the 'Reconfigure network' checkbox if you want to reset the existing
network configurations for the original 'Sites'. All network configuration values
are then reset to the standard values.
8. Click on 'Finish'.
The 'Sites' are merged.
The following window is opened. In the 'Required action' column, you are
shown which 'Stations' need initializing and for which 'Stations' a download
is sufficient.

9. Click on 'Show the log file.' to view the protocol.

10. Click on 'Save report as file...' to save and print a merging report. This report
also shows which 'Stations' must be initialized.
11. Click on the 'OK' button to close the window.

16.2 Connecting 'Sites' physically to one another

Connect the two 'Sites' physically to one another.
You will find more information in document 008851. See chapter 'Applicable
documents'.
See also
Applicable documents [ 11]

64
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
Extending the detector line to include additional devices
17

17 Changing and expanding the FDnet/C-NET

detector line

17.1 Extending the detector line to include additional

devices

NOTICE

Incorrect assignment between detector/detector group and customer text

Inaccurate messages in the event of an alarm
You must not change the FDnet topology at the same time as adding extra
devices.
After extending or changing a Site always run a test to check the assignment
between detector/detector group and customer text.

You will find additional information about the individual steps on the specified
pages.

1. Switch the FDnet detector line off. Link [ 37]

2. Fit and wire the new devices. Link [ 65]
3. Read-in the FDnet devices. Link [ 38]
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the 'Station' to the PC. Link [ 30]
6. Configure the new devices. Link [ 66]
7. Load the configuration from the PC to the 'Station'. Link [ 28]
8. Test the function of the 'Site'. Link [ 41]
9. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
10. Disconnect the PC from the 'Station'. Link [ 25]

17.1.1 Mount and wire new devices

During an extension of the line, all possible wiring work on the bases must be
carried out from devices that have already been localized. When replacing these
devices, these must be re-inserted in exactly the same place (observe the serial
number).
1. Remove these devices from their bases.
2. Fit and wire the new devices, like bases.
3. Insert the new devices into the new bases and write down the serial numbers
on the layout plan.

65
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
17 Replacing stationary devices of the same type

17.1.2 Configure a new device

1. Extend the configuration in SintesoWorks, e.g.in the 'Detection tree'.
2. Allocate the read-in devices to the elements of the detection tree or the control
tree in SintesoWorks.
3. If required, configure additional 'Controls' (also for several 'Stations') using the
layout plan or finalize available 'Controls'.

17.2 Replacing stationary devices of the same type

NOTICE

Incorrect assignment between detector/detector group and customer text

Inaccurate messages in the event of an alarm
You must not change the FDnet topology at the same time as adding extra
devices.
After extending or changing a Site always run a test to check the assignment
between detector/detector group and customer text.

You will find additional information about the individual steps on the specified
pages.

1. Switch the FDnet detector line off. Link [ 37]

2. Replace the FDnet device with a device of the same type. Several devices can
be replaced.
3. Rectify localization errors. Link [ 41]
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the 'Station' to the PC. Link [ 30]
6. Test the function of the 'Site'. Link [ 41]
7. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
8. Disconnect the PC from the 'Station'. Link [ 25]
You will find information about installing and uninstalling in the documentation for
the corresponding 'FDnet' device.
Refer to documents 009865 and A6V10227639 for information on how to replace
radio detectors. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

66
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
Permanently removing stationary devices
17

17.3 Permanently removing stationary devices

You will find additional information about the individual steps on the specified
pages.

1. Switch the FDnet detector line off. Link [ 37]

2. Remove the FDnet devices. Link [ 38]
3. Switch the FDnet detector line on. Link [ 37]
The control panel reports a 'Fault' per missing device.
4. Delete the FDnet devices on the Person Machine Interface. Link [ 39]
5. Connect the PC to the 'Station'. Link [ 25]
6. Load the configuration from the 'Station' to the PC. Link [ 30]
7. Remove the logical elements in SintesoWorks. Link [ 39]
8. Load the configuration from the PC to the 'Station'. Link [ 28]
9. Disconnect the PC from the 'Station'. Link [ 25]

17.4 Removing or replacing non-stationary devices

17.4.1 Temporarily removing an individual non-stationary device

It may be possible that an FDnet device must be temporarily removed from the
base. Afterwards the same FDnet device must be re-inserted at exactly the same
place in the FDnet.
1. Remove the FDnet device.
The control panel detects that the FDnet device is missing and reports a
'Fault'.
2. Perform the necessary activities.
3. Re-insert the FDnet device in the FDnet in the same, previous position.
4. Acknowledge the 'Fault'.
If this 'Fault' is no longer displayed, the control panel updates the settings of
the re-inserted FDnet device.
If this 'Fault' is still displayed, and/or the detector line is not in normal operation,
the 'detector line' has to be restarted.

The work described in this chapter may be performed when the FDnet detector
line is switched on.

See also
Restarting the detector line [ 37]

67
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
17 Removing or replacing non-stationary devices

17.4.2 Temporarily removing multiple non-stationary devices

For the purpose of painting work, it may be necessary to temporarily remove the
FDnet devices in a room. Each FDnet device must then be re-inserted in its original
base. The FDnet devices may not be exchanged.

You will find additional information about the individual steps on the specified
pages.

Mark the allocation of the devices to the respective base to avoid additional work
steps.

1. Switch the 'Zone' off. Link [ 38]

2. Remove the FDnet devices from the base and insert the dummy detector if
necessary.
3. Perform the tasks.
4. Re-insert the FDnet devices to the respective position.
5. Switch the 'Zone' on. Link [ 38]
For all the re-inserted FDnet devices, a localization fault is displayed.
6. Restart the FDnet detector line. Link [ 37]
If detectors have been swapped over or are missing, the following messages are
shown on the display of the Person Machine Interface:
'Zone', 'Serial no. ("ID-Nr.")', 'Dev.location fault'

The work described in this chapter may be performed when the FDnet detector
line is switched on.

17.4.3 Permanently removing non-stationary devices

You will find additional information about the individual steps on the specified
pages.

1. Switch the FDnet detector line off. Link [ 37]

2. Remove the FDnet devices and their bases. Link [ 38]
3. Switch the FDnet detector line on. Link [ 37]
4. Delete the FDnet devices individually via the Person Machine Interface on the
control panel. Link [ 39]
5. Connect the PC to the 'Station'. Link [ 25]
6. Load the configuration from the 'Station' to the PC. Link [ 30]
7. Remove the logical elements in SintesoWorks. Link [ 39]
8. Load the configuration from the PC to the 'Station'. Link [ 28]
9. Disconnect the PC from the 'Station'. Link [ 25]

68
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
Removing or replacing non-stationary devices
17

17.4.4 Replacing non-stationary devices of the same type

You will find additional information about the individual steps on the specified
pages.

1. Switch the test mode on. Link [ 39]

2. Replace the FDnet device. Link [ 69]
3. Switch normal operation on. Link [ 40]
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the 'Station' to the PC. Link [ 30]
6. Disconnect the PC from the 'Station'. Link [ 25]

The work described in this chapter may be performed when the FDnet detector
line is switched on.

17.4.5 Replacing a device

1. Remove the device you want to replace from the base.
2. Wait approx. 20 seconds.
3. Insert the new device of the same type.
The internal alarm indicator flashes for 10 seconds following successful
replacement.
Proceed as follows if the alarm indicator does not flash:
1. Ensure that you wait long enough before inserting.
2. Check whether other devices are missing on the detector line.
3. Check whether a device that is not of the same type has been inserted. If this is
the case, insert a device of the same type.
4. Restart the line.

17.4.6 Replacing non-stationary devices of different types

You will find additional information about the individual steps on the specified
pages.

1. Remove the FDnet device from its base.

The 'Station' detects that the device is missing and reports a 'Fault'.
2. Delete the FDnet device individually on the Person Machine Interface on the
control panel. Link [ 39]
3. Insert the new FDnet device in the base.
4. Read-in the FDnet devices. Link [ 38]
5. Connect the PC to the 'Station'. Link [ 25]
6. Load the configuration from the 'Station' to the PC. Link [ 30]
7. Replace the FDnet device in the 'Zone'. Link [ 70]
8. Load the configuration from the PC to the 'Station'. Link [ 28]
9. Disconnect the PC from the 'Station'. Link [ 25]

69
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
17 Replacing 'Manual call point' of the same type

The work described in this chapter may be performed when the FDnet detector
line is switched on.

17.4.6.1 Replacing a device in the 'Zone'

1. Select the 'Zone' in which you have replaced a device in SintesoWorks. The
'Find' or 'Find and replace' functions can be used to do this.
2. Replace the FDnet device.
You will find more information in document 009078. See chapter 'Applicable
documents'.

See also
Applicable documents [ 11]

17.5 Replacing 'Manual call point' of the same type

NOTICE

Incorrect assignment between detector/detector group and customer text

Inaccurate messages in the event of an alarm
You must not change the FDnet topology at the same time as adding extra
devices.
After extending or changing a Site always run a test to check the assignment
between detector/detector group and customer text.

You will find additional information about the individual steps on the specified
pages.

1. Switch on the replace mode. Link [ 71]

2. Replace the 'Manual call point' with a 'Manual call point' of the same type.
3. Switch off the replace mode. Link [ 71]
4. Test the 'Manual call point'. Link [ 71]
5. Switch normal operation on. Link [ 40]
6. Connect the PC to the 'Station'. Link [ 25]
7. Load the configuration from the 'Station' to the PC. Link [ 30]
8. Test the function of the 'Site'. Link [ 41]
9. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
10. Disconnect the PC from the 'Station'. Link [ 25]
You will find more information about installing and uninstalling in the
documentation for the corresponding 'Manual call point'.

70
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
Replacing 'Manual call point' of the same type
17

17.5.1 Switching on the replace mode

1. Select 'Functions' > 'All functions' > 'Detector' in the main menu.
2. In the 'Zone', enter the 'Zone' address and press <ok>.
3. Enter the detector address in 'Detect.' and press <ok>.
4. Select the 'Device replace mode ON' menu item.
The following message is shown following successful switching on: 'Command
executed'.
The yellow 'ISOLATION' LED lights up.
The detector line is de-energized.

17.5.2 Switching off replace mode

1. Select 'Functions' > 'All functions' > 'Detector' in the main menu.
2. Enter the zone address in 'Zone' and press <ok>.
3. Enter the detector address in 'Detect.' and press <ok>.
4. Select the 'Device replace mode OFF' menu item.
The following message is shown following successful switching off: 'Command
executed'.
The yellow 'ISOLATION' LED goes out.
The yellow 'DETECTOR TEST' LED lights up.
The 'Manual call point' is in test mode.

17.5.3 Testing 'Manual call point'

1. Check whether the 'Manual call point' is in test mode using the LED.
2. Activate the 'Manual call point' using the corresponding tools.
You will find information about this in the 'Manual call point' documentation.

71
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the FDnet/C-NET detector line
17 Convert two stubs into a loop

17.6 Convert two stubs into a loop

You will find additional information about the individual steps on the specified
pages.

The two stubs are assigned to the same line pair, e.g. 'Line' 11 and 'Line' 12.
1. Switch both the FDnet detector lines off. Link [ 37]
2. Wire both stubs to a loop. You will find more information about this in document
008851. See chapter 'Applicable documents'.
3. Read-in the FDnet devices. Link [ 38] Start with the first 'Line' (in the example
'Line' 11).
The second 'Line' is adopted and the loop is formed (in this example,
'Line' 1).
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the 'Station' to the PC. Link [ 30]
6. Test the function of the 'Site'. Link [ 41]
7. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
8. Disconnect the PC from the 'Station'. Link [ 25]

17.7 Connecting a sub-stub to a loop

You will find additional information about the individual steps on the specified
pages.

1. Switch the FDnet detector line off. Link [ 37]

2. Physically connect the sub-stub to the loop. You will find more information
about this in document 008851. See chapter 'Applicable documents'.
3. Read-in the FDnet devices. Link [ 38]
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the 'Station' to the PC. Link [ 30]
6. Test the function of the 'Site'. Link [ 41]
7. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
8. Disconnect the PC from the 'Station'. Link [ 25]

72
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning the control panel with MS9i detector lines
18

18 Commissioning the control panel with MS9i

detector lines
Prerequisites
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The current firmware and BDV are available on the PC.

You will find additional information about the individual steps on the specified
pages.

Commissioning steps
1. Create the pre-configuration of the MS9i detector line. You will find more
information in document 009078. See chapter 'Applicable documents'.
2. Prepare the 'Station' for commissioning - without BDV installation. Link [ 35]
3. Connect the PC to the 'Station'. Link [ 25]
4. Load the configuration from the PC to the 'Station'. Link [ 28]
5. Test the function of the 'Site'. Link [ 41]
6. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
7. Disconnect the PC from the 'Station'. Link [ 25]
8. Perform the completion tasks. Link [ 41]

73
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning control panel with collective detector lines
19 Pre-configuration

19 Commissioning control panel with collective

detector lines
Prerequisites
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The current firmware and BDV are available on the PC.

You will find additional information about the individual steps on the specified
pages.

Commissioning
1. Create the pre-configuration. Link [ 74]
2. Prepare the 'Station' for commissioning - without BDV installation. Link [ 35]
3. Connect the PC to the 'Station'. Link [ 25]
4. Load the configuration from the PC to the 'Station'. Link [ 28]
5. Test the function of the 'Site'. Link [ 41]
6. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
7. Disconnect the PC from the 'Station'. Link [ 25]
8. Perform the completion tasks. Link [ 41]

19.1 Pre-configuration
1. Create a 'Site' and the 'Station' FC2030 or FC2060 including customer text in
SintesoWorks.
2. Adapt the parameters, such as the configuration for the power supply, of the
'Station' in SintesoWorks if required.
3. Create the line card (collective) in the 'Hardware' task card.
4. Configure each individual collective detector line: Define the line type with end
element, 'Pulse memory', etc.
5. Create the 'Detection tree' as far as 'Zone' level in the 'Detection' task card.
6. Assign the 'Detection tree' to the 'Control tree' and the 'Hardware tree'.

You will find information about configuring collective detector lines in document
009078. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

74
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning control panel with collective detector lines
Reference measurement with EOL 4k7 and 3k3
19

19.2 Reference measurement with EOL 4k7 and 3k3

A reference measurement is performed each time a collective detector line is
started up if the end-of-line element (EOL) 4k7 or 3k3 is used.
If the cause of a fault, e.g. removal of a device for testing purposes, is not rectified
before the collective detector line is started up again, 'Line fault' is displayed.
The collective detector line is started up again after e.g. the following situations:
Test alarm
Resetting an alarm
'Zone'
'Exit Detector test
'Exit Installation test

See also
'Line Fault' error message [ 76]

19.3 Possible error messages

If FD20 multiple protocol detectors are operated on a line card (collective), a
short-circuit on the stub is indicated as an 'Open line'. This is because the
separator of the multiple protocol detector opens in a short-circuit. The 'Line' is
open and the short-circuit is isolated.

The following error messages may appear when collective detector lines are being
operated:
'Open line'
– The end-of-line element is not recognized or a detector or base is
defective.
– The collective detector line is no longer used. If the collective detector line
is no longer used, you must select the 'Not configured' setting in the detail
editor of the collective detector line for 'Collective line type' in
SintesoWorks.
'Line fault'
– Error message from detector, base or line due to a change in line
resistance. The cause may be a creeping short-circuit or an open line
which results in the detectors consuming irregular amounts of power or the
resistance value of the end-of-line element changing.
'No line supply'
– Problems with the hardware on this 'Line' or an external supply on this
'Line'
– Incorrectly cabled lines, e.g. L1+ commutation with L2- and L1-
commutation with L2+

See also
Troubleshooting procedure [ 76]

75
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning control panel with collective detector lines
19 Troubleshooting procedure

19.3.1 'Line Fault' error message

If the error message 'Line fault' is displayed for collective detector lines once the
'Station' has started, the cause may be a change in line resistance.
Greater resistance, e.g. due to corrosion of the base connections or faulty end-
of-line element:
Less resistance e.g. due to a defective 'Detector' or a faulty end-of-line element

See also
Reference measurement with EOL 4k7 and 3k3 [ 75]
Checking line resistance [ 77]

19.4 Troubleshooting procedure

You will find additional information about the individual steps on the specified
pages.

1. Test the collective detector line. Link [ 76]

2. Test the line resistance. Link [ 77]
3. Test the line continuity. Link [ 77]
4. Measure the insulation values. Link [ 77]
5. Commission the collective detector line step-by-step. Link [ 78]

19.4.1 Checking the collective detector line

When testing collective detector lines on the line card (collective) FCL2002, you
must observe the following points:
Detectors must not be triggered too soon after each other.
The total time required to check a collective detector is 50 s.
Once a detector has been triggered, the internal alarm indicator flashes for 15 s
and the line is automatically reset.
The length of time after which the line is ready for the next detector to be
triggered varies depending on the line type.

Type Total time required

Transzorb 45 s

EOL22Ex 40 s

EOL 4k7 50 s

EOl 3k3 50 s

Total time required to check a collective detector

76
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning control panel with collective detector lines
Troubleshooting procedure
19

19.4.2 Checking line resistance

To check the line resistance, a universal measuring instrument with internal

resistance of >20 k /V, a voltage range of 15 V to 30 V and a resistance range of
10 k to 10 M is required.

The 'Station' is in operation and the display shows the 'Line fault' error
message.
1. Switch the collective detector line off and on again.
- If the error message reappears within approx. 30 s., check the end-of-line
element for the following criteria: Correct end-of-line element, visual check
for corrosion, resistance value (3.3 k or. 4.7 k ), tolerances.
- If the error message reappears at a resistance value of 3.3 k and 4.7 k
hours, days or weeks later, check the line specifications, base contacts and
'Detectors' for creeping short-circuit or open line. The detector line could be
in the gray zone.
2. Once a recognized fault has been rectified, switch the collective detector line
off and on again.
3. If the error message reappears, continue with the tests and measurements in
the following chapters.

19.4.3 Checking the line continuity

1. Switch the 'Line' off.
2. Remove all 'Detectors' from bases and put base covers in their place.
3. Remove the wires from the connections on the line card.
4. Release the end-of-line element from the connection terminal.
5. Create a short-circuit at the end of the collective detector line.
6. Use the ohmmeter or a test buzzer to check for continuity at the maximum
permitted line resistance.
7. Rectify a recognized fault.
8. Reinsert the end-of-line element, rectify the short-circuit and reinsert the
'Detectors'.

19.4.4 Measuring insulation values

1. Switch the 'Line' off.
2. Remove all 'Detectors' from bases and put base covers in their place.
3. Remove the wires from the connections on the line card.
4. Release the end unit from the connection terminal and leave the connection
open.
5. Perform the following isolation measurements with the ohmmeter at a
maximum measurement voltage of 10 V.
- Each conductor to each conductor: >1 M
- Each conductor to earth: >1 M
- Each conductor to shielding: >1 M
- Shielding to earth: >1 M
6. If these values are not reached, check the installation for the following causes:
Damp or wet installation or devices.

77
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning control panel with collective detector lines
19 Troubleshooting procedure

Troubleshooting
1. Disconnect the collective detector line in the middle by e.g. removing the base
cover.
2. Measure each line half on its own.
3. Disconnect the faulty section in the middle.
4. Once the fault has been rectified, reconnect the disconnected line sections
correctly and measure the entire collective detector line.
5. Reinsert the end-of-line element and the 'Detectors'.
6. Connect the collective detector line to the control panel.

19.4.5 Commissioning the collective detector line step-by-step

A 'Detector' with KMK = 1 increases the line current by approx. 0.1 mA.

1. Connect the universal measuring instrument to the start of the collective

detector line.
2. Switch the 'Line' on.
3. Switch the 'Zone' off.
4. Measure and make a note of the line current.
5. Insert the 'Detectors' into the bases one after the other and check the
respective current.
When the 'Detector' is inserted, the current increases for up to 25 seconds
and then settles back to a quiescent current.

Troubleshooting
If the line current remains unaltered, the 'Detector' may be defective or the
connections corroded.
If the line current increases by more than the detector's quiescent current, the
'Detector' has residual current. Swap the 'Detector' in this case.
1. Switch the 'Zone' on again.
The error message should not be displayed any longer.
2. Test the system function as described above and continue with the completion
work.

78
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning of control panel with AnalogPLUS detector line
20

20 Commissioning of control panel with

AnalogPLUS detector line
Creating the pre-configuration for AlgoRex data migration
You need a pre-configuration in order to commission an AnalogPLUS detector line.
If you are using the line card (AnalogPLUS) for AlgoRex data migration, you must
migrate the AlgoRex configuration data for the FS20 fire detection system. You will
find more information about AlgoRex data migration in document 009078. See
chapter 'Applicable documents'.

Prerequisites
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The latest firmware is installed on the 'Station'.
The latest BDV is installed on the 'Station' or is available on the PC.

You will find additional information about the individual steps on the specified
pages.

1. Create the pre-configuration of the AnalogPLUS detector line. You will find
information about creating a pre-configuration and about AlgoRex data
migration in document 009078.
2. Load the pre-configuration in 'SintesoWorks'.
3. Prepare the 'Station' for commissioning - without BDV installation. Link [ 35]
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the PC to the 'Station'. Link [ 28]
6. Test the function of the 'Site'. Link [ 41]
7. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
8. Disconnect the PC from the 'Station'. Link [ 25]
9. Perform the completion tasks. Link [ 41]

79
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the AnalogPLUS detector line
21 Adding a device to the detector line

21 Changing and expanding the AnalogPLUS

detector line

21.1 Adding a device to the detector line

NOTICE

Unable to detect device when it is read in

An AnalogPLUS detector line cannot be expanded by reading a device in on the
'Station', as the system is unable to identify the device.

WARNING

No alarm when a device is read in

If a device is read in on the 'Station' on the AnalogPLUS detector line, but is not
assigned to any logical element in the configuration, the device cannot indicate an
alarm. No alarm will be indicated on the line when an alarm is triggered.

To expand an AnalogPLUS detector line by adding a new device, follow the steps
below:
You have already commissioned the AnalogPLUS detector line.
1. Adapt the detector line configuration in 'SintesoWorks'.
- Insert the new device in the configuration.
- If the device is inserted between devices that have already been
commissioned, the existing addresses must be adjusted by selecting 'Edit'
> 'Change element address: +1'.
2. Install the device on the detector line in accordance with the pre-configuration.
Link [ 65]
3. Put the AnalogPLUS detector line into operation. Link [ 79]

21.2 Replacing a device with one of a different type

To replace a device on the AnalogPLUS detector line with one of a different type,
follow the steps below:
1. Remove the device that you want to replace for good. Link [ 81]
2. Add the new device to the detector line. Link [ 80]

80
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the AnalogPLUS detector line
Removing a device for good
21

21.3 Removing a device for good

To remove a device from the AnalogPLUS detector line for good, follow the steps
below:
1. Load the configuration from the 'Station' to the PC. Link [ 30]
2. Switch the detector line off. Link [ 37]
3. Detach the device. Link [ 38]
- In the case of non-stationary devices, detach the base as well.
4. Remove the physical and logical representation of the device in 'SintesoWorks'.
You will find more information in document 009078. See chapter 'Applicable
documents'.
5. Load the configuration from the PC to the 'Station'. Link [ 28]
6. Switch the detector line on. Link [ 37]

21.4 Replacing a non-stationary device of the same type

To replace a non-stationary device on the AnalogPLUS detector line with one of
the same type, follow the steps below:
You have already commissioned the AnalogPLUS detector line.
The line is in normal operation.
1. Switch the test mode on. Link [ 39]
2. Replace the device. Link [ 69]
3. Test the device. Link [ 93]
4. Switch normal operation on. Link [ 40]

Non-stationary devices of the same type can also be replaced without activating
test mode. To do this, switch off the detector line, replace the device with one of
the same type and restart the detector line.

21.5 Replacing multiple non-stationary devices of the

same type with a line restart
You can replace one or more non-stationary devices of the same type without
activating test mode. This involves restarting the line after the devices have been
replaced.

When you remove devices from the detector line, error messages are displayed.

You have already commissioned the AnalogPLUS detector line.

The line is in normal operation.
1. Remove the devices from the line.
2. Replace each device that you have removed with one of the same type.
3. Restart the line. Link [ 37]

81
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the AnalogPLUS detector line
21 Replacing a stationary device and I/O module

21.6 Replacing a stationary device and I/O module

Stationary devices and I/O modules cannot be replaced using the 'Accept
replaced devices' command on the 'Station'. This command does not recognize
the replacements.

To replace stationary devices and I/O modules on the AnalogPLUS detector line,
follow the steps below:
You have already commissioned the AnalogPLUS detector line.
The line is in normal operation.
The presence of detector fault messages is permissible.
1. Switch the detector line off. Link [ 37]
2. Replace the device. Link [ 69]
3. Switch the detector line on. Link [ 37]

21.7 Converting a stub or loop

The following conversion options are available for the AnalogPLUS detector line:
Converting a stub into a loop
Converting a loop into a stub
To convert an AnalogPLUS detector line, follow the steps below:
1. Load the configuration from the 'Station' to the PC. Link [ 30]
2. Switch the detector lines off. Link [ 37]
3. Rewire the detector line.
- You will find more information on the topology of AnalogPLUS detector
lines in document 008843. See chapter 'Applicable documents'.
4. Change the configuration of the AnalogPLUS detector line in 'SintesoWorks' in
accordance with the new wiring.
- You will find more information on how to configure the topology for
AnalogPLUS detector lines in document 009078. See chapter 'Applicable
documents'.
5. Load the modified configuration from the PC to the 'Station'. Link [ 28]
6. Switch the detector line on. Link [ 37]
7. Test the function of the 'Site'. Link [ 41]

21.8 Querying the number of devices on the detector line

Query the number of devices that are accessible on the forward and backward
connection of the detector line to identify any wire breaks in a loop.
1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'No. of devices forward/backward' command.
The number of devices on the forward and backward connection of the detector
line is displayed.

82
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the AnalogPLUS detector line
Readdressing devices
21

21.9 Readdressing devices

To readdress devices on the AnalogPLUS detector line, follow the steps below:
You have already commissioned the AnalogPLUS detector line.
The line is in normal operation.
1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Re-address devices' command.
The devices on the detector line are readdressed.

If the detector line is complete, the process of readdressing the devices in a loop
takes approximately 11 s. If there is a wire break in the loop, device readdressing
may take around 21 s.

83
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning of control panel with interactive detector line
22 Commissioning of interactive detector line for AlgoRex data migration

22 Commissioning of control panel with

interactive detector line
The commissioning steps in this chapter apply for detector lines with line card
(interactive) and line card (interactive, Ex).

You will find information about commissioning an interactive detector line and
about AlgoRex data migration in chapter 'Commissioning of interactive detector
line for AlgoRex data migration [ 84]'.

Prerequisites
The line card and the devices on the detector line have been installed.
The acceptance test has been carried out for the detector lines.
The 'Station' has been put into operation.
The latest firmware is installed on the 'Station'.

Reading in devices
1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Read in installed devices' command.
The devices on the interactive detector line are read in.
The following message is shown following successful reading in: 'Command
executed'

More commissioning steps

You will find additional information about the individual steps on the specified
pages.

1. Test the function of the 'Site' and remedy the problems, if any. Link [ 41]
2. Perform the completion tasks. Link [ 41]

22.1 Commissioning of interactive detector line for

AlgoRex data migration
Creating the pre-configuration for AlgoRex data migration
If you are using the line card (interactive) for AlgoRex data migration, you must
create a pre-configuration. To do this, migrate the AlgoRex configuration data for
the FS20 fire detection system. You will find more information about AlgoRex data
migration in document 009078. See chapter 'Applicable documents'.

84
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning of control panel with interactive detector line
Commissioning of interactive detector line for AlgoRex data migration
22

Prerequisites
The 'Station' is installed, but the batteries are not connected yet.
The cables for the detector lines and the mains supply have been inserted in
the 'Station', but not yet connected.
SintesoWorks is installed on the PC.
The latest firmware is installed on the 'Station'.
The latest BDV is installed on the 'Station' or is available on the PC.

You will find additional information about the individual steps on the specified
pages.

1. Create the pre-configuration of the interactive detector line. You will find
information about AlgoRex data migration in document 009078.
2. Load the pre-configuration in 'SintesoWorks'.
3. Prepare the 'Station' for commissioning - without BDV installation. Link [ 35]
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the PC to the 'Station'. Link [ 28]
6. Test the function of the 'Site'. Link [ 41]
7. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
8. Disconnect the PC from the 'Station'. Link [ 25]
9. Perform the completion tasks. Link [ 41]

85
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the interactive detector line
23 Adding a device to the detector line

23 Changing and expanding the interactive

detector line

23.1 Adding a device to the detector line

WARNING

No alarm when there is no logical assignment

If a device is read in on the 'Station' on the interactive detector line, but is not
assigned to any logical element in the configuration, the device cannot indicate an
alarm. No alarm will be indicated on the line when an alarm is triggered.

To expand an interactive detector line by adding a new device, follow the steps
below:
1. Switch the detector line off. Link [ 37]
2. Fit and wire the new devices. Link [ 65]
3. Read in the devices. You will find more information in chapter 'Commissioning
of control panel with interactive detector line [ 84]'.
4. Connect the PC to the 'Station'. Link [ 25]
5. Load the configuration from the 'Station' to the PC. Link [ 30]
6. Configure the new devices. Link [ 66]
7. Load the configuration from the PC to the 'Station'. Link [ 28]
8. Test the function of the 'Site'. Link [ 41]
9. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 28]
10. Disconnect the PC from the 'Station'. Link [ 25]

23.2 Replacing a device with one of a different type

To replace a device on the interactive detector line with one of a different type,
follow the steps below:
1. Remove the device that you want to replace for good. Link [ 86]
2. Add the new device to the detector line. Link [ 86]

23.3 Removing a device for good

To remove a device from the interactive detector line for good, follow the steps
below:
You have already commissioned the interactive detector line.
The line is in normal operation.
1. Switch the detector line off. Link [ 37]
2. Detach the device. Link [ 38]
- In the case of non-stationary devices, detach the base as well.
3. Switch the detector line on. Link [ 37]

86
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the interactive detector line
Replacing a non-stationary device of the same type
23

Removing a device with 'SintesoWorks'

1. Load the configuration from the 'Station' to the PC. Link [ 30]
2. Switch the detector line off. Link [ 37]
3. Detach the device. Link [ 38]
- In the case of non-stationary devices, detach the base as well.
4. Remove the physical and logical representation of the device in 'SintesoWorks'.
You will find more information in document 009078. See chapter 'Applicable
documents'.
5. Load the configuration from the PC to the 'Station'. Link [ 28]
6. Switch the detector line on. Link [ 37]

23.4 Replacing a non-stationary device of the same type

When replacing non-stationary devices on an interactive Ex detector line during
operation, it takes the system 70 s/device to detect the device(s) concerned.
As a result, you must wait at least 70 s before the device is able to activate an
alarm.

To replace a non-stationary device on the interactive detector line with one of the
same type, follow the steps below:
You have already commissioned the interactive detector line.
The line is in normal operation.
The new device has not yet been connected.
1. Switch the test mode on. Link [ 39]
2. Replace the device. Link [ 69]
3. Test the device. Link [ 93]
4. Switch normal operation on. Link [ 40]

23.5 Replacing an I/O module

To replace stationary devices and I/O modules on the interactive detector line,
follow the steps below:
You have already commissioned the interactive detector line.
The line is in normal operation.
The presence of detector fault messages is permissible.
Only one I/O module may be replaced.
The new I/O module has not yet been connected.
1. Switch the detector line off. Link [ 37]
2. Replace the device. Link [ 69]
3. Switch the detector line on. Link [ 37]

87
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the interactive detector line
23 Replacing stationary manual call points of the same type

23.6 Replacing stationary manual call points of the same

type
When the replace mode is activated, no other commands can be executed on the
line.

The following steps do not apply to devices with a wireless connection.

To replace a stationary manual call point on the interactive detector line, follow the
steps below:
You have already commissioned the interactive detector line.
The line is in normal operation.
The presence of detector fault messages is permissible.
1. Switch on the replace mode. Link [ 71]
2. Replace the 'Manual call point' with a 'Manual call point' of the same type.
3. Switch off the replace mode. Link [ 71]

23.7 Converting a stub or loop

The following conversion options are available for the interactive detector line:
Converting a stub into a loop
Converting a loop into a stub
To convert an interactive detector line, follow the steps below:
1. Load the configuration from the 'Station' to the PC. Link [ 30]
2. Switch the detector lines off. Link [ 37]
3. Rewire the detector line.
- You will find more information on the topology of interactive detector lines
in document 008843. See chapter 'Applicable documents'.
4. Change the configuration of the interactive detector line in 'SintesoWorks' in
accordance with the new wiring.
- You will find more information on how to configure the topology for
interactive detector lines in document 009078. See chapter 'Applicable
documents'.
5. Load the modified configuration from the PC to the 'Station'. Link [ 28]
6. Switch the detector line on. Link [ 37]
Test the function of the 'Site'. Link [ 41]

88
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Changing and expanding the interactive detector line
Locating wire breaks
23

23.8 Locating wire breaks

For the purpose of locating a wire break in a loop, the detector line can be supplied
via just the forward connection or the backward connection.

When the detector line is switched off, the 'Stub line forward' and 'Stub line
backward' commands are not available.

If a stub has been configured, the 'Stub line forward' and 'Stub line backward'
commands are not available.

When the 'Station' is restarted, the 'Stub line forward' or 'Stub line backward'
supply mode is not retained.

You have already commissioned the AnalogPLUS detector line.

The line is in normal operation.
1. In the main menu, select 'Topology' > 'Hardware tree' > 'Station' > Line card >
Detector line.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. Select the 'Stub line forward' or 'Stub line backward' command.
Only the devices on the selected connection are supplied with power.
The 'Station' displays error messages for the devices on the connection
that is not being supplied with power.
4. Identify the location of the wire break.
- Analyze the messages for the missing devices.
- And/or
- Check the line voltage.

Wire break successfully located

1. Go to the 'Hardware tree' and navigate to the detector line.
2. Select 'Execute commands' > 'Restart line'.

Wire break not located

If the wire break could not be located by supplying the selected connection, try
supplying the connection in the opposite direction instead.
1. Select the 'Stub line forward' or 'Stub line backward' command, which must be
the opposite of the one you selected initially.
Only the devices on the selected connection are supplied with power.
The 'Station' displays error messages for the devices on the connection
that is not being supplied with power.
2. Identify the location of the wire break.
- Analyze the messages for the missing devices.
- And/or
- Check the line voltage.
3. If you are able to locate the wire break, follow the steps described under 'Wire
break successfully located'.

89
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning the sounder base FDSB291
24

24 Commissioning the sounder base FDSB291

If the product version of the sounder base FDSB291 or of the fire detector in the
sounder base FDSB291 is <30, then the 'Base sounder' element is not
automatically created when the FDnet devices are read in. If this is the case, then
you must create the 'Base sounder' element manually.
You will find more information in document 009078. See chapter 'Applicable
documents'.

You will find the product version (ES) on the type plate of the device.

ES
Type label of the sounder base

ES

Type label of the fire detector

90
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning the fire brigade periphery module FCI2001-D1
25

25 Commissioning the fire brigade periphery

module FCI2001-D1
The fire department periphery module FCI2001-D1 monitors the monitored inputs
and outputs for short-circuit and open line. The resistance values of the lines may
be read in and stored at the push of a button. If a deviation from the quiescent
value is detected, the control panel evaluates a short-circuit or an open line.
The following table shows the monitored inputs and outputs:

Terminal Pin Function

X4 4, 5 and 1, 2 Remote transmission or transmission device (RT Alarm)

and release element ('FSE')
X5 7, 8 'Key depot' (tamper monitoring)
X6 5, 6 Local alarm

X4 X5 X6

S101

View of the fire department periphery module

X4–X6 Connection terminals

S101 Button

Procedure
1. Check the connected lines for short-circuit and open line.
2. Connect the lines.
During the commissioning of the control panel, fault messages are
indicated, provided that there are any deviations from the basic settings.
3. Press the push-button S101.
The resistance values are read in.

91
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning I/O card (remote transmission) FCI2007-A1 and I/O card (horn/monitored) FCI2009-A1
26

26 Commissioning I/O card (remote

transmission) FCI2007-A1 and I/O card
(horn/monitored) FCI2009-A1
With the I/O card (remote transmission) FCI2007-A1 and I/O card (horn/monitored)
FCI2009-A1, the monitored outputs are monitored for short-circuit and open line.
The resistance values of the lines may be read in and stored at the push of a
button. If a deviation from the quiescent value is detected, the control panel
evaluates a short-circuit or an open line.
The following outputs must be calibrated upon commissioning:
FCI2007-A1: 'OUT1' to 'OUT3'
FCI2009-A1: 'OUT1' to 'OUT8'
You will find more information about the FCI2007-A1 and FCI2009-A1 I/O cards
and planning monitored outputs in documents 008843 and 008837. See chapter
'Applicable documents'.
S501

I/O card FCI2007-A1 and/or FCI2009-A1

S501 Button

Procedure
1. Check the connected lines for short-circuit and open line.
2. Connect the lines.
During the commissioning of the control panel, fault messages are
indicated, provided that there are any deviations from the basic settings.
3. Press the S501 button.
The resistance values are read in.

You can also read in the resistance values via the control panel's Person Machine
Interface.

92
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Testing detectors
Activate the detector
27

27 Testing detectors
The commissioning personnel perform the function test for the automatic fire
detectors and the 'Manual call points'.

You will find additional information about the individual steps on the specified
pages.

The detector line has been commissioned.

1. Switch the test mode on. Link [ 39]
2. Initiate the detector. Link [ 93]
3. Switch normal operation on. Link [ 40]
4. Test the logged test activations. Link [ 93]

27.1 Activate the detector

'DETECTOR TEST' is switched on.
1. Activate all automatic 'Detectors' and 'Manual call points' using the
corresponding tools.
2. Write down the sequence of the test activations.
The alarm indicator for the activated detector flashes at each test activation.
If an external alarm indicator is connected and correspondingly configured, the
external alarm indicator also lights up.
You will find information about triggering detectors in document 007004. See
chapter 'Applicable documents'.

See also
Applicable documents [ 11]

27.2 Testing logged test activations

1. Test the logged test activations. This can be done in two ways:
- Person Machine Interface: Select 'Event memory' in the main menu.
- SintesoWorks: Select the 'Commissioning' > 'Upload site event memory'
menu items.
2. Rectify existing errors if necessary, e.g. if the alarm indicator has not flashed or
no test entries exist.

93
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Testing detector with detector exchanger and tester or intelligent detector tester
28

28 Testing detector with detector exchanger and

tester or intelligent detector tester
In this chapter, 'service device' refers to the following devices:
Detector exchanger and tester FDUD292
Intelligent detector tester FDUD293
The service device allows for easy testing of the detector without first switching the
corresponding 'Zones', 'Sections' or 'Areas' in to test mode.

Enabling communication with the service device

1. Select the 'Topology' > 'Hardware tree' menu item via the main menu on the
'Station' Person Machine Interface.
2. Select the 'Station'.
3. Press the 'More Options' softkey.
4. Select 'Execute commands'.
5. Select the 'Enable MC link' command.
Communication between the service device and the 'Station' is enabled.

Testing detectors
Test the detectors according to the information in the following documents:
Detector exchanger and tester FDUD292: document 007227
Intelligent detector tester FDUD293: document 009718
In these documents you will find a description of the various test variants and the
operation of the service device. See chapter 'Applicable documents'.

Ending communication with the service device

Proceed as described under 'Enabling communication with the service device' and
select the 'Disable MC link' command.

See also
Applicable documents [ 11]

94
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Preparation and security
29

29 Updating the firmware of the 'Station'

29.1 Preparation and security

The following points must be observed before updating the firmware.
The firmware must be updated individually for each 'Station'. Exception:
'Stations' networked via FCnet/LAN. See the chapter 'Updating several
'Stations' simultaneously [ 98]'.
Data backup
– When the firmware of the main CPU is updated, the configuration data,
event memories and the alarm counter value are deleted. Load the
configuration data and event memories before updating in SintesoWorks.
You will find more information about the event memory and the alarm
counter in document 009078. See chapter 'Applicable documents'.
Converting the configuration data
– Updating the firmware requires the configuration data to be converted if the
new firmware and existing configuration are not compatible with one
another.
BDV compatibility
– The BDVs are compatible when the major version and the minor version
are identical. The Bug fix version is not relevant for the compatibility. You
will find Information about BDV names and versions in document 009078.
See chapter 'Applicable documents'.
The procedure for updating the firmware depends on the 'Station' configuration.
A 'Station' can be configured as follows:
– Standalone Station
– SAFEDLINK Station
– Router Station, Ethernet Station
– Modular 'Station' with CPU card
Windows firewall setting
– To connect the PC to the 'Station', the Windows firewall settings must be
changed if possible. You will find more information on this in chapter
'Setting Windows firewall [ 32]'.
Communication with GAP via FCnet/LAN
– A GAP with DHCP must be configured for a connection with the PC via
FCnet/LAN. You will find more information in document 009078. See
chapter 'Applicable documents'.
Once the firmware has been updated, the 'Station' configuration must be
loaded to 'SintesoWorks' in order to update the LRC data to the current
firmware status.

WARNING

Fire detection installation is deactivated during the firmware update

Fire may spread unhindered.
Supervision by people is required.
Re-activate the fire detection installation as soon as possible.

95
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Updating the firmware of the main CPU and the additional CPUs – Overview

NOTICE

Data loss during the firmware update

Configuration data and event memory are deleted in the 'Station'.
Load the configuration data and event memory to SintesoWorks before
updating the firmware.

NOTICE

Power failure during the firmware update

Firmware is not updated and 'Station' is not working. The firmware update cannot
be repeated and must be performed by the manufacturer.
Do not disconnect the Station from the power supply during the firmware
update.

See also
Applicable documents [ 11]

29.2 Updating the firmware of the main CPU and the

additional CPUs – Overview
The procedure for updating the firmware depends on the nature and function of the
'Station'. The procedures are described in the following chapters.

29.2.1 Standalone station and SAFEDLINK station

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in the chapter 'Preparation and

security [ 95]'.
1. Import the new firmware into SintesoWorks.
- Select the 'File' > 'Import new resource package' menu item and open the
file you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [ 30]
3. Convert the configuration if necessary and rectify conversion faults. Link
101]
4. Connect the PC to the 'Station'. Link [ 25]
5. Update the firmware on the main CPU and the additional CPUs. Link [ 102]
6. Initialize the 'Station'. Link [ 26]
7. Test the firmware version on the additional CPUs. Link [ 110]
- Update the firmware, if required, of the additional CPUs again, if there is a
higher firmware version available. Link [ 108]
8. Load the configuration from the 'Station' to the PC. Link [ 30]
9. Disconnect the PC from the 'Station'. Link [ 25]

96
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Updating the firmware of the main CPU and the additional CPUs – Overview
29

29.2.2 Router station and Ethernet station

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in the chapter 'Preparation and

security'.
A GAP with DHCP must be configured for the connection with the PC via
FCnet/LAN.
1. Import the new firmware into SintesoWorks.
- Select the 'File' > 'Import new resource package' menu item and open the
file you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [ 30]
3. Convert the configuration if necessary and rectify conversion faults. Link
101]
4. Connect the PC to the Ethernet switch (MM) FN2008-A1 via the FCnet/LAN.
5. Update the firmware on the main CPU and the additional CPUs. Link [ 102]
6. Initialize the 'Station'. Link [ 26]
- Remove the network connection to the 'Station'and connect the PC locally
to the 'Station'. Link [ 25]
7. Test the firmware version on the additional CPUs. Link [ 110]
- Update the firmware, if required, of the additional CPUs again, if there is a
higher firmware version available. Link [ 108]
8. Load the configuration from the 'Station' to the PC. Link [ 30]
9. Disconnect the PC from the 'Station'. Link [ 25]
10. Restore the network connection.

See also
Preparation and security [ 95]

97
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Updating the firmware of the main CPU and the additional CPUs – Overview

29.2.3 Modular station with CPU card

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in Preparation and security [ 95].

A GAP with DHCP must be configured for the connection with the PC via
FCnet/LAN.
1. Import the new firmware into SintesoWorks.
- Select the 'File' > 'Import new resource package' menu item and open the
file you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [ 30]
3. Convert the configuration if necessary and rectify conversion faults. Link
101]
4. Connect the PC to the communication card (FC2080) FCC2005.
5. Update the firmware on the CPU cards and the additional CPUs. Link [ 102]
6. Initialize the 'Station'. Link [ 26]
7. Test the firmware version on the additional CPUs. Link [ 110]
- Update the firmware, if required, of the additional CPUs again, if there is a
higher firmware version available. Link [ 108]
8. Load the configuration from the 'Station' to the PC. Link [ 30]
9. Disconnect the PC from the communication card.

29.2.4 Updating several 'Stations' simultaneously

You can update the firmware of max. eight networked 'Stations' and CPU cards
simultaneously. The 'Stations' and the CPU cards must be connected to one
another via FCnet/LAN.
Examples:
A modular 'Station' (e.g. FC2080) has two CPU cards FCC2004 and an
operating unit. The CPU cards and the operating unit are connected to the
communication card (FC2080) FCC2005 via an Ethernet cable.
Several 'Stations' are connected to each other via one or several 'Ethernet
switch (MM) FN2008-A1'.

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in 'Preparation and security [ 95]'.

A GAP with DHCP must be configured for the connection with the PC via
FCnet/LAN.
The 'Stations' and the CPU cards and the communication card are networked
with one another.
You can update not more than eight 'Stations' and CPU cards simultaneously.

98
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Updating the firmware of the additional CPUs only – Overview
29

1. Import the new firmware into SintesoWorks.

- Select the 'File' > 'Import new resource package' menu item and open the
file you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [ 30]
3. Convert the configuration if necessary and rectify conversion faults. Link
101]
4. Connect the PC to the communication card or to the Ethernet switch (MM)
FN2008-A1.
5. Update the firmware on the main CPU and the additional CPUs. Link [ 102]
- Set each 'Station' and CPU card individually in update mode. You can set
the 'Stations' and the CPU cards in update mode without any waiting time
one directly after the other.
- Wait until the updation of each 'Station' and CPU card is completed.
6. Initialize each 'Station' individually. Link [ 26] To do so, you must connect the
PC to each 'Station' locally. Link [ 25]
7. Test the firmware version on the additional CPUs on each 'Station'. Link
110]
- Update the firmware, if required, of the additional CPUs again, if there is a
higher firmware version available. Link [ 108]
8. Load the configuration from the 'Station' to the PC. Link [ 30]
9. Disconnect the PC from the 'Station'. Link [ 25]
10. Restore the network connection, if required.

29.3 Updating the firmware of the additional CPUs only –

Overview
If the Station firmware is up-to-date and components have been changed then it is
only necessary to update the additional CPUs. The procedure for updating the
firmware depends on the 'Station' function. The procedures are described in the
following chapters.

29.3.1 Standalone station and SAFEDLINK station

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in 'Preparation and security [ 95]'.

1. Connect the PC to the 'Station'. Link [ 25]
2. Enable the 'Station'.
- Press <MENU> and enter a valid PIN.
3. Update the firmware of the additional CPUs if there is a higher firmware version
status. Select the local connection as the connection type. Link [ 108]
4. Load the configuration from the 'Station' to the PC. Link [ 30]
5. Disconnect the PC from the 'Station'. Link [ 25]

99
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Update only the BDV

29.3.2 Router station and Ethernet station

You can update the additional CPUs in a networked 'Station' via FCnet/LAN. In this
way, you can update networked 'Stations' without disconnecting the network
connection and restoring the factory setting.

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in 'Preparation and security [ 95]'.

A GAP with DHCP must be configured for the connection with the PC via
FCnet/LAN.
1. Load the configuration from the 'Station' or your archive to the PC. Link [ 30]
2. Connect the PC to the FCnet/LAN via the Ethernet switch (MM) FN2008-A1.
3. Enable the 'Station'.
- Press <MENU> and enter a valid PIN.
4. Update the firmware of the additional CPUs if there is a higher firmware version
status. Select the connection via GAP and enter the address of the 'Station'
you want to update. Link [ 108]
5. Load the configuration from the PC to the 'Station'. Link [ 28]
6. Load the configuration from the 'Station' to the PC. Link [ 30]
7. Disconnect the PC from FCnet/LAN.

29.4 Update only the BDV

If the old and new BDVs are compatible (identical major and minor versions) and
there is no new firmware version available for the main CPU, it is also only possible
to update the BDV. You will find Information about BDV names and versions in
document 009078. See chapter 'Applicable documents'.
The procedure for updating the BDV depends on the 'Station' function. The
procedures are described in the following chapters.

See also
Applicable documents [ 11]

29.4.1 Standalone station and SAFEDLINK station

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in 'Preparation and security [ 95]'.

1. Import the new BDV into SintesoWorks.
- Select the 'File' > 'Import new BDV' menu item and open the file you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [ 30]
3. Convert the configuration and rectify conversion faults. Link [ 101]
4. Connect the PC to the 'Station'. Link [ 25]

100
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Converting the configuration
29

5. Enable the 'Station'.

- Press <MENU> and enter a valid PIN.
6. Load the converted configuration from the PC to the 'Station'. Link [ 28]
7. Disconnect the PC from the 'Station'. Link [ 25]

29.4.2 Router station and Ethernet station

You will find additional information about the individual steps on the specified
pages.

Familiarize yourself with the information in 'Preparation and security [ 95]'.

1. Import the new BDV into SintesoWorks.
- Select the 'File' > 'Import new BDV' menu item and open the file you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [ 30]
3. Convert the configuration and rectify conversion faults. Link [ 101]
4. Remove the network connection to the 'Station' and connect the PC. Link
25]
5. Enable the 'Station'.
- Press <MENU> and enter a valid PIN.
6. Load the converted configuration from the PC to the 'Station'. Link [ 28]
7. Disconnect the PC from the 'Station'. Link [ 25]
8. Restore the network connection.

29.5 Converting the configuration

In document A6V10244961, you will find detailed information about converting
'Sites'. See chapter 'Applicable documents'.

Converting the configuration

The 'Site' you want to convert is saved and loaded in SintesoWorks.
1. Select the 'Edit' > 'Convert site' menu item.

The following window is opened:

2. Select the BDV you want and click on 'Convert'.

The 'Action confirmation' window opens.
3. Click on 'Yes'.
The 'Site' is converted.

101
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Updating the firmware of the main CPU and the additional CPUs

29.6 Updating the firmware of the main CPU and the

additional CPUs
The procedure for updating the main CPU and additional CPUs depends on
whether the PMI & mainboard FCM2004, FCM2027 or the CPU card FCC2004 is
used in the 'Station'. The procedures are described in the following chapters:
'PMI & mainboard FCM2004 [ 102]'
'PMI & mainboard FCM2027 [ 104]'
'CPU card FCC2004 [ 106]'

PMI & mainboard FCM2004 PMI & mainboard FCM2027

29.6.1 PMI & mainboard FCM2004

Familiarize yourself with the information in 'Preparation and security [ 95]'.
1. Select 'Update' > 'FW update main and additional CPUs' from the menu bar.
2. If the 'Password check' window is open, enter the password '1234' and click on
'OK'.
The 'Confirmation' window opens.
3. NOTICE! Data loss. Save the configuration data before updating the firmware.
4. Click on 'Yes'.
The 'FW update main and additional CPUs' window opens.

5. Select the firmware version you want and click on 'Start'.

102
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Updating the firmware of the main CPU and the additional CPUs
29

The following window is opened:

6. Set the 'S38-2' switch to 'ON' on the rear of the operating unit.
7. Press the 'S32' button for approx. 5 s until the 'Station' restarts.

The firmware update starts and takes up to ten minutes.

8. Click on 'OK' in the 'Information' window.
The 'FW update main and additional CPUs' window is displayed. Only close
this window once the firmware update is complete.

9. Follow the procedures on the display of the 'Station' and wait until the following
lines appear:
- 'Switch-off S38-2 now'
- 'The panel will reboot automatically'
10. Click on 'Close' in the 'FW update main and additional CPUs' window.

103
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Updating the firmware of the main CPU and the additional CPUs

The following window is opened:

11. On the 'Station', set the 'S38-2' switch to 'OFF'.

The 'Station' is restarted many times. This procedure takes up to ten
minutes.
12. Click on 'OK' in the 'Information' window.
After the restart, the 'Station' display shows the available BDVs. It is not
necessary to install a BDV at this point.

Initializing the 'Station' instead of installing the BDV saves time. During
initialization, the BDV and the configuration data are loaded to the 'Station'.

29.6.2 PMI & mainboard FCM2027

Familiarize yourself with the information in the chapter 'Preparation and
security'.
1. Select 'Update' > 'FW update main and additional CPUs' from the menu bar.
2. If the 'Password check' window is open, enter the password '1234' and click on
'OK'.
The 'Confirmation' window opens.
3. NOTICE! Data loss. Save the configuration data before updating the firmware.
4. Click on 'Yes'.
The 'FW update main and additional CPUs' window opens.

5. Select the firmware version you want and click on 'Start'.

104
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Updating the firmware of the main CPU and the additional CPUs
29

The following window is opened:

6. Keep the 'S32' button on the rear of the operating unit pressed and press
<Acknowledge> on the Person Machine Interface at the same time for approx.
5 s until the 'Station' restarts.

A peeping sound confirms the function is being executed.

The firmware is updated and the 'Station' restarts several times. This
procedure takes up to ten minutes.
7. Click on 'OK' in the 'Information' window.
The 'FW update main and additional CPUs' window is displayed.

8. Click on 'Close' in the 'FW update main and additional CPUs' window once the
'Station' has restarted.

105
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Updating the firmware of the main CPU and the additional CPUs

The following window is opened:

9. Click on 'OK'.
After the restart, the 'Station' display shows the available BDVs. It is not
necessary to install a BDV at this point.

Initializing the 'Station' instead of installing the BDV saves time. During
initialization, the BDV and the configuration data are loaded to the 'Station'.

Error during firmware update

If errors occur during the firmware update, the error messages are shown after the
update on the 'Station' display. The line 'Press Silence buzzer button' is displayed
after the error messages.
1. Press <Silence buzzer> on the Person Machine Interface.
The 'Station' restarts.
After a few minutes, the 'Buzzer' sounds twice.
2. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.

See also
Preparation and security [ 95]

29.6.3 CPU card FCC2004

You will find information about the CPU card FCC2004, the LED matrix display
and operating the 'S8' button in document 008837. See chapter 'Applicable
documents'.

Familiarize yourself with the information in 'Preparation and security [ 95]'.

1. Select 'Update' > 'FW update main and additional CPUs' from the menu bar.
2. If the 'Password check' window is open, enter the password '1234' and click on
'OK'.
The 'Confirmation' window opens.
3. NOTICE! Data loss. Save the configuration data before updating the firmware.

106
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Updating the firmware of the main CPU and the additional CPUs
29

4. Click on 'Yes'.
The 'FW update main and additional CPUs' window opens.

5. Select the firmware version you want and click on 'Start'.

The following window is opened:

6. Set the CPU card as follows in update mode. If you are using two CPU cards,
set the main CPU card first and then the redundant CPU card in update mode.
You can set the redundant CPU card in update mode immediately after the
main CPU card.
- Briefly press the 'S8' button on the CPU card several times until a 'U' is
displayed on the LED matrix display.
- As soon as the 'U' is displayed, press and hold the 'S8' button for approx.
2 s to confirm the selection.
A checkmark on the LED matrix display confirms the selection.
The firmware is updated. This procedure takes up to ten minutes. The
update progress is shown on the LED matrix display.
7. Click on 'OK' in the 'Information' window.
The 'FW update main and additional CPUs' window is displayed.

8. Wait until successful completion of the update is shown as follows on the LED
matrix display:
- Active CPU: a
- Inactive CPU: i
The CPU card is restarted.

107
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Update the firmware of the additional CPUs

9. Click on 'Close' in the 'FW update main and additional CPUs' window once the
CPU card has restarted.
The following window is opened:

10. Click on 'OK'.

The firmware on the CPU card is updated. The CPU card is in normal
operation.

Error during firmware update

If errors occur during the firmware update, the following is shown on the LED
matrix display:
:-(

29.7 Update the firmware of the additional CPUs

NOTICE

Updating the firmware of the degraded mode module FN2001

If the firmware of the degraded mode module FN2001 has to be updated, it must
be temporarily connected to the slot for the main module FN2001 (from slot X12
to X13).

Familiarize yourself with the information in the chapter 'Preparation and

security'.
1. Select 'Update' > 'FW update additional CPUs' from the menu bar.
2. If the 'Password check' window is open, enter the password '1234' and click on
'OK'.
The following window is opened:

108
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Testing the firmware version of the additional CPUs
29

3. Select the connection type.

- Select 'Local connection' to establish a connection to the connected
standalone or SAFEDLINK 'Station'.
- Select 'Connection to GAP' to establish a connection via GAP to a
networked 'Station'. Enter the address of the 'Station' you want to update in
the 'Target station address' field. If you want to update the GAP 'Station'
itself, enter '0'.
4. Click on 'OK'.
The following window is opened.
The checkboxes for the CPUs that can be updated are checked.

5. Select the CPUs you want to update and click on 'Start'.

The following window is opened:

6. Press <MENU> on the 'Station' and enter a valid PIN.

7. Click on 'OK' in the 'Set access level' window.
The CPUs are updated.
The 'Information' window is opened after updating.
8. Note the update information and information about other procedures in the
'Information' window.
9. Click on 'OK'.
The 'Station' is restarted.
After a few minutes, the 'Buzzer' sounds twice.
10. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.
11. Click on 'Close' in the 'FW update additional CPUs' window.

See also
Preparation and security [ 95]

109
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
29 Testing the firmware version of the additional CPUs

29.8 Testing the firmware version of the additional CPUs

If you have updated the firmware of the main CPU and the additional CPUs in a
single step ('FW update main and additional CPUs'), you must then test the
firmware version of the additional CPUs to ensure that the CPUs were updated
correctly. Update the firmware, if required, of the additional CPUs again, if there is
a higher firmware version available.
To test the firmware version on the additional CPUs, proceed as follows:
1. Select 'Update' > 'FW update additional CPUs' from the menu bar.
2. If the 'Password check' window is open, enter the password '1234' and click on
'OK'.
The following window is opened:

3. Select the connection type.

- Select 'Local connection' to establish a connection to the connected
standalone or SAFEDLINK 'Station'.
- Select 'Connection to GAP' to establish a connection via GAP to a
networked 'Station'. In the field 'Target station address' enter the address of
'Station'. If you want to create a connection to GAP 'Station' itself, enter '0'.
4. Click on 'OK'.
The following window is opened.

5. Test the firmware version on the additional CPUs.

6. Click on 'Cancel' in the 'FW update additional CPUs' window.

110
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the 'Station'
Creating diagnosis report
29

29.9 Creating diagnosis report

To update the firmware versions for the creation of the diagnosis report, the
configuration data must be loaded in SintesoWorks.
The configuration data for the 'Station' is loaded to SintesoWorks.
1. Select 'Commissioning' > 'Diagnostics report' from the menu bar.
The 'Reports' window opens.
2. Select 'Diagnostics report' in the 'Report type' field.
3. Select the page format, page orientation, file name and memory location of the
report in the 'Output settings' section.
4. Click on 'Create report'.
The report is created and displayed.

You will find more information about creating reports and the diagnosis report in
document 009078. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

111
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating the firmware of the MCL-USB adapter FDUZ221

30 Updating the firmware of the peripheral

devices
You need the following tools to update the firmware of the periphery devices:
SintesoWorks
MCL-USB adapter FDUZ221 or FDUZ227

If the hardware product version is not compatible with the current firmware, a
corresponding error message is displayed during the update process.
In this instance, the hardware must be replaced in accordance with the
information in the 'Release Notes'.

30.1 Updating the firmware of the MCL-USB adapter

FDUZ221
The firmware of the MCL-USB adapter FDUZ221 must be updated if a new
firmware version is issued.

Preparation
The driver for the MCL-USB adapter is installed on the PC. You will find
instructions for installing the driver in document 009854. See chapter
'Applicable documents'.
1. Select 'File' > 'Import new resource package'.
2. In the selection window open the corresponding file F-FXS2007-XX_x_x_...zip.
3. Connect the MCL-USB adapter to the PC.
The orange LED on the MCL-USB adapter flashes for a short while. When the
device is ready for operation, the green LED lights up.

USB

FDUZ221

Connection of the PC to the MCL-USB adapter

112
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating the firmware of the MCL-USB adapter FDUZ221
30

Updating the firmware

1. Select 'Update' > 'FW update FDUZ221 MCL USB adapter'.
The connection to the device is established.
The 'FW update FDUZ221 MCL USB adapter' window opens.
The latest firmware package and the latest firmware version are suggested.
The green LED goes out.
2. Click on 'Start'.
When the hardware version is unknown, another 'FW update FDUZ221
MCL USB adapter' window is opened and you are prompted to check the
hardware version.
When the hardware version is known, the status bar indicates the update
progress.
The 'FW update FDUZ221 MCL USB adapter' window is closed after
updating.
The device is restarted.
A success message is indicated.
When the device is ready for operation, the green LED lights up.
3. Disconnect the MCL-USB adapter from the PC.
The firmware is updated.

113
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating the firmware of the floor repeater terminal FT2010

30.2 Updating the firmware of the floor repeater terminal

FT2010

WARNING

Incorrect assignment between detector/detector group and customer text

Misleading messages in the event of an alarm
Never change the wiring during the firmware update.

The firmware must be updated individually for each floor repeater terminal.

Preparation
The floor repeater terminal is fed by a 24 V external power supply or by the
FDnet detector line.
The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
1. Select 'File' > 'Import new resource package'.
2. In the selection window, open an F-Site-XX_x_x_...zip file matching the
'FXS2001'.
3. Open the device and connect the PC via the MCL-USB adapter to the device.

FT2010

X100
USB
MC-Link

FDUZ221/FDUZ227

24 V

Connect the PC to the floor repeater terminal

FDUZ221 MCL-USB adapter (interface USB/MC-LINK)

/
FDUZ227
X100 Connection for the MCL-USB adapter
FT2010 Floor repeater terminal

114
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating the firmware of the floor repeater terminal FT2010
30

Updating the firmware

1. Select 'Update' > 'FW update standard peripheral device'.
The 'FW update standard peripheral device' window opens.
SintesoWorks establishes the connection to the device and sets the device
to update mode.
The latest firmware package and the latest firmware version are suggested.
2. Select the firmware package that matches the 'Site'.
3. Click on 'Start'.
- If the hardware version is not compatible, click on 'Cancel' and check the
hardware version. Replace the hardware and start again at point 1.
The status bar indicates the update progress.
The 'FW update standard peripheral device' window is closed after
updating.
The device is restarted.
A success message is indicated.
4. Remove the MCL-USB adapter and lock the device.
The firmware is updated.

Manually setting device to update mode

Proceed as follows if you are prompted to manually set the device to update mode
in step 1:
1. Keep the 'More alarms' (1) and 'Reset' (2) buttons pressed at the same time
and disconnect the FDnet plug (X1) from the printed circuit board.
2. Wait at least ten seconds and re-insert the FDnet plug (X1).
The device is set to update mode.
3. Click on the 'FW update standard peripheral device' button in the 'OK' window
and go to 'Update firmware', step 2.

FT2010 Front view FT2010 printed circuit board

115
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating the firmware of the floor repeater display FT2011

30.3 Updating the firmware of the floor repeater display

FT2011

WARNING

Incorrect assignment between detector/detector group and customer text

Misleading messages in the event of an alarm
Never change the wiring during the firmware update.

The firmware must be updated individually for each floor repeater display.

Preparation
The floor repeater display is fed by a 24 V external power supply or by the
FDnet detector line.
The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
1. Select 'File' > 'Import new resource package'.
2. Open an F-Site-XX_x_x...zip file that matches the 'FXS2001' in the selection
window.
3. Open the device and connect the PC via the MCL-USB adapter to the device.
FT2011

X100
USB
MC-Link

FDUZ221/FDUZ227

24 V

Connect the PC to the floor repeater display

FDUZ221 MCL-USB adapter (interface USB/MC-LINK)

/
FDUZ227
X100 Connection for the MCL-USB adapter
FT2011 Floor repeater display

116
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating the firmware of the floor repeater display FT2011
30

Updating the firmware

1. Select 'Update' > 'FW update standard peripheral device'.
The 'FW update standard peripheral device' window opens.
SintesoWorks establishes the connection to the device and sets the device
to update mode.
The latest firmware package and the latest firmware version are suggested.
2. Select the firmware package that matches the 'Site'.
3. Click on 'Start'.
If the hardware version is not compatible, click on 'Cancel' and check the
hardware version. Replace the hardware and start again at point 1.
The status bar indicates the update progress.
The 'FW update standard peripheral device' window is closed after
updating.
The device is restarted.
A success message is indicated.
4. Remove the MCL-USB adapter and lock the device.
The firmware is updated.

Manually setting device to update mode

Proceed as follows if you are prompted to manually set the device to update mode
in step 1:
1. Keep the 'More alarms' (1) and 'Silence buzzer' (2) buttons pressed at the
same time and disconnect the FDnet plug (X1) from the printed circuit board.
2. Wait at least ten seconds and re-insert the FDnet plug (X1).
The device is set to update mode.
3. Click on the 'FW update standard peripheral device' button in the 'OK' window
and go to 'Update firmware', step 2.
1

FT2011 Front view FT2011 printed circuit board

117
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating firmware of mimic display driver FT2001-A1

30.4 Updating firmware of mimic display driver

FT2001-A1

WARNING

Incorrect assignment between detector/detector group and customer text

Misleading messages in the event of an alarm
Never change the wiring during the firmware update.

The firmware must be updated individually for each mimic display driver.

Preparation
The mimic display driver is fed by a 24 V external power supply or by the FDnet
detector line.
The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
1. Select 'File' > 'Import new resource package'.
2. In the selection window, open an F-Site-XX_x_x_...zip file matching the
'FXS2001'.
3. Connect the PC to the device via the MCL-USB adapter.
FT2001-A1

X2
USB
MC-Link

FDUZ221/FDUZ227

Connection of the PC to the mimic display driver

FDUZ221 MCL-USB adapter (interface USB/MC-LINK)

/
FDUZ227
X2 Connection for the MCL-USB adapter
FT2010 Mimic display driver

118
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating firmware of mimic display driver FT2001-A1
30

Updating the firmware

1. Select 'Update' > 'FW update standard peripheral device'.
The 'FW update standard peripheral device' window opens.
SintesoWorks establishes the connection to the device and sets the device
to update mode.
The latest firmware package and the latest firmware version are suggested.
2. Select the firmware package that matches the 'Site'.
3. Click on 'Start'.
The status bar indicates the update progress.
The 'FW update standard peripheral device' window is closed after
updating.
The device is restarted.
A success message is indicated.
4. Remove the MCL-USB adapter.
The firmware is updated.

Manually setting device to update mode

Proceed as follows if you are prompted to manually set the device to update mode
in step 1:
1. Set the DIP switch S200-1 to 'ON'.
The device is set to update mode.
2. Click on 'FW update standard peripheral device' in the 'OK' window.
3. Set the DIP switch S200-1 to 'OFF'.
4. Go to 'Update firmware', step 2.

X2

21

ON
S200

H201

FT2001-A1 Printed circuit board view

119
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating the firmware of the radio gateway FDCW221

30.5 Updating the firmware of the radio gateway

FDCW221

WARNING

Incorrect assignment between detector/detector group and customer text

Misleading messages in the event of an alarm
Never change the wiring during the firmware update.

The firmware must be updated individually for each radio gateway.

Following a FW update, the radio gateway has to detect all the devices again
before you can switch the 'Line' back on.

NOTICE

'Line' switched back on too soon

'Device location fault' is displayed.
At the end of the FW update, wait until the radio gateway has detected all the
devices again.
The 'Line' may only be switched back on once the radio gateway has detected
all the devices again.

Preparation
The radio gateway is internally fed by a 9 V battery.
The driver for the MCL-USB adapter is installed on the PC.
1. Select the 'File' > 'Import new resource package' menu item.
2. In the selection window, open an F-FXS2001-XX_x_x_...zip file matching the
Site.
3. Open the device and connect the PC via the MCL-USB adapter FDUZ221 or
FDUZ227 to the device.
FDCW221

USB

MC-Link

FDUZ221/FDUZ227

Connection of the PC to the radio gateway

FDUZ221 / MCL-USB adapter (interface USB/MC-LINK)

FDUZ227
FDCW221 Radio gateway

120
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating the firmware of the radio gateway FDCW221
30

Updating the firmware

1. Select the 'Update' > 'FW update standard peripheral device' menu item.
The 'FW update standard peripheral device' window opens.
The tool establishes the connection to the device and sets the device to
update mode.
The latest firmware package and the latest firmware version are suggested.
2. Select the firmware package that matches the 'Site'.
3. Click on 'Start'.
The status bar indicates the update progress.
The 'FW update standard peripheral device' window is closed after
updating.
The device is restarted.
A success message is indicated.
4. Remove the MCL-USB adapter and lock the device.
The firmware is updated.

Manually setting device to update mode

Proceed as follows if you are prompted to manually set the device to update mode
in step 1:
1. Disconnect the MC link cable from the MCL-USB adapter.
2. Hold the end of the MC link cable against the earth terminal of the radio
gateway.
3. Press the Reset button.
The device is set to update mode.
4. Insert the end of the MC link cable in the MCL-USB adapter again.
The tool establishes the connection to the device.
5. Click on the 'FW update standard peripheral device' button in the 'OK' window
and go to 'Update firmware', step 2.

MC-Link FDUZ221
Manual switching to update mode

121
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating the firmware of the radio gateway FDCW241

30.6 Updating the firmware of the radio gateway

FDCW241
You must update the firmware of the radio gateway FDCW241 with a SWING-Tool
and the MCL-USB adapter FDUZ227. You will find information on this in document
A6V10227639. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

30.7 Updating the firmware of the service device

FDUD29x
In this chapter, 'service device' refers to the following devices:
Detector exchanger and tester FDUD292
Intelligent detector tester FDUD293

Service devices FDUD29x with firmware version < 2.0 must be updated to
firmware version 2.0. To do this, contact your Siemens contact partner. From
firmware version 2.0, it is possible to update firmware as described below.

Preparation
The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
The service device FDUD29x has firmware version 2.0
1. Select 'File' > 'Import new resource package'.
2. In the selection window, open the most recent file with the corresponding
language F-FXS2007-XX_x_x_...zip.
3. Connect the PC to the device via the MCL-USB adapter.

USB
MC-Link

FDUD29x
FDUZ221/FDUZ227

PC connection to the service device

FDUZ221 MCL-USB adapter (interface USB/MC-LINK)

/
FDUZ227
FDUD29x Service device

122
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating the firmware of the service device FDUD29x
30

Updating the firmware

1. Select 'Update' > 'FW update FDUD292/3 (intelligent) detector exchanger and
tester'.
The 'FW update FDUD292/3 (intelligent) detector exchanger and tester'
window is opened and you are prompted to perform the switchover
manually.
2. Press buttons '1' and '3' on the device simultaneously and at the same time
switch on the device. If the device has already been switched on, please switch
it off.
SintesoWorks establishes the connection to the device.
3. Click on 'FW update FDUD292/3 (intelligent) detector exchanger and tester' in
the 'OK' window.
The 'FW update FDUD292/3 (intelligent) detector exchanger and tester'
window opens.
SintesoWorks establishes the connection to the device and sets the device
to update mode.
The latest firmware package and the latest firmware version are suggested.
4. Click on 'Start'.
The status bar indicates the update progress.
The 'FW update FDUD292/3 (intelligent) detector exchanger and tester'
window is closed after updating.
The device is restarted.
A success message is indicated.
5. Remove the MCL-USB adapter.
The firmware is updated.

123
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating firmware on the line tester FDUL221

30.8 Updating firmware on the line tester FDUL221

This chapter relates to the line tester FDUL221, device version with MC link
connection, order no. A5Q00022100

Preparation
The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
The line tester is fed either internally with batteries or via a mains adapter.
1. Select 'File' > 'Import new resource package'.
2. In the selection window, open the most recent file with the corresponding
language F-FXS2007-XX_x_x_...zip.
3. Connect the device to the PC via the MCL-USB adapter.

DC USB

FDUL221 FDUZ221/FDUZ227

MC-Link

B
Connect the PC to the line tester

FDUZ221 MCL-USB adapter (interface USB/MC-LINK)

/
FDUZ227
FDUL221 Line tester
DC Supply with network adapter DC 24 V / 625 mA
B Battery compartment 2 x 9 V

If the device has no MC link connection, it is an older device version with an

RS232 connection. You will find more information on this in the next chapter.

124
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating firmware on the line tester FDUL221
30

Updating the firmware

1. Select 'Update' > 'FW update FDUL221 line test device'.
The 'FW update FDUL221 line test device' window opens.
SintesoWorks establishes the connection to the device and sets the device
to update mode.
The latest firmware package and the latest firmware version are suggested.
2. Click on 'Start'.
If the hardware version is not compatible, click on 'Cancel' and check the
hardware version. Replace the hardware and start again at point 1.
The status bar indicates the update progress.
The 'FW update FDUL221 line test device' window is closed after updating.
The device is restarted.
A success message is indicated.
3. Remove the MCL-USB adapter.
The firmware is updated.

Manually setting device to update mode

Proceed as follows if you are prompted to manually set the device to update mode
in step 1:
1. Simultaneously press the ' ', ' ' and ' ' buttons on the device while in the 'FW
update FDUL221 line test device' window pressing 'OK'.
Another 'FW update FDUL221 line test device' window is opened and you
are prompted to release the buttons.
2. Only release the ' ' button.
The device is set to update mode.
3. Release the ' ' and ' ' buttons.
4. Click on the 'FW update FDUL221 line test device' button in the 'OK' window
and go to 'Update firmware', step 2.

125
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
30 Updating firmware on the line tester with serial interface FDUL221

30.9 Updating firmware on the line tester with serial

interface FDUL221
This chapter relates to the line tester FDUL221, device version with RS232
connection, order no. up to A5Q00004397 02

Preparation
The line tester is supplied via a mains adapter.
An RS232 port is available on the PC.
1. Select 'File' > 'Import new resource package'.
2. In the selection window, open the most recent file with the corresponding
language F-FXS2007-XX_x_x_...zip.
3. Connect the device to the PC via the RS232 interface in the battery
compartment.

DC

FDUL221
RS 232

B S

Connect the PC to the serial line tester

FDUL221 Line tester

RS 232 Serial port for the direct connection to the PC
S Serial interface RS 232
DC Supply with network adapter DC 24 V / 625 mA
B Battery compartment

126
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Updating the firmware of the peripheral devices
Updating firmware on the line tester with serial interface FDUL221
30

Updating the firmware

1. Select 'Update' > 'FW update serial FDUL221 line test device'.
The 'FW update serial FDUL221 line test device' window opens.
SintesoWorks establishes the connection to the device and sets the device
to update mode.
The latest firmware package and the latest firmware version are suggested.
2. Click on 'Start'.
The status bar indicates the update progress.
The 'FW update serial FDUL221 line test device' window is closed after
updating.
The device is restarted.
A success message is indicated.
3. Disconnect the connection with the PC.
The firmware is updated.

Manually setting device to update mode

Proceed as follows if you are prompted to manually set the device to update mode
in step 1:
1. Keep the ' ' and ' ' buttons on the device pressed and click on 'FW update
serial FDUL221 line test device' in the 'OK' window.
Another 'FW update serial FDUL221 line test device' window is opened and
you are prompted to release the buttons.
2. Release the buttons.
The device is set to update mode.
Click on the 'FW update serial FDUL221 line test device' button in the 'OK' window
and go to 'Update firmware', step 2.

127
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning external printer
31

31 Commissioning external printer

The external FUJITSU DL3750+ printer can be installed and commissioned using
the operating manual. The operating manual is on the CD delivered with the
printer.
To operate the printer on the fire detection system FS20 settings that differ from
the default values must be made in the following functions.
'MENU 1': Assignment of print functions to MENU1 in the printer Person
Machine Interface.
'MENU 2': Assignment of print functions to MENU2 in the printer Person
Machine Interface.
'HARDWRE': Changing the printer hardware options.
'ADJUST': Changing the setting options for the print position.
'CONFIG': Changing the configuration options.
The printer must be set to configuration mode in order to do this. You will find
information on this in document A6V10224853. See chapter 'Applicable
documents'. The following table shows the options to be set.

Function Value

MENU 1
EMULATE XL24E
FONT COUR 10
QUALITY LETTER
PITCH 10 CPI
LINE SP 6 LPI
CHAR-W NORMAL
CHAR-H NORMAL
ATTRIB NONE
PAGE LG 12.0 IN
LFT-END 1 COLM
TOP-MRG 1 LINE
LANGUAGE LATIN-9
CHR-SET SET1
AGM OFF
PRF-SKP NO-SKIP
ZEROFNT NO-SLSH
CR-CODE CR ONLY
LF-CODE LF & CR
RGHTEND WRAP
==END==

128
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning external printer
31

Function Value

MENU 2
EMULATE DPL24C+
FONT COUR 10
QUALITY LETTER
PITCH 10 CPI
LINE SP 6 LPI
CHAR-W NORMAL
CHAR-H NORMAL
ATTRIB NONE
PAGE LG 11.0 IN
LFT-END 1 COLM
TOP-MRG 1 LINE
LANGUAGE PAGE437
CHR-SET SET2
PRF-SKP NO-SKIP
ZEROFNT NO-SLSH
DC3-CDE ENABLE
CR-CODE CR ONLY
LF-CODE LF & CR
RGHTEND WRAP
==END==
HARDWRE
PPR-OUT DETECT
PRT-DIR BI-DIR
BUZZER ON
WORD-LG 8 BIT
BUFFER NONE
INTRFCE SERIAL
FORMAT 8NONE 1
BAUD-RT 9600
PROTOCL XON/XOF
DSR IGNORE
DUPLEX FULL
CTS IGNORE
CD IGNORE
==END==

129
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Commissioning external printer
31

Function Value

ADJUST
CNT-ORG 1 /6 IN
CNTFINE 1 /180
CUT-ORG 1 /6 IN
CUTFINE 1 /180
CNT-LFT 0 /90
CUT-LFT 0 /90
CUT-ADJ 0 /360
CNT-ADJ 0 /360
CNTADJL 0 /360
==END==
CONFIG
TEAROFF AUTO
TEARPOS VISIBLE
TEAR-EN 4 SEC
CUTLOAD BUTTON
DECODE DIRECT
AREACNT DISABLE
ON-LOAD ONLINE
LOCK NONE
//S// DISABLE
CONT-PE EDGE
GATHER DISABLE
CUT-CTL SPEED
SKIP-PR ENABLE
STATUS ENABLE
BANDCTL ENABLE
TOF-CTL DRIVER
==END==

Settings required

130
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Maintenance
General
32

32 Maintenance

32.1 General
General rule
It is assumed that the 'Site' was commissioned in accordance with the existing
directives, i.e. all functions have been tested and the 'Site' data has been saved
and archived.

Protocol
The measuring values (according to specifications) to be recorded belong to the
technical documentation in the system file.

NOTICE

Non-observance of rules during maintenance work

Insufficient maintenance and damage to the 'Site' or parts thereof
Always de-energize the 'Station' first before connecting, fitting or removing
components.
Prevent electrostatic discharge.
If undertaking work on components, you must use an EMC mat.
Do not touch the modules unnecessarily with your bare hands.
Do not unnecessarily switch off the 'Site' or parts thereof for long periods of
time.

32.2 Spare parts

You will find details for ordering spare parts for 'Stations' in document 009690.
You will find details for ordering Detectors and accessories in document
008164.
See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

131
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Maintenance
32 Testing and measuring instruments

32.3 Testing and measuring instruments

The following table shows an overview of the testing and measuring instruments
used.

Test Required auxiliaries Comment

Voltage, current and resistance measuring Universal measuring instrument Measuring ranges:
Voltage: AC/DC 1…500 V
Current: DC 100 mA…5 A
Resistance: 10 …10 M
Measurement error: 2 %
Internal resistance: 20 k
Testing batteries Battery tester Load resistance: 5
Poll diagnosis data Maintenance PC with SintesoWorks For requirements, see document
009078. See chapter 'Applicable
documents'.
Insert and remove FD20 point detectors Detector exchanger FDUD291, Compatible with all FD20 point
detector exchanger and tester detectors FDOOT, FDO and FDT
FDUD292 or intelligent detector
tester FDUD293
Test FD20 point detectors, Manual call points, Detector exchanger and tester Optionally, proximity or via
input/output modules and alarm devices FDUD292 or intelligent detector adapter cable
tester FDUD293
Test linear smoke detector FDL241-9 Adjustment kit FDLU291 Adjustment device and black
alarm test filter
Test flame detector FDF2x1-9 LE3 Test lamp
Test FDnet detector line Line tester FDUL221

32.4 Preparatory work

Inform the system owner
Inform the system owner of the scope and expected duration of work and also that
'Site' operation will be restricted.
For large-scale systems fill out the system shutdown notification sheet and have
this signed by the system owner.

Block system components

Block the following system components:
Remote alarm (log out on the receiving centre)
'Fire controls' and alarm equipment

Specify the procedure

Stipulate the times for the following test sequences with the system owner:
Test alarms (including remote transmission)
Performance check for 'Fire controls'
Additional instructions (if required)
Clarifications (if required)

132
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Maintenance
Test system data
32

32.5 Test system data

System test manual
Ensure that the system test manual is available and up to date.

Remote transmission
Check that the phone numbers and the names of the remote transmission
receivers are up to date.

Data backup for 'Site'

1. Check that the system data are saved.
Two copies must be archived with the 'Site', one copy with the technical
department.
2. Update the system data when the configuration is changed.
3. Note the date of execution in the system test manual.

Firmware
1. Read out the firmware version from the 'Station': To do this, select 'Topology' >
'Hardware tree' > 'Station' > 'More Options' > 'Show details' in the main menu.
2. Do not replace current firmware versions with the current version if this is not
necessary to correct faults or add functions.

'Event memory'
Check the content of the 'Event memory' and take the necessary measures.

Change in use
Verify whether a change of use or changes to the building have an effect on the
configuration and perform the necessary corrections.

Pending modification applications

Check that all pending modification applications such as corrections to the
diagrams or modifications to the fire brigade orientation plans have been
completed.

32.6 Testing the 'Station'

Check the hardware
Check the condition of the housing and the components.
Check the fixture of screws, terminals and plug connections.
Check that the batteries are not leaking (inspection).

Check labeling
Check that the inscription strips are correct and still easily legible.

133
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Maintenance
32 Check the power supply

Check the function

1. Enter the password.
2. Initiate the lamp test.
3. Check switchover of operating modes from 'Manned operation' to 'Unmanned
operation' and vice versa.
4. Switch an 'Area' off and on again.
5. Check the operation of an alarm.
6. Check the operation of a 'Fault'.
7. Block operation.

Clean the operating unit

Clean the display and the front plate with a wet cloth. Do not use any caustic
solvents!

32.7 Check the power supply

Check the current consumption
1. Measure the current consumption during 'Emergency power operation' and for
alarms with the highest alarm level (local alarm and global alarm).
2. Compare the measurement values with the calculation value for emergency
current capacity.

Checking the batteries

1. Measure the battery voltage (23 V min., max. asymmetry 1 V).
2. Measure the charging current.
3. Check the battery load capacity. The load test should only be performed if the
battery charge current is below 50 mA.
4. Disconnect the batteries from the charger. Do not subject the connections to
strain unnecessarily.
5. Connect the battery tester to both batteries (load resistance 5 ).
6. Test duration for battery 7 Ah: 20 minutes.
7. Test duration for battery 12 Ah: 30 minutes.
8. Measure the battery voltage (when the tester is connected). During the test the
battery voltage should not drop below 11 V per battery and not below 23 V for
both batteries. Always replace both batteries!

Checking for power supply faults

1. Disconnect the mains supply cable.
The following message is displayed: 'Mains failure'.
2. Disconnect the battery supply cable.
The following message is displayed: 'Supply failure'.

Checking the mains supply cable

1. Check whether the site mains supply cable is correctly fuse-protected and
labeled (fire detection system).
2. Check whether installed overvoltage dischargers are in order.

134
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Maintenance
Testing the printer
32

32.8 Testing the printer

1. Check the roll of paper in the printer and ensure that there are spare rolls
available.
2. Initiate the printer test and check the print-out for legibility and correct printing.
3. Check whether the events are correctly printed out.
You will find more information about the printer in document 008838. See chapter
'Applicable documents'.

See also
Applicable documents [ 11]

32.9 Checking 'Site' function

Test the functions of the 'Site' in the various test modes:
You will find information about testing a 'Site' in the chapter 'Testing' in document
008838. See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

32.10 Intervals for testing the system function

'Self test' of 'Detectors'
The 'Self test' is an automatic performance check for FD20 'Detectors'. The
function of the 'Detectors' must be checked regularly on site despite this.

Detector inspection
Annual visual check of all 'Detectors'.
Replace 'Detectors' that are badly soiled or mechanically damaged.

135
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Maintenance
32 Intervals for testing the system function

Function test
The following table shows the intervals recommended for the function check.
National specifications always take priority.

Function Activity Interval

(years)

1 2 5

Software Check date and time. X

Detector lines: Activate an 'Automatic detector' and a 'Manual call point' per 'Line'. X
FDnet Activate all 'Manual call points'. X
Trigger all automatic fire detectors. X
Check all 'Detectors' for soiling and application. X
Check the function of the input/output modules. X
On each 'Line' check whether a short-circuit or open line triggers a X
'Fault'.
Check the loop line function.
During short-circuit also check the separator function.
'Fire controls' Check activation of the 'Controls' up to and with the interface. X
Check the effects of the 'Controls' owned by the customer. Arrange a X
time with the customer.
'Mains failure' Check how long it takes until the 'Emergency power operation' fault
message is displayed during power failure.
Alarm devices In 'Emergency power operation' check all alarm devices taking the X
following event category into account:
'Pre-ALARM'
'ALARM'
'Fault'
Check the remote transmission equipment in accordance with the X
manufacturer's instructions.
Alarm organization Check the function of the delay times t1 and t2. X
Activate a global alarm with an 'Automatic detector' in the 'Unmanned X
operation' operating mode.
Activate a local and global alarm by setting a 'Manual call point' to the X
'Manned operation' and 'Unmanned operation' operating modes.
Check automatic switchover from 'Manned operation' to 'Unmanned X
operation' on the basis of the event memory entries.
Check activation of the remote transmission equipment with 'ALARM'. X
Actuate the corresponding danger level by activating a detector with the X
detector exchanger and tester or intelligent detector tester.

Intervals for the function test

136
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Maintenance
Completion work
32

32.11 Completion work

1. Activate a test alarm through the system operator with remote transmission.
2. Issue subsequent instructions if necessary.
3. Ensure that the system file is available and up to date.
4. Update the system data when the central configuration is changed. Archive a
copy with the 'Site' and a copy in the office.
5. Check the master data sheet (phone no., contact person, etc.).
6. Replace all used material.
7. Cancel all blockings and 'OFF' statuses.
8. Have the revision confirmed by the system owner.

137
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
33 Disconnecting 'Station' from the power supply

33 Repair

33.1 Disconnecting 'Station' from the power supply

Work on an open 'Station', e.g. changing components, cabling, etc. must only be
performed when the 'Station' is current-free. For this purpose the batteries must be
disconnected and the mains connection must be interrupted. The 'Station' cannot
be shut down.

NOTICE

Connecting or removing components during operation

Damage to components
Do not connect or remove components during operation.

You will find information about installing and uninstalling the components in
document 008851. See chapter 'Applicable documents'.

1. First disconnect the negative battery terminals, then the positive terminals.
2. Remove the disconnect terminal block that is mounted on a DIN rail in the
housing.
The mains connection is interrupted.
3. Exchange the components.
4. Re-insert the disconnect terminal block.
The mains connection is intact.
The 'Station' starts.
5. First connect the negative battery terminals, then the positive terminals.
6. Enter the date and time. To do this, select the 'Settings/administration' >
'System commands' > 'Set system time' menu items.
7. If need be, carry out partial commissioning.

Date and time are not saved in the 'Station'. The date and time must be reset to
restart the 'Station'.

33.2 Spare parts

You will find details for ordering spare parts for 'Stations' in document 009690.
You will find details for ordering Detectors and accessories in document
008164.
See chapter 'Applicable documents'.

See also
Applicable documents [ 11]

138
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
Fault messages on the Person Machine Interface
33

33.3 Fault messages on the Person Machine Interface

Fault messages on fire control panel FC20xx / fire terminal FT2040

1
8

10

5 12

Fault messages on the Person Machine Interface

The table below shows the causes and measures should a fault be displayed on a
fire control panel FC20xx or fire terminal FT2040.

LED LED flashes Cause What must be done

1 FAULT The 'Site' has a fault Check whether another fault LED is flashing,
if not:
– Check the display
– Check whether the 'Fault' control input is
activated
5 System Fault Failure of the main CPU Visual check of the cable connections
Check whether the red LED H37 on the
operating unit FCM20xx is on:
– Exchange PMI & mainboard
'Fault' of a component Restart 'Station'
– When the 'Fault' is still indicated:
exchange the module
Communication fault of a Check the transmission line
networked 'Station' Check the faulty 'Station'
8 Remote alarm Fault / Off Transmission equipment has a Check remote transmission
'Fault'
10 Alarm device Fault / Off 'Fault' affecting acoustic control Check the 'Line' for open circuit/short-circuit
lines or end-of-line element (EOL) is missing or
defective
12 Control function Fault / Off 'Fault' affecting fire control lines Check the 'Line' for open line/short-circuit
Check the function of the external control
devices
Check the function, any existing feedback
switch

139
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
33 Fault messages on the Person Machine Interface

Fault messages on fire terminal (Touch) FT2080

2
Fault LEDs on the FT2080

The table below shows the causes and measures should a fault be displayed on a
fire terminal FT2080. Faults are displayed by LEDs and/or symbols in the system
tabs on the display. You will find more information about the layout and functions of
the symbols on the FT2080 touch screen in document A6V10380629. See
'Applicable documents'.

LED Symbol Fault Cause What must be done

1 - FAULT The 'Site' has a fault Check if the fault LED 'System Fault'
is flashing; if it is not:
– Check the display
– Check whether the 'Fault' control
input is activated
2 System Fault Failure of the main CPU Visual check of the cable connections
Check whether the red LED H37 on
the operating unit FCM20xx is on:
– Exchange PMI & mainboard
'Fault' of a component Restart 'Station'
– When the 'Fault' is still indicated:
exchange the module
Communication fault of a Check the transmission line
networked 'Station' Check the faulty 'Station'
- Remote alarm Transmission equipment Check remote transmission
Fault / Off has a 'Fault'

140
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
Fault indicators on components
33

LED Symbol Fault Cause What must be done

- Alarm device Fault 'Fault' affecting acoustic Check the 'Line' for open
/ Off control lines circuit/short-circuit or end-of-line
element (EOL) is missing or defective

- Control function 'Fault' affecting fire control Check the 'Line' for open line/short-
Fault / Off lines circuit
Check the function of the external
control devices
Check the function, any existing
feedback switch

33.4 Fault indicators on components

The components are equipped with LED indicating the status of the component.
You will find the meaning of the indications in document 008837. See chapter
'Applicable documents'.

See also
Applicable documents [ 11]

33.5 Communication problems in networked systems

Date and time are not permanently saved in the 'Station'. If this data is not defined
correctly, it is not possible to communicate with the corresponding 'Station' in the
network or via SintesoWorks.

Date and time

The date and time must be checked regularly for the following reasons:
The deviation of the internal clock is up to four minutes per month.
When data is downloaded, and when a 'Station' is restarted, the internal clock
does not continue working.
If a 'Station' is de-energized, the date and time of the internal clock is lost.

Moving the network cable from one 'Station' to the next

Wait at least two minutes before inserting the cable into the next 'Station'.
If 'Stations' are fitted close to one another, you may be able to move the network
cable from one 'Station' to the next without first having to execute the
'Commissioning' > 'Disconnect' command in SintesoWorks. If this is done, a
connection cannot be immediately re-established on the next 'Station'.

141
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
33 Non-stationary devices of the same type have been swapped over

33.6 Non-stationary devices of the same type have been

swapped over
When FDnet devices have been swapped over in their bases, e.g. while work is
carried out, the 'Line' is not fault-free.
The following message is shown on the display of the Person Machine Interface for
each FDnet device that has been swapped over:
'Zone', 'Serial no. ("ID-Nr.")', 'Device missing'
If the FDnet detector line was restarted, the following message is displayed for
each swapped FDnet device:
'Zone', 'Serial no. ("ID-Nr.")', 'Dev.location fault'
To enable the 'Station' to become fault-free again, at least the device types in the
corresponding bases must be correct. 'Faults' of FDnet devices of the same type
that have been swapped over can then be rectified using the Person Machine
Interface without having to find the original base.

Procedure

You will find additional information about the individual steps on the specified
pages.

1. Rectify localization errors. Link [ 41]

2. Connect the PC to the 'Station'. Link [ 25]
3. Load the configuration from the 'Station' to the PC. Link [ 30]
4. Disconnect the PC from the 'Station'. Link [ 25]

142
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
Error message 'Topology is invalid'
33

33.7 Error message 'Topology is invalid'

If the topology of a FDnet detector line is invalid, after the detector line has been
read in, the error message 'Topology is invalid' is displayed. The table below shows
invalid topologies.

Stub on stub or loop interrupted

Stub on stub on loop

Several stubs starting from same

location on loop

Loop on loop

Invalid topologies

Troubleshooting
1. Check the detector line with the line tester FDUL221. You will find information
on this in document 008250. See chapter 'Applicable documents'.
2. Create a valid topology:
- Rectify the fault by changing over the wiring or plan the detector line again.
- If there are several stub outputs between two FDnet devices, change over
the wiring or add a line separator FDCL221 between each stub.
3. Read in the FDnet detector line again.

See also
Read in devices on detector line [ 38]

143
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
33 Error message 'Too many devices'

33.8 Error message 'Too many devices'

If the error message 'Too many devices' is displayed after you have removed and
added devices on an active line, run the following command: 'Restart line'.

33.9 Restart 'Station'

The configuration of the 'Station' remains the same.

There are the following ways in which to restart the 'Station':

Via the menu on the display
PMI & mainboard FCM2004 and FCM2027: With the 'S32' button
CPU card: With the 'S8' button

Via the menu on the display

If you are using two CPU cards, you must perform the following procedure once for
each CPU card.
1. Press <MENU>.
The PIN input dialog is indicated.
2. Enter a valid PIN and confirm with <ok>.
The 'User successfully logged in' message is displayed.
The main menu is displayed.
3. Select the 'Topology' > 'Hardware tree' > 'Station' menu items.
The elements of the 'Station' are listed.
4. Select module 101 or module 102 'CPU (FCC2001/06)'.
5. Press the 'More Options' softkey and select 'Execute commands'.
6. Select the 'Reset module' command.
The 'Station' restarts.
After a few minutes, the 'Buzzer' sounds twice.
7. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.

144
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
Restart 'Station'
33

PMI & mainboard FCM2004 and FCM2027

The switches S38-1 and S38-2 are set to the 'OFF' position on the PMI &
mainboard FCM2004.
1. On the PCB of the operating unit, press and hold down the 'S32' button for
< 2 s.
The 'Station' restarts.
After a few minutes, the 'Buzzer' sounds twice.
2. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.

CPU card
1. Briefly press the 'S8' button on the CPU card until a 'R' is displayed on the LED
matrix display.
2. As soon as the 'R' is displayed, press and hold the 'S8' button for approx. 2 s to
confirm the selection.
A checkmark on the LED matrix display confirms the selection.
The CPU card is restarted.

You will find information about the CPU card FCC2004, the LED matrix display
and operating the 'S8' button in document 008837. See chapter 'Applicable
documents'.

See also
Applicable documents [ 11]

145
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
33 Restoring factory setting on the 'Station'

33.10 Restoring factory setting on the 'Station'

There are the following ways in which to restore the factory setting on the 'Station':
Via the menu on the display
PMI & mainboard FCM2004 and FCM2027: With the 'S32' button
CPU card: With the 'S8' button

NOTICE

Restoring factory setting on the 'Station'

The configuration of the 'Station' is deleted!
Save the configuration data for the 'Station' before restoring the factory
setting.

Via the menu on the display

1. Press <MENU>.
You are prompted to enter a PIN.
2. Enter a valid PIN and confirm with <ok>.
The 'User successfully logged in' message is displayed.
The main menu is displayed.
3. Select the 'Topology' > 'Hardware tree' > 'Station' menu items.
4. Press the 'More Options' softkey and select 'Execute commands'.
5. Select the 'Factory reset' command.
The 'Station' restarts.
After a few minutes, the 'Buzzer' sounds twice.
6. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.
7. Enter the date and time. To do this, select the 'Settings/administration' >
'System commands' > 'Set system time' menu items.

146
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
Restoring factory setting on the 'Station'
33

PMI & mainboard FCM2004

1. Set the 'S38-1' switch to 'ON' on the rear of the operating unit.
2. Press the 'S32' button for > 2 s until the 'Station' restarts.

The 'Station' restarts.

3. Set the 'S38-1' switch to 'OFF' after the restart.
After a few minutes, the 'Buzzer' sounds twice.
4. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.
5. Enter the date and time. To do this, select the 'Settings/administration' >
'System commands' > 'Set system time' menu items.

PMI & mainboard FCM2027

1. Keep the 'S32' button on the rear of the operating unit pressed and
simultaneously press <Reset> on the Person Machine Interface at the same
time until the 'Station' restarts (>2 s).

The Station restarts.

After a few minutes, the 'Buzzer' sounds twice.
2. Press <Acknowledge> on the Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.
3. Enter the date and time. To do this, select the 'Settings/administration' >
'System commands' > 'Set system time' menu items.

147
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Repair
33 Restoring factory setting on the 'Station'

CPU card
1. Briefly press the 'S8' button on the CPU card several times until a 'F' is
displayed on the LED matrix display.
2. As soon as the 'F' is displayed, press and hold the 'S8' button for approx. 2 s to
confirm the selection.
A checkmark on the LED matrix display confirms the selection.
The CPU card is restarted.

You will find information about the CPU card FCC2004, the LED matrix display
and operating the 'S8' button in document 008837. See chapter 'Applicable
documents'.

See also
Applicable documents [ 11]

148
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Index

Index
Configuration
A Conversion, 101
Acceptance test, 20 Load to station, 26, 28
Alarm counter, 95 Loading to PC, 30
AnalogPLUS detector line, 79 Connecting a sub-stub to a loop
Converting a loop, 82 FDnet/C-NET detector line, 72
Converting a stub, 82 Connection to the station, 25
Expand, 80 Connectivity, 25
Removing a device, 81 Conversion, 101
Replacing a device (stationary), 82 Configuration, 101
Replacing a device with one of a different type, Convert stubs into loops
80
FDnet/C-NET detector line, 72
Replacing a device with one of the same type
Converting a loop
(non-stationary), 81
AnalogPLUS detector line, 82
Replacing an I/O module, 82
Interactive detector line, 88
Replacing multiple devices, 81
Converting a stub
Auto-configuration, 42
AnalogPLUS detector line, 82
Definition of terms, 22
Interactive detector line, 88
Detector line, 36
CPU
station, 35
Updating the firmware, 102
B CPU (other)
Back-up, 30 Updating the firmware, 108
Base sounder, 90 Customer text, 43

C D
Collective detector line, 74 Date/time, 141
Error messages, 75 Deleting
Testing, 76 Device, 39
Troubleshooting, 76 Detector
Commissioning, 21 Test mode, 39
According to wiring sequence, 19 Testing, 93, 94
Auto-configuration, 42 Detector exchanger and tester
Networked station, 47 Updating the firmware, 122
Overview, 21 Detector exchanger and tester FDUD292, 94
Standalone station with PC, with pre- Detector inspection, 135
configuration, 46 Detector line
Standalone station with PC, without pre- Auto-configure, 36
configuration, 45
Install, 19
Standalone station without PC, 42
ON, 37
With serial number, 19
Restart, 37
Without PC, 42
Switch off, 37
Communication problems, 141
Testing, 19
Component
Detector self-test, 135
Indication of faults, 141
Detector tester, 94

149
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Index

Device FDUD292 Detector exchanger and tester, 94

Remove, 67 FDUD293 intelligent detector tester, 94
Swapped, 142 FDUD29x
Download, 26, 28 Updating the firmware, 122
Download center FDUL221 line tester
URL, 11 Updating the firmware, 124
FDUL221 serial line tester
E Updating the firmware, 126
End-of-line element (EOL)
FDUZ221 MCL-USB adapter
Reference measurement for collective detector
Updating the firmware, 112
line, 75
FG2020, 49
Error message
Fire brigade periphery module FCI2001-D1, 91
Collective detector line, 75
Firewall
'Topology is invalid', 143
Security module (firewall) FN2009-A1, 54
Ethernet switch (MM) FN2008 A1, 51
Windows firewall, 32, 95
Event memory, 95
Floor repeater display
Expand
Updating the firmware, 116
AnalogPLUS detector line, 80
Floor repeater terminal
FDnet/C-NET detector line, 65
Updating the firmware, 114
Interactive detector line, 86
FN2008 A1
Site, 50
Ethernet switch (MM) FN2008-A1, 51
External printer, 128
FN2009-A1 safety, 54
F FT2001-A1 mimic display driver
Factory reset, 146 Updating the firmware, 118
Factory setting, 146 FT2010 floor repeater terminal
Fault indicators, 139 Updating the firmware, 114
FT2080, 140 FT2011 floor repeater display
FC2080, 48 Updating the firmware, 116
FCI2007-A1 I/O card (RT), 92 FT2080
FCI2009-A1 I/O card (horn/monitored), 92 Fault indicators, 140
FDCW221 radio gateway Operation, 24
Updating the firmware, 120 FUJITSU DL3750+, 128
FDnet/C-NET detector line Function test, 41, 135, 136
Connecting a sub-stub to a loop, 72 Fuse, 30
Convert stubs into loops, 72
Expand, 65
H
Hardware reset
Removing a device (non-stationary), 68
station, 144
Removing a device (stationary), 67
Removing a device temporarily, 68 I
Replacing a device with one of a different type I/O card (horn/monitored) FCI2009-A1, 92
(non-stationary), 69
I/O card (RT) FCI2007-A1, 92
Replacing a device with one of the same type
Indication of faults
(non-stationary), 69
Component, 141
Replacing a device with one of the same type
(stationary), 66 Initialize
Replacing manual call points, 70 station, 26, 26

150
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Index

Install N
Detector line, 19 Network cable
Intelligent detector tester Moving, 141
Updating the firmware, 122 Networked station, 47
Intelligent detector tester FDUD293, 94 Normal operation, 40
Interactive detector line, 84
Converting a loop, 88
O
ON
Converting a stub, 88
Detector line, 37
Expand, 86
Operation
Removing a device, 86
Fire control panel, 23
Replacing a device with one of a different type,
86 Fire terminal, 23
Replacing a device with one of the same type FT2080, 24
(non-stationary), 87
P
Replacing an I/O module, 87
Password, 102, 104, 106, 108, 110
Replacing manual call points (stationary), 88
PC
Interactive Ex detector line, 84
Connect to station, 25
L Disconnecting from station, 25
License, 24 PMI
Line resistance Fault indicators, 139
Testing, 77 Power supply
Line tester Configuring, 43
Updating the firmware, 124 Testing, 134
Load Pre-configuration
From PC to station, 26, 28 Definition of terms, 22
From station to PC, 30 Primary Setup Tool, 52
Load data to PC Printer
Site, 30 Testing, 135
Load data to the station Product version, 90
Site, 28
R
Localization error, 41
Radio gateway
M Updating the firmware, 120
Main CPU Radio gateway FDCW221, 122
Updating the firmware, 102 Updating the firmware, 122
Maintenance, 131 Radio gateway FDCW241, 122
MCL-USB adapter Updating the firmware, 122
Updating the firmware, 112 Read in
Measuring instrument, 132 Definition of terms, 22
Merge Device, 38
Sites, 62 Reference measurement for collective detector line
Mimic display driver End-of-line element (EOL), 75
Updating the firmware, 118 Remove
MS9i detector line, 73 Device, 67

151
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Index

Removing a device Site

AnalogPLUS detector line, 81 Expand, 50
Interactive detector line, 86 Load data to PC, 30
Removing a device (non-stationary) Load data to the station, 28
FDnet/C-NET detector line, 68 Merge, 62
Removing a device (stationary) Test intervals, 135
FDnet/C-NET detector line, 67 Sounder base FDSB291, 90, 90
Removing a device temporarily Spare parts, 131, 138
FDnet/C-NET detector line, 68 Stand-alone station, 42, 45, 46
Replacing a device (stationary) station
AnalogPLUS detector line, 82 Auto-configure, 35
Replacing a device with one of a different type Disconnect power, 138
AnalogPLUS detector line, 80 Factory setting, 146
Interactive detector line, 86 Hardware reset, 144
Replacing a device with one of a different type (non- Initialize, 26, 26
stationary) Load data, 26
FDnet/C-NET detector line, 69 Mount and install, 20
Replacing a device with one of the same type (non- Resetting, 146
stationary)
Restart, 144
AnalogPLUS detector line, 81
Switching off, 138
FDnet/C-NET detector line, 69
Swapped
Interactive detector line, 87
Device, 142
Replacing a device with one of the same type
Switch off
(stationary)
Detector line, 37
FDnet/C-NET detector line, 66
Switching off
Replacing an I/O module
station, 138
AnalogPLUS detector line, 82
System data, 133
Interactive detector line, 87
Replacing manual call points T
FDnet/C-NET detector line, 70 Test, 41, 135
Replacing manual call points (stationary) Test intervals, 135, 135
Interactive detector line, 88 Test mode, 39
Replacing multiple devices Detector, 39
AnalogPLUS detector line, 81 Exit, 40
Restart Test unit, 132
station, 144 Testing
Collective detector line, 76
S
Detector, 93, 93, 94, 94
Scalance X204 2, 51
Detector line, 19
Security module (firewall) FN2009-A1, 54
Function, 136
Serial line tester
Line resistance, 77
Updating the firmware, 126
Power supply, 134
Series number, 19
Printer, 135
Set parameter set
System data, 133
Use Person Machine Interface, 44
Time/date, 141
Topology is invalid, 143

152
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
 Index

Troubleshooting
Collective detector line, 76

U
Uninstalling
Device, 38
Update BDV, 100
Updating the firmware
Additional CPUs, 108
Main CPU and additional CPUs, 102
Periphery devices, 112
station, 95
Upload, 30

W
Windows firewall, 32, 95

Z
Zone
ON, 38
Switch off, 38

153
Building Technologies 009052_q_en_--
Fire Safety 2014-01-15
Issued by © 2006-2014 Copyright Siemens Switzerland Ltd
Siemens Switzerland Ltd Technical specifications and availability subject to change without notice.
Infrastructure & Cities Sector
Building Technologies Division
International Headquarters
Gubelstrasse 22
CH-6301 Zug
Tel. +41 41-724 24 24
www.siemens.com/buildingtechnologies

Document ID 009052_q_en_-- Manual FS20

Edition 2014-01-15 Register 6