fs720 PDF

FS720
Fire detection system

Commissioning
Maintenance
Troubleshooting
IP7
A6V10210416_j_en_-- Building Technologies

2018-08-29 Control Products and Systems
Imprint
Imprint
Technical specifications and availability subject to change without notice.
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.
Building Technologies Division
International Headquarters
Theilerstrasse 1a
CH-6300 Zug
Tel. +41 58 724-2424
www.siemens.com/buildingtechnologies
Edition: 2018-08-29
Document ID: A6V10210416_j_en_--
© Siemens Switzerland Ltd, 2008
2 | 178
Building Technologies A6V10210416_j_en_--
Fire Safety 2018-08-29
Table of contents
1 About this document ............................................................................. 9

1.1 Applicable documents ................................................................................11
1.2 Download center ........................................................................................11
1.3 Technical terms and abbreviations .............................................................12
1.4 Revision history .........................................................................................13
2 Safety ............................................................................................... 17
2.1 Safety instructions .....................................................................................17
2.2 Safety regulations for the method of operation ...........................................18
2.3 Standards and directives complied with......................................................20
2.4 Release Notes ...........................................................................................21
3 Mounting / Installation ......................................................................... 22
3.1 Installing and checking the detector line .....................................................22
3.1.1 Installing devices with serial number ...........................................22
3.1.2 Installing devices according to the wiring sequence .....................22
3.1.3 Checking the detector line ...........................................................23
3.2 Mount and install 'Station' ..........................................................................23
4 Connectivity and communication with 'Station'........................................ 24
4.1 Setting Windows firewall ............................................................................24
4.1.1 Windows XP ...............................................................................24
4.1.2 Windows 7 / Windows 8 / Windows 10 ........................................25
4.2 Network parameters ..................................................................................26
4.3 Connecting the PC to the station ................................................................27
4.4 Disconnecting the PC from the station .......................................................27
4.5 Loading data to the 'Station' .......................................................................28
4.6 Initializing 'Station' .....................................................................................28
4.7 Loading configuration from the PC to the station ........................................30
4.8 Loading configuration from the station to the PC ........................................32
4.9 Creating a backup of the 'Site' configuration ...............................................32
5 Commissioning overview ..................................................................... 34
5.1 Commissioning variants .............................................................................34
5.2 Definition of terms......................................................................................35
5.3 Standard gateway ......................................................................................36
5.4 Brief instructions on operating the 'Station' .................................................37
5.5 License ......................................................................................................37
3 | 178
6 A - Commissioning standalone 'Station' without PC .................................38
6.1 Configuring the power supply ..................................................................... 39
6.2 Entering customer texts using the Person Machine Interface...................... 39
6.3 Setting detector parameter sets ................................................................. 40
7 B1 - Commissioning standalone 'Station' with PC, without pre-configuration ..
.........................................................................................................41
8 B2 - Commissioning standalone 'Station' with PC, with pre-configuration ...42
9 C- Commissioning networked 'Stations' .................................................43
10 Adding a 'Station' to an existing 'Site'.....................................................44
11 Merging two 'Sites' ..............................................................................45
11.1 Adding 'Site' B to 'Site' A ............................................................................ 46
11.2 Connecting 'Sites' physically to one another............................................... 46
12 Changing and expanding the FDnet/C-NET detector line .........................47
12.1 Extending the detector line to include additional devices ............................ 47
12.1.1 Mount and wire new devices ....................................................... 47
12.1.2 Configure a new device............................................................... 48
12.2 Replacing stationary devices of the same type ........................................... 48
12.3 Permanently removing stationary devices .................................................. 49
12.4 Removing or replacing non-stationary devices ........................................... 49
12.4.1 Base with loop contact ................................................................ 49
12.4.2 Base without loop contact ........................................................... 51
12.4.3 Temporarily removing multiple non-stationary devices................. 54
12.4.4 Permanently removing non-stationary devices ............................ 54
12.5 Replacing 'Manual call point' of the same type ........................................... 55
12.5.1 Switching on the replace mode ................................................... 55
12.5.2 Switching off replace mode ......................................................... 56
12.5.3 Testing 'Manual call point' ........................................................... 56
12.6 Convert two stubs into a loop ..................................................................... 56
12.7 Connecting a sub-stub to a loop................................................................. 57
13 Calibrating an FDnet/C-NET detector line ..............................................58
13.1 Automatic line calibration ........................................................................... 59
13.2 Manual line calibration ............................................................................... 60
13.3 Calibration report ....................................................................................... 61
13.4 Troubleshooting ......................................................................................... 66
14 Commissioning a control panel with integrated extinguishing ....................70
14.1 Preparing the control panel with integrated extinguishing for commissioning .
.................................................................................................................. 71
14.2 Calibrating monitored outputs .................................................................... 72
14.3 CE marking ............................................................................................... 73
4 | 178
15 Detailed commissioning steps .............................................................. 74
15.1 Preparing 'Station' for commissioning.........................................................74
15.2 Preparing 'Station' for commissioning –without BDV installation .................75
15.3 Auto-configuring 'Station' ...........................................................................75
15.4 Auto-configuring the detector line ...............................................................76
15.5 Loading automatically created configuration to the PC ...............................77
15.6 Adapting configuration ...............................................................................77
15.7 Converting a standalone station to a networked station ..............................78
15.8 Switch off...................................................................................................79
15.8.1 Safety during switch-off ...............................................................79
15.8.2 Switching off the detector line......................................................79
15.8.3 Switch off zone ...........................................................................79
15.9 Switching on ..............................................................................................79
15.9.1 Switch on detector line ................................................................79
15.9.2 Switch on zone ...........................................................................80
15.10 Restarting the detector line ........................................................................80
15.11 Freezing outputs ........................................................................................81
15.12 Enabling frozen outputs .............................................................................81
15.13 Read in devices on detector line ................................................................82
15.14 Detaching the device .................................................................................82
15.15 Delete the device on Person Machine Interface..........................................83
15.16 Remove the elements ................................................................................83
15.17 Testing detectors .......................................................................................83
15.17.1 Activate the detector ...................................................................84
15.17.2 Testing logged test activations ....................................................84
15.18 Switching on test mode ..............................................................................84
15.19 Switch on normal operation........................................................................85
15.20 Rectify localization errors ...........................................................................86
15.21 Checking 'Site' function ..............................................................................86
15.22 Carrying out final commissioning work .......................................................86
16 Commissioning Ethernet switch (MM) FN2008-A1 .................................. 87
16.1 Install Primary Setup Tool ..........................................................................88
16.2 Assign IP address......................................................................................88
16.3 Configuring FN2008-A1 using Internet browser ..........................................89
17 Commissioning Ethernet switch (modular) FN2012-A1 ............................ 90
17.1 Standalone FN2012-A1 .............................................................................90
17.1.1 Specifying a pre-configured IP address .......................................90
17.2 FN2012-A1 integrated into station ..............................................................92
17.3 FN2012-A1 web interface ..........................................................................93
17.3.1 Commissioning a web interface ...................................................93
17.3.2 Changing the IP address .............................................................94
17.3.3 Configuring the redundancy role..................................................95
17.3.4 Activating/deactivating local ports................................................95
17.3.5 Activating fault monitoring for local ports .....................................96
17.3.6 Activating port mirroring ..............................................................96
17.4 Restarting and resetting the FN2012-A1 ....................................................97
5 | 178
18 Commissioning security module (firewall) FN2009-A1 .............................98
18.1 Installing Security Configuration Tool ......................................................... 99
18.2 Selecting type and entering MAC address................................................ 100
18.3 Entering network settings......................................................................... 101
18.4 Creating IP service definitions .................................................................. 104
18.5 Creating firewall rules .............................................................................. 106
19 Commissioning the fire brigade periphery module FCI2001-D1............... 108
20 Commissioning of I/O card (remote transmission) FCI2007-A1
and I/O card (horn/monitored) FCI2009-A1........................................... 109
21 Commissioning external printer ........................................................... 110
22 Updating the firmware........................................................................ 113
22.1 Preparation and security .......................................................................... 113
22.2 Station: Updating the FW of the main CPU and additional CPUs .............. 114
22.2.1 Standalone station and SAFEDLINK station .............................. 114
22.2.2 Router station and Ethernet station ........................................... 115
22.2.3 Updating several 'Stations' simultaneously ................................ 116
22.2.4 FW update for main CPU and additional CPUs ......................... 117
22.3 Station: Updating the FW of the additional CPUs only .............................. 125
22.3.3 FW update for additional CPUs ................................................. 126
22.4 Update only the BDV ............................................................................... 127
22.5 Converting the configuration .................................................................... 128
22.6 Testing the firmware version of the additional CPUs................................. 129
22.7 Creating diagnosis report ......................................................................... 130
22.8 Updating the FW of the peripheral devices ............................................... 130
22.8.1 MCL-USB adapter FDUZ22x..................................................... 131
22.8.2 Floor repeater terminal FT2010 ................................................. 132
22.8.3 Floor repeater display FT2011 .................................................. 134
22.8.4 Mimic display driver FT2001-A1 ................................................ 136
22.8.5 Radio gateway FDCW221 ......................................................... 138
22.8.6 Line tester FDUL221 ................................................................. 139
22.8.7 Line tester with serial interface FDUL221 .................................. 141
22.9 Updating the FW of Ethernet switch (modular) FN2012-A1 ...................... 142
22.9.1 Standalone FN2012-A1............................................................. 142
22.9.2 FN2012-A1 integrated into station ............................................. 145
6 | 178
23 Maintenance .................................................................................... 146
23.1 General ...................................................................................................146
23.2 Testing ....................................................................................................146
23.3 Testing and measuring instruments .........................................................147
23.4 Preparatory work .....................................................................................147
23.5 Test system data .....................................................................................148
23.6 Testing the 'Station' .................................................................................149
23.7 Check the power supply...........................................................................150
23.8 Testing the printer....................................................................................150
23.9 Calibrating lines .......................................................................................151
23.10 Checking 'Site' function ............................................................................151
23.11 Intervals for testing the system function....................................................152
23.12 Carrying out final maintenance work ........................................................153
24 Repair ............................................................................................. 154
24.1 Disconnect the station from the power supply ..........................................154
24.2 Spare parts ..............................................................................................155
24.3 Fault messages on the Person Machine Interface ....................................156
24.4 Fault indicators on components ...............................................................157
24.5 Communication problems in networked systems ......................................157
24.6 Correcting swapped devices ....................................................................158
24.7 Correcting an invalid topology ..................................................................159
24.8 Error message 'Too many devices' ..........................................................159
24.9 Restart 'Station' .......................................................................................160
24.10 Resetting a short-circuit ...........................................................................161
24.11 Restoring factory setting on the 'Station'...................................................163
24.12 Fiber-optic network module FN2006 / FN2007 troubleshooting steps .......165
Glossary ................................................................................................... 170
Index ...................................................................................................... 174
7 | 178
8 | 178
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 IP7.
Target groups
The information in this document is intended for the following target groups:
Target group Activity Qualification

System owner ● According to EN 50110-1, ● 'This person can be the owner,
'nominated person with the overall employer, proprietor or a delegated
responsibility to ensure the safe person.'
operation of the electrical ● 'Some of these duties can be
installation by setting rules and delegated to others as required. For
organisation or framework.' large or complex electrical
installations or networks, the duties
can be delegated for parts of the
installations or the network.'
Installation personnel ● Assembles and installs the product ● Has received specialist training in
components at the place of the area of building installation
installation. technology or electrical installations.
● Carries out a function check
following installation.
Commissioning personnel ● Configures the product at the place ● Has obtained suitable specialist
of installation according to training for the function and for the
customer-specific requirements. products.
● Checks the product operability and ● Has attended the training courses
releases the product for use by the for commissioning personnel.
operator.
● Searches for and corrects
malfunctions.
Maintenance personnel ● Carries out all maintenance work. ● Has obtained suitable specialist
● Checks that the products are in training for the function and for the
perfect working order. products.
● Searches for and corrects
malfunctions.
Source language and reference document

● The source/original 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.
9 | 178
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
> Relation sign and for identification between steps in a sequence,
e.g., 'Menu bar' > 'Help' > 'Help topics'
↑ Text Identification of a glossary entry
Supplementary information and tips
The 'i' symbol identifies supplementary information and tips for an easier way of
working.
10 | 178
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
Technical manual FDCW241 radio gateway, technical manual
Radio gateway
FDCW241
A6V10227652 FS720 Cerberus PRO Fire Detection System,
Components / Spare Parts / Repair Parts
A6V10229261 List of compatibility
A6V10260976 FS720 Fire Detection System, Site Conversion
Technical Manual Line FDUL221 Line Tester, Operation
tester FDUL221
008860 FT201x Floor Repeater Terminal / Floor Repeater
Display, Mounting
Installation MCL-USB FDUZ221 MCL-USB adapter, Mounting
Adapter FDUZ221
Installation MCL-USB FDUZ227 MCL-USB Adapter (Radio), Mounting
adapter (radio)
FDUZ227
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:
https://siemens.com/bt/download
l Enter the document ID in the search field.
You will also find information about search variants and links to mobile
applications (apps) for various systems on the home page.
11 | 178
About this document
1 Technical terms and abbreviations
1.3 Technical terms and abbreviations

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 details of further technical terms and abbreviations in the 'Glossary'
chapter.
See also
2 Applicable documents [➙ 11]
12 | 178
About this document
Revision history
1
1.4 Revision history

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 revision history:
Version Edition date Brief description

j 2018-08-29 Edition for IP7
New:
'Commissioning a control panel with integrated extinguishing [➙ 70]', 'Calibrating
an FDnet/C-NET detector line [➙ 58]', 'Calibrating lines [➙ 151]', 'Resetting a
short-circuit [➙ 161]'
Revised:
'Intervals for testing the system function [➙ 152]', 'Connecting the PC to the
station [➙ 27]', 'Commissioning a web interface [➙ 93]', 'FN2012-A1 integrated
into station [➙ 92]'
Chapter Check the power supply [➙ 150] amended: Step 5 in section 'Checking
the batteries' amended and steps 6 to 8 removed. Footnote added concerning
battery testers.
13 | 178
About this document
1 Revision history

i 2015-12-15 Edition for IP6
New:
Converting a standalone station to a networked station
Commissioning Ethernet switch (modular) FN2012-A1
Updating the FW of the FN2012-A1 Ethernet switch (modular)
Freezing outputs
Enabling frozen outputs
Switching off, Safety during switch-off, Switching on
Cyber security disclaimer
Network parameters
Fiber-optic network module FN2006 / FN2007 troubleshooting steps
Revised:
Chapter structure
Referenced documents updated
Disconnecting 'Station' from the power supply
Merging two 'Sites'
Loading data to the 'Station'
Loading configuration from the PC to the 'Station'
Loading configuration from the 'Station' to the PC
Creating a backup of the 'Site' configuration
Preparing 'Station' for commissioning –without BDV installation
Loading automatically created configuration to the PC
Completion work
Permanently removing stationary devices
Restart 'Station'
Restoring factory setting on the 'Station'
'Updating the firmware' chapter revised and restructured
Information regarding freezing outputs added to chapters 'Loading configuration
from the PC to the 'Station'' and 'Restarting the detector line'
Initializing 'Station'
Switching off the detector line, Switching off a zone
h 2014-01-13 FDUZ227 added to various chapters: May be used instead of FDUZ221
14 | 178
About this document
Revision history
1

g 2013-11-14 Edition for IP5
Change to date format according to ISO 8601
New:
Standard gateway pre-configured for standalone 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 standalone 'Station' with PC, without pre-
configuration' and 'B2 - Commissioning standalone 'Station' with PC, with pre-
configuration': Only applicable to C-NET detector lines
'Definition of terms' chapter revised
f 01.2013 Chapter 'Setting Windows firewall' updated for Windows 7
e 05.2012 Edition for IP4
New:
Updating the firmware of the main CPU and additional CPUs in a single step
Addition to chapter 'Setting Windows firewall', for Windows 7
Updating several networked 'Stations' simultaneously
Update the firmware of the additional CPUs via GAP
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
Revised:
Creating diagnosis report
Restart the station
Checking 'Site' function
Restoring factory settings
Checking the detector line
d 07.2010 Edition for MP3.0 XS:
Revision history 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 08.2009 Modifications for MP1XS
15 | 178
About this document
1 Revision history

b 05.2009 Modifications for MP1XS
a 11.2008 First edition
16 | 178
Safety
Safety instructions
2
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 a possibly harmful situation or possible damage to property

that may result from non-observance.
'NOTICE' does not relate to possible bodily injury.
17 | 178
Safety
2 Safety regulations for the method of operation
How risk of injury is presented

Information about the risk of injury is shown as follows:
WARNING
Nature and origin of the danger
Consequences if the danger occurs
● Measures / prohibitions for danger avoidance
How possible damage to property is presented

Information about possible damage to property is shown as follows:
NOTICE
Nature and origin of the danger
Consequences if the danger occurs
● Measures / prohibitions for danger avoidance
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, mounting, 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 voltage using a
'DANGER External voltage' sign.
● Route mains connections to products separately and fuse them with their own,
clearly marked fuse.
● Fit an easily accessible disconnecting device in accordance with IEC 60950-1
outside the installation.
● Produce earthing as stated in local safety regulations.
18 | 178
Safety
Safety regulations for the method of operation
2
CAUTION
Noncompliance with the following safety regulations
Risk of injury to persons and damage to property
● Compliance with the following regulations is required.
● Specialist electrical engineering knowledge is required for installation.

● Only an expert is permitted to carry out installation work.
Incorrect installation can take safety devices out of operation unbeknown to a
layperson.
Mounting, 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.
19 | 178
Safety
2 Standards and directives complied with
Modules and spare parts

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

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

A list of the standards and directives complied with is available from your Siemens
contact.
20 | 178
Safety
Release Notes
2
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.
21 | 178
Mounting / Installation
3 Installing and checking the detector line
3 Mounting / Installation
3.1 Installing and checking the detector line
You will find details on the technical term ↑ 'C-NET' in the chapter 'Glossary'.
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. Mount 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. Mount 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.
22 | 178
Mounting / Installation
Mount and install 'Station'
3
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.
Acceptance test
w 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 about 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:
l 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.
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 cables.
3. Insert the batteries but do not yet connect them.
You will find information on mounting and installing 'Stations' and components in
document A6V10210390. See chapter 'Applicable documents'.
See also
23 | 178
Connectivity and communication with 'Station'
4 Setting Windows firewall
4 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
4.1 Setting Windows firewall

● The Windows firewall may prevent the PC connecting to the 'Station'.
● A functioning Ethernet connection between the Cerberus-Engineering-Tool on
the PC and the FS720 control panels is required to update the firmware, for
example.
Setting Windows firewall

● Create a firewall rule for Windows. To do this, proceed as follows:
You must have administrator rights to make the following settings.
4.1.1 Windows XP
w You have administrator rights on your PC
1. Open the Windows start menu.
2. Select 'Settings' > 'Control panel' > 'Administrative Tools' > 'Services'.
3. Right-click on 'Windows Firewall/Internet Connection Sharing (ICS)' in the new
window.
4. Select 'All Tasks' > 'Exit' in the context menu.
5. Once the work is complete, reactivate the firewall. To do this, proceed as
described above but select 'All Tasks' > 'Start' in the context menu.
NOTICE
Security vulnerability in operating system due to deactivated firewall
Unauthorized access to your PC
● Activate the firewall after the firmware update.
24 | 178
Setting Windows firewall
4
4.1.2 Windows 7 / Windows 8 / Windows 10
There are different ways of setting up firewall rules in Windows 7/8/10. The
following settings apply for Siemens PCs which use group guidelines controlled
by the domain.
NOTICE
The following settings must be made under Local Security Policy.
● Open Local Security Policy to configure Windows Firewall with Advanced
Security.
w You have administrator rights on your PC.

w The PC is connected to the Siemens intranet.
1. Open the Control Panel.
– E.g., via the Windows Start menu in Windows 7.
– E.g., in Windows 10: Right-click on the Windows symbol at the bottom left
and select Control Panel in the context menu.
2. NOTICE! The following settings must be made under Local Security Policy.
Select 'Control Panel' > 'All Control Panel Items' > 'Administrative Tools' >
'Local Security Policy' > 'Windows Firewall with Advanced Security'.
3. Expand the subtree of the menu.
4. Right-click 'Inbound Rules' > 'New Rules'
a This opens the 'New Inbound Rule Wizard'.
5. Select 'Rule Type' and activate 'Program'.
6. Click 'Next >' to confirm and enter the program path to 'F-FXS7212.exe'.
– Example: C:\Program Files (x86)\Siemens\F-FX7230\XS_en_1-V5.0
– NOTICE! Remember to enter/add the new path if the version changes.
7. Click 'Next >' to confirm and then confirm the default setting 'Allow the
connection' in the next step ('Action').
8. In the next step 'Profile', remove the check mark from the 'Domain' checkbox.
a The 'Private' and 'Public' checkboxes are checked.
9. Click 'Next >' to confirm and enter an appropriate name in the next step
('Name'), such as 'FS720 application'.
10. Click 'Finish' to complete the process.
a A 'New Rule' has now been set and appears in the 'Inbound Rules' list.
It is necessary to make additional settings for the new rule:
1. Right-click the new rule and select 'Properties'.
2. Select the 'General' tab in the 'Rule Name Properties' window.
3. Set the following values:
– 'General': 'Activated'
– 'Action': 'Allow connection'
4. Select the 'Protocol and Ports' tab.
25 | 178
4 Network parameters
5. Set the following values:

– 'Protocol type': 'UDP'
– 'Local port': 'Specific Ports', and enter the value range '50067-50070' in the
box.
– 'Remote port': 'All Ports'
6. Confirm with 'OK'.
a The new firewall rule is now configured.
NOTICE
Security vulnerability in operating system due to open ports
Unauthorized access to your PC
● Deactivate the firewall rule configured above after the firmware update.
4.2 Network parameters

Ports in FS720
Use Port number Transport Application Comment
protocol protocol
Communication
Station-to-station 50501 UDP C-WEB
communication
Communication between 51000 UDP C-WEB
Engineering Tool and
station
Communication between 47808-47823 UDP BACnet ● Dependent on configuration
management station and ● Between BAC0 and BACF by
FS720 station default
Monitoring
Station to station 50502 UDP C-WEB
Remote access via cRSP 51001-51250 UDP C-WEB ● Dependent on configuration
Between Engineering Tool ● Rule for ports: portHost =
and station 51000 + hostID
Firmware update
Engineering tool 50067 UDP FW update
Panel 50068 UDP FW update
26 | 178
Connecting the PC to the station
4
4.3 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
Figure 1: Rear panel of operating unit and PC
LAN Ethernet connection

1 Required cable type: CAT 5, CAT 6, or CAT 7
4.4 Disconnecting the 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'.
27 | 178
4 Loading data to the 'Station'
4.5 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'.
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.
2The configuration of selected 'Stations' or all 'Stations' in the ↑ 'Site' can be
overwritten as an option.
See also
2 Loading configuration from the PC to the station [➙ 30]
2 Initializing 'Station' [➙ 28]
4.6 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.
28 | 178
Initializing 'Station'
4
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.
NOTICE
Faulty initialization for networked station
During initialization, the station must not be connected to the network or any other
station.
w The PC is connected locally to the 'Station'.

1. Highlight the 'Station' you want to initialize.
2. Select the 'Commissioning' > 'Initialize station' menu item.
a The following window is opened:
3. Click on 'Start'.
a The 'Set the station to access level 3' window opens.
4. Press <MENU> on the 'Station' and enter a valid PIN.
5. Click on 'OK' in the 'Set access level' window.
a The 'Station' is initialized.
a The 'Station' is restarted.
a 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
2 Loading data to the 'Station' [➙ 28]
29 | 178
4 Loading configuration from the PC to the station
4.7 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.
1Examples 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.
30 | 178
Loading configuration from the PC to the station
4
WARNING
Activation of fire or smoke dampers
If fire or smoke dampers are connected to the FS720 via an input/output module,
they may be activated when the station is switched off or when the station or
detector line is restarted.
● If necessary, block the outputs temporarily [➙ 81] before switching off the
station or restarting the station/detector line.
w The ↑ 'Site' is opened in Cerberus-Engineering-Tool.

w The PC is connected to the 'Station'.
w Networked 'Stations' are initialized.
w 'Station' and Cerberus-Engineering-Tool have the same 'Site' ID.
w 'Station' and Cerberus-Engineering-Tool are part of the same sales channel.
1. Select 'Commissioning' > 'Download site' in Cerberus-Engineering-Tool.
a The 'Download site' and 'Connect' windows open in Cerberus-Engineering-

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

a The 'Stations' are listed in the 'Download site' window.
3. Select the 'Stations' whose configuration you would like to load from 'Cerberus-
Engineering-Tool' to the 'Stations' and click on 'Start'.
a The 'Set access level' window may open in Cerberus-Engineering-Tool with
the 'Set the station to access level 3' prompt. Press <MENU> on the
'Station', enter the PIN and press <ok>.
4. Click on 'OK' in the 'Set access level' window in Cerberus-Engineering-Tool.
a The 'Action confirmation' window opens in Cerberus-Engineering-Tool.
5. Click on 'Yes'.
a The configuration is loaded to the 'Station'.
a The progress is displayed in the 'Download site' window in Cerberus-
Engineering-Tool.
a The 'Station' restarts.
a After a few minutes, the 'Buzzer' sounds twice at the 'Station'.
6. Press <Acknowledge> on the ↑ Person Machine Interface at the 'Station' 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
2 Loading data to the 'Station' [➙ 28]
31 | 178
4 Loading configuration from the station to the PC
4.8 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.
w The 'Site' is opened in Cerberus-Engineering-Tool.
w The PC is connected to the ↑ 'Station'.
w 'Station' and Cerberus-Engineering-Tool have the same 'Site' ID.
w 'Station' and Cerberus-Engineering-Tool are part of the same sales channel.
1. Select 'Commissioning' > 'Upload site'.
a The 'Upload site' and 'Connect' windows are opened.

a The 'Stations' are listed in the 'Upload site' window.
3. Select the 'Stations' whose configuration you would like to load to Cerberus-
Engineering-Tool and click on 'Start'.
a The 'Action confirmation' window opens.
4. Click on 'Yes'.
a The configuration is loaded to the PC.
a The progress is displayed in the 'Upload site' window.
4.9 Creating a backup of the 'Site' configuration

With the 'Create backup embedded configuration' function, you can create a
backup file of the ↑ 'Site' configuration.
The following conditions must be satisfied for a complete backup:
● 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
versions are saved in the BDV file name. You will find more information on
the format of the BDV file name in document A6V10210424.
● 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 backup file created. In this instance, 'incomplete' is
added to the file name of the backup file.
32 | 178
4
Creating a backup
w The 'Site' is opened in Cerberus-Engineering-Tool.
w The PC is connected to a 'Station'.
1. Select 'Commissioning' > 'Create backup embedded configuration'.
a The 'Create backup embedded configuration' and 'Connect' windows are
opened.

a The 'Site' configuration is loaded to the PC and saved as a backup file.
a The progress is displayed in the 'Create backup embedded configuration'
window.
Backup file
● The backup file is saved in the following directory as standard:
C:\ProgramData\Siemens\FX7230\[Softwareversion]\Sites\embeddedBackups
● The backup file has the following name:
<'Site' name>_<backup counter>(_incomplete).fsc
Example: Test_Site_007_incomplete.fsc
– 'Site' name: Name of the 'Site'.
– Backup counter: Three-digit number that is automatically assigned to each
backup.
– 'incomplete': If it was not possible to create a complete backup, 'incomplete'
is added to the file name.
● A maximum of ten 'Site' backup files are saved. If more than ten backup files
are created, the oldest file is automatically overwritten with the new one.
In the pre-settings, you can define that a backup 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'.
33 | 178
Commissioning overview
5 Commissioning variants
5 Commissioning overview
The 'Stations' on the C-WEB, such as control panels FC722/FC724 and fire
terminals FT724, 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
Impermissible commissioning procedures result in faults during operation.
● Only the procedures described in this document are permitted.
5.1 Commissioning variants
NOTICE
Not the current firmware version status of a newly installed fire detection
installation
Possible limitations for the configuration or use of devices.
● Compare the firmware version of a newly installed fire detection installation
with the currently approved firmware version status.
● Use the currently approved firmware version status.
● Update the firmware if required, in accordance with the chapter 'FW update
for main CPU and additional CPUs' in document A6V10210416; see chapter
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
● Adaptations on the ↑ Person
Tool
Machine Interface
With Without pre- B1 C
Cerberus- configuration ● Auto-configuration ● Initialize the 'Stations' for
Engineering- networking
Tool ● Adaptations in Cerberus-
Engineering-Tool ● Read in the C-NET devices by line
With pre- B2 ● Assign the logical elements to
configuration Cerberus-Engineering-Tool
● Read in the FDnet devices by line
● Assign the logical elements to
Cerberus-Engineering-Tool
Table 1: Commissioning variants
34 | 178
Definition of terms
5
5.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 the ↑ 'Station'
Auto-configuration results in the following:
● One ↑ 'Section' is created for each C-NET detector line.
● One ↑ 'Zone' is created for each 'Sensor'-'Channel' ('Automatic detectors',
and 'Manual call points').
● One 'Technical zone' is created for each 'Input'-'Channel'.
● 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 pre-configured. 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
↑ 'Detection tree' and ↑ 'Control tree'.
Adaptations The following procedures are examples of adaptations:
● Entering customer text for logical elements
● ↑ Changing detector parameter sets
● ↑ Configuring alarm devices
● Configuring 'Controls'
● Configuring the power supply
↑ Non-stationary devices Point detectors installed on a base apart from radio detectors.
35 | 178
5 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
5.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
36 | 178
Brief instructions on operating the 'Station'
5
5.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.
ok = <ok> Opens or runs a selected entry or menu item.
C Cancels all operating procedures and closes an open

= <C> list or 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
5.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.
37 | 178
A - Commissioning standalone 'Station' without PC
6 License
6 A - Commissioning standalone '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 [➙ 74]
3. Perform ↑ auto-configuration:
– Auto-configure 'Station'. Link [➙ 75]
OR
– Auto-configure detector lines individually. Link [➙ 76]
4. Adapt the auto-configuration in the ↑ Person Machine Interface, e.g.:
– Changing customer texts. Link [➙ 39]
– Set the ↑ parameter sets of the C-NET devices. Link [➙ 40]
5. Test the function of the ↑ 'Site' and remedy the problems, if any. Link [➙ 86]
6. Perform the completion tasks. Link [➙ 86]
38 | 178
Configuring the power supply
6
6.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 X1 / pin 1 '#BATT' X1 / pin 4 #COMMON
power supply unit
X1 / pin 2 X1 / pin 4 #COMMON
'#CONV'
X1 / pin 3 X1 / pin 4 #COMMON
'#MAINS'
Table 2: Configuring the power supply
You will find the pin assignments in document A6V10210368. See chapter
See also
6.2 Entering customer texts using the Person Machine

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

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

1. Select 'Topology' > ↑ 'Detection tree' > ↑ 'Area' > ↑ 'Section' > ↑ 'Zone' >
'Detect.' in the main menu.
2. Press the 'More Options' ↑ softkey.
3. Select 'Execute commands'.
4. Select the corresponding command:
– 'Select PS MANNED'
– 'Select PS UNMANNED'
– 'Select PS'
5. Select the desired ↑ parameter set.
a The following message is displayed: 'Command executed'
40 | 178
B1 - Commissioning standalone 'Station' with PC, without pre-configuration
7
7 B1 - Commissioning standalone '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 for C-NET detector lines.
Prerequisites
● The ↑ 'Station' is installed, but the batteries are not connected yet.
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 [➙ 74]
2. Perform auto-configuration:
– Auto-configure 'Station'. Link [➙ 75]
OR
– Auto-configure detector lines individually. Link [➙ 76]
3. Connect the PC to the 'Station'. Link [➙ 27]
4. Load the automatically created configuration to the PC. Link [➙ 77]
5. Adapt the configuration in Cerberus-Engineering-Tool. Link [➙ 77]
6. Load the configuration from the PC to the 'Station'. Link [➙ 30]
7. Test the function of the ↑ 'Site'. Link [➙ 86]
8. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [➙ 30]
9. Disconnect the PC from the 'Station'. Link [➙ 27]
41 | 178
B2 - Commissioning standalone 'Station' with PC, with pre-configuration
8
8 B2 - Commissioning standalone '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 [➙ 75]
5. Read-in the C-NET devices. Link [➙ 82]
6. Load the configuration from the 'Station' to the PC. Link [➙ 32]
9. Test the function of the 'Site'. Link [➙ 86]
42 | 178
C- Commissioning networked 'Stations'
9
9 C- Commissioning networked 'Stations'

You will find information on converting a ↑ standalone 'Station' to a networked
'Station' in chapter 'Converting a standalone station to a networked station
[➙ 78]'.
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 [➙ 75]
3. Connect the PC to each 'Station' individually. Link [➙ 27]
4. Initialize each 'Station' individually. Link [➙ 28]
5. Read-in the C-NET devices for all 'Stations'. Link [➙ 82]
43 | 178
Adding a 'Station' to an existing 'Site'
10
10 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 [➙ 75]
4. Initialize the 'Station'. Link [➙ 28]
44 | 178
Merging two 'Sites'
Setting detector parameter sets
11
11 Merging two 'Sites'

You can merge two ↑ 'Sites' to form one 'Site'.
NOTICE
Merging standalone 'Stations'
You have to convert ↑ standalone 'Stations' to networked ↑ 'Stations' to combine
'Stations' into one 'Site'. You will find more information in chapter 'Converting a
standalone station to a networked station [➙ 78]'.
Prerequisites
● Both 'Sites' are part of the same sales channel.
● Both 'Sites' have the same firmware version and ↑ BDV version.
● 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 stations and connected to an optical network (C-WEB/LAN).
– Large SAFEDLINK sub-nets are in the original state and not yet divided.
– Ethernet sub-nets 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 [➙ 28]
3. Load the configuration of all 'Stations' in 'Site' A from the PC to the 'Station'.
Link [➙ 30]
4. Connect the 'Sites' physically to one another. Link [➙ 46]
5. Load the configuration of the merged 'Site' from the 'Station' to the PC. Link
[➙ 32]
45 | 178
Merging two 'Sites'
11 Adding 'Site' B to 'Site' A
11.1 Adding 'Site' B to 'Site' A

w ↑ 'Site' A is open in Cerberus-Engineering-Tool.
1. Select 'Edit' > 'Merge sites'.
a The 'Merge sites' wizard opens.
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 'Merged site:' in field 'Site'.
4. Click on 'Next'.
a The conditions for merging are checked.
a The results of the check are listed in the 'Merge sites pre-check.' window.
5. Click on 'Next' if 'Result' is everywhere in the 'ok' column.
– If 'ok' is not everywhere, click on 'Cancel' and ensure that all the conditions
that are listed in the 'Check' column are satisfied.
a Cerberus-Engineering-Tool checks whether there are address conflicts at
'Stations' levels and suggests a possible new address.
a The possible new address is listed in the 'Station re-addressing.' window.
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'.
a The 'Sites' are merged.
a The 'Merge completed.' window opens.
9. The 'Required action' column informs you which action needs to be carried out
for the 'Stations':
– 'INITIALIZE': The 'Station' must be initialized
– 'DOWNLOAD': Loading the configuration from the PC to the 'Site' will
suffice
10. Click on 'Show the log file.' to view the protocol.
11. Click on 'Save report as file...' to save and print a merging report. This report
also shows which 'Stations' must be initialized.
12. Click on the 'OK' button to close the window.
11.2 Connecting 'Sites' physically to one another

Connect the two 'Sites' physically to one another.
You will find more information in document A6V10210390. See chapter 'Applicable
documents'.
See also
46 | 178
Changing and expanding the FDnet/C-NET detector line
Extending the detector line to include additional devices
12
12 Changing and expanding the FDnet/C-NET

detector line
12.1 Extending the detector line to include additional

devices
NOTICE
Incorrect assignment between detector/detector zone 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 zone and customer text.
pages.
1. Switch the C-NET detector line off. Link [➙ 79]

2. Mount and wire the new devices. Link [➙ 47]
4. Connect the PC to the ↑ 'Station'. Link [➙ 27]
6. Configure the new devices. Link [➙ 48]
12.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. Mount 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.
47 | 178
12 Replacing stationary devices of the same type
12.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'.
12.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 [➙ 86]
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
48 | 178
Permanently removing stationary devices
12
12.3 Permanently removing stationary devices
pages.

2. Remove the C-NET devices. Link [➙ 82]
5. Remove the physical representation of the devices and the logical elements in
Cerberus-Engineering-Tool. Link [➙ 83]
6. Switch the C-NET detector line on. Link [➙ 79]
You can also delete the physical representation of the C-NET devices individually
via the control panel's ↑ Person Machine Interface. Link [➙ 83]
12.4 Removing or replacing non-stationary devices

The product range includes bases with or without a loop contact.
12.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.
12.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 or address 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.

a The control panel detects that the C-NET device is missing and reports a
'Fault'.
2. Perform the necessary activities.
49 | 178
12 Removing or replacing non-stationary devices
3. Re-insert the C-NET device in the C-NET in the same, previous position.
4. Acknowledge the 'Fault'.
a If this 'Fault' is no longer displayed, the control panel updates the settings of
the re-inserted C-NET device.
a 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
2 Restarting the detector line [➙ 80]
12.4.1.2 Replacing non-stationary devices of the same type
pages.
1. Switch the test mode on. Link [➙ 84]

2. Remove the C-NET device you want to replace from the base.
3. Wait approx. 20 seconds.
4. Insert the new device of the same type.
a 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.
5. Switch ↑ normal operation on. Link [➙ 85]
50 | 178
Removing or replacing non-stationary devices
12
12.4.1.3 Replacing non-stationary devices of different types
pages.
1. Remove the C-NET device from its base.

a The ↑ 'Station' detects that the device is missing and reports a 'Fault'.
2. Delete the C-NET device on the ↑ Person Machine Interface on the control
panel. Link [➙ 83]
3. Insert the new C-NET device in the base.
7. Replace the C-NET device in the 'Zone'. Link [➙ 51]
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'.
12.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.
51 | 178
12.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
2 Correcting swapped devices [➙ 158]
12.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.
52 | 178
Removing or replacing non-stationary devices
12
12.4.2.3 Replacing a non-stationary device of a different type
pages.

a 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
control panel. Link [➙ 83]
4. Insert the new C-NET device in the base.
8. Replace the C-NET device in the 'Zone'. Link [➙ 53]
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
53 | 178
12.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.
1. Switch the 'Zone' off. Link [➙ 79]

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 [➙ 80]
a For all the re-inserted C-NET devices, a localization fault is displayed.
6. Restart the C-NET detector line. Link [➙ 80]
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'
12.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 [➙ 82]
4. Delete the C-NET devices individually via the ↑ Person Machine Interface on
the control panel. Link [➙ 83]
7. Remove the logical elements in Cerberus-Engineering-Tool. Link [➙ 83]
54 | 178
Replacing 'Manual call point' of the same type
12
12.5 Replacing 'Manual call point' of the same type
NOTICE
devices.
pages.
1. Switch on the replace mode. Link [➙ 55]

2. Replace the 'Manual call point' with a 'Manual call point' of the same type.
3. Switch off the replace mode. Link [➙ 56]
4. Test the 'Manual call point'. Link [➙ 56]
You will find more information about installing and uninstalling in the
documentation for the corresponding 'Manual call point'.
12.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.
a The following message is shown following successful switching on: 'Command
executed'.
a The yellow 'ISOLATION' LED lights up.
a The ↑ detector line is de-energized.
55 | 178
12 Convert two stubs into a loop
12.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.
a The following message is shown following successful switching off: 'Command
executed'.
a The yellow 'ISOLATION' LED goes out.
a The yellow 'DETECTOR TEST' LED lights up.
a The 'Manual call point' is in test mode.
12.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.
12.6 Convert two stubs into a loop
pages.
w 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 [➙ 79]
2. Wire both stubs to a ↑ loop. You will find more information about this in
3. Read-in the C-NET devices. Link [➙ 82] Start with the first 'Line' (in the
example 'Line' 11).
a The second 'Line' is adopted and the loop is formed (in this example,
'Line' 1).
See also
56 | 178
Connecting a sub-stub to a loop
12
12.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
57 | 178
Calibrating an FDnet/C-NET detector line
13 Connecting a sub-stub to a loop
13 Calibrating an FDnet/C-NET detector line

General
WARNING
Impermissible line configuration
An impermissible line configuration can cause the alarm devices connected to this
line to be supplied with insufficient power in the event of a fire. This prevents the
alarm from sounding in the corresponding parts of a building. This can cause
serious injuries or death.
● Make sure that all lines of a line card have a permissible line configuration by
calibrating them successfully. You will find information about the requirements
for a permissible line configuration in the 'Planning detector lines' chapter of
the document 'A6V10210362'.
Line calibration enables users to check whether sufficient power is being supplied
to all devices in an installed line during commissioning and ongoing operations; the
power supply can even be checked in the event of an alarm. This is particularly
helpful when the line topology or power-relevant configuration parameters of a line
are changed.
Another objective of line calibration is to determine how much additional line
resistance ΔRmax is possible before the line devices fall below the required supply
voltage in case of corrosion, gradual cable breakage, or thermal drift.
In the event of thermal drift, the line resistance RLine increases by ≈ 0.4 %/ °C.
In an unheated warehouse, the difference in temperatures under the ceiling in
summer and winter could amount to 50 °C. This could lead to the line resistance
being ≈ 20 % higher in summer than it is in winter.
The line calibration also shows the maximum possible current consumption of all
line devices per line card.
Time of a line calibration process

The time of a line calibration process depends on how this has been configured in
the 'Cerberus-Engineering-Tool' for each individual line.
The following configuration modes are available:
● 'Automatic with manual recalibration'
● 'Automatic without manual recalibration'
● 'Manual'
● ' - (disabled)'
In the default settings, a line is set to 'Automatic with manual recalibration' in the
configuration.
You will find information on configuring the line calibration in document
'A6V10210424'.
The duration of a line calibration consists of a 45-second base time plus about 1
second per installed 'Voice alarm sounder beacon/Voice al. sound. beacon base'
device on the line to be calibrated. This means a line with 252 'Voice alarm
sounder beacon/Voice al. sound. beacon base' devices can be calibrated in about
5 minutes.
58 | 178
Automatic line calibration
13
Calibration modes
Parameters Value Description

'Line calibration mode' 'Automatic without manual recalibration' Calibration of the selected line takes
place automatically each time the line
card is restarted if a setting relevant to
power consumption has been adjusted.
Manual recalibration of the line is not
possible during active operation.
'Automatic with manual recalibration' Calibration of the selected line takes
place automatically each time the line
card is restarted if a setting relevant to
power consumption has been adjusted.
Manual recalibration of the line is
possible during active operation.
'Manual' Calibration of the selected line can only
be triggered manually on the 'PMI'.
' - (disabled)' Calibration of the selected line is
deactivated.
13.1 Automatic line calibration
The line must be configured for automatic line calibration so that the system can
perform the process if necessary. You will find information on configuring the line
calibration in document 'A6V10210424'.
The station does not block the execution of a line calibration if some devices are
active on the line to be calibrated at this time. The station only blocks line
calibration if the station is in alarm condition.
The system automatically calibrates a line in the following cases after restarting
the fire control panel for the line card or the line:
● The line topology has changed.
● The configuration of the brightness level and/or the sound level of the sounders
has changed.
After each line calibration, the system saves a signature of all parameters and their
values that affect the power consumption of the line. After every restart, the
signature for the line is recalculated and compared against the signature for the
last calibration. If this comparison reveals that the signatures are different, the line
is automatically recalibrated.
In the following case, you need to manually calibrate all lines of a periphery board
or a line card, even if automatic calibration is activated:
● A periphery board with an integrated line card has been changed.
● A line card has been changed.
If the 'Automatic without manual recalibration' calibration mode is configured for a

line, then it must first be changed to the 'Automatic with manual recalibration' or
'Manual' calibration mode in the configuration. Otherwise, it will not be possible to
manually calibrate the line.
59 | 178
13 Manual line calibration
13.2 Manual line calibration

Calibrate a line manually on the 'PMI' in the following cases if automatic line
calibration is deactivated in the configuration of the line:
● The line topology has been changed.
has changed.
● The PMI displays a calibration error for a line.
Calibrate all lines of a periphery board or a line card manually on the 'PMI' in the
following cases, even if automatic line calibration has been activated in the
configuration of the line:

Calibrating lines manually
5 minutes.
The station does not block the execution of a line calibration if some devices are
active on the line to be calibrated at this time. The station only blocks line
calibration if the station is in alarm condition.
w The fire control panel has started up.

w There are no alarms present on the fire control panel.
w The configuration of the line permits manual calibration. You will find more
information about this in document 'A6V10210424'.
w Required access level: 3
1. Open the following path in the main menu on the 'PMI':
'Topology' > 'Hardware tree' > 'Station xx' > 'C-NET line card xx'
a The display shows the menu for the line card in question.
2. In the 'C-NET line card xx' menu, highlight the line you want to calibrate.
3. Select the 'More options' function in the softkey bar.
a The display shows a list.
4. In the list, select the following: 'Execute commands' > 'Calibrate'
a The system calibrates the selected line and then stores the calibration report
for the line.
60 | 178
Calibration report
13
13.3 Calibration report

The calibration report contains the main measurement results or the calibration
figures for a line calculated from these results.
Displaying the calibration report on the 'PMI'

1. Open the following path in the main menu on the 'PMI':
2. In the 'C-NET line card xx' menu, highlight the line for which you require the
calibration report.
4. In the list, select the following: 'Execute commands' > 'Calibration report'
a The display shows the calibration report.
5. Use the navigation keys to navigate through the entries in the calibration report.
You will find more information about the individual entries in the section
'Calibration report' below.
61 | 178
13 Calibration report
Figures and calculation variables

In the following section, you will find the main figures and calculation variables
needed to understand and interpret the calibration report.
Line calibration for lines with a stub topology has a reduced functional scope as
certain calculation variables cannot be measured.
Figure / calculation Description

variable
Iquiet The measured power consumption of a line in an quiescent condition.
Inom Calculated nominal power consumption of all devices in an alarm scenario.
Inom = ILine[t1] + ILoad compensation non-'Voice alarm sounder beacon/Voice al. sound.
beacon base' devices
The nominal power consumption is made up of the measured power consumption
of all 'Voice alarm sounder beacon/Voice al. sound. beacon base' devices on the
line and the calculated compensation value for all non-'Voice alarm sounder
beacon/Voice al. sound. beacon base' devices on the line.
Imax Calculated maximum power consumption of all devices in an alarm scenario with
a simultaneous cable break directly at the connection terminal or a short-circuit.
Imax = max(Icable break at terminal<A,B>) + Iload compensation non-'Voice alarm sounder
beacon/Voice al. sound. beacon base' devices
Information: For the calculation, the system takes the larger measured value for
an assumed cable break on connection terminals A or B.
Itot The calculated total power consumption of the line card in an alarm scenario.
RLine+ The measured line resistance on the plus wire of the line.
RLine- The measured line resistance on the minus wire of the line.
∆Rmax The calculated tolerance of the line when faced with a gradual cable break and
thermal drift.
The value reveals how much additional line resistance the line can still withstand
without the individual line devices falling below their required supply voltage in an
alarm scenario and in the worst assumed underlying conditions*.
The following applies for a permitted line: ∆Rmax >0 Ω
UDevice The measured voltage on an 'Voice alarm sounder beacon/Voice al. sound.
beacon base' line device in the worst assumed underlying conditions*.
* The worst possible underlying conditions include a gradual cable break directly
on one of the line's connection terminals and a maximum assumed thermal drift of
∆T = 10 °C.
62 | 178
Calibration report
13
Entries in the calibration report

Entry in the calibration Possible content* Description
report
Header: Line 1/2/1 Information on the line created for the
ReportCalibration 2018-04-24 10:11:12 calibration report.
1. Calibration status Line 1/2/1 UNCALIBRATED The entry indicates the calibration
Loop 1_1/1_2 status for the line. The calibration may
have the following status:
● Uncalibrated: There is no data on a
previously completed calibration
process for a line in the system.
Line 1/2/1 CALIBRATED - PASS ● Calibrated: There is data on a
Loop 1_1/1_2 previously completed calibration
process for a line in the system. The
Line 1/2/1 CALIBRATED - FAIL entry also shows whether the
Loop 1_1/1_2 calibration was successful.
Line 123 / 121 / 4 RE - CALIBRATION ● Recalibration required: During
Loop 1_1/1_2 active operation, this indicates
whether the line needs to be
recalibrated. The data from the last
calibration is no longer valid as the
line topology and/or configuration
parameters have been changed in a
way that affects the power
consumption of the line.
2. Time since last Date/time: 2018-04-20 11:12:13 The entry shows the last time the line
calibration Line 1/2/1 PASS was calibrated and whether the
calibration process was successful.
3. Power consumption of FDnet line card The entry shows the entire power
the line card Module 1/2 PASS Itot = 499 mA consumption of the line card in an alarm
scenario. The following results are
possible:
● Pass: The power consumption of
the line is below the maximum load
capacity of the line card of 0.5 A.
FDnet line card ● Fail: The power consumption of the
Module 1/2 FAIL Itot = 580 mA line is above the maximum load
capacity of the line card of 0.5 A.
FDnet line card ● Unknown: The entire power
Module 1/2 UNKNOWN Itot = 420 mA consumption of the line card is
unknown as either some of the lines
on the card have not been
calibrated or line calibration for
certain lines has been deactivated.
The displayed power consumption
is the sum of all calibrated lines on
the line card.
63 | 178
13 Calibration report

report
4. Power consumption of Loop 1_1/1_2 The entry indicates the calculated value
the line (nominal) Line 1/2/1 PASS Inom = 500 mA for the nominal power consumption of
the line. This is made up of the
measured power consumption of all
'Voice alarm sounder beacon/Voice al.
sound. beacon base' devices on the line
and the calculated compensation value
for all non-'Voice alarm sounder
beacon/Voice al. sound. beacon base'
devices on the line.
The following results are possible:
● Pass: The calculated nominal power
consumption is below 0.5 A.
Loop 1_1/1_2 ● Fail: The calculated nominal power
Line 1/2/1 FAIL Inom = 600 mA consumption is above 0.5 A.
5. Power consumption of Loop 1_1/1_2 The entry indicates the calculated

the line (maximum) Line 1/2/1 PASS Imax = 499 mA maximum power consumption of the
line. This is made up of the maximum
power consumption of all 'Voice alarm
sounder beacon/Voice al. sound.
beacon base' devices in the event of an
open line directly at the connection
terminal and the calculated
compensation value for all non-'Voice
alarm sounder beacon/Voice al. sound.
beacon base' devices on the line.
● Pass: The calculated maximum
power consumption is below 0.5 A.
Loop 1_1/1_2 ● Fail: The calculated maximum
Line 1/2/1 FAIL Imax = 649 mA power consumption is above 0.5 A.
6. Power consumption of Loop 1_1/1_2 The entry shows the measured power
the line while idling Line 1/2/1 PASS Iquiet = 12 mA consumption of the line in an unloaded
state.
7. Line resistance - Plus Loop 1_1/1_2 The entry shows the measured line
Line 1/2/1 PASS ..... R+ = 12.3 resistance on the line's plus cable in
ohm [Ω].
8. Line resistance - Minus Loop 1_1/1_2 The entry shows the measured line
Line 1/2/1 PASS ..... R- = 12.5 resistance on the line's minus cable in
ohm [Ω].
9. Tolerance of the line Loop 1_1/1_2 The entry shows the calculated value
resistance Line 1/2/1 PASS ..... dRmax = 20.0 for the maximum tolerance of the line
when faced with a gradual line break
and thermal drift.
● Pass: The calculated difference to
the current line resistance is >0 Ω.
Loop 1_1/1_2 ● Fail: The calculated difference to the
Line 1/2/1 FAIL ..... dRmax = - 2.1 current line resistance is ≤0 Ω.
64 | 178
Calibration report
13

report
10th to max. 252nd FDS227 - RR Entries 10 to max. 252 show the
Voltage drop on the Device 1/2/1/1 PASS U = 23.4 V calculated voltage drop on each 'Voice
individual 'Voice alarm alarm sounder beacon/Voice al. sound.
sounder beacon/Voice al. beacon base' device in the line.
sound. beacon base' The following results are possible:
devices on the line
● Pass: The calculated operating
voltage for the 'Voice alarm sounder
beacon/Voice al. sound. beacon
base' device in question is ≥ 16 V
for devices with beacon and ≥ 12 V
for devices without beacon.
FDS227 - RR ● Fail: The calculated operating
Device 1/2/1/1 FAIL U = 15.7 V voltage for the 'Voice alarm sounder
beacon/Voice al. sound. beacon
base' device in question is < 16 V
for devices with beacon and < 12 V
for devices without beacon.
* The specified lines, devices, and values are only examples.
65 | 178
13 Troubleshooting
13.4 Troubleshooting
Troubleshooting during line calibration
The following table lists options for troubleshooting for possible fault entries in the
calibration report:
Entry in the calibration Content* Troubleshooting

report
1. Calibration status Line 1/2/1 CALIBRATED - FAIL The last calibration of the line failed.
Loop 1_1/1_2 Check the other entries in the
calibration report for the line in order to
narrow down the cause.
Line 123 / 121 / 4 RE - CALIBRATION The line must be recalibrated. The data
Loop 1_1/1_2 from the last calibration is no longer
valid as the line topology and/or
configuration parameters have been
changed in a way that affects the power
consumption of the line.
Recalibrate the line. You will find more
information on this in chapter 'Manual
line calibration [➙ 60]'.
3. Power consumption of FDnet line card The power consumption of the line is
the line card Module 1/2 FAIL Itot = 590 mA above the maximum load capacity of
the line card of 0.5 A.
Possible causes and troubleshooting:
● Too many line devices are
connected to the line card.
● The configured settings for the
'Sounder volume' and 'Beacon
intensity' properties are too high.
– Reduce the sound level of the
alarm sounder or the intensity of
the beacons on the affected line
card. You will find information on
the configuration of the sound
level of the alarm sounder or the
intensity of the beacons in
document A6V10210424.
FDnet line card The entire power consumption of the
Module 1/2 UNKNOWN Itot = 469 mA line card is unknown as either some of
the lines on the card have not been
calibrated or line calibration for certain
lines has been deactivated.
Troubleshooting:
● Check the calibration status of the
individual lines on the line card:
– Activate the calibration for the
individual lines in the system
configuration.
66 | 178
Troubleshooting
13

report
4. Power consumption of Loop 1_1/1_2 The calculated nominal power
the line (nominal) Line 1/2/1 FAIL Inom = 680 mA consumption for the line is above 0.5 A.
5. Power consumption of Loop 1_1/1_2 The calculated maximum power
the line (maximum) Line 1/2/1 FAIL Imax = 680 mA consumption for the line is above 0.5 A.
67 | 178
13 Troubleshooting

report
9. Tolerance of the line Loop 1_1/1_2 The calculated difference to the current
resistance Line 1/2/1 FAIL ..... dRmax = - 2.1 line resistance is ≤0 Ω. In an alarm
scenario, individual devices may fail if a
cable break occurs at the same time
and/or a thermal drift increases the line
resistance.
● The conductor cross-section is too
low in relation to the laid length of
line.
● Faulty wiring between two line
devices.
– Check the operating voltage of
the individual devices in the
calibration report.
10th to max. 252nd FDS227 - RR The calculated operating voltage for the
Voltage drop on the Device 1/2/1/1 FAIL U = 15.7 V 'Voice alarm sounder beacon/Voice al.
individual 'Voice alarm sound. beacon base' device in question
sounder beacon/Voice al. is < 16 V for devices with beacon and
sound. beacon base' < 12 V for devices without beacon.
devices on the line ● The conductor cross-section is too
low in relation to the laid length of
line.
● Faulty wiring between two line
devices.
– Check the operating voltage of
the individual devices in the
calibration report.
*) The specified lines, devices, and values are only examples.
68 | 178
Troubleshooting
13
See also
2 Manual line calibration [➙ 60]
69 | 178
Commissioning a control panel with integrated extinguishing
14 Troubleshooting
14 Commissioning a control panel with

integrated extinguishing
Prerequisites
● The fire control panel is installed, but the batteries are not connected yet.
● The cables for the extinguishing components, the ↑ detector lines, and the line
supply have been inserted in the integrated fire detector and extinguishing
control panel but are not connected yet.
pages.
Commissioning steps
1. Create the ↑ pre-configuration for the extinguishing card and associated
extinguishing components. You will find more information in document
2. Prepare the integrated fire and extinguishing control panel for commissioning.
Link [➙ 71]
3. Connect the PC to the integrated fire and extinguishing control panel. Link
[➙ 27]
4. Load the configuration from the PC to the integrated fire and extinguishing
control panel. Link [➙ 30]
5. Calibrate the monitored outputs. Link [➙ 72]
7. Test the extinguishing function. You will find information about the
extinguishing test functions in document 'A6V10211076'.
PC to the integrated fire and extinguishing control panel. Link [➙ 30]
9. Disconnect the PC from the integrated fire and extinguishing control panel. Link
[➙ 27]
10. Perform the completion tasks. Link
See also
2 Preparing 'Station' for commissioning –without BDV
installation [➙ 75]
2 Connecting the PC to the station [➙ 27]
2 Loading configuration from the PC to the station [➙ 30]
2 Checking 'Site' function [➙ 86]
2 Disconnecting the PC from the station [➙ 27]
2 Preparing the control panel with integrated extinguishing for
commissioning [➙ 71]
2 Calibrating monitored outputs [➙ 72]
70 | 178
Preparing the control panel with integrated extinguishing for commissioning
14
14.1 Preparing the control panel with integrated

extinguishing for commissioning
1. Connect the cables for the extinguishing components, ↑ detector lines, and the
peripheral devices.
2. Connect the power supply (mains and batteries).
a The fire control panel starts and reads in the internal hardware.
a During start-up, the 'FAULT' LED flashes and the display shows the
progress.
a During start-up, the firmware version F-FXS7211 is displayed.
3. Wait until the display indicates the selection of the ↑ BDV.
a The fire control panel is prepared for commissioning.
It is not necessary to install the BDV for the further procedure. This saves having
to restart the 'Station'.
Following preparation, you can for instance perform the following steps, depending
on the selected commissioning variant:
● Load the configuration from the PC to the fire control panel.
71 | 178
14 Calibrating monitored outputs
14.2 Calibrating monitored outputs

The monitored outputs on the extinguishing card are monitored for short-circuits
and open lines. The lines' quiescent level can be imported and stored with a
calibration function on the 'PMI' display. If a deviation from the quiescent value is
detected, the control panel evaluates a short-circuit or an open line.
Perform calibration in the following cases:
● Initial commissioning: calibrate all installed extinguishing cards
● Amended hardware on the monitored outputs on an extinguishing card
WARNING
Uncalibrated or incorrectly calibrated outputs
Outputs that have not been calibrated or that have been calibrated incorrectly
could lead to short-circuits or open lines at the monitored outputs being detected
incorrectly. This could lead to a system fault being ignored and could result in
severe or fatal injuries.
● Calibrate the monitored outputs for all extinguishing cards when
commissioning for the first time.
● Calibrate the monitored outputs each time the hardware at the outputs on an
extinguishing card is modified.
w The monitored outputs are wired to the activated devices.

w The lines have already been checked for short-circuits and open lines.
w The lines' resistance values have already been measured and are within the
specified range.
w The installation publishes at least one general fault on a non-calibrated
monitored output on PMI.
w The installation is in the 'Quiet' state.
1. On the 'PMI' display, open the following path in the main menu:
'Topology' > 'Hardware tree' > 'Station xx'
a The display shows the menu for the station in question.
2. In the 'Station xx' menu, mark the entry 'Extg.gr xx' for the flooding zone in
question.
4. In the list, select the following: 'Execute commands' > 'Calibrate'
a The system reads and stores the quiescent levels of all monitored outputs on
the extinguishing card.
72 | 178
CE marking
14
14.3 CE marking
Following the successful acceptance of the integrated extinguishing system, the
template for the extinguishing system's CE marking must be filled out. You will find
the form for printing out and completing in document 'A6V11370445'.
On the form, cross the applicable features of the extinguishing system and enter
the corresponding times. The following table shows an example for the CE
marking:
XXXX
Siemens Switzerland Ltd, Building Technologies
Gubelstrasse 22
6300 Zug, Switzerland
18
XXXX-XXX-XXXXX
EN 12094-1, electrical automatic control and time delay devices
Class of the ambient conditions: A
Flooding zone 1 Comment
High pressure gas
Pre-controlled sprinkler system
Delay of the triggering signal (4.17) 0 to 60 s
Signal representing the flow of the extinguishing agent (4.18) Pressure switch
Monitoring of the state/position of components (4.19)
Stop key (4.20)
Control of the discharge time (4.21) Sec. / minutes
Manual-only mode (4.23)
Triggering signals to equipment within the fire extinguishing
installation (4.24)
Extinguishing signals to spare cylinders (4.25)
Triggering of equipment outside the fire extinguishing installation
(4.26)
Emergency abort device (4.27)
Control of extended discharge (4.28)
Release of the extinguishing agent for selected flooding zones (4.29)
Activation of alarm devices with different alarm signals (4.30)
Response time for the activation state ≤3 s
Response time for activation of the outputs ≤1 s
73 | 178
Detailed commissioning steps
15 Preparing 'Station' for commissioning
15 Detailed commissioning steps

In the following chapters, you will find detailed commissioning steps that are
referred to in several chapters.
15.1 Preparing 'Station' for commissioning

1. Connect the cables for the ↑ detector lines and the peripheral devices.
a The ↑ 'Station' starts and reads in the internal hardware.
progress.
4. Press the 'Install' ↑ softkey and confirm with the 'Yes' softkey.
a 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.
a You are prompted to enter a PIN.
7. Enter the PIN and confirm with <ok>.
a The 'User successfully logged in' message is displayed.
a The main menu is shown on the display.
8. Check the firmware of the 'Station' to ensure that it is up to date. To do this,
select the 'Topology' > 'Hardware tree' > 'Station' > 'More Options' > 'Show
details' menu items.
a 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'.
74 | 178
Preparing 'Station' for commissioning –without BDV installation
15
15.2 Preparing 'Station' for commissioning –without BDV

installation
1. Connect the cables for the ↑ detector lines and the peripheral devices.
a The ↑ 'Station' starts and reads in the internal hardware.
progress.
a 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'.
Following preparation, you can for instance perform the following steps, depending
on the selected commissioning variant:
● Initialize the 'Station'
● Auto-configure the 'Station'
● Load the configuration from the PC to the 'Station'
15.3 Auto-configuring 'Station'

1. Select 'Topology' > ↑ 'Hardware tree' > ↑ 'Station' in the main menu.
3. Select the 'Auto-configure station' command.
a The 'Station' is auto-configured.
a The following message is shown following successful ↑ auto-configuration:
'Command executed'
See also
75 | 178
15 Auto-configuring the detector line
15.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 startup,
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 'Line' 11. '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).
NOTICE
Overwriting an existing configuration
Parts of an existing customer-specific configuration are lost.
● First save an existing customer-specific configuration.
1. Select 'Main menu' > 'Topology' > ↑ 'Hardware tree' > ↑ 'Station' > 'Module'
(↑ line card) > 'Line'.
3. Select the 'Auto-configure line' command.
a The C-NET detector line is auto-configured.
a The following message is shown following successful ↑ auto-configuration:
'Command executed'
See also
76 | 178
Loading automatically created configuration to the PC
15
15.5 Loading automatically created configuration to the

PC
The description in this chapter only applies if a configuration has not yet been
loaded to the 'Station' and if the ↑ BDV was installed at the 'Station' after the
'Station' was started for the first time.
1. Select the 'File' > 'New site' menu item.

a The 'Create new site' window opens.
2. Select the 'Upload from station(s)' option field.
3. Click on 'Next'.
a The 'Create site by uploading from station(s)' and 'Connect' windows open.
4. In the 'Connect' window, select 'Local connection' and then click on 'OK'.
a The configuration is loaded to 'Cerberus-Engineering-Tool'.
a The progress is displayed in the 'Create site by uploading from station(s)'
window.
a The 'Site properties' window is opened after loading.
5. Change the entries if required and click on 'OK'.
a The 'New site confirmation' window opens.
6. Click on 'Yes'.
a The 'Site' is opened in Cerberus-Engineering-Tool.
15.6 Adapting configuration

Adapt the configuration of the ↑ Site' in Cerberus-Engineering-Tool, e.g.:
● Changing customer texts
● Setting the properties and the ↑ parameter sets
● Changing the assignment 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
77 | 178
15 Converting a standalone station to a networked station
15.7 Converting a standalone station to a networked

station
NOTICE
Configuring IP addresses manually
Once a standalone 'Station' has been converted to a networked 'Station', you
have to configure the IP address manually.
w The configuration for a ↑ 'Site' with a standalone 'Station' is loaded in

Cerberus-Engineering-Tool.
1. Select the 'Network' task card.
2. Open 'Global system configuration' > 'FS720 network configuration' > 'Ethernet
sub-net' in the tree structure.
3. Select 'Connections' to configure an Ethernet network.
– Alternative for SAFEDLINK network: Select 'Ethernet sub-net'.
– Select 'New element'.
– Add the 'SAFEDLINK sub-net' element.
– Open 'SAFEDLINK sub-net'.
– Select 'Connections'.
4. In the menu bar, click on 'Assign'.
a The 'Assign dialog' window opens.
5. Select the 'Station' on the right in the Network tree and click on 'Assign'.
a The standalone 'Station' is now a networked 'Station'.
6. Select the 'Station' under 'Connections'.
7. Configure the IP address on the 'Overview' tab.
a You have converted the standalone 'Station' to a networked 'Station'.
78 | 178
Switch off
15
15.8 Switch off
15.8.1 Safety during switch-off
WARNING
System parts that have been switched off make it impossible to acquire and
process alarms or faults!
Fire may spread unhindered.
● Deploy staff to monitor the deactivated area.
● You must switch deactivated parts of the 'Site' back on as soon as possible.
15.8.2 Switching off the detector line

1. Select 'Main menu' > 'Topology' > ↑ 'Hardware tree' > ↑ 'Station' > ↑ line card
> ↑ detector line.
3. WARNING! System parts that have been switched off make it impossible to
acquire and process alarms or faults! Select the 'Detector line OFF' command.
a The detector line is switched off.
15.8.3 Switch off zone

main menu.
2. Press the 'More Options' softkey and select 'Execute commands'.
3. WARNING! System parts that have been switched off make it impossible to
acquire and process alarms or faults! Select the 'Off' command.
a The 'Zone' is switched off.
15.9 Switching on
15.9.1 Switch on detector line

1. Select 'Main menu' > 'Topology' > ↑ 'Hardware tree' > ↑ 'Station' > ↑ line card
> ↑ detector line.
3. Select the 'Detector line ON' command.
a The detector line is switched on.
79 | 178
15 Restarting the detector line
15.9.2 Switch on zone

main menu.
3. Select the 'On' command.
a The 'Zone' is switched on.
15.10 Restarting the detector line
WARNING
1. Select 'Main menu' > 'Topology' > ↑ 'Hardware tree' > ↑ 'Station' > 'Module'
(line card) > 'Line'.
3. Select the 'Restart line' command.
a The ↑ detector line is restarted. The following messages are displayed:
'Line starting up'
'Device config.runs'
Start line test

Only test the line and line devices once the following messages have disappeared
from the PMI:
- 'Device config.runs'
- 'System startup completed'
80 | 178
Freezing outputs
15
15.11 Freezing outputs

You can freeze outputs with connected fire dampers to prevent them from being
activated if the 'Station' or line is restarted or in the event of a module reset. A
restart is required if a modified configuration is loaded to the 'Station'.
Duration of freeze
The output freeze lasts until the next restart or module reset. It is deactivated after
the restart or module reset. See chapter 'Enabling frozen outputs [➙ 81]' for how
to manually deactivate freezing.
w All line devices are switched on.

w Input/output modules with connected fire dampers are present on the line.
w The output freeze is activated / configured in the ↑ 'Site' configuration. See
1. At the 'Station', select the 'Station', a module, or a line in the hardware tree.
2. Select 'Execute Commands' > 'Freeze selected outputs ON'.
3. The 'Output positions frozen' message is displayed for the frozen outputs.
a You can now restart the 'Station' or the line or perform a module reset.
15.12 Enabling frozen outputs

w One or more outputs have been frozen / the 'Output positions frozen' message
is displayed for one or more outputs.
w All line devices are switched on.
1. At the 'Station', in the hardware tree select the 'Station', the module, or the line
that has been frozen or select the 'Output positions frozen' message for the
corresponding element.
2. Select 'Execute Commands' > 'Freeze selected outputs OFF'.
a Freezing of the outputs is deactivated.
81 | 178
15 Read in devices on detector line
15.13 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.
● For loop with line separator: Switch the second 'Line' or 'Line' 12 off.
● To read in a loop, always select the first 'Line', in this case 'Line' 11. 'Line' 12
is then read in automatically.
A loop is displayed with a 1-digit line number, in this case as 'Line' 1 once it
has been read in.
● Proceed in the same way from 'Line' 21/22 (loop 2) to 'Line' 41/42 (loop 4).
w For ↑ loop with line separator: The second 'Line' is switched off. Link [➙ 79]
1. In the main menu, select 'Topology' > ↑ 'Hardware tree' > ↑ 'Station' > ↑ line
card > ↑ detector line.
3. Select the 'Read in installed devices' command.
a The C-NET devices are read in.
a The following message is shown following successful reading in:
'Command executed'
15.14 Detaching the device

If you want to permanently remove a device, 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.
82 | 178
Delete the device on Person Machine Interface
15
15.15 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.
a The ↑ logical channel is displayed. For some devices, 'Device' is displayed
directly.
4. Press the 'More Options' softkey.
5. Select the 'Jump to link' menu item.
a The ↑ physical channel is displayed.
6. Press the 'Upper level' softkey.
a 'Device' is displayed.
7. Press the 'More Options' softkey.
8. Select the 'Execute commands' menu item.
9. Select the 'Remove/delete device' command.
a The control panel deletes the physical representation of the removed device.
a The logical channel element remains in the 'Zone'.
15.16 Remove the elements

If you have uninstalled an C-NET device for good, the corresponding elements,
e.g. the 'Cerberus-Engineering-Tool' must be removed from the logical structure
trees in Zone. You can search for elements using the 'Find' function.
documents'.
See also
15.17 Testing detectors

The commissioning personnel perform the function test for the ↑ automatic fire
detectors and the 'Manual call points'.
pages.
w The ↑ detector line has been commissioned.

1. Switch the test mode on. Link [➙ 84]
2. Initiate the detector. Link [➙ 84]
4. Test the logged test activations. Link [➙ 84]
83 | 178
15 Switching on test mode
15.17.1 Activate the detector

w 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.
a The ↑ alarm indicator for the activated detector flashes at each test activation.
a 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
15.17.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.
15.18 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.
a The yellow 'Detector test' LED lights up.
a 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'
84 | 178
Switch on normal operation
15
15.19 Switch on normal operation
There is a shortened procedure for switching individual 'Zones' to ↑ normal

operation. The procedure is described in the following section: 'Switching 'Zone' to
normal operation'
Switching 'Area', 'Section' or 'Zone' to normal operation

1. Select 'Topology' > ↑ 'Detection tree' in the main menu.
2. Select the element you want to switch to normal operation: ↑ 'Area',
↑ 'Section', or ↑ 'Zone'
4. Select a command from the following table.
a The element is switched to normal operation.
a The yellow 'Detector test' LED goes out.
Element Command
Area ● 'Non-MCP zones det.test END'
● 'MCP zones det.test END'
Section ● 'Non-MCP zones det.test END'
● 'MCP zones det.test END'
Zone ● 'Detector test END'
Commands under 'Execute commands'
You can also switch to normal operation at superordinate level for the command
in question. Test mode can also be exited in the 'Zone', 'Section' or 'Area', for
example.
Switching 'Zone' to normal operation

There is a shortened procedure for switching individual 'Zones' to normal operation:
1. Select 'Message summary' > 'Test message' in the main menu.
2. Select the displayed 'Zone' in test mode and press the 'Execute Commands'
softkey.
3. Select the 'Detector test END' command.
a The 'Zone' is switched to normal operation.
a The yellow 'Detector test' LED goes out.
85 | 178
15 Rectify localization errors
15.20 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.
a 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.
15.21 Checking 'Site' function

Test the function of the ↑ 'Site' in the various test modes.
You will find information on testing a 'Site' in the 'Testing' chapter of document
See also
15.22 Carrying out final commissioning work

Checking the date and time
1. Check the date and time.
2. Adjust the date and time, if required.
– To do this, select 'Settings/administration' > 'System commands' > 'Set
system time' in the main menu.
Setting the PIN for access levels

1. Set the PIN for access levels 1, 2.1, 2.2, and 3.
– To do this, select 'Settings/administration' > 'Manage PINs' in the main
menu.
2. Fit the housing cover.
3. 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.
86 | 178
Commissioning Ethernet switch (MM) FN2008-A1
Carrying out final commissioning work
16
16 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 A6V10210390. See chapter 'Applicable
documents'.
Commissioning
1. Install the 'Primary Setup Tool' software. Link [➙ 88]
2. Assign the IP address. Link [➙ 88]
3. Configure the FN2008-A1 using the Internet browser. Link [➙ 89]
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 A6V10210424.

The FN2008-A1 has no IP address in the factory setting. You must manually
assign the IP address.
See also
87 | 178
16 Install Primary Setup Tool
16.1 Install Primary Setup Tool
The 'Primary Setup Tool' software is included in the scope of supply for the
FN2008-A1.
l Start 'Primary Setup Tool' installation.

a Primary Setup Tool is installed.
a The DLC and PROFINET RT protocols are installed.
a 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 Primary Setup Tool.
16.2 Assign IP address
The FN2008-A1 is displayed as X204-2 in Primary Setup Tool.
w Primary Setup Tool is installed on the PC.

w 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'.
a 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.
a The assigned IP address is saved to the FN2008-A1.
5. Repeat the 'Load' process for each FN2008-A1.
a Each FN2008-A1 in the system has an individual IP address.
88 | 178
Configuring FN2008-A1 using Internet browser
16
16.3 Configuring 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.
WARNING
System manipulation due to unauthorized access
No alarm in a fire.
● Change the preset password.
● Create a password as per the IT security requirements from Siemens; see
chapter 'Password guidelines'.
1. Open the Internet browser and enter the FN2008-A1's IP address in the
address field.
a 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
a FN2008-A1 is configured.
89 | 178
17 Standalone FN2012-A1
17 Commissioning Ethernet switch (modular)

FN2012-A1
Malfunctions during a partial upgrade
Ethernet switch (modular) FN2012 is not compatible with Ethernet switch (MM)
FN2008 and so may only be used in panels ≥MP6.
See also
2 Updating the FW of Ethernet switch (modular) FN2012-A1
[➙ 142]
17.1 Standalone FN2012-A1

This description is for a standalone FN2012-A1 that is not connected to the station.
You will find information on mounting and installing the FN2012-A1 in document
The FN2012-A1 has no IP address in the factory setting.
Commissioning the standalone FN2012-A1

w The FN2012-A1 is not connected to the station.
1. Use the rotary switch to define a pre-configured IP address. Link [➙ 90]
2. Put the web interface into operation. Link [➙ 93]
3. Change the IP address of the FN2012-A1 in accordance with your network
requirements. Link [➙ 94]
4. Configure the redundancy role of the FN2012-A1. Link [➙ 95]
5. Deactivate any local ports on the FN2012-A1 that are not being used in
accordance with your safety requirements. Link [➙ 95]
6. Configure fault monitoring for local ports. Link [➙ 96]
17.1.1 Specifying a pre-configured IP address

You must assign a pre-configured IP address to a standalone FN2012-A1 as part
of its commissioning process.
1. Use the rotary switch on the FN2012-A1 to select an IP address in accordance
with the table further below.
2. Wait 10 s or reset the FN2012-A1 using the RESET button in order to apply the
set IP address.
If the rotary switch of the FN2012-A1 is in position 'E', the local ports are not
available. You cannot perform a firmware update or call up a web interface for the
FN2012-A1 when the switch is in position 'E'.
90 | 178
Standalone FN2012-A1
17
Rotary switch for device configuration
An Ethernet switch that is not integrated in a station must be configured via the
rotary switch. If the Ethernet switch is integrated, the rotary switch must be set to
'0'.
Using the rotary switch for device configuration, the Ethernet switch can be set to
pre-defined network addresses or operation modes.
To apply a new configuration, the setting must be made when the device is de-
energized or by means of a hardware reset.
Switch position IP address / operation mode Sub-net mask / operation mode

0 Configured via web interface or MoNet Configured via web interface or MoNet
bus bus
Factory setting: 0.0.0.0 Factory setting: 255.255.248.0
1 192.168.99.241 255.255.248.0
2 192.168.99.242 255.255.248.0
3 192.168.99.243 255.255.248.0
4 192.168.99.244 255.255.248.0
5 192.168.99.245 255.255.248.0
6 192.168.99.246 255.255.248.0
7 192.168.99.247 255.255.248.0
8 192.168.99.248 255.255.248.0
9 192.168.99.249 255.255.248.0
A 192.168.99.250 255.255.248.0
B 192.168.99.251 255.255.248.0
C 192.168.99.252 255.255.248.0
D Reserved (0.0.0.0) Reserved (255.255.255.255)
E Repeater operation Repeater operation
F 192.168.200.4 255.255.255.0
91 | 178
17 FN2012-A1 integrated into station
17.2 FN2012-A1 integrated into station

This description is for an FN2012-A1 that is connected to the station via a ribbon
cable.
You will find information on mounting and installing the FN2012-A1 in document
You will find an overview on converting a configuration in chapter 'Converting the

configuration [➙ 128]'.
You will find detailed information on converting a site to the latest market package
in document 'A6V10260976'. See chapter 'Applicable documents'
Commissioning an integrated FN2012-A1

w The FN2012-A1 is connected to the station via a ribbon cable.
w The rotary switch on the FN2012-A1 is set to '0'.
l Configure the integrated Ethernet switch FN2012-A1 in the Engineering Tool.
You will find detailed information on configuring the Ethernet switch FN2012-A1
in document A6V10210424. See chapter 'Applicable documents'.
See also
2 Commissioning a web interface [➙ 93]
2 Converting the configuration [➙ 128]
92 | 178
FN2012-A1 web interface
17
17.3 FN2012-A1 web interface
17.3.1 Commissioning a web interface
WARNING
Initial password not changed
The security of the web interface is not guaranteed if you do not change the initial
password. Network settings can be changed as a result of unauthorized access.
Changed network settings can cause the fire detection system to malfunction.
The web interface is blocked and can no longer be accessed if you do not change
the initial password within 7 operating days.
You will only be able to access the 'Password' tab in the web interface until the
initial password has been changed.
● When you first access the web interface, change the initial login password.
Opening the web interface

w Standalone FN2012-A1: You have pre-configured an IP address for the
FN2012-A1 using the rotary switch.
w Integrated FN2012-A1: In Engineering Tool, you have configured an IP address
for the FN2012-A1 that is valid within the sub-net.
w The FN2012-A1 and the PC are connected to the same Ethernet sub-net.
w Where applicable, the PC is connected to the Ethernet sub-net via a GAP.
1. Open the Internet browser and enter the pre-configured IP address of the
FN2012-A1 in the address field.
a The login window opens.
2. Enter the default login data in the Login window to log on:
– User name = 'admin'
– Password = 'fs20admin'
3. Select the 'Password' tab and set a customer-specific password. Information:
You will only be able to access the 'Password' tab in the web interface until the
initial password has been changed.
4. Confirm the password you have set with 'Save changes'.
a You have already commissioned the web interface.
See also
2 Specifying a pre-configured IP address [➙ 90]
93 | 178
17 FN2012-A1 web interface
17.3.2 Changing the IP address

When commissioning a standalone FN2012-A1, you must pre-configure the IP
address using the rotary switch. After that, you can assign an IP address to the
FN2012-A1 that cannot be pre-configured with the rotary switch.
Configuring the IP address manually

w The rotary switch has been used to pre-configure an IP address for the
FN2012-A1. Link [➙ 90]
w The web interface has been commissioned and the initial password changed.
Link [➙ 93]
1. Open the web interface of the FN2012-A1.
2. Select the 'Configuration' tab.
3. Enter the new IP address in the 'IP address' field.
4. Enter the sub-net mask in the 'Subnet mask' field.
5. Enter the standard gateway in the 'Default gateway' field.
6. Confirm your entries with 'Save changes'.
7. Set the rotary switch for device configuration to the '0' position.
8. Reset the FN2012-A1 using the RESET button on the device.
– If the FN2012-A1 is integrated and the rotary switch is already set to
position '0', you can reset the FN2012-A1 with the 'Reset device' button on
the 'Product' tab.
a You have changed the IP address of the FN2012-A1.
NOTICE
Setting the rotary switch to the '0' position
The change to the IP address only comes into effect when the rotary switch for
device configuration is set to the '0' position. If the rotary switch is set to a
different position, the standard settings for the corresponding position will be
adopted.
94 | 178
FN2012-A1 web interface
17
17.3.3 Configuring the redundancy role
Where an integrated FN2012-A1 is connected to the station, redundancy

management must be configured in Engineering Tool. It cannot be configured in
the web interface of the FN2012-A1.
w The FN2012-A1 has a valid IP address within the sub-net.

w The PC has access to the FN2012-A1 / is located within the same sub-net as
the FN2012-A1.
Link [➙ 93]
1. Open the web interface of the FN2012-A1 in the Internet browser.
2. In the web interface of the FN2012-A1, select the 'Configuration' tab.
3. Select the relevant role in the 'Redundancy role' field.
– If there are multiple FN2012-A1 devices on the Ethernet ring, one FN2012-
A1 must be designated as 'Manager' and all the other FN2012-A1 devices
granted the 'Client' role.
4. Save the settings with 'Save changes'.
17.3.4 Activating/deactivating local ports

Deactivate any local ports of the FN2012-A1 that are not being used to prevent
unauthorized persons from accessing the FN2012-A1 and the system via these
local Ethernet ports.
the FN2012-A1.
Link [➙ 93]
2. In the web interface of the FN2012-A1, select the 'Configuration' tab.
3. In accordance with how the ports have been assigned, select 'Disabled' to
deactivate local ports P2, P3, P4, or P5, or 'Enabled' to activate them.
4. Save the settings with 'Save changes'.
Resetting the FN2012-A1 to the factory setting automatically activates all local
ports. To reset it to the factory setting, press the RESET button for >5 s but <10 s.
95 | 178
17 FN2012-A1 web interface
17.3.5 Activating fault monitoring for local ports
Deactivated ports are not monitored for faults. Fault monitoring cannot be
configured for deactivated ports.

the FN2012-A1.
Link [➙ 93]
2. In the web interface of the FN2012-A1, select the 'Fault Mask' tab.
3. For local ports P2 to P5, select the appropriate type of fault monitoring: 'None',
'Link up', or 'Link down'.
– Activate 'Link down' monitoring for all the ports to which FS720 stations
have been connected.
Do not activate fault monitoring for local ports to which a management station has
been connected. With fault monitoring for local ports to which a management
station has been connected, a fault is displayed every time the management
station is restarted.
Activate fault monitoring only for ports to which FS720 stations have been
connected.
17.3.6 Activating port mirroring
NOTICE
Network settings may be disabled
When port mirroring is activated, this may disable the configured network settings.
Only use port mirroring for troubleshooting purposes for a limited period of time.
The network data traffic of source ports can be mirrored to a monitor port in order
to troubleshoot faults. Appropriate software can be used to record and save the
corresponding data traffic for subsequent fault analysis.
w You have specified a pre-configured IP address for the Ethernet switch
(modular) or configured the IP address manually.
w You have already commissioned the web interface.
1. Open the web interface of the Ethernet switch (modular).
2. Select the 'Configuration' tab.
3. Check the 'Enable port mirroring' checkbox.
4. Select the source ports and the monitor port.
5. Confirm your entries with 'Save changes'.
a You have activated port mirroring.
96 | 178
Restarting and resetting the FN2012-A1
17
17.4 Restarting and resetting the FN2012-A1

Via the web interface
You can perform the following resets on the 'Product' tab:
● Restart device: Click on 'Reset device'.
– The configuration is retained.
● Resetting the device to factory settings: Click on 'Factory reset'.
On the device
● Restart device: Press the RESET button.
– The configuration is retained.
● Resetting the device to factory settings: Press the RESET button for >5 s but
<10 s.
Resetting the FN2012-A1 to the factory setting automatically activates all ports.
97 | 178
Commissioning security module (firewall) FN2009-A1
18 Restarting and resetting the FN2012-A1
18 Commissioning security 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 [➙ 99]
2. Select the type and enter the MAC address. Link [➙ 100]
3. Enter the network settings. Link [➙ 101]
– Load configuration.
4. Create IP service definitions. Link [➙ 104]
5. Create firewall rules. Link [➙ 106]
– 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 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.
98 | 178
Installing Security Configuration Tool
18
18.1 Installing Security Configuration Tool
The 'Security Configuration Tool' software is included in the scope of supply for
the FN2009-A1.
l Install the 'Security Configuration Tool' software.

a The software is installed in the standard path 'SIMATIC' > 'SCALANCE' >
'Security' > 'Security Configuration Tool'.
a FN2009-A1 can be configured.
The FN2009-A1 is displayed as S612V2 in the Security Configuration Tool.
99 | 178
18 Selecting type and entering MAC address
18.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
w The PC is connected to FN2009-A1.
w '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'.
a More entry masks for required settings can be viewed.
Selecting type
1. Highlight the field below the 'Type' designation.
a The button for the dropdown list field is displayed.
2. Select 'S612V2'.
a Type is selected.
Entering MAC address

w The MAC address is known.
1. Double-click on the field below the 'MAC Address' designation.
a The MAC address can be edited.
2. Enter the MAC address for the FN2009-A1.

a MAC address is entered.
100 | 178
Entering network settings
18
18.3 Entering network settings

w The network topology is known.
w 'Advanced Mode' is selected.
l 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.
a 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.
w 'Module 1' is highlighted in the 'View' window.

1. Press <F4> on the keyboard or open the 'Edit' > 'Properties' menu.
a The 'Module Properties' window is displayed:
101 | 178
18 Entering network settings
2. Select the 'Routing Mode' tab.

a 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'.
a 'Internal sub-net mask' is automatically created.
a 'Routing Mode' is active.
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.

a The 'Network' tab is displayed.
2. Click on 'Add Router'.
a 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
a The router network data is entered.
102 | 178
Entering network settings
18
Loading the network settings to FN2009-A1

w MAC address is entered.
w IP addresses are entered.
1. Highlight the FN2009-A1 module in the project.
2. Select the 'Transfer > 'To Module' menu.
a The network settings are loaded to FN2009-A1.
a Network settings are entered.
103 | 178
18 Creating IP service definitions
18.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.

a The 'IP Service Definitions' window is opened.
2. Select the 'IP Services' tab.

3. Click on 'Add IP Service'.
a 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
a Required IP services are created.
5. Select the 'ICMP' tab.
6. Click on 'Add ICMP Service'.
a One row can be edited for one ICMP service.
104 | 178
Creating IP service definitions
18
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
a Optional IP services are created.

a 'IP Service Definitions' are created.
105 | 178
18 Creating firewall rules
18.5 Creating firewall rules

w IP service definitions are created.
w The network addresses are known.
1. Right-click on the module for which you want to create firewall rules.
2. Select 'Properties…'.
a The 'Module Properties' window for the selected module is displayed.
3. Select the 'Firewall Settings' tab.
a 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.
106 | 178
Creating firewall rules
18
6. Enter the required IP addresses.

a The firewall rules are created.
Loading the firewall rules to FN2009-A1

w The firewall rules are created.
1. Highlight the FN2009-A1 module in the project.
2. Select the 'Transfer > 'To Module' menu item.
a The firewall rules are loaded to FN2009-A1.
107 | 178
Commissioning the fire brigade periphery module FCI2001-D1
19
19 Commissioning the fire brigade periphery

module FCI2001-D1
The fire brigade 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
Figure 2: View of the fire brigade periphery module
X4–X6 Connection terminals

S101 Button
Procedure
1. Check the connected lines for short-circuit and open line.
2. Connect the lines.
a 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.
a The resistance values are read in.
108 | 178
Commissioning of I/O card (remote transmission) FCI2007-A1 and I/O card (horn/monitored) FCI2009-A1
20
20 Commissioning of 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 S501
FCI2007-A1 FCI2009-A1
S501 Button
Procedure
1. Check the connected lines for short-circuit and open line.
2. Connect the lines.
a 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.
a The resistance values are read in.
You can also read in the resistance values via the control panel's ↑ Person
Machine Interface.
109 | 178
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==
110 | 178
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==
111 | 178
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==
Table 3: Settings required
112 | 178
Updating the firmware
Preparation and security
22
22 Updating the firmware
22.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, event memory in the 'Station' and specific system data that is
only available on the 'Station' (e.g., modified customer texts, time stamps of
recent alarms, or persistent commands) are deleted.
● 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: 'Stations networked via C-WEB/LAN. See the chapter 'Updating
several 'Stations' simultaneously [➙ 116]'.
● 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 A6V10210424. See chapter 'Applicable
documents'.
● Converting the configuration data
– Updating the firmware requires the configuration data to be converted if the
new firmware and existing configuration are not compatible with one
another.
● ↑ BDV compatibility
– The BDVs are compatible when the major version and the minor version
are identical. The Bug fix version is not relevant for the compatibility. You
will find Information about BDV names and versions in document
113 | 178
22 Station: Updating the FW of the main CPU and additional CPUs
● The procedure for updating the firmware depends on the 'Station' configuration.
A 'Station' can be configured as follows:
– ↑ Standalone Station
– ↑ SAFEDLINK Station
– ↑ Router Station, ↑ Ethernet Station
– Modular 'Station' with -↑ CPU card
● Windows firewall setting
– To connect the PC to the 'Station', the Windows firewall settings must be
changed if possible. You will find more information on this in chapter
'Setting Windows firewall [➙ 24]'.
● 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 A6V10210424. See
See also
2 Updating several 'Stations' simultaneously [➙ 116]
22.2 Station: Updating the FW of the main CPU and

additional CPUs
The procedure for updating the firmware depends on the nature and function of the
↑ 'Station'. The procedures are described in the following chapters.
22.2.1 Standalone station and SAFEDLINK station

pages.
w You are familiar with the information in chapter 'Preparation and security
[➙ 113]'.
1. Import the new firmware into Cerberus-Engineering-Tool.
– Select 'File' > 'Import new resource package' from the menu and open the
file you want.
2. Load the configuration from the 'Station' or your archive to the PC. Link [➙ 32]
3. NOTICE! Possible data loss. Load the configuration data and event memory to
Cerberus-Engineering-Tool before updating the firmware.
– Saving the configuration data also backs up specific system data which is
only available on the 'Station'. This includes modified customer texts, time
stamps of recent alarms, or persistent commands.
4. Convert the configuration if necessary and rectify conversion faults. Link
[➙ 128]
6. Update the firmware on the main CPU and the additional CPUs. Link [➙ 117]
8. Test the firmware version on the additional CPUs. Link [➙ 129]
– Update the firmware, if required, of the additional CPUs again, if there is a
higher firmware version available. Link [➙ 126]
114 | 178
Station: Updating the FW of the main CPU and additional CPUs
22
22.2.2 Router station and Ethernet station
pages.
[➙ 113]'.
w A GAP with DHCP must be configured for the connection with the PC via C-
WEB/LAN.
– Select 'File' > 'Import new resource package' from the menu and open the
file you want.
3. NOTICE! Possible data loss. Load the configuration data and event memory to
Cerberus-Engineering-Tool before updating the firmware.
[➙ 128]
5. Via the Ethernet switch (MM) FN2008-A1, connect the PC to the C-WEB/LAN.
– Remove the network connection to the 'Station'and connect the PC locally
to the 'Station'. Link [➙ 27]
8. Test the firmware version on the additional CPUs. Link [➙ 129]
10. Restore the network connection.
115 | 178
22.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.
[➙ 113]'.
w A GAP with DHCP must be configured for the connection with the PC via C-
WEB/LAN.
w The 'Stations' are displayed together.
w You can update not more than eight 'Stations' simultaneously.
– Select the 'File' > 'Import new resource package' menu item and open the
file you want.
3. NOTICE! Data loss. Save the configuration data before updating the firmware.
[➙ 128]
5. 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.
7. Initialize each 'Station' individually. Link [➙ 28] To do so, you must connect the
PC to each 'Station' locally. Link [➙ 27]
8. Test the firmware version on the additional CPUs on each 'Station'. Link
[➙ 129]
10. Restore the network connection, if required.
116 | 178
22
22.2.4 FW update for main CPU and 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 [➙ 117]'
● 'PMI & mainboard FCM2027 [➙ 120]'
22.2.4.1 PMI & mainboard FCM2004

[➙ 113]'.
1. Select 'Update' > 'FW update main and additional CPUs' from the menu bar.
2. If the 'Password check' window opens, enter the password '12345678' and click
on 'OK'.
a The 'FW update main and additional CPUs' window opens.
4. Select the desired firmware version.

5. The firmware update can be started in two ways:
– Start the firmware update in Cerberus-Engineering-Tool.
– or
– Start the firmware update at the ↑ 'Station'. The procedure is described in
the following section.
Initializing the 'Station' instead of installing the ↑ BDV saves time. During
initialization, the BDV and the configuration data are loaded to the 'Station'.
You will find information on troubleshooting for the firmware update in chapter
'Error during firmware update [➙ 124]'.
117 | 178
Starting the firmware update at the 'Station' – FCM2004

1. Select 'Initiate update at station'.
2. Set the 'S38-2' switch to 'ON' on the rear of the operating unit.
3. Press the 'S32' button for approx. 5 s until the 'Station' restarts.
a The firmware update starts and takes up to ten minutes.
118 | 178
22
4. Click on 'OK' in the 'Information' window.

5. Select 'Run in background' in order to run the firmware update in the

background while continuing to work in Cerberus-Engineering-Tool.
a The active firmware update is indicated by the symbol on the right-

hand side of the status bar.
a 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.
6. 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'
7. On the 'Station', set the 'S38-2' switch to 'OFF'.
a The 'Station' is restarted many times. This procedure takes up to ten
minutes.
a After the restart, the 'Station' display shows the available BDVs. It is not
necessary to install a ↑ BDV at this point.
119 | 178
22.2.4.2 PMI & mainboard FCM2027

[➙ 113]'.
1. Select 'Update' > 'FW update main and additional CPUs' from the menu bar.
on 'OK'.
a The 'FW update main and additional CPUs' window opens.
4. Select the desired firmware version.

5. The firmware update can be started in two ways:
– Start the firmware update in Cerberus-Engineering-Tool.
– or
– Start the firmware update at the ↑ 'Station'. The procedure is described in
the following section.
Initializing the 'Station' instead of installing the ↑ BDV saves time. During
initialization, the BDV and the configuration data are loaded to the 'Station'.
You will find information on troubleshooting for the firmware update in chapter
'Error during firmware update [➙ 124]'.
120 | 178
22
Starting the firmware update at the 'Station' – FCM2027

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.
a A peeping sound confirms the function is being executed.

a The firmware is updated and the 'Station' restarts several times. This
procedure takes up to ten minutes.
121 | 178
3. Click on 'OK' in the 'Information' window.



a After the restart, the 'Station' display shows the available BDVs. It is not
necessary to install a ↑ BDV at this point.
22.2.4.3 Starting the firmware update in Cerberus-Engineering-Tool

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

– The available 'Stations' are preselected. If a 'Station' is available but not
preselected and a time stamp has been entered in the 'System status'
column, specific system data has been modified on the 'Station' but not yet
saved. The specific system data is deleted when you update the firmware.
NOTICE! Save the configuration data before updating the firmware.
122 | 178
22
4. Select 'Start'.
5. Confirm the firmware update with 'Yes' or reject the firmware update with 'No'.
6. Click on 'OK'.
123 | 178


a The progress of the firmware update is displayed on the 'Progress' tab.
Open the 'Progress' tab in the 'View' > 'Progress' menu.
a After the restart, the 'Station' display shows the available ↑ BDVs. It is not
necessary to install a BDV at this point.
22.2.4.4 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.
2. Press <Acknowledge> on the Person Machine Interface to switch off the
Updating additional CPUs at the 'Station'

If errors are present for additional CPUs following the firmware update, you can
perform the update for the additional CPUs again at the 'Station'.
1. In the 'Main menu', select the 'Topology' > 'Hardware tree' > 'Station' menu
item.
2. Press <More Options>.
3. Select 'Execute commands'.
a The 'Select command' window is displayed.
4. Select 'Update incompatible firmware'.
a The firmware of the additional CPUs is updated.
124 | 178
Station: Updating the FW of the additional CPUs only
22
22.3 Station: Updating the FW of the additional CPUs

only
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.
[➙ 113]'.
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 [➙ 126]
See also
2 Loading configuration from the station to the PC [➙ 32]

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.
[➙ 113]'.
w A ↑ GAP with DHCP is configured for the connection with the PC via C-
WEB/LAN.
2. Via the Ethernet switch (MM) FN2008-A1, connect the PC to the C-WEB/LAN.
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 [➙ 126]
6. Disconnect the PC from C-WEB/LAN.
125 | 178
22 Station: Updating the FW of the additional CPUs only
22.3.3 FW update for 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).
w You are familiar with the information in chapter 'Preparation and security'.
1. Select 'Update' > 'FW update additional CPUs' from the menu bar.
on 'OK'.
a The 'Connect' window opens.
3. Select the connection type:

– Select 'Local connection' to establish a connection to the connected
↑ standalone or ↑ SAFEDLINK 'Station'.
– Select 'Connection to GAP' to establish a connection via ↑ GAP to a
networked 'Station'. Enter the address of the 'Station' you want to update in
the 'Target station address' field. If you want to update the GAP 'Station'
itself, enter '0'.
4. Click on 'OK'.
a The 'FW update additional CPUs' window opens.
a The checkboxes for the CPUs that can be updated are checked in column
'Update'.
5. Select the CPUs you want to update and click on 'Start'.
a The 'Set access level' window opens.
6. Press <MENU> on the 'Station' and enter a valid PIN.
7. Click on 'OK' in the 'Set access level' window.
a The CPUs are updated.
a 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'.
a The 'Station' is restarted.
126 | 178
Update only the BDV
22
10. Press <Acknowledge> on the Person Machine Interface to switch off the
11. Click on 'Close' in the 'FW update additional CPUs' window.
See also
2 Preparation and security [➙ 113]
22.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
The procedure for updating the BDV depends on the ↑ 'Station' function. The
procedures are described in the following chapters.
See also
pages.
[➙ 113]'.
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 [➙ 128]
6. Load the converted configuration from the PC to the 'Station'. Link [➙ 30]
127 | 178
22 Converting the configuration
pages.
w Familiarize yourself with the information in 'Preparation and security [➙ 113]'.

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 [➙ 128]
4. Remove the network connection to the 'Station' and connect the PC. Link
[➙ 27]
6. Load the converted configuration from the PC to the 'Station'. Link [➙ 30]
8. Restore the network connection.
22.5 Converting the configuration

You will find detailed information on converting ↑ 'Sites' in document
Converting the configuration

w The 'Site' you want to convert is saved and loaded in Cerberus-Engineering-
Tool.
1. Select the 'Edit' > 'Convert site' menu item.
a The following window opens:
2. Select the ↑ BDV you want and click on 'Convert'.

a The 'Action confirmation' window opens.
3. Click on 'Yes'.
a The 'Site' is converted.
128 | 178
Testing the firmware version of the additional CPUs
22
22.6 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.
on 'OK'.
3. Select the connection type:

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

6. Click on 'Cancel' in the 'FW update additional CPUs' window.
129 | 178
22 Creating diagnosis report
22.7 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.
w The configuration data for the ↑ 'Station' is loaded to Cerberus-Engineering-
Tool.
1. Select 'Commissioning' > 'Diagnostics report' from the menu bar.
a The 'Reports' window opens.
2. Select the 'Diagnostics report' element in the 'Report type' field.
3. Select the page format, page orientation, file name and memory location of the
report in the 'Output settings' section.
4. Click on 'Create report'.
a The report is created and displayed.
You will find more information about creating reports and the diagnosis report in
See also
22.8 Updating the FW of the peripheral devices

You need the following tools to update the firmware of the peripheral 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'.
130 | 178
Updating the FW of the peripheral devices
22
22.8.1 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
w 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.
a 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
Figure 3: Connection of the PC to the MCL-USB adapter
Check the COM port setting under 'Options' > 'Preferences' > 'Periphery update'
before performing the firmware update.
1. Select 'Update' > 'Periphery update wizard'.

2. In the 'Password check' window, enter the password '12345678' and click on
the 'Next' button.
3. Select the FDUZ22x in the 'Devices:' field.
a The connection with the FDUZ22x is established.
a The latest firmware package and the latest firmware version are suggested.
4. Click on 'Next'.
5. Follow the instructions in the dialog and perform the update.
a The FDUZ22x restarts.
a When the device is ready for operation, the green LED on the FDUZ22x
lights up.
6. Disconnect the FDUZ22x from the PC.
a The firmware is updated.
131 | 178
22 Updating the FW of the peripheral devices
22.8.2 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
w The floor repeater terminal is fed by a 24 V external power supply or by the C-
NET detector line.
w The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
2. In the selection window, open an F-FXS7211-XX_x_x_...zip file matching the
↑ 'Site'.
3. Open the device and connect the PC via the MCL-USB adapter to the device.
FT2010
X100
USB
MC-Link
FDUZ221/FDUZ227
24 V
Figure 4: 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
132 | 178
22

the 'Next' button.
3. Select the 'Standard C-NET device' element in the 'Devices:' field.
a The connection with the floor repeater terminal is established.
4. Click on 'Next'.
a The floor repeater terminal restarts.
6. 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 3:
1. Keep the 'More alarms' (1) und '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).
a The device is set to update mode.
FT2010 Front view FT2010 printed circuit board
133 | 178
22.8.3 Floor repeater display FT2011
WARNING
The firmware must be updated individually for each ↑ floor repeater display.
Preparation
w The floor repeater display 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-FXS7211-XX_x_x...zip file that matches the
↑ 'Site'.
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
Figure 5: Connect the PC to the floor repeater display

FDUZ227
FT2011 Floor repeater display
134 | 178
22

the 'Next' button.
a The connection with the floor repeater display is established.
4. Click on 'Next'.
a The floor repeater display restarts.
6. Remove the MCL-USB adapter and lock the device.

in step 3:
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).
1
FT2011 Front view FT2011 printed circuit board
135 | 178
22.8.4 Mimic display driver FT2001-A1
WARNING
The firmware must be updated individually for each mimic display driver.
Preparation
w 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-FXS7211-XX_x_x_...zip file matching the
↑ 'Site'.
3. Connect the PC to the device via the MCL-USB adapter.
FT2001-A1
X2
USB
MC-Link
FDUZ221/FDUZ227
Figure 6: Connection of the PC to the mimic display driver

FDUZ227
FT2010 Mimic display driver
136 | 178
22

the 'Next' button.
a The connection with the mimic display driver is established.
4. Click on 'Next'.
a The mimic display driver restarts.
6. Remove the MCL-USB adapter.
137 | 178

in step 3:
1. Set the DIP switch S200-1 to 'ON'.
2. Follow the instructions in the dialog in the Engineering Tool.
3. Set the DIP switch S200-1 to 'OFF'.
4. Follow the additional instructions in the dialog in the Engineering Tool.
21
S200 ON
1 1
1
1 1
FT2001- Printed circuit board view

A1
22.8.5 Radio gateway FDCW221

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
See also
138 | 178
22
22.8.6 Line tester FDUL221

This chapter relates to the line tester FDUL221, device version with USB
connection or MC link connection, order no. A5Q00022100.
Preparation
1. Save the latest firmware file on your PC.
2. Select 'File' > 'Import new resource package' in the Engineering Tool.
3. In the selection window, open the firmware file with the corresponding
language F-FXS2007-XX_x_x_...zip.
Connection to PC via USB cable

w The line tester is fed either internally with batteries or via a mains adapter.
l Connect the device to the PC via the USB cable. You will find more information
in document 008250. See chapter 'Applicable documents'.
Connection to PC via FDUZ22x

PC.
w The line tester is fed either internally with batteries or via a mains adapter.
l Connect the device to the PC via the MCL-USB adapter. You will find more
information in document 008250. See chapter 'Applicable documents'.
DC USB
FDUL221 FDUZ221/FDUZ227
MC-Link
B
Figure 7: Connect the PC to the line tester

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.
139 | 178

the 'Next' button.
3. In the 'Devices:' field, select the 'FDUL221 C-NET line test device'.
a The connection with the line tester is established.
4. Press and hold down the '▲', '▼', and '√' buttons on the line tester and click on
the 'Next' button in the Engineering Tool at the same time.
5. Only release the '√' button.

6. Release the '▲' and '▼' buttons.
7. Follow the instructions in the dialog in the Engineering Tool and perform the
update.
a The line tester restarts.
140 | 178
22
22.8.7 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
w The line tester is supplied via a mains adapter.
w 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
Figure 8: Connect the PC to the serial line tester
FDUL22 Line tester

1
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

the 'Next' button.
3. In the 'Devices:' field, select the 'FDUL221 C-NET line test device'.
a The connection with the line tester is established.
141 | 178
4. Press and hold down the '▲', '▼', and '√' buttons on the line tester and click on
the 'Next' button in the Engineering Tool at the same time.
5. Only release the '√' button.

6. Release the '▲' and '▼' buttons.
7. Follow the instructions in the dialog in the Engineering Tool and perform the
update.
a The line tester restarts.
22.9 Updating the FW of Ethernet switch (modular)

FN2012-A1
See also
2 Commissioning Ethernet switch (modular) FN2012-A1 [➙
90]
22.9.1 Standalone FN2012-A1

'Cerberus-Engineering-Tool' assumes the function of the TFTP server from which
the FN2012-A1 obtains the firmware. The FN2012-A1 must be connected to a sub-
net containing at least one station that can provide the PC with the DHCP.
You can perform the firmware update for the FN2012-A1 in two ways:
● Updating the firmware in the web interface
or
● Updating the firmware with the RESET button on the device
The web interface is not available while the firmware update is active.
142 | 178
Updating the FW of Ethernet switch (modular) FN2012-A1
22
Updating the firmware in the web interface

the FN2012-A1.
w The FN2012-A1 is connected to a sub-net containing at least one station.
Link [➙ 93]
w Cerberus-Engineering-Tool is switched on.
w 'Cerberus-Engineering-Tool' is connected to the sub-net.
w The FN2012-A1 is not in repeater mode (rotary switch position 'E').
1. Start the firmware update in Cerberus-Engineering-Tool:
– Select the 'Update' > 'FW update main CPU' menu item.
– Select the required firmware version in the 'Update package:' field.
– Select 'Initiate update at station'.
2. Open the web interface of the FN2012-A1.
3. Select the 'FW update' tab.
4. Enter the address of 'Cerberus-Engineering-Tool'. You will find
recommendations for standard configurations in the table 'Recommended
standard IP addresses for tool' below.
5. Click on 'Start FW update'.
a The FN2012-A1 connects to 'Cerberus-Engineering-Tool'.
a The firmware of the FN2012-A1 is updated.
a The FAULT LED on the FN2012-A1 shows the status of the firmware update.
System and connection type IP address

Local connection 192.168.200.5
Connection to GAP 192.168.201.5
Table 4: Recommended standard IP addresses for tool
143 | 178
Updating the firmware with the Reset button on the device

the FN2012-A1.
w The FN2012-A1 is connected to a sub-net containing at least one station.
w Cerberus-Engineering-Tool is switched on.
w 'Cerberus-Engineering-Tool' is connected to the sub-net.
w The FN2012-A1 is not in repeater mode (rotary switch position 'E').
1. Start the firmware update in Cerberus-Engineering-Tool:
– Select the 'Update' > 'FW update main CPU'' menu item.
– Select the required firmware version in the 'Update package:' field.
– Select 'Initiate update at station'.
2. Hold down the Reset button on the FN2012-A1 for 10 seconds.
a After 5 s, the FAULT LED switches on.
a After 10 s, the FAULT LED switches off.
a The firmware of the FN2012-A1 is updated.
a The FAULT LED on the FN2012-A1 shows the status of the firmware update.
Function displays of the FAULT-LED

Function display Meaning FAULT-LED flashing pattern (every 2 sec.)
Normal Operation Normal operation t
0 125 250 375 500 625 750 875 1000 1125 1250 1375 1500 1625 1750 1875 [ms]
FW Update Mode Ready for firmware update t
0 125 250 375 500 625 750 875 1000 1125 1250 1375 1500 1625 1750 1875 [ms]
FW Update Ethernet switch is loading t

Running firmware 0 125 250 375 500 625 750 875 1000 1125 1250 1375 1500 1625 1750 1875 [ms]
FW Update Failed FW update could not be t

completed, network
0 125 250 375 500 625 750 875 1000 1125 1250 1375 1500 1625 1750 1875 [ms]
connection may be
interrupted
Checksum Failed The FW checksum is not t
correct 0 125 250 375 500 625 750 875 1000 1125 1250 1375 1500 1625 1750 1875 [ms]
Fatal FAULT Ethernet switch generates t

another fault 0 125 250 375 500 625 750 875 1000 1125 1250 1375 1500 1625 1750 1875 [ms]
Table 5: FAULT-LED flashing pattern
Function display Possible troubleshooting actions

FW Update Failed ● Ethernet switch tries to establish the connection again to load the FW.
● Restart the FW update via Cerberus-Engineering-Tool.
Checksum Failed ● Restart the FW update via Cerberus-Engineering-Tool.
Fatal FAULT ● Carry out a reset. If unsuccessful, there is a hardware fault.
● Replace Ethernet switch. Check whether other error messages are displayed
in the FS720 system.
Table 6: Troubleshooting
144 | 178
Updating the FW of Ethernet switch (modular) FN2012-A1
22
22.9.2 FN2012-A1 integrated into station

w The FN2012-A1 is connected to the station via a ribbon cable.
w The FN2012-A1 is connected to the sub-net via an Ethernet cable.
w The FN2012-A1 has been created in the hardware tree in Engineering Tool or
has been read in on the station.
w In Engineering Tool, an IP address that is valid within the sub-net has been
configured for the FN2012-A1.
w The rotary switch on the FN2012-A1 is set to '0'.
l Update the FW of the main CPU and the additional CPUs. Link [➙ 114]
Or
l Update the FW of the additional CPUs only. Link [➙ 125]
145 | 178
Maintenance
23 General
23 Maintenance
23.1 General
General rule
It is assumed that the ↑ 'Site' was commissioned in accordance with the existing
directives, i.e., all functions have been tested and the 'Site' data has been saved
and archived.
Protocol
● Measurement values must be recorded according to specifications.
● Recorded measurement values must be stored in the site 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.
23.2 Testing
FS720 offers various test functions for efficient testing of devices and logical
functions. Some test methods can be combined, others have to be carried out
individually.
The fire detection installation is in 'Test' operation mode if one of the following test
modes is activated:
● 'Detector test'
● 'Walk test'
● 'Control test'
● 'Installation test'
● Test variants
You will find more information on testing the system in document A6V10211076.
146 | 178
Maintenance
Testing and measuring instruments
23
23.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Ω
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 Adapter for detector exchanger detectors. Some detectors also require
FDUD491 the adapter for 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 Adjustment kit FDLU291 Adjustment device and black alarm test
FDL241-9 filter
Test flame detector FDF2x1-9 LE3 Test lamp
Test ↑ C-NET detector line Line tester FDUL221
23.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)
147 | 178
Maintenance
23 Test system data
23.5 Test system data

System test manual
Ensure that the system test manual is available and up to date.
Remote transmission
Check that the phone numbers and the names of the remote transmission
receivers are up to date.
Data backup for 'Site'

1. Check that the system data are saved.
a 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 current 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 the current firmware version with the latest version unless this is
necessary to correct faults or add functions.
'Event memory'
Check the content of the 'Event memory' and take the necessary measures, e.g.,
switch on elements that have been switched off temporarily.
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.
148 | 178
Maintenance
Testing the 'Station'
23
23.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 operation modes from 'Manned operation' to 'Unmanned
operation' and vice versa.
4. Switch an 'Area' off and on again.
5. Check the operation of an alarm.
6. Check the operation of a 'Fault'.
7. Block operation.
Clean the operating unit

Clean the display and the front plate with a wet cloth. Do not use any caustic
solvents.
149 | 178
Maintenance
23 Check the power supply
23.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 with local and global alarms.
2. Compare the measurement values with the calculation value for emergency
current capacity.
Checking the batteries

1. Measure the battery voltage
– Min. 23 V, asymmetry max. 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.
5. Connect a conventional battery tester 1 and follow the associated operating
instructions.
1 Suitable battery testers are, for example: Celltron SCP 6/12 or Midtronics ACT V,
recommended by Powersonic, or Fluke battery tester 500 series.
Checking for power supply faults

1. Disconnect the mains supply cable.
a The following message is displayed: 'Mains failure'.
2. Disconnect the battery supply cable.
a 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.
23.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
150 | 178
Maintenance
Calibrating lines
23
23.9 Calibrating lines
WARNING
Impermissible line configuration
An impermissible line configuration can cause the alarm devices connected to this
line to be supplied with insufficient power in the event of a fire. This prevents the
alarm from sounding in the corresponding parts of a building. This can cause
serious injuries or death.
● Make sure that all lines of a line card have a permissible line configuration by
calibrating them successfully. You will find information about the requirements
for a permissible line configuration in the 'Planning detector lines' chapter of
the document 'A6V10210362'.
Calibrate a line manually on the 'PMI' in the following cases if automatic line
calibration is deactivated in the configuration of the line:
● The line topology has been changed.
has changed.
● The PMI displays a calibration error for a line.
Calibrate all lines of a periphery board or a line card manually on the 'PMI' in the
following cases, even if automatic line calibration has been activated in the
configuration of the line:

5 minutes.
You will find more information on line calibration in chapter 'Calibrating an FDnet/C-
NET detector line [➙ 58]'.
See also
2 Calibrating an FDnet/C-NET detector line [➙ 58]
23.10 Checking 'Site' function

Test the function of the ↑ 'Site' in the various test modes.
You will find information on testing a 'Site' in the 'Testing' chapter of document
See also
151 | 178
Maintenance
23 Intervals for testing the system function
23.11 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 X
triggers a 'Fault'.
● Check the loop line function.
● During short-circuit also check the separator function.
'Fire controls' Check activation of the 'Controls' up to and with the interface. X
Check the ↑ effects of the 'Controls' owned by the customer. X
Arrange a time with the customer.
'Mains failure' Check how long it takes until the 'Emergency power operation' fault X
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.
152 | 178
Maintenance
Carrying out final maintenance work
23

(years)
1 2 5
↑ Alarm organization Check the function of the delay times t1 and t2. X
Activate a global alarm with an 'Automatic detector' in the X
'Unmanned operation' operation mode.
Activate a local and global alarm by setting a 'Manual call point' to X
the 'Manned operation' and 'Unmanned operation' operation
modes.
Check automatic switchover from 'Manned operation' to X
'Unmanned operation' on the basis of the event memory entries.
Check activation of the remote transmission equipment with X
'ALARM'.
Table 7: Intervals for the function test

(years)
1 2 5
Outputs of type: Check the ↑ effects of the outputs owned by the customer. Arrange X
● 'Actuator/valve' a time with the customer.
Outputs of type: Triggering of the outputs. You will find information on testing the X
● 'Exting. fire control' outputs in document 'A6V10211076'.
● 'External equipment'
Table 8: Intervals for the extinguishing function test
23.12 Carrying out final maintenance 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.
153 | 178
Repair
24 Disconnect the station from the power supply
24 Repair
24.1 Disconnect the 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.
WARNING
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. WARNING! It is impossible to process alarms or faults if a station is

switched off! Switch the 'Station' off by performing a reset.
a The 'Station' shuts down and is switched off for several seconds.
2. Disconnect the 'Station' before the 'Station' starts up again:
– First disconnect the negative battery terminals, then the positive terminals.
– Remove the disconnect terminal block that is mounted on a DIN rail in the
housing.
a The mains connection is interrupted.
3. Exchange the components.
4. Re-insert the disconnect terminal block.
a The mains connection is intact.
a 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'.
154 | 178
Repair
Spare parts
24
24.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
155 | 178
Repair
24 Fault messages on the Person Machine Interface
24.3 Fault messages on the Person Machine Interface
1
8
10
5 12
Figure 9: 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 Fault System 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 Fault / Off Remote Remote transmission has a ● Check remote transmission
alarm 'Fault'
10 Fault / Off Alarm 'Fault' affecting acoustic ● Check the 'Line' for open circuit/short-
device control lines circuit or end-of-line element (EOL) is
missing or defective
12 Fault / Off Control 'Fault' affecting fire control ● Check the 'Line' for open line/short-circuit
function lines ● Check the function of the external control
devices
● Check the function, any existing
feedback switch
156 | 178
Repair
Fault indicators on components
24
24.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
24.5 Communication problems in networked systems

Problem: You are unable to communicate with a ↑ 'Station' in a networked ↑ site.
This may be due to the following causes.
Date and time are not correct

l Check the date and time of the 'Station'.
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 Cerberus-Engineering-Tool.
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 using the 'Download site' function, 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.
Network cable disconnected too quickly / connection to 'Station' not

disconnected correctly
If 'Stations' are mounted close to one another, you may be able to move the
network cable from one 'Station' to the next without disconnecting the connection
correctly. If this is done, a connection cannot be immediately re-established on the
next 'Station'.
l Disconnect the connection between PC and 'Station':
– In Cerberus-Engineering-Tool , select the 'Commissioning' > 'Disconnect'
command.
– Wait at least two minutes before inserting the network cable into the next
'Station'.
157 | 178
Repair
24 Correcting swapped devices
24.6 Correcting swapped devices

When non-stationary 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:
● 'Zone', 'Serial no. ("ID-Nr.")', 'Dev.location fault'
Troubleshooting
'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.
w The device types in the corresponding bases are correct.

3. Load the configuration from the 'Station' to the PC.
158 | 178
Repair
Correcting an invalid topology
24
24.7 Correcting an invalid topology

If the topology of a C-NET detector line is invalid, the error message 'Topology is
invalid' is displayed after the ↑ detector line has been read in. The table below
shows invalid topologies.
Invalid topologies
Stub on ↑ stub or ↑ loop interrupted
Stub on stub on loop
Several stubs starting from same

location on loop
Loop on loop
Troubleshooting
1. Check the detector line with the line tester FDUL221. You will find more
information about 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
2 Read in devices on detector line [➙ 82]
24.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'.
159 | 178
Repair
24 Restart 'Station'
24.9 Restart 'Station'
WARNING
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
Via the menu on the display

1. Press <MENU>.
a The PIN input dialog is displayed.
2. Enter a valid PIN and confirm with <ok>.
a The main menu is displayed.
3. Select the 'Topology' > ↑ 'Hardware tree' > 'Station' menu items.
a The elements of the 'Station' are listed.
4. Select module 101 or module 102 'CPU (FCC2001/06)'.
6. Select the 'Reset module' command.
a The 'Station' shuts down.
a The 'Station' is switched off for several seconds.
160 | 178
Repair
Resetting a short-circuit
24
With the 'S32' button
w Switches S38-1 and S38-2 are set to the 'OFF' position on the PMI &
mainboard FCM2004.
l On the PCB of the operating unit, press and hold down the 'S32' button for
<2 s.
a The 'Station' shuts down.
a The 'Station' is switched off for several seconds.
24.10 Resetting a short-circuit

General
The operating personnel can reset a pending short-circuit error without having to
restart the entire line. A line restart generally takes longer than resetting a short-
circuit. You will find more information on restarting a detector line in chapter
'Restarting the detector line [➙ 80]'.
Resetting a short-circuit on a stub requires all line devices after the short-circuit to
be restarted and for the order of the line devices to be reentered on the stub. This
is why it is generally quicker to restart a stub than to reset the short-circuit.
When resetting a short-circuit, the system closes the open line separators before
and after the location of the preceding short-circuit, reconnecting the resulting
stubs in a loop. A prerequisite for this is that the service personnel have already
rectified the short-circuit. If the short-circuit is still present after resetting the
detector line, then the line separators of the line devices will reopen and the short-
circuit error will remain.
In the event of a short-circuit at the terminal, the line separator of the station and
the line separator of the first line device on the detector line isolates the short-
circuit.
161 | 178
Repair
24 Resetting a short-circuit
Figure 10: Resetting a short-circuit on an 'C-NET' detector line
Resetting a short-circuit on the Person Machine Interface

w A 'Short circuit' error is present on at least one 'C-NET' detector line.
w Required access level: 2.2
1. Open the path to the affected line card in the main menu on the 'PMI' display:
2. Highlight the affected line in the 'C-NET line card xx' menu.
4. In the list, select the following: 'Execute commands' > 'Reset short circuit'
a The system closes all open line separators.
Information: If the short-circuit has not been rectified, the line separators will
immediately reopen.
Information: The 'Open line' message can still be displayed for some time even
if the short-circuit has been successfully reset. The message disappears when
the system no longer detects any open detector lines after several measuring
cycles.
See also
2 Restarting the detector line [➙ 80]
162 | 178
Repair
Restoring factory setting on the 'Station'
24
24.11 Restoring factory setting on the 'Station'

There are the following ways in which to restore the factory setting on the
↑ 'Station':
● Via the menu on the display
● With the 'S32' button
Via the menu on the display

1. Press <MENU>.
a You are prompted to enter a PIN.
2. Enter a valid PIN and confirm with <ok>.
a The main menu is displayed.
3. Select the 'Topology' > 'Hardware tree' > 'Station' menu items.
5. NOTICE! Configuration will be deleted! Save the configuration data for the
'Station' before restoring the factory setting.
6. WARNING! It is impossible to acquire and process alarms or faults without a
site configuration! Select the 'Factory reset' command.
PMI & mainboard FCM2004

'Station' before restoring the factory setting.
2. Set the 'S38-1' switch to 'ON' on the rear of the operating unit.
site configuration! Press the 'S32' button for >2 s until the 'Station' restarts.

4. Set the 'S38-1' switch to 'OFF' after the restart.
163 | 178
Repair
24 Restoring factory setting on the 'Station'
PMI & mainboard FCM2027

↑ 'Station' before restoring the factory setting.
site configuration! Keep the 'S32' button on the rear of the operating unit
pressed and simultaneously press <Reset> on the ↑ Person Machine Interface
until the 'Station' restarts (>2 s).
a The Station restarts.

164 | 178
Repair
24
24.12 Fiber-optic network module FN2006 / FN2007

troubleshooting steps
Faults on a specific line can be located by referring to the LED indicators and the
table below.
The following fault scenarios are examples that relate to node1, line1 and node2,
line2. Faults on the copper side concern line1 within node1, for example.
Item Pwr RX1 Fail1 EF1 LNK1 Possible cause LNK2 EF2 Fail2 RX2 Pwr x
x
Node 1 / line 1 Node 2 / line 2
1 ON ON OFF OFF FLS Normal operation FLSH OFF OFF ON ON
HG G
2 ON OFF ON OFF OFF Optical fibers wrong way round FLSH OFF ON OFF ON
G
3a ON OFF ON OFF OFF Break in optical fiber RX1 OFF OFF OFF ON ON
3b ON ON OFF OFF OFF Break in optical fiber RX2 OFF OFF ON OFF ON
4 OFF OFF OFF OFF OFF Energy supply interrupted FLSH OFF ON 1 OFF ON
G 1
5 ON ON OFF ON 2 FLS Ground fault at A1/B1 FLSH OFF OFF ON ON

HG G
6 ON ON OFF OFF OFF A1/B1 wrong way round FLSH OFF OFF ON ON
G
7 ON ON OFF OFF OFF Break in A1 or B1 FLSH OFF OFF ON ON
G
Table 9: Searching for faults on fiber optic cable network module based on LED status
1 Depending on which module with a fully intact supply is connected, RX1 / RX2
is OFF, and Fail1 or Fail2 is ON.
2 In the event of a ground fault, LED EF1 lights up and LED EF2 flashes (to
indicate that the ground fault is being forwarded).
Legend for LED patterns

LED OFF
LED ON, in relevant color
LED flashing [FLSHG], in relevant color
165 | 178
Repair
24 Fiber-optic network module FN2006 / FN2007 troubleshooting steps
1 Normal condition
Node 1 FN2006/FN2007 FN2006/FN2007 Node 2
Line1 Link1 RX1 RX2 Link2 Line2

A1 A2
EF1 EF2
B1 B2
Fail1 Fail2
Fault example zone
Line2 Fail2 Fail1 Line1

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
A1 B1 A2 B2 A Power B B Power A B1 A1 B2 A2
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 11: Normal condition
2 Optical fibers wrong way round


A1 A2
EF1 EF2
B1 B2
Fail1 Fail2

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 12: Optical fibers wrong way round
In addition, the following light up on the affected lines: fault indicators H2 / H3 on

the FN2001 network modules.
166 | 178
Repair
24
3 Break in optical fibers


A1 A2
EF1 EF2
B1 B2
Fail1 Fail2

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 13: Break in optical fiber Rx1

A1 A2
EF1 EF2
B1 B2
Fail1 Fail2

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 14: Break in optical fiber Rx2
167 | 178
Repair
24 Fiber-optic network module FN2006 / FN2007 troubleshooting steps
4 Energy supply interrupted


A1 A2
EF1 EF2
B1 B2
Fail1 Fail2

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 15: Energy supply interrupted
In addition, the following light up on the affected FN2001 network modules: fault
indicators H2 and H3. The fault relay on the affected module responds.
5 Ground fault on line 1, A1/B1


A1 A2
EF1 EF2
B1 B2
Fail1 Fail2

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 16: FN2006_FN2007_Fehlerszenario_5_Erdschluss_B1_VP
The ground fault on line 1 (A1/B1) is mirrored on line 2 (A2/B2); in addition, EF2
flashes. The fault relay on the affected module responds.
168 | 178
Repair
24
6 Line 1, A1/B1 connection wrong way round


A1 A2
EF1 EF2
B1 B2
Fail1 Fail2

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 17: A1 and B1 have been connected the wrong way round on line 1
indicators H3 (line 1) and H2 (line 2).
7 Line 1, break in A1 or B1 connection


A1 A2
EF1 EF2
B1 B2
Fail1 Fail2

A2 A1
EF2 EF1
B2 B1
Link2 RX2 RX1 Link1
VsysA VsysA
H3 H2 H3 H2
H1 H1
FN2001 FN2001
Figure 18: Break in A1 on line 1
indicators H3 (line 1) and H2 (line 2).
169 | 178
Glossary
Glossary
Alarm device
Element in the fire detection system for acoustic and/or visual alarming, e.g. alarm sounder, beacon.
Alarm indicator
Visual display to signal an alarm or pre-alarm.
Alarm organization
Covers all measures which are used for alarming, rescue, preventing a fire from spreading, fire fighting, and
orientation in the event of a fire. Alarm organization may differ depending on the 'Manned' or 'Unmanned'
operation mode.
Area
The top level in the detection tree. Sections and zones are assigned to the area.
Assignment
Creating a reference between two elements, e.g., logical channel and physical channel.
Auto-configuration
A zone is created for each sensor channel (automatic detector and manual call point). A control is created
for each alarm sounder. IO-modules, FT2010, FT2011, and external alarm indicators are not auto-
configured.
Automatic fire detector

Device which measures a physical parameter (e.g. warmth) in order to detect a fire.
BACnet
Abbreviation for 'Building Automation and Control Networks'. It is a network protocol for standardized
communication between devices from different manufacturers in building automation, such as for
communication between a management station (MMS) and a fire detection installation.
BDV
Abbreviation for 'Base Data Variant'. Configuration files for the embedded software. A BDV contains
country-specific templates, all texts, specifications for message layout, menu definitions, specifications for
activating the LEDs on the PMI, detector parameter set settings, definitions for system-specific parts of the
tool interface, etc.
C-NET
Addressed detector line for C-NET devices.
Control tree
Structure tree with control group and control.
CPU
Abbreviation for 'Central Processing Unit'. The computing unit of the fire control panel.
Detection tree
Diagram of the geographical and organizational arrangements of sensors in a building. This is a hierarchical
structure comprising the area, section, and zone.
170 | 178
Glossary
Detector line
Electrical connection between the detectors and the fire control panel. There are collective detector lines
and addressed detector lines.
Effect
An impact caused by a control, e.g., activation of a hardware output or a command.
Ethernet station
Participants in the Ethernet sub-net without local connection for the PC.
External alarm indicator

Optical element for displaying the fire location, which is at some distance from the detector. It is normally
mounted in the room at the point where the corresponding detector is accessible.
Floor repeater display

A display device without operating elements.
Floor repeater terminal

A display device with operating elements for acknowledging and resetting alarms and faults.
GAP
Abbreviation for 'Global Access Point'. Participant in the Ethernet sub-net for the connection between the
Ethernet sub-net and a management station (BACnet client) and / or for remote access with the PC. If there
is a secondary GAP, the GAP becomes the main GAP. Can be operated as a DHCP server in the Ethernet
sub-net.
Hardware tree
Depiction of the hardware of a fire detection installation.
Line card
Card for connecting peripheral devices. The card can be a plug-in card or it can be integrated into the
periphery board.
Line separator
An electronic switch which automatically disconnects the defective part of the line in the event of a short-
circuit.
Logical channel
Depiction of a logical device function in the detection or control tree. The logical channel is always the
bottom level in the structure tree.
Loop
Detector line topology which runs from the fire control panel via the fire detectors and back to improve
operational reliability. This type of wiring allows all detectors to communicate with the control panel even in
the event of an open line or short-circuit.
Non-stationary device
Devices mounted with a base (exception: alarm sounders and radio detectors).
171 | 178
Glossary
Normal operation
The fire detection installation is supplied with mains voltage.
Parameter set
Defined detector behavior, e.g. in terms of sensitivity, resistance to deceptive phenomena, response time.
Detectors can be operated with different parameter sets.
Physical channel
Depiction of a device's physical function in the hardware tree. The physical channel is always the bottom
level in the hardware tree.
PMI
The arrangement of operating and display elements on a fire control panel or on a fire terminal. Includes the
LEDs, buttons, the display, and the operation options such as the key switch, fire brigade control and
display (FBA), and the EVAC NL Person Machine Interface.
Pre-configuration
A sub-configuration of the hardware tree, detection tree, and control tree created before commissioning the
fire detection installation.
Radio gateway
Interface converter for converting from detector line protocol to radio.
Router station
Participant in the SAFEDLINK sub-net for the connection between the SAFEDLINK sub-net and the
Ethernet sub-net (FCnet/C-WEB/LAN) via the Ethernet switch (modular) FN2012-A1.
SAFEDLINK
Physical network of an FS20 / FS720 fire detection system with the network module (SAFEDLINK) and the
network cable.
SAFEDLINK station
Participants in the SAFEDLINK sub-net with local connection for the PC.
Section
Level in detection tree of the fire detection system. The section is assigned to the area. It is used for
combining zones.
Site
Depiction of fire detection installation: The top level in the figure showing the installed system. Combines
hardware tree, detection tree, and control tree.
Soft keys
Softkeys are buttons which you can use to carry out functions and which are displayed in the three fields of
the softkey line on the display. These three black fields contain the names of the functions in white font. The
functions of the softkeys change dynamically depending on the situation and the contents of the display.
Always the most important functions are assigned to the softkeys 1 and 2.
Standalone station
Standalone station with local connection for the PC.
172 | 178
Glossary
Station
Unit for system control. Fire control panel or fire terminal.
Stationary device
Devices that are directly installed without a base, e.g. manual call points, input/output modules and alarm
sounders or radio detectors.
Stub
Detector line which is only connected to the fire control panel on one side. In the event of an open line or
short-circuit, it may no longer be possible for all fire detectors to communicate with the fire control panel.
Zone
Level in the detection tree. The zone has at least one fire detector. The decision on alarm is made at zone
level. The zone is assigned to a section or an area.
173 | 178
Index /
Index
Connecting a sub-stub to a loop
A FDnet/C-NET detector line .............................. 57
Acceptance test ............................................... 23 Connection to the station .................................. 24
Access levels Connectivity .................................................... 24
Setting the PIN ............................................... 86 Conversion.................................................... 128
Alarm counter ................................................ 113 Configuration ................................................ 128
Auto-configuration ............................................ 38 Convert stubs into loops
Definition of terms ........................................... 35 FDnet/C-NET detector line .............................. 56
Detector line ................................................... 76 CPU
Station ............................................................ 75 Updating the firmware ................................... 117
Automatic CPU (other)
Line calibration ............................................... 59 Updating the firmware ................................... 126
Customer text .................................................. 39
B
Backup ........................................................... 32
D
Date / time .................................................... 157
C
Calculation variables Deleting
Line calibration ............................................... 62 Device ............................................................ 83
Calibrating lines manually ................................. 60 Detector
Calibration modes Test mode ...................................................... 84
Line calibration ............................................... 59 Testing ........................................................... 83
Calibration report Detector inspection ........................................ 152
General .......................................................... 61 Detector line
Indicators ........................................................ 61 Auto-configuration........................................... 76
Line calibration ......................................... 61, 61 Install.............................................................. 22
CE marking Restart............................................................ 80
Extinguishing .................................................. 73 Switch off........................................................ 79
Commissioning ................................................ 34 Switching on ................................................... 79
According to wiring sequence ......................... 22 Testing ........................................................... 22
Auto-configuration........................................... 38 Detector self-test............................................ 152
Networked station ........................................... 43 Device
Overview ........................................................ 34 Remove .......................................................... 49
Standalone station with PC, with pre- Remove (base without loop contact) ............... 52
configuration .............................................. 42 Replace (base without loop contact)................ 52
Standalone station with PC, without pre- Replacing (different types) .............................. 53
configuration .............................................. 41 Replacing (stationary) ..................................... 48
Standalone station without PC ........................ 38 Swapped ...................................................... 158
With serial number .......................................... 22 Temporarily remove ........................................ 54
Without PC ..................................................... 38 Disconnect power
Communication problems................................ 157 Station .......................................................... 154
Component Download.................................................. 28, 30
Indication of faults ......................................... 157 Download center
Configuration URL ................................................................ 11
Conversion ................................................... 128
Load to station .......................................... 28, 30
Loading to PC ................................................. 32
174 | 178
Index /
E FN2009-A1 ..................................................... 98
Entries in the calibration report FN2012-A1
Line calibration................................................ 63 Integrated into station ..................................... 92
Error message Standalone ..................................................... 90
'Topology is invalid' ....................................... 159 FT2001-A1 mimic display driver
Ethernet switch Updating the firmware ................................... 136
IP address ................................................ 90, 94 FT2010 floor repeater terminal
Web interface ................................................. 93 Updating the firmware ................................... 132
Ethernet switch (MM) ....................................... 87 FT2011 floor repeater display
Event memory............................................... 113 Updating the firmware ................................... 134
Expand FUJITSU DL3750+ ........................................ 110
FDnet/C-NET detector line .............................. 47 Function test ..................................... 86, 151, 152
Site ................................................................. 44 Fuse .............................................................. 32
External printer.............................................. 110
Extinguishing G
General
CE marking ..................................................... 73
Calibration report ............................................ 61
F Line calibration ............................................... 58
Factory setting .............................................. 163
Fault indicators.............................................. 156 H
Hardware reset
FCI2007-A1 I/O card (remote transmission) ...... 109
Station .......................................................... 160
FCI2009-A1 I/O card (horn / monitored) ........... 109
FDnet/C-NET detector line
I
Connecting a sub-stub to a loop ...................... 57 I/O card (horn/monitored) FCI2009-A1 ............. 109
Convert stubs into loops.................................. 56 I/O card (remote transmission) FCI2007-A1 ...... 109
Expand ........................................................... 47 Indication of faults
Removing a device (non-stationary) ................ 54 Component ................................................... 157
Removing a device (stationary) ....................... 49 Indicators
Replacing a device with one of a different type Calibration report ............................................ 61
(non-stationary).......................................... 51
Initialize
Replacing a device with one of the same type
Station ............................................................ 28
(non-stationary).......................................... 50
Install
Replacing manual call points ........................... 55
Detector line ................................................... 22
FDUL221 line tester
IP address
Updating the firmware ................................... 139
Ethernet switch ......................................... 90, 94
FDUL221 serial line tester
Updating the firmware ................................... 141 K
FDUZ221 MCL-USB adapter Key figures
Updating the firmware ................................... 131 Line calibration ............................................... 62
Fire brigade periphery module FCI2001-D1 ...... 108
Firewall L
Safety module ................................................. 98 License .......................................................... 37
Windows 7 ...................................................... 25 Line
Windows firewall ..................................... 24, 114 Auto-configuration........................................... 76
Windows XP ................................................... 24 Restart............................................................ 80
Floor repeater display Line calibration
Updating the firmware ................................... 134 Automatic ....................................................... 59
Floor repeater terminal Calibrating lines manually ............................... 60
Updating the firmware ................................... 132 Calibration modes ........................................... 59
FN2008 A1 ..................................................... 87 Calibration report ............................................ 61
175 | 178
Index /
Displaying the calibration report ...................... 61 Power supply

Entries in the calibration report........................ 63 Configuring ..................................................... 39
Figures and calculation variables .................... 62 Testing ......................................................... 150
General .......................................................... 58 Pre-configuration
Manual ................................................... 60, 151 Definition of terms........................................... 35
Time ............................................................... 58 Preparation
Troubleshooting .............................................. 66 Station ............................................................ 74
Line tester Preparation without BDV
Updating the firmware ................................... 139 Station ............................................................ 75
Load Primary Setup Tool .......................................... 88
From PC to station .................................... 28, 30 Printer
From station to PC .......................................... 32 Testing ......................................................... 150
Load data to PC
Site ................................................................. 32 R
Radio gateway FDCW221 ............................... 138
Load data to the station
Site ................................................................. 30
Radio gateway FDCW241 ............................... 138
Localization error ............................................. 86
M Read in
Main CPU Definition of terms........................................... 35
Updating the firmware ................................... 117 Device ............................................................ 82
Maintenance.................................................. 146 Remove
Manual Device ............................................................ 49
Line calibration ....................................... 60, 151 Device (base without loop contact).................. 52
MCL-USB adapter Device (temporary) ......................................... 54
Updating the firmware ................................... 131 Removing a device (non-stationary)
Measuring instrument ..................................... 147 FDnet/C-NET detector line .............................. 54
Merge Removing a device (stationary)
Sites ............................................................... 45 FDnet/C-NET detector line .............................. 49
Mimic display driver Replace
Updating the firmware ................................... 136 Device (base without loop contact).................. 52
Device (different types) ................................... 53
N Device (stationary) .......................................... 48
Network cable
Replacing a device with one of a different type (non-
Moving.......................................................... 157 stationary)
Networked station ............................................ 43 FDnet/C-NET detector line .............................. 51
Normal operation ............................................. 85 Replacing a device with one of the same type (non-
stationary)
O FDnet/C-NET detector line .............................. 50
Original language .............................................. 9
Replacing manual call points
P FDnet/C-NET detector line .............................. 55
Password ................................ 117, 120, 126, 129 Resetting
PC FN2012-A1 ..................................................... 97
Connect to station ........................................... 27 Short-circuit .................................................. 161
Disconnecting from station .............................. 27 Restart
PMI Detector line ................................................... 80
Fault indicators ............................................. 156 FN2012-A1 ..................................................... 97
Station .......................................................... 160
176 | 178
Index /
S T
Safety module (firewall) .................................... 98 Test ........................................................ 86, 151
Scalance X204 2 ............................................. 87 Test intervals ......................................... 152, 152
Serial line tester Test mode ...................................................... 84
Updating the firmware ................................... 141 Detector.......................................................... 84
Series number................................................. 22 Exit ................................................................. 85
Set parameter set Test unit ....................................................... 147
Use Person Machine Interface ........................ 40 Testing
Setting the PIN Detector.................................................... 83, 83
for access levels ............................................. 86 Detector line ................................................... 22
Short-circuit Function ....................................................... 152
Resetting ...................................................... 161 Power supply ................................................ 150
Site Printer........................................................... 150
Expand ........................................................... 44 System data ................................................. 148
Load data to PC .............................................. 32 Time
Load data to the station................................... 30 Line calibration ............................................... 58
Merge ............................................................. 45 Time / date ................................................... 157
Test intervals ................................................ 152 Topology is invalid ......................................... 159
Source language ............................................... 9 Troubleshooting
Spare parts ................................................... 155 Line calibration ............................................... 66
Standalone station ................................ 38, 41, 42
Start U
Uninstalling
Detector line ................................................... 80
Device ............................................................ 82
Station
Update BDV ................................................. 127
Auto-configure ................................................ 75
Disconnect power ......................................... 154
Additional CPUs............................................ 126
Factory setting .............................................. 163
Main CPU and additional CPUs .................... 117
Hardware reset ............................................. 160
Peripheral devices ........................................ 130
Initialize .......................................................... 28
Station .......................................................... 113
Load data ....................................................... 28
Upload ........................................................... 32
Mount and install............................................. 23
Preparation ..................................................... 74 W
Preparation without BDV ................................. 75 Web interface
Resetting ...................................................... 163 Ethernet switch ............................................... 93
Restart .......................................................... 160 Windows 7
Switching off ................................................. 154 Firewall ........................................................... 25
Swapped Windows firewall ...................................... 24, 114
Device .......................................................... 158 Windows XP
Switch off Firewall ........................................................... 24
Detector line ................................................... 79
Switching off Z
Zone
Station .......................................................... 154
Switch off ........................................................ 79
Switching on
Switching on ................................................... 80
Detector line ................................................... 79
System data.................................................. 148
177 | 178
Issued by © Siemens Switzerland Ltd, 2008
Siemens Switzerland Ltd Technical specifications and availability subject to change without notice.
Building Technologies Division
International Headquarters
Theilerstrasse 1a
CH-6300 Zug
+41 58 724 2424
www.siemens.com/buildingtechnologies
Document ID: A6V10210416_j_en_-- FS720

Edition: 2018-08-29

fs720 PDF

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 PDF

Uploaded by

Copyright:

Available Formats

FS720

Fire detection system

A6V10210416_j_en_-- Building Technologies

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

© Siemens Switzerland Ltd, 2008

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

1 About this document

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

Target group Activity Qualification

Source language and reference document

Conventions for text marking

⊳ Requirement for a behavior instruction

Supplementary information and tips

1.1 Applicable documents

1.2 Download center

1.3 Technical terms and abbreviations

1.4 Revision history

The table below shows this document's revision history:

Version Edition date Brief description

Version Edition date Brief description

Version Edition date Brief description

Version Edition date Brief description

2.1 Safety instructions

Symbol for danger

Additional danger symbols

General danger Explosive atmosphere

Voltage/electric shock Laser light

Signal word Danger level

NOTICE 'NOTICE' identifies a possibly harmful situation or possible damage to property

How risk of injury is presented

How possible damage to property is presented

2.2 Safety regulations for the method of operation

● Specialist electrical engineering knowledge is required for installation.

Mounting, 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

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

3.2 Mount and install 'Station'

4 Connectivity and communication with 'Station'

4.1 Setting Windows firewall

Setting Windows firewall

You must have administrator rights to make the following settings.

4.1.2 Windows 7 / Windows 8 / Windows 10

w You have administrator rights on your PC.

5. Set the following values:

4.2 Network parameters

4.3 Connecting the PC to the station

Figure 1: Rear panel of operating unit and PC

LAN Ethernet connection

4.4 Disconnecting the PC from the station

4.5 Loading data to the 'Station'

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

Command Overwrites the Sets the address Overwrites the

4.6 Initializing 'Station'

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