Cerberuspro Commissioning, Maintenance & Troubleshooting - A6v10210416 (Ip6)

FS720
Fire detection system

Commissioning
Maintenance
Troubleshooting
IP6
A6V10210416_i_en_AU Building Technologies

2015-12-15 Control Products and Systems
Legal notice
Legal notice
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
Gubelstrasse 22
CH-6301 Zug
Tel. +41 41 724-2424
www.siemens.com/buildingtechnologies
Edition: 2015-12-15
Document ID: A6V10210416_i_en_AU
© Siemens Switzerland Ltd, 2008
2 | 156
Building Technologies A6V10210416_i_en_AU
Fire Safety 2015-12-15
Table of contents
1 About this document ............................................................................. 7

1.1 Applicable documents ................................................................................. 9
1.2 Download center ........................................................................................10
1.3 Technical terms and abbreviations .............................................................10
1.4 Revision history .........................................................................................11
2 Safety ............................................................................................... 14
2.1 Safety instructions .....................................................................................14
2.2 Safety regulations for the method of operation ...........................................16
2.3 Standards and directives complied with......................................................18
2.4 Release Notes ...........................................................................................18
3 Mounting / Installation ......................................................................... 19
3.1 Installing and checking the detector line .....................................................19
3.1.1 Installing devices with serial number ...........................................19
3.1.2 Installing devices according to the wiring sequence .....................19
3.1.3 Checking the detector line ...........................................................20
3.2 Mount and install 'Station' ..........................................................................20
4 Connectivity and communication with 'Station'........................................ 21
4.1 Setting Windows firewall ............................................................................21
4.1.1 Windows XP ...............................................................................21
4.1.2 Windows 7 / Windows 8 / Windows 10 ........................................22
4.2 Network parameters ..................................................................................23
4.3 Connecting the PC to the station ................................................................24
4.4 Disconnecting the PC from the station .......................................................24
4.5 Loading data to the 'Station' .......................................................................25
4.6 Initializing 'Station' .....................................................................................25
4.7 Loading configuration from the PC to the station ........................................27
4.8 Loading configuration from the station to the PC ........................................29
4.9 Creating a backup of the 'Site' configuration ...............................................29
5 Commissioning overview ..................................................................... 31
5.1 Commissioning variants .............................................................................31
5.2 Definition of terms......................................................................................32
5.3 Standard gateway ......................................................................................33
5.4 Brief instructions on operating the 'Station' .................................................34
5.5 License ......................................................................................................34
6 A - Commissioning standalone 'Station' without PC ................................ 35
6.1 Configuring the power supply .....................................................................36
6.2 Entering customer texts using the Person Machine Interface......................36
6.3 Setting detector parameter sets .................................................................37
7 B1 - Commissioning standalone 'Station' with PC,
without pre-configuration ..................................................................... 38
8 B2 - Commissioning standalone 'Station' with PC,
with pre-configuration .......................................................................... 39
3 | 156
9 C- Commissioning networked 'Stations' .................................................40
10 Adding a 'Station' to an existing 'Site'.....................................................41
11 Merging two 'Sites' ..............................................................................42
11.1 Adding 'Site' B to 'Site' A ............................................................................ 43
11.2 Connecting 'Sites' physically to one another............................................... 43
12 Changing and expanding the FDnet/C-NET detector line .........................44
12.1 Extending the detector line to include additional devices ............................ 44
12.1.1 Mount and wire new devices ....................................................... 45
12.1.2 Configure a new device............................................................... 45
12.2 Replacing stationary devices of the same type ........................................... 46
12.3 Permanently removing stationary devices .................................................. 47
12.4 Removing or replacing non-stationary devices ........................................... 48
12.4.1 Base with loop contact ................................................................ 48
12.4.2 Base without loop contact ........................................................... 51
12.4.3 Temporarily removing multiple non-stationary devices................. 53
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 ................................................... 56
12.5.2 Switching off replace mode ......................................................... 56
12.5.3 Testing 'Manual call point' ........................................................... 56
12.6 Convert two stubs into a loop ..................................................................... 57
12.7 Connecting a sub-stub to a loop................................................................. 57
13 Detailed commissioning steps ..............................................................58
13.1 Preparing 'Station' for commissioning......................................................... 58
13.2 Preparing 'Station' for commissioning –without BDV installation ................. 59
13.3 Auto-configuring 'Station' ........................................................................... 59
13.4 Auto-configuring the detector line............................................................... 60
13.5 Loading automatically created configuration to the PC ............................... 61
13.6 Adapting configuration ............................................................................... 61
13.7 Converting a standalone station to a networked station .............................. 62
13.8 Switch off................................................................................................... 63
13.8.1 Safety during switch-off ............................................................... 63
13.8.2 Switching off the detector line...................................................... 63
13.8.3 Switch off zone ........................................................................... 63
13.9 Switching on .............................................................................................. 64
13.9.1 Switch on detector line ................................................................ 64
13.9.2 Switch on zone ........................................................................... 64
13.10 Restarting the detector line ........................................................................ 64
13.11 Freezing outputs ........................................................................................ 65
13.12 Enabling frozen outputs ............................................................................. 65
13.13 Read in devices on detector line ................................................................ 66
13.14 Detaching the device ................................................................................. 66
13.15 Delete the device on Person Machine Interface ......................................... 67
13.16 Remove the elements ................................................................................ 67
4 | 156
13.17 Testing detectors .......................................................................................67
13.17.1 Activate the detector ...................................................................68
13.17.2 Testing logged test activations ....................................................68
13.18 Switching on test mode ..............................................................................68
13.19 Switch on normal operation........................................................................69
13.20 Rectify localization errors ...........................................................................70
13.21 Checking 'Site' function ..............................................................................70
13.22 Carrying out final commissioning work .......................................................70
14 Commissioning Ethernet switch (MM) FN2008-A1 .................................. 71
14.1 Install Primary Setup Tool ..........................................................................72
14.2 Assign IP address......................................................................................72
14.3 Configuring FN2008-A1 using Internet browser ..........................................73
15 Commissioning Ethernet switch (modular) FN2012-A1 ............................ 74
15.1 Standalone FN2012-A1 .............................................................................74
15.1.1 Specifying a pre-configured IP address .......................................75
15.2 FN2012-A1 integrated into station ..............................................................76
15.3 FN2012-A1 web interface ..........................................................................77
15.3.1 Commissioning a web interface ...................................................77
15.3.2 Changing the IP address .............................................................78
15.3.3 Configuring the redundancy role..................................................79
15.3.4 Activating/deactivating local ports................................................79
15.3.5 Activating fault monitoring for local ports .....................................80
15.3.6 Activating port mirroring ..............................................................80
15.4 Restarting and resetting the FN2012-A1 ....................................................81
16 Commissioning security module (firewall) FN2009-A1 ............................. 82
16.1 Installing Security Configuration Tool .........................................................83
16.2 Selecting type and entering MAC address..................................................83
16.3 Entering network settings ...........................................................................84
16.4 Creating IP service definitions ....................................................................87
16.5 Creating firewall rules ................................................................................88
17 Commissioning the fire brigade periphery module FCI2001-D1 ................ 90
18 Commissioning of I/O card (remote transmission) FCI2007-A1
and I/O card (horn/monitored) FCI2009-A1 ............................................ 91
19 Commissioning external printer ............................................................ 92
20 Updating the firmware ......................................................................... 95
20.1 Preparation and security ............................................................................95
20.2 Station: Updating the FW of the main CPU and additional CPUs ................96
20.2.1 Standalone station and SAFEDLINK station ................................96
20.2.2 Router station and Ethernet station .............................................97
20.2.3 Updating several 'Stations' simultaneously ..................................98
20.2.4 FW update for main CPU and additional CPUs............................99
20.3 Station: Updating the FW of the additional CPUs only ..............................107
20.3.1 Standalone station and SAFEDLINK station ..............................107
20.3.2 Router station and Ethernet station ...........................................107
20.3.3 FW update for additional CPUs .................................................108
5 | 156
20.4 Update only the BDV ............................................................................... 109
20.4.1 Standalone station and SAFEDLINK station .............................. 109
20.4.2 Router station and Ethernet station ........................................... 110
20.5 Converting the configuration .................................................................... 110
20.6 Testing the firmware version of the additional CPUs................................. 111
20.7 Creating diagnosis report ......................................................................... 112
20.8 Updating the FW of the peripheral devices ............................................... 112
20.8.1 MCL-USB adapter FDUZ22x..................................................... 113
20.8.2 Floor repeater terminal FT2010 ................................................. 114
20.8.3 Floor repeater display FT2011 .................................................. 116
20.8.4 Mimic display driver FT2001-A1 ................................................ 118
20.8.5 Radio gateway FDCW221 ......................................................... 120
20.8.6 Line tester FDUL221 ................................................................. 121
20.8.7 Line tester with serial interface FDUL221 .................................. 123
20.9 Updating the FW of Ethernet switch (modular) FN2012-A1 ...................... 125
20.9.1 Standalone FN2012-A1............................................................. 125
20.9.2 FN2012-A1 integrated into station ............................................. 127
21 Maintenance..................................................................................... 128
21.1 General ................................................................................................... 128
21.2 Testing .................................................................................................... 128
21.3 Testing and measuring instruments ......................................................... 129
21.4 Preparatory work ..................................................................................... 129
21.5 Test system data ..................................................................................... 130
21.6 Testing the 'Station' ................................................................................. 131
21.7 Check the power supply...........................................................................132
21.8 Testing the printer.................................................................................... 133
21.9 Checking 'Site' function ............................................................................ 133
21.10 Intervals for testing the system function ................................................... 133
21.11 Carrying out final maintenance work ........................................................ 134
22 Repair ............................................................................................. 135
22.1 Disconnect the station from the power supply .......................................... 135
22.2 Spare parts.............................................................................................. 136
22.3 Fault messages on the Person Machine Interface .................................... 137
22.4 Fault indicators on components ............................................................... 138
22.5 Communication problems in networked systems ...................................... 138
22.6 Correcting swapped devices .................................................................... 139
22.7 Correcting an invalid topology .................................................................. 140
22.8 Error message 'Too many devices' .......................................................... 141
22.9 Restart 'Station' ....................................................................................... 141
22.10 Restoring factory setting on the 'Station' .................................................. 142
22.11 Fiber-optic network module FN2006 / FN2007 troubleshooting steps ....... 144
Glossary ................................................................................................... 149
Index ....................................................................................................... 151
6 | 156
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 IP6.
Target groups
The information in this document is intended for the following target groups:
Target group Activity Qualification

Installation personnel ● Assembles and installs the ● Has received specialist training in the
product components at the area of building installation technology
place of installation. or electrical installations.
● Carries out a function check
following installation.
Commissioning personnel ● Configure the product at the ● Has obtained suitable specialist training
place of installation according to for the function and for the products.
customer-specific requirements. ● Has attended the training courses for
● Check the product operability commissioning personnel.
and release the product for use
by the operator.
● Searches for and corrects
malfunctions.
Maintenance personnel ● Carries out all maintenance ● Has obtained suitable specialist training
work. for the function and for the products.
● Checks that the products are in
perfect working order.
● 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.
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_--_--
7 | 156
About this document
1 Applicable documents
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.
8 | 156
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
Technisches FDCW241 radio gateway, technical manual
Handbuch Funk-
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
Technisches FDUL221 Line Tester, Operation
Handbuch
Linientestgerät
FDUL221
008860 FT201x Floor Repeater Terminal / Floor Repeater
Display, Mounting
Montage MCL-USB- FDUZ221 MCL-USB adapter, Mounting
Adapter FDUZ221
Installation MCL-USB FDUZ227 MCL-USB Adapter (Radio), Mounting
Adapter (Funk)
FDUZ227
9 | 156
About this document
1 Download center
1.2 Download center

You can download various types of documents, such as data sheets, installation
instructions, and license texts via the following Internet address:
http://siemens.com/bt/download
κ Enter the document ID in the 'Find by keyword' input box.
You will also find information about search variants and links to mobile
applications (apps) for various systems on the home page.
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
1 Applicable documents [➙ 9]
10 | 156
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

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
11 | 156
About this document
1 Revision history

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 2013-01 Chapter 'Setting Windows firewall' updated for Windows 7
e 2012-05 Edition for IP4
New: Revised:
Updating the firmware of the main Creating diagnosis report
CPU and additional CPUs in a single Restart the station
step
Checking 'Site' function
Addition to chapter 'Setting Windows
Restoring factory settings
firewall', for Windows 7
Checking the detector line
Updating several 'Stations'
simultaneously
Update the firmware of the additional
CPUs via GAP
Creating a backup of the 'Site'
configuration
Replacing C-NET device: 20 s wait
time instead of 40 s
Updating the firmware of the
peripheral devices: Resetting the line
card no longer necessary
Updating the FDCW241
FDCW221 removed
Commissioning of I/O card (remote
transmission) FCI2007-A1 and I/O
card (horn/monitored) FCI2009-A1
d 2010-07 Edition for MP3.0 XS:
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
12 | 156
About this document
Revision history
1

c 2009-08 Modifications for MP1XS
b 2009-05 Modifications for MP1XS
a 2008-11 First edition
13 | 156
Safety
2 Safety instructions
2 Safety
2.1 Safety instructions

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

This is the symbol for danger. It warns of risks of injury.
Follow all measures identified by this symbol to avoid injury or death.
Additional danger symbols

These symbols indicate general dangers, the type of danger or possible
consequences, measures and prohibitions, examples of which are shown in the
following table:
General danger Explosive atmosphere
Voltage/electric shock Laser light
Battery Heat
Signal word
The signal word classifies the danger as defined in the following table:
Signal word Danger level

DANGER DANGER identifies a dangerous situation, which will result directly in death or
serious injury if you do not avoid this situation.
WARNING WARNING identifies a dangerous situation, which may result in death or serious
injury if you do not avoid this situation.
CAUTION CAUTION identifies a dangerous situation, which could result in slight to
moderately serious injury if you do not avoid this situation.
NOTICE NOTICE identifies possible damage to property that may result from non-
observance.
14 | 156
Safety
Safety instructions
2
How risk of injury is presented

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

Information about possible damage to property is shown as follows:
NOTICE
Nature and origin of the danger
Consequences if the danger occurs
● Measures / prohibitions for danger avoidance
15 | 156
Safety
2 Safety regulations for the method of operation
2.2 Safety regulations for the method of operation

National standards, regulations and legislation
Siemens products are developed and produced in compliance with the relevant
European and international safety standards. Should additional national or local
safety standards or legislation concerning the planning, 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 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.
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.
16 | 156
Safety
Safety regulations for the method of operation
2
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.
Modules and spare parts

● Components and spare parts must comply with the technical specifications
defined by Siemens. Only use products specified or recommended by
Siemens.
● Only use fuses with the specified fuse characteristics.
● Wrong battery types and improper battery changing lead to a risk of explosion.
Only use the same battery type or an equivalent battery type recommended by
Siemens.
● Batteries must be disposed of in an environmentally friendly manner. Observe
national guidelines and regulations.
Disregard of the safety regulations
Before they are delivered, Siemens products are tested to ensure they function
correctly when used properly. Siemens disclaims all liability for damage or injuries
caused by the incorrect application of the instructions or the disregard of danger
warnings contained in the documentation. This applies in particular to the following
damage:
● Personal injuries or damage to property caused by improper use and incorrect
application
● Personal injuries or damage to property caused by disregarding safety
instructions in the documentation or on the product
● Personal injury or damage to property caused by poor maintenance or lack of
maintenance
17 | 156
Safety
2 Standards and directives complied with
2.3 Standards and directives complied with

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

Limitations to the configuration or use of devices in a fire detection installation with
a particular firmware version are possible.
WARNING
Limited or non-existent fire detection
Personal injury and damage to property in the event of a fire.
● Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
● Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.
NOTICE
Incorrect planning and/or configuration
Important standards and specifications are not satisfied.
Fire detection installation is not accepted for commissioning.
Additional expense resulting from necessary new planning and/or configuration.
● Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
● Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.
18 | 156
Mounting / Installation
Installing and checking the detector line
3
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.
19 | 156
Mounting / Installation
3 Mount and install 'Station'
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
ϖ 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:
κ Read in the devices from both sides of the ↑ loop. To do this, change over the
↑ detector line cables as follows:
– Connect the feed line of the detector line to connection socket B.
– Connect the return line of the detector line to connection socket A.
 The devices are read in from the other side of the loop. This allows the devices
which previously couldn't be read in to be displayed.
3.2 Mount and install 'Station'

1. Mount and install the 'Station' according to the information in document
2. Insert the cables for the ↑ detector lines and the mains supply into the housing
but do not yet connect the 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
20 | 156
Connectivity and communication with 'Station'
Setting Windows firewall
4
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
ϖ 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.
21 | 156
4 Setting Windows firewall
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.
ϖ You have administrator rights on your PC.

ϖ 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'
 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.
 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 '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.
22 | 156
Network parameters
4
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'.
 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
23 | 156
4 Connecting the PC to the station
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 Cable, type CAT 5 or CAT 7, crossover, max. 100 m
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 'Cerberus-Engineering-Tool' > 'Commissioning' in Disconnect.
2. Disconnect the cable connection between PC and 'Station'.
3. Wait ≥2 min. before you establish a connection to another 'Station'.
24 | 156
Loading data to the 'Station'
4
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
1 Loading configuration from the PC to the station [➙ 27]
1 Initializing 'Station' [➙ 25]
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.
25 | 156
4 Initializing 'Station'
Initialize 'Station'
NOTICE
Connection module (card cage) FCA2006-A1 defective or installed incorrectly
Control panels identified incorrectly, e.g. FC726 identified as FC724.
● Check that the connection module (card cage) FCA2006-A1 is installed
correctly.
NOTICE
Faulty initialization for networked station
During initialization, the station must not be connected to the network or any other
station.
ϖ The PC is connected locally to the ↑ 'Station'.

1. Highlight the 'Station' you want to initialize.
2. Select the 'Commissioning' > 'Initialize station' menu item.
 The following window is opened:
3. Click on 'Start'.
 The 'Set the station to access level 3.2' window opens.
4. Press <MENU> on the 'Station' and enter a valid PIN.
5. Click on 'OK' in the 'Set access level' window.
 The 'Station' is initialized.
 The 'Station' is restarted.
 After a few minutes, the 'Buzzer' sounds twice.
6. Press <Acknowledge> on the ↑ Person Machine Interface to switch off the
'Buzzer'. Do not perform any more actions on the 'Station' until the 'Buzzer' has
sounded for the second time.
See also
1 Loading data to the 'Station' [➙ 25]
26 | 156
Loading configuration from the PC to the station
4
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.
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 [➙ 65] before switching off the
station or restarting the station/detector line.
27 | 156
4 Loading configuration from the PC to the station
ϖ The ↑ 'Site' is opened in Cerberus-Engineering-Tool.

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

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

 The 'Stations' are listed in the 'Download site' window.
3. Select the 'Stations' whose configuration you would like to load from Cerberus-
Engineering-Tool to the 'Stations' and click on 'Start'.
 The 'Set access level' window may open in Cerberus-Engineering-Tool with
the 'Set the station to access level 3.2' 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.
 The 'Action confirmation' window opens in Cerberus-Engineering-Tool.
5. Click on 'Yes'.
 The configuration is loaded to the 'Station'.
 The progress is displayed in the 'Download site' window in Cerberus-
Engineering-Tool.
 The 'Station' restarts.
 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
1 Loading data to the 'Station' [➙ 25]
28 | 156
Loading configuration from the station to the PC
4
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.
ϖ The 'Site' is opened in Cerberus-Engineering-Tool.
ϖ The PC is connected to the 'Station'.
ϖ 'Station' and Cerberus-Engineering-Tool have the same 'Site' ID.
ϖ 'Station' and Cerberus-Engineering-Tool are part of the same sales channel.
1. Select 'Commissioning' > 'Upload site'.
 The 'Upload site' and 'Connect' windows are opened.

 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'.
 The 'Action confirmation' window opens.
4. Click on 'Yes'.
 The configuration is loaded to the PC.
 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.
29 | 156
4 Creating a backup of the 'Site' configuration
Creating a backup
ϖ The ↑ 'Site' is opened in Cerberus-Engineering-Tool.
ϖ The PC is connected to a ↑ 'Station'.
1. Select 'Commissioning' > 'Create backup embedded configuration'.
 The 'Create backup embedded configuration' And 'Connect' windows are
opened.

 The 'Site' configuration is loaded to the PC and saved as a backup file.
 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'.
30 | 156
Commissioning overview
Commissioning variants
5
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

In order to satisfy Ordinance No. 305/2011 (the Construction Products Regulation –
CPR), the firmware of a newly installed fire detection installation must be current
market package version IP6 or higher.
NOTICE
Firmware version of a newly installed fire detection installation not updated
No CPR conformity
● Compare the firmware version of a newly installed fire detection installation
with the firmware version IP6.
● Update the firmware if necessary.
The table below provides an overview of the procedure for commissioning the
'Stations'. The letters A, B1, B2 and C refer to the detailed descriptions in the
following chapters.
Standalone control panel Networked 'Stations'

Without No pre- A Not possible.
Cerberus- configuration ● Auto-configuration
Engineering- possible
● Adaptations on the ↑ Person Machine
Tool
Interface
With Without pre- B1 C
Cerberus- configuration ● Auto-configuration ● Initialize the 'Stations' for
Engineering- networking
● Adaptations in Cerberus-Engineering-
Tool
Tool ● Read in the C-NET devices by line
With pre- B2 ● Assign the logical elements to
configuration ● Read in the FDnet devices by line Cerberus-Engineering-Tool
● Assign the logical elements to

Cerberus-Engineering-Tool
Table 1: Commissioning variants
31 | 156
5 Definition of terms
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
32 | 156
Standard gateway
5
↑ Non-stationary devices Point detectors installed on a base apart from radio detectors.
↑ Stationary devices All devices apart from point detectors, e.g.:
● Manual call point
● Radio detector
● Input/output modules
● Alarm sounder
● ↑ Line separator
● ↑ Radio gateway
● ↑ Floor repeater terminal
● ↑ Floor repeater display
● Mimic display driver
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
33 | 156
5 Brief instructions on operating the 'Station'
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.
34 | 156
A - Commissioning standalone 'Station' without PC
License
6
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 [➙ 36]
2. Prepare the ↑ 'Station' for commissioning. Link [➙ 58]
3. Perform auto-configuration:
– Auto-configure 'Station'. Link [➙ 59]
OR
– Auto-configure detector lines individually. Link [➙ 60]
4. Adapt the auto-configuration in the ↑ Person Machine Interface, e.g.:
– Changing customer texts. Link [➙ 36]
– Set the ↑ parameter sets of the C-NET devices. Link [➙ 37]
5. Test the function of the ↑ 'Site' and remedy the problems, if any. Link [➙ 70]
6. Perform the completion tasks. Link [➙ 70]
35 | 156
6 Configuring the power supply
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 periphery board Connect with

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 '#CONV' X1 / pin 4 #COMMON
X1 / pin 3 '#MAINS' X1 / pin 4 #COMMON
Table 2: Configuring the power supply
You will find the pin assignments in document A6V10210368. See chapter
'Applicable documents'.
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 'Detector' appears if no
customer text is assigned to the 'Zone'. The customer text of the next
superordinate element ('Zone' > 'Detector' > 'Zone' > 'Section') appears if no
customer text is assigned to the 'Area' either.
36 | 156
Setting detector parameter sets
6
6.3 Setting detector parameter sets

1. Select 'Topology' > ↑ 'Detection tree' > 'Area' > ↑ 'Section' > 'Zone' > 'Detect.'
in the main menu.
2. Press the 'MoreOptions' softkey.
3. Select 'Execute commands'.
4. Select the corresponding command:
– 'Select PS MANNED'
– 'Select PS UNMANNED'
– 'Select PS'
5. Select the desired ↑ parameter set.
 The following message is displayed: 'Command executed'
37 | 156
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 [➙ 58]
2. Perform auto-configuration:
– Auto-configure 'Station'. Link [➙ 59]
OR
– Auto-configure detector lines individually. Link [➙ 60]
3. Connect the PC to the 'Station'. Link [➙ 24]
4. Load the automatically created configuration to the PC. Link [➙ 61]
5. Adapt the configuration in Cerberus-Engineering-Tool. Link [➙ 61]
6. Load the configuration from the PC to the 'Station'. Link [➙ 27]
7. Test the function of the ↑ 'Site'. Link [➙ 70]
8. Remedy any errors you notice and load the corrected configuration from the
PC to the 'Station'. Link [➙ 27]
9. Disconnect the PC from the 'Station'. Link [➙ 24]
38 | 156
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 up to
'Zone' level.
2. Prepare the ↑ 'Station' for commissioning – without ↑ BDV installation. Link
[➙ 59]
5. Read-in the C-NET devices. Link [➙ 66]
6. Load the configuration from the 'Station' to the PC. Link [➙ 29]
9. Test the function of the 'Site'. Link [➙ 70]
39 | 156
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
[➙ 62]'.
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 [➙ 59]
3. Connect the PC to each 'Station' individually. Link [➙ 24]
4. Initialize each 'Station' individually. Link [➙ 25]
5. Read-in the C-NET devices for all 'Stations'. Link [➙ 66]
40 | 156
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 [➙ 59]
4. Initialize the 'Station'. Link [➙ 25]
41 | 156
Merging two 'Sites'
11 Setting detector parameter sets
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 [➙ 62]'.
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 [➙ 43]
2. Initialize all ↑ 'Stations' that have a new address. Link [➙ 25]
3. Load the configuration of all 'Stations' in 'Site' A from the PC to the 'Station'.
Link [➙ 27]
4. Connect the 'Sites' physically to one another. Link [➙ 43]
5. Load the configuration of the merged 'Site' from the 'Station' to the PC. Link
[➙ 29]
42 | 156
Merging two 'Sites'
Adding 'Site' B to 'Site' A
11
11.1 Adding 'Site' B to 'Site' A

ϖ ↑ 'Site' A is open in Cerberus-Engineering-Tool.
1. Select 'Edit' > 'Merge sites'.
 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'.
 The conditions for merging are checked.
 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.
 Cerberus-Engineering-Tool checks whether there are address conflicts at
'Stations' levels and suggests a possible new address.
 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'.
 The 'Sites' are merged.
 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
43 | 156
Changing and expanding the FDnet/C-NET detector line
12 Extending the detector line to include additional devices
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 [➙ 63]

2. Mount and wire the new devices. Link [➙ 45]
4. Connect the PC to the ↑ 'Station'. Link [➙ 24]
6. Configure the new devices. Link [➙ 45]
44 | 156
Extending the detector line to include additional devices
12
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.
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'.
45 | 156
12 Replacing stationary devices of the same type
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 [➙ 70]
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
46 | 156
Permanently removing stationary devices
12
12.3 Permanently removing stationary devices
pages.

2. Remove the C-NET devices. Link [➙ 66]
5. Remove the physical representation of the devices and the logical elements in
Cerberus-Engineering-Tool. Link [➙ 67]
6. Switch the C-NET detector line on. Link [➙ 64]
You can also delete the physical representation of the C-NET devices individually
via the control panel's ↑ Person Machine Interface. Link [➙ 67]
47 | 156
12 Removing or replacing non-stationary devices
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.

 The control panel detects that the C-NET device is missing and reports a
'Fault'.
2. Perform the necessary activities.
3. Re-insert the C-NET device in the C-NET in the same, previous position.
4. Acknowledge the 'Fault'.
 If this 'Fault' is no longer displayed, the control panel updates the settings of
the re-inserted C-NET device.
 If this 'Fault' is still displayed, and / or the ↑ detector line is not in normal
operation, the detector line has to be restarted.
See also
1 Restarting the detector line [➙ 64]
48 | 156
Removing or replacing non-stationary devices
12
12.4.1.2 Replacing non-stationary devices of the same type
pages.
1. Switch the test mode on. Link [➙ 68]

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.
 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 [➙ 69]
49 | 156
12.4.1.3 Replacing non-stationary devices of different types
pages.
1. Remove the C-NET device from its base.

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

 The 'Station' detects that the device is missing and reports a 'Fault'.
3. Delete the C-NET device individually on the Person Machine Interface on the
control panel. Link [➙ 67]
4. Insert the new C-NET device in the base.
8. Replace the C-NET device in the 'Zone'. Link [➙ 52]
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
52 | 156
12
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 [➙ 63]

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 [➙ 64]
 For all the re-inserted C-NET devices, a localization fault is displayed.
6. Restart the C-NET detector line. Link [➙ 64]
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'
53 | 156
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 [➙ 66]
4. Delete the C-NET devices individually via the Person Machine Interface on the
control panel. Link [➙ 67]
7. Remove the logical elements in Cerberus-Engineering-Tool. Link [➙ 67]
54 | 156
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 [➙ 56]

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]
5. Switch ↑ normal operation on. Link [➙ 69]
You will find more information about installing and uninstalling in the
documentation for the corresponding 'Manual call point'.
55 | 156
12 Replacing 'Manual call point' of the same type
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.
 The following message is shown following successful switching on: 'Command
executed'.
 The yellow 'ISOLATION' LED lights up.
 The ↑ detector line is de-energized.
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.
 The following message is shown following successful switching off: 'Command
executed'.
 The yellow 'ISOLATION' LED goes out.
 The yellow 'DETECTOR TEST' LED lights up.
 The 'Manual call point' is in test mode.
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.
56 | 156
Convert two stubs into a loop
12
12.6 Convert two stubs into a loop
pages.
ϖ The two ↑ stubs are assigned to the same line pair, e.g., 'Line' 11 and 'Line' 12.
1. Switch both the C-NET detector lines off. Link [➙ 63]
2. Wire both stubs to a ↑ loop. You will find more information about this in
3. Read-in the C-NET devices. Link [➙ 66] Start with the first 'Line' (in the
example 'Line' 11).
 The second 'Line' is adopted and the loop is formed (in this example,
'Line' 1).
See also
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 | 156
Detailed commissioning steps
13 Preparing 'Station' for commissioning
13 Detailed commissioning steps

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

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

↑ 'Station'.
58 | 156
Preparing 'Station' for commissioning –without BDV installation
13
13.2 Preparing 'Station' for commissioning –without BDV

installation
1. Connect the cables for the ↑ detector lines and the peripheral devices.
2. Connect the power supply (mains and batteries).
 The ↑ 'Station' starts and reads in the internal hardware.
 During start-up, the 'FAULT' LED flashes and the display shows the
progress.
 During start-up, the firmware version F-FXS7211 is displayed.
3. Wait until the display indicates the selection of the ↑ BDV.
 The 'Station' is prepared for commissioning.
It is not necessary to install the BDV for the further procedure. This saves having
to restart the ↑ 'Station'.
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'
13.3 Auto-configuring 'Station'

1. Select 'Topology' > 'Hardware tree' > ↑ 'Station' in the main menu.
3. Select the 'Auto-configure station' command.
 The 'Station' is auto-configured.
 The following message is shown following successful ↑ auto-configuration:
'Command executed'
See also
59 | 156
13 Auto-configuring the detector line
13.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'.
2. Press the 'MoreOptions' softkey and select 'Execute commands'.
3. Select the 'Auto-configure line' command.
 The C-NET detector line is auto-configured.
 The following message is shown following successful ↑ auto-configuration:
'Command executed'
See also
60 | 156
Loading automatically created configuration to the PC
13
13.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.

 The 'Create new site' window opens.
2. Select the 'Upload from station(s)' option field.
3. Click on 'Next'.
 The 'Create site by uploading from station(s)' and 'Connect' windows are
opened.
4. In the 'Connect' window, select 'Local connection' and then click on 'OK'.
 The configuration is loaded to 'Cerberus-Engineering-Tool'.
 The progress is displayed in the 'Create site by uploading from station(s)'
window.
 The 'Site properties' window is opened after loading.
5. Change the entries if required and click on 'OK'.
 The 'New site confirmation' window opens.
6. Click on 'Yes'.
 The 'Site' is opened in Cerberus-Engineering-Tool.
13.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 allocation of 'Zones' and 'Sections'
● Configuring controls
● Configuring the operating and display units
● Configuring the network
You will find information on configuring an ↑ 'Site' in document A6V10210424.

See chapter 'Applicable documents'.
See also
61 | 156
13 Converting a standalone station to a networked station
13.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.
ϖ The configuration for an ↑ 'Site' with a standalone 'Station' is loaded to

Cerberus-Engineering-Tool.
1. Select the 'Network' task card.
2. Open 'Global system configuration' > 'FS720 network configuration' > 'Ethernet
sub-net' in the tree view.
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'.
 The 'Assign dialog' window opens.
5. Select the 'Network tree' on the right of the 'Station' and click on 'Assign'.
 The standalone 'Station' is now a networked 'Station'.
6. Select the 'Station' under 'Connections'.
7. Configure the IP address on the 'Overview' tab.
 You have converted the standalone 'Station' to a networked 'Station'.
62 | 156
Switch off
13
13.8 Switch off
13.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.
13.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.
 The detector line is switched off.
13.8.3 Switch off zone

1. Select 'Topology' > ↑ 'Detection tree' > 'Area' > ↑ 'Section' > 'Zone' in the main
menu.
3. WARNING! System parts that have been switched off make it impossible to
acquire and process alarms or faults! Select the 'Off' command.
 The 'Zone' is switched off.
63 | 156
13 Switching on
13.9 Switching on
13.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.
 The detector line is switched on.
13.9.2 Switch on zone

1. Select 'Topology' > ↑ 'Detection tree' > 'Area' > ↑ 'Section' > 'Zone' in the main
menu.
3. Select the 'On' command.
 The 'Zone' is switched on.
13.10 Restarting the detector line
WARNING
1. Select 'Main menu' > 'Topology' > 'Hardware tree' > ↑ 'Station' > 'Module' (line
card) > 'Line'.
3. Select the 'Restart line' command.
 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'
64 | 156
Freezing outputs
13
13.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 [➙ 65]' for how
to manually deactivate freezing.
ϖ All line devices are switched on.

ϖ Input/output modules with connected fire dampers are present on the line.
ϖ The output freeze is activated / configured in the ↑ 'Site' configuration. See
document A6V10210424.
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.
 You can now restart the 'Station' or the line or perform a module reset.
13.12 Enabling frozen outputs

ϖ One or more outputs have been frozen / the 'Output positions frozen' message
is displayed for one or more outputs.
ϖ 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'.
 Freezing of the outputs is deactivated.
65 | 156
13 Read in devices on detector line
13.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 startup,
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' / '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).
ϖ For ↑ loop with line separator: The second 'Line' is switched off. Link [➙ 63]
1. In the main menu, select 'Topology' > 'Hardware tree' > ↑ 'Station' > ↑ Line
card > ↑ Detector line.
3. Select the 'Read in installed devices' command.
 The C-NET devices are read in.
 The following message is shown following successful reading in:
'Command executed'
13.14 Detaching the device

If you want to permanently remove a device, uninstall the device and, if required,
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.
66 | 156
Delete the device on Person Machine Interface
13
13.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.
 The logical channel is displayed. For some devices, 'Device' is displayed
directly.
5. Select the 'Jump to link' menu item.
 The physical channel is displayed.
6. Press the 'Upper level' softkey.
 'Device' is displayed.
8. Select the 'Execute commands' menu item.
9. Select the 'Remove/delete device' command.
 The control panel deletes the physical representation of the removed device.
 The logical channel element remains in the 'Zone'.
13.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
13.17 Testing detectors

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

1. Switch the test mode on. Link [➙ 68]
2. Initiate the detector. Link [➙ 68]
3. Switch normal operation on. Link [➙ 69]
4. Test the logged test activations. Link [➙ 68]
67 | 156
13 Switching on test mode
13.17.1 Activate the detector

ϖ DETECTOR TEST is switched on.
1. Activate all automatic 'Detectors' and 'Manual call points' using the
corresponding tools.
2. Write down the sequence of the test activations.
 The ↑ alarm indicator for the activated detector flashes at each test activation.
 If an ↑ external alarm indicator is connected and correspondingly configured,
the external alarm indicator also lights up.
You will find information about triggering detectors in document A6V10212047.
See also
13.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.
13.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.
 The yellow 'DETECTOR TEST' LED lights up.
 The element is in test mode.
Element Command
Area ● 'Non-MCP zones det.test'
● 'MCP zones det.test'
↑ Section ● 'Non-MCP zones det.test'
● 'MCP zones det.test'
Zone ● 'Detector test'
68 | 156
Switch on normal operation
13
13.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.
 The element is switched to normal operation.
 The yellow 'DETECTOR TEST' LED goes out.
Element Command
Area ● 'Non-MCP zones det.test END'
● 'MCP zones det.test END'
↑ Section ● 'Non-MCP zones det.test END'
● 'MCP zones det.test END'
Zone ● 'Detector test END'
Commands under 'Execute commands'
You can also switch to ↑ normal operation at superordinate level for the
command in question. Test mode can also be exited in the 'Zone', 'Section' or
'Area', for example.
Switching 'Zone' to ↑ normal operation

There is a shortened procedure for switching individual 'Zones' to normal operation:
1. Select 'Message summary' > 'Test message' in the main menu.
2. Select the displayed 'Zone' in test mode and press the 'Execute Commands'
softkey.
3. Select the 'Detector test END' command.
 The 'Zone' is switched to normal operation.
 The yellow 'DETECTOR TEST' LED goes out.
69 | 156
13 Rectify localization errors
13.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.
 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.
13.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
13.22 Carrying out final commissioning work

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.
3. Set the PIN for access levels 1, 2, 3,1, and 3,2.
– To do this, select 'Settings/administration' > 'Manage PINs' in the main
menu.
4. Fit the housing cover.
5. 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.
70 | 156
Commissioning Ethernet switch (MM) FN2008-A1
Carrying out final commissioning work
14
14 Commissioning Ethernet switch (MM)

FN2008-A1
This description focuses on correctly integrating the 'Ethernet switch (MM)
FN2008-A1' in the fire detection installation. More information about the product
can be found on the data carrier in the scope of supply and at the following
address: http://support.automation.siemens.com (Manufacturer designation:
Scalance X204-2)
NOTICE
Alternate products for 'Ethernet switch (MM) FN2008-A1'
No compliance with EN 54
● For an EN-54-compliant fire detection installation, you must use the permitted
'Ethernet switch (MM) FN2008-A1'.
The 'Ethernet switch (MM) FN2008-A1' is a class A equipment and may cause
radio interference in residential areas. If interference does occur, observe the
relevant information in document A6V10210390. See chapter 'Applicable
documents'.
Commissioning
1. Install the 'Primary Setup Tool' software. Link [➙ 72]
2. Assign the IP address. Link [➙ 72]
3. Configure the FN2008-A1 using the Internet browser. Link [➙ 73]
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
71 | 156
14 Install Primary Setup Tool
14.1 Install Primary Setup Tool
The 'Primary Setup Tool' software is included in the scope of supply for the
FN2008-A1.
κ Start 'Primary Setup Tool' installation.

 Primary Setup Tool is installed.
 The DLC and PROFINET RT protocols are installed.
 Primary Setup Tool recognizes one or more connected FN2008-A1 without IP
address via the DLC protocol.
The FN2008-A1 is displayed as X204-2 in Primary Setup Tool.
14.2 Assign IP address
The FN2008-A1 is displayed as X204-2 in Primary Setup Tool.
ϖ Primary Setup Tool is installed on the PC.

ϖ Several FN2008-A1 are physically linked in the system.
1. Connect the PC to any available FN2008-A1 port P1…P4 using a network
cable.
2. Start the Primary Setup Tool via 'Start' > 'Programs' > 'Simatic'.
 Primary Setup Tool lists one or more FN2008-A1 (X204-2).
3. Select each FN2008-A1 one after the other and issue a unique IP address
(192.168.1.xxx) to each FN2008-A1.
4. Click on the connected FN2008-A1 in the tree view and select the 'Load' menu
item.
 The assigned IP address is saved to the FN2008-A1.
5. Repeat the 'Load' process for each FN2008-A1.
 Each FN2008-A1 in the system has an individual IP address.
72 | 156
Configuring FN2008-A1 using Internet browser
14
14.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.
1. Open the Internet browser and enter the FN2008-A1's IP address in the
address field.
 The login window opens.
2. Login:
– User name = 'admin'
– Password = 'admin'
3. Select 'System' > 'Passwords' in the tree view and set a new password for the
following fields:
– 'New User Password'
– 'New Admin Password'
4. Confirm the entered password with 'Confirmation'.
5. Click 'Set Values'.
6. Select 'X204-2' > 'Ring' in the tree view and check the 'Enable ring redundancy'
checkbox.
– Select the 'Automatic Redundancy Detection' redundancy mode.
7. Select 'X204-2' > 'Fault Mask' in the tree view and check the
'Enable Link Down Monitoring' checkbox for each connected port:
– Port 5 and 6 = Ring
– Port 1 = The connected ↑ 'Station'
– Port 2 to 4 only if more stations 'Stations' are connected
 FN2008-A1 is configured.
73 | 156
15 Standalone FN2012-A1
15 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
1 Updating the FW of Ethernet switch (modular) FN2012-A1
[➙ 125]
15.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

ϖ The FN2012-A1 is not connected to the station.
1. Use the rotary switch to define a pre-configured IP address. Link [➙ 75]
2. Put the web interface into operation. Link [➙ 77]
3. Change the IP address of the FN2012-A1 in accordance with your network
requirements. Link [➙ 78]
4. Configure the redundancy role of the FN2012-A1. Link [➙ 79]
5. Deactivate any local ports on the FN2012-A1 that are not being used in
accordance with your safety requirements. Link [➙ 79]
6. Configure fault monitoring for local ports. Link [➙ 80]
74 | 156
Standalone FN2012-A1
15
15.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'.
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 Configured via web interface or
MoNet bus MoNet 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
75 | 156
15 FN2012-A1 integrated into station
15.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
Commissioning an integrated FN2012-A1

ϖ The FN2012-A1 is connected to the station via a ribbon cable.
ϖ The rotary switch on the FN2012-A1 is set to '0'.
1. Create the FN2012-A1 in the site configuration:
– In Engineering Tool, create the 'Ethernet switch (modular, FN2012)'
element in the hardware tree for the station to which the FN2012-A1 is
connected.
– Or
– Read the new devices in on the station and then load the configuration
from the station to the PC.
2. Configure an IP address for the FN2012-A1 that is valid on the sub-net:
– In Engineering Tool, select 'Network' task card > 'Global system
configuration' > 'FS720 network configuration' > 'Ethernet sub-net' >
'Connections' > 'Station with the FN2012-A1'.
– On the 'Overview' tab, enter the IP address of the FN2012 in the 'IP
address network switch' field.
3. Configure redundancy management for the Ethernet ring in Engineering Tool.
– You will find more information in document A6V10210424.
4. Configure the local ports and fault monitoring for local ports in the web
interface:
– Put the web interface into operation. Link [➙ 77]
– Deactivate any local ports on the FN2012-A1 that are not being used in
accordance with your safety requirements. Link [➙ 79]
– Configure fault monitoring for local ports. Link [➙ 80]
76 | 156
FN2012-A1 web interface
15
15.3 FN2012-A1 web interface
15.3.1 Commissioning a web interface
WARNING
Changing the initial password
When you first access the web interface, change the initial login password.
If you do not change the initial password, the security of the web interface cannot
be guaranteed. Network settings can be changed as a result of unauthorized
access. Changed network settings can cause the fire detection system to
malfunction.
Opening the web interface

ϖ Standalone FN2012-A1: You have pre-configured an IP address for the
FN2012-A1 using the rotary switch.
ϖ Integrated FN2012-A1: In Engineering Tool, you have configured an IP address
for the FN2012-A1 that is valid within the sub-net.
ϖ The FN2012-A1 and the PC are connected to the same Ethernet sub-net.
ϖ 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.
 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.
4. Confirm the password you have set with 'Save changes'.
 You have already commissioned the web interface.
See also
1 Specifying a pre-configured IP address [➙ 75]
77 | 156
15 FN2012-A1 web interface
15.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

ϖ The rotary switch has been used to pre-configure an IP address for the
FN2012-A1. Link [➙ 75]
ϖ The web interface has been commissioned and the initial password changed.
Link [➙ 77]
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.
 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.
78 | 156
FN2012-A1 web interface
15
15.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.
ϖ The FN2012-A1 has a valid IP address within the sub-net.

ϖ The PC has access to the FN2012-A1 / is located within the same sub-net as
the FN2012-A1.
Link [➙ 77]
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'.
15.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 [➙ 77]
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.
79 | 156
15 FN2012-A1 web interface
15.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 [➙ 77]
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.
15.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.
ϖ You have specified a pre-configured IP address for the Ethernet switch
(modular) or configured the IP address manually.
ϖ 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'.
 You have activated port mirroring.
80 | 156
Restarting and resetting the FN2012-A1
15
15.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.
81 | 156
Commissioning security module (firewall) FN2009-A1
16 Restarting and resetting the FN2012-A1
16 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 [➙ 83]
2. Select the type and enter the MAC address. Link [➙ 83]
3. Enter the network settings. Link [➙ 84]
– Load configuration.
4. Create IP service definitions. Link [➙ 87]
5. Create firewall rules. Link [➙ 88]
– 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.
82 | 156
Installing Security Configuration Tool
16
16.1 Installing Security Configuration Tool
The 'Security Configuration Tool' software is included in the scope of supply for
the FN2009-A1.
κ Install the 'Security Configuration Tool' software.

 The software is installed in the standard path 'SIMATIC' > 'SCALANCE' >
'Security' > 'Security Configuration Tool'.
 FN2009-A1 can be configured.
The FN2009-A1 is displayed as S612V2 in the Security Configuration Tool.
16.2 Selecting type and entering MAC address
The corresponding MAC address can be found on the front of the FN2009-A1.
The FN2009-A1 is type S612V2.
Preparation
ϖ The PC is connected to FN2009-A1.
ϖ 'Security Configuration Tool' is started.
1. Create a new project using the 'Project' > 'New' menu and enter the
administrative project data, 'User name' and 'Password'.
2. Save the new project.
3. Select 'View' > 'Advanced Mode'.
 More entry masks for required settings can be viewed.
83 | 156
16 Entering network settings
Selecting type
1. Highlight the field below the 'Type' designation.
 The button for the dropdown list field is displayed.
2. Select 'S612V2'.
 Type is selected.
Entering MAC address

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

 MAC address is entered.
16.3 Entering network settings

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

1. Double-click on the field below the 'IP Address ext.' designation.
 The external IP address for the FN2009-A1 can be edited.
2. Enter the following IP address: 10.169.29.80.
84 | 156
Entering network settings
16
Entering routing mode, 'Routing Mode'
The following settings apply for the planned network access to ↑ GAP with
activated DHCP server.
'192.168.201.X' must be changed accordingly for network access to the standby
router or with IP address details.
ϖ 'Module 1' is highlighted in the 'View' window.

1. Press <F4> on the keyboard or open the 'Edit' > 'Properties' menu.
 The 'Module Properties' window is displayed:
2. Select the 'Routing Mode' tab.

 The following entry mask is displayed:
85 | 156
16 Entering network settings
3. Check the 'Routing active' checkbox.

4. Enter the following 'internal module IP address': 192.168.201.2.
5. Confirm input with 'OK'.
 'Internal sub-net mask' is automatically created.
 'Routing Mode' is active.
Entering router network data, 'Router'
The following settings apply for the planned network access to GAP with activated
DHCP server.
1. Open the 'Module Properties' window again.

 The 'Network' tab is displayed.
2. Click on 'Add Router'.
 The 'Sub-net Mask' '255.255.255.0' is already entered.
3. Correct the 'Sub-net Mask' from '255.255.255.0' to '255.255.0.0'.
4. Enter the following network data:
– 'Router IP': 192.168.201.1
– 'Network ID': 192.168.0.0
 The router network data is entered.
Loading the network settings to FN2009-A1

ϖ MAC address is entered.
ϖ IP addresses are entered.
1. Highlight the FN2009-A1 module in the project.
2. Select the 'Transfer > 'To Module' menu.
 The network settings are loaded to FN2009-A1.
 Network settings are entered.
86 | 156
Creating IP service definitions
16
16.4 Creating IP service definitions
NOTICE
Different ↑ BACnet port settings in FN2009-A1 and Cerberus-Engineering-Tool
No communication possible
● Configure the same BACnet port in FN2009-A1 and Cerberus-Engineering-
Tool.
1. Open the 'Options' > 'IP Service Definitions' menu.

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

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

 'IP Service Definitions' are created.
16.5 Creating firewall rules

ϖ IP service definitions are created.
ϖ The network addresses are known.
1. Right-click on the module for which you want to create firewall rules.
2. Select 'Properties…'.
 The 'Module Properties' window for the selected module is displayed.
88 | 156
Creating firewall rules
16
3. Select the 'Firewall Settings' tab.

 The following window is displayed without entries:
4. Click on 'Add Rule' for each firewall rule you would like to create.
5. Select the corresponding settings and IP services from the dropdown list fields.
6. Enter the required IP addresses.
 The firewall rules are created.
Loading the firewall rules to FN2009-A1

ϖ The firewall rules are created.
1. Highlight the FN2009-A1 module in the project.
2. Select the 'Transfer > 'To Module' menu item.
 The firewall rules are loaded to FN2009-A1.
89 | 156
Commissioning the fire brigade periphery module FCI2001-D1
17
17 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.
 During the commissioning of the control panel, fault messages are
indicated, provided that there are any deviations from the basic settings.
3. Press the push-button S101.
 The resistance values are read in.
90 | 156
Commissioning of I/O card (remote transmission) FCI2007-A1 and I/O card (horn/monitored) FCI2009-A1
18
18 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.
 During the commissioning of the control panel, fault messages are
indicated, provided that there are any deviations from the basic settings.
3. Press the S501 button.
 The resistance values are read in.
You can also read in the resistance values via the control panel's ↑ Person
Machine Interface.
91 | 156
Commissioning external printer
19
19 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==
92 | 156
19
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==
93 | 156
19
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
94 | 156
Updating the firmware
Preparation and security
20
20 Updating the firmware
20.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 [➙ 98]'.
● Data backup
– When the firmware of the main CPU is updated, the configuration data,
event memories and the alarm counter value are deleted. Load the
configuration data and event memories before updating in 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
95 | 156
20 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 [➙ 21]'.
● 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
1 Updating several 'Stations' simultaneously [➙ 98]
20.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.
20.2.1 Standalone station and SAFEDLINK station
pages.
ϖ You are familiar with the information in chapter 'Preparation and security
[➙ 95]'.
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 [➙ 29]
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
[➙ 110]
6. Update the firmware on the main CPU and the additional CPUs. Link [➙ 99]
8. Test the firmware version on the additional CPUs. Link [➙ 111]
– Update the firmware, if required, of the additional CPUs again, if there is a
higher firmware version available. Link [➙ 108]
96 | 156
Station: Updating the FW of the main CPU and additional CPUs
20
20.2.2 Router station and Ethernet station
pages.
[➙ 95]'.
ϖ 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.
[➙ 110]
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 [➙ 24]
8. Test the firmware version on the additional CPUs. Link [➙ 111]
10. Restore the network connection.
97 | 156
20.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.
[➙ 95]'.
ϖ A GAP with DHCP must be configured for the connection with the PC via C-
WEB/LAN.
ϖ The 'Stations' are displayed together.
ϖ 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.
[➙ 110]
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 [➙ 25] To do so, you must connect the
PC to each 'Station' locally. Link [➙ 24]
8. Test the firmware version on the additional CPUs on each 'Station'. Link
[➙ 111]
10. Restore the network connection, if required.
98 | 156
20
20.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 [➙ 99]'
● 'PMI & mainboard FCM2027 [➙ 102]'
20.2.4.1 PMI & mainboard FCM2004

[➙ 95]'.
1. Select 'Update' > 'FW update main and additional CPUs' from the menu bar.
2. If the 'Password check' window is open, enter the password '1234' and click on
'OK'.
 The '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 [➙ 106]'.
99 | 156
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.
 The firmware update starts and takes up to ten minutes.
100 | 156
20
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.
 The active firmware update is indicated by the symbol on the right-

hand side of the status bar.
 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'.
 The 'Station' is restarted many times. This procedure takes up to ten
minutes.
 After the restart, the 'Station' display shows the available BDVs. It is not
necessary to install a ↑ BDV at this point.
101 | 156
20.2.4.2 PMI & mainboard FCM2027

[➙ 95]'.
1. Select 'Update' > 'FW update main and additional CPUs' from the menu bar.
'OK'.
 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 [➙ 106]'.
102 | 156
20
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 peeping sound confirms the function is being executed.

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



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

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

– 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.
104 | 156
20
4. Select 'Start'.
5. Confirm the firmware update with 'Yes' or reject the firmware update with 'No'.
105 | 156
6. Click on 'OK'.


 The progress of the firmware update is displayed on the 'Progress' tab.
Open the 'Progress' tab in the 'View' > 'Progress' menu.
 After the restart, the 'Station' display shows the available ↑ BDVs. It is not
necessary to install a BDV at this point.
20.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'.
 The 'Select command' window is displayed.
4. Select 'Update incompatible firmware'.
 The firmware of the additional CPUs is updated.
106 | 156
Station: Updating the FW of the additional CPUs only
20
20.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.
ϖ Familiarize yourself with the information in 'Preparation and security [➙ 95]'.

2. Enable the 'Station'.
– Press <MENU> and enter a valid PIN.
3. Update the firmware of the additional CPUs if there is a higher firmware version
status. Select the local connection as the connection type. Link [➙ 108]
See also
1 Loading configuration from the station to the PC [➙ 29]

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.

ϖ A ↑ GAP with DHCP is configured for the connection with the PC via C-
WEB/LAN.
1. Load the configuration from the ↑ 'Station' or your archive to the PC. Link
[➙ 29]
2. Connect the PC to the C-WEB/LAN via the Ethernet switch (MM) FN2008-A1.
4. Update the firmware of the additional CPUs if there is a higher firmware version
status. Select the connection via GAP and enter the address of the 'Station'
you want to update. Link [➙ 108]
6. Disconnect the PC from C-WEB/LAN.
107 | 156
20 Station: Updating the FW of the additional CPUs only
20.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).
ϖ Familiarize yourself with the information in the chapter 'Preparation and

security'.
1. Select 'Update' > 'FW update additional CPUs' from the menu bar.
'OK'.
 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'.
 The 'FW update additional CPUs' window opens.
 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'.
 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.
 The CPUs are updated.
 The 'Information' window is opened after updating.
8. Note the update information and information about other procedures in the
'Information' window.
108 | 156
Update only the BDV
20
9. Click on 'OK'.
 The 'Station' is restarted.
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
1 Preparation and security [➙ 95]
20.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.

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 [➙ 110]
6. Load the converted configuration from the PC to the 'Station'. Link [➙ 27]
109 | 156
20 Converting the configuration
pages.

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

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

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

 The 'Action confirmation' window opens.
3. Click on 'Yes'.
 The 'Site' is converted.
110 | 156
Testing the firmware version of the additional CPUs
20
20.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.
'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'.
 The following window is opened.
5. Test the firmware version on the additional CPUs.

6. Click on 'FW update additional CPUs' in the 'Cancel' window.
111 | 156
20 Creating diagnosis report
20.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.
ϖ The configuration data for the ↑ 'Station' is loaded to Cerberus-Engineering-
Tool.
1. Select 'Commissioning' > 'Diagnostics report' from the menu bar.
 The 'Reports' window opens.
2. Select 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'.
 The report is created and displayed.
You will find more information about creating reports and the diagnosis report in
See also
20.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'.
112 | 156
Updating the FW of the peripheral devices
20
20.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
ϖ The driver for the MCL-USB adapter is installed on the PC.
1. Select 'File' > 'Import new resource package'.
2. In the selection window open the corresponding file F-FXS2007-XX_x_x_...zip.
3. Connect the MCL-USB adapter to the PC.
 The orange LED on the MCL-USB adapter flashes for a short while. When the
device is ready for operation, the green LED lights up.
USB
FDUZ221/FDUZ227
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 '1234' and click on the
'Next' button.
3. Select the FDUZ22x in the 'Devices:' field.
 The connection with the FDUZ22x is established.
 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.
 The FDUZ22x restarts.
 When the device is ready for operation, the green LED on the FDUZ22x
lights up.
6. Disconnect the FDUZ22x from the PC.
 The firmware is updated.
113 | 156
20 Updating the FW of the peripheral devices
20.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
ϖ The ↑ floor repeater terminal is fed by a 24 V external power supply or by the
C-NET detector line.
ϖ The driver for the MCL-USB adapter FDUZ221 or FDUZ227 is installed on the
PC.
2. In the selection window, open an F-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
114 | 156
20

'Next' button.
3. Select the 'Standard C-NET device' element in the 'Devices:' field.
 The connection with the floor repeater terminal is established.
4. Click on 'Next'.
 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) and 'Reset' (2) buttons pressed at the same time
and disconnect the C-NET plug (X1) from the printed circuit board.
2. Wait at least ten seconds and re-insert the C-NET plug (X1).
 The device is set to update mode.
FT2010 Front view FT2010 printed circuit board
115 | 156
20.8.3 Floor repeater display FT2011
WARNING
The firmware must be updated individually for each ↑ floor repeater display.
Preparation
ϖ The ↑ floor repeater display is fed by a 24 V external power supply or by the C-
NET detector line.
PC.
2. 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
116 | 156
20

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

in step 3:
1. Keep the 'More alarms' (1) und '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
117 | 156
20.8.4 Mimic display driver FT2001-A1
WARNING
The firmware must be updated individually for each mimic display driver.
Preparation
ϖ The mimic display driver is fed by a 24 V external power supply or by the C-
NET detector line.
PC.
2. In the selection window, open an F-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
118 | 156
20

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

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
20.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
120 | 156
20
20.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

ϖ The line tester is fed either internally with batteries or via a mains adapter.
κ 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.
ϖ The line tester is fed either internally with batteries or via a mains adapter.
κ 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.
121 | 156

'Next' button.
3. In the 'Devices:' field, select the 'FDUL221 C-NET line test device'.
 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.
 The line tester restarts.
122 | 156
20
20.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
ϖ The line tester is supplied via a mains adapter.
ϖ An RS232 port is available on the PC.
2. In the selection window, open the most recent file with the corresponding
language F-FXS2007-XX_x_x_...zip.
3. Connect the device to the PC via the RS232 interface in the battery
compartment.
DC
FDUL221
RS 232
B S
Figure 8: Connect the PC to the serial line tester
FDUL221 Line tester

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

'Next' button.
3. In the 'Devices:' field, select the 'FDUL221 C-NET line test device'.
 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.
 The line tester restarts.
124 | 156
Updating the FW of Ethernet switch (modular) FN2012-A1
20
20.9 Updating the FW of Ethernet switch (modular)

FN2012-A1
See also
1 Commissioning Ethernet switch (modular) FN2012-A1
[➙ 74]
20.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.
Updating the firmware in the web interface

the FN2012-A1.
ϖ The FN2012-A1 is connected to a sub-net containing at least one station.
Link [➙ 77]
ϖ Cerberus-Engineering-Tool is switched on.
ϖ 'Cerberus-Engineering-Tool' is connected to the sub-net.
ϖ 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'.
 The FN2012-A1 connects to 'Cerberus-Engineering-Tool'.
 The firmware of the FN2012-A1 is updated.
 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
125 | 156
20 Updating the FW of Ethernet switch (modular) FN2012-A1
Updating the firmware with the Reset button on the device

the FN2012-A1.
ϖ The FN2012-A1 is connected to a sub-net containing at least one station.
ϖ Cerberus-Engineering-Tool is switched on.
ϖ 'Cerberus-Engineering-Tool' is connected to the sub-net.
ϖ 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.
 After 5 s, the FAULT LED switches on.
 After 10 s, the FAULT LED switches off.
 The firmware of the FN2012-A1 is updated.
 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
126 | 156
Updating the FW of Ethernet switch (modular) FN2012-A1
20
20.9.2 FN2012-A1 integrated into station

ϖ The FN2012-A1 is connected to the station via a ribbon cable.
ϖ The FN2012-A1 is connected to the sub-net via an Ethernet cable.
ϖ The FN2012-A1 has been created in the hardware tree in Engineering Tool or
has been read in on the station.
ϖ In Engineering Tool, an IP address that is valid within the sub-net has been
configured for the FN2012-A1.
ϖ The rotary switch on the FN2012-A1 is set to '0'.
κ Update the FW of the main CPU and the additional CPUs. Link [➙ 96]
Or
κ Update the FW of the additional CPUs only. Link [➙ 107]
127 | 156
Maintenance
21 General
21 Maintenance
21.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.
21.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.
128 | 156
Maintenance
Testing and measuring instruments
21
21.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 Universal measuring instrument Measuring ranges:
resistance 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 Detector exchanger DX791 Compatible with all FD720 point
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 Adjustment kit FDLU291 Adjustment device and black alarm test
detector FDL241-9 filter
Test flame detector FDF2x1-9 LE3 Test lamp
Test ↑ C-NET detector line Line tester FDUL221
21.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)
129 | 156
Maintenance
21 Test system data
21.5 Test system data

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

1. Check that the system data are saved.
 Two copies must be archived with the 'Site', one copy with the technical
department.
2. Update the system data when the configuration is changed.
3. Note the date of execution in the system test manual.
Firmware
1. Read out the current firmware version from the ↑ 'Station': To do this, select
'Topology' > 'Hardware tree' > 'Station' > 'MoreOptions' > '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.
130 | 156
Maintenance
Testing the 'Station'
21
21.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.
131 | 156
Maintenance
21 Check the power supply
21.7 Check the power supply

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

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

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

1. Check whether the site mains supply cable is correctly fuse-protected and
labeled (fire detection system).
2. Check whether installed overvoltage dischargers are in order.
132 | 156
Maintenance
Testing the printer
21
21.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
21.9 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
21.10 Intervals for testing the system function

'Self test' of 'Detectors'
The 'Self test' is an automatic performance check for FD720 'Detectors'. The
function of the 'Detectors' must be checked regularly on site despite this.
Detector inspection
● Annual visual check of all 'Detectors'.
● Replace 'Detectors' that are badly soiled or mechanically damaged.
Function test
The following table shows the intervals recommended for the function check.
National specifications always take priority.
Function Activity Interval

(years)
1 2 5
Software Check date and time. X
↑ Detector lines: Activate an 'Automatic detector' and a 'Manual call point' per 'Line'. X
C-NET Activate all 'Manual call points'. X
Trigger all ↑ automatic fire detectors. X
Check all 'Detectors' for soiling and application. X
Check the function of the input/output modules. X
● On each 'Line' check whether a short-circuit or open line X
triggers a 'Fault'.
● Check the loop line function.
● During short-circuit also check the separator function.
133 | 156
Maintenance
21 Carrying out final maintenance work
Function Activity Interval

(years)
1 2 5
'Fire controls' Check activation of the 'Controls' up to and with the interface. X
Check the ↑ effects of the 'Controls' owned by the customer. X
Arrange a time with the customer.
'Mains failure' Check how long it takes until the 'Emergency power operation' fault
message is displayed during power failure.
↑ Alarm devices In 'Emergency power operation' check all alarm devices taking the X
following event category into account:
● 'Pre-ALARM'
● 'ALARM'
● 'Fault'
Check the remote transmission equipment in accordance with the X
manufacturer's instructions.
↑ Alarm organization Check the function of the delay times t1 and t2. X
Activate a global alarm with an 'Automatic detector' in the 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
21.11 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.
134 | 156
Repair
Disconnect the station from the power supply
22
22 Repair
22.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.
 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.
 The mains connection is interrupted.
3. Exchange the components.
4. Re-insert the disconnect terminal block.
 The mains connection is intact.
 The 'Station' starts.
5. First connect the negative battery terminals, then the positive terminals.
7. If need be, carry out partial commissioning.
Date and time are not saved in the ↑ 'Station'. The date and time must be reset to
restart the 'Station'.
135 | 156
Repair
22 Spare parts
22.2 Spare parts

● You will find details for ordering spare parts for 'Stations' in document
A6V10227652.
● You will find details for ordering Detectors and accessories in document
A6V10225323.
See also
136 | 156
Repair
Fault messages on the Person Machine Interface
22
22.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 'Fault' ● Check remote transmission
alarm
10 Fault / Off Alarm 'Fault' affecting acoustic control ● Check the 'Line' for open circuit/short-
device lines circuit or end-of-line element (EOL) is
missing or defective
12 Fault / Off Control 'Fault' affecting fire control lines ● Check the 'Line' for open line/short-circuit
function ● Check the function of the external control
devices
● Check the function, any existing
feedback switch
137 | 156
Repair
22 Fault indicators on components
22.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
22.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

κ 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'.
κ 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'.
138 | 156
Repair
Correcting swapped devices
22
22.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.
ϖ The device types in the corresponding bases are correct.

3. Load the configuration from the 'Station' to the PC.
139 | 156
Repair
22 Correcting an invalid topology
22.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
1 Read in devices on detector line [➙ 66]
140 | 156
Repair
Error message 'Too many devices'
22
22.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'.
22.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>.
 The PIN input dialog is displayed.
2. Enter a valid PIN and confirm with <ok>.
 The main menu is displayed.
3. Select the 'Topology' > 'Hardware tree' > 'Station' menu items.
 The elements of the 'Station' are listed.
4. Select module 101 or module 102 'CPU (FCC2001/06)'.
6. Select the 'Reset module' command.
 The 'Station' shuts down.
 The 'Station' is switched off for several seconds.
141 | 156
Repair
22 Restoring factory setting on the 'Station'
With the 'S32' button
ϖ Switches S38-1 and S38-2 are set to the 'OFF' position on the PMI &
mainboard FCM2004.
κ On the PCB of the operating unit, press and hold down the 'S32' button for
<2 s.
 The 'Station' shuts down.
 The 'Station' is switched off for several seconds.
22.10 Restoring factory setting on the 'Station'

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

1. Press <MENU>.
 You are prompted to enter a PIN.
2. Enter a valid PIN and confirm with <ok>.
 The 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.
142 | 156
Repair
Restoring factory setting on the 'Station'
22
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.
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).
 The Station restarts.

143 | 156
Repair
22 Fiber-optic network module FN2006 / FN2007 troubleshooting steps
22.11 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.
Number Pwr x RX1 Fail1 EF1 LNK1 Possible cause LNK2 EF2 Fail2 RX2 Pwr x
Node 1 / line 1 Node 2 / line 2
1 ON ON OFF OFF FLSHG Normal operation FLSHG OFF OFF ON ON
2 ON OFF ON OFF OFF Optical fibers wrong FLSHG OFF ON OFF ON
way round
3a ON OFF ON OFF OFF Break in optical fiber OFF OFF OFF ON ON
RX1
3b ON ON OFF OFF OFF Break in optical fiber OFF OFF ON OFF ON
RX2
4 OFF OFF OFF OFF OFF Energy supply FLSHG OFF ON 1 OFF 1 ON
interrupted
5 ON ON OFF ON 2 FLSHG Ground fault at A1/B1 FLSHG OFF OFF ON ON
6 ON ON OFF OFF OFF A1/B1 wrong way FLSHG OFF OFF ON ON
round
7 ON ON OFF OFF OFF Break in A1 or B1 FLSHG OFF OFF ON ON
Table 8: Searching for faults on fiber-optic cable converter 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).
144 | 156
Repair
22
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 10: 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 11: Optical fibers wrong way round
In addition, the following light up on the affected lines: fault indicators H2 / H3 on
the FN2001 network modules.
145 | 156
Repair
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 12: 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 13: Break in optical fiber RX2
146 | 156
Repair
22
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 14: 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 15: FN2006 / FN2007 Fault scenario 5, Ground fault 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.
147 | 156
Repair
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 16: 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 17: Break in A1 on line 1
indicators H3 (line 1) and H2 (line 2).
Legend for LED patterns

LED OFF
LED ON, in relevant color
LED flashing [FLSHG], in relevant color
148 | 156
Glossary
Glossary
Alarm device CPU
Element in the fire detection system for acoustic Abbreviation for 'Central Processing Unit'. The
and/or visual alarming, e.g. alarm sounder, computing unit of the fire control panel.
beacon.
Detection tree
Alarm indicator Diagram of the geographical and organizational
Visual display to signal an alarm or pre-alarm. arrangements of sensors in a building. This is a
hierarchical structure comprising the area,
section, and zone.
Alarm organization
Covers all measures which are used for Detector line
alarming, rescue, preventing a fire from
spreading, fire fighting, and orientation in the Electrical connection between the detectors and
event of a fire. Alarm organization may differ the fire control panel. There are collective
depending on the 'Manned' or 'Unmanned' detector lines and addressed detector lines.
operation mode.
Effect
Assignment An impact caused by a control, e.g., activation of
Creating a reference between two elements, a hardware output or a command.
e.g., logical channel and physical channel.
Ethernet station
Auto-configuration Participants in the Ethernet sub-net without local
A zone is created for each sensor channel connection for the PC.
(automatic detector and manual call point). A
control is created for each alarm sounder. IO- External alarm indicator
modules, FT2010, FT2011, and external alarm Optical element for displaying the fire location,
indicators are not auto-configured. which is at some distance from the detector. It is
normally mounted in the room at the point where
Automatic fire detector the corresponding detector is accessible.
Device which measures a physical parameter
(e.g. warmth) in order to detect a fire. Floor repeater display
A display device without operating elements.
BACnet
Abbreviation for 'Building Automation and Floor repeater terminal
Control Networks'. It is a network protocol for A display device with operating elements for
building automation, such as for communication acknowledging and resetting alarms and faults.
between a management station (MMS) and a fire
detection installation. GAP
Abbreviation for 'Global Access Point'.
BDV Participant in the Ethernet sub-net for the
Abbreviation for 'Base Data Variant'. connection between the Ethernet sub-net and a
Configuration files for the embedded software. A management station (BACnet client) and / or for
BDV contains country-specific templates, all remote access with the PC. If there is a
texts, specifications for message layout, menu secondary GAP, the GAP becomes the main
definitions, specifications for activating the LEDs GAP. Can be operated as a DHCP server in the
on the PMI, detector parameter set settings, Ethernet sub-net.
definitions for system-specific parts of the tool
interface, etc. Line card
Card for connecting peripheral devices. The card
C-NET can be a plug-in card or it can be integrated into
Addressed detector line for C-NET devices. the periphery board.
Control tree
Structure tree with control group and control.
149 | 156
Glossary
Line separator SAFEDLINK

An electronic switch which automatically Physical network of an FS20 / FS720 fire
disconnects the defective part of the line in the detection system with the network module
event of a short-circuit. (SAFEDLINK) and the network cable.
Logical channel SAFEDLINK station

Depiction of a logical device function in the Participants in the SAFEDLINK sub-net with
detection or control tree. The logical channel is local connection for the PC.
always the bottom level in the structure tree.
Section
Loop Level in detection tree of the fire detection
Detector line topology which runs from the fire system. The section is assigned to the area. It is
control panel via the fire detectors and back to used for combining zones.
improve operational reliability. This type of wiring
allows all detectors to communicate with the Site
control panel even in the event of an open line or
Depiction of fire detection installation: The top
short-circuit.
level in the figure showing the installed system.
Combines hardware tree, detection tree, and
Non-stationary device control tree.
Devices mounted with a base (exception: alarm
sounders and radio detectors). Standalone station
Standalone station with local connection for the
Normal operation PC.
The fire detection installation is supplied with
mains voltage. Station
Unit for system control. Fire control panel or fire
Parameter set terminal.
Defined detector behavior, e.g. in terms of
sensitivity, resistance to deceptive phenomena, Stationary device
response time. Detectors can be operated with
Devices that are directly installed without a base,
different parameter sets.
e.g. manual call points, input/output modules
and alarm sounders or radio detectors.
PMI
The arrangement of operating and display Stub
elements on a fire control panel or on a fire
Detector line which is only connected to the fire
terminal. Includes the LEDs, buttons, the display,
control panel on one side. In the event of an
and the operation options such as the key
open line or short-circuit, it may no longer be
switch, fire brigade control and display (FBA),
possible for all fire detectors to communicate
and the EVAC NL Person Machine Interface.
with the fire control panel.
Pre-configuration Zone
A sub-configuration of the hardware tree,
Level in the detection tree. The zone has at least
detection tree, and control tree created before
one fire detector. The decision on alarm is made
commissioning the fire detection installation.
at zone level. The zone is assigned to a section
or an area.
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.
150 | 156
Index
Index
A D
Acceptance test............................................... 20 Date / time .................................................... 138
Alarm counter ................................................. 95 Deleting
Auto-configuration ........................................... 35 Device ............................................................ 67
Definition of terms ........................................... 32 Detector
Detector line ................................................... 60 Test mode ...................................................... 68
Station ............................................................ 59 Testing ........................................................... 67
Detector inspection ........................................ 133
B Detector line
Backup ........................................................... 29 Auto-configuration........................................... 60
Install .............................................................. 19
C
Commissioning ............................................... 31 Restart............................................................ 64
According to wiring sequence.......................... 19 Switch off ........................................................ 63
Auto-configuration ........................................... 35 Switching on ................................................... 64
Networked station ........................................... 40 Testing ........................................................... 19
Overview ........................................................ 31 Detector self-test ........................................... 133
Standalone station with PC, Device
with pre-configuration ..................................... 39 Remove .......................................................... 48
Standalone station with PC, Remove (base without loop contact) ............... 51
without pre-configuration ................................ 38 Replace (base without loop contact)................ 51
Standalone station without PC ........................ 35 Replacing (different types) .............................. 52
With serial number .......................................... 19 Replacing (stationary) ..................................... 46
Without PC ..................................................... 35 Swapped ...................................................... 139
Communication problems ............................... 138 Temporarily remove ........................................ 53
Component Disconnect power
Indication of faults ......................................... 138 Station .......................................................... 135
Configuration Download .................................................. 25, 27
Conversion ................................................... 110 Download center
Load to station .......................................... 25, 27 URL ................................................................ 10
Loading to PC ................................................. 29
Connecting a sub-stub to a loop E
FDnet/C-NET detector line .............................. 57 Error message
Connection to the station .................................. 21 'Topology is invalid' ....................................... 140
Connectivity .................................................... 21 Ethernet switch
Conversion ................................................... 110 IP address ................................................ 75, 78
Configuration ................................................ 110 Web interface ................................................. 77
Convert stubs into loops Ethernet switch (MM) ....................................... 71
FDnet/C-NET detector line .............................. 57 Event memory................................................. 95
CPU Expand
Updating the firmware ..................................... 99 FDnet/C-NET detector line .............................. 44
CPU (other) Site ................................................................. 41
Updating the firmware ................................... 108 External printer................................................ 92
Customer text ................................................. 36
151 | 156
Index
F I
Factory setting ............................................... 142 I/O card (horn/monitored) FCI2009-A1................ 91
Fault indicators .............................................. 137 I/O card (remote transmission) FCI2007-A1 ........ 91
FCI2007-A1 I/O card (remote transmission) ........ 91 Indication of faults
FCI2009-A1 I/O card (horn / monitored) .............. 91 Component ................................................... 138
FDnet/C-NET detector line Initialize
Connecting a sub-stub to a loop ...................... 57 Station ............................................................ 25
Convert stubs into loops.................................. 57 Install
Expand ........................................................... 44 Detector line ................................................... 19
Removing a device (non-stationary) ................ 54 IP address
Removing a device (stationary) ....................... 47 Ethernet switch ......................................... 75, 78
Replacing a device with one of
a different type (non-stationary)....................... 50 L
Replacing a device with one of License ........................................................... 34
the same type (non-stationary) ........................ 49 Line
Replacing manual call points........................... 55 Auto-configuration........................................... 60
FDUL221 line tester Restart............................................................ 64
Updating the firmware ................................... 121 Line tester
FDUL221 serial line tester Updating the firmware ................................... 121
Updating the firmware ................................... 123 Load
FDUZ221 MCL-USB adapter From PC to station .................................... 25, 27
Updating the firmware ................................... 113 From station to PC .......................................... 29
Fire brigade periphery module FCI2001-D1 ......... 90 Load data to PC
Firewall Site ................................................................. 29
Safety module................................................. 82 Load data to the station
Windows 7 ...................................................... 22 Site ................................................................. 27
Windows firewall ....................................... 21, 96 Localization error ............................................. 70
Windows XP ................................................... 21
Floor repeater display M
Main CPU
Updating the firmware ................................... 116
Updating the firmware ..................................... 99
Floor repeater terminal
Maintenance ................................................. 128
MCL-USB adapter
FN2008 A1 ...................................................... 71
FN2009-A1...................................................... 82
Measuring instrument ..................................... 129
FN2012-A1
Merge
Integrated into station ..................................... 76
Sites ............................................................... 42
Standalone ..................................................... 74
Mimic display driver
FT2001-A1 mimic display driver
FT2010 floor repeater terminal N
Updating the firmware ................................... 114 Network cable
FT2011 floor repeater display Moving.......................................................... 138
Updating the firmware ................................... 116 Networked station ............................................ 40
FUJITSU DL3750+ ........................................... 92 Normal operation ............................................. 69
Function test..................................... 70, 133, 133
Fuse ............................................................... 29 O
Original language .............................................. 7
H
Hardware reset
Station .......................................................... 141
152 | 156
Index
P Resetting
Password .................................. 99, 102, 108, 111 FN2012-A1 ..................................................... 81
PC Restart
Connect to station ........................................... 24 Detector line ................................................... 64
Disconnecting from station .............................. 24 FN2012-A1 ..................................................... 81
PMI Station .......................................................... 141
Fault indicators ............................................. 137
Power supply S
Safety module (firewall) .................................... 82
Configuring ..................................................... 36
Scalance X204 2 ............................................. 71
Testing ......................................................... 132
Serial line tester
Pre-configuration
Definition of terms ........................................... 32
Series number ................................................ 19
Preparation
Set parameter set
Station ............................................................ 58
Use Person Machine Interface ........................ 37
Preparation without BDV
Site
Station ............................................................ 59
Expand ........................................................... 41
Primary Setup Tool .......................................... 72
Load data to PC.............................................. 29
Printer
Load data to the station................................... 27
Testing ......................................................... 133
Merge ............................................................. 42
R Test intervals ................................................ 133
Radio gateway FDCW221 .............................. 120 Source language ............................................... 7
Updating the firmware ................................... 120 Spare parts ................................................... 136
Radio gateway FDCW241 .............................. 120 Standalone station ................................ 35, 38, 39
Updating the firmware ................................... 120 Start
Read in Detector line ................................................... 64
Definition of terms ........................................... 32 Station
Device ............................................................ 66 Auto-configure ................................................ 59
Remove Disconnect power ......................................... 135
Device ............................................................ 48 Factory setting .............................................. 142
Device (base without loop contact) .................. 51 Hardware reset ............................................. 141
Device (temporary) ......................................... 53 Initialize .......................................................... 25
Removing a device (non-stationary) Load data ....................................................... 25
FDnet/C-NET detector line .............................. 54 Mount and install............................................. 20
Removing a device (stationary) Preparation ..................................................... 58
FDnet/C-NET detector line .............................. 47 Preparation without BDV ................................. 59
Replace Resetting ...................................................... 142
Device (base without loop contact) .................. 51 Restart.......................................................... 141
Device (different types) ................................... 52 Switching off ................................................. 135
Device (stationary) .......................................... 46 Swapped
Replacing a device with one of Device .......................................................... 139
a different type (non-stationary) Switch off
FDnet/C-NET detector line .............................. 50 Detector line ................................................... 63
Replacing a device with one of Switching off
the same type (non-stationary)
Station .......................................................... 135
FDnet/C-NET detector line .............................. 49
Switching on
Replacing manual call points
Detector line ................................................... 64
FDnet/C-NET detector line .............................. 55
System data ................................................. 130
153 | 156
Index
T
Test ........................................................ 70, 133
Test intervals .......................................... 133, 133
Test mode ....................................................... 68
Detector.......................................................... 68
Exit ................................................................. 69
Test unit........................................................ 129
Testing
Detector.................................................... 67, 67
Detector line ................................................... 19
Function ....................................................... 133
Power supply ................................................ 132
Printer........................................................... 133
System data ................................................. 130
Time / date .................................................... 138
Topology is invalid.......................................... 140
U
Uninstalling
Device ............................................................ 66
Update BDV .................................................. 109
Additional CPUs............................................ 108
Main CPU and additional CPUs ...................... 99
Peripheral devices ........................................ 112
Station ............................................................ 95
Upload ............................................................ 29
W
Web interface
Ethernet switch ............................................... 77
Windows 7
Firewall ........................................................... 22
Windows firewall ........................................ 21, 96
Windows XP
Firewall ........................................................... 21
Z
Zone
Switch off ........................................................ 63
Switching on ................................................... 64
154 | 156
Index
155 | 156
Issued by © Siemens Switzerland Ltd, 2008
Siemens Switzerland Ltd
Building Technologies Division Technical specifications and availability subject to change without notice.
International Headquarters
Gubelstrasse 22
CH-6301 Zug
+41 41-724 24 24
www.siemens.com/buildingtechnologies
Document ID: A6V10210416_i_en_AU Manual FS720

Edition: 2015-12-15

Cerberuspro Commissioning, Maintenance & Troubleshooting - A6v10210416 (Ip6)

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

Cerberuspro Commissioning, Maintenance & Troubleshooting - A6v10210416 (Ip6)

Uploaded by

Copyright:

Available Formats

FS720

Fire detection system

A6V10210416_i_en_AU Building Technologies

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

© Siemens Switzerland Ltd, 2008

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

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

2.1 Safety instructions

Symbol for danger

Additional danger symbols

General danger Explosive atmosphere

Voltage/electric shock Laser light

Signal word Danger level

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

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

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

ϖ The PC is connected locally to the ↑ 'Station'.

4.7 Loading configuration from the PC to the station

1Examples of special cases: