FS720 Fire Detection System: Commissioning Maintenance Troubleshooting

FS720
Fire detection system

Commissioning
Maintenance
Troubleshooting
IP5
A6V10210416_h_en_-- Building Technologies

2014-03-26 Control Products and Systems
Legal notice
Legal notice
Technical specifications and availability subject to change without notice.
© 2008-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-03-26
Document ID: A6V10210416_h_en_--
2
Building Technologies A6V10210416_h_en_--
Fire Safety 2014-03-26
Table of contents
1 About this document ......................................................................................7

1.1 Applicable documents.......................................................................................9
1.2 Download center...............................................................................................9
1.3 Technical terms .............................................................................................. 10
1.4 History of changes .......................................................................................... 10
2 Safety ............................................................................................................ 12
2.1 Safety instructions .......................................................................................... 12
2.2 Safety regulations for the method of operation ................................................ 13
2.3 Standards and directives complied with ..........................................................15
2.4 Release Notes ................................................................................................ 15
3 Mounting/Installation ....................................................................................16
3.1 Installing and checking the detector line .......................................................... 16
3.1.1 Installing devices with serial number ................................................ 16
3.1.2 Installing devices according to the wiring sequence .......................... 16
3.1.3 Checking the detector line ................................................................ 16
3.2 Mount and install 'Station' ............................................................................... 17
4 Commissioning – overview .......................................................................... 18
4.1 Commissioning variants .................................................................................. 18
4.2 Definition of terms........................................................................................... 19
4.3 Standard gateway ........................................................................................... 20
4.4 Brief instructions on operating the 'Station' ...................................................... 20
4.5 License ........................................................................................................... 21
5 Connectivity and communication with 'Station'.......................................... 22
5.1 Connecting the PC to the station..................................................................... 22
5.2 Disconnecting PC from the 'Station' ................................................................ 22
5.3 Loading data to the 'Station' ............................................................................ 23
5.4 Initializing 'Station' .......................................................................................... 23
5.5 Loading configuration from the PC to the 'Station' ........................................... 25
5.6 Loading configuration from the 'Station' to the PC ........................................... 26
5.7 Creating a back-up of the 'Site' configuration................................................... 27
6 General commissioning steps ..................................................................... 29
6.1 Preparing 'Station' for commissioning.............................................................. 29
6.2 Preparing 'Station' for commissioning – without BDV installation ..................... 30
6.3 Auto-configuring 'Station' ................................................................................ 30
6.4 Auto-configuring the detector line.................................................................... 31
6.5 Loading automatically created configuration to the PC .................................... 31
6.6 Adapting configuration .................................................................................... 32
6.7 Switch on detector line.................................................................................... 32
6.8 Switching off the detector line ......................................................................... 32
6.9 Restarting the detector line ............................................................................. 33
6.10 Switching off 'Zone' ......................................................................................... 33
3
6.11 Switching on 'Zone'......................................................................................... 33
6.12 Read in devices on detector line ..................................................................... 33
6.13 Detaching the device ...................................................................................... 34
6.14 Delete the device on Person Machine Interface .............................................. 34
6.15 Remove the elements ..................................................................................... 34
6.16 Switching on test mode................................................................................... 35
6.17 Switch on normal operation ............................................................................ 35
6.18 Rectify localization errors ................................................................................ 36
6.19 Checking 'Site' function................................................................................... 36
6.20 Completion work ............................................................................................. 37
7 A - Commissioning stand-alone 'Station' without PC ................................. 38
7.1 Configuring the power supply.......................................................................... 39
7.2 Entering customer texts using the Person Machine Interface .......................... 39
7.3 Setting detector parameter sets ...................................................................... 40
8 B1 - Commissioning stand-alone 'Station' with PC, without pre-
configuration ................................................................................................ 41
9 B2 - Commissioning stand-alone 'Station' with PC,
with pre-configuration .................................................................................. 42
10 C- Commissioning networked 'Stations' ..................................................... 43
11 Adding a 'Station' to an existing 'Site' ......................................................... 44
12 Merging two 'Sites' ....................................................................................... 45
12.1 Adding 'Site' B to 'Site' A ................................................................................. 46
12.2 Connecting 'Sites' physically to one another.................................................... 48
13 Changing and expanding the FDnet/C-NET detector line ........................... 49
13.1 Extending the detector line to include additional devices ................................. 49
13.1.1 Mount and wire new devices ............................................................ 49
13.1.2 Configure a new device.................................................................... 50
13.2 Replacing stationary devices of the same type................................................ 50
13.3 Permanently removing stationary devices ....................................................... 51
13.4 Removing or replacing non-stationary devices ................................................ 51
13.4.1 Base with loop contact ..................................................................... 51
13.4.1.1 Temporarily removing an individual non-stationary device ................ 51
13.4.1.2 Replacing non-stationary devices of the same type .......................... 52
13.4.1.3 Replacing non-stationary devices of different types .......................... 53
13.4.2 Base without loop contact ................................................................ 53
13.4.2.1 Temporarily removing an individual non-stationary device ................ 54
13.4.2.2 Replacing non-stationary devices of the same type .......................... 54
13.4.2.3 Replacing a non-stationary device of a different type........................ 55
13.4.3 Temporarily removing multiple non-stationary devices...................... 55
13.4.4 Permanently removing non-stationary devices ................................. 56
13.5 Replacing 'Manual call point' of the same type ................................................ 57
13.5.1 Switching on the replace mode ........................................................ 57
13.5.2 Switching off replace mode .............................................................. 58
13.5.3 Testing 'Manual call point' ................................................................ 58
13.6 Convert two stubs into a loop .......................................................................... 58
4
13.7 Connecting a sub-stub to a loop...................................................................... 59
14 Commissioning Ethernet switch (MM) FN2008-A1 ...................................... 60
14.1 Install Primary Setup Tool ............................................................................... 61
14.2 Assign IP address........................................................................................... 61
14.3 Configure FN2008-A1 using Internet browser.................................................. 62
15 Commissioning safety module (firewall) FN2009-A1 .................................. 63
15.1 Installing Security Configuration Tool .............................................................. 64
15.2 Selecting type and entering MAC address.......................................................64
15.3 Entering network settings................................................................................ 65
15.4 Creating IP service definitions......................................................................... 68
15.5 Creating firewall rules ..................................................................................... 69
16 Commissioning the fire brigade periphery module FCI2001-D1................. 71
17 Commissioning I/O card (remote transmission) FCI2007-A1
and I/O card (horn/monitored) FCI2009-A1 .................................................. 72
18 Testing detectors.......................................................................................... 73
18.1 Activate the detector ....................................................................................... 73
18.2 Testing logged test activations ........................................................................ 73
19 Updating the firmware of the 'Station' .........................................................74
19.1 Preparation and security ................................................................................. 74
19.2 Updating the firmware of the main CPU and the additional CPUs – Overview . 75
19.2.1 Standalone station and SAFEDLINK station ..................................... 75
19.2.2 Router station and Ethernet station .................................................. 76
19.2.3 Updating several 'Stations' simultaneously ....................................... 76
19.3 Updating the firmware of the additional CPUs only – Overview........................ 77
19.4 Update only the BDV ...................................................................................... 78
19.5 Converting the configuration ........................................................................... 79
19.6 Setting Windows firewall ................................................................................. 80
19.7 Updating the firmware of the main CPU and the additional CPUs .................... 80
19.7.1 PMI & mainboard FCM2004 ............................................................. 80
19.7.2 PMI & mainboard FCM2027 ............................................................. 82
19.8 Update the firmware of the additional CPUs .................................................... 86
19.9 Testing the firmware version of the additional CPUs........................................ 87
19.10 Creating diagnosis report ................................................................................ 88
20 Updating the firmware of the peripheral devices ........................................ 89
20.1 Updating the firmware of the MCL-USB adapter FDUZ22x .............................. 89
20.2 Updating the firmware of the floor repeater terminal FT2010 ........................... 90
20.3 Updating the firmware of the floor repeater display FT2011 ............................. 92
20.4 Updating firmware of mimic display driver FT2001-A1 ..................................... 94
20.5 Updating the firmware of the radio gateway FDCW241 ................................... 96
20.6 Updating firmware on the line tester FDUL221 ................................................ 96
20.7 Updating firmware on the line tester with serial interface FDUL221 ................. 98
5
21 Commissioning external printer ................................................................ 100
22 Maintenance................................................................................................ 103
22.1 General ........................................................................................................ 103
22.2 Spare parts................................................................................................... 103
22.3 Testing and measuring instruments .............................................................. 103
22.4 Preparatory work .......................................................................................... 104
22.5 Test system data .......................................................................................... 104
22.6 Testing the 'Station' ...................................................................................... 105
22.7 Check the power supply ............................................................................... 106
22.8 Testing the printer......................................................................................... 107
22.9 Checking 'Site' function................................................................................. 107
22.10 Intervals for testing the system function ........................................................ 107
22.11 Completion work ........................................................................................... 108
23 Repair .......................................................................................................... 109
23.1 Disconnecting 'Station' from the power supply............................................... 109
23.2 Spare parts................................................................................................... 109
23.3 Fault messages on the Person Machine Interface ......................................... 110
23.4 Fault indicators on components .................................................................... 111
23.5 Communication problems in networked systems ........................................... 111
23.6 Non-stationary devices of the same type have been swapped over ............... 111
23.7 Error message 'Topology is invalid' ............................................................... 112
23.8 Error message 'Too many devices' ............................................................... 113
23.9 Restart 'Station' ............................................................................................ 113
23.10 Restoring factory setting on the 'Station' ....................................................... 114
Index ........................................................................................................... 117
6
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 FS720. More information can
be found in the corresponding documents under 'Applicable documents'.
To understand this document, you must have complete knowledge of document

A6V10210355. See chapter 'Applicable documents'.
Scope
The information contained in this document is valid for introduction package IP5.
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 Has obtained suitable specialist training for
of installation according to the function and for the products.
customer-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
7
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.
8
About this document
Applicable documents
1
1.1 Applicable documents

Document ID Title
A6V10210355 FS720 Fire Detection System, System Description

A6V10210362 FS720 Fire Detection System, Planning
A6V10210368 FS720 Fire Detection System, Product Data
A6V10210390 FS720 Fire Detection System, Mounting / Installation
A6V10210424 FS720 Fire Detection System, Configuration
A6V10211076 FC72x/FT724, Fire Control Panel / Fire Terminal, Operation
A6V10212047 Automatic Fire Detector, Technical Manual
A6V10224853 FS20/FS720 Fire Detection System, External Printer,
Application Note
A6V10225323 FD720 Cerberus PRO, Synova, AlgoRex Detector System,
Equipment Overview
A6V10227639 FDCW241 radio gateway, technical manual
A6V10227652 FS720 Cerberus PRO Fire Detection System, Components /
Spare Parts / Repair Parts
A6V10229261 List of compatibility
A6V10260976 FS720 Fire Detection System, Site Conversion
008250 FDUL221 Line Tester, Operation
008860 FT201x, floor repeater terminal / floor repeater display,
installation
009771 Open-source software (OSS) licenses
009854 FDUZ221 MCL-USB adapter, Installation
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.
9
About this document
1 Technical terms
1.3 Technical terms

Term Explanation
AI Alarm indicator
BDV Base data variant
C-NET Addressed detector line
ES Product version
MCL Maintenance and commissioning link
'MCP' Abbreviation for 'Manual call point'
You will find additional technical terms and their explanation in document
A6V10210355, in the chapter 'Glossary'. See chapter 'Applicable documents'.
See also
Applicable documents [ 9]
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
h 2014-01-13 FDUZ227 added to various chapters: May be used instead of FDUZ221

g 2013-11-14 Edition for IP5
Change to date format according to ISO 8601
New:
Standard gateway pre-configured for stand-alone stations
Revised:
Firmware update updated
Replacing a device without Cerberus-Engineering-Tool
CPR replaces CPD: The Construction Products Regulation (CPR 305/2011) replaces the
previous Construction Products Directive (CPD 89/106).
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'
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 C-NET detector lines
'Definition of terms' chapter revised
f 2013-01 Chapter 'Setting Windows firewall' updated for Windows 7
10
About this document
History of changes
1
Version Edition date Brief description
e 2012-05 Edition for IP4

New: Revised:
Updating the firmware of the main CPU Creating diagnosis report
and additional CPUs in a single step Restart the station
Addition to chapter 'Setting Windows Checking 'Site' function
firewall', for Windows 7
Restoring factory settings
Updating several 'Stations'
simultaneously Checking the detector line
Update the firmware of the additional
CPUs via GAP
Creating a back-up of the 'Site'
configuration
Replacing C-NET 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 FDCW241
FDCW221 removed
Commissioning of I/O card (remote
transmission) FCI2007-A1 and I/O card
(horn/monitored) FCI2009-A1
d 2010-07 Edition for MP3.0 XS:
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 the firmware of the 'Station'", "Restarting 'Station'", "Restoring
'Station' to factory setting", "Loading configuration from the PC to the 'Station'"
Chapter structure changed
c 2009-08 Modifications for MP1XS
b 2009-05 Modifications for MP1XS
a 2008-11 First edition
11
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.
12
Safety
Safety regulations for the method of operation
2
How risk of injury is presented

Information about the risk of injury is shown as follows:
WARNING

Measures / prohibitions for danger avoidance
How possible damage to property is presented

Information about possible damage to property is shown as follows:
NOTICE

Measures / prohibitions for danger avoidance
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.
13
Safety
2 Safety regulations for the method of operation
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.
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.
14
Safety
Standards and directives complied with
2
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
2.3 Standards and directives complied with

A list of the standards and directives complied with is available from your Siemens
contact.
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.
15
Mounting/Installation
3 Installing and checking the detector line
3 Mounting/Installation
3.1 Installing and checking the detector line

Most C-NET devices are installed on a base and can be changed with ease.
The bases of non-stationary C-NET devices and stationary C-NET devices must be
installed and uninstalled when the C-NET detector line is switched off and
disconnected from the power supply.
Prerequisites
The C-NET detector line is not connected to the control panel and is
disconnected from the power supply when the C-NET devices are being
installed, wired and inserted.
The C-NET 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 C-NET 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 C-NET 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 C-NET 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.
3.1.3 Checking the detector line
NOTICE
Simultaneous connection of line tester and C-NET detector line to the control
panel
Damage to line tester or control panel
Do not connect the line tester and the C-NET detector line to the control panel
at the same time.
16
Mounting/Installation
Mount and install 'Station'
3
Acceptance test
The C-NET detector line is not connected to the control panel.
1. Connect the line tester FDUL221 to the newly installed C-NET detector line.
2. Test the C-NET detector line for short-circuits, open lines and earth faults.
3. Check the number of the devices on the C-NET 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 C-NET 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 C-NET 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
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 A6V10210390 document. See chapter 'Applicable documents'.
See also
17
Commissioning – overview
4 Commissioning variants
4 Commissioning – overview
The 'Stations' on the C-WEB, such as control panels FC722/FC724 and fire
terminals FT724 and FT2080, are connected to the power supply and
commissioned by the installation and commissioning personnel.
Networked 'Stations' must only be commissioned with Cerberus-Engineering-
Tool.
Standalone control panels can be commissioned with or without Cerberus-
Engineering-Tool.
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 IP5 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 IP5.
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.

Cerberus- configuration Auto-configuration
Engineering- possible
Tool Adaptations on the Person Machine
Interface
With Cerberus- Without pre- B1 C
Engineering- configuration Auto-configuration Initialize the 'Stations' for networking
Tool
Adaptations in Cerberus-Engineering- Read in the C-NET devices by line
Tool Assign the logical elements in
With pre- B2 Cerberus-Engineering-Tool
configuration Read in the devices by line
Assign the logical elements in
Cerberus-Engineering-Tool
Commissioning variants
18
Definition of terms
4
4.2 Definition of terms

Auto-configuration Auto-configuration is performed using a command on the Person Machine Interface. In this
process, the C-NET devices are read in and a configuration created.
There are two types of auto-configuration.
Auto-configuration of an individual C-NET detector line
Auto-configuration of 'Station'
Auto-configuration results in the following:
One 'C-NET' 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 C-NET 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 Cerberus-Engineering-Tool 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 C-NET 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 'C-NET' and 'Detection 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.
19
4 Standard gateway
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
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'

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
20
License
4
4.5 License
When the data is first loaded from the PC to the 'Station', the 'Station' receives the
license from Cerberus-Engineering-Tool. Communication between the 'Station' and
Cerberus-Engineering-Tool is then only possible with a valid license.
21
Connectivity and communication with 'Station'
5 Connecting the PC to the station
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 FS720 network' chapter in document
See also
5.1 Connecting the PC to the station

For most commissioning, maintenance and repair work a PC with installed
Cerberus-Engineering-Tool is required. The figure below shows the connection
between the PC and 'Station'.
LAN 11
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 Cerberus-Engineering-Tool.
2. Disconnect the cable connection between PC and 'Station'.
3. Wait 2 min. before you establish a connection to another 'Station'.
22
Loading data to the 'Station'
5
5.3 Loading data to the 'Station'

Data is loaded from Cerberus-Engineering-Tool 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 A6V10210424. 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
Loading configuration from the PC to the 'Station' [ 25]
Initializing 'Station' [ 23]
5.4 Initializing 'Station'

Each 'Station' in a 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 Cerberus-Engineering-Tool.
A standalone 'Station' does not have to be initialized.
23
5 Initializing 'Station'
'Initialize 'Station'
NOTICE
Connection module (card cage) FCA2006-A1 defective or installed incorrectly

Control panels identified incorrectly, e.g. FC726 identified as FC724.
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'.
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' [ 23]
24
Loading configuration from the PC to the 'Station'
5
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 Cerberus-Engineering-Tool on the PC into the 'Station'.
NOTICE
Different network configuration in 'Cerberus-Engineering-Tool' 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.
The 'Site' is opened in Cerberus-Engineering-Tool.

The PC is connected to the 'Station'.
Networked 'Stations' are initialized.
'Station' and Cerberus-Engineering-Tool have the same 'Site' ID.
'Station' and Cerberus-Engineering-Tool 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 'Download site' are listed in the 'Stations' window.
3. Select the 'Stations' whose configuration you would like to load from 'Cerberus-
Engineering-Tool' 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 <Station> on the 'MENU', enter the PIN and
press <ok>.
25
5 Loading configuration from the 'Station' to the PC
4. Click on 'Set access level' in the 'OK' 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.
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' [ 23]
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
Cerberus-Engineering-Tool on the PC.
The PC is connected to the 'Station'.
'Station' and Cerberus-Engineering-Tool have the same 'Site' ID.
'Station' and Cerberus-Engineering-Tool are in the same organizational unit.
1. Select 'Commissioning' > 'Upload site'.
The 'Upload site' and 'Connect' windows are opened.

The 'Stations' are listed in the 'Upload site' window.
26
Creating a back-up of the 'Site' configuration
5
3. Select the 'Stations' whose configuration you would like to load to Cerberus-
Engineering-Tool and click on 'Start'.
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
Cerberus-Engineering-Tool.
The BDVs for all 'Stations' must be compatible with the BDV for the 'Site'
loaded in Cerberus-Engineering-Tool.
– 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 Cerberus-Engineering-Tool.
You will find Information about BDV names and versions in document
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.
Creating a back-up
The PC is connected to a 'Station'.
1. Select 'Commissioning' > 'Create backup embedded configuration'.
The 'Create backup embedded configuration' and 'Connect' windows are
opened.
27
5 Creating a back-up of the 'Site' configuration

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\FX7230
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'.
28
General commissioning steps
Preparing 'Station' for commissioning
6
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-FXS7211 is displayed.
3. Wait until the display indicates the selection of the BDV.
4. Press the 'Install' softkey and confirm with the 'Yes' softkey.
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 'Station' > 'Topology' > 'Station' > 'Hardware tree More' > 'Options'
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'.
29
6 Preparing 'Station' for commissioning – without BDV installation
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-FXS7211 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
30
Auto-configuring the detector line
6
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 C-NET 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.
3. Select the 'Auto-configure line' command.
The C-NET 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
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 'Cerberus-Engineering-Tool'.
The advancement status is displayed in the 'Create site by uploading from
station(s)' window.
The 'Site properties' window is opened after loading.
31
6 Adapting configuration
5. Change the entries if required and click on 'OK'.

The 'New site confirmation' window opens.
6. Click on 'Yes'.
6.6 Adapting configuration

Adapt the configuration in the 'Site' in Cerberus-Engineering-Tool 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 A6V10210424.

See chapter 'Applicable documents'.
See also
6.7 Switch on detector line

Detector line.
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

Detector line.
3. Select the 'Detector line OFF' command.
The yellow 'ISOLATION' LED lights up.
The detector line is switched off.
32
Restarting the detector line
6
6.9 Restarting the detector line

Detector line.
3. Select the 'Restart line' command.
The C-NET detector line is restarted.
The following message is displayed following restart: 'Command executed'.
6.10 Switching off 'Zone'

1. Select 'Topology' > 'Detection tree' > 'Area' > 'Section' > 'Zone' in the main
menu.
3. Select the 'Off' command.
The 'Zone' is switched off.
6.11 Switching on 'Zone'

menu.
3. Select the 'On' command.
The 'Zone' is switched on.
6.12 Read in devices on detector line
NOTICE
Incorrect order for reading in a loop

Error when reading in a loop.
The C-NET 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).
Detector line.
33
6 Detaching the device
3. Select the 'Read in installed devices' command.

The C-NET devices are read in.
The following message is shown following successful reading in:
'Command executed'
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.
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.
5. Select the 'Jump to link' menu item.
The physical channel is displayed.
6. Press the 'Upper level' softkey.
'Device' is displayed.
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 C-NET device for good, the corresponding elements,
e.g. the 'Zone' must be removed from the logical structure trees in Cerberus-
Engineering-Tool. You can search for elements using the 'Find' function.
You will find more information in document A6V10210424. See chapter 'Applicable
documents'.
See also
34
Switching on test mode
6
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'
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'
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 'Zones'
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'
4. Select a command from the following table.
The element is switched to normal operation.
The yellow 'DETECTOR TEST' LED goes out.
35
6 Rectify localization errors
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.
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.
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 C-NET
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
See also
36
Completion work
6
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.
37
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 Cerberus-Engineering-

Tool are commissioned.
Prerequisites
The detector lines and C-NET 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 [ 39]
2. Prepare the 'Station' for commissioning. Link [ 29]
3. Perform auto-configuration:
- 'Auto-configure 'Station' Link [ 30]
OR
- Auto-configure detector lines individually Link [ 31]
4. Adapt the auto-configuration in the Person Machine Interface, e.g.:
- Changing customer texts. Link [ 39]
- Setting parameter sets of the C-NET devices. Link [ 40]
5. Test the function of the 'Site' and remedy the problems, if any. Link [ 36]
6. Perform the completion tasks. Link [ 37]
38
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
You will find the pin assignments in document A6V10210368. See chapter
See also
7.2 Entering customer texts using the Person Machine

Interface
menu.
2. Select the element you want to label with a customer text.
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.
39
7 Setting detector parameter sets
7.3 Setting detector parameter sets

1. Select 'Topology' > 'Detection tree' > 'Area' > 'Section' > 'Zone' > 'Detect.' in the
main menu.
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'
40
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 Cerberus-Engineering-Tool.
The procedure in this chapter applies exclusively to standalone 'Stations' and is

only valid forC-NET detector lines.
Prerequisites
the 'Station', but not yet connected.
Cerberus-Engineering-Tool is installed on the PC.
The current firmware and BDV are available on the PC.
pages.
Commissioning
1. Prepare the 'Station' for commissioning. Link [ 29]
2. Perform auto-configuration:
- Auto-configure 'Station'. Link [ 30]
OR
- Auto-configure detector lines individually. Link [ 31]
3. Connect the PC to the 'Station'. Link [ 22]
4. Load the automatically created configuration to the PC. Link [ 31]
5. Adapt the configuration in Cerberus-Engineering-Tool. Link [ 32]
6. Load the configuration from the PC to the 'Station'. Link [ 25]
7. Test the function of the 'Site'. Link [ 36]
8. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [ 25]
9. Disconnect the PC from the 'Station'. Link [ 22]
41
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 C-NET detector lines.
In this commissioning variant, in,Cerberus-Engineering-Tool, first manually

configure a 'Site' up to 'Line' level. Then read in the C-NET devices and adapt the
configuration manually in Cerberus-Engineering-Tool.
Prerequisites
pages.
Commissioning
1. In Cerberus-Engineering-Tool create a 'Site' and configure it manually to the
'Zone' level.
2. Prepare the 'Station' for commissioning - without BDV installation. Link [ 30]
5. Read-in the C-NET devices. Link [ 33]
6. Load the configuration from the 'Station' to the PC. Link [ 26]
42
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
pages.
Commissioning
1. Create a 'Site' and the 'Stations' in Cerberus-Engineering-Tool and pre-
configure, if required.
2. Prepare each 'Station' individually for commissioning - without BDV installation.
Link [ 30]
3. Connect the PC to each 'Station' individually. Link [ 22]
4. Initialize each 'Station' individually. Link [ 23]
5. Read-in the C-NET devices for all 'Stations'. Link [ 33]
43
Adding a 'Station' to an existing 'Site'
11
11 Adding a 'Station' to an existing 'Site'

Prerequisites
pages.
Commissioning
1. In Cerberus-Engineering-Tool, create the 'Station' to be integrated and
configure it, if required.
2. Prepare the 'Station' for commissioning - without BDV installation. Link [ 30]
4. Initialize the 'Station'. Link [ 23]
44
Merging two 'Sites'
Setting detector parameter sets
12
12 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 (C-WEB/LAN).
– Large SAFEDLINK sub-nets are in the original state and not yet divided.
– Ethernet sub-net are in the original state.
pages.
Commissioning
1. Add Site' B to 'Site' A. Link [ 46]
2. Initialize all 'Stations' that have a new address. Link [ 23]
3. Load the configuration of all 'Stations' in 'Site' A from the PC to the 'Station'.
Link [ 25]
4. Connect the 'Sites' physically to one another. Link [ 48]
5. Load the configuration of the merged 'Site' from the 'Station' to the PC. Link
26]
45
Merging two 'Sites'
12 Adding 'Site' B to 'Site' A
12.1 Adding 'Site' B to 'Site' A

'Site' A is opened in Cerberus-Engineering-Tool.
1. In the 'Edit' menu, select the 'Merge sites' menu item.
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.
Cerberus-Engineering-Tool checks whether there are address conflicts at
'Stations' levels and suggests a possible new address.
46
Merging two 'Sites'
Connecting 'Sites' physically to one another
12
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.
47
Merging two 'Sites'
12 Connecting 'Sites' physically to one another
12.2 Connecting 'Sites' physically to one another

Connect the two 'Sites' physically to one another.
documents'.
See also
48
Changing and expanding the FDnet/C-NET detector line
Extending the detector line to include additional devices
13
13 Changing and expanding the FDnet/C-NET

detector line
13.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 C-NET 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.
pages.
1. Switch the C-NET detector line off. Link [ 32]

2. Fit and wire the new devices. Link [ 49]
6. Configure the new devices. Link [ 50]
13.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.
49
13 Replacing stationary devices of the same type
13.1.2 Configure a new device

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

devices.
pages.

2. Replace the C-NET device with a device of the same type. Several devices can
be replaced.
3. Rectify localization errors. Link [ 36]
You will find information about installing and uninstalling in the documentation for
the corresponding 'C-NET' device.
Refer to document A6V10227639 for information on how to replace radio
detectors. See chapter 'Applicable documents'.
See also
50
Permanently removing stationary devices
13
13.3 Permanently removing stationary devices

pages.

2. Remove the C-NET devices. Link [ 34]
3. Switch the C-NET detector line on. Link [ 32]
The control panel reports a 'Fault' per missing device.
4. Delete the C-NET devices on the Person Machine Interface. Link [ 34]
7. Remove the logical elements in Cerberus-Engineering-Tool. Link [ 34]
13.4 Removing or replacing non-stationary devices

The product range includes bases with or without a loop contact.
13.4.1 Base with loop contact

If an C-NET device is removed, the loop contact prevents the C-NET detector line
from being interrupted and thereby prevents a fault message.
The work described in this chapter may be performed when the C-NET detector
line is switched on.
13.4.1.1 Temporarily removing an individual non-stationary device

It may be possible that an C-NET device must be temporarily removed from the
base. Afterwards the same C-NET device must be re-inserted at exactly the same
place in the C-NET.
Document the serial number and the position in the C-NET for each device in
order to enable the device to be placed in the same position following its removal.
1. Remove the C-NET device.

The control panel detects that the C-NET device is missing and reports a
'Fault'.
2. Perform the necessary activities.
3. Re-insert the C-NET device in the C-NET in the same, previous position.
51
13 Removing or replacing non-stationary devices
4. Acknowledge the 'Fault'.

If this 'Fault' is no longer displayed, the control panel updates the settings of
the re-inserted C-NET device.
If this 'Fault' is still displayed, and/or the detector line is not in normal operation,
the 'detector line' has to be restarted.
See also
Restarting the detector line [ 33]
13.4.1.2 Replacing non-stationary devices of the same type
pages.
1. Switch the test mode on. Link [ 35]

2. Replace the C-NET device. Link [ 52]
3. Switch normal operation on. Link [ 35]
13.4.1.2.1 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.
52
Removing or replacing non-stationary devices
13
13.4.1.3 Replacing non-stationary devices of different types
pages.
1. Remove the C-NET device from its base.

The 'Station' detects that the device is missing and reports a 'Fault'.
2. Delete the C-NET device individually on the Person Machine Interface on the
control panel. Link [ 34]
3. Insert the new C-NET device in the base.
7. Replace the C-NET device in the 'Zone'. Link [ 53]
13.4.1.3.1 Replacing a device in the 'Zone'

1. Select the 'Zone' in which you have replaced a device in Cerberus-
Engineering-Tool. The 'Find' or 'Find and replace' functions can be used to do
this.
2. Replace the C-NET device.
documents'.
13.4.2 Base without loop contact

If a C-NET device is removed, the detector line is interrupted from this point. If the
device is on a stub or sub-stub, communication between the control panel and
downstream devices is interrupted. These devices are shown as missing on the
control panel.
The work described in this chapter may only be performed when the C-NET
detector line is switched off.
53
13.4.2.1 Temporarily removing an individual non-stationary device

Instances may arise when a C-NET device has to be temporarily removed from the
base. Afterwards the same device must be re-inserted at exactly the same place in
the C-NET.
Mark the allocation of the devices to the respective base to avoid additional work
steps.
pages.

3. Perform the tasks.
4. Re-insert the C-NET device in the corresponding position.
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'
See also
Non-stationary devices of the same type have been
swapped over [ 111]
13.4.2.2 Replacing non-stationary devices of the same type
pages.

2. Replace the C-NET device with a device of the same type. Several devices can
be replaced.
54
Removing or replacing non-stationary devices
13
13.4.2.3 Replacing a non-stationary device of a different type
pages.

The 'Station' detects that the device is missing and reports a 'Fault'.
3. Delete the C-NET device individually on the Person Machine Interface on the
4. Insert the new C-NET device in the base.
8. Replace the C-NET device in the 'Zone'. Link [ 55]
13.4.2.3.1 Replacing a device in the 'Zone'

1. Select the 'Zone' in which you have replaced a device in Cerberus-
Engineering-Tool. The 'Find' or 'Find and replace' functions can be used to do
this.
2. Replace the C-NET device.
documents'.
See also
13.4.3 Temporarily removing multiple non-stationary devices

The procedure in this chapter applies both for the base with loop contact and the
base without loop contact.
For the purpose of painting work, it may be necessary to temporarily remove the C-
NET devices in a room. Each C-NET device must then be re-inserted in its original
base. The C-NET devices may not be exchanged.
Mark the allocation of the devices to the respective base to avoid additional work
steps.
pages.
55
1. Switch the 'Zone' off. Link [ 33]

2. Remove the C-NET devices from their bases.
3. Perform the tasks.
4. Re-insert the C-NET devices to the respective position.
5. Switch the 'Zone' on. Link [ 33]
For all the re-inserted C-NET devices, a localization fault is displayed.
6. Restart the C-NET detector line. Link [ 33]
If detectors have been swapped over or are missing, the following messages are
shown on the display of the Person Machine Interface:
13.4.4 Permanently removing non-stationary devices

The procedure in this chapter applies both for the base with loop contact and the
base without loop contact.
pages.

2. Remove the C-NET devices and their bases. Link [ 34]
4. Delete the C-NET devices individually via the Person Machine Interface on the
7. Remove the logical elements in Cerberus-Engineering-Tool. Link [ 34]
56
Replacing 'Manual call point' of the same type
13
13.5 Replacing 'Manual call point' of the same type
NOTICE

devices.
pages.
1. Switch on the replace mode. Link [ 57]

2. Replace the 'Manual call point' with a 'Manual call point' of the same type.
3. Switch off the replace mode. Link [ 58]
4. Test the 'Manual call point'. Link [ 58]
You will find more information about installing and uninstalling in the
documentation for the corresponding 'Manual call point'.
13.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 detector line is de-energized.
57
13 Convert two stubs into a loop
13.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 'DETECTOR TEST' LED lights up.
The 'Manual call point' is in test mode.
13.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.
13.6 Convert two stubs into a loop

pages.
The two stubs are assigned to the same line pair, e.g. 'Line' 11 and 'Line' 12.
1. Switch both the C-NET detector lines off. Link [ 32]
2. Wire both stubs to a loop. You will find more information about this in document
3. Read-in the C-NET devices. Link [ 33] 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).
See also
58
Connecting a sub-stub to a loop
13
13.7 Connecting a sub-stub to a loop

pages.

2. Physically connect the sub-stub to the loop. You will find more information
about this in document A6V10210390. See chapter 'Applicable documents'.
See also
59
Commissioning Ethernet switch (MM) FN2008-A1
14 Connecting a sub-stub to a loop
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 Ethernet switch (MM) FN2008-A1. See chapter
Commissioning
1. Install the 'Primary Setup Tool' software. Link [ 61]
2. Assign the IP address. Link [ 61]
3. Configure the FN2008-A1 using the Internet browser. Link [ 62]
4. In Cerberus-Engineering-Tool, 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 See chapter
The FN2008-A1 has no IP address in the factory setting. You must manually
assign the IP address.
See also
60
Install Primary Setup Tool
14
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.
61
14 Configure FN2008-A1 using Internet browser
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.
62
Commissioning safety module (firewall) FN2009-A1
Configure FN2008-A1 using Internet browser
15
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 [ 64]
2. Select the type and enter the MAC address. Link [ 64]
3. Enter the network settings. Link [ 65]
- Load configuration.
4. Create IP service definitions. Link [ 68]
5. Create firewall rules. Link [ 69]
- 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 A6V10210390. 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.
63
15 Installing Security Configuration Tool
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.
64
Entering network settings
15
2. Select 'S612V2'.
Type is selected.
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:
65
15 Entering network settings
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.
66
Entering network settings
15
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
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.
67
15 Creating IP service definitions
15.4 Creating IP service definitions
NOTICE
Different BACnet port settings in FN2009-A1 and Cerberus-Engineering-Tool

No communication possible
Configure the same BACnet port in FN2009-A1 and Cerberus-Engineering-
Tool.
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.
68
Creating firewall rules
15

'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:
69
15 Creating firewall rules
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.
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.
70
Commissioning the fire brigade periphery module FCI2001-D1
16
16 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.
71
Commissioning I/O card (remote transmission) FCI2007-A1 and I/O card (horn/monitored) FCI2009-A1
17
17 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 A6V10210362 and A6V10210368.
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.
72
Testing detectors
Activate the detector
18
18 Testing detectors
The commissioning personnel perform the function test for the automatic fire
detectors and the 'Manual call points'.
pages.
The detector line has been commissioned.

1. Switch the test mode on. Link [ 35]
2. Initiate the detector. Link [ 73]
4. Test the logged test activations. Link [ 73]
18.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 A6V10212047.
See also
18.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.
- Cerberus-Engineering-Tool: 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.
73
Updating the firmware of the 'Station'
19 Preparation and security
19 Updating the firmware of the 'Station'
19.1 Preparation and security
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.
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 Cerberus-Engineering-Tool
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.
The following points must be observed before updating the firmware.

The firmware must be updated individually for each 'Station'. Exception:
'Station' networked via C-WEB/LAN. See the chapter 'Updating several
'Stations' simultaneously'.
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 Cerberus-
Engineering-Tool. You will find more information about the event memory
and the alarm counter in document Cerberus-Engineering-Tool. See
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
74
Updating the firmware of the main CPU and the additional CPUs – Overview
19
The procedure for updating the firmware depends on the 'Station' configuration.
A 'Station' can be configured as follows:
– StandaloneStation
– SAFEDLINKStation
– Router , EthernetStation
– 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 [ 80]'.
Communication with GAP via C-WEB/LAN
– A GAP with DHCP must be configured for a connection with the PC via C-
WEB/LAN. You will find more information in document C-WEB/LAN. See
Once the firmware has been updated, the 'Station' configuration must be
loaded to 'Cerberus-Engineering-Tool' in order to update the LRC data to the
current firmware status.
See also
Updating several 'Stations' simultaneously [ 76]
19.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.
19.2.1 Standalone station and SAFEDLINK station
pages.
Familiarize yourself with the information in 'Preparation and security [ 74]'.

1. Import the new firmware into Cerberus-Engineering-Tool.
- Select the 'File' > 'Import new FW package' menu item and open the file
you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [ 26]
3. Convert the configuration if necessary and rectify conversion faults. Link [ 79]
5. Update the firmware on the main CPU and the additional CPUs. Link [ 80]
7. Test the firmware version on the additional CPUs. Link [ 87]
- Update the firmware, if required, of the additional CPUs again, if there is a
higher firmware version available. Link [ 86]
75
19 Updating the firmware of the main CPU and the additional CPUs – Overview
19.2.2 Router station and Ethernet station
pages.

A GAP with DHCP must be configured for the connection with the PC via C-
WEB/LAN.
you want.
4. Connect the PC to the C-WEB/LAN via the Ethernet switch (MM) FN2008-A1.
- Remove the network connection to the 'Station'and connect the PC locally
to the 'Station'. Link [ 22]
7. Test the firmware version on the additional CPUs. Link [ 87]
10. Restore the network connection.
19.2.3 Updating several 'Stations' simultaneously

You can update the firmware of max. eight networked 'Stations' simultaneously.
The 'Stations' and the CPU cards must be connected to one another via C-
WEB/LAN.
Example: Several 'Stations' are connected to each other via one or several
'Ethernet switch (MM) FN2008-A1.'
pages.

WEB/LAN.
The 'Stations' are displayed together.
You can update not more than eight 'Stations' simultaneously.
you want.
76
Updating the firmware of the additional CPUs only – Overview
19
4. Connect the PC to the 'Ethernet switch (MM) FN2008-A1.'
- Set each 'Station' individually in update mode. You can set the 'Stations' in
update mode without any waiting time one directly after the other.
- Wait until the update of each 'Station' is completed.
6. Initialize each 'Station' individually. Link [ 23] To do so, you must connect the
PC to each 'Station' locally. Link [ 22]
7. Test the firmware version on the additional CPUs on each 'Station'. Link [ 87]
10. Restore the network connection, if required.
19.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.
pages.

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 [ 86]
77
19 Update only the BDV

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

WEB/LAN.
2. Connect the PC to the C-WEB/LAN via the Ethernet switch (MM) FN2008-A1.
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 [ 86]
7. Disconnect the PC from C-WEB/LAN.
19.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 A6V10210424. 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
pages.

1. Import the new BDV into Cerberus-Engineering-Tool.
- Select the 'File' > 'Import new BDV' menu item and open the file you want.
3. Convert the configuration and rectify conversion faults. Link [ 79]
78
Converting the configuration
19

6. Load the converted configuration from the PC to the 'Station'. Link [ 25]
pages.

1. Import the new BDV into Cerberus-Engineering-Tool.
- Select the 'File' > 'Import new BDV' menu item and open the file you want.
3. Convert the configuration and rectify conversion faults. Link [ 79]
4. Remove the network connection to the 'Station' and connect the PC. Link
22]
6. Load the converted configuration from the PC to the 'Station'. Link [ 25]
8. Restore the network connection.
19.5 Converting the configuration

In document A6V10260976, 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 Cerberus-Engineering-
Tool.
1. Select the 'Edit' > 'Convert site' menu item.
2. Select the BDV you want and click on 'Convert'.

3. Click on 'Yes'.
The 'Site' is converted.
79
19 Setting Windows firewall
19.6 Setting Windows firewall

The aim of the settings is to establish a functioning Ethernet connection between
the Cerberus-Engineering-Tool on the PC and FS720 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.
19.7 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 or FCM2027 is used in the 'Station.' The
procedures are described in the following chapters:
'PMI & mainboard FCM2004 [ 80]'
'PMI & mainboard FCM2027 [ 82]'
PMI & mainboard FCM2004 PMI & mainboard FCM2027
19.7.1 PMI & mainboard FCM2004

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.
80
Updating the firmware of the main CPU and the additional CPUs
19
5. Select the firmware version you want and click on 'Start'.

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.
81
19 Updating the firmware of the main CPU and the additional CPUs
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.
11. On the 'Station', set the 'S38-2' switch to 'OFF'.

The 'Station' is restarted many times. This procedure takes up to ten
minutes.
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'.
19.7.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.
'OK'.
3. NOTICE! Data loss. Save the configuration data before updating the firmware.
The 'FW update main and additional CPUs' window opens.
4. Select the desired firmware version.
82
19
5. The firmware update can be started in two ways:

- Start the firmware update at the 'Station'.
- Start the firmware update in Cerberus-Engineering-Tool.
Both options are described in the following sections.
Starting the firmware update at the 'Station'

1. Select 'Initiate update at station'.
2. 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.
83
19 Updating the firmware of the main CPU and the additional CPUs
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.
4. Select 'Run in background' in order to run the firmware update in the

background while continuing to work in Cerberus-Engineering-Tool.
Pop-up windows in the bottom right-hand corner of the software will notify
you when the firmware download and the firmware update are complete.
After the restart, the 'Station' display shows the available BDVs. It is not
necessary to install a BDV at this point.
Starting the firmware update in 'Cerberus-Engineering-Tool'

1. Select 'Initiate update from tool'.
2. Select the connection type.
The available 'Station' are displayed.
3. Select the 'Station' you want.

4. Select 'Start'.
84
19
5. Confirm the firmware update with 'Yes' or reject the firmware update with 'No'.
6. Select 'Run in background' in order to run the firmware update in the

background while continuing to work in Cerberus-Engineering-Tool.
The active firmware update is indicated by the symbol on the right-hand side
of the status bar.
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.
See also
Preparation and security [ 74]
85
19 Update the firmware of the additional CPUs
19.8 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.
'OK'.

- 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'.

86
Testing the firmware version of the additional CPUs
19
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.
11. Click on 'Close' in the 'FW update additional CPUs' window.
See also
Preparation and security [ 74]
19.9 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.
'OK'.
87
19 Creating diagnosis report

- 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 'Connection to GAP' enter the address of
'Station'. If you want to create a connection to GAP 'Connection to GAP'
itself, enter '0'.
4. Click on 'OK'.
The following window is opened.
5. Test the firmware version on the additional CPUs.

6. Click on 'FW update additional CPUs' in the 'Cancel' window.
19.10 Creating diagnosis report

To update the firmware versions for the creation of the diagnosis report, the
configuration data must be loaded in Cerberus-Engineering-Tool.
The configuration data for the 'Station' is loaded to Cerberus-Engineering-Tool.
1. Select 'Commissioning' > 'Diagnostics report' from the menu bar.
The 'Reports' window opens.
2. Select 'Report type' in the 'Diagnostics report' 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
See also
88
Updating the firmware of the peripheral devices
Updating the firmware of the MCL-USB adapter FDUZ22x
20
20 Updating the firmware of the peripheral

devices
You need the following tools to update the firmware of the periphery devices:
Cerberus-Engineering-Tool
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'.
20.1 Updating the firmware of the MCL-USB adapter

FDUZ22x
The firmware of the MCL-USB adapter FDUZ221 or the MCL-USB adapter (radio)
FDUZ227 must be updated if a new firmware version is issued.
Preparation
The driver for the MCL-USB adapter is installed on the PC.
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/FDUZ227
Connection of the PC to the MCL-USB adapter
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.
89
20 Updating the firmware of the floor repeater terminal FT2010
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.
20.2 Updating the firmware of the floor repeater terminal

FT2010
WARNING

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 C-
NET detector line.
The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
2. In the selection window, open an F-Site-XX_x_x_...zip file matching the
'FXS7211'.
3. Open the device and connect the PC via the MCL-USB adapter to the device.
90
Updating the firmware of the floor repeater terminal FT2010
20
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

1. Select 'Update' > 'FW update standard peripheral device'.
The 'FW update standard peripheral device' window opens.
Cerberus-Engineering-Tool establishes the connection to the device and
sets the device to update mode.
2. Select the firmware package that matches the 'Site'.
- 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.
4. Remove the MCL-USB adapter and lock the device.
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 C-NET plug (X1) from the printed circuit board.
2. Wait at least ten seconds and re-insert the C-NET 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.
91
20 Updating the firmware of the floor repeater display FT2011
FT2010 Front view FT2010 printed circuit board
20.3 Updating the firmware of the floor repeater display

FT2011
WARNING

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 C-
NET detector line.
PC.
2. Open an F-Site-XX_x_x...zip file that matches the 'FXS7211' 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
92
Updating the firmware of the floor repeater display FT2011
20

FDUZ227
FT2011 Floor repeater display

If the hardware version is not compatible, click on 'Cancel' and check the
updating.
4. Remove the MCL-USB adapter and lock the device.

in step 1:
1. Keep the 'More alarms' (1) and 'Silence buzzer' (2) buttons pressed at the
same time and disconnect the C-NET plug (X1) from the printed circuit board.
2. Wait at least ten seconds and re-insert the C-NET plug (X1).
3. Click on the 'FW update standard peripheral device' button in the 'OK' window
1
FT2011 Front view FT2011 printed circuit board
93
20 Updating firmware of mimic display driver FT2001-A1
20.4 Updating firmware of mimic display driver

FT2001-A1
WARNING

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 C-
NET detector line.
PC.
2. In the selection window, open an F-Site-XX_x_x_...zip file matching the
'FXS7211'.
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

FDUZ227
FT2010 Mimic display driver

94
Updating the firmware of the radio gateway FDCW241
20
updating.
4. Remove the MCL-USB adapter.

in step 1:
1. Set the DIP switch S200-1 to 'ON'.
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.
21
S200 ON
1 1
1
1 1
FT2001-A1 Printed circuit board view
95
20 Updating the firmware of the radio gateway FDCW241
20.5 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
See also
20.6 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
PC.
The line tester is fed either internally with batteries or via a mains adapter.
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.
96
Updating firmware on the line tester FDUL221
20

1. Select 'Update' > 'FW update FDUL221 line test device'.
The 'FW update FDUL221 line test device' window opens.
If the hardware version is not compatible, click on 'Cancel' and check the
The 'FW update FDUL221 line test device' window is closed after updating.
3. Remove the MCL-USB adapter.

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.
3. Release the ' ' and ' ' buttons.
4. Click on the 'FW update FDUL221 line test device' button in the 'OK' window
97
20 Updating firmware on the line tester with serial interface FDUL221
20.7 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.
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

1. Select 'Update' > 'FW update serial FDUL221 line test device'.
The 'FW update serial FDUL221 line test device' window opens.
The 'FW update serial FDUL221 line test device' window is closed after
updating.
98
Updating firmware on the line tester with serial interface FDUL221
20
3. Disconnect the connection with the PC.


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.
Click on the 'FW update serial FDUL221 line test device' button in the 'OK' window
99
Commissioning external printer
21
21 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 FS720 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==
100
21
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==
101
21
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
102
Maintenance
General
22
22 Maintenance
22.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 system data have 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.
22.2 Spare parts

You will find details for ordering spare parts for 'Stations' in document
A6V10227652.
You will find details for ordering Detectors and accessories in document
A6V10225323.
See also
22.3 Testing and measuring instruments

The following table shows an overview of the test devices and measuring
instruments used.
Test Required auxiliaries Comment
Voltage, current and resistance Universal measuring instrument Measuring ranges:

measuring Voltage: AC/DC 1…500 V
Current: DC 100 mA…5 A
Resistance: 10 …10 M
Measurement error: 2 %
Internal resistance: 20 k
103
Maintenance
22 Preparatory work
Test Required auxiliaries Comment
Testing batteries Battery tester Load resistance: 5

Poll diagnosis data Maintenance PC with Cerberus- For requirements, see document
Engineering-Tool A6V10210424. See chapter 'Applicable
documents'.
Insert and remove FD720 point Detector exchanger DX791 Compatible with all FD720 point detectors
detectors Adapter for detector exchanger Some detectors also require the adapter for
FDUD491 detector exchanger FDUD491.
Test FD720 point detectors Test gas REF 8-S (recommended),

REF 8, hot air fan
Test manual call points, line devices
and alarm devices
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 C-NET detector line Line tester FDUL221
22.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 center)
'Fire controls' and alarm equipment
Extinguishing stations
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)
22.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.
104
Maintenance
Testing the 'Station'
22
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.
22.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.
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.
105
Maintenance
22 Check the power supply
Clean the operating unit

Clean the display and the front plate with a wet cloth. Do not use any caustic
solvents!
22.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.
106
Maintenance
Testing the printer
22
22.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 A6V10211076. See
See also
22.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
See also
22.10 Intervals for testing the system function

'Self test' of 'Detectors'
The 'Self test' is an automatic performance check for FD720 '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.
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
C-NET 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.
107
Maintenance
22 Completion work
Function Activity Interval

(years)
1 2 5
'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 time X
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
Intervals for the function test
22.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.
108
Repair
Disconnecting 'Station' from the power supply
23
23 Repair
23.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
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.
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'.
23.2 Spare parts

You will find details for ordering spare parts for 'Stations' in document
A6V10227652.
You will find details for ordering Detectors and accessories in document
A6V10225323.
See also
109
Repair
23 Fault messages on the Person Machine Interface
23.3 Fault messages on the Person Machine Interface
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.
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 FCM72xx 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 / Transmission equipment has a Check remote transmission
Off 'Fault'
10 Alarm device Fault / 'Fault' affecting acoustic control Check the 'Line' for open circuit/short-circuit
Off lines or end-of-line element (EOL) is missing or
defective
12 Control function Fault / 'Fault' affecting fire control lines Check the 'Line' for open line/short-circuit
Off Check the function of the external control
devices
Check the function, any existing feedback
switch
110
Repair
Fault indicators on components
23
23.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 A6V10210368. See
See also
23.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 Station.
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 'Cerberus-
Engineering-Tool' > 'Commissioning' command in Disconnect. If this is done, a
connection cannot be immediately re-established on the next 'Stations'.
23.6 Non-stationary devices of the same type have been

swapped over
When C-NET 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 C-NET device that has been swapped over:
'Zone', 'Serial no. ("ID-Nr.")', 'Device missing'
If the C-NET detector line was restarted, the following message is displayed for
each swapped C-NET device:
To enable the 'Station' to become fault-free again, at least the device types in the
corresponding bases must be correct. 'Faults' of C-NET 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.
111
Repair
23 Error message 'Topology is invalid'
Procedure
pages.

23.7 Error message 'Topology is invalid'

If the topology of a C-NET 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 C-NET devices, change over
the wiring or add a line separator FDCL221 between each stub.
3. Read in the C-NET detector line again.
See also
Read in devices on detector line [ 33]
112
Repair
Error message 'Too many devices'
23
23.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'.
23.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
With the 'S32' button

1. Press <MENU>.
The PIN input dialog is indicated.
2. Enter a valid PIN and confirm with <ok>.
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)'.
6. Select the 'Reset module' command.
113
Repair
23 Restoring factory setting on the 'Station'
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.
23.10 Restoring factory setting on the 'Station'

There are the following ways in which to restore the factory setting on the 'Station':
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.

1. Press <MENU>.
You are prompted to enter a PIN.
2. Enter a valid PIN and confirm with <ok>.
The main menu is displayed.
3. Select the 'Topology' > 'Hardware tree' > 'Station' menu items.
5. Select the 'Factory reset' command.
114
Repair
Restoring factory setting on the 'Station'
23

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.

3. Set the 'S38-1' switch to 'OFF' after the restart.
115
Repair
23 Restoring factory setting on the 'Station'
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.

116
Index
Index
A D
Acceptance test, 17 Date/time, 111
Alarm counter, 74 Deleting
Auto-configuration, 38 Device, 34
Definition of terms, 19 Detector
Detector line, 31 Test mode, 35
Station, 30 Testing, 73
Detector inspection, 107
B Detector line
Back-up, 27 Auto-configuration, 31
Install, 16
C
ON, 32
Commissioning, 18
Restart, 33
According to wiring sequence, 16
Switch off, 32
Auto-configuration, 38
Testing, 16
Networked station, 43
Detector self-test, 107
Overview, 18
Device
Standalone station with PC, with pre-
configuration, 42 Remove, 51
Standalone station with PC, without pre- Remove (base without loop contact), 54
configuration, 41 Replace (base without loop contact), 54
Standalone station without PC, 38 Replacing (different types), 55
With serial number, 16 Replacing (stationary), 50
Without PC, 38 Swapped, 111
Communication problems, 111 Temporarily remove, 55
Component Download, 23, 25
Indication of faults, 111 Download center
Configuration URL, 9
Conversion, 79
Load to station, 23, 25
E
Error message
Loading to PC, 26
'Topology is invalid', 112
Connecting a sub-stub to a loop
Ethernet switch (MM) FN2008 A1, 60
FDnet/C-NET detector line, 59
Event memory, 74
Connection to the station, 22
Expand
Connectivity, 22
Conversion, 79
Site, 44
Configuration, 79
External printer, 100
Convert stubs into loops
CPU
Updating the firmware, 80
CPU (other)
Customer text, 39
117
Index
H
F Hardware reset
Factory reset, 114
station, 113
Factory setting, 114
Fault indicators, 110 I
FCI2007-A1 I/O card (RT), 72 I/O card (horn/monitored) FCI2009-A1, 72
FCI2009-A1 I/O card (horn/monitored), 72 I/O card (RT) FCI2007-A1, 72
FDnet/C-NET detector line Indication of faults
Connecting a sub-stub to a loop, 59 Component, 111
Convert stubs into loops, 58 Initialize
Expand, 49 Station, 23, 23
Removing a device (non-stationary), 56 Install
Removing a device (stationary), 51 Detector line, 16
Replacing a device with one of a different type
(non-stationary), 53 L
Replacing a device with one of the same type License, 21
(non-stationary), 52 Line tester
Replacing manual call points, 57 Updating the firmware, 96
FDUL221 line tester Load
Updating the firmware, 96 From PC to station, 23, 25
FDUL221 serial line tester From station to PC, 26
Updating the firmware, 98 Load data to PC
FDUZ221 MCL-USB adapter Site, 26
Updating the firmware, 89 Load data to the station
Fire brigade periphery module FCI2001-D1, 71 Site, 25
Firewall Localization error, 36
Security module (firewall) FN2009-A1, 63
M
Windows firewall, 75, 80
Main CPU
Floor repeater display
Maintenance, 103
Floor repeater terminal
MCL-USB adapter
FN2008 A1
Measuring instrument, 103
Ethernet switch (MM) FN2008-A1, 60
Merge
FN2009-A1 safety, 63
Sites, 45
FT2001-A1 mimic display driver
Mimic display driver
FT2010 floor repeater terminal
Updating the firmware, 90 N
FT2011 floor repeater display Network cable
Updating the firmware, 92 Moving, 111
FUJITSU DL3750+, 100 Networked station, 43
Function test, 36, 107, 107 Normal operation, 35
Fuse, 27
118
Index
Replacing a device with one of a different type (non-

O stationary)
ON FDnet/C-NET detector line, 53
Detector line, 32 Replacing a device with one of the same type (non-
stationary)
P FDnet/C-NET detector line, 52
Password, 80, 82, 86, 87
Replacing manual call points
PC
Connect to station, 22
Restart
Disconnecting from station, 22
station, 113
PMI
Fault indicators, 110 S
Power supply Scalance X204 2, 60
Configuring, 39 Security module (firewall) FN2009-A1, 63
Testing, 106 Serial line tester
Pre-configuration Updating the firmware, 98
Definition of terms, 19 Series number, 16
Preparation Set parameter set
Station, 29 Use Person Machine Interface, 40
Preparation without BDV Site
Station, 30 Expand, 44
Primary Setup Tool, 61 Load data to PC, 26
Printer Load data to the station, 25
Testing, 107 Merge, 45
Test intervals, 107
R Spare parts, 103, 109
Radio gateway FDCW221, 96
Stand-alone station, 38, 41, 42
Station
Radio gateway FDCW241, 96
Auto-configure, 30
Disconnect power, 109
Read in
Factory setting, 114
Definition of terms, 19
Hardware reset, 113
Device, 33
Initialize, 23, 23
Remove
Load data, 23
Device, 51
Mount and install, 17
Device (base without loop contact), 54
Preparation, 29
Device (temporary), 55
Preparation without BDV, 30
Removing a device (non-stationary)
Resetting, 114
Restart, 113
Removing a device (stationary)
Switching off, 109
Swapped
Replace
Device, 111
Device (base without loop contact), 54
Switch off
Device (different types), 55
Detector line, 32
Device (stationary), 50
Switching off
Station, 109
119
Index
System data, 104
T
Test, 36, 107
Test intervals, 107, 107
Test mode, 35
Detector, 35
Exit, 35
Test unit, 103
Testing
Detector, 73, 73
Detector line, 16
Function, 107
Power supply, 106
Printer, 107
System data, 104
Time/date, 111
Topology is invalid, 112
U
Uninstalling
Device, 34
Update BDV, 78
Additional CPUs, 86
Main CPU and additional CPUs, 80
Periphery devices, 89
Station, 74
Upload, 26
W
Windows firewall, 75, 80
Z
Zone
ON, 33
Switch off, 33
120
Index
121
Issued by © 2008-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 A6V10210416_h_en_-- Manual FS720

Edition 2014-03-26 Register 6

FS720 Fire Detection System: Commissioning Maintenance Troubleshooting

Uploaded by

Copyright:

Available Formats

FS720 Fire Detection System: Commissioning Maintenance Troubleshooting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FS720 Fire Detection System: Commissioning Maintenance Troubleshooting

Uploaded by

Copyright:

Available Formats

FS720

Fire detection system

A6V10210416_h_en_-- Building Technologies

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

1 About this document ......................................................................................7

1 About this document

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

Target group Activity Qualification

Reference document and source language

Conventions for text marking

Requirement for a behavior instruction

1. Behavior instruction with at least two operation sequences

– 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

X] Reference to a page number

'Text' Quotation, reproduced identically

<Key> Identification of keys

Supplementary information and tips

1.1 Applicable documents

A6V10210355 FS720 Fire Detection System, System Description

1.2 Download center

1.3 Technical terms

1.4 History of changes

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

Version Edition date Brief description

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

Version Edition date Brief description

e 2012-05 Edition for IP4

2.1 Safety instructions

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

General danger Explosive atmosphere

Voltage/electric shock Laser light

Signal word Danger level

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

How risk of injury is presented

Nature and origin of the danger

How possible damage to property is presented

Nature and origin of the danger

2.2 Safety regulations for the method of operation

Fit an easily accessible disconnecting device in accordance with IEC 60950-1

Assembly, installation, commissioning and maintenance

Testing the product operability

Modifications to the system design and the products

Modules and spare parts

Disregard of the safety regulations

2.3 Standards and directives complied with

2.4 Release Notes

Limited or non-existent fire detection

Incorrect planning and/or configuration

3.1 Installing and checking the detector line

3.1.1 Installing devices with serial number

3.1.2 Installing devices according to the wiring sequence

3.1.3 Checking the detector line

Error when reading in the devices