FS20 Fire Detection System: Configuration

FS20
Fire detection system

Configuration
MP6
009078_q_en_-- 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: 009078_q_en_--
© Siemens Switzerland Ltd, 2006
2 | 406
Building Technologies 009078_q_en_--
Fire Safety 2015-12-15
Table of contents
1 About this document ........................................................................... 13

1.1 Applicable documents ................................................................................15
1.2 Download center ........................................................................................16
1.3 Technical terms and abbreviations .............................................................16
1.4 Revision history .........................................................................................17
2 Safety ............................................................................................... 22
2.1 Safety instructions .....................................................................................22
2.2 Safety regulations for the method of operation ...........................................24
2.3 Standards and directives complied with......................................................26
2.3.1 CPR conformity and firmware version .........................................26
2.4 Release Notes ...........................................................................................26
2.5 Cyber security disclaimer ...........................................................................27
3 Installation ......................................................................................... 28
3.1 System requirements .................................................................................28
3.2 Installing the engineering tool set ...............................................................29
3.3 Installation via the input prompt..................................................................30
3.3.1 Installation and uninstallation with default parameter values ........30
3.3.2 Installation with modified parameter values .................................31
3.3.3 Uninstallation with modified parameter values .............................32
3.3.4 Installation with initialization file ...................................................32
3.3.5 Validation and error log file ..........................................................34
3.4 IP settings for several network cards ..........................................................35
3.5 Starting Engineering Tool...........................................................................35
3.6 Exit Engineering tool ..................................................................................36
4 Software administration ....................................................................... 37
4.1 Engineering tool set: File name and version ...............................................37
4.2 BDV: File name and version ......................................................................37
4.3 Firmware: File name and version ...............................................................38
4.4 Pre-settings ...............................................................................................38
4.4.1 General.......................................................................................39
4.4.2 Commissioning ...........................................................................40
4.4.3 Assign.........................................................................................40
4.4.4 Editing ........................................................................................42
4.4.5 Firmware package ......................................................................42
4.4.6 Help ............................................................................................43
4.4.7 Internet .......................................................................................43
4.4.8 LRC web server ..........................................................................44
4.4.9 Periphery update.........................................................................44
4.4.10 SintesoView ................................................................................45
4.4.11 Site .............................................................................................46
4.5 BDV import ................................................................................................46
4.6 Resources import.......................................................................................47
3 | 406
4.7 Lifecycle Responsibility Concept (LRC)...................................................... 47
4.7.1 Loading / renewing licenses ........................................................ 47
4.7.2 Returning licenses ...................................................................... 52
4.7.3 Display licensing information ....................................................... 52
4.7.4 Installing several different engineering tool sets........................... 53
4.7.5 Saving a parts list for the 'Site' .................................................... 53
4.8 License key ............................................................................................... 53
4.9 Calling up log files of Engineering Tool ...................................................... 53
5 GUI ...................................................................................................54
5.1 Overview of the program window ............................................................... 54
5.2 Menu bar ................................................................................................... 55
5.3 Toolbar ...................................................................................................... 58
5.4 Help and tooltips ........................................................................................ 59
5.5 Template for customer data ....................................................................... 60
5.6 Task cards................................................................................................. 60
5.7 Task card components............................................................................... 61
5.8 Scroll bars and window separating lines ..................................................... 61
5.9 Expanding and collapsing the elements in the structure tree ...................... 62
5.10 Multiselection............................................................................................. 62
5.11 Navigating within the program window ....................................................... 63
5.11.1 Navigating with task cards........................................................... 63
5.11.2 Navigating with hyperlinks ........................................................... 63
5.11.3 Navigating with shortcuts ............................................................ 64
5.12 Status bar .................................................................................................. 64
5.13 Error indication and problem identification .................................................. 65
5.14 SintesoView............................................................................................... 67
5.15 Dynamic loading ........................................................................................ 70
6 Program operation ..............................................................................72
6.1 Creating a site ........................................................................................... 72
6.1.1 Loading an existing 'site' .............................................................72
6.1.2 Create 'Site' based on an existing configuration........................... 73
6.1.3 Creating a new 'site' .................................................................... 74
6.1.4 Editing 'site' properties ................................................................ 75
6.2 Creating a station ...................................................................................... 76
6.3 Create element .......................................................................................... 77
6.4 Replacing element ..................................................................................... 79
6.5 Delete element .......................................................................................... 79
6.6 Editing elements ........................................................................................ 80
6.7 Table ......................................................................................................... 80
6.7.1 Copying properties in the table .................................................... 80
6.7.2 Inserting text in columns ............................................................. 81
6.8 Entering quicktext ...................................................................................... 81
6.9 Copying, cutting, and pasting elements ...................................................... 82
6.10 Moving an element .................................................................................... 83
6.11 Re-addressing elements ............................................................................ 84
6.12 Assigning elements....................................................................................85
4 | 406
6.13 Assignment with Data Matrix code .............................................................88
6.14 Assigning elements several times ..............................................................89
6.15 Assigning the effects of a control................................................................90
6.16 Deleting links .............................................................................................90
6.17 Finding ......................................................................................................91
6.18 Finding and replacing.................................................................................92
6.19 Exporting an XML ......................................................................................94
6.20 Exporting an SIB-X ....................................................................................96
6.21 Exporting and importing CSVs ...................................................................97
6.21.1 Exporting CSVs ..........................................................................97
6.21.2 Editing the CSV file .....................................................................97
6.21.3 Importing CSVs...........................................................................99
6.21.4 Protocol of the CSV import ..........................................................99
6.22 Change display logo ................................................................................100
6.23 Creating reports .......................................................................................101
6.23.1 Customer text report .................................................................102
6.23.2 Device report ............................................................................103
6.23.3 Diagnostics report .....................................................................104
6.23.4 Event memory report.................................................................105
6.23.5 Import information report ...........................................................106
6.23.6 Node report...............................................................................107
6.23.7 'Peripherals test report' .............................................................108
6.23.8 Soiling report.............................................................................109
6.23.9 Tree report ................................................................................110
7 Connectivity and communication with 'Station'...................................... 111
7.1 Connecting the PC to the station ..............................................................111
7.2 Disconnecting the PC from the station .....................................................111
7.3 Connecting SintesoView ..........................................................................112
7.4 Load data to the station ...........................................................................113
7.5 Initializing the station ...............................................................................113
7.6 Loading configuration from the PC to the station ......................................114
7.7 Loading configuration from the station to the PC ......................................115
7.8 Loading event memory to PC ...................................................................116
7.9 Loading the site log files to the PC ...........................................................117
7.10 Merge two sites .......................................................................................118
7.11 Handover .................................................................................................118
8 Updating the firmware ....................................................................... 119
8.1 Updating the firmware of the 'Station' .......................................................119
8.1.1 'Site' conversion ........................................................................119
8.1.2 Conversion log ..........................................................................120
8.2 Updating the firmware of the peripheral devices .......................................120
8.3 Converting a station .................................................................................121
5 | 406
9 Configuration –Overview .................................................................... 122
9.1 With pre-configuration.............................................................................. 123
9.2 Without pre-configuration ......................................................................... 124
9.3 Customer text .......................................................................................... 124
10 AlgoRex/SIGMASYS data migration .................................................... 125
10.1 System requirements ............................................................................... 125
10.2 Options and limitations............................................................................. 126
10.2.1 Supported stations .................................................................... 126
10.2.2 Supported lines and limitations.................................................. 126
10.2.3 Number of channels per 'Zone'.................................................. 126
10.2.4 AlgoRex limitations ................................................................... 127
10.2.5 SIGMASYS limitations .............................................................. 127
10.2.6 Sequence of the import process ................................................ 127
10.2.7 Diagram of possible assignment ............................................... 128
10.3 Overview of steps .................................................................................... 129
10.4 Exporting configuration data .................................................................... 130
10.4.1 AlgoWorks export ..................................................................... 130
10.4.2 PLAND100 export ..................................................................... 131
10.5 Creating a site for data migration ............................................................. 133
10.5.1 Creating a station...................................................................... 133
10.5.2 Creating line cards .................................................................... 133
10.5.3 Creating FDnet/C-NET lines...................................................... 133
10.6 Importing configuration data..................................................................... 134
10.6.1 Importing hardware ................................................................... 135
10.6.2 Importing controls ..................................................................... 137
10.6.3 Error log.................................................................................... 138
10.7 Adapting configuration ............................................................................. 139
10.7.1 Adapting the number of channels per zone ............................... 139
10.7.2 Adapting controls ...................................................................... 139
10.7.3 Setting visibility ......................................................................... 141
10.7.4 AlgoRex: Creating base sounders for FDnet/C-NET devices ..... 141
10.7.5 Correcting the AnalogPLUS address ......................................... 142
10.7.6 AnalogPLUS/Interactive: Correcting multiple verification
DC1192c, DC1151, CB320A ..................................................... 142
10.7.7 Interactive: Correcting DCW1151/DOW1171 assignment .......... 143
10.7.8 Adapting properties ................................................................... 145
10.8 Loading the configuration in the 'station'................................................... 145
10.9 Completing migration ............................................................................... 146
10.9.1 Exporting an SIB-X ................................................................... 146
10.9.2 Deleting import information ....................................................... 147
6 | 406
11 'Hardware' task card ......................................................................... 148
11.1 'Station'....................................................................................................149
11.1.1 Intervention concept (IC) ...........................................................150
11.1.2 Configuring permanent access for SintesoView .........................151
11.2 Onboard I/Os ...........................................................................................152
11.3 FDnet detector line ..................................................................................152
11.3.1 Automatic fire detectors ............................................................153
11.3.2 Detector parameter sets............................................................155
11.3.3 Sensor mode with multi-sensor fire detectors ............................156
11.3.4 Base sounder............................................................................157
11.3.5 External alarm indicator ............................................................159
11.3.6 Alarm sounder and interbase ....................................................160
11.3.7 Aspirating smoke detector .........................................................161
11.3.8 Input/output module FDCIO223 .................................................163
11.3.9 Zone module FDCI223 ..............................................................166
11.4 Power supply ...........................................................................................167
11.5 I/O cards..................................................................................................169
11.6 LED indicator FTO2002 ...........................................................................170
11.7 Ethernet switch (modular) FN2012 ...........................................................171
11.8 Inputs/outputs ..........................................................................................172
11.9 Creating the line card ...............................................................................174
11.10 Collective detector line .............................................................................175
11.10.1 Creating 'Zones' and assigning them to collective
detector lines ............................................................................175
11.10.2 Setting the properties of the collective detector line ...................176
11.10.3 Setting the properties of the line devices ...................................178
11.11 MS9i detector line ....................................................................................178
11.11.1 Creating and assigning line elements and 'Zones' .....................179
11.11.2 Creating controls and assigning them to line elements ..............180
11.11.3 Setting the properties of the MS9i detector line..........................180
11.11.4 Setting the properties of the line elements .................................181
11.12 AnalogPLUS detector line ........................................................................182
11.12.1 Creating and assigning line elements and 'Zones' .....................183
11.12.3 Configuring the line type for an AnalogPLUS detector line .........184
11.12.4 Setting the properties of the AnalogPLUS detector line..............184
11.12.5 Configuring line element addresses...........................................185
11.13 Interactive detector line ............................................................................187
11.13.1 Creating 'Zones' and assigning them to an interactive
detector line ..............................................................................188
11.13.3 Configuring the line type for an interactive detector line .............189
11.13.4 Setting the properties of the interactive detector line..................189
7 | 406
12 'Detection' task card .......................................................................... 193
12.1 Creating 'Detection tree'........................................................................... 193
12.2 'Area' ....................................................................................................... 194
12.2.1 Alarm verification concept (AVC)............................................... 194
12.2.2 Immediate global alarming ........................................................ 198
12.2.3 Alarm organization mode .......................................................... 199
12.2.4 Switching times for 'Unmanned operation' ................................. 199
12.3 'Section' ................................................................................................... 199
12.4 'Zone' ...................................................................................................... 200
12.4.1 'Automatic zone'........................................................................ 200
12.4.2 'Manual zone' ............................................................................ 204
12.4.3 'Technical zone' ........................................................................ 205
12.4.4 'Sub-system zone' ..................................................................... 206
12.4.5 'Flow switch zone' ..................................................................... 207
12.4.6 'Sprinkler zone' ......................................................................... 208
12.4.7 'Gas zone'................................................................................. 210
12.4.8 'XC10 zone' .............................................................................. 211
12.4.9 'FSE zone' [DE]......................................................................... 215
12.5 Configuring the 'Zone' .............................................................................. 216
12.5.1 Multi-detector dependency ........................................................ 219
12.5.2 Multi-detector dependency with latching .................................... 220
12.5.3 Two-zone dependency .............................................................. 221
12.5.4 Additional criteria for pre-stage and main stage ......................... 222
12.6 Assign hardware tree to the detection tree ............................................... 224
12.7 Collective detector line via input/output module FDCIO223 or
zone module ............................................................................................ 225
12.8 Neural fire detector FDOOTC241............................................................. 226
12.8.1 Configuring fire detection .......................................................... 226
12.8.2 Configuring gas detection.......................................................... 227
12.8.3 Configuring environment monitoring .......................................... 227
12.9 Redux module [DE].................................................................................. 229
12.10 Key safe adapter [DE]: Configuring the technical zone ............................. 230
13 'Control' task card ............................................................................. 232
13.1 Dual CPU – switchover and degraded mode ............................................ 232
13.2 Creating control tree ................................................................................ 232
13.3 Alarming control group ............................................................................. 233
13.3.1 Automatically isolating remote transmission .............................. 236
13.3.2 Properties of the assigned effect elements ................................ 237
13.4 Universal control group ............................................................................ 239
13.4.1 Fire control................................................................................ 239
13.4.2 Time control .............................................................................. 246
8 | 406
13.5 Evac control group ...................................................................................251
13.5.1 Assigning universal evac control ...............................................251
13.5.2 Universal evac control properties ..............................................253
13.5.3 Cause of the phased evac control .............................................255
13.5.4 Effect of the phased evac control ..............................................256
13.5.5 Properties of the phased evac control .......................................257
13.5.6 2-stage evacuation, special case [GB] .......................................258
13.6 Counter control group and alarm counter control ......................................260
13.7 Damper control group ..............................................................................261
13.7.1 Creating and configuring a damper control ................................261
13.7.2 Damper control states ...............................................................262
13.7.3 Assignment of effects dependent on wiring................................263
13.7.4 Fire damper control properties ..................................................268
13.7.5 Properties of the assigned effects .............................................269
13.7.6 EDE export ...............................................................................270
13.7.7 Configuring LEDs for damper control.........................................270
13.8 Extinguishing standard interface SST [DE] ...............................................273
13.9 External alarm indicator ...........................................................................277
13.10 Loop sounder, loop sounder/beacon, and base sounder ..........................278
13.11 Sounder line via input/output module FDCIO223 ......................................279
13.12 Input/output module FDCIO223 with monitored input/output .....................282
13.12.1 Configuring monitored input ......................................................282
13.12.2 Configuring monitored output ....................................................283
13.13 Addressable alarm indicator FDCAI221....................................................284
13.14 Key safe adapter [DE]: Configuring controls .............................................285
14 'Operation' task card ......................................................................... 289
14.1 Global system configuration .....................................................................289
14.1.1 System behavior .......................................................................290
14.1.2 Global PIN configuration ...........................................................292
14.1.3 Country settings ........................................................................292
14.1.4 Master clock .............................................................................293
14.2 Person Machine Interface (PMI)...............................................................294
14.2.1 Basic settings............................................................................294
14.2.2 LEDs ........................................................................................296
14.2.3 Standard keys ...........................................................................299
14.2.4 Favorites...................................................................................300
14.2.5 Configuring standard keys and favorites ....................................303
14.2.6 Toggle function .........................................................................308
14.3 Visibility ...................................................................................................313
14.3.1 Properties of the visibility...........................................................314
14.3.2 Standard visibility ......................................................................315
14.3.3 Standby visibility .......................................................................316
14.3.4 Expanded visibility ....................................................................319
14.3.5 Configuring visibility on FC2080 ................................................320
14.3.6 Configuring visibility for Sinteso Mobile......................................321
9 | 406
14.4 Floor repeater terminal FT2010 and floor repeater display FT2011........... 322
14.4.1 FT2010/FT2011 core and configuration groups ......................... 322
14.4.2 Visibility .................................................................................... 326
14.4.3 LEDs ........................................................................................ 327
14.4.4 Function keys ........................................................................... 327
14.4.5 Assigning the configurable keys and LEDs ................................ 328
14.5 LED indicator FTO2002 and mimic display driver FT2001 ........................ 330
14.5.1 Element 'LED ind./mimic 24 LED groups' .................................. 331
14.5.2 Element 'LED ind./mimic 48 LEDs' ............................................ 333
14.5.3 Configuring mimic display driver FT2001 ................................... 335
14.6 Event printer ............................................................................................ 335
14.7 Fire brigade periphery [DE] ...................................................................... 338
14.7.1 Key depot adapter FCI2019 ...................................................... 342
14.8 ESPA 4.4.4 interface (pager) ................................................................... 344
14.9 EVAC panel [NL] ..................................................................................... 346
14.10 Alarming equipment (UGA) [FR] ..............................................................348
14.10.1 Creating the 'UGA' and 'UGA alarm zone' elements .................. 348
14.10.2 Assigning UGA to the RS485 module ........................................ 349
14.10.3 Configuring visibility .................................................................. 350
14.10.4 UGA Master-Slave principle ...................................................... 351
14.11 CERLOOP gateway [FR] ......................................................................... 352
14.11.1 Creating RS232 module ............................................................ 352
14.11.2 Creating and assigning the CERLOOP gateway ........................ 353
14.11.3 Configuring visibility .................................................................. 354
14.11.4 Entering CERLOOP group numbers.......................................... 355
14.12 Key safe adapter [DE].............................................................................. 355
14.12.1 Assigning LEDs ........................................................................ 357
15 'Network' task card ............................................................................ 359
15.1 Network parameters ................................................................................ 359
15.2 Network configuration .............................................................................. 359
15.2.1 Creating networked 'Stations' .................................................... 359
15.2.2 Configuring a 'Station' as a router station .................................. 361
15.2.3 Configuring a 'Station' as GAP .................................................. 362
15.2.4 Configuring GAP with DHCP server .......................................... 363
15.2.5 Manual allocation of addresses in the sub-nets ......................... 364
15.2.6 Entering routes for external access to extended
networks via GAP ..................................................................... 366
15.2.7 Setting network speed for SAFEDLINK ..................................... 368
15.2.8 Configuring remote access with two GAPs ................................ 368
15.2.9 Configuring remote access via cRSP ........................................ 370
15.2.10 Configuring redundancy management ....................................... 371
15.3 Establishing connection from PC to FS20 network ................................... 376
15.4 Setting up a Maximum Transmission Unit (MTU)...................................... 377
15.5 Monitoring Ethernet switch (MM) and safety module (firewall) .................. 378
15.6 Connecting management stations via BACnet/Ethernet ........................... 379
15.6.1 Planning BACnet configuration.................................................. 379
10 | 406
15.7 Global BACnet configuration ....................................................................380
15.7.1 Configuring global BACnet settings ...........................................380
15.7.2 Disabling switch-off and switch-on messages ............................381
15.7.3 Delegating multiple alarms for 'Zones' .......................................381
15.7.4 Configuring BACnet client .........................................................382
15.7.5 Monitoring BACnet client ...........................................................383
15.7.6 Configuring 'Standby visibility' for the management station ........384
15.8 BACnet device configuration ....................................................................385
15.8.1 'BACnet device object' –Overview .............................................385
15.8.2 BBMD entry (BDT entry) ...........................................................388
15.8.3 BACnet Notification Class Element............................................389
15.9 Checklist for network and BACnet configuration .......................................391
15.10 Site configuration, status MP2.1...............................................................394
15.10.1 Converting configuration in accordance with BDV 32.................394
16 FG2020 ........................................................................................... 395
Glossary ................................................................................................... 396
Index ...................................................................................................... 400
11 | 406
12 | 406
About this document
Applicable documents
1
1 About this document

Goal and purpose
This document describes the configuration of an FS20 fire detection system using
the engineering tool set FX2030.
Scope
The information in documents 008838 and 009052 is prerequisite for configuration
of the fire detection system with the engineering tool set FX2030. See chapter
'Applicable documents'.
This document is valid for market package MP6.
Target groups
The information in this document is intended for the following target groups:
Target group Activity Qualification

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_COUN A6V10215123_a_de_DE
TRY A6V10215123_a_en_--
-- = multilingual or international A6V10315123_a_--_--
Date format
The date format in the document corresponds to the recommendation of
international standard ISO 8601 (format YYYY-MM-DD).
13 | 406
About this document
1 Applicable documents
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.
14 | 406
About this document
Applicable documents
1
1.1 Applicable documents

Document ID Title
008109 FDS221 Alarm sounder, Technical manual
008331 List of compatibility
008836 FS20 Fire Detection System, Description
008837 FS20 Fire Detection System, Product Data
008843 FS20 Fire Detection System, Planning
009026 FS20 Fire Detection System, Inscription Strips
009052 FS20 Fire Detection System Commissioning,
Maintenance, Troubleshooting
009122 FDCIO223 input/output module, technical
documentation
010095 FDS229 Alarm sounder beacon, Technical manual
A6V10209291 FDOOTC241 Neural fire detector, Technical manual
A6V10211122 FDCI221, FDCIO221 Input Module, Input/Output
Module, Technical Manual
A6V10224853 FS20/FS720 Fire Detection System, External Printer,
Application Note
A6V10244961 FS20 Fire Detection System, Site Conversion
A6V10257473 XC10 Extinguishing control unit, XC1001-A /
XC1005-A /
XC1003-A, Installation / Commissioning / Maintenance
A6V10281424 FG2020-D1, Technical Manual
A6V10320090 FDSB221, FDSB229 Sounder interbase, sounder
beacon interbase, Technical manual
A6V10334410 Technical manual for aspirating smoke detectors
FDA221 and FDA241
007023 FDCI222, FDCIO222, FDCIO224 Input module,
Input/output module, Technical manual
Additional documents for AlgoRex/SIGMASYS data migration

Document ID Title
Online help AlgoWorks station management
Online help PLAND100
008725 AlgoRex fire detection system, design and planning
15 | 406
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
l 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
BDV Base data variant
ES Product version
FDnet Addressed detector line
FSD Fire brigade key depot
RT Remote transmission
You will find details of further technical terms and abbreviations in the 'Glossary'
chapter.
See also
2 Applicable documents [➙ 15]
16 | 406
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

q 2015-12-15 Edition for MP6
New:
Configuring the operation mode for SintesoView
In chapter 'AlgoRex / SIGMASYS data migration': Limitations and information for
control migration, importing controls, adapting controls, AlgoRex: Creating base
sounders for FDnet devices
Ethernet switch (modular) FN2012
Configuring redundancy management (with subchapters)
Assigning elements several times
Editing the CSV file
'Peripherals test report'
Time control (with subchapters)
Inserting text in columns
Installation via the input prompt
Soiling report
Cyber security disclaimer
Configuring the key safe adapter [DE]: 'Key safe adapter [DE]', 'Key safe adapter
[DE]: Configuring controls', 'Key safe adapter [DE]: Technical zone for LED',
'Assigning LEDs'
Damper control group, incl. 'EDE export' sub-chapter
Network parameters with reference to document 009052
'Opening an XML file in Excel' in 'Creating reports'
17 | 406
About this document
1 Revision history

Revised
Referenced documents updated, screenshots updated throughout the document
New structure in chapter 'AlgoRex/SIGMASYS data migration', changes made to
chapters 'Installing the engineering tool set', 'Calling up log files', 'Toolbar',
'Number of channels per 'Zone'', warning added regarding assigning FDA241
sensors in chapters 'Aspirating smoke detector' and 'Assigning hardware tree to
the detection tree', notice added regarding cause link for sounder assigned as an
effect with active 'Activation timeout 'manned''/'Activation timeout 'unmanned''
property in chapters 'Alarming control group', 'Properties of the assigned effect
elements', 'Assigning the 'Universal evac control' element', 'Cause of the 'Phased
evac control' element', and 'Sounder line via input/output module FDCIO223',
chapter 'Importing CSVs': Information added regarding character length of
customer texts and automatic shortening on import, chapter 'Overview of the
program window' revised, chapter 'Adapting the number of channels per zone' in
'AlgoRex/SIGMASYS data migration', chapters 'Input/output module FDCIO223'
and 'Inputs/outputs' updated and option 'Enable temporary freeze of output
position' added, chapter 'Exporting and importing CSVs' revised in terms of
content and structure, chapter 'Aspirating smoke detector', chapter 'Global PIN
configuration' edited, chapter 'Settings for LRC web server': 'Traceability' added,
chapter 'PLAND100 export', information on reserved IP addresses added to
chapters 'Configuring a 'Station' as a router station' and 'Manual allocation of
addresses in the sub-nets, chapter 'Finding' updated, pre-settings updated,
chapter 'Exporting an XML' updated, video fire controller FDV241 removed,
chapter 'Assigning elements' updated, information on use as a test site added to
chapter 'Creating a new 'Site'', information on converting a station added to
chapter 'Replacing an element', chapter 'Creating reports' and sub-chapters
updated, chapter 'Creating a standalone station' removed, chapter ''Network' task
card' updated, chapter 'BACnet Notification Class element' updated
Windows 8.1 and 10.0 supported, Windows Vista and Windows XP no longer
supported
p 2014-01-15 Revised:
'Toggle function': Note on switched-off 'Zones' added
18 | 406
About this document
Revision history
1

o 2013-11-14 Edition for MP5
Change to date format according to ISO 8601
New:
Template for customer-specific 'Site' data
PIN configuration
Converting a 'Station'
'Import information report'
AlgoRex/SIGMASYS data migration
Setting up a Maximum Transmission Unit (MTU)
Resources import
Handover
Configuring visibility for Sinteso Mobile
AnalogPLUS detector line
Interactive detector line
Zone module FDCI223
Creating the line card
Revised:
System requirements: Not compatible with Windows 2000
Configuring a 'Station' as GAP
The maximum value that can be set for the address of a 'Station' is 252.
'Editing site properties': 1000 instead of 250 characters
'Pre-settings': New pre-settings
'Menu bar': Changes and new menu items
'Export XML': User-defined XML export
'Expanding and collapsing the elements in the structure tree': Filter function
'Assigning with the help of Data Matrix code': Automatic assignment
Notes about license keys
'Settings for Data Matrix code reader': Note about 'Serial communication
parameters' for reading devices with USB-COM port
Network addresses in the chapter 'Task card 'network''
'Alarm verification concept': Settings for 'Alarming type 'thermal''
FDV242 deleted
'Configuration - Overview' revised
'Setting the properties of the collective detector line': Settings for 'Events' tab
deleted
'Alarm verification concept (AVC)': Configuring the AVC settings for the line alarm
'Collective detector line via input/output module FDCIO223 or zone module': Zone
module FDCI223
'FDnet detector line': 'Events' tab
'Input/output module FDCIO223': Reference to document 008331
''Hardware' task card': Chapter restructured
19 | 406
About this document
1 Revision history

n 05.2012 Edition for MP-EN 4.0
New: Revised:
I/O card (remote transmission) I/O cards
FCI2007-A1 'Zones'
I/O card (horn/monitored) FCI2009-A1 Configuring 'Zone'
Gas zone Reports
Multi-detector dependency with latching File name and version of engineering
CSV export/import tool set, firmware, and BDV
Link to documentation for the FG2020 Collective detector line via input/output
SintesoView settings module FDCIO223
Calling up log files Sounder line via input/output module
FDCIO223
Input/output module FDCIO223
Entire chapter ''Hardware' task card'
Input/output module FDCIO223 with
monitored input/output Configuring collective detector line
Option to configure 252 devices per Configuring the MS9i detector line
detector line Onboard I/Os
'Create and assign' function for MS9i 'XC10 zone'
detector line 'Operation' task card: 'Global system
New quicktext settings configuration' chap. up to 'Visibility'
Mouse wheel settings CERLOOP gateway
Key safe adapter Alarming equipment (UGA)
Alarm counter value configurable 2-stage evacuation
Reading device for Data Matrix code Neural fire detector FDOOTC241
Change display logo
LED indicator FTO2002
Dual CPU – switchover and degraded
mode
Alarm sounder and interbase
Aspirating smoke detector
Support for Windows 7
Remote access with two GAPs
Remote access via cRSP
Text for favorites
m 07.2010 Chapter "Loading configuration from the PC to the 'Station'" revised
l 05.2010 Edition for MP3.0
Revision history redefined and standardized, dynamic loading, merging two 'Sites',
network configuration, management stations via BACnet/Ethernet, route entries
for installation, new FDCAI221, general chapter structure
k 08.2009 Chapter 8.2.2 restructured
New: Chapter 8.4.3.1 and 8.5.6.4
j 04.2009 Modifications for MP2.1
i 02.2009 Chapter "Line card (collective)" revised
h 12.2008 Modifications for MP2.1
g 08.2008 Modifications for MP2.1
f 08.2008 Modifications for MP2.1
e 07.2008 Modifications for MP2.1
20 | 406
About this document
Revision history
1

d 06.2008 Modification for MP1.3 and MP2.1
c 01.2008 Chapters 4 to 7 restructured and modifications for MP1.2
b 07.2007 Chapter Configuration reworked and modified for MP1.2
a 11.2006 First edition
21 | 406
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.
22 | 406
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
23 | 406
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.
24 | 406
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
25 | 406
Safety
2 Standards and directives complied with
2.3 Standards and directives complied with

A list of the standards and directives complied with is available from your Siemens
contact.
2.3.1 CPR conformity and firmware version

In order to satisfy Ordinance No. 305/2011 (the Construction Products Regulation –
CPR), the firmware of a newly installed fire detection installation must be current
market package version MP6 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 MP6.
● Update the firmware if necessary.
2.4 Release Notes

Limitations to the configuration or use of devices in a fire detection installation with
a particular firmware version are possible.
WARNING
Limited or non-existent fire detection
Personal injury and damage to property in the event of a fire.
● Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
● Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.
NOTICE
Incorrect planning and/or configuration
Important standards and specifications are not satisfied.
Fire detection installation is not accepted for commissioning.
Additional expense resulting from necessary new planning and/or configuration.
● Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
● Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.
26 | 406
Safety
Cyber security disclaimer
2
2.5 Cyber security disclaimer

Products, solutions and services from Siemens include security functions to ensure
the secure operation of building automation and control, fire safety, security
management, and physical security systems. The security functions on these
products, solutions and services are important components of a comprehensive
security concept. Drafting, implementing and managing a comprehensive and up-
to-date security concept, customized to individual needs, is nevertheless
necessary, and may result in additional plant- or site-specific preventive measures
to ensure secure operation of your site regarding building automation and control,
fire safety, security management, and physical security. These measures may
include, for example, separating networks, physically protecting system
components, user training, multi-level defensive measures, etc. For additional
information on security as part of building technology and our product, solution and
service offerings, please contact your Siemens sales representative or project
department. We strongly recommend to always comply with our security advisories
on the latest security threats, patches and other related measures.
http://www.siemens.com/cert/en/cert-security-advisories.htm
27 | 406
Installation
3 System requirements
3 Installation
3.1 System requirements
Hardware
Component Minimum requirements
Processor Pentium M1.6
Main memory 512 MB
Hard disk 400 MB, better still 1 GB of free memory
Network connection Ethernet RJ45
Screen resolution 1024 x 768
Colors 65535
Software
Operating system Version
Windows 7 x86 (32-bit), SP1
Windows 7 x64 (64-bit), SP1
Windows 8.1 x86 (32-bit)
Earlier and up to and including MP-En 4.0 / IP4: Windows XP / Windows Vista
(both 32-bit version only). Not compatible: Windows 2000
Component Minimum requirements

Acrobat Reader Version 6 or higher
Browser Internet Explorer or similar browser
Administrator rights to the OS of the PC are required for the installation of the
software.
Data migration
The following system requirements apply to data migration:
AlgoRex system version XX_1140_830_YY

XX:country code
YY:version number
AlgoWorks software version V1.94
SIGMASYS system version xxx
PLAND100 software version V9.0
SintesoWorks F-FX2030-XL_en_1-5.0.0.R2 or later
version
28 | 406
Installation
Installing the engineering tool set
3
3.2 Installing the engineering tool set

When the engineering tool set FX2030 is installed, the following components are
installed too:
● Firmware package FXS2001
● SintesoWorks FXS2002
● Base data variant (BDV) FXS2004
● Set of help documents FXS2006
● Periphery update package FXS2007
When the SintesoWorks is installed, the two routes in the table below are entered
in the PC's network settings.
Network address Network mask ↑ Gateway address Metric

192.168.0.0 255.255.0.0 192.168.200.1 10
192.168.0.0 255.255.0.0 192.168.201.1 10
Table 1: Persistent routes
Installing the engineering tool set FX2030

1. Run the installation file.
a The installation routine starts and guides you through the installation.
2. Follow the instructions of the installation routine and observe the installation
paths.
Installation paths
During installation, you can change the standard installation paths offered.
You can change various paths subsequently within the software, but you must
then move the respective folder manually to the new location.
We do not recommend that you change the paths after successful installation in
the software.
The path for the log files cannot be changed afterwards.
If you install a version of the software with another major or minor version, new
standard installation paths are created. The existing installation paths are
retained.
You can also open the directory for log files as follows via the Start menu:
Start > All Programs > Siemens > F-FX2030 > [Version] 1 > Log files
1 [Version] = Version of the software, e.g., EN_en_1-V1
See also
2 Engineering tool set: File name and version [➙ 37]
2 Installing several different engineering tool sets [➙ 53]
29 | 406
Installation
3 Installation via the input prompt
3.3 Installation via the input prompt

Installation via the Command Prompt automatically uninstalls earlier engineering
tool set versions and installs the required version automatically. When installing via
the Command Prompt, no installation routine is executed, i.e., no dialog windows
are displayed that guide you through the installation.
NOTICE
Data will be deleted
Installation via the Command Prompt automatically uninstalls earlier installations
of the engineering tool set. This may lead to data being deleted, e.g., BDVs.
● Take the default uninstall parameters into account and change the parameter
values to prevent data being deleted.
The uninstall and installation process cannot be interrupted.
Installation via the input prompt is supported from engineering tool set version
4.0.0. Older versions have to be uninstalled manually.
The instructions below apply to installation in Windows 7 and 8.1.
3.3.1 Installation and uninstallation with default parameter values

The tables below display the default parameters.
Installation parameter Default value

Installation path C:\Program Files (x86)\Siemens\F-
FX2030\XL_en_x-Vx.x
Data path C:\ProgramData\Siemens\F-FX2030
Engineering Tool interface language on English
initial start-up
BDV language on initial start-up English
Launch Engineering Tool after Yes
installation
Uninstallation parameter Default value

Remove BDVs Yes
Remove additional documents No
Remove firmware packages No
Remove site configurations No
Remove reports No
Remove proposed input texts No
Remove site property templates No
30 | 406
Installation
3
Uninstallation and installation

w The executable installation file for the engineering tool set is saved to your PC.
1. Windows 7: Open the Command Prompt:
– Click on the Start button.
– Enter 'Command Prompt' in the search field and click on Command
Prompt.
a The Command Prompt is opened.
2. Windows 8.1: Open the Command Prompt:
– Switch to the app screen. Use the mouse to click on the arrow at the
bottom edge of the screen.
– Navigate to the 'Windows System' category on the app screen.
– Select the Windows System under 'Command Prompt'.
a The Command Prompt is opened.
3. In the Command Prompt, navigate to the drive on which the executable
installation file is saved, e.g., by entering 'C:'.
4. Enter 'cd' to navigate to the file path where the executable file is saved, e.g.,
'cd Users\User1\Downloads'.
5. Run the installation file using the default parameters:
– Enter the character '>', the name of the installation file, and the sequence of
characters '/S', e.g., '>F-F-FX2030-GB_en_1-7.0.0.R.exe /S'.
a The software starts to uninstall earlier versions and install the required
engineering tool set.
a The progress is displayed on the Command Prompt.
a Engineering Tool launches automatically following installation.
3.3.2 Installation with modified parameter values
Pay attention to the information regarding validation and the error log file when
generating parameter commands. Link [➙ 34]
You can pre-configure the parameter commands with an installation file.
Link [➙ 32]
l Proceed as for the default installation and enter the required parameters after
the '/S' sequence of characters. Separate each parameter command with a
space.
The table below shows the commands for changing the individual parameters. 'new
value' represents the new parameter value.
Parameters Command
Installation path /INSTALL_DIR="new value"
Data path /SHARED_DATA_DIR="new value"
Engineering Tool interface language on /TOOL_LANGUAGE="new value"
initial start-up
BDV language on initial start-up /BDV_LANGUAGE="new value"
Launch Engineering Tool after /START_TOOL=yes/no
installation
31 | 406
Installation
Values for Engineering Tool interface language and BDV language

Bulgarian (bg), Chinese (zh_CN), Croatian (hr), Czech (cs), Danish (da), English
(en), English (en_CA), English (en_GB), English (en_IE), English (en_US),
Estonian (et), Finnish (fi), Dutch; Flemish (nl), Flemish (nl_BE), French (fr_BE),
French (fr_CA), French (fr_CH), French (fr_FR), German (de), German (de_AT),
German (de_CH), German (de_DE), Greek (el), Hebrew (iw), Hungarian (hu),
Italian (it_CH), Italian (it_IT), Lithuanian (lt), Norwegian (no), Polish (pl), Portuguese
(pt), Portuguese (pt_BR), Romanian (ro), Russian (ru), Serbian (sr), Slovak (sk),
Slovenian (sl), Spanish (es), Spanish (es_ES), Swedish (sv), Turkish (tr), Ukrainian
(uk)
Examples
/TOOL_LANGUAGE="French (fr_BE)"
/BDV_LANGUAGE="Dutch"
See also
2 Installation with initialization file [➙ 32]
3.3.3 Uninstallation with modified parameter values
Pay attention to the information regarding validation and the error log file when
generating parameter commands. Link [➙ 34]
You can pre-configure the parameter commands with an installation file.
Link [➙ 32]
l Proceed as for the default installation and enter the required parameters for
uninstallation after the '/S' sequence of characters. Separate each parameter
command with a space.
The table below shows the commands for changing the individual parameters. 'new
value' represents the new parameter value.
Parameters Command
Remove BDVs /REMOVE_BDVS=yes/no
Remove additional documents /REMOVE_ADD_DOCTOS=yes/no
Remove firmware packages /REMOVE_FIRMWARE=yes/no
Remove site configurations /REMOVE_SITES=yes/no
Remove reports /REMOVE_TRACES=yes/no
Remove proposed input texts /REMOVE_QUICKTEXTS=yes/no
Remove site property templates /REMOVE_SITEINFO=yes/no
The sequence of the parameter commands is not important.
3.3.4 Installation with initialization file

You can pre-configure the parameter commands for the installation and
uninstallation in an initialization file (.ini). The file is called up during installation and
the commands saved on it are executed.
32 | 406
Installation
3
3.3.4.1 Creating an initialization file
NOTICE
Data will be deleted if the installation file is incorrect
The parameter commands will be ignored if the installation file is not formulated
correctly. No error message will be shown. The default parameters will be used.
Data may be deleted during automatic uninstallation.
● Ensure that the initialization file is correctly formulated.
The example below shows the structure of an initialization file including all the
possible parameter commands and default values.
[Remove components at uninstall]

REMOVE_BDVS=yes
REMOVE_ADD_DOCTOS=no
REMOVE_FIRMWARE=no
REMOVE_SITES=no
REMOVE_TRACES=no
REMOVE_QUICKTEXTS=no
REMOVE_SITEINFO=no
[Install parameters]
INSTALL_DIR="C:\Program Files (x86)\Siemens\F-FX2030\XL_en_x-Vx.x"
SHARED_DATA_DIR="C:\ProgramData\Siemens\F-FX2030"
TOOL_LANGUAGE="English (en)"
BDV_LANGUAGE="English (en)"
START_TOOL=yes
Table 2: Example structure of an initialization file with default values
Proceed as follows to create an initialization file.

1. Open a text editor, e.g., the editor in Word.
2. Create the required parameter commands as shown in the example and enter
the required parameter values.
3. Save the file as an ini file.
Important information about the initialization file:
● No slashes '/' must be used in front of parameter commands in the initialization
file.
● If the same parameter commands are transferred to the Command Prompt and
an initialization file is called up at the same time, only the parameter commands
from the initialization file will be taken into account.
● You do not have to define all parameters in the initialization file. The default
value is set for undefined parameters.
● If there is no earlier version of the engineering tool set installed on the PC, the
parameters for the 'Remove components at uninstall' section will be ignored.
33 | 406
Installation
3.3.4.2 Calling up an initialization file

w You have created an initialization file that includes all the necessary parameter
commands.
l Proceed as for the default installation and enter the command '/FILE="answer
file"' after the '/S' sequence of characters, where 'answer file' must contain the
path and the name of the initialization file, e.g., '>F-F-FX2030-GB_en_1-
7.0.0.R.exe /S /FILE="C:\Users\User1\answerfile.ini"'.
3.3.5 Validation and error log file

You must formulate the parameter commands correctly using the following rules:
● The paths must be correct and complete.
● The installation path and the data path must end with the ID of the engineering
tool set, e.g., XL_en-1-V1.0.
● The installation path and the data path must not be the same.
● There must be sufficient memory for the installation files on the hard disk. See
the chapter 'System requirements [➙ 28]'.
● The Engineering Tool interface language and the BDV language must be valid
and correctly formulated.
If a parameter command contains an invalid value, e.g., an invalid path or an
invalid language, the installation will be interrupted and an error log file created.
The error log file is saved in the same directory as the executable installation file.
The Command Prompt will inform you if the installation has failed. If the
installation is interrupted due to an error, the path for the error log file will be
displayed.
34 | 406
Installation
IP settings for several network cards
3
3.4 IP settings for several network cards

To connect to a ↑ 'Station' via the FS20 network or directly to the 'Station', you can
use an additional network card on the PC, for example, a 'USB to Ethernet
adapter'.
If you use more than one network card on the PC and all are set for DHCP, you
must observe the following points:
● Once the data has loaded from the PC to a 'Station', the standard gateway for
the Intranet/Internet can be overwritten when initializing a 'Station' or
disconnecting a connection to a 'Station'.
● You can specify the IP settings for the connection to the FS20 network
manually.
● For manually specified IP settings for the FS20 network, there is no conflict
with a DHCP server in the FS20 network.
Manually specifying IP settings

1. Change the IP settings for the network card with which you are establishing the
connection to the FS20 network from DHCP to manual.
2. Enter one of the following IP addresses.
– For direct connection to the ↑ 'Station': 192.168.200.5 / 255.255.255.0
– For access via the FS20 network: 192.168.201.5
a IP settings are manually specified.
a Network settings for the Intranet/Internet are not overwritten.
If you have manually specified the IP settings for the FS20 network, you must
also change the manually specified network settings when changing the
connection between a direct connection to the ↑ 'Station' and access via FS20
network.
3.5 Starting Engineering Tool

You can start Engineering Tool as follows:
● Click the software symbol on the desktop.
● In the task bar, click on 'Start' > 'Programs' > 'Siemens' > 'FX2030' > [Version] 1
> 'F-FXS2002'.
1 [Version] = Version of the software
If you are starting SintesoWorks for the first time, you will need to load the license.
Otherwise the functions of SintesoWorks are not available.
License test
The licenses are checked when SintesoWorks is started. When no objection or
warning messages appear, the licenses are valid.
The following objection or warning messages may occur:
● Warning that there are no valid licenses. This warning occurs after
SintesoWorks has been started for the first time.
● Warning that the validity has expired.
● Warning that the validity will expire.
● Objection that the licenses have been manipulated, e.g. date changed on the
PC.
See also
2 Lifecycle Responsibility Concept (LRC) [➙ 47]
35 | 406
Installation
3 Exit Engineering tool
3.6 Exit Engineering tool

You can exit Engineering Tool as follows:
● In the menu bar, click on 'File' > 'Exit'.
● Click on the 'X' button in the title bar.
If you have made changes to the software and not saved these, you are asked if
you wish to save them.
36 | 406
Software administration
Engineering tool set: File name and version
4
4 Software administration
4.1 Engineering tool set: File name and version

File name format:
[Prefix]-[Country]_[Language]_[Sales channel]-[Meta data version].R.exe
Example: F-FX2030-GB_en_1-7.0.0.R.exe
Designation Coding
Prefix F-FX2030
Country Double digit, in accordance with ISO 3166-1 ALPHA-2
Language Double digit, in accordance with ISO 639-1:2002
Sales channel Single digit, numerical (1-4)
Meta data version Three levels separated by full stops: Major, minor, bugfix
Numerical, any number of points per level
R Release
.exe File extension, upper-case or lower-case letters
4.2 BDV: File name and version

File name format:
[Prefix]-[Country]_[Language]_[Sales channel]-[Meta data version]_[↑ BDV
version]([Variant]).eBDV
Example: F-FXS2004-GB_en_1-60.8.1_01.eBDV
Designation Coding
Prefix F-FXS2004
↑ BDV version Double digit, numerical with leading zero when applicable
Variants Optional, single digit, only CAPS
.eBDV Extension of every BDV, upper-case or lower-case letters
The file name of a ↑ BDV must not be changed by the user.

BDVs with file names which do not correspond to the format cannot be used by
the software.
See also
2 BDV import [➙ 46]
37 | 406
4 Firmware: File name and version
4.3 Firmware: File name and version

File name format:
[Prefix]-[Country]_[Language]_[Sales channel]-[Meta data
version]_([Variant])_[Firmware version].zip
Example: F-FXS2001-XE_xx_x-60.7.0_00.zip
Designation Coding
Prefix F-FXS2001
XE: Several countries
xx: All languages
x: All sales channels
Variants Optional, multiple digits, upper-case letters, lower-case
letters, numbers and '-'
Firmware version Double digit, numerical with leading zero when applicable
.zip Extension of every firmware, upper-case or lower-case
letters
The file name of the firmware must not be changed by the user.
Firmware with file names which do not correspond to the format cannot be used
by the software.
See also
2 Resources import [➙ 47]
4.4 Pre-settings
You can specify presettings for the software in the 'General' window.
The pre-settings are described in the following chapters.
Specifying presettings
1. In the menu bar, click on 'Options' > 'Preferences'.
a The 'General' window opens.
2. Click on a view in the window on the left.
a The presettings for this view are displayed in the window on the right.
3. Select the presettings you want and click on 'Apply'.
a The presettings are saved.
38 | 406
Pre-settings
4
Restore default settings

1. Click on the desired view on the left in the 'General' window.
2. Click on 'Restore defaults'.
a The standard settings in the selected view are restored.
Software paths
If you change program paths then you must move the respective folder manually
to the new location.
If, during installation of the software, no other path has been entered, then the
shared data directory is in the following path:
C:\Documents and Settings\All Users\
Application Data\Siemens\F-FX2030\[Version] 1
1 [Version] = Version of the software, e.g., EN_en_1-V1
The common data directory contains the following subfolders:

● 'Additional_Documents'
● ↑ 'BDV'
● 'FS20_SW'
● 'Help'
● 'Logfiles'
● 'Sites'
● 'Technicalfiles'
4.4.1 General
The following can be set in the 'General' view:

● 'Number of recently opened files:': Number of files that were recently opened
and that are displayed in the 'File'.
● 'Automatically open last site at tool startup': If the checkbox is checked, the
↑ 'Site' that was opened last is loaded when the program starts.
● 'Additional documents directory:': Path to the folder where additional
documents can be stored, e.g., country-specific information, application
guidelines, or product information.
● 'Tool language:': Selection of the language for the program interface.
See also
2 Assigning elements [➙ 85]
39 | 406
4 Pre-settings
4.4.2 Commissioning
The following can be set in the 'Commissioning' view:

'Automatic backup embedded configuration': If the checkbox is activated, then the
configuration which is currently saved in the ↑ 'Site' will be loaded into the PC and
saved as a backup. This procedure is carried out automatically each time that you
load a configuration from the PC into the 'Station' with the command 'Download
site'.
You will find additional information for the creation of a backup file in document
009052. See chapter 'Applicable documents'.
See also
4.4.3 Assign
The following can be set in the 'Assign' view:
Assign dialog settings

● 'Auto-selection of the type in the Assign dialog': These settings relate to the
behavior in the 'Assign dialog', 'New cause dialog', and 'New effect dialog'
windows. If the checkbox is activated, the first assignable element is found and
displayed in the window automatically. If the checkbox is deactivated, you must
first select a category in the window on the left. Then the first assignable
element of this category is displayed in the window on the right.
● 'Enable display of errors and warnings in the assign dialog tree': If the
checkbox is checked, error messages and warnings are displayed in the
'Assign dialog'.
40 | 406
Pre-settings
4
Data Matrix code reader settings

● 'Use Data Matrix Code reader': If the checkbox is activated, you can use a
reading device to read in the Data Matrix codes on a layout plan. During this
process, the device type and the serial number of the devices are read-in.
● 'Port:': Port for the reading device
The following can be set in the 'Serial communication parameters' category:
● 'Baud rate:': The baud rate specifies the symbols to be transferred per time
unit.
● 'Parity bits:': Type of parity control coding
● 'Data bits:': Amount of data for transfer
● 'Stop bits:': Data transfer stop bit
● 'enable DTR': If the checkbox is activated, the ready state of the destination
data terminal will be indicated by an interface control signal.
● 'enable RTS': If the checkbox is activated, the ready state of the sending data
terminal will be indicated by an interface control signal being sent to the
destination data terminal.
The settings of the 'Serial communication parameters' do not apply for reading
devices with USB-COM port.
The settings only go into effect when you reopen the 'Assign dialog' window.
See also
2 Assignment with Data Matrix code [➙ 88]
41 | 406
4 Pre-settings
4.4.4 Editing
The following can be set in the 'Editing' view:

● 'Quicktext proposals filtration style': To make entering texts in SintesoWorks
easier, texts that have already been entered are listed as proposed texts.
– 'first letters': First letters are compared.
– 'contain string': The letter sequence at any position in the word is
compared.
● 'Maximum proposals count': Number of proposed texts that are saved.
● 'Reset proposals': Delete existing proposed texts.
● 'Edit proposals': Enter or edit proposed texts.
● 'Import proposals': Import proposed texts in the '.properties' format.
● 'Export proposals': Export proposed texts in the '.properties' format.
● 'Ignore mouse wheel': If you check this checkbox, the mouse wheel of the
computer mouse will be deactivated. This prevents settings in a drop-down list
being unintentionally changed if you are scrolling in the detail editor with the
mouse wheel.
The setting 'Ignore mouse wheel' does not go into effect until you select a new
element in the structure tree. The setting is not yet adopted for the currently
selected element.
See also
2 Entering quicktext [➙ 81]
4.4.5 Firmware package
In the view 'Firmware package', you can define the path to the folder in which
firmware files are saved. This folder also stores files that are imported using the
'Import new resource package' function.
See also
42 | 406
Pre-settings
4
4.4.6 Help
In the 'Help' view, you can define the path to the folder in which help files are
saved. This folder also stores files that are imported using the 'Import new resource
package' function.
See also
4.4.7 Internet
The 'Internet' view contains details for Internet access to the ↑ LRC web server.
The Internet access is used for loading, renewing or returning the licenses. You
have three options:
● Without proxy: The checkbox 'Enable proxy' is unchecked.
● Via proxy: The checkbox 'Enable proxy' is checked. The information on 'Proxy
host:' and 'Proxy port:' is provided by the IT administrator.
● Via proxy with authentication: The checkboxes 'Enable proxy' and 'Enable
proxy authentication' are checked.
Please ask your IT administrator about the access method you should use and
whether 'MTU size for DSL connection:' needs to be adapted.
See also
43 | 406
4 Pre-settings
4.4.8 LRC web server
The following can be set in the 'LRC server' view:

● 'LRC server URL:': The URL for the ↑ LRC web server
● 'Server user name:': The user name for the LRC web server
● 'Server password:': The password for the LRC web server
The user name and password are saved here by clicking on the 'Remember user
name and password' option in the 'License wizard' window.
'Traceability'
The following can be set in the 'Traceability' view:

● 'Always try upload at startup': If there is an Internet connection, LRC data is
loaded to the LRC server automatically when the Engineering Tool starts.
● 'Enable background trace upload': If there is an Internet connection, LRC data
is loaded to the LRC server automatically in the background.
See also
4.4.9 Periphery update
In the 'Periphery update' view, the ports for updating the peripheral devices can be
defined:
● For devices that are connected directly to the COM port.
● For devices that are connected via USB or FDUZ22x.
The settings are automatically set as standard when a device is updated.
44 | 406
Pre-settings
4
4.4.10 SintesoView
The following can be set in the 'SintesoView' view:

● 'Connect SintesoView automatically to the last connected station when opening
SintesoView taskcard': If the checkbox is activated, then SintesoView will be
connected automatically when you open the 'SintesoView' task card. The
connection is made with the most recently connected ↑ 'Station'. The
connection must be set up once manually after SintesoWorks has started.
● 'SintesoView favorite list': In this list, you can save frequently used 'Stations'
with the connection details. The 'Stations' in the Favorites list are listed in the
'SintesoView' > 'Connect to favorite' menu. This makes it possible for you
SintesoView to connect quickly and easily with 'Stations'.
● 'Add new favorite': Adding new 'Station' to the Favorites list.
● 'Edit selected favorite': Edit 'Station' in the Favorites list.
● 'Delete selected favorite': Delete 'Station' from the Favorites list.
Adding new ↑ 'Station' to the Favorites list

1. Click on 'Add new favorite'.
a The 'Add new favorite station' window opens.
2. Enter the name, IP address, 'Station' ID, and PIN of the 'Station'.
45 | 406
4 BDV import
3. Click on 'OK'.
a The 'Station' is added to the Favorites list.
a In the task card 'SintesoView', the 'Station' are listed in the 'SintesoView' >
'Connect to favorite' menu.
See also
2 SintesoView [➙ 67]
2 Connecting SintesoView [➙ 112]
4.4.11 Site
The following can be set in the 'Site' view:

● Path to the folder where the ↑ 'Sites' are stored.
● Path to the ↑ 'BDV' folder: This folder contains the BDV that was included
when the software was installed or that has been imported using the 'Import
new BDV' function. This folder may contain more than one BDV.
● Preferred BDV language: This selection determines which BDV language is
displayed if the BDV contains several languages. If the preferred language is
not included in the current BDV, English is used as standard.
4.5 BDV import

A ↑ BDV can be made available in File by clicking on the 'Import new BDV' >
'SintesoWorks' menu item. During this import process, the BDV is saved into the
standard BDV path from a selectable location.
All imported BDVs are kept in a list which indicates the BDVs permitted for
producing a new ↑ 'Site' or changing an existing 'Site'.
When importing a new ↑ BDV, you will be asked whether you wish to delete old
BDVs.
Existing ↑ 'Sites' have saved the BDV used with the 'Site' data and do not need
access to the BDV in the aforementioned standard BDV path. You can therefore
delete old BDVs if you do not wish to create any 'Sites' with old BDVs or convert
'Sites' into an old BDV.
See also
2 BDV: File name and version [➙ 37]
46 | 406
Resources import
4
4.6 Resources import

New resources can be made available in File by clicking the menu item 'Import new
resource package' > 'SintesoWorks'. The following resources can be imported:
● Firmware
● Peripheral firmware
● Help file
The resources are identified by their file name and file extension and saved in the
corresponding standard directories. The standard directories can be defined in the
'Options' > 'General' menu.
See also
2 Firmware: File name and version [➙ 38]
4.7 Lifecycle Responsibility Concept (LRC)

With the Lifecycle Responsibility Concept (LRC), the licensing and the 'Site' data
storage are regulated. For this, the ↑ LRC web database is used, a web application
in SintesoWorks.
Licensing
Each organizational unit receives its own licenses for its users of SintesoWorks.
The user must be registered on the LRC web server. Users may load their licenses
using a tool function. The licenses are valid for three, six or twelve months. Before
the expiry of the license, the user must renew it.
Two licenses are required:
● The primary license makes it possible to work with SintesoWorks.
● The default license enables the communication between the 'Stations'.
'Site' data storage

The user of SintesoWorks must regularly, e.g. monthly, store a parts list of the
'Sites' he has created on the LRC web server. There is a function for this in
SintesoWorks.
See also
2 Saving a parts list for the 'Site' [➙ 53]
4.7.1 Loading / renewing licenses

You may load licenses with the 'Retrieve your licenses.' option.
The 'Renew your licenses.' option can be used to renew licenses soon before or
after they expire. This option can be selected at the earliest 60 days before the
licenses' expiration date.
Loading or renewing licenses online

w You have an account on the ↑ LRC web server.
w You are a member of a registered organizational unit.
w You have received an e-mail with the required information (URL, user name,
password).
1. Launch Engineering Tool.
2. In the menu bar, click on 'File' > 'Manage licenses'.
a The following window is opened:
47 | 406
4 Lifecycle Responsibility Concept (LRC)
3. Select 'Manage your licenses online (recommended).'.

4. Select 'Retrieve your licenses.' or 'Renew your licenses.'.
5. Click on 'Next'.
48 | 406
Lifecycle Responsibility Concept (LRC)
4
6. Enter your user name and the password and click on 'Finish'.
a The connection with the LRC web server is established.
a The user name and the password are authenticated.
a The licenses for the corresponding software version of SintesoWorks are
generated.
a The following window opens and the installed licenses are listed:
7. Click on 'Restart tool'.

a SintesoWorks is restarted.
49 | 406
Loading or renewing licenses offline

If you do not have a connection with the LRC web server you will have to load or
renew the licenses off-line.
w You know the installation code. You find the installation code under 'Help' >
'About'.
1. Contact the HQ Administrator by phone or email to apply for the licenses.
a The HQ Administrator then checks the membership of your organizational
unit and verifies whether other installation codes are registered with the
same user account.
a The HQ Administrator creates the identities, generates the licenses and
sends you the files on a CD or by e-mail.
The following window opens:
3. Select 'Manage your licenses offline (for this option, please contact your
administrator).' and 'Install your licenses.'.
4. Click on 'Next'.
a The following window opens and the installation code is displayed.
50 | 406
Lifecycle Responsibility Concept (LRC)
4
5. Click on 'Browse' and select the license file.

6. Click on 'Finish'.
a The licenses for the corresponding software version of SintesoWorks are
generated.
a The following window opens and the installed licenses are listed:

a SintesoWorks is restarted.
51 | 406
4.7.2 Returning licenses

If SintesoWorks is being installed on a new PC, the licenses on the previously used
PC must be returned and then reloaded on the new PC.
Returning licenses online

w SintesoWorks is still installed and the licenses have not expired.
w The previously used PC is not defective.
a The 'License wizard' window opens.
2. Highlight 'Manage your licenses online (recommended).'.
3. Highlight 'Uninstall the current licenses.'.
4. Click on 'Next'.
a The 'License wizard' window for entering the password is opened.
5. Enter your user name and the password and click on 'Finish'.
a The connection with the ↑ LRC web server is established.
a The user name and the password are authenticated.
a The LRC web server is informed about the return of the licenses.
a The installation code is deleted from the user profile.
a The license data on the hard disk is deleted.
a The 'License wizard' window is opened along with the confirmation
message.
a SintesoWorks is restarted with the message 'Licence missing'.
Returning licenses offline

If you are not connected to the LRC web server or the previously used PC is
defective, the licenses must be returned offline.
1. Inform the HQ Administrator by phone or E-mail about the PC change and
state the installation code of the new PC.
a The HQ Administrator accepts the change and changes the installation
code in the user profile on the LRC web server.
2. Uninstall SintesoWorks.
4.7.3 Display licensing information

You can display information about the installed licenses as follows:
1. Select 'Help' > 'About' from the menu bar.
2. Click in the new window on the following button:
a The 'Installed licenses' window opens.

a Information about the installed licenses is displayed, e.g. expiration date and
license keeper.
52 | 406
License key
4
4.7.4 Installing several different engineering tool sets

Several engineering tool sets with different country or language versions can be
installed on one PC.
w You have downloaded two engineering tool sets, A and B, from the ↑ LRC web
server or received them on a data carrier.
1. Install engineering tool set A.
2. Load the licenses for organizational unit A from the LRC web server for
engineering tool set A.
3. Install engineering tool set B.
4. Load the licenses for organizational unit B from the LRC web server for
engineering tool set B.
4.7.5 Saving a parts list for the 'Site'

You can save a parts list of the currently loaded 'Site' by loading the files on to the
↑ LRC web server.
l Select 'File' > 'Upload traceability report' from the menu bar.
a SintesoWorks is connected with the LRC web server.
a The parts list of the currently loaded 'Site' is loaded on to the LRC web server.
4.8 License key

↑ License keys are needed to enable ↑ stations for network functions. A maximum
of one license key can be installed in each 'Station'.
Some examples of network functions are:
● SintesoView
● ↑ BACnet for ↑ management stations
● Sinteso Mobile
● Sinteso Touch PC
You will find more information about ↑ license keys in document 008843. See
chapter 'Applicable documents'.
4.9 Calling up log files of Engineering Tool

You can open the directory containing the log files of Engineering Tool via the start
menu:
● Start > All Programs > Siemens > F-FX2030 > [Version] 1 > Log files
1 [Version] = Version of the software
53 | 406
GUI
5 Overview of the program window
5 GUI
5.1 Overview of the program window
1 Title bar 6 Hyperlinks

2 Menu bar 7 Status bar
3 Task cards 8 Tree
4 Table 9 Toolbar
5 Detail editor
54 | 406
GUI
Menu bar
5
5.2 Menu bar

The menu structure and menu items are fixed for each task card. Individual menu
items may be shaded out depending on the task card selected. Menu items that
can not be run are shaded gray.
There are the following main menus and submenus:
Main menu Submenu Description

File New site Create new 'Site'
Open Open the existing configuration of a 'Site'
Save Save the current configuration of the 'Site'
Save as ... Save the current configuration under a new name
Site properties Display and edit 'Site' properties
Close Exit the currently open configuration
Manage licenses Load, renew or return a license
Import new BDV Import ↑ BDV
Import new resource package Import of the following packages: Firmware, help
Upload traceability report Load the parts list of the currently loaded 'Site' on the
↑ LRC server
SiB-X export Export configuration data in SIB-X format
Reports Create reports via the 'Site'
Site export (XML) Export the 'Site' in XML format
Compare sites Compare configurations or BDVs
CSV import Import data in CSV format
CSV export Export data in a CSV file
Show CSV import log Displaying the protocol of the CSV import
[List of the most recently Open one of the most recently opened 'Sites'
opened 'Sites']
Exit Exit SintesoWorks
55 | 406
GUI
5 Menu bar

Edit New station Create new 'Station'
New station with address Creating a new 'Station' with individual address entering
New element Create new element
Undo Undo the last action
Redo Restore the last undo action
Copy Copy elements or values
Cut Cut elements or values
Paste Paste elements or values
Paste without children Paste element without child elements
Delete Delete element
Combi delete Can only be executed in the task card 'Hardware'. Deletes
element along with referenced logical element.
Replace element Replacing element
Show replace element log
Change element address: -1 Decrease the address of the selected element as well as all
higher elements by one
Change element address: +1 Increase the address of the selected element as well as all
higher elements by one
Merge sites Merge two 'Sites'
Exchange logo in site Change display logo
Convert site Convert the configuration of the 'Site'
Show conversion log Display the conversion log
Import lines... Transferring lines from other existing systems
Remove import information Reset from migration mode to normal mode
Show import log Shows the log file
View Find Find elements by different search criteria
Find and replace Find and replace elements by different search criteria
Find next Jump from one hit to the next
Progress Open the 'Progress' window
Show problems Displaying problems of an element
Show all problems Displaying problems of the entire 'Site'
56 | 406
GUI
Menu bar
5

Commissioning Assign Open the 'Assign' window to assign elements
Unassign ↑ Delete assignment
Create and Assign Open the 'Create and Assign' window to simultaneously
create and assign devices
Disconnect Interrupt communication to 'Station'
Initialize station Initialize 'Station'
Download site Load.the configuration of the 'Site' in the 'Station'
Upload site Load configuration of the 'Site' to the PC
Create backup embedded Create a backup of the'Site' configuration
configuration
Upload site event memory Load the event memory of the 'Site' to the PC
Upload site log files Load the log files from the selectable 'Stations' to the PC
Diagnostics report Create reports via the 'Site'
Handover site Transfer the configuration of the 'Site' to a third-partySite'
Handover station Transfer the identity of a 'Station' to a third-partyStation'
Update Periphery update wizard Update the firmware of peripheral devices
Disconnect Disconnect the connection to the station
FW update main CPU Update the firmware of the main CPU
FW update additional CPUs Update the firmware of the additional ↑ CPUs
FW update main and Updating the firmware of the main CPU and the additional
additional CPUs CPUs
SintesoView Connect Connect SintesoView
Connect to favorite Connect SintesoView with 'Station' from the Favorites list
Add to favorites Add connected 'Station' to the Favorites list
Disconnect Disconnect SintesoView
Network Reset network configuration Set standard values for the IP addresses and network
masks of all sub-nets. Overwrite all manual changes to
these values.
Reset sub-net network Set standard values for the IP addresses and network
configuration masks of all selected sub-nets. Overwrite all manual
changes to these values.
Convert to GAP See chapter 'Site configuration, status MP2.1 [➙ 394]' for
Convert to SAFEDLINK host site configuration (↑ BDV <32)
Convert to ethernet host
Create GAP configuration
Options Preferences Set the software pre-settings
Help Help Display documentation
View additional documents View additional documents
&Show shortcuts Show keyboard shortcut
About Display details of the installed version
57 | 406
GUI
5 Toolbar
5.3 Toolbar
The toolbar allows the operator to access functions quickly.
The following functions can be run directly via the toolbar:
Symbol Menu Item Description

'New site’ Opens the 'Create new site' window
'Open' Opens existing 'Site'
'Save' Saves the current configuration of the 'Site'
'Reports' Opens the 'Reports' window
'Copy' Copies selected elements or values
'Cut' Cuts selected elements or values
'Paste' Pastes copied elements or values
'Paste without Pastes copied elements without children
children' elements
'Delete' Deletes selected elements/subtrees
'Undo' Undoes the last action
'Redo' Restores the most recent action that was
undone
'New station' Opens and closes the 'New station' window
'New element' Opens and closes the 'New element' window
'Open progress view' Opens and closes the 'Progress' window
'Find' Opens the 'Find' window
'Help' Opens the documentation overview
'Download site' Loads the configuration of the 'Site' to the
'Station'
'Upload site' Loads the configuration of the 'Site' to the PC
'Assign' Opens and closes the 'Assign' window for
assigning elements
'Create and Assign' Opens and closes the 'Create and Assign'
window for simultaneous creating and
assigning of devices
58 | 406
GUI
Help and tooltips
5
5.4 Help and tooltips

There are two sources of information in SintesoWorks:
● Help
● Tooltips
Help
There are three ways of calling up the Help function:
● Press <F1>.
● Select 'Help' > 'Help' from the menu bar.
● Click on the symbol in the toolbar.
A PDF document containing an overview of the documentation opens. To open a
document, click on its name in the overview.
Tooltips
Tooltips are windows within the software with context-sensitive detail information.
Tooltips are shown when the mouse pointer is moved over a element designation
or element property in the detail editor.
Figure 1: Example for the Tooltip of an element property

To display the Tooltip of an element, proceed as follows:
1. Highlight an element in the tree view.
a The element and its properties are displayed in the detail editor.
2. In the detail editor, move the mouse pointer over the element designation in the
uppermost tab.
a The Tooltip is displayed.
Figure 2: Example for the Tooltip of an element
59 | 406
GUI
5 Template for customer data
5.5 Template for customer data

When creating a new ↑ 'Site', a form for entering customer-specific data opens in
the 'Create new site' window.
The data that is entered in the 'Creator:' section can be saved as the standard
template by clicking 'Set creator values as default'.
See also
2 Creating a new 'site' [➙ 74]
5.6 Task cards

The task cards show different perspectives of a ↑ 'Site' in the program window.
The 'Site' is configured in the perspectives.
Every task card has a name and its own icon. The particular perspective is shown
when a task card is clicked.
Figure 3: Task cards

SintesoWorks has the following task cards:
● 'Hardware': Configuration and display of all hardware components of a 'Site'
● 'Detection': Configuration and display of the detection applications
● 'Control': Configuration and display of the control applications
● 'Operation': Configuration and display of the global 'Site' settings and of the
operating properties of all operating and display devices within the 'Site'
● 'Network': Configuration and display of the network
● 'SintesoView': With 'SintesoView', a 'Station' connected to the PC can be
viewed or viewed and operated.
See also
2 Overview of the program window [➙ 54]
60 | 406
GUI
Task card components
5
5.7 Task card components

Each task card has the following components:
● Structure tree
● Table
● Detail editor
● Hyperlinks
Structure tree
The display and function of the structure tree correspond to the structure tree in
Windows Explorer. Each element in the structure tree is displayed using an icon
and text.
The elements contain configuration data.
The root element of each structure tree is the ↑ 'Site' element.
Problems and special instructions are shown with red and yellow exclamation
marks in the structure tree.
You will find more information in chapter 'Error indication and problem
identification [➙ 65]'.
Table
The child elements of the highlighted element in the tree are shown in the table. If
a highlighted element in the structure tree has no child element, the table remains
empty.
The table provides a selection of the most important properties of the child
elements.
Elements that can not be edited are shaded gray.
Detail editor
The detail editor shows properties of an element or several highlighted elements
within the table or the structure tree. If no element in the table is highlighted, the
properties of the element highlighted in the structure are shown.
The properties of an element are depicted in various tabs. If an element is
assigned, then an additional tab will be displayed with the designation of the
assigned task card. This tab contains the properties of the 'Overview' tab of the
assigned element.
Hyperlinks
Hyperlinks are shown in the lower part of the detail editor, provided that the
selected element is assigned to other elements.
The view changes to the assigned element of the corresponding task card by
clicking on a hyperlink.
5.8 Scroll bars and window separating lines

Control elements in the software, e.g. scroll bars and window separating lines,
correspond to the Windows standard.
Scroll bars are automatically displayed as required and each window can be
expanded and minimized at a window separating line.
61 | 406
GUI
5 Expanding and collapsing the elements in the structure tree
5.9 Expanding and collapsing the elements in the

structure tree
An element with subtree can be expanded or collapsed according to functionality in
Windows Explorer.
Elements in the structure tree can be expanded and collapsed as follows:
● Click on the buttons '+' or '–' next to a tree element.
● Double-click on an element.
● Highlight the element and press the right or left arrow key.
To expand or collapse all of the elements in a subtree, proceed as follows:
● Highlight the element and press <*> or </> on the numeric keypad
● Highlight the element and click on the '+' or '–' buttons on the upper right in the
structure tree.
Figure 4: Buttons for expanding and collapsing a subtree
Filtering the elements in the structure tree

The filter function is used to display certain elements when the structure tree is
expanded and collapsed. The search field for the filter function is located on the top
right of the tree structure next to the '+' and '–' buttons.
Character strings can be entered in the filter function search field. When the
structure tree is expanded and collapsed with the '+' and '–' buttons, only elements
containing the defined character string are displayed. The character strings entered
can contain the wildcard '*'.
5.10 Multiselection
Multiselection allows, e.g. entry of a customer text for several elements in one
procedure. Multiselection is possible in the table and in the tree view. Selecting one
or more lines corresponds to the Windows standard.
If several elements are selected in the tree view, nothing is indicated in the table.
The intersection of selected elements is displayed in the detail editor. If the
properties of the selected elements are different then the appropriate field is shown
in the detail editor by quadrates. Following multiselection, the tab name in the
detail editor is 'Multiselection'.
Figure 5: Multiselection
Because of dynamic loading you can select a maximum of eight 'Stations' in the
tree and table at the same time.
See also
2 Dynamic loading [➙ 70]
62 | 406
GUI
Navigating within the program window
5
5.11 Navigating within the program window

Navigation in the program window functions according to the Windows standard.
Navigation between the task cards or the perspectives of a ↑ 'Site' is specific to
SintesoWorks. Opening a perspective or changing from one perspective to the
other is possible using the following control elements:
● Task cards
● Hyperlinks
● Shortcuts
You will find information on operating elements in the following chapters.
5.11.1 Navigating with task cards

Click on a task card to switch to the corresponding perspective.
Figure 6: Task cards
See also
5.11.2 Navigating with hyperlinks

You can use hyperlinks to navigate between the task cards. If an element is
assigned, the ↑ link is indicated by a hyperlink in the bottom part of the detail
editor. The view changes to the assigned element when you click on a hyperlink.
Figure 7: Detail editor with hyperlink
See also
63 | 406
GUI
5 Status bar
5.11.3 Navigating with shortcuts

The table below lists the shortcuts.
Description Shortcut
Changing between task cards <Ctrl> + <F8>
Changing between windows of a task card <Ctrl> + <F7>
Opening and closing subtrees Left or right arrow keys
Navigating between elements in the structure tree Up or down arrow keys
Navigating between columns of the table ● Tab
● Left or right arrow keys (apart from in editing mode;
then only if the entire field is highlighted)
Navigating between lines of the table ● <Enter> or <Shift> + <Enter>
● Tab in the last column
● Right arrow key in the last column (apart from in
editing mode; then only if the entire field is
highlighted)
● Up or down arrow keys (apart from in editing mode)
Editing cells in the table <F2>
Navigating between the tabs in the detail editor ● <Ctrl> + <Page Up> or <Ctrl> + <Page Down>
● Arrow keys if the tabs are highlighted
Navigating between the parameters of a tab in the <Tab> or <Shift> + <Tab>
detail editor
5.12 Status bar

The following information is displayed on the status bar:
● The problem description of a selected element.
● A symbol for information on the connection status between 'Station' and the
PC.
Figure 8: Status bar
64 | 406
GUI
Error indication and problem identification
5
5.13 Error indication and problem identification

'Error' when loading to the 'Station'
An 'Error' prevents the configuration being loaded to the 'Station'.
The following message is displayed:
l Open the 'All problems' window to display the errors for the entire 'Site'.
Or
l Display the errors for one element.
Displaying the 'Error' for the entire ↑ 'Site'

1. Select 'View' > 'Show all problems' from the menu bar.
a The 'All problems' window opens.
a The 'All problems' window displays 'Error', 'Warning', and 'Info' entries
relating to the configuration of the entire 'Site'.
2. In the 'All problems' window, double-click on an entry to display the element.

a The respective task card opens and the element is displayed in the structure
tree.
If you activate the checkbox 'Invisible', then problems in elements will be

displayed which are not visible to the user. This can be helpful for troubleshooting
with the hotline.
65 | 406
GUI
5 Error indication and problem identification
Displaying the 'Error' for one element

l Read the information in the status bar at the bottom edge of the program
window and / or click on the information in the status bar.
Or
1. Right-click on an element with a red or yellow exclamation mark.
2. In the shortcut menu, select the 'Show problems' menu item.
Or
1. Highlight an element with red or green exclamation mark.
2. Select 'View' > 'Show problems' from the menu bar.
a The 'Problems' window opens.
a In the 'Problems' window, an 'Error', 'Warning', or 'Info' entry concerning the
element selected is displayed.
If the highlighted element has only one problem, then the problem will be
described in the status bar. If the element has several problems, then the number
of problems will be displayed in the status bar.
Figure 9: Status bar with problem description
Figure 10: Status bar with number of problems
66 | 406
GUI
SintesoView
5
'Error' and 'Warning' identification in the tree view

● Red exclamation mark next to an element: 'Error', e.g., inadmissible or
duplicate element
● Yellow exclamation mark next to an element: 'Warning', e.g., missing ↑ link
A ↑ 'Site' can be stored on the PC even if there is an 'Error'.
Figure 11: 'Error' in the tree view
See also
5.14 SintesoView
SintesoView is software for the PC which can be used to display the ↑ Person
Machine Interface of a ↑ 'Station' on the PC. For example, it can be used to access
the ↑ site for maintenance purposes.
Depending on the operation mode, SintesoView can either be used for display
purposes or for display and operation purposes.
The link between SintesoView and a 'Station' can be structured as follows:
● Local connection via any 'Station' in the system
● Connection via the Global Access Point (GAP)
SintesoView is an integrated part of SintesoWorks, but can also be installed on a
PC as the standalone application 'FXS2009'.
You will need an installed ↑ license key and appropriate authorization for the
'Station' in order to use SintesoView. The license key must support the
SintesoView function. The license key need only be installed in the 'Station' that
has the Person Machine Interface that is to be displayed in SintesoView.
You will find more information about license keys in document 008843. See
The connection to a ↑ 'Station' with a license key is also possible via a 'Station'
without a license key.
SintesoView has the same ↑ visibility as the connected 'Station'. You can
therefore gain global visibility with SintesoView in a networked ↑ site. To do so,
the license key must be installed in a ↑ 'Station' with global visibility and
connected to SintesoView.
67 | 406
GUI
5 SintesoView
SintesoView is opened via the 'SintesoView' task card in the program window.
001 AAA
001 ABC YYYY 1

ABC
ZZZ ZZZ ZZZ

ABCDEFGHI ABCDEFGHI ABCDEFGHI
Figure 12: Example for SintesoView in 'View and Operate' operation mode (red frame)
The button with the loudspeaker symbol (bottom right in the figure) is used to
switch an activated buzzer on and off.
However it is only possible to switch the buzzer on and off on the PC and not on
the connected ↑ station.
The connection with a 'Station' is shown by the ↑ Person Machine Interface

(display, LEDs, keys) transmitted.
The 'SintesoView access' operation mode is indicated by a red frame around the
Person Machine Interface.
An enable granted for SintesoView is retained when a 'Station' restarted.
SintesoView has the following operation modes:

● 'Limited access (view only)'
● 'Full access (view/operation)'
For both operation modes, an authorization must be configured on the ↑ 'Station'.
In addition, a ↑ license key must be installed. The license key must support the
SintesoView function.
You will find more information about license keys in document 008843. See
'Limited access (view only)'

In this operation mode, SintesoView indicates the same as the ↑ 'Station'
connected to it, but you cannot operate the linked 'Station'.
The figure in SintesoView indicates the display with all indicated texts, all LEDs in
their current state and all buttons.
68 | 406
GUI
SintesoView
5
'Full access (view/operation)'

In this operation mode, the connected 'Station' is visualized as in the 'Limited
access (view only)' operation mode. Additionally, the 'Station' can be operated with
SintesoView, while normal operation on the 'Station' is blocked, but can be
reactivated.
As operation on a ↑ 'Station' must have priority, this restriction (blocking) on the

'Station' can be canceled at any time.
Each time an attempt is made to operate the ↑ 'Station', a window is displayed
with the option to abort the connection with SintesoView.
The LED test also tests the display. However, the LEDs are not displayed in
'SintesoView'.
You will find more information on configuring a permanent operation mode for
SintesoView in chapter 'Configuring permanent access for SintesoView [➙ 151]'.
See also
2 Connecting SintesoView [➙ 112]
69 | 406
GUI
5 Dynamic loading
5.15 Dynamic loading

To increase the performance of 'SintesoWorks', not all 'Stations' are loaded to the
software at the same time for ↑ 'Sites' with more than eight ↑ 'Stations'. 'Stations'
that are not loaded are shown in gray and in italics. The 'Stations' are dynamically
loaded and unloaded, depending on the selection. You can load a maximum of
eight 'Stations' at the same time.
The following sections describe dynamic loading in various software functions.
Structure tree view

As soon as a ↑ 'Station' that is not loaded is clicked on, it is loaded. You can
highlight a maximum of eight 'Stations' at the same time. If you highlight more than
eight 'Stations', an error message appears.
Figure 13: Structure tree view with stations that are and are not loaded
History of the ↑ 'Stations'

Only the history of the 'Stations' that is currently loaded is displayed on the 'History'
tab of the 'Site properties' window as standard. If you would like to see the history
of all 'Stations', click on 'Get station logs'.
Search function
For the functions 'Find' and 'Find and replace', you can specify whether only the
loaded 'Stations' or not only the loaded 'Stations' but also those which are not
loaded are to be included.
Designation of problems and displaying errors

The ↑ 'Stations' that are not loaded are shown in gray in the 'All problems' window.
If you would like to view the errors and warnings of a 'Station' that is not loaded,
click on the 'Station' to load it.
70 | 406
GUI
Dynamic loading
5
'Assign' function
When elements are assigned with the 'Assign' function, the ↑ 'Stations' that are not
loaded are shown in gray. If you would like to create a ↑ link to an element of a
'Station' that is not loaded, you must click on the 'Station' to load it.
Figure 14: Window with stations that are and are not loaded
The buttons below can be used to navigate through the list of elements that can be
assigned in sequence. Elements that are not loaded are then loaded.
See also
2 Error indication and problem identification [➙ 65]
2 Finding [➙ 91]
2 Finding and replacing [➙ 92]
2 Editing 'site' properties [➙ 75]
71 | 406
Program operation
6 Creating a site
6 Program operation
It is possible that SintesoWorks will start to run slightly slower over time, e.g.,
after extensive copying / pasting or when creating / deleting a large number of
↑ 'Stations'. If this happens, we would recommend reloading the ↑ 'Site'.
SintesoWorks will then work normally again.
6.1 Creating a site

The following possibilities are open to you when you create a ↑ 'Site':
● Load existing 'Site' in SintesoWorks
● Create 'Site' based on an existing configuration
● Create new 'Site'
You will find information on the procedures in the following chapters.
6.1.1 Loading an existing 'site'
NOTICE
Unauthorized characters in the ↑ 'Site' name or in the path: < > / \ | : ? * " % #
'Site' may not be able to be saved or loaded.
● Do not use any of the following characters in the 'Site' name or in the path:
<>/\|:?*"%#
The progress of the 'Upload from station(s)' is shown in the status bar.
If communication between the PC and 'Station' is interrupted, a message
indicating that the upload has been aborted is displayed.
w The ↑ 'Site' already contains a configuration.

w The PC is connected to a 'Station'.
1. Select 'File' > 'New site' from the menu bar or click on the following button in
the toolbar:
a The first 'Create new site' window opens.

2. Select the 'Upload from station(s)' option.
3. Click on 'Next'.
a The configuration of the 'Site' is loaded in SintesoWorks.
a The second 'Create new site' window opens.
4. Enter the required information, e.g. the 'Site' name.
5. Click on 'Create'.
a The 'Site' is created in SintesoWorks.
See also
72 | 406
Program operation
Creating a site
6
6.1.2 Create 'Site' based on an existing configuration
NOTICE
<>/\|:?*"%#
w The configuration file to be copied is available on the PC.

w The configuration file has the '.fsc' extension.
1. Select 'File' > 'New site' from the menu bar or click on the following button in
the toolbar:
a The 'Create new site' window opens.

2. Select the 'Create based on existing configuration' option.
3. Select the configuration file to be copied from 'Existing configuration:'.
4. Click on 'Next'.
a The configuration file is copied.
a The 'Site properties' window opens.
5. Enter the required information, e.g. the 'Site' name.
6. Click on 'OK'.
a The 'Site' is created.
See also
73 | 406
Program operation
6 Creating a site
6.1.3 Creating a new 'site'
NOTICE
<>/\|:?*"%#
Use as a test site

To identify a 'Site' as a test site, the value 'Test site' must be set in the properties
for 'LRC site usage'. The 'Site' identified as a test site must not be used for actual
fire detection in a customer site. When site data is evaluated on the LRC server, a
distinction is made between a test site and a customer site. All site data is loaded
onto the LRC server, regardless of how it has been identified.
1. Launch Engineering Tool.
2. Select 'File' > 'New site' from the menu bar or click on in the toolbar.
3. Select the 'Create new' option.
4. Select the ↑ BDV.
5. Click on 'Next'.
a The BDV is being loaded.
6. Enter the required information, e.g., the ↑ 'Site' name. Mandatory fields are
highlighted with an asterisk (*).
7. Click on 'Create'.
a The 'Site' is created.
See also
2 Template for customer data [➙ 60]
74 | 406
Program operation
Creating a site
6
6.1.4 Editing 'site' properties
NOTICE
<>/\|:?*"%#
w The ↑ 'Site' is loaded.

1. Click on the 'File' > 'Site properties' menu item or use the shortcut <Ctrl> + <I>.
a The 'Site properties' window opens.
2. Edit the properties.
– Fields marked with '*' must be completed.
3. Select the 'Comment' tab to enter a comment.
– The comment can be max. 1000 characters long.
– Click the 'Add time and date ' button to add the current date and time. This
enables you to enter comments with a time stamp.
4. Select the 'Site' tab to display the log file of the 'History'.
75 | 406
Program operation
6 Creating a station
6.2 Creating a station

When creating the first ↑ 'Station', you can choose between 'Standalone station'
and networked 'Stations' of types 'SAFEDLINK station' and 'Ethernet station'.
When a 'SAFEDLINK station' is created, it may already be assigned to a specific
↑ SAFEDLINK sub-net.
Additional ↑ 'Stations' can only be created as networked.
Figure 15: Window to creating a 'station'
Creating 'Station'
w A ↑ 'Site' has been created.
1. Open the 'New station' window. This can be done in the following ways:
– Click on the symbol in the toolbar.

– Select 'Edit' > 'New station' from the menu bar.
– Right-click in the tree view and select 'New station' in the context menu.
a The 'New station' window opens above the table.
2. Select a 'Station' from the 'Type:' selection list.
3. Select a template from the 'Template:' selection list.
4. Select the corresponding network for networked ↑ 'Stations'.
5. Select the number of new 'Stations' in the 'Amount:' field.
6. Click on 'Add'.
a The 'Station' is created.
Networked 'Stations'
Details for creation of networked 'Stations' can be found in chapter 'Creating
networked 'Stations''.
76 | 406
Program operation
Create element
6
Creating a 'Station' with an individual address

This function is normally called up when migrating from old systems if a particular
address is to be assigned to a 'Station'.
Once the 'Station' has been created, the address cannot be changed any more.
The maximum value that can be set for the address of the 'Station' is 250.
1. Select 'Edit' > 'New station with address' from the menu bar.
a The 'New station with address' window opens.
2. Set the desired properties and click on 'Add'.

a The 'Station' is created with the address entered.
See also
2 Creating networked 'Stations' [➙ 359]
6.3 Create element

You can create an element in the following ways:
● In the 'New element' window
● Via the context menu in the tree view
● In the table
Creating an element in the 'New element' window

w A ↑ 'Station' has been created.
w An element is selected for which a sub-element can also be displayed.
w The ↑ 'Site' element is not selected.
1. Open the 'New element' window. This can be done in the following ways:
– Click on the symbol in the toolbar.

– Select 'Edit' > 'New element' from the menu bar.
– Right-click in the tree view and select 'New element' in the context menu.
a The 'New element' window opens above the table.
2. Select an element from the 'Type:' selection list.

3. Select a template from the 'Template:' selection list.
4. Select the number of new elements in the 'Amount:' field.
5. Click on 'Add'.
a The element is created.
77 | 406
Program operation
6 Create element
Creating an element via the context menu in the tree view

w A 'Station' has been created.
1. Right click on an element in the tree view below which you want to create an
element.
2. In the context menu, select the 'New' and then select the desired element and
the template.
Creating an element in the table

w A 'Station' has been created.
1. Select an element in the tree view under which you want to create an element.
2. Double-click on the 'Append ...' field in the table.
3. Select the element type with the corresponding template from the selection list.
78 | 406
Program operation
Replacing element
6
6.4 Replacing element

You can replace the template of one element with another template of the same
element type. In certain cases you can also replace an element with an element of
another type.
Replacing element
1. In the tree view, highlight the element that you wish to replace.
2. Select 'Edit' > 'Replace element' from the menu bar.
a The 'Replace element' window opens.
3. Select a different element type or a different template.
4. Click on 'Replace'.
a The element is replaced.
5. Check the settings and the ↑links of the new element and make changes, if
necessary.
Using the 'Replace element' function for 'Stations' converts the 'Stations'. You will
find more information in chapter 'Converting a station [➙ 121]'.
6.5 Delete element

An element can be deleted in the tree or in the table. The subtree of the element is
also deleted when an element is deleted. If the element that is to be deleted is
referenced in other elements, for example in a ↑ link to 'Causes' in a control, a
message appears indicating that the references will be deleted at the same time. If
an assigned ↑ logical channel is deleted, the physical channel is no longer
assigned.
You can delete an element as follows:
● Using the button in the toolbar
● Using 'Edit' > 'Delete' in the menu bar
● Via the context menu
● With <Delete>
79 | 406
Program operation
6 Editing elements
6.6 Editing elements

Elements can be edited in the table or detail editor. Editing is not possible in the
tree view.
Editing an element in the table

1. In the tree view, select the parent element of the element that you wish to edit.
a The child element and its properties are displayed in the table.
2. Edit the properties of the element in the table.
Editing elements in the detail editor

1. In the tree view, select the element that you wish to edit.
a The properties of the highlighted element are displayed in the detail editor.
2. Edit the desired properties.
Editing several elements simultaneously

1. In the tree view, select the elements that you wish to edit.
a The properties that are available in all the highlighted elements are
displayed in the detail editor.
2. Edit the desired properties.
a The properties will be changed in all of the highlighted elements.
6.7 Table
6.7.1 Copying properties in the table

In the table, you can copy editable properties of an element, such as customer text,
into any number of adjacent cells of other elements.
Copying property
1. Click the cell with the property that you want to copy.
a The cell is marked by a frame.
2. Guide the mouse pointer to the bottom right corner of the highlighted cell.
a The mouse pointer changes to a white cross.
3. With the left mouse button pressed, drag the white cross over the cells in the
same column into which you want to copy the property.
a Highlighted cells have a gray background.
4. Release the pressed left mouse button.
a The copying process is complete.
80 | 406
Program operation
Entering quicktext
6
6.7.2 Inserting text in columns

Texts can be inserted in the table in columns from the clipboard. The texts on the
clipboard may be copies of other files, e.g., columns copied from Excel.
Example: Prepare customer texts for zones in an Excel column, copy the column to
the clipboard, and insert it in the table in Engineering Tool in column 'Customer
text'.
Inserting text in columns

w The texts required are saved in a file, e.g., in an Excel file.
1. Copy the column containing the prepared texts, e.g., the Excel column.
2. In Engineering Tool, highlight the element containing the subelements for
which you wish to insert text in columns in the table, e.g., 'Section'.
3. Right-click on the first element in the column in which you wish to insert text.
4. Select 'Paste values from clipboard' in the context menu.
a The copied texts are inserted in the column from the clipboard.
a The texts are assigned to the elements in the table in ascending order of
address.
6.8 Entering quicktext

When writing 'Customer text' and 'Intervention text' in the detail editor, as in the
table, texts that have already been used are displayed in a list when the first letter
or a matching sequence of characters is entered. You can navigate through the list
by scrolling, using the mouse, or using the Up/Down arrow keys and <Enter>. The
list is updated continually as text is entered.
See also
2 Editing [➙ 42]
81 | 406
Program operation
6 Copying, cutting, and pasting elements
6.9 Copying, cutting, and pasting elements

The functions for copying, cutting and pasting elements correspond to the
Windows standard and can be used in the tree and the table as well as between
the tree and the table.
When copying and cutting, the entire subtree of an element, if it exists, is placed on
the clipboard. Copied and cut elements can be pasted in one after another at
various positions.
When pasting, the customer text and other data are transferred. Properties,
for example the element's address, are updated according to the new position in
the tree.
Conditions
● Elements that are generated automatically when creating parent elements can
not be copied/cut separately.
● The following elements cannot be copied:
– Links to elements in the hardware tree
– Links that are only allowed to exist once in the ↑ 'Site'
● Copying / cutting is only possible within a 'Site'.
● When copying/cutting and pasting between two 'Stations', both 'Stations' must
be loaded.
Copying element
You can copy an element as follows:
● Using 'Edit' > 'Copy' in the menu bar
● With the keyboard shortcut <Ctrl> + <C>
Pasting copied element with subtree

You can paste a copied element with subtree as follows:
● Using 'Edit' > 'Paste' in the menu bar
● With the keyboard shortcut <Ctrl> + <V>
Pasting copied element without subtree

You can paste a copied element without subtree as follows 1:
● Using 'Edit' > 'Paste without children' in the menu bar
1 If the element has permanent child elements, they are also pasted with the
function 'Paste without children'. Example: A detector cannot be pasted without the
'Sensor' child element.
Cutting element
You can cut an element as follows:
● Using 'Edit' > 'Cut' in the menu bar
● With the keyboard shortcut <Ctrl> + <X>
82 | 406
Program operation
Moving an element
6
Pasting cut element

You can paste a cut element as follows:
● Using 'Edit' > 'Paste' in the menu bar
● With the keyboard shortcut <Ctrl> + <V>
6.10 Moving an element

You can move an element using the standard Windows function 'Drag and drop' or
with 'Cut' and 'Paste'.
When dragging an element, the mouse pointer shows whether the element can be
placed at the respective position or on the respective element. An element with
child elements cannot be dragged and dropped without its child elements. If a
subtree is moved, then various attributes of the parent element are automatically
updated, such as the address of the element in the ↑ zone.
If you press the 'Ctrl' key when dragging, the mouse pointer indicates a '+' and
copies the element when dropping.
An element can only be moved or copied from one ↑ 'Station' to another 'Station'
if both 'Stations' are loaded.
An element can be moved only within the same task card.
Handling ↑ links when moving

Moving elements inside a ↑ 'Station':
● The links to the hardware are also moved.
● The links to the control are also moved.
Moving elements between different 'Stations':
● The links to the hardware are deleted.
● The links to the control and detection elements are also moved.
83 | 406
Program operation
6 Re-addressing elements
6.11 Re-addressing elements

Elements can be re-addressed in the tree view, e.g. to close gaps in the address
sequence or to paste elements into particular positions. This application is mainly
of use in the 'Detection' task card at the 'Zone' level.
Depending on the element category, the elements are readdressed either system-
wide or only within the parent element. If, for example, you readdress a 'Zone', then
'Zones' will be readdressed system-wide. If you readdress a logical channel in a
'Zone', then only the logical channels within the 'Zone' will be readdressed. Before
elements are readdressed system-wide, a message is displayed that you must
confirm.
Reducing address by 1
Gaps are produced in the address sequence when you delete, cut / paste, move,
or re-address elements throughout ↑ stations. Proceed as follows to close gaps in
the address sequence:
1. Highlight the element after the gap in the tree view.
2. Select 'Edit' > 'Change element address: -1' from the menu bar.
a Depending on the highlighted element, the following window will be
displayed:
3. Click on 'Yes'.
a The address of the element selected and all elements of the same level with
higher addresses are decreased by 1 across the system or within the parent
element, respectively.
84 | 406
Program operation
Assigning elements
6
Raising address by 1
Proceed as follows to paste an element, e.g. an additional 'Zone', to a particular
position in the address sequence:
1. Highlight the element before which you want to insert an element in the tree
view.
2. Select 'Edit' > 'Change element address: +1' from the menu bar.
a Depending on the highlighted element, the following window will be
displayed:
3. Click on 'Yes'.
a The address of the element selected and all elements of the same level
with higher addresses are increased by 1 across the system or within the
parent element, respectively.
a A gap appears in the address sequence.
4. Create a new element and enter the address that corresponds to the gap in the
detail editor.
a The new element is moved to the position of the gap.
6.12 Assigning elements

Elements from the same or different task cards can be assigned using the 'Assign'
function. A ↑ physical channel is assigned to a logical channel.
Opening 'Assign dialog'

The 'Assign dialog' window can be opened as follows:
● button in the toolbar
● 'Commissioning' > 'Assign'' menu item
● Context menu
● <Ctrl> + <L>
The opened window can remain open when changing the task cards.
In the 'Hardware' task card, the 'Assign' function is not available.
85 | 406
Program operation
6 Assigning elements
Structure of 'Assign dialog'

1 2
1 3
1 4
1 5
1
9
8
7
1 6
1
1 List with assignable event categories, inputs and outputs

● 'Manual type selection': Select individual elements or several elements
by holding the 'CTRL' key down
● 'Grouped type selection': Select all elements in a category or the entire
category
2 Dropdown list to select the task card
3 Checkbox to activate search by ID no. (5)
4 Assign to Data Matrix code
5 Dropdown list to select the ID no.
6 Tree view of the assignable elements:
● Light gray text: The path leads to an element that cannot be assigned
● Bold text: The path leads to an element that can be assigned
● Bold characters, greyed out: assignable element
● Inverted characters, blue: highlighted element
7 'Always jump to next assignable element' checkbox: If the checkbox is
checked, the next assignable element is highlighted after assigning.
8 'Next assignable element (ALT+S)' button: Navigate to the next assignable
element
9 'Previous assignable element (ALT+W)' button: Navigate to the previous
assignable element
86 | 406
Program operation
Assigning elements
6
Assigning elements
1. In the task card tree view, highlight the element you would like to assign.
2. Open the 'Assign dialog' window.
3. Select the category from the list (1).
4. Select the task card in the drop-down list field (2).
5. Search for the element you want using the ID no. (4) or in the tree view (5).
6. Highlight the element.
7. Click on 'Assign'.
a The elements are assigned.
Instead of using the 'Assign' button, you can use the keyboard shortcut <Alt> +
<A>. If necessary, several elements can be assigned in this manner without
having to change between the tree view and the 'Assign dialog' dialog with the
mouse. To do this, the 'Always jump to next assignable element' checkbox must
be activated.
By default, the first assignable element is found and displayed automatically in the
tree view (5). You can change this behavior in the pre-settings. You will find more
information on this in chapter 'General [➙ 39]'.
See also
2 General [➙ 39]
87 | 406
Program operation
6 Assignment with Data Matrix code
6.13 Assignment with Data Matrix code

You can use a reading device for Data Matrix code to assign FDnet devices to
'Zones' using a layout plan. The adhesive labels of the device are stuck on to the
layout plan. The Data Matrix code on the adhesive labels contains details about the
type and the serial number (ID no.) of the device. Devices can be assigned
manually or automatically.
w A layout plan with the stuck on adhesive labels with Data Matrix code is
available.
w A reading device for Data Matrix code is connected to the PC.
w In the pre-settings, in the 'Assign' view, the 'Use Data Matrix Code reader'
checkbox is activated and the correct port has been selected for the reading
device.
1. Select the 'Detection' task card.
2. In the tree view, select the 'Zone' that you wish to assign to the devices.
4. Check the 'Use serial no. ("ID-Nr."):' checkbox.
5. Select the category on the left in the window.
Manual assignment
1. Read-in the Data Matrix code of the desired device on the layout plan.
a The corresponding device with the physical channel is highlighted on the
right in the window in the 'Hardware tree'.
2. Check the displayed serial number on the upper right in the window.
a The device is assigned to the 'Zone'.
Automatic assignment
1. Start automatic assignment. Click the button for automatic assignment next to
the 'Use serial no. ("ID-Nr."):' checkbox.
2. Read-in the Data Matrix code of the desired device on the layout plan.
a The device is automatically assigned to the 'Zone'.
See also
2 Assign [➙ 40]
88 | 406
Program operation
Assigning elements several times
6
6.14 Assigning elements several times

Multiple assignment allows several elements and event categories, inputs, or
outputs to be assigned to each other at the same time.
Assigning elements several times simultaneously

1. Select the 'Assign' function for the element to be assigned.
2. Hold down the 'CTRL' key and select several event categories, inputs, or
outputs in the left-hand column.
3. Hold down the 'CTRL' key and select several elements to be assigned in the
right-hand column.
a You have assigned several elements simultaneously.
89 | 406
Program operation
6 Assigning the effects of a control
6.15 Assigning the effects of a control

1. Select the 'Control' task card.
2. Open the 'Station' in the tree view.
3. Open the control group you want.
4. Open the control element you want.
5. Select 'Assign' via the icon or via the 'Commissioning' > 'Assign' menu.
a The 'New effect dialog' window opens.
6. Click on an effect in the window on the left.
a At the right of the window, the elements that can be assigned are
highlighted in the corresponding tree.
a In the case of an output with confirmation, a second 'Hardware tree' opens
for assigning the confirmation input.
a If you are assigning outputs in the 'Hardware tree', you can select the
elements via the ID no.
a You have assigned a control effect.
The 'New effect dialog' window remains open. You can assign further effects.
6.16 Deleting links

Proceed as follows to delete a ↑ link between two elements:
1. Select an assigned element in the tree view or in the table.
2. Select 'Commissioning' > 'Unassign' from the menu bar.
a The link is deleted.
OR
1. Click on an assigned element in the tree view or in the table with the right
mouse button.
2. From the context menu, select 'Unassign'.
a The link is deleted.
In the 'Hardware' task card, the command 'Unassign' is not available.
90 | 406
Program operation
Finding
6
6.17 Finding
You can use the 'Find' function to search for elements in accordance with various
search criteria, e.g. according to 'Address', 'Customer text' or 'Problem'.
The search criteria available depend on the selected task card.

The 'Find' function is limited to the selected task card.
Performing search
1. Select the desired task card and highlight the element in the tree view in which
you wish to search.
2. Open the 'Find' window. The window can be opened as follows:
– 'View' > 'Find' menu item
– <Ctrl> + <F>
– button in the toolbar
3. Select a search criterion and enter the search value in the top right field.
4. Select the search options.
5. Click on 'Find all' or 'Find next'.
a 'Find all' searches for and highlights all elements which correspond to the
search criterion.
a 'Find next' jumps from one hit to the next.
6. Click on 'Cancel' to end the current search and remove the highlighting from
the elements found.
You can use the <F3> key instead of the 'Find next' button.
91 | 406
Program operation
6 Finding and replacing
Search options
● 'Entire site': Search in the entire ↑ 'Site'.
● 'Selected sub-tree': Search in the highlighted subtree.
● 'Include': Search for values that have as a component the search value that
you entered in the upper right field.
● 'Exactly': Search for values that precisely match the search value that you
entered in the upper right field.
● 'Include unloaded stations': If you have checked the checkbox, then both
loaded and not loaded 'Stations' will be included in the search. See the chapter
'Dynamic loading [➙ 70]'.
● 'Category:': Limited search within one element category. The drop-down list
contains all of the element categories, independent of the selected task card. If
you select an element category that is not present in the task card selected,
then the search will be fruitless.
See also
6.18 Finding and replacing

You can use the 'Find and replace' function to search for elements in accordance
with various search criteria, e.g. according to 'Address', 'Customer text' or
'Problem'.
Figure 16: Finding and replacing
The search criteria available depend on the selected task card.

The 'Find and replace' function is limited to the selected task card.
Finding and replacing

1. Select the desired task card and highlight the element in the tree view in which
you wish to search.
2. Select 'View' > 'Find and replace'.
a The 'Find and replace' window opens.
3. Select a search criterion.
4. Enter the search value in the field at the upper right and the replacement value
in the field below it.
5. Select the search options.
92 | 406
Program operation
Finding and replacing
6
6. Click on a button:
– 'Find next' jumps from one hit to the next.
– 'Replace' replaces the hit with the replacement value.
– 'Replace all' replaces all the hits found with the replacement value.
– 'Cancel' stops the current search and removes the highlighting on elements
found.
You can use the <F3> key instead of the 'Find next' button.
Search options
● 'Entire site': Search in the entire ↑ 'Site'.
● 'Selected sub-tree': Search in the highlighted subtree.
● 'Include': Search for values that have as a component the search value that
you entered in the upper right field.
● 'Exactly': Search for values that precisely match the search value that you
entered in the upper right field.
● 'Include unloaded stations': If you have checked the checkbox, then both
loaded and not loaded 'Stations' will be included in the search. See the chapter
'Dynamic loading [➙ 70]'.
● 'Category:': Limited search within one element category. The drop-down list
contains all of the element categories, independent of the selected task card. If
you select an element category that is not present in the task card selected,
then the search will be fruitless.
93 | 406
Program operation
6 Exporting an XML
6.19 Exporting an XML

You can export the configuration of the ↑ 'Site' into an XML file. This file can be
edited with any XML-compatible software, so that reports with different criteria and
representation forms can be output.
Examples of using an XML export:
● Creating country-specific reports
● Creating input files for external systems, e.g., SWING tool
Exporting XML file

1. Open a Site using the 'File' > 'New site' or 'Open' menu item.
2. Click on the 'File' > 'Site export (XML)' menu item.
a The 'Reports' window is opened with the setting 'Site XML export'.
3. On the 'Stations' tab, select the stations for which you wish to generate an XML
export.
– The maximum number of 'Stations' that can be loaded is limited. If the
configuration of the Site exceeds the limit, you must activate / deactivate
one or more 'Stations' for the export.
4. Select the 'Output settings' tab.
Standard XML export

1. Check the 'Create Standard XML report' checkbox.
2. Select the path, enter a file name, and click on 'Create report'.
a You have exported the configuration of the 'Site' into an XML file.
94 | 406
Program operation
Exporting an XML
6
User-defined XML export

The user-defined XML export supports direct XSLT transformation of the export. To
do this, you need an XSLT transformation file.
1. Check the 'Create XSLT based export' checkbox.
2. Define an XSLT transformation file. For a transformation file from ↑ 'BDV',

select 'Use file from BDV'. For any other transformation file, select 'Use file
from file system'.
3. Select the path, enter a file name, and click on 'Create report'.
a You have exported the configuration of the 'Site' into a user-defined XML file.
95 | 406
Program operation
6 Exporting an SIB-X
6.20 Exporting an SIB-X

The SiB-X export function can be used to export the configuration data definitions
into an XML file in SiB-X format. SiB-X is the format for exchanging configuration
data between various products of Siemens Building Technologies,
e.g., Management System MM8000.
Exporting configuration data

1. Open a ↑ site using the 'File' > 'New site' or 'Open' menu item.
2. Click on the 'File' > 'SiB-X export' menu item.
a The 'SiB-X export' window opens.
3. Select the 'Stations' you want.

4. Select the path, enter a file name, and click on 'Start'.
a The configuration data is exported.
96 | 406
Program operation
Exporting and importing CSVs
6
6.21 Exporting and importing CSVs
The menu entries for CSV export and import are available only in the 'Detection'
task card.
Only data in the ↑ 'Detection tree' is taken into account for CSV export or CSV
import.
CSV export:
● Export data from SintesoWorks in CSV format. Link [➙ 97]
● Edit and add data in the CSV file. Link [➙ 97]
CSV import:
● Import data to SintesoWorks in CSV format. Link [➙ 99]
See also
2 Exporting CSVs [➙ 97]
6.21.1 Exporting CSVs

2. Highlight the ↑ 'Site' or a subtree in the tree view.
3. Select 'File' > 'CSV export' from the menu bar.
a The 'CSV export' window opens.
4. Select the path and change the file name if needed. In the default settings, the
'Site' name is used with the supplement '_exchange' as the file name.
5. Click on 'OK'.
6. If you have not yet saved the 'Site', you will be prompted to save the 'Site'. If
this is the case, click on 'Yes'.
a The CSV file is saved at the specified location.
6.21.2 Editing the CSV file

Example: The data of a ↑ 'Site' is exported into a CSV file. Customer-specific data,
e.g., the customer texts, is edited or added in this file. Afterwards, the CSV file is
imported back into the 'Site'.
CAD ID and note
The 'CAD-ID' and 'Note' columns of the CSV file can be used to save additional
information that is not shown in Engineering Tool or at the station, e.g., the CAD-
based position of the corresponding node. The text must be no more than 40
characters for each cell. The text is only visible in the CSV file.
Editing customer text

l Edit the text in the 'Customer text' column.
Length of customer text
A customer text must be no more than 40 characters. If a customer text contains
more than 40 characters in the CSV file, the text is shortened to 40 characters
automatically when it is imported. A warning is shown in the 'CSV import log' if the
customer text has been shortened.
97 | 406
Program operation
6 Exporting and importing CSVs
Creating new elements in the CSV file

1. Enter the 'Area address' in the first column.
2. Depending on the element type, enter the 'Section address', 'Zone address',
and 'Channel address' elements.
3. Enter the element type in the 'Type' column, taking the following into account:
– The element type is an abbreviation of the corresponding element in the
detection tree.
– The element type abbreviation must match your localized ↑ BDV.
– If the element type is missing or does not match your localized BDV, the
new elements cannot be imported.
– The table below shows the detection tree elements and the corresponding
element type abbreviations.
– Only the elements listed in the table can be added to the detection tree as
part of a CSV import.
– If the language of this documentation does not match the BDV language,
you may not be able to use the element type abbreviation listed in the
table. Contact your local or regional company for a translation of the
element type abbreviations.
4. Enter additional data, e.g., 'Customer text'.
Element in the detection tree Element type in the CSV file

'Type' column
↑ Section SE
Automatic zone, Single, standard ZAS
Automatic zone, Multi, standard ZAM
Gas zone, CO gas alarm ZG
Manual zone, Standard ZM
Technical zone, Standard (ack./latching) ZT
Sprinkler zone, Standard ZSP
Flow switch zone, Standard ZFS
Sub-system zone, Standard ZSS
Sub-system zone, ASD system ZSA
Autom. detector, wired EAW
Autom. detector, wireless EAR
Collective EC
Manual call point, wired EMW
Manual call point, wireless EMR
Gas detector EG
98 | 406
Program operation
Exporting and importing CSVs
6
6.21.3 Importing CSVs
Length of customer text

A customer text must be no more than 40 characters. If a customer text contains
more than 40 characters in the CSV file, the text is shortened to 40 characters
automatically when it is imported. A warning is shown in the 'CSV import log' if the
customer text has been shortened.
Column title
The import file may contain the column title as per the local BDV or the English
column title:
Area address, Section address, Zone address, Channel address, Customer text,
Note, Zone intervention text, Plan no., Structured address, Type.

2. Select 'File' > 'CSV import' from the menu bar.
a The 'CSV import' window opens.
3. Select the CSV file that you wish to import.
4. Click on 'OK'.
a The specified CSV file is imported.
5. Open the protocol of the CSV import and rectify problems if necessary.
6.21.4 Protocol of the CSV import

The protocol for the CSV import displays problems that occurred during CSV
import. You can filter the problems according to 'Error', 'Warning' and 'Info'.
Displaying the protocol of the CSV import

2. Select 'File' > 'Show CSV import log' from the menu bar.
a The 'CSV import log' window opens.
a A list of 'Error', 'Warning' and 'Info' messages can be seen in the window.
3. Double-click on a message to jump directly to the corresponding element.
99 | 406
Program operation
6 Change display logo
6.22 Change display logo

By default, in the normal state of the ↑ 'Station', the Siemens logo is shown on the
display. You can replace the Siemens logo with a customer specific logo. The logo
must be available as a GIF file and must meet the following requirements:
● Maximum size: 251 x 56 pixels
● Black and white
● No transparency
● Not interlaced
Replacing the standard logo

1. Select 'Edit' > 'Exchange logo in site' from the menu bar.
2. Click on 'OK'.
3. Select the file with the new logo.
4. Load the configuration from the PC to the ↑ 'Station'.
a After a restart of the 'Station', the new logo is shown on the display.
Restoring the standard logo

1. Select 'Edit' > 'Exchange logo in site' from the menu bar.
2. Click on 'Reset to default'.

3. Load the configuration from the PC to the ↑ 'Station'.
a After a restart of the 'Station', the standard logo is shown on the display.
a The file with the replaced logo is saved in the same folder in which the ↑ 'Site'
configuration is saved.
See also
2 Loading configuration from the PC to the station [➙ 114]
100 | 406
Program operation
Creating reports
6
6.23 Creating reports

You can generate various reports as PDF or XML files in the 'Reports' window.
Creating a report
1. Select the task card from which you wish to create a report.
2. Select 'File' > 'Reports' from the menu bar or click on the symbol in the
toolbar.
a The 'Reports' window opens.
3. Select the corresponding report in the 'Report type' field.
4. Select the page format, page orientation, file name, and location of the report
on the 'Output settings' tab.
5. If available, on the 'Stations' tab, select the 'Stations' for which you wish to
generate a report.
6. If available, set additional properties on the 'Settings' tab.
7. Click on 'Create report'.
a The report is created and displayed.
Figure 17: Example for the window for creating reports

You will find information on the individual reports and additional settings in the
following chapters.
101 | 406
Program operation
6 Creating reports
Opening an XML file in Excel

Reports in XML format are opened in Excel by default.
If reports in XML format do not open automatically in your operating system,
proceed as follows:
1. Right-click the XML report or the XML file in the File Explorer.
2. Select 'Open with' > 'Choose Default Program...'.
3. Select the 'XML Editor' program.
4. Activate the 'Always use the selected program to open this kind of file' option.
5. Click on 'OK'.
a XML reports are opened in Excel by default.
6.23.1 Customer text report
The 'Customer text report' lists the customer texts of all elements of the respective
task card.
● Create report link [➙ 101]
You can make the following settings in the 'Settings' section:
● 'Displayed top level of the tree': Topmost level of the structure tree that is
displayed in the report.
● 'Displayed bottom level of the tree': Lowermost level of the structure tree that is
In the task cards 'Operation' and 'Network', the section 'Settings' is empty.
102 | 406
Program operation
Creating reports
6
6.23.2 Device report
Regardless of which task card is selected, the 'Device report' lists the number of
elements available in the 'Hardware tree', ↑ 'Detection tree', and ↑ 'Control tree'.
On the one hand, the elements are listed as in the tree view, with the number of
elements in the parent element. On the other hand, each element type is listed with
the total number of elements.
The output elements are:
● ↑ 'Detection tree': Elements 'Area', ↑ 'Section', and 'Zone' with the assigned
devices
● ↑ 'Control tree': Elements 'Control group' and 'Control' with the assigned
devices
● 'Hardware tree': 'Station' and 'Modules' elements, and FDnet devices
103 | 406
Program operation
6 Creating reports
6.23.3 Diagnostics report
The 'Diagnostics report' lists the 'Site info properties' and the software and firmware
versions of the hardware in the entire ↑ 'Site'.
Only the properties existing in the elements are listed here, i.e. only some of the
following possible properties:
● Hardware version ● Series number

● Software version ● Hardware name
● Firmware version ● Hardware type
● Firmware revision ● Ethernet MAC address
● Product version
104 | 406
Program operation
Creating reports
6
6.23.4 Event memory report
The 'Event memory report' lists the events of a ↑ 'Site'.

You can use filter options to limit the number of listed events, e.g. events of a
particular event category within a particular time period.
● You can use 'Browse...' to open a CSV file of the event memory that you have
uploaded through the menu item 'Commissioning' > 'Upload site event
memory'.
● You can use 'Upload...' to establish the connection to a ↑ 'Station' and load the
event memory to the PC.
● You can specify the date and time for the start and end point of the report in the
fields 'Start date' and 'End date'.
● In the section 'Event categories' you can select the event categories that are to
be taken into consideration in the report.
105 | 406
Program operation
6 Creating reports
6.23.5 Import information report
The 'Import information report' outputs a list of imported elements and their IDs
following completion of an import from inventory systems.
The following filter settings are possible:
● 'Whole site' creates a report for the entire 'Site'
● 'Selected station' creates a report for the selected ↑ 'Station'
106 | 406
Program operation
Creating reports
6
6.23.6 Node report
In the 'Node report', the element of the respective task card highlighted in the tree
view is listed in table format.
● 'Full property set': All visible properties of the highlighted element are output.
● 'Property subset': A subset of the properties is output. The selection is
dependent on the ↑ BDV used.
● 'Include sub-tree' This setting indicates whether only the highlighted elements
will be output or also the subtree as well.
Not all settings are available in the task cards 'Operation' and 'Network'.
107 | 406
Program operation
6 Creating reports
6.23.7 'Peripherals test report'
The 'Peripherals test report' lists the last test activations of the peripheral devices.
The test date and the activation type is listed for each test activation.
You can set the date range for the test activations to be listed on the 'Settings'
tab.
108 | 406
Program operation
Creating reports
6
6.23.8 Soiling report
The 'Soiling report' lists the 'Compensation value' of the detectors.

The following elements are listed for each detector:
● Device customer text
● Device address path
● Operating years
● Compensation level
● Compensation value:
– Normal, no action required
– 100 %, warning, detector replacement recommended
– 150 %, maximum, detector replacement required
● Logical customer text
● Logical address
● Serial no. ("ID-Nr.")
109 | 406
Program operation
6 Creating reports
6.23.9 Tree report
In the 'Tree report', properties of the elements from the structure tree of the
respective task card are listed in table format, e.g., ↑ parameter set, 'Serial no.
("ID-Nr.")', and 'Template ID'.
● 'Displayed top level of the tree': Topmost level of the structure tree that is
110 | 406
Connectivity and communication with 'Station'
Connecting the PC to the station
7
7 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.
A ↑ GAP can be configured with a DHCP server. This results in a PC

automatically receiving an IP address when a connection is established to the
GAP via FCnet/LAN.
See also
2 Establishing connection from PC to FS20 network [➙ 376]
7.1 Connecting the PC to the station

For most commissioning, maintenance and repair work a PC with installed
SintesoWorks is required. The figure below shows the connection between the PC
and ↑ 'Station'.
LAN 11
Figure 18: Rear panel of operating unit and PC
LAN Ethernet connection

1 Cable, type CAT 5 or CAT 7, crossover, max. 100 m
7.2 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 'SintesoWorks' > 'Commissioning' in Disconnect.
2. Disconnect the cable connection between PC and 'Station'.
3. Wait ≥2 min. before you establish a connection to another 'Station'.
111 | 406
7 Connecting SintesoView
7.3 Connecting SintesoView

w Enabling for viewing and / or operating the ↑ 'Station' with SintesoView is
granted.
w The PC is connected to the ↑ 'Site'.
1. Select the 'SintesoView' task card.
2. Select 'SintesoView' > 'Connect' from the menu bar.
a The selection window for the connection is displayed.
3. Select the connection and confirm with 'OK'.
a The 'Connect SintesoView' window opens.
4. Select the 'Station' that you wish to display and/or operate and enter a valid
PIN.
5. Click on 'OK'.
a The connection is established.
Connect from the Favorites list with 'Station'

w Enabling for viewing and / or operating the ↑ 'Station' with SintesoView is
granted.
w The PC is connected to the 'Site'.
1. Select the 'SintesoView' task card.
2. Select 'SintesoView' > 'Connect to favorite' from the menu bar.
3. Select the desired 'Station' from the list.
a The connection is established.
You will find a description of enabling for viewing and/or operating with
SintesoView in document 008838. See chapter 'Applicable documents'.
You can use the pre-settings to cause SintesoView to be connected automatically

with the most recently connected ↑ 'Station' when you open the task card
'SintesoView'.
See also
112 | 406
Load data to the station
7
7.4 Load data to the station

Data is loaded from SintesoWorks to the 'Station' when the following commands
are performed.
● 'Initialize station'
● 'Download site'
If you use more than one network cards on the PC, observe the information
contained in chapter 'IP settings for several network cards [➙ 35]'.
The table below shows which data is overwritten in the 'Station'.
Command Overwrites the Sets the address Overwrites the

↑ BDV of the 'Station' configuration
'Initialize station' 1 Yes Yes Yes
'Download site' Yes No Yes 2
1 Command is only performed for the 'Station' that is connected to the PC via LAN.
2The configuration of selected 'Stations' or all 'Stations' in the ↑ 'Site' can be
overwritten as an option.
See also
2 Initializing the station [➙ 113]
7.5 Initializing the 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 SintesoWorks.
A ↑ standalone 'Station' does not have to be initialized.
You will find a detailed description for initialization of a 'Station' in document

'009052'. See chapter 'Applicable documents'.
See also
2 Load data to the station [➙ 113]
113 | 406
7 Loading configuration from the PC to the station
7.6 Loading configuration from the PC to the station

You can use the 'Download site' function to load the configuration of one ↑ 'Site'
from the SintesoWorks on the PC into the 'Station'.
NOTICE
Different network configuration in SintesoWorks and networked ↑ 'Site'
When the selection displayed for 'Download site' is manually modified, in special
cases1 it may be necessary to reset a 'Station' to the factory setting as well as a
'Initialize station'.
● Do not modify the selection displayed for 'Download site' in normal cases.
● Check the sequence when loading different configuration states in special
cases 1.
● After any change of the network configuration, make sure that all 'Stations' in
the 'Site' for the 'Download site' procedure are selected and can be accessed.
● Temporarily update non-accessible 'Stations' to the latest status of the global
network configuration prior to integration in the network.
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.
w The ↑ 'Site' is opened in SintesoWorks.

w The PC is connected to the 'Station'.
w Networked 'Stations' are initialized.
w 'Station' and SintesoWorks have the same 'Site' ID.
w 'Station' and SintesoWorks are part of the same sales channel.
1. Select 'Commissioning' > 'Download site' in SintesoWorks.
a The 'Download site' and 'Connect' windows open in SintesoWorks.
2. Select the connection in the 'Connect' window and click on 'OK'.

a The 'Stations' are listed in the 'Download site' window.
114 | 406
Loading configuration from the station to the PC
7
3. Select the 'Stations' whose configuration you would like to load from
SintesoWorks to the 'Stations' and click on 'Start'.
a The 'Set access level' window may open in SintesoWorks with the 'Set the
station to access level 3' prompt. Press <MENU> on the 'Station', enter the
PIN and press <ok>.
4. Click on 'OK' in the 'Set access level' window in SintesoWorks.
a The 'Action confirmation' window opens in SintesoWorks.
5. Click on 'Yes'.
a The configuration is loaded to the 'Station'.
a The progress is displayed in the 'Download site' window in SintesoWorks.
a The 'Station' restarts.
a After a few minutes, the 'Buzzer' sounds twice at the 'Station'.
6. Press <Acknowledge> on the ↑ Person Machine Interface at the 'Station' to
switch off the 'Buzzer'. Do not perform any more actions on the 'Station' until
the 'Buzzer' has sounded for the second time.
See also
2 Load data to the station [➙ 113]
7.7 Loading configuration from the station to the PC

The 'Upload site' function can be used to load the configuration of a ↑ 'Site' to
SintesoWorks on the PC.
w The 'Site' is opened in SintesoWorks.
w The PC is connected to the 'Station'.
w 'Station' and SintesoWorks have the same 'Site' ID.
w 'Station' and SintesoWorks are part of the same sales channel.
1. Select 'Commissioning' > 'Upload site'.
a The 'Upload site' and 'Connect' windows are opened.
2. Select the connection in the 'Connect' window and click on 'OK'.

a The 'Stations' are listed in the 'Upload site' window.
3. Select the 'Stations' whose configuration you would like to load to
SintesoWorks and click on 'Start'.
a The 'Action confirmation' window opens.
4. Click on 'Yes'.
a The configuration is loaded to the PC.
a The progress is displayed in the 'Upload site' window.
115 | 406
7 Loading event memory to PC
7.8 Loading event memory to PC

The 'Upload site event memory' can be used to load the event memory of one or
more ↑ 'Stations' in the ↑ 'Site' from any 'Station' to the PC.
w A valid 'Site' is loaded.
w All 'Stations' have the same ↑ BDV version and the same global configuration
so that site-wide communication is supported.
w 'Station' and SintesoWorks must belong to the same organizational unit.
w The PC is connected to a 'Station' in the 'Site' via an Ethernet cable.
1. In the 'Commissioning' menu, select the 'Upload site event memory' menu item.
a The 'Connect' window opens.
2. Select the connection setting and confirm with 'OK'.
a The selection window opens.
3. Select the 'Stations' whose event memory you would like to load to the PC.
4. Determine the memory location and the file name.
5. Click on 'Start'.
a The data is transferred.
a The status of the transfer is shown in the status bar.
a The data is saved as a CSV file the specified location.
116 | 406
Loading the site log files to the PC
7
7.9 Loading the site log files to the PC

You can load log files of individual 'Stations' of a 'Site' to the PC. The log files are
stored in a compressed archive that is determined by the user. The archive
contains a folder for each 'Station'.
Example:
LogFilesArchiveExample.zip
\Station1\
syslog_0.log
syslog_1.log
syslog_2.log
\Station2\
syslog_0.log
syslog_1.log
w A 'Site' is loaded.
w All 'Stations' have the same ↑ BDV version and the same global configuration
so that site-wide communication is supported.
w 'Station' and SintesoWorks must be in the same organizational unit.
w The PC is connected to a 'Station' in the 'Site' via an Ethernet cable.
1. In the 'Commissioning' menu, select the 'Upload site log files' menu item.
a The 'Upload site log files' and 'Connect' windows are opened.
2. Select the connection in the 'Connect' window and click 'OK'.
a The 'Stations' are listed in the 'Upload site log files' window.
3. Select the 'Stations' the log files of which you would like to load to the PC.
4. Determine the memory location and the file name.
5. Click on 'Start'.
a The data is transferred.
a The status of the transfer is shown in the status bar.
a The data is saved in the specified file.
117 | 406
7 Merge two sites
7.10 Merge two sites

You can merge two ↑ 'Sites' to form one 'Site'. The examples below illustrate
possible reasons for merging:
● Two neighboring buildings have one fire detection installation each. Both fire
detection installations are to be merged to form a shared fire detection
installation.
● A new fire detection system with a redundant network is installed. To speed up
commissioning, two service technicians split the 'Site' into two parts, which are
commissioned separately. Once both parts have been commissioned, they are
merged to form a single 'Site'.
You will find a detailed description of how to merge two ↑ 'Sites' in document
See also
7.11 Handover
The configuration of the ↑ 'Site' and the ↑ 'Stations' from a third-party business
channel can be transferred to another business channel. You will find the
'Handover site' and 'Handover station' functions in the 'Commissioning' menu.
For more information about 'handover', contact your designated in-country
Siemens regional company.
118 | 406
Updating the firmware
Updating the firmware of the 'Station'
8
8 Updating the firmware
8.1 Updating the firmware of the 'Station'

There are three options for updating the firmware of the ↑ 'Station':
● 'FW update main CPU': Updating the main CPU
● 'FW update additional CPUs': Updating additional ↑ CPUs, e.g., the periphery
cards
● 'FW update main and additional CPUs': Updating the main CPU and additional
CPUs in a single step
You will find a detailed description for updating firmware in document 009052. See
See also
8.1.1 'Site' conversion

When the firmware is updated, the existing 'Site' is converted on the basis of the
new ↑ BDV. The ↑ 'Site' can be converted automatically or manually. Manual
conversion is called up in SintesoWorks via the 'Edit' > 'Convert site' menu item.
Properties of the conversion

● Only the configuration data is converted.
● The process data of the ↑ 'Station' is not converted. The default values of the
new firmware are transferred and the 'Station' recalculates the process data.
● The critical conversions are logged for the entire 'Site'. The logs can be viewed
in the 'Conversion log' window or printed from the log file.
You will find detailed information about converting in document A6V10244961 and
an overview in document 009052. See chapter 'Applicable documents'.
See also
119 | 406
8 Updating the firmware of the peripheral devices
8.1.2 Conversion log

The conversion log is displayed in the 'Conversion log' window. The log can be
used to detect and correct errors in the converted configuration.
Figure 19: 'Converter log' window with the 'Error', 'Warning', and 'Info' entries
The ↑ 'Site' is converted when the firmware is updated. You will find more
information about this in document 009052. See chapter 'Applicable documents'.
See also
8.2 Updating the firmware of the peripheral devices

You can update the firmware of the following peripheral devices:
● ↑ Floor repeater terminal FT2010
● ↑ Floor repeater display FT2011
● ↑ Radio gateway FDCW221
● Radio gateway FDCW241
● Mimic display driver FT2001-A1
● MCL-USB adapter FDUZ221
● Detector exchanger and tester FDUD292 and intelligent detector tester
FDUD293
● Line tester FDUL221
To connect a peripheral device to the PC, you need the MCL-USB adapter.
You will find more information in document 009052. See chapter 'Applicable
documents'.
See also
120 | 406
Converting a station
8
8.3 Converting a station

The 'Replace element' function is used to convert a configuration from a small
station type to a larger station type.
The following conversions are possible:
● FC2020 to FC2030 or FC2040 or FC2060
● FC2030 to FC2060
● FC2040 to FC2060
The possible conversions are determined by the ↑ BDV used and may differ from
those shown above.
How to convert a ↑ 'Station'

w A 'Station' of type FC2020, FC2030, or FC2040 is available.
1. Select the 'Station' to be converted.
2. In the menu, click on 'Edit' > 'Replace element'.
3. Select the target station type for the conversion.
4. Confirm your selection with 'Yes'.

a The configuration of the 'Station' has been converted.
Conversion log
The critical conversions are logged for the converted ↑ 'Station'. The logs can be
viewed in the 'Conversion log' window or printed from the log file.
121 | 406
Configuration –Overview
9 Converting a station
9 Configuration –Overview
A 'Site' has a physical and a logical structure. The structures are shown and
configured in the SintesoWorks task cards. The table below shows elements and
assignment of the appropriate structure.
Structure type Structure tree Task card

Physical structure Hardware tree 'Hardware'
Logical structure ↑ Detection tree 'Detection'
↑ Control tree 'Control'
Operation tree 'Operation'
Network tree 'Network'
The physical structure is read in by the ↑ 'Station' or created manually. The logical
structure can be created either manually during the ↑ pre-configuration or
automatically on the 'Station' by auto-configuration. Parts of the logical structure
are pre-configured in the ↑ BDV template for a 'Station'.
The list below shows a selection of configurable elements in a ↑ 'Site':
● Configuring the components of the 'Station'
● Detector zones
● Detector settings
● ↑ Multi-detector dependency
● ↑ Alarm organization
● Controls (alarming, fire, NAC, extinguishing)
● Networking control panels and operating panels ('Stations')
● ↑ Visibility for events and functions
● Service intervention
● Customer texts
● Intervention texts
122 | 406
With pre-configuration
9
Deactivating the mouse wheel of the computer mouse
NOTICE
Unintended scrolling in drop-down lists
Configuration error caused by unintended modification of settings
● Read the following description.
● To deactivate the mouse wheel, activated the checkbox 'Ignore mouse wheel'
in the pre-settings.
When you scroll with the mouse wheel in the detail editor, it could happen that you
will unintentionally change the settings in a drop-down list. In order to prevent this,
you can deactivate the mouse wheel. To do so, proceed as follows:
1. In the menu bar, click on 'Options' > 'Preferences'.
a The 'General' window opens.
2. Click on the left in the window on 'Editing'.
3. Check the 'Ignore mouse wheel' checkbox.
a The mouse wheel is deactivated.
The setting 'Ignore mouse wheel' does not go into effect until you select a new
element in the structure tree. The setting is not yet adopted for the currently
selected element.
See also
2 Editing [➙ 42]
9.1 With pre-configuration

● In SintesoWorks, the ↑ 'Site' is configured in its logical structure based on the
planning documents, the layout plan, etc. It is ↑ pre-configured.
● During commissioning, the pre-configuration is loaded to the ↑ 'Station'.
● Once the pre-configuration is loaded to the 'Station', the 'Station' is restarted.
During this process, the 'Station' components and peripheral devices are read
in. The resulting physical structure is loaded into the SintesoWorks together
with the logical structure.
● The logical and physical structure are assigned in SintesoWorks and loaded
back into the 'Station'.
123 | 406
9 Without pre-configuration
9.2 Without pre-configuration

During commissioning, first the components and the ↑ 'Station' periphery are read
in. There are two ways of reading in the periphery:
● The FDnet detector lines are read in individually. The resultant physical
structure is loaded in SintesoWorks. Afterwards, the logical structure is created
in SintesoWorks and assigned to the physical structure.
● The FDnet detector lines are read in by auto-configuration. This results in the
physical structure and the logical structure. The two structures are loaded to
SintesoWorks.
Auto-configuration can be performed for the 'Station' or for individual ↑ detector
lines.
● MS9i detector lines, ↑ collective detector lines, and AnalogPLUS detector lines
are not read in. These have to be pre-configured in full.
● The interactive detector line is read in and must then be configured manually.
9.3 Customer text

Customer text can be entered for each element in the structure tree. The customer
text is shown on the display of a ↑ 'Station'. The length of the customer text is
checked during entry.
Customer text is displayed in accordance with the following rules:
Elements except 'Zone' element

If a message associated with an element appears, the corresponding customer text
is displayed. If no customer text is assigned to the element, the customer text of
the superordinate element is displayed with a customer text.
Example: If a ↑ 'Section' has no customer text, then the customer text of the
'Detection area' is displayed.
'Zone' element
If an alarm message for a 'Zone' appears, the customer text of the detector sensor
assigned to it is displayed. If the assigned detector sensor is not assigned any
customer text, the customer text for the 'Zone' is displayed. If no customer text is
assigned to the 'Zone' either, the customer text of the next superordinate element
appears.
124 | 406
System requirements
10
10 AlgoRex/SIGMASYS data migration

This chapter describes the migration of configuration data from an AlgoRex or
SIGMASYS fire detection system to an FS20 fire detection system. It describes
general requirements and detailed steps that must be taken when planning and
performing data migration.
10.1 System requirements

Data migration
The following system requirements apply to data migration:
AlgoRex system version XX_1140_830_YY

XX:country code
YY:version number
AlgoWorks software version V1.94
SIGMASYS system version xxx
PLAND100 software version V9.0
SintesoWorks F-FX2030-XL_en_1-5.0.0.R2 or later
version
See also
2 System requirements [➙ 28]
125 | 406
10 Options and limitations
10.2 Options and limitations

This chapter describes practical data migration options and system limitations. The
options described are only examples and do not cover all possible combinations.
10.2.1 Supported stations

Configuration data can be imported into ↑ 'Stations' of type 'FC2020', 'FC2030',
'FC2040', 'FC2060', or 'FC2080'.
10.2.2 Supported lines and limitations

The configuration data is imported line by line. The following ↑ line cards are
supported:
● AnalogPLUS line card (FCL2005)
● Interactive line card (FCL2006)
● FDnet line card (onboard/FCL2001)
It is strictly prohibited to import an FDnet line into a Cerberus PRO

configuration.
NOTICE
Importing a Sinteso FDnet line into a Cerberus PRO configuration
↑ 'Station' is inoperable.
● Never import an FDnet line into a Cerberus PRO configuration.
During the import process, specific ↑ line cards which contain lines are offered for
selection. The biggest unit that can be assigned is a line card and the smallest unit
is a line.
When you assign a line to a ↑ line card, the next free line card is used.
You can import lines from AlgoRex and SIGMASYS Stations into FS20 Stations;
see diagrams below. All physical devices, the devices with this assigned detection
logic, and parts of the control logic are included in the import. The detection logic
and control logic are not visible during the import process.
10.2.3 Number of channels per 'Zone'

In FS20 up to 99 channels per 'Zone' are possible. The Channel address must not
be greater than 99.
After importing an AlgoRex configuration with more than 99 channels per 'Zone', all
channels with addresses >99 are indicated with an error message in
SintesoWorks. The configuration has to be adapted. You will find more information
in chapter 'Adapting the number of channels per zone [➙ 139]'.
126 | 406
Options and limitations
10
10.2.4 AlgoRex limitations

Migrating controls
● Only AlgoRex control zones 4 and 6 can be migrated to FS20.
● Formulas for AlgoRex control zones are not migrated to FS20.
● AlgoRex command elements are not migrated to FS20.
● AlgoRex features combined controls, which function as a 'Fire control' and an
'Evac control' at the same time, e.g., Struct 1751, Struct 1654, and Struct 1551.
These controls can have a 'Sounder' and other channels as effects. In FS20
there are no combined controls, as a 'Sounder' can only be assigned to 'Evac
control'. The migrated combined controls must be adapted manually in FS20.
Link [➙ 139]
● LED indicators are not migrated from AlgoRex to FS20.
● AlgoRex causes which do not have any equivalent cause in FS20 cannot be
migrated.
● If a detector is linked as an effect several times in AlgoRex, only the first link is
migrated to FS20. It is not possible to link a detector to several effects in FS20.
10.2.5 SIGMASYS limitations

Migrating controls
● Every control (output) is migrated as an effect of its own, newly created control
group.
● All activation sources are treated as causes of the control and assigned as
such.
● The following elements of a SIGMASYS control are migrated to FS20:
– Name of the control or customer text
– Logical address
– Physical inputs and outputs
● Panel outputs are not migrated to FS20
10.2.6 Sequence of the import process

When an AlgoRex station is imported, the assigned logical elements are included
in the import. 'Zones' are assigned new numbers because the numbering of each
'Section' starts from 1 in the case of the existing CSX numbers.
The sequence of the 'Zones' is retained during the import process. Therefore,
'Zones' should be imported in the sequence in which they appear in the AlgoRex
configuration. Otherwise, when a 'Zone' with a lower number is subsequently
imported, the numbering of all subsequent 'Zones' that have already been imported
will be adapted.
127 | 406
10 Options and limitations
10.2.7 Diagram of possible assignment

The figures below show possible logical assignments between AlgoRex Stations or
SIGMASYS Stations and FS20-Stations. The circles represent the logical areas.
Station 1 FS20
Station 2
Assignment of two inventory stations to one FS20-Stations
Station FS20 1
FS20 2
Assignment of one inventory station to two FS20-Stations
128 | 406
Overview of steps
10
Station1 FS20 1
Station 2
FS20 2
Station 3
Assignment of several inventory station to two FS20-Stations
10.3 Overview of steps

The data migration sequence is outlined below.
● Export configuration data from AlgoWorks or PLAND100
● Create new ↑ 'Site' in SintesoWorks
– Create ↑ 'Station' in SintesoWorks
– Create line cards and lines required
● Import data into SintesoWorks
● For each line:
– Assign imported 'Elements'
– Adapt configuration, e.g., adapt controls or detection, if required
– Download and start 'Site'
● Completing migration
– 'Import information report'
– 'SiB-X export' for management stations
– 'Remove import information'
129 | 406
10 Exporting configuration data
10.4 Exporting configuration data
10.4.1 AlgoWorks export

Configuration data from AlgoRex which is to be imported into FS20 must be
created in AlgoWorks as an export file. The following steps describe how to create
an export file in AlgoWorks.
w The ↑ site version and the software version meet system requirements.
1. Click on 'Save Configuration Data As' in the 'File' menu
2. In the 'Save as' window, select the *.fsm data type.
3. Select a storage location for the file and click on 'Save'.
a The export file has been created.
You will find more detailed information in the online help for AlgoWorks.
130 | 406
Exporting configuration data
10
10.4.2 PLAND100 export

Configuration data from SIGMASYS must be imported into FS20 as a PLAND100
export file. The following steps describe how to create an export file in PLAND100.
PLAND100 only exports FDnet lines.
You will find more detailed information in the online help for PLAND100.
w The ↑ site version and the software version meet system requirements for data
migration. Link [➙ 125]
1. Select the FDC and open the 'Set component' window.
2. Check the 'Component preparing for FS20 migration' checkbox in the 'Set
component' window.
a The FDC icon indicates that preparation for migration is under way.
3. Check the site configuration: Menu item 'Parameterize' > 'Check'.

– If the check of the site configuration was not completed without errors, the
export will not start.
4. Select menu items 'Site' > 'Export' in the main menu.
131 | 406
10 Exporting configuration data
5. Select format 'SIGMASYS-FS20 migration (MPx)'.
6. Select the 'Create' button.

a The export file is saved.
Serial numbers are not recorded in SIGMASYS. In other words, following the
import, the serial numbers are output with 0. Serial numbers are assigned to the
devices once the configuration has been loaded to the station and a new upload
to the PC has been performed.
132 | 406
Creating a site for data migration
10
10.5 Creating a site for data migration

See also
2 Creating a site [➙ 72]
10.5.1 Creating a station
Configuration data can be imported into ↑ 'Stations' of type 'FC2020', 'FC2030',

'FC2040', 'FC2060', or 'FC2080'.
You will find more information on the creation of ↑ 'Stations' in chapter 'Creating a
station [➙ 76]'.
10.5.2 Creating line cards

w A ↑ 'Station' has been created.
1. Highlight the 'Station'.
2. Select 'New element'.
3. Add the line cards.
a The line cards are created.
10.5.3 Creating FDnet/C-NET lines
You will find details on the technical term ↑ 'FDnet' in the chapter 'Glossary'.
When importing FDnet lines, the control panel creates 2 ↑ stubs for each
unassigned ↑ loop. So that the stubs can be assigned correctly, you must create
them prior to running the import.
You will find detailed information about creating lines and converting stubs in
document 009052.
133 | 406
10 Importing configuration data
10.6 Importing configuration data

Overview of the 'Import dialog' window
1 2
1 3
1
7
1
6
1
5
1 4
1
1 Drop-down menu for selecting the structure tree for the migration: Hardware
or control
2 List of assignable elements
3 Tree structure of the current 'Site'
● Normal text: The path leads to an element that cannot be assigned
● Bold text: The path leads to an element that can be assigned
4 'Undo' button: Undo previous action
'Redo' button: Redo previous action
5 'Previous assignable element' button: Navigate to the previous assignable
element
6 'Next assignable element' button: Navigate to the next assignable element
7 Status line for displaying errors, warnings, and information
134 | 406
Importing configuration data
10
10.6.1 Importing hardware
Only ↑ detector lines for which line cards are readily available can be imported.
To import a line card of a specific type, for example, this line card must be
available in the station.
w A 'Site' has been created.

w At least one ↑ 'Station' has been created.
w All required line elements have been created.
1. In the menu bar, click on 'Edit' > 'Import lines...'.
2. Confirm with 'Yes'.

3. Select the import file.
a The 'Import dialog' window opens. The elements contained in the import file
are displayed on the left-hand side of the window. The elements contained
in your 'Site' are displayed on the right-hand side of the window.
4. In the drop-down menu, select the 'Hardware' structure tree.
5. Select the line or line element you wish to assign on the left-hand side of the
window.
a If the selected element also appears in your 'Site' , it is highlighted in bold

on the right-hand side of the window.
135 | 406
6. Click on the small arrows on the right to open the structure tree.
7. Select the corresponding element on the right to assign it to the element from
the import list.
8. Click on 'Import'.
9. Repeat steps 5 to 8 until all elements have been imported.
10. Go to the 'Control' structure tree to import controls.
– See chapter 'Importing controls [➙ 137]'.
– Or
11. Click on 'Close'
a The data has been imported.
Following the import, the serial number for the interactive devices shows as "0000
0000". However, the serial number has been saved correctly internally. When the
↑ site is reopened, the correct serial number is displayed.
136 | 406
Importing configuration data
10
10.6.2 Importing controls
Import of combined controls

Combined controls must be adapted manually following import. See chapter
'Adapting controls [➙ 139]'.
w A 'Site' has been created.

w At least one ↑ 'Station' has been created.
1. In the open 'Import dialog' window, go to the 'Control' structure tree in the drop-
down menu.
– Or
2. In the menu bar, click on 'Edit' > 'Import lines...'.
3. Confirm with 'Yes'.

4. Select the import file.
a The 'Import dialog' window opens. The elements contained in the import file
are displayed on the left-hand side of the window. The elements contained
in your 'Site' are displayed on the right-hand side of the window.
5. In the drop-down menu, select the 'Control' structure tree.
6. Select the control you wish to assign on the left-hand side of the window.
a If the selected element also appears in your 'Site' , it is highlighted in bold

on the right-hand side of the window.
137 | 406
7. Click on the small arrows on the right to open the structure tree.
8. Select the corresponding element on the right to assign it to the element from
the import list.
9. Click on 'Import'.
10. Repeat steps 6 to 9 until all elements have been imported.
11. Click on 'Close'
a The data has been imported.
10.6.3 Error log

The FS20 system logs all import operations performed and all messages. The log
contains useful information for troubleshooting. It can be filtered by the following
message types:
● Error
● Warning
● Info
● Debug
To open the import log:

w You have performed at least one import operation.
l In the menu bar, click on 'Edit' -> 'Show import log'
138 | 406
Adapting configuration
10
10.7 Adapting configuration
10.7.1 Adapting the number of channels per zone

1. Select the 'Detection' > 'Detection area' > 'Section' > 'Zone' task card.
2. Assign all channels with addresses >99 to a different 'Zone'.
– Select the channel and hold down the mouse button to drag it to a different
'Zone'.
3. Correct the address of the channel on the 'Overview' tab to value between 1
and 99.
10.7.2 Adapting controls

Migrating a combined control from AlgoRex to FS20:
● In FS20, a temporary 'AlgoRex migration control group' is created with
'AlgoRex migration controls' and, if applicable, 'Fire controls'.
● Site configurations with 'AlgoRex migration control groups' are considered
faulty and cannot be loaded to the 'Station'.
● The site configuration has to be adapted manually.
● Once adapted, the 'AlgoRex migration control group' must be deleted, together
with the 'AlgoRex migration controls'.
Adapting controls manually

In the example below, the migration from AlgoRex to FS20 has already been
performed and the control elements are available in the FS20 site configuration.
139 | 406
10 Adapting configuration
Example scenario
1. Create a new 'Fire control group'.

2. Move the entire 'Fire control' under the 'AlgoRex migration control group' into
the newly created 'Fire control group', e.g., by holding down the mouse button
and dragging the element or by using 'Cut' and 'Paste'.
3. Create a new 'Universal evac control' under the 'Evac control group'.
4. Move the desired effects from the 'AlgoRex migration control' to the effects in
the newly created 'Universal evac control', e.g., by holding down the mouse
button and dragging the element or by using 'Cut' und 'Paste'.
5. In the 'AlgoRex migration control', select all causes under 'Migrated causes'.
140 | 406
10
6. Select the 'Edit' > 'Replace element' menu item.

7. In the 'Replace element' window, select the correct type and template, then
click on 'Replace'.
8. Move the causes from the 'AlgoRex migration control' to the causes in the
newly created 'Universal evac control', e.g., by holding down the mouse button
and dragging the element or by using 'Cut' and 'Paste'.
9. Delete the empty 'AlgoRex migration control group'.
10.7.3 Setting visibility

The 'Visibility' defines which parts of a ↑ 'Site' can be viewed or operated on a
↑ 'Station'.
'Visibility' configuration settings in AlgoWorks are not included in the import

operation. Set the 'Visibility' after the import.
You will find more information on 'Visibility' in chapter Visibility [➙ 313].
10.7.4 AlgoRex: Creating base sounders for FDnet/C-NET

devices
No base sounders are created during the migration from AlgoRex FDnet devices
to FS20.
Creating 'Base sounder'

w In AlgoRex, the FDnet device (Struct 1417) was assigned to a 1560, 1564, or
1565 element.
l After migration: Create the 'Base sounder' element under the device.
Link [➙ 77]
In AlgoRex, an FDnet device may be assigned to several base sounders. In

FS20, a device may only be assigned to one base sounder. During the migration
from AlgoRex to FS20, only the first link was migrated with a base sounder.
141 | 406
10.7.5 Correcting the AnalogPLUS address

The AnalogPLUS I/O module DC1136 has 2 D-bus addresses. Since the D-bus
addresses are no longer visible in the FS20, this multiple reservation is also no
longer visible on the ↑ line card in the tool.
Importing a line containing a DC1136 creates an address gap. This gap must be
corrected or closed manually in FS20.
To correct the address gap, proceed as follows:
w An AnalogPLUS I/O module DC1136 has been imported.
1. Select the AnalogPLUS I/O module DC1136.
2. Click on 'Edit' > 'Change element address: -1'
You will find a detailed description of reducing the address of elements in chapter
"Re-addressing elements".
See also
2 Re-addressing elements [➙ 84]
10.7.6 AnalogPLUS/Interactive: Correcting multiple verification

DC1192c, DC1151, CB320A
AlgoRex has the elements EL col. det. 1/2/3, structureNo: 1510/1511/1512. The
multiple verification of the alarms will change depending on to which of these
elements the conventional detector channel of peripheral devices DC1192c,
DC1151 or CB320A has been assigned.
Alarm verification is modeled differently in FS20. The collective detector channel
has the 'Pulse memory' property.
Because of these differences in modeling, the alarm verification of the peripheral
devices DC1192c, DC1151, or CB320A is not transferred automatically when
configuration data is imported from AlgoRex. The 'Pulse memory' must be reset.
142 | 406
10
To set the 'Pulse memory' property, proceed as follows:

w The corresponding line device is imported.
1. Select the line element.
2. Select the property from the 'Pulse memory' drop-down list.
Values in brackets lie outside the authorized range.
You will find additional information in the chapter 'Setting the properties of the line
devices'.
See also
2 Setting the properties of the line devices [➙ 178]
10.7.7 Interactive: Correcting DCW1151/DOW1171 assignment

The following description is for the import and commissioning of interactive line
cards which use the ↑ radio gateway with the DWA1151 switching unit and contain
the following devices:
● DCW1151 wireless fire detection system
● DOW1171 radio smoke detector
The following correction does not have to be made when using the radio gateway
with the DWA1151 switching unit.
The DCW1151 wireless fire detection system and the DOW1171 radio smoke
detector are not recognized as wireless devices in Algorex.
Following the import of interactive line cards in FS20, the DCW1151 wireless fire
detection system is displayed in the system as a DC1154 input/output module and
the DOW1171 radio smoke detector is displayed as a DF1191 flame detector.
With this configuration, the radio system can also be operated on the AlgoRex
EP5. The full functional scope of the radio gateway can be configured with the EP7
version of the DCW1151 fire detection system (DCW1151-B). The digital output
channel of the DC1154 input module is not needed for this application.
The input channel must be assigned for battery monitoring.
The output channel only has to be configured if the output contact of the DCW1151
wireless fire detection system is being used. The output channel must not be
configured as a monitored output with feedback to the input; otherwise, an error
message will be displayed after the output is activated.
NOTICE
Incorrect assignment of the DOW1171 radio smoke detector will suppress the
output of warnings about low battery charge levels.
Your device may fail unnoticed due to a discharged battery.
● Replace the imported devices and check the assignment in 'Detection tree'.
143 | 406
Correcting the assignment

Proceed as follows to replace the imported devices:
w An interactive line card containing a DCW1151 wireless fire detection system
or a DOW1171 radio smoke detector has been imported.
1. In the 'Taskcard' 'Hardware', select the DCW1151 wireless fire detection
system displayed as a DC1154 or the DOW1171 radio smoke detector
displayed as a DF1191.
2. Click on 'Edit' -> 'Replace element'.
3. Click on 'Replace'.
a DC1154 becomes DCW1151 (DC1154) or DF1191 becomes DOW1171

(DF1191).
Once the devices have been replaced, the serial number shows as "0000 0000".
However, the serial number has been saved correctly internally. When the site is
reopened, the correct serial number is displayed.
In the case of an import, the replacement triggers an error in the 'Detection tree'.
The logical channel to which the DOW1171 is assigned must be deleted and re-
assigned. This step must be carried out in the event of recommissioning.
The ↑ parameter sets for the DOW1171 cannot be set or selected until after the
devices have been replaced.
In the case of recommissioning, the input channel of the DCW1151 (DC1154) must
be assigned in a zone so that battery trouble can be reported. The output channel
of the DCW1151 (DC1154) corresponds to the normal output channel of the
DCW1151-B and must be assigned if necessary.
You will find more information about this topic in chapter 'Integration in AlgoRex
control panel' in document 'DCW1151, DOW1171 wireless fire detection system',
doc. no. 1787.
The 'Replace element' action can be undone by repeating the process.
144 | 406
Loading the configuration in the 'station'
10
10.7.8 Adapting properties

Due to the differences in modeling, the following properties are not imported into
FS20 automatically and are lost during the import process. Adapt the following
properties manually:
In AlgoWorks In FS20 Applies to Differences More information

Action text Action text Detection task Action texts are predefined in Configuring the 'Zone'
card > Zones AlgoWorks and assigned to the [➙ 216]
corresponding zones. In FS20,
action texts are entered directly
in the corresponding field.
V2 Investigation ↑ Detector In AlgoWorks, the investigation Alarm verification
time (t2) lines, collective time is set for individual zones. concept (AVC) [➙ 194].
detector lines In FS20 the investigation time Setting the properties of
is set for areas. When a new the collective detector
area is created in FS20, a line [➙ 176]
default value of 5 minutes is set
for the investigation time.
If necessary, you can also set
investigation times for
individual zones separately in
FS20.
ALERT sound, 'ALERT' tone Alarm sounders In AlgoWorks, the properties of Properties of the base
EVAC sound and 'EVAC and audible alarm sounders and audible sounder [➙ 157]
tone' bases on FDnet bases are set on the Alarm sounder and
detector lines transponder. In FS20 these interbase [➙ 160]
properties are set in the detail
editor.
I/O mode 'Output mode' Interactive In AlgoWorks, the value of Inputs/outputs [➙ 172]
inputs/outputs 'Output mode' is set in
checkboxes. In FS20, the value
is set via a drop-down list.
10.8 Loading the configuration in the 'station'

See also
145 | 406
10 Completing migration
10.9 Completing migration
You will also find important information in 'Import information report'.
You will find more information about creating reports in chapter Creating reports
[➙ 101]
10.9.1 Exporting an SIB-X

For management systems like the MM8000, you need the configuration data in
SiB-X format. SiB-x is an exchange format for configuration data.
Export the configuration data in SiB-X format as follows:
1. Open a ↑ 'Site' via the 'File' > 'New site' or 'Open' menu item.
2. Click on the 'File' > 'SiB-X export' menu item.
a The 'SiB-X export' window opens.
3. Select the 'Stations' you want.

4. Select the path, enter a file name, and click on 'Start'.
a The configuration data is exported.
146 | 406
Completing migration
10
10.9.2 Deleting import information
NOTICE
Data loss
Once import information has been deleted, it cannot be retrieved.
● Make sure that all necessary information has been imported.
● Create a backup of the configuration before you delete the import information.
An import operation is only complete when the 'Remove import information'

command is executed. This command deletes files that are no longer required and
releases memory space.
When the command is executed, the following information is deleted:
● The import history, i.e., the information about which lines have previously been
imported. If, for example, a file that has previously been imported is imported
again once the import information has been deleted, the line elements that
have previously been imported will also be offered for selection for import.
● Data that was included in the import for the commissioning of management
stations is also deleted.
● The element 'Import info'.
Deleting import information

w You have performed at least one import operation.
l In the menu bar, click on 'Edit' > 'Remove import information'.
a The import information is deleted.
147 | 406
'Hardware' task card
11 Completing migration
11 'Hardware' task card

The components of the ↑ 'Station' and the peripheral devices are shown in the
'Hardware' task card.
The components are automatically read in when the 'Station' is started.
The FDnet devices must be read in with a command on the 'Station'.
Figure 20: Task card with the tree view and table
The devices used with ↑ 'Stations' FC2030 and FC2060 of the collective line as
well as the MS9i detector line must be produced manually in the 'Hardware tree'.
Once the data has been loaded to SintesoWorks, the components of the ↑ 'Station'
and the FDnet devices are visible in the 'Hardware tree'.
Elements such as the 'LED indicator (FTO2002)' can be removed or added if they
were not automatically created.
148 | 406
'Station'
11
11.1 'Station'
Figure 21: Settings in the detail editor

In the detail editor of the ↑ 'Station', the following properties can be set:
● 'Overview' tab:
– 'Customer text' of 'Station'
● 'Details' tab:
– Stopping the local and global ↑ alarming equipment by means of
'Acknowledge', which is activated by 'Immediate intervention type 'manned''
/ 'Immediate intervention type 'unmanned'' or 'Service intervention type
'manned'' / 'Service intervention type 'unmanned''.
– Activation of a message so that the customer is reminded to perform the
maintenance work. 'Maintenance interval [months]' can be set in months.
● 'BACnet Notification Class element' tab, see chapter 'BACnet Notification Class
Element [➙ 389]'.
● 'SintesoView' tab, see chapter 'Configuring permanent access for SintesoView
[➙ 151]'.
● 'Network' tab:
– 'IP address' of the Ethernet port or SAFEDLINK port
● 'Events' tab: 'Event categories' and event texts
● 'Intervention' tab, see chapter 'Intervention concept (IC) [➙ 150]'.
● 'Buzzer' tab:
– 'Element address' and 'Customer text' of the buzzer
– The 'Disable operating terminal buzzer while SintesoView is active'
checkbox defines whether the buzzer should be switched off while
'SintesoView' is active.
● 'Operation' tab: ↑ Visibility on the event categories. Visibility is set on all event
categories as standard. Visibility can also be selected for individual event
categories:
– 'ALARMS'
– 'Pre-ALARMS'
– 'Faults'
– 'Isolations'
– 'Test messages'
– ↑ 'Technical messages'
– 'Activations'
– 'Information'
● 'Control' tab: Indicates to which events the 'Station' is assigned as a cause
element for a control in the 'Control tree'.
149 | 406
11 'Station'
11.1.1 Intervention concept (IC)

The ↑ intervention concept (IC) is a standard configuration for immediate
intervention and service intervention.
Events such as a fault caused by a soiled detector are monitored during a
preconfigured period of time. If the normal operation conditions are not re-
established within this period of time, the maintenance personnel is informed
(service intervention). In this way, it is possible to rectify a fault locally before
informing the maintenance personnel.
You will find a detailed description of the intervention concept in document 008836.
See chapter 'Applicable documents'.
The intervention concept verifies the following event categories:
● 'All faults'
● 'All isolations'
● 'All test messages'
● 'All technical messages'
● 'All activations'
● 'All information messages'
Configuring the ↑ intervention concept
Figure 22: Detail editor with settings for ↑ intervention concept
1. Select the 'Hardware' task card.

2. Highlight a ↑ 'Station' in the tree view.
3. Select the 'Intervention' tab in the detail editor and set the properties you want.
Immediate intervention
The following can be set for immediate intervention:
● Separately for 'Manned operation' and 'Unmanned operation':
– 'Disabled'
– 'Delayed intervention'
– 'Global intervention only'
– 'Local intervention only'
● Time t1 for (intervention) attendance check:
A new event must be acknowledged within this period, otherwise the
↑ intervention concept switches to ↑ global alarming.
● ↑ Alarming equipment:
'RT Fire', 'RT Fault', 'RT 1' - 'RT 8', 'Internal sounder'
150 | 406
'Station'
11
Service intervention
The following can be set for service intervention:
● Separately for 'Manned operation' and 'Unmanned operation':
– 'Disabled'
– 'Delayed intervention'
– 'Direct intervention'
● Time for service intervention ts:
The cause of an event must be remedied within this period, otherwise the
↑ intervention concept activates the service intervention alarming equipment.
● Alarming equipment:
'RT Fire', 'RT Fault', 'RT 1' - 'RT 8', 'Internal sounder'
11.1.2 Configuring permanent access for SintesoView

Permanent access has to be configured for each 'Station' of the ↑ 'Site'.
Configuring permanent access means that access at the 'Station' is not required.
You will find more information on the SintesoView operation modes in chapter
'SintesoView [➙ 67]'.
Configuring permanent access

2. Select the 'Station' for which you wish to configure permanent access for
SintesoView.
3. Select the 'SintesoView' tab in the detail editor.
4. Select the operation mode in the 'Permanent SintesoView access' field.
5. Load the configuration from the PC to the station.
a Permanent access is configured.
Figure 23: Configuring the operation mode for SintesoView
Indicating permanent access

The 'Indicate permanent SintesoView access' checkbox specifies whether
permanent access of SintesoView is indicated at the 'Station' with a message.
151 | 406
11 Onboard I/Os
11.2 Onboard I/Os

The following inputs / outputs are available on the periphery board:
● 'I/O': Configurable inputs / outputs (24 V)
● 'RT fire/NOT monitored': Connection of an ↑ RT channel for RT alarm
● 'RT fire/monitored': Monitored output for RT Alarm
● 'RT fault/NOT monitored': Connection of an RT channel for RT Fault
● 'RT fault/monitored': Monitored output for RT Fault
● 'Sounder/monitored': Monitored sounder output
These inputs and outputs are shown in the 'Hardware tree' under the 'Onboard
I/Os' element.
You will find information on the settings in the detail editor of the inputs / outputs in
chapter 'Inputs/outputs [➙ 172]'.
If the output is assigned to the ↑ effect of a control, you can set additional
properties in the 'Control' tab of the detail editor. You will find a description of these
settings in chapter 'Properties of the assigned effect elements [➙ 237]'.
11.3 FDnet detector line

Setting the properties of an FDnet detector line
'Up to 252 devices allowed per line':

This setting specifies the maximum permissible number of devices per FDnet
detector line:
● Checkbox activated: A maximum of 252 devices are permitted on the
↑ detector line.
● Checkbox deactivated: A maximum of 126 devices are permitted on the
detector line.
'Events' tab
The 'Events' tab allows you to make ↑ AVC settings for line alarms. You will find
more information on this in chapter 'Alarm verification concept (AVC) [➙ 194]'.
Line card (FDnet/C-NET) FCL2001

The ↑ line card (FDnet / C-NET) FCL2001 is used for expanding the integrated
FDnet detector lines and has the same functions. Four ↑ loops or eight ↑ stubs
can be connected to a line card (FDnet/C-NET). The line card (FDnet/C-NET) is
read in automatically.
See also
2 Creating 'Detection tree' [➙ 193]
2 Alarm verification concept (AVC) [➙ 194]
152 | 406
FDnet detector line
11
11.3.1 Automatic fire detectors

Setting properties of an automatic fire detector
2. In the tree view, open the ↑ 'Station' > the ↑ line card > the ↑ loop or the
↑ stub.
3. Highlight an ↑ automatic fire detector.
4. Set the properties you want in the detail editor.
The properties are described in the following sections. Not all properties are
available, depending on the automatic fire detector.
Figure 24: Properties in the detail editor of an automatic fire detector
'Internal AI disabled in idle mode'

This setting specifies whether the internal ↑ alarm indicator of the device is
deactivated in quiescent condition. If the checkbox is activated, then the weak
flashing of the internal alarm indicator will be deactivated in quiescent condition.
This setting can be used in environments in which the flashing would disturb, e.g.
in a theater or cinema. Independent of the setting, the internal alarm indicator lights
up as before when there is an alarm.
If the internal alarm indicator is deactivated, then communication is not possible
between the device and the detector exchanger and tester or the intelligent
detector tester. The internal alarm indicator is temporarily activated and
communication is possible, e.g., for checking the detector, with the command
'Enable MC link' on the ↑ Person Machine Interface of the station. The internal
alarm indicator is deactivated once again with the command 'Disable MC link'.
You will find information for checking detectors in document 009052. See chapter
'Direct activation of external AI'

This setting specifies which conditions must be fulfilled so that the external alarm
indicator is activated directly.
● 'No direct activation': The external alarm indicator is not activated directly.
● 'By the ZONE of the detector in the same base': The conditions are fulfilled
when the event was triggered by any given device in the 'Zone'.
● 'By the DETECTOR in the same base': The conditions are fulfilled when the
event was triggered by the detector with the external alarm indicator.
In the detail editor of the assigned 'Zone', you can set level at which the external
alarm indicator will be activated:
● In 'PRE-STAGE' and 'MAIN STAGE'
● Only in 'MAIN STAGE'
This setting is not possible in 'Zones' without 'PRE-STAGE'.
In addition to the direct activation, you can assign and configure a control with the
external alarm indicator. You will find more information on this in chapter ''Control'
task card [➙ 232]'.
153 | 406
11 FDnet detector line
'External AI activation in detector/walk test'

This setting specifies whether the external alarm indicator is activated in 'Detector
test' or 'Walk test' mode. The checkbox can only be activated if direct activation is
configured for the external alarm indicator.
'Direct activation of base sounder'

This setting specifies which conditions must be fulfilled so that the base sounder is
activated directly:
● 'No direct activation': The base sounder is not activated directly.
event was triggered by the detector with the base sounder.
In the detail editor of the assigned 'Zone', you can set level at which the base
sounder will be activated:
In addition to this setting of the base sounder, you can configure a 'Universal evac
control' and assign it to a base sounder. You will find more information on this in
chapter 'Evac control group [➙ 251]'.
If both the direct activation and the control are active simultaneously with different
output modes ('Alert' and 'Evac') then the base sounder is activated with the mode
'Evac'.
'Base sounder mode'

This setting specifies in which mode the base sounder is activated:
'Alert' or 'Evac'
This setting is in reference only to direct activation, which is configured with the
property 'Direct activation of base sounder'. The mode can be set separately for an
additionally configured control.
154 | 406
FDnet detector line
11
11.3.2 Detector parameter sets
You will find a detailed description of the ↑ parameter sets in the documentation
for the corresponding detector.
The ↑ parameter sets influence the detection behavior of the ↑ automatic fire
detector. This enables the detection behavior to be adapted to the fire phenomena
and environmental influences at the place of installation.
Examples:
● If a fire detector is used in a production hall, a parameter set that is immune to
deceptive phenomena must be selected.
● If the smoke detector is used in a hospital room, a parameter set that ensures
the earliest possible alarming must be selected.
Set parameter set
Figure 25: Detail editor with settings for detector ↑ parameter set

2. In the tree view, open the ↑ 'Station' > the line card > the ↑ loop or the ↑ stub.
3. Open the detector.
4. Highlight the element 'Sensor'.
5. Set the desired parameter set in the detail editor.
With S-LINE detectors, the parameter sets for the 'Manned operation' and
'Unmanned operation' can be set separately. In the case of C-LINE detectors, you
can set only one parameter set.
The available ↑ parameter sets are adapted, depending on the selected sensor
mode. If, for example, you select the sensor mode '1: T only', then only the
parameter sets for heat detectors will be displayed.
155 | 406
11.3.3 Sensor mode with multi-sensor fire detectors

In the case of multi-sensor fire detectors, you can set which sensor is to be used.
Setting the sensor mode
Figure 26: Properties in the detail editor of the sensor of a multi-sensor fire detector

↑ stub.
3. Open the multi-sensor fire detector, e.g. FDOOTC241.
4. Highlight the element 'Sensor'.
5. In the detail editor, select the desired sensor mode with the property 'Sensor
operating mode':
– '0: OOT(C)': Application as neural fire detector
– '2: O only': Application as smoke detector
– '1: T only': Application as heat detector
The available ↑ parameter sets are adapted, depending on the selected sensor
mode. If, for example, you select the sensor mode '1: T only', then only the
parameter sets for heat detectors will be displayed.
156 | 406
FDnet detector line
11
11.3.4 Base sounder
11.3.4.1 Properties of the base sounder

Setting the properties of the base sounder
↑ stub.
3. Open a detector with a base sounder.
4. Highlight the element 'Base sounder'. 1
5. Set the properties you want in the detail editor. The properties are described in
the following sections.
1 If the element 'Base sounder' was not created automatically at the time of read-in,
then you must create it manually. You will find more information on this in chapter
'Creating base sounder [➙ 158]'.
Figure 27: Properties in the detail editor of a base sounder
'ALERT tone'
This setting specifies the tone in the 'Alert' mode.
'EVAC tone'
This setting specifies the tone in the 'Evac' mode.
'Sounder volume'
This setting specifies the sound level in the activated status.
157 | 406
11.3.4.2 Creating base sounder

If the product version of the sounder base FDSB291 or of the fire detector in the
sounder base FDSB291 is <30, then the 'Base sounder' element is not
automatically created when the FDnet devices are read in. If this is the case, then
you must create the 'Base sounder' element manually.
You will find the product version (ES) on the type plate of the device.
ES
Figure 28: Type label of the sounder base
ES
Figure 29: Type label of the fire detector
Creating 'Base sounder' element

1. In the 'Hardware' task card, select > ↑ 'Station' > 'FDnet line card
(onboard/FCL2001)' > 'Line'.
2. Create the element 'Base sounder' for the detector inserted in the sounder
base. Link [➙ 77]
158 | 406
FDnet detector line
11
11.3.5 External alarm indicator

Some FDnet devices have an output for an ↑ external alarm indicator. The output
can be used to actuate an external alarm indicator and for controls.
Setting the properties of the external alarm indicator

↑ stub.
3. Open the device with one output for an external alarm indicator.
4. Highlight the element 'Ext. AI'.
Figure 30: Properties in the detail editor of one output for an external alarm indicator
'Output mode'
The setting defines the behavior of the output signal in the active or inactive status
of the logic. Examples:
● 'Inactive: Off / active: On': The output signal is deactivated when the logic is
inactive and activated when it is active.
● 'Inactive: Off / active: Intermittent, fast (0.25s/0.25s)': The output signal is
deactivated when the logic is inactive. When the logic is active, it is 0.25 s
HIGH and 0.25 s LOW (alternating).
● 'Always Off': The output signal is deactivated when the logic is either inactive or
active.
'Output fail safe position'

This setting specifies the position of the output if the communication between
device and line interface is disrupted or if the line voltage fails.
159 | 406
11.3.6 Alarm sounder and interbase

You can configure the properties for the acoustic and optical alarming for the
following devices:
● Alarm sounder FDS221
● Alarm sounder with supplementary optical indication FDS229
● Sounder interbase FDSB221
● Sounder beacon interbase FDSB229
Setting properties of the alarm sounders and interbases

3. Open the element 'FDS221', 'FDS229', 'FDSB221' or 'FDSB229'.
4. Highlight the element 'Sounder' or 'Sounder beacon'.
Figure 31: Properties in the detail editor of the element 'Sounder'
Figure 32: Properties in the detail editor of the element 'Sounder beacon'
'ALERT tone'
This setting specifies the tone in the 'Alert' mode.
'EVAC tone'
This setting specifies the tone in the 'Evac' mode.
'Sounder volume'
This setting specifies the sound level in the activated status.
'Beacon activation'
This setting specifies the activation mode of the beacon.
This property is available only for FDS229 and FDSB229.
160 | 406
FDnet detector line
11
'Flashing pattern'
This setting specifies the flashing pattern of the beacon. If you select a flashing
pattern with a self-test function, then the beacon will light up briefly every couple of
hours. If you do not want the beacon to light up during ↑ normal operation, then
you must select a flashing pattern without self-test function.
This property is available only for FDSB229.
You will find additional information on the interbases and alarm sounders in the
following documents:
FDS221: Document 008109
FDS229: Document 010095
FDSB221 and FDSB229: Document A6V10320090
See also
11.3.7 Aspirating smoke detector
You will find more information about the aspirating smoke detectors in document
A6V10334410. See chapter 'Applicable documents'.
The elements 'FDA221' and 'FDA241' each contain the following physical
channels:
● 'Sensor 1'
● 'Sensor 2'
● 'Air flow'
● 'ASD info'
WARNING
Incorrect sensor link for the FDA221 and FDA241
If the FDA221 or FDA241 sensors are assigned to different 'Zones', the detection
behavior corresponding to the ↑ parameter set is not guaranteed.
● Assign both FDA221 or FDA241 sensors to the same 'Zone' in the 'Detection
tree'.
Setting the properties of the aspirating smoke detector

↑ stub.
3. Open the element 'FDA221' or 'FDA241'.
4. Highlight a physical channel.
161 | 406
Properties of the elements 'Sensor 1' and 'Sensor 2'
Figure 33: FDA221: Settings in the detail editor of the element 'Sensor 1'
Figure 34: FDA241: Settings in the detail editor of the element 'Sensor 1'
'Parameter set'
This setting specifies the ↑ parameter set of the detector for 'Manned operation'
and 'Unmanned operation'.
'Parameter set 'manned''

This setting specifies the ↑ parameter set of the detector for 'Manned operation'.
'Parameter set 'unmanned''

This setting specifies the ↑ parameter set of the detector for 'Unmanned operation'.
'Sensor operating mode FDA' ('Sensor 1' only)

This setting specifies the sensor mode of the detector.
Properties of the 'Air flow' element
Figure 35: Settings in the detail editor of the element 'Air flow'
'Purge mode'
This setting specifies the cleaning mode of the air flow tube.
'Max. allowed air flow deviation'

This setting specifies the maximum allowable air flow deviation from the air flow at
the time of commissioning. Values in brackets are outside the authorized range.
'Air flow fault delay'

This setting specifies how long the fault message is delayed if the air flow is
outside the valid range.
See also
162 | 406
FDnet detector line
11
11.3.8 Input/output module FDCIO223
You will find more information on input / output module FDCIO223 in document
The input/output module FDCIO223 has two inputs/outputs, which can be used as
follows:
● Connection of ↑ collective detector lines
● Connection of sounder lines
● Monitored output
● Monitored input
If the product version of your input/output module FDCIO223 is ≥40, you can use
the inputs/outputs in mixed operation, i.e. you can use an input/output module for
two different applications from among the ones listed above. You will find the
product version (ES) on the type plate of the input/output module.
Siemens Switzerland Ltd.

Fire Safety & Security Products
FDCIO223
S24218-B102-A1 40 ES
EN54-18:2005
EN54-17:2005 G206054
IdNr.
SW-Vers.
Swiss Made
Figure 36: Type plate of input/output module FDCIO223
You will find more information on input/output module FDCIO223 in document

163 | 406
Setting the properties of the 'Collective/input/sounder/output' element

3. Open the element 'FDCIO223'.
4. Highlight the element 'Collective/input/sounder/output'.
The properties are described in the following sections. Only certain properties are
available, depending on how the element 'Collective/input/sounder/output' is
configured. If the element 'Collective/input/sounder/output' is configured as a
↑ collective detector line, for example, then you can only set the properties in the
range 'Collective line'. The other properties are grayed out.
Figure 37: Properties in the detail editor of the ↑ physical channel of the input / output module
FDCIO223
'Collective line type'

This setting specifies which type of ↑ collective detector line is connected.
'Coll. line: alarm response / fault delay'

This setting specifies the alarm reaction time and the fault delay time of the
↑ collective detector line. The alarm reaction time refers to the device's internal
alarm verification. Values in brackets are outside the authorized range.
'Input inverted'
This setting specifies whether the input is inverted.
● Checkbox activated: Input is active when signal is changing from HIGH to
LOW.
● Checkbox deactivated: Input is active when signal is changing from LOW to
HIGH.
'Input monitoring':
This setting specifies the monitoring of the input:
● Monitoring for open line
● Monitoring for short circuit and open line
● No monitoring
'ALERT mode'
This setting defines the behavior of the output signal in the 'Alert' mode for the
active or inactive status of the logic.
'EVAC/output mode'
● Use as sounder line: The setting defines the behavior of the output signal in the
'Evac' mode for the active or inactive status of the logic.
● If used as a monitored output: This setting defines the behavior of the output
signal in the active or inactive status of the logic.
164 | 406
FDnet detector line
11
'Sounder line/output: fault delay'

This setting specifies the delay time for the transmission of faults of the sounder
line or of the output, respectively. Values in brackets are outside the authorized
range.
'Sounder line/output: load resistor'

This setting specifies the load resistance for the monitoring of the sounder line or of
the output, respectively.

'Enable temporary freeze of output position'

If the checkbox is checked, the 'Freeze selected outputs ON' command is available
for the output. The position of the output is not changed if the ↑ 'Station' or line is
restarted, a configuration is loaded to the 'Station', or a module is reset.
See also
2 Collective detector line via input/output module FDCIO223
or zone module [➙ 225]
2 Sounder line via input/output module FDCIO223 [➙ 279]
2 Input/output module FDCIO223 with monitored
input/output [➙ 282]
165 | 406
11.3.9 Zone module FDCI223

The zone module FDCI223 is operated on the 'FDnet' and has one input. The
following ↑ detector lines can be connected to the input:
● ↑ Collective detector line
● Collective detector line for areas at risk of explosion (zones 1 and 2)
● Conventional detector line
Setting the properties of the 'Collective' element

3. Open the element 'FDCI223'.
4. Highlight the element 'Collective'.
The properties are described in the following sections.
Figure 38: Properties in the detail editor for the ↑ physical channel of the zone module

'Coll. line: alarm response / fault delay'

This setting specifies the alarm reaction time and the fault delay time of the
↑ collective detector line. The alarm reaction time refers to the device's internal
alarm verification. Values in brackets are outside the authorized range.
166 | 406
Power supply
11
11.4 Power supply

Operation modes
The power supply for the ↑ 'Stations' has the following operation modes:
● Operation with battery backup
– The power supply unit feeds the hardware with system voltage,
continuously charging the batteries. In the event of mains voltage failure,
the batteries take over the power supply of the 'Station' without interruption.
● Operation without battery backup
– The power supply unit feeds the hardware with system voltage. The
emergency power supply is ensured via an externally buffered network.
● Operation with an external DC power supply unit
– The supply comes directly via a 24 V feed line. This is the normal operation
mode for the fire terminal FT2040.
● Operation with redundant supply
– The fire terminal can be supplied with a 24 V voltage through a fire control
panel. In accordance with EN 54, a redundant supply source is required in
this case. The fire terminal board is therefore provided with two
independent DC supply inputs.
Features
The following properties can be set for the power supply:
● Mains supervision: Monitoring for power loss.
● Battery supervision: Monitoring switched on or off.
● Converter supervision: Monitoring switched on or off.
● ↑ Emergency power operation: Delay time for fault display in the case of power
loss.
Setting properties
Depending on the operation mode, certain forms of monitoring must be ↑ switched
off. Normally when the station is equipped with a power supply unit and batteries,
no monitorings need deactivating. The configuration of the delay time for the fault
indication in case of a power failure is independent from the operation mode.
Figure 39: Detail editor with settings for the power supply
To set the properties, proceed as follows:
2. Open a 'Station' in the tree view.
3. Highlight 'Power supply FC' or 'Power supply FT'.
4. Activate/deactivate the checkboxes as indicated in the following table in the
'Overview' tab of the detail editor.
167 | 406
11 Power supply
Operation mode 'Mains 'Battery 'Converter Display delay

supervision supervision supervision 'Emergency
enabled' enabled' enabled' power delay',
'Enabled'
With battery √ √ √ √ or –
backup
Without battery √ – √ –
backup
With an external – – – –
DC power supply
unit
With redundant √ √ – √ or –
supply
Table 3: Configuration of the power supply
√ Checkbox checked
– Checkbox unchecked
You will find the hardware configuration in document 009052. See chapter
See also
168 | 406
I/O cards
11
11.5 I/O cards

I/O card (programmable) FCI2008-A1
The I/O card (programmable) FCI2008-A1 has 12 programmable inputs / outputs.
I/O card (remote transmission) FCI2007-A1

The I/O card (remote transmission) FCI2007-A1 has eight inputs / outputs for alarm
and fault transmission.
I/O card (horn/monitored) FCI2009-A1

The I/O card (horn / monitored) FCI2009-A1 has eight monitored outputs for alarm
and fault transmission.
You will find additional information on the I/O cards in document 008837. See
Create I/O card

1. Select 'Hardware' > ↑ 'Station' in the task card.
2. Create the I/O card for the 'Station'. Link [➙ 77]
Setting the properties of the I/O cards

In the detail editor of the elements 'I/O card (remote transm., FCI2007)' and 'I/O
card (horn/monitored, FCI2009)', you can set the following in the 'Details' tab:
Figure 40: Settings in the detail editor of an I/O card

'Sounder output monitoring': This setting specifies in accordance with which
standard the outputs will be monitored. You will find more information in document
The properties of the inputs / outputs of an I/O card are described in chapter
'Inputs/outputs [➙ 172]'.
See also
169 | 406
11 LED indicator FTO2002
11.6 LED indicator FTO2002

Creating 'LED indicator (FTO2002)' element
1. Select 'Hardware' > ↑ 'Station' in the task card.
2. Create the 'LED indicator (FTO2002)' element for the 'Station'. Link [➙ 77]
3. Highlight the element 'LED indicator (FTO2002)'.
4. Enter the address in the 'Element address' tab of the detail editor, which is set
on the LED indicator with the S15 switch. Address range: 20…35.
You will find more information on the LED indicator and the S15 switch in
document 008837. See chapter 'Applicable documents'.
When the hardware is read-in, the address set in the LED indicator is
automatically transferred in SintesoWorks.
Properties of the 'LED indicator (FTO2002)' element

In the detail editor of the 'LED indicator (FTO2002)' element, the following can be
set on the 'Details' tab:
Figure 41: Properties in the detail editor of the LED indicator

'Suppress LED test': This setting specifies whether an LED test is also carried out
on the LED indicator when an LED test is performed on the connected ↑ 'Station'.
If the 'Suppress LED test' checkbox is activated, a LED test is not carried out on
the LED indicator.
170 | 406
Ethernet switch (modular) FN2012
11
11.7 Ethernet switch (modular) FN2012
IP address
The IP address of the FN2012-A1 is configured in the following element:
● 'Network' task card > 'Global system configuration' > 'FS20 network
configuration' > 'Ethernet sub-net' > 'Connections' > 'Station with the FN2012-
A1' > 'Overview' tab > 'IP address network switch' field
Resetting the network configuration

If the 'Reset network configuration' command is executed in the 'Network' menu,
the IP address of the FN2012-A1 is set to 192.168.99.x. The network mask is set
to 255.255.248.0.
Commissioning
In document 009052, you will find a description of how to commission an FN2012-
A1 that is connected to the station via a ribbon cable. See chapter 'Applicable
documents'.
Redundancy management
You can configure redundancy management for Ethernet networks with several
elements of the 'Ethernet switch (modular, FN2012)' type in the 'Redundancy
management configuration' element in the 'Network' task card. Link [➙ 371]
Standalone FN2012
Standalone FN2012-A1 devices that are not connected to the station cannot be
configured in Engineering Tool. You will find more information on commissioning
standalone FN2012-A1 devices in document 009052. See chapter 'Applicable
documents'.
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.
171 | 406
11 Inputs/outputs
11.8 Inputs/outputs
Setting the properties of the inputs/outputs
2. Open the ↑ 'Station' in the tree view.
3. Open the element with the inputs/outputs, e.g. an I/O card, an input/output
module or the onboard I/Os.
4. Highlight an input/output.
The properties are described in the following sections. Not all properties are
available, depending on the input/output.
Properties in the 'Overview' tab of an input
'Input inverted'
● Checkbox activated: Input is active when signal is changing from HIGH to
LOW.
● Checkbox deactivated: Input is active when signal is changing from LOW to
HIGH.
'Short circuit monitoring enabled'

This setting specifies whether the monitoring is activated when there is a short
circuit. The short circuit monitoring requires a special wiring.
If the short circuit monitoring is deactivated, then a short circuit is evaluated as
'active'. This can be used for the connection of old detectors with bimetallic
switches or of manual call points with switches. For these applications, you must
deactivate the short circuit monitoring and assign the input to a 'Zone'.
'Suppress fault message upon 'open line' on input'

If the checkbox is checked, open line monitoring of the input / output module is
suppressed on the control panel.
If the input is operated without an EOL resistor, the checkbox must be checked.
Properties on the 'Overview' tab of an output with monitoring
172 | 406
Inputs/outputs
11
'Output mode'
● 'Inactive: Off / active: On': The output signal is deactivated when the logic is
inactive and activated when it is active.
● 'Inactive: Off / active: Intermittent, fast (0.25s/0.25s)': The output signal is
deactivated when the logic is inactive. When the logic is active, it is 0.25 s
HIGH and 0.25 s LOW (alternating).
● 'Always Off': The output signal is deactivated when the logic is either inactive or
active.

'Enable temporary freeze of output position'

If the checkbox is checked, the 'Freeze selected outputs ON' command is available
for the output. The position of the output is not changed if the ↑ 'Station' or line is
restarted, a configuration is loaded to the 'Station', or a module is reset.
'Output monitoring'
This setting defines the jumper position of the device for configuring output
monitoring.
See also
173 | 406
11 Creating the line card
11.9 Creating the line card

You can create the following line cards for fire control panels FC2030, FC2060 and
FC2080:
● Line card (FDnet/C-NET)
● Line card (collective)
● Line card (MS9i)
● Line card (AnalogPLUS)
● Line card (interactive)
● Line card (interactive, Ex)
Allocating addresses
In the case of control panel FC2030, the line cards are assigned addresses 111 to
112. In the case of control panels FC2060 and FC2080, the line cards are
assigned addresses 111 to 115. The cards in the card cage are addressed from
right to left.
Creating the line card

1. In the 'Hardware' task card, select a > ↑ 'Station' of type FC2030, FC2060, or
FC2080.
2. Create one of the elements below for the 'Station'. Link [➙ 77]
– 'FDnet line card (onboard/FCL2001)'
– 'Interactive line card (FCL2006)'
– 'Interactive Ex line card (FCL2007)'
– 'AnalogPLUS line card (FCL2005)'
– 'MS9i line card (FCL2003)'
– 'Collective line card (FCL2002)'
3. Enter customer texts.
174 | 406
Collective detector line
11
11.10 Collective detector line

Eight collective ↑ stubs can be connected to the FCL2002 ↑ line card (collective).
The following detector systems are supported: MS7, MS9, MS24, DS11, Sinteso
multi-protocol (e.g. FDOOT241-9), SynoLINE600 and SIGMACON
You will find a list of the supported detectors in document 'List of compatibility'.
Although the ↑ line card (collective) is read in, the ↑ collective detector line must
always be fully pre-configured.
Configuring the ↑ collective detector line

1. Create a suitable ↑ 'Station'. Link [➙ 76]
2. Create the ↑ line card (collective).
3. Create the 'Zones' and assign it to the collective detector lines. Link [➙ 175]
4. Set the properties of the collective detector line. Link [➙ 176]
5. Set the properties of the line devices. Link [➙ 178]
You will find additional information about the individual steps on the specified
pages.
11.10.1 Creating 'Zones' and assigning them to collective detector

lines
2. Create the logical elements as far as the 'Zone' level. Link [➙ 193]
3. Assign the 'Zone' to a 'Devices' element / event category 'Collective' from a
↑ collective detector line in the 'Hardware tree'. Link [➙ 85]
Figure 42: Assigning a 'Zone' to a ↑ collective detector line
See also
175 | 406
11 Collective detector line
11.10.2 Setting the properties of the collective detector line
NOTICE
Incorrect selection of the 'Collective line type'
Damage to detector
● Select the correct 'Collective line type'.
Damage to the detector caused by incorrectly selecting the 'Collective line type'
can only be determined by performing a detector check and cannot be evaluated
by the control panel.
You will find information about the respective 'Collective line type' listed below
and described in document 008836. See chapter 'Applicable documents'.

2. Highlight a ↑ collective detector line in the tree view.
The settings are described in the following sections.
'Overview' tab
Figure 43: Detail editor with settings for the ↑ collective detector line
'Collective line type':
Type of the connected ↑ collective detector line.
Configuration data cannot be loaded in the control panel if the 'Not configured'
setting is selected when the ↑ detector line is assigned. Delete the ↑ assignment
or select the correct detector line type.
If ↑ collective detector lines are not used, then you must select the setting 'Not
configured' for 'Collective line type'.
● 'No grey zone / transzorb diode (20V)':

– For MS24, DS11, Sinteso multi-protocol (e.g. FDOOT241-9) and
SynoLINE600 with transzorb as end-of-line
– Line characteristics: RL <150 Ω, CL <300 nF, CL with detector <4.5 µF, LL
<5 mH
– Detection of a creeping open line or short-circuit
● 'No grey zone / EOL22(Ex)':
– For MS7, MS9, MS24, DS11, Sinteso multi-protocol (e.g. FDOOT241-9),
SynoLINE600 and SIGMACON with EOL22(Ex) as end-of-line
<5 mH
– Detection of a creeping open line or short-circuit
176 | 406
11
● 'Grey zone / 3.3k Ohm' (not VdS 2489-compliant):

SynoLINE600 and SIGMACON with 3.3 kΩ as end-of-line
<5 mH
– This line type can only be used for modernization.
● 'Grey zone / 4.7k Ohm' (not VdS 2489-compliant):
SynoLINE600 and SIGMACON with 4.7 kΩ as end-of-line
<5 mH
– This line type can only be used for modernization.
● 'Not configured':
– Select this setting when the ↑ collective detector line is not used.
'Short circuit = ALARM':
If the checkbox is checked, a short-circuit is evaluated as an alarm on the
collective detector line. Some detector types require this function. Use the 'List of
compatibility' document to check that there are no detector types on the detector
line that do not permit activation of this function. See chapter 'Applicable
documents'.
'Details' tab
Figure 44: Detail editor with settings for collective detector line
'Fault delay':
This setting specifies how long a fault on the ↑ detector line must be present
before a fault message is displayed. In accordance with EN 54, the entered value
may not exceed a maximum of 100 s.
177 | 406
11 MS9i detector line
11.10.3 Setting the properties of the line devices

2. Open a collective detector line in the tree view.
3. Highlight the element 'Devices'.
You can set the following properties in the detail editor of the 'Devices' element:
Figure 45: Detail editor with settings for the line devices
'Pulse memory':
This setting specifies which pulse memory function is used for the alarm
verification. Values in brackets lie outside the authorized range.
● 'None': Alarm signals are brought to the application without further verification.
● 'One stage': ↑ danger level 3 starts a one-stage verification.
● '(Two stage)': Danger level 3 starts a two-stage verification.
11.11 MS9i detector line

The line elements (detectors, input/output modules) connected to the ↑ line card
(MS9i) FCL2003 cannot be read in by the FS20 fire detection system. The line
elements must be created manually. The following element types exist:
● 'MS9i detector': for ↑ automatic fire detectors:
– Base Z90i, Z94i
– Master base Z90Mi, Z94Mi
– Master element E90Mi, collective line or digital input
● 'MS9i MCP': for each manual call point type
● 'MS9i multi master': for the multimaster card K5M010
A total of four must be created from this element, with subordinate addresses.
● 'MS9i module': for the control element E90Ci
Configuring the MS9i detector line

Although the ↑ line card (MS9i) is read in, the MS9i detector line must always be
fully pre-configured.
2. Create the line card (MS9i). Link [➙ 174]
3. Create the line elements and 'Zones' and assign them to one another.
Link [➙ 179]
4. Create the controls and assign them to the line elements. Link [➙ 180]
5. Set the properties of the MS9i detector line. Link [➙ 180]
6. Set the properties of the line elements. Link [➙ 181]
pages.
178 | 406
MS9i detector line
11
11.11.1 Creating and assigning line elements and 'Zones'

You can use the function 'Create and Assign' to create and assign several line
elements to one another in the 'Hardware tree' and the 'Zones' in the ↑ 'Detection
tree' in a single step. While doing so, you can specify the customer texts for the
'Zones'.
Figure 46: Creating and assigning line elements

2. Open 'Station' > 'Detection area' in the tree view.
3. Highlight the element 'Section'.
4. Open the 'Create and Assign' window. The 'Create and Assign' window can be
opened as follows:
– button in the toolbar

– 'Commissioning' > 'Create and Assign' menu item
– Context menu
– <Ctrl> + <K>
5. Select the desired 'Zone' and the element type on the left in the window.
a The 'Hardware tree' is depicted at the right of the window. The elements
that can be assigned are highlighted.
6. Select the MS9i detector line on which you wish to create the line element.
7. In the 'No. of devices:' field, select the template for the 'Zone'.
8. You can enter the customer text of the 'Zone customer text:' in the field 'Zone'.
9. Enter the number of line elements that you wish to create in the 'No. of
devices:' field.
10. Enter the address of the line element in the '(First) device address:' field. If you
create several line elements, enter the address of the first line element.
11. Click on 'Create & Assign'.
a The line element and the 'Zone' are created and assigned.
a If you create several line elements, a 'Zone' is created for each line element.
179 | 406
11 MS9i detector line
You can also create and assign the line elements without the function 'Create and
Assign'. To do so, proceed as follows.
1. Create the line elements in the 'Hardware' task card.

2. Create the 'Zones' in the 'Detection' task card.
3. Assign the line elements to the 'Zones'.
11.11.2 Creating controls and assigning them to line elements

2. Create the logical elements as far as the 'Controls' level. Link [➙ 232]
3. Assign 'Fire control' > 'Causes' to the ↑ 'Detection tree'.
4. Assign 'Fire control' > 'Effects' to 'Output' of 'MS9i module' element.
5. Select the 'New effect dialog' command in the 'Outputs with confirmation'
window.
6. Assign the 'Output' and 'Input' channels of the 'MS9i module' element.
You will find more information on program operation in chapter 'Assigning

elements [➙ 85]'.
11.11.3 Setting the properties of the MS9i detector line

2. Highlight an MS9i detector line in the tree view.
'Overview' tab
Figure 47: Detail editor with settings for the MS9i detector line
↑ 'Loop':
This setting specifies the detector line topology. Activate the checkbox if the MS9i
detector line is a loop.
180 | 406
MS9i detector line
11
'Details' tab
Figure 48: Detail editor with settings for the MS9i detector line
'Fault delay':
'Events' tab
11.11.4 Setting the properties of the line elements

2. Open a line element in the tree view.
3. Highlight the physical channel, e.g. 'Sensor'.
'MS9i detector' and 'MS9i multi master'
Figure 49: Detail editor with properties of the sensor

'Drift supervision enabled':
If the checkbox is activated, then a drift query will be performed regularly for the
device. A drift message is displayed as service information. The drift query can be
used only for devices of the MS9i+ type. The checkbox may not be activated for
other devices.
'Pulse memory':
181 | 406
11 AnalogPLUS detector line
'MS9i module' element
Figure 50: Detail editor with properties of the input

'Inverted':
This setting specifies whether the input or the output is inverted.
● Inverted input: The input is evaluated as active when the input signal is
inactive.
● Inverted output: The output is activated when the assigned control is inactive.
11.12 AnalogPLUS detector line

The line elements (↑ automatic fire detectors, manual call points, input/output
modules) connected to the ↑ line card (AnalogPLUS) FCL2005 cannot be read in
by the FS20 fire detection system. The line elements must be created manually.
You will find more information on the line elements that are supported on the
AnalogPLUS detector line in documents 008836 and 008331. See chapter
Configuring the AnalogPLUS detector line

The AnalogPLUS detector line must always be pre-configured in full.
pages.

2. Create the ↑ line card (MS9i). Link [➙ 174]
3. Create the line elements and 'Zones' and assign them to one another.
Link [➙ 183]
4. Configure the line type. Link [➙ 184]
6. Set the properties of the AnalogPLUS detector line. Link [➙ 184]
7. Set the properties of the line elements. Link [➙ 186]
You will find more information on using AlgoRex data migration to ↑ pre-configure
the AnalogPLUS detector line in chapter 'AlgoRex/SIGMASYS data migration
[➙ 125]'.
182 | 406
11
11.12.1 Creating and assigning line elements and 'Zones'

To create and assign line elements and 'Zones' for the AnalogPLUS detector line,
follow the steps below:
2. Open the ↑ 'Station' > 'Detection area' in the tree view.
3. Highlight the element 'Section'.
4. Open the 'Create and Assign' window.
5. Select the desired 'Zone' and the element type on the left in the window.
Figure 51: Creating and assigning line elements
6. Select the AnalogPLUS detector line on which you wish to create the line
element.
7. In the 'Zone template:' field, select the template for the 'Zone'.
8. You can enter the customer text of the 'Zone customer text:' in the field 'Zone'.
9. Enter the number of line elements that you wish to create in the 'No. of
devices:' field.
10. Enter the address of the line element in the '(First) device address:' field. If you
create several line elements, enter the address of the first line element.
11. Click on 'Create & Assign'.
a The line element and the 'Zone' are created and assigned.
a If you create several line elements, a 'Zone' is created for each line element.
You can also create and assign the line elements without the function 'Create and
Assign'. To do so, proceed as follows.
1. Create the line elements in the 'Hardware' task card.

2. Create the 'Zones' in the 'Detection' task card.
3. Assign the line elements to the 'Zones'.
183 | 406

w The line elements are now available in the 'Hardware tree'.
3. Assign 'Fire control' > 'Effects' to elements of the AnalogPLUS detector line.
– Select the 'New effect dialog' command in the 'Outputs with confirmation'
window.
– Assign the 'Output' and 'Input' channels of the AnalogPLUS elements.
You will find more information on assigning the 'Fire control' element in chapter
'Assigning fire control [➙ 240]'.
11.12.3 Configuring the line type for an AnalogPLUS detector line

The line type configuration for the AnalogPLUS detector line is indicated by the
'Hardware' checkbox on the following tab: 'Overview' task card > AnalogPLUS
detector line > 'Loop'.
Figure 52: Topology configuration
Configuring the AnalogPLUS detector line as a ↑ loop

By default, each AnalogPLUS detector line is pre-configured as a loop. The
checkbox 'Loop' is activated.
Configuring the AnalogPLUS detector line as a ↑ stub

A stub has to be configured manually.
1. Select the ↑ detector line.
2. Select the 'Overview' tab.
3. Uncheck the 'Loop' checkbox.
11.12.4 Setting the properties of the AnalogPLUS detector line

Select the 'Hardware' task card.
1. Highlight the AnalogPLUS detector line in the tree view.
'Overview' tab
↑ 'Loop':
This setting specifies the ↑ detector line topology. You will find more information in
chapter 'Configuring the line type for an AnalogPLUS detector line [➙ 184]'.
184 | 406
11
'Details' tab
Figure 53: Detail editor with settings for the AnalogPLUS detector line
'Fault delay':
'Events' tab
11.12.5 Configuring line element addresses

The addresses of the line elements on the AnalogPLUS detector line are
generated in the order in which the elements are added. You can subsequently
configure the address of a line element on the AnalogPLUS detector line manually.
2. Select a line element on the AnalogPLUS detector line.
3. Go to the 'Overview' tab and enter the address of the line element in the
'Element address' field.
The configurable address of an AnalogPLUS line element is not the same as the
D-bus address. The D-bus addresses are no longer visible in the FS20.
185 | 406

'Sensor' element
Figure 54: Sensor settings

'Multi verification'
● 'Simple': Single signal verification with standard sensitivity
● 'Multi': Multiple signal verification with standard sensitivity
● 'Simple / sensitive': Single signal verification with enhanced sensitivity
● 'Multi / sensitive': Multiple signal verification with enhanced sensitivity
'Input', 'Output' and 'Horn' elements
Figure 55: Input, output and horn settings

'Inverted':
This setting specifies whether the input or the output is inverted.
inactive.
● Inverted output: The output is activated when the assigned control is inactive.
186 | 406
11
'Collective' element
Figure 56: 'Collective' settings

'Pulse memory':
11.13 Interactive detector line

There are two ways to commission the line elements, e.g., ↑ automatic fire
detectors, manual call points, input/output modules, that are connected to the
↑ line card (interactive) or line card (interactive, Ex):
● By reading them into the ↑ 'Station'
● By using AlgoRex data migration to perform ↑ pre-configuration
You will find more information on the line elements that are supported on the
interactive detector line in documents 008836 and 008331. See chapter
Configuring an interactive detector line following data migration

w You have already created a ↑ pre-configuration by carrying out data migration.
Link [➙ 125]
1. Create the 'Zones' and assign it to the interactive detector lines. Link [➙ 188]
3. Set the properties of the interactive detector line. Link [➙ 189]
Configuring an interactive detector line after reading in the line

w You have already commissioned the ↑ detector line. You will find more
information about this in document 009052.
w You have loaded the ↑ 'Station' configuration into 'SintesoWorks'.
1. Create the 'Zones' and assign it to the interactive detector lines. Link [➙ 188]
3. Set the properties of the interactive detector line. Link [➙ 189]
187 | 406
11 Interactive detector line
11.13.1 Creating 'Zones' and assigning them to an interactive

detector line
2. Create the logical elements as far as the 'Zone' level. Link [➙ 193]
3. Assign the 'Zone' to an element from the desired interactive detector line in the
'Hardware tree'. Link [➙ 85]
Figure 57: Assigning a 'Zone' to an interactive detector line

w The line elements are now available in the 'Hardware tree'.
3. Assign 'Fire control' > 'Effects' to elements of the AnalogPLUS detector line.
– Select the 'Outputs with confirmation' command in the 'New effect dialog'
window.
– Assign the 'Output' and 'Input' channels of the AnalogPLUS elements.
You will find more information on assigning the 'Fire control' element in chapter
'Assigning fire control [➙ 240]'.
188 | 406
11
11.13.3 Configuring the line type for an interactive detector line

The line type configuration for the interactive detector line is indicated by the
Hardware' checkbox on the following tab: 'Overview' task card > Interactive
detector line > 'Loop'.
Figure 58: Topology configuration
Configuring the interactive detector line as a ↑ loop

By default, each interactive detector line is pre-configured as a loop. The checkbox
'Loop' is activated.
Configuring the interactive detector line as a ↑ stub

A stub has to be configured manually.
1. Select the ↑ detector line.
2. Select the 'Overview' tab.
3. Uncheck the 'Loop' checkbox.
11.13.4 Setting the properties of the interactive detector line

Select the 'Hardware' task card.
1. Go to the tree view and highlight the interactive or interactive Ex detector line.
'Overview' tab
↑ 'Loop':
This setting specifies the ↑ detector line topology. You will find more information in
chapter 'Configuring the line type for an interactive detector line [➙ 189]'.
'Details' tab
Figure 59: Detail editor with settings for interactive detector line
'Fault delay':
'Events' tab
189 | 406

'Direct activation of external AI'

This setting specifies which conditions must be fulfilled so that the external alarm
indicator is activated directly.
● 'No direct activation': The external alarm indicator is not activated directly.
event was triggered by the detector with the external alarm indicator.
In the detail editor of the assigned 'Zone', you can set level at which the external
alarm indicator will be activated:
In addition to the direct activation, you can assign and configure a control with the
external alarm indicator. You will find more information on this in chapter ''Control'
task card [➙ 232]'.
'External AI activation in detector/walk test'

This setting specifies whether the external alarm indicator is activated in 'Detector
test' or 'Walk test' mode. The checkbox can only be activated if direct activation is
configured for the external alarm indicator.
Figure 60: Settings for multi-sensor smoke detector
'Parameter set'
This setting specifies the detector ↑ parameter set. The parameter set can be used
to configure the detector sensitivity.
Figure 61: Sensor settings
190 | 406
11
'Inverted':
inactive.
'Short circuit monitoring enabled'

This setting specifies whether the monitoring is activated when there is a short
circuit. The short circuit monitoring requires a special wiring.
If the short circuit monitoring is deactivated, then a short circuit is evaluated as
'active'. This can be used for the connection of old detectors with bimetallic
switches or of manual call points with switches. For these applications, you must
deactivate the short circuit monitoring and assign the input to a 'Zone'.
Figure 62: Input settings
'Output mode'
● 'Inactive: Intermittent / active: Off': The output signal is intermittent when the
logic is inactive and switched off when it is active.
● 'Inactive: Off / active: Intermittent': The output signal is switched off when the
logic is inactive and intermittent when it is active.
● 'Inactive: Off / active: On': The output signal is switched off when the logic is
inactive and switched on when it is active.
● 'Inactive: On / active: Off': The output signal is switched on when the logic is
inactive and switched off when it is active.
The 'intermittent' output signal is now supported by 'DC1192h'.

Figure 63: Output settings

191 | 406
'Pulse memory'
Figure 64: Settings for 'Collective' element
192 | 406
'Detection' task card
Creating 'Detection tree'
12
12 'Detection' task card

The following logical elements are shown in the 'Detection' task card:
● 'Area'
– The 'Area' element is also created when creating a ↑ 'Station'.
– Additional 'Area' elements can be created for each 'Station'.
● ↑ 'Section'
– A 'Section' element is also created when creating a 'Station'.
– Additional 'Section' elements can be created for each 'Station'.
● 'Zone'
– The 'Zone'element can be created manually.
● 'Logical channel'
– The 'Logical channel' element can be created manually during ↑ pre-
configuration. But this is not usually necessary because this element is
created when assigning to the corresponding hardware element. If a ↑ link
is deleted, the channel is retained.
If the control panel is configured using the 'Auto-configure line' (FDnet lines only)
or 'Auto-configure station' function, the 'Section', 'Zone', and 'Logical channel'
elements are created automatically. The physical and logical channels are
assigned automatically.
You will find more information about the auto-configuration in document 009052.
See also
12.1 Creating 'Detection tree'

To create the ↑ 'Detection tree', proceed as follows:
1. Select 'Detection' > 'Station' > 'Detection area' > 'Section' in the task card.
2. Use the corresponding template to create a 'Section' for the 'Zone'. Link [➙ 77]
When creating the ↑ 'Detection tree', you can use the functions 'CSV export' and
'CSV import' in order to export and import customer-specific data, e.g., customer
texts. You will find more information on this in chapter 'Exporting and importing
CSVs [➙ 97]'.
See also
2 Exporting and importing CSVs [➙ 97]
193 | 406
12 'Area'
12.2 'Area'
Each ↑ 'Station' contains the following 'Areas':
'Detection area'
'Detection area' is the uppermost element in the ↑ 'Detection tree'. Several
'Detection area' are possible per 'Station':
● FC2020, FC2030, FC2040: Max. 4
● FC2060: Max. 8
● FC2080: Max. 24
The 'Detection area' has an ↑ alarm verification concept (AVC) and can be
configured and assigned to the controls independently of other ↑ areas.
'Station area'
'Station area' occurs just once and unites the alarm verification (AVC) functionality
for hardware-related elements which are not in the 'Detection area'. This includes
e.g collective line alarms and degraded mode operation. The 'Station area' can be
displayed and navigated just like any other 'Detection area'. It has no child
elements and is identical to the 'Detection area' in terms of alarm verification.
12.2.1 Alarm verification concept (AVC)

The ↑ 'Alarm Verification Concept' (AVC) serves the purpose of delayed alarm
transmission and takes into account the interaction of the operating personnel in
the alarming sequence.
In the event of a fire, a local alarm is triggered. The operating staff have a certain
amount of time to investigate the location given for the fire. In case of a ↑ false
alarm or minor incident, the intervention of the fire brigade (global alarm) can be
avoided in good time.
You will find a detailed description of the 'Alarm Verification Concept' in document
You can configure one 'Alarm Verification Concept' each for various event
categories, e.g., for ' --All Fire ALARMS' or 'All Pre-ALARMS'.
Configuring 'Alarm Verification Concept'

2. Highlight 'Detection area' in the tree view.
3. Select the 'Alarm verification' tab in the detail editor.
4. Set the properties you want for the various event categories.
Figure 65: Detail editor with settings for ↑ alarm verification concept
194 | 406
'Area'
12
'LOCAL alarming stopped by ACKN.'

This setting specifies which local ↑ alarming equipment is stopped by the
command 'Acknowledge'. Activate the respective checkbox.
'GLOBAL alarming stopped by ACKN.'

This setting specifies which global alarming equipment is stopped by the command
'Acknowledge'. Activate the respective checkbox.
't1 [EN54-2: t1+t2 of AVC=max. 10 min.]'

This setting specifies the reaction time t1. A new event must be acknowledged
within this period, otherwise the ↑ alarm verification concept or the intervention
concept switches to ↑ global alarming. In accordance with EN 54-2, the total of t1
and t2 must not exceed a maximum of ten minutes.
Figure 66: Detail editor with settings for alarm verification concept
'Alarming type 'manned'' and 'Alarming type 'unmanned''

This setting specifies the type of alarming for 'Manned operation' or 'Unmanned
operation', respectively:
● 'Local alarming only'
● 'Delayed alarming'
● 'Global alarming only'
195 | 406
12 'Area'
'Alarming type 'thermal''

This setting specifies the alarming type for thermal detectors.
● '* Not used *': The alarming type for thermal detectors is not defined. The
settings for 'Alarming type 'manned'' and 'Alarming type 'unmanned'' are used.
● 'Global alarming only': The ↑ AVC changes to ↑ global alarming immediately.
No distinction is made between ↑ 'manned' and ↑ 'unmanned'.
These settings only apply to heat detectors (FDnet, interactive, AnalogPLUS) and
not to the temperature sensors of multi-sensor fire detectors.
'Local alarming devices 'manned'' and 'Local alarming devices

'unmanned''
This setting specifies which local alarming equipment is to be activated in 'Manned
operation' or 'Unmanned operation', respectively. Activate the respective checkbox.
'Global alarming devices 'manned'' and 'Global alarming devices

'unmanned''
These settings specify which global ↑ alarming equipment is to be activated in
'Manned operation' or 'Unmanned operation', respectively. Activate the respective
checkbox.
196 | 406
'Area'
12
Configuring the ↑ AVC settings for the line alarm

2. Highlight a ↑ detector line in the tree view.
3. Go to the 'Events' tab and select the category 'Collective FIRE ALARM (line
alarm) | ------General autom. Fire ALARM'.
4. Configure the AVC settings.
The settings are described in the sections above and below.
Figure 67: AVC settings for the line alarm

'Use individual AVC settings':
This setting specifies which alarming settings are used for the event:
● Checkbox deactivated: The superordinate alarming settings that are specified
in the 'Area' are used for the event.
● Checkbox activated: Individual alarming settings are used for the event. The
associated properties can be set as soon as the checkbox is activated. The
settings are described in the sections above.
– 'Alarming type 'manned'', 'Alarming type 'unmanned'', and 'Alarming type
'thermal''.
– Investigation time t2
– 'Local alarming devices 'manned'' and 'Local alarming devices 'unmanned''
– 'Global alarming devices 'manned'' and 'Global alarming devices
'unmanned''
197 | 406
12 'Area'
12.2.2 Immediate global alarming

The 'Immediate global alarming' setting is used to determine under which of the
following preconditions the ↑ alarm verification concept is directly and globally
alarmed:
● ' - (disabled)'
● 'Upon 2nd alarm within area'
● 'Upon 2nd alarm within area OR fault within station'
● 'Upon 2nd alarm within site'
● 'Upon 2nd alarm OR fault within site'
● 'Always (upon first alarm)'
Figure 68: Detail editor with settings for immediate global alarming
Settings for intervention

If you select the 'Upon 2nd alarm within area OR fault within station' or 'Upon 2nd
alarm OR fault within site' setting for immediate ↑ global alarming, the following
must be observed in the ↑ 'Station' settings:
The setting in the following fields must not be 'Station' for the 'Intervention' category
in the 'IC Fault' tab of the 'Disabled' detail editor:
● 'Immediate intervention type 'manned''
● 'Immediate intervention type 'unmanned''
Always select a defined setting.
Figure 69: Detail editor with settings for 'Station'

If individual devices are not to be activated using 'IC Fault', uncheck the
corresponding checkbox.
198 | 406
'Section'
12
12.2.3 Alarm organization mode

The 'Alarm organization mode' setting determines which statuses and functions,
e.g., switchovers and indicators, of the ↑ alarm organization are used in this 'Area'.
The following can be set:
● 'Always manned (no messages/no LED/no switching fct.)'
● 'Always unmanned (no messages/no LED/no switching fct.)'
● 'Manned/unmanned (with messages/with LED/with switching fct.)'
Figure 70: Detail editor with settings for alarm organization mode
12.2.4 Switching times for 'Unmanned operation'

The time at which ↑ alarm organization automatically switches over to 'Unmanned
operation' can be specified. This is required if, for example, the alarm organization
is manually switched back to 'Unmanned operation' after being automatically
switched over to 'Manned operation'.
Four times can be entered in the 'Overview' tab.
Figure 71: Detail editor with switching times for 'Unmanned operation'
12.3 'Section'
The level ↑ 'Section' is used for the zoning of 'Zones' and has no functions of its
own. In one element 'Section', for example, all 'Zones' can be combined on one
building floor. Doing so facilitates the operation.
199 | 406
12 'Zone'
12.4 'Zone'
The various 'Zone' types are described in the following chapters.
12.4.1 'Automatic zone'

↑ Automatic fire detectors are evaluated in the 'Automatic zone'. The 'Zone' can
however also be configured for inputs or collective detector lines.
You can select between a variety of different templates that are pre-configured for
various applications for the creation of a 'Automatic zone'.
The following table shows the properties of the templates along with the event
category and the event text of the message that is generated with an alarm.
Main features and typical application Typical event category Event text 1
'Single, Standard': ● 'PRE-STAGE': ● 'PRE-STAGE':

● ↑ Single-detector dependency – ' --Pre-ALARM, fire' – 'Pre-ALARM'
● With 'Pre-ALARM' ● 'MAIN STAGE': ● 'MAIN STAGE':
– ' ------General autom. Fire – 'Autom. FIRE ALARM'
ALARM'
'Single, no pre-alarm': ' ------General autom. Fire ALARM' 'Autom. FIRE ALARM'
● Single-detector dependency
● Without 'Pre-ALARM'
'Single, non-latching alarm': ' ------Autom. Fire ALARM, 'Autom. FIRE ALARM'
● Single-detector dependency programmable'
'Single, ALARM sub-system': ● 'PRE-STAGE': ● 'PRE-STAGE':
● Single-detector dependency – ' --Pre-ALARM, fire' – 'Pre-ALARM'
– ' ------General autom. Fire – 'ALARM sub-system'
ALARM'
'Single, Exting. discharged': ● 'PRE-STAGE': ● 'PRE-STAGE':
– ' ------Exting. discharged – 'Exting. discharged'
(Aut. Fire AL.)'
'Single, Exting. pre-alarm': ● 'PRE-STAGE': ● 'PRE-STAGE':
– ' ------Exting. pre-alarm – 'Exting. pre-alarm'
(Aut. Fire AL.)'
'Single, Gas alarm': ● 'PRE-STAGE': ● 'PRE-STAGE':
● Evaluation of gas detectors that are – ' --Pre-ALARM, fire' – 'Pre-ALARM'
connected via an input ● 'MAIN STAGE': ● 'MAIN STAGE':
● Single-detector dependency – ' ------General autom. Fire – 'Gas ALARM'
● With 'Pre-ALARM' ALARM'
200 | 406
'Zone'
12
'Single, Gas warning': ● 'PRE-STAGE': ● 'PRE-STAGE':

● Evaluation of gas detectors that are – ' --Pre-ALARM, fire' – 'Pre-ALARM'
connected via an input ● 'MAIN STAGE': ● 'MAIN STAGE':
● Single-detector dependency – ' ------General autom. Fire – 'Gas warning'
● With 'Pre-ALARM' ALARM'
● Only ↑ local alarming is activated in
'MAIN STAGE'
'Single, door holders': ' ------General autom. Fire ALARM' 'ALARM door holders'
● Only the local alarming is activated in
'MAIN STAGE'
'Single, local ALARM': ● 'PRE-STAGE': ● 'PRE-STAGE':
● Only the local alarming is activated in – ' ------General autom. Fire – 'Autom. local ALARM'
'MAIN STAGE' ALARM'
'Multi, standard': ● 'PRE-STAGE': ● 'PRE-STAGE':
● ↑ Multi-detector dependency – ' --Pre-ALARM, fire' – 'Pre-ALARM'
ALARM'
'Multi, garage': ' ------General autom. Fire ALARM' 'Autom. FIRE ALARM'
● Multi-detector dependency
'Multi, store': ● 'PRE-STAGE': ● 'PRE-STAGE':
● Multi-detector dependency – ' --Pre-ALARM, fire' – 'Pre-ALARM'
● Only the local alarming is activated in – ' ------General autom. Fire – 'Autom. FIRE ALARM'
'MAIN STAGE' ALARM'
'Multi, 2 det. dependency': ● 'PRE-STAGE': ● 'PRE-STAGE':
ALARM'
201 | 406
12 'Zone'
'Multi, ALARM sub-system': ● 'PRE-STAGE': ● 'PRE-STAGE':

– ' ------General autom. Fire – 'ALARM sub-system'
ALARM'
'Multi, 2 det. dependency II' [AT]: ● 'PRE-STAGE': ● 'PRE-STAGE':
● Multi-detector dependency – ' ------Autom. First ALARM' – 'Autom. FIRST ALARM'
● Only the local alarming is activated in – ' ------General autom. Fire – 'Autom. FIRE ALARM'
'PRE-STAGE' ALARM'
'Multi, 2 det. dependency III' [CH]: ● 'PRE-STAGE': ● 'PRE-STAGE':
● Multi-detector dependency – ' ------Autom. First ALARM' – 'Autom. FIRST ALARM'
ALARM'
'Two-zone dependency' ● 'PRE-STAGE': ● 'PRE-STAGE':
● With 'Pre-ALARM' – ' ------Autom. First ALARM' – 'Autom. FIRST ALARM'
● Only the local alarming is activated in ● 'MAIN STAGE': ● 'MAIN STAGE':
'PRE-STAGE' – ' ------General autom. Fire – 'Autom. FIRE ALARM'
ALARM'
Table 4: Properties of the templates
1Text that is shown on the display of the Person Machine Interface when the event
occurs.
202 | 406
'Zone'
12
↑ Single-detector dependency and ↑ multi-detector dependency

The following table shows the required number of detectors with ↑ danger level
(GS) 2 or 3 in order to meet the criteria for 'PRE-STAGE'/'MAIN STAGE'' and to
trigger an alarm.
Template Required number of detectors with ↑ danger

level (GS)
'PRE-STAGE' 'MAIN STAGE'
GS 2 GS 3 GS 2 GS 3
'Single, standard' 1 0 0 1
'Single, no pre-alarm' 0 0 0 1
'Single, non-latching alarm' 0 0 0 1
'Single, ALARM sub-system' 1 0 0 1
'Single, Exting. discharged' 1 0 0 1
'Single, Exting. pre-alarm' 1 0 0 1
'Single, Gas alarm' 1 0 0 1
'Single, Gas warning' 1 0 0 1
'Single, door holders' 0 0 0 1
'Single, local ALARM' 1 0 0 1
'Multi, standard' 1 0 2 1
'Multi, garage' 0 0 0 2
'Multi, store' 1 0 2 1
'Multi, 2 det. dependency' 0 1 0 2
'Multi, ALARM sub-system' 0 1 0 2
'Multi, 2 det. dependency II' [AT] 0 1 0 2
'Multi, 2 det. dependency III' [CH] 0 1 0 2
'Two-zone dependency' 0 1 0 0
Table 5: Single-detector dependency and multi-detector dependency
203 | 406
12 'Zone'
12.4.2 'Manual zone'

'Manual call points' are evaluated in the 'Manual zone'. The 'Zone' can however
also be configured for inputs or collective detector lines. The danger signals are
evaluated with an OR link. Each manual call point in the 'Zone' can generate an
alarm, but not a ↑ pre-alarm.
various applications for the creation of a 'Manual zone'.
Typical application Typical event category Event text 1
'Standard': ' ----Manual Fire ALARM' 'Manual FIRE ALARM'

Evaluation of manual fire detectors
'ALARM sub-system': ' ----Manual Fire ALARM' 'ALARM sub-system'
Evaluation of a sub-system that is connected via an input
'Local ALARM': ' ----Manual Fire ALARM' 'Manual local ALARM'
Evaluation of manual fire detectors that generate only a
local alarm
'Redundancy ALARM': ' ----Manual Fire ALARM' 'Redundancy ALARM'
Evaluation of manual fire detectors that generate a
redundancy alarm
occurs.
204 | 406
'Zone'
12
12.4.3 'Technical zone'

In 'Technical zone', inputs for ↑ technical messages, e.g., fault or danger by
extraneous equipment, are evaluated.
various applications for the creation of a 'Technical zone'. The following table
shows the properties of the templates along with the event category and the event
text of the message that is generated with an event. The templates are all with
↑ single-detector dependency and without 'Pre-ALARM'.
'Standard (ack./latching)': ' --Other technical message' 'Technical message'

The event must be acknowledged with
latching
'Standard (ack./non-latching)': ' --Technical message: programmable' 'Technical message'
The event must be acknowledged without
latching
'Fault sub-system': ' --Other fault' 'Fault sub-system'
Evaluation of fault messages of a connected
sub-system
'Sub-system OFF': ' --Sub-system isolation' 'Sub-system OFF'
Evaluation of switched off messages of a
connected sub-system
'Fault extinguishing system': ' --Other fault' 'Fault extinguish.'
sub-system
'Gas ALARM': ' --Other technical message' 'Technic. Gas ALARM'
Evaluation of alarms of a connected gas
detector or a gas detector system
'Fault network device': ' --Other fault' 'Fault netw. device'
network device e.g. a switch or router
'Fault fiber network module': ' --Other fault' 'Technical message'
LWL network module
occurs.
See also
2 Monitoring Ethernet switch (MM) and safety module
(firewall) [➙ 378]
205 | 406
12 'Zone'
12.4.4 'Sub-system zone'

Signals from connected sub-systems are evaluated in the 'Sub-system zone', e.g.
from collective fire control panels, aspirating smoke detection systems and gas
detection systems.
various types of sub-systems for the creation of a 'Sub-system zone'.
category and the event text of the message that is generated with various events.
Typical application Event in the sub- Typical event category Event text 1
system
'Standard': 'Pre-ALARM' ' --Pre-ALARM, fire' 'PreALARM sub-syst.'
Evaluation of a fire detector 'ALARM' ' ------General autom. Fire ALARM' 'ALARM sub-system'
sub-system that is
connected via inputs and Isolation ' --Sub-system isolation' 'Sub-system OFF'
outputs
Fault ' --Other fault' 'Fault sub-system'
'ASD system': 'Pre-ALARM' ' --Pre-ALARM, fire' 'PreALARM sub-syst.'
Evaluation of a aspirating 'ALARM' ' ------General autom. Fire ALARM' 'ALARM sub-system'
smoke detection system
that is connected via inputs Isolation ' --Other information' 'Active information'
and outputs
Fault ' --Other fault' 'Fault sub-system'
'Gas system': 'Pre-ALARM' ' ----CO gas ALARM' 'Gas warning'
Evaluation of a gas 'ALARM' ' ----CO gas ALARM' 'Gas ALARM'
detection sub-system that
is connected via inputs and Isolation ' --Sub-system isolation' 'Sub-system OFF'
outputs Fault ' --Other fault' 'Fault sub-system'
occurs.
Each template has four inputs and four outputs. Depending on the sub-system, not
all inputs and outputs must be assigned. If, for example, a sub-system is unable to
generate any 'Pre-ALARM', then leave the 'Input 'Pre-alarm'' unassigned.
Inputs
● 'Input 'Pre-alarm''
● 'Input 'Alarm''
● 'Input 'Fault''
● 'Input 'Isolation''
Various events of the sub-system are evaluated with the inputs. If an input is
activated, the corresponding event test will be displayed. See table above.
206 | 406
'Zone'
12
Outputs
Events of the sub-system can be acknowledged and reset with the outputs.
● If you acknowledge an event, the output 'Output 'Acknowledge'' is activated for
3 s.
● If you reset an event, the output 'Output 'Reset'' will be activated. The duration
of the activation is dependent on the setting 'Reset time' in the 'Details' tab:
– 'Enabled' checkbox deactivated: The output is activated for 3 s.
– 'Enabled' checkbox activated: The duration of the activation can be set
between 1 s and 5 min. If the reset is carried out successfully prior to the
expiration of the set time, then the output will be deactivated again
immediately.
You will find more information on the properties of a 'Zone' in chapter 'Configuring
the 'Zone' [➙ 216]'.
12.4.5 'Flow switch zone'

In larger sprinkler systems, the piping system is distributed over several floors and
the supply network has an outlet on every floor. Flow rate indicators are built into
these outlets. These signal where the water runs to and generate an additional
report for reporting to the sprinkler station.
The flow rate indicator is evaluated with an OR link. Each flow rate indicator in the
'Zone' can generate an alarm.
category and the event text of the message that is generated with an event.
'Standard': ' ------Exting. discharged (Aut. Fire 'Flow swi. released'

● Evaluation of flow rate indicators AL.)'
● ↑ Single-detector dependency
occurs.
207 | 406
12 'Zone'
12.4.6 'Sprinkler zone'

F
H
Figure 72: General setup of the sprinkler system
F Flow rate indicator: special detector zone

S Sprinkler station with one or two contacts
H Hydrant network
A sprinkler system is a piping system that is terminated at several locations with

sprinkler heads. It is normally fed by the public network of hydrants. The sprinkler
station is installed directly after the house feed. It separates the sprinkler network
from the hydrant network due to overpressure in the sprinkler network. The
sprinkler station signals when the sprinkler network is opened somewhere and
water begins to flow. This condition is reported to the fire control panel via a
contact (optionally also two). This then triggers an alarm with immediate response
from the fire brigade.
In larger sprinkler systems, the piping system is distributed over several floors and
the supply network has an outlet in every floor. Flow rate indicators are built into
these outlets. These signal where exactly the water runs to and generate an
additional report for reporting to the sprinkler station.
Creating 'Sprinkler zone' element

Create the 'Sprinkler zone' element in the 'Detection' task card.
Creating 'Flow switch zone' element

Create the 'Flow switch zone' element in the 'Detection' task card.
208 | 406
'Zone'
12
Assigning 'Sprinkler zone' element

The 'Sprinkler zone' element has the 'Causes' channel for connecting the 'Input
'Sprinkler 1'' and 'Input 'Sprinkler 2'' contacts of the sprinkler station and the
'Referenced flow switch zones' channel, which is assigned to the flow rate indicator
zone.
To assign 'Input 'Sprinkler 1'', proceed as follows:
l Assign 'Causes' under 'Sprinkler zone' to an input. Link [➙ 85]
To assign 'Input 'Sprinkler 2'', proceed in the same way.

To assign 'Referenced flow switch zones', proceed as follows:
l Assign 'Referenced flow switch zones' under 'Sprinkler zone' to a 'Flow switch
zone'. Link [➙ 85]
209 | 406
12 'Zone'
12.4.7 'Gas zone'

Gas detectors are evaluated with the 'Gas zone'. You can select between a variety
of different templates that are pre-configured for various applications for the
creation of a 'Gas zone'.
'CO gas alarm': ' ----CO gas ALARM' 'CO gas ALARM'
● Evaluation of gas detectors
'CO gas warning': ' ----CO gas ALARM' 'CO gas warning'
● Evaluation of gas detectors
● 'Alarming type 'unmanned'': 'Local alarming
only'
'CO gas warning + alarm': ● 'PRE-STAGE': ● 'PRE-STAGE':
● Evaluation of gas detectors – ' ----CO gas ALARM' – 'CO gas warning'
● Single-detector dependency ● 'MAIN STAGE': ● 'MAIN STAGE':
● With 'Pre-ALARM' – ' ----CO gas ALARM' – 'CO gas ALARM'
● In 'PRE-STAGE', 'Alarming type 'unmanned'' is
set to 'Local alarming only'
occurs.
210 | 406
'Zone'
12
12.4.8 'XC10 zone'

Extinguishing systems are actuated and monitored by the autonomous
extinguishing control panel. The input/output module FDCIO222 is used as the
interface to the extinguishing control panel in the fire detection installation. Events
of the extinguishing control panel are forwarded to the fire control panel via the
interface and the commands from the fire control panel are transmitted to the
extinguishing control unit.
You will find more information about the XC10 extinguishing control panel and the
configuration examples in document A6V10257473. See chapter 'Applicable
documents'.
The 'XC10 zone' element has four inputs and three outputs. These must be
assigned to the inputs and outputs of the FDCIO222.
Figure 73: 'XC10 zone' element in the structure tree
Sub-element of 'XC10 Input or output on Function

zone' FDCIO222
Input 'Discharged' IN1 Activating or resetting the
extinguishing release
Input 'Fault' IN2 Fault message
Input 'Pre-alarm' IN3 Activating or resetting the
extinguishing pre-alarm
Input 'Blocked' IN4 Blocking or enabling the
Output 'Reset' OUT A Resetting the extinguishing
release
Output 'Block OUT B Blocking the automatic and
autom.+manual' manual extinguishing release
Output 'Block autom.' OUT C Blocking the automatic
'Input 'Discharged''
The extinguishing control panel detects the activation or resetting of the
extinguishing release by activating or deactivating 'Input 'Discharged''.
When 'Input 'Discharged'' is activated, the FC20 displays the message 'Exting.
discharged'. The activation of the extinguishing release is displayed as an alarm
and the ↑ AVC is started.
The message does not disappear automatically when 'Input 'Discharged'' is
deactivated, i.e. when a reset is made on the extinguishing control panel. The
message must be acknowledged and reset on the FC20.
211 | 406
12 'Zone'
'Input 'Fault''
The extinguishing control panel detects the occurrence or disappearance of a fault
by activating or deactivating 'Input 'Fault''. When 'Input 'Fault'' is activated, the
FC20 displays a fault message.
The message does not disappear automatically when 'Input 'Fault'' is deactivated,
i.e. when the fault indication disappears on the extinguishing control panel. The
message must be acknowledged on the FC20.
'Input 'Pre-alarm''
The extinguishing control panel detects the activation or resetting of the
extinguishing pre-alarm by activating or deactivating 'Input 'Pre-alarm''.
When 'Input 'Pre-alarm'' is activated, the FC20 displays the message 'Exting. pre-
alarm'. The activation of the extinguishing pre-alarm is displayed as an alarm and
the AVC is started.
The message does not disappear automatically when 'Input 'Pre-alarm'' is
deactivated, i.e. when a reset is made on the extinguishing control panel. The
message must be acknowledged and reset on the FC20.
'Input 'Blocked''
The extinguishing control panel detects the blocking or releasing of automatic and
manual extinguishing release by activating or deactivating 'Input 'Blocked''.
The blocking is indicated as isolation on the FC20 ↑ Person Machine Interface.
'Output 'Reset''
This output is used to reset the extinguishing release from a 'FS20' operating
terminal. The FC20 activates 'Output 'Reset'', when the 'Reset' command is
executed on the Person Machine Interface.
'Output 'Block autom.+manual''

This output is used to block the automatic and manual extinguishing release from a
FS20 operating terminal. The FC20 activates 'Output 'Block autom.+manual'', when
the 'Autom.+man. exting. OFF' command is executed on the Person Machine
Interface.
'Output 'Block autom.''

This output is used to block the automatic extinguishing release from a FS20
operating terminal. The FC20 activates 'Output 'Block autom.'', when the 'Autom.
exting. OFF' command is executed on the Person Machine Interface.
212 | 406
'Zone'
12
Assigning input or output
Figure 74: Assigning input or output

In order to assign the inputs and outputs of the 'XC10 zone' to the inputs and
outputs of the FDCIO222, proceed as follows:
2. Open ↑ 'Station' > 'Detection area' > ↑ 'Section' > 'XC10 zone' in the tree view.
3. Highlight an input or an output e.g. 'Input 'Discharged''.
4. In the menu bar, click on 'Assign'.
a The 'Assign dialog' window opens.
5. On the right in the window, select the corresponding input or output of the
FDCIO222.
a The input or output of the 'XC10 zone' is assigned to the input or output of the
FDCIO222.
Properties of the 'XC10 zone' element

In the detail editor of the 'XC10 zone' element, the following can be set on the
'Details' tab:
Figure 75: Properties in the detail editor of the 'XC10 zone'
213 | 406
12 'Zone'
'Autom. exting. release blockable from FS20'

This setting specifies whether the automatic extinguishing release can be blocked
from the FS20 operating terminal. If the checkbox is activated, the blocking
proceeds as follows:
1. On the ↑ Person Machine Interface of the FC20, the user selects an 'XC10
zone' and executes the 'Autom. exting. OFF' command.
2. This command activates 'Output 'Block autom.''.
3. The command must be confirmed by the extinguishing control panel within five
seconds. The extinguishing control panel confirms the command by an open
line on 'IN4'.
4. If the command is confirmed within five seconds, the FC20 displays the
message 'Aut. ext.OFF FC'. 'Output 'Block autom.'' remains active until the
block on the Person Machine Interface of the FC20 is released again.
5. If the command is not confirmed within five seconds, the 'Output 'Block autom.''
is deactivated and the FC20 displays the message 'XC10 not blockable'.
'Autom.+manual exting. release blockable from FS20'

This setting specifies whether the automatic and manual extinguishing release can
be blocked from the FS20 operating terminal. If the checkbox is activated, the
blocking proceeds as follows:
1. On the Person Machine Interface of the FC20, the user selects a 'XC10 zone'
and executes the 'Autom.+man. exting. OFF' command.
2. This command activates 'Output 'Block autom.+manual''.
3. The command must be confirmed by the extinguishing control panel within five
seconds. The extinguishing control panel confirms the command by a short-
circuit on 'IN4'.
4. If the command is confirmed within five seconds, the FC20 displays the
message 'Aut+man ext.OFF FC'. 'Output 'Block autom.+manual'' remains
active until the block on the Person Machine Interface of the FC20 is released
again.
5. If the command is not confirmed within five seconds, the 'Output 'Block
autom.+manual'' is deactivated and the FC20 displays the message 'XC10 not
blockable'.
'Show blocking of autom. exting. release on FS20 operating terminal'

This setting specifies whether blocking of the automatic extinguishing release from
the extinguishing control panel is displayed on the FS20 operating terminal. If the
checkbox is activated, the blocking proceeds as follows:
1. The automatic extinguishing release is blocked by the extinguishing control
panel.
2. 'Input 'Blocked'' is activated.
3. On the Person Machine Interface of the FC20, the message 'Aut. ext.OFF XC'
is displayed.
'Resettable from FS20'

This setting specifies whether the ↑ extinguishing control can be reset from the
FS20 operating terminal. If the checkbox is activated, the resetting proceeds as
follows:
1. On the Person Machine Interface of the FC20, the user executes the 'Reset'
command.
2. This command activates 'Output 'Reset'' for three seconds.
3. The extinguishing control panel reports the successful reset by deactivating
'Input 'Discharged'' and/or 'Input 'Pre-alarm''.
4. If these inputs are not deactivated within 10 seconds, FC20 displays the
message 'XC10 n. resettable' for 60 seconds.
214 | 406
'Zone'
12
'Reset time'
This setting specifies the period for which the system attempts to reset the
extinguishing control before the attempt is considered a failure. For a correct
function, ten seconds must be set.
The property 'Reset time' can be set only if the checkboxes 'Resettable from FS20'
and 'Enabled' are activated.
See also
12.4.9 'FSE zone' [DE]

A release element is assigned to the 'FSE zone'. With the release element, a fire
alarm is generated manually, which in turn unlocks the fire brigade key depot. To
operate the release element, a key is required which is exclusively in the
possession of the fire brigade.
The following table shows the properties of the template for the 'FSE zone' along
with the event category and the event text of the message that is generated with an
event.
'Standard': ' ----Manual Fire ALARM' 'Manual FIRE ALARM'

● Evaluation of release elements
occurs.
215 | 406
12 Configuring the 'Zone'
12.5 Configuring the 'Zone'

2. Highlight a 'Zone' in the tree view.
3. Select the 'Overview' or the 'Details' tab in the detail editor.
4. Set the desired properties. The settings are described in the following sections.
Depending on the 'Zone', not all settings are available.
Figure 76: Settings in the 'Overview' tab
Figure 77: Settings in the 'Details' tab
'Customer text'
The text in the 'Customer text' field is displayed on the ↑ Person Machine Interface
together with messages from the respective element. You will find more
information on customer text in chapter 'Customer text [➙ 124]'.
'Intervention text'
The text in the 'Intervention text' field is displayed on the ↑ Person Machine
Interface when there is an alarm in the corresponding 'Zone'. The text can contain
a maximum of four lines. To insert a line break, enter the following text:
$(BR)
'Channel activation'
This setting specifies the zone stage at which the logical channels generate an
activation message and activate their internal ↑ alarm indicators:
216 | 406
Configuring the 'Zone'
12
'External AI activation' and 'Base sounder activation'

These settings specify at which level the external alarm indicators or base
sounders are activated by the assigned devices:
These settings take effect only if a direct activation of the external alarm indicator
or of the base sounder is configured. You will find more information on direct
activation in chapter 'Detector parameter sets [➙ 155]'.
'OFF allowed'
Option Effect
Checkbox checked 'Zone' can be switched off using an operating
command.
Checkbox unchecked 'Zone' cannot be switched off using an operating
command.
'Timeout detector/walk test'

A time-out for the modes 'Detector test' or 'Walk test', respectively, can be specified
with the setting 'Timeout detector/walk test' .
Option Effect
'Enabled' checkbox The 'Detector test' and 'Walk test' modes are not
unchecked ended automatically.
1 h 00 min to 23 h 59 min After this time has elapsed, the mode 'Detector test'
or 'Walk test', respectively, is ended automatically.
'Criteria PRE-STAGE' and 'Criteria MAIN STAGE'

These settings indicate the necessary criteria for reaching 'PRE-STAGE' or 'MAIN
STAGE'. The criteria are fulfilled when the specified number of devices in the
'Zone' reach ↑ danger level 2 or 3. The top field shows the number of devices with
danger level 2 and the bottom field the number with danger level 3.
Example:
● The criteria for 'PRE-STAGE' are fulfilled when 1 device reaches ↑ danger
level 2.
● The criteria for 'MAIN STAGE' are fulfilled when 1 device reaches danger
level 3.
The criteria for 'MAIN STAGE' take priority over the criteria for 'PRE-STAGE'.
'Additional criteria for PRE-/MAIN STAGE'

This property specifies additional criteria for the settings 'Criteria PRE-STAGE' and
'Criteria MAIN STAGE'. It can thus be ensured that 'PRE-STAGE' or 'MAIN
STAGE' will be reached with ↑ multi-detector dependency or two-zone
dependency, even in unusual situations.
You will find more information on this in chapter 'Additional criteria for pre-stage
and main stage [➙ 222]'.
217 | 406
'Two-zone dependency'
This property specifies whether the 'Zone' can be used for two-zone dependency.
This property is activated, e.g. for 'Automatic zone', with the 'Two-zone
dependency' template.
You will find more information on two-zone dependency in chapter 'Two-zone
dependency [➙ 221]'.
'Multi detector dependency with latching'

This property specifies whether multi-detector dependency with latching is
activated. This property is activated, e.g. for 'Automatic zone', with the 'Two-zone
dependency' template.
You will find more information on this in chapter 'Multi-detector dependency with
latching [➙ 220]'.
'Reset time'
Option Effect
'Enabled' checkbox Reset time cannot be set. In this case, the suitable
unchecked reset time is set by the control panel.
'Enabled' checkbox The appropriate reset time can be set by the user,
activated e.g. when sub-systems are connected.
'Reset time': 1 s to 5 min The system attempts to reset the element within this
time before the attempt is considered a failure. If the
element can be reset prior to the expiration of the set
time, then it can be reset immediately.
'Always resettable'
This property is only available for the 'Manual zone'.
Option Effect
Checkbox checked 'Zone' can always be reset (message 'Glass broken'
from manual call points that are still active).
Checkbox unchecked 'Zone' can only be reset if all assigned manual call
points are in quiescent condition.
218 | 406
12
12.5.1 Multi-detector dependency
NOTICE
↑ Multi-detector dependency for collective detector lines
Application does not comply with standards.
● Multi-detector dependency may not be set up with collective detector lines.
You can choose between the following templates for 'Automatic zone' to configure
the ↑ multi-detector dependency:
● 'Multi, 2 det. dependency'
● 'Multi, 2 det. dependency II' [AT]
● 'Multi, 2 det. dependency III' [CH]
Depending on the selection, the following properties are set in the 'Details' tab of
the detail editor.
'Multi, 2 det. dependency' and 'Multi, 2 det. dependency III' [CH]:

The checkbox 'Multi detector dependency with latching' is deactivated. The
↑ danger level of the detectors is not stored. The ↑ multi-detector dependency is
used for a stationary fire.
'Multi, 2 det. dependency II' [AT]:

The checkbox 'Multi detector dependency with latching' is activated. The detectors
assigned to a 'Zone' are evaluated in a multi-detector dependency with the signal
being stored. If the 'Zone' reaches the pre-stage then the ↑ danger levels of the
detectors that have reached the criteria of the pre-stage are stored as a criterion
for the main stage. As soon as the required number of detectors have stored the
criteria for the main stage then the main stage is reached and signaled accordingly.
Example:
If a detector signals danger level 3, the 'Zone' reaches the pre-stage and a first
alarm is triggered. Danger level 3 of the detector is stored as the criterion for the
main stage. As soon as further detectors signal danger level 3, the zone 'Zone'
reaches the main stage and a second alarm is triggered.
Multi-detector dependency can be used for a moving fire, for example for detecting
a fire on a conveyor belt.
219 | 406
Standard settings
The table below shows the standard settings of the 'Automatic zone' in the 'Events'
tab of the detail editor.
Template Settings
'Multi, 2 det. dependency' Freely selectable
'Multi, 2 det. dependency II' [AT] 1 detector with ↑ danger level 3:
● Automatic first alarm
● ↑ Local alarming only (no delay times, internal sounder only)
2 detectors with danger level 3:
● Automatic fire alarm
● 'Manned operation': Delayed alarming
● 'Unmanned operation': ↑ Global alarming only
'Multi, 2 det. dependency III' [CH] 1 detector with danger level 3:
● Automatic first alarm
● 'Manned operation': Delayed alarming
● 'Unmanned operation': Global alarming only
2 detectors with danger level 3:
● Automatic fire alarm
● 'Manned operation' and 'Unmanned operation': Global alarming only
Table 12: Standard settings
12.5.2 Multi-detector dependency with latching

The property 'Multi detector dependency with latching' in the detail editor of a
'Automatic zone' specifies whether ↑ multi-detector dependency with latching is
activated. If the property is activated, then the detectors of the 'Zone' are evaluated
as follows:
As soon as the 'Zone' reaches 'PRE-STAGE', the ↑ danger levels of the detectors
which fulfilled the criteria for 'PRE-STAGE' are latched. When the criteria set for
'MAIN STAGE' are fulfilled, the 'Zone' reaches 'MAIN STAGE'. This can be
triggered by the following events:
● Detectors with latched danger levels report a higher danger level.
AND/OR
● Other detectors report additional danger levels.
Example
'Criteria PRE-STAGE': 1 detector with ↑ danger level 3
'Criteria MAIN STAGE': 2 detectors with danger level 3
1. One detector reports danger level 3.
2. The 'Zone' reaches 'PRE-STAGE'.
3. Danger level 3 of the detector is latched as the criterion for 'MAIN STAGE'.
4. One other detector reports danger level 3.
5. The 'Zone' reaches 'MAIN STAGE', independent of whether the first detector
still reports danger level 3 or not.
220 | 406
12
↑ Danger levels
If a detector with latched danger level reaches a higher danger level, then the
higher danger level will be latched. Example:
1. Danger level 2 is latched.
2. The detector reports danger level 3.
3. Danger level 3 is latched.
Resetting an alarm
Whether or not a ↑ pre-alarm or alarm can be reset does not depend on the
latched ↑ danger levels of the detectors but rather on the current danger levels.
The latching is used only as a criterion for reaching the 'MAIN STAGE'. A pre-alarm
or alarm in 'PRE-STAGE' can thus be reset before the 'MAIN STAGE' is reached,
insofar as the current danger levels of the detectors have returned to 0.
12.5.3 Two-zone dependency

If the ↑ multi-detector dependency extends over two 'Zones', they can be assigned
to each other. If one of the two 'Zones'' reaches 'PRE-STAGE', it will send a
message. If the second 'Zone' also reaches 'PRE-STAGE', then both 'Zones'
change to the main stage and send a corresponding message. One 'Zone' cannot
reach the main stage alone.
Configuring two-zone dependency
Figure 78: Configuring two-zone dependency
w Two elements 'Detection' are present with the 'Two-zone dependency' template
in the 'Automatic zone' task card.
1. In the tree view, highlight the first 'Zone' for the two-zone dependency.
3. Select 'Two-zone dependency' at the left in the window.
a The ↑ 'Detection tree' is depicted at the right of the window. The elements
4. Select the second 'Zone' for the two-zone dependency.
a The two 'Zones' are assigned to each other.
See also
221 | 406
12.5.4 Additional criteria for pre-stage and main stage
Figure 79: Additional criteria for reaching the pre-stage or the main stage, respectively
In the detail editor of the 'Zone', you can define additional criteria for the settings
'Additional criteria for PRE-/MAIN STAGE' and 'Criteria PRE-STAGE' with the
property 'Criteria MAIN STAGE'. It can thus be ensured that 'PRE-STAGE' or
'MAIN STAGE' will be reached with ↑ multi-detector dependency or two-zone
dependency, even in certain situations. The situations and settings are described
in the following sections.
↑ Multi-detector dependency
● 'Fallback to single detector/zone dependency':
If the number of detectors is no longer sufficient in ↑ normal operation, a switch
is made to ↑ single-detector dependency in order to fulfill the multi-detector
dependency that has been set, e.g., in the event of a fault or when a detector
has been isolated. If this is the case, then 1 detector with ↑ danger level 2 or 3
is sufficient to trigger 'PRE-STAGE' or 'MAIN STAGE'.
The chronological order of the events is not relevant, i.e., a switch is made to
single-detector dependency with both of the following variants:
– First, danger level 2 or 3 is reached. Afterwards, the number of detectors
becomes less than required.
– First the number of detectors becomes less than required. Afterwards
danger level 2 or 3 is reached.
● 'TRVB S123: Danger level(s) + fault(s) and/or isolation(s)':
Faults and isolations of the detectors are evaluated in addition to the danger
levels as criteria for reaching 'PRE-STAGE' or 'MAIN STAGE', respectively.
When a danger level is reached and a fault and/or an isolation is reported in
addition, then 'PRE-STAGE' or 'MAIN STAGE', respectively, is reached.
The chronological order of the events is not relevant, i.e., 'PRE-STAGE' or
'MAIN STAGE' is reached with both of the following variants:
– First, a danger level is reached. Afterwards a fault and/or an isolation is
reported.
– First, a fault and/or an isolation is reported. Afterwards, a ↑ danger level is
reached.
● 'VDE0833: Danger level(s) first + new fault(s)':
Faults of the detectors are evaluated in addition to the ↑ danger levels as
criteria for reaching 'PRE-STAGE' or 'MAIN STAGE'. When a danger level is
reached and an additional danger level and/or a fault is reported, then 'PRE-
STAGE' or 'MAIN STAGE', respectively, is reached.
The chronological order of the events is relevant, i.e., the criteria for 'PRE-
STAGE' or 'MAIN STAGE' are only fulfilled if the first the danger level is
reached and then a fault is reported afterwards. Faults that were already
previously reported are not taken into account.
● ' - (none)':
No additional criteria are evaluated for reaching 'PRE-STAGE' or 'MAIN
STAGE', respectively. 'PRE-STAGE' or 'MAIN STAGE' are only reached if the
detectors report the number of danger levels that is set for the properties
'Criteria PRE-STAGE' and 'Criteria MAIN STAGE'.
222 | 406
12
Example of use
Figure 80: Application example for additional criteria

'Criteria MAIN STAGE': Two detectors must report ↑ danger level 3 in order for
'MAIN STAGE' to be reached.
Additional criterion: 'VDE0833: Danger level(s) first + new fault(s)'
1. One detector reports danger level 3.
2. One detector of the same 'Zone' reports a fault.
3. The 'Zone' reaches 'MAIN STAGE'.
Two-zone dependency
Behavior with two-zone dependency is similar to that with ↑ multi-detector
dependency.
WARNING
Differing settings in the assigned 'Zones'
Unforeseen behavior in the event of fire
● With two-zone dependency in both assigned 'Zones', select the same setting
for the property 'Additional criteria for PRE-/MAIN STAGE'.
● 'VDE0833: Danger level(s) first + new fault(s)':

'MAIN STAGE' is reached when one of the two assigned 'Zones' is in 'PRE-
STAGE' and a fault is reported in the second 'Zone'.
● 'TRVB S123: Danger level(s) + fault(s) and/or isolation(s)' and 'Fallback to
single detector/zone dependency':
'MAIN STAGE' is reached in the following cases:
– One of the assigned 'Zones' is in 'PRE-STAGE'. A fault and/or isolation is
reported in the second 'Zone'.
– A fault and/or isolation is reported in one of the assigned 'Zones'. The
second 'Zone' reaches 'PRE-STAGE'.
● ' - (none)':
No additional criteria are evaluated for reaching 'PRE-STAGE' or 'MAIN
STAGE', respectively.
223 | 406
12 Assign hardware tree to the detection tree
12.6 Assign hardware tree to the detection tree
WARNING
Incorrect sensor link for the FDA221 and FDA241
If the FDA221 or FDA241 sensors are assigned to different 'Zones', the detection
behavior corresponding to the ↑ parameter set is not guaranteed.
● Assign both FDA221 or FDA241 sensors to the same 'Zone' in the 'Detection
tree'.
To assign the 'Hardware tree' to the ↑ 'Detection tree', proceed as follows:

2. Open 'Detection area' > ↑ 'Section' in the tree view.
3. Highlight 'Zone' or 'Physical channel', if pre-configuration has been carried out
up to this level.
a The 'Hardware tree' is displayed in the 'Assign dialog' window. The
elements that can be assigned are highlighted.
5. Mark the corresponding sensor.

a 'Zone' is assigned to the sensor.
You can use a reading device for Data Matrix code to assign devices using a
layout plan with 'Zones'. You will find more information on this in chapter
'Assigning with the help of Data Matrix code [➙ 88]'.
See also
2 Assignment with Data Matrix code [➙ 88]
224 | 406
Collective detector line via input/output module FDCIO223 or zone module
12
12.7 Collective detector line via input/output module

FDCIO223 or zone module
You can use the following elements to connect ↑ collective detector lines:
● Inputs/outputs of input/output module FDCIO223
● Input of the zone module FDCI223
To do this, you must assign the physical channel of the FDCIO223 or the FDCI223
to a 'Zone'.
Assigning a ↑ collective detector line

2. Open ↑ 'Station' > 'Area' > ↑ 'Section' in the tree view.
3. Highlight a 'Zone'.
5. Select 'Collective' at the left in the window.
6. Open the FDCIO223 input/output module and select
'Collective/input/sounder/output'.
– or
7. Open the zone module FDCI223 and select 'Collective'.
a 'Collective/input/sounder/output' or 'Collective' is assigned to the 'Zone'.
225 | 406
12 Neural fire detector FDOOTC241
Setting the properties of the ↑ collective detector line

1. Highlight the assigned collective detector line in the tree view.
You will find a description of the properties in the 'Hardware' tab in the following
chapters: 'Input/output module FDCIO223 [➙ 163]' and 'Zone module FDCI223'.
You can also set the properties in the 'Hardware' task card.
'Reset time'
The 'Reset time' setting in the detail editor of the 'Zone' has no influence on a
↑ collective detector line.
See also
2 Input/output module FDCIO223 [➙ 163]
12.8 Neural fire detector FDOOTC241

The ↑ parameter sets influence the detection behavior of the detectors. This
enables the detection behavior to be adapted to the fire phenomena and
environmental influences at the place of installation.
Regardless of the fire detection parameter sets, the CO detection behavior can be
influenced by separate parameter sets and set specifically to the environmental
influences.
You will find detailed information about the FDOOTC241 neural fire detector in
document A6V10209291. See chapter 'Applicable documents'.
See also
12.8.1 Configuring fire detection

The 'Sensor' element can be assigned to a 'Automatic zone'. To determine the
↑ danger level, the progression of the following factors is evaluated:
● Smoke density
● Temperature
● CO content, depending on the set fire parameter set
Assigning 'Sensor' to 'Automatic zone'

l Assign the 'Automatic zone' to a 'Sensor' element of a neural fire detector /
event category 'Automatic'. Link [➙ 85]
Setting ↑ parameter sets

You will find additional information in the chapters 'Detector parameter sets
[➙ 155]' and 'Sensor mode with multi-sensor fire detectors [➙ 156]'.
226 | 406
Neural fire detector FDOOTC241
12
12.8.2 Configuring gas detection

You can assign the 'Gas sensor' element to a 'Technical zone' or 'Gas zone'.
According to EN 54, it is not permitted to assign the gas sensor to a 'Automatic
zone' and therefore generate a fire alarm. The CO concentration progression is
used to evaluate the ↑ danger level.
Assigning 'Gas sensor' to 'Zone'

1. Create a 'Gas zone' or 'Technical zone' using the 'Gas ALARM' template.
2. Assign the 'Zone' to a 'Gas sensor' element of a neural fire detector.
Link [➙ 85]
Setting a↑ parameter set

1. Highlight 'FDOOTC241/Gas sensor' in the tree view.
2. Select the 'Hardware' tab in the detail editor.
3. Set the desired parameter sets.
See also
12.8.3 Configuring environment monitoring

The 'Ambient supervision' channel is assigned to a 'Technical zone'. The channel is
used to monitor the temperature or CO concentration in the environment. If the set
threshold is undershot or exceeded, the channel becomes active and can therefore
trigger a message or control.
Assigning 'Ambient supervision' to 'Technical zone'

2. Assign the 'Technical zone' to the 'Ambient supervision' element of a neural fire
detector / event category 'Input'. Link [➙ 85]
Setting properties
Figure 81: Detail editor with settings for environment monitoring
1. Highlight 'FDOOTC241/Ambient supervision' in the tree view.

227 | 406
12 Neural fire detector FDOOTC241
The following can be set in the 'Hardware' tab:

● 'Usage'
The type of environment monitoring can be set here:
– 'Temperature higher than threshold (Celsius)'
– 'Temperature lower than threshold (Celsius)'
– 'CO concentration higher than threshold (ppm)'
● 'Hysteresis'
If the temperature or CO concentration deviates from the threshold value, the
input can switch between active and inactive. To prevent this, a hysteresis can
be defined. As soon as the threshold value is reached and the input is
activated, it is not deactivated again until the temperature or the CO
concentration at least drops below the threshold value or rises above it by the
defined hysteresis value.
Hysteresis values:
– 'Normal'
– 'Large/slow'
● 'Threshold temperature (Celsius)'
The temperature threshold values can be set here. If this threshold value is
undershot or exceeded (depending on 'Usage'), the channel becomes active.
The threshold value must be between -20 °C and +50 °C.
This field can only be edited if the 'Temperature higher than threshold (Celsius)'
or 'Temperature lower than threshold (Celsius)' setting was selected for
'Usage'.
● 'Threshold CO concentration (ppm)'
The CO concentration threshold values can be set here. If this threshold value
is exceeded, the channel becomes active. The threshold value must be
between 20 and 600 ppm.
This field can only be edited if the 'CO concentration higher than threshold
(ppm)' setting was selected for 'Usage'.
The following can be set in the 'Overview' tab:
Figure 82: Detail editor with settings for environment monitoring

● 'Evaluation filter time'
Here, the time during which a signal must be present such that the input is
evaluated as active can be set for the input. A time of between one second and
five minutes can be set. Do not use this setting together with 'Hysteresis'.
228 | 406
Redux module [DE]
12
12.9 Redux module [DE]

The Redux module serves for data transmission and power supply redundancy of a
fire brigade indication panel (FAT).
The data cable is connected to the control panel's RS485 interface.
If one of the connection lines to the FAT fails due to a short-circuit or open line,
complete functionality is ensured. The line fault is signaled by the fault relay of the
Redux module which drops in case of a fault.
The fault output of the Redux module is wired to an input of the periphery board
and assigned to a 'Technical zone' of type 'Fault sub-system'.
Assigning 'Technical zone' to 'Onboard I/Os'

1. Create a 'Technical zone' using the 'Fault sub-system' template.
2. Assign the 'Technical zone' to an 'I/O' element / event category 'Input' in the
'Hardware tree'. Link [➙ 85]
229 | 406
12 Key safe adapter [DE]: Configuring the technical zone
12.10 Key safe adapter [DE]: Configuring the technical

zone
The 'LED 'Key depot unlocked'' must be configured in order to operate a key safe
adapter [DE]. To this end, a 'Technical zone' must be created and assigned. Then
the LEDs on the corresponding Person Machine Interfaces are assigned to the
'Technical zone'. See the chapter 'Assigning LEDs [➙ 357]'.
Prerequisite
● The key safe adapter has been created and assigned. See the chapter 'Key
safe adapter [DE] [➙ 355]'.
● The controls for the key safe adapter have been created and assigned. See the
chapter 'Key safe adapter [DE]: Configuring controls [➙ 285]'.
Configuring 'Technical zone'

1. Select the 'Detection' task card and create a new 'Technical zone' with the
template ' Acknowledgeable/non-latching' for the station with the key safe
adapter, e.g., using the context menu.
2. Edit the customer text for the 'Technical zone', e.g., 'Key depot unlocked'.
3. Assign the 'Technical zone' as follows:
– Select the 'Input' element in 'Manual type selection' on the left-hand side of
the 'Assign dialog'.
– When activating the 'Key safe adapter' via FCI2008: Select the output I/O 5
under FCI2008 in the hardware tree on the right-hand side of the 'Assign
dialog'.
– Or
– When activating the 'Key safe adapter' via FDCIO222/224: Select I/O 4
under FCI2007 in the hardware tree on the right-hand side of the 'Assign
dialog'.
230 | 406
Key safe adapter [DE]: Configuring the technical zone
12
4. Then assign the LEDs on the corresponding Person Machine Interfaces to the
'Technical zone'. See the chapter 'Assigning LEDs [➙ 357]'.
231 | 406
'Control' task card
13 Dual CPU – switchover and degraded mode
13 'Control' task card

Controls are configured in the 'Control' task card. The controls are combined into
the following ↑ control groups:
● 'Alarming control group': Controls for internal and external sounders and
remote transmission outputs for Fire and Fault.
● ↑ 'Fire control group': Controls for building equipment.
● 'Evac control group': Controls for ↑ alarm and announcement devices.
● 'Counter control group': Registration of fire alarms and test activities.
Each control group has one or more control elements including one or more inputs
(Causes) and one or more outputs (Effects).
You will find more information on control groups in the following chapters.
13.1 Dual CPU – switchover and degraded mode

The following information helps you in deciding which measures you need to
configure if the main CPU fails, in the case of a ↑ 'Station' with a dual CPU.
If, in the case of a 'Station' with a dual CPU, the main CPU fails, the second ↑ CPU
is switched over to. From the time of the failure and during the period of the
switchover, further modules can detect a communication fault to the main CPU and
can switch to ↑ degraded mode, with the corresponding configuration.
As an example, the active outputs on the I/O card (RT) or the I/O card
(horn/monitored) are deactivated after 30 s. After the switchover to the second
CPU and completed communication between the other modules and the second
CPU, the outputs are activated again.
13.2 Creating control tree

1. Select 'Control' > 'Station' in the task card.
2. Create a 'Station' element for the 'Control group'.
4. Create a control element for the 'Control group'.
Several elements are already created for 'Stations' with the template 'Alarming
pre-configured', e.g. 'Alarming control group' with pre-configured 'RT controls'.
See also
2 Create element [➙ 77]
232 | 406
'Control' task card
Alarming control group
13
13.3 Alarming control group

The alarming control group includes the following control elements:
● 'Internal sounder control'
● 'External sounder control'
● 'RT fire control'
● 'RT fault control'
● 'RT 1 control' to 'RT 8 control'
● 'RT device control'
Figure 83: Alarming control group

● The causes of the elements are assigned to the event verification of the
↑ station.
● The ↑ effects of the different 'RT' elements are assigned to the corresponding
on-board I/Os, the fire brigade periphery module or the I/O card
(programmable). A confirmation input can be assigned to the effects.
● The effects of the 'Sounder' elements can be assigned to the base sounder or
↑ loop sounder on the FDnet detector line or to the corresponding on-board
I/Os, the fire brigade periphery module, or the I/O card (programmable).
● A fault input and a confirmation input can be assigned to the 'RT device
control'.
233 | 406
'Control' task card
13 Alarming control group
Assigning cause
NOTICE
Incorrect cause link for 'Activation timeout 'manned'' / 'Activation timeout
'unmanned''
The 'Activation timeout 'manned'' / 'Activation timeout 'unmanned'' sounder
property is only evaluated for one 'Area' or for elements from one 'Area'.
w One or more sounders are assigned as 'Control' ↑ effects.
w The 'Activation timeout 'manned'' property and / or 'Activation timeout
'unmanned'' is active.
● Only assign one 'Area' or elements from one 'Area' as the cause of the
'Control'.

3. Highlight 'Alarming control group' in a control element of the 'Causes'.
5. In the window click an event category and select the cause from the list.
a The appropriate tree is shown in the right side of the window. The elements
6. Select the appropriate ID No. or open the tree and select the corresponding
element.
a 'Causes' is assigned to the element.
234 | 406
'Control' task card
13
Assigning an ↑ effect
3. Highlight the 'Alarming control group' element in a control element of the
'Effects'.
5. Click an output with or without confirmation on the left in the window.

a The hardware tree is depicted on the right in the window. The elements that
can be assigned are highlighted.
a In the case of an output with confirmation, a second 'Hardware tree' opens
for assigning the confirmation input.
6. Select the appropriate ID No. (outputs only) or open the tree and select the
corresponding element.
a 'Effects' is assigned to the element.
235 | 406
'Control' task card
13.3.1 Automatically isolating remote transmission

If remote transmission is active, under certain circumstances this can be isolated
automatically.
There are two ways of doing this:
● ' --Access level <> default level': Remote transmission is automatically
deactivated when the current access level of an assigned ↑ Person Machine
Interface (PMI) corresponds to at least the configured level.
● 'All activations': The activated remote transmission is automatically deactivated
when an input in any control, e.g. a door contact, changes status.
' --Access level <> default level'

To assign a ↑ Person Machine Interface (PMI) to the cause, proceed as follows:
1. Select 'Control' > ↑ 'Station' > 'Alarming control group' > 'RT' element in the
task card.
2. Assign 'Causes' to a PMI in the 'Operation tree' / event category 'Cause 'RT
isolation'' > ' --Access level <> default level'. Link [➙ 85]
3. Highlight the assigned PMI element in the tree view.

4. In the 'Required access level' field of the detail editor, determine the minimum
access level that must be reached for remote transmission to be deactivated.
236 | 406
'Control' task card
13
'All activations'
To attain automatic isolation by any control, proceed as follows:
1. Select 'Control' > ↑ 'Station' > 'Alarming control group' > 'RT' element in the
task card.
2. Assign 'Causes' to a 'Fire control' element in the 'Control tree' / event
category'Cause 'RT isolation'' > 'All activations'. Link [➙ 85]
3. In the tree view, highlight the 'Fire control' link and use the hyperlink in the
detail editor to navigate to the original 'Fire control' element.
4. Assign its cause to the corresponding input.
13.3.2 Properties of the assigned effect elements

You can set additional properties in the assigned effect elements of an ↑ alarming
control. The settings are described in the following sections.
If the ↑ effect is assigned to an RT channel, you can set the following:
Figure 84: Settings in the detail editor of an assigned RT channel
'OFF allowed while AVC active (t1/t2)'

This setting specifies whether the ↑ RT channel may be switched off while the
↑ AVC is active i.e., while the times t1 and t2 are running.
Independent of this setting, the 'ÜE ab' command is always executed by a fire
brigade operating panel (FDOP).
237 | 406
'Control' task card
'Minimal duration of activation'

This setting specifies the minimum period during which the ↑ RT channel remains
active even if the cause for triggering is no longer available.
If the ↑ effect is assigned to a sounder line, you can set the following:
Figure 85: Settings in the detail editor of an assigned sounder line
'Enabled':
The two settings 'Enabled' specify whether a time-out is used for the activation of
the control. The time-out can be set separately for 'Manned operation' and
'Unmanned operation'.
NOTICE
'unmanned''
'Control'.
'Activation timeout 'manned'':

This setting specifies the duration of the time-out in 'Manned operation'. The time-
out is started when the control is activated. After the expiration of the set time, the
sounder is deactivated automatically.
'Activation timeout 'unmanned'':

This setting specifies the duration of the time-out in 'Unmanned operation'. The
time-out is started when the control is activated. After the expiration of the set time,
the sounder is deactivated automatically.
238 | 406
'Control' task card
Universal control group
13
13.4 Universal control group

The ↑ 'Fire control group' combines several 'Fire controls'. In the 'Fire control', one
or more 'Input' elements are created in the cause. An event can be assigned to
this. The executing element will be assigned to the ↑ effect of the 'Fire control'
element.
13.4.1 Fire control
Figure 86: 'Fire control' element in the tree view

The element 'Fire control' is used in order to control facilities when a particular
event occurs e.g., to close fire doors or to switch off 'Zones'. Events within the
↑ 'Site' and inputs can be assigned as causes for the control. Commands and
outputs can be assigned as ↑ effects of the control.
Causes Control ↑ Effects

Event ➨ 'Fire control' ➨ Command
Input Output with or without
confirmation
Table 13: Causes and effects of the control
The assigned inputs and outputs must be in the same 'Station' as the control.
Logically combining causes

In the 'Formula' field of the control, configure the combination type for the causes
with '*' (AND), '+' (OR), '-' (NOT).
Templates for 'Fire control'

● 'Standard Fire control'
● 'Door holders'
In the case of the 'Door holders' template, the checkbox 'Controls a 'door holders'
application' is activated in the default settings for the detail editor.
See also
2 Fire control properties [➙ 242]
239 | 406
'Control' task card
13 Universal control group
13.4.1.1 Assigning fire control

Assigning causes
2. Open 'Station' > ↑ 'Fire control group' > 'Fire control' in the tree view.
3. Highlight the element 'Causes'.
a The 'New cause dialog, Assign dialog' window opens.
5. Select an event category or an input at the left in the window.
6. Select the element you want.
a The element is assigned with 'Causes'.
240 | 406
'Control' task card
13
Assigning ↑ effects
Two trees, one above the other, are visible in the figure below. The lower tree
appears only when a confirmation input can be assigned.
To assign an effect, proceed as follows:
2. Open 'Station' > 'Fire control group' > 'Fire control' in the tree view.
3. Highlight the element 'Effects'.
5. Select an output or command on the left in the window.
a The element is assigned with 'Effects'.
241 | 406
'Control' task card
13.4.1.2 Fire control properties
Figure 87: Properties in the detail editor of the element 'Fire control'
'START mode'
This setting defines the conditions for the activation of the control. The following
conditions are possible:
● 'Undefined (no autom. activation)': The control can only be activated manually
with a command.
● 'Formula true': The control is activated when the Boolean expression in the field
'Formula' is true.
● 'Value rising and >= threshold (all causes OR-combined)': The control is
activated as soon as a particular number of events of the respective event
category has occurred. This value is in the detail editor of the cause element, in
the field 'Threshold'.
'STOP mode'
This setting defines the conditions for the deactivation of the control. The following
● 'Undefined (no autom. deactivation)': The control can only be deactivated
manually with a command.
● 'Formula false': The control is deactivated when the Boolean expression in the
field 'Formula' is false again.
● 'All causes inactive': The control is deactivated when all assigned causes are
inactive again.
'Formula'
Several causes can be assigned with a formula. The following operators are
possible:
● OR = '+'
● AND = '*'
● NOT = '–'
When brackets are used, a mixture of operators can also be used.
Example: '1 * (2 + 3)' means '1 AND (2 OR 3)'.
If no formula has been defined, all causes are linked with the OR function.
242 | 406
'Control' task card
13
Delay times and time-out

● 'Activation delay': The activation of the control is delayed by the set time after
the activation condition is met.
● 'Deactivation delay': The deactivation of the control is delayed by the set time
after the deactivation condition is met.
● 'Activation timeout': The time-out is started when the control is activated. After
the expiration of the set time, the control is deactivated again automatically,
even if the conditions for activating the control are still fulfilled.
The property 'Activation timeout' can be set only if the checkbox 'Enabled' is
activated.
● 'Deactivation timeout': The time-out is started when the control is deactivated.

After the expiration of the set time, the control is activated again automatically,
even if the conditions for deactivating the control are still fulfilled.
The property 'Deactivation timeout' can be set only if the checkbox 'Enabled' is
activated.
The following properties can be set in the 'Details' tab:
Figure 88: Properties in the detail editor of the element 'Fire control'
'Accept commands 'Fire controls ON/OFF' from FBF'

This setting indicates whether the control can be switched off or on, respectively,
by a command on the fire brigade Person Machine Interface (PMI). If the checkbox
is checked, then all ↑ effects of the control will be switched off or on by the FBF
command for the corresponding 'Area'.
This setting is relevant only for controls in accordance with the ↑ VdS definition.
'Controls a 'door holders' application'

This property indicates whether the control is used for a fire door. If the checkbox is
activated, then fire doors will be shut automatically when the control is switched off.
This prevents fire doors from remaining open in the event of an alarm if the control
has been switched off.
If the control was created with the template 'Door holders', then the checkbox
'Controls a 'door holders' application' is activated in the default settings.
'OFF allowed'
This setting indicates whether or not and under which circumstances the element
can be switched off:
● 'Always': 'The element can always be switched off.
● 'Never': The element can never be switched off.
● 'NOT if activated automatically by causes': The element cannot be switched off
if it was activated automatically by its causes. The element can only be
switched off if it is in quiescent condition or if it was activated by a manual
command at the ↑ Person Machine Interface or by a 'Fire control'.
243 | 406
'Control' task card
'DEACTIVATION allowed'
can be deactivated:
● 'Always': The element can always be deactivated.
● 'NOT if activated automatically by causes': The element cannot be deactivated
deactivated if it was activated by a manual command on the ↑ Person Machine
Interface or by a 'Fire control'.
'Reactivation upon unsuccessful reset'

This setting indicates whether an already deactivated control is to be reactivated
once again if the event that triggered the control was not able to be reset.
● Checkbox activated: The control is reactivated. The event is treated as a new
event.
● Checkbox deactivated: The control is not reactivated. The event is not treated
as a new event.
'Control test allowed'

This setting indicates whether the control can be switched to the 'Control test
mode' by a command on the ↑ Person Machine Interface.
13.4.1.3 Properties of the assigned cause elements

You can set additional properties in the assigned cause elements of the 'Fire
control'. The settings are described in the following sections.
↑ Assigning to an event
If the cause of the control is an event, you can set the following properties in the
assigned cause element:
Figure 89: Properties in the detail editor of a cause element when assigning to an event
'Event category':
Event category that is assigned to the control as the cause.
'Threshold':
The value in this field specifies how many events of the corresponding event
category are required in the element or the subtree, to activate the control. If the
control is deactivated again, it is re-activated by a new event of the given event
category.
This setting only comes into effect if the control's detail editor, in the 'START mode'
field, the 'Value rising and >= threshold (all causes OR-combined)' setting is
selected.
'Include sub-tree':
This setting specifies whether only events in the assigned element are considered
or in the subtree, too.
244 | 406
'Control' task card
13
'Deactivate cause when event is ACKNOWLEDGED':

This setting specifies when the cause is deactivated:
● Checkbox activated: The cause is deactivated as soon as the assigned event is
acknowledged.
● Checkbox deactivated: The cause is deactivated as soon as the assigned
event disappears.
If the assigned event cannot be acknowledged, this setting has no effect. The
cause is always deactivated as soon as the event disappears.
'ACTIVE if no communication to source':

This setting specifies the condition of the cause, if no connection to 'Station' exists
that contains the assigned element. The condition can be ACTIVE or INACTIVE.
↑ Assigning to an ↑ 'AVC' / 'IC' event

If the cause of the control is a 'AVC' or a 'IC' event, you can specify an additional
criterion for the activation of the cause in the assigned cause element.
Figure 90: Properties in the detail editor of the cause element when assigning to an 'AVC'/'IC' event
The 'AVC/IC state' setting specifies, which condition the 'AVC' or 'IC' must be in, so
that the cause becomes active. The following settings are possible:
● 'AVC/IC: Local alarming': The 'AVC' / 'IC' is the 'local alarming' condition. There
is no delay time.
● 'AVC/IC: Global alarming': The 'AVC' / 'IC' is the 'global alarming' condition.
● 'AVC/IC: Alarming delayed (t1/t2/ts)': The delay time t1 or t2 of the 'AVC' or t1
or ts of the 'IC' is running.
● 'AVC/IC: Alarming delayed, t1 running': The delay time t1 of the 'AVC' or 'IC' is
running.
● 'AVC: Alarming delayed, t2 running': The delay time t2 of the 'AVC' is running.
● 'IC: Intervention stopped (t1 acknowledged)': The delay time t1 of the 'IC' has
been ended with 'Acknowledge'.
For the 'AVC/IC state' property, a maximum of one checkbox may be active.
Otherwise an error is displayed in the cause element.
Example:
The cause is assigned to the ' --AVC, Fire ALARM' event category and the
'Detection area' element. In the detail editor of the 'Detection area' element, the
'AVC/IC: Global alarming' checkbox is activated.
The cause is only active when a 'Fire ALARM' triggers the 'AVC' and the 'AVC' is in
the 'global alarming' condition.
245 | 406
'Control' task card
↑ Assigning to an input
If the cause is an input, you can set the following properties in the assigned cause
element of the control:
Figure 91: Properties in the detail editor of the cause element when assigning to an input
'Evaluation filter time': This setting specifies how long the signal of the assigned
input must be active for the cause to be evaluated as active.
13.4.2 Time control
● Controlling the time for activating and deactivating assigned effects

● 'Time control cause' cause element: Configuring the data and time for
activating and deactivating assigned effects
● Assigned effects: Commands and outputs
WARNING
Activation or deactivation operations performed incorrectly in the event of a time
switchover.
If the time is put forward by one hour, activation or deactivation operations
scheduled to take place within this switchover period, e.g., between 02:00 a.m.
and 03:00 a.m., will not be performed. If the time is put back by one hour,
activation or deactivation operations scheduled to take place within this
switchover period, e.g., between 02:00 a.m. and 03:00 a.m., will be performed
twice.
● If you have configured time switchover for the site, do not configure any
activation or deactivation operations to take place during the switchover
period, e.g., between 02:00 a.m. and 03:00 a.m.
NOTICE
Configuring several causes
Only one cause element may be active within a 'Time control' at any one time.
The times for activating and deactivating causes must not overlap if several
causes are configured for one 'Time control'.
● If a 'Time control' has several cause elements, do not configure activation and
deactivation times that overlap.
Causes Control Effects

'Time control cause': Activation and ➨ 'Time control' ➨ Command
deactivation date and time Output
246 | 406
'Control' task card
13
13.4.2.1 Time control properties

In the detail editor of the 'Time control' element, the following properties can be set:
'Overview' tab
● Customer text
'Details' tab
'Activation' events hidden'

● When the checkbox is checked, activated events of the control are not
displayed on any operating unit, are not saved in the Event memory, and are
not printed out.
'OFF allowed'

247 | 406
'Control' task card
13.4.2.2 Creating and configuring a time control cause

Creating 'Time control cause'

2. Open the 'New element' window.
3. Select 'Add'.
a The 'Time control cause' cause element is created.
Configuring 'Time control cause'
WARNING
Activation or deactivation operations performed incorrectly in the event of a time
switchover.
If the time is put forward by one hour, activation or deactivation operations
scheduled to take place within this switchover period, e.g., between 02:00 a.m.
and 03:00 a.m., will not be performed. If the time is put back by one hour,
activation or deactivation operations scheduled to take place within this
switchover period, e.g., between 02:00 a.m. and 03:00 a.m., will be performed
twice.
● If you have configured time switchover for the site, do not configure any
activation or deactivation operations to take place during the switchover
period, e.g., between 02:00 a.m. and 03:00 a.m.
NOTICE
Configuring several causes
Only one cause element may be active within a 'Time control' at any one time.
The times for activating and deactivating causes must not overlap if several
causes are configured for one 'Time control'.
● If a 'Time control' has several cause elements, do not configure activation and
deactivation times that overlap.
248 | 406
'Control' task card
13
'Overview' tab
● Customer text
● Activation - Time: Defines the time at which the 'Time control cause' element
will be activated on the specified day
● Activation - Days of the week: Defines the day/s on which the activation will
take place at the specified time
● Deactivation - Time: Defines the time at which the 'Time control cause' element
will be deactivated on the specified day
● Deactivation - Days of the week: Defines the day/s on which the deactivation
will take place at the specified time
249 | 406
'Control' task card
13.4.2.3 Assigning time control effects
l Use the 'Assign' function to assign commands and outputs as effects.

Link [➙ 90]
250 | 406
'Control' task card
Evac control group
13
13.5 Evac control group

The evacuation control group makes it possible to configure a complete evacuation
function for each alarm device group, e.g., on one floor. Two function blocks are
available for each control:
● Alert
The assigning of all conditions, so that the corresponding ↑ alarm devices
transmit a warning signal.
● Evac
The assigning of all conditions, so that the corresponding alarm devices
transmit an evacuation signal.
Events in the ↑ 'Station', the 'Detector lines', the ↑ 'Section', or the 'Zone' (cause)
initiate evacuation control.
The evacuation control group unites the following evacuation control elements:
● 'Universal evac control'
● 'Phased evac control'
13.5.1 Assigning universal evac control

Assigning cause
NOTICE
'unmanned''
'Control'.

2. Open ↑ 'Station' > 'Evac control group' > 'Universal evac control' in the tree
view.
251 | 406
'Control' task card
13 Evac control group

5. Select an event category or an input at the left in the window.
a The element is assigned with 'Causes'.
Assigning an ↑ effect

2. Open ↑ 'Station' > 'Evac control group' > 'Universal evac control' in the tree
view.
a The element is assigned with 'Effects'.
In order to navigate quickly to a particular device in the window 'New effect

dialog', you can activated the checkbox 'Use serial no. ("ID-Nr."):' and select the
serial number of the desired device from the drop-down list.
252 | 406
'Control' task card
Evac control group
13
13.5.2 Universal evac control properties
Figure 92: Properties in the detail editor of the 'Universal evac control' element
'START mode'
This setting defines the conditions for the activation of the control. The following
● 'Undefined (no autom. activation)': The control can only be activated manually
with a command.
● 'Formula true': The control is activated when the Boolean expression in the field
'Formula' is true.
● 'Value rising and >= threshold (all causes OR-combined)': The control is
activated as soon as a particular number of events of the respective event
category has occurred. This value is in the detail editor of the cause element, in
the field 'Threshold'.
'STOP mode'
This setting defines the conditions for the deactivation of the control. The following
● 'Undefined (no autom. deactivation)': The control can only be deactivated
manually with a command.
● 'Formula false': The control is deactivated when the Boolean expression in the
field 'Formula' is false again.
● 'All causes inactive': The control is deactivated when all assigned causes are
inactive again.
'Formula'
Several causes can be assigned with a formula. The following operators are
possible:
● OR = '+'
● AND = '*'
● NOT = '–'
When brackets are used, a mixture of operators can also be used.
Example: '1 * (2 + 3)' means '1 AND (2 OR 3)'.
If no formula has been defined, all causes are linked with the OR function.
253 | 406
'Control' task card
Delay times and time-out

● 'Activation delay': The activation of the control is delayed by the set time after
the activation condition is met.
● 'Deactivation delay': The deactivation of the control is delayed by the set time
after the deactivation condition is met.
● 'Activation timeout': The time-out is started when the control is activated. After
the expiration of the set time, the control is deactivated again automatically,
even if the conditions for activating the control are still fulfilled.
The property 'Activation timeout' can be set only if the checkbox 'Enabled' is
activated.
● 'Deactivation timeout': The time-out is started when the control is deactivated.

After the expiration of the set time, the control is activated again automatically,
even if the conditions for deactivating the control are still fulfilled.
The property 'Deactivation timeout' can be set only if the checkbox 'Enabled' is
activated.
Figure 93: Properties in the detail editor of the 'Universal evac control' element

'OFF allowed'
can be deactivated:
254 | 406
'Control' task card
Evac control group
13
'Reactivation upon unsuccessful reset'

This setting indicates whether an already deactivated control is to be reactivated
once again if the event that triggered the control was not able to be reset.
● Checkbox activated: The control is reactivated. The event is treated as a new
event.
● Checkbox deactivated: The control is not reactivated. The event is not treated
as a new event.

13.5.3 Cause of the phased evac control

The 2-stage evacuation has separate causes for ALERT and EVAC. The graphic
below shows the event categories that can be assigned to an element of the
hardware tree, detection tree, or control tree.
Figure 94: 'New cause dialog, Assign dialog' window with the ' ----All autom. Fire ALARMS' event
category
NOTICE
'unmanned''
'Control'.
To assign 'Causes ALERT' or 'Causes EVAC', proceed as follows:

2. Open ↑ 'Station' > 'Evac control group' in the tree view.
3. In 'Phased evac control', highlight the 'Causes ALERT' or 'Causes EVAC'
element.
4. Select 'Assign'.
5. Click on an event category in the left of the window and select an event from
the list.
255 | 406
'Control' task card
6. In the right of the window, select the tree and mark the corresponding
highlighted element in it.
a 'Causes' is assigned to the element.
13.5.4 Effect of the phased evac control

The ↑ effect is assigned to the corresponding hardware (sounders). Different
tonalities can be selected for the warning (ALERT) and evacuation (EVAC) for the
sounder.
Figure 95: Window 'Assign dialog' for assigning a sounder

To assign the ↑ effect, proceed as follows:
2. Open 'Station' > 'Evac control group' in the tree view.
3. In 'Phased evac control', highlight the 'Effects' element.
a The 'EVAC sounder' command is highlighted, and the ↑ hardware tree is
displayed at the right of the window.
5. Mark the corresponding highlighted element in the tree.
a 'Effects' is assigned to the element.
256 | 406
'Control' task card
Evac control group
13
13.5.5 Properties of the phased evac control
Figure 96: 'Details' tab for the 'Phased evac control' element

'OFF allowed'
can be deactivated:

257 | 406
'Control' task card
13.5.6 2-stage evacuation, special case [GB]

Evacuation is undertaken in two stages. First, all floors are warned (ALERT). After
that, the evacuation (EVAC) of individual floors is performed at particular intervals
(phases), starting with the floor on which the seat of fire is located, in order to
prevent a blocking of the escape routes.
● In the first phase the floor on which the fire is located as well as the one above
and the two top floors, all basement floors and possibly the ground floor are
evacuated.
● In additional phases, one upper and one lower floor are also evacuated at
predefined intervals. If need be, additional floors can be evacuated during the
same phase.
Floor Evacuation phases

UG EG Floor Floor Floor Floor Floor Floor Floor Floor Floor Floor
2 3 4 5 6 7 8 9 10 11
UG 1 1 2 2 3 3 4 4 5 5 1 1
EG 1 1 1 2 2 3 3 4 4 5 1 1
Floor 2 1 2 1 1 2 3 3 4 4 5 1 1
Floor 3 1 3 2 1 1 2 3 4 4 5 1 1
Floor 4 1 4 3 2 1 1 2 3 4 5 1 1
Floor 5 1 5 4 3 2 1 1 2 3 4 1 1
Floor 6 1 5 4 4 3 2 1 1 2 3 1 1
Floor 7 1 5 4 4 3 3 2 1 1 2 1 1
Floor 8 1 5 4 4 3 3 2 2 1 1 1 1
Floor 9 1 5 5 4 4 3 3 2 2 1 1 1
Floor 10 1 5 5 5 4 4 3 3 2 2 1 1
Floor 11 1 5 5 5 4 4 3 3 2 2 1 1
Table 15: Example of evacuation process in the event of a fire on the fifth floor
UG Basement
EG Ground floor
Floor Floor
1-5 Evacuation phases
Evacuation if fire breaks out on the fifth floor:

● Phase 1: Floor 5, floor 6, floor 10, floor 11, and basement
● Phase 2: Floor 4, floor 7
● Phase 5: EG
258 | 406
'Control' task card
Evac control group
13
Configuration example for the 2-phase evacuation control element

w Each floor is represented by one ↑ section.
w Each floor is equipped with a combined 'ALERT sounder'/'EVAC sounder'.
1. Create the 'Phased evac control' element for each floor.
2. In the first 'Phased evac control', highlight the 'Causes ALERT' element.
3. Assign 'Causes ALERT' with all sections. Leave the delay times of the sections
at '00:00:00' as immediate warning is required on each floor.
4. Use multiselection to select all sections and use the 'Copy' function to copy
them.
5. Highlight 'Causes EVAC'' and insert the sections using the 'Paste' function.
6. Repeat the 'Paste' function for each 'Causes ALERT' and 'Causes EVAC'
element in each 'Phased evac control' element.
7. Configure the delay times for evacuation. Use the column for floor 5 in the
above table to do this.
– Open 'Phased evac control / 4th floor' > 'Causes EVAC'.
– Evacuation phase 1: Highlight 'Section / 3rd floor' and 'Section / 4th floor' in
turn and set each to 5 minutes in the 'Delay' detail editor.
– Evacuation phase 2: Highlight 'Section / 2nd floor' and 'Section / 5th floor' in
turn and set each to 10 minutes in the 'Delay' detail editor.
– Continue up to evacuation phase 4.
8. Using this method and referring to the table above, configure the delay times
for evacuation for each 'Phased evac control' element.
Figure 97: 2-stage evacuation
259 | 406
'Control' task card
13 Counter control group and alarm counter control
13.6 Counter control group and alarm counter control

The 'Counter control group' groups the control elements 'Alarm counter control'.
With the 'Alarm counter control', the following events of the ↑ 'Stations' can be
registered:
● ' --All Fire ALARMS'
● 'All test activations'
The 'Counter control group' and 'Alarm counter control' elements are not available
in the 'Control tree' as standard. They must be created, if required. Information on
the creation of 'Control tree' can be found in chapter 'Creating control tree
[➙ 232]'.
Assigning 'Alarm counter control'

The 'Alarm counter control' element can be assigned to one or more ↑ 'Stations'.
While doing this, one or both event categories of a 'Station' can be assigned.
Figure 98: Assigning alarm counter control

2. Open 'Station' > 'Counter control group' in the tree view.
3. Highlight the element 'Alarm counter control'.
a The 'New cause dialog' window opens.
a The 'Detection tree' is depicted at the right of the window. The elements
5. Select the event category on the left in the window.
6. On the right in the window, select the desired 'Station'.
a The 'Station' is assigned to 'Alarm counter control'.
Switching the ↑ alarm counter off and on

You can configure a standard button or a favorite such that you can switch the
alarm counter off and at the touch of a button. To do that, assign the standard
button or the favorite to the 'OFF' or 'ON' commands and to 'Counter control group'
or 'Alarm counter control'.
260 | 406
'Control' task card
Damper control group
13
13.7 Damper control group

● Contains the 'Fire damper control' and 'Smoke extraction control' elements
● Control of fire and smoke dampers that are connected to the FS20 via inputs
and outputs, e.g., via an input/output module on the detector line
● Causes which can be assigned: Events associated with the 'Site' and inputs
● Assigned effects: Outputs and other controls
– The damper actuator is controlled via outputs
– The output / damper state is monitored via inputs
Causes Control ↑ Effects

Event, input ➨ 'Fire damper control' ➨ Inputs and outputs that are
'Smoke extraction control' connected to the dampers
Example of fire damper control

A fire damper control corresponds to the ventilation zone.
Fire damper control could be activated by a fire alarm, for example. In the event of
a fire alarm, the open fire dampers are closed.
Example of smoke damper control

Smoke damper control could be activated by an input, for example. If the input is
activated by the fire brigade, the smoke dampers are opened.
13.7.1 Creating and configuring a damper control

1. Create a 'Damper control group' in the control tree and underneath this a 'Fire
damper control' or a 'Smoke extraction control'.
2. Assign the cause element to an event or to an input and make the settings for
the cause element properties.
3. Assign the pre-configured effect elements to an FDCIO222/4 input/output
module in accordance with the wiring. Link [➙ 263]
– An output with monitoring must be configured for each damper.
– For 'Fire damper control': The output without monitoring is optional and is
only required if you want to connect the damper actuator to the
FDCIO222/4 using both poles.
4. Optional: Create additional channels under the 'Fire damper control' or 'Smoke
extraction control' and assign them to a FDCIO222/4.
– An output with monitoring must be configured for each damper.
– For 'Fire damper control': The output without monitoring is optional and is
only required if you want to connect the damper actuator to the
FDCIO222/4 using both poles.
261 | 406
'Control' task card
13 Damper control group
5. In the hardware tree for the assigned FDCIO222/4 outputs, set the following
'Output mode': 'Inactive: On / active: Off'
6. For 'Fire damper control': Set the properties of the control. Link [➙ 268]
7. Set the properties of the assigned effects. Link [➙ 269]
8. In the 'Global behaviour' element, configure the properties for the BACnet
notifications and the BACnet priorities for the damper controls. Link [➙ 290]
– If necessary, activate the 'BACnet alarm notification in section enabled'
property to send a 'Section summary' to sub-systems over BACnet.
a The damper control has been configured.
9. Optional: Export the BACnet parameters as an EDE file to enable subsequent
configuration of the Desigo PX controller. Link [➙ 270]
13.7.2 Damper control states
The damper control state and the display of this state on the PMI are dependent
on the limit value for open or closed dampers OR on the state of the 'Main
damper'.
Fire damper control

Fixed state: It is not possible to change the assignment between the state of the
control and the state of the fire damper.
Control state Fire damper state

Inactive Open
Active Closed
Smoke damper control:

Changeable state: The assignment between the state of the control and the state
of the smoke damper can be inverted if wired accordingly. The table below shows
the default state that applies in each case:
Control state Smoke damper state

Inactive Closed
Active Open
You will find more information on the message texts that are displayed on the PMI
when a damper control is activated, deactivated, or malfunctions in document
008838.
262 | 406
'Control' task card
13
13.7.3 Assignment of effects dependent on wiring

The assignment of effects is dependent on how the FDCIO222/4 is wired to the
contacts of the fire/smoke damper actuator.
An output with monitoring must be configured for each damper. The output
without monitoring is optional and is only required if you want to connect the
damper actuator to the FDCIO222/4 using both poles.
Monitoring the control with the inputs of the FDCIO222/4

With the FDCIO222/4, it is possible to monitor whether control of the damper
actuator (e.g., 'Close damper') has been performed correctly (e.g., 'Damper
closed'). Motor 'M' of the damper actuator is controlled via one output (fire damper)
or via two outputs (smoke damper) on the FDCIO222/4. The damper state is
monitored via two inputs on the FDCIO222/4. You will find more information in
Description of the effect elements

The following effects are pre-configured:
● 'Fire damper control'
– 'Fire damper output/supervised': Control of the damper actuator motor for
opening or closing the damper. The inputs for monitoring the damper state
are located under this output.
– 'Damper output/NOT supervised': The wiring for the energy supply can be
routed via this output.
● 'Smoke extraction control'
– 'Smoke extraction damper output/supervised': Counterclockwise control of
the damper actuator motor for opening the damper. The inputs for
monitoring the damper state are located under this output.
– 'Damper output/NOT supervised': Clockwise control of the damper actuator
motor for closing the damper. This output is inverted by default because the
normal condition of the damper is 'closed', i.e., when the control is in the
inactive state, the output contact is closed/active.
263 | 406
'Control' task card
13.7.3.1 Fire dampers: Wiring and assignment

This chapter describes the wiring and assignment aspects based on the default
states of the damper controls [➙ 262].
Effects which can be Input/Output of the FDCIO222/4 Contact on the Wired to contact/s...on the
assigned in Engineering Tool FDCIO222/4 damper actuator
Fire damper 21:Output OUT A M1
output/supervised
Damper output/NOT 22:Output OUT B M2
supervised
Input 'Damper inactive' 11:Input IN 1 S4 and S6
Input 'Damper active' 12:Input IN 2 S1 and S2
Contact position with 'Input 'Damper inactive'', fire damper open

AC IN AC IN
DC IN - DC IN + 1
24 23 22 21
OUT B
OUT A
M
FDCIO222/4 1 2 S1 S2 S3 S4 S5 S6
IN1 IN2 IN3 IN4

11 12 13 14
1 Contacts S4 and S6 closed: Damper state 'Open'
264 | 406
'Control' task card
13
Contact position with 'Input 'Damper active'', fire damper closed

AC IN AC IN
DC IN - DC IN +
1
24 23 22 21
OUT B
OUT A
M
FDCIO222/4 1 2 S1 S2 S3 S4 S5 S6
IN1 IN2 IN3 IN4

11 12 13 14
1 Contacts S1 and S2 closed: Damper state 'Closed'
265 | 406
'Control' task card
13.7.3.2 Smoke dampers: Wiring and assignment

This chapter describes the wiring and assignment aspects based on the default
states of the damper controls [➙ 262].
Effects which can be Input/Output of the FDCIO222/4 Input on the Wired to contact/s...on the
assigned in Engineering Tool FDCIO222/4 damper actuator
Smoke extraction damper 21:Output OUT A M2
output/supervised
Damper output/NOT 22:Output OUT B M3
supervised
Input 'Damper inactive' 11:Input IN 1 S1, S2
Input 'Damper active' 12:Input IN 2 S4, S6
Contact position with 'Input 'Damper inactive'', smoke damper closed

AC IN AC IN
DC IN + DC IN - 1
24 23 22 21
OUT B
OUT A
OUT D OUT C
FDCIO222/4 M
1 2 3 S1 S2 S3 S4 S5 S6
LINE +
LINE +
LINE -
LINE -
IN1 IN2 IN3 IN4

11 12 13 14
1 Contacts S4 and S6 closed: Damper state 'Closed'
266 | 406
'Control' task card
13
Contact position with 'Input 'Input 'Damper active'', smoke damper

open
AC IN AC IN
DC IN + DC IN - 1
24 23 22 21
OUT B
OUT A
OUT D OUT C
FDCIO222/4 M
1 2 3 S1 S2 S3 S4 S5 S6
LINE +
LINE +
LINE -
LINE -
IN1 IN2 IN3 IN4
11 12 13 14
1 Contacts S1 and S2 closed: Damper state 'Open'
267 | 406
'Control' task card
13.7.4 Fire damper control properties

'Overview' tab
Specific properties for 'Fire damper control':
'Threshold 'closed'' (priority 1)

A 'Fire damper control' corresponds to the ventilation zone. The limit value
corresponds to a subset of fire dampers within the ventilation zone. As soon as the
limit value is reached, i.e., the fire dampers constituting the subset are closed, the
control becomes active and the state of the 'Fire damper control' / ventilation zone
is displayed on the PMI. The control is also active if the 'Main damper' is closed.
The control state and the display of this state on the PMI are dependent on the limit
value OR on the state of the 'Main damper'.
'Threshold 'open'' (priority 2)

A 'Fire damper control' corresponds to the ventilation zone. The limit value
corresponds to a subset of fire dampers within the ventilation zone. As soon as the
limit value is reached, i.e., the fire dampers constituting the subset are open, the
control becomes inactive. The control is also inactive if the 'Main damper' is open.
While the 'Main damper' is closed, the control is unable to switch to the
'Inactive/Open' state.
The control state and the display of this state on the PMI are dependent on the limit
value OR on the state of the 'Main damper'.
Recommendation for the 'Threshold 'closed'' and 'Threshold 'open''

parameter values
w You have no specific requirements for the parameter values.
l Enter a value for each of 'Threshold 'closed'' and 'Threshold 'open''
corresponding to the number of dampers in this 'Fire damper control'.
The effect of entering the number of dampers in the 'Fire damper control' as a
parameter value is that all dampers must be open or closed in order for the state of
the 'Fire damper control' to be 'open' or 'closed'.
If, contrary to the above recommendation, the sum of the parameter values of
'Threshold 'closed'' and 'Threshold 'open'' corresponds to the number of dampers
in this 'Fire damper control', both conditions ('closed' and 'open') can be met at the
same time. In this case the control state is 'closed'.
Example of use
● The 'open' state of the 'Fire damper control' can be assigned as a cause for an
additional control in order to switch on a fan.
– NOTICE! Check that activating fans will not damage any of the dampers.
● The 'closed' state of the 'Fire damper control' can be used to check and ensure
that all fire dampers are closed in the event of fire.
268 | 406
'Control' task card
13
You will find more information on the message texts that are displayed on the PMI
when a damper control is activated, deactivated, or malfunctions in document
008838.
'BACnet object name'

Customer-specific object name for the BACnet object. The 'BACnet object name'
can be selected in accordance with the project-specific naming system for the
relevant BACnet project.
13.7.5 Properties of the assigned effects

'Overview' tab
'Main damper' ('Fire damper control' only)

If the checkbox is checked, the damper is the main damper. The state of the
control/ventilation zone is set to 'closed' if the main damper is 'closed'.
'Timeout 'close''
Defines the time within which the 'closed' state must be confirmed once the control
has activated the output.
'Timeout 'open''
Defines the time within which the 'open' state must be confirmed once the control
has activated the output.
Cascading of damper controls

You can assign the 'Effects' element to another damper control. Effect elements
with a reference to another damper control can also be defined as the 'Main
damper'.
'BACnet object name'

Customer-specific object name for the BACnet object. The 'BACnet object name'
can be selected in accordance with the project-specific naming system for the
relevant BACnet project.
269 | 406
'Control' task card
13.7.6 EDE export

● Contains the BACnet parameters for the damper controls
● Can be used for the configuration of Desigo PX controllers
● Software required: XSLT processor for converting the SiB-X export on the
basis of an XSLT style sheet
– Example: Command Line Transformation Utility (msxsl.exe)
● Provided by FS20: XSLT style sheet
Generating an EDE export

w You have an XSLT processor or equivalent software with this functionality, e.g.,
msxsl.exe.
w You have created and configured the damper controls. Link [➙ 261]
1. Perform the SiB-X export for the site in SintesoWorks. Link [➙ 96]
2. In SintesoWorks, select 'Help' menu > 'View additional documents' >
'EDE_export'.
– The XSLT style sheet can be found inside the 'EDE_export' folder in XSL
format.
3. Use the SiB-X export as an input document and the XSL file as a style sheet
for generating the EDE export in your XSLT processor.
The EDE export only contains the BACnet parameters for the damper controls. It
does not contain BACnet parameters for any other site elements.
13.7.7 Configuring LEDs for damper control

The state of the fire and/or smoke dampers can be displayed on an LED indicator
FTO200x.
Example: State of a fire damper displayed by means of two LEDs on LED indicator
FTO2008
● Open: LED 1 lights up green
● Closed: LED 1 lights up red
● Damper moving, i.e., is in the process of closing or opening: LED 1 and 2 OFF
● Timeout occurred while opening or closing the damper or a fault is pending:
LED 1 OFF, LED 2 lights up yellow
Configuring an LED indicator

1. Select the 'Hardware' task card and create an LED indicator FTO2008 for the
relevant station.
2. Go to the 'Overview' tab and set the address of the LED indicator to a value of
between 20 and 35 in accordance with the DIP switch setting on the LED
indicator.
3. Select the 'Operation' task card and create the 'LED ind./mimic 48 LEDs'
element for the relevant station.
4. Assign the 'LED ind./mimic 48 LEDs' element to the LEDs of the FTO2008 in
the hardware tree.
270 | 406
'Control' task card
13
Configuring LED 1 for the 'Open' (green) and 'Damper moving' (OFF)
damper states
1. Select 'LED/output | 1' and assign the LED as follows:
– Go to the left of the 'New cause dialog' and select the 'Damper changing
position' event under 'Events 'Information''.
– On the right-hand side, select the required 'Fire damper output/supervised'
from the control tree: 'Control tree' > 'Station' > 'Damper control group' >
'Fire damper control' > 'Effects' > 'Fire damper output/supervised'.
– Click on 'Assign'.
2. Select the cause element that has been created under 'LED/output | 1' and set
the following properties on the 'Overview' tab:
– Colour: 'Green'
– Priority: '01 (highest)'
– LED mode: 'Inactive: On / active: Off'
Configuring LED 1 for the 'Closed' damper state

1. Assign 'LED/output | 1' to another cause as follows:
– Go to the left of the 'New cause dialog' and select the ' ----Technical
message: Damper/confirmed' event under 'Events 'Technical message''.
– On the right-hand side, select the same 'Fire damper output/supervised' as
for the first assignment from the control tree: 'Control tree' > 'Station' >
'Damper control group' > 'Fire damper control' > 'Effects' > 'Fire damper
output/supervised'.
– Colour: 'Red'
– Priority: '02'
– LED mode: 'Inactive: Off / active: On'
Configuring LED 1 for the 'Timeout/Fault' (OFF) damper state

1. Assign 'LED/output | 1' to another cause as follows:
– Go to the left of the 'New cause dialog' and select the 'All faults' event
under 'Events 'Fault''.
output/supervised'.
– Colour: 'Green'
– Priority: '03'
271 | 406
'Control' task card
3. Assign the same 'LED/output | 1' element to another cause as follows:

– Go to the left of the 'New cause dialog' and select the ' ----Technical
message: Damper/unexpected' event under 'Events 'Technical message''.
output/supervised'.
– Colour: 'Green'
– Priority: '04'
Configuring LED 2 for the 'Timeout/Fault' damper state

l Select 'LED/output | 2' and assign the LED as follows:
– Go to the left of the 'New cause dialog' and select the 'All faults' event
under 'Events 'Fault''.
output/supervised'.
272 | 406
'Control' task card
Extinguishing standard interface SST [DE]
13
13.8 Extinguishing standard interface SST [DE]

The extinguishing standard interface SST is used for the control and indication of
the extinguishing activation of a third party extinguishing control installation. The
input/output module FDCIO224, which is integrated in the fire control panel, is used
as an interface between the fire control panel and the extinguishing control
installation. The inputs of the fire control panel for the extinguishing control
equipment are monitored for short-circuit and open line.
The following events are evaluated by the extinguishing control system via the
inputs of the input/output module:
● 'Input 'Discharged''
● 'Fault extinguish.'
Extinguishing is activated via an output of the input/output module.
Creating an output for extinguishing actuation

An output of the input/output module is used to actuate the extinguishing process
via the extinguishing control system. The command for the extinguishing actuation
is give by detector zone(s) of the fire control panel.
Figure 99: 'New cause dialog, Assign dialog' window for assigning the cause for the extinguishing
actuation
Figure 100: 'New cause dialog, Assign dialog' window for assigning the ↑ effect for the extinguishing
actuation
To assign the cause and ↑ effect of the extinguishing actuation, proceed as
follows:
2. Highlight the ↑ 'Station' in the tree view and create a ↑ 'Fire control group'
element and a 'Fire control' element below this.
3. Select 'Assign'.
4. Highlight 'Causes' and, in the 'New cause dialog' window, highlight 'Event' in
the ' ----All autom. Fire ALARMS' list.
5. Select the relevant automatic ↑ zone(s) and click on 'Assign'.
a 'Causes' is assigned to the zone(s).
273 | 406
'Control' task card
13 Extinguishing standard interface SST [DE]
6. Highlight 'Fire control' and set the conditions for extinguishing activation in the
detail editor, 'Overview' button.
7. Highlight 'Effects' and, in the 'New effect dialog' window, highlight 'Output/NO
confirmation'.
8. Select the relevant 'Output' of input/output module FDCIO224 and click on
'Assign'.
a 'Effects' is assigned to the 'Output'.
Assigning 'Input 'Discharged''

An input of the input/output module serves is used to confirm extinguishing
activated.
Figure 101: 'Assign dialog' window for assigning the 'Input 'Discharged'' element
To assign 'Input 'Discharged'', proceed as follows:
2. Open the ↑ 'Station' in the tree view.
3. Highlight a ↑ 'Section' and create an 'XC10 zone' element.
4. Open 'XC10 zone' and highlight 'Input 'Discharged''.
a 'Input 'Discharged'' is highlighted and the 'Hardware tree' appears. The
elements that can be assigned are highlighted.
6. In the 'Assign dialog' window, select the relevant 'Input' of input/output module
FDCIO224 and click on 'Assign'.
a 'Input 'Discharged'' is assigned to the 'Input'.
274 | 406
'Control' task card
Extinguishing standard interface SST [DE]
13
Creating a 'Fault extinguish.' input
Figure 102: 'New element' window for creating the technical ↑ zone for 'Fault extinguish.'
Figure 103: 'Assign dialog' window for assigning the 'Fault extinguish.' input
To create and assign the 'Fault extinguish.' input, proceed as follows:
1. Highlight 'Section'.
2. In the 'New element' window, select the ↑ zone 'Type:' in the 'Technical zone'
and 'Fault extinguishing system' in the 'Template:' field, and click on 'Add'.
3. Highlight the 'Technical zone' zone.
4. Open the 'Assign dialog' window and highlight 'Input'.
a The 'Hardware tree' is shown. The elements that can be assigned are
highlighted.
5. Select the relevant 'Input' of input/output module FDCIO224 and click on
'Assign'.
a 'Technical zone' is assigned to the 'Input'.
Creating fire brigade operating panel (FBF)

You will find more information in chapter 'Fire brigade periphery [DE] [➙ 338]'.
275 | 406
'Control' task card
13 Extinguishing standard interface SST [DE]
Configuring the ↑ visibility on the fire brigade operating panel (FBF)

To ensure that the extinguishing system activation is correctly signaled by the LED
on the fire brigade operating panel, the 'XC10 zone' element must be assigned to
the fire brigade operating panel.
Figure 104: 'Assign dialog' window for assigning the visibility on the fire brigade operating panel (FBF)
To assign the visibility on the fire brigade operating panel (FBF), proceed as
follows:
1. Select the 'Operation' task card.
2. Open 'FBF' in the tree view.
3. Highlight 'Visible Extinguishing zones'.
a 'Visible Extinguishing zones' is highlighted and the ↑ 'Detection tree'is
shown. The 'XC10 zone' element that can be assigned is highlighted.
5. Select 'XC10 zone' and click on 'Assign'.
a 'Visible Extinguishing zones' is assigned to 'XC10 zone'.
276 | 406
'Control' task card
External alarm indicator
13
13.9 External alarm indicator

The ↑ external alarm indicator output of a FDnet device can be used for any
evacuation control or ↑ fire control.
Assigning external alarm indicator output
Figure 105: 'New cause dialog, Assign dialog' window with 'Output/NO confirmation'
w The output for the ↑ external alarm indicator is not used for direct activation.
The option 'Direct activation of external AI' is set in the detail editor of the
detector for the setting 'No direct activation'.
2. In the tree view, open
↑ 'Fire control group' > 'Fire control'
- OR -
'Evac control group' > 'Universal evac control' or 'Phased evac control'.
3. Highlight 'Effects'.
4. Select 'Assign'.
5. Highlight 'Output/NO confirmation' at the left of the window.
6. Open the corresponding FDnet device in the ↑ hardware tree.
7. Highlight 'Ext. AI' and click on 'Assign'.
a The ↑ effect of the control is assigned to the ↑ external alarm indicator output.
See also
2 Automatic fire detectors [➙ 153]
277 | 406
'Control' task card
13 Loop sounder, loop sounder/beacon, and base sounder
13.10 Loop sounder, loop sounder/beacon, and base

sounder
'Sounder', 'Sounder beacon', and 'Base sounder' can be assigned to the following
controls:
● In the alarming control group as:
– Internal 'Sounder'
– External 'Sounder'
● In the evac control group for:
– Universal evacuation
– 2-stage evacuation
Assigning 'Sounder'
Figure 106: 'Control' task card, alarming and evac control groups, with 'New effect dialog' window for
assigning a sounder

2. Depending on the application in question, open the following in the tree view:
'Alarming control group' > 'Internal sounder control' or 'External sounder control'
- OR -
'Evac control group' > 'Universal evac control' or 'Phased evac control'
4. Select 'Assign'.
a 'Assign dialog' is highlighted at the left of the 'Sounder' window.
5. In 'Hardware tree', select the 'Sounder' channel.
a 'Effects' is assigned to 'Sounder'.
278 | 406
'Control' task card
Sounder line via input/output module FDCIO223
13
Configuring 'Sounder'
Figure 107: 'Control' task card with 'Hardware' detail editor

The 'Sounder' configuration is displayed in the detail editor of the 'Control' task
card, provided that the following conditions are met:
● 'Sounder' is assigned to the control ↑ effect.
● 'Sounder' is highlighted in the tree view.
In the detail editor the following configurations are possible:
● Using 'Hardware', 'ALERT tone' and 'EVAC tone' and 'Sounder volume' can be
set.
● With 'Sounder beacon' using 'Hardware', 'Beacon activation' can additionally be
configured.
● Using 'Overview', a time limit can be set for 'Manned operation' and 'Unmanned
operation' separately.
The settings for 'Sounder' can also be viewed in the detail editor of the 'Hardware'
task card, using 'Overview' and 'Control'.
13.11 Sounder line via input/output module FDCIO223

You can use the two inputs/outputs of the input/output module FDCIO223 for the
connection of 'Sounder' lines.
You can assign a 'Sounder' line as an ↑ effect for the following controls:
● 'Internal sounder control'
● 'External sounder control'
Assigning the 'Sounder' line
Figure 108: Assigning sounder line

2. In the tree view, open the ↑ 'Station' and then one of the following controls:
– 'Alarming control group' > 'Internal sounder control' or 'External sounder
control'
– 'Evac control group' > 'Universal evac control' or 'Phased evac control'
279 | 406
'Control' task card
13 Sounder line via input/output module FDCIO223

a 'Collective/input/sounder/output' is assigned to 'Effects'.
Setting the properties of the 'Sounder' line

1. Highlight the assigned 'Sounder' line in the tree view.
The following properties can be set in the 'Overview' tab:
Figure 109: Settings in the detail editor of the sounder line
'Enabled':
The two settings 'Enabled' specify whether a time-out is used for the activation of
the control. The time-out can be set separately for 'Manned operation' and
'Unmanned operation'.
'Activation timeout 'manned'':

This setting specifies the duration of the time-out in 'Manned operation'. The time-
out is started when the control is activated. After the expiration of the set time, the
sounder is deactivated automatically.
280 | 406
'Control' task card
Sounder line via input/output module FDCIO223
13
'Activation timeout 'unmanned'':

This setting specifies the duration of the time-out in 'Unmanned operation'. The
time-out is started when the control is activated. After the expiration of the set time,
the sounder is deactivated automatically.
NOTICE
'unmanned''
'Control'.
You will find a description of the properties in the 'Hardware' tab in chapter
'Input/output module FDCIO223 [➙ 163]'.
See also
281 | 406
'Control' task card
13 Input/output module FDCIO223 with monitored input/output
13.12 Input/output module FDCIO223 with monitored

input/output
You can configure the two inputs / outputs of the input / output module FDCIO223
as monitored inputs and / or outputs.
You can assign one monitored input as cause for the following controls:
● 'Fire control'
You can assign one monitored output as an ↑ effect for the following control:
● 'Fire control'
See also
13.12.1 Configuring monitored input

Assigning input
Figure 110: Assigning input

2. Open ↑ 'Station' > ↑ 'Fire control group' > 'Fire control' in the tree view.
5. Select 'Input' at the left in the window.
a 'Collective/input/sounder/output' is assigned to 'Causes'.
282 | 406
'Control' task card
Input/output module FDCIO223 with monitored input/output
13
Setting properties of the input

1. Highlight the assigned input in the tree view.
Figure 111: Settings in the detail editor of the input

'Evaluation filter time':
This setting specifies the minimum amount of time the signal of the assigned input
must be active for the control to be evaluated as active.
13.12.2 Configuring monitored output

Assign output
Figure 112: Assign output

2. Open ↑ 'Station' > ↑ 'Fire control group' > 'Fire control' in the tree view.
5. Select 'Output/NO confirmation' at the left in the window.
a 'Collective/input/sounder/output' is assigned to 'Effects'.
283 | 406
'Control' task card
13 Addressable alarm indicator FDCAI221
Setting properties of the output

1. Highlight the assigned output in the tree view.
13.13 Addressable alarm indicator FDCAI221

The addressable ↑ alarm indicator FDCAI221 can be assigned to any cause using
a control. The addressable alarm indicator can be assigned to the effects of the
following controls:
● ↑ 'Fire control group':
– 'Fire control'
● 'Evac control group':
– 'Universal evac control'
– Phased evac control
Assigning an addressable ↑ alarm indicator

2. Open the control you want in the tree view.
5. Select the addressable alarm indicator in the tree view of the assignable
elements.
a 'Effects' is assigned to the addressable alarm indicator.
Figure 113: Assigning FDCAI221
284 | 406
'Control' task card
Key safe adapter [DE]: Configuring controls
13
13.14 Key safe adapter [DE]: Configuring controls

A fire control group must be configured with the two fire controls 'ÜE aktiv/bestätigt'
and 'Summenalarm' in order to operate a key safe adapter [DE].
Prerequisite
The key safe adapter has been created and assigned. See the chapter 'Key safe
adapter [DE] [➙ 355]'.
Creating a fire control group

1. Select the 'Control' task card and create a new 'Fire control group' for the
station with the key safe adapter, e.g., using the context menu.
2. Edit the customer text for the 'Fire control group', e.g., 'Key safe adapter'.
3. Create two elements of type 'Fire control' with the template 'Standard Fire
control' or without a BFST function for the 'Fire control group', e.g., using the
context menu.
4. Edit the customer text for the two 'Fire controls':
– 'Fire controls 1': 'ÜE aktiv/bestätigt'
– 'Fire controls 2': 'Summenalarm'
Assigning the 'ÜE aktiv/bestätigt' fire control

1. Use the 'Assign' function to assign the 'Causes' to the control as follows:
– Select the ' --Activation/confirmed' element under 'Events 'Activation'' in
'Manual type selection' on the left-hand side of the 'New cause dialog'.
– Select the 'RT fire control' element in the control tree on the right-hand side
of the 'New cause dialog'.
285 | 406
'Control' task card
13 Key safe adapter [DE]: Configuring controls
2. Use the 'Assign' function to assign the 'Effects' to the control as follows:
– Select the 'Output/NO confirmation' element under 'Outputs' in 'Manual type
selection' on the left-hand side of the 'New cause dialog'.
under FCI2008 in the hardware tree on the right-hand side of the 'New
cause dialog'.
– Or
– When activating the 'Key safe adapter' via FDCIO222/224: Select the
output 22 under FDCIO222/224 in the hardware tree on the right-hand side
286 | 406
'Control' task card
Key safe adapter [DE]: Configuring controls
13
Assigning the 'Summenalarm' fire control

1. Use the 'Assign' function to assign the 'Causes' to the control as follows:
– Select the ' --All Fire ALARMS' element under 'Events 'Alarm and Pre-
alarm'' in 'Manual type selection' on the left-hand side of the 'New cause
dialog'.
– Select one or more stations which are to activate the key safe adapter on
the right-hand side of the 'New cause dialog'.
287 | 406
'Control' task card
13 Key safe adapter [DE]: Configuring controls
2. Use the 'Assign' function to assign the 'Effects' to the control as follows:
– Select the 'Output/NO confirmation' element under 'Outputs' in 'Manual type
selection' on the left-hand side of the 'New cause dialog'.
under FCI2008 in the hardware tree on the right-hand side of the 'New
cause dialog'.
– Or
– When activating the 'Key safe adapter' via FDCIO222/224: Select the
output 21 under FDCIO222/224 in the hardware tree on the right-hand side
See also
2 Key safe adapter [DE]: Configuring the technical
zone [➙ 230]
2 Assigning LEDs [➙ 357]
288 | 406
'Operation' task card
Global system configuration
14
14 'Operation' task card

The 'Operation' task card contains the logical elements for the global system
configuration and for configuring the operation and indication units.
14.1 Global system configuration
The element 'Global system configuration' is available once per ↑ 'Site' and
contains the following elements:
● 'Global behaviour'
● 'Global PIN configuration'
● 'Country settings'
● 'Global system time'
You will find information on this in the following chapters.
289 | 406
14 Global system configuration
14.1.1 System behavior

The 'Global behaviour' element contains the settings for the system behavior:
● 'Events': The event categories in the system are displayed with the
corresponding properties.
● 'Commands': The system commands are displayed with the corresponding
access levels.
Properties for 'Global behaviour' on the 'Overview' tab
'System wide isolation of all buzzers enabled'

This setting specifies whether the 'Buzzers' of all 'Stations' can be switched off
system-wide with a command.
Properties for 'Global behaviour' on the 'Details' tab
'Type of address information'

This setting specifies which address information is displayed in messages: Plan no.
and/or element address. The setting is depending on the element and on the
availability of the plan no.
'BACnet alarm notification in section enabled'

If this checkbox is checked, a BACnet notification or 'Section summary' is created if
an alarm occurs within an FS20 section. The BACnet object type of the 'Section
summary' is 'Binary Value'. The 'Section summary' can be transmitted to sub-
systems, e.g., to Desigo PX.
'BACnet notifications of detector lines enabled'

If this checkbox is checked, a BACnet notification is created if a fault or information
event occurs on an FS20 detector line or on a device within the detector line. A
'Line fault summary' or 'Line information summary' is created, the BACnet object
type of which is 'Life-Safety'.
'BACnet priority of Fire/Smoke extraction dampers, commanding via

control'
This setting defines the BACnet priority for fire and smoke dampers when the
dampers are controlled automatically by damper controls.
290 | 406
14
'BACnet priority of Fire/Smoke extraction dampers, commanding via

Operating terminal'
This setting defines the BACnet priority for fire and smoke dampers when the
dampers are controlled manually via an operating terminal.
'Enabled'
This setting specifies whether a reminder message is displayed before the 'Time
limited isolation' of a 'Zone' or a 'Detector' expires and the 'Zone' or the 'Detector' is
switched back on again automatically.
' --Expiry reminder of time lim. isol.'

This setting specifies when the reminder message is displayed. If, for example, the
setting is '00:05', a reminder message is displayed five minutes before the duration
of the isolation (bypass) expires and the 'Zone' or the 'Detector' is switched back on
again automatically. This setting applies for all 'Zones' and 'Detectors' within the
↑ 'Site'.
'Danger level latching in installation test mode'

This setting specifies whether the ↑ danger levels from detectors are latched in a
'Automatic zone' when the 'Zone' is in 'Installation test' mode. A single individual
can use this setting to test a 'Zone' with ↑ multi-detector dependency. If a detector
with latched danger level reaches a higher danger level, then the higher danger
level will be latched.
The latched ↑ danger levels are deleted in the following cases:
● The 'Installation test' mode is ended.
● The 'Zone' reaches 'PRE-STAGE' or 'MAIN STAGE', respectively, and the
corresponding event message is acknowledged or reset. In addition, the
danger levels of the detector must also return to 0.
'Walk test activation mode'

This setting specifies which ↑ alarm devices are activated in the 'Walk test' mode.
'Duration of sounder activation in walk test'

This setting specifies the length of time for which the ↑ alarm devices are activated
in 'Walk test' mode.
'Suppress messages 'Change recommended'/'Change required' from

FDnet devices'
This setting specifies whether the service information messages 'Change
recommended' and 'Change required' should be displayed.
See also
2 Multi-detector dependency with latching [➙ 220]
291 | 406
14 Global system configuration
14.1.2 Global PIN configuration

The PINs for the access levels of a ↑ 'Site' can be set either in 'SintesoWorks' or at
a ↑ 'Station'. The required pre-setting is specified in 'SintesoWorks'.
After a firmware update, all PINs are deleted and must be reset.
If the configuration of the ↑ 'Site' is converted and loaded in the 'Station', the set
PINs remain valid.
Pre-setting for PIN configuration

1. Select the 'Operation'' > 'Global system configuration' > 'Global PIN
configuration' task card.
2. Set the 'Overview' on the 'PIN configuration method' tab.
PIN configuration
NOTICE
No firmware update possible due to no 'Access level 3'
● At least one PIN with 'Access level 3' must be configured.
w 'Global PIN configuration' is configured for the 'PIN configuration in Engineering

tool'.
1. Select 'Mandatory PIN' and enter the PIN on the 'Overview' tab.
2. Create the 'Global PIN configuration' element for the 'Optional PIN'.
3. Select 'Optional PIN' and enter the PIN on the 'Overview' tab.
A maximum of 10 PINs with 'Access level' can be configured. At least one PIN
must be configured. Each PIN must be unique.
14.1.3 Country settings

Country-specific settings are defined in the 'Country settings' element.
292 | 406
14
14.1.4 Master clock

The 'Global system time' element shows which ↑ 'Station' is the master clock.
When the first 'Station' is created, SintesoWorks assigns this element to the first
'Station' (address 1) automatically. The ↑ link to the 'Station' may therefore be
deleted or need to be changed. If this is the case, then the link must be created
again.
Figure 114: Assign master clock

To assign the master clock, proceed as follows:
2. Open 'Global system configuration' in the tree view.
3. Highlight 'Global system time'.
a At the right in the window, the 'Hardware tree' is displayed.
5. Select the relevant ↑ 'Station' and click on 'Assign'.
a 'Global system time' is assigned to the 'Station'.
293 | 406
14 Person Machine Interface (PMI)
14.2 Person Machine Interface (PMI)

The 'PMI' element contains the configurable elements of the Person Machine
Interface:
● Basic settings
● 'LEDs'
● 'Standard keys'
● 'Favorite keys'
● ↑ Visibility
You will find information on these elements in the following chapters.
14.2.1 Basic settings

You will find the basic settings for the ↑ Person Machine Interface in the detail
editor of the 'PMI' element.
'Overview' tab
'Logout timeout'
This setting specifies the length of time after which the ↑ Person Machine Interface
of the ↑ 'Station' automatically switches back to 'Default access level' if no key is
pressed.
'Operation timeout 'ALARM''

of the ↑ 'Station' automatically switches from the menu display to the message
display if no key is pressed. This time-out is used if ALARM events are present.
'Operation timeout 'NO alarm''

of the ↑ 'Station' automatically switches from the menu display to the message
display if no key is pressed. This time-out is used if no ALARM events are present.
The time outs are only used if the corresponding 'Enabled' checkbox is activated.
'Default access level'

This setting specifies the standard access level of the ↑ 'Station'. If the 'Station' has
a key switch, then this setting is for the 'off' position.
294 | 406
Person Machine Interface (PMI)
14
'Access level 'key switch''

If the ↑ 'Station' has a key switch, then this setting specifies the access level in the
'on' position.
'Details' tab
'Reminder buzzer'
This setting specifies at which events the 'Buzzer' is reactivated at regular intervals
as a reminder that something needs to be done. Example: In the case of an
ALARM event, the 'Buzzer' sounds twice every 15 seconds briefly.
'Default alarm view'

This setting specifies in which view messages are shown on the display in the case
of an alarm e.g. 'Standard message view' or 'Extended message view'. You will find
information on the various views in the document 008838. See chapter 'Applicable
documents'.
'Enabled'
This setting specifies whether a time-out is used for the display backlight.
'Backlight timeout'
This setting specifies after which time period the display backlight is switched off.
The backlight is only switched off when the following occurs:
● An alarm event has occurred.
● No unacknowledged event has occurred.
● The 'Buzzer' is not active.
● No key is pressed.
295 | 406
14.2.2 LEDs
Functions of the LEDs
● Signal events and states
● Help guide the operator
Configuring LEDs
● Each LED can be assigned to up to twelve causes.
● For each cause, you can set the LED properties e.g., 'Priority', 'LED mode', and
'Colour'.
Assigning causes to LEDs

You can assign the following types of causes:
● Pre-defined cause: You select an event from a pre-defined list. If the event
occurs within the ↑ visibility of the ↑ 'Station', the LED is activated. You will find
more information on this in chapter 'Assigning the pre-defined cause [➙ 297]'.
● Event in a specific element within the ↑ 'Site': You select an event and the
element, including its subelements, in which the event must occur so that the
LED is activated. You will find more information on this in chapter 'Assigning
event [➙ 298]'.
When you configure a LED, you must change the inscription on the LED on the
↑ Person Machine Interface, if required. You will find editable inscription strips for
the Person Machine Interface in the 'Inscription strips' document. See chapter
See also
296 | 406
14
14.2.2.1 Assigning the hardware ID to the LED

The figure below shows the assignment of the hardware ID to the corresponding
LED on the ↑ Person Machine Interface. The numbers correspond to the hardware
ID of the LED.
~ bc ef
d
1 2 3
hi kl no
m
j
4 5 6
rs v yz
wx
tu
pq
7 8 9
3 * 0 #
4
5 C ok
6
24
25
Figure 115: Assigning the hardware ID to the LED on the ↑ Person Machine Interface
You will find the hardware ID in the detail editor of the LED in the 'HW ID LED' field.
Figure 116: Detail editor of a LED with details of the hardware ID
14.2.2.2 Assigning the pre-defined cause

● You can assign the pre-defined causes to each configurable LED. You can
assign several pre-defined causes to one LED.
● If you assign several causes, the LED properties must be different from each
other e.g. 'Priority', 'LED mode', or 'Colour'.
Assigning an LED with a pre-defined cause

1. Select the 'Operation'' > ↑ 'Station' > Element with LEDs > LED task card.
3. Select 'Pre-defined causes' at the left in the window and highlight 'Standard' at
the right in the window.
a The 'Cause / Undefined' element is created under the LED.
5. Highlight the 'Cause / Undefined' element.
7. If required, change the inscription on the LED on the device.
You will find editable inscription strips in the 'Inscription strips' document. See
297 | 406
Setting the properties of the assigned cause element on the

'Overview' tab
● 'Event filter': Event that activates the cause and thus the LED. All events within
the configured ↑ visibility of the element are evaluated.
● 'Colour': Color of the LED when activated.
● 'LED mode': Lighting mode of the LED when activated.
● 'Priority': Priority of the cause compared with other causes which are assigned
to the same LED.
● 'Include unreliable events': If the checkbox is checked, the unreliable events
will be included in the evaluation of the cause. An unreliable event is an event
from another station which lost the connection after the event occurred.
14.2.2.3 Assigning event

● You can assign one or more events within the ↑ 'Site' to each configurable
LED.
● If you assign several causes, the LED properties must be different from each
other, e.g., 'Priority', 'LED mode', or 'Colour'.
Assigning an LED to an event

1. Select the 'Operation'' > 'Station' > Element with LEDs > LED task card.
3. Select an event category on the left in the window.
4. On the right in the window, select a tree and an element.
a The event is assigned to the LED.
6. Highlight the assigned event and set the properties you want in the detail
editor.
Setting the properties of the assigned event
● 'Colour': Color of the LED when activated.

● 'LED mode': Lighting mode of the LED when activated.
● 'Priority': Priority of the cause compared with other causes which are assigned
to the same LED.
● 'Include unreliable events': If the checkbox is checked, the unreliable events
will be included in the evaluation of the cause. An unreliable event is an event
from another station which lost the connection after the event occurred.
298 | 406
14
14.2.3 Standard keys
Figure 117: 'Standard keys' element in the tree view

Each standard key can be assigned a function or a toggle function. With that you
can quickly carry out often used actions and commands.
You can configure the following types of functions:
● 'Dialog': The key is assigned to a specific view on the display of the ↑ Person
Machine Interface. Pressing on the key shows the view on the display e.g.
'Dialog 'Config viewer, Topology'' > 'Detection tree'.
● 'Action': The key is assigned to a pre-defined action. Pressing on the key
executes the action e.g. 'All sounders OFF'.
● Commands:
– Command for a specific element: The key is assigned to a command and
an element within the ↑ 'Site'. Pressing on the key executes the command
for this element, e.g., 'Detector test' for a particular 'Manual zone'.
– Command for the 'Zone' element category: The key is assigned to a
command and the 'Zone' element category. Pressing on the key shows the
window for entering the address for the 'Zone'. After entering the address,
the command for the corresponding element is executed.
When you configure a standard key, you may have to change the inscription on
the standard key on the ↑ Person Machine Interface. You will find editable
inscription strips for the Person Machine Interface in the 'Inscription strips'
document. See chapter 'Applicable documents'.
You will find information on configuration of standard keys in chapter 'Configuring

standard keys and favorites [➙ 303]'.
See also
299 | 406
14.2.4 Favorites
Figure 118: 'Favorite keys' element in the tree view

There are a maximum of eight favorites of which three are preconfigured. Each
favorite can be assigned a function. With that you can quickly carry out often used
actions and commands.
The favorites are represented in the display of the ↑ Person Machine Interface.
The first three favorites are assigned to the three softkeys in the main menu. All
favorites are listed in the 'Favorites' menu. To execute a favorite function, you must
press the corresponding key on the keypad.
You will find information on the keys in the ↑ Person Machine Interface in
You can configure the following types of functions:

● 'Function': The favorite is assigned to a function from the 'Functions' menu of
the 'Station'. Pressing on the key shows the corresponding window for entering
the element category or the address on the display of the Person Machine
Interface.
● 'Dialog': The favorite is assigned to a specific view on the display. Pressing on
the key shows the view on the display e.g. 'Dialog 'Config viewer, Topology'' >
'Detection tree'.
● 'Action': The favorite is assigned to a pre-defined action. Pressing on the key
executes the action e.g. 'All sounders OFF'.
● Commands:
– Command for a specific element: The favorite is assigned to a command
and an element within the 'Site'. Pressing on the key executes the
command for this element e.g. 'Detector test' > 'Manual zone'.
– Command for the element category: The favorite is assigned to a command
and an element category e.g. 'Zone' or 'Section'. Pressing on the key
shows the window for entering the address for the element category on the
display. After entering the address, the command for the corresponding
element is executed.
300 | 406
14
Configurable favorites for FT2080

You can exclusively configure the following favorites for the fire terminal (Touch):
- 'Action' > 'All sounders OFF'
- 'Action' > 'All sounders ON'
- 'Dialog 'Message viewer, Message summary'' > 'Reset selection'
- 'Dialog 'Config viewer, Topology''
- 'Dialog 'Admin viewer, Add user''
- 'Dialog 'Admin viewer, Delete user''
- 'Dialog 'Admin viewer, LED test'' > 'LED test'
You will find information on configuration of favorites in chapter 'Configuring

standard keys and favorites [➙ 303]'.
14.2.4.1 Creating favorites
Three favorites are preconfigured.

2. Open the ↑ 'Station' > 'PMI' in the tree view.
3. Highlight 'Favorite keys'.
5. Enter the number of favorites required in the 'Amount:' field.

6. Click on 'Add'.
a The 'Favorite' element is created.
301 | 406
14.2.4.2 Text for favorites

For 'Function' and 'Action', there are pre-defined texts, which are shown on the
↑ Person Machine Interface display, e.g., 'Action' 'All sounders OFF'.
The pre-defined text is only displayed if the 'Customer text' field for the 'Favorite'
element is empty. When you enter customer text for the 'Favorite' element, this text
is displayed on the Person Machine Interface instead of the pre-defined text.
If there are no predefined texts available, you must provide customer text.
Customer text for favorites

If the customer text is used for a softkey, you can enter a maximum of 13
characters per line. If you want to enter more text, you can use two lines. To insert
a line break, enter the following text:
$(BR)
Example of a customer text covering two lines:
Figure 119: Example of a customer text covering two lines
14.2.4.3 Defining the position of the favorites

The position specifies at which place the favorite is displayed in the 'Favorites'
menu. The positions are from top left to bottom right. The favorites with positions '1'
to '3' are assigned to the three softkeys in the main menu.
To create a further favorite, it has the position '0' by default. You must set the
position to at least '1'.
Figure 120: Detail editor of the favorite with details of the position
To define the position of the favorite, proceed as follows:
1. Highlight the 'Favorite' element in the tree view.
2. Select the 'Overview' tab in the detail editor.
3. In the 'Position' field enter the position of the favorite.
a The favorites are correspondingly arranged.
302 | 406
14
14.2.5 Configuring standard keys and favorites
14.2.5.1 Assigning the hardware ID to the standard key

The figure below shows the assignment of the hardware ID to the corresponding
standard key on the ↑ Person Machine Interface. The numbers correspond to the
hardware ID of the standard key.
~ bc ef
d
1 2 3
hi kl no
m
j
4 5 6
rs v yz
wx
tu
pq
7 8 9
0 #
*
9 C ok
13
14
Figure 121: Assigning the hardware ID to the standard key on the ↑ Person Machine Interface
You will find the hardware ID in the detail editor of the standard key in the 'HW ID
KEY' field.
Figure 122: Detail editor of a standard key with details of the hardware ID
Favorites have no hardware ID.
303 | 406
14.2.5.2 Assigning standard keys and favorites

To assign a function to a standard key or a favorite, proceed as follows:
2. In the tree view, open ↑ 'Station' > 'PMI' > 'Standard keys' or 'Favorite keys'.
3. Highlight a 'Key' element or 'Favorite'.
5. Select a type of function on the left in the window: 'Function', 'Dialog', 'Action',
or command.
a Depending on the selected type of function, the selection on the right in the
window is adapted. The selection options are described below.
6. On the right in the window, select the desired element.
a The standard key or the favorite is assigned to the function.
8. If required, change the inscription on the standard key on the ↑ Person
Machine Interface.
↑ Assigning to 'Function'
If you select 'Function' on the left in the window, you can select 'Standard' on the
right in the window. You can set the properties of the function in the detail editor of
the assigned function.
Figure 123: Assigning favorite to a function
'Function' cannot be assigned to a standard key, but must be assigned to a

favorite.
304 | 406
14
↑ Assigning to 'Dialog'
If you select 'Dialog' on the left in the window, you can select 'Standard' on the right
in the window. You can set the properties of the view in the detail editor of the
assigned 'Dialog'.
Figure 124: Assigning a standard key or favorite to an 'Dialog' function
Assigning to 'Action'
If you select 'Action' on the left in the window, you can select a pre-defined action
on the right in the window.
Figure 125: Assigning a standard key or favorite to an 'Action' function
305 | 406
↑ Assigning to a command for a specific element

If you select a command on the left in the window, you can select a tree and the
element on the right in the window for which the command is to be executed.
Figure 126: Assigning a standard key or a favorite to a command and an element
↑ Assigning to a command for a 'Zone'

If you select 'Command/element category' on the left in the window, you can select
a command from the list on the right in the window. The command can be applied
for 'Zones'.
Figure 127: Assigning a standard key or a favorite to a command and an element category
You can also assign the 'Function', 'Dialog', 'Action', and 'Command/element
category' functions via the 'New element' window.
306 | 406
14
14.2.5.3 Properties of the assigned functions

In the detail editor of the functions which are assigned to the standard keys and the
favorites, you can set different properties depending upon the assigned functions.
'Access level'
This setting specifies the access level which is required for executing the functions.
You can set this property for each function.
↑ Assigning to 'Function'
If the favorite is assigned to 'Function', you can set the following properties in the
detail editor of the function:
Figure 128: Properties in the detail editor of the function

'Function': This setting specifies which function from the 'Functions' menu should
be executed.
↑ Assigning to 'Dialog'
If the standard key or the favorite is assigned to a 'Dialog', function, you can set the
following properties in the detail editor of the function:
Figure 129: Properties in the detail editor of the 'Dialog' function

● 'Dialog name': View that should be shown on the display of the Person
Machine Interface.
● 'Dialog argument': Additional setting for the view. The selection is dependent
on the setting in the 'Dialog name' field.
↑ Assigning to a command for a specific element

If the standard key or the favorite is assigned to a command function for a specific
element, you can set the following properties in the detail editor of the function:
Figure 130: Properties in the detail editor of the command function

● 'Command parameter': The assigned command is specified in more detail with
this setting. If you have e.g. assigned the 'Set PS' command as a function, you
must set the desired 'Parameter set'.
The 'Command parameter' property is only displayed in the detail editor if a

command was assigned, which requires a more detailed specification.
● 'Enabled' and 'Reverse command': These settings are used when you
configure a standard key with a toggle function. Link [➙ 308]
307 | 406
↑ Assigning to a command for an element category

If the standard key or the favorite is assigned to a command function for an
element category, you can set the following properties in the detail editor of the
function:
Figure 131: Properties in the detail editor of the command function

'Access level': Defines the access level for the command
14.2.6 Toggle function

You can assign a command and the associated reverse command to a standard
key, e.g., ↑ switch off / switch on and activate / deactivate. Pressing on the key
executes either the command or the reverse command.
Which command is performed when a key is pressed depends on the current
condition of the LED which is assigned to the standard key:
● LED inactive: The command is executed by pressing a key again.
● LED active: The reverse command is executed by pressing a key again.
This means the LED must be configured such that it is active when the command
has been carried out.
Example:
● The standard key is assigned to 'Automatic zone' 2.
● Command = 'Detector test'
● Reverse command = 'Detector test END'
● The LED is active if 'Automatic zone' 2 is in the 'Detector test' status.
When the assigned 'Zone' is switched off, you cannot execute any commands for
this zone using the toggle function of the standard key.
To configure a standard key to the toggle function, you must first configure the
standard key and then the LED. You will find information on this in the following
chapters.
You will find information on how to assign the hardware IDs to the respective LED
and standard key on the ↑ Person Machine Interface in the following chapters:
● 'Assigning the hardware ID to the LED [➙ 297]'
● 'Assigning the hardware ID to the standard key [➙ 303]'
A toggle function cannot be configured for favorites.
When you configure a standard key for a toggle function, you may have to change
the inscription on the standard key and the LED on the ↑ Person Machine
Interface. You will find editable inscription strips for the Person Machine Interface
in the 'Inscription strips' document. See chapter 'Applicable documents'.
See also
308 | 406
14
14.2.6.1 Configuring standard key for the toggle function

Configuring the command
Figure 132: Assigning a standard key to a command and an element

2. Open ↑ 'Station' > 'PMI' > 'Standard keys' in the tree view.
3. Highlight a 'Key' element.
5. Select a command on the left in the window e.g. 'Detector test'.
6. On the right in the window, select an element, e.g., a 'Zone' from the
↑ 'Detection tree'.
a The 'Key' is assigned to the command and the element.
a The command is displayed under the 'Key' in the tree view.
309 | 406
Configuring a reverse command
Figure 133: Configuring a reverse command
1. Highlight the assigned command in the tree view.

2. Select the 'Overview' tab in the detail editor.
3. Check the 'Enabled' checkbox.
4. In the 'Reverse command' field, select the reverse command, e.g., 'Detector
test END'.
a The reverse command is configured.
When you assign a command which requires a more detailed specification, you
must set the 'Reverse command parameter' property additionally in the detail
editor. If you have assigned the 'OFF/timer' command, for example, you must set
the desired time.
Figure 134: Configuring a reverse command
310 | 406
14
Assigning the standard key to the LED
Figure 135: Assigning the standard key to the LED
1. Highlight the configured standard key in the tree view.

3. Select 'Related LED' at the left in the window.
a At the right in the window, the 'Operation tree' is displayed.
4. Select the appropriate LED for the standard key.
a The standard key is assigned to the LED.
311 | 406
14.2.6.2 Configuring LED for the toggle function
Figure 136: Assigning a LED to an event

2. Open ↑ 'Station' > 'PMI' > 'LEDs' in the tree view.
3. Highlight the appropriate LED for the standard key.
a The 'New cause dialog' window opens.
5. Select an event category on the left in the window e.g. 'Detector test mode'.
6. On the right in the window, select the same element from the ↑ 'Detection tree'
that you have assigned to the standard key.
a The LED is assigned to the 'Zone'.
8. Highlight the assigned cause element and set the LED properties in the detail
editor. The LED properties are described in chapter 'Assigning event [➙ 298]'.
9. If required, change the inscription on the LED and the standard key on the
↑ Person Machine Interface.
See also
312 | 406
Visibility
14
14.3 Visibility
The ↑ visibility defines which parts of a ↑ 'Site' can be viewed and/or operated on a
↑ 'Station'.
You can configure the visibility as follows:
● 'Site': Visibility for the entire 'Site'
● 'Site without areas': Visibility for all events from the 'Hardware tree' of the 'Site'
● 'Station': Visibility for a 'Station' within the 'Site' with all 'Areas' in this 'Station',
incl. 'Hardware tree'
● 'Station without areas': Visibility for all events from the 'Hardware tree' of the
'Station'
● 'Area': Visibility for an 'Area' within a 'Station'
Additionally, you can define which event categories are visible for each assigned
element.
Types of ↑ visibility
● Standard visibility: The normal visibility if no additional conditions are met.
● Standby visibility: This visibility is activated when a monitored ↑ 'Station' fails.
● Expanded visibility: This visibility can be activated manually at the ↑ Person
Machine Interface.
You will find information on this in the following chapters.
You will find more information about the visibility in document 008838. See
See also
313 | 406
14 Visibility
14.3.1 Properties of the visibility
Figure 137: Properties in the detail editor of the ↑ visibility
'Max. access level'

In this field you can define the maximum access level that is possible on the
↑ 'Station' when this ↑ visibility is active. If several visibilities are active
simultaneously, e.g. the standard visibility and the expanded visibility, the
maximum value that is set in the 'Max. access level' field is valid.
'Visible secondary events'

This setting specifies from which normally not visible elements, the activation
messages are displayed if they are activated by an element in the visible part.
You can define the visible event categories in the detail editor of the elements
assigned to the visibility in the 'Overview' tab.
Figure 138: Properties in the detail editor of the element assigned to the visibility
'ALL event categories visible'

If this checkbox is activated, all the event categories are visible.
'Visible event categories'

If only a specific event category is to be visible e.g. 'ALARMS' and 'Faults', you can
define the event category here. The setting is only possible if the 'ALL event
categories visible' checkbox is deactivated.
314 | 406
Visibility
14
14.3.2 Standard visibility

The standard visibility defines which events in which elements can be viewed and /
or operated on the ↑ 'Station' in ↑ normal operation.
You can configure the visibility as follows:
● 'Site': Visibility for the entire 'Site'
● 'Site without areas': Visibility for all 'Site' events, but not for the detection tree
● 'Station': Visibility for a 'Station' within the 'Site' with all 'Areas' in this 'Station',
incl. 'Hardware tree'
● 'Station without areas': Visibility for all 'Station' events, but not for the detection
tree
● 'Area': Visibility for an 'Area' within a 'Station'
Additionally, you can define which event categories are visible for each assigned
element.
When creating a 'Station', the 'Standard visibility' element is pre-configured with
↑ visibility of its own 'Station'. You can add additional elements to the pre-
configured visibility or delete it and replace it with a different visibility.
Configuring standard visibility
Figure 139: Configuring standard visibility

3. Highlight the element 'Standard visibility'.
5. Select the ↑ visibility you want on the left in the window.
6. On the right in the window, select the corresponding element.
a The element is assigned with 'Standard visibility'.
315 | 406
14 Visibility
14.3.3 Standby visibility

A 'Station' with standby visibility monitors one or more 'Stations' or ↑ management
stations. If a monitored 'Station' or management station fails, the standby visibility
becomes active. This provides you with visibility of the 'Station' with standby
↑ visibility for the failed 'Station' or management station.
The standby visibility has to be deactivated via the ↑ Person Machine Interface of
the 'Station'. You will find more information in document 008838. See chapter
There are two different standby visibilities:
● 'Standby visibility for Operating terminal': For monitoring FS20 'Stations'.
● 'Standby visibility for Management station': For monitoring a management
station.
Creating standby visibility

2. In the tree view, open the 'Station' and highlight the 'PMI' element.
4. In the 'Type:' field select 'Standby visibility for Operating terminal' or 'Standby
visibility for Management station'.
5. Click on 'Add'.
a The standby visibility is created.
You can also create the standby visibility using the 'Assign' function.
316 | 406
Visibility
14
Configuring 'Standby visibility for Operating terminal'

During configuration, you must define which 'Station' is monitored and which
↑ visibility the monitored 'Station' has.
w The element 'Standby visibility for Operating terminal' is created.
2. Open 'Station' > 'PMI' in the tree view.
3. Highlight the element 'Standby visibility for Operating terminal'.
5. On the left in the window, from the 'Visibility' list, select the visibility of the
monitored 'Station'.
a The element is assigned to the standby visibility.
8. On the left in the window, from the 'PMI supervision for standby visibility' list,
select the 'Visibility activation upon failure of Operating terminal..' entry.
9. On the right in the window, select the 'Station' which is to be monitored.

a The 'Station' is assigned to 'Standby visibility for Operating terminal'.
317 | 406
14 Visibility
Configuring 'Standby visibility for Management station'

w The element 'Standby visibility for Management station' is created.
w The 'Station' is configured with 'BACnet client supervision'. You will find more
information on this in chapter 'Global BACnet configuration [➙ 380]'.
2. Open 'Station' > 'PMI' in the tree view.
3. Highlight the element 'Standby visibility for Management station'.
5. On the left in the window, from the 'Visibility' list, select the visibility of the
monitored management station.
a The element is assigned to the standby visibility.
8. On the left in the window, from the 'PMI supervision for standby visibility' list,
select the 'Visibility activation upon failure of Management station..' entry.
9. On the right in the tree, select 'BACnet client supervision'.

a 'BACnet client supervision' is assigned to 'Standby visibility for Management
station'.
See also
2 Global BACnet configuration [➙ 380]
318 | 406
Visibility
14
14.3.4 Expanded visibility

Expanded ↑ visibility enables increased visibility compared against standard
visibility. The expanded visibility is used so that e.g. the commissioning or
maintenance personnel can temporarily access other parts of the system. If, for
example, a ↑ 'Station' in the standard visibility only has visibility for one 'Area', the
expanded visibility can be configured in such a way that the entire 'Station'
becomes visible on activation.
The expanded visibility can be configured such that it can only be activated with
the failure of a monitored 'Station'.
The expanded visibility has to be activated and deactivated by a command on the
↑ Person Machine Interface.
The expanded ↑ visibility is used in [AT] to give the ↑ 'Stations' visibility of the rest
of the system in the event of a system collapse due to several network errors, in
accordance with TRVB S 123.
Creating expanded ↑ visibility
Figure 140: Creating expanded visibility

2. In the tree view, open the ↑ 'Station' and highlight the 'PMI' element.
4. Select 'Expanded visibility' in the 'Type:' field.
5. Click on 'Add'.
a The 'Expanded visibility' element is created.
You can also create the standby visibility using the 'Assign' function.
Configuring expanded ↑ visibility
Figure 141: Configuring expanded visibility

3. Highlight the element 'Expanded visibility'.
5. On the left in the window, from the 'Visibility' list, select the expanded visibility.
a The element is assigned with 'Expanded visibility'.
319 | 406
14 Visibility
Configuring expanded visibility with monitoring

If you configure the expanded visibility such that it can only be activated in the
event of a failure of a monitored ↑ 'Station' then you must assign the 'Station' to be
monitored additionally.
Figure 142: Assigning expanded visibility and monitored 'Station'
w The expanded visibility is created and configured according to the above

mentioned steps.
1. Highlight the 'Expanded visibility' element in the tree view.
3. On the left in the window, from the 'PMI supervision for expanded visibility' list,
select the 'Visibility activation by command upon failure of Operating terminal..'
entry.
4. On the right in the window, select the 'Station' which is to be monitored.
a The 'Station' is assigned to 'Expanded visibility'.
14.3.5 Configuring visibility on FC2080

Because of the fact that the FC2080 fire control panel has no integrated operating
unit, you must configure at least one operating unit within the 'Site' in such a way
that it has a ↑ visibility of the FC2080.
Figure 143: Configuring visibility on FC2080
w The 'FC2080' element is present in the structure tree.

w The ↑ 'Stations' that are to have a ↑ visibility of the FC2080 are present in the
structure tree.
2. In the tree view, open the 'Station' that is to have a visibility of the FC2080.
3. Open the 'PMI' window and highlight the 'Standard visibility' element.
5. Select the desired visibility on the left in the window.
6. On the right in the window, select the 'FC2080' element.
a The visibility on the FC2080 is configured.
320 | 406
Visibility
14
14.3.6 Configuring visibility for Sinteso Mobile

To configure 'Visibility' for smartphones in FXS2002, proceed as follows:
1. Select 'Operation' > ↑ 'Station' in the task card.
2. Create the 'Sinteso Mobile' element for the 'Station'.
3. Open 'Sinteso Mobile' in the tree view.
4. Select 'Standard visibility'.
5. Select 'Assign'.
6. In the 'Assign' window, select the 'Station' on which you want to set 'Visibility'
for smartphones and confirm your choice by clicking 'Assign'.
7. Go to the tree view and select the assigned 'Station'. Then select the
'Overview' tab.
8. Activate the 'ALL event categories visible' option.
a 'Visibility' for smartphones has now been specified.
a All 'Event categories of the 'Station' are visible for smartphones.
Figure 144: Configuring ↑ visibility
321 | 406
14 Floor repeater terminal FT2010 and floor repeater display FT2011
14.4 Floor repeater terminal FT2010 and floor repeater

display FT2011
↑ Floor repeater terminal (FRT)
The following can be configured for the floor repeater terminal:
● ↑ Visibility
● Causes for the activation of the LEDs
● Six keys
↑ Floor repeater display (FRD)

The following can be configured for the floor repeater display:
● ↑ Visibility
● Causes for the activation of a LED
14.4.1 FT2010/FT2011 core and configuration groups

In order to configure the ↑ floor repeater terminal (FRT) or ↑ floor repeater display
(FRD), an 'Operation' element is created in the 'FDnet line card
(onboard/FCL2001)' task card for each FDnet where floor repeater terminals or
displays are connected to the FRT/FRD core detector line. 'FRT configuration
group' elements can be created for the floor repeater terminals and 'FRD
configuration group' for the floor repeater displays. Each of these elements can be
assigned to up to eight 'FRT' (FT2010) or 'FRD' (FT2011).
It is currently also possible to assign 'FRT' or 'FRD' which are connected to

another FDnet line card (onboard/FCL2001).
Only assign channels that are connected to the FRT/FRD core assigned to the
'FDnet line card (onboard/FCL2001)'.
322 | 406
Floor repeater terminal FT2010 and floor repeater display FT2011
14
14.4.1.1 Configuration after reading in the hardware

Creating 'FRT/FRD core' elements and assigning them to the FDnet
line card (onboard/FCL2001)
2. Highlight the 'Station' in the tree view.
a 'FRT/FRD core' is highlighted and in Hardware tree the element 'FDnet line
card (onboard/FCL2001)' is highlighted.
a 'FRT/FRD core' is created and assigned to the FDnet line card
(onboard/FCL2001).
Creating 'FRT configuration group' or 'FRD configuration group'

elements
l Create the 'FRT configuration group' or 'FRD configuration group' element for
'FRT/FRD core'. Link [➙ 77]
323 | 406
Assigning configuration groups to the channel of the FT2010 or

FT2011 device
1. Highlight 'FRT configuration group' or 'FRD configuration group' in the tree
view.
2. Select 'Assign'.
a In the 'Assign dialog' window, 'FRT' or 'FRD' is highlighted and the

Hardware tree is displayed. The 'FRT' or 'FRD' element of the 'FT2010' or
'FT2011' device is highlighted.
3. Select the element and click on 'Assign'.
a The configuration group is assigned to the channel of the FT2010 or FT2011
device.
14.4.1.2 Pre-configuring the 'FT2010/FT2011 core' element

Creating 'FRT/FRD core' elements
1. Select 'Operation' > 'Station' in the task card.
2. Create the 'FRT/FRD core' element for the 'Station'. Link [➙ 77]
Creating 'FRT configuration group' or 'FRD configuration group'

elements
l Create the 'FRT configuration group' or 'FRD configuration group' element for
'FRT/FRD core'. Link [➙ 77]
Creating 'FRT' or 'FRD' elements

l Create the 'FRT' or 'FRD' element for 'FRT configuration group' or 'FRD
configuration group'. Link [➙ 77]
In a later step, once the hardware has been read in and is loaded in the
SintesoWorks, the elements still have to be assigned to the hardware via the
Assign function:
● 'FRT/FRD core' with 'FDnet line card (onboard/FCL2001)'
● 'FRT configuration group' with 'FRT channel' or
'FRD configuration group' with 'FRD channel'.
324 | 406
14
14.4.1.3 Setting views in the Person Machine Interface display
Figure 145: Detail editor of configuration group

In the detail editor of the configuration group, users can select between the normal
2-line view or the extended 4-line view.
Checkbox unchecked Normal 2-line view

Checkbox checked Extended 4-line view
Table 17: 'Display Extended message view' in detail editor
325 | 406
14.4.2 Visibility
Display
The 'Visibility' element can be used to determine which events can be shown in the
display for the floor repeater terminal (FRT) and ↑ floor repeater display (FRD).
The following selection is available:
● ↑ 'Site': ↑ Visibility for the entire 'Site'
● 'Site without areas': Visibility for all events from the Hardware tree of the 'Site'
● ↑ 'Station': Visibility for a 'Station' within the 'Site', with all ↑ areas in this
'Station'
'Station'
● 'Area': Visibility for one 'Area' within a control panel
● ↑ 'Section': Visibility for one 'Section' within a control panel
● 'Zone': Visibility for one 'Zone' within a control panel
This can be restricted further, so that for example only the alarm and fault event
categories are displayed instead of all events of an area.
Assigning 'Visibility'
2. Open ↑ 'Station' > 'FRT/FRD core' > 'FRT configuration group' or 'FRD
configuration group' in the tree view.
3. Highlight 'Visibility'.
a The event categories of 'Visibility' are displayed.
5. Select the event category and the corresponding 'Station', 'Area', 'Section', or
'Zone' element, and click on 'Assign'.
a 'Visibility' is assigned to the element.
Selecting element categories

One or more event categories can be selected in the detail editor of the assigned
elements.
Figure 146: 'Section' detail editor for selecting specific event categories
326 | 406
14
14.4.3 LEDs
The LEDs on the ↑ Person Machine Interface signal events and conditions. In
addition, the LEDs support the operator's orientation.
Figure 147: 'Programmable LED', 'Cause' detail editor

The following LEDs properties can be configured:
● Criterion that should activate the LED
● Color of the LED
● LED mode when LED is activated
The ↑ visibility must be configured on the corresponding category so that the LED
becomes active.
14.4.4 Function keys

Frequently used commands can be assigned to the function keys, e.g.:
Activate/Deactivate, Test, Configuration ('Set PS MANNED', 'Switch to
UNMANNED', etc.).
Assigning a function to the function keys

2. In the tree view, open ↑ 'Station' > 'FRT/FRD core' > in the example 'FRT
configuration group' > 'FRT' > 'Function keys'.
3. Highlight the corresponding 'Function key'.
1. In the window, select 'Commands 'Configuration'', for example, followed by a

function.
a The ↑ Detection tree is now shown. The elements that can be assigned are
highlighted.
2. Highlight e.g. 'Area', and click on 'Assign'.
a 'Function key' is assigned to 'Area'.
Assigning commands
Commands are assigned in the same way as with standard keys. You will find
more information on this in chapter 'Configuring standard keys and favorites
[➙ 303]'.
The ↑ visibility must be configured on the corresponding category so that the

function key becomes active.
327 | 406
14.4.5 Assigning the configurable keys and LEDs

Assigning the key ID to the key
The figure below shows the assignment of the key ID to the corresponding
configurable key on the ↑ Person Machine Interface of the ↑ floor repeater
terminal. The numbers correspond to the key ID.
1 4
2 5
3 6
Figure 148: Assigning the key ID to the key on the Person Machine Interface of the ↑ floor repeater
terminal
You will find the key ID in the detail editor of the key in the 'Key ID' field.
Figure 149: Detail editor of a key with details of the key ID
328 | 406
14
Assigning the LED ID to the LED

The figures below show the assignment of the LED ID to the corresponding
configurable LED on the ↑ Person Machine Interface of the ↑ floor repeater
terminal and ↑ floor repeater display. The numbers correspond to the LED ID.
1 4
2 5
3 6
Figure 150: Assigning the LED ID to the LED on the ↑ Person Machine Interface of the ↑ floor repeater
terminal
Figure 151: Assigning the LED ID to the LED on the Person Machine Interface of the ↑ floor repeater
display
You will find the LED ID in the detail editor of the LED in the 'LED ID' field.
Figure 152: Detail editor of a LED with details of the LED ID
329 | 406
14 LED indicator FTO2002 and mimic display driver FT2001
14.5 LED indicator FTO2002 and mimic display driver

FT2001
You will find details on the technical term ↑ 'FDnet' in the chapter 'Glossary'.
The following devices can be used as a mimic display:

● LED indicator FTO2002: For installation in the control panel. This contains 24
LED groups with one red and one yellow LED each.
● Mimic display driver FT2001: It controls up to 48 LEDs that are installed on a
ground plan panel. Communication is via the FDnet.
The mimic display driver has the following inputs and outputs:
– Two control outputs for local buzzer and LED 'SystemOn'
– Two inputs for 'Silence buzzer' and 'START LED test'
There are two elements for creating the mimic display in the 'Operation' task card:
● 'LED ind./mimic 24 LED groups'
With the 'LED ind./mimic 24 LED groups' element, the ↑ visibility of each LED
group (red/yellow) can be configured for a ↑ 'Section' or a 'Zone'.
● 'LED ind./mimic 48 LEDs'
Each LED can assign any event to the 'LED ind./mimic 48 LEDs' element.
Both elements must be created.
↑ Pre-configuration
To create the mimic display, proceed as follows:
2. Create the 'Station' element, for example, for the 'LED ind./mimic 48 LEDs'.
Link [➙ 77]
In a later step once the hardware has been read in and is loaded in SintesoWorks,
the hardware must still be assigned via the Assign function.
330 | 406
LED indicator FTO2002 and mimic display driver FT2001
14
When the hardware has already been read in

To create and assign the mimic display, proceed as follows:
2. Highlight the ↑ 'Station' in the tree view.
4. Highlight 'LED ind./mimic 48 LEDs', for example.

5. In the ↑ hardware tree, select the corresponding 'LEDs' (LED indicator
FTO2002) or 'LEDs/outputs' (FT2001) element.
a The mimic display is created and assigned to the hardware.
14.5.1 Element 'LED ind./mimic 24 LED groups'

Assigning events
Figure 153: Window 'Assign dialog' for assigning a 'Visibility' of the element 'LED ind./mimic 24 LED
groups' to an event
To assign the 'LED ind./mimic 24 LED groups' element to an event, proceed as
follows:
2. Open 'LED ind./mimic 24 LED groups' in the tree view.
3. Highlight a 'Visibility' element.
4. 'LED ind./mimic 24 LED groups' is highlighted at the left of the window.
5. In the ↑ 'Detection tree', select the ↑ 'Section' or the 'Zone'.
331 | 406
a The 'Visibility' element of 'LED ind./mimic 24 LED groups' is assigned to the
↑ section or ↑ zone.
7. Repeat these steps for each 'Visibility' element (each 'Visibility' element
corresponds to one of the 24 LED groups, from top to bottom).
Setting properties
Figure 154: Detail editor 'LED ind./mimic 24 LED groups', 'Overview'

● 'LED mode': Defines which states of the reference elements are indicated by
the LED of an LED group.
Alarm and fault:
– Red LED: Alarm (activation in Fire/Evac controls) -> LED permanently on.
– Yellow LED: Fault -> LED intermittent
Alarm, fault and off:
– Red LED: Alarm (activation in Fire/Evac controls) -> LED permanently on.
– Yellow LED: Fault -> LED intermittent, Off -> LED permanently on.
The criterion is met when at least one event of the corresponding event
category occurs in the referenced element or in its subtree.
● 'Supply supervision enabled': Defines whether a local supply is present which
is to be monitored.
332 | 406
LED indicator FTO2002 and mimic display driver FT2001
14
14.5.2 Element 'LED ind./mimic 48 LEDs'

Assigning events
Figure 155: 'New cause dialog' window for assigning a 'Visibility' of the 'LED ind./mimic 48 LEDs' to an
event
To assign the 'LED ind./mimic 48 LEDs' element to an event, proceed as follows:
2. Open 'LED ind./mimic 48 LEDs' in the tree view.
3. Highlight a 'Visibility' element.
4. In the 'Assign dialog' window, highlight an event category, e.g., 'All technical
messages'.
5. Select an element from the tree you want, e.g., 'Technical zone' from the
↑ Detection tree.
a The 'Visibility' element of 'LED ind./mimic 48 LEDs' is assigned to the event
category.
7. Repeat these steps for each 'Visibility' element (each 'Visibility' element
corresponds to one of the 48 LEDs, from top to bottom).
333 | 406
Setting properties
Figure 156: 'LED ind./mimic 48 LEDs', 'Overview' detail editor

● 'Supply supervision enabled': Defines whether a local supply is present which
is to be monitored.
Figure 157: 'Visibility', 'Overview' detail editor

In the detail editor of the 'Visibility' element, the following properties can be set:
● 'LED mode': Defines the mode of the LED in active or inactive status,
respectively.
● 'Threshold': Defines how many events from the defined event category need to
be active at the same time in the assigned element or its subtree for the cause
to be considered active by the control.
● 'ACTIVE if no communication to source': Defines the cause's default status
(active or quiet) should communication be interrupted to the ↑ station where
the referenced element is stored.
334 | 406
Event printer
14
14.5.3 Configuring mimic display driver FT2001
Figure 158: 'LEDs/outputs' detail editor

In the detail editor the following properties can be set:
● 'Suppress LED test, connector 1', 'Suppress LED test, connector 2'
Blocks the triggering of an LED test of the outputs on connection 1 or 2 via the
local input.
● 'Output mode, connector 1', 'Output mode, connector 2'
Active mode of outputs connected to connection 1 or 2:
– 'LEDs, bright mode'
– 'LEDs, dimmed mode'
– 'Relays'
See also
2 Element 'LED ind./mimic 48 LEDs' [➙ 333]
14.6 Event printer

The event printer logs all ↑ site events from its configured ↑ visibility.
An internal or external event printer is connected to a ↑ 'Station' via the RS232 and
RS845 interfaces. These interfaces are read in when the Station is powered up.
You will find a description of the commissioning of the external Fujitsu DL3750+
printer in document A6V10224853. See chapter 'Applicable documents'.
Depending on the printer used, the following elements must be created in the
'Operation' task card and assigned to the hardware:
● 'Built-in printer'
● 'External printer'
Pre-configuring element printer

To create the 'Built-in printer'/'External printer' element, proceed as follows:
1. Select 'Operation' > ↑ 'Station' in the task card, along with the interface to
which the printer is connected.
2. Create the 'Station' or 'Built-in printer' element for the 'External printer'.
Link [➙ 77]
Once the hardware has been read in and is loaded to SintesoWorks, the element
has to be assigned to the hardware using the Assign function.
335 | 406
14 Event printer
Hardware is already read in
Figure 159: 'Assign dialog' window for creating and assigning the 'Built-in printer' or 'External printer'
element
To create the 'Built-in printer'/'External printer' element and assign it to the
hardware, proceed as follows:
2. In the tree view, highlight the ↑ 'Station' with the interface to which the printer is
connected.
4. In the 'Assign dialog' window, select 'Built-in printer'/'External printer'.
a In the Hardware tree, the 'RS232 module (FCA2001)'/'Ethernet interface'
element is highlighted under 'RS232 printer'/'Ethernet printer'.
5. Highlight the element and click on 'Assign'.
a The element is created and assigned to the hardware.
336 | 406
Event printer
14
↑ Visibility configuration
The visibility that the event printer logs is defined in the 'Visibility' element.
The following selection is available:
● 'Site': Visibility for the entire ↑ site.
● 'Site without areas': Visibility for all events from the 'Hardware tree' of the site.
● 'Station': Visibility for one 'Station' within the site, with all ↑ areas in this
'Station'
'Station'.
● 'Area': Visibility on an area within a control panel
Figure 160: 'Assign dialog' window for assigning the ↑ visibility

To configure the visibility, proceed as follows:
2. In the tree view, open 'Built-in printer'/'External printer' and highlight 'Visibility'.
a 'Visibility' list and the 'Hardware tree' or ↑ detection tree are displayed.
4. Select the site, station, or ↑ area and click on 'Assign' (you can assign the
visibility to several elements).
a 'Visibility' is assigned to the corresponding element.
337 | 406
14 Fire brigade periphery [DE]
14.7 Fire brigade periphery [DE]

The fire brigade periphery comprises the following devices:
● FBF: Fire brigade operating panel
● FSD: Fire brigade key depot
● FAT: Fire brigade indication panel
● FAT with FBF: Fire brigade indication panel with fire brigade operating panel
● FSE: Releasing element link [➙ 215]
The devices are connected as follows:
● FSD is assigned to the fire brigade periphery module FCI2001.
● FBF can either be connected via the fire brigade periphery module FCI2001 or
an RS485 interface.
● FAT and FAT with FBF are connected to the ↑ 'Station' via an RS485 serial
interface.
To configure the devices, the logical element must be created in the 'Operation'
task card and assigned to the corresponding hardware element.
↑ Pre-configuration
To create the logical element, proceed as follows:
2. Create the FBF, FSD, FAT, or FAT with FBF element for the 'Station'.
Link [➙ 77]
3. Enter the customer text(s).
In a later step, once the hardware has been read in and is loaded in the
SintesoWorks, the element still has to be assigned to the hardware via the Assign
function.
338 | 406
Fire brigade periphery [DE]
14
When the hardware has already been read in
Figure 161: 'Assign dialog' window for creating and assigning the logical element
To create the device logical element and assign it to the fire brigade periphery
module, proceed as follows:
4. Select the corresponding element (FBF, FSD, FAT, FAT with FBF) in the list.
a The 'Hardware tree' is shown.
5. Highlight the relevant element in 'Fire brig. periphery interf. (FCI2001)'.
a The element is created and assigned to the hardware.
339 | 406
Connecting with RS485
Figure 162: 'Assign dialog' window for creating and assigning to the RS485 interface
To create the logical FBF or FAT element and to assign it to the RS485 module
(FCA2002) element, proceed as follows:
4. Select the corresponding element (FBF or FBF) in the list.
a The 'Hardware tree' is shown.
5. Highlight a 'UFP' element in 'RS485 module (FCA2002)'.
a The element is created and assigned to the RS485 module (FCA2002).
Configuring ↑ visibility
The following visibilities can be configured:
● Fire brigade operating panel FBF:
– Visibility on the remote transmission control FIRE
– Visibility on the extinguishing controls
– Visibility:
'Site': Visibility for the entire ↑ site.
'Area': Visibility for one ↑ area within a control panel.
'Station': Visibility for one 'Station' within the site, with all areas in this
'Station'.
● Fire brigade key depot FSD:
– Visibility on the remote transmission control FIRE
340 | 406
14
● Fire brigade indication panel FAT:

– Visibility:
'Site': Visibility for the entire ↑ site.
'Site without areas': Visibility for all events from the Hardware tree of the
site.
'Station': Visibility for one 'Station' within the site, with all areas in this
'Station'.
'Station without areas': Visibility for all events from the 'Hardware tree' of
the 'Station'.
'Area': Visibility on an area within a control panel
● Fire brigade indication panel FAT with fire brigade operating panel FBF:
– Same visibilities as FAT and/or FBF
The visibilities for 'Site', 'Area', and 'Station' can be restricted further so that, for
example, only the alarm and fault event categories are displayed instead of all
events for an area.
Figure 163: Configuring ↑ visibility of logical elements

To configure the visibility, proceed as follows:
2. In the tree view, open the element to be configured, e.g. 'FBF'.
3. Highlight the control 'Visible Extinguishing zones,' for example.
a 'Visible Extinguishing zones' is highlighted.
5. Select the corresponding element in the ↑ control tree and click on 'Assign'.
a 'Visible Extinguishing zones' is assigned to the selected element.
Figure 164: 'FBF' detail editor for selecting certain event categories
elements.
341 | 406
Operation of the fire brigade key depot (FSD)
Figure 165: 'FSD', 'Hardware' detail editor

In the 'FSD' detail editor, there are special settings for the fire brigade key depot
Hardware if the checkbox in the 'Operated' field is checked:
● 'Release mode'. You can select when the fire brigade key depot is to be
unlocked:
– 'RT active/confirmed'
– 'Fire alarm or Gas alarm and RT active/confirmed'
– 'RT active/confirmed or RT active/unexpected'
● 'Released by Sabotage ALARM': If the box contains a checkmark, the fire
brigade key depot is also unlocked by a sabotage alarm.
The sabotage alarm is activated by a door contact fitted in the 'Station'. For
service purposes, the function can be switched off at the ↑ Person Machine
Interface before the 'Station' is opened.
● 'Sabotage contact active upon 'FSD Sabotage'': If the checkmark is placed, the
specific output for notification of an intrusion panel is activated in the event of
an FSD sabotage message.
14.7.1 Key depot adapter FCI2019

Creating a key depot adapter
1. Select > 'FC2080' or 'FG2020' in the 'Operation' task card.
2. Create the 'Key safe adapter' element for 'FC2080' or 'FG2020'. Link [➙ 77]
Sub-elements of the key depot adapter

The 'Key safe adapter' element has the following sub-elements:
● 'Visibility': ↑ Visibility of the key safe adapter. The visibility must be assigned to
the 'RT fire control' control.
● 'Sabotage input': This input is activated if the key depot adapter was sabotaged
or the lid of the key depot adapter was opened.
● 'RT fire active': This output is activated if the assigned 'RT fire control' control
was activated, but the activation has not yet been acknowledged.
● 'RT fire active/confirmed': This output is activated if the assigned 'RT fire
control' control was activated, and the activation was acknowledged.
● 'Heating activation': Output for the activation of the heating unit of a key depot
adapter.
342 | 406
14
Setting properties of the key safe adapter
Figure 166: Properties of the key depot adapter

'Release mode':
This setting specifies under which conditions the fire brigade key depot is
unlocked.
'Released by Sabotage ALARM':
This setting specifies if the fire brigade key depot is additionally unlocked by a
sabotage alarm. The sabotage alarm is triggered by a door contact built into the
↑ 'Station'. For service purposes, the function can be switched off at the ↑ Person
Machine Interface before the 'Station' is opened.
Assigning the key depot adapter

1. Open the 'Key safe adapter' element in the structure tree.
2. Highlight 'Visibility' and assign the visibility of the key depot adapter to 'RT fire
control'.
3. Highlight the inputs and outputs and assign them to the corresponding
input/output in the 'Hardware' task card.
343 | 406
14 ESPA 4.4.4 interface (pager)
14.8 ESPA 4.4.4 interface (pager)

The ESPA 4.4.4 interface is used for transmitting event messages from the fire
detection installation to Pager, telephone systems, light signaling systems and
other trades. The ESPA 4.4.4 interface can be obtained from suppliers.
To configure the ESPA 4.4.4 interface the 'Operation' element must be created in
the 'Pager' task card and assigned to the hardware. The ↑ visibility for events on
the ↑ site, the ↑ area, or the ↑ Station can be assigned to the 'Pager' element.
Creating ESPA 4.4.4 interface and assigning to hardware

To create the 'Pager' element, proceed as follows:
1. Select > ↑ 'Station' in the 'Operation' task card.
2. Create the 'Pager' element for the 'Station'. Link [➙ 77]
3. Enter the customer text.
To assign the 'Pager' element to the 'UFP' RS485 channel, proceed as follows:
1. Highlight the 'Pager' element in the tree view.
2. Open the 'Assign dialog' window and highlight 'Pager'.
a The Hardware tree is shown. The elements that can be assigned are
highlighted.
3. Select a 'UFP' element and click on 'Assign'.
a 'Pager' is assigned to 'UFP'.
344 | 406
ESPA 4.4.4 interface (pager)
14
↑ Visibility
The following visibilities can be assigned using the Assign function:
● 'Site': Visibility for ↑ site events.
● 'Site without areas': Visibility for events from the Hardware tree of the site.
● 'Station': Visibility for Station events.
● 'Station without areas': Visibility for events from the Hardware tree of the
↑ Station.
● 'Area': Visibility for the ↑ areas.
To assign the visibility, proceed as follows:
1. In the tree view, open 'Pager' and highlight 'Visibility'.
a 'Visibility' list and Hardware tree or ↑ Detection tree are displayed.

3. Select the site, Assign dialog or Station in the 'Area' window and click on
'Assign' (you can assign the visibility on several elements).
a 'Visibility' is assigned to the corresponding element.
elements (remove checkmark from 'ALL event categories visible').
Figure 167: Detail editor 'Station', 'Overview', selection of event categories
345 | 406
14 EVAC panel [NL]
14.9 EVAC panel [NL]

The EVAC panel is an operating and indication unit for manual evacuation control,
integrated in the ↑ Person Machine Interface of the control panel or remotely
connected via an RS485 interface. The EVAC panel consists of a master and up to
four slaves. Master and slave both have up to ten indicators for the evacuation
zones. Both the universal and two-stage evacuation control are suited to automatic
evacuation.
Creating 'Evac panel'

2. Create the 'Evac panel' element for the 'Station'. Link [➙ 77]
a The 'Evac panel' element is created along with the 'Evac master' element.
Assigning the 'Evac master' to the hardware

1. Highlight the 'Evac master' element in the tree view.
a The hardware tree is depicted. The 'Evac master unit (FTO2007)' element
that can be assigned is highlighted in the 'Channel' element.
a 'Evac master' is assigned to 'Channel'.
Setting the properties of the 'Evac master' element
● 'Buzzer silenced by FS20 operating terminal': Defines whether silencing the

buzzer on the FS20 operating terminal also silences the buzzer of the Evac
panel.
● 'Access level of keys 'Start'/'Stop'': Defines the access level required to execute
the functions of the 'Start' and 'Stop' keys.
346 | 406
EVAC panel [NL]
14
Creating 'Evac slave'

1. Select 'Operation' > 'Evac panel' in the task card.
2. Create the 'Evac panel' element for 'Evac slave'. Link [➙ 77]
Assigning the 'Evac slave' to the hardware

1. In the tree view, highlight the 'Evac slave' element that you have just created.
a The ↑ hardware tree is depicted. The 'Evac slave unit (FTO2007)' element
that can be assigned is highlighted in the 'Channel' element.
a 'Evac slave' is assigned to 'Channel'.
Assigning EVAC panel with evac control

To assign an 'Evac zone' element with the evac control, proceed as follows:
1. In the tree view, highlight an 'Evac zone' element in 'Evac master' or 'Evac
slave'.
a The ↑ control tree is depicted. The 'Universal evac control'/'Phased evac

control' elements that can be assigned are highlighted.
a 'Evac zone' is assigned to 'Universal evac control' or 'Phased evac control'.
4. Repeat these steps for each 'Evac zone' element (each 'Evac zone' element
corresponds to one of the ten evacuation zones, from top to bottom).
347 | 406
14 Alarming equipment (UGA) [FR]
14.10 Alarming equipment (UGA) [FR]

The alarming equipment (UGA) is an operating and indication unit for four alarm
zones. The unit has its own control for the ↑ alarm devices by alarm zone and its
own degraded mode behavior. The alarming equipment is linked to the control
panel via an RS485 interface. Up to four alarm zones can be configured for the
alarming equipment.
Configuring alarming equipment (UGA)
pages.
1. Create the 'UGA' and 'UGA alarm zone' elements. Link [➙ 348]
2. Assign the 'UGA' element to the RS485 module. Link [➙ 349]
3. Configure the ↑ visibility. Link [➙ 350]
4. Configure the UGA master-slave principle. Link [➙ 351]
14.10.1 Creating the 'UGA' and 'UGA alarm zone' elements

2. Create the 'UGA' element for the 'Station'. Link [➙ 77]
3. Create the 'UGA' element for 'UGA alarm zone'.
348 | 406
Alarming equipment (UGA) [FR]
14
14.10.2 Assigning UGA to the RS485 module
Figure 168: Assigning 'UGA' element
w In 'Hardware tree' the 'RS485 module (FCA2002)' element is available.

2. Highlight the 'UGA' element in the tree view.
4. Select 'UGA' at the left in the window.
5. Open the RS485 module and select a 'UFP' element.
a 'UFP' is assigned to 'UGA'.
349 | 406
14 Alarming equipment (UGA) [FR]
14.10.3 Configuring visibility
Figure 169: Assigning a ↑ visibility

2. In the tree view, open 'UGA alarm zone' element and highlight 'Visibility'.
a At the right in the window, the 'Detection tree' is displayed.
4. Select the ↑ visibility: 'Area', ↑ 'Section', or 'Zone'.
a The element is assigned with 'Visibility'.
350 | 406
Alarming equipment (UGA) [FR]
14
14.10.4 UGA Master-Slave principle

If 'UGA' 1 is connected to ↑ 'Station' 1, then 'Station' 2 which behaves like a remote
'UGA' 1 can be connected to 'UGA' 2. 'UGA' 2 displays the same information as
'UGA' 1 and carrying out an operation on 'UGA' 2 has the same effect as carrying
out an operation directly on 'UGA' 1.
Figure 170: Assigning the UGA slave alarm zone to the UGA master alarm zone
To assign the UGA slave alarm zone to the UGA master alarm zone, proceed as
follows:
2. In the tree view, open the second ↑ 'Station' and highlight '2:UGA'.
a 'Other UGA' is highlighted.
4. In the tree, open the first 'Station' and highlight '1:UGA alarm zone'.
a '2:UGA' is linked to '1: UGA alarm zone'.
351 | 406
14 CERLOOP gateway [FR]
14.11 CERLOOP gateway [FR]

The CERLOOP gateway can exclusively be used in France due to the special
situation with CERLOOP ring and STTs. The CERLOOP gateway is used for
sending alarm and presence messages to the participants (STT) in the CERLOOP
network. FS20-'Stations' are represented as CERLOOP participants with an
independent CERLOOP address. The telegrams are only sent in one direction via
an RS232 interface, i.e. from theFS20-'Station' to the communication module for
CERLOOP nodes K1H061.
NOTICE
Overvoltage
Device defect
● The RS232 module may only be inserted or removed when the ↑ 'Station' is
current-free.
Configuring the CERLOOP gateway
pages.
1. Create the 'RS232 module (FCA2001)' element. Link [➙ 352]

2. Create and assign the CERLOOP gateway. Link [➙ 353]
3. Configure the ↑ visibility of the CERLOOP gateway. Link [➙ 354]
4. Enter the CERLOOP group numbers. Link [➙ 355]
14.11.1 Creating RS232 module

1. In the task card, select 'Hardware' > ↑ 'Station' with the built-in RS232 module
> 'Communication interfaces'.
2. Create the 'Communication interfaces' element with the 'RS232 (FCA2001) /
CERLOOP' template for 'RS232 module (FCA2001)'. Link [➙ 77]
352 | 406
CERLOOP gateway [FR]
14
14.11.2 Creating and assigning the CERLOOP gateway
Figure 171: Creating and assigning the CERLOOP gateway

2. In the tree view, highlight the ↑ 'Station' with the RS232 module.
4. Highlight 'CERLOOP' at the left of the window.
5. Using 'RS232 module (FCA2001)' select the 'CERLOOP' element.
a The 'CERLOOP gateway' element is created and assigned to the hardware.
Setting the properties of the ↑ CERLOOP gateway
Figure 172: Properties in the detail editor of the CERLOOP Gateway
1. Select the 'CERLOOP gateway' element in the tree view.

2. Set the following properties in the detail editor:
– 'CERLOOP node address': Address of the CERLOOP node (K1H061), to
which the ↑ CERLOOP gateway is connected.
– 'Presence telegram interval': Interval for sending the presence message.
353 | 406
14 CERLOOP gateway [FR]
14.11.3 Configuring visibility

Assigning a ↑ visibility
You must configure the visibility of the CERLOOP gateway for all 'Stations', which
are defined as CERLOOP participants.
Figure 173: Assigning a visibility

2. In the tree view, open 'CERLOOP gateway' element and highlight 'Visibility'.
4. Select the 'Station' you want. You can assign several 'Stations' simultaneously.
a 'Visibility' is assigned to the 'Station'.
Setting CERLOOP address
Figure 174: CERLOOP address in detail editor of the assigned station
1. Highlight the assigned 'Station' in the tree view.

2. In the detail editor, in the 'CERLOOP address' field, set the CERLOOP address
of the 'Station'. Each 'Station' must have a unique address. In the Tooltip of the
'CERLOOP address' field, you will find the permitted addresses.
354 | 406
Key safe adapter [DE]
14
14.11.4 Entering CERLOOP group numbers

For each 'Zone' of a referenced 'Station' the CERLOOP group number must be
entered with the corresponding 'Zone' that should be shown in CERLOOP.
Figure 175: Detail editor of a 'Zone'

To configure the CERLOOP group number, proceed as follows for each 'Zone' to
be shown in CERLOOP:
2. In the tree view, open 'Area' > ↑ 'Section' and highlight 'Zone'.
3. Enter a number between 0 and 48700 in the 'Plan no.' field. This number
corresponds to the CERLOOP group number.
14.12 Key safe adapter [DE]

Creating 'Key safe adapter'
2. Create the 'Key safe adapter' element for the desired station, e.g., using the
context menu.
355 | 406
14 Key safe adapter [DE]
Assigning 'Key safe adapter'

w An FCI2008 with an available input 1 or an FDCIO222/224 with an available
input 11 is present in the hardware tree.
1. Assign the visibility of the 'Key safe adapter' to the desired element.
2. Use the 'Assign' function to assign the 'Sabotage input' as follows:
– When activating the 'Key safe adapter' via FCI2008: Assignment to input
I/O 1 of the FCI2008.
– Or
– When activating the 'Key safe adapter' via FDCIO222/224: Assignment to
input 11 of the FDCIO222/224.
3. Use the 'Assign' function to assign the 'Heating activation' as follows:
– When activating the 'Key safe adapter' via FCI2008: Assignment to output
I/O 4 of the FCI2008.
– When activating the 'Key safe adapter' via FDCIO222/224: Assignment to

output 23 of the FDCIO222/224.
a The 'Key safe adapter' is assigned.

a The 'RT fire active/confirmed' and 'RT fire active' elements do not need to be
assigned.
See also
2 Key safe adapter [DE]: Configuring controls [➙ 285]
2 Key safe adapter [DE]: Configuring the technical
zone [➙ 230]
2 Assigning LEDs [➙ 357]
356 | 406
Key safe adapter [DE]
14
14.12.1 Assigning LEDs

The 'LED 'Key depot unlocked'' must be configured in order to operate a key safe
adapter [DE]. To this end, a 'Technical zone' must be created and assigned. See
the chapter 'Key safe adapter [DE]: Configuring the technical zone [➙ 230]'. Then
the LEDs on the corresponding Person Machine Interfaces are assigned to the
'Technical zone'.
Prerequisite
● The key safe adapter has been created and assigned. See the chapter 'Key
safe adapter [DE] [➙ 355]'.
● The controls for the key safe adapter have been created and assigned. See the
chapter 'Key safe adapter [DE]: Configuring controls [➙ 285]'.
● The 'Technical zone' has been created and assigned. See the chapter 'Key
safe adapter [DE]: Configuring the technical zone [➙ 230]'.
357 | 406
14 Key safe adapter [DE]
Assigning the 'Key depot unlocked' LED

1. In the 'Operation' task card, select the Person Machine Interface on which you
want to configure the 'LED 'Key depot unlocked''.
2. Edit the customer text for the LED, e.g., 'Key depot unlocked'.
3. Create a cause for the LED, e.g., using the context menu.
4. Select the 'LED 'Key depot unlocked'' element as the 'Event filter' on the
'Overview' tab.
5. Select the 'Key depot unlocked' LED and assign it as follows using the 'Assign'
function:
– Select the 'All technical messages' element under 'Events 'Technical
message'' in 'Manual type selection' on the left-hand side of the 'New cause
dialog'.
– Select 'Technical zone | Key depot unlocked' in the detection tree on the
right-hand side
6. Perform steps 1 to 5 for all Person Machine Interfaces on which you want to
configure an 'LED 'Key depot unlocked''.
358 | 406
'Network' task card
Network parameters
15
15 'Network' task card

Configure the network settings for the fire detection system in the 'Network' task
card.
You will find all permissible networking types and the required network settings
described in detail in document '008843'.
You will find pre-conditions for configuration and the required work steps in
document '009052'. See chapter 'Applicable documents'.
The following chapter describes the corresponding configuration in SintesoWorks.
See also
15.1 Network parameters
You will find details of the ports in FS20 in document 009052. See chapter
15.2 Network configuration
15.2.1 Creating networked 'Stations'

Networked ↑ 'Stations' must be assigned to the 'Ethernet' or 'SAFEDLINK' sub-net:
'New station'' window, 'Ethernet station' or 'SAFEDLINK station' option.
In the 'Network' task card, references for 'Stations' are automatically created under
the 'Global system configuration' > 'FS20 network configuration' > 'Ethernet sub-
net' elements.
IP addresses for Ethernet and ↑ router stations

IP addresses ranging from 192.168.200.0…192.168.200.255 to
192.168.255.0…192.168.255.255 are reserved in FS20 can cannot be used.
↑ Ethernet 'Stations'
The 'Fx20xx/Ethernet' references for all Ethernet 'Stations' can be found in the
'Connections' element under 'Ethernet sub-net'.
359 | 406
'Network' task card
15 Network configuration
↑ SAFEDLINK 'Stations'
The 'SAFEDLINK sub-net' element is automatically created under 'Ethernet sub-
net'. The 'Fx20xx/SAFEDLINK' references for all SAFEDLINK 'Stations' can be
found in the 'Connections' element underneath it.
If the SAFEDLINK 'Stations' are split into several sub-nets, more 'SAFEDLINK sub-
net' elements can be created using the 'New element' function.
The 'Fx20xx/SAFEDLINK' references can then be moved to the various sub-nets
using the 'Drag and drop', 'Cut' and 'Paste' or 'Unassign' and 'Assign' functions.
If you create a ↑ standalone 'Station' and then expand the ↑ 'Site' with 'Stations',
the standalone 'Station' automatically adopts the network settings of the first
'Station' added.
360 | 406
'Network' task card
Network configuration
15
15.2.2 Configuring a 'Station' as a router station

A ↑ SAFEDLINK station is configured as a ↑ router station. The router station
connects the 'SAFEDLINK sub-net' with the 'Ethernet sub-net'.
The router station is created by assigning the 'Functions' element to the
'Fx20xx/SAFEDLINK' reference.
The ↑ router station provides access to the private addresses of 'SAFEDLINK

sub-net'. The Ethernet participants must therefore recognize the router station as
being the ↑ gateway of the route to the 'SAFEDLINK sub-net'.
'Assign dialog' window to define the ↑ router station

Proceed as follows to define the 'Router' or 'Standby router':
1. Open the 'Global system configuration' > 'FS20 network configuration'>
'Ethernet sub-net' > 'SAFEDLINK sub-net' elements in the tree view of the
'Network' task card.
2. Highlight 'Functions' and open the 'Assign dialog' window.
3. Select 'Router' or 'Standby router' from the list and the reference for the
'Station' you want from the tree.
a The 'Station' is configured as a router station or ↑ standby router station.

361 | 406
'Network' task card
15.2.3 Configuring a 'Station' as GAP
If a ↑ SAFEDLINK Station is configured as ↑ 'GAP' or 'Secondary GAP', it must

also be configured as a router or a standby router; otherwise, local or general
access via the Ethernet port will not be possible.
The GAP station is created by assigning the 'Functions' element to the

'Fx20xx/Ethernet' or 'Fx20xx/SAFEDLINK' reference.
Proceed as follows to configure the 'Station' as ↑ 'GAP' or 'Secondary GAP':

w 'Station' is configured as a ↑ router station or ↑ Ethernet station.
1. Open the 'Global system configuration' > 'FS20 network configuration' >
'Ethernet sub-net' elements in the tree view of the 'Network' task card.
2. Highlight 'Functions' and open the 'Assign dialog' window.
3. Select 'GAP' or 'Secondary GAP' from the list and the reference for the 'Station'
you want from the tree.
a The 'Station' is defined as 'GAP' or 'Secondary GAP'.
362 | 406
'Network' task card
15
15.2.4 Configuring GAP with DHCP server
NOTICE
↑ GAP with DHCP server on public network
Devices on the public network have incorrect IP addresses.
● A GAP must only be configured on private networks with a DHCP server.
A ↑ GAP can be configured with a DHCP server. This results in a PC automatically

receiving an IP address when a connection is established to the GAP via
FCnet/LAN.
w The ↑ 'Station' is configured as ↑ GAP.

1. Open the 'Global system configuration' > 'FS20 network configuration' >
'Ethernet sub-net' > 'Functions' elements in the tree view of the 'Network' task
card.
2. Highlight the 'Station'.
3. Check the 'DHCP server enabled' checkbox on the 'Overview' tab of the detail
editor.
a The 'Station' is configured with DHCP server.
363 | 406
'Network' task card
15.2.5 Manual allocation of addresses in the sub-nets

If the 'Ethernet sub-net' is incorporated in an existing IT infrastructure, the settings
for the sub-net mask and IP address must be made manually following the IT
administrator's instruction.

'Ethernet sub-net'
Configure the 'Ethernet sub-net' as follows:
1. Open the 'Network' > 'Global system configuration' elements in the tree view of
the 'FS20 network configuration' task card.
2. Highlight 'Ethernet sub-net'.
3. Enter the network mask (4 groups of digits, separated by dots) in the 'Netmask'
field.
4. Open 'Ethernet sub-net' > 'Connections' in the tree view.
5. Highlight all 'Fx20xx/Ethernet' one after the other.
6. Enter the IP address in the 'Overview' tab of the detail editor.
364 | 406
'Network' task card
15
'SAFEDLINK sub-net'
1. Open the 'Network' > 'Global system configuration' > 'FS20 network
configuration' elements in the tree view of the 'Ethernet sub-net' task card.
2. Highlight 'SAFEDLINK sub-net'.
3. Enter the network mask (4 groups of digits, separated by dots) in the 'Netmask'
field.
4. Open 'SAFEDLINK sub-net' > 'Connections' in the tree view.
5. Highlight all 'Fx20xx/SAFEDLINK one after the other.
6. Enter the IP address in the 'Overview' tab of the detail editor.
See also
2 Setting network speed for SAFEDLINK [➙ 368]
365 | 406
'Network' task card
15.2.6 Entering routes for external access to extended networks

via GAP
In order that a PC or a ↑ management station from an external network has access
to all ↑ 'Stations' in the extended network via router and ↑ GAP, routes must be
entered in the GAP and in the Ethernet sub-net.
Although all network addresses in this chapter are examples, they are consistent.
Function of the route in the ↑ GAP

The route in the GAP is required for the following situations:
There is a 'Security module (firewall) FN2009-A1' router between the extended
network in the fire detection system and the external network.
● 'Destination address' of the route is 'SintesoWorks' and/or the management
stations
● ↑ 'Gateway' is the FS20 address of the 'Security module (firewall) FN2009-A1'
router
Function of the route in the Ethernet sub-net

The route in the Ethernet sub-net is required for the following situations:
The extended network in the fire detection system has a standby router.
There is a 'Security module (firewall) FN2009-A1' router between the extended
network in the fire detection system and the external network.
● 'Destination address' of the route is 'SintesoWorks' and/or the management
stations
● ↑ 'Gateway' is the Ethernet address of the GAP
Additional conditions for access

● GAP must be connected to 'FCnet/LAN'.
● 'Security module (firewall) FN2009-A1' must be configured.
366 | 406
'Network' task card
15
Entering the route in the ↑ GAP

● Route via 'Security module (firewall) FN2009-A1' to 'Destination address'
– 'Destination address': 10.169.29.0
– 'Netmask': 255.255.255.0
– ↑ 'Gateway': Internal IP address of the 'Security module (firewall) FN2009-
A1' – 192.168.100.10
Enter the routes in the GAP as follows:
1. Select the 'Network' task card.
2. Open 'Global system configuration' > 'FS20 network configuration' > 'Ethernet
sub-net' > 'Functions' > 'GAP' in the structure tree.
3. Highlight 'Routes'.
4. Enter the network data.
Figure 176: Route in the GAP
Entering route in the Ethernet sub-net

● Route via GAP to 'Destination address' PC/management station
– 'Destination address': 10.169.29.0
– 'Netmask': 255.255.255.0
– ↑ 'Gateway': Ethernet address of the GAP – 192.168.100.1
Enter the routes in the Ethernet sub-net as follows:
1. Select the 'Network' task card.
2. Open 'Global system configuration' > 'FS20 network configuration' > 'Ethernet
sub-net' in the structure tree.
3. Highlight 'Routes'.
4. Enter the network data.
Figure 177: Route in the Ethernet sub-net
367 | 406
'Network' task card
15.2.7 Setting network speed for SAFEDLINK

The network speed is set to the 'Standard' setting for high cable quality. If using
lower cable quality or if problems arise with long cables, the 'Low' speed must be
set.
Figure 178: 'SAFEDLINK sub-net' detail editor

To set the network speed, proceed as follows:
1. Open the 'Network' > 'Global system configuration' > 'FS20 network
configuration' elements in the tree view of the 'Ethernet sub-net' task card.
2. Highlight 'SAFEDLINK sub-net'.
3. Select setting 'Network speed' for 'Low' in the detail editor.
a The network speed is set for low cable qualities.
15.2.8 Configuring remote access with two GAPs
pages.
1. Configure one ↑ 'Station' as 'GAP' and one 'Station' as 'Secondary GAP'.

Link [➙ 362]
2. Configure the ↑ GAP 'Station' with DHCP server. Link [➙ 363]
3. In 'GAP', create a 'Route' element and enter the following values. Link [➙ 366]
– 'Destination address': Sub-net of ↑ management station A – 10.169.29.0
– 'Netmask': 255.255.255.0
– ↑ 'Gateway': Address of 'Security module (firewall)' A – 192.168.100.10
4. In 'Secondary GAP', create a 'Route' element and enter the following values.
– 'Destination address': Sub-net of management station B – 10.169.30.0
– 'Netmask': 255.255.255.0
– 'Gateway': Address of 'Security module (firewall)' B – 192.168.100.11
368 | 406
'Network' task card
15
5. In 'Ethernet sub-net', create two 'Route' elements.

6. Enter the following values in the first Route' element. Link [➙ 366]
– 'Destination address': Sub-net of management station A – 10.169.29.0
– 'Netmask': 255.255.255.0
– 'Gateway': Address of 'GAP' – 192.168.100.1
7. Enter the following values in the second Route' element:

– 'Destination address': Sub-net of management station B – 10.169.30.0
– 'Netmask': 255.255.255.0
– 'Gateway': Address of 'Secondary GAP' – 192.168.100.2
You will find more information about remote access with two ↑ GAPs in document
See also
369 | 406
'Network' task card
15.2.9 Configuring remote access via cRSP

To configure remote access via the 'common Remote Service Platform' (cRSP)
remote maintenance platform, you must request the following values from your
cRSP contact:
● 'Destination address'
● 'Netmask'
● ↑ 'Gateway'
You will find more information about remote access via cRSP in document
Configuring remote access via cRSP

1. Configure one ↑ 'Station' as ↑ 'GAP' or 'Secondary GAP'. Link [➙ 362]
2. In 'GAP' or 'Secondary GAP', create a 'Route' element.
3. In the 'Route' element, enter the values for 'Destination address', 'Netmask',
and ↑ 'Gateway'. You will get the values from your cRSP contact.
4. In 'Ethernet sub-net' create a 'Route' element.

5. In the 'Route' element, enter the values for 'Destination address' and 'Netmask'.
You will get the values from your cRSP contact.
– Enter the Ethernet address of the GAP as the value of ↑ 'Gateway'.
You will find information on entering routes in chapter 'Entering routes for external
access to extended networks via GAP [➙ 366]'.
Establishing connection
1. Log in on the cRSP website.
2. Establish the FS20 connection to your ↑ 'Site' (VPN tunnel).
3. Select the 'Connection to IP address' option in the 'Connect' window.
4. Enter 'localhost' or '127.0.0.1'.
5. Click on 'OK'.
370 | 406
'Network' task card
15
15.2.10 Configuring redundancy management

In the 'Redundancy management configuration' element, you can configure
redundancy management for Ethernet networks that have several Ethernet
switches (modular) FN2012 [➙ 171].
You will find the 'Redundancy management configuration'' element in the 'Network'
> 'Global system configuration' > 'FS20 network configuration' > 'Ethernet sub-net'
task card.
For the 'Redundancy management configuration', the 'Type of redundancy

configuration' can be configured manually on the 'Overview' tab.
You cannot make any manual configuration settings if you opt for the 'Automatic'
configuration.
The 'Loop wired network' configuration requires you to configure the 'Redundancy
manager' manually.
The 'Stub wired network' configuration requires you to manually configure the
suppression of ring and port faults for the external ports.
The following chapters describe the various configuration types for 'Redundancy
management configuration'.
371 | 406
'Network' task card
15.2.10.1 Automatic configuration
For automatic configuration, the value 'Automatic' is set in the 'Type of redundancy
configuration' field.
Automatic configuration for 'Redundancy management configuration' is the default
configuration for a ↑ 'Site'. You cannot make any manual configuration settings if
you opt for automatic configuration.
In an automatically configured Ethernet network with several 'Stations', an FN2012
has the function of the 'Redundancy manager' allocated to it by the system. The
'Redundancy manager' is defined automatically in the Ethernet network. Ring faults
and port faults are not suppressed.
If a ↑ 'Site' only has one 'Station' or if the 'Station' is not linked to any other
'Station' via an Ethernet network, ring faults and port faults are suppressed
automatically.
Automatic configuration cannot be used if the fire detection system is configured

with a 'Stub wired network'. Manual configuration is required for a 'Stub wired
network'.
372 | 406
'Network' task card
15
15.2.10.2 Configuring stub wiring
To configure a 'Stub wired network' Ethernet network, you have to set 'Stub wired
network' in the 'Type of redundancy configuration' field.
When configuring the 'Stub wired network', you must suppress ring errors and port
errors for the ports located at the respective end of the stub. A 'Redundancy
manager' cannot be configured.
Configuring 'Stub wired network'
1. Highlight the 'Redundancy management configuration' element in the tree view

of the 'Network' task card.
2. Check the 'Suppress ring fault' checkbox.
a The suppression of ring faults is activated.
3. Select the 'Redundancy management configuration'.
4. Use the 'Assign' function to assign the 'Redundancy management
configuration' as follows:
– Select the 'Assign dialog' element on the left-hand side of the 'Ring port
fault suppression'.
– In the hardware tree on the right-hand side of the 'Assign dialog', select the
ports located at the end of the stub in each case.
– You must assign a 'Ring port fault suppression' to the corresponding port
twice for the 'Redundancy management configuration'.
a Suppression of port errors is activated for the ports at the respective end of the
stub.
a You have configured the 'Redundancy management configuration' for 'Stub
wired network'.
373 | 406
'Network' task card
15.2.10.3 Configuring loop wiring
The 'Loop wired network' must be configured manually if the function of the
'Redundancy manager' is to be allocated to a specific FN2012.
If the function of the 'Redundancy manager' does not have to be allocated to a

specific FN2012, the automatic configuration type can be used for the 'Loop wired
network'.
To configure a 'Loop wired network' Ethernet network with a manually configured

'Redundancy manager', you have to set 'Loop wired network' in the 'Type of
redundancy configuration' field.
Configuring 'Redundancy manager'
1. Highlight the 'Redundancy management configuration' element in the tree view

of the 'Network' task card.
2. Use the 'Assign' function to assign the 'Redundancy management
configuration' to an FN2012.
a You have configured a 'Redundancy manager'.
a You have assigned the function of the 'Redundancy manager' to an FN2012.
a You have configured the 'Redundancy management configuration' for 'Loop
wired network'.
374 | 406
'Network' task card
15
15.2.10.4 Site-specific configuration
For a customer-specific Ethernet network configuration, you have to set 'Type of

redundancy configuration' in the 'Site-specific'.
For the 'Site-specific' configuration, you can configure the following elements
manually:
● Suppression of ring faults
● 'Redundancy manager'
● Suppression of port faults
Proceed as described in the previous chapters to configure the individual elements.
375 | 406
'Network' task card
15 Establishing connection from PC to FS20 network
15.3 Establishing connection from PC to FS20 network
When the SintesoWorks is installed, the two routes in the table below are entered
in the PC's network settings.
Network address Network mask ↑ Gateway address Metric

192.168.0.0 255.255.0.0 192.168.200.1 10
192.168.0.0 255.255.0.0 192.168.201.1 10
Table 18: Persistent routes
A connection from the PC to the FS20 network can be established with the
following three variants:
● Local connection
– The PC is connected to the Ethernet connection of a ↑ standalone or
↑ SAFEDLINK station.
– The PC automatically receives an IP address.
● Connection to GAP
– The PC is connected to the 'FCnet/LAN'.
– The PC automatically receives an IP address when the DHCP is configured
on the GAP.
● Connection to IP address
– The PC is connected to the 'FCnet/LAN'.
– The PC's IP address must be set manually.
– If there are external routers between SintesoWorks and ↑ GAP, the
necessary routers must be configured for the FCnet/LAN and all
↑ SAFEDLINK sub-nets.
The connection can be established using the following menu items:

● For SintesoWorks
– 'Commissioning' > 'Download site'
– 'Commissioning' > 'Upload site'
– 'Commissioning' > 'Upload site event memory'
– 'Commissioning' > 'Upload site log files'
● For SintesoView
– 'SintesoView' > 'Connect'
The 'Connect' window is opened when a command is performed.
376 | 406
'Network' task card
Setting up a Maximum Transmission Unit (MTU)
15
15.4 Setting up a Maximum Transmission Unit (MTU)

The default setting for the MTU size is 1500 bytes. If a FW update fails, you can
set lower values and apply them optionally for the 'Connection to IP address'.
The defined MTU size must be applied for remote access via cRSP.
Set the MTU as shown below:
Figure 179: Maximum Transmission Unit (MTU)

This setting can be selected optionally for a 'Connection to IP address'.
Figure 180: Maximum Transmission Unit (MTU) 02
377 | 406
'Network' task card
15 Monitoring Ethernet switch (MM) and safety module (firewall)
15.5 Monitoring Ethernet switch (MM) and safety module

(firewall)
The 'Ethernet switch (MM) FN2008-A1' and 'Security module (firewall) FN2009-A1'
network elements must be monitored for faults in the Ethernet. To do this,
terminals F1 and F2 (fault) on the connector strip of the detector contact are
connected to a configurable input/output on the periphery board or an input/output
module.
The fault message is configured in the 'Technical zone' with the 'Fault network
device' template.
Create the fault message as follows:
1. Select 'Detection' > 'Detection area' > 'Section' in the task card.
2. Use the 'Fault network device' template to create the 'Section' element for the
'Technical zone'. Link [➙ 77]
The 'Technical zone' element must be assigned to the corresponding input.
Figure 181: 'Assign dialog' window to assign the 'Technical zone'
1. Highlight the 'Technical zone' element in the tree view.

a 'Input' is highlighted in the list.
3. Select the corresponding 'I/O' element and click on 'Assign'.
a The ↑ link is created.
See also
2 'Technical zone' [➙ 205]
378 | 406
'Network' task card
Connecting management stations via BACnet/Ethernet
15
15.6 Connecting management stations via

BACnet/Ethernet
↑ Management stations (↑ BACnet clients) are connected to FS20 via BACnet /
Ethernet.
● A BACnet client is connected to the FS20 sub-system via the Ethernet interface
of the Global Access Point (GAP).
● Every single ↑ 'Station' that is to communicate with the BACnet protocol must
be enabled with a ↑ license key. The license key must support the BACnet
function for management stations.
● SintesoWorks can export the FS20 configuration in SiB-X format so that a
BACnet client can import this data.
BACnet is a communication log and requires its own logical IDs (BACnet device ID)
for the 'Stations', so that each 'Station' is uniquely recognized as a BACnet
participant.
The 'BACnet device ID' is made up of two parts: the number for the 'BACnet
device object' and the instance number.
In 'SintesoWorks', the entry for a 'BACnet device ID' is always a decimal number
for the instance number. The ↑ area type is added internally.
Device IDs must be configured at the following points:

● 'BACnet client configuration': In the 'BACnet device ID' property
– The configuration is dependent on 'BACnet client'.
● 'BACnet device object': In the 'Address' property
– 'BACnet device ID' is managed by FS20.
15.6.1 Planning BACnet configuration

The following information is required for ↑ BACnet configuration:
● IP addresses for BACnet devices and ↑ GAP
● Unique BACnet device ID for each BACnet device
● There should be one BBMD (BACnet Broadcast Management Device) each per
sub-net, with one entry each for the other BBMDs and their IP addresses
379 | 406
'Network' task card
15 Global BACnet configuration
15.7 Global BACnet configuration
15.7.1 Configuring global BACnet settings

BACnet communication must be active for ↑ BACnet settings to be configured.
Activate BACnet communication as follows:
1. Open the 'Network' element in the tree view of the 'Global system configuration'
task card.
2. Highlight 'Global BACnet configuration'.
3. Check the 'Enable BACnet communication' checkbox on the 'Details' tab.
a BACnet communication is activated.
a More settings can be configured.
Figure 182: Global ↑ BACnet settings

The following values in the detail editor must match the settings of the
↑ management station:
The ↑ BACnet device ID consists of the 'Device' area type and the instance
number.
● 'Address range, lower limit' / 'Address range, upper limit':

Range for instance number values for identifying the FS20 stations in BACnet.
The address range is exported in SiB-X format.
● 'BACnet character set':
Character set that is used in the BACnet protocol for text strings. FS20
functions internally with Unicode in UTF-8 format.
Selectable character sets:
– UCS-2 (Unicode 2 bytes)
– ANSI X3.4 (ASCII 7 bits)
– ISO Latin 1 (8 bits)
380 | 406
'Network' task card
Global BACnet configuration
15
15.7.2 Disabling switch-off and switch-on messages

In the standard setting, messages for switching logical channels off and on are
sent to connected ↑ BACnet clients. These messages can be disabled.

Disable switch-off and switch-on messages as follows:
2. Select the 'Details' tab in the detail editor.
3. Check the 'Suppress BACnet mode ‘OFF’ in channels' checkbox.
a Switch-off and switch-on messages are disabled.
15.7.3 Delegating multiple alarms for 'Zones'

In the standard setting, the ↑ pre-alarm and alarm messages are signaled on the
'Zones'. This leads to problems in the ↑ BACnet model if it is in the 'Multiple alarms
per zone' setting.

These ↑ BACnet messages can be delegated to the logical channels and replace
the messages for 'Activation' there.
Activate the 'Multiple alarms per zone on BACnet' as follows:
2. Select the 'Details' tab in the detail editor.
3. Check the 'Multiple alarms per zone on BACnet' checkbox.
a 'Multiple alarms per zone on BACnet' is activated.
381 | 406
'Network' task card
15.7.4 Configuring BACnet client

The 'Network' element must be created in the tree view of the 'BACnet client
configuration' task card so that the ↑ BACnet client can be configured.
This element defines the ↑ management stations or third-party devices that are
accepted by the FS20 system. The customer text of this element is also used in the
event memory to log all actions triggered by a management station.
A BACnet client is identified by the 'BACnet device ID'.
Creating 'BACnet client configuration' element

1. Select 'Network' > 'Global system configuration' > 'Global BACnet configuration'
in the task card.
2. Create the 'BACnet client configuration' element for each ↑ BACnet client.
Link [➙ 77]
3. Enter the customer text.
Properties of the 'BACnet client configuration' element
Figure 185: 'BACnet client configuration' detail editor

The 'BACnet client configuration' that was assigned to the client must be entered in
the 'Details', 'BACnet device ID' detail editor. It must be aligned with the
management station data.
If required for the management station, the deactivated ↑ BACnet input fields can
be activated with the 'Check BACnet client address' checkbox. This is absolutely
not recommended. The reason for this is that the 'BACnet client' has a fixed IP
address and no DHCP server is used.
If 'BACnet device ID', 'BACnet network no.' and 'BACnet IP address' are to be used
to identify the BACnet client in addition to 'BACnet UDP port', these properties can
be set aligned with the management station data as follows.
l Check the 'BACnet client configuration' checkbox in the 'Details' tab of the
detail editor 'Check BACnet client address'.
a The fields are activated.
Figure 186: 'BACnet client configuration' detail editor
382 | 406
'Network' task card
Global BACnet configuration
15
15.7.5 Monitoring BACnet client

↑ Stations can monitor the connections to a ↑ BACnet client. To do this, each
station must be assigned a 'BACnet client supervision' element for each BACnet
client that is to be monitored. This element triggers a fault message if the
connection to the BACnet client is interrupted.
Configuration for monitoring requires the following points:
● Creating the 'BACnet client supervision' element
● Assigning the 'BACnet client supervision' and 'BACnet client configuration'
elements
● Determining 'Client supervision timeout'
Creating 'BACnet client supervision' element

1. Select 'Network' > ↑ 'Station' in the task card.
2. Create the 'Station' element for the 'BACnet client supervision' for each
↑ BACnet client that is to be monitored. Link [➙ 77]
Assigning the 'BACnet client supervision' and 'BACnet client

configuration' elements
1. Highlight the 'BACnet client supervision' element in the tree view.
a The 'BACnet client configuration' elements are highlighted in the list.
3. Select the corresponding element and click on 'Assign'.
Figure 187: Window 'Assign dialog' for assigning the element 'BACnet client supervision'
383 | 406
'Network' task card
Determining 'Client supervision timeout'
Figure 188: 'BACnet client supervision' detail editor, 'Overview'

In the detail editor 'BACnet client supervision' ('Overview'), the time after which a
fault message is displayed is defined in 'Client supervision timeout'.
The time period must match the ↑ BACnet client's query cycle, with which the
BACnet client queries the station's system status.
l Set a value 2.2. times that of the query cycle in the 'Client supervision timeout'
field.
15.7.6 Configuring 'Standby visibility' for the management station

'Station' can be assigned to a ↑ 'Standby visibility for Management station'. If the
↑ management station fails, the assigned 'Station' automatically receives this
↑ visibility.
You will find information on configuration of the standby view for management
stations in chapter 'Standby visibility [➙ 316]'.
384 | 406
'Network' task card
BACnet device configuration
15
15.8 BACnet device configuration
15.8.1 'BACnet device object' –Overview

In the tree view of the 'Network' task card, each ↑ 'Station' contains a 'BACnet
device object' element. It is used to identify the 'Station'in the ↑ BACnet.
● In the 'BACnet device object' tab of the detail editor, the 'Overview' element
contains an address and a predefined customer text ('Own device'). The
address is used directly as a 'BACnet device ID' and must be in the same
address range that has been entered in the global settings for BACnet.
● The configuration of the BACnet stack, including the BBMD function and the
properties of the device object for BACnet transaction control, can be found in
the 'Details' tab of the detail editor.
Figure 189: 'BACnet device object' detail editor, 'Details' tab
15.8.1.1 BACnet transaction control

The following properties of the 'BACnet device object' must be set in all ↑ stations
and be consistent for the entire ↑ site.
● 'APDU timeout'
Defines the timeout for the ↑ BACnet transaction control.
● 'APDU segment timeout'
Defines the timeout for the requirement of another part of a segmented BACnet
message.
● 'No. of APDU retries'
Defines the maximum number of repetitions for a BACnet transaction.
385 | 406
'Network' task card
15 BACnet device configuration
15.8.1.2 Configuration of the BACnet communications stack,

including BBMD function
As a rule there is just one value that has to be defined on all ↑ stations:
● 'UDP port no.'
Defines the number of the UDP port used for ↑ BACnet communication. The
default 47808 (0xbac0) corresponds to the standard. All participants, including
the BACnet clients, must use the same number.
The BBMD configuration in contrast needs only be made for one station per IP
sub-net. If using stations on the Ethernet this must be agreed with the BACnet
clients if they are in the same IP sub-net.
Configuration includes:
● 'Enable BBMD'
Enables the BBMD (BACnet Broadcast Management Device) functionality. This
is a BACnet function for the exchange of broadcast messages between
different IP sub-nets. If BBMD is enabled, then there is a 'BDT entry' and/or
'Enable FDT' is set to active.
● 'Two hops'
Selects either 'unicast' as the standard procedure for a partner BBMD (actively
set) or 'direct broadcast' if the IP routers are configured such that they pass on
broadcasts for other sub-nets (inactively set). The ↑ GAP, for example, cannot
do this.
● 'Enable FDT'
Enables remote BACnet devices to register in the 'Foreign Device Table' (FDT)
of the BBMD. This is required if there is no separate BBMD in their sub-nets.
● 'No. of FDT entries'
Defines the maximum number of FDT entries ('Foreign Device Table').
BBMD is a ↑ BACnet function that is required exactly once for each sub-net. One
device assumes this function and must recognize its partners in the other sub-
nets (BDT entries). Exception: One single device in a sub-net without this BBMD
function can also register as a third-party device with a BBMD in another sub-net
(dynamic FDT entry).
386 | 406
'Network' task card
15
15.8.1.3 Configuring a 'Station' as BBMD
A ↑ router 'Station' can carry out the ↑ GAP, BBMD, and router functionalities in
parallel.
Note the following information while selecting a ↑ 'Station' for configuration as
BBMD for performance optimization.
1. If a ↑ standby router 'Station' is set up, this should be activated as the BBMD.
2. If no standby router 'Station' is set up, the ↑ router 'Station' should be activated
as the BBMD.
Configuration requires the following points:
● Selection of the ↑ 'Station'
● Configuration of the 'Station' as BBMD
Selection of the 'Station'

1. In the tree view of the 'Network' task card, open the 'Global system
configuration' > 'FS20 network configuration' > 'Ethernet sub-net' >
'Connections' elements
or 'SAFEDLINK sub-net' > 'Connections'.
2. Highlight 'Fx20xx'/'Ethernet' or 'Fx20xx'/SAFEDLINK' and select the 'Station' via
the 'Network' hyperlink in the detail editor.
a The 'Station' is selected.
Configuration of the ↑ 'Station' as BBMD
The number 'No. of FDT entries' corresponds to the maximum supported by

FS20.
1. Open 'Station' in the structure tree.

2. Highlight 'BACnet device object'.
3. Select 'Details' in the detail editor.
4. Check the 'Enable BBMD' checkbox.
5. Check the 'Enable FDT' checkbox only if a BACnet client has to register to this
BBMD.
6. Leave the standard setting 'Two hops’. This configuration is tested with the
standard setting in the 'Broadcast distribution mask' of a 'BDT entries'.
a 'Station' is configured as BBMD.
387 | 406
'Network' task card
15.8.1.4 Configuring all stations

● The value for 'APDU timeout' should be agreed with the management station
integrator. We would recommend 10 seconds with MM8000.
● The value for 'APDU segment timeout' should also be agreed upon. We would
recommend 5 seconds.
● The value for 'No. of APDU retries' corresponds to the ↑ BACnet standard and
does not need to be changed.
● The 'UDP port no.' setting corresponds to the standard (47808 = 0xbac0). It
only needs changing if the entire system expects it to.
15.8.2 BBMD entry (BDT entry)

'BACnet device object' elements can be added to the 'BDT entry' element when the
BBMD function is activated.
This element defines the ↑ management station or the third-party device that has
the BBMD function in its sub-net. A 'BDT entry' element is required for each sub-
net with its own BBMD.
Creating 'BDT entry'

1. Select 'BACnet device object'.
2. Create the 'BDT entry' element for each BBMD. Link [➙ 77]
Configuring 'BDT entry'
Figure 190: 'BDT entry' detail editor, 'Details'

To configure 'BDT entry', proceed as follows:
1. Highlight 'BDT entry'.
2. Select 'Details' in the detail editor.
3. Enter the agreed IP address for the BACnet client.
4. Leave the predefined values for 'UDP port no.' and 'Broadcast distribution
mask' unchanged. The port number of the client must match its own, and the
mask value matches the pre-setting for 'Two hops'.
388 | 406
'Network' task card
15
15.8.3 BACnet Notification Class Element

All ↑ stations contain a list of 25 pre-defined entries under 'BACnet Notification
Class element' in the detail editor. Each entry stands for a ↑ BACnet notification
class and has one unique address and one customer text within a station. The
addresses are used in the BACnet object ID as instance numbers. The customer
text provides information on which elements of the application are represented by
this notification class. The internal assignment cannot be changed. The settings
should only be changed according to a ↑ management station integrator's
specification, and only when the behavior of different sub-systems has to be
adapted to a superordinate system.
Address Customer text Address Customer text

1 Areas 14 System
2 Sections 15 UGA
3 Zones 16 ↑ AVC
4 Sensors 17 ↑ IC
5 Control groups 18 Network
6 Controls 19 ↑ BACnet client
7 Spare 20 BACnet device
8 Channels (log.) 21 Line Summaries
9 Stations 22 Section Summaries
10 Module/Submodules 23 Control Groups HVAC
11 Lines 24 Controls HVAC
12 Devices 25 Channels (phys.) HVAC
13 Channels (phys.)
Table 19: Notification classes
To configure 'BACnet Notification Class element', proceed as follows:

1. In the 'Network' task card, highlight all the 'Fx20xx' stations one after the other.
2. Select 'BACnet Notification Class element' in the detail editor.
3. Set the priorities for each event notification.

4. Check the box for 'Acknowledge required' wherever acknowledgement is
required for status changes.
389 | 406
'Network' task card
The following settings are possible for each notification class:

● 'Event notification priorities'
The priority of an event message per status change and which of these
changes can be acknowledged at a management station is determined here.
The priorities for the event messages should be selected from the 0 to 63
range that is intended for 'LifeSafety' applications. The highest priority starts at
0 and the lowest ends at 255.
● 'Acknowledge required'
Here, the following status changes are defined (in this order):
– 'to-offnormal': Entry of an event
– 'to-fault': Entry of a fault
– 'to-normal': ↑ Normal operation re-established
Internally the FS20 fire detection system only processes the
acknowledgements for the 'to-offnormal' and 'to-fault' status changes. The 'to-
normal' status change can also be supported with acknowledgement for
↑ BACnet clients.
● There are no predefined entries for the recipients of event messages; these
must be entered by the BACnet clients at runtime.
390 | 406
'Network' task card
Checklist for network and BACnet configuration
15
15.9 Checklist for network and BACnet configuration

The checklists below list settings that must be entered and / or checked for
↑ BACnet integration.
Checklist for network configuration
Figure 191: Example of network configuration
Element in the structure tree Configuration in the detail editor Required setting/value
'Ethernet sub-net' 'Netmask' 255.255.255.0
'GAP' 'DHCP server enabled' Depending on network configuration
'SAFEDLINK sub-net' 'Netmask' 255.255.255.0
'Network speed' Standard
'Router' 'Router Ethernet IP address' 192.168.x.x
Table 20: Checklist for network configuration
391 | 406
'Network' task card
15 Checklist for network and BACnet configuration
Checklist for ↑ BACnet configuration
Figure 192: Example of ↑ BACnet configuration
Element in the structure Configuration in the detail editor Required setting/value

tree
'Global BACnet 'Enable BACnet communication' Activated
configuration'
'BACnet character set' UCS-2
'Address range, lower limit' 0
'Address range, upper limit' 4194302
'Suppress BACnet mode ‘OFF’ in channels' Deactivated
Creating 'BACnet client configuration' Several clients possible
'BACnet client 'BACnet device ID' Enter
configuration'
'Check BACnet client address' Depending on network configuration
'BACnet network no.' 0
'BACnet IP address' Depending on network configuration
'BACnet UDP port' 47808
'BACnet device object' (on 'UDP port no.' 47808
every 'Station')
'APDU timeout' 00:00:10
'No. of APDU retries' 3
'APDU segment timeout' 00:00:05
'BACnet device object' 'Enable BBMD' Activated
(only on one ↑ 'Station')
'Enable FDT' Deactivated
'Two hops' Activated
'No. of FDT entries' 2
392 | 406
'Network' task card
Checklist for network and BACnet configuration
15
Element in the structure Configuration in the detail editor Required setting/value

tree
'BACnet client supervision' 'Client supervision timeout' 2.2 times value of BACnet client's
query cycle
'BDT entry' 'IP address' for partner BBMD Depending on network configuration
'UDP port no.' 47808
'Broadcast distribution mask' 255.255.255.255
Table 21: Checklist for BACnet configuration
Checklist in the event of problems with integration

Problem Possible causes and measures
Communication fault Check the following points:
between a ↑ BACnet client ● A suitable ↑ license key is installed in all 'Stations'
and a FCnet-↑ 'Station'',
● BACnet communication is enabled in all 'Stations'
e.g., displayed on MM8000
● BACnet clients (device IDs) are correctly configured
● IP addresses are entered correctly in all 'Stations' and on the PC
● Routes are entered correctly on the PC
Communication fault Check the following points:
between SintesoWorks and ● Access to the 'Station' is registered with password
'Station'
● IP addresses are entered correctly in the 'Station' and on the PC
● Routes are entered correctly on the PC
Transactions are aborted 'APDU timeout' on 'Stations' and ↑ management station must be at least 6 s
(network analysis,
e.g. Wireshark: 'Abort' –
'timeout' message)
Table 22: Checklist in the event of problems with integration
393 | 406
'Network' task card
15 Site configuration, status MP2.1
15.10 Site configuration, status MP2.1

If an MP2.1 site configuration (BDV <32) is loaded in SintesoWorks, the network
configuration is shown as before. The 'Network' > 'Convert to GAP', 'Convert to
SAFEDLINK host', 'Convert to ethernet host', and 'Create GAP configuration' menu
items are also available.
It is therefore possible to maintain the 'Site' to status MP2.1 and add 'Stations' to it.
However, the 'Site' must be converted in accordance with BDV 32, if the limits of
the site size are exceeded when expanding or merging two 'Sites'.
15.10.1 Converting configuration in accordance with BDV 32

When converting older 'Sites' in accordance with ↑ BDV 32, the new structure is
created for 'Global system configuration' and the references for the ↑ 'Stations' are
stored under 'Connections'.
Observe the following points for conversion:
● Up to 32 'Stations' are permitted in a pure ↑ SAFEDLINK network.
● The number of 'Stations' in the SAFEDLINK sub-net is limited to 16 in a
heterogeneous network.
The SAFEDLINK sub-net of an older site version could have included up to 32
'Stations'. This number of 'Stations' stations must again be split into several (at
least two) SAFEDLINK sub-nets. Other 'New element' elements can be created
using the 'SAFEDLINK sub-net' function. The 'Fx20xx/SAFEDLINK' references
can then be moved to the various sub-nets using the 'Drag and drop', 'Cut', and
'Paste' or 'Unassign' and 'Assign' functions.
● The ↑ CAP station no longer exists with its previous function. It is changed into
↑ GAP + ↑ router station.
You will find detailed information on converting in document A6V10244961 and an
overview in document 009052. See chapter 'Applicable documents'.
See also
394 | 406
FG2020
16
16 FG2020
You will find information on the configuration of FG2020 in document
A6V10281424. See the chapter 'Applicable documents [➙ 15]'.
395 | 406
Glossary
Glossary
Alarm device BDV
Element in the fire detection system for acoustic Abbreviation for 'Base Data Variant'.
and/or visual alarming, e.g. alarm sounder, Configuration files for the embedded software. A
beacon. BDV contains country-specific templates, all
texts, specifications for message layout, menu
definitions, specifications for activating the LEDs
Alarm indicator on the PMI, detector parameter set settings,
Visual display to signal an alarm or pre-alarm. definitions for system-specific parts of the tool
interface, etc.
Alarm organization
Covers all measures which are used for CAP
alarming, rescue, preventing a fire from CAP = Central Access Point. Term valid up to
spreading, fire fighting, and orientation in the MP2.1. Also used in the tool for corresponding
event of a fire. Alarm organization may differ systems higher than MP2.1. Connection station
depending on the 'Manned' or 'Unmanned' between the SAFEDLINK and Ethernet sub-nets.
operation mode.
Alarm verification concept Detector line technology in which all detectors
Concept for preventing false alarms which takes that are connected to the same detector line
into account the interaction of the operating have a collective address. This makes it
personnel in the alarming sequence. impossible to identify individual detectors.
Alarming control Control group

Monitoring and controlling the alarming Combination of several similar controls.
equipment
Control tree
Alarming equipment Structure tree with control group and control.
Alarm devices and remote transmissions
CPU
Area Abbreviation for 'Central Processing Unit'. The
The top level in the detection tree. Sections and computing unit of the fire control panel.
zones are assigned to the area.
Danger level
Automatic fire detector A fire detector signal which conveys the
Device which measures a physical parameter possibility of fire. Automatic fire detectors, for
(e.g. warmth) in order to detect a fire. example, have danger levels 0 to 3. Manual call
points only have danger levels 0 and 3. 0 = no
AVC danger, 1 = possible danger, 2 = probable
Abbreviation for 'Alarm Verification Concept'. danger, 3 = highly probable danger.
BACnet Degraded mode

Abbreviation for 'Building Automation and Defined reduced mode of operation which
Control Networks'. It is a network protocol for occurs when part of the fire detection installation
building automation, such as for communication (e.g., main CPU) fails.
between a management station (MMS) and a fire
detection installation. Detection tree
Diagram of the geographical and organizational
arrangements of sensors in a building. This is a
hierarchical structure comprising the area,
section, and zone.
396 | 406
Glossary
Detector line GAP

Electrical connection between the detectors and Abbreviation for 'Global Access Point'.
the fire control panel. There are collective Participant in the Ethernet sub-net for the
detector lines and addressed detector lines. connection between the Ethernet sub-net and a
management station (BACnet client) and / or for
Detector line topology remote access with the PC. If there is a
secondary GAP, the GAP becomes the main
Arrangement of devices on the detector line.
GAP. Can be operated as a DHCP server in the
Depending on the detector line, up to three
Ethernet sub-net.
topology types are possible: Loop, stub, stub on
loop
Gateway
Effect Network bridges which link two different systems
/ networks with one another and transfer the
An impact caused by a control, e.g., activation of
different communication and transmission
a hardware output or a command.
standards / protocols.
Emergency power operation Global alarming
The fire detection installation is supplied by the
Global alarming equipment (e.g., remote
second source of power, e.g., batteries.
transmission) is actuated and external
intervention forces (e.g., the fire brigade) are
Ethernet station alerted.
Participants in the Ethernet sub-net without local
connection for the PC. Hardware tree
Depiction of the hardware of a fire detection
External alarm indicator installation.
Optical element for displaying the fire location,
which is at some distance from the detector. It is IC
normally mounted in the room at the point where
Abbreviation for 'intervention concept'
the corresponding detector is accessible.
Extinguishing control Intervention concept

Concept with two independent verifications:
Control which controls a connected extinguishing
Attendance check for quick intervention on-site
system and evaluates and displays its states.
and intervention check for servicing measures.
False alarm Isolation
Alarm not triggered by a danger.
Status of one part of the fire detection
installation, which suppresses the evaluation of
FDnet all signals.
Addressed detector line for FDnet devices.
License key
Fire control Hardware modules for activating functions.
Control which is activated in the event of a fire
alarm. Line card
Card for connecting peripheral devices. The card
Floor repeater display can be a plug-in card or it can be integrated into
A display device without operating elements. the periphery board.
Floor repeater terminal Link

A display device with operating elements for Creating a reference between two elements,
acknowledging and resetting alarms and faults. e.g., logical channel and physical channel.
397 | 406
Glossary
Local alarming PMI

Local alarming equipment (e.g. acoustic or The arrangement of operating and display
optical) is actuated in order to call up elements on a fire control panel or on a fire
intervention personnel and to alert people of a terminal. Includes the LEDs, buttons, the display,
possible fire hazard. and the operation options such as the key
switch, fire brigade control and display (FBA),
Logical channel and the EVAC NL Person Machine Interface.
Depiction of a logical device function in the
detection or control tree. The logical channel is Pre-alarm
always the bottom level in the structure tree. Stage before an alarm for information early on,
should an event occur.
Loop
Detector line topology which runs from the fire Pre-configuration
control panel via the fire detectors and back to A sub-configuration of the hardware tree,
improve operational reliability. This type of wiring detection tree, and control tree created before
allows all detectors to communicate with the commissioning the fire detection installation.
control panel even in the event of an open line or
short-circuit. Radio gateway
Interface converter for converting from detector
LRC line protocol to radio.
Abbreviation for 'Lifecycle Responsibility
Concept'. Software license server for the Router station
Engineering Tool.
Participant in the SAFEDLINK sub-net for the
connection between the SAFEDLINK sub-net
Management station and the Ethernet sub-net (FCnet/C-WEB/LAN)
A superordinate system for monitoring and via the Ethernet switch (modular) FN2012-A1.
operating safety-related sites and buildings, e.g.,
fire, intrusion, access, heating, ventilation. RT
The abbreviation for remote transmission.
Manned
Switching status of the alarm organization, if SAFEDLINK
operating personnel are present and can
Physical network of an FS20 / FS720 fire
intervene should an event arise (alarm, fault).
detection system with the network module
(SAFEDLINK) and the network cable.
Multi-detector dependency
When using multi-detector dependency, the SAFEDLINK station
danger levels of several detectors are included
Participants in the SAFEDLINK sub-net with
in the alarm decision. Measures such as
local connection for the PC.
alarming or closing the fire doors are only
initiated when the defined dependencies occur
(e.g., two detectors detect danger level 3). Section
Level in detection tree of the fire detection
Normal operation system. The section is assigned to the area. It is
used for combining zones.
The fire detection installation is supplied with
mains voltage.
Single-detector dependency
Parameter set With single-detector dependency, the alarm
decision depends on the danger level of one
Defined detector behavior, e.g. in terms of
detector. The first detector in the zone which
sensitivity, resistance to deceptive phenomena,
detects the corresponding danger level, triggers
response time. Detectors can be operated with
the fire alarm.
different parameter sets.
Physical channel Site

Depiction of fire detection installation: The top
Depiction of a device's physical function in the
level in the figure showing the installed system.
hardware tree. The physical channel is always
Combines hardware tree, detection tree, and
the bottom level in the hardware tree.
control tree.
398 | 406
Glossary
Standalone station
Standalone station with local connection for the
PC.
Standby router station

Participant in the SAFEDLINK sub-net, in
redundancy to the router station, for the
connection between the SAFEDLINK sub-net
and the Ethernet sub-net (FCnet/C-WEB/LAN)
via Ethernet switch (modular) FN2012-A1.
Station
Unit for system control. Fire control panel or fire
terminal.
Stub
Detector line which is only connected to the fire
control panel on one side. In the event of an
open line or short-circuit, it may no longer be
possible for all fire detectors to communicate
with the fire control panel.
Technical message
Events (e.g., from third-party systems) evaluated
via sensors or contacts which are forwarded to
the fire control panel.

Level in control tree of the fire detection system.
The fire control group contains the fire controls.
Unmanned
Switching status of the alarm organization, if
operating personnel are not present and cannot
intervene should an event arise (alarm, fault).
VdS
Abbreviation for 'Vertrauen durch Sicherheit', a
company in the Gesamtverband der Deutschen
Versicherungswirtschaft e.V. (GDV). Inspection
and certification body for fire detection systems
in Germany.
Visibility
Defines which part of a site is visible and can be
operated on a station.
Zone
Level in the detection tree. The zone has at least
one fire detector. The decision on alarm is made
at zone level. The zone is assigned to a section
or an area.
399 | 406
Index
Index
A Base sounder .......................... 154, 157, 158, 278
Access level ........................................... 294, 314 Direct activation ............................................ 154
Address .......................................................... 84 Features ....................................................... 157
Alarm counter ................................................ 260 Output mode................................................. 154
Alarm counter control ..................................... 260 BDT entry ..................................................... 388
Alarm indicator BDV
Addressable ................................................. 284 File name ....................................................... 37
External ................................. 153, 159, 190, 277 Importing ........................................................ 46
Internal ......................................................... 153 Version ........................................................... 37
Alarm indicator, internal Buzzer .......................................................... 290
Deactivate .................................................... 153
Alarm sounder beacon FDS229 ....................... 160 C
CERLOOP .................................................... 352
Alarm sounder FDS221 .................................. 160
CERLOOP gateway ....................................... 352
Alarm verification concept ............................... 194
Checklist
Alarming control group.................................... 233
BACnet ......................................................... 392
Alarming equipment (UGA) ............................. 348
Network configuration ................................... 391
AnalogPLUS detector line ............................... 182
Collapse
Area ............................................................. 194
Element in the structure tree ........................... 62
Assign
Collective detector line............................. 175, 176
Damper control effects .................................. 263
Via FDCIO223 .............................................. 225
Detection tree ............................................... 224
Common Remote Service Platform (cRSP) ....... 370
Element .......................................................... 85
Configuration
Hardware tree ............................................... 224
Conversion ................................................... 394
Automatic fire detectors
Load to station ...................................... 113, 114
Features ....................................................... 153
Loading to PC ............................................... 115
Automatic zone .............................................. 200
Configuring
AVC ............................................................. 194
Zone ............................................................. 216
B Connect management stations via
Backlight ....................................................... 295 BACnet/Ethernet ....................................... 379
Backup ........................................................... 40 Connecting PC to FCnet ................................. 376
BACnet Connection from PC to FCnet .......................... 376
Checklist ....................................................... 392 Control
BACnet client Dampers....................................................... 261
Configuring ................................................... 382 Control group
Monitoring..................................................... 383 Alarming ....................................................... 233
BACnet configuration Counter ........................................................ 260
Global ........................................................... 380 Evacuation.................................................... 251
Project planning ............................................ 379 Control tree ................................................... 232
BACnet device configuration ........................... 385 Controls ........................................................ 232
BACnet device object ..................................... 385 Task card ..................................................... 232
BACnet Notification Class Element................... 389 Conversion
BACnet settings global ................................... 380 Configuration ................................................ 394
BACnet/Ethernet ............................................ 379 Protocol ........................................................ 120
Banner.......................................................... 100 Site ............................................................... 119
Barcode ......................................... 40, 40, 88, 88 Conversion log .............................................. 120
400 | 406
Index
Copy E
Element .......................................................... 82 Editing
Features ......................................................... 80 Element .......................................................... 80
Counter control group .................................... 260 System properties ........................................... 75
Country settings ............................................ 292 Effects
Create Damper control ............................................. 263
Element .......................................................... 77 Element
Site ................................................................. 72 Assign ............................................................ 85
Station ............................................................ 76 Copy ............................................................... 82
Create and assign ......................................... 179 Create ............................................................ 77
cRSP (common Remote Service Platform) ....... 370 Cut ................................................................. 82
cRSP remote maintenance platform................. 370 Deleting .......................................................... 79
CSV Editing ............................................................ 80
Exporting ........................................................ 97 Move .............................................................. 83
Import ............................................................. 99 Paste .............................................................. 82
Protocol .......................................................... 99 Re-address ..................................................... 84
Customer text ........................................ 124, 216 Replace .......................................................... 79
Cut Element in the structure tree
Element .......................................................... 82 Collapse ......................................................... 62
Expand ........................................................... 62
D Engineering tool
Damper control ............................................. 261
Log file............................................................ 53
Assigning effects........................................... 263
Engineering tool set
State ............................................................. 262
File name........................................................ 37
Dampers
Install ........................................................ 29, 53
Monitoring ..................................................... 263
Version ........................................................... 37
Data Matrix code ........................................ 40, 88
Error display ................................................... 67
Data migration............................................... 125
ESPA 4.4.4 interface...................................... 344
Deleting
Ethernet printer ............................................. 335
Element .......................................................... 79
Ethernet switch (MM) ..................................... 378
Detection tree ............................................... 193
Ethernet switch (modular) ............................... 171
Assign .......................................................... 224
EVAC panel .................................................. 346
Detector
Evacuation control group ................................ 251
Parameter sets ............................................. 155
Event printer ................................................. 335
Sensor mode ................................................ 156
Exit
Detector flashing ........................................... 153
Software ......................................................... 36
Detector line
Expand
Collective ...................................................... 225
Element in the structure tree ........................... 62
Display backlight ........................................... 295
Expanded visibility ......................................... 319
Display logo .................................................. 100 Export
Download .............................................. 113, 114
SiB-X .............................................................. 96
Download center
XML................................................................ 94
URL ................................................................ 16
Exporting
Dynamic loading .............................................. 70
CSV................................................................ 97
External alarm indicator............. 153, 159, 190, 277
External printer.............................................. 335
Extinguishing standard interface SST............... 273
401 | 406
Index
F Firmware
FAT .............................................................. 338 File name ....................................................... 38
Favorite Update station .............................................. 119
PMI............................................................... 300 Version ........................................................... 38
Favorites list Firmware import ............................................... 47
SintesoView .................................................... 45 Floor repeater display FT2011 ......................... 322
FBF .............................................................. 338 Floor repeater terminal FT2010 ....................... 322
FC2080......................................................... 320 Flow rate indicator zone .................................. 207
FCI2007-A1 I/O card (remote transmission) ...... 169 FN2008-A1 ................................................... 378
FCI2008-A1 I/O card (programmable) ............... 169 FN2009-A1 ............................................ 366, 378
FCI2009-A1 I/O card (horn/monitored) .............. 169 FN2012-A1 ................................................... 171
FCL2001 line card (FDnet/C-NET) ................... 152 FSD ............................................................. 338
FCL2002 line card (collective) ......................... 175 FSE zone ...................................................... 215
FCL2003 line card (MS9i) ............................... 178 FT2001 ......................................................... 330
FDCAI221 ..................................................... 284 FT2010 ......................................................... 322
FDCIO223 input/output module................. 163, 279 FT2011 ......................................................... 322
Collective detector line .................................. 225 FTO2002 ...................................................... 330
Monitored input ............................................. 282 Fuse ............................................................... 40
Monitored output ........................................... 282
Product version............................................. 163 G
GAP ............................................... 362, 366, 368
Sounder line ................................................. 279
Gas zone ...................................................... 210
FDOOTC241 neural fire detector ..................... 226
Gateway
FDS221 alarm sounder ................................... 160
CERLOOP.................................................... 352
FDS229 alarm sounder beacon ....................... 160
Global behaviour............................................ 290
FDSB221 sounder interbase ........................... 160
FDSB229 sounder beacon interbase ................ 160
H
Features Hardware tree
Automatic fire detectors ................................ 153 Assign .......................................................... 224
Copy ............................................................... 80 Help ............................................................... 59
Inputs/outputs ............................................... 172 Help file import ................................................ 47
Station .......................................................... 149 History ............................................................ 70
FG2020 ........................................................ 395 Hours ........................................................... 293
File name
BDV................................................................ 37 I
Engineering tool set ........................................ 37 I/O card (horn/monitored) FCI2009A1 ............... 169
Firmware ........................................................ 38 I/O card (programmable) FCI2008-A1............... 169
Finding ........................................................... 91 I/O card (remote transmission) FCI2007-A1 ...... 169
Finding and replacing ....................................... 92 IC 150
Fire brigade periphery..................................... 338 Import
Fire control .................................................... 239 CSV................................................................ 99
Fire damper Resources ...................................................... 47
State............................................................. 262 Importing
Fire dampers BDV................................................................ 46
Control.......................................................... 261 Initialize
Monitoring..................................................... 263 Station .......................................................... 113
Fire door ....................................................... 243 Input/output module FDCIO223 ....................... 163
Inputs/outputs
Features ....................................................... 172
Onboard ....................................................... 152
402 | 406
Index
Install M
Engineering tool set .................................. 29, 53 Manual allocation of addresses in sub-nets ...... 364
Interactive detector line .................................. 187 Manual zone ................................................. 204
Internal alarm indicator Master clock ................................................. 293
Deactivate .................................................... 153 Menu bar ........................................................ 55
Internet settings............................................... 43 Mimic display ................................................ 330
Intervention concept (IC) ................................ 150 Mimic display driver FT2001 ........................... 330
Monitoring
K Dampers ....................................................... 263
Key depot adapter FCI2019 ..................... 342, 342
Short-circuit .......................................... 172, 191
Key switch .................................................... 295
Mouse wheel ........................................... 42, 123
Move
L
Latching ................................................ 220, 291 Element .......................................................... 83
LED MS9i detector line.......................................... 178
PMI ............................................................... 296 Multi-detector dependency................ 203, 219, 222
LED indicator (FTO2002)................................ 170 Multi-detector dependency with latching ........... 220
LED indicator FTO2002 ........................... 170, 330 Multiselection .................................................. 62
License .......................................................... 52 Multi-sensor fire detector ................................ 156
Load/renew ..................................................... 47
Returning ........................................................ 52
N
Navigating
License key .................................................... 53
With hyperlinks ............................................... 63
License test .................................................... 35
With shortcuts ................................................. 64
Licensing ........................................................ 47
With task cards ............................................... 63
Licensing information ....................................... 52
Lifecycle Responsibility Concept (LRC) .............. 47
Checklist ....................................................... 391
Line
Network speed, SAFEDLINK .......................... 368
Collective ...................................................... 225
Neural fire detector FDOOTC241 .................... 226
Line card (collective) FCL2002 ........................ 175
Line card (FDnet/C-NET) FCL2001.................. 152 O
Line card (MS9i) FCL2003 .............................. 178 Onboard I/Os ................................................ 152
Load Operation mode
From PC to station ................................ 113, 114 SintesoView .................................................. 151
From station to PC ........................................ 115 Original language
Load data to PC Source language............................................. 13
Event memory .............................................. 116 Output mode ................................... 159, 173, 191
Log file .......................................................... 117
Site ............................................................... 115 P
Pager ........................................................... 344
Load data to the station
Parameter sets.............................................. 155
Site ............................................................... 114
Partner BBMD entry (BDT entry) ..................... 388
Load event memory to PC .............................. 116
Paste
Log file ......................................................... 117
Element .......................................................... 82
Engineering tool ........................................ 53, 53
PC
Logo ............................................................ 100
Connect to station ......................................... 111
Loop ............................................................ 374
Disconnecting from station ............................ 111
Loop sounder ................................................ 278
Peripheral devices
Loop sounder/flashlight .................................. 278
Updating the firmware ................................... 120
LRC ............................................................... 47
Peripheral firmware import ................................ 47
LRC web server .............................................. 44
403 | 406
Index
Permanent access S
SintesoView .................................................. 151 Safety module (firewall) ........................... 366, 378
PMI ....................................................... 294, 294 Saving list of parts............................................ 53
Favorite ........................................................ 300 Scroll bars ....................................................... 61
LED .............................................................. 296 Scroll wheel............................................. 42, 123
Standard key ................................................ 299 SD adapter.................................................... 342
Power supply ................................................. 167 Sensor mode ................................................. 156
Pre-settings ..................................................... 38 Settings
Firmware files ................................................. 42 Automatic fire detectors ................................ 153
General program settings................................ 39 Inputs/outputs ............................................... 172
Help files......................................................... 43 Short-circuit monitoring ............................ 172, 191
Internet settings .............................................. 43 Shortcuts ........................................................ 64
LRC web server .............................................. 44 SiB-X export .................................................... 96
Periphery Update Tool .................................... 44 Single-detector dependency ............................ 203
Quicktext settings ........................................... 42 SintesoView
SintesoView .................................................... 45 Favorites list ................................................... 45
'Site' settings................................................... 46 Operation mode ............................................ 151
Printer .......................................................... 335 SintesoView settings ........................................ 45
Problem identification ....................................... 67 Site
Product version.............................................. 158 Conversion ................................................... 119
Input/output module FDCIO223..................... 163 Create ............................................................ 72
Program window .............................................. 54 Editing properties ............................................ 75
Proposed texts................................................. 42 Load data to PC............................................ 115
Protocol Load data to the station ................................ 114
Conversion ................................................... 120 Smoke damper
Protocol of the CSV import ................................ 99 State............................................................. 262
Smoke dampers
Q Control.......................................................... 261
Quicktext................................................... 42, 81
Monitoring .................................................... 263
Software
R
Re-address Exit ................................................................. 36
Element .......................................................... 84 Start ............................................................... 35
Reading device Sounder base FDSB291 .......................... 158, 158
Data Matrix code............................................. 40 Sounder beacon interbase FDSB229 ............... 160
Reading device for Data Matrix code .................. 88 Sounder interbase FDSB221 ........................... 160
Redundancy management .............................. 371 Sounder line
Automatic ..................................................... 372 Via FDCIO223 .............................................. 279
Loop ............................................................. 374 Source language.............................................. 13
Site-specific .................................................. 375 Sprinkler control............................................. 208
Stub.............................................................. 373 Sprinkler zone ............................................... 208
Redux module ............................................... 229 Standard key
Remote access PMI............................................................... 299
cRSP ............................................................ 370 Standard visibility ........................................... 315
Two GAPs .................................................... 368 Standby visibility ............................................ 316
Replace .......................................................... 92 Start
Element .......................................................... 79 Software ......................................................... 35
Reports......................................................... 101 State
Router station ................................................ 361 Damper control ............................................. 262
404 | 406
Index
Station U
Create ............................................................ 76 UGA ............................................................ 348
Features ....................................................... 149 Updating the firmware
Initialize ........................................................ 113 Peripheral devices ........................................ 120
Load data ..................................................... 113 Upload ......................................................... 115
Router station ............................................... 361
Status bar ....................................................... 64 V
Version
Stub ............................................................. 373
BDV................................................................ 37
Sub-system zone........................................... 206
Engineering tool set ........................................ 37
System behavior ........................................... 290
Firmware ........................................................ 38
System properties
Visibility ................................................. 313, 320
Editing ............................................................ 75
Extended ...................................................... 319
System requirements
Standard ....................................................... 315
Hardware ........................................................ 28
Standby ........................................................ 316
Software ......................................................... 28
System time .................................................. 293 W
Walk test ...................................................... 291
T Window separating lines................................... 61
Task card ....................................................... 60
Components ................................................... 61 X
Controls ........................................................ 232 XC10 ........................................................... 211
Detection ...................................................... 193 XML export ..................................................... 94
Hardware ...................................................... 148
Network ........................................................ 359 Z
Zone ............................................................ 200
Operation...................................................... 289
Automatic ..................................................... 200
Technical zone .............................................. 205
Configuring ................................................... 216
Time ............................................................ 293
Flow rate indicator ........................................ 207
Time control .................................................. 246
FSE .............................................................. 215
Toggle function ............................................. 308
Gas .............................................................. 210
Toolbar........................................................... 58
Manual ......................................................... 204
Tooltips .......................................................... 59
Sprinkler ....................................................... 208
Two-zone dependency ............................ 221, 223
Sub-system .................................................. 206
Technical ...................................................... 205
XC10 ............................................................ 211
405 | 406
Issued by © Siemens Switzerland Ltd, 2006
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: 009078_q_en_-- Manual FS20

Edition: 2015-12-15

FS20 Fire Detection System: Configuration

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

FS20 Fire Detection System: Configuration

Uploaded by

Copyright:

Available Formats

FS20

Fire detection system

009078_q_en_-- Building Technologies

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

© Siemens Switzerland Ltd, 2006

1 About this document ........................................................................... 13

1 About this 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

Additional documents for AlgoRex/SIGMASYS data migration

1.2 Download center

1.3 Technical terms and abbreviations

1.4 Revision history

The table below shows this document's revision history:

Version Edition date Brief description

Version Edition date Brief description

Version Edition date Brief description

Version Edition date Brief description

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

Disregard of the safety regulations

2.3 Standards and directives complied with

2.3.1 CPR conformity and firmware version

2.4 Release Notes

2.5 Cyber security disclaimer

Component Minimum requirements

AlgoRex system version XX_1140_830_YY

3.2 Installing the engineering tool set

Network address Network mask ↑ Gateway address Metric

Installing the engineering tool set FX2030

The path for the log files cannot be changed afterwards.

1 [Version] = Version of the software, e.g., EN_en_1-V1

3.3 Installation via the input prompt

The uninstall and installation process cannot be interrupted.

The instructions below apply to installation in Windows 7 and 8.1.

3.3.1 Installation and uninstallation with default parameter values

Installation parameter Default value

Uninstallation parameter Default value

Uninstallation and installation

3.3.2 Installation with modified parameter values

Values for Engineering Tool interface language and BDV language

3.3.3 Uninstallation with modified parameter values

The sequence of the parameter commands is not important.

3.3.4 Installation with initialization file

3.3.4.1 Creating an initialization file

[Remove components at uninstall]