Softwarehandbook 62

Table of Contents
Integral Software V 6.2.
Manual.
B-HB-010EN Manual Integral Software 6.2 V 2.1 1

Table of Contents
2 Manual Integral Software 6.2 V 2.1 B-HB-010EN

Table of Contents
Table of Contents
1 General..................................................................................................................................... 7
2 Installation ................................................................................................................................ 8
2.1 System Requirements............................................................................................................................................ 8
2.2 Integral Software pack installation...................................................................................................................... 9
2.3 BMZ Integral USB Driver Installation ............................................................................................................ 13
3 New Features in Integral Software Pack 6.2 .............................................................................15
3.1 General.................................................................................................................................................................. 15
3.2 Overview of New Features in comparison with SW 6.1.x ........................................................................... 15
3.2.1 Integration of the Control Panel Integral MAP ....................................................................................................................... 15
3.2.2 Additions to existing hardware features..................................................................................................................................... 15
3.2.3 New Features ................................................................................................................................................................................. 15
3.3 Integral Software Pack changes......................................................................................................................... 16
3.3.1 Listgenerator .................................................................................................................................................................................. 16
3.3.2 ServiceAssistant ............................................................................................................................................................................. 16
4 Integral Listgenerator...............................................................................................................18
4.1 General.................................................................................................................................................................. 18
4.1.1 USB dongle .................................................................................................................................................................................... 19
4.1.2 System Limits................................................................................................................................................................................. 19
4.2 Start Up ................................................................................................................................................................. 20
4.2.1 New Configuration ....................................................................................................................................................................... 20
4.2.2 Existing Configurations................................................................................................................................................................ 20
4.2.3 Configuration Window................................................................................................................................................................. 21
4.3 Definitions............................................................................................................................................................ 22
4.3.1 Project Properties.......................................................................................................................................................................... 22
4.3.2 General Settings............................................................................................................................................................................. 23
4.3.3 Store fault ....................................................................................................................................................................................... 24
4.3.4 Automatic disablement................................................................................................................................................................. 25
4.3.5 Intervention ................................................................................................................................................................................... 26
4.3.6 Delay switching.............................................................................................................................................................................. 27
4.3.7 Time ................................................................................................................................................................................................ 27
4.3.8 Event memory ............................................................................................................................................................................... 28
4.3.9 Software redundancy .................................................................................................................................................................... 29
4.3.10 Logical Number............................................................................................................................................................................. 29
4.4 Assembly............................................................................................................................................................... 30
4.4.1 B3 or B5 subcontrol unit ............................................................................................................................................................. 30
4.4.2 B4-A2- or B6-X2-subcontrol unit .............................................................................................................................................. 31
4.4.3 B6-X1F-subcontrol unit C1......................................................................................................................................................... 32
4.4.4 B4-A1- or B6-X1-subcontrol unit C1 ........................................................................................................................................ 33
4.4.5 Subcontrol unit naming................................................................................................................................................................ 34
4.4.6 Internal Operating Panel B3-CII / B4-CII ............................................................................................................................... 34
4.4.7 Internal Operating Panel B5-CII / B6-CII ............................................................................................................................... 35
4.4.8 Main processor unit B3-MCU32 / B4-MCU32........................................................................................................................ 36
4.4.9 Main processor unit B5-MCU32 / B6-MCU32........................................................................................................................ 37
4.4.10 Loop modules DXI2 / B3-DAI2 / B4-DAI / B4-DAI2....................................................................................................... 37
4.4.11 B3-MTI8 Monologue Technology Module............................................................................................................................... 40
4.4.12 B3-IM8 Module for monitored inputs....................................................................................................................................... 42
4.4.13 Stub line Module B3-LEE23 for 140 detector series............................................................................................................... 43
4.4.14 B3-LEE24 loop circuit module for 150 detector series .......................................................................................................... 44
4.4.15 B3-DCI6 DC technology module............................................................................................................................................... 45
4.4.16 B3-DTI2 Dialogue Technology Module ................................................................................................................................... 46
4.4.17 B4-EIO input/output module .................................................................................................................................................... 47
4.4.18 B4-EIP Indicator Panel................................................................................................................................................................ 48
4.4.19 B3-BAF / B4-BAF control module ........................................................................................................................................... 49
4.4.20 B5-BAF / B6-BAF control module ........................................................................................................................................... 51
4.4.21 Remote operating panel B3-CIE / B5-MMI-CII..................................................................................................................... 52
4.4.22 Universal Input/Output Module B3-UIO ................................................................................................................................ 53
4.4.23 Fire brigade indicator panel FAT – DIN14662........................................................................................................................ 55
4.4.24 External indicator panel for 4 extinguishing zones IPES ....................................................................................................... 56
4.4.25 External indicator panel for 8 extinguishing zones IPEL....................................................................................................... 57
4.4.26 External LED Indicator Panel for up to 32 detector zones EAT32..................................................................................... 58
Table of Contents
4.4.27 External LED Indicator Panel for up to 64 detector zones EAT64..................................................................................... 59

4.4.28 Relay module B3-REL16 ............................................................................................................................................................. 60
4.4.29 Relay module B3-REL10 ............................................................................................................................................................. 60
4.4.30 B5-MRI16 Multifunction relay module ..................................................................................................................................... 61
4.4.31 REL5 Onboard relay module...................................................................................................................................................... 61
4.4.32 B4-REL6 Onboard relay module................................................................................................................................................ 62
4.4.33 B3-OM8 Module for monitored outputs .................................................................................................................................. 62
4.4.34 B3-LPI Subcontrol Unit Coupling ............................................................................................................................................. 64
4.4.35 Universal Communications Module B3-USI4 .......................................................................................................................... 66
4.4.36 Universal Interface Module B4-USI........................................................................................................................................... 68
4.4.37 Reserve............................................................................................................................................................................................ 70
4.4.38 B3-HFI Interface Converter........................................................................................................................................................ 70
4.4.39 Subcontrol unit connection ......................................................................................................................................................... 71
4.4.40 Issuing logical device numbers.................................................................................................................................................... 71
4.4.41 Update to new modules – upgrade module .............................................................................................................................. 72
4.4.42 Update to a new control unit – upgrade control unit .............................................................................................................. 73
4.5 Protocols............................................................................................................................................................... 75
4.5.1 PPA ZZK....................................................................................................................................................................................... 75
4.5.2 SAT SSI .......................................................................................................................................................................................... 76
4.5.3 SPP .................................................................................................................................................................................................. 76
4.5.4 Integral Standard Protocol (ISP)................................................................................................................................................. 77
4.5.5 SecoNET connection ................................................................................................................................................................... 78
4.5.6 SecoNET Repeater ....................................................................................................................................................................... 79
4.6 Logical properties ................................................................................................................................................ 80
4.6.1 Configuration settings for the detector zone element ............................................................................................................. 80
4.6.2 Configuration settings for the input element............................................................................................................................ 81
4.6.3 Configuration settings for the output element ......................................................................................................................... 82
4.6.4 Configuration settings for the external element ....................................................................................................................... 85
4.6.5 Configuration settings for the printer element ......................................................................................................................... 86
4.6.6 Configuration settings for the operating panel element .......................................................................................................... 87
4.6.7 Configuration settings for the Battery element......................................................................................................................... 89
4.6.8 Configuration settings for the Mains element........................................................................................................................... 90
4.6.9 Configuration settings for the Delay level element.................................................................................................................. 91
4.6.10 Configuration settings for the Fire Brigade Control Panel element ...................................................................................... 92
4.6.11 Configuration settings for the Indicator element ..................................................................................................................... 95
4.6.12 Configuration settings for the Loop element............................................................................................................................ 98
4.6.13 Parameter Settings for the RemoteAccess element.................................................................................................................. 99
4.7 Boolean definitions ........................................................................................................................................... 100
4.7.1 System thresholds of Boolean Definitions.............................................................................................................................. 100
4.7.2 Boolean Definition Selection window ..................................................................................................................................... 101
4.7.3 Input criterion.............................................................................................................................................................................. 103
4.7.4 Logic gates.................................................................................................................................................................................... 107
4.7.5 Selection cursor ........................................................................................................................................................................... 107
4.7.6 Connections ................................................................................................................................................................................. 107
4.7.7 Negation (NOT).......................................................................................................................................................................... 108
4.7.8 Negation (NOT).......................................................................................................................................................................... 109
4.7.9 AND (AND)................................................................................................................................................................................ 109
4.7.10 OR (OR)....................................................................................................................................................................................... 110
4.7.11 Exclusive OR (XOR).................................................................................................................................................................. 111
4.7.12 Greater than ................................................................................................................................................................................. 112
4.7.13 More than ..................................................................................................................................................................................... 112
4.7.14 RS-Flipflop................................................................................................................................................................................... 112
4.7.15 D-Flipflop .................................................................................................................................................................................... 113
4.7.16 Counter ......................................................................................................................................................................................... 113
4.7.17 Impulse ......................................................................................................................................................................................... 114
4.7.18 Low-High ..................................................................................................................................................................................... 114
4.7.19 High-Low ..................................................................................................................................................................................... 115
4.7.20 Clock generator ........................................................................................................................................................................... 115
4.8 Detector zone macros....................................................................................................................................... 116
4.8.1 Table of Detector zone macros ................................................................................................................................................ 116
4.8.2 Parameters for Detector Zone Macros.................................................................................................................................... 117
4.8.3 Module-specific settings............................................................................................................................................................. 118
4.9 Operating macros .............................................................................................................................................. 119
4.9.1 Table of Operating Macros........................................................................................................................................................ 119
4.9.2 Parameters for operating macros.............................................................................................................................................. 120
4.10 Privilege macros ............................................................................................................................................... 121
4.10.1 Table of Authorisation macros ................................................................................................................................................. 121
4.10.2 Parameters for Authorisation Macros...................................................................................................................................... 122
4.11 Integral User ..................................................................................................................................................... 123
Table of Contents
4.12 Range filters ...................................................................................................................................................... 125

4.12.1 Range filter table.......................................................................................................................................................................... 125
4.12.2 Range filters ................................................................................................................................................................................. 126
4.12.3 Parameters for a range................................................................................................................................................................ 127
4.12.4 Range filter selection................................................................................................................................................................... 127
4.12.5 Example of the range filter ........................................................................................................................................................ 128
4.13 Message filters .................................................................................................................................................. 130
4.13.1 Table of Message Filters............................................................................................................................................................. 130
4.13.2 Parameters for message filter .................................................................................................................................................... 131
4.13.3 Element states in message filters .............................................................................................................................................. 131
4.13.4 Internal states............................................................................................................................................................................... 133
4.13.5 Commands ................................................................................................................................................................................... 134
4.13.6 Message filter selection............................................................................................................................................................... 134
4.14 Messages............................................................................................................................................................ 136
4.14.1 Messages table ............................................................................................................................................................................. 136
4.14.2 Parameter setting for messages ................................................................................................................................................. 137
4.14.3 Message type ................................................................................................................................................................................ 138
4.15 Sum criterium ................................................................................................................................................... 138
4.15.1 Table of sum criteria ................................................................................................................................................................... 138
4.15.2 Parameter settings for sum criteria ........................................................................................................................................... 139
4.16 Printer templates .............................................................................................................................................. 140
4.16.1 Table of Printer Templates ........................................................................................................................................................ 140
4.16.2 Parameters for printer templates .............................................................................................................................................. 141
4.16.3 Selecting the printer templates .................................................................................................................................................. 141
4.17 Further programming hints............................................................................................................................ 142
4.17.1 Macros - Library .......................................................................................................................................................................... 142
4.17.2 Warning when exporting............................................................................................................................................................ 143
4.17.3 Application Options ................................................................................................................................................................... 143
4.17.4 Delete elements ........................................................................................................................................................................... 144
4.17.5 References .................................................................................................................................................................................... 144
4.17.6 Table of List templates ............................................................................................................................................................... 145
4.17.7 Parameters for List templates.................................................................................................................................................... 145
5 IntegralText ...........................................................................................................................147
5.1 Screen elements ................................................................................................................................................. 147
5.1.1 Overview ...................................................................................................................................................................................... 147
5.1.2 Standard Screen Elements ......................................................................................................................................................... 148
5.1.3 Element Types (Tree View)....................................................................................................................................................... 149
5.1.4 Records (List View) .................................................................................................................................................................... 150
5.1.5 Input bar....................................................................................................................................................................................... 151
5.1.6 Tool bar ........................................................................................................................................................................................ 152
5.1.7 Commands ................................................................................................................................................................................... 153
5.1.8 Miscellaneous............................................................................................................................................................................... 153
5.2 Menu - Commands ........................................................................................................................................... 154
5.2.1 System menu................................................................................................................................................................................ 154
5.2.2 File menu...................................................................................................................................................................................... 155
5.2.3 Edit menu..................................................................................................................................................................................... 158
5.2.4 BMZ menu................................................................................................................................................................................... 161
5.2.5 View menu ................................................................................................................................................................................... 163
5.2.6 Options Menu.............................................................................................................................................................................. 164
5.2.7 Window menu ............................................................................................................................................................................. 167
5.2.1 Help menu.................................................................................................................................................................................... 167
5.3 Structure of a Record of the BMZ Integral................................................................................................... 168
5.4 Structure of a Record of the BMZ Maxima .................................................................................................. 169
5.5 Available element types .................................................................................................................................... 170
5.6 Process for producing the records.................................................................................................................. 171
6 WinLoader .............................................................................................................................173
6.1 Installation and Starting the Program ............................................................................................................ 173
6.2 Display in WinLoader when connected......................................................................................................... 174
6.2.1 B3/B4-MCU32 display............................................................................................................................................................... 174
6.2.2 Display B5-MCU32 / B6-BCU................................................................................................................................................. 175
6.3 Establishing a connection using COM or USB............................................................................................ 176
6.3.1 Establishing a connection over the COM interface............................................................................................................... 176
6.3.2 Establishing a connection over the USB interface................................................................................................................. 178

Table of Contents
6.4 Feeding in data (Download) ............................................................................................................................ 179

6.4.1 Download over COM interface ................................................................................................................................................ 180
6.4.2 Download over the USB interface ........................................................................................................................................... 181
6.4.3 Check Centralized Download ................................................................................................................................................... 181
6.5 Delete Files (only in Local Download mode)............................................................................................... 182
6.6 Download Files (only in Local Download mode)........................................................................................ 182
6.7 Options ............................................................................................................................................................... 182
6.7.1 General ......................................................................................................................................................................................... 182
6.7.2 Communications Settings .......................................................................................................................................................... 182
6.7.3 Language....................................................................................................................................................................................... 182
6.7.4 Profiles .......................................................................................................................................................................................... 183
6.8 LocalFlash........................................................................................................................................................... 183
6.8.1 Operating Files ............................................................................................................................................................................ 183
6.8.2 Uploading Operating files.......................................................................................................................................................... 183
6.8.3 Optional Files .............................................................................................................................................................................. 185
6.8.4 Uploading a Background Logo ................................................................................................................................................. 185
6.8.5 Delete Background Logo ........................................................................................................................................................... 186
6.8.6 Uploading Reaction Texts.......................................................................................................................................................... 187
6.8.7 Delete reaction texts ................................................................................................................................................................... 189
7 ServiceAssistant .....................................................................................................................190
7.1 Starting the Program ......................................................................................................................................... 190
7.2 Set project path .................................................................................................................................................. 190
7.3 The User Interface ............................................................................................................................................ 191
7.4 ServiceMonitor................................................................................................................................................... 191
7.4.1 Establishing a connection .......................................................................................................................................................... 192
7.4.2 Event memory ............................................................................................................................................................................. 193
7.4.3 Trigger memory........................................................................................................................................................................... 195
7.4.4 Event dependent event list ........................................................................................................................................................ 196
7.4.5 Show error counters ................................................................................................................................................................... 197
7.4.6 Show version information ......................................................................................................................................................... 198
7.4.7 Send a Command ........................................................................................................................................................................ 199
7.4.8 Software redundancy .................................................................................................................................................................. 200
7.4.9 Freeze outputs ............................................................................................................................................................................. 200
7.4.10 Logging System Messages.......................................................................................................................................................... 203
7.5 Loop Assistant ................................................................................................................................................... 204
7.5.1 Construction ................................................................................................................................................................................ 204
7.5.2 Establishing a connection .......................................................................................................................................................... 205
7.5.3 Read in loop topology to B3-DAI2, B4-DAI2, B3-LEE24, B3-DTI2 ............................................................................... 205
7.5.4 Loop topology configuration on B3-DAI2 and B4-DAI2 ................................................................................................... 207
7.5.5 Configure/reset loop topology on B3-DAI2 and B4-DAI2 ................................................................................................ 211
7.5.6 Adopt loop topology addresses on B3-DAI2 and B4-DAI2................................................................................................ 212
7.5.7 Determine loop topology at B3-LEE24 .................................................................................................................................. 213
7.5.8 Configure loop topology to B3-LEE24................................................................................................................................... 215
7.5.9 Program/reset loop topology at B3-LEE24 ........................................................................................................................... 217
7.5.10 Determine loop topology at B3-DTI ....................................................................................................................................... 217
8 NetworkAssistant ..................................................................................................................217
9 Trouble-shooting ....................................................................................................................218
Responsible for the content of this document:

Dipl.Ing. (FH) René Türk, M.Sc.
Product Management Fire Alarm Systems
Tel: +43-1-81157-337  E-Mail: r.tuerk@schrack-seconet.com

General  System Requirements
1 General
The term “Integral Software” encompasses all software components (programs) for planning, commissioning,
maintenance and diagnostics for control panels from the Integral family.
The Integral Software comprises of several independent individual programmes, all of which work independ-
ently of one another and as marked by a separate version number. In order to make the responsibility for the
user of ensuring that the compatibility of individual programs among one another easier, the programs are not
issued separately, but are tailored to suit each other and put together to form a pack. Every such software pack
is assigned a version number in turn (e.g. Integral Software Version 6.2).
The Integral Software Pack Version 6.2 is shipped on a CD-ROM and contains the following tools:
The following parts are described in this documentation:
General Part
 Installation
 New features in SW 6.2
Software tools
 Listgenerator
 IntegralText
 WinLoader
 ServiceAssistant
The Integral Software is used for the following applications:
 BMZ Integral Fire alarm control panel, modular system

 BLZ Integral Combined fire alarm and extinguishing control panel
 SLZ Integral Control mechanism for controlling extinguishing systems
 BMZ Integral C Fire alarm control panel, compact system (2-4 loops)
 BMZ Integral C1 Fire alarm control panel, compact system (1 loop)

Installation  System Requirements
2 Installation
The Integral Software Pack version 6.2 is available as an installation file on the CD-ROM. In the event that
version 6.1 of the Integral Software Pack has already been installed on the PC, then the upgrade to version 6.2
of the Integral Software Pack can only be carried out using a new installation file on the CD-ROM.
The software must first be installed on the PC before it can be used. The execution of the installation proce-
dure as mentioned is necessary, as the files can not be simply copied into a folder. Moreover, during the instal-
lation process, the program is registered in Windows, and the adapted in accordance with the current configura-
tion.
2.1 System Requirements

In order for the installation of the Integral Software Pack to be able to be carried out, the following require-
ments exist with regard to hardware and software:
Minimum System Requirements for PC or Laptop
CPU Pentium Processor

Processor speed 1 GHz
RAM min. 128 MB*
* dependent on the operating system as well as the number of programs running
Interface 1 serial RS232 and 1 USB 1.1 or higher for USB Dongle*
* optional parallel interface for using a parallel interface dongle
Miscellaneous Mouse and keyboard

Hard drive 60 MB free storage space on the hard drive
Drives 1 CD-ROM drive for software installation
Graphics card 1024x768 Pixel resolution, 256 colours
Operating system Windows 2000 SP3
Windows XP
Windows Vista
Windows 7
Interface
In the event that your computer does not have an RS232 serial interface, we recommend using a
PCMCIA card which will then make this serial interface available.

Installation  Integral Software pack installation.
2.2 Integral Software pack installation.

The installation CD and a computer with the hitherto described requirements are required for the installation
process. The descriptions hereafter refer to the Windows XP user interface, and may differ depending on the
actual configuration of the computer.
An existing distribution of version 5.x or older of the Integral Software Pack won’t be unin-
stalled. An update to a current Version can only be done within the Versions (e. g. 5.1.1 to 5.1.3
but not 5.1.1 to 6.1.1). In the event of an Integral control panel already existing, an upgrade to
version 6.2 must be carried out as part of maintenance works or when the configuration is
changed.
To start the installation, the following steps must be carried out:
Insert the Installation CD in to the CD/DVD drive
If the CD/DVD drive’s auto play function has been

activated, then the installation will start automatically.
In the event that the installation process does not start
automatically, then Windows Explorer must be
opened. Select the CD/DVD drive, and then right
click on the CD/DVD drive. The Auto play function
can be selected from the dropdown menu.
In the event that the Auto play function cannot be set,

then Windows Explorer must be opened. There the
CD/DVD drive must be selected. To start the installa-
tion of Integral Software Pack 6.2, the file “Auto-
run.exe” must be opened.
Installation of the Integral Software
For the installation of Integral Software Pack 6.2 administrator rights are required. If such rights
have not been granted, then an error message will be displayed.
In this instance you should contact your system administrator.
Next it is possible to choose between German and

English as the Setup language.

The installation of Integral Software version 6.2

now begins.
Click on the “Next” button to continue.
An information window is displayed. The software

license agreement for Listgenerator is described
here. Read through this information carefully, and
select “I accept the agreement” and then click on
the “Next” button.
Select the folder in which the Integral projects

should be saved. Click on “Browse”, to select an
existing folder. Click on the “Next” button to con-
tinue.
To ensure the correct use of the Integral Software, you are only allowed to change the drive let-
ter, under the directory structure is created.

There are two different installations available for in-

stallation:
 Integral Software German
 Integral Software English
Additionally the following components can also be

selected:
 Integral Text
 Listgenerator dongle driver
 Templates Austria
 Templates Germany
Select the desired type of installation and then click

on "Next" to continue.
Select the program folder in which the Integral pro-

gram links should be saved.
Click on “Browse”, to select an existing folder.
The default setting is “Seconet/Integral”.
Additional tasks such as
 Detector labels,
 Shortcuts or
 RemoteAccess connection
can be selected.
If you activate „RemoteAccess connection for tools“, only the necessary buttons to use Re-
moteAccess at all Integral Softwaretools will be generated. To use RemoteAccess you must install
the optional Software Pack and use the compatible Dongle.

Then an overview of the installation with all parame-

ters that have been set is displayed. Now click on
“Install” to begin the installation process.
The installation process is now carried out. Please

wait, while the installation process of Integral Soft-
ware Pack 6.2 is carried out.
To complete the installation, the computer must be

restarted.
Click on “Finish” to restart the computer.
After the Integral Software Pack has been installed, a folder is created in the “Programs” folder on the start
menu called “Seconet”. From the folder “Integral” contained therein, the individual programs can be executed.
This is only applicable if the default settings are used. If a user-defined label was chosen, then the entry in the
menu is named accordingly.

Installation  BMZ Integral USB Driver Installation
2.3 BMZ Integral USB Driver Installation
Using the Winloader or the ServiceAssistant of the Integral Software Pack 6.2 communications to the Integral
system can be established in two different ways. When a connection is established to the B3-Hardware plat-
form, the COM connection, as used in Integral Software versions 5.x and earlier, is used. From the B5 hard-
ware platform onwards, communications take place over a USB connection. In order to be able to use the USB
connection, the Integral USB driver must be installed. The USB driver is copied onto the PC during the instal-
lation of Integral Software 6.2.
The descriptions hereafter refer to the Windows XP user interface, and may differ depending on the actual
configuration of the computer.
When first establishing a connection, the Windows

operating system’s automatic hardware detection will
display the message “New hardware found”.
The "Assistant for finding new hardware" will open.
Select “Software von einer Liste oder bestimmten

Quelle installieren (für fortgeschrittene Benutzer)” and
click on “Next” to continue.
Selcect „Durchsuchen“ to search for the USB driver

source. The USB driver is always in
„\Seconet\Integral\USB“ and doesn’t depend on the
directory drive.
Click on “Next” to continue.
This message is displayed when the driver is being

installed, because the Integral USB driver is not
signed in the Windows Operating System.
Click on “Continue installation” to continue.

Installation  BMZ Integral USB Driver Installation
The Integral USB driver is installed and registered in

the operating system.
Then the window will appear that the assistant is com-

plete, with the Integral USB driver thereby being suc-
cessfully installed.
Click on "Finish" to finish the installation process.
Then a Windows information window will display a

message about the successful installation.

New Features in Integral Software Pack 6.2  General
3 New Features in Integral Software Pack 6.2

3.1 General
Version 6.2 of the Integral Software is available with German and English versions, and comes on a CD.
3.2 Overview of New Features in comparison with SW 6.1.x

The main task of Integral Software V6.2 is to implement the Control Panel Integral MAP.
3.2.1 Integration of the Control Panel Integral MAP

 Support for new hardware items B5-CII and B5-MMI-CIP
 Support for new hardware items B6-CII
3.2.2 Additions to existing hardware features

 Additions B3-MMI-FAT features
 Additions B3-MMI-FPA features
3.2.3 New Features

 Deactivation of the wire break detection at activating primary output B6-BAF
 Version control of the ISP-Protocol
 Seperation of the existing ServiceAssistant into ServiceAssistant and NetworkAssistant

New Features in Integral Software Pack 6.2  Integral Software Pack changes
3.3 Integral Software Pack changes

V 6.2 of the Integral Software Pack is compatible with Windows 2000 SP3, Windows XP, Windows Vista and
Windows 7.
3.3.1 Listgenerator
Version information
All described new features and modifications refer to Integral
List generator version 6.2
In the “Help” menu, you can display a version window by
clicking on the “Info about...” menu point.
Deactivating OC-recognition B6-BAF
In level 2 “Logical properties” of the Listgenera-

tor, the option „no OC-recognition on activation“
 for the “output” element type can be config-
ured for each primary output of the B6-BAF.
3.3.2 ServiceAssistant
Seperation of the existing ServiceAssistant

From V6.2 the existing ServiceAssistant will be seperated into „Ser-
viceAssistant“ (ServiceMonitor, LoopAssistant) and „NetworkAssis-
tant“ (NetworkMonitor, NetworkAssistant).
ServiceAssistant
NetworkAssistant
New Features in Integral Software Pack 6.2  Integral Software Pack changes
When updating from version 5.1 to version 6.2 of the software, these changes must be carried manu-
ally.
In software version 6.2 an additional output type (type

4) has been defined for the BA-SOL in ListGenerator.
The output numbers of the BA-SOLs on the loop
must be entered under this output type - type 4.
In level 2 “Logical properties” of the Listgenerator,

the desired output behaviour (tone type, output limit)
must be configured for the “output” element type.
The basic output options  or the specific output
behaviour  for each activation criteria can be con-
figured for the output.
In LoopAssistant it is only possible to select outputs

of type 4 for the BA-SOL.
If the programming is not modified when the update
from version 5.1 to version 6.2 of the software pack is
carried out, LoopAssistant will display an error mes-
sage.

Integral Listgenerator  General
4 Integral Listgenerator
4.1 General
Definition The Integral Listgenerator is used to generate the project-specific programming for a
fire alarm control panel or a extinguishing system control panel. In this process, the
system’s hardware is defined, the addresses and parameters (including Integral loop
technology) are assigned and logical links are created.
Validity area The Integral Listgenerator is used for the following applications:
BMZ Integral
Fire alarm control panel, modular system
BLZ Integral
Combined fire alarm and extinguishing system control panel
SLZ Integral
Control mechanism for controlling extinguishing systems
BMZ Integral C
Fire alarm control panel, compact system (2 loops)
BMZ Integral C1
Fire alarm control panel, compact system (1 loop)
Demo version The decisive difference between the demo version and the full version, in that to use
the full version a dongle must be connected to the USB interface of the PC. Without
the dongle, the export function of the Listgenerator is not available, otherwise the
demo version is fully functional.
Default Programming Default programmings are available, in which the most important presettings for
(Template files) various different standard programmings have already been defined. It is recom-
mended, when creating a project-specific programming to work exclusively from
these default programmings. The files can be found in the project folder, which was
created when the Integral software was first installed.
MacroLibrary A MacroLibrary is available, in which the most frequently used parameter settings for
the various elements are summarised in parameter records. They can be selected
from macro lists and assigned to the elements.
LanguageLibrary A language library is available, in which the available language versions of the stan-
dard texts (= texts on the display of the control panel’s operating panel) are summa-
rised. The desired languages can be selected from a list in the Integral Listgenerator.

Integral Listgenerator  General
4.1.1 USB dongle
Use The USB dongle that is shipped with the full version of the Integral software, must
be connected to a USB port on the PC.
Function The Integral Software is fully functional both with or without using the Dongle.
Without the dongle, however, the user can not export (compile) a customer-specific
configuration that he has generated in Listgenerator in a format, which can be
downloaded into the control panel. In simple terms, the only function of the dongle
is to permit the export function of the Integral Listgenerator.
Compatibility The USB dongle is supported from version 5.0.0 of the Integral Software Pack.
The parallel dongle continues to be supported by the software, but is no longer
shipped.
SecoNET Dongle A separate SecoNET dongle is required for programming a SecoNET network. The
SecoNET dongle is registered to a single person, and contains a unique ID. This
information must be given when ordering the SecoNET software pack.
RemoteAccess-Dongle For using the RemoteAccess software pack, a separate RemoteAccess Dongle is
required.
RemoteControlPanel- For using the RemoteControlPanel software pack, a separate RemoteControlPanel
Dongle Dongle is required.
The fault-free operation of the external devices (printers, scanners, CD-ROM etc.) which oper-
ate from the same parallel interface as the same time as the dongle has not been tested. How-
ever, there are no known problems.
4.1.2 System Limits

The Integral Listgenerator automatically checks the logical system limits with each entry made, which occur
when the system is extended. If the maximum has been reached, then a message is automatically displayed.
per subcontrol unit per subcontrol unit loop

Subcontrol Units -- max. 16
Operating Panels (external, internal) max. 8 max. 16 x 8
Printers (external, internal) max. 3 max. 16 x 3
Fire brigade control panels max. 8 max. 16 x 8
Detector zones max. 256 max. 16 x 256
Inputs, controllers, and indicators max. 256 of each max. 16 x 256 of each
Boolean definitions max. 512 max. 512 (from Version 3.4.0)
Flip-Flop (RS-FF, D-FF) max. 256 max. 16 x 256
Counter max. 256 max. 16 x 256
Timers (Pulse, positive edge, negative
max. 32 max. 16 x 32 *)
edge, clock generator)
External devices (e.g. sprinkler sys-
max. 256
tems)
Delay levels max. 16
Customer-specific texts 6500 with an average of 25 characters per text
*) 16x32 timers can only be used under specific circumstances. As a rule, only 32 timers can be used per subcontrol unit loop.

Integral Listgenerator  Start Up
4.2 Start Up
The start screen appears after starting the Listgenera-
tor. The menu changes dynamically depending on the
selected view.
 Menu bar: The menu bar contains the list of commands.

 Menu command: A command in the menu bar.
 Tool bar: The tool bar contains a selected list of shortcuts.
 Button: A command in the short cut bar.
The following two possibilities exist for starting a new project:
 New: To add a new configuration.

 Open: Opens an existing configuration.
4.2.1 New Configuration

In order to add a new configuration, a document type must
first of all be selected. In this instance it is possible to
choose between a B5 / B6 Integral (BMZ Integral, BMZ
Integral C, BMZ Integral C1) and a SecoNET Master Con-
trol Unit.
 BMZ Integral: The B5 / B6 Integral selection is used

for configuring individual fire alarm control panels or up to
16 connected fire alarm control panels in a subcontrol unit
loop.
 SecoNET master control unit: The selection of the

master control unit is used for centralized operation and
indication of a SecoNET control panel network that con-
forms to EN 54 and VdS standards. It consists of a BMZ
Integral subcontrol unit with a full door, to which a remote
SecoNET operating panel with an integrated log printer has
been attached via the MMI-BUS.
4.2.2 Existing Configurations

The relevant project can be selected from the list of
existing projects.

Integral Listgenerator  Start Up
4.2.3 Configuration Window

After having chosen between a new or an existing configuration, the configuration window then appears. There
are, generally speaking, two views:
View 1: Physical View View 2: Logical properties
 Menu bar: The menu bar contains the list of commands.
 Tool bar: The tool bar contains a list of shortcuts. This is where it is possible to switch between both the
views.
 Subcontrol Units: All types of subcontrol units, which are supported by the software can be selected.
 Connections: It is possible to configure the networking of subcontrol units to form a subcontrol unit loop.
It should be ensured, however, that a suitable networking module must be used for the networking process.
 Workspace Physical: In the "Physical" workspace, the control panels and their networking are shown.
 Workspace for logical properties: In the “logical properties” workspace, the details about the different
types of elements are shown.
 Element type: The “Elementtype” dropdown menu dynamically adjusts itself depending on the configura-
tion and contains all the elements that have been configured e.g. inputs, detector zones, external operating
panels, batteries, outputs, printers, network, delay level, loop, fire brigade control panel, extinguishing zone
etc.
 Sorting: Here is decided whether the entries in the workspace should be sorted in ascending or descending
order based on the logical element number.
 Filters: The displayed range of logical numbers can be set using filters. e.g. filter from 1 to 10, and only logi-
cal numbers 1 to 10 will be displayed.
 Display: In the display section every type of element can be given a user-defined display profile. Moreover, it
is also possible to change the display mode (list or table) of the workspace.

Integral Listgenerator  Definitions
4.3 Definitions
All general definitions are described hereafter, which are
available for the programming of the Integral.
4.3.1 Project Properties

The following options exist for the definition of
configuration properties.
 Project name
The name of the project must be entered here.
 Programmer
Name of the person who will undertake the
programming and configuration.
 Version
Version number is entered here. This must be in
the format X.X.X. This version number is not
automatically updated. For every modification, it
must be remembered that the version number
must be calculated by hand.
Recommendation: Version 0.0.1 for the start of the project. Version 1.0.0 when the programming has
been completed and handed over to the client.
The version number increased with the relevant highest level of priority, if:
 Position 1: the structure of the system changes, e.g. a new module is added or a current one removed, a
new version of the software is uploaded, etc.
 Position 2: the peripherals change, i.e. a new element is added (hitherto a reserve option) or an available
element is removed.
 Position 3: the parameter settings change, e.g. a detector zone changes from automatic (ALZSP) to non-
automatic/manual (DKM), an output uses a break contact instead of a make contact, etc.
 Language
The necessary country language is selected here, in which the standard texts should appear on the displays of
the operating panels as well as in printouts from internal and external log printers.
 Hardware type
The hardware type determines whether a BMZ, BLZ or SLZ is being used.
 Company Name
Here it is possible to choose between the names of the companies in the group of companies.
 Notes
In the notes pane, programming modification information for every version must be documented. Only by
doing this is it possible to ensure that changes in the software have be observed.

4.3.2 General Settings
The following general settings can be made:
 Message on warm start

A warm start is displayed as a module fault on
the operating panel, until it has been reset
manually.
 Contamination only in daytime operation

Cases of contamination that occur during night time operation will only be indicated when operation
switches over to daytime operation on the operating panel. The prerequisite for this happening, is that day-
time and night time operation have been configured using delay levels.
 SCU operation blocked

If the control panel is used in connection with a BMZ Maxima, then when a connection has been estab-
lished, then operation of the operating panel is blocked. In the event of there being a cabling fault, then op-
eration at the operating panels of the BMZ Integral are automatically unblocked.
 store active state of BSE/BFS-LED’s

By activating the active state of the BSE/BFS-LED’s will be saved and continue to appear, even if the sys-
tem will be reseted by “Reset Alarm/System” on the control panel.
 SecoNET Connection Fault Message

immediately: A connection fault on the SecoNET is indicated immediately as soon as it occurs on the
operating panel.
never: A connection fault on the SecoNET is never indicated on the operating panel.
delayed: A connection fault on the SecoNET is only indicated once the entered time delay period
has elapsed. (Time entry of between 1 minute and 2 hours)
 SecoNET Client Fault Message

immediately: A SecoNET client fault is indicated immediately as soon as it occurs on the operating
panel.
never: A SecoNET client fault is never indicated on the operating panel.
delayed: A SecoNET client fault is only indicated once the entered time delay period has elapsed.
(Time entry of between 1 minute and 2 hours)
 Display filter SCU number

Detector zone: Where the slave control unit number is displayed on the master control unit for detector
zones can be filtered.
All elements: Where the slave control unit number is displayed on the master control unit for all elements
can be filtered.

 Display leading zeros

Display elements with If this flag is set, then it is possible to change in the following fields whether ele-
leading zeros: ments are shown on the Integral.
SCU number: It is possible to display the SCU number as a two or three digit number. If the
SCU number has less than two or three digits, then the empty digits will be re-
placed with zeros.
Element number: It is possible to display the element number (e.g. the detector zone) as a two,
three, four or five digit number. If the element number has less than two, three,
four or five digits, then the empty digits will be replaced with zeros.
Indicator number: It is possible to display the indicator number (e.g. the detector) as a two or three digit
number. If the indicator number has less than two or three digits, then the empty
digits will be replaced with zeros.
 Separators
SCU number / Element Number: The separator used when being displayed on the control panel can be
configured for between the SCU number and the element number. The
following characters can be configured: - / . : e.g. SCU 1/1 or SCU 1.1
Element number / Indicator: The separator used when being displayed on the control panel can be
configured for between the element number and the indicator. The
following characters can be configured: - / . : e.g. Zone 1/1 or Zone
1.1
 Display LED unfiltered alarm bit (DAI)

If this flag is set, then the detection of a characteristic, which can lead to an alarm in the system, is indicated
on the detector. It must be in normal operating mode (i.e. not in revision mode). It is indicated by the detec-
tor by means of the LED flashing. This function is also known as the signature alarm.
SCU number conversion table

In a standard project subcontrol unit numbers can be issued between 1-254. If SCU numbers outside of this
numerical range are required, then a conversion table must be generated and stored in the master control
unit. E.g. subcontrol unit no. 429 corresponds to subcontrol unit no. 3 in reality. In the master control unit
the number 429 is indicated for subcontrol unit no. 3. The configuration can only be done in the master con-
trol unit.
SecoNET-Number (0-999)
To change the display of a SCU in a master control unit.
e. g.: SCU-Number 200  Display in a SCU : e. g. 200-3
SecoNET-Number 300  Display in a master control unit: e. g. 300-3
4.3.3 Store fault

Here it can be configured, whether, when there is an
element fault, the triggered fault message should be
stored in the fire alarm control panel. When the fault has
been dealt with, then the accompanying fault message
must be manually reset at the operating panel of the fire
alarm control panel.
 All element types

The setting only refers to the elements displayed in
the selection field.

4.3.4 Automatic disablement

By activating this function, a period of time will begin if there is an alarm in one or more detector zones after a
collective alarm reset has occurred. If a new alarm occurs in one of the detector zones where there has previ-
ously been an alarm within this period of time, then the detector zone in question will be automatically disabled.
After another subsequent group alarm reset, all automatically disabled detector zones will be activated again.
The detector zones can also be manually reactivated at any time.
 Activation period: The “automatic disablement” function can be configured here. The value can be entered
in the input field for the duration of the time window [from 1.00 secs to 18:00 hours].
 Can be activated from: The automatic disablement can be triggered by a group alarm reset from one (or
even several or all) of the systems below.
Operating panel: Applies for all operating panels of a subcontrol unit or of a subcontrol unit
loop
Fire brigade control panel Applies for all fire brigade control panels of a subcontrol unit or of a sub-
control unit loop
Management system: Applies to all connected management systems
Master control unit: Applies for the master control unit of a SecoNET
However, at least one system must be selected, otherwise automatic disablement will not start.
 All element types: The setting only refers to the elements displayed in the selection field.

4.3.5 Intervention
Configuration the intervention functions.
 Extension periods
Number of repeated extension periods possible
(standard setting: 0)
 Display explore time

Acknowledgement time: Definition of the
acknowledgement time
(Standard setting: 30 secs)
Explore time: Definition of the explore time
(Standard setting: 3 minutes)
 Operating macro
in which are used, in order to restrict the operation of elements of a subcontrol unit or links control units
on a command level. For example it is possible to define that the intervention is only operational in a certain
user level.
 Cancel intervention when

Alarm from: Intervention is cancelled when an alarm message originates from certain
element types. These element types can be freely defined (Standard setting:
detector zone).
Fault from: Intervention is cancelled when a fault message originates from certain ele-
ment types. These element types can be freely defined (Standard setting:
detector zone).
 Zone dependent explore time

In the event that for specific detector zones a different standard explore time should apply than the previ-
ously entered standard explore time, then this can be set by defining a zone filter for the relevant detector
zones.
Thanks to the zone filter, a separate explore time can be set for the selected zone.
The programming of a delay level is necessary in this instance.
 Name
Freely selectable text for labelling the zone-
dependent explore time.
 Explore time
The desired explore time is entered in this field
(min. 1.00s up to max. 18:00 hrs).
 Zone filter selection

The zone filter must be selected from this table,
upon which the zone-dependent explore time is ef-
fective.

4.3.6 Delay switching

 Master
All the defined delay levels for a subcontrol unit (SCU)
or a subcontrol unit loop (SCU loop) are assigned to a
specific SCU, from where they are then synchronised.
This SCU is known as the Master (default = 1).
 Behaviour in the event of the Master failing

It is possible to configure how the delay levels should
behave, in the event that the Master fails.
Take up safe position: It can be configured, that in the event of the Master failing that all delay levels
are automatically switched to the state “Night” and thereafter remain in this
state until the connection to the Master is re-established.
Stay controllable: It can be configured that all delay level remain locally controllable i.e. only on
the SCU, in the event that the Master fails. Automatic changeover continues
to occur. If the connection to the Master is re-established, then all delay levels
are automatically synchronised.
4.3.7 Time
The BMZ Integral is able to switch automatically
between standard time and summer time.
 Master
Selects from which subcontrol unit within the
BMZ Integral network of control units, the
date and time should be used for all other sub-
control units.
 Changeover to Summer Time

Configuration of the changeover to summer
time
Automatically: By selecting this checkbox the changeover from summer time to standard time and
vice versa is carried out automatically.
Start of summer time: Definition of the point in time at which the changeover to summer time should
occur
End of summer time: Definition of the point in time at which the changeover to winter time should oc-
cur

4.3.8 Event memory

The Integral system has an event log memory, in which the last 200 events are constantly stored, and the event
log memory can be extended by 65,000 events by use of an extension using an SD card. The content of the
memory can, as previously, be printed out on any printer connected to the fire alarm control panel, or with the
help of the ServiceAssistant or the control panel display can be read out and displayed in plain text. If the event
log memory is read out with the help of ServiceAssistant, then it can also be saved for further processing. Fur-
thermore the Integral System also has a trigger memory. The trigger memory (max. 200 events) makes a copy of
the event log memory and write protects this copy for 72 hours. It is thereby also possible, even when a consid-
erable period of time has elapsed to identify the source that caused the fault or the alarm to be triggered. To
activate the trigger memory, a trigger condition must be defined.
 Message filter
One or more message filters can be selected and logically linked (using OR or AND links) for the memory
of the internal log printer in the select message filter dialogue box. This setting applies for all internal print-
ers of a subcontrol unit (SCU) or a subcontrol unit loop (SCU loop).
 Trigger condition
Allows the targeted processing of the data required (e.g. alarm or fault). The trigger criteria is contained in a
Boolean definition. As standard the trigger is for a group alarm or group fault.
 End recording after 100 events

ends the recording by the trigger memory after 100 events
 Trigger lock time

The time is set to 72 hours as standard. I.e. the trigger memory saves the data for 72 hours. Only once the
72 hour period has expired is it possible for a new event to be copied into the trigger memory, or if the trig-
ger lock time was manually reset in the ServiceMonitor assistant, then the memory is available immediately
again.
 Extended Event Memory

This function is only available if a B5-MCU32 or higher with an integrated SD card is available.

4.3.9 Software redundancy

The “Software redundancy active” function can only be configured for B4/B6 control units.
 Software redundancy active

The functions of emergency operation can be set.
 Start emergency operation after x restarts

Here it is possible to configure after how many re-
starts of the system within a specific period of time
the system should be switched into emergency opera-
tion.
 Within x hours
The time interval can be set, which is appropriate for
the occurrence of restarts. I.e. if there are 3 system re-
starts within 24 hours, then the system will change
over to emergency operation.
 Functions, which are deactivated in emergency

operation
Here it is possible to configure, which functions
should be deactivated in the event of the system being
operated in emergency mode.
The function “Operation at the fire brigade control panel” should never be deactivated in emergency operation.
The software redundancy configured in Listgenerator must also be activated in ServiceAssistant,
as otherwise a module fault will be displayed at the control unit.
4.3.10 Logical Number

An input window is opened for entering the logical numbers of elements. The element in question will be ad-
dressed using this logical number for further steps in the configuration process. This operation of all elements
is also carried out and indicated using the logical number at the operating panel.
The range for logical numbers differs depending on the element type. The maximum range of logical numbers,
however, is from 1 to 65534.

Integral Listgenerator  Assembly
4.4 Assembly
In this chapter, all the settings are described for the hardware components, which are available when configur-
ing the Integral.
4.4.1 B3 or B5 subcontrol unit

In this case the Integral hardware configuration is shown based upon a B5 unit:
 Assign numbers…: Defines the properties of the auto numbering of the logical element numbers.
 Name: Name of the subcontrol unit(e.g. porter – ground floor)
 Number: Determines the number of subcontrol units in a subcontrol unit (1 to 16).
When using a B3-MCU32, the logical number must also be set using hardware using the modules’
address switch.
When a B5-MCU32 is used, the subcontrol unit numbers are set when uploading the control unit
software in WinLoader.
 Modules: The available modules for fitting to the subcontrol unit can be selected here.
 CII: Connection socket on the B3-MCU32 or B5-MCU32 module for the internal operating panel
 1: MCU connection slot, must be fitted with a B3-MCU32 or B5-MCU32 module.
When using a B5-MCU32 is must be ensured that the B5-BUS and a B5-PSU are fitted in the
control unit.
 2-8: General connection slots, can be fitted with modules as required.

 9: General connection slot.
The relay card connection slots 11-13 are only available when fitted with B3-BAF, B5-BAF, B5-
MRI16 or B3-LPI modules.
 PSU: PSU connection slot, must be fitted with a B3-PSU5 or B5-PSU module.
 11-13: Connection slots for relay modules – they can only be fitted with B3-REL10 or B3-REL16(E) mod-
ules.

How a B3 Integral can be updated to a B5 Integral is described in the chapter “Updating to a

new control unit”.
4.4.2 B4-A2- or B6-X2-subcontrol unit

In this case the Integral C hardware configuration is shown based upon a B6-X2 unit:
When using a B4-MCU32, the logical number must also be set using hardware using the modules’
address switch.
When a B6-MCU32 is used, the subcontrol unit numbers are set when uploading the control unit
software in WinLoader.
 CII: Connector plug on the basic circuit board of the Integral C for the internal operating panel
 B6-X2-BCU: Main module (B4 or B6), fitted for certain, contains the functions of the MCU32, BAF, DXI2
and REL5 modules.
 Optional connection slot: Only the B4-USI, B4-DAI or B4-EIO modules can be fitted in this connection
slot.
How the B4 Integral C is updated to a B6 Integral C or the Integral C is updated to an Integral, is

described in the chapter “Updating to a new control unit”.

4.4.3 B6-X1F-subcontrol unit C1

In this case the Integral C1 hardware configuration is shown based upon a B6-X1F unit:
When a B6-MCU32 is used, the subcontrol unit numbers are set when uploading the control
unit software in WinLoader.
 CII: Connector plug on the basic circuit board of the Integral C1 for the internal operating panel
 B6-X1F-BCU: Main module, fitted for certain, contains the functions of the MCU32, BAF, DXI2 and
REL5 modules and the connection for a Fire Brigade Control Panel.
How the B6 Integral C1 can be updated to an Integral is described in the chapter “Updating to a
new control unit”.

4.4.4 B4-A1- or B6-X1-subcontrol unit C1

In this case the Integral C1 hardware configuration is shown based upon a B6-X1 unit:
When using a B4-MCU32, the logical number must also be set using hardware using the mod-
ules’ address switch.
When a B6-MCU32 is used, the subcontrol unit numbers are set when uploading the control
unit software in WinLoader.
 CII: Connector plug on the basic circuit board of the Integral C1 for the internal operating panel
 B6-X1-BCU: Main module (B4 or B6), fitted for certain, contains the functions of the MCU32, BAF, and
DXI2 modules.
How the B4 Integral C1 is updated to a B6 Integral C1 or the Integral C1 is updated to an Integral,

is described in the chapter “Updating to a new control unit”.

4.4.5 Subcontrol unit naming

 Name
Unique label for the subcontrol unit or serves to lo-
cate the subcontrol unit in the building more quickly,
if several subcontrol units are connected in the sub-
control unit loop. A sensible name is for example the
location of the subcontrol unit.
4.4.6 Internal Operating Panel B3-CII / B4-CII

The B3-CII and B4-CII modules (Control and Indicating Unit, Integrated) are components of the internal op-
erating panel of a BMZ Integral or BMZ Integral C/C1. The module controls the LCD indicator, the operating
keyboard (keypad) as well as the in-built log printer of the fire alarm control panel. This module is connected
using a ribbon cable to the modules B3-MCU32, B4-BCUA2 or. B4-BCUA1, B5-MCU32 or B6-BCU X2 or
B6-BCU X1/X1F.
 Log.No.: The logical number of the relevant operating panel is assigned here.
 Printer: It is possible to configure whether a log printer is connected to this operating panel, as well as what
logical number it should have.
 Module may be absent: If this option is activated, then there is no fault message at the BMZ if the relevant
operating panel has been configured but has not been connected (e.g. for an SCU loop for servicing pur-
poses when individual SCUs are not fitted with an operating panel, ONLY FOR COMMISSIONING
PURPOSES).

4.4.7 Internal Operating Panel B5-CII / B6-CII

The B5-CII and B6-CII modules (Control and Indicating Unit, Integrated) are components of the internal op-
erating panel of a BMZ Integral or BMZ Integral C/C1. The module controls the LCD indicator, the operating
keyboard (keypad) as well as the in-built log printer of the fire alarm control panel. This module is connected
using a ribbon cable to the modules B5-MCU32 or B6-BCU X2 or B6-BCU X1/X1F.
 Log.No.: The logical number of the relevant operating panel is assigned here.
 Printer: It is possible to configure whether a log printer is connected to this operating panel, as well as what
logical number it should have.
 Module may be absent: If this option is activated, then there is no fault message at the BMZ if the relevant
operating panel has been configured but has not been connected (e.g. for an SCU loop for servicing pur-
poses when individual SCUs are not fitted with an operating panel, ONLY FOR COMMISSIONING
PURPOSES).

4.4.8 Main processor unit B3-MCU32 / B4-MCU32

The B3-MCU32 or B4-MCU32 (Master Control Unit, 32 Bit) module can be found in every BMZ Integral or
Integral C. The module acts as the main processor, and received data that has been processed by the other
modules. It undertakes all necessary processes required for the logical behaviour of the fire alarm control panel
and delivers the results back to the relevant modules, which then trigger the necessary operations. The
B3-MCU32 and B4-MCU32 manage the configuration data and the system time. The system software and con-
figuration data are loaded through the service interface and the system diagnosis carried out.
 Remote Control panel: If access is required through a Remote Control Panel, then the control check box
must be marked and the logical number of the operating panel entered.
A Remote Control Panel takes a logical address of the type operating panel, thereby reducing the
number of physical operating panels that can be connected by one.

4.4.9 Main processor unit B5-MCU32 / B6-MCU32

The B5-MCU32 or B6-MCU32 module can be found in every new BMZ Integral or Integral C. The module
acts as the main processor, and received data that has been processed by the other modules. It undertakes all
necessary processes required for the logical behaviour of the fire alarm control panel and delivers the results
back to the relevant modules, which then trigger the necessary operations. The B5-MCU32 and B6-MCU32
manage the configuration data and the system time. The system software and configuration data are loaded
through the service interface and the system diagnosis carried out.
 SD/MMC memory card: The B5-MCU or B6-MCU can be optionally fitted with a standard issue memory
card. Memory cards of types “SD card” and “MMC card” are supported.
The supported memory capacity can be between 32MB up to a maximum of 2GB.
A plausibility check is carried out, which ensures, that the memory capacity requirements of the configured
functions do not exceed the capacity of the SD card. When the control panel is started up the SD card is
queried. If a lower memory capacity is detected than is required, then a corresponding fault message will fol-
low (e.g. module fault). Moreover, an error message also occurs if the manual write protection on the mem-
ory card is activated.
If there are several SD cards in a single SCU loop, then all the configured functions are available on all the
SD cards. The plausibility check on start-up is carried out for each B5-MCU.
The event memory log of the B5-MCU or B6-MCU thereby is expanded from 200 entries previously to an
extra 65,000 entries.
Additionally the extended event memory still needs to be released (see event memory).
 Remote Control panel: If access is required through a remote operating panel (RemoteAccessPanel), then
the control check box must be marked and the logical number of the operating panel entered.
A Remote Control Panel takes a logical address of the type operating panel, thereby reducing the
number of physical operating panels that can be connected by one.
4.4.10 Loop modules DXI2 / B3-DAI2 / B4-DAI / B4-DAI2

The DXI module (Dialog eXtended Line Interface) or DAI (Dialog Analog Interface) contains 1 or 2 loops for
connecting addressable detectors and modules with integrated short circuit isolators. This technology will here-
after be referred to as Integral Loop Technology. Per loop, a total of up to a max. 250 elements (DXI) and up
to a max. of 128 elements (DAI) can be connected. Elements can be detectors or modules. Per automatic de-
tector, it is also possible to connect either a parallel indicator panel or a base-mounted buzzer. The latter re-
quires neither to be configured in the Integral Listgenerator or in the LoopAssistant.

In addition to the possible settings listed below, other settings can be made for each ring in the dialogue menu
“Loop configuration data” (e.g. deactivation of short circuit to earth monitoring, active parallel indicator output
on the module BX-AIM etc.)
B4-DAI / DXI2 (B6-X1, B6-X1F) B3-DAI2 / B4-DAI2 / DXI2 (B6-X2)
 Loop x (x = 1..2), Log.No.

It can be configured whether the relevant loop should be available and what logical number it should have.
 Line x (x=1..4), Log.No.

It can be configured, whether the relevant loop should be operated as a stub. The Log.No. then refers to the
stub line number.
 Detector zones
A range of numbers for elements of the type "detector zone" are determined for each loop (e.g. 1-10 or 11-
20). The assignment of addresses to the detectors is carried out later during the commissioning process us-
ing LoopAssistant, however, during the addressing stage, the user is only able to select from the range of
numbers set out in this menu point. The formation of detector zones which span across multiple loops as
well as subcontrol units is allowed, i.e. the detectors of a detector zone can both be part of different loops as
well as different subcontrol units. When using modules (BX-AIM, BA-OI2, BA-OI3) it should be taken into
consideration whether the modules should behave later as a detector or as a detector zone (is defined during
commissioning using LoopAssistant). In this instance, this must be taken into consideration when assigning
the range of numbers. It is recommended to choose the ranges of numbers in such a way, that there are
enough free numbers available on this loop for possible subsequent extensions, thereby ensuring the con-
figuration does not require altering using Integral Listgenerator.
 Inputs
A range of numbers for elements of the type "input" are determined for each loop (e.g. 151-160). The as-
signment of addresses to the modules is carried out later during the commissioning process using LoopAs-
sistant, however, during the addressing stage, the user is only able to select from the range of numbers set
out in this menu point. It is recommended to choose the ranges of numbers in such a way, that there are
enough free numbers available on this loop for possible subsequent extensions, thereby ensuring the con-
figuration does not require altering using Integral Listgenerator.
 Outputs Type 1 (COM81)

This menu point only applies for the COM81 input/output module (found in old installations and no longer
shipped). A range of numbers is assigned for elements of the type “Output” (e.g. 151-155) for each loop.
The assignment of addresses to the modules is carried out later during the commissioning process using
LoopAssistant, however, during the addressing stage, the user is only able to select from the range of num-
bers set out in this menu point. It is recommended to choose the ranges of numbers in such a way, that
there are enough free numbers available on this loop for possible subsequent extensions, thereby ensuring
the configuration does not require altering using Integral Listgenerator.

 Outputs Type 2 (OI2, OI3, REL4, FOL)

A range of numbers is assigned for elements of the type “Output Type 2” (e.g. 160-180) for each loop. The
assignment of addresses to the modules is carried out later during the commissioning process using
LoopAssistant, however, during the addressing stage, the user is only able to select from the range of num-
bers set out in this menu point.
The module OI2 or OI3 is preferably used for controlling special detectors, in this instance, however, a de-
tector address is assigned to the module at a later point during the commissioning process using LoopAssis-
tant. The address must therefore be assigned in the "detector zone" menu point and not in the “Output”
menu point. It is recommended to choose the ranges of numbers in such a way, that there are enough free
numbers available on this loop for possible subsequent extensions, thereby ensuring the configuration does
not require altering using Integral Listgenerator.
 Outputs Type 3 (IOM)

A range of numbers is assigned to an element of the type “Output Type 3” (e.g. 181-190) for each loop. The
assignment of addresses to the module is carried out later during the commissioning process using LoopAs-
out in this menu point.
 Outputs Type 4 (SOL)

A range of numbers is assigned to an element of the type “Output Type 4” (e.g. 151-154) for each loop. The
assignment of addresses to the module is carried out later during the commissioning process using LoopAs-
out in this menu point.
 Flash frequency (1, 2)

Two flash frequencies which are independent of one another can be programmed with an impulse as well as
a pause in a range from 1 sec to 15.50 minutes. These flash frequencies can then be assigned during the as-
signment of logical properties (view 2) to one of the outputs controlled by this module in the “Output con-
figuration” dialogue panel.
Loop detector zones can be configured across multiple loops. This should, however, only be
done in extenuating circumstances (e.g. for manual call points in stairwells).

4.4.11 B3-MTI8 Monologue Technology Module

The Integral module B3-MTI8 (Monolog Transmission Interface 8 Lines) is used for connecting up to eight
stub lines, which can either be programmed as detector zones or as monitored inputs. The operating mode of
the individual stub lines can be set independently of one another using jumper caps on the module.
The module therefore contains two possible element types (detector zones and inputs), which are then subdi-
vided into so-called subelement types (e.g. Monolog, Beam Ardea, ...). Every line can be assigned one subele-
ment type.
 Line x (x = 1..8): It can be configured, what subelement type is connected to the stub line. The following
types of subelement types can be selected:
 None  Beam Mini-Boom  SecuriStar 521
 Monologue  Input  Series 130/A without
 Beam Ardea  VdS Interface Prealarm
 FM U7698B  Input DFG-60 BLK3  SecuriStar 521 without
 RAS TITANUS 1000  Valve Monitoring Prealarm
 RAS AD1-F  Primary Input  SLR-E-IS
 Beam SPB-E  Series 130/A  DCD-1E-IS
 Beam SPA-E  Series 130 Ex-i
 Log.No.
The Log.No. indicates the stub number. The logical number may only occur once per element type in the
entire Integral subcontrol unit loop. If the option “not available” is chosen, then the field for entering the
logical device number is automatically blanked out.
Detector zones and inputs can be mixed in any order on a B3-MTI8 module. The use of different subtypes
of an element type per B3-MTI8 is not possible. However, several different subelement types can be used
per module.

For special detectors like beam detectors, flame detectors, smoke aspirating systems among others, there are
particular conditions that prevail, with regard to whether they can be combined on one and the same B3-
MTI8 module!
“DV special detectors” (directly supplied special detectors) and “EV special detectors” (externally supplied
special detectors are differentiated between. The following points must be observed in this regard:
 Different DV special detectors can not be operated in a mixed fashion on a single B3-MTI8 module.
In certain circumstances, several B3-MTI8 modules must be used.
 EV special detectors can be operated without restrictions in a mixed fashion on a single B3-MTI8
module.
In the planning stage, the following rules must be adhered to within a detector zone
 The operating modes may be combined in any way required

 It is only possible to use a single set of parameters for each operating mode. The number
of selected subtypes with the same parameters is immaterial.
 The Listgenerator has an automatic checking mechanism, so that incorrect programming
is not possible.
Operating mode Device types Parameter set

Monologue Technology Monologue 1
Beam Ardea 1
FM U7698B 1
RAS TITANUS 1000 1
RAS AD1-F 1
wire supplied Beam SPB-B 1
Special detectors Beam SPA-E 2
(Monologue Technology) Beam Miniboom 3
Input Input 1
VdS Interface 2
Valve Monitoring 2
Input DFG-60 BLK 3
Primary Input 3
Detector series 130 Series 130/A 1
Series 130 Ex-i 2
SecuriStar 521 1
Series 130/A without Prealarm 1
SecuriStar 521 without Prealarm 1
SLR-E-IS 1
DCD-1E-IS 1
Example: If the operating mode Input, with the subtype “VdS Interface" (parameter set 2) is programmed for
a module for a stub line, then for further stub lines on the same module, no further inputs with sub-
types with other parameter sets, e.g. “Primary Input” (parameter set 3) can be set. If such an input is
also required, then this input must be programmed on another B3-MTI8 module.

4.4.12 B3-IM8 Module for monitored inputs

The B3-IM8 Integral module (Input Monitored, 8 Lines) is equipped for connecting 8 detector zones or 8 pri-
mary inputs. The operating mode of the individual stub lines can be set independently of one another using
programming and jumper cap settings on the module.
The module therefore contains two possible element types (detector zones and inputs), which are then subdi-
vided into so-called subelement types (e.g. input, Beam Ardea, ...). Every line can be assigned one subelement
type.
 Line x (x = 1..8)
It can be configured which subelement type can be connected to the stub line.
The following types of subelement types can be selected:
 None  Series 130/A  SLR-E-IS

 Input  Series 130 Ex-i  DCD-1E-IS
 VdS Interface  SecuriStar 521  Sabotage line
 Input DFG-60 BLK3  Series 130/A without
 Series 130/52x ARE
 Valve Monitoring Prealarm
 Primary Input  SecuriStar 521 without
Prealarm
 Log.No.
The Log.No. indicates the stub number. The logical number may only occur once per element type in the
entire Integral subcontrol unit loop. If the option “not available” is chosen, then the field for entering the
logical device number is automatically blanked out.
Detector zones and inputs can be mixed in any order on one and the same B3-MTI8 module.

4.4.13 Stub line Module B3-LEE23 for 140 detector series

The B3-LEE 23 (Line Extension Unit(=Einheit) 23) component is used for supplying and monitoring up to
eight stub lines each containing a maximum of 30 HX140 series detectors.
A maximum of five modules of type B3-LEE 23 can be fitted in slots 2 to 9 of the module rack of a BMZ In-
tegral unit.
 Trend x (x = 1..2): Activate evaluation for Trend 1 and 2. The settings of the trend evaluation are only
restricted module. For the trend evaluation to happen, the threshold for Trend 1 or Trend 2 must be ex-
ceeded for the entire length of the query by one detector. Only after this time has elapsed is contamination
displayed on the control panel. If the value falls below the threshold value prior to the end of the time listed,
then the counter is reset and the time will start from zero again the next time the threshold value is ex-
ceeded.
 Contamination level: Entry for the significance of the contamination as an integer between 1 and 4.
 Length of query: Once the value that has been entered has been exceeded, then a contamination message is
indicated in the subcontrol unit. Valid input formats:
 from 10 min to 310 min in 10 min intervals
 from 1 h to 31 h in 1 h intervals
 Line: Selection of the desired stub line
 Detector zone: Entry of the detector zone number, with a maximum of 8 detector zones per stub line
 Detectors: Enter the physical detector number (the address set on the detector in the correct physical se-
quence). An underscore is used as a placeholder for gaps, so that it is possible to assign as many logical
numbers as are required.
The entries for the detector zones and detectors must correspond exactly to the precise hardware
configuration. If this is not the case, a module fault will be shown after the control panel is
started up. If there are alterations to the hardware configuration, the values must be modified and
the control panel reprogrammed.

4.4.14 B3-LEE24 loop circuit module for 150 detector series

The B3-LEE 24 Integral module (Line Extension Unit(=Einheit) 24) is used for supplying and monitoring up
to four loop circuits each containing a maximum of 127 detectors from the Hekatron HX140 series of detec-
tors.
A maximum of five modules of type B3-LEE 24 can be fitted in slots 2 to 9 of the module rack of a BMZ In-
tegral unit.
 Trend x (x = 1..2): Activate evaluation for Trend 1 and 2. The settings of the trend evaluation are only
restricted module. For the trend evaluation to happen, the threshold for Trend 1 or Trend 2 must be ex-
ceeded for the entire length of the query by one detector. Only after this time has elapsed is contamination
displayed on the control panel. If the value falls below the threshold value prior to the end of the time listed,
then the counter is reset and the time will start from zero again the next time the threshold value is ex-
ceeded.
 Contamination level: Entry for the significance of the contamination as an integer between 1 and 4.
 Length of query: Once the value that has been entered has been exceeded, then a contamination message is
indicated in the subcontrol unit. Valid input formats:
 from 1 h to 31 h in 1 h intervals
 Loop x (x=1..4): Select the desired loop circuit to activate it.
 Log.No.: Enter the logical loop number.
 Detector zone: Range of the logical numbers for this type of element, which should be reserved on the
corresponding loop.
 Outputs Type 1: Range of logical numbers for the control modules of type SBS157 and UAS159, which
should be reserved on the relevant loop.

4.4.15 B3-DCI6 DC technology module

The B3-DCI6 (Direct Current Interface, 6) module contains 6 lines (inputs), which are primarily intended for
connecting detector zones in DC technology, although dependent on the intended use the relevant selection
must be made. A line can also, if required, be operated as a monitored input.
 Line x (x = 1..6): It can be configured, what should be connected to the line. The following settings can be
made using the dropdown list:
 none Reserve, Element does not exist

 DC Line Normal DC technology detector zone with current increase evaluation
(560 Alarm, 11k Idle)
 DC Line Normal+ Ex 9004 DC Technology Detector Zone (560 Alarm, 11k idle)
with old Ex-Barrier
 DC Line Normal+ Ex Z487 DC Technology Detector Zone (560 Alarm, 11k idle)
with Ex-Barrier of type Z487 manufactured by the company
Pepperl&Fuchs
 DC Line invert DC technology detector zone with current decrease evalua-
tion (560 Alarm, 11k Idle)
 Input Monitored input with DC technology resistance values (560
Controlled, 11k Idle)
 VdS Interface Extinguishing inputs working on current intensifying princi-

ple
 Pressure gauge blocking valve Manometer blocking valve inputs working on current intensi-
fying principle
 Valve Monitoring Valve monitoring inputs working on current intensifying
principle
 Primary Input Primary inputs working on current intensifying principle
 Log.No.: Entry for the logical number of the detector zone or of the input.
 Evaluate detector range: Address evaluation from 0...9 using different resistance values activated over the
third wire (Z core).

4.4.16 B3-DTI2 Dialogue Technology Module

Integral module B3-DTI2 is used for supplying and monitoring up to two loops each with a maximum of 128
detectors and modules using Maxima dialogue technology.
If required, each of the two loop circuits can be split in to two stub lines. In such cases, a maximum of 64 de-
vices can be connected and managed per stub line.
 Loop 1 / Loop 2: Activating the loop circuit:
 Log.No.: Entering the logical loop/stub line number
 Stub operation (Stitch mode): If the loop circuit is operating in stub operating mode then this checkbox
must be activated.
 Detector zones: logical number range for detector zones which are permitted to be programmed on this
loop.
 Inputs: Logical number range for inputs on the B2-DI2 module.
 Outputs Type 1: Logical number range for controls on the B2-DOI2 module.
 Outputs Type 4: Logical number range for monitored controls on the B2-DOM module.
 Maximum no. of LEDs: The maximum number of alarm LEDs is entered. The default value for this input
field is 3. Only integers between 1 and 10 are permissible.
If more than three alarm LEDs have been configured, then a power consumption calculation
should be carried out accordingly.

4.4.17 B4-EIO input/output module

The B4-EIO module is a component of every Integral C SLZ/BLZ unit and can also be optionally fitted in the
free connection slot of every B4-BCU-A2x or B6-BCU-X2 main processor module (Integral C system).
 Line x (x = 1..10): It can be configured whether line x should be available and which logical number it
should have. Lines 1 to 10 can be programmed as inputs or detector zones as required. Monitored outputs
are assigned logical numbers.
 Log.No.: The logical line number or output number is entered here
 Output x (x = 1..8): It can be configured whether output x should be available and what logical number
(integers from 1 to 65534) it should have.
 Blink frequency (1, 2): The outputs of the B4-EIO module can be controlled either statically (constantly)
or intermittently. Two blink frequencies can be defined, which can then be subsequently assigned to outputs
1-8 of the B4-EIO.
 Keyswitch: Whether a key switch is being used on the EIP indicator panel, and what logical number the
input should have.
 Indicators: The parameters for an EIP external indicator panel can be set here.

4.4.18 B4-EIP Indicator Panel

The B4-EIP indicator panel is an LED indicator panel for indicating an extinguishing zone.
 Log.No.: Enter the logical number of the first indicator here.
 Inscription: Every indicator output can have a text assigned to it, which can then be exported (for printing
out the push-in strips for the LED indicator panel) through the Datei (File) menu "Paneeltexte expor-
tieren…” (Export panel texts).
all ... Activates all fields
none ... to deactivate all fields

4.4.19 B3-BAF / B4-BAF control module
The B3-BAF or B4-BAF (Basic Functions) module

contains the following functions of a fire alarm con-
trol panel:
 Fire Brigade Control Panel connection in accor-

dance with DIN 14661
 Connection of transmission equipment (main de-
tector)
 Connection of an alarm system (main siren)
 Interface for the MMI BUS for connecting exter-
nal devices e.g. B3-CIE operating panel with or
without a printer, fire brigade indicator panel as
well as B3-UIO universal I/O module.
The B3-BAF module can be connected to connection slots 2 to 9 of an Integral subcontrol unit, but when relay
modules are being used, a module of type B5-BAF, B5-MRI16, B3-BAF or B3-LPI auf must be fitted to con-
nection slot 9. The B4-BAF module must be fitted in the corresponding connection slot on the B4-main proc-
essor unit. Consequently no further extension module can be used on a B4 subcontrol unit.
 FBF parallel: It can be configured, whether a Fire Brigade Control Panel is connected to the module (e.g.
FBF2003 and Wiesmeier FBF0720 v7.0b) and what logical number it should have.
 Output 1 (Main detector): It can be configured whether monitored output 1 (OM1) should be available and
what logical number (integers from 1 to 65534) it should have. This output is intended for loads from 16Ω
to 1kΩ and is primarily intending for connecting transmission equipment to the fire brigade. The load ranges
of the output must be set using the jumpers on board the module according to the intended purpose of the
module.
 Output 2: It can be configured whether monitored output 2 (OM2) should be available and what logical
number (integers from 1 to 65534) it should have. This output is intended for loads from 16Ω to 1kΩ and is
primarily intending for connecting alarm system, e.g. the main siren. The load ranges of the output must be
set using the jumpers on board the module according to the intended purpose of the module.
 MMI – Bus: Per MMI Bus up to 8 external devices can be configured, although the number appearing on
the left edge of the selection field is the same as the physical address of the configured device. This physical
address must later be set on the device using a rotary switch during the installation and commissioning proc-
ess, although the physical order of the devices on the MMI Bus can be selected independent of the configu-
ration. Each device must also be assigned a logical number by using the “Edit...” menu point. With this
number the device is displayed and operated on the display of the fire alarm control panel. The system limits
with regard to the maximum quantity of devices must be observed.
 Module may be absent: This option can be individually activated for every MMI Bus device for the B4-
BAF or B3-BAF. Consequently there is no error message generated in the event the relevant MMI Bus de-
vice has been configured but is not connected.

 Service function can not be activated:

If this option is activated, then the function of the service pin is deactivated.
The following actions are triggered by removing the service pin:
 On the B3-BAF / B5-BAF monitored outputs OM1/2 go to IDLE

 On the B3-BAF or the B3-LPI the bistable relays on the modules B3-REL10, B3-REL16 and B3-
REL16E are frozen in their current state.
 On the BMZ Integral C & C1 the monitored outputs OM1/2 go to IDLE. The non-monitored outputs
are frozen in their current state.
 In the ServiceAssistant (electronic service pin) all monitored outputs on the B3-BAF, B5-BAF and B3-
OM8 go to IDLE. The bistable relays on the modules B5-MRI16, B3-REL10, B3-REL16, B3-REL16E,
and loop modules BA-REL4, BA-OI3 and BA-IOM are frozen in their current state. For the loop
modules, the fail-safe position is adopted if this parameter has been configured. From version 5.1 the
outputs on the loop modules are frozen independent of the fail-safe position.
The physical status of the relays will only revert to being the same as the logical state when the service
pin is pushed back in. This way it is possible to carry out logic tests on fire alarm devices, whilst the ser-
vice pin also acts as a way of preventing triggering devices unintentionally during maintenance work.
 Flash frequency (1, 2): Two flash frequencies which are independent of one another can be programmed
with an impulse as well as a pause in a range from 1 sec to 15.50 minutes. These flash frequencies can then
be assigned during the assignment of logical properties to one of the outputs controlled by this module in
the “Output configuration” dialogue panel.
How a B3-BAF can be updated to a B5-BAF is described in the chapter “Updating tot new
modules”.

4.4.20 B5-BAF / B6-BAF control module

The B5-BAF or B6-BAF(Basic Functions) module contains the following functions of a fire alarm control
panel:
 Fire Brigade Control Panel connection in accordance with DIN 14661

 Connection of transmission equipment (main detector)
 Connection of an alarm system (main siren)
 Controlling of relay modules B3-REL10, B3-REL16, B3-REL16E
 Interface for the MMI BUS for connecting external devices e.g. B3-CIE operating panel,
B5-CIE with or without a printer, fire brigade indicator panel as well as B3-UIO universal I/O module.
The B5-BAF module can be connected to connection slots 2 to 9 of an Integral subcontrol unit, but when relay
modules are being used, a module of type B5-BAF, B5-MRI16, B3-BAF or B3-LPI auf must be fitted to con-
nection slot 9. The B6-BAF module must be fitted in the corresponding connection slot on the B6-main proc-
essor unit. Consequently no further extension module can be used on a B6 subcontrol unit.
 FBF parallel: It can be configured, whether a Fire Brigade Control Panel is connected to the module
(FBF2003 and Wiesmeier FBF0720 v7.0b) and what logical number it should have.
 Output 1 (Main detector): It can be configured whether monitored output 1 (OM1) should be available
and what logical number (integers from 1 to 65534) it should have. This output is intended for loads from
16Ω to 1kΩ and is primarily intending for connecting transmission equipment to the fire brigade. The load
ranges of the output must be set by making a selection with regard to “Sensitivity of Fault Detection” ac-
cording to the intended purpose of the module.
 Output 2: It can be configured whether monitored output 2 (OM2) should be available and what logical
number (integers from 1 to 65534) it should have. This output is intended for loads from 16Ω to 1kΩ and is
primarily intending for connecting alarm system, e.g. the main siren. The load ranges of the output must be
set by making a selection with regard to “Sensitivity of Fault Detection” according to the intended purpose
of the module.
 Input 1 / Input 2: Input 1 and Input 2 are used to query galvanically isolated contacts. Input 1 is used as
the reply contact for unit MDL-F.

 MMI – Bus: Per MMI Bus up to 8 external devices can be configured, although the number appearing on
the left edge of the selection field is the same as the physical address of the configured device. This physical
address must later be set on the device using a rotary switch during the installation and commissioning
process, although the physical order of the devices on the MMI Bus can be selected independent of the con-
figuration. Each device must also be assigned a logical number by using the “Edit...” menu point. With this
number the device is displayed and operated on the display of the fire alarm control panel. The system limits
with regard to the maximum quantity of devices must be observed.
 Module may be absent: This option can be individually activated for every MMI Bus device for the B5-
BAF. Consequently there is no error message generated in the event the relevant MMI Bus device has been
configured but is not connected.
 Flash frequency (1, 2): Two flash frequencies which are independent of one another can be programmed
4.4.21 Remote operating panel B3-CIE / B5-MMI-CII
 Operating panel: Logical number of the operating panel
 Printer: Logical number of the operating panel printer
 FBF- parallel: Logical number of the fire brigade control panel, which is connected to the external operat-
ing panel.
 Properties: To select fire brigade control panels made by different manufacturers.
It should be ensured that B3-CIE (HighEnd) or B5-MMI-CII (MAP) operating panels can only
be connected to a B5-BAF or B6-BAF.

4.4.22 Universal Input/Output Module B3-UIO

The B3-UIO module is used to control floor plan and parallel indicator tableaux. The module is also used as an
input/output module located remotely away from the control unit for querying potential-free contacts, as well
as for controlling non-monitored horns, lamps, relays etc. The system connection is via the MMI-BUS.
 Master: Definition of the MASTER – B3-UIO module, which when several B3-UIO modules are intercon-
nected, prescribes the flashing rhythm of all LED outputs. e.g. 9/1 means connection slot 9 of the BAF and
MMI Bus device no. 1
 Indicators
The LED outputs of the B3-UIO module are described as being of the element type indicators.
Quantity: Quantity of indicators used (max. 56 + 8).
Alarm signal Activation of the B3-UIO module’s alarm signal output.
LEDBlink: Flashing frequency for the LED outputs for intermittent controlling.
Log. No. of 1.: Logical number of the first indicator on the B3-UIO module.
Acoustic fault signal Activation of the out for acoustic fault signals.
 Inputs
Quantity: Quantity of inputs used (max. 8 + 56).
Define The logical addresses of the inputs can be changed.
AB acoustic alarm inactive: AB acoustic alarm not used.
Acoustic AB UIO input 1: Must be activated, if the alarm or fault acoustic signal is activated on the B3-
UIO module is, otherwise it is not possible for a reset to be carried out. One
input is therefore reserved for the acoustic signal reset.
Indicator test inactive: Indicator test not used.
Indicator test UIO input 2: In order to be able to connect the indicators of the B3-UIO module, the B3-
UIO input 2 must be marked. The indicator test can be then be activated via
this input. All LEDs are then activated.
Indicator test operating Select the logical number of the control panel from which the reminder test
panel: can be activated. All LEDs are then activated.

 Outputs: Dialogue for definition of the logical numbering of the outputs of the B3-UIO module.
Quantity: Quantity of outputs used (max. 8).
OUTBlink: Flash frequency for intermittent controlling of outputs.
Define: The logical addresses of the outputs can be changed here.
B3-UIO Inputs
It is possible in this input window to change the logical input numbers of the B3-UIO.
B3-UIO Outputs
It is possible in this input window to change the logical output numbers of the B3-UIO.

4.4.23 Fire brigade indicator panel FAT – DIN14662

Input window for defining the hardware structure of the FAT-DIN14662.
 FAT-DIN 14662 Log.No.: Logical number of the fire brigade indicator panel
 FBF parallel Log.No.: Logical number of the German fire brigade control panel, which is connected to the
fire brigade indicator panel.
 Properties: To select fire brigade control panels made by different manufacturers.

4.4.24 External indicator panel for 4 extinguishing zones IPES

External LED indicator panel for 4 extinguishing zones.
 Flashing frequency: Blink frequency for the LED outputs (indicators)
 Flash synchronisation: Data about the B3-UIO card (Master) which should carry out the flash synchroni-
sation
 Indicators test: Entry about the operating panel from which an indicator test for the IPES can be carried
out by using the “Indicator test” button.
 Keyswitch: Entry of the logical number of the input used for the keyswitch.
 Numbering: Logical starting number for the indicator outputs.
 Sections: 1-2 corresponds to extinguishing zone indicator 1 and 2 etc.
 Inscription: Every indicator output can have a text assigned to it, which can then be exported (for printing

4.4.25 External indicator panel for 8 extinguishing zones IPEL

External LED indicator panel for 8 extinguishing zones.
 Blink synchronisation: Data about the B3-UIO card (Master) which should carry out the flash synchroni-
sation
 Indicators test: Entry about the operating panel from which an indicator test for the IPEL can be carried
 Keyswitch: Entry of the logical number of the input used for the keyswitch.
 Inscription: Every indicator output can have a text assigned to it, which can then be exported (for printing

4.4.26 External LED Indicator Panel for up to 32 detector zones EAT32
LED indicator panel for indication of alarm,

fault and disablement states for 32 detector
zones.
An automatic assignment of control criteria
for indicators (pairs of LEDs - one red LED
and one yellow LED) can be easily config-
ured on this panel.
Red LED: flashes in the event of an

alarm (alarm, silent alarm and
simulated alarm) in a detector
zone
Yellow LED: Flashes when there is a fault

and is permanently lit when a
detector zone is disabled.

 Flash synchronisation: Data about the B3-UIO card (Master) which should carry out the flash synchronisa-
tion (The first B3-UIO card attached to the EAT is the default setting)
 Indicators test: Entry about the operating panel from which an indicator test for the EATxx can be carried
 Assistant for automatic assignment:
DZ areas: By entering detector zone numbers it is possible to automatically assign the de-
tector zones to the individual LED pairs. A single detector zone or a from/to
detector zone range can be entered. “-” and “,” should be used as a separator.
UZ: Slave control unit number in a SecoNET Network.
 Remove assignments:
All automatic: all automatically generated entries are removed
all manual: all manually generated entries are removed
In both instances the contents of the descriptive fields are also deleted!
 Manual assignment in a section:

all: The indicator outputs are automatically assigned. If there are unused indicators
in a section, then they are activated.
None: Deletes the manual assignments

4.4.27 External LED Indicator Panel for up to 64 detector zones EAT64
LED indicator panel for indication of alarm,

fault and disablement states for 64 detector
zones. An automatic assignment of control
criteria for indicators (pairs of LEDs - one
red LED and one yellow LED) can be easily
configured on this panel.
Red LED: flashes in the event of an

alarm (alarm, silent alarm and
simulated alarm) in a detector
zone
Yellow LED: Flashes when there is a fault

and is permanently lit when a
detector zone is disabled.

 Flash synchronisation: Data about the B3-UIO card (Master) which should carry out the flash synchroni-
sation (The first B3-UIO card attached to the EAT is the default setting)
 Indicators test: Entry about the operating panel from which an indicator test for the EATxx can be carried
 Assistant for automatic assignment:
DZ areas: By entering detector zone numbers it is possible to automatically assign the
detector zones to the individual LED pairs. A single detector zone or a
from/to detector zone range can be entered. “-” and “,” should be used as a
separator.
UZ: Slave control unit number in a SecoNET Network.

 Remove assignments:
All automatic: all automatically generated entries are removed
all manual: all manually generated entries are removed
In both instances the contents of the descriptive fields are also deleted!
 Manual assignment in a section:

all: The indicator outputs are automatically assigned. If there are unused indica-
tors in a section, then they are activated.
None: Deletes the manual assignments

4.4.28 Relay module B3-REL16

The B3-REL16 (Relay Output, 16) onboard module consists of 16 freely programmable bistable 24 V / 3 A
outputs. The relays are either controlled by the module B3-BAF, B5-BAF, B5-MRI16 or B3-LPI, must always
be fitted in connection slot 9.
 Output x (x = 1.0.16): It can be configured whether output x should be available and what logical number
Relay module B3-REL16E is identical to module B3-REL16 in terms of technical specifications

and function, but, however, also contains additional relay contacts and resistors (3.3kΩ monitor-
ing resistance and 680 Ω working resistance) for use as a VdS extinguishing interface. Using
jumpers it is possible to choose between normal relay contacts and VdS interfaces.
4.4.29 Relay module B3-REL10

The B3-REL10 (Relay Output, 10) onboard module consists of 10 freely programmable bistable 230 V / 3 A
outputs. The relays are either controlled by the module B3-BAF, B5-BAF, B5-MRI16 or B3-LPI, must always
be fitted in connection slot 9.
 Output x (x = 1..10): It can be configured whether output x should be available and what logical number

4.4.30 B5-MRI16 Multifunction relay module

The B5-REL16 module contains 16 bistable, freely programmable 24 V/3 A relay contacts. The B5-MRI16
module can be fitted in connection slots 2 to 9 of an Integral subcontrol unit. When using relay modules, how-
ever, one unit of type B5-BAF, B5-MRI16, B3-BAF or B3-LPI must be fitted in connection slot 9.
 Flash frequency (1, 2): Two flash frequencies which are independent of one another can be programmed
4.4.31 REL5 Onboard relay module

The REL5 (Relay Output, 5) onboard module consists of 5 freely programmable bistable 230 V / 3 A outputs.
The relay is controlled by the B6-X2-BCU module.

4.4.32 B4-REL6 Onboard relay module

The B4-REL6 (Relay Output, 6) onboard module consists of 6 freely programmable bistable 230 V / 3 A out-
puts. The relay is controlled by the B4-BCU A2 module.
4.4.33 B3-OM8 Module for monitored outputs

The B3-OM8 (Output Monitored, 8) module contains 8 freely programmable monitored outputs for a load
range from 16 Ω to 1 kΩ. The load ranges of the output must be set using the jumpers on board the module
according to the intended purpose of the module.
 Flash frequency (1, 2): Two flash frequencies which are independent of one another can be programmed

 Servicefunction not activateable:

If this option is activated, then the function of the service pin is deactivated.
By removing the service pin:
 On the B3-OM8, the monitored outputs OM1 - OM8 go to IDLE

 In the ServiceAssistant (electronic service pin) all monitored outputs on the B3-BAF, B5-BAF and
B3-OM8 go to IDLE. In this state the bistable relays on the modules B5-MRI16, B3-REL10, B3-
REL16, B3-REL16E, as well as loop modules BA-REL4, BA-OI3 und BA-IOM are frozen in their
current state. For the loop modules, the fail-safe position is adopted, if this has been configured.
From Integral Software Pack version 5.1 the outputs on the loop modules are frozen independent
of the fail-safe position. The physical status of the relays will only revert to being the same as the
logical state when the service pin is pushed back in. This way it is possible to carry out logic tests
on fire alarm devices, whilst the service pin also acts as a way of preventing triggering devices unin-
tentionally during maintenance work.

4.4.34 B3-LPI Subcontrol Unit Coupling

The B3-LPI (Loop Interface) module consists of 2 RS485 interfaces and is primarily intended for the network-
ing of Integral subcontrol units (SCUs) into a subcontrol unit loop (SCU loop). As well as a connection slot for
a PCMCIA modem for RemoteAccess use, the module also contains an interface for controlling relay modules
B3-REL10 and B3-REL16. The module can be fitted in connection slots 2 to 9 of an Integral subcontrol unit.
To use relay modules when using the B3-LPI module, the B3-LPI must be fitted to connection slot 9.
 Loop 0A/0B It is possible to configure whether the interface is active and what purpose it should be used
for. The following settings can be made using the dropdown list:
<none>: no selection is made, interface inactive
LoopApplication: Protocol for networking SCUs to form an SCU loop
ZZK-Protocol: Protocol for connecting a SC unit, or a SC unit loop as a slave control unit to a
BMZ Maxima, MCT or other superordinated system, which supports the ZZK
protocol. Single detector operation can be activated as an additional option for
the superordinated system for Integral loop technology. Further project-specific
settings can be made for the ZZK protocol.
Integral Standard Proto- Protocol for connecting a subcontrol unit or subcontrol unit loop to a superordi-
col: nated management system. Further project-specific settings can be made for the
ISP protocol.
SecoNET connection The BMZ Integral is connected to the SecoNET network using the SecoNET
connection. For this purpose, communications modules B3-USI4, B3-LPI and
B4-USI can be used. Additionally, the interface, bit rate and parity must be con-
figured for the connection to the neighbouring nodes in the SecoNET (it should
always be ensured in so doing, that port A of one node is always connection to
port B of the neighbouring node). The SecoNET topology does not require set-
ting. A BMZ Integral can only be connected to the SecoNET network in one
location. The SecoNET connection can consequently therefore only be set once
per BMZ Integral.

SecoNET-Repeater: The SecoNET repeater can be used to add one the BMZ Integral’s communica-
tions modules to the SecoNET network. For this purpose, communications
modules B3-USI4, B3-LPI and B4-USI can be used. The SecoNET repeater does
not connect the BMZ Integral to the SecoNET. On a SecoNET repeater, the
interface, bit rate and parity must be configured for the connection to the
neighbouring nodes in the SecoNET (it should always be ensured in so doing,
that port A of one node is always connection to port B of the neighbouring
node). The SecoNET topology does not require setting.
 Loop 1A/1B, Loop 0A: It can be configured whether the PCMCIA modem slot is used for the RemoteAc-
cess function. The following settings can be made using the dropdown list:
Integral RemoteAccess: The complete configuration of the RemoteAccess is contains in the chapter Re-
moteAccess.
The information about the configuration of individual modules is described in
this chapter.
 Set…: Using the Set... command, the parameters for the required operating mode can be configured.
 Properties: Preset settings can be selected from the dropdown list for the relevant operating mode. Please
contact technical support if you have any questions.
 Flash frequency (1, 2): Two flash frequencies which are independent of one another can be programmed
 Service function can not be activated: If this option is activated, then the function of the service pin is
deactivated.
By removing the service pin:
 On the B3-LPI the bistable relays on the modules B3-REL10, B3-REL16 and B3-REL16E are fro-
zen in their current state.
 In the ServiceAssistant (electronic service pin) all monitored outputs on the B3-BAF, B5-BAF and
B3-OM8 go to IDLE. In this state the bistable relays on the modules B5-MRI16, B3-REL10, B3-
REL16, B3-REL16E, as well as loop modules BA-REL4, BA-OI3 und BA-IOM are frozen in their
current state. For the loop modules, the fail-safe position is adopted, if this has been configured.
From version 5.1 the outputs on the loop modules are frozen independent of the “fail-safe posi-
tion”.
The physical status of the relays will only revert to being the same as the logical state when the ser-
vice pin is pushed back in. This way it is possible to carry out logic tests on fire alarm devices,
whilst the service pin also acts as a way of preventing triggering devices unintentionally during
maintenance work.

4.4.35 Universal Communications Module B3-USI4

The B3-USI4 (Universal Serial Interface, 4) module contains 4 serial interfaces (either RS485, RS422 or RS232)
and is intended on the one hand for networking of Integral subcontrol units (SCUs) to form a subcontrol unit
loop (SCU loop)as well as (simultaneously) forming a connection to other fire alarm control panels or foreign
systems such as printers, pagers, telephony controllers and above all management systems. The module can be
fitted in connection slots 2 to 9 of an Integral subcontrol unit.
 Line/Loop 0A/0B: It is possible to configure whether the interface is active and what purpose it should be
used for. The interface types RS232, RS422 or RS485 can be selected. The following settings can be made
using the dropdown list:

RingApplication: Protocol for networking SCUs to form an SCU loop
Printer: Protocol for serial connection of a printer. Printers that have already been tai-
lored for this purpose can be selected, with it also being possible to make further
project-specific settings for the serial protocol.
SSI Protocol: Protocol for connection to a superordinated SAT management system. If you
plan to use this, please contact Technical Support beforehand. Further project-
specific settings can be made for the SSI protocol.
SPP drivers: Dialogue panel for defining the interface type for the SPP driver. Serial printers,
pagers or the SMS box are connected using the SPP interface. The interface pa-
rameters must be adapted in accordance with the requirements of the interface of
the connected device.
ISP protocol.

per BMZ Integral.
moteAccess.
this chapter.
 Line/Loop 1A/1B: It is possible to configure whether the interface is active and what purpose it should be
used for. Dependent on the settings for Line/Loop 0A/0B not all the protocols listed hereafter are available
in the drop down list. The interface types RS422 or RS485 can be selected. The following settings can be
made using the dropdown list:

plan to use this, please contact Technical Support beforehand. Further project-
specific settings can be made for the SSI protocol.
ISP protocol.
per BMZ Integral.

moteAccess.
this chapter.
4.4.36 Universal Interface Module B4-USI

The B4-USI (Universal Serial Interface) module contains 2 serial interfaces (either RS485, RS422 or RS232) and
is intended on the one hand for networking of Integral subcontrol units (SCUs) to form a subcontrol unit loop
(SCU loop)as well as forming a connection to foreign systems such as printers, pagers, telephony controllers
and above all management systems.
 Line/Loop 0A/0B: It is possible to configure whether the interface is active and what purpose it should be
used for. The interface types RS232, RS422 or RS485 can be selected. The following settings can be made
using the dropdown list:

ZZK-Protocol: Protocol for connecting a SC unit, or a SC unit loop as a slave control unit to
a BMZ Maxima, MCT or other superordinated system, which supports the
ZZK protocol. Single detector operation can be activated as an additional
option for the superordinated system for Integral loop technology. Further
project-specific settings can be made for the ZZK protocol.
Printer: Protocol for serial connection of a printer. Printers that have already been
tailored for this purpose can be selected, with it also being possible to make
further project-specific settings for the serial protocol.
plan to use this, please contact technical support in Sulzburg beforehand.
Further settings can be made for the SSI protocol.
SPP drivers: Defining the interface type for the SPP driver.
Serial printers, pagers or the SMS box are connected using the SPP interface.
The interface parameters must be adapted in accordance with the require-
ments of the interface of the connected device.
Integral Standard Protocol: Protocol for connecting a subcontrol unit or subcontrol unit loop to a su-
perordinated management system. Further project-specific settings can be
made for the ISP protocol.
SecoNET connection The BMZ Integral is connected to the SecoNET network using the
SecoNET connection. For this purpose, communications modules B3-USI4,
B3-LPI and B4-USI can be used. Additionally, the interface, bit rate and
parity must be configured for the connection to the neighbouring nodes in
the SecoNET (it should always be ensured in so doing, that port A of one
node is always connection to port B of the neighbouring node). The
SecoNET topology does not require setting. A BMZ Integral can only be
connected to the SecoNET network in one location. The SecoNET connec-
tion can consequently therefore only be set once per BMZ Integral.
SecoNET-Repeater: The SecoNET repeater can be used to add one the BMZ Integral’s commu-
nications modules to the SecoNET network. For this purpose, communica-
tions modules B3-USI4, B3-LPI and B4-USI can be used. The SecoNET
repeater does not connect the BMZ Integral to the SecoNET. On a
SecoNET repeater, the interface, bit rate and parity must be configured for
the connection to the neighbouring nodes in the SecoNET (it should always
be ensured in so doing, that port A of one node is always connection to port
B of the neighbouring node). The SecoNET topology does not require set-
ting.
Integral RemoteAccess: The complete configuration of the RemoteAccess is contains in the chapter
RemoteAccess.
The information about the configuration of individual modules is described
in this chapter.
 PC Card: A PCMCIA Modem can be configured for the Integral RemoteAccess function. The following
settings can be made using the dropdown list:

Integral RemoteAccess: The complete configuration of the RemoteAccess is contains in the chapter
RemoteAccess.
The information about the configuration of individual modules is described
in this chapter.

4.4.37 Reserve
The Reserve module, is used to reserve a connection slot as a placeholder for further extensions to the control
unit topology. The reserve is also frequently used for the B3-HFI interface converter module.
In the comments text field, an information text can be entered.

Sample text: "This connection slot is reserved for a B3-USI4 module".
4.4.38 B3-HFI Interface Converter

The B3-HFI module is used to physically house as well as supplying buffered power to up to two optical fibre
data converters, with data transmission occurring via communications module B3-USI4. The connection to the
B3-USI4 module is made from the front side of the module rack by plugging in two connection cables. A
maximum of four B3-HFI modules can be fitted in connection slots 2 to 8 of the module rack (and in slot 9
too if no relays require controlling). During the configuration process, it should be ensured that a connection
slot next to the B3-HFI is fitted with a B3-USI4 module. The B3-HFI does not require any software support
for configuration.

4.4.39 Subcontrol unit connection

Definition of the properties of a subcontrol unit connection.
 Connection type: Defines the connection type. It is possible to choose between a direct connection (using
cable-based connections) and a modem connection. Ask support about tested modems.
 Bit rate: In the event of sporadic connection faults due to poor line quality, the bit rate can, if required, be
altered. (default = 57600 Bit/s).
 Interface type: The subcontrol units can either be connected to one another using a redundant connection
(2 cables, then RS485 redundant) or a simple connection (1 cable then RS485).
Depending on the connection type and module used, it is possible to select between different types of inter-
face (RS232, RS422 and RS485).
4.4.40 Issuing logical device numbers

Every element of a subcontrol unit (SCU) as well as of a subcontrol unit loop (SCU loop) must be uniquely
identifiable, i.e. a logical number can only be assigned a maximum of one time per element. In Listgenerator,
there is the possibility to determine the autonumbering properties of logical element numbers.
 From Log. No.: The chosen settings apply from this number.
 Fill empty spaces: If there are gaps in the sequential numbering of an element, then they are filled by the
autonumbering routine during the next fitting process.
 Append: The autonumbering process between with the highly already issued logical number of an element
at the next fitting process.

4.4.41 Update to new modules – upgrade module

The updating of old modules to new modules (upgrading modules) is explained with an example using the follow-
ing steps:
 First the fitting level of the Integral must be opened.

 Then select the new module (e.g. if a B3-BAF module should be upgraded to a B5-BAF, then the B5-BAF
module symbol should be selected).
 Next click on the fitted B3-BAF module.
The following confirmation window is opened:
 The action must be carried out by clicking on OK.

 Then the B3-BAF is removed from the system and replaced by a B5-BAF. The B5-BAF automatically inher-
its all the B3-BAF’s settings.

4.4.42 Update to a new control unit – upgrade control unit

When renovating old systems, or when extending existing systems, there may be a need to change the type of
control unit. In order to not have to completely reprogram an Integral or Integral C, there is an option in List-
generator to upgrade the control unit. When updating (upgrade control unit) a control unit, the following steps
must be followed:
 First open level 1.

 Then right click with the mouse on the control unit which needs to be upgraded (for example an Integral C1
should be upgraded to a B5 Integral).
 In the selection window, select the control unit type to which the unit should be upgraded to. The possible
selections in the window are dependent on the type of control unit to be upgraded.
 After selecting the control unit to which the control unit should be upgraded, the following confirmation
window opens:
 The action must be carried out by clicking on OK.

 The control unit is now upgraded to the selected control unit type.

When upgrading from control units, the following points must be observed:
B4 Integral C1
When upgrading a B4 Integral C1 to a B4 Integral C, then the B4-DAI with a single loop auto-
matically becomes a B4-DAI2 with two loops.
When upgrading a B4 Integral C1 to a B6 Integral C, then the B4-DAI with a single loop auto-
matically becomes a DXI2 with two loops, and the B4-BAF becomes a B6-BAF automatically.
Moreover, the B4-MCU32 becomes a B6-MCU32.
When upgrading an Integral C1 to an Integral the B4-BAF automatically becomes a B5-BAF,
and the B4-DAI with a loop automatically becomes a B3-DAI2 with two loops. Depending on
the selected Integral control unit, a B4-MCU32 becomes a B3-MCU32 or a B5-MCU32.
When upgrading a B4 Integral C1 to a B6 Integral C1/C1F the B4-BAF automatically becomes
a B6-BAF, and the B4-DAI with a loop automatically becomes a B3-DAI2 with one loop.
Moreover, the B4-MCU32 becomes a B6-MCU32.
B4 Integral C
When upgrading a B4 Integral C to a B6 Integral C the B4-BAF automatically becomes a B6-
BAF, and the B4-DAI with a loop automatically becomes a DXI2 with two loops. Moreover,
the B4-MCU32 becomes a B6-MCU32.
When upgrading an Integral C to an Integral the B4-BAF automatically becomes a B5-BAF, and
the B4-DAI with a loop automatically becomes a B3-DAI2 with two loops. The REL6 is auto-
matically replaced by a REL10 when upgraded. Depending on the selected Integral control unit,
a B4-MCU32 becomes a B3-MCU32 or a B5-MCU32.
Integral B3
When upgrading a B3 Integral to a B5 Integral, the B3-BAF automatically becomes a B5-BAF,
and the B3-MCU32 automatically becomes a B5-MCU32. The B3-PSU5 is automatically re-
placed by a B5-PSU when upgraded.
B6 Integral C1
When upgrading a B6 Integral C1 to a B6 Integral C, then the DXI2 with a single loop auto-
matically becomes a DXI2 with two loops. Moreover, a REL5 is added.
When upgrading a B6 Integral C1 to a B6 Integral C1F, an REL5 is added.
When upgrading an Integral C1 to an Integral the B6-BAF automatically becomes a B5-BAF,
and the DXI2 with a loop automatically becomes a B3-DAI2 with two loops. Moreover, a
REL10 is added. Moreover, the B6-MCU32 becomes a B5-MCU32.
B6 Integral C1F
When upgrading a B6 Integral C1F to a B6 Integral C, then the DXI2 with a single loop auto-
matically becomes a DXI2 with two loops.
When upgrading an Integral C1F to an Integral the B6-BAF automatically becomes a B5-BAF,
and the DXI2 with a loop automatically becomes a B3-DAI2 with two loops. The REL5 is
automatically replaced by a REL10 when upgraded. Moreover, the B6-MCU32 becomes a B5-
MCU32.
B6 Integral C
When upgrading an B6 Integral C to an Integral, the B6-BAF automatically becomes a B5-BAF,
and the DXI2 with two loops automatically becomes a B3-DAI2 with two loops. The REL5 is
automatically replaced by a REL10 when upgraded. Moreover, the B6-MCU32 becomes a B5-
MCU32.
It should be noted that an Integral C with a B4-USI or a B4-EIO can not be upgraded to an
Integral. In this instance, the B4-USI or B4-EIO must first be deleted by hand, and after the
upgrade, the functions must be added using the relevant modules in the Integral.

Integral Listgenerator  Protocols
4.5 Protocols
In this chapter, all the protocols are described, which are available when configuring the Integral.
4.5.1 PPA ZZK

The ZZK protocol defines the ZZK interface for the connection of a BMZ Integral as a slave control unit (SC)
to a BMZ Maxima as master control unit (MCU).
 Logical Number: Logical Number of the superordinated system, and is assigned as an element of the type
“Master system”.
 Slave control unit number (0..99): Slave control unit number of the subcontrol unit or the subcontrol unit
loop for the connection to a MaxNet (0 = Standard-MaxNet, 1-99 = Enhanced MaxNet).
 Bit rate: The Bit rate is set to 9600 bit/s as standard, with a reduction in the bit rate leading to an improve-
ment in the event of connection problems as a result of poor quality cabling. The parity is always even. The
data format is thereby always: 1 start bit, 8 data bits, 1 parity bit and 1 stop bit.
 Repeat time: The repeat time is the waiting time for acknowledging messages by the superordinated system.
For the connection to a BMZ Maxima or MCT4 a value of 30 ms must be set. A value of 200 ms is recom-
mended for other superordinated systems. If a repeat time that is not long enough is selected and the su-
perordinated system acknowledges the messages too slowly, this can lead to connection faults being indi-
cated. The value must be between 30 and 255 ms. This has a direct effect on the transmission rate.
 Interface type: The interface can be operated as either an RS232, RS485 or RS422 on the B3-USI4 module.
In addition hardware jumpering must be carried out on the module. Only RS485 operating mode is possible
on the B3-LPI module.
 Redundancy: The connection to the superordinated system can either redundant or non-redundant. Only a
redundant connection is possible on the B3-LPI module.

4.5.2 SAT SSI

The SSI protocol defines the interface for connection of the SAT management system. The interface parame-
ters must be adapted in accordance with the requirements of the interface of the control panel.
 Bit rate: The bit rate can be selected as necessary from a dropdown list (default = 2400 Bit/s).
 Interface type: The interface can be operated either as an RS232 or RS422. In addition hardware jumpering
must be carried out on the module.
4.5.3 SPP
The SPP driver defines the interface for connecting a serial printer, pager or the SMS box. The interface pa-
rameters must be adapted in accordance with the requirements of the interface of the connected device.
 Logical Number: Logical Number of the foreign device, and is assigned as an element of the type
“printer”.
 Parity The parity can be set, as required, to "even", "odd" or "none".
 Interface type: The interface can be operated either as an RS232 or RS422. In addition hardware jumpering
must be carried out on the module.

4.5.4 Integral Standard Protocol (ISP)

The ISP defines the interface for connecting a superordinated foreign system to a single BMZ Integral or any
foreign system to the SecoNET.
 Redundancy: The connection to the superordinated system can be either redundant (only for BMZ Inte-
gral) or non-redundant.
 Parity The parity can be set, as required, to “even” or “odd”.
 Interface type: The interface can be operated as either an RS232, RS485 or RS422 on the B3-USI4 module,
but hardware jumpering must also be undertaken on the module. Only RS485 operating mode is possible on
the B3-LPI module.

4.5.5 SecoNET connection

The BMZ Integral or Integral C is connected to the SecoNET network using the SecoNET connection. For
this purpose, communications modules B3-USI4, B3-LPI and B4-USI can be used.
 Management System LogNo: Defines the management system, which should be indicated when there is a
fault on the control unit’s display.
 Master control unit LogNo: Defines the master control unit, which should be indicated when there is a
fault on the control unit’s display.
 Connection type: Defines the connection type. It is possible to choose between a direct connection (using
 Bit rate: The bit rate can be selected as necessary from a dropdown list (default = 57600 Bit/s).
 Connection type: The interface can be operated as either an RS232, RS485 or RS422 on the B3-USI4 mod-
ule. In addition hardware jumpering must be carried out on the module. Only RS485 operating mode is pos-
sible on the B3-LPI module.

4.5.6 SecoNET Repeater

The SecoNET repeater can be used to add one the BMZ Integral’s communications modules to the SecoNET
network. The B3-USI4, B3-LPI, B4-USI are the communications modules used. The SecoNET repeater does
not connect the BMZ Integral to the SecoNET. On a SecoNET repeater, the interface (RS232, RS422, and
RS485), the bit rate and the parity must be set for the connection to adjacent nodes in the SecoNET network.
Port A of a node must always be connected with port B of the neighbouring port. The SecoNET topology does
not require setting.
 Connection type: Defines the connection type. It is possible to choose between a direct connection (using
 Connection type: The interface can be operated as either an RS232, RS485 or RS422 on the B3-USI4 mod-
ule. In addition hardware jumpering must be carried out on the module. Only RS485 operating mode is pos-
sible on the B3-LPI module.

Integral Listgenerator  Logical properties
4.6 Logical properties

The logical properties encompass all element types, which are configured in Integral Listgenerator on level 2.
4.6.1 Configuration settings for the detector zone element

Every detector zone must be assigned a detector zone macro.
 Detector zone macro: The selection of a detector zone macro, is compulsory to determine the functional
characteristic of the relevant detector zone. The type that can be found in the detector zone must be de-
fined.
 operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol
unit or links control units on a command level.
For example it is possible to define that the detector zone is only operational in a certain user level.
 Delay level: The function of detector zone can be different depending on whether there is day time or night
time operation. (e.g. daytime => delay / night => without delay).
If no delay level is selected, than the detector zone is basically in night time operation. To be able to select a
delay level, this must be defined beforehand.
 2 Detector Dependency: At least two detectors in the relevant detector zone must enter alarm state to
fulfil this criteria.

4.6.2 Configuration settings for the input element

The following parameters can be defined for each input element:
 Subtype: For the input concerned, two subtypes can be assigned:

 general
 extinguishing system
The subtypes can, e.g. be filtered using an aggregate criteria.
 operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol
unit or links control units on a command level. For example it is possible to define that the input is only op-
erational at the operating panel in a certain user level.
 Invisible: If this function is activated, then the state of the input in question, is neither indicated on the
display or by the log printer on the BMZ Integral, the input therefore being “invisible” to the outside world.
This function is used preferably, when the input in question is linked with external alarms or external faults.
 Invert input: It is accepted as standard that inputs are activated by make contacts (normally open). It is
however possible, by inverting the input in question, to activate it using a break contact (normally closed).

4.6.3 Configuration settings for the output element

The following parameters can be defined for each output element:
 Subtype: Every output can be assigned a so-called „subtype“ (e.g. main detector, main siren, smoke ventila-
tion,...). For messages which affect the output in question, this subtype is given as additional information on
the display and/or the log printer of the BMZ Integral.
 Operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol
unit or links control units on a command level. For example it is possible to define that the output is only
operational in a certain user level.
 Further settings:
Critical: If this option is activated then the print out of the system configuration will
contain the text “critical” for the relevant output.
Can be controlled again: Is used to automatically reactive the output in question once that output has
been reset from the operating panel or the fire brigade control panel e.g. in
the event of an alarm occurring again.
Key Switch dependent Outputs which have been assigned this function, are automatically disabled, if
(Alarm): the user at the operating panel changes to another user level than level 1 (key
switch position => blocked) The output in question can then neither be
triggered, nor operated by the user. The output is then automatically disabled
if there is no alarm present in the system.
Key Switch dependent (Con- Outputs which have been assigned this function, are automatically disabled, if
trol criteria): the user at the operating panel changes to another user level than level 1 (key
switch position => blocked) The output in question can then neither be
triggered, nor operated by the user. The output is then disabled automatically,
if the control criterion for this output is not active.
Reply signal: Must be activated, if the relevant controller for controlling a transmission
system with an optional reply line is used and this reply wire is connected to
the reply input of the relevant controller. (e.g. MDL-F)
Timeout: Information about how long is takes for the reply, if this period is exceeded,
then a fault is generated (maximum 5 minutes).

Active when disabled: This function is used, for example for holding magnet outputs, and has the
effect that the output in question is automatically triggered, if it was disabled
beforehand.
Break Contact: If this function is activated, then the output acts as break contact (normally
closed).
Active in fail-safe position: If this function is activated, then the output is always controlled, if:
 The control unit is powerless (mains and battery supply)
 A warm start is carried out (system reset)
 The control unit is changed over to the B side as a result of a
single error in the system
 If the output is on a loop (loop technology) and the loop loses
power.
Triggering in emergency op- If the System goes into emergency operation the output will be triggerd.
eration:
no OC-recognition on acti- This function configures the monitored outputs of the system Integral C/C1
vation (B6-BAF). If this function is activated, then the wire break detection is dis-
abled in the cause of the initiation of a primary output.
 Output configuration: The output configuration defines the standard output configuration for the output
(e.g. static or flashing). It is, for example, possible for an output to be defined, that flashes as standard when in
controlled state. The output configuration can still, however, be individually adapted for every control criteria,
if required. See Overwriting out configuration.
 Control criterion: If several control criteria have been defined, then priorities are used to define the order
(4 = lowest priority, 1 = highest priority).
 Boolean definition: The Boolean definition, which is selected, is used as a control criteria. This means that
is the Boolean definition is true, then the output is controlled.
Overwriting output configuration If this function is activated, then there is the opportunity to adapt the
output time limit, or to select the flashing frequency.
 Activation time limit:

None: The output is controlled until the criteria, which led to the output being trig-
gered, is no longer present again. (e.g. by alarm reset)
intern: Can be used for every output. There are 2 possibilities:
 Logical: The device is controlled for a set amount of time (e.g. 2
mins) if control criteria occur. The device is then automatically reset,
even if the control criteria are still present. The relevant device no
longer appears on the list of devices being controlled that appears on
the BMZ Integral Control panel immediately after the automatic re-
set process.
 Physical: The device is controlled for a set amount of time (e.g. 2
even if the control criteria are still present. Following the automatic
reset process the relevant device however remains in the list of de-
vices being controlled that appear on the BMZ Integral control panel
until the control criteria which caused the alarm to be triggered is no
longer present. (e.g. by alarm reset)

external: The external output time limit only works with loop module outputs. The
time is generated directly by the loop module controller and be chosen in the
range between 0.1 and 12 seconds. There are 2 possibilities:
 Logical: The device is controlled for a set amount of time (e.g. 1.1
secs) if control criteria occur. The device is then automatically reset,
even if the control criteria are still present. The relevant device no
longer appears on the list of devices being controlled that appears on
the BMZ Integral Control panel immediately after the automatic re-
set process.
 Physical: The device is controlled for a set amount of time (e.g. 2
even if the control criteria are still present. Following the automatic
reset process the relevant device however remains in the list of de-
vices being controlled that appear on the BMZ Integral control panel
until the control criteria which caused the alarm to be triggered has
been reset again (e.g. by means of an alarm reset).
 Output time limit:
Constant: The output is constantly controlled.
Flashing: The output is intermittently controlled with the previously set flash frequency
1 or flash frequency 2.
 Type of Sound: This parameter is only used by loop sirens (BA-SOL). There are different types of tone that
can be selected e.g. DIN tone.

4.6.4 Configuration settings for the external element

The following parameters can be defined for each external element:
 Operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol
unit or links control units on a command level. For example it is possible to define that the detector zone is
only operational in a certain user level.
 Alarm on:
Linked result: A previously defined Boolean definition can be selected. If this Boolean
definition is true, then an alarm is triggered at the fire alarm control panel.
Sum criterion: A previously defined sum criterion can be selected. If this sum criterion is
true, then an alarm is triggered at the fire alarm control panel.
States of the input: Inputs can be selected and their state defined. If one of the inputs enters the
defined state, then an alarm is triggered at the BMZ.
 Fault on:
Linked result: A previously defined Boolean definition can be selected. If this Boolean
definition is true, then a fault is triggered at the fire alarm control panel.
Sum criterion: A previously defined sum criterion can be selected. If this sum criterion is
true, then a fault is triggered at the fire alarm control panel.
States of the input: Inputs can be selected and their state defined. If one of the inputs enters the
defined state, then an alarm is triggered at the BMZ.

4.6.5 Configuration settings for the printer element

The following parameters can be defined for each printer element:
 Subtype: For the log printer concerned, three subtypes can be assigned:
 Remote printer
 General
 Operating panel printer
The subtypes can be filtered, for example, using a sum criterion.
 Disablement on Cold Start: When this function is activated, the printer remains disable for as long after a
new start, until the user turns it on again manually.
 Zone filters: Zone filters all specific subzones of elements available in a subcontrol unit or a group of con-
trol units, e.g. detector zones, outputs etc. to be drawn together. A zone filter can then for example be used
for restricting indicators on operating panels and printers, as well as for defining of sum criteria etc.
 Operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol
 Message filters: Message filters are used to permit or suppress the printing out of specific messages or
commands on operating panel printers or external printers. Every printer of a subcontrol unit or a group of
control units can be assigned up to 3 different message filters.

4.6.6 Configuration settings for the operating panel element

The following parameters can be defined for each operating panel element:
 Automatic change of operating level: When the operating level of more than 1, once an set period of
time (1 min – 12 hours) has expired, the operating level automatically switches to 1.
 Appearance: The appearance type of display indications can be selected in accordance with the Austrian or
German standard. The available section:
 Austria
 Germany
 Germany (VDS)
 Transmission equipment: Selection of the output (logical number) which is assigned to the transmission
equipment at the operating panel. The transmission equipment can be disabled via the button on the operat-
ing panel.
 Alarm system device: Selection of the output (logical number) which is assigned to the alarm systems field
at the operating panel. The output should be the logical number of the main siren. The main siren can be
disabled via the button on the operating panel.
 Alarm on Revision Alarm: If this function is activated, then revision alarms are also indicated by the group
alarm LED on the operating panel. The revision must be started from the operating panel. If the function is
started using ServiceAssistant, then the LED in the operating panel does not have a function.
 Buzzer silenced pressed:

Also reset sirens: Outputs which had been assigned to the subtype main siren or auxiliary siren,
are reset along with the internal acoustics of the BMZ Integral by pressing
the <Buzzer silenced> button on the operating panel of the BMZ Integral or
the Fire Brigade Control Panel.
Reset other operating panel If this function is activated, then the acoustics (internal and/or external) of
acoustics all operating panels of the relevant BMZ Integral or all operating panels in
the BMZ Integral control unit group is reset at the same time as soon as the
<Buzzer silenced> key is pressed at the relevant operating panel.

 Output to fire protection equipment:

BSE/BFS-LED on activa- It is possible to configure here, whether the LED for the “fire protection
tion equipment output” on the operating panel should light up when an output
that is configured with the subtype BSE/BFS is being controlled.
BSE/BFS-LED on fault: It is possible for the B3/B4-CII to configure here, whether the LED for the
“fire protection equipment fault” on the operating panel should light up
when an output that is configured with the subtype BSE/BFS has a fault.
 Zone filters: Zone filters all specific subzones of elements available in a subcontrol unit or a group of con-
 Authorisation: The authorisation structure can be defined for the relevant operating panel.
 Authorisation codes: The every user level, the numerical code (maximum eight digits) can be defined
which must be entered to swap to this level at the operating panel.
 Operable in user level: Using “edit” for every selected menu item it is possible to configure in which user
level the relevant menu point should be available.
 Authorisation macro:
As standard: The relevant operating panel serves exclusively as an indicating operating
panel in user level 1. This means that no commands can be sent to detector
zones or other element types from the control unit. In one of the higher user
levels (levels 2-8), then commands can be sent to detector zones or to other
element types.
Standard, intervention in The functions are identical with those of the “Standard” setting, but it is,
level 1: however, also possible in user level 1 to initialise an Intervention.

Non-operable: The relevant operating panel serves exclusively as an indication operating

panel. No commands can be sent to detector zones or other element types
from the control panel.
Non-operable, intervention The functions are identical with those in the “non-operable” setting, but it is,
possible: however, possible to initialise an Intervention.
 Change of authorisation without switch: If this function is not activated, then it is not possible to change
the authorisation level without a keyswitch.
A change of authorisation without using the switch must always be selected!
4.6.7 Configuration settings for the Battery element

The following parameters can be defined for each battery element:
 Battery exists: Must always be activated if rechargeable batteries are used to maintain the mains power sup-
ply in the event of a power failure.
 Battery test:
automatic check: Must always be activated, in order to check the batteries automatically
at the preset interval (standard setting: 15 min)
 Always display Log. No.:

Should always be activated, to allow the assignment of customer texts.
 Operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol

4.6.8 Configuration settings for the Mains element

The following parameters can be defined for each battery element:
 Fault message:
immediately: The fault message of the power failure is indicated immediately at the control
unit.
never: The fault message of the power failure is never indicated at the control unit.
delayed: The fault message of the power failure is indicated after a defined period of time
at the control unit.
 Always display Log. No.:

Should always be activated, to allow the assignment of customer texts.
 Operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol

4.6.9 Configuration settings for the Delay level element

The following parameters can be defined for each delay level element:
In order to define the day => night changeover times of a specific delay level, the days, on which an automatic
changeover should occur, should be selected. The changeover time must be entered as per the above example.
The BMZ Integral also supports the automatic changeover between night and day, but in this instance country-
specific regulations must always be observed.
 Changeover time:
Day  Night (absent): The switchover from day to night operation happens automatically.
Night  day (present): The switchover from night to day operation happens automatically.

4.6.10 Configuration settings for the Fire Brigade Control Panel element
It should be noted, that a maximum of 8 elements of type Fire Brigade Control Panel are supported per sub-
control unit.
This is because the Fire brigade display panels (FATs) and the fire brigade control panels (FBFs) share the Fire
Brigade Control Panel element type in Listgenerator. Either 8 FATs, 8 FBFs or 7 FATs and 1 FBF etc. can be
connected to the individual subcontrol unit.
This means that the FATs and FBFs share the logical number range 1-65534.
B3-MMI-FPA Fire Brigade Control Panel
 Level 1-8: Level 7 is normally always activated for a Fire Brigade Control Panel. If level 7 is not assigned to
a Fire Brigade Control Panel, then the test transmission equipment key does not work.
 Transmission equipment: No transmission equipment can be assigned to the FBF.
 Customer text:
1st line: It is possible to select between
 No text
 Customer text line
 FBF Text line
 FBF Text line
 Customer text pursuant to ÖNORM F3031
For example if „1st line customer text“ is selected, then in the first line of the FBF the text is shown, that is
also shown in the first line in the operating panel. It is therefore possible to adapt the FBF’s indications.

By selecting „1st line FBF Text“ or „2nd line FBF Text“ it is possible to create a display texts for the FBF,
which do not appear on the control unit’s operating panel. The texts for the 1st and 2nd line of the FBF text
are also generated in Integral Text Tool (Special text line 1 and special text line 2).
2. line: The same setting options apply as for the first line.
 Zone filters: Zone filters all specific subzones of elements available in a subcontrol unit or a group of con-
B3-MMI-FAT Fire brigade display panel
 Level 1-8: Standard setting is level 1. No configuration is necessary.
 Transmission equipment: The logical number of the transmission equipment is to be set that is to be dis-
abled, when the transmission equipment reset button is pressed on the FAT.
 Use alarm memory: By selecting this, the alarm memory is activated. The number (between 0 and 32) of
the alarm memory entries must then be determined.
After triggering the transmission equipment, all old messages in the memory are deleted and only
the current messages are shown!

 Customer text:
1. line: It is possible to select between
 No text
 FBF Text line
 FBF Text line
 Customer text pursuant to ÖNORM F3031
.
For example if „1st line customer text“ is selected, then in the first line of the
FBF the text is shown, that is also shown in the first line in the operating
panel. It is therefore possible to adapt the FBF’s indications.
By selecting „1st line FBF Text“ or „2nd line FBF Text“ it is possible to cre-
ate a display texts for the FBF, which do not appear on the control unit’s
operating panel. The texts for the 1st and 2nd line of the FBF text are also
generated in Integral Text Tool (Special text line 1 and special text line 2).
2. line: The same setting options apply as for the first line.
 Zone filters: Zone filters all specific subzones of elements available in a subcontrol unit or a group of con-

4.6.11 Configuration settings for the Indicator element

Indicators (outputs) are used to control low voltage LEDs. They are a separate element in their own right, start-
ing with logical number 100 and are controlled by a UIO card.
 Activation criterion 1, 2:
none: The indicator is not activated.
Link: The indicator is activated if the output criteria of the selected Boolean defini-
tion is true.
Group criteria: The indicator is activated, if the selected group criteria is true.
Element state: The indicator is activated if the output criteria of the previously selected
Boolean definition is true.
 Triggering:
Alarm criteria: It can be entered whether when activating the indicator whether an acoustic
alarm should also be activated.
Fault criteria: It can be entered whether when activating the indicator whether an acoustic
fault should also be activated.
 Output configuration: Here it is possible to set whether each indicator and each control criterion
should be activated constantly or intermittently (flashing). The frequency at
which the indicator flashes is generally set along with the UIO card’s parame-
ters. Control criterion 1 has a higher priority than control criteria 2. This
means that the output behaviour of control criterion 2 is overwritten by that
of control criterion 2.

It should be noted that when an acoustic alarm signal or acoustic fault signal is selected that the
first two outputs on the device are used as indicators and consequently are always assigned logi-
cal numbers x56 (for acoustic alarm signals) and x57 (for acoustic fault alarms).
Example Controlling Indicator 100 (fault criteria):

If the detector zone 101 is active, then indicator 100 and the fault acoustics are controlled.

Example Controlling Indicator 100 (fault criteria):

If detector zone 101 is active, then indicator 100 and the alarm acoustics are controlled.

4.6.12 Configuration settings for the Loop element
 Ground fault monitoring off: If a cross is entered, then the ground fault monitoring for the loop is deacti-
vated.
 AIM Option Operation(Alarm LED detector active): If conventional Hochiki detectors are used, then
the LED of the detector can be activated in the event of an alarm. This function is then valid for all AIM
modules which are used on the same loop.
 Delayed device fault: An error message only occurs after the device has been queried unsuccessfully 10
times (standard query = 2).
 Evaluate Signature alarm: The signature alarm is a special method for quickly testing an automatic detec-
tor. This function is available from MTD 533 detectors.
During the first, short time that the testing gas is blown into the detector, the detector immediately detects that the test is taking
place and shows this with a flashing LED. If a second blast of testing gas is then sprayed in, the detector momentarily activates
the alarm bit.
 Undervoltage detection active: Activated the MTD 533’s undervoltage bit, if the ring voltage is below a
defined value.
 Evaluate ageing bit: Activates the evaluation of the ageing bit in the MTD 533.
 Quick start-up: The detector recognition is then optimized on startup. For previous generations of detec-
tors it is recommended, if there are problems during startup, to deactivate the option.
 Alarm LEDs simultaneously active: It is possible to select between standard and Chinese standard. A
maximum of 2 alarm LEDs can be active per loop (detector LED and 1 external UPI is the equivalent to 1
LED).
 Operating macro: Operating macros are used, in order to restrict the operation of elements of a subcontrol
Every loop must always be assigned the loop operating macro.
 Delay input fault: A delay time for fault messages of monitored inputs which are on a loop can be pro-
grammed (e.g. inputs for sprinkler systems)

4.6.13 Parameter Settings for the RemoteAccess element

How a service call is defined is described in the documentation for setting up RemoteAccess / Service calls.
 Linked result: A previously defined Boolean definition can be selected. If this Boolean definition is true,
then the service phone call is triggered.
 Message filters: Message filters are used to permit or suppress the printing out of specific messages or
commands on operating panel printers or external printers. Every printer of a subcontrol unit or a group of
control units can be assigned up to 3 different message filters.
 Authorisation level: This determines from which user level RemoteAccess is allowed to be deployed from.
 Authorisation macro:
As standard: RemoteAccess serves exclusively as an indicating operating panel in user
level 1. This means that no commands can be sent to detector zones or other
element types from the control unit. In one of the higher user levels (levels
2-8), then commands can be sent to detector zones or to other element
types.
As standard: The functions are identical with those of the “Standard” setting, but it is,
intervention in level 1: however, also possible in user level 1 to initialise an Intervention.
Non-operable: RemoteAccess serves exclusively as an indicator panel. No commands can be

sent to detector zones or other element types from the control panel.
Non-operable, intervention The functions are identical with those in the “non-operable” setting, but it is,
possible: however, possible to initialise an Intervention.

Integral Listgenerator  Boolean definitions
4.7 Boolean definitions

Boolean definitions are used to, among other things, to trigger specific events (e.g. alarm from a specific detec-
tor zone, activation of an input, aggregate alarm, power supply fault etc.) query them in the BMZ Integral and
to trigger specific outputs. In the event that several events are being queried, they can be linked with one an-
other using logical gates, such as e.g. AND, OR, XOR; NOT, etc.
4.7.1 System thresholds of Boolean Definitions

When determining Boolean definitions as well as when using the necessary tools, the following system thresh-
olds must be observed:
per subcontrol
per subcontrol unit loop
unit
max. 512
Boolean definitions max. 512
(from Version 3.4.0)
Flip-Flop (RS-FF, D-FF) max. 256 max. 16 x 256
Counter max. 256 max. 16 x 256
Timer (Pulse, positive edge, nega-
max. 32 max. 16 x 32
tive edge, clock generator)
The time values that can be set differ from one application to another. Only certain time steps can be select for
the individual time ranges. When entering times outside the defined time ranges, a rounding automatically oc-
curs, and a suitable fault message in the event that the maximum permissible time is exceeded.
Time ranges Time intervals
0 - 3.1 sec 100 ms

4 sec – 31 sec 1 sec
40 sec - 5.1 min 10 sec
5.5 min to 15.5 min 30 sec
16 min – 31 min 1 min
40 min – 5 h 10 min 10 min
5.5 h – 15 h 30 min 30 min
16 h – 31 h 1h
Furthermore, it should be noted that a maximum 128 input criteria can be defined per Boolean definition.

4.7.2 Boolean Definition Selection window

If Boolean definitions have already been determined, then ones can be selected from the list of available ones,
or new ones created and edited.
 New: Definition of a new Boolean definition. An empty Boolean definition is opened.

 Edit: Edit the Boolean definition that is marked in the list.
 Edit Copy: Create a copy of the Boolean definition marked in the list and edit it. The Boolean definition,
from which the copy was created, is not changed in the process.
 Delete: Delete the selected Boolean definition.
 Reference: Displays the references to which the exist for the Boolean definition marked in the list. After
clicking the button, the outputs, to which the relevant Boolean definitions are assigned, are listed.
 The three buttons that are found in the bottom right of the window are used to import
and export Boolean definitions and to open and edit macro libraries.
After clicking on the „New“ button, the input window appears to create a Boolean definition. This is split
into 3 areas, for the input criteria, definition area and output criteria.

 Tool bar: The tool bar can undo or redo specific processes. Furthermore, additional columns and be
added or deleted.
 Toolbar: In the toolbar, as well as the connection, there are different logical gates for linking the input crite-
rion to the output criterion.
 Name: In the name field, the output criterion must be assigned a name, with which is can be selected from
the table for Boolean definitions. The name ideally describes the main function of the link.
 Input criterion: The input criteria (max. 128) are defined here. Input criteria are queries of specific events in
the BMZ. By double clicking on an empty field, a new input criterion can be created, or by double clicking
on an existing input criteria it can be edited. By marking and deleting, it is possible to remove an input crite-
rion.
 Columns: Columns are used (in the checked field) for the placing of the logic gates. They can be extended
as required (Menu "Column, Add") or removed again (Menu "Column, Delete"). The logical gates are used to link
the input criterion, whereby in the most simple case an input criterion is assigned directly to an output crite-
rion without recourse to logic gates. By selecting the logic gate in the toolbar (or the "Tools" menu) they can be
placed in the columns using drag and drop methods. With the help of the „Connect“ tool, the input criteria,
logic gates and the output criteria must be linked with one another using lines.
 Output criteria: The Boolean definition is assigned an output criterion. This Boolean definition delivers a
result (true or false) and can then be assigned to one or more outputs as so-called control criteria.
It must be ensured that all input criteria, the output criterion as well as inputs and outputs of
logic gate have a connection, as otherwise the Boolean definition is not complete.

4.7.3 Input criterion

The querying of a specific event (aggregate alarm) or element state (e.g. an alarm from a specific detector zone)
in the BMZ Integral is called an input criterion. If several input criteria are defined, than they can be linked with
the help of logic gates to a Boolean definition.
 Type: Constant
 Parameter: 0/false/low or 1/true/high
 Type: Element:
 Parameter:
Element type: Selection of the element type to be queried (detector zone, input, ... etc.)
Element no.: Logical number of the element to be queried
e.g.: Input = 1,4,7,10-15 => the query refers to the detector zones 1,4,7 and 10-15
simultaneously
Significance: Significance that should be queried (adopt standard setting)
Individual element: Possibility to query individual detectors (individual detector address) within the detector
zones
States: Definition of the element states to be queried
e.g. a detector zone is queried for alarms

Every element can be assigned element states. States are used e.g. as input criterion for Boolean definitions. The
list of states and their substates is different from one element type to the next.
 State: Definition of the element states to be queried e.g. a detector zone is queried for alarms
 Substate: For example an input is monitors for a fault state, and queries for a short circuit as a substate.
 Type: Sum criterion
 Parameter: A sum criterion can be chosen from the list as an input criteria for a Boolean definition.

 Type: Date / Time
 Parameter: With the help of the „Date / time“ input criterion, the system time of the BMZ Integral can be
queried and outputs triggered depending on date or time.
Month Month to be queried

Day: Calendar date to be queried
Weekday: Weekday to be
Hour: Hour to be queried
Minute: Minute to be queried
Note: „*“ means – there should be no query here
 Type: Command
 Parameter: With the help of querying of commands, it is possible to query keyboard operations.
Internal buzzer off: Key „Buzzer silenced“
Reset aggregate alarm „Reset Alarm/System“ key
Reset external buzzers: Key „Main siren off“

 Type: Boolean definition
 Parameter: Results from existing Boolean definitions can be used as the input criterion for new Boolean
definitions.
 Type: SecoNET event
 Parameter: Sent events from the master control unit can be used as input criterion for a Boolean definition.
A maximum of 64 events can be received from the master control unit.

4.7.4 Logic gates

For the logical linking of input criteria, there is a range of logic gates available. They can either be selected using
the toolbar or the „Tools“ menu”. They can then be placed accordingly using drag and drop.
Tool symbol Label

Selection cursor
Connections
Negation (NOT)
AND (AND)
OR (OR)
Exclusive OR (XOR)
Negation (NOT)
Greater than
More than
RS-Flipflop
D-Flipflop
Counter
Impulse
Low-High
High-Low
Clock generator
For some gates the number of inputs can be extended by marking and dragging the bottom right edge or addi-
tional information can be entered by double click on the gate (e.g. pulse duration).
4.7.5 Selection cursor

The cursor is used to select from tools and input criteria. By double clicking on specific
logic gates, parameters e.g. the duration of an impulse can be entered.
4.7.6 Connections
The tool is used to connect input criteria, logical gates and the output criterion with
one another using a line (conduits).
A conduit is created by single clicking on the start and end position with the connec-
tion tool (see example 1). The conduit is automatically snapped to the grid.
Example 1:
The automatic alignment of every conduit can also be changed in a user-defined manner. The conduit must
first by selected by means of a single click with the selection tool and then dragged to the desired position using
drag and drop (see example 2).

Example 2
4.7.7 Negation (NOT)

Negation can be used to invert an input or output at a logical gate. The negation is
indicated by a circle.
By placing the symbol on the input or output of a gate as desired, this input or output
of the gate is marked with a circle on it (see example).
Negation can also be undone, by means of a second negation or by deleting the nega-
tion.
Comments
Some inputs or outputs do not permit a negation and this will not happen when the
input/output is clicked on.
Examples
Negated input of an AND gate: Negated output of an OR gate:

4.7.8 Negation (NOT)

The output of the inverter always takes the opposite value of that that has been
inputted.
Example
Truth table
Input Output:
I1 O
0 1
1 0
4.7.9 AND (AND)

The output of the „AND“ gate has the value 1 when every input has the value 1.
Normally the gate has 2 inputs, but my marking and dragging the bottom edge, the
gate can be expanded to having up to 32 inputs.
Examples
With 2 inputs (standard): With 4 inputs:
Truth table
Input Output: Input Output:

I1 I2 O I1 I2 I3 I4 O
0 0 0 0 0 0 0 0
0 1 0 0 0 0 1 0
1 0 0 0 0 1 0 0
1 1 1 0 0 1 1 0
0 1 0 0 0
0 1 0 1 0
0 1 1 0 0
0 1 1 1 0
1 0 0 0 0
1 0 0 1 0
1 0 1 0 0
1 0 1 1 0
1 1 0 0 0
1 1 0 1 0
1 1 1 0 0

4.7.10 OR (OR)
The output of the “OR” gate has the value 1 when at least one input has the
value 1. Normally the gate has 2 inputs, but my marking and dragging the bot-
tom edge, the gate can be expanded to having up to 32 inputs.
Examples
Truth table

I1 I2 O I1 I2 I3 I4 O
0 0 0 0 0 0 0 0
0 1 1 0 0 0 1 1
1 0 1 0 0 1 0 1
1 1 1 0 0 1 1 1
0 1 0 0 1
0 1 0 1 1
0 1 1 0 1
0 1 1 1 1
1 0 0 0 1
1 0 0 1 1
1 0 1 0 1
1 0 1 1 1
1 1 0 0 1
1 1 0 1 1
1 1 1 0 1

4.7.11 Exclusive OR (XOR)

The output of the “XOR” gate has the value 1 when an odd number of inputs
have the value 1. Normally the gate has 2 inputs, but my marking and dragging
the bottom edge, the gate can be expanded to having up to 32 inputs.
Examples
Truth table
I1 I2 O I1 I2 I3 I4 O
0 0 0 0 0 0 0 0
0 1 1 0 0 0 1 1
1 0 1 0 0 1 0 1
1 1 0 0 0 1 1 0
0 1 0 0 1
0 1 0 1 0
0 1 1 0 0
0 1 1 1 1
1 0 0 0 1
1 0 0 1 0
1 0 1 0 0
1 0 1 1 1
1 1 0 0 0
1 1 0 1 1
1 1 1 0 1

4.7.12 Greater than

Certain input criteria can be composed of several variables (e.g. Alarm, Fault, Disable-
ment etc.) and deliver, in additional to the value (OR of the variables) the number of
variables with this value.
The output of the „Greater than“ gate has the value 1, when more than the defined
quantity of input variables display the value 1.
By double clicking on the system, the

threshold value can be set.
Example
Detector zone 1 and 2 are configured to alarm state. In this instance the output criterion is “True” if in Zone 1
or Zone 2 at least two detectors are in alarm state.
4.7.13 More than

The output takes the value when at least the defined number of input variables have
the value 1. Normally the gate has 2 inputs, but my marking and dragging the bottom
right edge, the gate can be expanded to having up to 16 inputs.
By double clicking on the gate it is possible

to enter the threshold value x [1..16] in the
input field.
4.7.14 RS-Flipflop
The RS-Flipflop is a cache for logical information. The output has the value 1 when the
S input has the value 1. The output keeps the value 1 regardless of the state of the S
input. Only when the value 1 is also present as the R input is the RS-Flipflop reset and
the output returns to 0 (the R input is dominant over the S input).

4.7.15 D-Flipflop
The D-Flipflop consists of a data input (D1) and a trigger input (C1). The output takes
the value of the D input as a result of a low-high (change from 0 to 1) at the C input.
The output remains in this state until the next low-high at the C input. The C input is
known as the clock input.
4.7.16 Counter
The counter makes it possible to count up as well as down. If the + input (counter
input forwards) has the value 1, then the counter is increased by 1. If the - input
(counter input backwards) has the value 1, then the counter is decreased by 1.
If the value 1 occurs at the reset input (R input) then the counter is reset to 0. If the
value 1 occurs at the set input (S input) then the counter is reset to 255. Setting has
priority over counting and resetting has priority over setting.
By double clicking on the counter symbol a start value „from x“ and an end value „to
x“ can be set [x = 0…255]. The output of the counter takes the value 1 if the counter
has reached or exceeded the start value that has been set. The output retains the value 1
until it reaches the end value that has been set. If he exceeds the end value, then the
output once again assumes the value 0.

4.7.17 Impulse
The output has the value 1 when the input has the value 1. The output holds this value
for a programmable time (= the pulse duration) regardless of the state of the input.
By double clicking on the gate symbol the pulse duration [0.10 sec to 31.00 h] can be
entered in the entry field. In the event of the input changing from 0 to 1, then the pulse
duration is restarted (retriggered).
4.7.18 Low-High
In the event that the value increases (changes from 0 to 1) at the input of the gate, then
the output changes to value 1 after a programmable delay period.
In the event of the value decreasing (changing from 1 to 0) at the gate’s input, the out-
put immediately changes from 1 to 0.
By double clicking on the gate the delay time [0.10 sec to 31.00 h] can be entered in the
entry field.

4.7.19 High-Low
In the event that the value increases (changes from 0 to 1) at the input of the gate, then
the output changes to value 1 immediately.
In the event of the value decreasing (changing from 1 to 0) at the gate’s input, the out-
put changes from 1 to 0 after a programmable delay period.
By double clicking on the gate the delay time [0.10 sec to 31.00 h] can be entered in the
entry field.
4.7.20 Clock generator

If the input of the gate has the value 1, then a pulse repetition starts at the output. The
pulse repetition always starts with a full impulse. If the input changes value to 0, then
the pulse repetition is stopped at the output, after the last impulse has completely fin-
ished.
By double clicking on the gate, the impulse duration [0.10 sec to 31.00 h] can be en-
tered in the entry field.

Integral Listgenerator  Detector zone macros
4.8 Detector zone macros

Detector zone macros are used to define parameters, which are relevant for the function of detector zones, e.g.
delay, intervention, alarm buffering etc.
4.8.1 Table of Detector zone macros

In the table all detector zone macros are listed that are available in the project.
 New: Definition of a new detector zone macro. An empty detector zone macro is opened.
 Edit: Edit the detector zone macro that is marked in the list.
 Edit Copy: Create a copy of the detector zone macro marked in the list and edit it. The detector zone
macro, from which the copy was created, is not changed in the process.
 Delete: Delete the selected detector zone macro.
 Reference: Displays the references to which detector zone macro marked in the list exists. After clicking the
button, the detector zone, to which the relevant detector zone macros have been assigned, are listed.
and export detector zone macros and to open and edit macro libraries.

4.8.2 Parameters for Detector Zone Macros

The detector zone macro is used to shape the basic properties of the detector zone element.
 Name: The detector zone macro must have had a name assigned to it (max. 30 characters). The macro can
then be found using this name in the detector zone macro table.
 Subtype: The subtype is indicated on the operating panel display of the fire alarm control panel and allows
selective treatment, if e.g. an aggregate criterion exists.
 Revision holding time: Time until a revision alarm is automatically reset (Default = 10 sec).
 Silent alarm: A “silent alarm” is not indicated on the operating panel of the fire alarm control panel (neither
visually nor acoustically) and is intended for special purposes. A “silent alarm” is automatically reset after a
configurable time (Default = 10 sec). When a configured threshold value (e.g. max. 3 alarms in 10 min) is
exceeded, then the next alarm in this detector zone is indicated and treated like a “normal” alarm.
 Delay (blocked for silent alarm): This dialogue area organises the forwarding of the „hard alarm“ of a
detector zone and is subdivided into the state DAY (= delay level active) and NIGHT (= delay level not ac-
tive or not assigned). The relevant delay level is assigned to the detector group in the „Detector Zone Con-
figuration Data“ dialogue. The following delays in forwarding the „hard alarm“ can be configured:
immediately: The „hard alarm“ is forwarded immediately with the „normal“ alarm message.
Always blocked: The „hard alarm“ is blocked. There is only a „normal“ alarm message. When configur-
ing the “silent alarm” the “hard alarm” is always blocked.
Intervention: The „hard alarm“ follows in accordance with the settings of the intervention mode.
Delay: The „hard alarm“ follows after the settable delay period (0.10 secs to 31.00 hours).
 Significance: The configured delay can be limited up to a set significance (default = always valid)
 Module-specific: Additional settings can be made using the button, which refer to specific line technolo-
gies.

4.8.3 Module-specific settings
 Alarm cache: For example, prewait time 31 secs, wait time 31 secs, which means: In the event of an alarm it
is saved in the control panel. After 31 seconds the alarm is automatically reset and a new counter (waiting time)
started. If there is another alarm during this time, then it is forwarded. Once the period has expired, and there
has been no alarm, this is detected in the memory.
 Deceptive alarm detection (only on MTI, DCI, DTI): Detector contamination is only generated if the
threshold value is exceeding during the evaluation period.
 (Only on DAI) Re-evaluate alarm after: This is the period of time after an alarm reset in which a further
alarm criterion is not evaluated.
 Permissible commands (DAI, LEE23/24, DTI): Permissible commands for operating a single detector
in a detector zone.
 Contamination:
Always visible: The message is always sent with significance of 4.
Visible from significance: Currently not used.
Never visible: The contamination is not announced.

Integral Listgenerator  Operating macros
4.9 Operating macros

Operability macros are used, in order to restrict the operability of elements of a subcontrol unit or links control
units on a command level.
4.9.1 Table of Operating Macros

In this window there is the opportunity to define new operating macros or to edit existing ones.
 New: Definition of a new operation macro. An empty operation macro is opened.

 Edit: Edit the operation macro that is marked in the list.
 Edit Copy: Create a copy of the operation macro marked in the list and edit it. The operation macro, from
which the copy was created, is not changed in the process.
 Delete: Delete the selected operation macro.
 Reference: Displays the references to which operation macro marked in the list exists. After clicking the
button, the operating groups, to which the relevant operating macros have been assigned, are listed.
and export operating macros and to open and edit macro libraries.

Integral Listgenerator  Operating macros
4.9.2 Parameters for operating macros

The structure of the „operating macros“ window is split into three definition fields.
 Name: The operating macro must have had a name assigned to it (max. 30 characters). The macro can then
be found using this name in the operating macro table.
 Command: The relevant commands can be selected in the command input field, which should be used
with/without restrictions in the various user levels.
 Unrestricted application: If this criteria is assigned to a command, the command can be used without
restriction in every user level.
 Restricted application: If this criteria is assigned to a command, the command can be used with restric-
tions in every user level for which the command has been released. Additionally a dependency can be de-
fined. Only if the dependency is fulfilled/not fulfilled, can the command be executed in the defined user
levels.
Dependency fulfilled: States in which operating level the command is permissible. This parameter is
only used, where there is no control criteria and the result of the link, or the
sum criteria is “true”. In there is no dependency, then the result is always
“true”.
Dependency not fulfilled: States in which operating level the command is permissible. This parameter is
only used, where there is no control criteria and the result of the link, or the
sum criteria is “not true”.
Dependency: In the “dependency” field, the criterion for dependency is set out. Only if the
link result is „True“ or „not true“, can an operation be undertaken depending
on the user level and what is released.
If an activation criterion States in which operating level the command is permissible. This parameter is
exists: only used if the activation criteria is present and an operation is possible. This
criteria is only applicable for outputs.
Example: In the previously shown picture of the Loop operating macro, it is possible to reset the loop in
user levels 2,3 and 8, because there is no fault on the loop present. If the loop has a fault, then it is only
possible to reset the loop in user level 8.

Integral Listgenerator  Privilege macros
4.10 Privilege macros

A privileges macro displays to/by which user level devices and their functions are visible or can be operated.
Privilege macros can be assigned to the “operating panel”, “master control unit” and “management system”
element types.
4.10.1 Table of Authorisation macros

In the table all authorisation macros are listed that are available in the project.
 New: Definition of a new authorisation macro.

 Edit: Edit the authorisation macro that is marked in the list.
 Edit Copy: Create a copy of the authorisation macro marked in the list and edit it. The authorisation macro,
from which the copy was created, is not changed in the process.
 Delete: Delete the selected authorisation macro.
 Reference: Displays the references to which the authorisation macro marked in the list exists. After clicking
the button, the elements, to which the relevant authorisation macros have been assigned, are listed.
The three buttons that are found in the bottom right of the window are used to import
 and export authorisation macros and to open and edit macro libraries.

Integral Listgenerator  Privilege macros
4.10.2 Parameters for Authorisation Macros
 Name: The authorisation macro must have had a name assigned to it (max. 30 characters). The macro can
then be found using this name in the authorisation macro table.
 Element type: In the element type list, those elements for which authorisation has been granted is marked
with a .
 Functional type: In the functional type list, those elements for which authorisation has been granted is
marked with a .
 Visibility: If privileges have been set then the “Visible in” entry is marked with a .
 Operability: In the list of all available commands, those for which authorisation has been granted is marked
with a .
 User Level: The selected user levels are marked with a .
The navigation within the authorisation macro window is explained in greater detail below:
By single clicking on the element type, all the functions which can be carried out using this element will be dis-
played. Only once a specific function type has been single clicked upon will the commands that can be used for
the selected function type appear in the “operability” pane, and the entry “visible in” will then appear in the
“visibility” pane. By single clicking on “visible in” or on each individual command it is then possible to grant
the privileges required by then double clicking on one or more levels in the “user level” field. The levels are
then marked with a tick.
If all user levels should be allowed to use a particular command, a double click on this element is sufficient to
do so (the user levels are then no longer shown for this element). This is also applicable for making an item
visible, or for making ALL commands available to ALL user levels for a particular type of function, with a dou-
ble click on this item again being sufficient. It is of course also possible to give unrestricted privileges for a
certain device type by means of a double click.
Only visible functional types can be operated.

Integral Listgenerator  Integral User
The menu item “Keys in Level 1” can be used to define which keys’ function for level 1 access privileges and
which do not.
These settings should not be altered.
4.11 Integral User

For every project, users can be added with specific privileges.
 New: Definition of a new user.

 Edit: Edit the user that is marked in the list.
 Edit Copy: Create a copy of the user marked in the list and edit it. The user, from whom the copy has been
created, is not modified in any way.
 Delete: Delete the selected user.
 Reference: Displays the references to which user marked in the list exists.
 and export users and to open and edit macro libraries.

Integral Listgenerator  Integral User
 Name: The username can be freely selected and is required for identification purposes.
 Password: The password can be freely selected and is required for identification purposes.
 TelNo: The Server telephone no. must be entered for the callback function or for the service call.
 Behaviour: This entry is necessary if the control unit should call the user back at the telephone number that
has been entered. For a mobile user, this option is not allowed to be activated.
 Rights: Define the user rights for operation, firmware download, and for configuration of the control unit.
never: No rights are granted.
Immediately: After dial-in immediate and unrestricted access is possible.
Once released: Access is possible once local permission has been given.
Pursuant to VDE 0833-1, access is only allowed after permission has been granted locally at the
fire alarm control panel.

Integral Listgenerator  Range filters
4.12 Range filters

Range filters all specific subzones of elements available in a subcontrol unit or a group of control units, e.g.
detector zones, outputs etc. to be drawn together. A range filter can then for example be used both for restrict-
ing indicators on operating panels and printers, as well as for defining of sum criteria etc.
4.12.1 Range filter table

In the table all range filters are listed that are available in the project.
 New: Definition of a new range filter.

 Edit: Edit the range filter that is marked in the list.
 Edit Copy: Create a copy of the range filter marked in the list and edit it. The range filter, from which the
copy was created, is not altered.
 Delete: Delete the selected range filter.
 Reference: Displays the references to which range filter marked in the list exists. After clicking the button,
the elements, to which the relevant range filters have been assigned, are listed.
 and export range filters and to open and edit macro libraries.

4.12.2 Range filters

A range filter is defined by selecting the relevant element type. In the example, there is the element type “out-
put”. Various options can then be set.
 not used: No filter is defined for the marked element type.
 Filter nothing: All elements of the marked element type can pass through the filter.
 Filter all: No elements of the marked element type can pass through the filter.
 Ranges: Only specific elements (e.g. output 1-2) can pass through the filter. All other elements of this ele-
ment type are rejected by the filter.
New: New ranges can be assigned for the selected element type – e.g. output 1-2. Furthermore it
is also defined in which user level the range is to operate.
Edit: The selected range can be edited.
Delete: The selected range can be deleted.
 Filter unused element types: No elements of the unmarked element type can pass through the filter.

4.12.3 Parameters for a range
 Element number: Enter the element numbers of the relevant range for the selected element type. e.g. the
detector zone element type was selected, and this input refers to detector zones 1-4.
 Operable in user level: Definition in which user levels the released elements can be operated. e.g. the de-
tector zones 1-4 can only be operated in user levels 2,3 and 8.
4.12.4 Range filter selection

In this input window, a ready or pre-defined range filter can be selected.

4.12.5 Example of the range filter

Example 1: Creating a range filter for a subcontrol unit, which should have the effect that the indication and
operation of various detector zones is restricted. The range filter has no effect on other operating panels of
subcontrol units.
In order to define a range filter, choose the „Range filter“ menu item in the „Definitions“ menu and click on
the “new” button. The range filter window opens.
To set up a range filter for detector zones, select the element type “detector zone”. In the input window
“Range” enter the detector zones in the “element number” field. In addition, define in which user levels the
detector zones can be operated. This setting is made in the “Range” window in the “User level of control”
field.

Example 2: Assigning the created range filter.
The range filter is assigned to the operating panel by selecting the menu item „2 logical properties” in the menu
“Section” and selecting the element type “Operating panel” from the dropdown list and operating panel 1 is
opened. Then, in the window that follows, click on the “Range filter” button and select the created filter from
the list.
If you go back to the range filter definition once the range filter has been assigned, then the operating panel 1
appears in the reference list for the range filter in question.

Integral Listgenerator  Message filters
4.13 Message filters

Message filters are used to permit or suppress the printing out of specific messages or commands on operating
panel printers or external printers. Every printer of a subcontrol unit or a group of control units can be as-
signed up to 3 different message filters.
In order to define a message filter, select menu item “Message filters...” from the “Definitions” menu.
4.13.1 Table of Message FiltersIn this window there is the opportunity to define new message fil-
ters or to edit existing ones.
 New: Definition of a new message filter.
 Edit: Edit the message filter that is marked in the list.
 Edit Copy: Create a copy of the message filter marked in the list and edit it. The message filter, from which
the copy has been created, is not modified in any way.
 Delete: Delete the selected message filter.
 Reference: Displays the references to which message filter marked in the list exists.
The three buttons that are found in the bottom right of the window are used to im-
 port and export message filters and to open and edit macro libraries.
When exporting: The project properties dialogue box appears every time the file is exported. It is
therefore possible to change the version number every time or to enter hints about
changes.

4.13.2 Parameters for message filter
 Name: The name of the message filter is entered in the „Name“ field.
 Element states: The states of the elements are defined which should be filtered using this button. e.g. for
the detector zone element only alarms should be printed out. The message filter must be configured in such
a way that the alarm state of the detector zone element type are filtered. This message filter can be assigned
to a printer.
 Internal states: There is the state „warm start“ among the internal states, which can be filtered. This state is
announced, if the subcontrol unit in question switches over from side A to side B as a result of different
hardware errors (e.g. defective modules, falsely configured modules etc.). This message can be suppressed.
 Commands: Both the operating panel printer as well as external printers normally (when there are no mes-
sage filters being used) issue two messages when a command is entered at an operating panel. The first mes-
sage is for the command that was just entered. The second message is to acknowledge that the command
was successfully executed. To save time and paper, the printing out of commands can be suppressed, since it
generally suffices if only the acknowledgements are printed out.
4.13.3 Element states in message filters

It should be noted that each change of state comprises of the following 2 messages.
„incoming event“: e.g. “fault” state after state change from idle => fault
„outgoing event“: e.g. “idle” state after state change from fault => idle
The menu point to be configured alters the display accordingly, dependent on whether the setting “filter
checked states” (display => filter only outgoing event) or “let checked states pass” (display => let only incom-
ing events pass) has been set.

Example: Don’t filter information.
In the following example for the input element type, the states “fault” and “disablement” are so programmed
that all information (incoming and outgoing events) are let through.
Example: Filter outgoing information.
The “active” state is so programmed, that only incoming information is allowed to pass through. The menu
item “only allow incoming events” has also been activated. This means that only the event “input active” is let
through. If the input were to change to a passive state, then this information would be filtered and also not
printed.

It should be noted that each change of state comprises of the following 2 messages.
„incoming event“: e.g. “active” state after state change from idle => active
„outgoing event“: e.g. state “idle (input passive)” after change of state from active => idle (in-
put passive)
The menu point to be configured alters the display accordingly, dependent on whether the setting “filter
checked states” (display => filter only outgoing event) or “let checked states pass” (display => let only incom-
ing events pass) has been set.
It should be checked without fail whether “filter marked states” or “let marked states through” is
set in the bottom left of the window before carrying out these settings.
4.13.4 Internal states

There is the state „warm start“ among the internal states, which can be filtered. This state is announced, if the
subcontrol unit in question switches over from side A to side B as a result of different hardware errors (e.g.
defective modules, falsely configured modules etc.). This message can be suppressed.

4.13.5 Commands
Both the operating panel printer as well as external printers normally (when there are no message filters being
used) issue two messages when a command is entered at an operating panel. The first message is for the com-
mand that was just entered, with the second message being for the acknowledgement for the successful execu-
tion of the command. To save time and paper, the printing out of commands (see picture) can be suppressed,
since it generally can be sufficient if only the acknowledgements are printed out.
4.13.6 Message filter selection

In order to assign an generated message filter to a operating panel printer or to an external print, the menu item
“2 logical properties” is selected from the “Section” menu. The the element type „printer“ must be selected. By
double clicking on the printer, to which the message filter should be assigned, the following picture is opened:
Operating panel printers or external printers can be assigned up to four different message filters (level 1 to level
4). The operation, i.e. the activation and disabling and selection of the message filters for levels 1 to 4, can be
restricted to certain user levels using an operating macro.

 Name: The list of defined message filters is contained underneath the name item. For example as message
filter level 1 - Beispielsweise wird als Meldungsfilter Ebene 1, “Drucker STD“ has been assigned to operating
panel printer 1.
 Link: Message filters can also be combined. To do this, make the relevant message filters and choose either
an OR or an AND link.
 Define…: New message filters can be generated with this button.

Integral Listgenerator  Messages
4.14 Messages
With the help of messages, it is possible to automatically execute nearly all commands which can also be exe-
cuted at the operating panel of the fire alarm control panel manually (message type = command) based on a
certain event (=link, the logical state of a Boolean definition. Moreover messages in the internal data format of
the fire alarm control panel can also be configured (message type = text).
4.14.1 Messages table

In this window there is the opportunity to define new messages or to edit existing ones.
 New…: Definition of a new message.
 Edit…: Edit the message that is marked in the list.
 Edit Copy: Create a copy of the message marked in the list and edit it. The message, from which the copy
has been created, is not modified in any way.
 Delete: Delete the selected message.
The three buttons that are found in the bottom right of the window are
 used to import and export messages and to open and edit macro libraries.

Integral Listgenerator  Messages
4.14.2 Parameter setting for messages
 Name: The message must have had a name assigned to it (max. 30 characters).
 Link: A Boolean definition must be selected from the dropdown list.
 Message for Link result: First it needs to be defined, based upon which logical state (0/False/Low or
1/True/High) of the selected link that the message should be executed. A message can also be configured
for both states. Moreover, the setting must be actively selected, then a message in the form of a command
or message can be configured.
When configuring a command, this must always be assigned an authorisation level, as othewise it can not be
executed. If the command should be executed for several elements, then a range filter can if required also be
assigned a range filter.
When configuration messages, it is recommended that you contact technical support.
 Priority: Default = low, in the instance of their being several simultaneously occuring messages, the ones
with the higher priority will be processed preferentially (e.g. alarms).
 Reactivate: After using the “reset” command, it is possible to configure whether in the event of their being
an outstanding activation criterion, whether an additional activation criterion should cause it to be reacti-
vated.

Integral Listgenerator  Sum criterium
4.14.3 Message type

Messages can either be of the type "Command" or
"Text".
 Command: It is simple to configure a command ana-

logue to manual operation at the operating panel of the
fire alarm control panel.
 Text: A message can be configured in the internal data

format of the fire alarm control panel.
4.15 Sum criterium

Sum criteria are used to query certain “sum states” of elements (e.g. sum alarm, sum fault, power supply fault
etc.). It can them be further processed with logical links (Boolean definitions) as a so-called “input criterion”.
4.15.1 Table of sum criteria

In this window there is the opportunity to define new sum criteria or to edit existing ones.
 New: Definition of a new sum criterion.

 Edit: Edit the sum criterion that is marked in the list.
 Edit Copy: Create a copy of the sum criterion marked in the list and edit it. The sum criterion, from which
the copy was created, is not changed in the process.
 Delete: Delete the selected sum criterion.
 Reference: Displays the references to which sum criterion marked in the list exists.
The three buttons that are found in the bottom right of the window are used
 to import and export sum criteria and to open and edit macro libraries.

Integral Listgenerator  Sum criterium
4.15.2 Parameter settings for sum criteria

A sum criterion delivers a logical total overview of a range of available values of at least 1 (sub)state of one or
more element and function types in a subcontrol unit (SCU) or in a subcontrol unit loop (SCU loop). If the
selected state occurs for at least 1 element and functional type (corresponds to an OR link) then the sum crite-
rion is logically 1 (true/high). A meaningful selection of sum criteria considerably facilitates the programming
of Boolean definitions.
 Name: The „Name“ field, the name of the sum criterion to be defined is entered.
 States: In the list of all available states, the selected ones are marked by a . If only 1 state is selected, then
1 substate for this state must be entered. If more than 1 state is selected, then all available substates are
automatically selected.
 Substates: If only 1 state is selected, then partial amounts of substates can be selected (e.g. disablement ->
disablement using key). The selected substates are marked with a . All substates can also be selected in one
go.
 Significance: If a (sub)state can have several significances (e.g. prealarm and alarm of the SSD 531 optical
smoke detector) then the required significance must be entered. Otherwise this value must be set to 1.
 Element types: In the list of all available element types, the selected ones are marked by a . If only 1 ele-
ment type is selected, then 1 subelement type for this must be entered. If more than 1 element type is se-
lected, then all available subelement types are automatically selected. All element types can also be selected
in one go.
 Subelement types: If only 1 element type is selected, then partial amounts of subelement types can be se-
lected (e.g. detector zone -> manual call point). The selected subelement types are marked with a . All
subelement types can also be selected in one go.
 Functional types: In the list of all available function types, the selected ones are marked by a . The func-
tional type „element itself“ is to be chosen with few exceptions.
 Range filters: The sum criterion can be restricted to one or more range filters with a specific range of val-
ues.

Integral Listgenerator  Printer templates
4.16 Printer templates

The Listgenerator programming is printed out using the “File/Print” menu.
If the scope of the information of the Listgenerator programming to be printed out is to be restricted, then a
so-called “Printer template” must be created.
4.16.1 Table of Printer Templates

In the table all printer templates are listed that are available in the project.
 New: Definition of a new printer template.

 Edit: Edit the printer template that is marked in the list.
 Edit Copy: Create a copy of the printer template marked in the list and edit it. The printer template, from
which the copy was created, is not changed in the process.
 Delete: Delete the selected printer template.
 Reference: Displays the references to which printer template marked in the list exists. After clicking the
button, the elements, to which the relevant printer template has been assigned, are listed.
 and export printer templates and to open and edit macro libraries.

Integral Listgenerator  Printer templates
4.16.2 Parameters for printer templates

Elements which are printed in the documentation of the Listgenerator configuration are marked with a tick.
They can be activated/deactivated as required. The numbering of the chapters is updated automatically.
When creating new printer templates, a unique name must be entered in the name field of this printer template.
4.16.3 Selecting the printer templates

Select a predefined printer template from the input window. After carrying out the „print“ command, a printer
template can be selected if required from a dropdown list. Printer templates are created under the Defini-
tions/Printer Templates menu item.
If the entire scope of the documentation needs to be printed, than in the printer template selection field, the
entry <none> should be selected.

Integral Listgenerator  Further programming hints
4.17 Further programming hints

In this chapter, all other information is described, which could not be assigned to a unique theme.
4.17.1 Macros - Library

The macro library contains all the macros defined in a configuration.
 Current file: All defined macros for the current configuration are listed here by name.
 Library: The macros that have been saved in an existing library can be imported (loaded from a file) or a
newly formed library can be exported (saved as a file). In both lists (current file and library) marked macros
can be copied back and forth, deleted (reference must be 0) or renamed (one 1 macro may be marked).
 Also copy macros used in references: When activated, cross references (e.g. a Boolean definition contain-
ing a sum criterion) are automatically copied across too.
per subcontrol unit per subcontrol unit loop

Range filters max. 15 max. 15
Message filters max. 16 max. 16
Group criteria max. 255 max. 255
Operating macros max. 64 max. 64
Detector zone macros max. 64 max. 64
Boolean definitions max. 255 max. 255
Messages max. 255 max. 255
Privilege macros max. 64 max. 64
Printer templates max. 255 max. 255

4.17.2 Warning when exporting

Information window for indicating warnings and errors when exporting configurations. Warnings are messages
that advise you that e.g. compiled Boolean definitions are not required for the export. This can be possible, e.g.
if Boolean definitions have already been created for later use, but are not being used. The configuration file will
continue to be exported and the .lpd file created.
If faults occur (e.g. detector zones without a detector zone macro, incomplete Boolean defini-
tions etc.) on the other hand, then the export of the configuration file is stopped and no .lpd file
is produced.
4.17.3 Application Options
 Export configuration files:
binary: Configuration is only exported in binary form (*.lpd). This is also the recom-
mended standard setting.
Text (.TXT): Configuration is only exported in text format (for development purposes only).
Both formats: Configuration is exported in both formats (binary and text).
 Memory:
Create a backup copy: When saving changes, a backup copy of the current *.lpd configuration file is pro-
duced.
The backup file has the same filename, but instead of being saved with the file-
name extension, it is saved with a ~ character.
 Show project properties dialogue box:
When saving: The project properties dialogue box appears every time the file is saved. It is there-
fore possible to change the version number every time or to enter hints about
changes.

4.17.4 Delete elements

All logical elements are listed in this information window, for which there is no longer a physical element.
This information occurs where changing from level 1 (fitting) to level 2 (logical properties) and signals that
logical elements were removed during the fitting process. By deleting the elements are also removed from level
2. Examine the following example:
In level one, outputs 107-116 were fitted to a REL16. Then the change was made to level 2. Since the outputs
107-116 are not required, the programmer changed back to level 1 and deactivated the outputs that were not
required. Then by changing back to level 2 again the information window opens and remarks that no physical
elements exist any longer for the outputs 107-116. . The elements are removed by deleting them. If the ele-
ments however, had been previously configured in level 2, then the settings are permanently deleted.
4.17.5 References
In this information window, all elements are listed that have been assigned links (e.g. Boolean definitions, sum
criteria, operating macro etc.).

4.17.6 Table of List templates

It is possible to choose between a tabular and list-style layout in the “Logical properties” menu on the monitor.
To have a better overview, the table view can be adapts to have a separate macro for each element.
In the table all list templates are listed that are available in the project.
 New: Definition of a new list template.

 Edit: Edit the list template that is marked in the list.
 Edit Copy: Create a copy of the list template marked in the list and edit it. The list template, from which the
copy has been created, is not modified in any way.
 Delete: Delete the selected list template.
 Reference: Displays the references to which list template marked in the list exists.
 and export list templates and to open and edit macro libraries.
4.17.7 Parameters for List templates
 Name: The list template must have had a name assigned to it (max. 30 characters). The macro can then be
found using this name in the list template table.
 Element type: Selection of the element types to edit. The view can be individually adapted for every ele-
ment type in level 2.
The view of the element type is edited by selecting columns 1-4.

Example: The settings for the element type detector zone were carried out as follows:
The view in level 2 is as follows:

IntegralText  Screen elements
5 IntegralText
5.1 Screen elements
The screen elements are described in this chapter with are available in the IntegralText Tool.
5.1.1 Overview
The main window of the IntegralText contains the following main screen elements:
 System menu: The system menu contains general command, which refer to the active document.
 Menu bar: All commands are listed by categories, which are required to work with IntegralText in the menu
bar.
 Tool bar: The tool bar is displayed horizontally or vertically on the edge of the application window or as a
separate window. It offers quick access to frequently used IntegralText commands. In order to hide or open
the tool bar, the tool bar command can be selected from the menu view. By clicking the left mouse button
between the symbols, the tool bar can be dragged to where you want it. One frame displays the new posi-
tion.
 Tab bar: The tab list can be set user-specifically and is used to change quickly between the open documents.
 Element types (Tree view): All control units and their element types are listed, with there being at least
one record in existence.
 Records (List View): In this view all records are displayed of the element type chosen in the tree view. The
records are sorted initially in ascending numerical order. New records are always appended at the end of the
list.
 Entry bar: New records are entered and existing records modified in the entry bar.
 Status bar: The status bar can be found at the bottom edge of the IntegralText window and displays further
information about editing the records.

5.1.2 Standard Screen Elements

The standard screen elements are described in this chapter with are available in the IntegralText Tool.
Document window: The document window of IntegralText consists of three sections.

 The left part (tree view) shows the element types for which records already exist.
 In the right part (list view) the records of the element type selected in the left part are displayed.
 The third part is the input bar, with the help of which the records are created or modified.
Program window: The main IntegralText window contains the menu bar, toolbar, status bar and the opened
documents. To move between the opened documents or to sort them, look at the commands of the system and
window menu.
Window frame: Every window is surrounded by a window frame. If you hover with the mouse cursor over the
window frame, the cursor changes into a double-ended arrow. If you left click with the mouse now, you can
change the size of the window.
Title bar:
The title bar extends above the upper edge of the window. It contains the name of the application and the ac-
tive document. The title bar can be dragged to move the window. Note: Dialogue windows can also be moved
by dragging their title bar. A double click on the title bar toggles between increasing the size of the window to
fill the whole screen, and returning it to its original size and position.
A title bar can contain the following elements:
System menu of the application
System menu of the document
Minimise
Maximise
Refresh
Close
Status bar:
The status bar can be found at the bottom edge of the IntegralText window and displays further information
about editing the records. If you select a menu entry or move the mouse over a button on the toolbar, then the
left part of the toolbar describes the function that that button performs.
In the right part of the status bar the number of records in the list view are displayed as well as which of the
following keys are activated:
SHIFT: The shift key is activated.
NUM: The number lock key on the numeric keypad is activated.
SCR: The scroll lock key is activated.
Scroll bar:
The scroll bar can be used to change the visible section on the screen. A mouse click on the arrows moves the
visible selection by one line. A mouse click on the light grey area moves the visible selection by one page. The
visible bar can also be dragged to the required position using the mouse.

Toolbar on the page view:

The following options are available in the toolbar of the page view:
Print: The print dialogue field, from which a print job can be started, is called up using this
button.
Next page: Displays the next page view.
Previous page: Displays the previous page view.
One page / two pages: Toggles between whether one or two pages should be visible at the same time.
Zoom in: The page can be examined more closely using this option.
Zoom out: Gives a larger overview of the printed page.
Close: Closes the page view and returns to the editing window.
5.1.3 Element Types (Tree View)

All control units and their element types are listed, with there being at least one record in existence. Choose the
element type which should be displayed in the list view.
If the tree view is the current window, then the commands copy, cut and delete record apply to all records with
the selected element type.
Right click with the mouse on the control unit or element type to display the relevant context menu.

5.1.4 Records (List View)

In this view all records are displayed of the element type chosen in the tree view. The records are sorted in
ascending numerical order. New records are always appended at the end of the list. To sort the records in a
user-defined way, click on the column heading with the mouse for the column that should be used for sorting.
Clicking on the same column again will reverse the order of the sorting of the column.
Clicking on a record with the mouse marks that record. The marking can also be moved using the arrow keys.
The marked record is copied into the input bar for editing.
In order to mark several records, hold the following keys down and then select a record:
SHIFT: All records between the current record up to and including the chosen one are marked.
CTRL: Only the record that is chosen is marked additionally (the other marking is not affected).
Both keys can also be pressed simultaneously.
Meaning of the arrows:
Highlights the record which has just been entered or edited.
Highlights the record which already exists and which should be overwritten.
Highlights the records which contain at least more characters in a line than are allowed.
The display type can be changed using the command "List view setting (menu view)".

5.1.5 Input bar

New records are entered and existing records modified in the input bar.
 SC: The number of the slave control units, for which a text should be entered, is selected from the list. Only
the numbers of slave control units are available that have previously been added.
 Element type: The element type, for which a text should be entered, can be selected from the list.
 No.: The element number for the corresponding element type is entered here.
 Detector: For the 'Zone' element type it is possible to enter a subnumber (detector number) - (This input is
possible for all element types, but it is not always meaningful to do so).
 Normal / Special:The text for the operating panel and the printer (normal text) is entered here. Addition-
ally, the text for an FBF (special text) can be entered. There are fields for the first three lines to be entered.
If more lines are required, then they should be entered in the third line and separated from one another us-
ing the character combination \u.
 HighEnd: The text for the high end operating panel (HighEnd text) is entered here. There is a text area for
entering the text.
 Info: The additional text is entered here. There is a text area for entering the text.
 Text-Type add / change: Here it is possible to determine which text type should be affected by the
changes. If for example only the normal text should be changed, then all other text types must be deacti-
vated, so that the text contained in them is not changed.
 New / Change: These buttons can be used to either add a new record (new) or to confirm the changes to
an existing record (change).

5.1.6 Tool bar

The tool bar is displayed horizontally or vertically on the edge of the application window or as a separate win-
dow. It offers quick access to frequently used IntegralText commands.
In order to hide or open the tool bar, the tool bar command can be selected from the menu view. By clicking
the left mouse button between the symbols, the tool bar can be dragged to where you want it. One frame dis-
plays the new position.
Creates a new document.
Opens an existing document.
Saves an open document under the same filename as before.

Presents the document in print view on the screen – so its appearance is as it would be when
printed.
Prints a document.
Deletes the marked data and moves it to the clipboard.
Copies the marked data into the clipboard.
Pastes in the data that is in the clipboard.
Copies the marked data and transfers the data in tabular form into the clipboard (Excel)
Pastes data in tabular from (e.g. from Excel) from the clipboard.
Searches for the entered text.
Toggles the automatic element numbering on and off (automatic incrementing).

Toggles the automatic element numbering on and off (automatic incrementing only for No., not
for Sub No.).
Number of characters per line for normal text.
Number of characters per line for special text.
Adds a new main or slave control unit.
Enters the version, text name and other settings.
Jump to next record of this element type that has too many characters per line.
Toggles the character table on/off.
Sets the format of the list view.
Toggles the gridlines on/off in list view.
Displays information about IntegralText.
Displays help about a command or a screen element.

5.1.7 Commands
Automatic autoincrementing
If automatic autoincrementing is switched on, then after a new record has been created, or an existing one has
been changed, then the element subnumber (for groups) or the element number (for all other element types) is
automatically increased by 1.
Autoincrementing only of element number

If autoincrementing only of the element number is switched on, then only the element number (also for zones)
is automatically increased by 1 after a new record has been successfully created or an existing record has been
changed.
Characters per line (normal text)

The maximum number of characters permissible per line for normal text. The length of the lines on the display
of the BMZ Integral is 20 characters. Please ask the technician about the maximum length of lines for the
BMZ.
Characters per line (special text)

The maximum number of characters permissible per line for special text. Please ask the technician about the
maximum length of special texts for the BMZ.
Next too long text

If the number of maximal permissible characters per line is reduced, then all records which have at least one
line containing more characters than allowed, are marked with a dark red arrow. To then move the marking
from one record to the next where there are too many characters per line, it is possible to do so by clicking on
the button “Next too long text” in the toolbar.
5.1.8 Miscellaneous
Space for docking the toolbar: The toolbar can be docked to any edge of the main window of the Integral-
Text, or be placed as a freely floating window anywhere on the screen. To do his, hold down the left mouse
button between the symbols, and drag the toolbar to the position you wish to move it to. A frame is displayed
which shows the position which it will have, when the mouse button is released.

IntegralText  Menu - Commands
5.2 Menu - Commands

All the menu commands which are available in the IntegralText Tool are described in this chapter.
5.2.1 System menu

The system menu contains the following commands:
Restore
Restores the size and position of the active window, in which it previously was prior to the commands full
screen or symbol being selected.
Move
Moves the window with the keyboard. The command is not available when the window is in full screen mode.
Change size
Changes the size of the window with the keyboard.
Press one of the DIRECTION ARROWS (LEFT, RIGHT, UP or DOWN) on the keyboard, to move the
pointer to the edge that you want to move. The frame size can be changed using the DIRECTION ARROWS.
The selected window size is confirmed with the ENTER KEY (ESC cancels this action). The command is not
available when the window is in full screen mode.
Minimise
Minimises the window down to the size of the symbol.
Maximise
Displays the window in full screen size
Close
Closes the active window or dialogue box. If several windows are open for a single document (Menu: Window
/ Command: New window), then the Close command only closes a single window from the document system
menu. To close all windows at once, you can use the Close command in the File menu.
Next
Changes to the next open document window

5.2.2 File menu

The file menu contains the following commands:
New: Creates a new document. The standard settings (characters per line, language, ...) can be set using the
standard settings (Options menu).
Open: Opens an existing document. Several documents can be opened simultaneously in IntegralText. Using
the Window menu, it is possible to switch between several simultaneously opened documents.
Close: Closes an open document. In the event that a document is closed without being saved, then all changes
will be lost that have been made since the document was last saved.
Save: Saves an open document under the same filename as before. The document is always saved in the newest
file format using the Save command. If the document should be saved in another format, then Save and select
format should be selected.
Save as...: Saves an opened document under a specified filename, using the newest file format. To save the
currently active document in another file format, select the “Save and select format” command should be used.
Open with keyword file...: Opens IntegralText files (file format version 1) which were created using another
keyword file. After selecting the file to be opened you are asked to specify the keyword file.
Save and select format...: Saves the active document in another file format. This command is only available
when the document only covers a single Standard BMZ (no slave control units).
In the dialogue box that appears after selecting Save and select format, it is possible to select the file format.
Data that does not exist in this format will not be saved.
The following formats can be selected:

Maxima C Version: Saves the data as Maxima file version C (DBF file). This file can be read with all
Maxima Text tools.
IntegralText Version 1: Saves the data in a format for IntegralText prior to version 3.0.0 and the text parser.
IntegralText Version 2: Saves the data in file format 2. The file can be read with IntegralText version 3.0.0
and higher. Slave control units can be saved from this version.
IntegralText Version 3: Saves the data in file format 3. The file can be read with IntegralText version 3.1.0
and higher. Special texts can be saved from this version.
IntegralText Version 4: Saves the data in file format 4. The file can only be read with IntegralText version
3.2.0 and higher. HighEnd texts and Info texts can be saved from this version.
IntegralText Version 5: Saves the data in file format 5. This is the current file format. It can only be read by
IntegralText version 3.3.0 and higher. SC names, file information and the list view
settings can be saved from this version.
Export: Creates the TPD file which is to be read into the BMZ. This file is created in the export folder, which
is setting using the “Folder” menu item in the Options menu. The dialogue box contains the following con-
tents, and appears after the Export command is selected, if there are slave control units in the document.
Export all control units: A file is created for every slave control unit, which must then be read into the
corresponding control unit.
Export one control unit: Select the slave control unit which should be exported.
Save Maxima texts as DBF file: If a slave control unit is defined as a Maxima, then a DBF file is created in
the export folder, which can then be subsequently processed by the Maxima
Textcompiler.
Save all SC texts in DBF file Currently not yet available.

(Standard Maxnet):
When the dialogue box for exporting a file appears, you are not asked when any existing file
should be overwritten!

Export HighEnd Control Panel: Creates the TPD file which is to be read into the HighEnd control panel.
This file is created in the export folder, which is setting using the “Folder” menu item in the Options menu.
The contents of the dialogue box correspond to those of the “Export” command and appear after the “Export
HighEnd control panel” command, if there are slave control units mentioned in the document.
Export old versions - Structure 2.0.0 / Structure 3.0.0: Creates the tpd file which is read into the BMZ (for
Integral prior to version 5.1.0.) This file is created in the export folder, which is setting using the “Folder”
menu item in the Options menu. The contents of the dialogue box correspond to those of the “Export” com-
mand and appear after the “Export old versions” command, if there are slave control units mentioned in the
document. Data which are not available in this version, are not exported.
Page setup...: Selects the paper format and page margins for printing the documents. The possible settings
depend on the printer that is selected. When setting the page margins, it is necessary to ensure that these mar-
gins are not smaller that the printable page margins.
Print...: Prints a document. If there is more than one BMZ or SCs, then a dialogue box appears for selecting
what should be printed. Thereafter, the Print dialogue box appears, if which you can specify the page range to
be printed, the number of copies, the printer to be used, and other printer setting options. The following op-
tions allow you to define how the document should be printed:
Printer Select the desired printer from the list.

Properties Displays a dialogue box with the settings for the selected printer.
Print as file The print data is saved to a file, so that it can be printed out later.
Page range Information about the pages which should be printed out:
All – prints the entire document
Pages - prints the page range which you specify in the “From” and “To” fields.
Copies Specifies the number of copies which should be printed of the specified page range.
Print preview: Displays the document in print view on the screen – as it should appear when printed. When
this command is selected, the main window is replaced by a page view window, in which one or two pages can
be displayed in print format. In the toolbar on the page view window, it is possible to select whether one or two
pages should be visible at the same time. It is also possible to flick through the pages of the document, to
enlarge/shrink the pages or to start a print job.
Print Setup: Selects a printer and a printer connection. After selecting the command, the Print Setup dialogue
box appears, in which it is possible to set the printer and its connection. The follow options are available as
standard:
Printer: Select the desired printer from the list.
Properties: Displays a dialogue box with the settings for the selected printer.
Paper: Select the paper format, on which the document should be printed. It is also possible to
specify from which paper tray the printer should take the paper.
Format: Select between landscape and portrait format.
1, 2, 3, 4: Opens the last 4 edited documents.
Exit: Exits IntegralText. Alternatively, it is also possible to use the “Close” command in the system menu.
IntegralText then suggests saving the changes to the document prior to closing. In the event that a document is
closed without being saved, then all changes will be lost that have been made since the document was last
saved. Before an untitled document is closed, IntegralText displays the Save as... dialogue box and suggests
giving the document a name and saving it.

5.2.3 Edit menu

The Edit menu contains the following commands:
Cut: The marked records or texts are removed and placed into the clipboard.
Copy: The marked records are copied into the clipboard.
Paste: Pastes the records from the clipboard into the marked place. This command is unavailable, if the clip-
board is empty or if the data does not have the correct format.
Copy to Excel...: Copies the marked data and transfers the data in tabular form into the clipboard (e.g. for
Excel) It is possible to set the data source and the data format in the dialogue box. The following settings are
available:
All element types of Copies the records of the entire document.

all SCs:
All element types of Copies the records of the currently selected slave control unit.
the current SC:
Current element type: Copies the records of the currently selected element type (only available if records are
shown in list view).
Marked records of the Copies the records which are marked in the list view (only available if records are
current element type: marked in the list view).
New: Creates a new (empty) format definition with which the records are copied into the
clipboard and then opens the Define format dialogue box.
Edit: Opens the selected format definition in the Define format dialogue box to modify the
settings.
Edit Copy: Creates a new format definition with the settings contained in the selected format defi-
nition and opens this in the Define format dialogue box.
Delete: Deletes the selected format definition. (The last definition can not be deleted).

Paste from Excel...: Pastes data in tabular from (e.g. from Excel) from the clipboard. The individual columns
of the Excel list must be separated using a tabulator character.
Select column: In the "Select columns" range field the number of columns is entered in which the data for
this field in the display area of the dialogue box is contained.
Load clipboard: Data which has been copied into the clipboard can be loaded into the display area using the
“Load clipboard” button.
Number: Enter the column number in which the element number (an integer from 1 to 65536 1) is
located.
Detector: Enter the column number in which the Sub-Number or Detector number (an integer from
0 to 255 1) is located.
Line 1: Entry of the column number in which the text for the first line or all lines is located. If the
character string \u or \c are present then they are treated as an optional or non-optional
line break. See Structure of a record.
Line 2 – 4: Entry of the column number in which the text for the 2nd, 3rd or 4th lines is located. If the
character string \u or \c are present then they are treated as an optional or non-optional
line break. If break characters are contained in the previous lines, then the line if moved
accordingly.
1) There should be no spaces between the numbers. If the number does not correspond to the range of values, or if there is no number in the filed, then
this line can not be added and therefore it will be skipped and the process will continue with the next line.
Save settings: The current column settings are saved using the “Save settings” button. These settings only
apply for the user who is currently logged into Windows (every user has their own settings).
Load settings: The settings are reloaded using the “Load settings” button or serve as initial values when
the program is started.
Select all: All lines are selected (marked) using the “Select all” button.
Invert selection: The "Invert selection" button inverts the selection (marked lines) so that the unmarked lines
become marked and the marked lines become unmarked.
Convert umlauts If the „Convert umlauts from ANSI to ASCII“ option is activated then the text entered
from ANSI to using the ANSI character (used by Windows) is converted into the ASCII character set
ASCII: (used by the BMZ Integral). This affects the country specific special characters (e.g. um-
lauts). IntegralText uses the ASCII character set.
Paste into: It is possible to select the control unit to which the data should be assigned using the “SC”
list.
The element type to which the data should be assigned (see element types) can be selected
using the “Element” list.
Insert selection: Using the „Insert selection“ button, only the selected (marked) lines are added.
Insert all: All lines are added using the "Insert all" button, regardless of which lines are marked. If an
element that is to be inserted has the number of an element that already exists, then a dia-
logue box appears, in which it is possible to select whether the element should be overwrit-
ten.

Copy to another element...: Copies the marked records from the list view to another element type in the same
document. If you have created records for the element type „operating panel“, they can e.g. be copied to the
„Printer“ element type. The records are not copied into the clipboard in this instance.
Insert into another element...: Inserts the contents of the clipboard into a slave control unit for another ele-
ment type. If a record already exists with the same number, then a dialogue box appears, in which it is possible
to select whether the record should be overwritten. This command is unavailable, if the clipboard is empty or if
the data does not have the correct format.
Edit sub-number...: It is possible to edit the subnumber using this command, even if the entry field is deacti-
vated. The sub number (detector number) is normally entered directly in the entry bar. This is only possible for
the “Zone” element type. For other element types a sub number is not meaningful, but it is possible to enter
one with the help of this dialogue box.
Edit marked records...: Edits the records marked in the list view, and assigns the same text to all of them.
The text of the last marked record is displayed in the dialogue box. At the same time, the text type, which
should be entered or modified is activated. Text types, which should not be altered should be deactivated. If a
text type is activated, but the entry field is empty, then this text type is deleted for all marked records.
Text / Special Text: The text is entered in the fields "Line 1" and "Line 2". In the event that more than two
lines are required, then the remaining lines should be entered in the field “Line 3”. Line
breaks can be entered in the field “Line 3” by entering the characters “\u”.
IntegralText checks the number of characters entered in the first two lines. You may
only enter as many characters as have been defined in the Settings dialogue box.
HighEnd-Text: The text in the entry field is used for being displayed on the HighEnd control panel. The
number of available characters is displayed next to the entry field. Negative numbers
mean that the text is too long and will be truncated.
Info-Text: This text can not be exported. It serves solely for entering user-defined information.
Delete record: Deletes the marked records.
Mark all: Marks all records of the current element type:
Go to...: Opens a dialogue box for entering the element and sub number. If no sub number is entered, then the
first record with the element number is marked.
Search...: Searches in the records of the current element type for the text that is entered.
When searching, forced (\c) and unforced (\u) line breaks are replaced by two spaces, i.e. if the search string is
entered containing two consecutive spaces, then this will also be found in the first part is at the end of one line
and the second part starts at the beginning of the next line.

5.2.4 BMZ menu

The BMZ menu contains the following commands:
New SC...: Adds a new main or slave control unit.
Slave control unit number: Selects the SC number. Only numbers are available are listed.
Control Panel Type: Type of BMZ. (Maxima or Integral)
Master control unit: A master control unit displays all SCs. Therefore when exporting it, the texts
for all control units are entered into the export file. This is only possible using
a BMZ Integral.
Import new SC...: Pastes an existing file as a new SC.

After selecting the file, the SC number and the BMZ type for the new SC must be entered. If several SCs exist
in the selected file, then this must be carried out for each SC. For the SCs which should not be added, the dia-
logue box should be closed using „Cancel“, to be able to continue with the next SC.
a BMZ Integral.
Delete SC: Deletes the currently selected slave control unit (SC). All texts for this SC are also removed.
Change SC...: Changes the settings for the currently selected slave control unit (SC).
a BMZ Integral.
Properties SC...: Changes the properties for the currently selected slave control unit (SC). These settings are
saved in the file. If this properties window is shown upon opening or exporting, then no changes can be made.
There are the following possible settings in the dialogue box:

 SC info tab:
Text name: The text name can have a maximum of 31 characters.
Version: Enter the version of the text here (version, revision, level).
The numbers may be between 0 and 255.
max. characters per line: Maximum number of characters per line for normal text. (only the first two
lines are checked).
max. characters per line for Maximum number of characters per line for special text. (only the first two lines
special text: are checked).
 File info tab:

Project engineer: Name of the project engineer.
Info: Further information can be entered here.
Show this field when: It is possible to select whether a dialogue window with these properties should
be shown when opening, saving and/or exporting a file.
 Export tab: These settings apply for the selected control unit.
Text: Fill lines with spaces -> Text line is filled up with spaces up to the maximum
Special Text: permitted number of characters per line. (only for the first two lines). This may
be necessary for connecting foreign systems (e.g. PSA, Global Alarm Server
etc.). Fill up second line, even when empty: The second line is filled with
spaces even when no text has been entered in this line. This may be necessary
for connecting foreign systems (e.g. PSA, Global Alarm Server etc.).
The special text can be displayed on the FBF.
 Export general: These settings apply for the entire document.

SC name for master control Select whether the normal text for the master control unit should be ex-
unit: ported before or after the SC names, e.g.:
SC name
Text line 1
Text line 2
SC name for master control Select whether the HighEnd text for the master control unit should be
unit HighEnd text: exported before or after the SC names, e.g.:
SC name
HighEnd Text line 1
HighEnd Text line 2
Normal Text for Select whether the normal text should be exported before or after the HighEnd
HighEnd-Text: Text. e.g.:
SC name (optional, only possible for master control unit)
Text line 1
Text line 2
HighEnd Text line 1
HighEnd Text line 2
5.2.5 View menu

The view menu contains the following commands:
Tool bar: Toggles the toolbar on/off.
Status bar: Toggles the status bar on/off.
Tab bar...: Changes the settings of the tab bar. The dialogue box makes it possible to toggle the tab bar on or
off, or to choose whether it should be displayed at the top or the bottom.
The tab bar is used to change quickly between the opened documents. It shows the filenames as register cards.
Show tab bar: Activates the tab bar.

Only display if there is The tab bar is only displayed, if more than one document is opened (or a docu-
more than one window ment has several windows).
open:
Top: The tab bar is shown at the top of the screen.
Bottom: The tab bar is shown at the bottom of the screen.
Character table: Toggles the character table on/off. If the character table is displayed then a tick is shown
next to this menu entry. In the character table, all the characters that can be used1), are shown. While this dia-
logue window is open, it is possible to continue working normally with IntegralText. The dialogue can be
moved using the Move option. To close the character table, click on the „Close“ button, or click on the symbol
in the toolbar.
How to enter characters which are not on the keyboard:

1. Left click with the mouse on the characters that are required. They will then appear at the cursor posi-
tion in the entry field.
2. Select the "copy" button (the selected characters are copied into the clipboard).
3. Click on the line of the entry field in the entry bar, in which the characters should be entered.
4. Select the "Insert" command.
1)To use all the characters with an ASCII code of more than 127 (the last four lines in the dia-
logue box), the operating panel’s display must be capable of showing graphics (not the case for
German operating panels). The German umlauts (upper and lower case) are however possible.
List view setting...: Sets the format of the list view.

Data The list view can use a single line or multiple lines. In single line mode, all texts are shown
in a separate column. In the multiple line mode, the selected text types are shown below
one another.
Lines Select the text types to be displayed. This is only possible if the list view has been set to
“multiple line” mode.
Show gridlines Shows gridlines in the list view between the records.

5.2.6 Options Menu

The options menu contains the following commands:
Settings...: Opens the settings dialogue box. These settings only apply to the active document and are also
saved in this document.
 Language:
Code page (Language) of the The code page (language) in which the texts are written can be set (must be
inputted texts the same as the language setting in the Integral Listgenerator). This setting is
required for the language-specific special characters (e.g. umlauts).
 Entry bar:
Auto increment: The element number is increased by one after a new record is generated, or a
record is changed.
 automatic: For zones the element sub number is increased, for all other
element types the element number is increased.
 only Element Number: Only the element number is increased.
Do not delete text after inser- The data in the entry fields are not deleted after a new record is created or a
tion: record is modified.
 Export general: Description under menu BMZ / SC properties…

Default-Settings...: Opens the Default settings dialogue box. The default settings apply when creating a new
file or act as the general settings of IntegralText.
 Language:
Code page (Language) of the in- The code page (language) in which the texts are written can be set (must be
putted texts the same as the language setting in the Integral Listgenerator). This setting
is required for the language-specific special characters (e.g. umlauts).
IntegralText language (Pro- If the installation CD supports several languages, then the language can be
gram)(Only default settings): changed for IntegralText. This setting has no effect on the created or modi-
fied files.
 Company:
Company Logo The company logo can be selected here. It is used when printing.
 General:
Show File Info dialogue box be- Shows the dialogue box for entering the version and the name of the texts
fore saving: (only in documents with only one control unit).
Print cover sheet: A cover sheet is printed for the first page.
Print lines between detector Lines are printed between the detector zones, so that the individual ele-
zones: ments can be visibly separated from the next detector zone.
Print filename path: The complete path is printed in the header before the filename. Where
there is a long file path, there might not be enough space, in which case the
filename or path is truncated.

 Text:
max. characters per line: Maximum number of characters per line for normal text. (only the first two
lines are checked).
max. characters per line for spe- Maximum number of characters per line for special text. (only the first two
cial text: lines are checked).
 File info: Description under menu BMZ / SC properties…
 Export: Description under menu BMZ / SC properties…
 Export general: Description under menu BMZ / SC properties…
 Input bar: Description under menu Options / Settings…
 List view:
Data: The list view can use a single line or multiple lines. In single line mode, all
texts are shown in a separate column. In the multiple line mode, the se-
lected text types are shown below one another.
Lines: Select the text types to be displayed. This is only possible if the list view has
been set to “multiple line” mode.
Show gridlines: Shows gridlines in the list view between the records.
Folders...: For setting different folders for IntegralText.
Working folder: The "Open", "Save as" and "Import SC" dialogue box uses this folder. Enter the
complete path on the entry field or select it by clicking on the button. If you
select the "Last opened folder" option field, then it is not possible to enter the file
path. The dialogue fields are then always set to the folder in which a file was last
selected.
Export folder: The exported texts are saved in this folder.

Enter the complete path on the entry field or select it by clicking on the but-
ton. If you select the "Ask about folder when exporting" option field, then it is
not possible to enter the file path. You will be asked to specify the folder every
time when exporting. You can also enter which folder should be suggested as
standard.
Keywords file...: Entry about the keywords file, which is used to open IntegralText files. The same keywords
file as the text parser uses must be set. The element types in the BMZ Integral about which texts can be written
are entered in the keywords file. The keywords file should contain at least 25 keywords.

5.2.7 Window menu

The Window menu contains the following commands:
New window: Opens the same document in a new window. Several document windows can be opened. It is
possible then to look at different sections or views of a document at the same time this way. In the event that
the contents of the file is changed in one of the windows that is opened, then the changes are adopted by all the
windows that contain the same document. If a new window is opened, then it becomes the active window, and
is displayed in front of all the other opened windows.
Overlapping: Arranges the windows in IntegralText so that they overlap one another.
Side by side: Arranges the windows in IntegralText so that they next to one another.
Arrange symbols: Arranges the windows that have been minimized by IntegralText. If there is an open docu-
ment window there, it can occur that some or all symbols are covered, because they are underneath the docu-
ment window.
1, 2, 3, 4: At the bottom of the Window menu, IntegralText displays a list of the currently opened window
views. If there are more than nine of them, the command „Further windows“ is displayed, with which you can
open a dialogue box with all the windows. A tick is shown in front of the active window. A window view can
be selected from the list to activate it.
5.2.1 Help menu

The Help menu contains the following commands:
Help to IntegralText: Opens the Help program and shows the start page.
Read me...: Displays the "ReadMe.txt" file. It contains important information about the IntegralText which is
not contained in this help file.
Info about IntegralText...: In order to display the copyright information and the version number of the copy
of IntegralText.

IntegralText  Structure of a Record of the BMZ Integral
5.3 Structure of a Record of the BMZ Integral

A record can consist of several text types.
 Text for operating panel and printer (normal text)

 Text for FBF (special text)
 Text for HighEnd control panel (HighEnd Text)
 Other information (Info Text)
Every record is assigned to an element type and has an element number. For the 'Zone' element type it is possi-
ble to enter a subnumber (detector number) - (This input is possible for all element types, but it is not always
meaningful to do so).
Normal and Special Text:

There are fields for the first three lines to be entered. If more lines are required, then these are entered in the
field for the third line and are separated from one another by entering the \u character combination.
Text output on display:

The BMZ Integral’s display shows 20 characters per line. The first two lines must be visible straightaway after
pressing the „Site info“ key, and further lines are reached by scrolling.
Text output on printer:

The BMZ Integral’s printer prints 24 characters per line. All lines are printed underneath one another.
Text output on FBF:

Number of characters and lines should be found out from the technician.
Normal Text:
The text should not have more than 20 characters per line, so that the output on the display and on the printer is
identical. If, for example, two text lines each with 22 characters are available, then on the display, after 20 char-
acters have been displayed, then subsequent ones appear on the next line and the second line is moved to the
third or fourth line. The text is on two lines on the printer.
If another text output device (e.g. external printer, PSA, management system etc.) is connected to the BMZ
Integral, then the technician must be consulted about the number of characters per line and the number of lines.
If 'forced breaks' are used, then the BMZ Integral checks whether the text until the next break still fits on the
line for every output device. The characters must be counted to know whether a forced break is required or not.
When using forced breaks, please consult the technician beforehand (the character combination for the forced
break is \c, and that for a normal line break is \u).
HighEnd-Text:
There is a text area for entering the text. The text is entered here (change of line using ENTER). The free width
on the display, in pixels, is shown next to the entry field. Negative values mean that the text is too long and will
be truncated. The font that is used does not exactly correspond to the one that is used on the HighEnd control
panel. The entered text might differ from the actual line length, but the numbers next to the entry field are ex-
actly correct.
When exporting the HighEnd-Text it is also optionally possible to write the normal text (if available) before the
HighEnd-Text.
Info-Text:
There is a text area for entering the text. The text is entered here (change of line using ENTER). This text can
not be exported! It serves solely for entering user-defined information.

IntegralText  Structure of a Record of the BMZ Maxima
5.4 Structure of a Record of the BMZ Maxima

For the basic structure of a record see the structure of a record of the BMZ Integral.
Differences to the Integral text format:
 A record may contain a maximum of two lines (additional lines are not saved).
 The lines must have a length of 20 characters (any characters above that will be truncated).
 Only element types Zone, Input, Output and Monitored Output are allowed (all records with other element
types are not saved).
 The highest permitted element number is 4095 and for monitored outputs 256 (records with higher element
numbers will not be saved).
 Only for Zone element types are sub numbers allowed (for records of other element types with sub
numbers are not saved).
 The highest allowed sub number is 99 (records with higher sub numbers are not saved).
 Forced line breaks are not allowed (when the records are saved, then the forced breaks are replaced by a
space, after 20 characters a line break is inserted, and after another 20 characters the text is truncated).

IntegralText  Available element types
5.5 Available element types

Currently available element types (from Integral Software Version 5.0.0)
0 Zone *) Detector zone / detector (sub numbers are possible)
1 Input *) Switching contacts connected to the BMZ

Devices which are controlled by the BMZ (fire prevention doors,
2 Output *)
sirens, ...)
3 External Alarms or faults from external devices
4 Printer Internal (operating panel printer) or external printer
5 operating panel Indicator operating panels (not Fire Brigade Control Panels)
6 Battery Battery in the BMZ
7 Mains power Power supply
8 ModAkt Module – active side
9 ModPas Module - passive side
10 Delay Delay switching (daytime / night time changeover)
11 Fire Brigade Control Panel Fire Brigade Control Panel
12 Subcontrol unit Subcontrol unit of the whole BMZ
13 Intervention Intervention
14 Indicator LED output for panel
15 wire Data connection between the subcontrol units
16 MasterSystem PC management system (e.g. SLS, ...)
17 Loop Loop circuit to which the detectors and modules are connected
18 ServiceTool Remote Maintenance
19 Maintenance Planned maintenance
20 extinguishing zone
Fault message to a slave control unit that a master control unit is miss-
21 Master control unit
ing
Fault message to a master control unit that a slave control unit is miss-
22 Slave control unit
ing
23 Network N3 connections
24 MonOutput *) BMZ Maxima monitored outputs
25 ExtPrinter BMZ Maxima external printer
The name of the element types is dependent on the keywords file used.
*) Only these element types are used with the BMZ Maxima.

IntegralText  Process for producing the records
5.6 Process for producing the records

A record (text) should be created for every available element. There are various text types.
 Text for operating panel and printer (normal text)

 Text for FBF (special text)
 Text for HighEnd control panel (HighEnd Text)
 Other information (Info Text)
Process for entering a new record:
1. Choose the control unit, for which the record should be created.
2. Select the element type from the list, for which the record should be created.
3. Enter the element number and sub number.
4. The text is entered in the fields "Line 1" and "Line 2". In the event that more than two lines are re-
quired, then the remaining lines should be entered in the field “Line 3”. Line breaks can be entered in
the field “Line 3” by entering the characters \u. IntegralText checks the number of characters entered
in the first two lines. Only as many characters can be entered as have been entered in the „Settings"
dialogue box (Options / Command settings menu. See also toolbar / characters per line). If necessary
the other text types can also be entered, or existing records can be changed later.
5. By pressing ENTER or the “new” button, the record is added to the end of the list, and is marked with
a blue arrow .
If the element type is not available, then it is added in the tree view. If a record with the same number already
exists, this is displayed in the list view and marked with a red arrow . It can be decided whether the existing
record should be overwritten. Moreover, only the text types can be added that are selected.
If auto increment is activated, then after a record is successfully added or changed, then the element number is
increased by one. Depending on settings, the text remains in the input fields or is deleted (see Options / Com-
mand settings menu).
Process for modifying an existing record:
1. Select the record in the list view. This record is copied into the fields of the input bar.
2. Change or supplement the individual text types. If the number or element type has been changed, then
a new record is generated.
3. By selecting the „Change“ button or entering the keyboard shortcut the record is changed in the ad-
dress and marked with a blue arrow .
4. If the number or subnumber was changed, then this record is treated like a new one, and it can be de-
cided whether the new record should be added. Moreover, only the text types can be added that are se-
lected.
increased by one. Depending on how the system is set, the text will remain in the input fields or will be deleted.
However, the text is not loaded from an existing record (see Options / Command settings menu).
Process when modifying the text types for existing records:
1. Select the control unit, the element type, and if necessary a sub number or selection of the existing re-
cord in the list view.
IntegralText  Process for producing the records
2. Enter the desired type of the text.

3. So that the existing text types remain unchanged, only the text type to be changed can be selected in
the „Enter / modify text type“ field.
4. By selecting the “Change” button or entering the keyboard shortcut the record is changed in the ad-
dress and marked with a blue arrow .
5. If the number or subnumber was changed, then this record is treated like a new one, and it can be de-
cided whether the new record should be added. Moreover, only the text types can be added that are se-
lected.
increased by one. Depending on how the system is set, the text will remain in the input fields or will be deleted.
However, the text is not loaded from an existing record (see Options / Command settings menu).
The “Edit marked records” (Edit menu) command can also be used to change one or more records which
should have the same text.
Example:
First a detector zone number without a detector number must be written for the “Zone” element type. This
text is output when a detector zone is disabled and should describe the detector zone’s general location (e.g. for
zone 15: "Room 1st floor" or Zone 21: "Ground floor kitchen").
Then a record must be created for every detector (e.g. for detector 15/1: "1st floor room 101" or detector 21/7:
"Ground floor kitchen - dishwasher").
If a record is not created for a detector, then a text is used that is created without a detector number.
The location of the detector can be found from the plans. The number must be compared with the submitted
plans.
The remaining element types of the BMZ Integral can be obtained from the technician.

WinLoader  Installation and Starting the Program
6 WinLoader
All functions which WinLoader has are described in this chapter.
6.1 Installation and Starting the Program
WinLoader is automatically installed during the Integral software setup process. It is preconfigured for use with
the version of the software with which it has been shipped. It is therefore recommended not to make any other
changes in settings, apart from those necessary settings for the communications port described below.
The program is started by clicking on the WinLoader in the start menu, or the quick start bar on the desktop.
After WinLoader has been started, the settings must be

changed using the “Options/Communications…”
menu item.
The used COM or USB port must be selected. When

using RemoteAccess settings for the RemoteAccess
Server can also be used.
The new configuration settings are then automatically

saved into the currently active profile by clicking on
the “OK” button.
Information about using the USB interface can be found in the hardware description.

WinLoader  Display in WinLoader when connected
6.2 Display in WinLoader when connected

Depending on the type of connection (COM or USB) with the MCU of an Integral, other information is also
displayed. For example, with a USB connection with an B5-MCU other data is in the flash memory than when
there is a COM connection with a B3-MCU32E2. This is linked to the control unit's operating system. With the
introduction of the B5-MCU, a new operating system is also used for the Integral.
6.2.1 B3/B4-MCU32 display

If the connection to the fire alarm control panel has been made successfully, then various items of information
are displayed about the control panel on the PC monitor. The display is split into three areas:
 Control Panel Information: Control panel type, subcontrol unit number, program status, booter version,
flash memory size, RAM size, EEPROM size and free flash memory of the attached (selected) MCU
 Files in Flash Memory: Software components which are currently stored in the BMZ’s flash memory.
Structure: Determined by software compatibility
Data: Version number of the data - project-specific
Name: Description and additional information which are entered by the programmer of the system.
 Local files: Software components which have been selected by the user for uploading into the BMZ.

WinLoader  Display in WinLoader when connected
6.2.2 Display B5-MCU32 / B6-BCU

If the connection to the fire alarm control panel has been made successfully, then various items of information
are displayed about the control panel on the PC monitor. The display is split into three areas:
 Control Panel Information: Control panel type, subcontrol unit number, program status, booter version,
flash memory size, RAM size, EEPROM size of the attached (selected) MCU
 Files in Flash Memory: Software components which are currently stored in the BMZ’s flash memory.
Structure: Determined by software compatibility
Data: Version number of the data - project-specific
Name: Description and additional information which are entered by the programmer of the system.
 Local files: Software components which have been selected by the user for uploading into the BMZ.

WinLoader  Establishing a connection using COM or USB
6.3 Establishing a connection using COM or USB

Depending on the type of Integral MCU used, a different type of connection must be selected (COM or USB).
The appropriate profile can be selected using the “Options / Load profile…” menu item. The connection type
is already set in the profiles.
6.3.1 Establishing a connection over the COM interface

In order to display information about the fire alarm control panel or to upload or download files a connection
first needs to be established from the PC to the control panel. The following steps must be taken:
 Connect the Service PC cable to the front side of the B3-MCU32E2 or the B4-BCU A2E and to the PC
(serial interface COM1 .. COM8).
 Start WinLoader on the PC.
 Manually select the profile or connection type using the „Options / Communication...“ menu item.
 Select local or central establishing of connection.
Local Download over COM interface

To establish a connection for a local download, the following procedure must be observed:
Select the “Local” radio button, to select the local connec-

tion.
Click on the “Connect” button to start establishing the

connection.
Pull the reset pin (RESET) out briefly and push it back in.
The establishing of the connection begins. If the connec-

tion is established successfully, then various information
about the Flash memory and its configuration is displayed
in the top third of the screen (see Display chapter). If a
connection fault occurs, then this is indicated by means of
an error message.
Communications in local download mode can then only be established with the BMZ Integral or BMZ Integral
C/C1 which is directly connected via the USB cable. In the case of an Integral subcontrol unit loop (2-16
SCUs) the loading process must therefore be carried out separately for each subcontrol unit.
When communications are established, the control panel is placed out of order. A subcontrol
unit loop only becomes fully functionally again, when ALL subcontrol units have been restarted
using the SAME software components.

Centralised Download over COM interface

To establish a connection for a centralized download, the following procedure must be observed:
Select the option field „Centralized“, to select the central-

ized connection.

connection.
The connected is established immediately WITHOUT

resetting the control panel!
A B3-MCU32E2 or B4-BCU A2 or newer are required to

do this. Fault-free system operation (both sides A + B are
in operation) and an intact subcontrol unit loop are also
basic requirements.
If the connection has been successfully established, then

the Flash memory and configuration information are dis-
played as standard about the directly connected MCU in the
top third of the screen.
WinLoader then tries to detect all subcontrol units which

are currently available. If more than one MCU is recog-
nised, then the state of other control panels can also be
displayed by selecting the available MCU addresses:
If a connection fault occurs, then this is indicated by means
of an error message.
During the entire connection process, and the entire loading process, all subcontrol units con-
nected to the control panel remain fully operational. Only once all subcontrol units have been
automatically reset, is the BMZ actual placed offline for a short period of time. The subcontrol

6.3.2 Establishing a connection over the USB interface

In order to display information about the fire alarm control panel or to upload or download files a connection
first needs to be established from the PC to the control panel. The following steps must be taken:
 Connect the USB cable to the front side of the B5-MCU32 or B6-BCU as well as to the PC.
 Start WinLoader on the PC.
 Manually select the profile and connection type using the “Options / Communication...” menu item.
 Select local or central establishing of connection.
 Set the control unit address (only for local download)
Local Download over the USB interface

To establish a connection for a local download, the following procedure must be observed:
Select the “Local” radio button, to select the local connec-

tion.
connection.
Pull the reset pin (RESET) out briefly and push it back in.
The establishing of the connection begins. If the connec-

tion is established successfully, then various information
about the Flash memory and its configuration is displayed
in the top third of the screen (see Display chapter). If a
connection fault occurs, then this is indicated by means of
an error message.
The control unit address is defined after the local connec-

tion has been established using the SCU-number field in
WinLoader. If the number is shown in black, then this is
the current value stored in the control unit. If a new SCU
number is selected, then it will appear in red. After restart-
ing the system, the new SCU number is adopted and then
when the connecting is established again locally, it is
shown in black again.
Communications in local download mode can then only be established with the BMZ Integral
which is directly connected via the USB cable. In the case of an Integral subcontrol unit loop (2-
16 SCUs) the loading process must therefore be carried out separately for each subcontrol unit.
When communications are established, the fire alarm control panel is placed out of order. A sub-
control unit loop only becomes fully functionally again, when ALL subcontrol units have been
restarted using the SAME software components.

WinLoader  Feeding in data (Download)
Centralized Download over the USB Interface

To establish a connection for a centralized download, the following procedure must be observed:
Select the option field „Centralized“, to select the central-

ized connection.
Click on the „Connect“ button to start establishing the

connection.
The connection is established WITHOUT resetting the

BMZ!!!
Fault-free system operation (both sides A + B are in op-

eration) and an intact subcontrol unit loop is basic re-
quirement.
If the connection has been successfully established, then

the Flash memory and configuration information are dis-
played as standard about the directly connected MCU in
the top third of the screen.
WinLoader then tries to detect all subcontrol units which

are currently available. If more than one MCU is recog-
nised, then the state of other control panels can also be
displayed by selecting the available MCU addresses:
If a connection fault occurs, then this is indicated by
means of an error message.
During the entire connection process, and the entire loading process, all subcontrol units con-
nected to the control panel remain fully operational. Only once all subcontrol units have been
automatically reset, is the BMZ actual placed offline for a short period of time. The subcontrol
6.4 Feeding in data (Download)
One or more components can be simultaneously uploaded. The components are added to a file list ('Local files'
list). All entries in the file list are written into the B3-MCU32E2, B4-BCUA2E or B5-MCU32’s flash memory in
the process. For tasks that are frequently repeated, it is possible to save as many file lists (*.LST files) (using the
menu “File / Save File List...”) and load them again (“File / Load File List …”).
The following components can be added to the file list using the “File / Add to List…” menu item. The fol-
lowing file types are supported:
Filetype extension LD CD
Operating program B3/ B4-MCU b3mcu_*.bin (e.g.: b3mcu_6_1_3.bin) x
Operating program B5/B6-MCU b5mcu_*.elf (e.g.: b3mcu_6_1_3.elf) x
Configuration *.lpd x x
Customer texts *.tpd x x
Memory image *.mem x
The other components of the Integral Software, such as standard texts and the program library are automati-
cally added by WinLoader.
In order to feed in the data from the file list into the control unit, choose the menu item “Flash / Read in
Data” or double click on the or button.
6.4.1 Download over COM interface

The download using the COM interface option is only available for the B3-MCU32E2 and B4-BCUA2E. Two
variations are differentiated between. The local download must be undertaken at least once before the commis-
sioning of the Integral. If the system is then functional, and there are no faults in the system, then the central-
ized download can be used.
If the local files are successfully transferred to the

flash memory of the MCU using the local download
method then a positive message appears: The con-
trol unit must now be reset. (Pull the reset pin and
push it back in)
For the centralized download using the COM inter-

face, the data integrity of all control units is checked
once the loading process has finished, and if this has
happened successfully they are then reset at the
same time. They then restart with the new data. The
time it takes for them to restart is substantially
quicker than if they are RESET using the reset pin.
A report is then generated about the upload process,
and can be saved as a text file is required.

6.4.2 Download over the USB interface

The download using the USB interface option is only available for the B5-MCU32 and B6-BCU. Two varia-
tions are differentiated between. The local download must be undertaken at least once before the commission-
ing of the Integral. If the system is then functional, and there are no faults in the system, then the centralized
download can be used.
If the local files are successfully transferred to the

flash memory of the MCU using the local download
method then a positive message appears: The con-
trol unit must now be reset.
For the centralized download using the USB inter-

face, the data integrity of all control units is checked
once the loading process has finished, and if this has
happened successfully they are then reset at the
same time. They then restart with the new data. A
report is then generated about the upload process,
and can be saved as a text file is required.
6.4.3 Check Centralized Download
The menu item “Flash / Check Centralized

Download” can be used to check whether all MCUs
in a SCU loop have successfully received the con-
figuration data.
A report is issued.
If an error is displayed, then the affected subcontrol units must be located and checked.
Where any doubt remains, repeat the loading process with a local download!

WinLoader  Delete Files (only in Local Download mode)
6.5 Delete Files (only in Local Download mode)

The entire Flash memory of the B3-MCU32E2, B4-BCUA2E, B5-MCU or B6-BCU is deleted using the “Flash
/ Delete everything” menu item.
If only a certain component should be deleted from the Flash memory, then this component should be marked
in the “Files in Flash” list and deleted by pressing the “Del” key or by selecting the “Flash / Delete Entry”
menu item.
6.6 Download Files (only in Local Download mode)

It is possible to download certain components (configuration, operating program and customer texts) from the
fire alarm control panel and to save them in separate files. Furthermore, it is also possible to save the entire
contents of the flash memory in a single file (flash memory image). This is done via the “Flash / read files”
menu item.
All files that have been downloaded can then be uploaded again into the fire alarm control panel.
It is not possible under any circumstance to edit downloaded files or to change them! The read-
ing out of the files is intended for backup purposes (e.g. when changing the MCU).
6.7 Options
In this chapter the possible settings for the menu item “Options” are described.
6.7.1 General
For the establishment of a connection to function correctly, the
relevant library must be entered in the “Options / General…”
dialogue, with the same version being entered as was used to create
the configuration in Listgenerator.
The following libraries are required for this:

Version check Version.dat
Program Library b3.plb
C16x Booter C16XBOOT.plb
Language Library b3.llb
User Library Schrack.ulb
The WinLoader is always shipped with the applicable settings for the version shipped, and it is
recommended that only an experienced user should make any changes!!
6.7.2 Communications Settings

COM1 is set as standard in the software installation. Ports COM 1 to COM 8 can be freely selected. In the
event of transfer faults occurring frequently, it may be advisable to reduce the baud rate. Data must always be
simultaneously transferred to sides A + B. On B5/B6 “USB – Port” must be selected. If the option RemoteAc-
cess was selected during the installation, then settings for the RemoteAccess Server can also be set.
6.7.3 Language
The WinLoader supports German and English language operation and can be changed from one language to
the other during operation.

WinLoader  LocalFlash
6.7.4 Profiles
Any alteration made to the options listed above is saved in the currently active profile. All settings are therefore
once again available the next time the program is started.
It is possible to use several different configurations from version 2.0.0 and above by saving and loading as
many profiles as required. The profiles are saved in the Windows Registry. The currently active profile is dis-
played in the title bar in between square brackets [ ].
It is possible to save the current profile under whichever name you wish by using the “Options / Save profile
…” menu item. Using the ‘Options / Load Profile …’ menu item, a saved profile can be loaded. A profile that
has become superfluous to requirements can be deleted from the registry using the “Options / Delete Pro-
file...” menu item.
6.8 LocalFlash
The LocalFlash is another flash memory, which is independent of the MCU’s central memory. This means that
the operating software of a module is no longer stored in the MCU, but is stored in the module’s local memory
(e.g. B5-CIE). The WinLoader’s LocalFlash function allows it to access this memory in order to make altera-
tions to data required for operation when the Integral Software is updated at a later date. It is also possible to
store optional files from a module in the flash memory. The operating files as well as the optional files can be
uploaded independently and separately to one another.
The LocalFlash function is only available for the Integral HighEnd Operating Panel (B3-CIE)
and can only be executed during centralized download. The LocalFlash function is supported
from the B3-MCU32E2 or B5-MCU32 as well as from version 5.1 of the Integral Software Pack.
6.8.1 Operating Files

The operating files of a LocalFlash module consist of several program components. The operating program is
stored in the program library (as a .plb file), with the standard texts and the character set being stored in the
Language Library (as a .llb file). These program components were already stored in the module’s flash memory
in the factory.
It is only necessary to update the operating files when there is a new version of the Integral software issued.
6.8.2 Uploading Operating files

By clicking on the button, a dialogue box for the LocalFlash
process is opened. If a connection to the control panel al-
ready exists, then all the control panels that are connected
to one another and the modules contained within them are
read out and listed.
If there is no connection to the control panel, then a con-
nection must be established by clicking on the button.
Modules which contain a LocalFlash memory are denoted
by this symbol.
This symbol next to the module description denotes a
module without LocalFlash memory.
The number in square brackets next to the module descrip-
tor denotes the connection slot number in the module rack.

If a module in the left pane is marked, then the operating

data as well as information about the software version used
and additional information (e.g. language pack) for this
module is displayed in the right pane.
If the module in question already has the current operating

software installed, then it will be displayed as per the figure
to the right.
If an update is available for a module, then this is automati-

cally denoted by the red symbol and a red arrow in the
right pane.
The operating files that are required are automatically gener-

ated by WinLoader from the current version of the software
and do NOT need to be selected. No new update available
The process of uploading new files is known as LocalFlash

(as longer as no optional files need to be uploaded), and
happens using the menu:
„Flash / Read in files“ or by double clicking on the

button.
Once a successful Flash update has taken place, then the

control panel must be reset so that the new files can take
effect.
Update available
The WinLoader is always shipped with the applicable settings for the version shipped, and it is
recommended that only an experienced user should make any changes!!
If a device can not be accessed, or it is unavailable when a

connection has been established, e.g. it has been configured
with the “not always available” option, or it has a fault, then
this device is shown as per the figure to the right with a
symbol next to it.

6.8.3 Optional Files

It is also possible to upload optional files (currently only for the high end operating panel) such as a reaction
texts into the module’s flash memory. The files required for this are found in the user library (*.ulb file), which
can be defined using the “Options / General…” menu. The control panel does not need resetting once op-
tional files have been uploaded.
6.8.4 Uploading a Background Logo

If the high end operating panel has no background logo, then the display will display the name of the company
in text, as it was set in the Listgenerator configuration software, when the display is in a fault-free operating
mode. The background logo is saved in the user library.
The logo is uploaded by right-clicking on the pane below the

pane title “LocalFlash – optional data” and by then selecting
the “Add optional files...” menu option.
In the dialogue box that appears, the option “HighEnd-

LogoBitmap” must be selected and then confirmed with
OK.
The LogoBitmap is read into the High End Operating Panel

by using the menu item “Flash / Read in data” or by double
clicking on the button.
Successful data transfer into the LocalFlash is confirmed by

this message. It is not necessary to the reset the system. The
new background logo will only be visible once the back-
ground has been changed (e.g. by calling up and exiting the
operating panel menu again).

6.8.5 Delete Background Logo

It is only necessary to delete the background logo if a background logo should no longer be displayed. If the
logo, however, only needs to be replaced, then it is not necessary to delete the existing logo. Uploading the
background logo again replaces an existing background logo automatically.
The new background logo will only be visible once the background has been changed (e.g. by calling up and
exiting the operating panel menu again).
To delete the background logo, the correct line must be

selected by right clicking on it, and then clicking “Delete” in
the context menu which subsequently appears.
After confirming that the deletion process should take place,

the background logo is permanently deleted from the high
end operating panel’s flash memory. The high end operating
panel now has no background logo, so therefore the display
will display the name of the company in text, as it was set in
the Listgenerator, when the display is in a fault-free operat-
ing mode.

6.8.6 Uploading Reaction Texts

The reaction texts are saved in the high end operating panel’s LocalFlash memory, and are displayed instead of
the customer texts. It is, however, also possible to display the customer texts (location information) by also
pressing one of the multi-function keys.
Reaction texts can be generated using version 3.0 or higher of the IntegralText program.
The reaction texts are uploaded by right-clicking on the pane

below the pane title “LocalFlash – optional data” and by
then selecting the “Add optional files...” menu option.
In the dialogue box that appears, the option “Measuresinfo-

texts” must be selected and then confirmed with OK.
After clicking on the OK button, a dialogue box opens to

allow you to chose the correct Integral text file (*.tpd). Then
the required file should be chosen.

The file with the reaction texts is read in by using the menu
item “Flash / Read in data” or by double clicking on the
button.
Successful data transfer into the LocalFlash is confirmed by

this message. It is not necessary to the reset the system.

6.8.7 Delete reaction texts

It is only necessary to delete the reaction texts, if reaction texts are no longer required by the high end operating
panel. If the file containing the reaction texts only needs to be replaced, then the existing file does not need to
be deleted. Uploading the reaction texts file again replaces the existing one automatically.
To delete the reaction texts background logo, the correct

line must be selected by right clicking on it, and by then
clicking “Delete” in the context menu which subsequently
appears.
After confirming that the deletion process should take place,

the reaction texts are permanently deleted from the high end
operating panel’s flash memory. There are now no longer
any reaction texts in the high end operating panel.

ServiceAssistant  Starting the Program
7 ServiceAssistant
ServiceAssistant is a tool in its own right and is included in the Integral Software Pack. It is used as an assis-
tance tool for the commissioning, maintenance and servicing of the Integral System and consists of the follow-
ing program components:
 ServiceMonitor
 LoopAssistant
 NetworkMonitor
 NetworkAssistant
7.1 Starting the Program
The program is started as per any other Integral Soft-

ware tool, by clicking on the ServiceAssistant program
icon in the start menu, quick start panel or desktop (in
this instance, for example, it is being executed using
the start menu).
7.2 Set project path
After starting the ServiceAssistant, a project path must

be selected. All generated files are saved to this project
path.
The standard project folder  is set when installing
version 6.1 of the software pack. The project folder
can be changed if required by using the “Directory...”
 button.
An existing project folder can be selected via the
dropdown menu . If there is direct input into the
dropdown menu, than a new project folder below the
project folder is created once the "OK" button is
clicked on.

ServiceAssistant  The User Interface
7.3 The User Interface

The ServiceAssistant is arranged as follows for all four program parts:
 Menu bar: Different functions can be started from the menu bar depending on the program.
 Program button for selection the individual parts of the program: It is possible to switch between the
individual parts of the program via the individual buttons.
 Shortcut bar: The most important program functions are available using individual quickstart buttons.
 Status bar: The communication status to the Integral System is displayed on the status bar.
7.4 ServiceMonitor
The ServiceMonitor receives all internal messages via the Integral System’s serial interface. Commands can also
be sent to the Integral System with help from a menu point. The most important functions of ServiceMonitor
are:
 Reading out the event log memory

 Displaying error counters
 Displaying version information
 Logging System Messages
 Send a Command
 Freeze outputs

ServiceAssistant  ServiceMonitor
7.4.1 Establishing a connection

For establishing a connection either the galvanically isolated RS 232 interface (B3/B4) or the USB interface
(B5/B6) on the BMZ Integral or BMZ Integral C&C1 can be used. The PC is connected using the Service PC
cable or the USB cable.
Connection settings
It may be necessary in the menu item „Settings“  to

adapt the COM-  or USB-interface  that is used.
A connection is automatically established when start-
ing the ServiceAssistant via the “Auto Connect” menu
item .
Connect/Disconnect Connection
A connection is established to the Integral System
using the „Action/Connect“ menu item  and the
connection is then disconnected using the menu point
„Action/Disconnect“ .
A connection can also be established or terminated

using the shortcut  .

7.4.2 Event memory

The Integral system contains an event memory, in which the last 200 events are saved in a non-volatile manner.
In the Integral Listgenerator settings can be configured, which allow a more specific compilation of the infor-
mation required (see trigger function): Moreover, in Listgenerator, the extended event log memory with SD
card (up to 65,735 entries) can be configured.
The event log memory is opened using the menu item

"Action/Event and Listview" .
The event log memory can also be opened over the

shortcut .
A section window opens . A context menu can be

opened by right clicking the mouse in the event log
memory section window. The memory is read out
using the “Eventmemory”  menu item.

In the dialogue window that subsequently appears, the

list range can be set that should be read out. If a SD
card has been configured, than more than 200 entries
can be read out.
In the section window  the selected list range of the

event memory, is displayed, sorted by date.
The „Eventmemory“ section window is subdivided into several columns:
Curr. ...: The serial number increments by one for every event that occurs, and is reset to the value 0
in the event of a cold or warm start.
Element: The element type (incl. subtype) of the event is displayed in this column.
Element no.: The complete element number is displayed in this column. The element number can vary
depending on element type.
Status Command In this column, the possible element states and commands of the relevant element are dis-
played.
Date: The date and time of the event is shown in this column.
Additional In- Additional system messages are listed in this column.

formation:

7.4.3 Trigger memory
For a defined event (a trigger) a copy of the event log memory (trigger memory) is made. The trigger is defined
using a Boolean definition and a threshold value (a quantity of events) in Listgenerator. Once the copy has been
created, then the Boolean definition is ignored for a configurable period of time (trigger off-time).
A context menu can be opened by right clicking the

mouse in the event log memory section window. The
memory is read out using the “Triggermemory” 
menu item. In the section window  the trigger mem-
ory is shown sorted by date.
The trigger lock time can be reset using ServiceMoni-

tor using the “Action/Trigger locktime Reset” menu
item  (e.g. after having read out the trigger memory).

7.4.4 Event dependent event list

A context menu can be opened by right clicking the
mouse in the event log memory section window.
Event-dependent event lists can be displayed by select-
ing from the individual menu points . In this in-
stance this is restricted to currently occurring events.
For the event-dependent event lists, there are five

different lists to choose from:
 Alarm list
 Fault list
 Deactivate list
 Trigger list
 Contamination list
Save event list

Every event list that is generated (incl. the event log memory and the trigger memory) can be saved as an XML
file using the context menu “Save EventList”. The XML files are saved in the project folder, which was selected
when starting ServiceAssistant. The saving of the file is confirmed by an information window.
The filename is made up of the following information:
Open EventList
A saved EventList (incl. event log memory and trigger memory) can be opened via the “Open EventList...”
context menu.
Restore Deactivations
A saved list of deactivations can be loaded into the event log memory section window by being opened. Using
the function „Restore DeactivateList“ the listed elements will be disabled. The disablement of the elements is
carried out regardless of their current state.

7.4.5 Show error counters

The error counters are automatically displayed when a system fault occurs. Not only is the fault displayed, but
additional information is also displayed.
If the error counter is not automatically opened, it can

also be opened used the menu item “Action/Show
Errors...” .
The error counter can also be opened using the short-

cut .

7.4.6 Show version information
It may be necessary for service-related reasons, that the version information for the individual modules is
required. The version information can be queried with the help of the ServiceMonitor from a subcontrol unit,
for the entire subcontrol unit loop.
A window with the version information for all

available subcontrol units and their modules can
be displayed using the menu item “Action/Show
Versions…” .
The version information can also be opened us-

ing the shortcut .
This data can be saved as a file using the “Save”

button, with the file type suffix “.ver”.

7.4.7 Send a Command
It is possible to send commands to the Integral System using the function “Send Command...”. For this a
FROM  TO function is also supported.
An input window is opened via the menu item “Ac-

tion/Send Command...” .
In this event window, the element type , the element

range  and the command to be executed  can be
selected. The command is then sent to the Integral
System by clicking on the “OK” button .

7.4.8 Software redundancy
It is possible using the „Software redundancy“ function, to activate the configured software redundancy for B6
control units in Listgenerator.
An input window is opened via the menu item “Ac-

tion/Software redundancy” .
In this input window, it is possible to turn software

redundancy on… or off… . The action is finished
by clicking on the “Close” button .
7.4.9 Freeze outputs

The “Freeze outputs...” function is used for maintenance and repair purposes, with all monitored outputs on
the Bx-BAF and B3-OM8 being sent to IDLE. In this state the bistable relays on the modules B3-REL10, B3-
REL16, B3-REL16E, as well as loop modules BA-REL4, BA-OI3 und BA-IOM are frozen in their current
state.
The physical state of the outputs will only revert to being the same as the logical state when the “Freeze out-
puts…” function is reset. This way it is possible to carry out logic tests on fire alarm devices, whilst this func-
tion also acts as a way of preventing triggering devices unintentionally during maintenance work.
A dialogue window is opened using the “Freeze out-

puts...” shortcut .

In this dialogue window the “Freeze outputs...” func-

tion can be turned on or off  and the state  que-
ried.
Turning on "Freeze output..."

After clicking on the freeze output “on...” button an
input window opens. There it is possible to select,
whether the “Freeze output” function should be sent
to ALL  or to only a selected subcontrol unit . By
pressing the “OK” button , a query window opens.
The outputs are frozen by clicking on the „Ja“ (Yes)

button.
Depending on the topology of the control units, after a

few seconds a confirmation window will be displayed.
If, for differing reasons, various outputs can not be
frozen, then these outputs are listed in the confirma-
tion window.
Turning off "Freeze output..."

After clicking on the freeze output “off...” button an
input window opens. There it is possible to select,
whether the “Freeze output” function should be sent
to ALL  or to only a selected subcontrol unit .
By clicking on the “OK” button  the command
“Freeze output” OFF is sent to the Integral system.

Depending on the topology of the control units, after

a few seconds a confirmation window will be dis-
played.
Freeze output state query

After clicking on the output freeze “query state” but-
ton, a state query is sent to ALL subcontrol units.
Depending on the control unit topology, the informa-
tion about the outputs will be displayed in the confir-
mation window.

7.4.10 Logging System Messages
The system messages show the internal functional procedures of the Integral System. The system messages of
the connected subcontrol unit can be displayed and logged using the ServiceMonitor.
The view of the system messages can be subdivided into two section windows:
 System message 
All system messages are continuously listed.
 Plain text message
Marked system messages are shown in plain text.
The current system message is always selected by using the button “Focus on last message” .
In the “TelegramLogger” menu, there are the follow-

ing submenu items:
 „Clear“ 
The content of the system messages section
window is deleted.
 „Use Logfile…“ 
The location for saving the log file is defined.
 „Browse Logfile“ 
By activating or deactivating this menu logging
is started or stopped.


ServiceAssistant  Loop Assistant
7.5 Loop Assistant

The complete address and setting of parameters for Integral loop technology is carried out centrally with the
help of LoopAssistant. Moreover, the program contains helpful functions for commissioning, maintenance and
fault tracking.
 Loop length calculation

 Loop configuration
 Support when fault tracking
 RevisionsAssistant
 Reading out device data
7.5.1 Construction
The LoopAssistant subdivides upon opening into the two following panes:
 DCU (CustomView) 
The loop is configured in this window. The automatic and non-automatic detectors are assigned zone
numbers and detector numbers, and the loop modules are assigned logical input and output numbers.
Furthermore, specific parameters can be set for individual loop devices.
 DCU (EEPromView) 
In this window the data from the loop is shown as it is saved in the control unit’s EEprom. If the
loop’s topology changes, then the modified data must be programmed into the control unit. The con-
trol unit was working with the data that is shown in this window.

7.5.2 Establishing a connection
For establishing a connection the galvanically isolated RS 232 interface (B3/B4) or the USB interface (B5/B6)
on the BMZ Integral or BMZ Integral C&C1 is used. The PC is connected using the Service PC Cable (Art.
No. FG81719 – RS232 or Art. No. FG022051 - USB).
Establish the connection

A connection is established or terminated using the
shortcut  .
7.5.3 Read in loop topology to B3-DAI2, B4-DAI2, B3-LEE24, B3-DTI2

By using the “Read” menu item, the actual physical extension of the loop is communicated from one or more
subcontrol units to the B3-DAI2, B4-DAI2 and B3-DTI2 modules. Installation faults, such as short circuits or
interruptions to circuits are detected and displayed. If there is a B3-LEE24 in a subcontrol unit, then only the
activated loops are displayed.
In the section pane the DCU (CustomView)  must

be marked, then a context menu is opened by right
clicking with the mouse. The loop/loops is/are read in
using the menu item “Read” .
A pop-up window will appear prior to the loops being

read in. This window advises that the loops in the
DCU zone window (custom view), that might have
been configured, will be erased. If you click on “OK”
then the reading process is started.

The connection to the subcontrol unit(s) is established

and the physical loop configuration is read in.
Once the reading in process has taken place, then the

physically communicated current status is displayed in
a tree structure. All configured subcontrol units (SCU),
DAI and DTI modules and loops/lines are displayed.
Meaning of the symbols:

Loop device not configured
Interruption after the loop device
Short circuit after the loop device
False address in loop device (Loops: adopt addresses)
In the “DCU (EEpromView)” pane , after the loop

configuration of the currently saved loop topology has
been read from the EEprom, it is then displayed. In
the case of a new system then this configuration is a
test configuration.

7.5.4 Loop topology configuration on B3-DAI2 and B4-DAI2
Once the physical structure has been communicated, the loop devices must be assigned their logical addresses.
The loop devices are only evaluated or controlled over the assigned logical numbers.
By selecting a loop device, an extra window opens, in

which the logical number is entered. By pressing the
“Apply Changes” button  the entered information is
accepted and then selection changed to the next loop
device.
If all loop devices were configured, then the entered

parameters are visible in the “DCU (CustomView)”
pane . In order to save the configured data locally
the “DCU (CustomView)”  must be marked and the
short “Save”  clicked upon.
A project properties window opens, in which addi-

tional information about the project can be entered:
 Project name (project folder, which was selected
when ServiceAssistant was opened)
 Project engineer
 Version (Version number for better tracking)
 Notes (Descriptions of changes between ver-
sions)
By clicking on the “OK” button the data is saved.

After having been saved successfully the full path of the saved file can be found in the pane “DCU (Custom-
View)”.
Depending on the type of loop device, different parameters can be configured. In that case it concerns the
parameter types, detector, special detector, inputs and outputs. Based on the following four examples, the pa-
rameter types are explained.
Parameter type Detector:

applies to all manual detector types.
 Log.Number: Enter the detector zone number

 DetNumber: Enter the detector number within the
detector zone
 AlarmLevel: Enter the significance
By clicking on the “Apply Changes” button  the set
parameters are applied.

Parameter type Zone: Applies to all automatic detectors.
 Log. number: Enter the detector zone number

 DetNumber: Enter the detector number within the detec-
tor zone
 AlarmLevel: Enter the significance
 Alarm Current: Enter the available alarm current for the
alarm output for a single detector indication (5mA, 2mA)
 Temperature: Enter the temperature class (A1, A2, B)
and enter the temperature index (no active index, Index
R, Index S)
 PreAl Threshold: Enter the prealarm threshold (none,
50%, 75%), prealarm: Enter the significance and sensitiv-
ity: Enter the sensitivity level for the smoke sensor
(normal, increased, reduced, strongly reduced)
 Sensor behaviour: The detector’s sensor behaviour can be
configured differently for daytime (delayed) and night
time (not delayed) switching (and for temperature and
smoke, only temperature, only smoke).
 PI-linkage: Configuration of the alarm output for a single
detector indication.
 Detector controls own alarm output: The alarm output
becomes passive or active in the event of this detector
entering alarm state.
By clicking on the “Apply Changes” button  the set pa-
rameters are applied.
After clicking on the “PI-Linkage” button, a new window

opens. In the detector selection field, all detectors from the
same loop are shown. The detectors can be chosen individu-
ally and added using the button “>>” into the field “trig-
gered by PI” or removed using the button “<<”. All detec-
tors, which can be found in the field “triggered by PI” trig-
ger the alarm output of the relevant detector in the event of
an alarm occurring.
By clicking on the “OK” button the configuration is applied.

Special detector parameter type:

Applies, for example to the BA-OI3 loop module
The BA-OI3 can be configured as a special detector or as an

Input/Output module.
When the BA-OI3 is used as a special detector, the option

field “Detector”  must be activated.
 Log.Number: Enter the detector zone number

 DetNumber: Enter the detector number within the detec-
tor zone
 AlarmLevel: Enter the significance
 Parameter set: Select the connected special detector.
By clicking on the “Apply Changes” button  the set pa-

Parameter type Input/Output module:

When the BA-OI3 is used as an Input/Output module, the
option field “I/O”  must be activated. The parameter
settings for inputs and outputs are shown for the BA-OI3
and are identical for all other Input/Output modules.
 Detector: If the option field is activated, then the input is
evaluated as a detector zone, otherwise when deactivated,
the input is evaluated as being an input.
-{}- invert.: The input is inverted if the option field is
activated.
 Übw: If the option field is activated, then the detector
zone/input has line monitoring.
 LogNumber: Enter the detector zone or input number.
 DetNumber: Enter the detector number within the detec-
tor zone
 AlarmLevel: Enter the significance
 Output: Enter the output number
 FailSave: In the event of a communications fail, the fail-
safe position will be adopted. When the setting is
 Unchanged: No change in state is undertaken for the
output.
 Opened: Then the output is switched to the idle posi-
tion
 Closed: Then the output is switched to the operating
position
By clicking on the “Apply Changes” button  the set pa-

7.5.5 Configure/reset loop topology on B3-DAI2 and B4-DAI2

After configuring the physical loop topology, the configuration must be programmed into the Integral System.

clicking with the mouse. The loop/loops is/are saved
into the EEprom using the menu item “Program” .
The connection to the subcontrol unit(s) is established and the physical loop configuration is programmed.
After the loop configuration has been successfully

programmed, the Integral System is reset. By pressing
the “Reset immediately” button, the Integral System is
reset straightaway.
An information window opens, which must be con-

firmed used the “OK” button.
After the Integral System has been successfully reset,

and the loops have been reinitialised, by selecting
“Read” again, the programmed loops will be shown in
the pane “DCU (EEpromView)” .

7.5.6 Adopt loop topology addresses on B3-DAI2 and B4-DAI2
Once the physical loop topology has been programmed, the loop devices must be uniquely addressed by the
Integral system. A unique address is saved in the EEprom of the loop device. This unique addressing is used
internally by the Integral System.

clicking with the mouse. All loop devices are addressed
using the “Loops: Mapping”  menu point.
An information window opens, which must be con-

firmed used the “OK” button.
Once the loop devices have been successfully ad-

dressed, the configured loops are displayed in the pane
“DCU (CustomView)”  by once again selecting to
“Read”. After the loops have been successfully com-
missioned, the formations displayed in the “DCU
(CustomView)” and “DCU (EEpromView)” panes are
identical.

7.5.7 Determine loop topology at B3-LEE24
Once the reading in process has taken place, then the physically communicated current status is displayed in a
tree structure. Now the structure of the loops must be sent to the B3-LEE24, since they are not automatically
read in.
By marking the loop and right clicking with the mouse,

a context menu appears. Select “Explore loop topol-
ogy”.
When the “Explore loop topology” has been selected,

an information window opens. In this window it is
possible to pursue the registration and deregistration
of individual devices.
After the topology has been determined, the topology

status must be read in. By marking the loop and right
clicking with the mouse, a context menu appears. Click
on “Read”.

The connection is established and the physical loop

configuration is read in.
Once the loop has been read in successfully, then it is

displayed. In brackets  the number of the hardware
address of the device is displayed, which has been set
directly for the loop device.
Displaying faults
In the event of a wire break in the loop, the informa-
tion field remains open once the loop topology has
been determined. In this window the number of de-
vices is displayed which have been found and the rea-
son for the fault displayed.
Once the loop has been read, the position of the wire
break  is now shown.
In this example the wire break is after the first device
with the hardware address 42 on the loop.

7.5.8 Configure loop topology to B3-LEE24

Once the physical topology has been determined, the loop devices must be assigned their logical addresses. The
physical topology is therefore assigned a logical topology. The loop devices are only evaluated or controlled
over the logical numbers.
By selecting a loop device, an extra window opens, in

which the hardware type  must first of all be deter-
mined.
Depending on the hardware type that is selected, the

entry for the “LogNumber”  alters accordingly.
Hardware type:
UAS159-I
Module configured as an input module (alarm of the
fault message)
UAS159-0
Module configured as a control module
SBS157-I
Module configured as an input module (alarm of the
fault message)
SBS157-0
Module configured as a control module
After the hardware type of the loop device has been determined, the input window “LogNumber”  and
“Det.Number” , in which the logical number is entered. By pressing the “Apply Changes” button, the en-
tered information is accepted and then selection changed to the next loop device.
If all loop devices were configured, then the entered

parameters are visible in the “DCU (CustomView)”
pane . In order to save the configured data locally
the “DCU (CustomView)”  must be marked and the
short “Save”  clicked upon.

A project properties window opens, in which addi-

tional information about the project can be entered:
 Project name (project folder, which was selected
when ServiceAssistant was opened)
 Project engineer
 Version (Version number for better tracking)
 Notes (Descriptions of changes between ver-
sions)
By clicking on the “OK” button the data is saved.
After having been saved successfully the full path of the saved file can be found in the pane “DCU (Custom-
View)”.

NetworkAssistant  Loop Assistant
7.5.9 Program/reset loop topology at B3-LEE24
After configuring the physical loop structure, the configuration must be programmed into the Integral System.
See chapter 7.5.5 Configure/reset loop topology on B3-DAI2 and B4-DAI2
7.5.10 Determine loop topology at B3-DTI
Once the reading in process has taken place, then the physically communicated current status is displayed in a
tree structure. The topology of the loop at the B3-DTI is automatically determined and therefore no further
settings are required.
Once the loop has been read in successfully, then it is

displayed. In brackets  the number of the hardware
address of the device is displayed, which has been set
directly for the loop device.
It must be ensured that the address set at the detector has also been entered in the configuration
of the B3-DTI2 in Listgenerator.
8 NetworkAssistant
NetworkAssistant is a tool in its own right and is included in the Integral Software Pack. It is used as an assis-
tance tool for the commissioning, maintenance and servicing of the SecoNET Network and consists of the
following program components:
 Network-Monitor
 Network-Assistant
For further information please have a look at the tecnical documentation.

Trouble-shooting
9 Trouble-shooting
Problems with USB dongle when using Windows Vista operating system
To guarantee that the USB Dongle (CRYPTO-BOX) for the Integral Software Pack works properly, the USB
drivers for Windows Vista (CRYPTO-BOX USB driver files for Windows Vista) must be downloaded and
installed from the website of the manufacturer of the USB Dongle (www.marx.com).

220
Manual Integral Software 6.2 V 2.1
B-HB-010EN
© Schrack Productions – B-HB-010DE - V 2.1 - 03.2010 Gedruckt auf chlorfrei gebleichtem Papier Technische Änderungen vorbehalten!

Softwarehandbook 62

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Softwarehandbook 62

Uploaded by

Copyright:

Available Formats

Table of Contents

Integral Software V 6.2.

B-HB-010EN Manual Integral Software 6.2 V 2.1 1

2 Manual Integral Software 6.2 V 2.1 B-HB-010EN

4.4.27 External LED Indicator Panel for up to 64 detector zones EAT64..................................................................................... 59

4.12 Range filters ...................................................................................................................................................... 125

B-HB-010EN Manual Integral Software 6.2 V 2.1 5

6.4 Feeding in data (Download) ............................................................................................................................ 179

Responsible for the content of this document:

6 Manual Integral Software 6.2 V 2.1 B-HB-010EN

The following parts are described in this documentation:

The Integral Software is used for the following applications:

 BMZ Integral Fire alarm control panel, modular system

B-HB-010EN Manual Integral Software 6.2 V 2.1 7

2.1 System Requirements

Minimum System Requirements for PC or Laptop

CPU Pentium Processor

Miscellaneous Mouse and keyboard

8 Manual Integral Software 6.2 V 2.1 B-HB-010EN

2.2 Integral Software pack installation.

To start the installation, the following steps must be carried out:

Insert the Installation CD in to the CD/DVD drive

If the CD/DVD drive’s auto play function has been

In the event that the Auto play function cannot be set,

Installation of the Integral Software

Next it is possible to choose between German and

B-HB-010EN Manual Integral Software 6.2 V 2.1 9

The installation of Integral Software version 6.2

Click on the “Next” button to continue.

An information window is displayed. The software

Select the folder in which the Integral projects

10 Manual Integral Software 6.2 V 2.1 B-HB-010EN

There are two different installations available for in-

Additionally the following components can also be

Select the desired type of installation and then click

Select the program folder in which the Integral pro-

The default setting is “Seconet/Integral”.

Click on the “Next” button to continue.

Additional tasks such as

Click on the “Next” button to continue.

B-HB-010EN Manual Integral Software 6.2 V 2.1 11

Then an overview of the installation with all parame-

The installation process is now carried out. Please

To complete the installation, the computer must be

Click on “Finish” to restart the computer.

12 Manual Integral Software 6.2 V 2.1 B-HB-010EN

2.3 BMZ Integral USB Driver Installation

When first establishing a connection, the Windows

The "Assistant for finding new hardware" will open.

Select “Software von einer Liste oder bestimmten

Selcect „Durchsuchen“ to search for the USB driver

Click on “Next” to continue.

This message is displayed when the driver is being

Click on “Continue installation” to continue.

B-HB-010EN Manual Integral Software 6.2 V 2.1 13

The Integral USB driver is installed and registered in

Then the window will appear that the assistant is com-

Click on "Finish" to finish the installation process.

Then a Windows information window will display a

14 Manual Integral Software 6.2 V 2.1 B-HB-010EN

3 New Features in Integral Software Pack 6.2

3.2 Overview of New Features in comparison with SW 6.1.x

3.2.1 Integration of the Control Panel Integral MAP