Table of contents About this document ................11 Applicable documents ................13 Download center ..................14 Technical terms and abbreviations .............14 Revision history ..................14 Safety ....................20 Safety instructions ..................20 Safety regulations for the method of operation ...........21 Standards and directives complied with............23 IT security instructions ................23 2.4.1 PIN guidelines................23...
Page 4
BDV import ....................43 Resources import ..................43 License key ....................43 Calling up log files of Engineering Tool ............43 GUI ....................44 Overview of the program window ............... 44 Menu bar ....................45 Toolbar ...................... 48 Help and tooltips ..................49 Template for customer data ...............
Page 5
6.16 Assignment with Data Matrix code .............83 6.17 Assigning elements several times ..............84 6.18 Assigning the effects of a control..............85 6.19 Deleting links .....................85 6.20 Finding and replacing.................86 6.21 'Switch to 'Search and replace'' button ............87 6.22 Exporting an XML ..................88 6.23 Exporting an SIB-X ..................90 6.24 Exporting and importing CSVs ..............91 6.24.1...
Page 6
Configuration –Overview ..............113 With pre-configuration ................114 Without pre-configuration ................. 115 Customer text ..................115 'Hardware' task card ................116 10.1 'Station' ....................116 10.1.1 Intervention concept (IC) ............117 10.1.2 Configuring permanent access for Cerberus-Remote ....119 10.2 Onboard I/Os ................... 119 10.3 C-NET detector line .................
Page 7
11.5 Configuring the 'Zone' ................162 11.5.1 Multi-detector dependency ............164 11.5.2 Multi-detector dependency with latching ........165 11.5.3 Two-zone dependency ..............166 11.5.4 Additional criteria for pre-stage and main stage ......167 11.6 Assign hardware tree to the detection tree ..........169 11.7 Collective detector line via input/output module FDCIO223 or zone module ........................170 11.8 Neural fire detector OOHC740 ..............171 11.8.1...
Page 8
'Operation' task card ................255 13.1 Global system configuration ..............255 13.1.1 System behavior ............... 255 13.1.2 Global PIN configuration ............258 13.1.3 Country settings ................ 259 13.1.4 Master clock ................259 13.2 Person Machine Interface (PMI) ............... 259 13.2.1 Basic settings ................
Page 9
Configuring remote access via cRSP ........320 14.2.10 Configuring cloud gateway FG2004...........322 14.2.11 Configuring redundancy management ........324 14.3 Establishing connection from PC to FS720 network .........327 14.4 Setting up a Maximum Transmission Unit (MTU) ........328 14.5 Monitoring Ethernet switch (MM) and safety module (firewall) ....329 14.6 Connecting management stations via BACnet/Ethernet......330...
Page 10
Extinguishing ..................345 16.1 Basic configuration steps ................. 345 16.2 Configuring the extinguishing card ............346 16.2.1 Configuring inputs and outputs ..........347 16.3 Configuring automatic extinguishing activation ......... 349 16.4 Configuring an extinguishing control group ..........353 16.5 Configuring flooding zone control ............. 354 16.5.1 Causes functions ..............
About this document Applicable documents 1 About this document Goal and purpose This document describes the configuration of an FS720 fire detection system using the engineering tool set FX7230. Scope The information in documents A6V10211076 and A6V10210416 is a prerequisite for configuring the fire detection system with the engineering tool set FX7230.
Page 12
About this document Applicable documents Conventions for text marking Markups Special markups are shown in this document as follows: ⊳ Requirement for a behavior instruction Behavior instruction with at least two operation sequences – Version, option, or detailed information for a behavior instruction ⇨...
About this document Applicable documents 1.1 Applicable documents Document ID Title A6V10210355 FS720 Fire Detection System, System Description A6V10210362 FS720 Fire Detection System, Planning A6V10210368 FS720 Fire Detection System, Product Data A6V10210416 FS720 Fire Detection System, Commissioning, Maintenance, Troubleshooting A6V10211076...
You can download various types of documents, such as data sheets, installation instructions, and license texts via the following Internet address: https://siemens.com/bt/download Enter the document ID in the search field. You will also find information about search variants and links to mobile applications (apps) for various systems on the home page.
Page 15
About this document Revision history The table below shows this document's revision history: Version Edition date Brief description 2018-08-29 Edition for IP7 New: 'Target group 'IT security officer'' [➙ 11], 'IT security instructions [➙ 23]', 'PIN guidelines [➙ 23]', 'Password guidelines [➙ 23]', 'Reporting/logging and monitoring [➙...
Page 16
About this document Revision history Version Edition date Brief description 2015-12-15 Edition for IP6 New: Configuring the operation mode for Cerberus-Remote Ethernet switch (modular) FN2012 Configuring redundancy management (with subchapters) Assigning elements several times Editing the CSV file 'Peripherals test report' Time control (with subchapters) Creating a station with FBP [AU] Inserting text in columns...
Page 17
About this document Revision history Version Edition date Brief description 2013-11-14 Edition for IP5 Change to date format according to ISO 8601 New: Template for customer-specific 'Site' data PIN configuration Converting a 'Station' 'Import information report' AlgoRex/SIGMASYS data migration Setting up a Maximum Transmission Unit (MTU) Resources import Handover Configuring visibility for Cerberus Mobile...
Page 18
About this document Revision history Version Edition date Brief description 05.2012 Edition for IP4 New: I/O card (remote transmission) FCI2007-A1 I/O card (horn/monitored) FCI2009-A1 Gas zone Multi-detector dependency with latching CSV export/import Cerberus-Remote settings Calling up log files Input/output module FDCIO223 Input/output module FDCIO223 with monitored input/output Option to configure 252 devices per detector line New quicktext settings...
Page 19
About this document Revision history Version Edition date Brief description 06.2010 Edition for MP3.0 XS: Revision history redefined and standardized, dynamic loading, merging two 'Sites', network configuration, management stations via BACnet/Ethernet, route entries for installation, new FDCAI221, general chapter structure 08.2009 Chapter 8.2.2 restructured Chapters 8.4.3.1 and 8.5.6.4 recreated...
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 ●...
2.2 Safety regulations for the method of operation National standards, regulations and legislation Siemens products are developed and produced in compliance with the relevant European and international safety standards. Should additional national or local safety standards or legislation concerning the planning, mounting, installation,...
Page 22
Modifications to the system design and the products Modifications to the system and to individual products may lead to faults, malfunctioning and safety risks. Written confirmation must be obtained from Siemens and the corresponding safety bodies for modifications or additions. 22 | 412 Building Technologies...
Personal injury or damage to property caused by poor maintenance or lack of maintenance 2.3 Standards and directives complied with A list of the standards and directives complied with is available from your Siemens contact. 2.4 IT security instructions 2.4.1 PIN guidelines You can log into the system and enable an 'Access level' with a Personal Identification Number (PIN).
2.4.3 Reporting/logging and monitoring Monitor the network and the system. 'FS720' offers the follow security-relevant logging functions: Logger Position Pre-configured 'Login/logout' person in the 'FS720' system via PMI with PIN syslog opt/log* Yes syslog opt/log* Yes 'Login/logout' person in the 'FS720' system via PMI with key...
Siemens’ portfolio undergoes continuous development to make it more secure. Siemens strongly recommends that updates are applied as soon as they are available and that the latest versions are used. Use of versions that are no longer supported, and failure to apply the latest updates may increase your exposure to cyber threats.
Installation System requirements 3 Installation 3.1 System requirements Hardware Component Minimum requirements Processor In line with the minimum requirements for the operating system used. Main memory You will find a list of the supported operating systems further down. Hard disk 1 GB of free memory Network connection Ethernet RJ45...
The existing installation paths are retained. You can also open the directory for log files as follows via the Start menu: Start > All Programs > Siemens > F-FX7230 > [Version] > Log files [Version] = Version of the software, e.g., EN_en_1-V1 See also 2 Engineering tool set: File name and version [➙...
IP settings for several network cards 3.3 IP settings for several network cards To connect to a ↑ 'Station' via the FS720 network or directly to the 'Station', you can use an additional network card on the PC, for example, a 'USB to Ethernet adapter'.
The instructions below apply to installation in Windows 7 and 8.1. 3.6.1 Installation and uninstallation with default parameter values The tables below display the default parameters. Installation parameter Default value Installation path C:\Program Files (x86)\Siemens\F- FX7230\XS_en_x-Vx.x Data path C:\ProgramData\Siemens\F-FX7230 English Engineering Tool interface language on...
Installation Installation via the input prompt Uninstallation and installation w The executable installation file for the engineering tool set is saved to your PC. 1. Windows 7: Open the Command Prompt: – Click on the Start button. – Enter 'Command Prompt' in the search field and click on Command Prompt.
Installation Installation via the input prompt Values for Engineering Tool interface language and BDV language Bulgarian (bg), Chinese (zh_CN), Croatian (hr), Czech (cs), Danish (da), English (en), English (en_CA), English (en_GB), English (en_IE), English (en_US), Estonian (et), Finnish (fi), Dutch; Flemish (nl), Flemish (nl_BE), French (fr_BE), French (fr_CA), French (fr_CH), French (fr_FR), German (de), German (de_AT), German (de_CH), German (de_DE), Greek (el), Hebrew (iw), Hungarian (hu), Italian (it_CH), Italian (it_IT), Lithuanian (lt), Norwegian (no), Polish (pl), Portuguese...
Page 32
REMOVE_ADD_DOCTOS=no REMOVE_FIRMWARE=no REMOVE_SITES=no REMOVE_TRACES=no REMOVE_QUICKTEXTS=no REMOVE_SITEINFO=no [Install parameters] INSTALL_DIR="C:\Program Files (x86)\Siemens\F-FX7230\XS_en_x-Vx.x" SHARED_DATA_DIR="C:\ProgramData\Siemens\F-FX7230" TOOL_LANGUAGE="English (en)" BDV_LANGUAGE="English (en)" START_TOOL=yes Table 3: Example structure of an initialization file with default values Proceed as follows to create an initialization file. 1. Open a text editor, e.g., the editor in Word.
Installation Installation via the input prompt 3.6.4.2 Calling up an initialization file w You have created an initialization file that includes all the necessary parameter commands. Proceed as for the default installation and enter the command '/FILE="answer file"' after the '/S' sequence of characters, where 'answer file' must contain the path and the name of the initialization file, e.g., '>F-F-FX7230-NL_nl_2- 7.0.0.R.exe /S /FILE="C:\Users\User1\answerfile.ini"'.
Software administration Engineering tool set: File name and version 4 Software administration 4.1 Engineering tool set: File name and version File name format: [Prefix]-[Country]_[Language]_[Sales channel]-[Meta data version].R.exe Example: F-FX7230-NL_nl_2-7.0.0.R.exe 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...
Software administration Firmware: File name and version 4.3 Firmware: File name and version File name format: [Prefix]-[Country]_[Language]_[Sales channel]-[Meta data version]_([Variant])_[Firmware version].zip Example: F-FXS7211-XE_xx_x-60.7.0_00.zip Designation Coding Prefix F-FXS7211 Country Double digit, in accordance with ISO 3166-1 ALPHA-2 XE: Several countries Language Double digit, in accordance with ISO 639-1:2002 xx: All languages Sales channel...
Software administration CDV: File name and version 4.4 CDV: File name and version File name format: [Prefix]-[Country]_[Language]_[Sales channel]-[Meta data version]_[CDV version]([Variant]).eCDV Example: F-FXS2021-XS_en_1-70.28.2_02.eCDV Designation Coding Prefix F-FXS2021 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...
If, during installation of the software, no other path has been entered, then the shared data directory is in the following path: C:\Documents and Settings\All Users\ Application Data\Siemens\F-FX7230\[Version] [Version] = Version of the software, e.g., EN_en_1-V1 The common data directory contains the following subfolders: ●...
Software administration Pre-settings 4.5.2 Cerberus Remote Figure 1: Settings for Cerberus Remote The following can be set in the 'Cerberus-Remote' view: ● 'Connect Cerberus-Remote automatically to the last connected station when opening Cerberus-Remote taskcard': If the checkbox is activated, then Cerberus-Remote will be connected automatically when you open the 'Cerberus-Remote' task card.
Software administration Pre-settings 4.5.3 Commissioning The following can be set in the 'Commissioning' view: 'Automatic backup embedded configuration': If the checkbox is activated, then the configuration which is currently saved in the ↑ 'Site' will be loaded into the PC and saved as a backup.
Software administration Pre-settings ● 'Data bits:': Amount of data for transfer ● 'Stop bits:': Data transfer stop bit ● 'enable DTR': If the checkbox is activated, the ready state of the destination data terminal will be indicated by an interface control signal. ●...
Software administration Pre-settings 4.5.5.2 Customer text suggestions The following can be set in the 'Customer text proposals' view: Property / function Value Description 'Customer text proposals 'first letters' The Engineering Tool shows texts that have already filtration style' been entered as text suggestions to make entering texts easier.
Software administration Pre-settings 4.5.8 Periphery update In the 'Periphery update' view, the ports for updating the peripheral devices can be defined: ● For devices that are connected directly to the COM port. ● For devices that are connected via USB or FDUZ22x. The settings are automatically set as standard when a device is updated.
4.9 Calling up log files of Engineering Tool You can open the directory containing the log files of Engineering Tool via the start menu: ● Start > All Programs > Siemens > F-FX7230 > [Version] > Log files [Version] = Version of the software 43 | 412...
Overview of the program window 5 GUI 5.1 Overview of the program window Title bar Hyperlinks Menu bar Status bar Task cards Tree Table Toolbar Detail editor 44 | 412 Building Technologies A6V10210424_j_en_-- Fire Safety 2018-08-29...
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...
Page 46
Menu bar Replace element Replacing element Show replace element log Change element address: -1 Decrease the address of the selected element as well as all higher elements by one Change element address: +1 Increase the address of the selected element as well as all higher elements by one Merge sites Merge two 'Sites'...
Page 47
Menu bar Cerberus- Connect Connect Cerberus-Remote Remote Connect to favorite Connect Cerberus-Remote with 'Station' from the Favorites list Add to favorites Add connected 'Station' to the Favorites list Disconnect Disconnect Cerberus-Remote Network Reset network configuration Set standard values for the IP addresses and network masks of all sub-nets.
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'...
Help and tooltips 5.4 Help and tooltips There are two sources of information in Cerberus-Engineering-Tool: ● Help ● Tooltips Help There are three ways of calling up the Help function: ● Press <F1>. ● Select 'Help' > 'Help' from the menu bar. ●...
Template for customer data 5.5 Template for customer data When creating a new ↑ 'Site', a form for entering customer-specific data opens in the 'Create new site' window. The data that is entered in the 'Creator' section can be stored as a standard template with 'Set creator values as default'.
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.
Expanding and collapsing the elements in the structure tree 5.9 Expanding and collapsing the elements in the structure tree An element with subtree can be expanded or collapsed according to functionality in Windows Explorer. Elements in the structure tree can be expanded and collapsed as follows: ●...
Navigating within the program window 5.11 Navigating within the program window Navigation in the program window functions according to the Windows standard. Navigation between the task cards or the perspectives of a ↑ 'Site' is specific to Cerberus-Engineering-Tool. Opening a perspective or changing from one perspective to the other is possible using the following control elements: ●...
Status bar 5.11.3 Navigating with shortcuts The table below lists the shortcuts. Description Shortcut Changing between task cards <Ctrl> + <F8> Changing between windows of a task card <Ctrl> + <F7> Opening and closing subtrees Left or right arrow keys Navigating between elements in the structure tree Up or down arrow keys Navigating between columns of the table...
Error indication and problem identification 5.13 Error indication and problem identification 'Error' when loading to the 'Station' An 'Error' prevents the configuration being loaded to the 'Station'. The following message is displayed: Open the 'All problems' window to display the errors for the entire ↑ 'Site'. Display the errors for one element.
Page 56
Error indication and problem identification Displaying the 'Error' for one element Read the information in the status bar at the bottom edge of the program window and / or click on the information in the status bar. 1. Right-click on an element with a red or yellow exclamation mark. 2.
Cerberus Remote 'Error' and 'Warning' identification in the tree view ● Red exclamation mark next to an element: 'Error', e.g., inadmissible or duplicate element ● Yellow exclamation mark next to an element: 'Warning', e.g., missing ↑ assignment A ↑ 'Site' can be stored on the PC even if there is an 'Error'. Figure 13: 'Error' in the tree view See also 2 Dynamic loading [➙...
Page 58
Cerberus Remote Cerberus-Remote is opened via the 'Cerberus-Remote' task card in the program window. 001 AAA 001 ABC YYYY ABCDEFGHI ABCDEFGHI ABCDEFGHI Example of Cerberus-Remote in operation mode 'Full access (view/operation)' with red frame The button with the loudspeaker symbol (bottom right in the figure) is used to switch an activated buzzer on and off.
Page 59
Cerberus Remote 'Limited access (view only)' In this operation mode Cerberus-Remote indicates the same as the 'Station' connected to it, but you cannot operate the linked 'Station'. The figure in 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 'Station' is visualized as in the 'Limited access (view only)' operation mode.
Dynamic loading 5.15 Dynamic loading To increase the performance of Cerberus-Engineering-Tool, not all 'Stations' are loaded to the software at the same time for ↑ 'Sites' with more than eight ↑ 'Stations'. 'Stations' that are not loaded are shown in gray and in italics. The 'Stations' are dynamically loaded and unloaded, depending on the selection.
Page 61
Dynamic loading 'Assign' function When elements are assigned with the 'Assign' function, the 'Stations' that are not loaded are shown in gray. If you would like to create an ↑ assignment to an element of a 'Station' that is not loaded, you must click on the 'Station' to load it. Figure 15: Window with stations that are and are not loaded The buttons below can be used to navigate through the list of elements that can be assigned in sequence.
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 large number of ↑ 'Stations'. If this happens, we would recommend reloading the ↑...
Program operation Creating a site 6.1.2 Create 'Site' based on an existing configuration NOTICE Unauthorized characters in the ↑ 'Site' name or in the path: < > / \ | : ? * " % # 'Site' may not be able to be saved or loaded. ●...
Program operation Creating a site 6.1.3 Creating a new 'site' NOTICE Unauthorized characters in the ↑ 'Site' name or in the path: < > / \ | : ? * " % # 'Site' may not be able to be saved or loaded. ●...
Program operation Creating a site 6.1.4 Editing 'site' properties NOTICE Unauthorized characters in the ↑ 'Site' name or in the path: < > / \ | : ? * " % # 'Site' may not be able to be saved or loaded. ●...
Page 66
Program operation Creating a site 2. In the 'Site properties' dialog, enter the identification number under 'Equipment no.'. Info: The BDV used may also restrict the sequence of characters permitted in the 'Equipment no.' input field. The characters are marked in red if they do not meet the specifications.
Program operation Creating a station 6.2 Creating a station If you are creating a ↑ 'Station' for the first time, decide whether the 'Station' will be networked or if it is going be a ↑ 'Standalone station'. You can create 'Stations' with the following network properties: ●...
Program operation Creating a station with FBP [AU] Creating a 'Station' with an individual address This function is normally called up when migrating from old systems if a particular address is to be assigned to a 'Station'. Once the 'Station' has been created, the address cannot be changed any more. The maximum value that can be set for the address of the 'Station' is 250.
Page 69
Program operation Create element 1. Open the 'New element' window. This can be done in the following ways: – Click on the symbol in the toolbar. – Select 'Edit' > 'New element' from the menu bar. – Right-click in the tree view and select 'New element' in the context menu. a The 'New element' window opens above the table.
Program operation Replacing element 6.5 Replacing element You can replace the template of one element with another template of the same element type. In certain cases you can also replace an element with an element of another type. Replacing element 1.
Program operation Table Editing several elements simultaneously 1. In the tree view, select the elements that you wish to edit. a The properties that are available in all the highlighted elements are displayed in the detail editor. 2. Edit the desired properties. a The properties will be changed in all of the highlighted elements.
Program operation Entering quicktext 6.8.2 Inserting text in columns Texts can be inserted in the table in columns from the clipboard. The texts on the clipboard may be copies of other files, e.g., columns copied from Excel. Example: Prepare customer texts for zones in an Excel column, copy the column to the clipboard, and insert it in the table in Engineering Tool in column 'Customer text'.
Program operation Copying, cutting, and pasting elements 6.10 Copying, cutting, and pasting elements The functions for copying, cutting and pasting elements correspond to the Windows standard and can be used in the tree and the table as well as between the tree and the table.
Program operation Moving an element 6.11 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.
Page 75
Program operation Re-addressing elements Reducing address by 1 Gaps are produced in the address sequence when you delete, cut / paste, move, or re-address elements throughout ↑ stations. Proceed as follows to close gaps in the address sequence: 1. Highlight the element after the gap in the tree view. 2.
Program operation Assigning elements 6.13 Assigning elements Elements from the same or different task cards can be assigned using the 'Assign' function. A ↑ physical channel is assigned to a ↑ logical channel. Opening 'Assign dialog' The 'Assign dialog' window can be opened as follows: ●...
Page 77
Program operation Assigning elements Tree view of the assignable elements: ● Light gray text: The path leads to an element that cannot be assigned ● Bold text: The path leads to an element that can be assigned ● Bold characters, greyed out: assignable element ●...
Program operation Creating additional information elements 6.14 Creating additional information elements You can use 'New additional information element' to add additional information to an element in one of the following structure trees: ● 'Hardware tree' ● 'Detection tree' ● 'Control tree' ●...
Page 79
Program operation Creating additional information elements Creating 'New additional information element' A 'New additional information element' can only be created on the 'Station' level or below. A New additional information element cannot be created below the element Global system configuration. Additional New additional information element elements of any type can be created below a New additional information element of type Additional component.
Page 80
Program operation Creating additional information elements 5. Under 'Amount:' select the number of additional elements to be created. 6. Click on 'Add' in the 'New additional information element' window. a The tool creates the selected 'New additional information element' element under the marked element.
Page 81
Program operation Creating additional information elements Searching for 'New additional information element' elements and replacing their meta data You can use the 'Find and replace' function to search for 'New additional information element' elements and replace their meta data. This reduces the time needed for configuration when you have to change lots of meta data for a 'New additional information element' element at the same time.
Program operation Importing CDVs 6.15 Importing CDVs ↑ CDV stands for 'Country Data Variant'. After importing a valid CDV into the configuration tool, elements within the structure tree can be provided with structured additional information. This structured additional information can be used to search for specific information in the configuration tool.
Program operation Assignment with Data Matrix code 6.16 Assignment with Data Matrix code You can use a reading device for Data Matrix code to assign C-NET devices to 'Zones' using a layout plan. The adhesive labels of the device are stuck on to the layout plan.
Program operation Assigning elements several times 6.17 Assigning elements several times Multiple assignment allows several elements and event categories, inputs, or outputs to be assigned to each other at the same time. Assigning elements several times simultaneously 1. Select the 'Assign' function for the element to be assigned. 2.
Program operation Assigning the effects of a control 6.18 Assigning the effects of a control 1. Select the 'Control' task card. 2. Open the 'Station' in the tree view. 3. Open the control group you want. 4. Open the control element you want. 5.
Program operation Finding and replacing 6.20 Finding and replacing You can use the 'Find and replace' function to apply various search criteria to search for and replace elements, e.g., according to 'Address', 'Customer text', or 'Problem'. Figure 18: Finding and replacing The search criteria available depend on the selected task card.
Program operation 'Switch to 'Search and replace'' button Search options ● 'Entire site': Search in the entire ↑ 'Site'. ● 'Selected sub-tree': Search in the highlighted subtree. ● 'Include': Search for values that have as a component the search value that you entered in the upper right field.
Program operation Exporting an XML 2. Adjust the search if necessary. 3. Execute the required search function. You will find information on the search functions in chapter 'Finding and replacing [➙ 86]'. See also 2 Finding and replacing [➙ 86] 6.22 Exporting an XML You can export the configuration of the ↑...
Page 89
Program operation Exporting an XML Standard XML export 1. Check the 'Create Standard XML report' checkbox. 2. Select the path, enter a file name, and click on 'Create report'. a You have exported the configuration of the 'Site' into an XML file. User-defined XML export The user-defined XML export supports direct XSLT transformation of the export.
The SiB-X export function can be used to export the configuration data definitions into an XML file in SiB-X format. SiB-X is the format for exchanging configuration data between various products of Siemens Building Technologies, e.g., Management System MM8000. Exporting configuration data...
Program operation Exporting and importing CSVs 6.24 Exporting and importing CSVs The menu entries for CSV export and import are available only in the 'Detection' task card. Only data in the ↑ 'Detection tree' is taken into account for CSV export or CSV import.
Page 92
Program operation Exporting and importing CSVs Creating new elements in the CSV file 1. Enter the 'Area address' in the first column. 2. Depending on the element type, enter the 'Section address', 'Zone address', and 'Channel address' elements. 3. Enter the element type in the 'Type' column, taking the following into account: –...
Program operation Exporting and importing CSVs 6.24.3 Importing CSVs Length of customer text A customer text must be no more than 40 characters. If a customer text contains more than 40 characters in the CSV file, the text is shortened to 40 characters automatically when it is imported.
Change display logo 6.25 Change display logo By default, in the normal state of the ↑ 'Station', the Siemens logo is shown on the display. You can replace the Siemens logo with a customer specific logo. The logo must be available as a GIF file and must meet the following requirements: ●...
Program operation Creating reports 6.26 Creating reports You can generate various reports as PDF or XML files in the 'Reports' window. Creating a report 1. Select the task card from which you wish to create a report. 2. Select 'File' > 'Reports' from the menu bar or click on the symbol in the toolbar.
Program operation Creating reports 6.26.1 Customer text report The 'Customer text report' lists the customer texts of all elements of the respective task card. ● Create report link [➙ 95] You can make the following settings in the 'Settings' section: ●...
Program operation Creating reports 6.26.2 Device report Regardless of which task card is selected, the 'Device report' lists the number of elements available in the ↑ 'Hardware tree', ↑ 'Detection tree', and ↑ 'Control tree'. On the one hand, the elements are listed as in the tree view, with the number of elements in the parent element.
Program operation Creating reports 6.26.3 Diagnostics report The 'Diagnostics report' lists the 'Site info properties' and the software and firmware versions of the hardware in the entire ↑ 'Site'. ● Create report link [➙ 95] Only the properties existing in the elements are listed here, i.e. only some of the following possible properties: ●...
Program operation Creating reports 6.26.4 Event memory report The 'Event memory report' lists the events of a ↑ 'Site'. ● Create report link [➙ 95] You can use filter options to limit the number of listed events, e.g. events of a particular event category within a particular time period.
Program operation Creating reports 6.26.5 Import information report The 'Import information report' outputs a list of imported elements and their IDs following completion of an import from inventory systems. ● Create report link [➙ 95] The following filter settings are possible: ●...
Program operation Creating reports 6.26.7 Peripherals test report The 'Peripherals test report' lists the last test activations of the peripheral devices. The test date and the activation type is listed for each test activation. Creating a 'Peripherals test report' 1. Load the latest configuration from the station to the PC. Link [➙ 108] 2.
Program operation Creating reports 6.26.8 Soiling report The 'Soiling report' lists the 'Compensation value' of the detectors. ● Create report link [➙ 95] The following elements are listed for each* detector: ● Device customer text ● Device address path ● Operating years ●...
Program operation Creating reports 6.26.9 Tree report In the 'Tree report', properties of the elements from the structure tree of the respective task card are listed in table format, e.g., ↑ parameter set, 'Serial no. ("ID-Nr.")', and 'Template ID'. ● Create report link [➙...
IP address when a connection is established to the GAP via C-WEB/LAN. See also 2 Establishing connection from PC to FS720 network [➙ 327] 7.1 Connecting the PC to the station For most commissioning, maintenance and repair work a PC with installed Cerberus-Engineering-Tool is required.
Connectivity and communication with 'Station' Connecting Cerberus Remote 7.3 Connecting Cerberus Remote w Enabling for viewing and / or operating the ↑ 'Station' with Cerberus-Remote is granted. w The PC is connected to the ↑ 'Site'. 1. Select the 'Cerberus-Remote' task card. 2.
Connectivity and communication with 'Station' Load data to the station 7.4 Load data to the station Data is loaded from Cerberus-Engineering-Tool to the ↑ 'Station' when the following commands are performed. ● 'Initialize station' ● 'Download site' If you use more than one network cards on the PC, observe the information contained in chapter 'IP settings for several network cards [➙...
Connectivity and communication with 'Station' Loading configuration from the PC to the station 7.6 Loading configuration from the PC to the station You can use the 'Download site' function to load the configuration of one ↑ 'Site' from the Cerberus-Engineering-Tool on the PC into the ↑ 'Station'. NOTICE Different network configuration in 'Cerberus-Engineering-Tool' and networked 'Site'...
Connectivity and communication with 'Station' Loading configuration from the station to the PC 1. Select 'Commissioning' > 'Download site' in Cerberus-Engineering-Tool. a The 'Download site' and 'Connect' windows open in Cerberus-Engineering- Tool. 2. Select the connection in the 'Connect' window and click on 'OK'. a The 'Stations' are listed in the 'Download site' window.
Connectivity and communication with 'Station' Loading event memory to PC 3. Select the 'Stations' whose configuration you would like to load to Cerberus- Engineering-Tool and click on 'Start'. a The 'Action confirmation' window opens. 4. Click on 'Yes'. a The configuration is loaded to the PC. a The progress is displayed in the 'Upload site' window.
You will find the 'Handover site' and 'Handover station' functions in the 'Commissioning' menu. For more information about 'handover', contact your designated in-country Siemens regional company. 110 | 412 Building Technologies A6V10210424_j_en_--...
Updating the firmware Updating the firmware of the 'Station' 8 Updating the firmware 8.1 Updating the firmware of the 'Station' There are three options for updating the firmware of the ↑ 'Station': ● 'FW update main CPU': Updating the main CPU ●...
Updating the firmware Updating the firmware of the peripheral devices 8.2 Updating the firmware of the peripheral devices You can update the firmware of the following peripheral devices: ● Floor repeater terminal FT2010 ● Floor repeater display FT2011 ● Radio gateway FDCW221 ●...
Configuration –Overview Converting a station 9 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...
Configuration –Overview With pre-configuration Deactivating the mouse wheel of the computer mouse NOTICE Unintended scrolling in drop-down lists Configuration error caused by unintended modification of settings ● Read the following description. ● To deactivate the mouse wheel, activated the checkbox 'Ignore mouse wheel' in the pre-settings.
Configuration –Overview Without pre-configuration 9.2 Without pre-configuration During commissioning, first the components and the ↑ 'Station' periphery are read in. There are two ways of reading in the periphery: ● The C-NET detector lines are read in individually. The resultant physical structure is loaded in Cerberus-Engineering-Tool.
'Hardware' task card 'Station' 10 'Hardware' task card The components of the ↑ 'Station' and the peripheral devices are shown in the 'Hardware' task card. The components are automatically read in when the 'Station' is started. The C-NET devices must be read in with a command on the 'Station'. Figure 23: Task card with the tree view and table Once the data has been loaded into Cerberus-Engineering-Tool, the components of the 'Station' and the C-NET devices are visible in the 'Hardware tree'.
'Hardware' task card 'Station' ● 'Events' tab: 'Event categories' and event texts ● 'Intervention' tab, see chapter 'Intervention concept (IC) [➙ 117]'. ● 'Buzzer' tab: – 'Element address' and 'Customer text' of the buzzer – The 'Disable operating terminal buzzer while Cerberus-Remote is active' checkbox defines whether the buzzer should be switched off while 'Cerberus-Remote' is active.
Page 118
'Hardware' task card 'Station' Configuring intervention concept Figure 25: Detail editor with settings for the intervention concept 1. Select the 'Hardware' task card. 2. Highlight a ↑ 'Station' in the tree view. 3. Select the 'Intervention' tab in the detail editor and set the properties you want. Immediate intervention The following can be set for immediate intervention: ●...
'Hardware' task card Onboard I/Os 10.1.2 Configuring permanent access for Cerberus-Remote Permanent access has to be configured for each ↑ 'Station' of the ↑ 'Site'. Configuring permanent access means that access at the 'Station' is not required. You will find more information on the Cerberus-Remote operation modes in chapter 'Cerberus Remote [➙...
'Hardware' task card C-NET detector line 10.3 C-NET detector line Adjusting the properties for a C-NET detector line in the 'Overview' 'Up to 252 devices allowed per line': This setting specifies the maximum permissible number of devices per C-NET detector line: ●...
'Hardware' task card C-NET detector line 10.3.1 Automatic fire detectors Setting properties of an automatic fire detector 1. Select the 'Hardware' task card. 2. In the tree view, open the 'Station' > the line card > the loop or stub. 3.
'Hardware' task card C-NET detector line In the detail editor of the assigned 'Zone', you can set level at which the base sounder will be activated: ● In 'PRE-STAGE' and 'MAIN STAGE' ● Only in 'MAIN STAGE' This setting is not possible in 'Zones' without 'PRE-STAGE'. In addition to this setting of the base sounder, you can configure a 'Universal sounder evac control' and assign it to a base sounder.
'Hardware' task card C-NET detector line 10.3.3 Sensor mode with multi-sensor fire detectors In the case of multi-sensor fire detectors, you can set which sensor is to be used. Setting the sensor mode Figure 29: Properties in the detail editor of the sensor of a multi-sensor fire detector 1.
'Hardware' task card C-NET detector line 'EVAC tone' This setting specifies the tone in the 'Evac' mode. 'Sounder volume' This setting specifies the sound level in the activated status. 10.3.5 External alarm indicator Some C-NET devices have an output for an ↑ external alarm indicator. The output can be used to actuate an external alarm indicator and for controls.
'Hardware' task card C-NET detector line 10.3.6 Alarm sounder and interbase You can configure the properties for the acoustic and optical alarming for the following devices: ● Alarm sounder FDS221 ● Alarm sounder with supplementary optical indication FDS229 ● Sounder interbase DBS721 ●...
'Hardware' task card C-NET detector line 'Flashing pattern' This setting specifies the flashing pattern of the beacon. If you select a flashing pattern with a self-test function, then the beacon will light up briefly every couple of hours. If you do not want the beacon to light up during ↑ normal operation, then you must select a flashing pattern without self-test function.
Page 127
'Hardware' task card C-NET detector line Sounder element – parameters in the 'Overview' tab Parameters Value Description 'Custom audio library ID' Indicator field The audio library displays the parameter that the sounder in question is using. [0]: Standard audio library Note: The configured ID number in the allocated [1...2047]: No.
Page 128
'Hardware' task card C-NET detector line Parameters Value Description 'ALERT tone' '1: Continuous, 970Hz [BS The parameter defines the alarm tone that the 5839]' sounder plays when active. The alarm tones are standardized. The values in '2: Intermittent, 950Hz [BS brackets refer to the underlying standard or 5839]' guideline.
'Hardware' task card C-NET detector line 10.3.8 Aspirating smoke detector You will find more information about the aspirating smoke detectors in document A6V10334410. See chapter 'Applicable documents'. The elements 'FDA221' and 'FDA241' each contain the ↑ following physical channels: ● 'Sensor 1' ●...
Page 130
'Hardware' task card C-NET detector line 'Parameter set 'manned'' This setting specifies the ↑ parameter set of the detector for 'Manned operation'. 'Parameter set 'unmanned'' This setting specifies the ↑ parameter set of the detector for 'Unmanned operation'. 'Sensor operating mode FDA' ('Sensor 1' only) This setting specifies the sensor mode of the detector.
You will find the product version (ES) on the type plate of the input/output module. Siemens Switzerland Ltd. Fire Safety & Security Products FDCIO223...
Page 132
'Hardware' task card C-NET detector line 'Collective line type' This setting specifies which type of ↑ collective detector line is connected. 'Coll. line: alarm response / fault delay' This setting specifies the alarm reaction time and the fault delay time of the ↑...
'Hardware' task card C-NET detector line 'Enable temporary freeze of output position' If the checkbox is checked, the 'Freeze selected outputs ON' command is available for the output. The position of the output is not changed if the ↑ 'Station' or line is restarted, a configuration is loaded to the 'Station', or a module is reset.
'Hardware' task card Power supply 10.4 Power supply Operation modes The power supply for the ↑ 'Stations' has the following operation modes: ● Operation with battery backup – The power supply unit feeds the hardware with system voltage, continuously charging the batteries. In the event of mains voltage failure, the batteries take over the power supply of the 'Station' without interruption.
'Hardware' task card LED indicator FTO2002 Setting the properties of the I/O cards In the detail editor for the elements 'I/O card (remote transm., FCI2007)' and 'I/O card (horn/monitored, FCI2009)', you can adjust the following in the 'Details' tab: Figure 41: Settings in the detail editor of an I/O card 'Sounder output monitoring': This setting specifies in accordance with which standard the outputs will be monitored.
'Hardware' task card. 1. Open the 'Network' task card. 2. Highlight the following element: 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' > 'Connections' > 'Station with the FN2012' 3. In the 'Overview' tab, enter the IP address of the FN2012 under 'IP address network switch'.
Page 138
Activate fault monitoring only for ports to which FS720 stations have been connected. w An 'Ethernet switch (modular, FN2012)' element is created within a station in the 'Hardware' task card.
'Hardware' task card Inputs/outputs Commissioning You will find a description of how to commission an FN2012-A1 that is connected to the station via a ribbon cable in document A6V10210416. See chapter 'Applicable documents'. Redundancy management You can configure redundancy management for Ethernet networks with several elements of the 'Ethernet switch (modular, FN2012)' type in the 'Redundancy management configuration' element in the 'Network' task card.
Page 140
'Hardware' task card Inputs/outputs 'Short circuit monitoring enabled' This setting specifies whether the monitoring is activated when there is a short circuit. The short circuit monitoring requires a special wiring. If the short circuit monitoring is deactivated, then a short circuit is evaluated as 'active'.
'Detection' task card Creating 'Detection tree' 11 'Detection' task card The following logical elements are shown in the 'Detection' task card: ● ↑ 'Area' – The 'Area' element is also created when creating a ↑ 'Station'. – Additional 'Area' elements can be created for each 'Station'. ●...
'Detection' task card 'Area' 11.2 'Area' Each control panel contains the following 'Areas': 'Detection area' 'Detection area' is the uppermost element in the 'Detection tree'. Several 'Station' are possible per 'Detection area': ● FC722, FC724: Max. 4 ● FC726: Max. 8 The 'Detection area' has an alarm verification concept (AVC) and can be configured and assigned to the controls independently of other areas.
Page 143
'Detection' task card 'Area' 'LOCAL alarming stopped by ACKN.' This setting specifies which local ↑ alarming equipment is stopped by the command 'Acknowledge'. Activate the respective checkbox. 'GLOBAL alarming stopped by ACKN.' This setting specifies which global alarming equipment is stopped by the command 'Acknowledge'.
Page 144
'Detection' task card 'Area' 'Alarming type 'thermal'' This setting specifies the alarming type for thermal detectors. ● '* Not used *': The alarming type for thermal detectors is not defined. The settings for 'Alarming type 'manned'' and 'Alarming type 'unmanned'' are used. ●...
Page 145
'Detection' task card 'Area' Configuring the AVC settings for the line alarm 1. Select the 'Hardware' task card. 2. Highlight a ↑ detector line in the tree view. 3. Go to the 'Events' tab and select the category 'Collective FIRE ALARM (line alarm) | ------General autom.
'Detection' task card 'Area' 11.2.2 Immediate global alarming The 'Immediate global alarming' setting is used to determine under which of the following preconditions the ↑ alarm verification concept is directly and globally alarmed: ● ' - (disabled)' ● 'Upon 2nd alarm within area' ●...
'Detection' task card 'Section' 11.2.3 Alarm organization mode The 'Alarm organization mode' setting determines which statuses and functions, e.g., switchovers and indicators, of the ↑ alarm organization are used in this 'Area'. The following can be set: ● 'Always manned (no messages/no LED/no switching fct.)' ●...
Page 148
'Detection' task card 'Zone' The following table shows the properties of the templates along with the event category and the event text of the message that is generated with an alarm. Main features and typical application Typical event category Event text 'Single, Standard': ●...
Page 149
'Detection' task card 'Zone' Main features and typical application Typical event category Event text 'Single, local ALARM': ● 'PRE-STAGE': ● 'PRE-STAGE': ● Single-detector dependency – ' --Pre-ALARM, fire' – 'Pre-ALARM' ● With 'Pre-ALARM' ● 'MAIN STAGE': ● 'MAIN STAGE': ● Only the local alarming is activated in –...
Page 150
'Detection' task card 'Zone' ↑ Single-detector dependency and ↑ multi-detector dependency The following table shows the required number of detectors with ↑ danger level (GS) 2 or 3 in order to meet the criteria for 'PRE-STAGE'/'MAIN STAGE'' and to trigger an alarm. Template Required number of detectors with danger level (GS)
'Detection' task card 'Zone' 11.4.2 'Manual zone' 'Manual call points' are evaluated in the 'Manual zone'. The 'Zone' can however also be configured for inputs or collective detector lines. The danger signals are evaluated with an OR link. Each manual call point in the 'Zone' can generate an alarm, but not a ↑...
Page 152
'Detection' task card 'Zone' Main features and typical application Typical event category Event text 'Fault extinguishing system': ' --Other fault' 'Fault extinguish.' Evaluation of fault messages of a connected sub-system 'Gas ALARM': ' --Other technical message' 'Technic. Gas ALARM' Evaluation of alarms of a connected gas detector or a gas detector system 'Fault network device': ' --Other fault'...
'Detection' task card 'Zone' 11.4.4 'Sub-system zone' Signals from connected sub-systems are evaluated in the 'Sub-system zone', e.g. from collective fire control panels, aspirating smoke detection systems and gas detection systems. You can select between a variety of different templates that are pre-configured for various types of sub-systems for the creation of a 'Sub-system zone'.
'Detection' task card 'Zone' Outputs Events of the sub-system can be acknowledged and reset with the outputs. ● If you acknowledge an event, the output 'Output 'Acknowledge'' is activated for 3 s. ● If you reset an event, the output 'Output 'Reset'' will be activated. The duration of the activation is dependent on the setting 'Reset time' in the 'Details' tab: –...
'Detection' task card 'Zone' 11.4.6 'Sprinkler zone' Figure 50: General setup of the sprinkler system Flow rate indicator: special detector zone Sprinkler station with one or two contacts Hydrant network A sprinkler system is a piping system that is terminated at several locations with sprinkler heads.
Page 156
'Detection' task card 'Zone' Assigning 'Sprinkler zone' element The 'Sprinkler zone' element has the 'Causes' channel for connecting the 'Input 'Sprinkler 1'' and 'Input 'Sprinkler 2'' contacts of the sprinkler station and the 'Referenced flow switch zones' channel, which is assigned to the flow rate indicator zone.
'Detection' task card 'Zone' 11.4.7 'Gas zone' Gas detectors are evaluated with the 'Gas zone'. You can select between a variety of different templates that are pre-configured for various applications for the creation of a 'Gas zone'. The following table shows the properties of the templates along with the event category and the event text of the message that is generated with an alarm.
Page 158
'Detection' task card 'Zone' Sub-element of 'XC10 Input or output on Function zone' FDCIO222 Input 'Discharged' Activating or resetting the extinguishing release Input 'Fault' Fault message Input 'Pre-alarm' Activating or resetting the extinguishing pre-alarm Input 'Blocked' Blocking or enabling the extinguishing release Output 'Reset' OUT A...
Page 159
'Detection' task card 'Zone' 'Output 'Reset'' This output is used to reset the extinguishing release from a 'FS720' operating terminal. The FC720 activates 'Output 'Reset'', when the 'Reset' command is executed on the Person Machine Interface. 'Output 'Block autom.+manual'' This output is used to block the automatic and manual extinguishing release from a FS720 operating terminal.
Page 160
'Autom.+manual exting. release blockable from FS720' This setting specifies whether the automatic and manual extinguishing release can be blocked from the FS720 operating terminal. If the checkbox is activated, the blocking proceeds as follows: 1. On the Person Machine Interface of the FC720, the user selects a 'XC10 zone' and executes the 'Autom.+man.
This setting specifies whether blocking of the automatic extinguishing release from the extinguishing control panel is displayed on the FS720 operating terminal. If the checkbox is activated, the blocking proceeds as follows: 1. The automatic extinguishing release is blocked by the extinguishing control panel.
'Detection' task card Configuring the 'Zone' 11.5 Configuring the 'Zone' 1. Select the 'Detection' task card. 2. Highlight a 'Zone' in the tree view. 3. Select the 'Overview' or the 'Details' tab in the detail editor. 4. Set the desired properties. The settings are described in the following sections. Depending on the 'Zone', not all settings are available.
Page 163
'Detection' task card Configuring the 'Zone' These settings take effect only if a direct activation of the external alarm indicator or of the base sounder is configured. You will find more information on direct activation in chapter 'Detector parameter sets'. 'OFF allowed' Option Effect...
'Detection' task card Configuring the 'Zone' 'Multi detector dependency with latching' This property specifies whether multi-detector dependency with latching is activated. This property is activated, e.g. for 'Automatic zone', with the 'Two-zone dependency' template. You will find more information on this in chapter 'Multi-detector dependency with latching'.
'Detection' task card Configuring the 'Zone' 'Multi, 2 det. dependency II' [AT]: The checkbox 'Multi detector dependency with latching' is activated. The detectors assigned to a 'Zone' are evaluated in a multi-detector dependency with the signal being stored. If the 'Zone' reaches the pre-stage then the danger levels of the detectors that have reached the criteria of the pre-stage are stored as a criterion for the main stage.
'Detection' task card Configuring the 'Zone' Example 'Criteria PRE-STAGE': 1 detector with danger level 3 'Criteria MAIN STAGE': 2 detectors with danger level 3 1. One detector reports danger level 3. 2. The 'Zone' reaches 'PRE-STAGE'. 3. Danger level 3 of the detector is latched as the criterion for 'MAIN STAGE'. 4.
'Detection' task card Configuring the 'Zone' 3. Select 'Two-zone dependency' at the left in the window. a The ↑ 'Detection tree' is depicted at the right of the window. The elements that can be assigned are highlighted. 4. Select the second 'Zone' for the two-zone dependency. 5.
Page 168
'Detection' task card Configuring the 'Zone' ● 'VDE0833: Danger level(s) first + new fault(s)': Faults of the detectors are evaluated in addition to the danger levels as criteria for reaching 'PRE-STAGE' or 'MAIN STAGE', respectively. When a danger level is reached and an additional danger level and/or a fault is reported, then 'PRE-STAGE' or 'MAIN STAGE', respectively, is reached.
'Detection' task card Assign hardware tree to the detection tree 11.6 Assign hardware tree to the detection tree WARNING Incorrect sensor link for the FDA221 and FDA241 If the FDA221 or FDA241 sensors are assigned to different 'Zones', the detection behavior corresponding to the ↑...
'Detection' task card Collective detector line via input/output module FDCIO223 or zone module 11.7 Collective detector line via input/output module FDCIO223 or zone module You can use the following elements to connect ↑ collective detector lines: ● Inputs/outputs of input/output module FDCIO223 ●...
'Detection' task card Neural fire detector OOHC740 Setting the properties of the collective detector line 1. Highlight the assigned collective detector line in the tree view. 2. Set the properties you want in the detail editor. You will find a description of the properties in the 'Hardware' tab in the following chapters: 'Input/output module FDCIO223 [➙...
'Detection' task card Neural fire detector OOHC740 11.8.2 Configuring gas detection You can assign the 'Gas sensor' element to a 'Technical zone' or 'Gas zone'. According to EN 54, it is not permitted to assign the gas sensor to a 'Automatic zone' and therefore generate a fire alarm.
Page 173
'Detection' task card Neural fire detector OOHC740 If the temperature or CO concentration deviates from the threshold value, the input can switch between active and inactive. To prevent this, a hysteresis can be defined. As soon as the threshold value is reached and the input is activated, it is not deactivated again until the temperature or the CO concentration at least drops below the threshold value or rises above it by the defined hysteresis value.
'Detection' task card Redux module [DE] 11.9 Redux module [DE] The Redux module serves for data transmission and power supply redundancy of a fire brigade indication panel (FAT). The data cable is connected to the control panel's RS485 interface. If one of the connection lines to the FAT fails due to a short-circuit or open line, complete functionality is ensured.
'Control' task card Creating control tree 12 'Control' task card Controls are configured in the 'Control' task card. The controls are combined into the following ↑ control groups: ● 'Alarming control group': Controls for internal and external sounders and remote transmission outputs for Fire and Fault. ●...
'Control' task card Alarming control group 12.2 Alarming control group The alarming control group includes the following control elements: ● 'Internal sounder control' ● 'External sounder control' ● 'RT fire control' ● 'RT fault control' ● 'RT 1 control' to 'RT 8 control' ●...
Page 177
'Control' task card Alarming control group Assigning cause NOTICE Incorrect cause assignment for 'Activation timeout 'manned'' / 'Activation timeout 'unmanned'' The 'Activation timeout 'manned'' / 'Activation timeout 'unmanned'' sounder property is only evaluated for one 'Area' element in the detection tree or for elements within one 'Area' element.
'Control' task card Alarming control group Assigning effect 1. Select the 'Control' task card. 2. Open the 'Station' in the tree view. 3. Highlight the 'Effects' element in a control element of the 'Alarming control group'. 4. Open the 'Assign dialog' window. 5.
Page 179
'Control' task card Alarming control group 2. Assign 'Causes' to a PMI in the 'Operation tree' / event category 'Cause 'RT isolation'' > ' --Access level <> default level'. Link [➙ 76] 3. Highlight the assigned PMI element in the tree view. 4.
'Control' task card Alarming control group 12.2.2 Properties of the assigned effect elements You can set additional properties in the assigned effect elements of an ↑ alarming control. The settings are described in the following sections. If the ↑ effect is assigned to an RT channel, you can set the following: Figure 62: Settings in the detail editor of an assigned RT channel 'OFF allowed while AVC active (t1/t2)' This setting specifies whether the ↑...
Page 181
'Control' task card Alarming control group 'Enabled': The two settings 'Enabled' specify whether a time-out is used for the activation of the control. The time-out can be set separately for 'Manned operation' and 'Unmanned operation'. NOTICE Incorrect cause assignment for 'Activation timeout 'manned'' / 'Activation timeout 'unmanned'' The 'Activation timeout 'manned'' / 'Activation timeout 'unmanned'' sounder property is only evaluated for one 'Area' element in the detection tree or for...
'Control' task card Universal control group 12.3 Universal control group The ↑ 'Fire control group' combines several 'Fire controls'. In the 'Fire control', one or more 'Input' elements are created in the cause. An event can be assigned to this. The executing element will be assigned to the ↑ effect of the 'Fire control' element.
Page 183
'Control' task card Universal control group 6. Select the element you want. 7. Click on 'Assign'. a The element is assigned to 'Causes'. Assigning effects Two trees, one above the other, are visible in the figure below. The lower tree appears only when a confirmation input can be assigned.
Page 184
'Control' task card Universal control group 12.3.1.2 Fire control properties Figure 64: Properties in the detail editor of the element 'Fire control' 'START mode' This setting defines the conditions for the activation of the control. The following conditions are possible: ●...
Page 185
'Control' task card Universal control group Delay times and time-out ● 'Activation delay': The activation of the control is delayed by the set time after the activation condition is met. ● 'Deactivation delay': The deactivation of the control is delayed by the set time after the deactivation condition is met.
Page 186
'Control' task card Universal control group 'OFF allowed' This setting indicates whether or not and under which circumstances the element can be switched off: ● 'Always': 'The element can always be switched off. ● 'Never': The element can never be switched off. ●...
Page 187
'Control' task card Universal control group 'Threshold': The value in this field specifies how many events of the corresponding event category are required in the element or the subtree, to activate the control. If the control is deactivated again, it is re-activated by a new event of the given event category.
'Control' task card Universal control group Example: The cause is assigned to the ' --AVC, Fire ALARM' event category and the 'Detection area' element. In the detail editor of the 'Detection area' element, the 'AVC/IC: Global alarming' checkbox is activated. The cause is only active when a 'Fire ALARM' triggers the 'AVC' and the 'AVC' is in the 'global alarming' condition.
Page 189
'Control' task card Universal control group NOTICE Configuring several causes Only one cause element may be active within a 'Time control' at any one time. The times for activating and deactivating causes must not overlap if several causes are configured for one 'Time control'. ●...
Page 190
'Control' task card Universal control group 12.3.2.2 Creating and configuring a time control cause Creating 'Time control cause' 1. Highlight the element 'Causes'. 2. Open the 'New element' window. 3. Select 'Add'. a The 'Time control cause' cause element is created. Configuring 'Time control cause' WARNING Activation or deactivation operations performed incorrectly in the event of a time...
Page 191
'Control' task card Universal control group 'Overview' tab ● Customer text ● Activation - Time: Defines the time at which the 'Time control cause' element will be activated on the specified day ● Activation - Days of the week: Defines the day/s on which the activation will take place at the specified time ●...
'Control' task card Evac control group 12.3.2.3 Assigning time control effects Use the 'Assign' function to assign commands and outputs as effects. Link [➙ 85] 12.4 Evac control group The 'Evac control group' element is the higher-level configuration element for all evac.
Page 193
'Control' task card Evac control group Configuring universal sounder evac. control The sequence only contains the necessary configuration steps. You will find information about the elements that can be assigned or created, as well as the parameters, in separate sections further down in this chapter. NOTICE Incorrect cause assignment for 'Activation timeout 'manned'' / 'Activation timeout 'unmanned''...
Page 194
'Control' task card Evac control group 5. Assign the required events to the 'Causes' function with 'Assign', e.g., a fire alarm in a detection area. Alternatively, you could also assign an input signal. Tip: You can use multiselection to mark several events for an assignable element and assign these as causes.
Page 195
'Control' task card Evac control group 'Universal sounder evac control' – parameters in the 'Overview' tab Parameters Values Description 'START mode' 'No automatic activation' The operating personnel can only activate the control manually with a command. 'Formula true' The system activates the control when the Boolean expression in the 'Formula' field is true.
Page 196
'Control' task card Evac control group Parameters Values Description 'Enabled' On/off The parameter determines a defined time period. Once this period has elapsed, the control is 'Activation timeout' Input field for time period automatically deactivated again, even if at least one [hh:mm:ss] activation condition is still met.
Page 197
'Control' task card Evac control group Parameters Value Description 'DEACTIVATION allowed' ‒ The parameter determines whether the control can be deactivated again when it has been automatically activated by a cause. The following options can be configured: 'NOT if activated ●...
Page 198
'Control' task card Evac control group 'Universal sounder evac control' – 'Causes' assignments – parameters in the 'Overview' tab Parameters Values Description 'Event category' Indicator field The field displays the event category which results in the system triggering the cause function. 'Threshold' Numerical input field The parameter determines the minimum number of...
'Control' task card Evac control group 'Universal sounder evac control' – 'Effects' assignments – parameters in the 'Overview' tab The following table describes possible parameters in the 'Overview' tab for 'Effects' assignments: Parameters Values Description 'Enabled' On/off Activates or deactivates the 'Activation timeout 'manned'' parameter.
Page 200
'Control' task card Evac control group The table shows the configurable phased evac. controls: Evac control Description 'Phased sounder evac Element for configuring a phased evac. control with control' alarm devices that can only play tones. You will find more information on this phased evac. control in chapter 'Phased sounder evac.
Page 201
'Control' task card Evac control group w An 'Evac control group' element is created in the 'Control tree'. 1. For each separate building zone to be evacuated, create a 'Phased sounder evac control' element under the 'Evac control group' element. This could be a single floor, for example.
Page 202
'Control' task card Evac control group 6. Assign one or more 'PHASED sounder' elements to the 'Effects' element with 'Assign'. Alternatively, you can assign separate alarm devices for each of the evacuation phases 'Alert' and 'Evac' with the 'ALERT sounder' and 'EVAC sounder' elements.
Page 203
'Control' task card Evac control group 'Phased sounder evac control' – parameters in the 'Details' tab Parameters Value Description 'Accept commands On/off Acoustic sounders connected to the control can be 'Sounders ON/OFF'' from switched off at any time using the corresponding FBF' button on the fire brigade operating panel (FBF) when the parameter is activated.
Page 204
'Control' task card Evac control group 'Phased sounder evac control' – 'Causes' assignments – parameters in the 'Overview' tab The parameters described below are not available or cannot be configured in every 'Causes' assignment. The following table describes possible parameters in the 'Overview' tab for 'Causes' assignments: Parameters Values...
Page 205
'Control' task card Evac control group 12.4.2.2 Phased voice evac. control The sounders FDS225 and FDS227 and the sounder base FDSB227 play corresponding voice messages with an optional pre-notification tone instead of an 'Alert' tone or an 'Evac' tone. Among other things, these devices can perform phased evac.
Page 206
'Control' task card Evac control group w An 'Evac control group' element is created in the 'Control tree'. 1. For each separate building zone to be evacuated, create a 'Phased voice evac control' element under the 'Evac control group' element. This could be a single floor, for example.
Page 207
'Control' task card Evac control group 7. Assign the required events to the 'Causes EVAC FIRE (+DEGRADED MODE)' and 'Causes ALERT' elements with 'Assign'. For the 'Causes ALERT' element, this can be a fire alarm in a detection zone, for example. Alternatively, you could also assign an input signal.
Page 208
'Control' task card Evac control group 'Phased voice evac control' – parameters in the 'Overview' tab Parameters Values Description 'Custom audio library ID' Numerical input field The parameter determines which audio library should be used by the devices assigned to the Adjustment range: control.
Page 209
'Control' task card Evac control group Parameters Value Description 'DEACTIVATION allowed' ‒ The parameter determines whether the control can be deactivated again when it has been automatically activated by a cause. The following options can be configured: 'NOT if activated ●...
Page 210
'Control' task card Evac control group 'Phased voice evac control' – 'Causes' elements – parameters in the 'Overview' tab The parameters described below are not available or cannot be configured in every 'Causes' element. Parameters Value Description 'Priority' Indicator field The parameter shows the priority with which a causes function is activated.
Page 211
'Control' task card Evac control group 'Phased voice evac control' – 'Causes' elements – parameters in the 'Details' tab The parameters described below are not available or cannot be configured in every 'Causes' element. Parameters Value Description On/off 'Reactivation upon This setting determines whether the system is to unsuccessful reset' reactivate an already deactivated control again if the...
Page 212
'Control' task card Evac control group 'Phased voice evac control' – 'Effects' assignments – parameters in the 'Overview' tab The following table describes possible parameters in the 'Overview' tab for 'Effects' assignments: Parameters Values Description 'Enabled' On/off Activates or deactivates the 'Activation timeout 'manned'' parameter.
Page 213
'Control' task card Evac control group Example of evacuation process in the event of a fire on the fifth floor The evacuation processes and delay times listed in the section are for example purposes only. Please see the planning documents for the building in question for actual evacuation processes and delay times.
Page 214
'Control' task card Evac control group Sample configuration for a 2-stage, multi-phase building evacuation process w There is a ↑ 'Section' element created for each floor in the 'Hardware' task card. w At least one alarm device or sounder of 'PHASED sounder' type is installed on every floor.
Page 215
'Control' task card Evac control group 5. Leave the 'Delay' parameter for the 'Section' elements or the 'Detection area' element at '00:00:00' as immediate warning is required on each floor. 6. Use multiselection to select all 'Section' elements or the 'Detection area' element under the 'Causes ALERT' element and copy these using the 'Copy' function.
Page 216
'Control' task card Evac control group 9. Highlight the configured 'Phased sounder evac control' element or the 'Phased voice evac control' element and copy it using the 'Copy' function. 10. Use 'Paste' to add the copied 'Phased sounder evac control' element or the 'Phased voice evac control' element to the 'Evac control group' element.
Page 217
'Control' task card Evac control group 14. Configure the delay times for the evacuation of this floor in the 'Table' view using the 'Delay' parameter. Information: The delay times specify how much time needs to elapse before this floor is evacuated if a fire alarm is signaled on one of the floors in the table. Information: Please see the planning documents for the building in question for specific evacuation times.
'Control' task card Evac control group 12.4.3 Prioritized voice evac. control The sounders FDS225 and FDS227 and the sounder base FDSB227 play corresponding voice messages with an optional pre-notification tone instead of an 'Alert' tone or an 'Evac' tone. In addition to the phased voice evac. controls with predefined priorities for the individual ↑...
Page 219
'Control' task card Evac control group Configuring prioritized voice evac. control The sequence only contains the necessary configuration steps. You will find information about the elements that can be assigned or created, as well as the parameters, in separate sections further down in this chapter. NOTICE Incorrect cause assignment for 'Activation timeout 'manned'' / 'Activation timeout 'unmanned''...
Page 220
'Control' task card Evac control group 7. Assign the required events to the elements 'Causes EVAC FIRE (+DEGRADED MODE)', 'Causes EVAC EMERGENCY', 'Causes ALERT', 'Causes CUSTOM 1', and 'Causes CUSTOM 2' with 'Assign'. For the 'Causes ALERT' element, this can be a fire alarm in a detection zone, for example. Alternatively, you could also assign an input signal.
Page 221
'Control' task card Evac control group 'Prioritized voice evac control' – parameters in the 'Overview' tab Parameters Values Description 'Custom audio library ID' Numerical input field The parameter determines which audio library should be used by the devices assigned to the Adjustment range: control.
Page 222
'Control' task card Evac control group Parameters Value Description 'DEACTIVATION allowed' ‒ The parameter determines whether the control can be deactivated again when it has been automatically activated by a cause. The following options can be configured: 'NOT if activated ●...
Page 223
'Control' task card Evac control group 'Prioritized voice evac control' – 'Causes' elements – parameters in the 'Overview' tab The parameters described below are not available or cannot be configured in every 'Causes' element. Parameters Value Description 'Priority' Numerical input field The parameter defines the priority with which a causes function is activated.
Page 224
'Control' task card Evac control group 'Prioritized voice evac control' – 'Causes' elements – parameters in the 'Details' tab The parameters described below are not available or cannot be configured in every 'Causes' element. Parameters Value Description On/off 'Reactivation upon This setting determines whether the system is to unsuccessful reset' reactivate an already deactivated control again if the...
Page 225
'Control' task card Evac control group 'Prioritized voice evac control' – 'Effects' assignments – parameters in the 'Overview' tab The following table describes possible parameters in the 'Overview' tab for 'Effects' assignments: Parameters Values Description 'Enabled' On/off Activates or deactivates the 'Activation timeout 'manned'' parameter.
'Control' task card Evac control group 12.4.4 Configuring an audio sequence w A 'Phased voice evac control' element or a 'Prioritized voice evac control' element is created within a 'Evac control group' element. 1. Under the element in question, mark the 'Causes' element whose 'Audio sequence' you wish to configure.
Page 227
'Control' task card Evac control group 'Audio sequence'- parameters Parameters Values Description 'Audio stop mode' ‒ The parameter determines when the system terminates a current audio sequence when the activating cause group is deactivated. Information: If several cause groups are active at the same time, the system always plays the audio sequence of the cause group with the highest priority.
Page 228
'Control' task card Evac control group Parameters Values Description 'Pre-announce tone' '1: Continuous, 970Hz [BS An alarm tone with the selected characteristics is 5839]' played before the voice message. The alarm tones are standardized. The values in '2: Intermittent, 950Hz [BS brackets refer to the underlying standard or 5839]' guideline.
Page 229
'Control' task card Evac control group Parameters Values Description '1st message' 'M1: Evac FIRE' The parameter determines which standard voice message should be played first when this cause 'M2: Evac EMERGENCY' group is activated. 'M3: Alert' Information: All available voice messages can be selected for the 'Causes CUSTOM 1' and 'Causes 'M4: Test' CUSTOM 2' cause groups.
'Control' task card Counter control group and alarm counter control Parameters Values Description '2nd message' The voice messages that The parameter determines which standard voice can be selected message should be played second when this cause correspond to those for the group is activated.
Contains the 'Fire damper control' and 'Smoke extraction control' elements ● Control of fire and smoke dampers that are connected to the FS720 via inputs and outputs, e.g., via an input/output module on the detector line The damper controls have the following configuration elements: ●...
'Control' task card Damper control group 12.6.1 Creating and configuring a damper control 1. Create a 'Damper control group' in the control tree and underneath this a 'Fire damper control' or a 'Smoke extraction control'. 2. Assign the cause element to an event or to an input and make the settings for the cause element properties.
'Control' task card Damper control group 12.6.2 Damper control states The damper control state and the display of this state on the PMI are dependent on the parameter value for 'Tolerance 'open'' OR on the state of the 'Main damper'. Fire damper control Fixed state: It is not possible to change the assignment between the state of the control and the state of the fire damper.
Page 234
'Control' task card Damper control group Description of the effect elements The following effects are pre-configured: ● 'Fire damper control' – 'Fire damper output/supervised': Control of the damper actuator motor for opening or closing the damper. The inputs for monitoring the damper state are located under this output.
Page 235
'Control' task card Damper control group Contact position with 'Input 'Damper inactive'', fire damper open AC IN AC IN DC IN - DC IN + FDCIO222/4 S1 S2 S3 S4 S5 S6 Contacts S4 and S6 closed: Damper state open Contact position with 'Input 'Damper active'', fire damper closed AC IN AC IN...
Page 236
'Control' task card Damper control group 12.6.3.2 Smoke dampers: Wiring and assignment This chapter describes the wiring and assignment aspects based on the default states of the damper controls [➙ 233]. Effects which can be Input/Output of the FDCIO222/4 Input on the Wired to contact/s...on the assigned in Engineering Tool...
Page 237
'Control' task card Damper control group Contact position with 'Input 'Input 'Damper active'', smoke damper open AC IN AC IN DC IN + DC IN - OUT D OUT C FDCIO222/4 S1 S2 S3 S4 S5 S6 Contacts S1 and S2 closed: Damper state open 237 | 412 A6V10210424_j_en_-- Building Technologies...
'Control' task card Damper control group 12.6.4 Fire damper control properties 'Overview' tab Specific properties for 'Fire damper control': 'Tolerance 'open'' A 'Fire damper control' element corresponds to a ventilation zone with a defined number of fire dampers. The parameter determines the ventilation zone's maximum number of fire dampers that must not be in the 'Open' position to allow the fire damper control to accept the overall status 'Open'.
'Control' task card Damper control group 12.6.5 Properties of the assigned effects 'Overview' tab 'Main damper' ('Fire damper control' only) If the checkbox is checked, the damper is the main damper. The state of the control/ventilation zone is set to 'closed' if the main damper is 'closed'. 'Timeout 'close'' Defines the time within which the 'closed' state must be confirmed once the control has activated the output.
XSLT style sheet – Example: Command Line Transformation Utility (msxsl.exe) ● Provided by FS720: XSLT style sheet Generating an EDE export w You have an XSLT processor or equivalent software with this functionality, e.g., msxsl.exe. w You have created and configured the damper controls. Link [➙ 232] 1.
Page 241
'Control' task card Damper control group Configuring LED 1 for the 'Open' (green) and 'Damper moving' (OFF) damper states 1. Select 'LED/output | 1' and assign the LED as follows: – Go to the left of the 'New cause dialog' and select the ' --Damper changing position' event under 'Events 'Information''.
'Control' task card Extinguishing standard interface SST [DE] Configuring LED 2 for the 'Timeout/Fault/Unexpectedly open/Unexpectedly closed' damper state 1. Select 'LED/output | 2' and assign the LED as follows: – Go to the left of the 'New cause dialog' and select the 'All faults' event under 'Events 'Fault''.
Page 243
'Control' task card Extinguishing standard interface SST [DE] Creating an output for extinguishing actuation An output of the input/output module is used to actuate the extinguishing process via the extinguishing control system. The command for the extinguishing actuation is give by detector zone(s) of the fire control panel. Figure 70: 'New cause dialog, Assign dialog' window for assigning the cause for the extinguishing actuation Figure 71: 'New cause dialog, Assign dialog' window for assigning the effect for the extinguishing...
Page 244
'Control' task card Extinguishing standard interface SST [DE] Assigning 'Input 'Discharged'' An input of the input/output module serves is used to confirm extinguishing activated. Figure 72: 'Assign dialog' window for assigning the 'Input 'Discharged'' element To assign 'Input 'Discharged'', proceed as follows: 1.
Page 245
'Control' task card Extinguishing standard interface SST [DE] Creating a 'Fault extinguish.' input Figure 73: 'New element' window for creating the technical ↑ zone for 'Fault extinguish.' Figure 74: 'Assign dialog' window for assigning the 'Fault extinguish.' input To create and assign the 'Fault extinguish.' input, proceed as follows: 1.
Page 246
'Control' task card Extinguishing standard interface SST [DE] Configuring the visibility on the fire department operating panel (FBF) To ensure that the extinguishing system activation is correctly signaled by the LED on the fire brigade operating panel, the 'XC10 zone' element must be assigned to the fire brigade operating panel.
'Control' task card External alarm indicator 12.8 External alarm indicator The ↑ external alarm indicator output of a C-NET device can be used for any evacuation control or ↑ fire control. Assigning external alarm indicator output Figure 76: 'New cause dialog, Assign dialog' window with 'Output/NO confirmation' w The outlet for the external alarm indicator is not used for direct activation.
'Control' task card Loop sounder, loop sounder/beacon, and base sounder 12.9 Loop sounder, loop sounder/beacon, and base sounder 'Sounder', 'Sounder beacon', and 'Base sounder' can be allocated to the following controls: ● In the alarming control group as: – Internal 'Sounder' –...
'Control' task card Sounder line via input/output module FDCIO223 Configuring 'Sounder' Figure 78: 'Control' task card with 'Hardware' detail editor The 'Sounder' configuration is displayed in the detail editor of the 'Control' task card, provided that the following conditions are met: ●...
Page 250
'Control' task card Sounder line via input/output module FDCIO223 4. In the toolbar, click on 'Assign'. a The 'New effect dialog' window opens. a The 'Hardware tree' is depicted at the right of the window. The elements that can be assigned are highlighted. 5.
'Control' task card Input/output module FDCIO223 with monitored input/output 'Activation timeout 'unmanned'': This setting specifies the duration of the time-out in 'Unmanned operation'. The time-out is started when the control is activated. After the expiration of the set time, the sounder is deactivated automatically. NOTICE Incorrect cause assignment for 'Activation timeout 'manned'' / 'Activation timeout 'unmanned''...
'Control' task card Addressable alarm indicator FDCAI221 12.12 Addressable alarm indicator FDCAI221 The addressable ↑ alarm indicator FDCAI221 can be assigned to any cause using a control. The addressable alarm indicator can be assigned to the effects of the following controls: ●...
'Operation' task card Global system configuration 13 'Operation' task card The 'Operation' task card contains the logical elements for the global system configuration and for configuring the operation and indication units. 13.1 Global system configuration The element 'Global system configuration' is available once per ↑ 'Site' and contains the following elements: ●...
Page 256
If this checkbox is checked, a BACnet notification is created if a fault or information event occurs on an FS720 detector line or on a device within the detector line. A 'Line fault summary' or 'Line information summary' is created, the BACnet object type of which is 'Life-Safety'.
Page 257
'Operation' task card Global system configuration ' --Expiry reminder of time lim. isol.' This setting specifies when the reminder message is displayed. If, for example, the setting is '00:05', a reminder message is displayed five minutes before the duration of the isolation (bypass) expires and the 'Zone' or the 'Detector' is switched back on again automatically.
● Change the preset PIN. ● Create an 8-figure PIN according to the IT security requirements from Siemens; see PIN guidelines. NOTICE No firmware update possible due to no 'Access level 3' ● At least one PIN with 'Access level 3' must be configured.
'Operation' task card Person Machine Interface (PMI) 13.1.3 Country settings Country-specific settings are defined in the 'Country settings' element. 13.1.4 Master clock The 'Global system time' element shows which ↑ 'Station' is the master clock. When the first 'Station' is created, Cerberus-Engineering-Tool assigns this element to the first 'Station' (address 1) automatically.
'Operation' task card Person Machine Interface (PMI) 13.2.1 Basic settings You will find the basic settings for the ↑ Person Machine Interface in the detail editor of the 'PMI' element. 'Overview' tab The following properties can be set in the 'Overview' tab: 'Logout timeout' This setting specifies the length of time after which the ↑...
'Operation' task card Person Machine Interface (PMI) 'Reminder buzzer' This setting specifies at which events the 'Buzzer' is reactivated at regular intervals as a reminder that something needs to be done. Example: In the case of an ALARM event, the 'Buzzer' sounds twice every 15 seconds briefly. 'Default alarm view' This setting specifies in which view messages are shown on the display in the case of an alarm e.g.
Page 262
'Operation' task card Person Machine Interface (PMI) 13.2.2.1 Assigning the hardware ID to the LED The figure below shows the assignment of the hardware ID to the corresponding LED on the ↑ Person Machine Interface. The numbers correspond to the hardware ID of the LED.
Page 263
'Operation' task card Person Machine Interface (PMI) Setting the properties of the assigned cause element on the 'Overview' tab ● 'Event filter': Event that activates the cause and thus the LED. All events within the configured ↑ visibility of the element are evaluated. ●...
'Operation' task card Person Machine Interface (PMI) 13.2.3 Standard keys Figure 88: 'Standard keys' element in the tree view Each standard key can be assigned a function or a toggle function. With that you can quickly carry out often used actions and commands. You can configure the following types of functions: ●...
'Operation' task card Person Machine Interface (PMI) 13.2.4 Favorites Figure 89: 'Favorite keys' element in the tree view There are a maximum of eight favorites of which three are preconfigured. Each favorite can be assigned a function. With that you can quickly carry out often used actions and commands.
Page 266
'Operation' task card Person Machine Interface (PMI) 13.2.4.1 Creating favorites Three favorites are preconfigured. 1. Select the 'Operation' task card. 2. Open the ↑ 'Station' > 'PMI' in the tree view. 3. Highlight 'Favorite keys'. 4. Open the 'New element' window. 5.
'Operation' task card Person Machine Interface (PMI) 13.2.4.3 Defining the position of the favorites The position specifies at which place the favorite is displayed in the 'Favorites' menu. The positions are from top left to bottom right. The favorites with positions '1' to '3' are assigned to the three softkeys in the main menu.
Page 268
'Operation' task card Person Machine Interface (PMI) 13.2.5.2 Assigning standard keys and favorites To assign a function to a standard key or a favorite, proceed as follows: 1. Select the 'Operation' task card. 2. In the tree view, open ↑ 'Station' > ↑ 'PMI' > 'Standard keys', or 'Favorite keys'. 3.
Page 269
'Operation' task card Person Machine Interface (PMI) Assigning to 'Dialog' If you select 'Dialog' on the left in the window, you can select 'Standard' on the right in the window. You can set the properties of the view in the detail editor of the ↑...
Page 270
'Operation' task card Person Machine Interface (PMI) Assigning to a command for a specific element If you select a command on the left in the window, you can select a tree and the element on the right in the window for which the command is to be executed. Figure 97: Assigning a standard key or a favorite to a command and an element Assigning to a command for a 'Zone' If you select 'Command/element category' on the left in the window, you can select...
Page 271
'Operation' task card Person Machine Interface (PMI) 13.2.5.3 Properties of the assigned functions In the detail editor of the functions which are ↑ assigned to the standard keys and the favorites, you can set different properties depending upon the assigned functions.
'Operation' task card Person Machine Interface (PMI) Assigning to a command for an element category If the standard key or the favorite is assigned to a command function for an element category, you can set the following properties in the detail editor of the function: Figure 102: Properties in the detail editor of the command function 'Access level': Defines the access level for the command...
Page 273
'Operation' task card Person Machine Interface (PMI) 13.2.6.1 Configuring standard key for the toggle function Configuring the command Figure 103: Assigning a standard key to a command and an element 1. Select the 'Operation' task card. 2. Open ↑ 'Station' > 'PMI' > 'Standard keys' in the tree view. 3.
Page 274
'Operation' task card Person Machine Interface (PMI) Configuring a reverse command Figure 104: 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.
Page 275
'Operation' task card Person Machine Interface (PMI) 3. Select 'Related LED' at the left in the window. a At the right in the window, the 'Operation tree' is displayed. 4. Select the appropriate LED for the standard key. 5. Click on 'Assign'. a The standard key is assigned to the LED.
'Operation' task card Visibility 13.3 Visibility The visibility defines which parts of a ↑ 'Site' can be viewed and/or operated on a ↑ 'Station'. You can configure the visibility as follows: ● 'Site': Visibility for the entire 'Site' ● 'Site without areas': Visibility for all events from the 'Hardware tree' of the 'Site' ●...
'Operation' task card Visibility 'Visible secondary events' This setting specifies from which normally not visible elements, the activation messages are displayed if they are activated by an element in the visible part. You can define the visible event categories in the detail editor of the elements assigned to the visibility in the 'Overview' tab.
'Station'. You will find more information in document A6V10211076. See chapter 'Applicable documents'. There are two different standby visibilities: ● 'Standby visibility for Operating terminal': For monitoring Stations 'FS720'. ● 'Standby visibility for Management station': For monitoring a management station.
Page 279
'Operation' task card Visibility Creating standby visibility 1. Select the 'Operation' task card. 2. In the tree view, open the 'Station' and highlight the 'PMI' element. 3. Open the 'New element' window. 4. In the 'Type:' field select 'Standby visibility for Operating terminal' or 'Standby visibility for Management station'.
Page 280
'Operation' task card Visibility 8. On the left in the window, from the 'PMI supervision for standby visibility' list, select the 'Visibility activation upon failure of Operating terminal..' entry. 9. On the right in the window, select the 'Station' which is to be monitored. 10.
'Operation' task card Visibility 9. On the right in the tree, select 'BACnet client supervision'. 10. Click on 'Assign'. a 'BACnet client supervision' is assigned to 'Standby visibility for Management station'. See also 2 Global BACnet configuration [➙ 330] 13.3.4 Expanded visibility Expanded ↑...
'Operation' task card Visibility Configuring expanded visibility Figure 112: Configuring expanded visibility 1. Select the 'Operation' task card. 2. Open the ↑ 'Station' > 'PMI' in the tree view. 3. Highlight the 'Expanded visibility' element. 4. In the toolbar, click on 'Assign'. a The 'Assign dialog' window opens.
'Operation' task card Floor repeater terminal FT2010 and floor repeater display FT2011 4. Select 'Standard visibility'. 5. Select 'Assign'. 6. In the 'Assign' window, select the 'Station' on which you want to set 'Visibility' for smartphones and confirm your choice by clicking 'Assign'. 7.
'Operation' task card Floor repeater terminal FT2010 and floor repeater display FT2011 13.4.2 Visibility Display The 'Visibility' element can be used to determine which events can be shown in the display for the ↑ floor repeater terminal (FRT) and the ↑ floor repeater display (FRD).
'Operation' task card Floor repeater terminal FT2010 and floor repeater display FT2011 13.4.3 LEDs The LEDs on the ↑ Person Machine Interface signal events and conditions. In addition, the LEDs support the operator's orientation. Figure 116: 'Programmable LED', 'Cause' detail editor The following LEDs properties can be configured: ●...
'Operation' task card Floor repeater terminal FT2010 and floor repeater display FT2011 13.4.5 Assigning the configurable keys and LEDs Assigning the key ID to the key The figure below shows the assignment of the key ID to the corresponding configurable key on the ↑ Person Machine Interface of the ↑ floor repeater terminal.
Page 287
'Operation' task card Floor repeater terminal FT2010 and floor repeater display FT2011 Assigning the LED ID to the LED The figures below show the assignment of the LED ID to the corresponding configurable LED on the ↑ Person Machine Interface of the ↑ floor repeater terminal and ↑...
'Operation' task card LED indicator FTO2002 and mimic display driver FT2001 13.5 LED indicator FTO2002 and mimic display driver FT2001 You will find details on the technical term ↑ 'C-NET' in the chapter 'Glossary'. The following devices can be used as a mimic display: ●...
'Operation' task card LED indicator FTO2002 and mimic display driver FT2001 13.5.1 Element 'LED ind./mimic 24 LED groups' Assigning events Figure 122: Window 'Assign dialog' for assigning a 'Visibility' of the element 'LED ind./mimic 24 LED groups' to an event To assign the 'LED ind./mimic 24 LED groups' element to an event, proceed as follows: 1.
'Operation' task card LED indicator FTO2002 and mimic display driver FT2001 13.5.2 Element 'LED ind./mimic 48 LEDs' Assigning events Figure 124: 'New cause dialog' window for assigning a 'Visibility' of the 'LED ind./mimic 48 LEDs' element to an event To assign the 'LED ind./mimic 48 LEDs' element to an event, proceed as follows: 1.
Page 291
'Operation' task card LED indicator FTO2002 and mimic display driver FT2001 Setting properties Figure 125: 'LED ind./mimic 48 LEDs', 'Overview' detail editor ● 'Supply supervision enabled': Defines whether a local supply is present which is to be monitored. Figure 126: 'Visibility', 'Overview' detail editor In the detail editor of the 'Visibility' element, the following properties can be set: ●...
'Operation' task card Event printer 13.5.3 Configuring mimic display driver FT2001 Figure 127: 'LEDs/outputs' detail editor In the detail editor the following properties can be set: ● 'Suppress LED test, connector 1', 'Suppress LED test, connector 2' Blocks the triggering of an LED test of the outputs on connection 1 or 2 via the local input.
Page 293
'Operation' task card Event printer Hardware is already read in Figure 128: 'Assign dialog' window for creating and assigning the 'Built-in printer' or 'External printer' element To create the 'Built-in printer' or 'External printer' element and assign it to the hardware, proceed as follows: 1.
'Operation' task card Fire brigade periphery [DE] Visibility configuration The ↑ visibility that the event printer logs is defined in the 'Visibility' element. The following selection is available: ● 'Site': Visibility for the entire ↑ site. ● 'Site without areas': Visibility for all events from the 'Hardware tree' of the site. ●...
Page 295
'Operation' task card Fire brigade periphery [DE] ↑ Pre-configuration To create the logical element, proceed as follows: 1. Select 'Operation' > 'Station' in the task card. 2. Create the FBF, FSD, FAT, or FAT with FBF element for the 'Station'. Link [➙...
Page 296
'Operation' task card Fire brigade periphery [DE] Connecting with RS485 Figure 131: 'Assign dialog' window for creating and assigning to the RS485 interface To create the logical FBF or FAT element and to assign it to the RS485 module (FCA2002) element, proceed as follows: 1.
Page 297
'Operation' task card Fire brigade periphery [DE] ● Fire brigade indication panel FAT: – Visibility: 'Site': visibility on the entire site 'Site without areas': Visibility for all events from the Hardware tree of the site. 'Station': Visibility for one 'Station' within the site, with all areas in this 'Station'.
'Operation' task card EVAC panel [NL] Operation of the fire brigade key depot (FSD) Figure 134: 'FSD', 'Hardware' detail editor In the 'Hardware' detail editor, there are special settings for the fire brigade key depot FSD if the checkbox in the 'Operated' field is checked: ●...
Page 299
'Operation' task card EVAC panel [NL] Assigning the 'Evac master' to the hardware 1. Highlight the 'Evac master' element in the tree view. 2. Open the 'Assign dialog' window. a The hardware tree is depicted. The 'Channel' element that can be assigned is highlighted in the 'Evac master unit (FTO2007)' element.
Page 300
'Operation' task card EVAC panel [NL] Properties of the 'Evac master' element – 'Overview' tab The properties of the 'Evac master' element in the 'Details' tab can only be configured if the EVAC panel [NL] is installed outside the station, it has its own power supply, and it is connected to the station via an RS485 module (FCA2002).
Page 301
'Key switch/PIN code on ● The access protection is provided by a key FS720 operating terminal' switch or PIN code at the connected FS720 station. Information: For this type of access protection, the 'Access level of keys 'Start'/'Stop'' property can be used to determine the access level that the operating personnel require in order to use the 'Start' and 'Stop' buttons.
Page 302
'Operation' task card EVAC panel [NL] Assigning the 'Evac slave' to the hardware 1. In the tree view, highlight the 'Evac slave' element that you have just created. 2. Open the 'Assign dialog' window. a The ↑ hardware tree is depicted. The 'Channel' element that can be assigned is highlighted in the 'Evac slave unit (FTO2007)' element.
'Operation' task card Alarming equipment (UGA) [FR] 13.9 Alarming equipment (UGA) [FR] The alarming equipment (UGA) is an operating and indication unit for four alarm zones. The unit has its own control for the ↑ alarm devices by alarm zone and its own degraded mode behavior.
'Operation' task card Alarming equipment (UGA) [FR] 13.9.3 Configuring visibility Figure 138: Assigning a visibility 1. Select the 'Operation' task card. 2. In the tree view, open 'UGA alarm zone' element and highlight 'Visibility'. 3. In the menu bar, click on 'Assign'. a The 'Assign dialog' window opens.
(STT) in the CERLOOP network. FS720-'Stations' are represented as CERLOOP participants with an independent CERLOOP address. The telegrams are only sent in one direction via an RS232 interface, i.e. from the FS720-'Station' to the communication module for CERLOOP nodes K1H061. NOTICE...
'Operation' task card CERLOOP gateway [FR] 13.10.2 Creating and assigning the CERLOOP gateway Figure 140: Creating and assigning the CERLOOP gateway 1. Select the 'Operation' task card. 2. In the tree view, highlight the ↑ 'Station' with the RS232 module. 3.
'Operation' task card CERLOOP gateway [FR] 13.10.3 Configuring visibility Assigning a visibility You must configure the ↑ visibility of the CERLOOP gateway for all 'Stations', which are defined as CERLOOP participants. Figure 142: Assigning a visibility 1. Select the 'Operation' task card. 2.
General The voice alarm and announcement system 'Cerberus PACE' does not currently support a connection to an FS720 fire detection system. The availability of this function is communicated in a product line announcement. The external voice alarm and sound system 'Cerberus PACE' is connected to an FS720 fire detection system via an RS485 interface.
Page 309
'Operation' task card Integrating 'Cerberus PACE' system 1. Highlight the following element in the 'Hardware' task card: 'FC72x' > 'Communication interfaces' Information: It must be the 'FC72x' station element to which the 'Cerberus PACE' system is connected. Information: This and the next two steps can be omitted if the hardware has already been imported.
Page 310
'Operation' task card Integrating 'Cerberus PACE' system 6. Highlight the 'Visibility' element within the created 'Cerberus PACE' element. 7. Use 'Assign' to assign the visibility of the required parts of the fire detection system to the 'Cerberus PACE' system. For example, this can be the station to which the 'Cerberus PACE' system is connected.
'Operation' task card Configuring connection event for Cerberus Mobile 13.12 Configuring connection event for Cerberus Mobile A station can be configured so that it issues an event when a mobile device establishes a connection to the station via the 'Cerberus Mobile' application. All stations that have corresponding visibility of the station then display a corresponding message on the display of the Person Machine Interface.
Engineering-Tool. See also 2 Applicable documents [➙ 13] 14.1 Network parameters You will find details of the ports in FS720 in document A6V101039439. See chapter 'Applicable documents'. 14.2 Network configuration 14.2.1 Creating networked 'Stations' Networked ↑ 'Stations' must be assigned to the 'Ethernet' or 'SAFEDLINK' sub-net: ''New station' window, 'Ethernet station' or 'SAFEDLINK station' option.
'Network' task card Network configuration The 'Fx72x/SAFEDLINK' references can then be moved to the various sub-nets using the 'Drag and drop', 'Cut' and 'Paste' or 'Unassign' and 'Assign' functions. If you create a ↑ standalone 'Station' and then expand the ↑ 'Site' with 'Stations', the standalone 'Station' automatically adopts the network settings of the first 'Station' added.
Proceed as follows to configure the 'Station' as 'GAP' or 'Secondary GAP': w 'Station' is configured as a ↑ router station or ↑ Ethernet station. 1. Open the 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' elements in the tree view of the 'Network' task card.
IP address when a connection is established to the GAP via C- WEB/LAN. w The ↑ 'Station' is configured as GAP. 1. Open the 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' > 'Functions' elements in the tree view of the 'Network' task card.
Page 316
6. Enter the IP address in the 'Overview' tab of the detail editor. 'SAFEDLINK sub-net' 1. Open the 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' elements in the tree view of the 'Network' task card. 2. Highlight 'SAFEDLINK sub-net'.
'Destination address' of the route is 'Cerberus-Engineering-Tool' and/or the management stations ● ↑ 'Gateway' is the FS720 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.
Page 318
– 192.168.100.10 Enter the routes in the GAP as follows: 1. Select the 'Network' task card. 2. Open 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' > 'Functions' > 'GAP'.' in the structure tree. 3. Highlight 'Routes'. 4. Enter the network data.
Figure 147: 'SAFEDLINK sub-net' detail editor To set the network speed, proceed as follows: 1. Open the 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' elements in the tree view of the 'Network' task card. 2. Highlight 'SAFEDLINK sub-net'.
'Network' task card Network configuration 4. In 'Secondary GAP', create a 'Route' element and enter the following values. – 'Destination address': Sub-net of management station B – 10.169.30.0 – 'Netmask': 255.255.255.0 – 'Gateway': Address of 'Security module (firewall)' B – 192.168.100.11 5.
Page 321
GAP [➙ 317]'. Establishing connection 1. Log in on the cRSP website. 2. Establish the FS720 connection to your ↑ 'Site' (VPN tunnel). 3. Select the 'Connection to IP address' option in the 'Connect' window. 4. Enter 'localhost' or '127.0.0.1'.
Network configuration 14.2.10 Configuring cloud gateway FG2004 The cloud gateway FG2004 is networked with the stations of an FS720 system via Ethernet and enables connection to a cloud. You will find information on setting a station up as a router in chapter 'Configuring a 'Station' as a router station [➙...
Page 323
'Network' task card Network configuration 6. Assign the FG2004 Station to the 'Standard visibility' element using 'Assign'. Optional: If required, assign visibility of the FG2004 Station to other stations with a 'PMI'. 7. Highlight the following element in the 'Operation' task card: 'Site' > 'Global system configuration' >...
Ethernet networks that have several Ethernet switches (modular) FN2012 [➙ 137]. You will find the 'Redundancy management configuration'' element in the 'Network' > 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' task card. For the 'Redundancy management configuration', the 'Type of redundancy configuration' can be configured manually on the 'Overview' tab.
Page 325
'Network' task card Network configuration 14.2.11.2 Configuring stub wiring To configure a 'Stub wired network' Ethernet network, you have to set 'Stub wired network' in the 'Type of redundancy configuration' field. When configuring the 'Stub wired network', you must suppress ring errors and port errors for the ports located at the respective end of the stub.
Page 326
'Network' task card Network configuration 14.2.11.3 Configuring loop wiring The 'Loop wired network' must be configured manually if the function of the 'Redundancy manager' is to be allocated to a specific FN2012. If the function of the 'Redundancy manager' does not have to be allocated to a specific FN2012, the automatic configuration type can be used for the 'Loop wired network'.
192.168.200.1 192.168.0.0 255.255.0.0 192.168.201.1 Table 17: Persistent routes A connection from the PC to the FS720 network can be established with the following three variants: ● Local connection – The PC is connected to the Ethernet connection of a ↑ standalone or ↑...
'Network' task card Setting up a Maximum Transmission Unit (MTU) ● For Cerberus-Remote – 'Cerberus-Remote' > 'Connect' The 'Connect' window is opened when a command is performed. 14.4 Setting up a Maximum Transmission Unit (MTU) The default setting for the MTU size is 1500 bytes. If a FW update fails, you can set lower values and apply them optionally for the 'Connection to IP address'.
'Network' task card Monitoring Ethernet switch (MM) and safety module (firewall) 14.5 Monitoring Ethernet switch (MM) and safety module (firewall) The 'Ethernet switch (MM) FN2008-A1' and 'Security module (firewall) FN2009-A1' network elements must be monitored for faults in the Ethernet. To do this, terminals F1 and F2 (fault) on the connector strip of the detector contact are connected to a configurable input/output on the periphery board or an input/output module.
'Network' task card Connecting management stations via BACnet/Ethernet 14.6 Connecting management stations via BACnet/Ethernet ↑ Management stations (↑ BACnet clients) are connected to FS720 via BACnet / Ethernet. ● A BACnet client is connected to the FS720 sub-system via the Ethernet interface of the Global Access Point (GAP).
Page 331
Range for instance number values for identifying the FS720 stations in BACnet. The address range is exported in SiB-X format. ● 'BACnet character set': Character set that is used in the BACnet protocol for text strings. FS720 functions internally with Unicode in UTF-8 format. Selectable character sets: –...
'Network' task card so that the ↑ BACnet client can be configured. This element defines the ↑ management stations or third-party devices that are accepted by the FS720 system. The customer text of this element is also used in the event memory to log all actions triggered by a management station.
'Network' task card Global BACnet configuration Creating 'BACnet client configuration' element 1. Select 'Network' > 'Global system configuration' > 'Global BACnet configuration' in the task card. 2. Create the 'BACnet client configuration' element for each BACnet client. Link [➙ 68] 3.
Page 334
'Network' task card Global BACnet configuration Creating 'BACnet client supervision' element 1. Select 'Network' > ↑ 'Station' in the task card. 2. Create the 'BACnet client supervision' element for the 'Station' for each BACnet client that is to be monitored. Link [➙ 68] Assigning the 'BACnet client supervision' and 'BACnet client configuration' elements 1.
'Network' task card BACnet device configuration 14.7.6 Configuring 'Standby visibility' for the management station 'Station' can be assigned to a ↑ 'Standby visibility for Management station'. If the ↑ management station fails, the assigned 'Station' automatically receives this ↑ visibility. You will find information on configuration of the standby view for management stations in chapter 'Standby visibility [➙...
Page 336
Configuration of the 'Station' as BBMD Selection of the 'Station' 1. In the tree view of the 'Network' task card, open the elements 'Global system configuration' > 'FS720 network configuration' > 'Ethernet sub-net' > 'Connections' or 'SAFEDLINK sub-net' > 'Connections'.
'Network' task card BACnet device configuration 1. Open 'Station' in the structure tree. 2. Highlight 'BACnet device object'. 3. Select 'Details' in the detail editor. 4. Check the 'Enable BBMD' checkbox. 5. Check the 'Enable FDT' checkbox only if a BACnet client has to register to this BBMD.
'Network' task card BACnet device configuration 14.8.3 BACnet Notification Class Element All ↑ stations contain a list of 25 pre-defined entries under 'BACnet Notification Class element' in the detail editor. Each entry stands for a ↑ BACnet notification class and has one unique address and one customer text within a station. The addresses are used in the BACnet object ID as instance numbers.
Page 339
'to-fault': Entry of a fault – 'to-normal': ↑ Normal operation re-established Internally the FS720 fire detection system only processes the acknowledgements for the 'to-offnormal' and 'to-fault' status changes. The 'to- normal' status change can also be supported with acknowledgement for ↑...
'Network' task card Checklist for network and BACnet configuration 14.9 Checklist for network and BACnet configuration The checklists below list settings that must be entered and / or checked for ↑ BACnet integration. Checklist for network configuration Figure 161: Example of network configuration Element in the structure tree Configuration in the detail editor Required setting/value...
Page 341
'Network' task card Checklist for network and BACnet configuration Checklist for BACnet configuration Figure 162: Example of BACnet configuration Element in the structure tree Configuration in the detail editor Required setting/value 'Global BACnet configuration' 'Enable BACnet communication' Activated 'BACnet character set' UCS-2 'Address range, lower limit' 'Address range, upper limit'...
Page 342
'Network' task card Checklist for network and BACnet configuration Element in the structure tree Configuration in the detail editor Required setting/value 'BACnet client supervision' 'Client supervision timeout' 2.2 times value of BACnet client's query cycle 'BDT entry' 'IP address' for partner BBMD Depending on network configuration 'BACnet UDP port' 47808...
'Network' task card MP1XS site configuration status 14.10 MP1XS site configuration status If an MP1XS site configuration (BDV <32) is loaded in Cerberus-Engineering-Tool, the network configuration is shown as before. The 'Network' > 'Convert to GAP', 'Convert to SAFEDLINK host', 'Convert to ethernet host', and 'Create GAP configuration' menu items are also available.
Cloud gateway FG2004 15 Cloud gateway FG2004 FG2004 must be prepared and configured for 'C-WEB/Ethernet' in line with the document 'FG2004 Cloud-Gateway – A6V11382550', see chapter 'Applicable documents'. You will find information on configuring the FG2004 in the Engineering Tool in chapter 'Configuring cloud gateway FG2004 [➙...
Basic configuration steps 16 Extinguishing This chapter describes the configuration of the components for single-sector extinguishing within an integrated FS720 fire detection and extinguishing system with the engineering tool set FX7230. 16.1 Basic configuration steps The configuration of the extinguishing components comprises the basic steps described below.
Extinguishing Configuring the extinguishing card 7. Configure the forwarding of the extinguishing trigger state of a flooding zone to an output according to EN 12094-1. Link [➙ 391] 8. Optional: Adapt or configure the global settings for extinguishing. Link [➙ 396] This includes, for example, setting up the PIN for the extinguishing terminals.
Extinguishing Configuring the extinguishing card 4. Optional: Below the 'Terminals' element, create a new 'Optional XTO2001' element for every necessary remote extinguishing terminal. 5. Enter the required customer text and, if necessary, the physical address in the 'Overview' tab for the 'Optional XTO2001' element. 16.2.1 Configuring inputs and outputs The sequence only contains the necessary configuration steps.
Page 348
Extinguishing Configuring the extinguishing card 'Extinguishing card (XCI2005)' – 'Outputs' – parameters in the 'Overview' tab The table below describes the configurable parameters for 'Output' elements in the 'Overview' tab. Not every 'Output' element has all of the parameters described below.
The configuration process is performed using the conventional activation zones for an 'FS720' fire detection installation. You will find more information on configuring the individual 'Zone' types in chapter ''Detection' task card [➙ 141]'.
Page 350
Extinguishing Configuring automatic extinguishing activation Configuring automatic extinguishing activation with one activation zone This extinguishing activation option has only one activation zone, which is not dependent on other activation zones. The activation of the flooding zone is only dependent on an individual detector or a detector zone in the activation zone. As a result, this type of activation is ideal for object protection, whereby individual objects, such as control cabinets or machines, need to be protected by a flooding zone.
Page 351
Extinguishing Configuring automatic extinguishing activation Configuring automatic extinguishing activation with multiple activation zones This type of extinguishing activation consists of several activation sectors that can request pre-activation or triggering of the assigned flooding zone separately from one another. Requests are evaluated in the associated 'Extinguishing sector control' element for the flooding zone in question.
Page 352
Extinguishing Configuring automatic extinguishing activation 'Zone'element – parameters in the 'Details' tab The following table describes the parameters in the 'Extinguishing activation criteria' area of the 'Details' tab. You will find information about all other parameters in chapter 'Configuring the 'Zone' [➙...
Extinguishing Configuring an extinguishing control group 16.4 Configuring an extinguishing control group The 'Extinguishing control group' element is a superordinate control element for the flooding zone. The flooding zone is summarized in an 'Extinguishing sector control' element. Creating and configuring the 'Extinguishing control group' The sequence only contains the necessary configuration steps.
Extinguishing Configuring flooding zone control 16.5 Configuring flooding zone control An 'Extinguishing sector control' element contains causes and effects of the extinguishing controls for a flooding zone. Main features and typical Typical event category Event text application Contains causes and ' ----Activation/extinguishing pre- 'Exting.
Page 355
Extinguishing Configuring flooding zone control Typical event category Event text Main features and typical application ' ----Other extinguishing fault' 'PressureSw.timeout' 'Module reset req.' 'Input / output' 'Output fuse fault' 'X-bus fault' 'Configurat. fault' 'Fault aux.function' ' --Earth fault' 'Earth fault ($(POLARITY))' ' --Control test mode' 'Control test mode' 'System information'...
Page 356
Extinguishing Configuring flooding zone control 4. Configure the 'Extinguishing sector control' element in the 'Details' tab. 5. Create the required 'Causes' functions in the 'Causes' zone and configure them. You will find information on creating and configuring 'Causes' functions in chapter 'Causes functions [➙...
Page 357
Extinguishing Configuring flooding zone control Parameters Value Description On/off 'Fault if pressure switch not If the parameter is activated, the system issues a active when timeout fault if the pressure switch is not active after the expires' timeout period has expired. After the timeout period has expired, the extinguishing system switches to the ''Released' phase' state in all cases.
Page 358
Extinguishing Configuring flooding zone control 'Extinguishing sector control' – parameters in the 'Details' tab Parameters Value Description 'Accept commands 'Fire On/off The parameter defines that this control is a fire controls ON/OFF' from control within the meaning of the VdS definition. FBF' When the parameter is activated, all of the control's effects can be switched off with the corresponding...
Extinguishing Configuring flooding zone control 16.5.1 Causes functions Causes for activating or deactivating controls are configured with 'Causes' functions. The causes are assigned to the corresponding inputs on the extinguishing card. A 'Causes' function can be assigned up to eight inputs which trigger the respective 'Causes' function.
Page 360
Extinguishing Configuring flooding zone control 9. Assign the associated input, to which the manual call points are connected, on the extinguishing card to the 'Manual release' function with 'Assign'. This could be a 'Collective input', for example. 10. Highlight the assigned 'Input' element and enter the required customer text in the 'Overview' tab.
Page 361
Extinguishing Configuring flooding zone control Standard 'Causes' functions The table below describes 'Causes' functions, which are created automatically in the 'Causes' zone with the creation of an 'Extinguishing sector control' element. Designation Description 'Automatic release' Assignment of causes for the automatic triggering of extinguishing in the flooding zone.
Page 362
Extinguishing Configuring flooding zone control Pre-configured 'Causes functions of the 'Emergency hold' element type Designation Description 'Emergency hold / 'Emergency hold' function with the following additional function: Automatic release blocked' ● The system blocks the automatic activation of the extinguishing process via fire detectors if no extinguishing process is activated for the flooding zone and the 'Emergency hold' switch is held.
Page 363
Extinguishing Configuring flooding zone control Designation Description 'Block automatic+manual Assignment of causes for which the system switches automatically into the 'Block release' automatic+manual release' operation mode. This operation mode blocks both the automatic activation of extinguishing via fire detectors and the manual activation via manual call points.
Page 364
Extinguishing Configuring flooding zone control Designation Description 'Programmable input' Assignment of causes for a freely selectable state which is then displayed on the extinguishing terminal with an LED. In the corresponding LED element of the extinguishing terminal, a 'Local event' element must be created in the 'Operation tree' with the 'Programmable input activated' template.
Page 365
Extinguishing Configuring flooding zone control 'Causes' functions – parameters in the 'Overview' tab The following parameters only apply to the 'Causes' function 'Automatic release'. Parameters Values Description 'No. of zone requests for EXTINGUISHING PRE-ACTIVATION' 'Requests 'Automatic Input field for number The parameter defines the number of exting.
Page 366
Extinguishing Configuring flooding zone control Example of pre-activation / activation of the flooding zone The parameters 'No. of zone requests for EXTINGUISHING PRE-ACTIVATION' and 'No. of zone requests for EXTINGUISHING RELEASE' determine the conditions that must be met for the flooding zone to transfer to the state ''Pre- activated' phase' or ''Activated' phase'.
Page 367
Extinguishing Configuring flooding zone control 'Causes' functions – parameters in the 'Details' tab The error handling in the 'Details' tab only works for causes which are connected to the extinguishing card directly. The error behavior of causes, which are not connected to the extinguishing card directly, must be configured in a special 'Causes' function, such as 'Fault ->...
Extinguishing Configuring flooding zone control 16.5.2 Effects functions Activations and deactivations of controls are configured with 'Effects' functions. The control effects are assigned to the corresponding outputs on the extinguishing card. An 'Effects' function can be assigned up to eight outputs which trigger the respective 'Effects' function.
Page 369
Extinguishing Configuring flooding zone control 12. Assign the associated output, to which the 'Sounder' is connected, on the extinguishing card to the 'Sounder' function with 'Assign'. This is an 'Output/monitored' element. 13. Highlight the assigned element and enter the required customer text in the 'Overview' tab.
Page 370
Extinguishing Configuring flooding zone control Standard 'Effects' functions The table below describes the 'Effects' functions, which the Engineering Tool creates automatically in the 'Effects' zone with the creation of an 'Extinguishing sector control' element. They are a fundamental part of the configuration for an extinguishing system.
Page 371
Extinguishing Configuring flooding zone control Additional standard 'Effects' functions The table below describes additional standard 'Effects' functions which may be required on a country-specific basis. They can be created manually and deleted again if necessary. Designation Description 'Illuminated warning panel' Function for activating an 'Illuminated warning panel' in the flooding zone.
Page 372
Extinguishing Configuring flooding zone control 'Effects functions of the 'Function' element type The table below describes the 'Effects' functions, which can also be created manually. Designation Description Preset function type: 'Actuator/valve' 'Actuator/valve main/res. Function for triggering the opening of the pneumatic shut-off valves on the main cyl.
Page 373
Extinguishing Configuring flooding zone control Designation Description 'Start valve' Function for switching a valve which must always be switched in a defined, safe state, e.g., open or closed, if extinguishing is triggered. These valves have at Template ID: '5...' least two separate solenoids – one for opening and one for closing. After the loss of the activation state, the valve remains in the last state.
Page 374
Extinguishing Configuring flooding zone control Designation Description Preset function type: 'External equipment' 'Ventilator system' Function for controlling a ventilator system. Template ID: '9...' Activation state: ''Activated' phase' Deactivation state: 'Quiet' 'Activated 'Release Function for controlling an external system which is to be activated if the flooding actuator' until reset' zone is in the phases between the ''Release actuator' phase' and 'Quiet' states.
Page 375
Extinguishing Configuring flooding zone control Designation Description 'Activated while Fire controls OFF' Template ID: '27...' 'Activated while actuator OFF' Template ID: '33...' 'Fault' Template ID: '28...' 'Emergency hold indication' Template ID: '30...' 'Emergency abort indication' Template ID: '31...' 375 | 412 A6V10210424_j_en_-- Building Technologies Fire Safety...
Page 376
Extinguishing Configuring flooding zone control 'Effects' functions – parameters in the 'Overview' tab The 'Effects' functions have defined parameters. The following functions are exceptions: ● 'Sounder' ● 'Illuminated warning panel' You will find information about the parameters of both functions in a separate section further down in this chapter.
Page 377
Extinguishing Configuring flooding zone control Parameters Values Description 'Activation delay' Input field for time period Defines the period of time for which the [Hr:min:sec] activation of the 'Effects' function is delayed. The max. delay time is 30 minutes. 'Deactivation state' 'Quiet' Defines the state in which the extinguishing system must be for the...
Page 378
Extinguishing Configuring flooding zone control 'Effects' functions – 'Sounder' parameters in the 'Overview' tab The table below describes the parameters in the 'Overview' tab for 'Effects' functions of the 'Sounder' type. Parameters Values Description Parameters for the relevant 'Inactive: Off / active: Intermittent, Determines the signal characteristics of the system states: slow (1.25s/0.75s)'...
Extinguishing Configuring an extinguishing reporting zone 'Effects' functions – parameters in the 'Details' tab The error handling in the 'Details' tab only works for effects which are connected to the extinguishing card directly. The error behavior of effects, which are not connected to the extinguishing card directly, must be configured in a special 'Causes' function, such as 'Fault ->...
Page 380
Extinguishing Configuring an extinguishing reporting zone 'Extinguishing reporting zone' – 'Reporting 'pre-alarm'' – properties of the template Main features and typical application Typical event category Event text ● Monitors the trigger signal for ' ----Pre-ALARM, extinguishing 'Exting. released' extinguishing in the relevant released' flooding zone NOTICE! This event has an...
Page 381
Extinguishing Configuring an extinguishing reporting zone 3. Assign a 'Extinguishing sector control' element to the 'Extinguishing reporting zone' element with 'Assign'. You will find information on creating and configuring an 'Extinguishing sector control' element in chapter 'Configuring flooding zone control [➙ 354]'. 'Extinguishing reporting zone' –...
Extinguishing Configuring the extinguishing terminal 16.7 Configuring the extinguishing terminal The 'Extinguishing terminal' element contains all configurable indication elements and operating elements of an extinguishing terminal. Creating and configuring an 'Extinguishing terminal' element The sequence only contains the necessary configuration steps. You will find information about the elements that can be assigned or created, as well as the parameters, in separate sections further down in this chapter.
Page 383
Extinguishing Configuring the extinguishing terminal 6. Assign one or several 'Local event' elements to the required LED lights in the 'LED' zone with 'New element'. 7. Configure the assigned 'Local event' elements. You will find the allocation of the hardware ID for the physical LEDs on the extinguishing terminal in a separate section further down in this chapter.
Page 384
Extinguishing Configuring the extinguishing terminal 'Extinguishing terminal' – parameters in the 'Overview' tab The table below describes the parameters in the 'Overview' tab for a 'Extinguishing terminal' element: Parameters Values Description 'Logout timeout' Input field for time period Determines how long after the last press of the button the operating terminal reverts to [Hr:min:sec] the standard access level.
Extinguishing Configuring the extinguishing terminal 16.7.1 Buttons and LED elements Physical assignment of 'LED' and 'Keys' elements on the extinguishing terminal With the hardware ID, an 'LED' or a 'Keys' element can be assigned to the physical components on the extinguishing terminal. The relevant hardware ID can be found directly on the element in the 'Operation tree' and in the 'Overview' tab of the element in question.
Page 386
Extinguishing Configuring the extinguishing terminal The following graphic and tables below make it possible to assign the 'LED' elements and 'Keys' elements to the physical LEDs and buttons: Figure 164: Extinguishing terminal – LED and button assignment The described LEDs and buttons on the extinguishing terminal are visible in the configuration program and can therefore be freely configured.
Page 387
Extinguishing Configuring the extinguishing terminal 'HW ID LED' Comment Pre-configured for indicating an active 'Emergency hold' function. Can be adjusted if necessary. Freely configurable Pre-configured for indicating deactivated external equipment: 'External equipment OFF' Can be adjusted if necessary. Freely configurable Table 23: Configurable LEDs 'HW ID KEY' Physical button...
Extinguishing Configuring the extinguishing terminal 16.7.2 'Action' elements 'Extinguishing terminal' – 'Keys' – 'Action' elements The table below describes the configurable effects when the assigned button on the extinguishing terminal is pressed. An 'Action' element represents a cause in each case. Designation Description 'Reset warning panel'...
Extinguishing Configuring the extinguishing terminal 16.7.3 'Local event' elements 'Extinguishing terminal' – 'LED' – 'Local event' elements The table below describes the configurable causes which light up the assigned LED on the extinguishing terminal. An 'Local event' element represents a cause in each case.
Page 390
Extinguishing Configuring the extinguishing terminal Designation Description 'Peripheral device One of the devices which does not directly belong to extinguishing is activated. activated' These may, for example, be devices for monitoring the valve position or the position of a mechanical shut-off device. The triggering signal of the relevant device must be wired to an input on the extinguishing card.
Extinguishing Configuring the forwarding of the extinguishing released state 'Local event' elements – parameters in the 'Overview' tab The table below describes the parameters in the 'Overview' tab for a 'Local event' element: Parameters Value Description 'Colour' 'Red' Lighting color of the LED when activated 'Yellow' 'Green'...
Page 392
Extinguishing Configuring the forwarding of the extinguishing released state Configuring the forwarding of the 'Released' extinguishing state The flooding zone for which the forwarding of the 'Released' state is to be configured has already been configured. You will find information on configuring the flooding zone in chapter 'Configuring flooding zone control [➙...
Page 393
Extinguishing Configuring the forwarding of the extinguishing released state 7. Use 'Assign' to assign the relevant 'Extinguishing reporting zone' element of the flooding zone from the detection tree to the 'Causes' element. To do this, select the ' --Pre-ALARM, extinguishing' event category on the left in the 'Assign' dialog and then select the corresponding 'Extinguishing reporting zone' element of the flooding zone on the left in the detection tree.
Page 394
Extinguishing Configuring the forwarding of the extinguishing released state 15. Use 'Assign' to assign the 'Fire control' element no. 1 to the 'Causes' element as the cause. To do this, select the 'All isolations' event category on the left in the 'Assign' dialog and then select the 'Fire control' element no.
Page 395
Extinguishing Configuring the forwarding of the extinguishing released state 18. Use 'Assign' to assign the 'Fire control' element no. 2 to the 'Auxiliary function off' element as the cause. To do this, select the 'All activations' event category on the left in the 'Assign' dialog and then select the 'Fire control' element no. 2 on the left in the control tree.
Extinguishing Configuring global extinguishing settings 16.9 Configuring global extinguishing settings The 'Operation' task card can be used to adjust global settings for extinguishing under the 'Global extinguishing configuration' element. 'Global extinguishing configuration' – parameters in the 'Overview' Parameters Values Description 'Pressure switch activation On/off The parameter determines whether the actuator on the extinguishing...
Change the preset PIN. ● Create an 8-figure PIN according to the IT security requirements from Siemens; see chapter 'PIN guidelines [➙ 23]'. The defined PIN is valid for the internal extinguishing terminal as well as all additional configured remote extinguishing terminals.
Page 398
Extinguishing Configuring global extinguishing settings 4. In the input fields 'PIN digit 1' to 'PIN digit 8', enter one number between 1 and Information: The digits 5 to 8 can be deactivated individually by removing the tick next to 'Enabled'. But do not miss out any digits. Information: The preset PIN is: 8x '1'.
Glossary Glossary Alarm device Element in the fire detection system for acoustic and/or visual alarming, e.g. alarm sounder, beacon. Alarm indicator Visual display to signal an alarm or pre-alarm. Alarm organization Covers all measures which are used for alarming, rescue, preventing a fire from spreading, fire fighting, and orientation in the event of a fire.
Page 400
Glossary Cause group Configuration element that summarizes causes that trigger control in a particular case. CDV stands for 'Country Data Variant'. A CDV file limits the value range for a specific country; these limited values can be used for a meta datum for 'additional information' elements. When entering the meta datum, the configuration tool displays a drop-down menu that lists the possible values.
Page 401
Glossary External alarm indicator Optical element for displaying the fire location, which is at some distance from the detector. It is normally mounted in the room at the point where the corresponding detector is accessible. Extinguishing control Control which controls a connected extinguishing system and evaluates and displays its states. False alarm Alarm not triggered by a danger.
Page 402
Glossary Line card Card for connecting peripheral devices. The card can be a plug-in card or it can be integrated into the periphery board. Local alarming Local alarming equipment (e.g. acoustic or optical) is actuated in order to call up intervention personnel and to alert people of a possible fire hazard.
Page 403
Ethernet sub-net (FCnet/C-WEB/LAN) via the Ethernet switch (modular) FN2012-A1. The abbreviation for remote transmission. SAFEDLINK Physical network of an FS20 / FS720 fire detection system with the network module (SAFEDLINK) and the network cable. SAFEDLINK station Participants in the SAFEDLINK sub-net with local connection for the PC.
Page 404
Glossary Stub Detector line which is only connected to the fire control panel on one side. In the event of an open line or short-circuit, it may no longer be possible for all fire detectors to communicate with the fire control panel. Technical message Events (e.g., from third-party systems) evaluated via sensors or contacts which are forwarded to the fire control panel.
Page 407
Index / Editing ............70 Extinguishing reporting zone ......379 Move .............. 74 Configuring ........... 380 Paste .............. 73 Extinguishing standard interface SST....242 Re-address ............. 74 Extinguishing terminal Replace ............70 Configuring ........... 382 Element in the structure tree PIN configuration ..........
Page 408
Index / Fire dampers I/O card (horn/monitored) FCI2009A1 ....135 Control ............231 I/O card (programmable) FCI2008-A1....135 Monitoring............. 233 I/O card (remote transmission) FCI2007-A1 ..135 Fire door ............185 IC 117 Firmware Import File name............35 CSV..............93 Update station ..........
Page 409
Index / Log file ............109 Paste Engineering tool ........43, 43 Element ............73 Logo .............. 94 Loop ............326 Connect to station ......... 104 Loop sounder ..........248 Disconnecting from station ......104 Loop sounder/flashlight ........248 Peripheral devices Updating the firmware ........
Page 410
Index / Sounder interbase DBS721 ...... 125, 125 Re-address Sounder line Element ............74 Via FDCIO223 ..........249 Reading device Source language ..........11 Data Matrix code..........39 Sprinkler control ..........155 Reading device for Data Matrix code ....83 Sprinkler zone ..........
Page 411
Index / UDP port Walk test ............257 BACnet ............331 Voice sounder ..........257 UGA ............303 Window separating lines........51 Universal evac. control ........192 Universal sounder evac. control XC10 ............157 Configuring ........... 193 XML export ............. 88 Updating the firmware Peripheral devices ........