Académique Documents
Professionnel Documents
Culture Documents
MAXIMA
1.0 General 3
1.1 Important note about servicing and maintenance work 4
1.2 Course content 4
1.3 About this training manual 4
2.0 General 5
2.1 BMZ MAXIMA SecoNET connection 5
2.2 Application of SecoNET-Applications 5
3.0 Limitations 6
3.1 Intervention 6
3.2 Delay 6
3.3 Key Switch Dependency 6
3.4 SecoNET Area Filters 6
3.5 NetworkEvents 6
3.6 SecoNET Main Control Unit Fire Brigade Control Panel 7
3.6.1 Austria, NORM F3031 7
3.6.2 Germany, DIN 14661 7
3.6.2 Germany, DIN 14662 8
3.6.4 FBF-Munich 8
3.6.5 Switzerland, SN054002 8
3.6.6 Sweden 8
3.6.7 Sweden, SS3654 9
3.6.8 Sweden, Intervention Panel 9
3.7 Status Queries 10
4.0 Training Examples 11
4.1 Example 1 (Software Version pre 5.1) 11
4.1.1 Network Configuration 12
4.2 Example 2 (Software Version pre 5.1) 13
4.2.1 Network Structure 14
5.0 List of Document Versions 15
SCHRACK Seconet AG
Training in Vienna
Trainingscenter@schrack-seconet.com
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.
These limitations apply not only for the BMZ MAXIMA fire alarm control panel, but also for BMZ
Integral units, if they are incorporated in a MaxNET.
In the chapters that follow, the effects on the indication and operation of the BMZ MAXIMA on the
SecoNET main control unit or on a management system are shown.
3.1 Intervention
Intervention of a BMZ MAXIMA fire alarm control panel can not be indicated or carried out at the
SecoNET main control unit. (There are solutions for this problem, but they are very complicated)
3.2 Delay
The delay levels (daytime/nighttime switchover levels) of a BMZ MAXIMA fire alarm control
panel can not be indicated or carried out at the SecoNET main control unit.
When using SecoNET area filters, only elements of the assigned area are displayed on the main
control units operating panel. Since BMZ MAXIMA elements can not be assigned to any area,
they are not displayed on the operating panel.
3.5 NetworkEvents
The result of a boolean link can be sent in the form of a NetworkEvent to any subcontrol unit from
the SecoNET main control unit. Consequently controllers of a subcontrol unit can be triggered as a
result of any SecoNET events.
NetworkEvents are not supported by the BMZ MAXIMA. If the SecoNET main control unit sends
a NetworkEvent to a BMZ MAXIMA, then this NetworkEvent is rejected by the gateway.
3.6.4 FBF-Munich
This FBF is not supported by the B3 main control unit.
3.6.6 Sweden
Example:
Messages that have been sent repeatedly as a result of a status query are specially marked. These
specially marked messages can not be evaluated by the SecoNET main control unit or a
management system.
Exception:
After the connection to a subcontrol unit has been established, the current status of this subcontrol
unit must be requested (aggregate query). During this aggregate query, all statuses of the subcontrol
unit are sent repeatedly.
The duration of this aggregate query is defined (the start and end is marked by special messages).
All messages received during this aggregate query must be evaluated by the SecoNET main control
unit or by a management system (aggregate queries are replied to by the BMZ MAXIMA with
individual detector recognition).
BMZ 4
Integral
b n et 5 N3 t 3
Su NE) bn
e
(L I S u
BMZ 7 BMZ 1
Integral C Integral
BMZ
N3 MAXIMA
Subnet 2
Subnet 4
(E-MAXNET)
BMZ 6 BMZ 2
Integral C Integral
N3 Subnet 1 Service
PC
(Main loop)
LTS
BMZ 5 BMZ 3
Integral C Integral
Graphical depiction of a
Subnet loop
Graphical depiction of a
Router
Graphical depiction of a
RouterNode with Client
Graphical depiction of a
MaxnetSubnet
Graphical depiction of a
RouterNode with
Maxnet
Graphical depiction of a
Subnet stub
Graphical depiction of
the end of a stub
Router connection from one Subnet to the other, this is
only shown for illustrative purposes.
Subnet 5
(LINE)
Service
PC
BMZ 3
BMZ 5 Integral
Integral C
e
Manag
BMZ "X" ment
Integral system
N3 Subnet 1
BMZ 6
Integral C (MainNet)
BMZ 9
Integral
BMZ Integral
Subcontrol unit
BMZ 4
BMZ Integral loop
MAXIMA BMZ 9
e
Manag
ment Integral C
Subnet 2 system
UZ1
(MAXNET)
In this configuration there was originally no separate interface intended for a management system.
The service interface was intended more of a management system.
Note:
The optimal solution would be a separate interface in the main loop (sub loop 1) for the
management system. See BMZ INTEGRAL "X" in the example above. A B3-USI4 is
used in this control panel, with one interface used for the SecoNET network connection
and the second interface being used for connecting the management system!
An alternative solution would be to connection the management system to the first
interface of the B3-USI4 module on the BMZ INTEGRAL (control panel 9). The second
interface could be used for connection to the SecoNET network. A B3-LPI module is
required for connecting the INTEGRAL C.
File name: SecoNET_tech_MAXIMA-en.doc Version V 1.0 Page 13 (15)
Doc. No. see above SPT/G. Porcher 27.07.2009
SecoNET TECH T1 BMZ
BMZ MAXIMA
4.2.1 Network Structure
Description as per point 4.1.1.
Ing. Gnter
Porcher
Austria,
Vienna
2009.07.29
13:57:10
+02'00'