A6V10333423 Configuration Siemens Cerberus

FS920
Fire detection system

Configuration
MP-UL 1.0
A6V10333423_a_en_US
01/18/2012
Siemens Industry, Inc.

Building Technologies Division
Legal notice
Legal notice
Technical specifications and availability subject to change without notice.
2012 Copyright by Siemens Industry, Inc.
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:
8 Fernwood Road
Florham Park, NJ 07932
Tel. +1 973-593-2600
www.sbt.siemens.com/FIS
Edition: 01/18/2012
Document ID: A6V10333423_a_en_US
2
A6V10333423_a_en_US
01/18/2012
Table of contents
1
About this document .........................................................................................9
1.1
Applicable documents ........................................................................................10
1.2
Technical terms ..................................................................................................11
1.3
History of changes..............................................................................................11
Safety.................................................................................................................12
2.1
Safety instructions ..............................................................................................12
2.2
Safety regulations for the method of operation ..................................................13
2.3
Standards and directives complied with.............................................................15
2.4
Release Notes....................................................................................................15
Installation ........................................................................................................16
3.1
System requirements .........................................................................................16
3.2
Installing the engineering tool set.......................................................................16
3.3
IP settings for several network cards .................................................................18
3.4
Starting the software ..........................................................................................19
3.5
Exiting the software ............................................................................................19
Software administration ..................................................................................20
4.1
Lifecycle Responsibility Concept (LRC) .............................................................20

4.1.1
Loading / renewing licenses ...............................................................20
4.1.2
Returning licenses ..............................................................................24
4.1.3
Viewing license information ................................................................25
4.1.4
Installing several different engineering tool kits..................................25
4.1.5
Saving a parts list for the 'Site'............................................................25
4.2
Engineering tool set: File name and version ......................................................26
4.3
BDV: File name and version ..............................................................................26
4.4
Firmware: File name and version.......................................................................27
4.5
BDV import .........................................................................................................28
4.6
Firmware import .................................................................................................28
4.7
License key ........................................................................................................28
4.8
Calling up log files ..............................................................................................28
GUI .....................................................................................................................29
5.1
Overview of the program window.......................................................................29
5.2
Menu bar ............................................................................................................30
5.3
Toolbar ...............................................................................................................32
5.4
Help and tooltips.................................................................................................32
3
A6V10333423_a_en_US
01/18/2012
5.5
Pre-settings ........................................................................................................35
5.5.1
Commissioning settings ......................................................................36
5.5.2
Quicktext and mouse wheel settings ..................................................36
5.5.3
Firmware files settings ........................................................................37
5.5.4
Internet settings...................................................................................37
5.5.5
Settings for LRC web server ...............................................................38
5.5.6
General program settings ...................................................................39
5.5.7
Cerberus-Remote settings ..................................................................40
5.5.8
'Site' settings .......................................................................................41
5.6
Task cards ..........................................................................................................42
5.7
Task card components .......................................................................................43
5.8
Scroll bars and window separating lines ............................................................44
5.9
Expanding and collapsing the elements in the structure tree ............................44
5.10
Multiselection......................................................................................................44
5.11
Navigating within the program window...............................................................45

5.11.1
Navigating with task cards ..................................................................45
5.11.2
Navigating with hyperlinks ..................................................................45
5.11.3
Navigating with shortcuts ....................................................................46
5.12
Status bar ...........................................................................................................46
5.13
Designation of problems and displaying errors ..................................................47
5.14
Cerberus-Remote ...............................................................................................49
5.15
Dynamic loading .................................................................................................52
Program operation ...........................................................................................54
6.1
Creating a 'Site' ..................................................................................................54

6.1.1
Loading an existing 'Site' ....................................................................54
6.1.2
Creating 'Site' based on existing configuration ...................................55
6.1.3
Creating a new 'Site' ...........................................................................56
6.1.4
Editing the 'Site' properties .................................................................57
6.2
Creating a 'Panel' ...............................................................................................58
6.3
Creating an element ...........................................................................................60
6.4
Replacing an element.........................................................................................62
6.5
Deleting an element............................................................................................62
6.6
Editing an element..............................................................................................62
6.7
Copying properties in the table...........................................................................63
6.8
Entering quicktext ...............................................................................................63
6.9
Copying, cutting and pasting an element ...........................................................63
6.10
Moving an element .............................................................................................65
6.11
Re-addressing elements ....................................................................................65
6.12
Assigning elements ............................................................................................67
6.13
Creating and assigning devices .........................................................................68
6.14
Deleting a link .....................................................................................................71
6.15
Finding................................................................................................................71
4
A6V10333423_a_en_US
01/18/2012
6.16
Finding and replacing .........................................................................................73
6.17
Exporting and importing a CSV..........................................................................74

6.17.1
Exporting a CSV .................................................................................74
6.17.2
Importing a CSV..................................................................................75
6.17.3
CSV import log....................................................................................76
6.18
Changing display logo ........................................................................................76
6.19
Creating reports..................................................................................................77
6.19.1
'Customer text report'..........................................................................78
6.19.2
'Device report' .....................................................................................79
6.19.3
'Diagnostics report'..............................................................................79
6.19.4
'Event memory report' .........................................................................80
6.19.5
'Node report'........................................................................................81
6.19.6
'Tree report'.........................................................................................82
Connectivity and communication with 'Panel' ..............................................83
7.1
Connecting the PC to the panel .........................................................................83
7.2
Disconnecting PC from the 'Panel'.....................................................................83
7.3
Connecting Cerberus-Remote ...........................................................................84
7.4
Loading data to the 'Panel' .................................................................................85
7.5
Initializing 'Panel' ................................................................................................86
7.6
Loading configuration from the PC to the 'Panel' ...............................................86
7.7
Loading configuration from the 'Panel' to the PC ...............................................88
7.8
Loading event memory to PC.............................................................................89
7.9
Loading the 'Site' log files to the PC...................................................................90
7.10
Merging two 'Sites' .............................................................................................91
7.11
Updating the firmware of the 'Panel' ..................................................................91
Configuration Overview................................................................................92
8.1
Customer text .....................................................................................................93
'Hardware' task card ........................................................................................94
9.1
Intervention concept (IC) ....................................................................................94
9.2
Creating a detector circuit device.......................................................................96
9.3
Properties of detector circuit devices .................................................................97

9.3.1
Device with internal LED.....................................................................97
9.3.2
Input ....................................................................................................97
9.3.3
Output .................................................................................................98
9.3.4
HZM with conventional detector circuit ...............................................98
9.3.5
HCP with 'NAC/speaker/telephone' ....................................................98
9.3.6
Detector sensor...................................................................................99
9.3.7
Detector with audible base ...............................................................100
9.3.8
Detector with configurable output .....................................................100
9.3.9
Detector with ambient supervision....................................................101
9.3.10
FDCIO442.........................................................................................102
5
A6V10333423_a_en_US
01/18/2012
9.4
Periphery board ................................................................................................104

9.4.1
'Onboard NAC' element ....................................................................105
9.4.2
'Optional NAC (FCI2011)' element....................................................105
9.4.3
'City tie' and 'Leased line' elements ..................................................107
9.5
RS485 class A module (isolated) .....................................................................108
9.6
Power supply ....................................................................................................110
9.7
Releasing module.............................................................................................110
9.8
LED module FTO2008......................................................................................112
9.9
Dialer module (DACT) ......................................................................................113
9.10
SAFEDLINK interface (FN2001/2010) .............................................................114
10
'Detection' task card.......................................................................................115
10.1
Creating 'Detection tree' ...................................................................................116
10.2
'Area'.................................................................................................................117
10.2.1
Alarm verification concept (AVC) ......................................................117
10.2.2
Immediate global alarming................................................................120
10.3
'Section' ............................................................................................................120
10.4
'Zone' ................................................................................................................120
10.4.1
'Automatic alarm zone' ......................................................................122
10.4.2
'Manual alarm zone' ..........................................................................123
10.4.3
'Supervisory zone' .............................................................................123
10.4.4
'Waterflow zone' ................................................................................124
10.4.5
'Sub-system zone' .............................................................................124
10.4.6
'Trouble zone'....................................................................................126
10.4.7
'Status zone'......................................................................................126
10.4.8
'Gas zone' .........................................................................................127
10.5
Configuring the 'Zone'.......................................................................................127
10.6
Assigning hardware tree to detection tree........................................................130
11
'Control' task card ..........................................................................................131
11.1
Creating a control tree ......................................................................................131
11.2
'Alarming control group' ....................................................................................132

11.2.1
'RT control' elements.........................................................................133
11.2.2
Assigning 'RT control' elements........................................................134
11.2.3
'City tie' element ................................................................................136
11.2.4
Assigning the 'City tie' element .........................................................137
11.2.5
'Leased line' elements.......................................................................139
11.2.6
Assigning 'Leased line' elements ......................................................140
11.2.7
Properties of the controls for remote transmission ...........................141
11.2.8
'DACT control' element .....................................................................142
11.2.9
Assigning the 'DACT control' element...............................................142
11.2.10 Properties of the 'DACT control' element..........................................144
6
A6V10333423_a_en_US
01/18/2012
11.2.11 'NAC control' elements......................................................................145

11.2.12 Assigning 'NAC control' elements.....................................................146
11.2.13 Properties of 'NAC control' elements ................................................148
11.3
11.4
11.5
'Fire control group'............................................................................................149

11.3.1
'Fire control' element.........................................................................149
11.3.2
Assigning 'Fire control' element ........................................................150
11.3.3
Properties of element 'Fire control' ...................................................152
11.3.4
'ILED control' element .......................................................................154
11.3.5
Assigning an 'ILED control' element .................................................155
11.3.6
Properties of the 'ILED control' element ...........................................157
11.3.7
Properties of the assigned cause elements......................................158
11.3.8
Properties of the assigned effect elements.......................................160
'Evac control group' ..........................................................................................161

11.4.1
'Universal evac control' element .......................................................161
11.4.2
Assigning a 'Universal evac control' element....................................162
11.4.3
Properties of the 'Universal evac control' element............................163
11.4.4
11.4.5
Properties of the assigned effect elements.......................................168
'Releasing control group' ..................................................................................168

11.5.1
'Agent releasing control' element......................................................168
11.5.2
Assigning an 'Agent releasing control' element ................................170
11.5.3
Properties of the 'Agent releasing control' element ..........................172
11.5.4
'Sprinkler releasing control' element .................................................173
11.5.5
Assigning a 'Sprinkler releasing control' element .............................174
11.5.6
Properties of the 'Sprinkler releasing control' element .....................176
11.5.7
12
'Operation' task card......................................................................................180
12.1
Global system configuration .............................................................................180

12.1.1
System behavior ...............................................................................180
12.1.2
Master clock......................................................................................181
12.1.3
Country settings ................................................................................182
12.2
Person Machine Interface (PMI) ......................................................................182
12.3
Basic settings ...................................................................................................182
12.4
LEDs.................................................................................................................184
12.4.1
Assigning the hardware ID to the LED..............................................185
12.4.2
Assigning a pre-defined cause .........................................................185
12.4.3
Assigning an event............................................................................187
12.5
Standard keys ..................................................................................................188
12.6
Favorites...........................................................................................................189
12.6.1
Creating favorites..............................................................................191
12.6.2
Text for favorites ...............................................................................191
12.6.3
Defining position of favorite ..............................................................192

7

A6V10333423_a_en_US
01/18/2012
12.7
12.8
12.9
12.10
Configuring standard keys and favorites ..........................................................192

12.7.1
Assigning the hardware ID to the standard key ................................192
12.7.2
Assigning standard keys and favorites .............................................193
12.7.3
Properties of the assigned functions.................................................197
Toggle function .................................................................................................199

12.8.1
Configuring the standard key for the toggle function ........................200
12.8.2
Configuring the LED for the toggle function......................................202
Visibility.............................................................................................................203
12.9.1
Properties of visibility ........................................................................204
12.9.2
Standard visibility ..............................................................................205
12.9.3
Standby visibility................................................................................206
12.9.4
Expanded visibility.............................................................................207
LED module......................................................................................................209
12.10.1 LED module with 24 pre-configured LED zones...............................210
12.10.2 LED module with 48 individually configurable LEDs.........................212
12.11
Printer ...............................................................................................................215
12.12
Remote terminal and remote display................................................................218

12.12.1 Remote terminal FT2015 ..................................................................218
12.12.2 Remote display FT2014....................................................................218
12.12.3 Creating and assigning the remote terminal .....................................218
12.12.4 Creating and assigning the remote display.......................................220
12.12.5 Setting properties ..............................................................................221
12.12.6 Configuring the visibility ....................................................................221
12.12.7 Configuring LEDs ..............................................................................223
12.12.8 Assigning the hardware ID to the LED..............................................223
12.12.9 Configuring keys ...............................................................................225
13
'Network' task card.........................................................................................226
13.1
Global network configuration............................................................................226

13.1.1
Creating a stand-alone 'panel' ..........................................................226
13.1.2
Creating networked 'panels'..............................................................227
13.1.3
Configuring a 'Panel' as a router panel .............................................227
13.1.4
Configuring a 'Panel' as GAP............................................................228
13.1.5
Configuring GAP with DHCP server .................................................229
13.1.6
Manual allocation of addresses in the sub-nets................................229
13.1.7
Entering routes for external access to extended networks via GAP.230
13.1.8
Setting network speed for SAFEDLINK ............................................232
13.2
Establishing connection from PC to FS920 network ........................................233
13.3
Checklist for network configuration ..................................................................234

13.3.1
Checklist for network configuration ...................................................234
13.3.2
Checklist in the event of problems with integration...........................235
Index ................................................................................................................236
8
A6V10333423_a_en_US
01/18/2012
About this document

Applicable documents
1 About this document

Goal and purpose
This document describes the configuration of a FS920 fire detection system using the
engineering tool kit FX7230.
Scope
The information in the documents A6V10333380 and A6V10333434 is prerequisite for
configuration of the fire detection system with the engineering tool set FX7230. See
chapter 'Applicable documents'.
This document is valid for the market package MP-UL 1.0.
NOTICE
Fire detection system with Ethernet 'Panels' that does not comply with UL-864
No approval or system acceptance
For non-UL compliant features and settings refer to the table in document
A6V10356958, 'FC922/FC924/FT924 Fire Alarm Control Panel, Installation
Instructions'.
Ethernet 'Panels' are not permitted for the market package MP-UL 1.0. There are
however references to Ethernet 'Panels' in Cerberus-Engineering-Tool FXS7212 and
the set of help documents FXS7216.
Do not plan or configure any Ethernet 'Panels'.
Target groups
The information in this document is intended for the following target groups:
Target group
Activity
Commissioning personnel
Maintenance personnel
Recommended qualification
Configures the product at the

place of installation according to
customer-specific requirements.
Checks the product operability
and releases the product for use
by the operator.
Searches for and corrects
malfunctions.
Carries out all maintenance

work.
Checks that the products are in
perfect working order.
Searches for and corrects
malfunctions.
Has obtained suitable specialist training for the

function and for the products.
Has attended the training courses for
commissioning personnel.
Has obtained suitable specialist training for the

function and for the products.
9
A6V10333423_a_en_US
01/18/2012
About this document

Document identification
The document ID is structured as follows:
ID_ModificationIndex_Language_COUNTRY
Example: A6V10315023_a_en_US
Conventions for text marking

Markups
Special markups are shown in this document as follows:
Requirement for a behavior instruction
Intermediate result of a behavior instruction
End result of a behavior instruction
[ X]
Reference to a page number
'Text'
Quotation, reproduced identically
<Key>
Identification of keys
Supplementary information and tips

The 'i' symbol identifies supplementary information and tips for an easier way of
working.
1.1
Document ID
Title
A6V10333401
System description
A6V10333409
Mounting, Installation, Product Data
A6V10333396
Planning
A6V10333421
Inscription Strips
A6V10333434
Commissioning, Maintenance, Troubleshooting
A6V10333380
Operation
A6V10332926
List of compatibility
A6V10356958
Fire Alarm Control Panel, Installation Instructions
10
A6V10333423_a_en_US
01/18/2012
About this document

Technical terms
1.2
Technical terms
Term
Explanation
ASD
Application-specific detection
BBMD
BACnet broadcast management device
BDT
Broadcast device table
BDV
Base data variant
C-NET
Addressed detector circuit
FDT
Foreign device table
GAP
Global access point
IEC
Intelligent environmental compensation
LRC
Lifecycle responsibility concept
NAC
Notification appliance circuit
NFPA
National Fire Protection Association
PMI
Person Machine Interface
RT
Remote transmission
You will find more technical terms and explanations for them in document
A6V10333401, in the 'Glossary' chapter. See chapter 'Applicable documents'.
1.3
History of changes
The table below shows this document's history of changes:
Modification index Edition date
Brief description
First edition
01.2012
11
A6V10333423_a_en_US
01/18/2012
Safety
Safety instructions
2 Safety
2.1
Safety instructions
The safety notices must be observed in order to protect people and property.
The safety notices in this document contain the following elements:
Symbol for danger
Signal word
Nature and origin of the danger
Consequences if the danger occurs
Measures or prohibitions for danger avoidance
Symbol for danger

This is the symbol for danger. It warns of risks of injury.
Follow all measures identified by this symbol to avoid injury or death.
Additional danger symbols
These symbols indicate general dangers, the type of danger or possible
consequences, measures and prohibitions, examples of which are shown in the
following table:
General danger
Explosive atmosphere
Voltage/electric shock
Laser light
Battery
Heat
Signal word
The signal word classifies the danger as defined in the following table:
Signal word
Danger level
DANGER
DANGER identifies a dangerous situation, which will result directly in death or serious injury if
you do not avoid this situation.
WARNING
WARNING identifies a dangerous situation, which may result in death or serious injury if you do
not avoid this situation.
CAUTION
CAUTION identifies a dangerous situation, which could result in slight to moderately serious
injury if you do not avoid this situation.
NOTICE
NOTICE identifies possible damage to property that may result from non-observance.
12
A6V10333423_a_en_US
01/18/2012
Safety
Safety regulations for the method of operation
How risk of injury is presented

Information about the risk of injury is shown as follows:
WARNING
Measures / prohibitions for danger avoidance
How possible damage to property is presented

Information about possible damage to property is shown as follows:
NOTICE
2.2
Measures / prohibitions for danger avoidance

National standards, regulations and legislation
Siemens products are developed and produced in compliance with the relevant
European and international safety standards. Should additional national or local safety
standards or legislation concerning the planning, assembly, installation, operation or
disposal of the product apply at the place of operation, then these must also be taken
into account together with the safety regulations in the product documentation.
Electrical installations
WARNING
Electrical voltage
Electric shock
Work on electrical installations may only be carried out by certified electricians or

by instructed persons working under the guidance and supervision of a certified
electrician, in accordance with the electrotechnical regulations.
Wherever possible disconnect products from the power supply when carrying out
commissioning, maintenance or repair work on them.
Lock volt-free areas to prevent them being switched back on again by mistake.
Label the connection terminals with external voltage using a 'DANGER External
voltage' sign.
13
A6V10333423_a_en_US
01/18/2012
Safety
Route mains connections to products separately and fuse them with their own,
clearly marked fuse.
Fit an easily accessible disconnecting device in accordance with IEC 60950-1

outside the installation.
Produce earthing as stated in local safety regulations.
Assembly, installation, commissioning and maintenance
If you require tools such as a ladder, these must be safe and must be intended for
the work in hand.
When starting the fire control panel ensure that unstable conditions cannot arise.
Ensure that all points listed in the 'Testing the product operability' section below are
observed.
You may only set controls to normal function when the product operability has been
completely tested and the system has been handed over to the customer.
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 bodies which will receive the
corresponding alarms.
Modifications to the system layout and products

Modifications to the system and to individual products may lead to troubles,
malfunctioning and safety risks. Written confirmation must be obtained from Siemens
and the corresponding safety bodies for modifications or additions.
Modules and spare parts
Components and spare parts must comply with the technical specifications defined
by Siemens. Only use products specified or recommended by Siemens.
Only use fuses with the specified fuse characteristics.
Wrong battery types and improper battery changing lead to a risk of explosion.
Only use the same battery type or an equivalent battery type recommended by
Siemens.
Batteries must be disposed of in an environmentally friendly manner. Observe

national guidelines and regulations.
14
A6V10333423_a_en_US
01/18/2012
Safety
Standards and directives complied with
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:
2.3
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.
Standards and directives complied with

A list of the standards and directives complied with is available from your Siemens
contact.
2.4
Release Notes
Limitations to the configuration or use of devices in a fire detection installation with a
particular firmware version are possible.
WARNING
Limited or non-existent fire detection
Personal injury and damage to property in the event of a fire.
Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.
NOTICE
Incorrect planning and/or configuration
Important standards and specifications are not satisfied.
Fire detection installation is not accepted for commissioning.
Additional expense resulting from necessary new planning and/or configuration.
Read the 'Release Notes' before you plan and/or configure a fire detection
installation.
Read the 'Release Notes' before you carry out a firmware update to a fire
detection installation.
15
A6V10333423_a_en_US
01/18/2012
Installation
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
CD drive R/W
Available
Network connection
Ethernet RJ45
Screen resolution
1024 x 768
Colors
65535
Software
Operating system
Windows 2000, Windows XP, Windows Vista (32-bit version

only), Windows 7
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.
3.2
Installing the engineering tool set

When the engineering tool kit FX7230 is installed, the following components are
installed:
Firmware package FXS7211
Cerberus-Engineering-Tool FXS7212
Base data variant (BDV) FXS2004
Set of help documents FXS7216
Periphery update package FXS2007
When the Cerberus-Engineering-Tool 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
Persistent routes
16
A6V10333423_a_en_US
01/18/2012
Installation
Installing the engineering tool set
Installing the engineering tool kit FX7230

1. Run the installation file.
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.
You can change the following standard installation paths during installation:
Target directory
C:\Program Files\Siemens\F-FX7230\[Version] 1
Common data directory

C:\Documents and Settings\All Users\Application
Data\Siemens\F-FX7230\[Version] 1
Log file directory

Data\Siemens\F-FX7230\[Version] 1\Logfiles
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 log file directory via the start menu as follows:
Start > All Programs > Siemens > F-FX7230 > [Version] 1 > Logfiles
1
[Version] = Version of the software, e.g. US_en_1-V1

See also
Engineering tool set: File name and version [ 26]
Installing several different engineering tool kits [ 25]
17
A6V10333423_a_en_US
01/18/2012
Installation
IP settings for several network cards
3.3
IP settings for several network cards

To connect to a 'Panel' via the FS920 network or directly to the 'Panel', 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 'Panel', the standard gateway for the
Intranet/Internet can be overwritten when initializing a 'Panel' or disconnecting a
connection to a 'Panel'.
You can specify the IP settings for the connection to the FS920 network manually.
For manually specified IP settings for the FS920 network, there is no conflict with a
DHCP server in the FS920 network.
Manually specifying IP settings

1. Change the IP settings for the network card with which you are establishing the
connection to the FS920 network from DHCP to manual.
2. Enter one of the following IP addresses.
-
For direct connection to the 'Panel': 192.168.200.5 / 255.255.255.0
For access via the FS920 network: 192.168.201.5
IP settings are manually specified.

Network settings for the Intranet/Internet are not overwritten.
If you have manually specified the IP settings for the FS920 network, you must also
change the manually specified network settings when changing the connection
between a direct connection to the 'Panel' and access via FS920 network.
18
A6V10333423_a_en_US
01/18/2012
Installation
Starting the software
3.4
Starting the software

You can start the software as follows:
Click the software symbol on the desktop.
In the task bar, click on 'Start' > 'Programs' > 'Siemens' > 'FX7230' > [Version] 1 >
'F-FXS7212'.
[Version] = Version of the software
If you are starting Cerberus-Engineering-Tool for the first time, you will need to load the
licenses. Otherwise the functions of Cerberus-Engineering-Tool are not available.
License check
The licenses are checked when Cerberus-Engineering-Tool 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 CerberusEngineering-Tool has been started for the first time.
Message that the validity period is over.
Warning that the validity will expire.
Objection that the licenses have been manipulated, e.g. date changed on the PC.
See also
Lifecycle Responsibility Concept (LRC) [ 20]
3.5
Exiting the software

You can exit the software as follows:
In the menu bar, click on 'File' > 'Exit'.
Click on the 'X' button in the title bar.
If you have made changes in the software and not saved these, a window opens
asking 'Do you want to save the changes?'.
19
A6V10333423_a_en_US
01/18/2012
Software administration
Lifecycle Responsibility Concept (LRC)
4 Software administration
4.1

The Lifecycle Responsibility Concept (LRC) regulates licensing and 'Site' data storage.
The LRC web database, a web application in Cerberus-Engineering-Tool, is used to do
this.
Licensing
Each organizational unit receives its own licenses for its users of CerberusEngineering-Tool. 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 licenses expire, the user must renew them.
Two licenses are required:
The primary license makes it possible to work with Cerberus-Engineering-Tool.
The default license enables the communication between the 'Panels'.
'Site' data storage

The user of Cerberus-Engineering-Tool 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
Cerberus-Engineering-Tool.
See also
Saving a parts list for the 'Site' [ 25]
4.1.1
Loading / renewing licenses

You can use the 'Retrieve your licenses.' option to load licenses.
The 'Renew your licenses.' option can be used to renew licenses soon before or after
they expire. You can select this option at the earliest 60 days before the licenses'
expiry date.
Loading or renewing a licenses online

You have an account on the LRC web server.
You are a member of a registered organizational unit.
You have received an e-mail with the required information (URL, user name,
password).
20
A6V10333423_a_en_US
01/18/2012
1. In the menu bar, click on 'File' > 'Manage licenses'.

The following window is opened:
2. Select 'Manage your licenses online (recommended).'.

3. Select 'Retrieve your licenses.' and/or 'Renew your licenses.'.
4. Click on 'Next'.
5. Enter your user name and the password and click on 'Finish'.
The connection with the LRC web server is established.
The user name and the password are authenticated.
The licenses for the corresponding software version of Cerberus-EngineeringTool are generated.
The following window is opened and the installed licenses are listed:
21
A6V10333423_a_en_US
01/18/2012
6. Click on 'Restart tool'.
Cerberus-Engineering-Tool is restarted.
Loading or renewing licenses offline

If you are not connected to the LRC web server, the licenses must be loaded or
renewed offline.
You know the installation code. You will find the installation code under 'Help' >
'About'.
1. Contact the HQ Administrator by phone or email to apply for the licenses.
The HQ Administrator then checks the membership of your organizational unit
and verifies whether other installation codes are registered with the same user
account.
The HQ Administrator creates the identities, generates the licenses and sends
you the files on a CD or by e-mail.
22
A6V10333423_a_en_US
01/18/2012
3. Select 'Manage your licenses offline (for this option, please contact your
administrator).' and 'Install your licenses.'.
4. Click on 'Next'.
The following window is opened and the installation code is displayed.
5. Click on 'Browse' and select the license file.

6. Click on 'Finish'.
The licenses for the corresponding software version of Cerberus-EngineeringTool are generated.
The following window is opened and the installed licenses are listed:
Cerberus-Engineering-Tool is restarted.
23
A6V10333423_a_en_US
01/18/2012
4.1.2
Returning licenses
If Cerberus-Engineering-Tool 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
Cerberus-Engineering-Tool is still installed and the licenses have not expired.
The previously used PC is not defective.

The 'License wizard' window opens.
2. Highlight 'Manage your licenses online (recommended).'.
3. Highlight 'Uninstall the current licenses.'.
4. Click on 'Next'.
The 'License wizard' window for entering the password is opened.
5. Enter your user name and the password and click on 'Finish'.
The connection to the LRC web server is established.

The user name and the password are authenticated.
The LRC web server is informed when the licenses are returned.
The installation code is deleted from the user profile.
The license data on the hard disk is deleted.
The 'License wizard' window is opened along with the confirmation message.
Cerberus-Engineering-Tool is restarted with the message 'License 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.
The HQ Administrator accepts the change and changes the installation code in
the user profile on the LRC web server.
2. Uninstall Cerberus-Engineering-Tool.
24
A6V10333423_a_en_US
01/18/2012
4.1.3
Viewing license information

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

Information about the installed licenses is displayed, e.g. expiry date and license
owner.
4.1.4
Installing several different engineering tool kits

Several engineering tool kits with different country or language versions can be
installed on one PC.
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 kit A.
2. Load the licenses for organizational unit A from the LRC web server for
engineering tool kit A.
3. Install engineering tool kit B.
4. Load the licenses for organizational unit B from the LRC web server for
engineering tool kit B.
4.1.5
Saving a parts list for the 'Site'

You can back up a parts list of the 'Site' currently loaded by loading the data on to the
LRC web server.
Select 'File' > 'Transfer traceability report' from the menu bar.
Cerberus-Engineering-Tool is connected with the LRC web server.
The parts list of 'Site' currently loaded is loaded on to the LRC web server.
25
A6V10333423_a_en_US
01/18/2012
Engineering tool set: File name and version
4.2
Engineering tool set: File name and version

File name format:
[Prefix]-[Country]_[Language]_[Sales channel]-[Meta data version].R.exe
Example: F-FX7230-US_en_2-4.0.0.R.exe
4.3
Designation
Coding
Prefix
F-FX7230
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
Release
.exe
File extension, upper- or lower-case letters
BDV: File name and version

File name format:
[Prefix]-[Country]_[Language]_[Sales channel]-[Meta data version]_[BDV
version]([Variant]).eBDV
Example: F-FXS2004-US_en_2-41.6.1_01.eBDV
Designation
Coding
Prefix
F-FXS2004
Country
Language
Sales channel
Meta data version

BDV version
Double digit, numerical with leading zero when applicable
Variants
Optional, single digit, only CAPS
.eBDV
File extension of every BDV, upper- 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 arrangement cannot be used by
the software.
See also
BDV import [ 28]
26
A6V10333423_a_en_US
01/18/2012
Firmware: File name and version
4.4
Firmware: File name and version

File name format:
[Prefix]-[Country]_[Language]_[Sales channel]-[Meta data
version]_([Variant])_[Firmware version].zip
Example: F-FXS7211-XU_xx_x-41.6.1_00.zip
Designation
Coding
Prefix
F-FXS7211
Country

XU: Several countries
Language

xx: All languages
Sales channel

x: All sales channels
Meta data version

Variants
Optional, multiple digits, upper- or lower-case letters, numbers and

'-'
Firmware version
Double digit, numerical with leading zero when applicable
.zip
File extension of every firmware, upper- 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 arrangement cannot be
used by the software.
See also
Firmware import [ 28]
27
A6V10333423_a_en_US
01/18/2012
BDV import
4.5
BDV import
A BDV can be made available in Cerberus-Engineering-Tool by clicking on the 'File' >
'Import new BDV' 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 are asked whether you want 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 want to create any 'Sites' with old BDVs or convert 'Sites' into an
old BDV.
See also
BDV: File name and version [ 26]
4.6
Firmware import
Firmware can be made available in Cerberus-Engineering-Tool by clicking on the 'File'
> 'Import new FW package' menu item. During this import process, a firmware is saved
into the standard firmware path from a selectable location.
See also
Firmware files settings [ 37]
Firmware: File name and version [ 27]
4.7
License key
A license key can be installed in every 'Panel'. The FCA2012 license key enables the
'Cerberus-Remote' function.
4.8
Calling up log files

You can open the log file directory as follows:
Via the Start menu

Start > All Programs > Siemens > F-FX7230 > [Version] 1 > Logfiles
In Windows Explorer
Data\Siemens\F-FX7230\[Version] 1\Logfiles
1
[Version] = Version of the software
28
A6V10333423_a_en_US
01/18/2012
GUI
Overview of the program window
5 GUI
5.1
Overview of the program window
1
2
3
8
Program window
Title bar
Detail editor
Menu bar
Hyperlinks
Toolbar
Status bar
Task cards
Tree
Table
29
A6V10333423_a_en_US
01/18/2012
GUI
Menu bar
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
Action
File
New site
Create new 'Site'
Open
Open existing configuration of a 'Site'
Save
Save current configuration of 'Site'
Save as ...
Save current configuration under a new name
Site properties
'View and edit 'Site' properties
Close
Close configuration currently open
Manage licenses
Load, renew or return license
Import new BDV
Import BDV
Import new FW package
Import firmware
Import new help
Import Help file
Transfer traceability report
Load parts list of 'Site' currently loaded on to the LRC server
Compare sites
Compare configurations or BDVs
Reports
Create reports about 'Site'
CSV import
Import data in CSV format
CSV export
Export data in a CSV file
Show CSV import log
Viewing the CSV import log
[List of the recently opened 'Sites'] Open one of the recently opened 'Sites'
Edit
Exit
Exit Cerberus-Engineering-Tool
New panel
Create new 'Panel'
New panel with address
Create new 'Panel' with individual address
New element
Create new element
Undo
Undo last action
Redo
Restore action that was undone last
Copy
Copy elements or values
Cut
Cut elements or values
Paste
Paste elements or values
Paste without children
Paste element without child element
Delete
Delete element
Replace element
Replacing element
Change element address: -1
Decrease the address of the selected element as well as all higher

elements by one
30
A6V10333423_a_en_US
01/18/2012
GUI
Menu bar
Main menu
View
Commissioning
Submenu
Action
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 configuration of 'Site'
Show conversion log
View conversion log
Find
Search for elements using various search criteria
Find and replace
Search for and replace elements using various search criteria
Find next
Jump from one hit to the next
Show problems
Displaying an element's problems
Show all problems
Displaying problems for the entire 'Site'
Assign
Open 'Assign' window for assigning elements
Unassign
Delete link
Create and Assign
Open 'Assign' window for creating and assigning devices at the same
time
Disconnect
Interrupt communication to 'Panel'
Initialize panel
'Initialize 'Panel'
Transfer PC -> site
Load configuration of 'Site' to the 'Panel'
Transfer site -> PC
Load configuration of 'Site' to the PC
Create backup embedded

configuration
Create back-up of 'Site' configuration
Transfer site event memory -> PC Load event memory of 'Site' to the PC
Transfer site log files -> PC
Load log files from selectable 'Panels' to the PC
Diagnostics report
Create reports about 'Site'
FW update main CPU
Update firmware of the main CPU
FW update additional CPUs
Update the firmware of the additional CPUs
FW update main and additional

CPUs
Updating the firmware of the main CPU and the additional CPUs
Connect
Connect Cerberus-Remote
Connect to favorite
Connect Cerberus-Remote to 'Panel' from the favorite list
Add to favorites
Add connected 'Panel' to favorite list
Disconnect
Disconnect Cerberus-Remote
Reset network configuration
Set standard values for the IP addresses and network masks of all
sub-nets. All manual changes to these values are overwritten.
Reset sub-net network

configuration
Set standard values for the IP addresses and network masks of the
selected sub-net. All manual changes to these values are overwritten.
Options
Preferences
Set software's pre-settings
Help
Help
View documentation
View additional documents
View additional documents
About
View information about installed version
Update
Cerberus-Remote
Network
31
A6V10333423_a_en_US
01/18/2012
GUI
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
children'
Pastes copied elements without child elements
'Delete'
Deletes selected elements/subtrees
'Undo'
Undoes the last action
'Redo'
Restores the action last undone
'New panel'
Opens and closes the 'New panel' window
'New element'
Opens and closes the 'New element' window
'Find'
Opens the 'Find' window
'Help'
Opens the documentation overview
'Transfer PC ->
site'
Loads the configuration of the 'Site' to the 'Panel'
'Transfer site ->

PC'
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 creating
and assigning devices at the same time
5.4
Help and tooltips

There are two sources of information in Cerberus-Engineering-Tool:
Help
Tooltips
32
A6V10333423_a_en_US
01/18/2012
GUI
Help and 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.
WWW
HTML help
All documents which are marked with the following symbol are part of this HTML help:
System Description
A6V10333401
Planning
List of compatibility
A6V10333396
A6V10332926
Peripheral Devices
FC20xx / FT2050
Installation Instructions A6V10356958
Installation Instructions
Mounting / Installation / Product Data
A6V10333409
Inscription Strips
A6V10333421
Commissioning / Maintenance / Troubleshooting
A6V10333434
Configuration
A6V10333423
FC92x / FT924 Operation Manual

A6V10333380
FT2014 Remote Display

FT2015 Remote Terminal
A6V10329825
A6V10315025
Operation
Manuals
FC92x / FT924
(simple) A6V10333413
Graphic with an overview of the documentation
33
A6V10333423_a_en_US
01/18/2012
GUI
Help and tooltips
Tooltips
Tooltips are windows within the software with context-sensitive detail information.
Tooltips are shown when the mouse pointer is moved over an element designation or
element property in the detail editor.
Example of tooltip for an element property
To display an element's tooltip, proceed as follows:

1. Highlight an element in the tree view.
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 top
tab.
The tooltip is displayed.
Example of tooltip for an element
34
A6V10333423_a_en_US
01/18/2012
GUI
Pre-settings
5.5
Pre-settings
In the 'Preferences' window, you can specify software pre-settings.
The pre-settings are described in the following chapters.
Specifying pre-settings
1. In the menu bar, click on 'Options' > 'Preferences'.
The 'Preferences' window opens.
2. Click on a view on the left of the window.
The pre-settings for this view are displayed on the right of the window.
3. Select the pre-settings you want and click on 'Apply'.
The pre-settings are saved.
Restoring default settings

1. Click on the view you want on the left of the 'Preferences' window.
2. Click on 'Restore Defaults'.
The default settings for 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, the common data
directory is in the following path:
C:\Documents and Settings\All Users\
Application Data\Siemens\F-FX7230\[Version] 1
1
[Version] = Version of the software, e.g. US_en_1-V1
The common data directory contains the following subfolders:
'Additional_Documents'
'BDV'
'FS20_SW'
'Help'
'Logfiles'
'Sites'
'Technicalfiles'
35
A6V10333423_a_en_US
01/18/2012
GUI
Pre-settings
5.5.1
Commissioning settings
Commissioning settings
The following can be set in the 'Commissioning preferences' view:

'Automatic backup embedded configuration': If the checkbox is checked, the
configuration currently stored in the 'Site' is loaded to the PC and stored as the backup. This process is undertaken automatically each time you use the 'Transfer PC ->
site' command to load a configuration from the PC to the 'Panel'.
You will find more information about creating a back-up file in document
A6V10333434. See chapter 'Applicable documents'.
5.5.2
Quicktext and mouse wheel settings
Quicktext and mouse wheel settings
The following can be set in the 'Editing preferences' view:
'Quicktext proposals filtration style': To make entering texts in CerberusEngineering-Tool 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 '.properties' format.
'Export proposals': Export proposed texts in '.properties' format.
'Ignore mouse wheel': If you check this checkbox, the mouse wheel of the
computer mouse is deactivated. This prevents settings in a dropdown list being
unintentionally changed if you are scrolling in the detail editor with the mouse
wheel.
36
A6V10333423_a_en_US
01/18/2012
GUI
Pre-settings
The 'Ignore mouse wheel' setting only applies when you select a new element in the
structure tree. The setting is not adopted for the element currently selected.
See also
Entering quicktext [ 63]
5.5.3
Firmware files settings
Firmware files settings
In the 'Firmware package preferences' view, you can define the path to the folder in
which the firmware files are stored. This folder also stores files that are imported using
the 'Import new FW package' function.
See also
Firmware import [ 28]
5.5.4
Internet settings
Internet settings
The 'Internet preferences' view contains information for accessing the LRC web server
via the Internet. Internet access is used to load, renew and return licenses. You have
three options:
Without proxy: The checkbox for 'Enable proxy' is not checked.
Via proxy: The 'Enable proxy' checkbox is checked. The information on 'Proxy
host:' and 'Proxy port:' is provided by the IT administrator.
Via proxy with authentication: The 'Enable proxy' and 'Enable proxy authentication'
checkboxes are checked.
37

A6V10333423_a_en_US
01/18/2012
GUI
Pre-settings
Please ask your IT administrator about the access method you should use.
See also
5.5.5
Settings for LRC web server
Settings for LRC web server
The following can be set in the 'LRC server preferences' 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.
See also
Loading / renewing licenses [ 20]
Returning licenses [ 24]
38
A6V10333423_a_en_US
01/18/2012
GUI
Pre-settings
5.5.6
General program settings
General program settings
The following can be set in the 'Preferences' view:
'Number of recently opened files:': Number of files that were recently opened and
that are displayed in the 'File' menu.
'Automatically open last site at tool startup': If the checkbox is checked, the 'Site'
that was opened last is loaded when the program starts.
'Help file:': Path to the folder with the help files.
'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.
'Auto-selection of the type in the Assign dialog': This setting relates to behavior in
the 'Assign dialog', 'New cause dialog' and 'New effect dialog' windows. If the
checkbox is ticked, the first element which can be assigned is automatically looked
for and displayed in the window. If the checkbox is not ticked, you first need to
select a category on the left of the window. Then the first element of this category
which can be assigned is displayed on the right of the window.
See also
Assigning elements [ 67]
39
A6V10333423_a_en_US
01/18/2012
GUI
Pre-settings
5.5.7
Cerberus-Remote settings
Cerberus-Remote settings
The following can be set in the 'Cerberus-Remote preferences' view:
'Connect Cerberus-Remote automatically when opening Cerberus-Remote task

card': When the checkbox is checked, Cerberus-Remote is automatically
connected when you open the 'Cerberus-Remote task card. The connection is
established with the last connected 'Panel'. When Cerberus-Engineering-Tool is
started, the connection must be manually established once.
'Cerberus-Remote favorite list': You can store frequently used 'Panels' in this list
with the connection details. The 'Panels' in the favorite list are listed in the
'Cerberus-Remote' > 'Connect to favorite' menu. In this way, you can quickly and
easily connect Cerberus-Remote to 'Panels'.
'Add new favorite': Add new 'Panel' to favorite list.
'Edit selected favorite': Edit 'Panel' in the favorite list.
'Delete selected favorite': Delete 'Panel' from the favorite list.
Adding a new 'Panel' to the favorite list

1. Click on 'Add new favorite'.
The 'Add new favorite panel' window opens.
2. Enter the name, IP address, 'Panel' ID and PIN of the 'Panel'.
3. Click on 'OK'.
40
A6V10333423_a_en_US
01/18/2012
GUI
Pre-settings
The 'Panel' is added to the favorite list.

In the 'Cerberus-Remote' task card, the 'Panel' is listed in the 'Cerberus-Remote' >
'Connect to favorite' menu.
See also
Connecting Cerberus-Remote [ 84]
Cerberus-Remote [ 49]
5.5.8
'Site' settings
'Site' settings
The following can be set in the 'Site preferences' 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.
41
A6V10333423_a_en_US
01/18/2012
GUI
Task cards
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.
Task cards
Cerberus-Engineering-Tool has the following task cards:
'Hardware': Configuration and display of all hardware components of a 'Site'
'Detection': Configuration and display of detection applications
'Control': Configuration and display of control applications
'Operation': Configuration and display of global 'Site' settings and operating

properties of all operation and indication devices of the 'Site'
'Network': Configuration and display of the network
'Cerberus-Remote': A 'Panel' connected to the PC can be viewed or viewed and

operated with 'Cerberus-Remote'.
See also
Overview of the program window [ 29]
42
A6V10333423_a_en_US
01/18/2012
GUI
Task card components
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 about this in the chapter 'Designation of problems and
displaying errors [ 47]'.
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 cannot 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 shown in various tabs. If an element is assigned, an
additional tab with the name of the assigned task card is displayed. 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.
43
A6V10333423_a_en_US
01/18/2012
GUI
Scroll bars and window separating lines
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.
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 elements in the subtree of an element, proceed as follows:
Highlight the element and press <*> or </> on the keypad.
Highlight the element and click on the '+' or '' buttons in the top right of the
structure tree.
Buttons to expand or collapse a subtree
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'.
Multiselection
44
A6V10333423_a_en_US
01/18/2012
GUI
Navigating within the program window
Because of dynamic loading you can select a maximum of eight 'Panels' in the tree
and table at the same time.
See also
Dynamic loading [ 52]
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 for
Cerberus-Engineering-Tool. 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 about the operating elements in the following chapters.
5.11.1
Navigating with task cards

Click on a task card to switch to the corresponding perspective.
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. If you click on
a hyperlink, the view switches to the assigned element.
Detail editor with hyperlink
See also
45
A6V10333423_a_en_US
01/18/2012
GUI
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 subtree
Left or right arrow keys
Navigating between nodes in the

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)
5.12
Editing cell in the table
<F2>
Navigating between the tabs in the

detail editor
Navigating between the parameters

of a tab in the detail editor
<Tab> or <Shift> + <Tab>
<Ctrl> + <Page Up> or <Ctrl> + <Page Down>

Arrow keys if the tabs are highlighted
Status bar
The following information is displayed on the status bar:
The error description of a selected element.
A symbol for information on the connection status between the 'Panel' and the PC.
Status bar
46
A6V10333423_a_en_US
01/18/2012
GUI
Designation of problems and displaying errors
5.13

If errors have occurred during configuration, these errors are marked in the tree view
with a red exclamation mark.
A yellow exclamation mark next to an element indicates a warning, e.g. a missing link.
An error prevents loading to the 'Panel'.
A 'Site' can be stored on the PC even if there is an error.
Problem displayed in the tree view

You can display more information about a problem as follows:
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. Use a red or yellow exclamation mark to highlight an element.
2. Select 'View' > 'Show problems' from the menu bar.
The 'Problems' window opens.
In the 'Problems' window, an 'Error', 'Warning', or 'Info' entry concerning the
element selected is displayed.
47
A6V10333423_a_en_US
01/18/2012
GUI
If the highlighted element has just one problem, this problem is described in the
status bar. If the element has several problems, the number of problems is shown in
the status bar.
Status bar with description of problem
Status bar with number of problems
Displaying problems for the entire 'Site'

You can display more information about the problems in the configuration of the entire
'Site' as follows:
1. Select 'View' > 'Show all problems' from the menu bar.
The 'All problems' window opens.
The 'All problems' window displays 'Error', 'Warning', and 'Info' entries relating
to the configuration of the entire 'Site'.
2. To display the element with the problem, double-click on an entry in the 'All
problems' window.
The corresponding task card is opened and the element displayed in the structure
tree.
Displaying problems for the entire site
If you check the 'Invisible' checkbox, problems are displayed in the elements which
are not visible to the user. This may be helpful when troubleshooting with the hotline.
See also
48
A6V10333423_a_en_US
01/18/2012
GUI
Cerberus-Remote
5.14
Cerberus-Remote
Cerberus-Remote is software for the PC which can be used to display the Person
Machine Interface of a 'Panel' on the PC. For example it can be used to access the fire
detection system for maintenance purposes.
Depending on the operating mode, Cerberus-Remote can either be used for display
purposes or for display and operation purposes.
The link between Cerberus-Remote and a 'Panel' can be structured as follows:
Local connection via any 'Panel' in the fire detection system
Connection via the Global Access Point (GAP)
Cerberus-Remote is an integrated part of Cerberus-Engineering-Tool but may also be

installed on a PC as a stand-alone application 'FX7220'.
You will need an installed license key (at least L1) and appropriate authorization from
the 'Panel' in order to use Cerberus-Remote. The license key need only be installed in
the 'Panel' whose Person Machine Interface is to be displayed in Cerberus-Remote.
The connection to a 'Panel' with a license key is also possible via a 'Panel' without a
license key.
Cerberus-Remote has the same visibility as the connected 'Panel'. You can use
Cerberus-Remote in a fire detection installation with networked 'Panels' to gain global
visibility. Just one license key is needed for this per network if the license key is
installed in a 'Panel' with global visibility.
49
A6V10333423_a_en_US
01/18/2012
GUI
Cerberus-Remote
Cerberus-Remote is opened via the 'Cerberus-Remote' task card in the program

window.
Example of Cerberus-Remote in 'Full access (view/operation)' operating mode with a

red frame
The button with the loudspeaker symbol (bottom right in the figure) is used to enable
and bypass an activated buzzer.
However it is only possible to switch the buzzer on and off on the PC and not on the
connected 'Panel'.
The connection with a 'Panel' is shown by the Person Machine Interface (display,
LEDs, keys) transmitted.
The 'Cerberus-Remote access' operation mode is indicated by a red frame around
the Person Machine Interface.
An enable granted for Cerberus-Remote is retained when a 'Panel' restarted.
Cerberus-Remote has the following operation modes:
'Limited access (view only)'
'Full access (view/operation)'
For both operation modes, SintesoView must be enabled on the 'Panel'. In addition, a
license key (at least L1) must be installed.
50
A6V10333423_a_en_US
01/18/2012
GUI
Cerberus-Remote
'Limited access (view only)'

In this operation mode Cerberus-Remote indicates the same as the 'Panel' connected
to it, but you cannot operate the linked 'Panel'.
Cerberus-Remote indicates the display with all indicated texts, all LEDs in their current
state and all buttons.
'Full access (view/operation)'

In this operation mode the connected 'Panel' is visualized as in the 'Limited access
(view only)' operation mode. Additionally, the 'Panel' can be operated with CerberusRemote, while normal operation on the 'Panel' is blocked, but can be reactivated.
As operation on a 'Panel' must have priority, this restriction (blocking) on the 'Panel'
can be cancelled at any time.
Each time an attempt is made to operate on the 'Panel', a dialog is indicated with the
option to abort the connection with Cerberus-Remote.
The LED test also tests the display. The LEDs are not however displayed in
Cerberus-Remote.
See also
Cerberus-Remote settings [ 40]
Connecting Cerberus-Remote [ 84]
51
A6V10333423_a_en_US
01/18/2012
GUI
Dynamic loading
5.15
Dynamic loading
To increase the performance of Cerberus-Engineering-Tool, not all 'Panels' are loaded
to the software at the same time for 'Sites' with more than eight 'Panels'. 'Panels' that
are not loaded are shown in gray and in italics. The 'Panels' are dynamically loaded
and unloaded, depending on the selection. You can load a maximum of eight 'Panels'
at the same time.
The following sections describe dynamic loading in various software functions.
Structure tree view

As soon as a 'Panel' that is not loaded is clicked on, it is loaded. You can highlight a
maximum of eight 'Panels' at the same time. If you highlight more than eight 'Panels',
an error message appears.
Structure tree view with panels that are and are not loaded
History of the 'Panels'

Only the history of the 'Panels' that is currently loaded is displayed in the 'History' tab
of the 'Site properties' window as standard. If you would like to see the history of all
'Panels', click on 'Get panel logs'.
Search function
With the 'Find' and 'Find and replace' functions you can state whether only the loaded
'Panels' or both the loaded and unloaded 'Panels' are included.
52
A6V10333423_a_en_US
01/18/2012
GUI
Dynamic loading

The 'Panels' 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 'Panel' that is not loaded, click on the
'Panel' to load it.
'Assign' function
If elements are assigned using the 'Assign' function, the 'Panels' that are not loaded
are shown in gray. If you would like to assign an element to an element of a 'Panel' that
is not loaded, you must click on the 'Panel' to load it.
Window with panels 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
Finding [ 71]
Finding and replacing [ 73]
Designation of problems and displaying errors [ 47]
Assigning elements [ 67]
Editing the 'Site' properties [ 57]
53
A6V10333423_a_en_US
01/18/2012
Program operation
Creating a 'Site'
6 Program operation
It is possible that Cerberus-Engineering-Tool will start to run slightly slower over time,
e.g. after extensive copying/pasting or when creating/deleting a lot of 'Panels'. If this
happens, we would recommend reloading the 'Site'. Cerberus-Engineering-Tool will
then work normally.
6.1
Creating a 'Site'
When you create a 'Site', you have the following options:
Loading existing 'Site' in Cerberus-Engineering-Tool
Creating a 'Site' based on an existing configuration
Create new 'Site'
You will find information about the procedures in the following chapters.
6.1.1
Loading an existing 'Site'

The 'Site' already contains a configuration.
The PC is connected to a 'Panel'.
1. Select 'File' > 'New site' from the menu bar or click on the following button in the
toolbar:
The first 'Create new site' window opens.
2. Select the 'Transfer from panel(s)' option.
3. Click on 'Next'.
The 'Site' configuration is loaded to Cerberus-Engineering-Tool.
The second 'Create new site' window opens once the upload has successfully
completed.
4. Enter the necessary information, e.g. the 'Site' name.
5. Click on 'Create'.
The 'Site' is created in Cerberus-Engineering-Tool.
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:
<>/\|:?*"%#
54
A6V10333423_a_en_US
01/18/2012
Program operation
Creating a 'Site'
The progress of the upload is shown in the status bar.

If communication between the PC and 'Panel' is interrupted, a message indicating
that the upload has been aborted is displayed.
See also
6.1.2
Creating 'Site' based on existing configuration

The configuration file to be copied is present on the PC.
The configuration file name ends with '.fsc'.
1. Select 'File' > 'New site' from the menu bar or click on the following button in the
toolbar:
The 'Create new site' window opens.
2. Select the 'Create based on existing configuration' option.
3. Under 'Existing configuration:', select the configuration file to be copied.
4. Click on 'Next'.
The configuration file is copied.
The 'Site properties' window opens.
6. Click on 'OK'.
The 'Site' is created.
NOTICE
<>/\|:?*"%#
See also
55
A6V10333423_a_en_US
01/18/2012
Program operation
Creating a 'Site'
6.1.3
Creating a new 'Site'

1. Select 'File' > 'New site' from the menu bar or click on
The first 'Create new site' window opens.
in the toolbar.
2. Select the 'Create new' option.

3. Select the BDV.
4. Click on 'Next'.
The BDV is loaded.
The second 'Create new site' window opens.
6. Click on 'Create'.
The 'Site' is created.
NOTICE
<>/\|:?*"%#
See also
56
A6V10333423_a_en_US
01/18/2012
Program operation
Creating a 'Site'
6.1.4
Editing the 'Site' properties

When a 'Site' is loaded, the 'Site' properties can be edited.
Editing properties
Click on the 'File' > 'Site properties' menu item or use the shortcut <Crtl> + <I>.
The 'Site properties' window opens.
Window for editing the 'Site' properties
The 'Site' name and assigned BDV are shown in the 'Site properties' window.
Additional information can be found or entered in the 'Creator:', 'Customer:', and
'Contact:' text fields. Fields marked with '*' must be completed.
A comment can be entered in the 'Comment' tab. The comment must not exceed 250
characters.
The 'History' tab contains a log file for the 'Site'.
NOTICE
<>/\|:?*"%#
57
A6V10333423_a_en_US
01/18/2012
Program operation
Creating a 'Panel'
6.2
Creating a 'Panel'
When creating the first 'Panel', you can choose between 'Standalone panel' and
networked 'Panels' of types 'SAFEDLINK panel' and 'Ethernet panel'.
NOTICE
Instructions'.
When a 'SAFEDLINK panel' is created, it may already be assigned to a specific

SAFEDLINK sub-net.
Additional 'Panels' can only be created as networked.
Window for creating a 'Panel'
'Panel': Creating
A 'Site' is created.
1. Open the 'New panel' window. This can be done in the following ways:
Click on the
Select 'Edit' > 'New panel' from the menu bar.
- Right-click in the tree view and select 'New panel' in the context menu.
The 'New panel' window opens above the table.
2. Select a 'Panel' from the 'Type:' selection list.
3. Select a template from the 'Template:' selection list.
4. Select the corresponding network for networked 'Panels'.
5. Select the number of new 'Panels' in the 'Amount:' field.
6. Click on 'Add'.
The 'Panel' is created.
58
A6V10333423_a_en_US
01/18/2012
Program operation
Creating a 'Panel'
Networked 'Panels'
You will find details about how to create networked 'Panels' in the chapter 'Creating
networked 'panels' [ 227]'.
'Creating a 'Panel' with individual address

This function is normally called up when migrating from old systems if a particular
address is to be assigned to a 'Panel'.
Once the 'Panel' has been created, the address can no longer be changed.
1. Select 'Edit' > 'New panel with address' from the menu bar.
The 'New panel with address' window opens.
2. Set the properties you want and click on 'Add'.

The 'Panel' is created with the address entered.
See also
'Network' task card [ 226]
Creating networked 'panels' [ 227]
59
A6V10333423_a_en_US
01/18/2012
Program operation
Creating an element
6.3
Creating an element
You can create an element in the following ways:
In the 'New element' window
Using the context menu in the tree view
In the table
Creating an element in the 'New element' window
Window for creating an element
A 'Panel' is created.
An element is selected for which a sub-element can also be displayed.
The 'Site' node is not selected.
1. Open the 'New element' window. This can be done in the following ways:
Click on the
Select 'Edit' > 'New element' from the menu bar.
- Right-click in the tree view and select 'New element' in the context menu.
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'.
The element is created.
60
A6V10333423_a_en_US
01/18/2012
Program operation
Creating an element
Creating an element using the context menu in the tree view

1. Right-click in the tree view on an element under which you want to create an
element.
2. Select 'New' in the context menu and then select the element you want and the
template.
Creating an element using the context menu
Creating an element in the table

1. In the tree view, select an element 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.
Creating an element in the table
61
A6V10333423_a_en_US
01/18/2012
Program operation
Replacing an element
6.4
Replacing an element
You can replace the template for an element with another template of the same
element type. In certain cases, you can also replace an element with one of a different
type.
Replacing element
1. Highlight the element you want to replace in the tree view.
2. Select 'Edit' > 'Replace element' from the menu bar.
The 'Replace element ' window opens.
3. Select another element type or another template.
4. Click on 'Replace'.
The element is replaced.
5. Check the settings and the links of the new element and make changes if
necessary.
6.5
Deleting an 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:
6.6
Using the button
in the toolbar
Using 'Edit' > 'Delete' in the menu bar
Via the context menu
With <Delete>
Editing an element
You can edit elements in the table or detail editor. It is not possible to edit in the tree
view.
Editing an element in the table

1. Select the parent element of the element you want to edit in the tree view.
The child element and its properties are displayed in the table.
2. Edit the element properties in the table.
Editing an element in the detail editor

1. Select the element you want to edit in the tree view.
The properties of the highlighted element are displayed in the detail editor.
2. Edit the properties you want.
62
A6V10333423_a_en_US
01/18/2012
Program operation
Copying properties in the table
Editing several elements at the same time

1. Select the elements you want to edit in the tree view.
The properties present in all highlighted elements are displayed in the detail
editor.
2. Edit the properties you want.
The properties are changed in all highlighted elements.
6.7
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.
The cell is marked by a frame.
2. Guide the mouse pointer to the bottom right corner of the highlighted cell.
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.
Highlighted cells have a gray background.
4. Release the pressed left mouse button.
The copying process is complete.
6.8
Entering quicktext
When writing customer texts and counter-measures texts 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
Quicktext and mouse wheel settings [ 36]
6.9
Copying, cutting and pasting an element

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, e.g. the
element's address, are updated depending on the new position.
63

A6V10333423_a_en_US
01/18/2012
Program operation
Copying, cutting and pasting an element
Conditions
Elements that are generated automatically when creating parent elements can not
be copied/cut separately.
Cross links and reference links are not copied.
Copying/cutting is only possible within a 'Site'.
When copying/cutting and pasting between two 'Panels', both 'Panels' must be
loaded.
Copying element
You can copy an element as follows:
Using the button
in the toolbar
Using 'Edit' > 'Copy' in the menu bar
With the shortcut <Ctrl> + <C>
Pasting copied element with subtree

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

You can paste a copied element without subtree as follows 1:
Using the button
in the toolbar
Using 'Edit' > 'Paste without children' in the menu bar
1 If the element has fixed child elements, these are also inserted with the 'Paste without
children' function. Example: A detector cannot be inserted without the child element
'Sensor'.
Cutting element
You can cut an element as follows:
Using the button
in the toolbar
Using 'Edit' > 'Cut' in the menu bar
With the shortcut <Ctrl> + <X>
Pasting cut element

You can paste a cut element as follows:
Using the button
in the toolbar
Using 'Edit' > 'Paste' in the menu bar
With the shortcut <Ctrl> + <V>
64
A6V10333423_a_en_US
01/18/2012
Program operation
Moving an element
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 'Panel' to another 'Panel' if both
'Panels' are loaded.
An element can only be moved within the same task card.
Handling links when moving

Moving elements inside a 'Panel':
The links to the hardware are also moved.
The links to the control are also moved.
Moving elements between different 'Panels':
6.11
The links to the hardware are deleted.
The links to the control and detection elements are also moved.
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 'Zone' level.
Depending on the element category, the elements are re-addressed across the system
or only within the parent element. When you e.g. re-address a 'Zone', 'Zones' are readdressed across the system. When you re-address a logical channel in a 'Zone', only
the logical channels within the 'Zone' are re-addressed. Before elements are readdressed across the system, a message that you have to confirm is displayed.
65
A6V10333423_a_en_US
01/18/2012
Program operation
Re-addressing elements
Decreasing an address by 1
Gaps are produced in the address sequence when you delete, cut/paste, move or readdress elements throughout panels. To close gaps in the address sequence, proceed
as follows:
1. Highlight the element after the gap in the tree view.
2. Select 'Edit' > 'Change element address: -1' from the menu bar.
Depending on the highlighted element, the following window is displayed:
3. Click on 'Yes'.
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.
Increasing an address by 1
To insert an element, e.g. another 'Zone', in a certain position in the address
sequence, proceed as follows:
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.
Depending on the highlighted element, the following window is displayed:
3. Click on 'Yes'.
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.
A gap is created in the address sequence.
4. Create a new element and enter the address that corresponds to the gap in the
detail editor.
The new element is moved to the position of the gap.
66
A6V10333423_a_en_US
01/18/2012
Program operation
Assigning elements
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.
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 task cards.
The 'Assign' function cannot be called up in the 'Hardware' task card.
Window for assigning elements
1 List with assignable event categories, inputs and outputs

2 Dropdown list to select the task card
3 Checkbox to activate search by ID no. (4)
4 Dropdown list to select the ID no.
67
A6V10333423_a_en_US
01/18/2012
Program operation
Creating and assigning devices
5 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 text, grayed out: element that can be assigned
Inverted text, blue: highlighted element
6 'Always jump to next assignable element' checkbox: If the box is checked, the next
assignable element is highlighted after assigning.
7 'Previous assignable element (ALT+W)' button: Navigate to the previous assignable
element
8 'Next assignable element (ALT+S)' button: Navigate to the next assignable element
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 dropdown 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'.
The elements are assigned.
Instead of using the 'Assign' button, you can use the key combination <Alt> + <A>. If
necessary, several elements can be assigned to one another in this manner without
having to change between the tree view and 'Assign dialog' with the mouse. To do
this, the 'Always jump to next assignable element' checkbox must be checked.
The first element which can be assigned is automatically searched for and displayed
in the tree view (5) as standard. You can change this behavior in the presettings. You
will find information about this in the chapter 'General program settings [ 39]'.
6.13

You can use the 'Create and Assign' function to create at the same time several
devices and the associated physical channels in the 'Hardware tree' and the 'Zones' in
the 'Detection tree' and assign them to one another. During this process, you can state
customer texts for the 'Zones'.
The 'Create and Assign' window can be opened as follows:
'Commissioning' > 'Create and Assign' menu item
Context menu
<Ctrl> + <K>
68
A6V10333423_a_en_US
01/18/2012
Program operation
1 2 3
Window for creating and assigning devices
'Next assignable element (ALT+S)' button: Navigate to the next assignable detector
circuit
'Previous assignable element (ALT+W)' button: Navigate to the previous assignable

detector circuit
'Always jump to next assignable element' checkbox: If the checkbox is checked, the next
assignable detector circuit is highlighted after assigning.
List containing 'Zones' and devices which can be created and assigned
'No. of devices:' field: The number of devices you want to create can be entered here.
'Zone template:' field: Here you can select the template for the 'Zone'.
Tree view with detector circuits which can be assigned: Only those detector circuits on
which the device selected in the list (4) can be created are shown as circuits for
assignment.
Light gray text: The path leads to an element that cannot be assigned.
Black text: The path leads to a detector circuit which can be assigned.
Bold text, grayed out: Detector circuit which can be assigned.
'Zone customer text:' field: The customer text of the 'Zone' can be entered here.
'(First) device address:' field: The address of the device can be entered here. If several
devices are created, enter the address of the first device.
69
A6V10333423_a_en_US
01/18/2012
Program operation
Creating and assigning device

1. Select the 'Detection' task card.
2. Highlight the 'Section' element in the tree view.
3. In the toolbar, click 'Create and Assign'.
The 'Create and Assign' window opens.
4. From the list (4), select the 'Zone' and device that you want to create.
5. In the tree view (6), highlight the detector circuit on which you want to create the
device.
6. Select the template for the 'Zone' in the 'Zone template:' field.
7. In the 'Zone customer text:' field, it is possible to enter the customer text of the
'Zone'.
8. Enter the number of devices that you want to create in the 'No. of devices:' field.
9. Enter the address of the device in the '(First) device address:' field. If several
devices are created, enter the address of the first device.
10. Click the 'Create & Assign' button.
The device and the 'Zone' are created and assigned.
If you are creating several devices, a 'Zone' is created for each device.
Creating and assigning device with several physical channels

If you are assigning a device with several physical channels, e.g. 'HTRI-D', you can
state the 'Zone', template and customer text for each channel.
1. Proceed as described in steps 1 to 9.
2. Click on 'Create & Assign'.
3. Select the 'Zone' you want for each channel and the template.
4. Enter customer texts.
5. Click on 'OK'.
The device with the physical channels is created in the 'Hardware tree'.
A 'Zone' is created and assigned in the 'Detection tree' for each physical channel.
70
A6V10333423_a_en_US
01/18/2012
Program operation
Deleting a link
Instead of using the 'Create & Assign' button, you can use the key combination <Alt>
+ <A>. If necessary, several elements can be created and assigned to one another in
succession in this manner without the need to change between the tree view and
'Create and Assign' window with the mouse. To do this, the 'Always jump to next
assignable element' checkbox must be checked.
6.14
Deleting a link
To delete a link between two elements, proceed as follows:
1. Select a linked element in the tree view or the table.
2. Select 'Commissioning' > 'Unassign' from the menu bar.
The link is deleted.
OR
1. Right-click on a linked element in the tree view or the table.
2. Select 'Unassign' from the context menu.
The link is deleted.
The 'Unassign' command is not present in the 'Hardware' task card.
6.15
Finding
You can use the 'Find' function to search for elements using various search criteria,
e.g. you can search by 'Address', 'Customer text' or 'Problem'.
Finding
The search criteria available depend on the selected task card.

The 'Find' function is limited to the selected task card.
71
A6V10333423_a_en_US
01/18/2012
Program operation
Finding
Performing search
1. Select the task card you want and highlight in the tree view the element in which
you want to search.
2. Open the 'Find' window. The window can be opened as follows:
-
'View' > 'Find' menu item
<Ctrl> + <F>
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'.
''Find all' searches for and highlights all elements which correspond to the
search criterion.
'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 in place 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 which include the search value entered in the top right
field.
'Exactly': search for values which perfectly match the search value entered in the
top right field.
'Include unloaded panels': if you check the checkbox, both 'Panels' that are and are
not loaded are included in the search. See chapter 'Dynamic loading [ 52]'.
'Category:': limited search within one element category. The dropdown list contains
all element categories regardless of the task card selected. If you select an
element category that is not present in the task card selected, the search will be
fruitless.
See also
72
A6V10333423_a_en_US
01/18/2012
Program operation
Finding and replacing
6.16

You can use the 'Find and replace' function to search and replace elements using
various search criteria, e.g. you can search for 'Address', 'Customer text' or 'Problem'.
The search criteria available depend on the selected task card.

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

1. Select the task card you want and highlight in the tree view the element in which
you want to search.
2. Select 'View' > 'Find and replace'.
The 'Find and replace' window opens.
3. Select a search criterion.
4. Enter the search value in the top right field and the replacement value in the field
underneath.
5. Select the search options.
6. Click 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 in place of the 'Find next' button.
73
A6V10333423_a_en_US
01/18/2012
Program operation
Exporting and importing a CSV
Search options
'Entire site': search in the entire 'Site'.
'Selected sub-tree': search in the highlighted subtree.
'Include': search for values which include the search value entered in the top right
field.
'Exactly': search for values which perfectly match the search value entered in the
top right field.
'Include unloaded panels': if you check the checkbox, both 'Panels' that are and are
not loaded are included in the search. See chapter 'Dynamic loading [ 52]'.
'Category:': limited search within one element category. The dropdown list contains
all element categories regardless of the task card selected. If you select an
element category that is not present in the task card selected, the search will be
fruitless.
See also
6.17

The CSV export is used to export and if necessary edit data from CerberusEngineering-Tool in CSV format. The CSV import is used to import data into CerberusEngineering-Tool in CSV format. Only data in the 'Detection tree' is taken into account
for the CSV export and CSV import.
The menu entries for the CSV export and import are only present in the 'Detection'
task card.
You will find more information in the following chapters.
6.17.1
Exporting a CSV
With the CSV export, you can export data from the 'Detection tree' of a 'Site' to a CSV
file.
Example: The data of a 'Site' is exported to a CSV file. Customer-specific data, e.g. the
customer texts, is edited in this file. The file is then imported back into the 'Site' and the
customer texts are updated.
During the CSV export, the following elements are exported:
'Area address'
'Customer text'
'Section address'
'Zone intervention text'
'Zone address'
'Type'
'Channel address'
74
A6V10333423_a_en_US
01/18/2012
Program operation
Exporting a CSV
2. Highlight the 'Site' or a subtree in the tree view.
3. Select 'File' > 'CSV export' from the menu bar.
The 'CSV export' window opens.
4. Select the path and change the file name if necessary. The 'Site' name and the
extension '_exchange' are used as the file name as standard.
5. Click on 'OK'.
6. If you have not yet saved the 'Site', you are prompted to save the 'Site'. In this
instance, click on 'Yes'.
The CSV file is stored in the specified location.
6.17.2
Importing a CSV
With the CSV import, you can import data into a 'Site' in CSV format.
Example: The planning data for a fire detection installation is available in a CAD
program. Customer-specific data, e.g. customer texts, is exported from the CAD
program into a CSV file. This file is imported into the 'Detection tree' of a newly created
'Site'.
Importing a CSV
2. Select 'File' > 'CSV import' from the menu bar.
The 'CSV import' window opens.
3. Select the CSV file you want to import.

4. Click on 'OK'.
The specified CSV file is imported.
5. Open the CSV import log and rectify problems if necessary.
See also
CSV import log [ 76]
75
A6V10333423_a_en_US
01/18/2012
Program operation
Changing display logo
6.17.3
CSV import log

The CSV import log displays problems that occurred during the CSV import. You can
filter problems by 'Error', 'Warning' and 'Info'.
Viewing the CSV import log

2. Select 'File' > 'Show CSV import log' from the menu bar.
The 'CSV import log' window opens.
'Error', 'Warning' and 'Info' messages are listed in the window.
3. Double-click on a message to jump directly to the corresponding element.
6.18
Changing display logo

In the 'Panel''s normal status, the Siemens logo is shown on the display as standard.
You can replace the Siemens logo with a customer-specific logo. The logo must exist
as a GIF file and must satisfy the following conditions:
Maximum size: 251 x 56 pixels
Black and white
No transparency
Non-interlaced
Replacing 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 'Panel'.
After restarting the 'Panel', the new logo is shown on the display.
76
A6V10333423_a_en_US
01/18/2012
Program operation
Creating reports
Restoring 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 'Panel'.
After restarting the 'Panel', the standard logo is shown on the display.
The file with the replaced logo is saved in the same folder where the 'Site'
configuration is saved.
See also
Loading configuration from the PC to the 'Panel' [ 86]
6.19
Creating reports
You can create various reports as a PDF file in the 'Reports' window.
Creating a report
1. Select the task card from which you want to create a report.
2. Select 'File' > 'Reports' from the menu bar or click on the
The 'Reports' window opens.
3. Select the report you want in the 'Report type' field.

4. Enter the paper format, orientation, file name and memory location of the report in
the 'Output settings' area.
5. If available, set more properties.
6. Click on 'Create report'.
The report is created and displayed.
77
A6V10333423_a_en_US
01/18/2012
Program operation
Creating reports
Example of window for creating reports
You will find information about the individual reports and other settings in the following
chapters.
6.19.1
'Customer text report'
'Customer text report'
The 'Customer text report' lists the customer texts of all elements of the particular task
card.
In the 'Settings' section, you can set the following:
'Displayed top level of the tree': Uppermost level of the structure tree that is
displayed in the report.
'Displayed bottom level of the tree': Bottommost level of the structure tree that is
In the 'Operation' and 'Network' task cards, the 'Settings' area is empty.
78
A6V10333423_a_en_US
01/18/2012
Program operation
Creating reports
6.19.2
'Device report'
'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:
6.19.3
'Detection tree': 'Area', 'Section' and 'Zone' elements with the assigned devices
'Control tree': 'Control group' and 'Control' elements with the assigned devices
'Hardware tree': Element 'Site'
'Diagnostics report'
'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
79
A6V10333423_a_en_US
01/18/2012
Program operation
Creating reports
6.19.4
'Event memory report'
'Event memory report'
The 'Event memory report' lists the events of a 'Site'. Filter options allow you to restrict
the number of events listed, e.g. events of a certain event category within a certain
period.
With 'Browse...', you can open a CSV file of the event memory which you uploaded
using the 'Commissioning' > 'Transfer site event memory -> PC' menu item.
With 'Transfer -> PC...', you can establish the connection to a 'Panel' and upload
the event memory directly.
In the 'Start date' and 'End date' fields, you can specify the time and date for
starting and ending the report.
In the 'Event categories' area, you can select the event categories to be considered
in the report.
See also
Loading event memory to PC [ 89]
80
A6V10333423_a_en_US
01/18/2012
Program operation
Creating reports
6.19.5
'Node report'
'Node report'
In the 'Node report', the task card element highlighted in the tree view is listed in table
format.
'Full property set': All visible properties of the highlighted element are output.
'Property subset': Some of the properties are output. The selection depends on the
BDV used.
'Include sub-tree' This setting specifies whether only the highlighted elements are
output or the subtree is output too.
Not all settings are available in the 'Operation' and 'Network' task cards.
81
A6V10333423_a_en_US
01/18/2012
Program operation
Creating reports
6.19.6
'Tree report'
'Tree report'
In the 'Tree report', elements from the structure tree of the respective task card are
listed in table format.
'Displayed top level of the tree': Uppermost level of the structure tree that is
The table below shows which properties are output in each task card.
Features
Task card
'Hardware'
'Detection'
'Serial no.'
'Customer text'
'ASD / Sensitivity level'
'Template ID'
'Hyperlink'
'Control'
'Operation'
'Network'
X1
X
X
Properties output
In the 'Tree report' of the 'Operation' task card, the 'Customer text' is listed in a
separate column. In the 'Tree report' of the other task cards, the 'Customer text' is only
listed in the column with the structure tree.
82
A6V10333423_a_en_US
01/18/2012
Connectivity and communication with 'Panel'

Connecting the PC to the panel
7 Connectivity and communication with 'Panel'

A PC does not have to be directly connected to a 'Panel' to be able to communicate
with a 'Panel' in the 'Site'. The PC can be connected to any place in the Ethernet.
See also
Establishing connection from PC to FS920 network [ 233]
7.1
Connecting the PC to the panel

For most commissioning, maintenance and repair work a PC with installed CerberusEngineering-Tool is required. The figure below shows the connection between the PC
and 'Panel'.
Rear panel of operating unit and PC
LAN Ethernet connection
7.2
Cable, type CAT 5 or CAT 7, crossover, max.

100 m
Disconnecting PC from the 'Panel'

Since the IP address is linked to the MAC address for the connection between the PC
and 'Panel' and also remains in the cache should the connection be briefly lost for
2 min., you must note the following instructions.
NOTICE
Incorrect disconnection of 'Panel'
Establishment of connection to other 'Panel' not possible
Disconnect the PC from the 'Panel' as described in the following instructions.
The connection between the PC and the 'Panel' must be disconnected as follows:
1. Select 'Commissioning' > 'Disconnect' in Cerberus-Engineering-Tool.
2. Disconnect the cable connection between PC and 'Panel'.
3. Wait 2 min. before establishing a connection to another 'Panel'.
83
A6V10333423_a_en_US
01/18/2012

Connecting Cerberus-Remote
7.3
Connecting Cerberus-Remote
Approval for viewing and/or operating the 'Panel' with Cerberus-Remote is granted.
The PC is connected to the 'Site'.
1. Select the 'Cerberus-Remote' task card.
2. Select 'Cerberus-Remote' > 'Connect' from the menu bar.
The selection window for the connection is displayed.
3. Select the connection and confirm with 'OK'.
The 'Connect Cerberus-Remote' window opens.
4. Select the 'Panel' you want to view and/or operate and enter a valid PIN.
5. Click on 'OK'.
The connection is established.
Connecting to 'Panel' from the favorite list

Approval for viewing and/or operating the 'Panel' with Cerberus-Remote is granted.
The PC is connected to the 'Site'.
1. Select the 'Cerberus-Remote' task card.
2. Select 'Cerberus-Remote' > 'Connect to favorite' from the menu bar.
3. Select the 'Panel' you want from the list.
The connection is established.
You will find a description of how to enable for displaying and/or operating with
Cerberus-Remote in the document A6V10333380. See chapter 'Applicable
documents'.
In the pre-settings, you can specify that Cerberus-Remote is automatically connected

to the last connected 'Panel' when you open the 'Cerberus-Remote' task card.
See also
Cerberus-Remote settings [ 40]
Cerberus-Remote [ 49]
84
A6V10333423_a_en_US
01/18/2012

Loading data to the 'Panel'
7.4
Loading data to the 'Panel'

Data is loaded from Cerberus-Engineering-Tool to the 'Panel' when the following
commands are performed.
'Initialize panel'
'Transfer PC -> site'
If you are using several network cards on the PC, please note the information in the
chapter 'IP settings for several network cards [ 18]'.
The table below shows which data is overwritten in the panel 'Panel'.
Command
Overwrites the BDV Sets the address of

the 'Panel'
Overwrites the
configuration
'Initialize panel' 1
Yes
Yes
Yes
'Transfer PC -> site'
Yes
No
Yes 2
1 Command
2
is only performed for the 'Panel' that is connected to the PC via LAN.
The configuration of all 'Panels' in the 'Site' can be overwritten as an option.

See also
Initializing 'Panel' [ 86]
Loading configuration from the PC to the 'Panel' [ 86]
85
A6V10333423_a_en_US
01/18/2012

Initializing 'Panel'
7.5
Initializing 'Panel'
Each 'Panel' in a fire detection system with several networked 'Panels' must have a
unique address.
Once a 'Panel' has been started for the first time or once the firmware on the main
CPU has been updated, a 'Panel' has the address '1'. Networked 'Panels' must
therefore all be initialized.
If two 'Sites' are merged to form one 'Site', the 'Panels' with the same addresses in
the added 'Site' must each be given a new address.
The 'Initialize panel' procedure issues the 'Panel' an address within the 'Site'
according to the configuration in Cerberus-Engineering-Tool.
A standalone 'Panel' does not have to be initialized.
You will find the detailed description for initialization of a 'Panel' in document
See also
Loading data to the 'Panel' [ 85]
7.6
Loading configuration from the PC to the 'Panel'

The 'Transfer PC -> site' function can be used to load the configuration of a 'Site' from
Cerberus-Engineering-Tool on the PC to the 'Panel'.
NOTICE
Different network configuration in Cerberus-Engineering-Tool and networked 'Site'
When the selection displayed for 'Transfer PC -> site' is manually modified, in special
cases 1 it may be necessary to reset a 'Panel' to the factory setting as well as an
'Initialize panel'.
Do not modify the selection displayed for 'Transfer PC -> site' in normal cases.
Check the sequence when loading different configuration states in special
cases 1.
After changing the network configuration, make sure that all 'Panels' in the 'Site'
for the 'Transfer PC -> site' procedure are selected and can be accessed.
Temporarily update non-accessible 'Panels' to the latest status of the global
network configuration prior to integration in the network.
86
A6V10333423_a_en_US
01/18/2012

Loading configuration from the PC to the 'Panel'
The 'Site' is opened in Cerberus-Engineering-Tool.
The PC is connected to the 'Panel'.
Networked 'Panels' are initialized.
'Panel' and Cerberus-Engineering-Tool have the same 'Site' ID.
'Panel' and Cerberus-Engineering-Tool are in the same organizational unit.
1. Select 'Commissioning' > 'Transfer PC -> site'.
The 'Transfer site configuration to panel' and 'Connect' windows are opened.
2. Select the connection in the 'Connect' window and click on 'OK'.

The 'Panels' are listed in the 'Transfer site configuration to panel' window.
3. Select the 'Panels' whose configuration you would like to load from CerberusEngineering-Tool to the 'Panels' and click on 'Start'.
The 'Set access level' window may be opened with the 'Set the panel to access
level 3' prompt. Press <MENU> on the 'Panel', enter the PIN and press <ok>.
4. Click on 'OK' in the 'Set access level' window.

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

Loading configuration from the 'Panel' to the PC
1
Examples of special cases:
A 'Panel' is added to a networked 'Site' and a new network configuration, which is

different from the global network configuration of the connected 'Site', is loaded
upon initialization of this 'Panel'.
During the 'Transfer PC -> site' procedure a 'Panel' is temporarily not accessible.
Both examples can result in the 'Panel' no longer starting after the 'Transfer PC -> site'
procedure and the above actions having to be carried out.
See also
Loading data to the 'Panel' [ 85]
IP settings for several network cards [ 18]
7.7
Loading configuration from the 'Panel' to the PC

The 'Transfer site -> PC' function can be used to load the configuration of a 'Site' to
Cerberus-Engineering-Tool on the PC.
The 'Site' is opened in Cerberus-Engineering-Tool.
The PC is connected to the 'Panel'.
'Panel' and Cerberus-Engineering-Tool have the same 'Site' ID.
'Panel' and Cerberus-Engineering-Tool are in the same organizational unit.
1. Select 'Commissioning' > 'Transfer site -> PC'.
The 'Transfer site configuration to PC' and 'Connect' windows are opened.
2. Select the connection in the 'Connect' window and click on 'OK'.

The 'Panels' are listed in the 'Transfer site configuration to PC' window.
3. Select the 'Panels' whose configuration you would like to load to CerberusEngineering-Tool and click on 'Start'.
The 'Action confirmation' window opens.
4. Click on 'Yes'.
The configuration is loaded to the PC.
The advancement status is displayed in the 'Transfer site configuration to PC'
window.
88
A6V10333423_a_en_US
01/18/2012

Loading event memory to PC
7.8
Loading event memory to PC

The 'Transfer site event memory -> PC' can be used to load the event memory of one
or more 'Panels' in the 'Site' from any 'Panel' to the PC.
A valid 'Site' is loaded.
All 'Panels' have the same BDV version and the same global configuration so that
site-wide communication is supported.
'Panel' and Cerberus-Engineering-Tool must belong to the same organizational
unit.
The PC is connected to a 'Panel' in the 'Site' via an Ethernet cable.
1. In the 'Commissioning' menu, select the 'Transfer site event memory -> PC' menu
item.
The 'Connect' window opens.
2. Select the connection setting and confirm with 'OK'.
The selection window opens.
3. Select the 'Panels' whose event memory you would like to load to the PC.
4. Determine the memory location and the file name.
5. Click on 'Start'.
The data is transferred.
The status of the transfer is shown in the status bar.
The data is saved as a CSV file in the specified location.
See also
'Event memory report' [ 80]
89
A6V10333423_a_en_US
01/18/2012

Loading the 'Site' log files to the PC
7.9
Loading the 'Site' log files to the PC

You can load the log files of individual 'Panels' within a 'Site' to the PC.
The 'Transfer site log files -> PC' function in Cerberus-Engineering-Tool loads the log
files 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 'Panel'.
Example:
LogFilesArchiveExample.zip
\Panel1\
syslog_0.log
syslog_1.log
syslog_2.log
\Panel2\
syslog_0.log
syslog_1.log
A 'Site' is loaded.
All 'Panels' have the same BDV version and the same global configuration so that
site-wide communication is supported.
'Panel' and Cerberus-Engineering-Tool must be in the same organizational unit.
The PC is connected to a 'Panel' in the 'Site' via an Ethernet cable.
1. In the 'Commissioning' menu, select the 'Transfer site log files -> PC' menu item.
The 'Connect' window opens.
2. Select the connection setting and confirm with 'OK'.
The selection window opens.
Establishment of a connection is started and indicated.
3. Select the 'Panels' whose log files you would like to load to the PC.
4. Determine the memory location and the file name.
5. Click on 'Start'.
The data is transferred.
The status of the transfer is shown in the status bar.
The data is saved in the specified file.
90
A6V10333423_a_en_US
01/18/2012

Merging two 'Sites'
7.10
Merging 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
7.11
Updating the firmware of the 'Panel'

There are three ways in which to update the firmware of the 'Panel':
'FW update main CPU': Updates the main CPU
'FW update additional CPUs' updates additional CPUs, such as the periphery
boards
'FW update main and additional CPUs': updates the main CPU and additional
CPUs in one step
You will find a detailed description of how to update firmware in document

91
A6V10333423_a_en_US
01/18/2012
Configuration Overview
Updating the firmware of the 'Panel'
8 Configuration Overview
A 'Site' has a physical and a logical structure. The structures are shown and configured
in the Cerberus-Engineering-Tool 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
Control tree
Operation tree
Network tree
'Detection'
'Control'
'Operation'
'Network'
The physical structure is read in by the 'Panel' or created manually. The logical
structure can be created either manually during the pre-configuration or with autoconfiguration on the 'Panel'. Parts of the logical structure are pre-configured in the BDV
template for a 'Panel'.
The list below shows a selection of configurable elements in a 'Site':
Configuring the components of the 'Panel'
Detector groups
Detector settings
Multi-detector dependency
Alarm organization
Controls (alarming, fire, evacuation, releasing)
Networking control panels and operating panels ('Panels')
Visibility for events and functions
Service intervention
Customer texts
Intervention texts
Deactivating the mouse wheel of the computer mouse

NOTICE
Unintentional scrolling in dropdown lists
Configuration errors caused by unintentionally changing settings
Read the following description.

Check the 'Ignore mouse wheel' checkbox in the pre-settings to deactivate the
mouse wheel.
When you scroll with the mouse wheel in the detail editor, you may unintentionally
change settings in a dropdown list. To prevent this, you can deactivate the mouse
wheel. To do this, proceed as follows:
92
A6V10333423_a_en_US
01/18/2012
Configuration Overview
Customer text
1. In the menu bar, click on 'Options' > 'Preferences'.

The 'Preferences' window opens.
2. Click on 'Editing preferences' in the left of the window.
3. Check the 'Ignore mouse wheel' checkbox.
The mouse wheel is deactivated.
The 'Ignore mouse wheel' setting only applies when you select a new element in the
structure tree. The setting is not adopted for the element currently selected.
See also
Quicktext and mouse wheel settings [ 36]
8.1
Customer text
Customer text can be entered for each element in the structure tree. The customer text
is shown on the display of a 'Panel'. 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 next
superordinate element with a customer text is displayed.
Example: If a 'Section' has no customer text, the customer text of the 'Detection area'
is displayed.
'Zone' element
If an alarm message for a 'Zone', 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.
Customer texts in the 'Hardware' task card

If a new element is created in the 'Hardware' task card, the text of the template used is
adopted as the customer text as standard.
Example: If you create the 'HFP-11' element with the 'with audible base' template, the
element has the customer text 'with audible base'.
You can change the customer text if necessary.
93
A6V10333423_a_en_US
01/18/2012
'Hardware' task card

Intervention concept (IC)
9 'Hardware' task card

The components of the 'Panel' and the periphery devices are displayed in the
'Hardware' task card.
'Hardware' task card with the tree view and table
9.1

The intervention concept (IC) is a standard configuration for immediate intervention
and service intervention.
Events such as a 'Trouble' caused by a soiled detector are supervised during a
preconfigured period of time. If the normal operating 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 trouble locally before informing the maintenance
personnel.
You will find a detailed description of the intervention concept in document
The intervention concept can verify the following event categories:
'All troubles'
'All supervisories'
'All test messages'
'All activations'
'All information messages'
94
A6V10333423_a_en_US
01/18/2012

Configuring intervention concept
Detail editor with settings for the intervention concept
1. Select the 'Hardware' task card.

2. Highlight a 'Panel' in the tree view.
3. Select the 'Intervention' tab in the detail editor and set the properties you want.
It is possible to set the following properties for each event category.
Immediate intervention
The following settings can be made for 'Immediate intervention type':
'Disabled'
'Delayed intervention'
'Global intervention only'
'Local intervention only'
Time t1 for (intervention) attendance supervision:

When 'Disabled' is configured, a new event must be acknowledged within this time
period, otherwise the intervention concept switches to global alarming.
'Local alarming devices' and 'Global alarming devices':

Alarming equipment that is activated in the event of a local or global alarm.
Service intervention
The following settings can be made for 'Service intervention type':
'Disabled'
'Delayed intervention'
'Direct intervention'
Time ts for service intervention:

When 'Disabled' is configured, the cause of an event must be remedied within this
time period, otherwise the intervention concept activates the service intervention
alarming equipment.
'Alarming devices 'Service Intervention'':

Alarming equipment for the service intervention
95

A6V10333423_a_en_US
01/18/2012

Creating a detector circuit device
9.2
Creating a detector circuit device

Use the 'Create and Assign' function to create an C-NET device and at the same time
to assign it to the 'Detection tree'. The procedure is described in the chapter 'Creating
and assigning devices [ 68]'.
To create an C-NET device without the 'Create and Assign' function, proceed as
follows:
Creating a device

2. Open 'Panel' > 'C-NET card' in the tree view.
3. Highlight a class A circuit or class B circuit.
4. Open the 'New element' window.
5. In the 'Type:' field, select the C-NET device you want.
6. If various templates are available for selection, select the required template in the
'Template:' field.
7. Enter the number of C-NET devices needed in the 'Amount:' field and click on
'Add'.
The C-NET devices are created.
See also
Creating and assigning devices [ 68]
96
A6V10333423_a_en_US
01/18/2012

Properties of detector circuit devices
9.3

In the following chapters you will find a description of the properties you can set in the
detail editor of C-NET devices and their physical channels.
9.3.1
Device with internal LED

In the detail editor of a device with an internal LED, you can set the following in the
'Overview' tab:
Properties in the detail editor of a device with an internal LED
'LED deactivated': This setting specifies whether the internal LED of the device is
deactivated. If the checkbox is checked, green flashing of the internal LED, which
indicates normal operation, is deactivated.
This setting can be used in environments where green flashing would pose a
disturbance, e.g. in a theater or cinema. In the case of an alarm or trouble, the internal
LED functions as an alarm indicator and lights up red or yellow regardless of the
setting.
9.3.2
Input
In the detail editor of an input, e.g. of an 'HTRI-S', you can set the following in the
'Overview' tab:
Properties in the detail editor of an input
'Normally closed': This setting specifies whether the input is used as 'Normally closed'.
If the checkbox is checked, the input is evaluated as active when the input signal is
inactive.
97
A6V10333423_a_en_US
01/18/2012

9.3.3
Output
In the detail editor of an output, e.g. of an 'HTRI-R' or 'HFPO-11', you can set the
following in the 'Overview' tab:
Properties in the detail editor of an output
'Activated upon a degraded ALARM': This setting specifies whether the output is
activated during a degraded fire alarm and whether the output can be silenced.
9.3.4
HZM with conventional detector circuit

In the detail editor of the 'Conventional circuit' element in a 'Conventional zone module'
('HZM'), you can set the following in the 'Overview' tab:
Properties in the detail editor of the 'Conventional loop' element
'Detector alarm verification enabled': This setting specifies whether the detector alarm
verification is activated on the conventional detector circuit. If the detector alarm
verification is activated, an alarm event is checked before it is forwarded to the
assigned logical element.
9.3.5
HCP with 'NAC/speaker/telephone'

In the detail editor of the 'NAC/speaker/telephone' element in a 'Control point module'
('HCP'), you can set the following in the 'Overview' tab:
Properties in the detail editor of the '' element

98
A6V10333423_a_en_US
01/18/2012

'HCP usage': This setting specifies the use of the 'HCP'. Only NAC applications are
possible at present.
See also
Assigning 'NAC control' elements [ 146]
9.3.6
Detector sensor
In the detail editor of a detector sensor, you can set the following in the 'Overview' tab:
Depending on the detector type, not all settings are available.
Properties in the detail editor of a detector sensor
'Neural sensor operating mode': You can select the sensor mode in this field.
'ASD / Sensitivity level': In this field, you can select the ASD (application-specific
detection) setting or sensitivity level you want.
'Thermal sensor operating mode': In this field, you can specify whether the heat
sensor is used.
'Thermal sensor variant': This setting specifies the evaluation process for the heat
sensor.
'IEC enabled': This setting specifies whether 'Intelligent environmental

compensation' is activated.
You can find more information about the settings in the documentation for the
corresponding detector.
99
A6V10333423_a_en_US
01/18/2012

9.3.7
Detector with audible base

In the detail editor of a detector with 'Audible base', you can set the following in the
'Overview' tab:
Properties in the detail editor of a detector with an audible base
'Direct activation of audible base': This setting specifies which conditions must be
satisfied for the audible base to be activated directly:
'No direct activation': The audible base is not directly activated.
'By the ZONE of the detector in the same base': The conditions are satisfied if the
event was triggered by any device in the 'Zone'.
'By the DETECTOR in the same base': The conditions are satisfied if the event was
triggered by the detector with the audible base.
In the detail editor of the assigned 'Zone', you can set the level at which the audible
base is activated:
In 'PRE-STAGE' and 'MAIN STAGE'
Only in 'MAIN STAGE'
This setting is not possible in 'Zones' without 'PRE-STAGE'.

In addition to this setting for the audible base, you can configure an 'NAC control' or
'Universal evac control' and assign it to an 'Audible base'. You will find information
about this in the chapters ''Alarming control group' [ 132]' and ''Evac control group'
[ 161]'.
See also
Configuring the 'Zone' [ 127]
9.3.8
Detector with configurable output

In the detail editor of a detector with a configurable output, you can set the following in
the 'Overview' tab:
Properties in the detail editor of a detector with a configurable output
100
A6V10333423_a_en_US
01/18/2012

'Direct activation of output'

This setting specifies which conditions must be satisfied for the output to be directly
activated.
'No direct activation': The output is not directly activated.
'By the ZONE of the detector in the same base': The conditions are satisfied if the
event was triggered by any device in the 'Zone'.
'By the DETECTOR in the same base': The conditions are satisfied if the event was
triggered by the detector with the configurable output.
In the detail editor of the assigned 'Zone', you can set the level at which the output is
activated:
This setting is not possible in 'Zones' without 'PRE-STAGE'.

In addition to direct activation, you can assign a control to the output and configure it.
You will find information about this in the chapter ''Control' task card [ 131]'.
'Output activation in detector/walk test'

This setting specifies whether the output can be activated in the 'Detector test' or 'Walk
test' modes. The checkbox can only be checked when direct activation is configured for
the output.
See also
Configuring the 'Zone' [ 127]
9.3.9
Detector with ambient supervision

In the detail editor of the 'Ambient supervision' element, you can set the following in the
'Overview' tab:
Properties in the detail editor of the channel for ambient supervision
'Usage'
This setting specifies the type of ambient supervision.
101
A6V10333423_a_en_US
01/18/2012

'Hysteresis'
If the temperature or CO concentration deviates from the threshold value, the input
may switch back and forth 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 CO concentration falls below or
exceeds the threshold value by at least the defined hysteresis value.
Hysteresis values:
'Normal':
Temperature: 1 degree
CO concentration: 5 % of threshold value, maximum 15 ppm, minimum 2 ppm
'Large/slow'
Temperature: 5 degrees
CO concentration: Average value over 15 minutes, hysteresis of 6 ppm
'Threshold temperature (Fahrenheit)'

Here you can select the threshold value for the temperature. If this threshold value is
fallen below or exceeded (depending on 'Usage'), the channel is activated.
This field can only be edited if for 'Usage' you have selected the 'Temperature higher
than threshold (Fahrenheit)' or 'Temperature lower than threshold (Fahrenheit)' setting.
'Threshold CO concentration (ppm)'

Here you can select the threshold value for the CO concentration. If this threshold
value is exceeded, the channel is activated.
This field can only be edited if for 'Usage' you have selected the 'CO concentration
higher than threshold (ppm)' setting.
9.3.10
FDCIO442
In the detail editor of the 'Class B circuit' or 'Class A circuit' element of a FDCIO442,
you can set the following in the 'Overview' tab:
Properties in the detail editor of an input
'Normally closed'
This setting specifies whether the input is used as 'Normally closed'. If the checkbox is
checked, the input is evaluated as active when the input signal is inactive.
102
A6V10333423_a_en_US
01/18/2012

'Short circuit supervision enabled'

This setting specifies whether supervision for short-circuit is activated. Short-circuit
supervision requires special wiring.
If short-circuit supervision is deactivated, a short-circuit is evaluated as 'active'. This
can be used to connect old detectors with bimetal switches or manual pull stations with
switches. For these applications, you have to deactivate short-circuit supervision and
link the input to a 'Zone'.
In the detail editor of the 'Output' element, you can set the following in the 'Overview'
tab:
Properties in the detail editor of an output
'Output mode'
This setting defines how the output signal behaves when the logic is active or inactive.
Examples:
'Inactive: Off / active: On': The output signal is switched off when the logic is
inactive and switched on when the logic is active.
'Inactive: Off / active: Intermittent, fast (0.25s/0.25s)': The output signal is switched
off when the logic is inactive and HIGH for 0.25 s and LOW for 0.25 s (alternating)
when the logic is active.
'Always Off': The output signal is switched off when the logic is both inactive and
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 circuit voltage fails.
Configuration of input
In the following cases, two messages are displayed in the event of trouble at the
'Panel'.
Configuration A: The FDCIO442 input is configured as follows:
Normally open
'Short circuit supervision enabled'
Non-alarm-causing (e.g. 'Supervisory'-causing)
In the event of a short-circuit, the FDCIO442 not only reports the short-circuit trouble,
but also an input activation. On the 'Panel', trouble and activation (e.g. 'Supervisory')
are displayed.
103
A6V10333423_a_en_US
01/18/2012

Periphery board
Configuration B: The FDCIO442 input is configured as follows:
Normally closed
Non-alarm-causing (e.g. 'Supervisory'-causing)
In the event of an open circuit, the FDCIO442 not only reports the open circuit trouble,
but also an input activation. On the 'Panel', trouble and activation (e.g. 'Supervisory')
are displayed.
9.4
Periphery board
The periphery board contains the following elements as standard:
Outputs for remote transmission: 'RT alarm', 'RT trouble', 'RT supervisory' and 'RT
programmable'
'Onboard NAC'
You can also add the following elements:
'Optional NAC (FCI2011)'
'City tie'
'Leased line'
The 'Leased line / city tie module' can either be configured for the 'City tie' or 'Leased
line' application. The applications cannot be used in parallel.
Properties of the periphery board

In the detail editor of the periphery board, you can set the following in the 'Overview'
tab:
Properties in the detail editor of the periphery board
'Shut off auxiliary power output on reset of PRE-STAGE or MAIN STAGE event': This
setting specifies whether or not the additional 26 V supply output is temporarily deenergized when the system is reset.
104
A6V10333423_a_en_US
01/18/2012

Periphery board
9.4.1
'Onboard NAC' element

The 'Onboard NAC' element contains the NAC connections integrated on the periphery
board. The 'Onboard NAC' element can either be used with a class A circuit or two
class B circuits.
Properties of NAC circuits

In the detail editor of NAC circuits, you can set the following in the 'Overview' tab:
Properties in the detail editor of the NAC circuit
'BELL follower': This setting specifies whether the NAC output is synchronized with
the master NAC input on the periphery board. If the checkbox is checked, you
cannot assign the NAC circuit to an 'NAC control'.
'NAC output mode in degraded mode': This setting defines the output mode for
activating the NAC circuit during a degraded fire alarm.
See also
'NAC control' elements [ 145]
Properties of 'NAC control' elements [ 148]
9.4.2
'Optional NAC (FCI2011)' element

The 'Optional NAC (FCI2011)' element is used to extend the NAC connections
integrated on the periphery board. The 'Optional NAC (FCI2011)' element can either be
used with a class A circuit or two class B circuits.
You will find further information about the NAC module in document A6V10333409.
See chapter 'Applicable documents'.
105
A6V10333423_a_en_US
01/18/2012

Periphery board
Creating an 'Optional NAC (FCI2011)' element
Creating an 'Optional NAC (FCI2011)' element
You can create either the 'Optional NAC (FCI2011)' element or the 'Releasing module
(XCI2001)' element in the 'Hardware tree'. You cannot use both elements at the same
time.
2. Open the 'Panel' in the tree view and highlight the 'Periphery board (FCI2017)'
element.
4. Select 'Optional NAC (FCI2011)' in the 'Type:' field.
5. Click on 'Add'.
The 'Optional NAC (FCI2011)' element is created.
Creating an NAC circuit
Creating an NAC circuit

2. Open 'Panel' > 'Periphery board (FCI2017)' in the tree view.
3. Highlight the 'Optional NAC (FCI2011)' element.
5. Select a class A circuit or class B circuit in the 'Type:' field.
6. Click on 'Add'.
The NAC circuit is created.
The properties in the detail editor of NAC circuits are described in the chapter
''Onboard NAC' element'.
106
A6V10333423_a_en_US
01/18/2012

Periphery board
See also
'NAC control' elements [ 145]
Properties of 'NAC control' elements [ 148]
9.4.3
'City tie' and 'Leased line' elements

The 'City tie' element is an application of the 'Leased line / city tie module' and has an
'Alarm/supervised' output. The output is supervised for short-circuit and interrupt.
The 'Leased line' element is an application of the 'Leased line / city tie module' and has
three outputs:
'Alarm'
'Trouble'
'Supervisory'
The outputs are not supervised for short-circuit or interrupt.
'City tie' element in the tree view
'Leased line' element in the tree view
Creating 'City tie' and 'Leased line' elements
Creating 'City tie' and 'Leased line' elements

2. Open the 'Panel' in the tree view and highlight the 'Periphery board (FCI2017)'
element.
4. In the 'Type:' field, select the 'City tie' or 'Leased line' element.
5. Click on 'Add'.
The 'City tie' or 'Leased line' element is created.
107
A6V10333423_a_en_US
01/18/2012

RS485 class A module (isolated)
You will find more information about the 'Leased line / city tie module' in document
See also
Applicable documents [ 10]
'City tie' element [ 136]
Assigning the 'City tie' element [ 137]
'Leased line' elements [ 139]
Assigning 'Leased line' elements [ 140]
9.5

Creating an 'RS485 module (FCA2016)' element
Creating an RS485 class A module

2. Open the 'Panel' in the tree view and highlight the 'Communication interfaces'
element.
4. Select 'RS485 module (FCA2016)' in the 'Type:' field.
5. Click on 'Add'.
The 'RS485 module (FCA2016)' element is created.
Properties of the 'RS485 module (FCA2016)' element

In the detail editor of the 'RS485 module (FCA2016)' element, you can set the following
in the 'Overview' tab:
Properties in the detail editor of the RS485 module class A
'Module slot': Slot on the PMI & mainboard to which the RS485 class A module is
connected. This property is set automatically.
'Class A circuit': This setting specifies whether the RS485 circuit is wired as a class
A circuit or class B circuit.
'Baud rate': Baud rate of the interface.
108
A6V10333423_a_en_US
01/18/2012

You will find more information about the RS485 class A module in document
Creating devices on the RS485 circuit

You can connect up to eight devices on the RS485 circuit, e.g. 'FT2014', 'FT2015' and
'Printer (RPM)'. To do this, you must create the corresponding elements in the 'RS485
module (FCA2016)' element.
Creating devices on the RS485 circuit

2. Open 'Panel' > 'Communication interfaces' in the tree view.
3. Highlight the 'RS485 module (FCA2016)' element.
5. In the 'Type:' field, select the element you want to create.
6. Click on 'Add'.
See also
Printer [ 215]
Creating and assigning the remote terminal [ 218]
Creating and assigning the remote display [ 220]
109
A6V10333423_a_en_US
01/18/2012

Power supply
9.6
Power supply
In the detail editor of the power supply, you can set the following in the 'Overview' tab:
Properties in the detail editor of the power supply
'Power supply type': This setting specifies the type of power supply.
'Battery capacity': This setting specifies the capacity of the connected battery.
'Emergency power delay': This setting specifies the delay for the 'On battery'
trouble message display. The 'On battery' message indicates emergency power
operation during a mains failure.
The 'Emergency power delay' setting is only possible when the 'Enabled' checkbox is
checked.
You will find further information about the power supply in document A6V10333409.
See also
9.7
Releasing module
Creating a releasing module
Creating a releasing module

2. Highlight the 'Panel' in the tree view.
4. Select 'Releasing module (XCI2001)' in the 'Type:' field.
5. Click on 'Add'.
The 'Releasing module (XCI2001)' element is created.
110
A6V10333423_a_en_US
01/18/2012

Releasing module
Properties of the releasing module

In the detail editor of the releasing module, you can set the following in the 'Overview'
tab:
Properties in the detail editor of the releasing module
'Activated upon a degraded ALARM': This setting specifies whether the releasing
circuits are activated during a degraded fire alarm. The corresponding jumper must
also be set on the releasing module for the releasing circuits to be activated during a
degraded fire alarm. You will find information about this in document A6V10333409.
Properties of the releasing circuits

In the detail editor of releasing circuits, you can set the following in the 'Overview' tab:
Properties in the detail editor of a releasing circuit
'Activation duration': This setting specifies the activation duration of the releasing
circuit.
You will find more information about the releasing module in document
See also
111
A6V10333423_a_en_US
01/18/2012

LED module FTO2008
9.8
LED module FTO2008

Creating an 'LED module (FTO2008)' element
Creating an LED module

4. Select 'LED module (FTO2008)' in the 'Type:' field.
5. Click on 'Add'.
The 'LED module (FTO2008)' element is created.
6. Highlight the 'LED module (FTO2008)' element.
7. In the detail editor, enter the address which is set on the LED module with switch
S15 in the 'Address' field. Address range: 2035.
You will find more information about the LED module and switch S15 in document
When the hardware is imported, the address set for the LED module is automatically
transferred into Cerberus-Engineering-Tool.
Properties of the 'LED module (FTO2008)' element

In the detail editor of the 'LED module (FTO2008)' element, you can set the following in
the 'Details' tab:
Properties in the detail editor of the LED module
'Suppress LED test': This setting specifies whether an LED test is performed on the
LED module during an LED test on the connected 'Panel'. If the 'Suppress LED test'
checkbox is checked, an LED test is not performed on the LED module.
See also
LED module [ 209]
112
A6V10333423_a_en_US
01/18/2012

Dialer module (DACT)
9.9
Dialer module (DACT)

Creating a dialer module (DACT)
Creating a dialer module (DACT)

4. Select 'Dialer module (FCA2015)' in the 'Type:' field.
5. Click on 'Add'.
The 'Dialer module (FCA2015)' element is created.
Properties of the 'Supervised (open/short circuit) DACT channel'

element
In the detail editor of the 'Supervised (open/short circuit) DACT channel' element, you
can set the following in the 'Overview' tab:
Properties in the detail editor of the DACT channel
'Dialing mode line 1' and 'Dialing mode line 2': These settings specify the circuit 1 or 2
selection mode.
See also
'DACT control' element [ 142]
113
A6V10333423_a_en_US
01/18/2012

SAFEDLINK interface (FN2001/2010)
9.10

Creating an 'SAFEDLINK interface (FN2001/2010)' element
Creating SAFEDLINK interface

2. Open the 'Panel' in the tree view.
3. Highlight the 'CPU (FCM20xx)' element.
5. Select 'SAFEDLINK interface (FN2001/2010)' in the 'Type:' field.
6. Click on 'Add'.
The 'SAFEDLINK interface (FN2001/2010)' element is created.
Properties of the 'SAFEDLINK interface (FN2001/2010)' element

The following can be set in the detail editor of the 'SAFEDLINK interface
(FN2001/2010)' element:
Properties in the detail editor of the SAFEDLINK interface
'Suppress port troubles': You can use this property to configure a SAFEDLINK
connection as a class B circuit. To do this, first select the 'Port 1 troubles' setting in the
first 'Panel' of the SAFEDLINK connection. In the last 'Panel', select the 'Port 2
troubles' setting.
If you configure the SAFEDLINK connection as a class A circuit, select the ' - (none)'
setting.
If the ' - (none)' setting is selected, troubles arise when wiring as a class B circuit.
You will find more information about the network module (SAFEDLINK) FN2001 and
fiber network module FN2006/FN2007 in document A6V10333409. See chapter
'Applicable documents'.
See also
114
A6V10333423_a_en_US
01/18/2012
'Detection' task card

10
10 'Detection' task card

The following logical elements are shown in the 'Detection' task card:
'Area'
When a 'Panel' is created, the 'Area' element is created too.
Additional 'Area' elements can be created for each 'Panel'.
'Section'
When a 'Panel' is created, a 'Section' element is created too.
Additional 'Section' elements can be created for each Panel.
'Zone'
The 'Zone'element can be created manually.
'Logical channel'
The 'Logical channel' element can be created manually during preconfiguration. 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 'Panel' is configured using the 'Auto-configure circuit', 'Auto-configure panel' or

'Create and Assign' functions, the 'Section', 'Zone' and 'Logical channel' functions are
created automatically. The physical and logical channels are assigned automatically.
You will find further information about the auto-configuration in document
See also
Creating and assigning devices [ 68]
115
A6V10333423_a_en_US
01/18/2012
10

Creating 'Detection tree'
10.1
Creating 'Detection tree'

Use the 'Create and Assign' function to create the 'Detection tree' and at the same time
to assign with the 'Hardware tree'. The procedure is described in the chapter 'Creating
and assigning devices'.
Task card 'Detection' with the tree view and window 'New element'
To create the 'Detection tree' without the 'Create and Assign' function, proceed as
follows:
2. Open a 'Panel' > 'Detection area'.
3. Highlight 'Section'.
5. Select a 'Zone' and the corresponding template in the 'Type:' field.
6. Enter the number of Zones needed in the 'Amount:' field and click on 'Add'.
The 'Zones' are created.
See also
Creating an element [ 60]
116
A6V10333423_a_en_US
01/18/2012

'Area'
10.2
10
'Area'
Each 'Panel' contains the following 'Areas':
'Detection area'
'Panel area'
'Detection area'
'Detection area' is the uppermost element in the 'Detection tree'. Up to four 'Detection
area' are possible per FC924.
The 'Detection area' has an alarm verification concept (AVC) and can be configured
and assigned to the controls independently of other areas.
'Panel area'
'Panel area' occurs precisely once and groups together the functions of alarm
verification for elements that are not in the 'Detection area', e.g. degraded mode
operation.
The 'Panel area' can be displayed and navigated, like any 'Detection area'. It has no
child elements and is identical to the 'Detection area' in terms of alarm verification.
10.2.1
Alarm verification concept (AVC)

The alarm verification concept corresponds to the 'Positive alarm sequence'
according to UL 864.
You can use the 'Alarm Verification Concept' ('AVC') to configure the following:
Alarming equipment activated in the event of an alarm. The alarming equipment

can be defined for different kinds of alarms, e.g. for automatic or manual fire
alarms.
Different types of alarming depend on a detector's activated sensor type.
Delayed alarm transmission with operating staff interacting in the alarming process.
The 'Alarm Verification Concept' verifies the following event categories:
'All Fire ALARMS':
' --All automatic Fire ALARMS'
' --Manual Fire ALARM'
' --Waterflow ALARM'
'All Gas ALARMS':
' --CO gas ALARM'
You can configure the 'AVC' settings for each event category.
117
A6V10333423_a_en_US
01/18/2012
10

'Area'
'Alarm Verification Concept': Configuring
Detail editor with settings for 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.
The settings are described in the following sections.
Delay times t1 and t2
Response time t1: A new event must be acknowledged within this period,
otherwise the alarm verification concept switches to global alarming.
Investigation time t2: The cause of an event must be investigated within this period
and the system reset, otherwise the alarm verification concept changes to global
alarming.
'Alarming type'
The following alarming types exist:
'Local alarming only'
'Delayed alarming'
'Global alarming only'
For the event category ' --All automatic Fire ALARMS', you can set 'Alarming type' for
different sensor types:
'Alarming type 'thermal''
'Alarming type 'chamber''
'Alarming type 'neural''
118
A6V10333423_a_en_US
01/18/2012

'Area'
10
If no specific sensor type is activated then the general setting 'Alarming type' is used. If
several sensor types are active at the same time then the 'Alarming type' with the
highest priority is always used. The priorities are as follows:
First priority: 'Global alarming only'
Second priority: 'Delayed alarming'
Third priority: 'Local alarming only'
The general setting 'Alarming type' is not evaluated as soon as a specific sensor type
is active.
'Local alarming devices'

Alarming equipment that is activated in the event of a local alarm.
'Global alarming devices'

Alarming equipment that is activated in the event of a global alarm.
Example of use
Example of use
The setting for 'Alarming type 'chamber'' is 'Delayed alarming'. All other 'Alarming type'
are set to 'Global alarming only'.
1. An automatic alarm is triggered by a detector with the 'chamber' sensor type, e.g. a
smoke detector.
2. The setting for 'Alarming type 'chamber'' is used: 'Delayed alarming'. The delay
time starts to run.
3. A further automatic alarm is triggered by a detector with the 'thermal' sensor type,
e.g. a thermal detector.
4. The setting for 'Alarming type 'thermal'' is used: 'Global alarming only'. The global
alarming is triggered.
119
A6V10333423_a_en_US
01/18/2012
10

'Section'
10.2.2
Immediate global alarming

The 'Immediate global alarming' setting in the 'Details' tab determines under which of
the following conditions the global alarming is triggered immediately:
' - (disabled)'
'Upon 2nd alarm within area'
'Upon 2nd alarm within site'
'Always (upon first alarm)'
The setting for 'Immediate global alarming' is only relevant if at least one 'Delayed
alarming' has been set for 'Alarming type'.
Detail editor with settings for immediate global alarming
10.3
'Section'
The 'Section' level is used to group 'Zones' and does not have any of its own functions.
For example, all 'Zones' on a floor can be combined in a 'Section' element. This
simplifies operation.
10.4
'Zone'
There are the following types of 'Zone':
'Automatic alarm zone'
'Manual alarm zone'
'Supervisory zone'
'Waterflow zone'
'Sub-system zone'
'Trouble zone'
'Status zone'
'Gas zone'
The types are described in the following chapters.
120
A6V10333423_a_en_US
01/18/2012

'Zone'
10
The following table shows the devices that can be assigned to a 'Zone'.
'Zone'
Assignable devices
'Automatic detector'
'Input'
'Conventional zone module'
'Manual alarm zone'
'Manual pull station'

'Input'
'Supervisory zone'
'Input'
'Waterflow zone'
'Input'
'Sub-system zone'
'Input'
'Trouble zone'
'Input'
'Status zone'
'Input'
'Gas zone'
'Input'
Zone types with the assignable devices

Each device that satisfies the conditions for an alarm reports its own alarm event. No
alarm events are reported at 'Zone' level.
121
A6V10333423_a_en_US
01/18/2012
10

'Zone'
10.4.1

Automatic fire detectors are evaluated in the 'Automatic alarm zone'. The 'Zone' can
however also be configured for inputs or conventional detector circuits.
When creating a 'Automatic alarm zone', you can choose between different templates
which are pre-configured for various applications.
The table below shows the properties of the templates and event category and the
event text of the message which is generated during an alarm.
Main features and typical application
Typical event category
Event text 1
'Single, Standard':
Evaluation of automatic fire detectors
Single-detector dependency
Without 'Pre-ALARM'
' ----Automatic Fire ALARM'
'Autom.FIRE ALARM'
'Single, Pre-alarm':
With 'Pre-ALARM'
'Single, Tornado alarm':

Evaluation of inputs
Without 'Pre-ALARM'
' ----Automatic Tornado ALARM'
Multi, 2 det. dependency:

Multi-detector dependency
With 'Pre-ALARM'
In 'PRE-STAGE', the 'Alarming type' is set
to 'Local alarming only'
'PRE-STAGE':
' --Pre-ALARM (trouble)'
'MAIN STAGE':
'PRE-STAGE':
'MAIN STAGE':
'PRE-STAGE':
'Pre-ALARM'
'MAIN STAGE':
'Autom.FIRE ALARM'
'Tornado ALARM'
'PRE-STAGE':
'Autom.FIRE ALARM'
'MAIN STAGE':
'Autom.FIRE ALARM'
Properties of the templates

Text that appears on the display of the Person Machine Interface when the event
occurs.
1
122
A6V10333423_a_en_US
01/18/2012

'Zone'
10
Single-detector dependency and multi-detector dependency

The table below shows the required number of detectors with danger level (DL) 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 (DL)

'PRE-STAGE'
'MAIN STAGE'
DL 2
GS 3
DL 2
GS 3
'Single, Standard'
'Single, Pre-alarm'
'Single, tornado alarm'
'Multi, 2 det. dependency'
Single-detector dependency and multi-detector dependency
10.4.2
'Manual alarm zone'

'Manual pull stations' are evaluated in the 'Manual alarm zone'. The 'Zone' can
however also be configured for inputs or conventional detector circuits. The danger
signals are evaluated with an OR link.
The table below shows the properties of the template for the 'Manual alarm zone'.
Typical application
Event text 1
'Standard':
Evaluation of manual fire detector
' --Manual Fire ALARM'
'Man. FIRE ALARM'
Properties of the template

occurs.
1
10.4.3
'Supervisory zone'
The 'Supervisory zone' supervises events, e.g. pressure in releasing agent containers,
water level and water temperature in releasing water tanks and fuel supply for
releasing pumps.
The table below shows the properties of the template for the 'Supervisory zone'.
Typical application
Event text 1
'Standard':
Evaluation of optical fire detectors, inputs
and conventional detector circuits
'All supervisories'
'Supervisory'

1 Text that appears on the display of the Person Machine Interface when the event
occurs.
123
A6V10333423_a_en_US
01/18/2012
10

'Zone'
10.4.4
'Waterflow zone'
'Waterflow zone' supervises the waterflow in a sprinkler system. As soon as water
flows, this status is signaled to the fire control panel via a contact. The 'Waterflow zone'
can be assigned to inputs or conventional detector circuits.
The table below shows the properties of the template for the 'Waterflow zone'.
Typical application
Event text 1
'Standard':
Evaluation of flow meters that are
connected via inputs or conventional
detector circuit
' --Waterflow ALARM'
'Waterflow ALARM'

occurs.
1
10.4.5
'Sub-system zone'
In the 'Sub-system zone', signals from connected sub-systems are evaluated, e.g. from
conventional fire control panels, aspirating smoke detection systems and gas detection
systems.
When creating a 'Sub-system zone', you can choose between different templates
which are pre-configured for different types of sub-system.
event text of the message which is generated during various events.
Typical application
Event in the sub-system
Event text 1
'PreALARM sub-sys'
'ALARM sub-system'
' --Bypass (trouble)'
'Sub-sys.BYPASSED'
Trouble
' --Other trouble'
'Trbl sub-system'
'Pre-ALARM'
'PreALARM sub-sys'
'ALARM'
'ALARM sub-system'
Bypass
'Other information'
'Active info'
Trouble
' --Other trouble'
'Trbl sub-system'
' --CO gas ALARM'
'Gas warning'
' --CO gas ALARM'
'Gas ALARM'
'Sub-sys.BYPASSED'
' --Other trouble'
'Trbl sub-system'
'Standard':
'Pre-ALARM'
Evaluation of a fire detection sub'ALARM'
system that is connected via inputs
Bypass
and outputs
'ASD system':
Evaluation of an aspirating smoke
detection system that is connected
via inputs and outputs
'Gas system':
'Pre-ALARM'
Evaluation of a gas detection sub- 'ALARM'
system that is connected via inputs
Bypass
and outputs
Trouble

occurs.
124
A6V10333423_a_en_US
01/18/2012

'Zone'
10
Every template has four inputs and two outputs. Depending on the sub-system, not all
inputs and outputs have to be assigned. If e.g. a sub-system cannot generate a 'PreALARM', leave the 'Input 'PRE-STAGE'' unassigned.
Inputs
'Input 'PRE-STAGE''
'Input 'MAIN STAGE''
'Input 'Trouble''
'Input 'Bypass''
The inputs can be used to evaluate various events in the sub-system. If an input is
activated, the corresponding event text is displayed. Please refer to the table above.
Outputs
The outputs can be used to acknowledge and reset events in the sub-system.
When you acknowledge an event, the 'Output 'Acknowledge'' output is activated for
3 s.
When you reset an event, the 'Output 'Reset'' output is activated. The duration of
activation depends on the 'Reset time' setting in the 'Details' tab:
'Enabled' checkbox unchecked: The output is activated for 3 s.
'Enabled' checkbox checked: The activation period can be set to between 3 s

and 5 min. If the reset has been performed successfully before the set time
elapses, the output is immediately deactivated again.
Detail editor of the 'Sub-system zone'
125
A6V10333423_a_en_US
01/18/2012
10

'Zone'
10.4.6
'Trouble zone'
The 'Trouble zone' can be used to display trouble messages from devices that are
connected via inputs. When creating a 'Trouble zone', you can choose between
different templates which are pre-configured for various applications.
event text of the message which is generated during an event.
Typical application
Event text 1
'Trouble':
Message about troubles from a connected
device
' --Other trouble'
'Trouble'
'Bypass':
Message about bypasses from a connected
device
'Bypassed'
'Trouble network device':

Message about troubles from the 'Ethernet
switch (MM) FN2008-A1' and 'Security
module (firewall) FN2009-A1' network
elements
' --Other trouble'
'Trbl netw.device'
'Trouble fiber network module':

Message about troubles from a connected
fiber network module
' --Other trouble'
'Trouble'

occurs.
10.4.7
'Status zone'
The 'Status zone' can be used to display status messages, e.g. activations, from
devices that are connected via inputs.
The table below shows the properties of the template for the 'Status zone'.
Typical application
Event text 1
'Active':
Message about activations from a
connected device
' --Other activation'
'Active'

occurs.
1
126
A6V10333423_a_en_US
01/18/2012

Configuring the 'Zone'
10.4.8
10
'Gas zone'
Gas detectors are evaluated with the 'Gas zone'. When creating a 'Gas zone', you can
choose between different templates which are pre-configured for various applications.
event text of the message which is generated during an alarm.
Main features and typical application
Event text 1
'CO gas alarm':

Evaluation of gas detectors
Without 'Pre-ALARM'
' --CO gas ALARM'
'CO gas ALARM'
'CO gas warning':

Without 'Pre-ALARM'
'Alarming type': 'Local alarming only'
' --CO gas ALARM'
'CO gas warning'
'CO gas warning + alarm':

With 'Pre-ALARM'
In 'PRE-STAGE', the 'Alarming type' is set
to 'Local alarming only'
'PRE-STAGE':
' --CO gas ALARM'
'MAIN STAGE':
' --CO gas ALARM'
'PRE-STAGE':
'CO gas warning'
'MAIN STAGE':
'CO gas ALARM'

occurs.
1
10.5

2. Highlight a 'Zone' in the tree view.
3. Select the 'Overview' or 'Details' tab in the detail editor.
4. Set the required properties. The settings are described in the following sections.
Depending on the 'Zone', not all settings are available.
Settings in the 'Overview' tab
127
A6V10333423_a_en_US
01/18/2012
10

Settings in the 'Details' tab
'Customer text'
The text in the 'Customer text' field is displayed on the Person Machine Interface along
with the messages from the corresponding element. You will find more information
about customer text in the chapter 'Customer text'.
'Intervention text'
The text in the 'Intervention text' field is displayed on the Person Machine Interface
during an alarm in the corresponding 'Zone'. The text can contain a minimum of four
lines. To insert a line break, enter the following text:
$(BR)
'Channel activation'
This setting specifies the level at which the logical channels generate an activation
message and activate their internal alarm indicators:
'Output activation' and 'Audible base activation'

These settings specify the level at which the outputs or audible bases of assigned
devices are activated:
These settings are only applied when direct activation of the output or audible base is
configured. You will find further information about direct activation in the chapters
'Detector with configurable output' and 'Detector with audible base'.
128
A6V10333423_a_en_US
01/18/2012

10
'Timeout detector/walk test'

The 'Timeout detector/walk test' setting enables a time-out to be specified for the
'Detector test' or 'Walk test' modes.
Option
Effect
'Enabled' checkbox
unchecked
Time-out cannot be set.
1 h 00 min to 23 h 59 min
After this time elapses, the 'Detector test' or 'Walk test' mode is
terminated automatically.
'BYPASS allowed'
Option
Effect
Checkbox checked
'Zone' can be bypassed using an operating command.
Checkbox unchecked
'Zone' cannot be bypassed using an operating command.
'Criteria PRE-STAGE' and 'Criteria MAIN STAGE'

These settings indicate the criteria needed to reach 'PRE-STAGE' or 'MAIN STAGE'
and to trigger an alarm. The criteria are satisfied if the stated number of detectors in
the 'Zone' reach danger level 2 or 3. The top field shows the number of detectors with
danger level 2 and the bottom field the number with danger level 3.
Example:
The criteria for 'PRE-STAGE' are satisfied if 1 detector reaches danger level 2.
The criteria for 'MAIN STAGE' are satisfied if 1 detector reaches danger level 3.
The criteria for 'MAIN STAGE' take priority over the criteria for 'PRE-STAGE'.
'Reset time'
Option
Effect
'Enabled' checkbox
unchecked
Reset time cannot be set. In this case, the suitable reset time is
set by the control panel.
Checkbox 'Enabled'
checked
'Reset time': 1 s to 5 min
The user can set the appropriate reset time, e.g. if sub-systems
are connected.
The system attempts to reset the element within this time before
the attempt is considered a failure. If the element can be reset
before the set time, it is reset immediately.
129
A6V10333423_a_en_US
01/18/2012
10

Assigning hardware tree to detection tree
'Always resettable'
This property is only available for the 'Manual alarm zone'.
10.6
Option
Effect
Checkbox checked
'Zone' can always be reset (message 'glass broken' from manual

pull stations that are still active).
Checkbox unchecked
'Zone' can only be reset if all assigned manual pull stations are in
quiescent condition.
Assigning hardware tree to detection tree

Use the 'Create and Assign' function to assign the 'Hardware tree' with the 'Detection
tree'. The procedure is described in the chapter 'Creating and assigning devices'.
Assigning sensor to a 'Zone'
Proceed as follows to assign the 'Hardware tree' to the 'Detection tree' without the
'Create and Assign' function:
2. Open 'Detection area' > 'Section' in the tree view.
3. Highlight 'Zone' or 'Logical channel', if pre-configuration has been carried out up to
this level.
4. Open the 'Assign dialog' window.
The 'Hardware tree' is depicted in the 'Assign dialog' window. The elements
that can be assigned are highlighted.
5. Mark the corresponding sensor.
'Zone' or 'Logical channel' is assigned to the sensor.
130
A6V10333423_a_en_US
01/18/2012
'Control' task card

Creating a control tree
11
11 'Control' task card

Controls are configured in the 'Control' task card. The controls are combined in the
following control groups:
'Alarming control group': Controls for remote transmission ('RT controls', 'City tie',
'Leased line') and 'NAC controls'
'Fire control group': Controls for building equipment
'Evac control group': Controls for alarm and announcement devices
'Releasing control group': Controls for releasing systems
Each control group has one or more control elements, which each have one or more
inputs (causes) and one or more outputs (effects).
You will find more information about the control groups in the following chapters.
11.1
Creating a control tree
Task card 'Control' with the tree view and window 'New element'
To create the 'Control tree', proceed as follows:

1. Select the 'Control' task card.
2. Highlight a 'Panel' in the tree view.
4. In the 'Type:' field, select a 'Control group'.
5. Enter the number of elements required in the 'Amount:' field.
6. Click on 'Add'.
The elements are created.
8. Highlight a 'Control group' in the tree view.
9. Select a control element in the 'Type:' field of the 'New element' window.
10. Enter the number of elements required in the 'Amount:' field.
11. Click on 'Add'.
The elements are created.
In 'Panels' with the 'Alarming pre-configured' template, some elements are already
created, e.g. 'Alarming control group' with pre-configured 'RT controls'.
131
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

'Alarming control group'
See also
Creating an element [ 60]
11.2

The 'Alarming control group' contains the control elements for the most frequently used
alarming functions of a 'Site'. The control elements are in particular controlled using the
alarm verification concept and intervention concept.
The 'Alarming control group' contains the following control elements:
Controls for remote transmission:
'RT controls': 'RT alarm control', 'RT trouble control', 'RT supervisory control',
'RT programmable control'
'City tie'
'Leased line': 'Leased line alarm', 'Leased line supervisory', 'Leased line
trouble'
'DACT control'
'NAC controls'
The 'City tie' and 'Leased line' control elements are not present in the 'Control tree' as
standard. They must be created if necessary. See chapter 'Creating a control tree'.
There is only one 'Alarming control group' for each 'Panel'.
132
A6V10333423_a_en_US
01/18/2012
'Control' task card

11.2.1
11
'RT control' elements
'RT control' elements in the tree view
The 'RT controls' can be used to transfer events to a central location, e.g. the fire
department control panel.
The following types of 'RT controls' exist:
'RT alarm control': Transfer of 'ALARM' events
'RT trouble control': Transfer of 'Trouble' events
'RT supervisory control': Transfer of 'Supervisory' events
'RT programmable control': Freely configurable control
The 'AVC' or 'IC' of an element can be assigned in the 'Detection tree' as causes of the
control. The corresponding remote transmission outputs on the periphery board can be
assigned as effects of the control.
Causes
'AVC'/'IC'
Control
Effects
'RT alarm control'
'RT trouble control'

'RT supervisory control'
'RT programmable control'
Remote transmission outputs

on the periphery board
Causes and effects of the control

In 'Panels' with the 'Alarming pre-configured' template, the causes and effects of the
most frequently used alarming controls are already assigned.
The properties of the 'RT controls' are described in the chapter 'Properties of the
controls for remote transmission [ 141]'.
133
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.2.2
Assigning 'RT control' elements

In 'Panels' with the 'Alarming pre-configured' template, the causes and effects of the
most frequently used alarming controls are already assigned.
Assigning cause
Assigning a cause of 'RT control' elements
To assign a cause, proceed as follows:

2. Open the 'Panel' > 'Alarming control group' > 'RT alarm control' / 'RT trouble
control' / 'RT supervisory control' / 'RT programmable control' in the tree view.
3. Highlight the 'Causes' element.
4. In the toolbar, click 'Assign'.
The 'New cause dialog' window opens.
The 'Detection tree' is depicted on the right in the window. The elements that
can be assigned are highlighted.
5. Select the element you want.
The element is assigned to 'Causes'.
134
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning effect
Assigning an effect of 'RT control' elements
To assign an effect, proceed as follows:

2. Open the 'Panel' > 'Alarming control group' > 'RT alarm control' / 'RT trouble
control' / 'RT supervisory control' / 'RT programmable control' in the tree view.
3. Highlight the 'Effects' element.
The 'New effect dialog' window opens.
The 'Hardware tree' is depicted on the right in the window. The elements that
5. Select the corresponding output on the periphery board.
The output is assigned to 'Effects'.
135
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.2.3
'City tie' element
'City tie' element in the tree view
The 'City tie' element can be used to transfer alarms directly to the fire department
control panel. The 'AVC' or 'IC' of an element can be assigned in the 'Detection tree' as
causes of the control. The corresponding outputs of the 'Leased line / city tie module'
can be assigned as effects of the control.
Causes
'AVC'/'IC'
Control
'City tie'
Effects
'Leased line / city tie module'

The properties of the 'City tie' element are described in the chapter 'Properties of the
controls for remote transmission'.
See also
'City tie' and 'Leased line' elements [ 107]
136
A6V10333423_a_en_US
01/18/2012
'Control' task card

11.2.4
11
Assigning the 'City tie' element

Assigning cause
Assigning a cause of the 'City tie' element

2. Open 'Panel' > 'Alarming control group' > 'City tie' in the tree view.
137
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

Assigning effect
Assigning an effect of the 'City tie' element

2. Open 'Panel' > 'Alarming control group' > 'City tie' in the tree view.
5. Select the 'Alarm/supervised' output of the 'Leased line / city tie module'.
See also
138
A6V10333423_a_en_US
01/18/2012
'Control' task card

11.2.5
11
'Leased line' elements
'Leased line' elements in the tree view
The 'Leased line' elements can be used to transfer events to a central location, e.g. the
fire department control panel, via a leased telephone line.
The following elements with the 'Leased line' function exist:
'Leased line alarm': Transfer of 'ALARM' events
'Leased line supervisory': Transfer of 'Supervisory' events
'Leased line trouble': Transfer of 'Trouble' events
The 'AVC' or 'IC' of elements can be assigned in the 'Detection tree' as causes of the
control. The corresponding outputs of the 'Leased line / city tie module' can be
Causes
'AVC'/'IC'
Control
'Leased line alarm'

'Leased line supervisory'
'Leased line trouble'
Effects
'Leased line / city tie module'

The properties of the 'Leased line' element are described in the chapter 'Properties of
the controls for remote transmission'.
See also
139
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.2.6
Assigning 'Leased line' elements

Assigning cause
Assigning a cause of 'Leased line' elements

2. Open 'Panel' > 'Alarming control group' > 'Leased line alarm' / 'Leased line
supervisory' / 'Leased line trouble' in the tree view.
Assigning effect
Assigning an effect of 'Leased line' elements

2. Open 'Panel' > 'Alarming control group' > 'Leased line alarm' / 'Leased line
supervisory' / 'Leased line trouble' in the tree view.
140
A6V10333423_a_en_US
01/18/2012
'Control' task card

11

5. Select the corresponding output of the 'Leased line / city tie module'.
See also
11.2.7
Properties of the controls for remote transmission

In the detail editor of the 'RT control', 'City tie' and 'Leased line' elements, you can set
the following properties in the 'Overview' tab:
Properties in the 'Overview' tab
'RT ch. connected to Fire Department'

This setting specifies whether the 'RT channel' is connected to the fire department
control panel.
You can set the following properties in the 'Details' tab:
Properties in the 'Details' tab
'Control test allowed'

This setting specifies whether the control can be switched to 'Control test mode' mode
using the corresponding command.
141
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.2.8
'DACT control' element

Visibility on the 'Site' or a 'Panel' can be assigned as a cause of the control. The
'Supervised (open/short circuit) DACT channel' element can be assigned as an effect
of the control.
Causes
Control
Visibility on 'Site' or 'Panel'
'DACT control'
Effects
'Supervised (open/short
circuit) DACT channel'

See also
Dialer module (DACT) [ 113]
11.2.9
Assigning the 'DACT control' element

Assigning cause
Assigning a cause of the 'DACT control' element

2. Open 'Panel' > 'Alarming control group' > 'DACT control' in the tree view.
The 'Assign dialog' window opens.
The elements that can be assigned are highlighted.
5. Select the visibility you want.
142
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning effect
Assigning an effect of the 'DACT control' element

2. Open 'Panel' > 'Alarming control group' > 'DACT control' in the tree view.
5. Select the 'DACT control' element.
'DACT control' is assigned to 'Effects'.
See also
Dialer module (DACT) [ 113]
143
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.2.10
Properties of the 'DACT control' element

In the detail editor of the 'DACT control' element, you can set the following in the
'Details' tab:
The following can be set in the 'DACT accounts' tab:
Properties in the 'DACT accounts' tab
144
A6V10333423_a_en_US
01/18/2012
'Control' task card

11.2.11
11
'NAC control' elements
'NAC control' elements in the tree view
The 'NAC controls' is used to control NAC applications, e.g. NAC circuits on the
periphery board or the 'Control Point Module HCP'.
The following 'NAC controls' exist:
'Local NAC control'
'General NAC control'
The controls can be used for a variety of applications, e.g. for various causes and AVC
settings.
The following event categories can be assigned to elements of the 'Detection tree' as
causes of the control:
'AVC'/'IC'
Releasing discharge: 'Releasing first alarm', 'Releasing pre-discharge', 'Releasing

discharged'
Tornado alarm
NAC circuits ('Onboard NAC' and 'Optional NAC (FCI2011)') and periphery devices
can be assigned to NAC functions as effects of the control.
Causes
Event:
'AVC'/'IC'
Releasing discharge
Tornado alarm
Control
'Local NAC control'

'General NAC control'
Effects
NAC circuit ('Onboard NAC'

and 'Optional NAC
(FCI2011)')
Periphery device with NAC
function, e.g. 'HCP'

You can assign various priorities to the events. To do this, you have to assign the
event to the corresponding cause group:
'Causes priority 1 (high)'
'Causes priority 2 (medium)'
'Causes priority 3 (low)'
145
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

For each priority, you can set different output modes, e.g. audible signals and beacons.
If events of different priorities occur at the same time, the settings for the highest
priority are used. If several causes are assigned to the same priority, the causes are
assigned to an OR function.
See also
'Onboard NAC' element [ 105]
'Optional NAC (FCI2011)' element [ 105]
HCP with 'NAC/speaker/telephone' [ 98]
11.2.12
Assigning 'NAC control' elements

Assigning cause
Assigning a cause of 'NAC control' elements

2. Open 'Panel' > 'Alarming control group' > 'Local NAC control' or 'General NAC
control' in the tree view.
3. Highlight the 'Causes priority 1 (high)', 'Causes priority 2 (medium)' or 'Causes
priority 3 (low)' element.
5. In the left-hand side of the window, select 'AVC', 'Releasing' or 'Tornado' and select
the event category you want.
The element is assigned to the cause.
146
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning effect
Assigning an effect of 'NAC control' elements

2. Open 'Panel' > 'Alarming control group' > 'Local NAC control' or 'General NAC
control' in the tree view.
5. Select an NAC circuit or a periphery device with NAC function.
The element is assigned to 'Effects'.
See also
'Onboard NAC' element [ 105]
'Optional NAC (FCI2011)' element [ 105]
HCP with 'NAC/speaker/telephone' [ 98]
147
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.2.13
Properties of 'NAC control' elements

In the detail editor of the 'Local NAC control' and 'General NAC control' elements, you
can set the following properties in the 'Overview' tab:
Settings in the 'Overview' tab
'NAC output mode'

This setting defines the output mode for activating the 'NAC control'.
'Silenceable'
This setting specifies whether the 'NAC control' can be silenced.
'Silenceable in case of Waterflow event'

This setting specifies whether the 'NAC control' can be silenced when it was triggered
by a 'Waterflow ALARM'.
The 'Silenceable in case of Waterflow event' checkbox can only be checked when the
'Silenceable' checkbox is checked.
'Silence horns only'

This setting specifies whether horns and beacons, or just horns, can be silenced.
The 'Silence horns only' checkboxes can only be checked with the following settings:
'NAC output mode' is set to 'Horn/strobe'.
The 'Silenceable' checkbox is checked.
148
A6V10333423_a_en_US
01/18/2012
'Control' task card

'Fire control group'
11

11.3

The 'Fire control group' includes the following control elements:
'Fire control': Control for building equipment
'ILED control': Control for ILEDs
You will find more information on this in the following chapters.
11.3.1
'Fire control' element
'Fire control' element in the tree view
The 'Fire control' element is used to control equipment during a certain event, e.g.
closing fire doors or bypassing 'Zones'. Events and inputs can be assigned within the
'Site' as causes of the control. Commands and outputs can be assigned as effects of
the control.
Causes
Event
Input
Control
'Fire control'
Effects
Command
Output with or without
confirmation

The assigned input must be in the same 'Panel' as the control.
Several causes, which can be combined with AND, OR and NOT functions, can be
configured for a control.
The 'Fire control' can be created with the following templates:
'Standard fire control'
'Door holders'
In the 'Door holders' template, the 'Controls a 'door holders' application' checkbox is
checked in the detail editor as standard. You will find more information about this in the
chapter 'Properties of element 'Fire control''.
149
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.3.2
Assigning 'Fire control' element

Assigning cause
Assigning cause of the 'Fire control' element

2. Open 'Panel' > 'Fire control group' > 'Fire control' in the tree view.
The 'New cause dialog, Assign dialog' window opens.
5. In the left-hand side of the window, select an event category or an input.
The appropriate tree is shown in the right side of the window. The elements
150
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning effect
Assigning effect of the 'Fire control' element
The figure above shows two trees, one below the other. The lower tree appears only
when a confirmation input can be assigned.
2. Open 'Panel' > 'Fire control group' > 'Fire control' in the tree view.
5. In the left-hand side of the window, select an input or command.
151
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.3.3
Properties of element 'Fire control'

In the detail editor of the 'Fire control' element, you can set the following properties in
the 'Overview' tab:
'START mode'
This setting specifies the conditions for activating 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
'Formula' field is true.
'Value rising and >= threshold (all causes OR-combined)': The control is activated
as soon as a certain number of events occur in the corresponding event category.
This value is in the detail editor of the cause element, in the 'Threshold' field.
'STOP mode'
This setting specifies the conditions for deactivating the control. The following
conditions are possible:
'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
'Formula' field is false.
'All causes inactive': The control is deactivated when all assigned causes are
inactive.
'Formula'
Several causes can be linked with a formula. The following operators are possible:
OR = '+'
AND = '*'
NOT = ''
The operators can also be used mixed with brackets.

Example: '1 * (2 + 3)' means '1 AND (2 OR 3)'.
If no formula has been defined, all causes are linked with the OR function.
152
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Delay times and time-out
'Activation delay': Activation of the control is delayed by the set time when the
condition is met.
'Deactivation delay': Deactivation of the control is delayed by the set time when the
condition is met.
'Activation timeout': The time-out is started when the control is activated. Once the
set time has elapsed, the control is automatically deactivated, even if the conditions
for activation are still satisfied.
The 'Activation timeout' property can only be set when the 'Enabled' checkbox is
checked.
'Controls a 'door holders' application'

This setting specifies whether the control is used for a fire door. If the checkbox is
checked, fire doors are automatically closed when the control is bypassed. This
prevents fire doors remaining open in an alarm if the control was bypassed.
If the control was created with the 'Door holders' template, the 'Controls a 'door
holders' application' checkbox is checked as standard.

This setting specifies whether the control can be switched to 'Control test mode' mode.
See also
Properties of the assigned cause elements [ 158]
153
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.3.4
'ILED control' element
'ILED control' element
The 'ILED control' element can be used to control ILEDs. Events and inputs can be
assigned within the 'Site' as causes of the control. ILEDs can be assigned as effects of
the control.
Causes
Event
Input
Control
'ILED control'
Effects
'ILED'

You can assign various priorities to the events. To do this, you have to assign the
event to the corresponding cause group:
'Causes priority 1 (high)'
'Causes priority 2 (medium)'
'Causes priority 3 (low)'
For each priority, you can set an LED color. If events of different priorities occur at the
same time, the settings for the highest priority are used. If several causes are assigned
to the same priority, the causes are assigned to an OR function.
154
A6V10333423_a_en_US
01/18/2012
'Control' task card

11.3.5
11
Assigning an 'ILED control' element

Assigning cause
Assigning a cause of the 'ILED control' element

2. Open 'Panel' > 'Fire control group' > 'ILED control' in the tree view.
3. Highlight the 'Causes priority 1 (high)', 'Causes priority 2 (medium)' or 'Causes
priority 3 (low)' element.
155
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

Assigning effect
Assigning effect of the 'ILED control' element

2. Open 'Panel' > 'Fire control group' > 'ILED control' in the tree view.
5. Select the output for the ILED you want.
To quickly navigate to a certain device in the 'New effect dialog' window, you can
check the 'Use serial no.:' checkbox and select the serial number of the device you
want from the drop-down list.
156
A6V10333423_a_en_US
01/18/2012
'Control' task card

11.3.6
11
Properties of the 'ILED control' element

In the detail editor of the 'ILED control' element, you can set the following properties in
the 'Overview' tab:
LED color
For each priority of the causes, you can set an LED color: 'Red', 'Yellow' or 'Green'.

157
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.3.7
Properties of the assigned cause elements

You can set additional properties in the assigned cause elements of the 'Fire control'
and 'ILED 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:
Properties in the detail editor of the cause element when assigning to an event
'Event category':
Event category that is assigned to the control as a cause.
'Threshold':
The value in this field specifies how many events of the corresponding event category
have to occur in the element or subtree to activate the control. If the control was
deactivated, it is reactivated when a new event of the specified event category occurs.
This setting only applies when the 'Value rising and >= threshold (all causes ORcombined)' setting is selected in the 'START mode' field of the detail editor of the
control.
'Include sub-tree':
This setting specifies whether only events in the element are taken into account or also
those in the subtree.
'Sensor criteria':
This setting specifies which detector sensor type has to be active to activate the cause.
The setting is only possible when the cause is assigned to an automatic detector or a
superordinate element.
'ACTIVE if no communication to source':
This setting specifies the status of the cause that the assigned element has if there is
no connection to the 'Panel'. The status can be ACTIVE or INACTIVE.
158
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning to an 'AVC'/'IC' event

If the cause of the control is an 'AVC' or 'IC' event, you can specify an additional
criterion for activating the cause in the assigned cause element.
Properties in the detail editor of the cause element when assigning to an 'AVC'/'IC' event
The 'AVC/IC state' setting specifies what the 'AVC' or 'IC' status must be for the cause
to be active. The following settings are possible:
'AVC/IC: Local alarming': The 'AVC'/'IC' is in the 'Local alarming only' status. There
is no delay time.
'AVC/IC: Global alarming': The 'AVC'/'IC' is in the 'Global alarming only' status.
'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' was
ended with 'Acknowledge'.
For the 'AVC/IC state' property, a maximum of one checkbox may be checked.
Otherwise an error will be 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 checked.
The cause is only active if a 'Fire ALARM' triggers the 'AVC' and the 'AVC' is in the
'Global alarming only' status.
159
A6V10333423_a_en_US
01/18/2012
11
'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:
Properties in the detail editor of the cause element when assigning to an input
'Evaluation filter time': This setting specifies the minimum signal activation time for the
assigned input before the control is evaluated as active.
See also
Properties of element 'Fire control' [ 152]
11.3.8
Properties of the assigned effect elements

You can set additional properties in the assigned effect elements of a 'Fire control'. The
settings are described in the following sections.
Assigning to a command
If the effect of the control is a command, you can set the following properties in the
assigned effect element:
Properties in the detail editor of the effect element when assigning to a command
'Inverted': This setting specifies whether the command is performed when the
control is activated or deactivated. If the checkbox is unchecked, the command is
performed as long as the control is active. If the checkbox is checked, the
command is performed as long as the control is inactive.
'Command': Command that is assigned to the 'Fire control' as an effect.
'Command parameter': This setting specifies which parameters should be set by

the command, e.g. when 'Set ASD / Sensitivity level' was selected as a command.
160
A6V10333423_a_en_US
01/18/2012
'Control' task card

'Evac control group'
11
Assigning to an output with confirmation

If the effect of the control is an output with confirmation, you can set the following
properties in the assigned effect element:
Properties in the detail editor of the effect element when assigning to an output with confirmation
'Supervision time': This setting specifies the time limit within which confirmation must
take place after the output was activated.
11.4

The 'Evac control group' includes the 'Universal evac control' control elements. You will
find more information on this in the following chapters.
See also
Properties of element 'Fire control' [ 152]
11.4.1
'Universal evac control' element
'Universal evac control' element in the tree view
The 'Universal evac control' element can be used to control optical and acoustic alarm
devices for evacuation. Events and inputs can be assigned within the 'Site' as causes
of the control. Outputs and alarm devices can be assigned, e.g. 'Audible base' as
effects of the control.
Causes
Event
Input
Control
'Universal evac control'
Effects
Output
Alarm device
161
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.4.2
Assigning a 'Universal evac control' element

Assigning cause
Assigning cause of the 'Universal evac control' element

2. Open 'Panel' > 'Evac control group' > 'Universal evac control' in the tree view.
162
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning effect
Assigning effect of the 'Universal evac control' element

2. Open 'Panel' > 'Evac control group' > 'Universal evac control' in the tree view.
To quickly navigate to a certain device in the 'New effect dialog' window, you can
check the 'Use serial no.:' checkbox and select the serial number of the device you
want from the drop-down list.
11.4.3
Properties of the 'Universal evac control' element

In the detail editor of the 'Universal evac control' element, you can set the following
properties in the 'Overview' tab:
163
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

'START mode'
are possible:
a command.
'STOP mode'
with a command.
inactive.
'Formula'
OR = '+'
AND = '*'
NOT = ''

condition is met.
condition is met.
checked.
164
A6V10333423_a_en_US
01/18/2012
'Control' task card

11

See also
11.4.4

You can set additional properties in the assigned cause elements of the 'Universal
evac control'. The settings are described in the following sections.
'Event category':
'Threshold':
control.
165
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

'Include sub-tree':
'Sensor criteria':

is no delay time.

running.
166
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Example:
Assigning to an input
If the cause is an input, you can set the following properties in the assigned cause
element of the control:
Properties in the detail editor of the cause element when assigning to an input
'Delay': This setting specifies by how long activation of the control is delayed after
the conditions for activation are satisfied.
'Evaluation filter time': This setting specifies the minimum signal activation time for
the assigned input before the control is evaluated as active.
See also
Properties of the 'Universal evac control' element [ 163]
167
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

'Releasing control group'
11.4.5
Properties of the assigned effect elements

You can set additional properties in the assigned effect elements of a 'Universal evac
control'.
Properties in the detail editor of the effect element
'Activation timeout': The time-out is started when the control is activated. After the set
time has elapsed, the assigned device is automatically deactivated.
checked.
11.5

The 'Releasing control group' includes the following control elements:
'Agent releasing control': Control of agent releasing systems
'Sprinkler releasing control': Control of sprinkler systems
11.5.1
'Agent releasing control' element
'Agent releasing control' element in the tree view
The 'Agent releasing control' element is used to control releasing systems. 'ALARM'
events and inputs can be assigned within the 'Panel' as causes of the control.
Releasing circuits can be assigned as effects of the control.
Manual activation always overrides the 'Abort' function.
168
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Three types of cause exist for the 'Agent releasing control':
'Causes RELEASING': Causes for automatic or manual activation of releasing

discharge.
Automatic discharge: Assigning to the ' --All automatic Fire ALARMS' event
category in an element of the 'Detection tree', e.g. in a 'Section' or an
'Automatic alarm zone'.
Manual discharge: Assigning to the ' --Manual Fire ALARM' event category in
the element of the 'Detection tree' that contains the 'Releasing manual pull
station', e.g. in a 'Section' or a 'Manual alarm zone'.
Assigning to 'Master release' via an input
'Causes ABORT': Causes for activating the 'Abort' function. Assigning to an 'Abort
button' via an input.
'Causes LOW AGENT': 'Causes LOW AGENT' can be assigned to a pressure

sensor that measures pressure in the releasing agent container via an input.
If you are using more than one 'Releasing manual pull station', you have two options:
Assign all 'Releasing manual pull stations' to the same 'Manual alarm zone' and only
assign these 'Zone' to 'Causes RELEASING'.
OR
Assign all 'Releasing manual pull station' with a 'Manual alarm zone' and assign all of
these 'Zones' to 'Causes RELEASING'.
Causes
Control
Event:
' --All automatic Fire
ALARMS'
' --Manual Fire
ALARM'
Input:
'Abort button'
Pressure sensor
'Master release'
'Agent releasing control'
Effects
Releasing circuit

Several causes, which can be assigned to an OR function, can be configured for a
control.
See also
Releasing module [ 110]
169
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.5.2
Assigning an 'Agent releasing control' element

Assigning cause
Assigning a cause of the 'Agent releasing control' element

2. Open 'Panel' > 'Releasing control group' > 'Agent releasing control' in the tree view.
3. Highlight 'Causes RELEASING', 'Causes ABORT' or 'Causes LOW AGENT'.
The 'New cause dialog window is opened.
170
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning effects
Assigning an effect of the 'Agent releasing control' element

2. Open 'Panel' > 'Releasing control group' > 'Agent releasing control' in the tree view.
5. Select the releasing circuit you want.
See also
171
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.5.3
Properties of the 'Agent releasing control' element

In the detail editor of the 'Agent releasing control' element, you can set the following
'Pre-discharge alarm threshold'

This setting specifies how many automatic fire alarms are necessary to trigger the 'Predischarge' phase.
'Pre-discharge period'
This setting specifies the duration of the 'Pre-discharge' phase. Once this time has
elapsed, releasing discharge is activated. The phase is interrupted by manual
activation or 'Abort'.
'Manual release delay'

This setting specifies how long releasing discharge is delayed for after it was activated
on a 'Releasing manual pull station'.
'Abort function'
This setting specifies which 'Abort' function is used.
'Investigation time'
This setting indicates how long releasing discharge is delayed for when an 'Abort' was
triggered during the 'Pre-discharge' phase. The setting depends on the 'Abort' function
selected:
'ULI delay (UL International)': Pre-set to 10 seconds
'IRI delay (Industrial Risk Insurers)': Pre-set to the duration of the 'Pre-discharge'
phase
'AHJ delay (Authority Having Jurisdiction)': Pre-set to the duration of the 'Predischarge' phase
'NYC delay (New York City)': Configurable delay time between 0 and 2 minutes
172
A6V10333423_a_en_US
01/18/2012
'Control' task card

11

11.5.4
'Sprinkler releasing control' element
'Sprinkler releasing control' element in the tree view
The 'Sprinkler releasing control' element controls sprinkler systems. Events and inputs
can be assigned within the 'Site' as causes of the control. Releasing circuits can be
Causes
Event
Input
Control
Effects
'Sprinkler releasing control'
Releasing circuit

See also
173
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.5.5
Assigning a 'Sprinkler releasing control' element

Assigning cause
Assigning a cause of the 'Sprinkler releasing control' element

2. Open 'Panel' > 'Releasing control group' > 'Sprinkler releasing control' in the tree
view.
3. Highlight 'Causes'.
174
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
Assigning effects
Assigning an effect of the 'Sprinkler releasing control' element

2. Open 'Panel' > 'Releasing control group' > 'Sprinkler releasing control' in the tree
view.
5. Select the releasing circuit you want.
See also
175
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.5.6
Properties of the 'Sprinkler releasing control' element

In the detail editor of the 'Sprinkler releasing control' element, you can set the following
'START mode'
are possible:
a command.
'STOP mode'
with a command.
inactive.
'Formula'
OR = '+'
AND = '*'
NOT = ''

176
A6V10333423_a_en_US
01/18/2012
'Control' task card

11
condition is met.
condition is met.
checked.

See also
177
A6V10333423_a_en_US
01/18/2012
11
'Control' task card

11.5.7

You can set additional properties in the assigned cause elements of the 'Agent
releasing control' and 'Sprinkler releasing control'. The settings are described in the
following sections.
'Event category':
'Threshold':
control.
'Include sub-tree':
'Sensor criteria':
178
A6V10333423_a_en_US
01/18/2012
'Control' task card

11

is no delay time.

running.
Example:
See also
Properties of the 'Sprinkler releasing control' element [ 176]
179
A6V10333423_a_en_US
01/18/2012
12
'Operation' task card

Global system configuration
12 'Operation' task card

The 'Operation' task card contains the logical elements for the global system
configuration and for configuring the operation and indication units.
12.1
'Global system configuration' element
The 'Global system configuration' element is present once per 'Site' and contains the
following elements:
'Global behavior'
'Global system time'
'Country settings'
12.1.1
System behavior
The 'Global behavior' element contains the system behavior settings.
In the detail editor of the 'Global behavior' element, you can set the following properties
'System wide bypass of all buzzers enabled':

This setting specifies whether the 'Buzzers' of all 'Panels' can be bypassed across the
system with one command.
'Self-restoring supervisories':
This setting specifies whether the 'Panel' automatically removes an incoming
'Supervisory' message or generates an outgoing 'Supervisory' message if the
'Supervisory' status no longer exists.
180
A6V10333423_a_en_US
01/18/2012

12
'Self-restoring troubles':
This setting specifies whether the 'Panel' automatically removes an incoming 'Trouble'
message or generates an outgoing 'Trouble' message if the 'Trouble' status no longer
exists.
'Single event acknowledge required':
This setting specifies whether every event has to be acknowledged individually in
accordance with NFPA 72D.
'Enabled':
This setting specifies whether a reminder is displayed before a temporary restricted
bypass of a 'Zone' elapses and the 'Zone' is automatically enabled again.
'Expiry reminder for time lim. BYPASS of a zone':
This setting specifies when the reminder is displayed. If e.g. the setting is '00:05', a
reminder is displayed five minutes before the bypass duration elapses and the 'Zone' is
automatically switched back on. This setting applies to all 'Zones' within the 'Site'.
'Walk test activation mode':
This setting specifies which alarm devices are activated in 'Walk test' mode.
12.1.2
Master clock
The 'Global system time' element shows which 'Panel' is the master clock. When the
first 'Panel' is created, Cerberus-Engineering-Tool automatically assigns this element
to the first 'Panel' (address 1). It is possible that the link to the 'Panel' should be
deleted or changed. In this instance, the link has to be created again.
Assigning the master clock
181
A6V10333423_a_en_US
01/18/2012
12

Person Machine Interface (PMI)
To assign the master clock, proceed as follows:

1. Select the 'Operation' task card.
2. Open 'Global system configuration' in the tree view.
3. Highlight 'Global system time'.
The 'Hardware tree' is displayed in the right-hand side of the window.
5. Select the corresponding 'Panel' and click on 'Assign'.
'Global system time' is assigned to the 'Panel'.
12.1.3
Country settings
Country-specific settings are defined in the 'Country settings' element. The user cannot
change these settings.
12.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 about these elements in the following chapters.
12.3
Basic settings
The basic settings for the Person Machine Interface are contained in the detail editor of
the 'PMI' element. You can set the following properties in the 'Overview' tab:
'Logout timeout'
This setting specifies the time after which the Person Machine Interface of the Panel'
automatically switches back to 'Default access level' if no key is pressed.
The time-out is only used if the 'Enabled' checkbox is ticked.
182
A6V10333423_a_en_US
01/18/2012

Basic settings
12
'Default access level'

This setting specifies the default access level of the 'Panel'. If the 'Panel' has a key
switch, this setting applies to the 'off' position.
'Access level 'key switch''

If the 'Panel' has a key switch, this setting specifies the access level in the 'on' position.
'TROUBLE resound [UL requirement: enabled]'

If this checkbox is checked, the 'Resound interval' time is started when a 'Trouble'
event is acknowledged. The 'Buzzer' sounds if the event is still present after this time
has elapsed. If the 'Buzzer' is silenced or a new 'Trouble' event occurs, the 'Resound
interval' is started again. This checkbox must be checked for UL conformity.
'SUPERVISORY resound [UL requirement: enabled]'

If this checkbox is checked, the 'Resound interval' time is started when a 'Supervisory'
event is acknowledged. The 'Buzzer' sounds if the event is still present after this time
has elapsed. If the 'Buzzer' is silenced or a new 'Supervisory' event occurs, the
'Resound interval' is started again. This checkbox must be checked for UL conformity.
'Resound interval [UL requirement: 24h]'

This setting specifies the time interval at which the 'Buzzer' sounds. This property must
be set to 24 hours for UL conformity.
'Enabled' and 'Inhibit reset timeout'

If the checkbox is checked, the 'Reset' command on the Person Machine Interface is
blocked for a certain time after the first 'ALARM' event. The blocking duration can be
specified in the 'Inhibit reset timeout' field.
'Enabled' and 'Inhibit silence audibles timeout'

If the checkbox is checked, 'Audibles' cannot be silenced during a certain time. The
blocking duration can be specified in the 'Inhibit silence audibles timeout' field.
183
A6V10333423_a_en_US
01/18/2012
12

LEDs
12.4
LEDs
'LEDs' element in the tree view
The LEDs on the Person Machine Interface signal events and conditions. In addition,
the LEDs support the operator's orientation. Each LED can be assigned to up to twelve
causes. You can set the LED properties for each cause, e.g. 'LED mode' and 'Color'.
You can assign the following types of cause:
Pre-defined cause: Select an event from a pre-defined list. If the event occurs
within the visibility of the 'Panel', the LED is activated.
Event in a certain element within the 'Site': Select an event and the element in
which the event must occur for the LED to be activated.
You will find more information about this in the following chapters.
When you configure an LED, you must change the inscription of the LED on the
Person Machine Interface if necessary. You will find editable inscription strips for the
Person Machine Interface in document A6V10333421. See chapter 'Applicable
documents'.
See also
184
A6V10333423_a_en_US
01/18/2012

LEDs
12.4.1
12
Assigning the hardware ID to the LED

The figure below shows how to assign the hardware ID to the corresponding LED on
the Person Machine Interface. The numbers correspond to the hardware ID of the
LED.
SOFTKEY
1
SOFTKEY
2
SOFTKEY
3
Gas ALARM
7
8
9
Supervisory
Audibles
On
Silenced
Trouble
Acknowledge
Partial System
Disabled
Reset
User 1
User 2
User 3
System
Power
Ground Fault
13
14
15
16
17
18
User 4
Active
Trouble / Bypassed
User 5
Active
Trouble / Bypassed
User 6
Active
Trouble / Bypassed
22
23
User 7
24
25
User 9
rs
kl
8
0
2
5
hi
bc
Trouble
002
tu
ZONE
356 / 1
1/2/1 Customer text
ef
3
no
wx
Device missing
001
08/27/2010 02:31 PM
ZONE
352 / 1
1/2/21/203 10474A2
ALARM
000 000 000 007

ALM GAS SUP TBL
pq
Fx20xx
yz
9
#
C ok
User 8
User 10
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.
Detail editor of an LED with details of the hardware ID
12.4.2
Assigning a pre-defined cause

You can assign every configurable LED to one or more pre-defined causes. If you
assign several causes, the LED properties must be different, e.g. 'Priority', 'LED mode',
or 'Color'.
Assigning an LED to a pre-defined cause
185
A6V10333423_a_en_US
01/18/2012
12

LEDs
To assign an LED to a pre-defined cause, proceed as follows:

2. Open 'Panel' > 'PMI' > 'LEDs' in the tree view.
3. Highlight an LED.
5. Select 'Pre-defined causes' on the left of the window and highlight 'Standard' on the
right of the window.
The 'Cause / Undefined' element is created under the LED.
7. Highlight the 'Cause / Undefined' element.
8. Set the properties you want in the detail editor.
9. Change the inscription of the LED on the Person Machine Interface if necessary.
You will find editable inscription strips in document A6V10333421. See chapter
Properties of the assigned cause element

In the detail editor of the assigned cause element, you can set the following properties
'Event filter': Event that activates the cause and therefore the LED. All events within
the configured visibilty of the 'Panel' are evaluated.
'Color': Color of the LED when activated
'LED mode': Light mode of the LED when activated
'Priority': Priority of cause compared with other causes assigned to the same LED.
186
A6V10333423_a_en_US
01/18/2012

LEDs
12.4.3
12
Assigning an event
You can assign every configurable LED to one or more events within the 'Site'. If you
assign several causes, the LED properties must be different, e.g. 'Priority', 'LED mode'
or 'Color'.
Assigning an LED to an event
To assign an LED to an event, proceed as follows:

5. In the left-hand side of the window, select an event category.
6. In the right-hand side of the window, select a tree and an element.
The LED is assigned to the cause.
8. Highlight the assigned cause element and set the properties you want in the detail
editor.
187
A6V10333423_a_en_US
01/18/2012
12

Standard keys

12.5
'Color': Color of the LED when activated
'LED mode': Light mode of the LED when activated
Standard keys
'Standard keys' element in the tree view
You can assign a function or toggle function to each standard key. This allows you to
quickly perform frequently used actions and commands.
You can configure the following types of function:
'Dialog': The key is assigned to a certain view on the display of the Person Machine
Interface. When the key is pressed, the view is shown on the display, e.g. 'Dialog
'Config viewer, Topology'' > 'Detection tree'.
'Action': The key is assigned to a pre-defined action. When the key is pressed, the
action is performed, e.g. 'BYPASS all audibles'.
188
A6V10333423_a_en_US
01/18/2012

Favorites
12
Commands:
Command for a certain element: The key is assigned to a command and an

element within the 'Site'. When the key is pressed, the command for this
element is performed, e.g. 'Detector test' for a certain 'Manual alarm zone'.
Command for an element category: The key is assigned to a command and an

element category, e.g. 'Zone' or 'Section'. When the key is pressed, the window
for entering the address for the element category is shown on the display.
Once the address is entered, the command for the corresponding element is
performed.
When you configure a standard key, you must change the inscription of the standard
key on the Person Machine Interface if necessary. You will find editable inscription
strips for the Person Machine Interface in document A6V10333421. See chapter
You will find information about configuring standard keys in the chapter 'Configuring
standard keys and favorites'.
See also
Toggle function [ 199]
12.6
Favorites
'Favorite keys' element in the tree view
There is a maximum of eight favorites, of which three are preconfigured. You can
assign a function to every favorite. This allows you to quickly perform frequently used
actions and commands.
The favorites are shown in the Person Machine Interface display. The first three
favorites are assigned to the three softkeys in the main menu. All of the favorites are
listed in the 'Favorites' menu. To perform a favorite function, you must press the
corresponding key on the keypad.
189
A6V10333423_a_en_US
01/18/2012
12

Favorites
Display of the Person Machine Interface with the main menu and the three softkeys
You will find information about the keys in the Person Machine Interface in the
document A6V10333380. See chapter 'Applicable documents'.
You can configure the following types of function:
'Function': The favorite is assigned to a function from the 'Functions' menu of the
'Panel'. When the key is pressed, the corresponding window for entering the
element category or address is shown on the display of the Person Machine
Interface.
'Dialog': The favorite is assigned to a certain view on the display. When the key is
pressed, the view is shown on the display, e.g. 'Dialog 'Config viewer, Topology'' >
'Detection tree'.
'Action': The favorite is assigned to a pre-defined action. When the key is pressed,
the action is performed, e.g. 'BYPASS all audibles'.
Commands:
Command for a certain element: The favorite is assigned to a command and an

element within the 'Site'. When the key is pressed, the command for this
element is performed, e.g. 'Detector test' for a certain 'Manual alarm zone'.
Command for an element category: The favorite is assigned to a command and

an element category, e.g. 'Zone' or 'Section'. When the key is pressed, the
window for entering the address for the element category is shown on the
display. Once the address is entered, the command for the corresponding
element is performed.
You will find information about configuring favorites in the chapter 'Configuring
standard keys and favorites'.
190
A6V10333423_a_en_US
01/18/2012

Favorites
12.6.1
12
Creating favorites
Three favorites are pre-configured. If you want to create more favorites, proceed as
follows:
2. Open 'Panel' > 'PMI' in the tree view.
3. Highlight 'Favorite keys'.
5. Enter the number of favorites required in the 'Amount:' field.
6. Click on 'Add'.
The 'Favorite' element is created.
Window for creating a favorite
12.6.2
Text for favorites

Predefined texts exist for some favorite functions. These are shown on the Person
Machine Interface display. Predefined texts exist for the following favorite functions:
'Function'
'Action'
The predefined text is only displayed if the 'Customer text' field is empty. If you enter
customer text, this is displayed on the Person Machine Interface in its place.
If there are no predefined texts, you must specify 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 customer text on two lines:
Example of customer text on two lines
191
A6V10333423_a_en_US
01/18/2012
12

Configuring standard keys and favorites
12.6.3
Defining position of favorite

The position specifies where the favorite is shown in the 'Favorites' menu. The
positions run from the top left to the bottom right. The favorites with positions '1' to '3'
are assigned to the three softkeys in the main menu.
When you create a favorite, it has position '0' as standard. You have to set the position
to at least '1'.
Detail editor of the favorite with position specification
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. Enter the position of the favorite in the 'Position' field.
The favorites are arranged accordingly.
12.7
12.7.1
Assigning the hardware ID to the standard key

The figure below shows how to assign the hardware ID to the corresponding standard
key on the Person Machine Interface. The numbers correspond to the hardware ID of
the standard key.
SOFTKEY
1
SOFTKEY
2
SOFTKEY
3
Gas ALARM
7
8
9
Supervisory
Audibles
On
Silenced
Trouble
Acknowledge
Partial System
Disabled
Reset
User 1
User 2
User 3
System
Power
Ground Fault
13
14
15
16
17
18
User 4
Active
Trouble / Bypassed
User 5
Active
Trouble / Bypassed
User 6
Active
Trouble / Bypassed
22
23
User 7
24
25
User 9
rs
kl
8
0
hi
bc
ef
3
no
wx
Trouble
002
ZONE
356 / 1
1/2/1 Customer text
~
g
Device missing
001
08/27/2010 02:31 PM
ZONE
352 / 1
1/2/21/203 10474A2
tu
ALARM
000 000 000 007

ALM GAS SUP TBL
pq
Fx20xx
yz
9
#
C ok
User 8
User 10
Assigning the hardware ID to the standard key on the Person Machine Interface
192
A6V10333423_a_en_US
01/18/2012

12
You will find the hardware ID in the detail editor of the standard key in the 'HW ID KEY'
field.
Detail editor of a standard key with details of the hardware ID
Favorites do not have a hardware ID.
12.7.2
Assigning standard keys and favorites

To assign a standard key or favorite to a function, proceed as follows:
2. Open 'Panel' > 'PMI' > 'Standard keys' or 'Favorite keys' in the tree view.
3. Highlight a 'Standard key' or 'Favorite' element.
5. In the left-hand side of the window, select a function type: 'Function', 'Dialog',
'Action' or command.
Depending on the function type selected, the selection in the right-hand side of
the window is adapted. The possible selections are described below.
6. In the right-hand side of the window, select the element you want.
The standard key or favorite is assigned to the function.
8. Change the inscription of the standard key on the Person Machine Interface if
necessary.
193
A6V10333423_a_en_US
01/18/2012
12

Assigning to 'Function'
If you select 'Function' in the left-hand side of the window, you can select 'Standard' in
the right-hand side of the window. You can set the properties of the function in the
detail editor of the assigned function.
Assigning a favorite to a function
'Function' cannot be assigned to a standard key, only a favorite.
Assigning to 'Dialog'
If you select 'Dialog' in the left-hand side of the window, you can select 'Standard' in
the right-hand side of the window. You can set the properties of the view in the detail
editor of the assigned function.
Assigning a standard key or favorite to a 'Dialog' function
194
A6V10333423_a_en_US
01/18/2012

12
Assigning to 'Action'
If you select 'Action' in the left-hand side of the window, you can select a pre-defined
action from the list in the right-hand side of the window.
Assigning a standard key or favorite to an 'Action' function
Assigning to a command for a certain element

If you select a command in the left-hand side of the window, you can select a tree and
the element for which the command is to be performed in the right-hand side of the
window.
Assigning a standard key or favorite to a command and an element
195
A6V10333423_a_en_US
01/18/2012
12

Assigning to a command for an element category

If you select 'Command/element category' in the left-hand side of the window, you can
select a command from the list in the right-hand side of the window. You can define the
element category in the detail editor of the assigned function.
Assigning a standard key or 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.
See also
Properties of the assigned functions [ 197]
196
A6V10333423_a_en_US
01/18/2012

12.7.3
12
Properties of the assigned functions

In the detail editor of functions that are assigned to standard keys and favorites, you
can set different properties depending on the assigned function. The settings are
described in the following sections.
'Access level'
This setting specifies the access level required to perform the function. 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:
Properties in the detail editor of the function
'Function': This setting specifies which function is to be performed from the 'Functions'
menu.
Assigning to 'Dialog'
If the standard key or favorite is assigned to a 'Dialog' function, you can set the
following properties in the detail editor of the function:
Properties in the detail editor of the 'Dialog' function
'Dialog name': View that is to be shown on the display of the Person Machine
Interface.
'Dialog argument': Additional setting for the view. The selection depends on the
setting in the 'Dialog name' field.
197
A6V10333423_a_en_US
01/18/2012
12

Assigning to a command for a certain element

If the standard key or favorite is assigned to a command function for a certain element,
you can set the following properties in the detail editor of the function:
Properties in the detail editor of the command function
'Command parameter': This setting specifies the assigned command in more detail.
If you have assigned e.g. the 'Set ASD / Sensitivity level' command as the function,
you have to set the 'ASD / Sensitivity level' you want.
The 'Command parameter' property is only shown in the detail editor when a
command that requires specification in more detail was assigned.
'Enabled' and 'Reverse command': These settings are used when you configure a
standard key with a toggle function.
Assigning to a command for an element category

If the standard key or favorite is assigned to a command function for an element
category, you can set the following properties in the detail editor of the function:
Properties in the detail editor of the command function
'Enabled' and 'Reverse command': These settings are used when you configure a
standard key with a toggle function.
'Element category': Category of the element for which the command is to be

performed.
See also
198
A6V10333423_a_en_US
01/18/2012

Toggle function
12.8
12
Toggle function
You can assign a command and the associated reverse command to a standard key,
e.g. bypass/enable and activate/deactivate. When the key is pressed, either the
command or the reverse command is performed.
The command that is performed when the key is pressed depends on the current
status of the LED that is assigned to the standard key:
LED inactive: The command is performed the next time the key is pressed.
LED active: The reverse command is performed the next time the key is pressed.
The LED must be configured such that it is active when the command was performed.
Example:
The standard key is assigned to 'Automatic alarm zone' 2.
Command = 'Detector test'
Reverse command = 'Detector test END'
The LED is active if 'Automatic alarm zone' 2 is in the 'Detector test' status.
To configure a standard key with the toggle function, you must first configure the
standard key and then the LED. You will find more information on this in the following
chapters.
You will find the assignment of hardware IDs to the corresponding LED and standard
key on the Person Machine Interface in the following chapters: 'Assigning the hardware
ID to the LED' and 'Assigning the hardware ID to the standard key'
It is not possible to configure a toggle function for favorites.
When you configure a standard key with the toggle function, you must change the
inscription of the standard key and the LED on the Person Machine Interface if
necessary. You will find editable inscription strips for the Person Machine Interface in
document A6V10333421. See chapter 'Applicable documents'.
See also
Assigning the hardware ID to the LED [ 185]
Assigning the hardware ID to the standard key [ 192]
199
A6V10333423_a_en_US
01/18/2012
12

Toggle function
12.8.1
Configuring the standard key for the toggle function

Configuring a command
Assigning a standard key to a command and an element

2. Open 'Panel' > 'PMI' > 'Standard keys' in the tree view.
3. Highlight a 'Standard key' element.
5. In the left-hand side of the window, select a command, e.g. 'Detector test'.
6. In the right-hand side of the window, select an element, e.g. a 'Zone', from the
'Detection tree'.
'Standard key' is assigned to the command and the element.
In the tree view, the command is displayed under 'Standard key'.
200
A6V10333423_a_en_US
01/18/2012

Toggle function
12
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. Select the reverse command, e.g. 'Detector test END', in the 'Reverse command'
field.
The reverse command is configured.
If you assign a command that requires specification in more detail, you must also set
the 'Reverse command parameter' property in the detail editor. If you have assigned
e.g. the 'Set ASD / Sensitivity level' command, you have to set the 'ASD / Sensitivity
level' you want.
Assigning a standard key to an LED
Assigning a standard key to an LED
201
A6V10333423_a_en_US
01/18/2012
12

Toggle function
1. Highlight the configured standard key in the tree view.

3. In the left-hand side of the window, select 'Related LED'.
The 'Operation tree' is displayed in the right-hand side of the window.
4. Select the right LED for the standard key.
The standard key is assigned to the LED.
See also
Assigning standard keys and favorites [ 193]
12.8.2
Configuring the LED for the toggle function

3. Highlight the right LED for the standard key.
5. In the left-hand side of the window, select an event category, e.g. 'Detector test
mode'.
6. In the right-hand side of the window, select the same element you assigned to the
standard key from the 'Detection tree'.
202
A6V10333423_a_en_US
01/18/2012

Visibility
12
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 the chapter 'Assigning an event'.
9. Change the inscription of the LED and standard key on the Person Machine
Interface if necessary.
See also
Assigning an event [ 187]
12.9
Visibility
Visibility defines which parts of a 'Site' are visible and/or can be operated on a 'Panel'.
You can configure visibility as follows:
'Site': Visibility across the entire 'Site'
'Site without areas': Visibility for all events from the 'Hardware tree' of the 'Site'
'Panel': Visibility for a 'Panel' within the 'Site', with all 'Areas' in this 'Panel', incl.
'Hardware tree'
'Panel without areas': Visibility for all events from the 'Hardware tree' of the 'Panel'
'Area': Visibility for an 'Area' within a 'Panel'
You can also 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 if a supervised 'Panel' fails.
Expanded visibility: This visibility can be activated manually on the Person Machine
Interface.

You will find further information about the visibility in document A6V10333380. See
chapter 'Applicable documents'.
203
A6V10333423_a_en_US
01/18/2012
12

Visibility
12.9.1
Properties of visibility
In the detail editor of the visibility, you can set the following in the 'Overview' tab:
Properties in the detail editor of visibility
'Max. access level'

In this field, you can define the maximum access level possible on the 'Panel' when
this visibility is active. If more than one visibility is active at the same time, e.g.
standard visibility and expanded visibility, the highest value set in the 'Max. access
level' field applies.
Visible event categories

In the detail editor of the element assigned to visibility, you can define the visible event
categories in the 'Overview' tab.
Properties in the detail editor of the element assigned to visibility
'ALL event categories visible': If this checkbox is checked, all event categories are
visible.
'Visible event categories': If only certain event categories are to be visible, e.g.
'ALARMS' and 'Supervisories', you can define the event categories here. The
setting is only possible when the 'ALL event categories visible' checkbox is
unchecked.
204
A6V10333423_a_en_US
01/18/2012

Visibility
12.9.2
12
Standard visibility
Standard visibility defines which events are visible in which elements during normal
operation of the 'Panel'. When a 'Panel' is created, the 'Standard visibility' element is
pre-configured with visibility for its own 'Panel'. You can configure visibility for more
elements.
Configuring standard visibility
Configuring standard visibility

3. Highlight the 'Standard visibility' element.
5. In the left-hand side of the window, select the visibility you want.
6. In the right-hand side of the window, select the corresponding element.
The element is assigned to 'Standard visibility'.
See also
Properties of visibility [ 204]
205
A6V10333423_a_en_US
01/18/2012
12

Visibility
12.9.3
Standby visibility
A 'Panel' with standby visibility supervises one or more 'Panels'. If a supervised 'Panel'
fails, standby visibility is active. You therefore have visibility for the failed 'Panel' via the
'Panel' with standby visibility.
Standby visibility must be closed by the Person Machine Interface of the 'Panel'. You
will find information about this in document A6V10333380. See chapter 'Applicable
documents'.
Creating standby visibility
Creating standby visibility

2. Open the 'Panel' in the tree view and highlight the 'PMI' element.
4. Select 'Standby visibility for Operating terminal' in the 'Type:' field.
5. Click on 'Add'.
The 'Standby visibility for Operating terminal' element is created.
You can also create standby visibility with the 'Assign' function.
'Standby visibility for Operating terminal': Configuring

In the configuration, you have to define which 'Panel' is supervised and what visibility
the supervised 'Panel' has.
The 'Standby visibility for Operating terminal' element is created.
3. Highlight the 'Standby visibility for Operating terminal' element.
5. In the left-hand side of the window, select the visibility of the supervised 'Panel'
from the 'Visibility' list.
206
A6V10333423_a_en_US
01/18/2012

Visibility
12

The element is assigned to standby visibility.
8. In the left-hand side of the window, select the 'Visibility activation upon failure of
Operating terminal..' entry from the 'PMI supervision for standby visibility' list.
9. In the right-hand side of the tree, select the 'Panel' to be supervised.
The 'Panel' is assigned to 'Standby visibility for Operating terminal'.
See also
12.9.4
Expanded visibility
If required, expanded visibility can provide more visibility compared with standard
visibility. Expanded visibility is used such that the commissioning or maintenance
personnel can temporarily access other parts of the system. If e.g. a 'Panel' only has
visibility for an 'Area' in standard visibility, expanded visibility can be configured such
that the entire 'Panel' is visible on activation.
Expanded visibility can be configured such that it can only be activated when a
supervised 'Panel' fails.
Expanded visibility must be activated and deactivated on the Person Machine Interface
with a command.
Creating expanded visibility
Creating expanded visibility

2. Open the 'Panel' in the tree view and highlight the 'PMI' element.
4. Select 'Expanded visibility' in the 'Type:' field.
5. Click on 'Add'.
The 'Expanded visibility' element is created.
207
A6V10333423_a_en_US
01/18/2012
12

Visibility
You can also create expanded visibility with the 'Assign' function.
Configuring expanded visibility
Configuring expanded visibility

3. Highlight the 'Expanded visibility' element.
5. In the left-hand side of the window, select the expanded visibility from the 'Visibility'
list.
The element is assigned to 'Expanded visibility'.
Configuring expanded visibility with supervision

If you want to configure expanded visibility such that it can only be activated when a
supervised 'Panel' fails, you also have to assign the 'Panel' to be supervised.
Assigning expanded visibility and supervised 'panel'
Expanded visibility is created and configured in accordance with the steps listed
above.
1. Highlight the 'Expanded visibility' element in the tree view.
208
A6V10333423_a_en_US
01/18/2012

LED module
12
3. In the left-hand side of the window, select the 'Visibility activation by command
upon failure of Operating terminal..' entry from the 'PMI supervision for expanded
visibility' list.
4. In the right-hand side of the tree, select the 'Panel' to be supervised.
The 'Panel' is assigned to 'Expanded visibility'.
See also
12.10
LED module
Two possible applications exist for the LED module:
24 pre-configured LED zones with 2 LEDs each
48 individually configurable LEDs
24 pre-configured LED zones

Each LED zone can be assigned to an element from the 'Detection tree' or 'Control
tree', e.g. to a 'Zone' or a 'Control'.
The LEDs are pre-configured as follows:
LED
Condition
Meaning
Topmost LED in an
LED zone
Color: Red
Flashing
At least one unacknowledged 'ALARM' event is present in the assigned element.
Steady on
All 'ALARM' events in the assigned element are acknowledged.
Off
No 'ALARM' event is present in the assigned element.
Bottommost LED in an Flashing

LED zone
Color: Yellow
Steady on
Off
At least one unacknowledged 'Trouble', 'Supervisory' or 'Bypassed' event is present

in the assigned element.
All 'Trouble', 'Supervisory' and 'Bypassed' events in the assigned element are
acknowledged.
No 'Trouble', 'Supervisory' or 'Bypassed' events are present in the assigned
element.
48 individually configurable LEDs

Each LED can be configured in any fashion. You can assign up to twelve causes per
LED. You can assign as a cause one event in an element within the 'Site'. You can set
the LED properties for each cause, e.g. 'LED mode' and 'Color'.
You will find more information about the two possible applications in the following
chapters.
See also
LED module FTO2008 [ 112]
209
A6V10333423_a_en_US
01/18/2012
12

LED module
12.10.1
LED module with 24 pre-configured LED zones


4. Select 'LED module, 24 LED groups' in the 'Type:' field.
5. Click on 'Add'.
The 'LED module, 24 LED groups' element is created.
Assigning an LED module

You must assign the 'LED module, 24 LED groups' element in the 'Operation tree' to
an 'LED module (FTO2008)' element in the 'Hardware tree'. The 'LED module
(FTO2008)' element must be in the same 'Panel' as the 'LED module, 24 LED groups'
element.
An 'LED module (FTO2008)' element is present in the 'Hardware tree' of the

'Panel'.
3. Highlight the 'LED module, 24 LED groups' element.
210
A6V10333423_a_en_US
01/18/2012

LED module
12

5. Open the 'LED module (FTO2008)' element you want and highlight the 'LEDs'
element.
The 'LED module, 24 LED groups' element is assigned to the 'LED module
(FTO2008)' element.
Assigning the visibility of an LED zone

You can configure the visibility on an element in the 'Detection tree' or 'Control tree' for
each LED zone. One 'Visibility' element exists per LED zone.
Assigning the visibility of an LED zone
To assign the visibility of an LED zone, proceed as follows:

2. Open 'Panel' > 'LED module, 24 LED groups' in the tree view.
3. Highlight a 'Visibility' element.
The visibility of the LED zone is assigned.
7. Label the LEDs on the LED module.
211
A6V10333423_a_en_US
01/18/2012
12

LED module
See also
12.10.2
LED module with 48 individually configurable LEDs


4. Select 'LED module, 48 LEDs' in the 'Type:' field.
5. Click on 'Add'.
The 'LED module, 48 LEDs' element is created.
You must assign the 'LED module, 48 LEDs' element in the 'Operation tree' to an 'LED
module (FTO2008)' element in the 'Hardware tree'. The 'LED module (FTO2008)'
element must be in the same 'Panel' as the 'LED module, 48 LEDs' element.
An 'LED module (FTO2008)' element is present in the 'Hardware tree' of the
'Panel'.
3. Highlight the 'LED module, 48 LEDs' element.
212
A6V10333423_a_en_US
01/18/2012

LED module
12

5. Open the 'LED module (FTO2008)' element you want and highlight the 'LEDs'
element.
The 'LED module, 48 LEDs' element is assigned to the 'LED module (FTO2008)'
element.
You can assign every LED to one or more events within the 'Site'. You can assign up
to twelve causes per LED. If you assign several causes, the LED properties must be
different, e.g. 'Priority', 'LED mode' or 'Color'.
To assign an LED to an event as a cause, proceed as follows:
2. Open 'Panel' > 'LED module, 48 LEDs' in the tree view.
5. In the left-hand side of the window, select an event category.
The LED is assigned to the cause.
8. Highlight the assigned cause element and set the properties you want in the detail
editor.
9. Label the LEDs on the LED module.
213
A6V10333423_a_en_US
01/18/2012
12

LED module

'Threshold': The value in this field specifies how many events of the corresponding
event category have to occur in the element or subtree for the cause to be
evaluated as active.
'Acknowledge status': This setting specifies which status the events of the
corresponding event category in the assigned element or subtree must have such
that the cause is evaluated as active.
Example:
The LED is assigned to the 'All Fire ALARMS' event category in a 'Section'.
'All acknowledged' is set for the 'Acknowledge status' property.
The cause is only evaluated as active when all 'Fire ALARM' events within the
'Section' are 'Acknowledged'.
'LED mode': Light mode of the LED when activated and not activated.
'Color': Color of the LED when activated. The following settings are possible:
Topmost LED in an LED zone: Red or green
Bottommost LED in an LED zone: Yellow
'ACTIVE if no communication to source': This setting specifies the status of the

cause that the assigned element has if there is no connection to the 'Panel'. The
status can be ACTIVE or INACTIVE.
See also
214
A6V10333423_a_en_US
01/18/2012

Printer
12.11
12
Printer
Creating an 'Printer (RPM)' element
Creating a printer

4. Select 'Printer (RPM)' in the 'Type:' field.
5. Click on 'Add'.
The 'Printer (RPM)' element is created.
Assigning the 'Printer (RPM)' element

You must assign the 'Printer (RPM)' element to the 'RPM' element of an RS485
module in the 'Hardware tree'. The RS485 module must be in the same 'Panel' as the
printer.
Assigning the printer
An RS485 module is present with an unassigned 'RPM' element in the 'Hardware

tree' of the 'Panel'.
3. Highlight the 'Printer (RPM)' element.
5. Open an RS485 module and highlight the 'RPM' element.
The 'Printer (RPM)' element is assigned to the 'RPM' element.
215
A6V10333423_a_en_US
01/18/2012
12

Printer
Properties of the 'Printer (RPM)' element

In the detail editor of the 'Printer (RPM)' element, you can set the following properties
Properties in the detail editor of the printer
'Cancellation of printout': The printer can be set such that a print order, e.g. a report
print-out, is automatically cancelled when a new event occurs. In this way the new
event can be printed immediately. The 'Cancellation of printout' setting specifies
which type of event cancels a print order.
'Printer supervised': This setting specifies whether the connection to the printer is
supervised.
'Color printing': This setting specifies whether the printer prints in color.
'Column width': This setting specifies the column width of the print-out.
'Printer port': This setting specifies to which interface the printer is connected. If
you select a serial interface, you can select more interface properties in the bottom
part of the detail editor. If you select a parallel interface, the properties in the
bottom part of the detail editor are deactivated.
Properties in the detail editor of the printer
'Print 'Extended message view'': This setting specifies which view of the event
messages is printed:
'Extended message view': 4 lines per message
'Standard message view': 2 lines per message
216
A6V10333423_a_en_US
01/18/2012

Printer
12
Assigning the visibility of the printer

You must configure the visibility of the printer for elements of the 'Site' or for the entire
'Site'. The events in the assigned elements are visible to the printer and can be printed.
Assigning the visibility of the printer

2. Open 'Panel' > 'Printer (RPM)' in the tree view.
3. Highlight the 'Visibility' element.
The visibility of the printer is assigned.

visible.
unchecked.
See also
RS485 class A module (isolated) [ 108]
217
A6V10333423_a_en_US
01/18/2012
12

Remote terminal and remote display
12.12
12.12.1

Remote terminal FT2015
With the 'Remote terminal configuration' element, you can configure the remote
terminal FT2015. You will find more information about the individual configuration steps
on the specified pages.
Configuration steps
1. Create the 'Remote terminal configuration' element. Link [ 218]
2. Assign the 'Remote terminal configuration' element to the 'FT2015' element of an
RS485 module in the 'Hardware tree'. Link [ 218]
3. Set the properties of the 'Remote terminal configuration' element. Link [ 221]
4. Assign the visibility of the remote terminal. Link [ 221]
5. Configure the LEDs. Link [ 223]
6. Configure the keys. Link [ 225]
12.12.2
Remote display FT2014

With the 'Remote display configuration' element, you can configure the remote display
FT2014. You will find more information about the individual configuration steps on the
specified pages.
Configuration steps
1. Create the 'Remote display configuration' element. Link [ 220]
2. Assign the 'Remote display configuration' element to the 'FT2015' element of an
RS485 module in the 'Hardware tree'. Link [ 220]
3. Set the properties of the 'Remote display configuration' element. Link [ 221]
4. Assign the visibility of the remote display. Link [ 221]
5. Configure the LEDs. Link [ 223]
218
A6V10333423_a_en_US
01/18/2012

12.12.3
12
Creating and assigning the remote terminal

Creating an 'Remote terminal configuration' element
Creating the remote terminal

4. Select 'Remote terminal configuration' in the 'Type:' field.
5. Click on 'Add'.
The 'Remote terminal configuration' element is created.
Assigning the 'Remote terminal configuration' element

You must assign the 'Remote terminal configuration' element to the 'FT2015' element
of an RS485 module in the 'Hardware tree'. The RS485 module must be in the same
'Panel' as the 'Remote terminal configuration' element.
Assigning the remote terminal
An RS485 module is present with an unassigned 'FT2015' element in the

'Hardware tree' of the 'Panel'.
3. Highlight the 'Remote terminal configuration' element.
219
A6V10333423_a_en_US
01/18/2012
12

5. Open an RS485 module and highlight the 'FT2015' element.

The 'Remote terminal configuration' element is assigned to the 'FT2015' element.
See also
12.12.4
Creating and assigning the remote display

Creating an 'Remote display configuration' element
Creating the remote display

4. Select 'Remote display configuration' in the 'Type:' field.
5. Click on 'Add'.
The 'Remote display configuration' element is created.
Assigning the 'Remote display configuration' element

You must assign the 'Remote display configuration' element to the 'FT2014' element of
an RS485 module in the 'Hardware tree'. The RS485 module must be in the same
'Panel' as the 'Remote display configuration' element.
Assigning the remote display
An RS485 module is present with an unassigned 'FT2014' element in the

'Hardware tree' of the 'Panel'.
220
A6V10333423_a_en_US
01/18/2012

12
3. Highlight the 'Remote display configuration' element.

5. Open an RS485 module and highlight the 'FT2014' element.
The 'Remote display configuration' element is assigned to the 'FT2014' element.
See also
12.12.5
Setting properties
In the detail editor of the 'Remote terminal configuration' and 'Remote display
configuration' elements, you can set the following properties in the 'Details' tab:
Properties in the detail editor of the remote terminal or the remote display
'User PIN': You can enter a PIN in this field. This PIN is used to call up information and
settings on the remote terminal or the remote display, e.g. hardware and firmware
versions of the device. You can define a number between 0 and 9999 as the PIN.
12.12.6
Configuring the visibility

You must configure the visibility of the remote terminal or the remote display for
elements of the 'Site' or for the entire 'Site'.
Assigning the visibility of the remote terminal or the remote display
221
A6V10333423_a_en_US
01/18/2012
12


2. In the tree view, open the 'Panel' > 'Remote terminal configuration' or 'Remote
display configuration'.
3. Highlight the 'Standard visibility' element.
The visibility of the remote terminal or the remote display is assigned.

visible.
unchecked.
222
A6V10333423_a_en_US
01/18/2012

12.12.7
12
Configuring LEDs
The remote terminal FT2015 and the remote display FT2014 each have three
configurable LEDs. Each LED can be assigned to up to twelve causes. You can set the
LED properties for each cause, e.g. 'LED mode' and 'Color'.
You can assign the following types of cause:
Pre-defined cause: Select an event from a pre-defined list. If the event occurs
within the visibility of the 'Panel', the LED is activated. You will find information
about this in the chapter 'Assigning a pre-defined cause [ 185]'.
Event in a certain element within the 'Site': Select an event and the element in
which the event must occur for the LED to be activated. You will find information
about this in the chapter 'Assigning an event [ 187]'.
You will find the assignment of the hardware ID to the relevant LED on the Person
Machine Interface in the chapter 'Assigning the hardware ID to the LED [ 223]'.
12.12.8
Assigning the hardware ID to the LED

The figures below show how to assign the hardware ID to the corresponding LED on
the Person Machine Interface. The numbers correspond to the hardware ID of the
LED.
Remote terminal FT2015
9
10
11
Assigning the hardware ID to the LED on the Person Machine Interface of the remote terminal
223
A6V10333423_a_en_US
01/18/2012
12

Remote display FT2014
9
10
11
Assigning the hardware ID to the LED on the Person Machine Interface of the remote display
You will find the hardware ID in the detail editor of the LED in the 'HW ID LED' field.
Detail editor of an LED with details of the hardware ID
224
A6V10333423_a_en_US
01/18/2012

12.12.9
12
Configuring keys
The remote terminal FT2015 has three configurable keys. You will find information
about configuring keys in the following chapters:
Standard keys [ 188]
Configuring standard keys and favorites [ 192]
Assigning the hardware ID to the key

The figure below shows how to assign the hardware ID to the corresponding key on
the remote terminal's Person Machine Interface. The numbers correspond to the
hardware ID of the key.
4
5
6
Assigning the hardware ID to the key on the Person Machine Interface of the remote terminal
You will find the hardware ID in the detail editor of the key in the 'HW ID KEY' field.
Detail editor of a key with details of the hardware ID
225
A6V10333423_a_en_US
01/18/2012
13
'Network' task card

Global network configuration
13 'Network' task card

The network settings for the fire detection system are configured in the 'Network' task
card.
All permissible networking types and the required network settings are described in
detail in document A6V10333396.
You will find pre-conditions for configuration and the required work steps in document
The following chapter describes the corresponding configuration in CerberusEngineering-Tool.
NOTICE
Instructions'.
13.1
13.1.1

Creating a stand-alone 'panel'
When creating a stand-alone 'Panel', a network reference for the 'Panel' is created in
the following position:
'Network' task card: 'Global system configuration' > 'FS920 network configuration' >
'Ethernet sub-net' > 'Connections'
A network reference is created such that the 'Site' can be extended.
See also
Creating a 'Panel' [ 58]
226
A6V10333423_a_en_US
01/18/2012
'Network' task card

13.1.2
13
Creating networked 'panels'

Networked 'Panels' have to be assigned to the SAFEDLINK sub-net when they are
created. Ethernet 'Panels' are not permitted for MP-UL 1.0.
In the 'Network' task card, references for 'Panels' are automatically created under the
'Global system configuration' > 'FS920 network configuration' > 'Ethernet sub-net'
elements.
SAFEDLINK 'Panels'
The 'SAFEDLINK sub-net' element is automatically created under 'Ethernet sub-net'.
The 'Fx92x/SAFEDLINK references for all SAFEDLINK 'Panels' can be found under
the 'Connections' element.
If the SAFEDLINK 'Panels' are split into several sub-nets, more 'SAFEDLINK sub-net'
elements can be created using the 'New element' function.
The 'Fx92x/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 a stand-alone 'Panel' is created and 'Panels' are then added to the 'Site', the standalone 'Panel' automatically adopts the network settings of the first 'Panel' added.
See also
Creating a 'Panel' [ 58]
13.1.3
Configuring a 'Panel' as a router panel

A SAFEDLINK panel is configured as a router panel. The router panel connects the
'SAFEDLINK sub-net' with the 'Ethernet sub-net'.
The router panel is created by assigning the 'Functions' element to the
'Fx92x/SAFEDLINK' reference.
The router panel prevents the private addresses in the 'SAFEDLINK sub-net' from
becoming known in an external network. The Ethernet participants must therefore
recognize the router panel as being the gateway of the route to the 'SAFEDLINK subnet'.
Defining the router panel
227
A6V10333423_a_en_US
01/18/2012
13
'Network' task card

Proceed as follows to define the 'Router' or 'Standby router':

1. Select the 'Network' task card.
2. Open 'Global system configuration' > 'FS920 network configuration' > 'Ethernet
sub-net' > 'SAFEDLINK sub-net' in the tree view.
3. Highlight 'Functions'.
5. Select 'Router' or 'Standby router' from the list and the reference for the 'Panel' you
want from the tree.
The 'Panel' is configured as a router panel or standby router panel.
13.1.4
Configuring a 'Panel' as GAP

The GAP panel is created by assigning the 'Functions' element to the
'Fx92x/SAFEDLINK' reference.
Proceed as follows to configure the 'Panel' as 'GAP' or 'Secondary GAP':

The 'Panel' is configured as a router panel or Ethernet panel.
2. Open the 'Global system configuration' > 'FS920 network configuration' > 'Ethernet
sub-net' elements in the tree view.
3. Highlight 'Functions'.
5. The 'Assign dialog' window opens.
6. Select 'GAP' or 'Secondary GAP' from the list and the reference for the 'Panel' you
want from the tree.
The 'Panel' is defined as 'GAP' or 'Secondary GAP'.
228
A6V10333423_a_en_US
01/18/2012
'Network' task card

13.1.5
13
Configuring GAP with 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 Ethernet.
The 'Panel' is configured as GAP.

sub-net' > 'Functions' elements in the tree view.
3. Highlight the GAP 'Panel'.
4. Check the 'DHCP server enabled' checkbox in the 'Overview' tab of the detail
editor.
The 'Panel' is configured with DHCP server.
13.1.6
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'
2. Open the 'Global system configuration' > 'FS920 network configuration' elements in
the tree view.
3. Highlight 'Ethernet sub-net'.
4. Enter the network mask (four groups of digits, separated by dots) in the 'Netmask'
field of the detail editor.
5. Open 'Ethernet sub-net' > 'Connections' in the tree view.
229
A6V10333423_a_en_US
01/18/2012
13
'Network' task card

6. Highlight all 'Fx92x/Ethernet' one after the other.

7. Enter the IP address in the 'Overview' tab of the detail editor.
'SAFEDLINK sub-net'
3. Highlight 'SAFEDLINK sub-net'.
4. Enter the network mask (four groups of digits, separated by dots) in the 'Netmask'
field of the detail editor.
5. Open 'SAFEDLINK sub-net' > 'Connections' in the tree view.

6. Highlight all 'Fx92x/SAFEDLINK one after the other.
7. Enter the IP address in the 'Overview' tab of the detail editor.
See also
Setting network speed for SAFEDLINK [ 232]
13.1.7
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
'Panels' in the extended network via router and GAP, routes must be entered in the
GAP and in the Ethernet sub-net.
230
A6V10333423_a_en_US
01/18/2012
'Network' task card

13
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 Cerberus-Engineering-Tool and/or the

management stations.
'Gateway' is the FS920 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 Cerberus-Engineering-Tool and/or the

management stations.
'Gateway' is the Ethernet address of the GAP.
Additional conditions for access
GAP must be connected to 'C-WEB/LAN'.
'Security module (firewall) FN2009-A1' must be configured.
Entering route in the GAP

Route via 'Security module (firewall) FN2009-A1':
'Destination address' e.g.: 10.169.29.0
'Netmask': 255.255.255.0
'Gateway': 192.168.201.2
Enter the routes in the GAP as follows:

sub-net' > 'Functions' > 'GAP' in the structure tree.
3. Highlight 'Routes'.
4. Enter the network data.
Route in the GAP
231
A6V10333423_a_en_US
01/18/2012
13
'Network' task card

Entering route in the Ethernet sub-net

Route via GAP (PC, management station)
'Destination address' e.g.: 10.169.29.0
'Netmask': 255.255.255.0
'Gateway': 192.168.201.1
Enter the routes in the Ethernet sub-net as follows:

sub-net' in the structure tree.
3. Highlight 'Routes'.
4. Enter the network data.
Route in the Ethernet sub-net
13.1.8
Setting network speed for SAFEDLINK

The network speed is set in 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.
Detail editor with network speed setting
To set the network speed, proceed as follows:

3. Highlight 'SAFEDLINK sub-net'.
4. Select the 'Low' setting in the 'Details' tab in the 'Network speed' field of the detail
editor.
The network speed is set for low cable qualities.
232
A6V10333423_a_en_US
01/18/2012
'Network' task card

Establishing connection from PC to FS920 network
13.2
13
Establishing connection from PC to FS920 network

When the Cerberus-Engineering-Tool 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
Persistent routes
A connection from the PC to the FS920 network can be established with the following
three variants:
Local connection
The PC automatically receives an IP address
Connection to GAP
The PC automatically receives an IP address
Connection to IP address
The PC is connected to any place in the Ethernet. The IP address must be

specified.
The connection can be established using the following menu items:
For Cerberus-Engineering-Tool
'Commissioning' > 'Transfer PC -> site'
'Commissioning' > 'Transfer site -> PC'
'Commissioning' > 'Transfer site event memory -> PC'
'Commissioning' > 'Transfer site log files -> PC'
For Cerberus-Remote
'Cerberus-Remote' > 'Connect'
The 'Connect' window is opened when a command is performed.
233
A6V10333423_a_en_US
01/18/2012
13
'Network' task card

Checklist for network configuration
13.3

The checklists below list settings that must be entered and/or checked for the network
configuration.
13.3.1
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'
Default
'Router IP address'
192.168.x.x
'Router'
234
A6V10333423_a_en_US
01/18/2012
'Network' task card

13.3.2
13
Checklist in the event of problems with integration
Problem
Possible causes and measures
Communication trouble between CerberusEngineering-Tool and 'Panel'
Check the following points:

Access to the 'Panel' is registered with password
IP addresses are entered correctly in the 'Panel' and on the PC
Routes are entered correctly on the PC
Transactions are aborted (network analysis,

e.g. Wireshark: 'Abort' 'timeout' message)
'APDU timeout' on 'Panels' and management station must be at least 6 s
Checklist in the event of problems with integration

See also
License key [ 28]
235
A6V10333423_a_en_US
01/18/2012
Index
Index
Configurable output, 100
Configuration
Load to panel, 85, 86
Access level, 183, 204

Address, 65
Agent releasing control, 168
Alarm verification concept, 117
Alarming control group, 132
Area, 117
ASD
Application-specific detection, 99
Assign
Detection tree, 130
Element, 67
Hardware tree, 130
Loading to PC, 88
Configuring
Zone, 127
Connecting PC to C-WEB, 233
Connection from PC to C-WEB, 233
Control
Task card, 131
Control tree, 131
Controls, 131
Conventional detector circuit, 98
Copy
Element, 64
Audible base
Features, 100
Automatic alarm zone, 122
AVC, 117
Features, 63
Country settings, 182
Create
Element, 60
Panel, 58, 226
Site, 54
Back-up, 36, 36
Create and assign, 68
Banner, 76
CSV
BDV
Export, 74
File name, 26
Import, 75
Import, 28
Protocol, 76
Version, 26
CSV import log, 76
Bell follower, 105
Customer text, 93, 128
Buzzer, 180
Cut
Element, 64
C
Cerberus-Remote
Favorite list, 40
DACT control, 142
Settings, 40
Deleting
Checklist
Network configuration, 234
City tie, 107, 136
Clock, 181
Collapse
Element in the structure tree, 44
Element, 62
Detection
Task card, 115
Detection tree, 116
Assign, 130
Detector sensor, 99
236
A6V10333423_a_en_US
01/18/2012
Index
Detector settings, 99
Device
Create, 96
DHCP server, 229
Dialer module (DACT), 113
Display logo, 76
Download, 85, 86
F
Favorite
PMI, 189
Favorite list
Cerberus-Remote, 40
FDCIO442, 102
Dynamic loading, 52
Features
File name
Copy, 63
BDV, 26
Editing
Engineering tool kit, 26
Element, 62
System properties, 57
Element
Assign, 67
Copy, 64
Create, 60
Cut, 64
Firmware, 27
Finding, 71
Finding and replacing, 73
Fire control, 149
Fire control group, 149
Firmware
File name, 27
Deleting, 62
Import, 28
Editing, 62
Update panel, 91
Move, 65
Paste, 64
Re-address, 65
Replace, 62
Element in the structure tree
Collapse, 44
Expand, 44
Engineering tool kit
File name, 26
Install, 16, 25
Version, 26
Error display, 47
Evac control group, 161
Exit
Software, 19
Expand
Element in the structure tree, 44
Expanded visibility, 207
Export
CSV, 74
Version, 27
FN2001 network module (SAFEDLINK), 114
FN2009-A1, 230
FT2014 remote display, 218
FT2015 remote terminal, 218
FTO2008 LED module, 112
G
GAP, 228, 229, 230
Gas zone, 127
Global behavior, 180
H
Hardware
Task card, 94
Hardware tree, 96
Assign, 130
HCP, 98
Help, 32
History, 52
237

A6V10333423_a_en_US
01/18/2012
Index
Load data to PC
Event memory, 89
IC, 94
Log file, 90
IEC
Intelligent environmental compensation, 99
ILED control, 154
Import
CSV, 75
Initialize
Panel, 85, 86
Input
Features, 97
Installation
Engineering tool kit, 16, 25
Internal LED, 97
Internet settings, 37
Intervention concept (IC), 94
Site, 88
Load data to the panel
Site, 86
Load event memory to PC, 89
Log file, 28, 28, 90
Logo, 76
LRC, 20
LRC web server, 38
M
Manual alarm zone, 123
Manual allocation of addresses in sub-nets, 229
Master clock, 181
Menu bar, 30
Mouse wheel, 36, 92
K
Key switch, 183
Move
Element, 65
Multi-detector dependency, 123
Multiselection, 44
Leased line, 107, 139

LED
Internal, 97
PMI, 184
LED module, 209
Individually configurable LEDs, 209, 212
Pre-configured LED zones, 209, 210
LED module (FTO2008), 112
License, 25
Loading/renewing, 20
Return, 24
License check, 19
License information, 25
License key, 28
Licensing, 20
Lifecycle Responsibility Concept (LRC), 20
Load
From panel to PC, 88
N
NAC
Onboard, 105
Optional, 105
NAC circuit, 105, 106
NAC control, 145
NAC module, 105
Navigate
With hyperlinks, 45
With shortcuts, 46
With task cards, 45
Network configuration
Checklist, 234
Problems, 235
Network module (SAFEDLINK), 114
Network speed, SAFEDLINK, 232
From PC to panel, 85, 86

238
A6V10333423_a_en_US
01/18/2012
Index
O
Onboard NAC, 105
Operation
Task card, 180
Optional NAC, 105
Output
Configurable, 100
Features, 98
Quicktext, 36, 63
R
Re-address
Element, 65
Releasing circuit, 111
Releasing control group, 168
Output mode, 103
Releasing module, 110
Remote terminal FT2015, 218
Panel
Create, 58, 226
Initialize, 85, 86
Load data, 85
Router panel, 227
Stand-alone, 226
Paste
Element, 64
PC
Connect to panel, 83
Disconnecting from panel, 83
Periphery board, 104
PMI, 182, 182
Favorite, 189
LED, 184
Standard key, 188
Power supply, 110
Pre-settings, 35
Cerberus-Remote, 40
Firmware files, 37
General program settings, 39
Internet settings, 37
LRC web server, 38
Quicktext settings, 36
'Site' settings, 41
Printer, 215
Problem identification, 47
Program window, 29
Proposed texts, 36
Remote display FT2014, 218

Replace, 73
Element, 62
Reports, 77
Router panel, 227
RS485 class A module (isolated), 108
RT control, 133
S
SAFEDLINK interface, 114
Safety module (firewall), 230
Saving list of parts, 25
Scroll bar, 44
Scroll wheel, 36, 92
Short-circuit supervision, 103
Shortcuts, 46
Single-detector dependency, 123
Site
Create, 54
Load data to PC, 88
Load data to the panel, 86
Software
Exit, 19
Start, 19
Sprinkler releasing control, 173
Stand-alone panel, 226
Standard key
PMI, 188
Standard visibility, 205
Standby visibility, 206
239

A6V10333423_a_en_US
01/18/2012
Index
Start
Software, 19
Status bar, 46
Status zone, 126
Sub-system zone, 124
Supervisory
Short circuit, 103
Supervisory zone, 123
System behavior, 180
System properties
Editing, 57
System requirements, 16
System time, 181
W
Walk test, 181
Waterflow zone, 124
Window separating lines, 44
Z
Zone, 120
Automatic, 122
Configuring, 127
Gas, 127
Manual, 123
Status, 126
Sub-system, 124
Supervisory, 123
Task card, 42
Components, 43
Trouble, 126
Waterflow, 124
Control, 131
Detection, 115
Hardware, 94
Network, 226
Operation, 180
Time, 181
Toggle function, 199
Toolbar, 32
Tooltips, 32
Trouble zone, 126
U
Universal evac control, 161
Upload, 88
V
Version
BDV, 26
Engineering tool kit, 26
Firmware, 27
Visibility, 203, 221
Default, 205
Extended, 207
Standby, 206
240
A6V10333423_a_en_US
01/18/2012
Index
241
A6V10333423_a_en_US
01/18/2012
Issued by
8 Fernwood Road
Florham Park, NJ 07932
Tel. +1 973-593-2600
www.sbt.siemens.com/FIS
Document ID
A6V10333423_a_en_US
Edition
01/18/2012
2012 Siemens Industry, Inc.

Technical specifications and availability subject to change without notice.
FS920

A6V10333423 Configuration Siemens Cerberus

Uploaded by

Copyright:

Available Formats

A6V10333423 Configuration Siemens Cerberus

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

A6V10333423 Configuration Siemens Cerberus

Uploaded by

Copyright:

Available Formats

FS920

Fire detection system

Siemens Industry, Inc.

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

Applicable documents ........................................................................................10

Technical terms ..................................................................................................11

Safety instructions ..............................................................................................12

Safety regulations for the method of operation ..................................................13

Standards and directives complied with.............................................................15

System requirements .........................................................................................16

Installing the engineering tool set.......................................................................16

IP settings for several network cards .................................................................18

Starting the software ..........................................................................................19

Exiting the software ............................................................................................19

Software administration ..................................................................................20

Lifecycle Responsibility Concept (LRC) .............................................................20

Loading / renewing licenses ...............................................................20

Returning licenses ..............................................................................24

Viewing license information ................................................................25

Installing several different engineering tool kits..................................25

Saving a parts list for the 'Site'............................................................25

Engineering tool set: File name and version ......................................................26

BDV: File name and version ..............................................................................26

Firmware: File name and version.......................................................................27

BDV import .........................................................................................................28

Firmware import .................................................................................................28

License key ........................................................................................................28

Calling up log files ..............................................................................................28

Overview of the program window.......................................................................29

Menu bar ............................................................................................................30

Help and tooltips.................................................................................................32

Commissioning settings ......................................................................36

Quicktext and mouse wheel settings ..................................................36

Firmware files settings ........................................................................37

Settings for LRC web server ...............................................................38

General program settings ...................................................................39

Cerberus-Remote settings ..................................................................40

'Site' settings .......................................................................................41

Task cards ..........................................................................................................42

Task card components .......................................................................................43

Scroll bars and window separating lines ............................................................44

Expanding and collapsing the elements in the structure tree ............................44

Navigating within the program window...............................................................45

Navigating with task cards ..................................................................45

Navigating with hyperlinks ..................................................................45

Navigating with shortcuts ....................................................................46

Status bar ...........................................................................................................46

Designation of problems and displaying errors ..................................................47

Dynamic loading .................................................................................................52

Program operation ...........................................................................................54

Creating a 'Site' ..................................................................................................54

Loading an existing 'Site' ....................................................................54

Creating 'Site' based on existing configuration ...................................55

Creating a new 'Site' ...........................................................................56

Editing the 'Site' properties .................................................................57

Creating a 'Panel' ...............................................................................................58

Creating an element ...........................................................................................60

Copying properties in the table...........................................................................63

Entering quicktext ...............................................................................................63