FS720

Fire detection system

Release Notes IP7.0

Development Service Release 2

Firmware packages

A6V11513842_c_en_-- Building Technologies

Control Products and Systems
2

Building Technologies A6V11513842_c_en_--

Fire Safety 02.2020
 Legal notice
Technical specifications and availability subject to change without notice.
© 2020 Copyright by Siemens Switzerland Ltd

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

utilization of its contents and communication thereof to others without express
authorization are prohibited. Offenders will be held liable for payment of damages.
All rights created by patent grant or registration of a utility model or design patent
are reserved.

Issued by:
Siemens Switzerland Ltd.
Building Technologies Division
International Headquarters
Theilerstrasse 1a
CH-6300 Zug
Tel. +41 58 724-2424
www.siemens.com/buildingtechnologies

Edition: 14.02.2020
Document ID: A6V11513842_c_en_--

A6V11513842_c_en_-- Building Technologies

Control Products and Systems
 1 About this document ...........................................................................9
1.1 Purpose of the document .......................................................................9
1.2 Modification index ..................................................................................9
1.3 Related documents ................................................................................9

2 Introduction........................................................................................ 10
2.1 FS720 market package IP7.0 ............................................................... 10
2.2 System description .............................................................................. 10
2.1 Compatibility IP7.0 Delivery release/Development Service
Release 1 ↔ IP7.0 Development Service Release 2 ............................ 10

3 Versions and compatibility................................................................ 11

3.1 FXS7211 Firmware package ................................................................ 11
3.1.1 Introduction.......................................................................................... 11
3.1.2 Firmware package versions ................................................................. 11
3.1.3 Compatibility of peripheral devices ....................................................... 12
3.1.3.1 Compatibility of FT2010 / FT2011 (Floor Repeater Terminal / Display) . 12
3.2 FXS2007 Periphery update package .................................................... 13
3.2.1 Introduction.......................................................................................... 13
3.2.2 Periphery update package versions ..................................................... 13

4 Commissioning rules and restrictions ............................................. 14

4.1 Introduction.......................................................................................... 14
4.2 Commissioning rules............................................................................ 14

5 FXS7211 Firmware package .............................................................. 16

5.1 Introduction.......................................................................................... 16
5.2 Removed bugs & changes, FW version 61.0.66 ® 70.28.32 ................ 16
5.2.1 Introduction.......................................................................................... 16
5.2.2 No resound of base sounder with ‘Direct activation’ set to ‘By the
DETECTOR in the same base’............................................................. 16
5.2.3 Toggling onboard outputs when restarting the station........................... 16
5.2.4 ‘Simplified deletion of device’ does not work correctly in all cases ........ 17
5.2.5 Outputs ‘Acknowledge’/’Reset’ of ‘Sub-system zone’ not activated
on general purpose I/Os....................................................................... 17
5.2.6 Unexpected alarm during detector test with FDUD292 function ‘Test
alarm total’ ........................................................................................... 17
5.2.7 Incorrect licence handling by FC723 .................................................... 18
5.2.8 Line alarm when replacing an interactive detector ................................ 18
5.2.9 Station reboot when auto-configuring a station/line with inputs but
no ‘Technical zone’ template available in BDV ..................................... 18
5.2.10 Configuration of specific days for an ‘UNMANNED switching time’
in an area does not work ...................................................................... 19
5.2.11 Outputs of ‘Fire damper control’ and ‘Smoke extraction control’ do
not work with I/Os on periphery boards ................................................ 19
5.2.12 ‘Silence buzzer’ not possible via BACnet.............................................. 20
5.2.13 Station reboot after a very high number of connections/disconnections
of a Cerberus Mobile client .................................................................. 20
5.2.14 ‘Fault delay’ on detector lines ............................................................... 20
5.2.15 Short-time faults ‘Device missing’ on a SynoLOOP detector line........... 21
5.2.16 ‘Always manned’/’Always unmanned’ not indicated correctly via
BACnet ................................................................................................ 21
5.2.17 Frozen PMI display .............................................................................. 21
5.2.18 Incorrect no. of tested/untested devices in ‘Peripherals test report’ ....... 21
5.2.19 Peripheral test data is lost when downloading configuration ................. 22
5.2.20 Fault events from interactive lines during start-up of a station ............... 22
5.2.21 Fault events from interactive lines after migration from FC700.............. 22
5.2.22 Station crashes due to additional devices in an isolated ‘External
sounder control’ ................................................................................... 23

Building Technologies A6V11513842_c_en_--

Fire Safety 02.2020
 5.2.23 Manual zone with FDCIO223: re-alarm instead of ‘Glass broken’ ......... 23
5.2.24 Incorrect processing of faults on a C-NET detector loop ....................... 23
5.2.25 Fire control without effects: unexpected ‘Control test mode’ after
reboot .................................................................................................. 24
5.2.26 Unexpected faults upon simultaneous activation of more than
20 outputs ........................................................................................... 24
5.2.27 Configured SAFEDLINK connection disabled if no HW connected........ 24
5.3 Removed bugs & changes, FW version 70.28.32 ® 70.28.38 .............. 25
5.3.1 Introduction.......................................................................................... 25
5.3.2 Unsecure firmware update mode cannot be activated on all PMI
variants................................................................................................ 25
5.3.3 Additional information elements are lost ............................................... 25
5.4 Removed bugs & changes, FW version 70.28.38 ® 70.28.58 .............. 26
5.4.1 Introduction.......................................................................................... 26
5.4.2 No silence/unsilence function on Management Station for alarm
devices activated by a Technical Zone ................................................. 26
5.4.3 Interactive detector line with many radio devices does not start up
after migration from FC700 .................................................................. 26
5.4.4 Wrong event reported in case of permanent Cerberus Mobile access... 26
5.4.5 Station reboots after activation of a ‘Prioritized voice evac control’ ....... 27
5.4.6 ‘Position undefined’ of damper output not recognized upon start-up ..... 27
5.4.7 Alarm of a zone with 2 detector dependency cannot be reset on
Management station ............................................................................ 28
5.4.8 Function ‘Freeze selected outputs’ does not work with damper outputs 28
5.4.9 No events are sent to a BACnet client .................................................. 28
5.4.10 Hidden ‘Activation’ events of a ‘Fire control’ still visible on a
Management station ............................................................................ 29
5.4.11 ‘C-NET line card’ reports fault ‘Hardware missing’ ................................ 29
5.4.12 Station reboots when executing function ‘Show intervention text’ via
function key ......................................................................................... 29
5.4.13 Function ‘Freeze selected outputs’ does not work correctly in some
cases................................................................................................... 30
5.4.14 Sporadic faults from migrated sounder lines connected to an
‘I/O card (horn/monitored, FCI2009)’ .................................................... 30
5.4.15 FRD/FRT (FT2010/FT2011): start-up problems .................................... 30
5.4.16 Problems if a new generation alarm device (optical, acoustic, voice)
is removed while its settings are written ............................................... 31
5.4.17 ‘Minimal duration of activation’ of RT channels does not work correctly 31
5.5 Restrictions and known bugs, FW version 70.28.58 ............................. 32
5.5.1 Sounder activation ............................................................................... 32
5.5.2 Message ‘Station restarted’ in control panels with large configurations . 32
5.5.3 Only 1 message per event category and element on FAT
[VdS countries only] ............................................................................. 33
5.5.4 Alarms in zones with ‘Two-zone dependency’ ...................................... 33
5.5.5 FDCIO222/FDCIO224 short-circuit monitoring ..................................... 33
5.5.6 Floor Repeater Terminal FT2010 / Floor Repeater Display FT2011 ...... 34
5.5.7 Evac NL master/slave on different physical interfaces [NL only] ........... 34
5.5.8 Re-alarm of ‘Manual zone’ with interactive call point takes too long ...... 35
5.5.9 Incorrect event message ‘New devices found’ on interactive detector
line ...................................................................................................... 35
5.5.10 No cause input activation by an FDCIO223 input ................................. 35
5.5.11 Fault not removed when C-NET line is switched off .............................. 36
5.5.12 FDUD292 function ‘Test alarm total’ not possible when zone or
detector is switched off ........................................................................ 36
5.5.13 Abort of ‘Upload site’/‘Download site’, ‘Upload event memory’ or
‘Upload site log files’ with no evident reason ........................................ 36
5.5.14 No event ‘Incompatible FW’ for additional CPUs .................................. 36
5.5.15 SynoLOOP: fault remains until line is restarted after replacement
of a DC1136 ........................................................................................ 37
5.5.16 Sounder control cannot be silenced via button ‘Alarm device’ ............... 37
6

Building Technologies A6V11513842_c_en_--

Fire Safety 02.2020
 5.5.17 Station reboot when auto-configuring a line with more than
25 FDCIO222 and/or FDCIO224 .......................................................... 37
5.5.18 Evaluation of ‘Threshold’ function of controls not as expected .............. 38
5.5.19 Incorrect processing of ‘Activation delay’ in evac controls ..................... 40
5.5.20 Alarm disappears on connected Management station........................... 40

6 Miscellaneous .................................................................................... 41
6.1 Support ................................................................................................ 41

Building Technologies A6V11513842_c_en_--

Fire Safety 02.2020
 About this document

1 About this document

1.1 Purpose of the document
This document contains the technical Release Notes for the Firmware packages of
market package IP7.0 Development Service Release 2 of the FS720 fire detection
system. It mainly contains information about the international variant (“..XS_en..”)
and serves as a template for country-specific Release Notes which are prepared
by the Localization Managers of the countries where IP7.0 is used.
The document gives an overview of the release package and contains important
information about current limitations, bugs and work-arounds of the Firmware
packages. Furthermore, the removed bugs/restrictions in comparison to the latest
IP6.0 Release version and the IP7.0 Release versions are listed.
Information on the Engineering tool set and the Base Data Variants are described
in separate documents → see related documents [7] and [8].
The document does not describe the functions of the system in detail. Please refer
to the technical documentation for further information.

1.2 Modification index

Version Date Brief description

A6V11513842_c_en 14.02.2020 IP7.0, Development Service Release 2
A6V11513842_b_en 21.02.2019 IP7.0, Development Service Release 1
A6V11513842_a_en 11.12.2018 IP7.0, Delivery Release version
Tab. 1 Modification index

1.3 Related documents

Reference Document no. Content

[1] A6V10210416 FS720, Commissioning, maintenance, trouble-
shooting
[2] A6V10210355 FS720, Description
[3] A6V10210424 FS720, Configuration
[4] A6V10210362 FS720, Planning
[5] 009310 FT2010, Floor Repeater Terminal, Operation
[6] A6V10260976 FS720, Site conversion
[7] A6V11513850 Release Notes IP7.0, Engineering tool set
[8] A6V10874137 Release Notes all IPs, Base Data Variants
Tab. 2 Related documents

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
Introduction

2 Introduction

2.1 FS720 market package IP7.0

IP7.0 is the sixth market package of the fire detection system FS720.

2.2 System description

For an FS720 system overview and detailed descriptions of components and func-
tions, see document [2], A6V10210355 ‘FS720, Fire detection system, Description’.

2.1 Compatibility IP7.0 Delivery release/Development Service

Release 1 ↔ IP7.0 Development Service Release 2
The Base Data Variant versions of IP7.0 Development Service Release 2 are NOT
compatible with the Firmware package versions of IP7.0 Delivery Release and
Development Service Release 1 and vice versa.

DO NOT use incompatible combinations of Base Data Variant and Firmware

package! If you are updating an existing site to Development Service Release
COMPATIBILITY
2, convert the site configuration to the Development Service Release 2 Base
Data Variant version.

Base Data Variant Firmware package Compatible

version version
F-FXS2004-XS_en_2- F-FXS7211-XE_xx_x-
70.28.32
(Delivery Release)
ü
70.28.9_xx
70.28.38
(Delivery Release, Development
(Development Service Release 1)
ü
Service Release 1)
70.28.58
r
(Development Service Release 2)
70.28.32
r
(Delivery Release)
70.28.12_xx 70.28.38
r
(Development Service Release 2) (Development Service Release 1)
70.28.58
(Development Service Release 2)
ü
Tab. 3 IP7.0 compatibility Base Data Variants ↔ Firmware package versions

10

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 Versions and compatibility

3 Versions and compatibility

3.1 FXS7211 Firmware package

3.1.1 Introduction

The FXS7211 Firmware package contains a set of specific firmware components

for different controllers of the system and some peripheral devices (Floor Repeater
Terminal, Floor Repeater Display, ..). In order to guarantee consistency, the set of
firmware components is always released as one complete Firmware package.
Updates of the Firmware package can be made available independent from a
release of the Engineering tool set FX7230. An update package can be imported
into the Engineering tool set. See document [7] for further information.
The Firmware package is NOT country-specific; all countries use the same version.

3.1.2 Firmware package versions

Following FXS7211 Firmware packages have been officially released for delivery:
Firmware Update of Use in new Compatible with Remarks / major changes
package version existing sites sites/ version.. 3) compared to previous
F-FXS7211-XE_xx_x- to.. 1) stations 2)
F-FXS7211-XE_xx_x- Version
70.28.32_01 - - - IP7.0 Delivery Release ver-
sion; major changes see 5.2
70.28.38_01 - - 70.28.32_01 IP7.0 Development Service
Release 1; major changes
see 5.3
70.28.58_01 ‘Mandatory’ if integrated Mandatory 70.28.32_01 IP7.0 Development Service
Extinguishing is used, 70.28.38_01 Release 2; major changes
otherwise ‘Recommended’ see 5.4
Tab. 4 Released Firmware package versions

1)
Not allowed: an update of an existing site to this version is not allowed
Mandatory: all existing sites must be updated to this version or greater!
Recommended: all existing sites for which the bug fixes/changes compared to the previous version are relevant (see
respective chapter for a list of changes) must be updated to this version or greater!
Optional: the listed Firmware package only contains minor changes. For an update, see instructions in document [7].
2)
Not allowed: this version must not be used in new sites
Mandatory: if all required system components, e.g. also the Danger Management System, are available
with a compatible version, this Firmware package must be used in new IP7.0 sites and new stations which are
added to an existing IP7.0 site (if the version is not compatible with the version that runs on the already existing
stations (see 3)), the complete site must be updated to the new version - or, if the update of existing sites is not
mandatory (see 1)) then the new stations can be operated with the same FW version as the already existing ones).
Recommended: this Firmware package version must be used in new IP7.0 sites or new stations which are
added to an existing IP7.0 site if the bug fixes/changes compared to the previous version are relevant, i.e. the
concerned components/functions are used in the country (see respective chapter for a list of changes).
3)
Firmware package versions listed in this column are compatible with the version in the first column. These versions may
be used within the same network, i.e. the stations within the same network may run with any one of these versions.

When updating a site/station to a new FW package version, always ALL controllers (Main CPU and Additional CPUs) must
be updated!

11

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
Versions and compatibility

3.1.3 Compatibility of peripheral devices

The FW package FXS7211 always contains FW versions for the peripheral devices
which are compatible with the FW versions for the main CPU and the additional
CPUs contained in the same FW package. Normally, all peripheral devices that are
used in a site that runs with this FW package version shall be updated to device
FW versions of this FW package. However, it might be that the FW version of such
a peripheral device is already newer, e.g. because the FW of the peripheral device
has been updated and is already loaded in the production process but no complete
FW package FXS7211 has been released yet. In this case it is normally not rec-
ommended to downgrade to the older version. If this is required, it will specifically
be documented.
Furthermore, the FW versions of peripheral devices might not be compatible with
all device versions (HW).
The following chapters list the FW versions of the peripheral devices contained in
specific FW packages FXS7211 and the required compatibility information.
Please see also chapter 5 for information about functional restrictions depending
on the Firmware package.

3.1.3.1 Compatibility of FT2010 / FT2011 (Floor Repeater Terminal / Display)

FT2010/ Included in Compatible with Compatible with Remarks

FT2011 FW package FW package printed circuit
FW version version version board (PCB)
version
21 24.5.xx_00 24.5.xx_00 >=8 Devices will be delivered with PCB version
32.11.xx_00 32.11.xx_00 9 or higher and pre-loaded FW version
25 - 24.5.xx_00 >=8 V25 or higher which are backward compat-
32.11.xx_00 ible with old Cerberus market package
26 41.6.6x_00 24.5.xx_00 >=8 versions.
50.21_xx_00 32.11.xx_00 See also Maintenance Information
27 61.0.54_00 41.6.xx_00 CPS_FS_12_018_V01_MI_FT201x
61.0.66_00 50.21.xx_00
70.28.32_01 61.0.xx_00
70.28.38_01 70.28.32_01
70.28.58_01 70.28.38_01
70.28.58_01
Tab. 5 Compatibility FT2010/2011

If you are using a HW version or FW version which is not listed in the table above, please contact the
hotline for further information.

How to find FW version and PCB version of an FT2010/2011

On the FT2010/2011 open the ‘Service menu’ and execute the function ‘Device
information’ ® PCB version (“HW”) and FW version (“SW”) will be displayed (e.g.
‘HW, SW 8, 17’ = PCB version 8, FW version 17).
See document [5] for further information.

12

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 Versions and compatibility

3.2 FXS2007 Periphery update package

3.2.1 Introduction

The FXS2007 Periphery update package contains a set of specific firmware com-
ponents for periphery service devices like the line tester FDUL221 and the MCL-
USB Adapter FDUZ221. The FXS2007 component is used by the Engineering tool
set FX7230. Updates of the Periphery update package can be made available in-
dependent from a release of the Engineering tool set FX7230. An update package
can be imported into the FW Update tool and the Engineering tool set. See docu-
ment [7] for further information.
The Periphery update package is country-specific, i.e. it can be translated into the
country language.

3.2.2 Periphery update package versions

Following FXS2007 Periphery update packages have been officially released for
delivery:

Firmware package ver- Update 1) Remarks / major changes compared to previous

sion version
F-FXS2007-XX_en_x-…
1.13.0_00 - IP7.0 Delivery Release version;
Changes:
- FDUD29x: new version V3.2.4
- FDUL221: new version V4.2.3
1.14.0_00 Recommended IP7.0 Development Service Release 2 version;
Changes:
- FDUD29x: new version V3.2.8

Tab. 6 Released Periphery update package versions

1)
If an update to a listed Periphery update package version is marked as mandatory, all respective
service devices must be updated to this version or greater!
Periphery update packages marked as recommended or optional are recommended to be used
but are not mandatory.

13

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
Commissioning rules and restrictions

4 Commissioning rules and restrictions

4.1 Introduction
This chapter lists rules as well as known restrictions/bugs concerning the
commissioning process. For tool specific restrictions/known bugs and for Help
documentation set related restrictions/known bugs see document [7].

4.2 Commissioning rules

Please refer to the commissioning manual (see doc. [1]) for information about the
commissioning procedures. In the table below, some important rules are repeated.
Rule Reason/Comment
Before you start the commissioning of a site, The version that had been installed during the manu-
always update all stations to the most current facturing process might be older than the most current
Firmware package. version.
It is mandatory to check the installation with Only valid topologies can be processed by the system
the line tester FDUL221 and correct any in- and diagnosis and removal of installation errors are to
stallation error before the commissioning of be done with the line tester. The FC720 panels do not
an C-NET line is started. provide specific functions for this.
Do not manipulate anything on an C-NET line These messages are displayed when the line is get-
as long as one of the messages “Line starting ting ready and this process must not be interrupted by
up” or “Line busy, pl. wait” is displayed. the user.
DO NEVER To be able to keep track of the changes on the detec-
- change the installation topology tion line the system must either use the installation
AND topology or the IDs of the devices as a reference and
- exchange existing devices (= change IDs) therefore one of the two must be kept unchanged.
within the same step of the workflow! Otherwise the commissioning information of the exist-
ing devices might be lost and the complete line or a
One step of the workflow means: part of it must be re-commissioned.
- manipulation/changes on the line, read-in
- upload of the changes to the tool
- assignments/changes in the tool
- download to the station
Always switch off a detector line (powerless) The installation topology should only be changed in
before working on the installation ® installa- the powerless state.
tion changes, removal of line faults (short In case of temporary/short-term line faults (short-
circuit, open line), etc. circuit) in powered state, execute the line command
‘Restart line’ to restore the full loop functionality (open
line separators are closed etc.).
DO NEVER connect or disconnect any plug to Connecting/disconnecting plugs in powered state may
a HW module in powered state! Always dis- damage the HW.
connect all power supplies (mains, batteries,
3rd power supply/9V battery) first and make
sure that the HW is in powerless state.

14

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 Commissioning rules and restrictions

Rule Reason/Comment
Always switch off the detector line before
replacing one or several devices on C-NET.
Proceed as follows:
· Switch off the respective detector line
using the operating command ‘Detector
line OFF’
· Replace the device(s)
· Switch the detector line on using the op-
erating command ‘Detector line ON’
Execute the function ‘Accept replaced devic-
es’ on the respective detector line
Make sure that no new or replaced manual An active manual call point which is not part of the
call point is active when you execute the configuration yet (new or replaced) leads to a line
function ‘Accept replaced devices’ or ‘Device alarm when active in these cases.
replace mode OFF’
Tab. 7 Important commissioning rules

15

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5 FXS7211 Firmware package

5.1 Introduction
This chapter lists specific restrictions and known bugs of the current Firmware
package version (see 3.1.2) as well as removed bugs compared to older versions.
For commissioning rules and restrictions see chapter 4, for tool specific restrictions
and known bugs and for Help documentation set related restrictions and known
bugs see document [7].

5.2 Removed bugs & changes, FW version 61.0.66 ® 70.28.32

5.2.1 Introduction

This chapter describes which bugs/restrictions have been removed in the IP7.0
Delivery Release version compared to the latest IP6.0 version.

5.2.2 No resound of base sounder with ‘Direct activation’ set to ‘By the DETECTOR
in the same base’
[BTQ00068395]

Description
In the following case a base sounder cannot be resounded via the button ‘Alarm
device’ on the operating terminal even though the alarm event is still present:
– Configuration of the property ‘Direct activation of base sounder’ of a detector:
‘By the DETECTOR in the same base’
– This detector reports a danger level 3
è An alarm is reported by the assigned zone and the base sounder of the detec-
tor is activated by the direct activation function
– As long as the danger level 3 and the alarm event are present, the base sounder
can be silenced and resounded via the button ‘Alarm device’ on the operating
terminal
– If the danger level changes to 0 while the base sounder is active and then the
base sounder is silenced via button ‘Alarm device’, a resound is not possible
even though the alarm event of the zone is still present

Status
The bug has been fixed.

5.2.3 Toggling onboard outputs when restarting the station

[BTQ00189088]

Description
Outputs of the ‘Onboard I/Os (FCI2002)’, ‘Onboard I/Os (FCI2004)’ or or ‘Onboard
I/Os (FCI2010)’ configured with ‘Output mode’ ‘Inactive: On / active: Off’ toggle
between ‘on’ and ‘off’ for a short time when the station is restarted.

Status
A remark has been added to the technical documentation that outputs which are
configured as described above are not EN54 relevant and not fail-safe.

16

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.2.4 ‘Simplified deletion of device’ does not work correctly in all cases
[BTQ00120703]

Description
The new feature ‘simplified deletion of device’ does not work correctly with
stationary devices.
The new feature allows executing the command ‘Remove/delete device’ directly via
the message ‘Device missing’ which is displayed once the respective device has
been removed from the detector line.
In case of a stationary device, the element is deleted from the hardware tree of the
configuration but the message ‘Device missing’ is still displayed.
With non-stationary devices, also the message ‘Device missing’ is removed as ex-
pected.

Work-around/measure
Restart the station or upload the configuration to the Engineering tool and down-
load it again to the station (which is done in most cases anyway because the logi-
cal configuration of the removed device needs to be deleted in the configuration via
Engineering tool).

Status
The bug has been fixed.

5.2.5 Outputs ‘Acknowledge’/’Reset’ of ‘Sub-system zone’ not activated on general

purpose I/Os
[BTQ00245763]

Description
If the outputs ‘Acknowledge’ and ‘Reset’ of a ‘Sub-system zone’ are assigned to
general purpose I/Os of the ‘Onboard I/Os (FCI2002)’, ‘Onboard I/Os (FCI2004)’,
‘Onboard I/Os (FCI2010)’, ‘I/O card (progr., FCI2008)’ or ‘I/O card (remote transm.,
FCI2007)’, they will not be activated when on the FS720 ‘Acknowledge’ or ‘Reset’
is executed.

Status
The bug has been fixed.

5.2.6 Unexpected alarm during detector test with FDUD292 function ‘Test alarm
total’
[BTQ00265381]

Description
In case that the FDUD292 function ‘Test alarm total’ is executed twice on the same
detector with a delay of 60..65s between the two executions, the second execution
of the function leads to a normal fire alarm instead of a test alarm.

Work-around/measure
Wait at least 2 minutes before executing the function ‘Test alarm total’ a second
time.

Status
A delay has been added in order to prevent this situation.

17

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.2.7 Incorrect licence handling by FC723

[BTQ00298593]

Description
The licence handling of the station type FC723 is incorrect. Due to this, a
connection from a Cerberus Mobile, a 3rd party BACnet device or Cerberus-
Remote to such a station type is not possible even though the required licence key
is installed.

Work-around:
Use another station type in the same network for the connection (then access to
the respective FC723 is still possible).

Status
The bug has been fixed.

5.2.8 Line alarm when replacing an interactive detector

[BTQ00279516]

Description
Under certain circumstances a collective line alarm is triggered when an interactive
detector is replaced, even though the respective zone/channel is in detector test
mode.

Status
The bug has been fixed.

5.2.9 Station reboot when auto-configuring a station/line with inputs but no

‘Technical zone’ template available in BDV
[BTQ00289645]

Description
In case there are devices with inputs on a C-NET line, ‘Technical zones’ shall be
created, and the inputs assigned to these zones when the station/line is auto-
configured. If no template of the ‘Technical zone’ is available in the Base Data
Variant, the auto-configuration shall create nothing for such inputs.
Due to a bug, the station reboots when the auto-configuration is executed on a line
with inputs and no template of the ‘Technical zone’ is available in the Base Data
Variant.

Status
The bug has been fixed.

18

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.2.10 Configuration of specific days for an ‘UNMANNED switching time’ in an area

does not work
[BTQ00272647]

Description
Even though for an ‘UNMANNED switching time’ in an area element only specific
days of the week are configured, the switching is done every day.
Example:

Status
The bug has been fixed.

5.2.11 Outputs of ‘Fire damper control’ and ‘Smoke extraction control’ do not work
with I/Os on periphery boards
[BTQ00290750]

Description
I/Os of a ‘Periphery board (2-loop)’ FCI2002, a ‘Periphery board (4-loop)’ FCI2004
and a ‘Periphery board (1-loop)’ FCI2010 cannot be used as effects of a ‘Fire
damper control’ or a ‘Smoke extraction control’. The assignment of such I/Os is
possible but they do not work.

Status
The bug has been fixed.

19

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.2.12 ‘Silence buzzer’ not possible via BACnet

[BTQ00293462]

Description
Due to a bug, the command ‘Silence buzzer’ does not work from a device which is
connected via BACnet.

Status
The bug has been fixed.

5.2.13 Station reboot after a very high number of connections/disconnections of a

Cerberus Mobile client
[BTQ00294323]

Description
In case of a very high number of connections/disconnections of a Cerberus Mobile
client with a station, it can happen that the station reboots.

Status
The bug has been fixed.

5.2.14 ‘Fault delay’ on detector lines

[BTQ00300325]

Description
On the Interactive and SynoLOOP detector lines, there is a property ‘Fault delay’
which has the following function:

This property does not work with these types of detector lines.

Status
The function of the ‘Fault delay’ has been clarified and the descriptions in the
tooltip and the technical documentation have been adapted accordingly.

– Interactive and SynoLOOP detector lines:

The function is related to the collective input modules connected to the line and
not to the line itself. The property name and the tooltip description have been
adapted as follows:

20

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.2.15 Short-time faults ‘Device missing’ on a SynoLOOP detector line

[BTQ00300421]

Description
In case of multiple output or input activations within a short time (e.g. when an
alarm occurs and then multiple controls and their outputs are activated) it can
happen that some devices on an SynoLOOP detector line report faults ‘Device
missing’ for a short time. However, the line/devices are fully functional at all times.

Status
The bug has been fixed.

5.2.16 ‘Always manned’/’Always unmanned’ not indicated correctly via BACnet

[BTQ00304347]

Description
If an area ‘Alarm organization mode’ is configured as ‘Always manned’ or ’Always
unmanned’, it then stays in ‘manned’ or ‘unmanned’ operation mode and cannot be
switched to the other mode. Also no event ‘Manned operation’ or ‘Unmanned
operation’ is published.
Due to a bug, the state ‘Manned operation’ or ‘Unmanned operation’ is still
published on BACnet which then leads to an unwanted event on the connected
BACnet device.

Status
The bug has been fixed.

5.2.17 Frozen PMI display

[BTQ00296368, BTQ00296445]

Description
In some rare cases it can happen that the PMI display freezes. Key operations
then still seem to be executed and also LEDs are activated/deactivated but the
display shows the last content before the problem occurred and does not change
anymore. After a restart of the station everything works as expected again.
This e.g. has been observed when the customer text of a detector line was
changed or when the duration of a time limited zone isolation was entered.

Status
The bug has been fixed.

5.2.18 Incorrect no. of tested/untested devices in ‘Peripherals test report’

[BTQ00296365]

Description
Due to incorrect date evaluation by the embedded system, in some cases the
number of tested and untested devices in a ‘Peripherals test report’ is incorrect.

Status
The bug has been fixed.

21

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.2.19 Peripheral test data is lost when downloading configuration

[BTQ00305442]

Description
In the following case the current values of the peripheral test data (time stamps
used for the ‘Peripherals test report’) are lost:
– After the last upload of the site configuration to the tool, tests of peripheral
devices are carried out → the values of the respective devices are updated in
the station
– Before these changed station data is uploaded to the tool, a download to the
station is done → due to a bug, all values of the peripheral test data are then
overwritten with the values which had been stored when the configuration was
last uploaded and therefore all changes in the peripheral test data since the last
upload of the configuration are lost

Status
The bug has been fixed.

5.2.20 Fault events from interactive lines during start-up of a station

[BTQ00309450]

Description
After the restart of a station with interactive detector lines and an active connection
to a management station, the interactive detector lines sometimes report a fault
even though everything is fully functional. The reason is the heavy processing load
caused by the management station reading data from the station during the start-
up.

Status
The start-up procedure has been improved in order to avoid too heavy processing
loads.

5.2.21 Fault events from interactive lines after migration from FC700
[BTQ00310049, BTQ00316473, BTQ00313452]

Description
After the migration of interactive lines from FC700 to FS720, the interactive
lines/devices sometimes report faults even though everything was running without
a problem before the migration and no new problems exist.

Status
The bugs have been fixed.

22

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.2.22 Station crashes due to additional devices in an isolated ‘External sounder

control’
[BTQ00313055]

Description
In the following case the station crashes during the start-up:
– an existing ‘External sounder control’ is switched off in the station
– with the Engineering tool additional devices are assigned to this ‘External
sounder control’
– the changed configuration is downloaded to the station
– when the station restarts after the download, the isolation of the ‘External
sounder control’ remains but a problem with isolating the additionally added
channels of this ‘External sounder control’ occurs and the station crashes

Status
The bug has been fixed.

5.2.23 Manual zone with FDCIO223: re-alarm instead of ‘Glass broken’

[RTC190405]

Description
In the following case, a ‘Manual zone’ initiates a re-alarm upon the reset of a still
active alarm instead of resetting the alarm and reporting a ‘Glass broken’ event:
– a collective line of an FDCIO223 is assigned to the ‘Manual zone’
– property ‘Always resettable’ of the ‘Manual zone’ is enabled (= reset of an alarm
is always possible and in case the manual call point is then still active, a
message ‘Glass broken’ shall be reported)
– property ‘Coll. line: alarm response / fault delay’ of the FDCIO223 is set to a
value >35s.

Status
The bug has been fixed.

5.2.24 Incorrect processing of faults on a C-NET detector loop

[BTQ00307995]

Description
In the following case a C-NET detector line connected as loop is wrongly regarded
as stub connection in case of a line fault (short-circuit or open line) and therefore
all devices after the line fault are lost:
– a new C-NET detector line is connected to a station as loop
– devices on this new C-NET detector line are read in via command ‘Read in
installed devices’ (and possibly the detection tree configuration is added etc.)
– the line card with this detector line is never completely restarted (powerless or
command ‘Reset module’)

Status
The bug has been fixed.

For further information, please see also Maintenance Information

MI_18 _xxx_FS20_Line_start_up_en.

23

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.2.25 Fire control without effects: unexpected ‘Control test mode’ after reboot
[BTQ00297132]

Description
In the following case, a ‘Fire control’ unexpectedly switches to the ‘Control test
mode’:
– ‘Fire control’ without any effects (e.g. ‘Fire control’ which combines some
causes and is then used as cause for another control → “cascading”)
– This ‘Fire control’ is switched to ‘Control test mode’
è The ‘Control test mode’ is indicated with an event message
– The station which contains this ‘Fire control’ is restarted (automatically after a
download of the configuration or manually via reset button)
è After the restart the ‘Fire control’ is still in ‘Control test mode’ which is
indicated with an event message
– The ‘Fire control’ is switched back to normal operation with command ‘Control
test mode end’
è The ‘Control test mode’ event message is removed
– The station which contains this ‘Fire control’ is restarted (automatically after a
download of the configuration or manually via reset button)
è After the restart, instead of staying in normal operation mode, the ‘Fire control’
unexpectedly changes to ‘Control test mode’ again which is indicated with an
event message

Status
The bug has been fixed.

5.2.26 Unexpected faults upon simultaneous activation of more than 20 outputs

[BTQ00312634/BTQ00315935]

Description
If more than 20 outputs of FDCIO22x devices are activated simultaneously (by the
same event) it can happen that inputs of these devices for which the ‘Short circuit
monitoring’ is enabled temporarily report a fault.

Status
The bug has been fixed.

5.2.27 Configured SAFEDLINK connection disabled if no HW connected

[BTQ00262116]

Description
It is not possible anymore to use a standalone station with a configured
SAFEDLINK connection and a router function without having a SAFEDLINK
module physically connected. Due to a change in the SW the SAFEDLINK
connection is disabled in this case.
Such a setup is used for a BACnet connection via the then available SAFEDLINK
address. Now that the connection is disabled if no HW is connected, this is not
possible anymore.

Status
The bug has been fixed. The setup as described above works as expected again.

24

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.3 Removed bugs & changes, FW version 70.28.32 ® 70.28.38

5.3.1 Introduction

This chapter describes which bugs/restrictions have been removed in the IP7.0
Development Service Release 1 version compared to the IP7.0 Delivery Release
version.

5.3.2 Unsecure firmware update mode cannot be activated on all PMI variants
[BTQ00318678]

Description
With IP7.0 a new secure firmware update has been introduced which ensures that
only signed firmware images can be used. This is the standard firmware update
mode which is activated with the well-known procedure.
If an IP7.0 station needs to be downgraded to an older version which is not
available as a signed firmware image, an unsecure firmware update mode can still
be activated with a new key combination. With firmware version 70.28.32 this
unsecure mode can be activated as follows:
Keep the ‘S32’ button on the rear of the operating unit pressed and press
<Acknowledge> and <Silence buzzer> on the Person Machine Interface at the
same time for approx. 5 s until the station restarts.
This is not possible on a French station because the French front panel layout
does not provide the key <Silence buzzer>.

Status
To allow the activation of the unsecure firmware update on all station types with an
integrated operating terminal, the key combination has been changed with
firmware version 70.28.38. It can now be activated as follows:
Keep the ‘S32’ button on the rear of the operating unit pressed and press
<Acknowledge> and <Reset> on the Person Machine Interface at the same time
for approx. 5 s until the station restarts.

5.3.3 Additional information elements are lost

[BTQ00325144]

Description
Configured additional information elements (‘Additional component’, ‘Mounting
type’, ‘Commissioning date’, ‘Exchange date’) are lost when the configuration is
changed by the embedded system (e.g. HW read-in or removal of a device) and
then the configuration of the station is uploaded to the Engineering tool.

Status
The bug has been fixed.

25

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.4 Removed bugs & changes, FW version 70.28.38 ® 70.28.58

5.4.1 Introduction

This chapter describes which bugs/restrictions have been removed in the IP7.0
Development Service Release 2 version compared to the IP7.0 Development
Service Release 1 version.

5.4.2 No silence/unsilence function on Management Station for alarm devices

activated by a Technical Zone
[BTQ00260032]

Description
For alarm devices which were activated by a Technical zone, the function
silence/unsilence is not available on a connected Management Station.

Status
The bug has been fixed.

5.4.3 Interactive detector line with many radio devices does not start up after
migration from FC700
[BTQ00317980]

Description
Due to more restrictive timing conditions in FS720, an interactive detector line with
many radio gateways DCW1151 and many radio detectors DOW1171 does not
start up after migration from FC700 to FS720. After approx. 10 minutes the start-up
of the line is terminated with an error message.
This problem occurred with a line with 12 radio gateways and 109 radio detectors.

Work-around/measure
If this problem occurs, reduce the number of radio gateways and radio detectors on
the respective interactive detector line by moving some of the devices to a different
(existing or new) interactive detector line.

Status
The bug has been fixed.

5.4.4 Wrong event reported in case of permanent Cerberus Mobile access

[BTQ00272380]

Description
Even though for Cerberus Mobile permanent access is configured, 2 events are
reported, ‘Operat.(permanent)’ (correct) and in addition also ‘Operat.(temporary)’
(incorrect).

Status
The bug has been fixed.

26

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.4.5 Station reboots after activation of a ‘Prioritized voice evac control’

[BTQ00319390]

Description
In the following case the station reboots unexpectedly:
– ‘Prioritized voice evac control’ with (at least) a cause group which is silenceable
(= property ‘Effects are ‘Alarm devices’ if activated by this cause group’ is
TRUE), e.g. ‘Causes EVAC FIRE’
– The cause group has several causes, e.g. alarms from different zones
– The property ‘Activation delay’ of the cause group has a value >0, e.g. 30s
– New alarm in one of the assigned zones
è The ‘Activation delay’ of the cause group is started
– When the ‘Activation delay’ expires, the cause group is activated (→ event
‘Active/playing’) and plays the configured audio sequence
– The user silences with key ‘Alarm device’
è The cause group changes to ‘Active/silenced’
– New alarm in another one of the assigned zones
è The ‘Activation delay’ of the cause group is re-started (which is also wrong but
handled with a separate BTQ, see 5.5.19)
– The user successfully acknowledges and resets both alarms before the ‘Activa-
tion delay’ has expired
è Everything changes to quiet state (no alarm anymore, control/cause groups in
quiet state, etc.)
– Instead of being cancelled immediately, the ‘Activation delay’ timer continues in
the background and once it expires, the station reboots unexpectedly

Once the control is active and has been silenced, neither a new active cause nor
function ‘Alarm device’ (key on the PMI) immediately unsilences the control. In both
cases the ‘Activation delay’ time is started again, and the control is not
reactivated/unsilenced before this delay time expires. In both cases the control
should immediately be unsilenced.

Status
The bug has been fixed.

5.4.6 ‘Position undefined’ of damper output not recognized upon start-up

[BTQ00325823]

Description
In the following case the status ‘Position undefined’ of a ‘Smoke extraction damper
output/supervised’ or ‘Fire damper output/supervised’ is not recognized and the
respective fault event message is not reported:
– Output is in status ‘Position undefined’ when the station is started up
– Before the respective fault message is published, the output is activated
– When the output is then deactivated again and the status ‘Position undefined’
still exists, the respective fault event message is not published

Status
The bug has been fixed.

27

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.4.7 Alarm of a zone with 2 detector dependency cannot be reset on Management

station
[BTQ00325705]

Description
In the following case, an alarm cannot be reset as expected on a connected
Management station:
– Zone with 2 detector dependency
– Global setting ‘Multiple alarm per zone’ (country-specific, not visible to the user)
is set to true → each device that contributes to an alarm decision of a zone
initiates a separate alarm
– The zone is switched to ‘Installation test mode’
– A first detector is activated
è the zone changes to PRE-STAGE and reports a Pre-ALARM for this detector
– A second detector is activated
è the zone changes to MAIN STAGE and reports separate Automatic Fire
ALARMs for both detectors
– On the connected Management station, a ‘Reset’ is executed via one of the
detectors
è On the FS20 station, both alarms are reset as expected but on the
Management station, the second alarm remains
è This alarm only disappears if the zone is switched off and then switched on
again

Status
The bug has been fixed.

5.4.8 Function ‘Freeze selected outputs’ does not work with damper outputs
[BTQ00325859]

Description
With the command ‘Freeze selected outputs ON’ all outputs on an C-NET detector
line which are enabled for this function will keep their current state when the station
or line is restarted. Instead of keeping the current state, the damper outputs
change to the quiet state/position in this case.

Status
The bug has been fixed – the damper outputs which are enabled for the ‘Freeze
selected outputs’ function keep their current state when the station or detector line
is restarted.

5.4.9 No events are sent to a BACnet client

[BTQ00331499]

Description
In case that an “IP component” (e.g. faulty external firewall) is exchanged at
runtime, it can happen that no events are sent to a BACnet client anymore, but this
is not recognized by the client supervision.

Status
The bug has been fixed.

28

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.4.10 Hidden ‘Activation’ events of a ‘Fire control’ still visible on a Management sta-
tion
[BTQ00322256]

Description
In FS720 it is possible to hide ‘Activation’ events from ‘Fire controls by setting
property ‘’Activation’ events hidden’ to TRUE. Then, such events are not displayed
on any Operating terminal, not stored in the event memory and not printed but still
exist, i.e. they are still published in the network and are available for other controls
and transmitted via BACnet. Due to this, the amount of control events in the lists of
FS720 and of a connected Management station is different which is confusing for
the user.

Status
In order to be able to also hide such events for a connected Management station, a
new option has been added to the SiBX map:
<IncludeFeature name="isActivationHidden" svo="false"/>

5.4.11 ‘C-NET line card’ reports fault ‘Hardware missing’

[BTQ00328068]

Description
In case that on a ‘C-NET line card’ the localization of connected devices is
interrupted by a short-circuit, the line card restarts and reports a fault ‘Hardware
missing’.

Status
The bug has been fixed.

5.4.12 Station reboots when executing function ‘Show intervention text’ via function
key
[BTQ00328325]

Description
If on an Operating terminal which currently does not have any events to display the
function ‘Show intervention text’ is executed via a pre-programmed function key,
the station reboots unexpectedly.

Status
The bug has been fixed.

29

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.4.13 Function ‘Freeze selected outputs’ does not work correctly in some cases
[BTQ00330896]

Description
In the following case the function ‘Freeze selected outputs’ does not work as
expected:
– FDCIO with the following output configuration
– ‘Output mode’: ‘Inactive: On / active: Off’
– ‘Output failsafe position’: ‘Open’
– ‘Enable temporary freeze of output position’: true (box checked)
– the detector line to which the FDCIO is connected is in normal operation, the
output of the FDCIO is closed
– the function ‘Freeze outputs ON’ is executed on the detector line
– the detector line is switched off
è the output on the FDCIO is still closed
– a short-circuit occurs on the detector line
– the detector line is switched on again
è fault events ‘Short circuit’ and ‘Open line’ are published; the output on the
FDCIO is still closed
– the detector line is switched off again
è unexpectedly, the output on the FDCIO is now opened even though the func-
tion ‘Freeze selected outputs’ is still active

Status
The bug has been fixed.

5.4.14 Sporadic faults from migrated sounder lines connected to an ‘I/O card
(horn/monitored, FCI2009)’
[BTQ00330424]

Description
Sounder lines which have been migrated from a legacy system to an ‘I/O card
(horn/monitored, FCI2009)’ sporadically report a fault.

Status
The bug has been fixed.

5.4.15 FRD/FRT (FT2010/FT2011): start-up problems

[PCR 868512, Defect 873082]

Description
When the C-NET line start-up is interrupted (due to isolation or restart of the line),
the initial configuration of the FRD/FRT (FT2010/FT2011) might fail.
The FRD/FRT (FT2010/FT2011) remains in the unconfigured state and cannot
display any incidents. ‘Operation not possible’ will be displayed on the FRD/FRT.
See also Technical Product Information TPI_20_015.

Status
The bug has been fixed.

30

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.4.16 Problems if a new generation alarm device (optical, acoustic, voice) is

removed while its settings are written
[Defect 893417]

Description
If a new generation alarm device (optical, acoustic, voice) is removed from a
detector line before all the settings are written into the device, the C-NET line card
tries to write the settings endlessly. This then leads to several problems: no
download of new audio configurations to the new generation alarm device (optical,
acoustic, voice), FRTs/FRDs on that detector line are not configured, the detection
of missing devices takes much longer, etc.

Status
The bug has been fixed.

5.4.17 ‘Minimal duration of activation’ of RT channels does not work correctly

[Defect 943735]

Description
The function ‘Minimal duration of activation’ in the remote transmission channels
does not work correctly. When the remote transmission channel is activated by a
cause and then the cause disappears before a configured time ‘Minimal duration of
activation’ has expired, the remote transmission channel is still deactivated
immediately.

Status
The bug has been fixed.

31

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.5 Restrictions and known bugs, FW version 70.28.58

5.5.1 Sounder activation
[BTQ00005034, BTQ00014338]

Description
Some regulations (e.g. British Standard) require that upon pressing a manual call
point all related sounders must be activated within 3s.
This requirement cannot be met in all possible configurations with an arbitrary
number of sounders.
The 3s can be met if a maximum of 31 sounders is activated by one alarm.
More detailed application/configuration guidelines are described in a separate Ap-
plication Note; please contact PM for more information.

Work-around/measure
Make sure that the controls are configured such that not more than 31 sounders
are activated at the same time. If you need assistance, please contact the
Customer Support Center.

5.5.2 Message ‘Station restarted’ in control panels with large configurations

[BTQ00017718]

Description
Although not explicitly required by EN54-2, our interpretation is that a control panel
should complete start-up/restart within 300s. In control panels with large configura-
tions this requirement cannot always be met. In this case, we strongly recommend
indicating the start-up/restart with a system fault.

Work-around/measure
If a start-up/restart cannot be completed within 300s the property ‘Fault message
upon restart of station’ in the ‘Details’ tab of the respective station element should
be set to TRUE. This causes the station to report a system fault ‘Station restarted’.

32

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.5.3 Only 1 message per event category and element on FAT [VdS countries only]
[BTQ00021662]

Description
The FAT (Feuerwehr-Anzeige-Terminal) can only display 1 event per event
category and element. If an element initiates more than 1 event of the same event
category then only the first one is displayed on the FAT.

Example:
– Element: C-NET line
– Events: ‘Short circuit’ + ‘Open line’ (both messages: event category ‘Other fault’)
– FAT displays: ‘Short circuit’

Work-around/measure
-

5.5.4 Alarms in zones with ‘Two-zone dependency’

[BTQ00022434]

Description
In applications with ‘Two-zone dependency’ the following problem can occur:
– MAIN STAGE in both assigned zones even if a detector has been switched off
after triggering a PRE-STAGE:
– If a detector of a zone with ‘Two-zone dependency’ triggers the PRE-STAGE
(‘First alarm’) and this detector is switched off afterwards, the alarm is not re-
moved.
– If now a detector in the assigned zone for the ‘Two-zone dependency’ also
triggers a PRE-STAGE in that zone, both zones change to MAIN STAGE.

Work-around/measure
-

5.5.5 FDCIO222/FDCIO224 short-circuit monitoring

[BTQ00024518]

Description
Under the following circumstances an input of an FDCIO222/FDCIO224 is
activated undesirably:
– Short-circuit monitoring of the respective input is enabled
– The input is assigned to a ‘Technical zone’
– If on this input a new short-circuit occurs, a fault will be reported but the input
and the zone will be activated as well

Work-around/measure
-

33

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.5.6 Floor Repeater Terminal FT2010 / Floor Repeater Display FT2011

Restriction Work-around/measure
If more than 1 command is configured on a function key of a Floor Repeater Configure the same access level
Terminal and for these commands different access levels are defined, the high- for all commands on the same
est of the access levels is taken ® all commands can only be executed if this function key.
access level has been reached on the FRT.
[BTQ00021661]
The time for the transmission of an event to an FRT depends on the length of In systems with FRTs, keep the
the customer text – the longer the customer text of an event, the longer the customer texts as short as pos-
delay time until it is displayed on the FRT. sible.

Always all FRTs (FRDs) of the same ‘FRT configuration group’ (‘FRD configura- If the performance is no issue
tion group’) are restarted/configured if at least one of them needs to be restart- the FRTs (FRDs) can be as-
ed/configured (e.g. if an isolated detector line is switched on or upon a short- signed to different groups which
circuit) even if they are connected to different detector lines. have the same visibility.
Due to an internal limitation it can happen that the customer text of an event -
message cannot be displayed with the full length of 40 characters. A minimum
of 32 characters is always displayed; the last 1..8 characters can be cut off.
[BTQ00022399]
FRT and FRD do not display the date according to the country-specific system -
settings in the Base Data Variant.
The displayed format is always: ‘dd.mm.yy’.
[BTQ00022215, BTQ00021739]
Following characters must not be used in any of the texts that are displayed on -
an FRT or FRD (Customer text, Event text, Event category, Element category):
‘¦’, ‘$’ (except if used as part of a variable in an event text).
Tab. 8 Bugs/restrictions FRT/FRD

5.5.7 Evac NL master/slave on different physical interfaces [NL only]

[-]

Description
If the ‘Evac master’ and an ‘Evac slave’ of the same ‘Evac panel’ in the ‘Operation’
task card are assigned to 2 different physical interfaces – 1 to a local unit FTO2007
and 1 to a detached Evac panel on RS485/UFP - then the FS720 station crashes.

Work-around/measure
Always assign the ‘Evac master’ and all ‘Evac slaves’ of the same ‘Evac panel’ to
the same type of physical interface.

34

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.5.8 Re-alarm of ‘Manual zone’ with interactive call point takes too long
[BTQ00148584]

Description
Use case:
– ‘Manual zone’ configured with ‘Always resettable’ = false
è This means that an alarm cannot be reset as long as the respective manual
call point is still active (no message ‘Glass broken’)
– Interactive manual call point assigned to the zone
– Manual call point is activated
è Alarm is reported
– User acknowledges and resets the alarm while the manual call point is still ac-
tive
è The alarm is removed and the re-alarm is not reported until about 55s later
which is much too long

Work-around/measure
-

5.5.9 Incorrect event message ‘New devices found’ on interactive detector line
[BTQ00246298]

Description
If a device on an interactive detector line is physically removed from the
installation, it can either be deleted in the configuration via Operating terminal
command ‘Remove/delete device’ or then in the Engineering tool. If it is done in the
Engineering tool and then the changed configuration is downloaded, the event
message ‘New devices found’ is displayed after the station has rebooted even
though the respective device does not exist anymore.

Work-around/measure
Restart the respective detector line via command ‘Restart line’ or execute the
command ‘Accept replaced devices’, then the incorrect event message will
disappear.

5.5.10 No cause input activation by an FDCIO223 input

[BTQ00246276]

Description
In case of an earth fault (between + or – of the IO and earth) or an open line no
activation of an assigned cause input is initiated when the FDCIO input is activated
(wiring 1, 2, 3 or 4). As soon as the earth fault disappears, the cause input is
correctly activated (if the FDCIO input is still active).

Work-around/measure
-

35

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.5.11 Fault not removed when C-NET line is switched off

[BTQ00245919]

Description
In rare cases it can happen that a fault on a C-NET line (e.g. short-circuit) is not
removed when the line is switched off.

Work-around/measure
Switch the respective detector line on and then off again.

5.5.12 FDUD292 function ‘Test alarm total’ not possible when zone or detector is
switched off
[BTQ00240290]

Description
If a detector or the zone of the detector is switched off before the function ‘Test
alarm total’ of the detector tester & exchanger FDUD292 is executed, the detector
will not be activated.

Work-around/measure
Switch on the detector or its zone before testing with this function.

5.5.13 Abort of ‘Upload site’/‘Download site’, ‘Upload event memory’ or ‘Upload site
log files’ with no evident reason
[BTQ00130918, BTQ00257929, BTQ00257232]

Description
In rare cases it can happen that an upload or download of a large site configura-
tion, an upload of the event memory or an upload of the site log files is aborted with
no evident reason.

Work-around/measure
Repeat the upload or download from/to stations which had not been processed yet
before the abortion.

5.5.14 No event ‘Incompatible FW’ for additional CPUs

[BTQ00244553, BTQ00260197]

Description
After the first restart of a station after a ‘FW update additional CPUs’ no event
‘Incompatible FW’ is reported for additional CPUs with an incompatible firmware
version. This event is not reported before the station is restarted again. From then
on it is reported after each following restart as long as the firmware is incompatible.

Work-around/measure
-

36

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package

5.5.15 SynoLOOP: fault remains until line is restarted after replacement of a DC1136
[BTQ00298104]

Description
In case that a on a SynoLOOP detector line a DC1136 is replaced while the
detector line is running, the fault of the assigned logical channel is not removed
until the detector line has been restarted.

Work-around/measure
Do only replace a stationary device while the detector line is switched off (power-
less).

5.5.16 Sounder control cannot be silenced via button ‘Alarm device’

[BTQ00300887]

Description
If a sounder control (Universal sounder evac control, Phased sounder evac control,
Phased voice evac control, Prioritized voice evac control) is activated via an AVC
cause, e.g. ‘AVC, Fire ALARM’, then silencing of the control via button ‘Alarm
device’ is not possible if in the respective AVC configuration no alarming device is
configured (= no check box ticked in the properties for the ‘Local alarming devices’
and the ‘Global alarming devices’).

Work-around/measure
Configure any alarming device (but not the related control in the ‘Alarming control
group’), e.g. ‘External sounder’, in the respective AVC configuration.

5.5.17 Station reboot when auto-configuring a line with more than 25 FDCIO222
and/or FDCIO224
[BTQ00316054]

Description
If a C-NET detector line with more than 25 FDCIO222 and/or FDCIO224 connected
is auto-configured, the station reboots.

Work-around/measure
If there are more than 25 such devices connected to one of the C-NET lines of a
station, do not execute the command ‘Auto-configure line’ on this line and do not
use the command ‘Auto-configure station’ at all.

37

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.5.18 Evaluation of ‘Threshold’ function of controls not as expected

[BTQ00298136]

Description
Due to a bug, the ‘Threshold’ function of a control cause is not always evaluated as
expected in case that the option ‘Include sub-tree’ is enabled. The reason is that
since IP6.0 the logical channels in specific cases report a new event which is
hidden on the operating terminal but visible on the BACnet interface. By mistake
the hidden events are taken into account by the ‘Threshold’ function.
Such hidden events are reported by logical channels in case the parent zone or the
parent control is isolated or switched to test mode.

Work-around/measure
Split the configuration into separate causes in separate controls and then combine
the activations in an additional control.

Example:
– a control shall be activated if 2 or more zones in a section with 6 zones are
isolated; detection tree:

– configuration of the controls:

– control group with 1 control for each zone; each control with a cause with
category ‘Other isolation’ assigned to one of the zones, ‘Threshold ‘= 1,
‘Include sub-tree’ disabled; no effects:

38

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 FXS7211 Firmware package
Example for the configuration of a cause:

– different control group, 1 control with a cause with category ‘Other activation’
assigned to the above control group containing the “zone specific controls”,
‘Threshold’= 2, ‘Include sub-tree’ disabled:

Configuration of the cause:

39

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
FXS7211 Firmware package

5.5.19 Incorrect processing of ‘Activation delay’ in evac controls

[BTQ00319388]

Description
The property 'Activation delay' in the 'Universal sounder evac control' and the
cause groups of the 'Prioritized voice evac control' is not processed correctly.
The delay should be started upon the first activated cause or when the
control/cause group receives an activation command (and was in quiet state
before). Once the delay has expired and the control/cause group has been
activated, the delay shall not be started again until the control/cause group is in
quiet state and then a first cause is activated or command received, etc.

The current behaviour is as follows:

– Universal sounder evac control':
Once the control is active and has been silenced, neither a new active cause nor
function 'Alarm device' (key on the PMI) does immediately unsilence the control.
In both cases the 'Activation delay' time is started again, and the control is not
reactivated/unsilenced before this delay time expires. In both cases the control
should immediately be unsilenced.
– Cause group of a 'Prioritized voice evac control':
Once the cause group is active and has been silenced, neither a new active
cause nor function 'Alarm device' (key on the PMI) does immediately unsilence
the cause group. In both cases the 'Activation delay' time is started again, and
the cause group is not reactivated/unsilenced before this delay time expires. In
both cases the cause group should immediately be unsilenced.

Work-around/measure
DO NOT SET an ‘Activation delay’ in a ‘Universal sounder evac control’ or in a
cause group of a ‘Prioritized voice evac control’.

5.5.20 Alarm disappears on connected Management station

[Defect 950847]

Description
In case that a zone with an assigned manual call point with door contact, e.g.
FDM233, reports an alarm and then the door of the manual call point is opened for
more than 60s, then on a connected Management station the alarm will be
removed and only a fault is reported.
The FS20 PMI reports an alarm and a fault in this case.

Work-around/measure
-

40

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
 Miscellaneous

6 Miscellaneous
6.1 Support
For support please contact the Customer Support Center
Phone: +49 89 9221 8000
Fax: +49 89 636 720 000
E-mail: [email protected]
Intranet: https://intranet.sbt.siemens.com/fs/csc
Availability: MO-FR: 08:00 am. – 05:00 pm. CET

41

Building Technologies A6V11513842_c_en_--

Fire Safety & Security Products 02.2020
Issued by © 2006-2020 Copyright Siemens Switzerland Ltd
Siemens Switzerland Ltd Technical specifications and availability subject to change without notice
Building Technologies Division
International Headquarters
Theilerstrasse 1a
CH-6300 Zug
Tel. +41 41-724 24 24

www.siemens.com/buildingtechnologies
Document ID A6V11513842_c_en_-- Manual -
Edition 02.2020 Section -