Seconet PRJ en

SecoNET network
Basic Principles
for planning and configuration
Copyright 2001-2009 by SCHRACK Seconet AG

SecoNET CONFIGURATION
Table of Contents:
1.0 General 4
1.1 Important note about servicing and maintenance work 4
1.2 Course content 5
1.3 About this training manual 5
2.0 Basic Principles 6
2.1 Introduction 6
2.2 Network Structure 6
2.3 SecoNET Network - Terms 7
2.4 The SecoNET network principle 8
2.5 Connecting MAXIMA and Management Systems 9
2.6 Structure of the SecoNET network 10
2.7 The Main Control Unit 13
2.7.1 General 13
2.7.2 Actuation Concept 14
2.7.3 Indication and numbering 15
2.7.4 Area Filters 15
2.7.5 Hardware / Software 16
3.0 Configuration 17
3.1 Using several communications modules 17
3.2 SecoNET Network Extension 20
3.3 Small SecoNET Networks 21
3.4 Programming 22
3.5 Planning of the Service Interface(s) 22
3.6 Planning of Customer Texts 22
3.6.1 SecoNET with Management System 22
3.6.2 SecoNET with Main Control Unit 23
3.6.3 Network error number calculation 25
4.0 Information processing 28
4.1 Communications System Faults 28
4.2 Domains Concept 29
4.3 The Management System 30
4.4 The Main Control Unit 31
4.5 Routing 31
5.0 Connectivity Options with SecoNET 32
5.1 BMZ Integral or BMZ Integral C 32
5.2 BMZ Integral and a Management System 32
5.3 BMZ Integral, SecoNET Main Loop and Subordinated Loop 33
5.4 BMZ Integral Connecting two systems 33
6.0 The Relationship of the Fire Alarm Control Panel to the SecoNET Network 34
6.1 BMZ Integral 34
6.2 BMZ Maxima 34
6.3 Standard-Maxnet 35
6.4 Enhanced Maxnet 35
7.0 Training Examples 36
File name: SecoNET_PRJ-en.doc Version V 1.7 Page 2(42)
Doc. No. SPT/02:SecoNET_prj_2002 SPT/G. Porcher 30.09.2009
7.1 Example 1 36
7.1.1 Network Configuration 37
7.2 Example 2 38
7.2.1 Control Panel Configuration (only network modules) 39
7.2.2 Network Structure 40
7.3 Example 3 (with main control unit) 41
15.0 List of Document Versions 42

1.0 General
This documentation accompanies the training course for configuring a SecoNET network.
SCHRACK Seconet AG
Training in Vienna
If you have suggestions for

improvements to this document, or find
an error in it, then please send an e-mail
to:
Trainingscenter@schrack-seconet.com
1.1 Important note about servicing and maintenance work

If BMZ extinguishing systems or other devices are automatically controlled by fire alarm
devices, then electronic, mechanical and optical measures must be taken when carrying out
servicing and maintenance work, to ensure that the devices cannot be accidentally triggered!!!
Once the servicing or maintenance activities have been finished, the security precautions must
once again be removed!!!
Further information about this topic can be found in the relevant servicing information!!!
SCHRACK Seconet AG assumes no liability for technical or printing errors and omissions in this document. Furthermore, no liability is assumed for
damage which can be directly or indirectly traced back to usage of this documentation

1.2 Course content
COURSE AIMS: Participants should be able to perform all SecoNET network-related duties
covered in this course.
COURSE CONTENT: Basic Network Principles,

Configuration,
Information processing
Sample applications
PRE-REQUISITES: Course: Introduction to fire alarm technology

Course: BMZ INTEGRAL Basic Version + Network (subcontrol unit
loop) for configuration and sales
Knowledge of BMZ MAXIMA systems would be advantageous
1.3 About this training manual

This training manual is intended for use as accompanying documentation for the course. As such its
content corresponds in general to the course structure and should then serve as a work of reference
afterwards.

2.0 Basic Principles
2.1 Introduction
Decentralization of fire alarm control panels and the networking of control panels into snaller and
larger networks is becoming increasingly important. For this reason, when developing the BMZ
Integral, particular attention was paid from the outset to ensuring that the control panel could
support the decentralized structure and could be networked.
As the BMZ Integral was developed as a redundant system, one of the most important requirements
for networking was also to guarantee stability, failure prevention and functional security by using
redundant data transmission across the entire network. Since all the functions had already been
implemented at the outset, the same hardware could be used for the SecoNET network as for the
subcontrol unit loop.
The trend towards planning and realisation of industrial centres requires that ever more control
panels are networked, and an important factor is that the information for the entire system is
available in different locations by deploying management systems.
2.2 Network Structure

The starting point for networking of control panels was decentralization. The subcontrol unit loop
of a BMZ Integral represented the first step. Both cabling and interface redundancy was deployed in
order to network individual BMZ Integral (C) units with one another that were remotely situated
away from one another.
The networked control panels were called subcontrol unit loops and functioned with an external
appearance of being control panels.
Consequently the number of an element always only related to the
subcontrol unit loop, and not to an individual BMZ Integral (e.g. a
B3/B4 B3/B4
printer with the number 1 could only occur once in the subcontrol
unit loop).
BMZ Integral
(Subcontrol unit loop) The main detector output (e.g. for alerting the fire brigade) can be
controlled by every control panel in the subcontrol unit loop.
B3/B4 B3/B4
max. 16 Subcontrol units

2.3 SecoNET Network - Terms
Subnet Communications modules of a BMZ Integral form a loop network in the
SecoNET network. Every one of these SecoNET network loops (main loop,
subordinated loops) is described as a Subnet.
Node (Nodes) Every BMZ Integral communications module in a Subnet is called a Node.
Client Every system connected to a communications module (fire alarm control

panel, management system etc.) is called a Client.
Node-ID Every Node in the SecoNET network has a unique ID (physical address),
which is assigned when configuring a Node by List Generator. Logical
addresses are only configured once the network is operational.
Router To reduce the amount of communications in the SecoNET network, Subnets

are linked to one another by Routers. Information from one Subnet is only
then forwarded to another Subnet, if the information is also required there.
MaxNet An individual BMZ MAXIMA, BMZ MAXIMA standard network or BMZ

MAXIMA extended network
Subcontrol unit loop Networking of individual BMZ Integral or BMZ Integral C control panels to
form a network. All the control panels together have the external appearance
of a single control panel.
Management system A superordinated computer system for operating SecoNET network network
control panels and for displaying information about events occurring at
individual SecoNET network control panels.
Main control unit A superordinated BMZ Integral unit for operating SecoNET network network
control panels and for displaying information about events occurring at
individual SecoNET network control panels.

2.4 The SecoNET network principle
The starting point for the SecoNET network is a redundant loop circuit, like the one used for the
subcontrol unit loop of the spatially distributed Integral fire alarm control panel. This redundant
loop is also used in the SecoNET network in order to network several Integral fire alarm control
panels (or subcontrol unit loops) which are located away from one another. All the components
used in the SecoNET network have been awarded approvals.
The splitting of a logical Integral fire alarm control panel into several physical subcontrol units is
not relevant in the SecoNET network.
B3/B4 B3/B4 B3/B4 B3/B4
BMZ Integral BMZ Integral

(Subcontrol unit loop) (Subcontrol unit loop)
B3/B4 B3 B3 B3/B4
SecoNET
Subnet 1
B3/B4 B3 B3 B3/B4
BMZ Integral BMZ Integral

(Subcontrol unit loop) (Subcontrol unit loop)
B3/B4 B3/B4 B3/B4 B3/B4
BMZ BMZ
Integral Integral
SecoNET
Subnet 1
BMZ BMZ
Integral Integral
When networking BMZ control panels, at least two of the control panels must be BMZ Integral
control panels.
The other connected control panels can be Integral C control panels.
The numbering of elements can begin with the number 1 for every control panel that it connected
into the SecoNET network. If the connected control panel is part of a subcontrol unit loop, then the
number of an element may only occur once in the subcontrol unit loop.
It must be possible to actuate the main detector output from every connected SecoNET control
panel (the only exception being for a network with a main control unit).
2.5 Connecting MAXIMA and Management Systems

Using the BMZ Integral it is possible to connect management systems and MaxNets as redundant
stubs to the SecoNET network. A maximum of one stub connection per Integral control panel is
possible.
BMZ BMZ BMZ

Integral Integral Maxima
SecoNET
SecoLOG
BMZ BMZ
Integral Integral
Stub line connection:
Integral Standard Protocol preferred protocol for connecting management systems
N3 - ZZK-Protocol (Master)
N3 EZZK Protocol (Master) for connecting BMZ Maxima units, standard MaxNET and
enhanced MaxNET.

2.6 Structure of the SecoNET network
In the SecoNET network, every communications module is classed as a Node, via which a
connection to other communications modules (Nodes) is made.
The number of Nodes in a loop can be up to 62 (0 61) and theoretically 6 Clients (0 5) can be
addressed per Node. In practice, there are normally a maximum of 2 Clients (e.g.: the BMZ Integral
is one client and a management system is the second client).
Redundant loops are assigned hierarchically in the SecoNET network. By definition a main loop
exists, to which one or more subordinate loops can be connected.
The hierarchical assignment of redundant loops means that the redundancy increases the more
nodes there are. This means that there is a considerable improvement in available compared with
there being an individual loop. The quantity of Subnets (subordinated loops) is theoretically limited
to a maximum of 63 (0 62).
BMZ BMZ BMZ

BMZ
Integral Integral Integral
Integral
SecoNET SecoNET
(subordinated loop) (subordinated loop)
BMZ BMZ BMZ BMZ

Integral Integral Integral Integral
SecoNET
(main loop)
BMZ BMZ
BMZ
Integral Integral
Integral
SecoNET
(subordinated loop)
BMZ BMZ
Integral Integral
The maximum number of the SecoNET devices (BMZ Integral, BMZ Integral C, main control unit,
main control unit) is 254.

Further subordinated loops can be connected to subordinated loops. A loop can also take the form
of an open loop (stub), which is once again a separate Subnet.
BMZ BMZ
Integral Integral
SecoNET
(subordinated
loop)
BMZ BMZ BMZ BMZ
BMZ BMZ BMZ
SecoNET SecoNET
(subordinated (subordinated SecoNET
loop) loop) (subordinated open loop)
BMZ BMZ BMZ BMZ
SecoNET
(Main loop)
BMZ SecoLOG
BMZ BMZ
Integral
Integral Integral
SecoNET
(subordinated
loop)
BMZ BMZ
Integral Integral
The structure of the hierarchical loops (tree structure) must however always remain intact. The
configuration shown in the figure below is not permissible.
BMZ BMZ BMZ BMZ

SecoNET SecoNET
(subordinated (subordinated
loop) loop)
BMZ BMZ BMZ BMZ
BMZ
Integral
SecoNET SecoNET
(subordinated (subordinated
loop) loop)
BMZ BMZ BMZ BMZ

SecoNET
(main loop)
BMZ
BMZ
Integral
Integral

A subcontrol unit loop linked to a SecoNET network can be used for transmitting data from the
SecoNET network. In the following example the control panel TZ 1 is incorporated into the
SecoNET network. TZ1, TZ2, TZ3 and TZ4 form a subcontrol unit loop.
A B3 USI4 module is however required in subcontrol units 1 and 3. In subcontrol units TZ2 and
TZ4 either one B3-USI4 module or two B3-LPI modules can be used. A BMZ Integral C can not be
used for this configuration, as it only has two interfaces. As a result of this configuration an
additional Subnet is formed.
BMZ BMZ
Integral Integral
SecoNET
(subordinated
loop)
BMZ
BMZ BMZ BMZ BMZ
Integral BMZ BMZ
TZ 2 Integral Integral
TZ 3
SecoNET BMZ INTEGRAL
Subcontrol unit loop
(subordinated SecoNET
loop) SecoNET (subordinated open loop)
BMZ BMZ
BMZ BMZ
Integral Integral
Integral Integral
TZ 1 TZ 4
SecoNET
(main loop)
BMZ
BMZ BMZ
Integral
Integral Integral
SecoNET
(subordinated
loop)
BMZ BMZ
Integral Integral
This configuration can be used for transmitting SecoNET network data over a subcontrol unit loop.
In this case control panels TZ 1, TZ 3 and TZ 4 each require a B3 USI4 module and a B3 LPI
module. In this example a BMZ Integral C could be used for control panel TZ 2. Subcontrol unit
TZ1 is connected to the SecoNET network and serves simultaneously as a router.. Subcontrol units
TZ 3 and TZ 4 only function as routers. Additional Subnets are also formed in this configuration.
SecoNET
SecoNET
BMZ
BMZ
Integral
Integral
TZ 2
TZ 3
BMZ INTEGRAL
Subcontrol unit loop
SecoNET
SecoNET
BMZ BMZ
Integral Integral
TZ 1 TZ 4
SecoNET

2.7 The Main Control Unit
2.7.1 General
The SecoNET main control unit is used for centralised operation and indication for a SecoNET
control panel network. It consists of a BMZ Integral subcontrol unit with a full door, to which a
remote SecoNET High End Operating Panel (from software version SW 5.1.x) has been attached
via the MMI-BUS.
A maximum of 32 main control units can be connected in a SecoNET network if no management

system is being used (variant with a management system: maximum total quantity of main control
units and management systems 32).
In principle version C or later networking modules with larger memories (B3-LPI, B3-USI4) should
be used in the main control unit.
A centralized main detector is actuated from the main control unit.
BMZ BMZ BMZ

BMZ
Integral
SecoNET SecoNET
(subordinated loop) (subordinated loop)
BMZ BMZ BMZ BMZ

SecoNET
(main loop)
BMZ
BMZ BMZ Integral
Integral Integral HZ
SecoNET
(subordinated loop)
BMZ BMZ
Integral Integral

To note:
Maximum 64 events (per subcontrol unit) from the main control unit to the subcontrol unit
Maximum of 512 links per main control unit (maximum of 256 controllers locally)
No criteria for reactuation
Local controllers are actuated through links
External element (related only to main control units)
No internal operating panel is possible

No subcontrol unit loop with main control unit
Not an element of a detector zone
No DAI module
BMZ Integral C can not be used as a main control unit
2.7.2 Actuation Concept

By means of simple SecoNET links events from subcontrol units (UZ) can actuated controllers in
the main control unit.
It is possible using Events to use linked results from subcontrol units and linked results in the main
control unit to trigger controllers in the main control unit or the subcontrol unit.

2.7.3 Indication and numbering
Every subcontrol unit and main control unit is allocated a subcontrol unit number (0-254).
This assignment of numbers occurs during the configuration of the SecoNET network and has
nothing to do with the subcontrol unit number.
Standard text
AL ARM 1 0 1 - 1 0 0 0 7 / 0 2 3 001
SCU number
Element No. e.g.: group
Subelement number
Running List number
2.7.4 Area Filters

The use of area filters may be necessary if the possibilities offered by the domain structure are not
sufficient.
A maximum of 15 area filters can be programmed for SecoNET in the main control unit. The filters
are then assigned to the subcontrol units. One filter is possible per operating panel, if several
operating locations are connected to a single main control unit.
The assignment of the management system/main control unit to area filters is carried out based on
the number of the operating panel.

2.7.5 Hardware / Software
The following hardware is required for a main control unit:
As standard:
Integral with closed door
External operating panel (25 character display) with printer (only up to software version
5.0.x)
N3 High End Operating Panel with or without a printer (from software version 5.1.x)
BAF module (B5-BAF from software version 5.1.x)
USI4 or LPI (version C or higher)
Optional:
MTI module (only for use as an element input)
DCI module (only for use as an element input)

Relay 10/16/16E
The following hardware is required for a main control unit:
Software from version 5.0.x

3.0 Configuration
The topology and the design of the SecoNET network does not need to be considered when
configuring a BMZ Integral unit.
The individual BMZ Integral units are independently configured from one another. Only the
interface to the SecoNET network or other required interfaces for connecting the management
system and MaxNet to the SecoNET network must be configured.
When configuring these interfaces only the required protocol (Integral Standard Protocol or ZZK
Protocol) as well as RS232, RS422, RS485 (redundant or non-redundant) and the bit rate or parity
require configuring.
3.1 Using several communications modules

The SecoNET network is connected to side A of the processor of the first B3-USI4 module. All
SecoNET network information is then internally transferred to side B of the processor, from where
the SecoNET network is once again connected to side A of the processor of the next B3-USI4
module. All SecoNET network information is once again internally transferred to side B of the
processor, from where the SecoNET network can be connected to the next node (module).
BMZ INTEGRAL
B3 - B3 - B3 -
MCU USI4 USI4
Processor half A
SPI - BUS
Processor half B
B3 - B3 - B3 -
MCU USI4 USI4
SecoNet
SecoNet

In the event of a permanent failure of one half of the BMZ Integrals processor only one
communications module can continue to communicate with the SecoNET network (dependent on
which processor half has failed). In the instance shown here (processor half B has failed) only the
management system which is connected to the left B3-USI4 module can communicate with the
SecoNET network. A service PC which is connected to the right B3-USI4 module no longer has a
connection to the SecoNET network. Dependent on which B3-USI4 module is used for connecting
the BMZ Integral to the SecoNET network, the BMZ Integral may also no longer be connected to
the SecoNET network. To guarantee full redundancy of data transmission, a configuration as shown
should be avoided.
Processor half A
Processor half B
B3 -
USI4
SecoNet
SecoNet
Hardware diagram for the example above:
Service
Assistant
G
SecoLO
USI 4
USI 4
SecoNET
SecoNET

In order not to have the problem described above, there is the solution of splitting the B3-USI4
modules between two BMZ Integral control panels in the SecoNET network. The two BMZ Integral
control panels must be connected into the SecoNET network.
Service
Assistant
G
SecoLO
SecoNET
B3 USI4
SecoNET
By taking this measure, it is no longer possible for a management system failure or a service PC
failure to happen.

3.2 SecoNET Network Extension
The theoretically possible extension of the network can not be realised in practice. Instead of a large
Subnet with many nodes, several small Subnets with less nodes (8 16 nodes) should be used, with
the management system always being centrally located.
The following diagram shows and ideal configuration. This comprises of:
a main loop, onto which the management system, the ServiceAssistant and an extended Maxnet
are connected
and of
several subordinated loops, to which only fire alarm control panels are connected.
When symmetrically formed (with 8 nodes on each Subnet) this configuration consists of 43 nodes.
As a BMZ Integral can be connected to every node (which can consist of up to 16 subcontrol units
in turn), this configuration can consist of up to 43 x 16 (=688) BMZ Integral subcontrol units (and
an extended Maxnet !).
SecoNET
(untergeordneter
SecoNET Ring) erweitertes
(untergeordneter Maxnet
Ring)
BMZ
BMZ BMZ
SecoNET
SecoNET
(untergeordneter BMZ BMZ
Ring) (Hauptring)
SecoLOG -
Leitsystem
BMZ BMZ
SecoNET BMZ
(untergeordneter
Ring)
SecoNET
(untergeordneter
Ring)
ServiceAssistant

3.3 Small SecoNET Networks
SecoNET networks do not always need to be large networks with lots of control panels. By using a
main control unit is also also possible for smaller projects to be covered by a SecoNET network.
UZ 4
UZ 1
SecoNET
Subnet 1
UZ 3
UZ 3 Main Control Unit
A centralized main detector is actuated from the main control unit.

3.4 Programming
In order to be able to calculate the requirements for programming, the following points are to be
observed:
Programming of the subcontrol unit loops as before
Programming of control panels which are connected into the SecoNET network consists of
one programming per unit
Uploading software into every control panel
Configuration of a SecoNET network => commissioning on a stage-by-stage basis is more

time-consuming
3.5 Planning of the Service Interface(s)

In at least one control panel there must be a free interface for a Service PC. This means that neither
a management system nor a MaxNet should be connected to this control panel.
3.6 Planning of Customer Texts
3.6.1 SecoNET with Management System

The customer-specific texts are planned and programmed for every SecoNET subcontrol unit
(subcontrol unit loop).
Texts should also be prepared for connection faults between the control panels (Country-specific
regulations should be observed with regard to the text formulation. For connection faults the text
must be assigned to so-called fault numbers. These fault numbers are made up of Subnet, Node and
Port numbers.

3.6.2 SecoNET with Main Control Unit
The customer-specific texts are planned and programmed for every SecoNET subcontrol unit
(subcontrol unit loop or main control unit).
All the text information is saved in a single file.
The main control unit only needs texts for the elements in the main control unit (exceptions: texts
for e.g.: UZ1, UZ2, ...). All texts in the main control unit and the required texts for the subcontrol
units are automatically compiled together when exported using the Integral-Text-Tool, so that they
can then be uploaded into the main control unit
Example: Project "SPT-Trainingsland" (One main control unit and 4 other subcontrol units)
Texts for UZ1 main control unit (controlling elements, ....)

In the main control unit there is no element Gruppe (Hardware).
Texts for UZ2 (Elements Group, Controller, ....)

Texts should also be included for connection faults between the control panels (country-specific
regulations for text formulation should be observed. For connection faults the text must be assigned
to so-called fault numbers. They are compiled from the Subnet number, Node number and Port
Sub centrals 1,2 and 3
Main central
Network error numbers
Netzwork error Netzwork error

number "xxxx" number "yyyy"
xxxx => standard view
yyyy => view by delay of singnal
yyyy => standard view

xxxx => view by delay
A Subnet "X" B
Between two centrals in a SecoNET network there can be two different error messages for the same
connection. Standard view of the network error number is the same as the calculated number of
subnet-node-port adress, but if the logging of the network error have an delay than the network
error number of the other central is viewed (e.g. central a shows as standard "xxxx" an with an
delay "yyyy".

3.6.3 Network error number calculation
For creating customer text for network errors, you need the network numbers. These can be either
after the installation and configuration of the network or by previous planning and calculation to be
determined.
For an exact calculation to be carried out following procedure is required:
1) You need network configuration drawing => see example

2) At each center, the type of communication cards must be definated
3) The number of subnets must be defined
4) There must be connections between the various interfaces to be defined
Are previous points have been carried out, it can be definited each subnet address, node address
(per subnet for a communications card is always the same) and the port address.
B5 Pinguin C01 SW614
SubNet.Node.Port Net no. B6 C08 central 7 SW614

0 0 5 => 6
SubNet.Node.Port Net no.

0 0 1 => 2
5 = 0A (PC)
1 = 1A(loop) SubNet.Node.Port Net no.

0 1 0 => 17

SPT 0 1 2 => 19
5 = 0B (lPC)
GUE 0 = 0A (loop)
3 = 1B(loop) 2 = 0B (loop)
Sub net 0
4 = PC

0 0 3 => 4 0 = 0A (loop)
1 = 1A (loop)
Pinguin C07 z15 HighEnd SubNet.Node.Port Net no.

0 2 1 => 34
2 = 0B (loop)

3 = 1B (loop) 0 2 3 => 36

Sub net adress (decimal) + node adress (decimal)
Port adress: The values for the port you will found in following grafics, depending on whether a
central or a computer interface is connected.
Netz work error code = Subnetadress * 1024 + Node * 16 + (Interface number + 1)
Example: Netz work Error code = 0*1024 + 1*16 + 0 + 1 =17
Network- from From central to central from

error number SubNET.Node SubNet.Node
6 0.0 B5 Pinguin C01 SW614 Service-PC 0.0.1
4 0.0 B5 Pinguin C01 SW614 B6 C08 central 7 SW614 0.0.1
17 0.1 B6 C08 Central 7 SW614 B5 Pinguin C01 SW614 0.0
19 0.1 B6 C08 Central 7 SW614 Pinguin C07 z15 HighEnd 0.2
34 0.2 Pinguin C07 z15 HighEnd B6 C08 Central 7 SW614 0.1
36 0.2 Pinguin C07 z15 HighEnd B5 Pinguin C01 SW614 0.0
2 0.0 B5 Pinguin C01 SW614 Pinguin C07 z15 HighEnd 0.2
1. Port adress by communication with central units
SecoNet network communication
B3/B5 Integral
0 = 0A (loop) B4/B6 Integral

0 = 0A (loop)
0 = 0A (loop)
1 = 1A (loop)
4 = PC card
modem Interface
2 = 0B (loop)
2 = 0B (loop)
4 = PC card
3 = 1B (loop) 2 = 0B (loop) modem Interface

2. Port adress by communication with PC
For PC connection standard interface 0A is used.
PC to central connection
5 = 0A (PC)
Fire Alarm
Trainingcenter
Vienna
6 = 1A (PC)
5 = 0B (lPC)
6 = 1B (PC)
For PC- connection, this interface normaly not used !!!

4.0 Information processing
All nodes are connected to one another in a loop formation in the SecoNET network. Every client in
the SecoNET network has a direct point-to-point connection to a node (this doesnt apply for stub
line connections, which are connected to a node using the Integral Standard Protocol or the N3-
ZZK/N3-EZZK protocol, or for the BMZ Integral, which is internally connected to the node via the
SPI bus).
SecoNet SecoNet
Management
System
or
MaxNet
The information from a client reaches the node via the direct point-to-pint connection. The node
sends this information to all the other nodes in the SecoNET network. Information from the
SecoNET network is only transmitted from the node to a client if this client has been specifically
addressed.
On the whole, messages from fire alarm control panels are forwarded to all management systems. A
management system can directly address a client, in order to query or change the state of an element
of this client.
This type of information processing guarantees that a fire alarm control panel can be connected to
the SecoNET network reactionlessly (the fire alarm control panel's operations are not influenced by
the SecoNET network).
4.1 Communications System Faults

All transmission paths in the SecoNET network are permanently monitored. A fault on a
transmission path can be indicated at the management system.
A fault in the connection between the management system and a fire alarm control panel can be
indicated both on the management system (fire alarm control panel fault) and on the fire alarm
control panel (main control unit fault). It is indicated as a main control unit fault followed by the
master system number (see point 4.3).

4.2 Domains Concept
The SecoNET network can be split into a maximum of 15 domains. Every client can be assigned to
one or more domains.
A message is only forwarded from a node to an addressed client, if the recipient has been assigned
to at least one domain, to which the sender of the message has also been assigned.
The assignment of Clients to domains is programmed when configuring the SecoNET network. For
this reason the domains structure should already be set during the planning phase
Example:
Management system 1 belongs to domains 1-3 => receives all information from domains 1-3
Management system 2 belongs to domain 2 => therefore only receives information from UZ6
Main control unit (UZ2) => belongs to domain 1

=> receives all information from UZ4, UZ1, UZ5 and UZ8
Domains 1, 2, 3
Manage. Sys. 1
Domain 2 Domain 1
Manage. Sys 2 HZ (UZ) 2
Domain 2 Domain 1 Domain 1

UZ 6 B4 - UZ 8 B3 - UZ 4
Domain 3 Domain 1 Domain 1

B4 - UZ 7 B3 - UZ 5 B3 - UZ 1

4.3 The Management System
Indication of all SecoNET events and operation of subcontrol units.
During the configuration process it is possible to set which number the failure of a management
system is indicated on a BMZ Integral.
Example:
In UZ5 the management system element is configured as number 1.
Management System 1 fault is displayed if the management system fails.
If there are several management systems deployed in the SecoNET network, then management
system failures are indicated with an additional number (e.g. management system 1/2). Only when
all management systems fail will the fault be displayed with only the management system number
(e.g. Management System 1).
Note:
Only those management systems which belong to the same domains as the control panels will
be displayed as having faults on the fire alarm control panels.
All control panels which belong to the same domain as the management system must be
programmed to the same management system number!
Numbering order where there are several management systems:
Example: 2 management systems
The first number (1) is set during the BMZ programming for the management system element.
The second number is generated from the order of the addressing of the Subnet and Node number.
The lowest combination assumes the number 1.
1.) Management system "1" Subnet number 2, Node 4 => automatically displayed as 1/1 when there
is a failure.
2.) Management system "2" Subnet number 2, Node 5 => automatically displayed as 1/2 when there
is a failure.

4.4 The Main Control Unit
During the configuration process it is possible to set which number the failure of a main control unit
is indicated on a BMZ Integral.
Example:
In UZ5 the main control unit element is configured as number 1.

Display reads Fault main control unit 1 when the main control unit fails.
If there are several main control units deployed in the SecoNET network, then main control unit
failures are indicated with an additional number (e.g. main control unit 1/2). Only when all main
control units fail will the fault be displayed with only the main control unit number (e.g. main
control unit 1).
Note:
Only those main control units which belong to the same domains as the fire alarm control panels
will be displayed as having faults on the fire alarm control panels.
All fire alarm control panels which belong to the same domain as the main control unit must be
programmed to the same main control unit number!
Numbering order where there are several main control units:
Example: 2 main control units
The first number (1) is set during the BMZ programming for the main control unit element.
The second number is generated from the order of the addressing of the Subnet and Node number.
The lowest combination for the main control unit assumes the number 1.
1.) Main control unit "1" Subnet number 2, Node 3 => automatically displayed as 1/1 when there is
a failure.
2.) Main control unit "2" Subnet number 2, Node 8 => automatically displayed as 1/2 when there is
a failure.
4.5 Routing
If two Subnets are connected, then information received on one Subnet is only transferred on to the
second Subnet, if the information is also required by this Subnet.

5.0 Connectivity Options with SecoNET
5.1 BMZ Integral or BMZ Integral C

The BMZ Integral itself is connected internally via the SPI bus with the communications module.
The connection to the SecoNET network is made using a free interface on the communications
module. The modules B3-USI4 and B3-LPI can be used as communications modules with the BMZ
Integral and the module B4-USI can be used with the BMZ Integral C.
SecoNet SecoNet
5.2 BMZ Integral and a Management System

The connection to the SecoNET network is made using an interface on the communications module.
The connection to the management system is made using the second interface of the same
communications module. The B3-USI on the BMZ Integral can be used as the communications
module.
SecoNet SecoNet
Management
system,
MAXIMA,
MaxNet

5.3 BMZ Integral, SecoNET Main Loop and Subordinated Loop
The connection to the SecoNET network main loop as were as to the subordinated SecoNET
network loop is made by each using one interface of the same communications module. The B3-
USI on the BMZ Integral can be used as the communications module.
SecoNet
SecoNet (main loop)
(main loop) SecoNet
(subordinated loop)
5.4 BMZ Integral Connecting two systems

As a maximum of one management system or a MaxNet can be connected to a B3-USI4
communications module (the second interface is required by the SecoNET network), two
communications modules are required. A management system or a MaxNet can be connected to
each of these communications modules. The BMZ Integral itself is connected internally via the SPI
bus with one of the communications modules.
From a SecoNET network topology point of view, in this instance there are two nodes, with the first
node being connected to two clients (the BMZ Integral and the management system) and the second
node is connected to only one client (the second system).
SecoNet SecoNet
Mng. Sys, Mng. Sys,

MAXIMA, MAXIMA,
MaxNet MaxNet
This configuration should be avoided at all costs!!!

6.0 The Relationship of the Fire Alarm Control Panel to the SecoNET
Network
6.1 BMZ Integral

The BMZ Integral is in principle always connected with the communications module via the
internal SPI bus.
When a superordinated management system is directly connection to a BMZ Integral, then the
status of the connection between the communications module and the management system to the
BMZ Integral is displayed as follows:
A fault on a transmission path where the management system is redundantly connected is

displayed as being a connection fault.
The complete failure of the entire connection to the management system is displayed as a main
control unit fault.
When the BMZ Integral is connected to the SecoNET network, then SecoNET network faults are
displayed on the BMZ Integral as follows:
Transmission path faults in the SecoNET network are not displayed on the BMZ Integral.
The failure of the management system (or a fault in the connection between the BMZ Integral
and the management system) is displayed on the BMZ Integral as a main control unit fault.
If several management systems are connected to the SecoNET network, then the failure of
one/several management system(s) is displayed using SubElementNumbers, with the failure of
all management systems being displayed as a main control unit fault.
6.2 BMZ Maxima

The BMZ Maxima can be connected to the communications module both redundantly and
non-redundantly. Faults are displayed on the BMZ Maxima as follows:
A transmission path fault between the BMZ Maxima and the communications module when
connected redundantly is displayed as a flat module fault #20 or #21.
The complete failure of the connection between the BMZ Maxima and the communications
module is displayed as falt module fault #25..

6.3 Standard-Maxnet
The Standard Maxnet can be connected to the communications module both redundantly and
non-redundantly. Faults are displayed in the Standard Maxnet as follows:
The fault indication on the BMZ Maxima which is connected to the communications module
corresponds to that of the BMZ Maxima.
Other BMZ Maximas in the Standard Maxnet do not indicate faults that affect the SecoNET
network.
6.4 Enhanced Maxnet

The enhanced MaxNet can be connected to the communications module both redundantly and
non-redundantly. Faults are displayed in the enhanced Maxnet as follows:
The fault indication on the BMZ Maxima which is connected to the communications module
corresponded to that of the BMZ Maxima.
Other BMZ Maximas in the enhanced Maxnet do not indicate faults that affect the SecoNET
network.

7.0 Training Examples
All training examples serve merely as the basis of discussion in the seminar.
7.1 Example 1
BMZ 4
ET NET Integral
o N co e t 3
Sec net 5 e
S bn
Sub NE) Su
(LI
BMZ 1
BMZ 7 Integral
Integral C
BMZ
SecoNET MAXIMA
Subnet 2
SecoNET
BMZ 6
Subnet 4
BMZ 2 (E-MAXNET)
Integral C Integral
SecoNET
Service
Subnet 1 PC
(main loop) LTS
BMZ 5 BMZ 3
Integral C Integral

7.1.1 Network Configuration
The diagram shows the complete layout of a SecoNET network. Detailed information, such as the
Subnet numbers, Node or Client numbers are also displayed.
The SecoNET network configuration listing can be obtained using the Servicetool. The coloured
connections depict the router connections between the individual subnets.

7.2 Example 2
SecoNET
Subnet 5
(LINE)
BMZ 10 BMZ 1 SecoNET BMZ 2 SecoNET BMZ 7

Integral C Integral
Subnet 4
Integral Subnet 3 Integral C
Service
PC
BMZ 3
BMZ 5 Integral
Integral C
LTS
BMZ "X"
Integral
SecoNET
BMZ 6 Subnet 1
Integral C (main loop)
BMZ 9
Integral
BMZ Integral
Subcontrol unit
BMZ BMZ 4
Integral loop
MAXIMA
BMZ 9
Integral C
SecoNET
Subnet 2
UZ1
(MAXNET)

7.2.1 Control Panel Configuration (only network modules)
The table is currently only intended to make the SecoNET network structure easier to understand.
Sub- Control panel Control Comm. Interface connections

net type panel module A0 B0 A1 B1
number
B3-USI4 to B control
1 INTEGRAL BMZ 3 panel
B3-USI4 to Service PC
1 INTEGRAL BMZ 4 B3-USI4 to MAXIMA to MAXIMA to BMZ
1 INTEGRAL BMZ 9 B3-USI4
B3-USI4 to A0 BMZ 9 to B0 BMZ 9 - -
INTEGRAL C B4-USI4 to B0 BMZ 9 to A0 BMZ 9 - -
1 INTEGRAL C BMZ 5 B4-USI4
2 MAXIMA UZ1
In BMZ Integral Control Panels, B3 - LPI modules can also be used for communication.

7.2.2 Network Structure
The diagram shows the complete layout of a SecoNET network. Detailed information, such as the
Subnet numbers, Node or Client numbers are also displayed.

7.3 Example 3 (with main control unit)
Subnet 4
(LINE) BMZ 6
TZ 2
BMZ 8 Integral
Integral
BMZ 6
BMZ 4 TZ 1
Integral
Integral C
BMZ 1
Integral
SecoNET BMZ 3 SecoNET

BMZ 5 SecoNET
Integral Subnet 3
Subnet 1 Integral Subnet 2
(Main loop)
BMZ 2
Integral
HZ
Service
PC
SecoLOG
Control panel hardware without detector zones, controllers, etc.

BMZ 1 / UZ1:
1 pc B3-USI4
1 pc B3-LPI
BMZ 2 / UZ2 main control unit:

1 pc B3-USI4
BMZ 3 / UZ3:
1 pc B3-USI4
BMZ 4 / UZ4:
1 pc B4-USI
BMZ 5 / UZ5:
1 pc B3-USI4
BMZ 6 / UZ6:
1 pc B3-USI4

15.0 List of Document Versions
VERSION DATE INFORMATION ABOUT CHANGES MADE

P 0.0 25.07.2001 Unofficial version for information purposes
P 0.1 12.12.2001 Informative version P 0.0 extended
V 1.0 03.01.2002 First preliminary edition
V 1.1 18.01.2002 Revised edition (alterations, corrections)
V 1.2 30.01.2002 First edition
V 1.3 05.11.2002 Extension of point 1.1 Safety tips for servicing and maintenance
V 1.4 21.01.2005 New domains concept
V 1.5 18.02.2005 Extended / new: 4.2-4.4 Domains Concept, Management System,
Main Control Unit, 3.3 Main Control Unit and 7.0, 7.3 in entirety.
V1.6 27.07.2009 New chapter 3.6.3, expanded chapter 3.6.2
V1.7 30.09.2009 3.6.2 Chapter with an example expanted
Ing. Gnter
Porcher
Austria,
Vienna
2009.09.30
13:48:18
+02'00'


Seconet PRJ en

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

Seconet PRJ en

Uploaded by

Copyright:

Available Formats

SecoNET network

Copyright 2001-2009 by SCHRACK Seconet AG

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 3(42)

If you have suggestions for

1.1 Important note about servicing and maintenance work

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 4(42)

COURSE CONTENT: Basic Network Principles,

PRE-REQUISITES: Course: Introduction to fire alarm technology

Knowledge of BMZ MAXIMA systems would be advantageous

1.3 About this training manual

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 5(42)

2.2 Network Structure

max. 16 Subcontrol units

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 6(42)

Client Every system connected to a communications module (fire alarm control

Router To reduce the amount of communications in the SecoNET network, Subnets

MaxNet An individual BMZ MAXIMA, BMZ MAXIMA standard network or BMZ

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 7(42)

B3/B4 B3/B4 B3/B4 B3/B4

BMZ Integral BMZ Integral

BMZ Integral BMZ Integral

B3/B4 B3/B4 B3/B4 B3/B4

2.5 Connecting MAXIMA and Management Systems

BMZ BMZ BMZ

Stub line connection:

Integral Standard Protocol preferred protocol for connecting management systems

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 9(42)

BMZ BMZ BMZ

BMZ BMZ BMZ BMZ

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 10(42)

BMZ BMZ BMZ BMZ

BMZ BMZ BMZ BMZ

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 11(42)

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 12(42)

A maximum of 32 main control units can be connected in a SecoNET network if no management

BMZ BMZ BMZ

BMZ BMZ BMZ BMZ

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 13(42)

No criteria for reactuation

Local controllers are actuated through links

External element (related only to main control units)

No internal operating panel is possible

2.7.2 Actuation Concept

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 14(42)

Element No. e.g.: group

Running List number

2.7.4 Area Filters

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 15(42)

Integral with closed door

BAF module (B5-BAF from software version 5.1.x)

USI4 or LPI (version C or higher)

MTI module (only for use as an element input)

DCI module (only for use as an element input)

The following hardware is required for a main control unit:

Software from version 5.0.x

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 16(42)

3.1 Using several communications modules

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 17(42)

Hardware diagram for the example above:

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 18(42)

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 19(42)

File name: SecoNET_PRJ-en.doc Version V 1.7 Page 20(42)

A centralized main detector is actuated from the main control unit.

Example: Netz work Error code = 01024 + 116 + 0 + 1 =17