SecoNET Network

for Technicians
Part 1

Copyright 2001-2009 by SCHRACK Seconet AG

SecoNET - Technicians Part 1
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
1.4 SecoNET Network Definitions 6
2.0 Programming 8
2.1 List generator/Dongle 8
2.2 SecoNET Applications 9
2.3 Integral Standard Protocol (ISP) 10
2.4 SecoNET connection 12
2.5 SecoNET Repeater 13
2.6 SecoNET ZZK connection 13
2.7 SecoNET EZZK connection 14
3.0 Application of SecoNET Applications 15
3.1 General 15
3.2 Integral Standard Protocol (ISP) 16
3.3 SecoNET connection 16
3.4 SecoNET Repeater 17
3.5 ISP + SecoNET connection 18
3.6 ISP + SecoNET Repeater 18
3.7 SecoNET Connection + SecoNET Repeater 19
3.8 SecoNET Repeater + SecoNET Repeater 19
3.9 SecoNET Connection + SecoNET ZZK Connection 20
3.10 SecoNET Repeater + SecoNET ZZK Connection 20
3.11 SecoNET Connection + SecoNET EZZK Connection 21
3.12 SecoNET Repeater + SecoNET EZZK Connection 21
3.13 ISP + ISP 22
3.14 ISP + SecoNET ZZK connection 22
3.15 ISP + SecoNET EZZK connection 23
4.0 Configuration 24
4.1 SecoNET PC Cable 25
4.2 Connections 26
4.3 Interface Connection Configurations 28
4.4 Modem Sections 28
4.5 Displaying events in the SecoNET Network 28
5.0 Network Assistant 29
5.1 User Interface 30
5.2 NetworkView (Elements) 31
5.2.1 Network 31
5.2.1.1 NetworkView-Symbol 31
5.2.1.2 Subnet 31
5.2.1.3 Node 31
5.2.1.4 RouterNode 32
5.2.1.5 Client 32
5.2.1.6 Wire Break 32
File name: SecoNET_tech_1-en.doc Version V 1.9 Page 2 (71)
Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.3 Network Element Status Indication 33
5.4 PropertyView 35
5.5 Editable Values 36
5.6 Functions 38
5.6.1 Time-Master/-Slave Configuration 38
5.6.1.1 General 38
5.6.1.2 Time Master with a Main Control Unit / Control Panel 38
5.6.1.3 Time Master with three Control Panels 39
5.6.1.4 Time Master with Management System 39
5.6.2 Maxnet Configuration 40
5.6.3 Assigning Clients to Domains 41
5.6.3.1 General 41
5.6.3.2 Example of a Domain Assignment 42
5.7 Reading out the SecoNET Configuration 43
5.8 Uploading the SecoNET Configuration 43
5.8.1 Software up to version 5.0.x 43
5.8.1 Software from version 5.1.x 43
6.0 Commissioning a SecoNET network 44
6.1 Preparations 44
6.2 Partial Commissioning 44
6.2.1 Example 1 - Subnet - Extension 45
6.2.2 Example 2 - Subnet - Extension 47
6.2.3 Making a Network smaller 52
6.3 Virtual Configuration Node 54
6.4 Complete Commissioning 54
6.5 Testing and Fault finding 55
6.5.1 Reading the Topology 55
6.5.2 Network Error Messages 56
6.5.3 Error Message from virtual configuration nodes 58
6.5.4 Fault arising from insufficient RAM on communications cards 59
6.5.5 Error messages on the main control unit 60
6.5.6 Error messages on the sub control unit 60
6.5.7 Error messages on the centrals with 2 sub networks 61
6.6 Network error number calculation 63
6.6.1 Port adress by communication with central units 64
6.6.2 Port adress by communication with PC 65
7.0 Training Examples 66
7.1 Example 1 (Software Version pre 5.1) 66
7.1.1 Network Configuration 67
7.2 Example 2 (Software Version pre 5.1) 68
7.2.1 Control Panel Configuration (only network cards) 69
7.2.2 Network Structure 70
15.0 List of Document Versions 71

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 3 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
1.0 General
This document is the accompanying documentation for the SecoNET network training course.

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:
[email protected]

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.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 4 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
1.2 Course content
COURSE AIMS: Participants should be able to carry out all SecoNET network-related
tasks contained within the course content.

COURSE CONTENT: Definitions of terms,

Applications,
Software tools,
Configuration,
Programming,
Commissioning a SecoNET network
Extending a SecoNET network
Basic Fault Search

PRE-REQUISITES: Good PC, DOS and Windows skills

Course: Introduction to fire alarm technology
Course: BMZ INTEGRAL Basic + Network (Subcontrol unit loop)
Course: BMZ INTEGRAL List generator - basic
Course: BMZ INTEGRAL List generator - advanced
Course: Seconet planning (compulsory)
Advantageous for participants:
Course: BMZ MAXIMA basic + programming

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 also serve as a work of
reference afterwards. All examples have been compiled and tested for their practicality in order to
give you the best possible overview about how a SecoNET network works.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 5 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
1.4 SecoNET Network Definitions
Subnet
Communications modules of a BMZ Integral form a loop network in the SecoNET
network. Every one of these SecoNET loops (main loop, subordinated loops) is
described as a Subnet.

MainNet
Name given to a Subnet which is in the middle of several Subnets.

Node (Nodes)
Every BMZ Integral communications module in a Subnet is called a Node.

Subcontrol unit number

Every control panel must be assigned a UZ no. (subcontrol unit number in the range
of 1-254).

Client (Device)
Every system connected to a communications module (fire alarm control panel,
control system etc.) is called a Client.

Client Address
Due to the SecoNET networks topology, every client is given a hierarchical address
with the format Subnet.Node.Client.

ClientIdentifier
The type of a client (manufacturer and model) is known as the ClientIdentifier (every
Client must be identified when registering itself as part of the SecoNET network).

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 (see Client
Address) are only configured once the network is operational.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 6 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
Group
Every Client in the SecoNET network is assigned to a group. The assigning of a
Client to a group determines what information can be exchanged between the Client
and the SecoNET network. Currently the groups OperationUnit (for management
systems), DetectionUnit (for fire alarm control panels) and ServiceUnit (for
ServiceTools) exist. Assigning a Client to a group is done when the Client registers
on the SecoNET (and can be selected by the SecoNET).

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.

Main control unit

Superordinated BMZ Integral unit, at which all states of the SecoNET network can
be indicated, as well as for full operation of the BMZ Integral control panels
connected in the SecoNET.

Management system
Superordinated computer system for indication and full operation of states in the
SecoNET system.

TimeMaster
States from which control panel/main control unit/management system the SecoNET
clock should be synchronised.

TimeMasterPriority
States with which level of priority the synchronisation of the system clock should be
carried out (0...lowest priority, 255...highest priority). When devices have equal
priority, the Subnet Node Address is used to decide, with ascending order being
used.

Delay
Defines the delay level (intervals of 100ms) between subcontrol units when
collective commands as used.

Client Priority (Main control unit or management system)

Clients of the main control unit or management system groups, which are located in
the exactly the same domains as each other can be assigned a priority. Operation at a
management system/main control unit with low priority is blocked as long as there is
a connection to a management system/main control unit with higher priority.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 7 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
2.0 Programming

2.1 List generator/Dongle

It is necessary for every BMZ control panel connected in the SecoNET network to be programmed
separately. The control panels can be programmed using different PCs as well as by different
technicians. A SecoNET dongle is required to export the configuration data from list generator for a
SecoNET network project. This dongle also allows previous exported configurations to be used.

Every communications module in the SecoNET required its own unique ID (Node-ID). This ID is
required for the communications mechanism in the Subnet and for configuring a Node.
This ID is assigned by list generator (using the special SecoNET dongle). The individual BMZ
Integral units in a SecoNET network are independently configured from one another.

When exporting a SecoNET configuration, the

technician must enter whether he wishes to keep
(YES) the Node IDs that have been assigned or
whether he wants to assign new (NO) Node IDs.

Addresses with SecoNET Node ID are assigned afresh.

SecoNET Node ID addresses remain the same

Caution:

If an existing configuration is extended, then the Node IDs must be kept (otherwise the
configuration data saved in the communications modules will no longer be valid).

If a configuration for a new SecoNET project is compiled based on an existing

configuration, then new Node IDs must be assigned (otherwise the same Node IDs will
be used in two different projects).

As the Node IDs are only generated when the configuration is exported,
the configuration must then be saved again, so that the Node IDs that have
already been assigned can be taken into the LDB file and are available for an extension of
the configuration at a later point in time.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 8 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
2.2 SecoNET Applications
The following applications can be used on the B3-USI4 communications module and sometimes
also on B3-LPI and B4-USI communications modules.

Label Description Modules:

Integral Standard Protocol A superordinated management system is connected B3-USI4, B3-
to a single BMZ Integral with this application LPI, B4-USI
OR
connected to the SecoNET network
SecoNET connection The BMZ Integral is connected to the SecoNET B3-USI4, B3-
network using this application LPI, B4-USI
SecoNET connection The BMZ Integral main control unit is also B3-USI4, B3-,
(Main control unit) connected to the SecoNET network using this B4-USI
application
SecoNET-Repeater With this application, the communications module B3-USI4, B3-
can be switched into being a repeater in the LPI, B4-USI
SecoNET network The BMZ Integral, in which this
communications module can be found, is not
connected to the SecoNET network.
SecoNET ZZK A BMZ Maxima or a standard Maxnet is connected B3-USI4
connection to the SecoNET network using this application
SecoNET EZZK An extended Maxnet is connected to the SecoNET B3-USI4
connection network using this application

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 9 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
2.3 Integral Standard Protocol (ISP)
A superordinated management system can be connected to a single BMZ Integral or to the
SecoNET network with the ISP protocol. In List Generator the application Integral Standard
Protocol is selected for the desired interface for the communications module.

Programming a single control panel or a subcontrol unit loop and connection of a

management system:

If the ISP protocol is configured, then the management system is connected to the BMZ
Integral.

If no SecoNET application is configured on the second available interface, then the

management system is connected to the BMZ Integral (subcontrol unit loop).

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 10 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
Programming a single control panel or a subcontrol unit loop and connection of a
management system with ISP in a SecoNET network:

If a SecoNET application is also configured on the second available interface, then the
management system is connected to the SecoNET network.

Note:
In the illustrations above, only a B3-USI4 module is shown, so therefore to connect
subcontrol units, either a B3-LPI module or a B3-USI4 module is necessary in addition!

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 11 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
For the interface for connecting a management system, only RS232, RS422, RS485 and the bit rate,
parity etc. need to be configured. It is not necessary to configure the management system used (type
and function).
(picture swapped)

When connecting a superordinated management

system to a BMZ Integral, the management system is
depicted on the BMZ Integral as being a management
system. A logical number must be configured for this
management system.

2.4 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.
Management systems are depicted in the SecoNET network on the BMZ Integral as management
systems and main control units as main control units. A logical number must be set for both the
management system and the main control unit.
(picture swapped)
RS232, RS422, 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 (next control panel).
The SecoNET topology does not
require setting.

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.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 12 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
2.5 SecoNET Repeater
The SecoNET repeater can be used to
add one the BMZ Integrals
communications modules to the
SecoNET network.

The SecoNET repeater does not

connect the BMZ Integral to the
SecoNET network.
(picture swapped)

2.6 SecoNET ZZK connection

A BMZ Maxima or a standard Maxnet can be connected to the SecoNET network using the
SecoNET ZZK connection.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 13 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
2.7 SecoNET EZZK connection
An extended Maxnet can be connected to the SecoNET network by means of the SecoNET EZZK
connection. The B3-USI4 communications module can be used for this purpose.

When carrying out the SecoNET EZZK connection settings for the connection to the BMZ Maxima
main control unit (i.e. RS232/RS422 and the bit rate and parity) must be set.

The enhanced Maxnet is depicted as a Subnet in the SecoNET network. Every subcontrol unit (ZU)
in the enhanced Maxnet is depicted in the SecoNET network as a Node (with Client no. 0). A client
in the enhanced Maxnet can therefore be addressed like any other Client in the SecoNET network.

(picture updated)
Subnet "X"
Extended Maxnet
BMZ UZ 3
Integral
UZ 20
Node
UZ 2
(e.g.: 2)

BMZ SecoNET BMZ Node

Integral Integral UZ 1
(Main Loop) (e.g.: 1)
UZ 22 UZ 21 UZ 4
Node
(e.g.: 0) UZ 5
Node
BMZ (e.g.: 4)
Node
Integral
(e.g.: 3)
UZ 23

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 14 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.0 Application of SecoNET Applications

3.1 General
Configuration dialogue window of configured SecoNET applications for a B3-USI4 module:

BMZ MAXIMA
BMZ (Standard Maxnet)
INTEGRAL

NETWORK ? ? CLIENTS
Management
System

B3-USI4
B3-LPI
B4-USI

SecoNET SecoNET
Subnet Subnet

Description of the right illustration:

The first segment (top left) shows the connection of the BMZ Integral to the
communications module. If this connection exists, then information can be exchanged
between the BMZ Integral and the communications module. For this interface, the SPI Bus
is used, which connects all modules within the BMZ Integral with the B3-MCU32.

The second segment (top right) shows the connection from the management system to the
communications module. For these interfaces, in physical terms port 0 or port 1 of the
communications module is used.

The third segment (bottom left) shows the connection of the communications module to a
network (SecoNET or enhanced Maxnet). For this interface, in physical terms port 0 or port
1 of the communications module is used.

The fourth segment (bottom right) shows the connection of the communications module to a
network (SecoNET or enhanced Maxnet). Two networks can be connected to one another in
this way with a single communications module. For this interface, in physical terms port 0
or port 1 of the communications module is used.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 15 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.2 Integral Standard Protocol (ISP)
The Integral Standard Protocol is configured for one of the interfaces of the communications
module. The second interface is not used or is used for applications (e.g. loop applications) which
do not relate to the SecoNET network.

BMZ Management
INTEGRAL System

NETWORK ? ? CLIENTS
B3-USI4
B3-LPI
B4-USI

The communications module connects the BMZ Integral with a management system or MaxNet. In
the case of a management system, in this case it is a superordinated system. It is not possible to
connect a subordinated system (e.g. MaxNet) in this instance, as the second interface is not used.

In this special case it is not a SecoNET network (although a SecoNET application is used). When
configuration is carried out, no Node ID is assigned, and configuration is not necessary.

3.3 SecoNET connection

A SecoNET connection is configured for one of the interfaces of the communications module. The
second interface is not used or is used for applications (e.g. loop applications) which do not relate to
the SecoNET network.

BMZ
INTEGRAL
NETWORKA BCLIENTS

B3-USI4
B3-LPI
B4-USI

SecoNET
Subnet

The communications module connects the BMZ Integral with the SecoNET.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 16 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.4 SecoNET Repeater
A SecoNET repeater is configured for one of the interfaces of the communications module. The
second interface is not used or is used for applications (e.g. loop applications) which do not relate to
the SecoNET network.

NETWORKA BCLIENTS
B3-USI4
B3-LPI
B4-USI

SecoNET
Subnet

In this instance the BMZ Integral does not have a connection to the SecoNET.

TZ1 TZ2 TZ1 TZ2

BMZ INTEGRAL BMZ INTEGRAL

Subcontrol unit Subcontrol unit
loop (Building A) loop (Building B)

TZ4 TZ3 TZ4 TZ3

SecoNET
Subnet
(MainNet)
TZ1 TZ2

BMZ INTEGRAL
Subcontrol unit
loop (building C)
TZ4 TZ3

Three BMZ Integrals (each with a subcontrol unit loop in building A, B and C) should be connected
with a SecoNET. A B3-USI4 is required in each of these BMZ Integral units (TZ3 in building A,
TZ4 in building B and TZ1 in building C), on which one interface is used for the loop application
(subcontrol unit loop) and the second interface is used for the SecoNET connection (connecting the
BMZ Integral to the SecoNET network). Building A can now be connected to buildings B and C to
a SecoNET network.
The connection distance between building B and C is, however, too large (>1200m) to be able to
directly connect these buildings with one another. However, it would be possible to connect TZ4 in
building B and TZ2 in building C (< 1200m).
File name: SecoNET_tech_1-en.doc Version V 1.9 Page 17 (71)
Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
For this reason TZ2 in building C also requires a B3-USI4, in which one interface is used for the
loop application (subcontrol unit loop) and the second interface is used for the SecoNET repeater.
The connection between TZ4 in building B and TZ1 in building C via TZ2 in building C can now
be completed.
The events of the BMZ Integral in building C are only forwarded to the SecoNET network from the
interface of TZ1.

It should be remembered that for subcontrol unit loop communication with the SecoNET
network, two separate communications paths (circuits) are required between TZ1 and TZ2 in
building C.

3.5 ISP + SecoNET connection

Integral Standard Protocol is programmed on one interface of the communications module, and a
SecoNET connection on the second interface. The communications module connects the BMZ
Integral and a management system with the SecoNET.

BMZ Management
NETWORK ? ? CLIENTS INTEGRAL
System

B3-USI4

SecoNET
Subnet

3.6 ISP + SecoNET Repeater

Integral Standard Protocol is programmed on one interface of the communications module, and a
SecoNET repeater on the second interface. The communications module connects a management
system with the SecoNET. In this instance the BMZ Integral does not have a connection to the
SecoNET.

Management
NETWORK ? ? CLIENTS

system

B3-USI4

SecoNET
Subnet

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 18 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.7 SecoNET Connection + SecoNET Repeater
A SecoNET connection is programmed on one interface of the communications module, and a
SecoNET repeater on the second interface. This communications module connects the BMZ
Integral and two SecoNET Subnets with one another.

BMZ
INTEGRAL

NETWORKA B CLIENTS
B3-USI4

SecoNET SecoNET
Subnet Subnet

3.8 SecoNET Repeater + SecoNET Repeater

A SecoNET repeater is configured on both of the interfaces of the communications module. This
communications module connects two SecoNET Subnets with one another. In this instance the
BMZ Integral does not have a connection to the SecoNET.
NETWORKA B CLIENTS

B3-USI4

SecoNET SecoNET
Subnet Subnet

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 19 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.9 SecoNET Connection + SecoNET ZZK Connection
A SecoNET connection is programmed on one interface of the communications module, and a
SecoNET ZZK connection on the second interface. The communications module connects the BMZ
Integral and a BMZ Maxima (or a Standard Maxnet) with the SecoNET.

BMZ BMZ MAXIMA

INTEGRAL (Standard Maxnet)

NETWORKA B CLIENTS
B3-USI4

SecoNET
Subnet

3.10 SecoNET Repeater + SecoNET ZZK Connection

A SecoNET repeater is programmed on one interface of the communications module, and a
SecoNET ZZK connection on the second interface. The communications module connects a BMZ
Maxima (or a Standard Maxnet) with the SecoNET. In this instance the BMZ Integral does not have
a connection to the SecoNET.

BMZ MAXIMA
(Standard Maxnet)
NETWORKA B CLIENTS

B3-USI4

SecoNET
Subnet

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 20 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.11 SecoNET Connection + SecoNET EZZK Connection
A SecoNET connection is programmed on one interface of the communications module, and a
SecoNET EZZK connection on the second interface. This communications module connects the
BMZ Integral, a SecoNET Subnet and an enhanced Maxnet with one another.

BMZ
INTEGRAL

NETWORKA B CLIENTS
B3-USI4

SecoNET ERWEITERTES
Subnet MAXNET

3.12 SecoNET Repeater + SecoNET EZZK Connection

A SecoNET repeater is programmed on one interface of the communications module, and a
SecoNET EZZK connection on the second interface. This communications module connects a
SecoNET Subnet and an enhanced Maxnet with one another. In this instance the BMZ Integral does
not have a connection to the SecoNET.
NETWORK ? ? CLIENTS

B3-USI4

SecoNET ENHANCED
Subnet MAXNET

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 21 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.13 ISP + ISP
Integral Standard Protocol (ISP) is configured on both of the interfaces of the communications
module. This communications module connected the BMZ Integral with e.g. two management
systems.

Management
BMZ
System
INTEGRAL

NETWORK ? ? CLIENTS
Management
System

B3-USI4

3.14 ISP + SecoNET ZZK connection

Integral Standard Protocol is programmed on one interface of the communications module, and a
SecoNET ZZK connection on the second interface.

BMZ MAXIMA
BMZ (Standard Maxnet)
INTEGRAL
NETWORK ? ? CLIENTS

Management
System

B3-USI4

The communications module connects the BMZ Integral with a management system and a BMZ
Maxima (or a Standard Maxnet).

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 22 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
3.15 ISP + SecoNET EZZK connection
Integral Standard Protocol is programmed on one interface of the communications module, and a
SecoNET EZZK connection on the second interface.

BMZ Management
INTEGRAL

NETWORK ? ? CLIENTS
System

B3-USI4

ENHANCED
MAXNET

The communications module connects the BMZ Integral with a management system and an
enhanced MaxNet.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 23 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
4.0 Configuration
After all the BMZ Integral units have been connected to a SecoNET network, they require
configuring. The ServiceAssistant has been extended to include the functions "NetworkMonitor
and "NetworkAssistant for configuring the SecoNET network. The "NetworkMonitor" is used for
the visualization of message transmission in the SecoNET Network, whilst the "NetworkAssistant"
is used for visualizing the current topology and configuration of the SecoNET network.
For the configuration process a free SecoNET interface (Integral Standard Protocol) is required,
which the ServiceAssistant can use to connect to all SecoNET devices at any time.
In order to be able to configure the SecoNET network at any time, one or more interfaces should be
designated for connecting the ServiceAssistant. The SecoNET network can only be configured
from a BMZ Integral!

The possibility also exists of disconnecting the management system during the configuration
process, and to connect the ServiceAssistant to the interface that has been freed up. In this case, to
ensure that the SecoNET network is configured correctly, the ServiceAssistant must appear to be a
management system (Settings / CNP Options menu in NetworkMonitor).
A management system fault then appears on the control panels. For this reason, this method should
only be used for initial configuration / test configurations!

Another possibility would be to use a virtual Node. This node is not considered during the
SecoNET configuration process. For this method a transportable BMZ Integral with a special
configuration and adapter cable if necessary.

The ServiceAssistant requires the following parameters:

Integral Standard Protocol

RS232

Bit rate: 9600bps, 19200bps, 38400bps or 57600 bps

Parity even/odd

Note:
After the Integral Software Pack has been installed, the NetworkMonitor (ServiceAssistant) is set as
standard to 9600bps. The bit rate must therefore be changed prior to being used for the first time!

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 24 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
4.1 SecoNET PC Cable
The cable is used to allow a PC to communicate with the B3-USI4 module of a BMZ Integral. It can
be used on the Service PC as well as on the management system.
B3-USI4 PC

15-pol Sub D-Stecker 9-pol Sub D-Buchse

TXD 5 2 RXD

RXD 7 3 TXD

GND 13 5 GND

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 25 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
4.2 Connections
The following possibilities exist for connecting a management system to a communications module:

Module Port Interface Description

B3-USI4 Line/Loop 0A/0B RS232 (non-redundant or interface-redundant)

RS422 (non-redundant or interface-redundant)
RS485 (non-redundant or interface-redundant)
B3-USI4 Line/Loop 1A/1B RS422 (non-redundant or interface-redundant)
RS485 (non-redundant or interface-redundant)

B3-LPI Loop 0A/0B RS485 (only interface-redundant)

B3-LPI PC Card for remote access!

B4-USI Line/Loop 0A/0B RS232 (only non-redundant)

RS422 (non-redundant or interface-redundant)
RS485 (non-redundant or interface-redundant)
B4-USI PC Card for remote access!

The following possibilities exist for connecting Nodes in the SecoNET network:

Module Port Interface Description

B3-USI4 Line/Loop 0A/0B RS232 (only non-redundant)
RS422 (only non-redundant)
RS485 (non-redundant or line-redundant)
B3-USI4 Line/Loop 1A/1B RS422 (non-redundant)
RS485 (non-redundant or line-redundant)
B3-LPI Loop 0A/0B RS485 (non-redundant or line-redundant)
B3-LPI PC Card for remote access!
B4-USI Line/Loop 0A/0B on Port 0A:
RS232 (only non-redundant)
RS422 (only non-redundant)
RS485 (non-redundant or line-redundant)
on Port 0B:
RS422 (non-redundant)
RS485 (non-redundant or line-redundant)
B4-USI PC Card for remote access!
File name: SecoNET_tech_1-en.doc Version V 1.9 Page 26 (71)
Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
For connecting a BMZ Maxima (or a standard or an enhanced MaxNet) to a communications
module, the following possibilities exist:

Module Port Interface Description

B3-USI4 Line/Loop 0A/0B RS232 (non-redundant or interface-redundant)
RS422 (non-redundant or interface-redundant)
B3-USI4 Line/Loop 1A/1B RS422 (non-redundant or interface-redundant)
B3-LPI Loop 0A/0B no possibility -
B3-LPI PC Card no possibility -
B4-USI Line/Loop 0A/0B no possibility -
B4-USI PC Card no possibility -

When connecting Nodes in the SecoNET network attention should be paid that, as par the BMZ
Integral Subcontrol unit loop that Port xA (Interface-Master) must be connected to Port xB
(Interface-Slave) of the neighbouring Node.

(New graphic)

The only exception is the B4-USI module of

the BMZ Integral C, which can the master
function can be assigned to an interface by
configuration (Parameter Master interface on
port A or port B).

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 27 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
4.3 Interface Connection Configurations
Line/Loop with 15 pin socket on modules B3-USI4 and B4-USI:

Mode
RS422 RS485 RS232 Pin Pin Label
TxD0B+ L0BX+ 1 9 GND0B
TxD0B- L0BX- 2 10
RxD0B+ L0BY+ 3 11 GND0B
RxD0B- L0BY- 4 12
TXD0B- 5 13 GND0B
RTS0B+ 6 14
RXD0B- 7 15
CTS0B+ 8

Line/Loop 9 pin socket on modules B3-USI4, B4-USI and B3-LPI

Mode
RS422 RS485 Pin Pin Label
TxD1B+ L1BX+ 1 6 GND0B
TxD1B+ L1BX- 2 7
RxD1B+ L1BY+ 3 8 GND0B
RxD1B- L1BY- 4 9
5

4.4 Modem Sections

The same rules apply for the SecoNET Network as for the B3-subcontrol unit loop (maximum of
one modem connection in a closed loop).

4.5 Displaying events in the SecoNET Network

The entire SecoNET network information can only be shown on a management system, at the main
control unit or on the Service PC.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 28 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.0 Network Assistant
The Network Assistant is a component of the B3 & SecoNET configuration tool ServiceAssistant as
well as part of the Integral Software Pack from version 4.0.0 onwards.

The Network Monitor enables the configuration of connected SecoNET Nodes (modules USI and
LPI) to loops and stubs (so-called Subnets).

After starting the ServiceAssistant, you will find yourself in Service-Monitor operating mode. In
order to be able to change to the NetworkAssistant, the Network-Monitor operating mode first of all
needs to have been activated. Only then is it possible to change into the Network-Assistant
operating mode.

To be able to operate the Network-Assistant online, the connection to the SecoNET network must
previously have been established in Network-Monitor operating mode.

The point-to-point connection between the SecoNET network and the Network-Assistant is not
automatically established when required as per LoopAssistant, but must be established by the user
in the Network-Monitor operating mode. It can take about a minute to establish the connection.

The current status of the connection to the SecoNET network is displayed in the bottom right hand
corner of the screen in the status bar.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 29 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.1 User Interface
The screenshot shows the User Interface (UI) of the ServiceAssistant in the NetworkAssistant
operating mode.
The main part of the User Interface is used to display the topology of the SecoNET network that is
being examined (hereafter referred to as the NetworkView).

Selection Fields NetworkView PreviewNetwork

PropertyView Connection status and

interface used

Selection fields:
For supporting the user for navigation in the NetworkView.

PropertyView:
The properties of the element currently selected in NetworkView are displayed in list form.

PreviewNetwork
In this window the topology of the network can be read. On the basis of these visualizations
it is possible to recognize what differences there are compared with those shown in the
NetworkView (Data from an opened file).

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 30 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.2 NetworkView (Elements)

5.2.1 Network

5.2.1.1 NetworkView-Symbol

Network element text :

"Network X with X standing for the path and filename (if known).
The central point of a SecoNET network. All Subnets of a SecoNET network belong to a network.

5.2.1.2 Subnet

NetworkView symbols: , and

Network element text: X Subnet where X stands for the Subnet address. (MAXNET) is added to
the network element text, if the Subnet is a Maxnet subnet (see below).

One or more SecoNET Nodes form a Subnet. The Nodes are linked to each other either in the form
of a loop or as a stub (2 ends). Subnets can be linked with one another by routers.

Every Subnet has a user-defined Subnet Address which is unique within the network.

Subnet loop: Standard Subnet

Subnet stub: Subnet operated as a stub (line)
MaxnetSubnet: Subnet containing a Maxnet. There is only a single Node
(RouterNode with Maxnet) in the Subnet. The Maxnet is
connected to this Node.

5.2.1.3 Node

NetworkView Symbol

Network element text: X <ABC> with X standing for the Node address and ABC for the project
name assigned in List Generator.
USI and LPI modules can form SecoNET Nodes. The Nodes manage the Clients which are
connected to the Nodes (BMZ Integral, BMZ Maxima, ...).
Nodes have a unique address within their Subnet, which are user-defined. The labelling of a Node
takes place during the List Generator configuration and takes the form of the project name.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 31 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.2.1.4 RouterNode

NetworkView symbols: , and

Network element text: as per the Node

RouterNodes are special Nodes, which as well as having the functional role of a Node also act as a
connector between 2 Subnets.

A RouterNode consists of 2 parts. One part manages any Clients that might have been connected,
and the other part is used for making the connection to the next Subnet.

Furthermore, a RouterNode enables the connection of a Maxnets. The Maxnet is then displayed as a
separate Subnet in which there is only one Node.

RouterNode with ClientsIf there are Clients on the RouterNode, then they assume
the Subnet and Node addresses of this Node.
RouterNode Only used to display the connection to other Subnets.
RouterNode with Maxnet This type of Node are connected to a Maxnet. Such a
Node forms its own Subnet with only this single Node.

5.2.1.5 Client

NetworkView Symbol

Network element text: <ABC> where ABC stands for the configured name of the Client.
Every Node (also RouterNodes) can manage up to 6 Clients. The address of a Client is fixed. The
user can only assigned a label. Furthermore the user can decide to which domains a Client belongs.

5.2.1.6 Wire Break

NetworkView Symbols and

Network element text: Dependent on status either Open Circuit or End of Line.
Wire breaks can be intended (intended stub) or unintended (wire break, failure of a Node). If a
Subnet is not closed, then the last detected Node will be displayed as a wire break symbol.

Open Circuit Real wire break (Failure of a point-to-point connection, failure of a

Node, ...)
End Of Line Intended wire break end of a stub

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 32 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.3 Network Element Status Indication
Every network element can have different statuses. These statuses are indicated by means of a
symbol to the left of the symbol for the network element in question.

Every network element has at least the status that a network element below it in the hierarchy has
(Network Subnet Node/RouterNode/Wire Break Client).

If for example a Client has Fault status, then the Node of the Client, the Subnet of the Node and
the Network itself also have Fault status!

Statuses are inherited in an upward manner!!!

Three fault cases are possible:

undefined: Properties are not defined configuration

(programming) still however possible

(green) partially faulty: Faulty configuration data configuration

(programming) is however possible

(red) faulty: faulty configuration data no configuration

possible!!!

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 33 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
The table shows the possible fault statuses of every network element, as well as the possible
causes of these statuses.

(green) (red)
Network
Subnet Subnet address is not in the range of 0
to 62.
Subnet address is not unique
Open loop and Line Flag not set (wire
break)
Node Node address is not in the range of 0 to
62.
Node address is not unique
No EEPROM
RouterNode as per Node
RouterNode At least one No Maxnet subcontrol as per Node
(Maxnet) Maxnet Client units are available check At least one Maxnet Client Address is
does not have a connection to the Maxnet) not in the range 0 to 61
label At least one Maxnet Client is not
assigned to a domain
Client Client does not Connection fault between Client is not assigned to a Domain
have a label Node/Client Unknown connection type between
Node/Client
Wire break Wire break

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 34 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.4 PropertyView
The properties of the network element selected in the NetworkView are displayed in the
PropertyView. Different properties are displayed depending on the type and status of the selected
network element.

Properties which can be changed by the user, are displayed on a button to the right of the value of
the corresponding property. By clicking on the button, the edit mode is entered, which allows a
value to be changed.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 35 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.5 Editable Values
When changing values of a network element, it should be remembered that the values only take
effect once another network element is selected!!!

1. Subnet (Subnet Address)

Decimal value in the range of 0 to 62. Any text entered will be attempted to be changed
into a value. The entry is not checked as to whether it is valid!!!

2. Node (Node Address)

Decimal value in the range of 0 to 62. Any text entered will be attempted to be changed
into a value. The entry is not checked as to whether it is valid!!!

3. RouterNode

Decimal value in the range of 0 to 62. Any text entered will be attempted to be changed
into a value. The entry is not checked as to whether it is valid!!!

4. RouterNode (with Maxnet)

Decimal value in the range of 0 to 62. Any text entered will be attempted to be changed
into a value. The entry is not checked as to whether it is valid!!!

Maxnet
By clicking on the button you will enter a Maxnet configuration dialogue window. This
dialogue window is described in the Functions chapter.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 36 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5. Client

Clienttype
If the unit is a control panel then there is a fixed assignment, whereas for other Clients
you must select what type they are (e.g.: ServiceAssistant, SecoLOG, ...)

Name
Alphanumeric value with a maximum length of 32 characters. Any characters over this
limit are ignored when taken up by the system.

Connection Type
Type of connection between the Node and the Client. Options for selection are default
and service.

Time Master Priority (see point 1.4)

Delay (see point 1.4)

Subcontrol unit number (UZ 1-254)

ClientPriority
Only where there are several main control units (see point 1.4)

6. Wire break

Connection Type
Type of connection between the Node and the Client. Options for selection are default
and service.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 37 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.6 Functions

5.6.1 Time-Master/-Slave Configuration

5.6.1.1 General
The time is synchronised in the SecoNET Network using the Time-Master function. This is carried
out by a management system as standard. All clients in the network which rely on the network time
are displayed in this dialogue window.

There are 3 categories of Clients:

Time Slaves (B3, ...)

Time Masters (B3, ...)
Fixed Time Masters (Management systems, ...)

The Clients are sorted by priority and their logical address (Subnet.Node.Client) when displayed.
Example:
000.01.02.00 (Integral 1) means Subnet 1, Node 02 [in this Subnet),
Client 0 (of Node 02).
It is possible to change Slaves into Masters and vice versa. The buttons Add and Remove are
used for this purpose.

5.6.1.2 Time Master with a Main Control Unit / Control Panel

In the following example, the synchronisation of the time is carried out by control panel 1, as there
is no management system being used in this instance.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 38 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.6.1.3 Time Master with three Control Panels
In the following example, the synchronisation of the time is carried out by control panel 2 (main
control unit), as there is no management system being used in this instance. Only if the main control
unit were to fail would subcontrol unit control panel 1 carry out the synchronisation of the
SecoNET network.
(new illustration)

5.6.1.4 Time Master with Management System

In the "Time Master" configuration with a management system, the time is synchronised by the
management system.
(new illustration)

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 39 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.6.2 Maxnet Configuration
Maxnet subcontrol units are treated as Clients in the SecoNET-Network.

To enter the dialogue window above, the property Maxnet in the PropertyView of a RouterNode
must be changed to (selected) Maxnet.

In this dialogue window, the SecoNET Node Addresses are assigned for every individual subcontrol
unit. Maxnet Node Addresses with a range of 0 to 61 are valid. Only inputted values are not
accepted. A character string of up to 31 characters is permissible as a Node Name.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 40 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.6.3 Assigning Clients to Domains

5.6.3.1 General
In practice, the domain concept is mainly used in conjunction with management systems and main
control units. There can be a maximum of 15 domains. From version 5.1 of the software the
assignment of domain numbers is automatically carried out during the configuration process.

Clients can be assigned to one or more domains.

It should be noted that only Clients which belong to the same domains as one another can exchange
information between one another.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 41 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.6.3.2 Example of a Domain Assignment
The Client-Domain assignment relates to the illustration below.

(new illustration)

The configuration in this example consists of

two Subnets, a main control unit, a management
system and three subcontrol units.

The definitive configuration:

The management system belongs to domains 1
and 2.

Subcontrol unit 4 belongs to domain 1.

The main control unit belongs to domain 2.

Subcontrol units 3 and 5 belong to domain 2.

Therefore, only the information from subcontrol
units 3 and 5 are available on the main control
unit.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 42 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
5.7 Reading out the SecoNET Configuration
Reading out the network configuration can take quite a lot of time especially once the network has
reached a certain size. Current progress is not displayed, as progress displayed would only be able
to make a very rough estimate.

It is only possible to read out the configuration of the entire network. It is not possible to only read
out certain parts of a network.

However, it is possible to read out just the topology of the SecoNET network. This will shorten the
search for connection faults. It is not always necessary to read out the entire network information, in
order to see whether or not it was possible to establish a connection between 2 nodes.

5.8 Uploading the SecoNET Configuration

5.8.1 Software up to version 5.0.x

As when the configuration data is being read out, it is also only possible to upload the entire
network during the upload process. The partial upload of configuration data is not supported, as
alterations to a single Node have an effect on the configuration data of the entire network, and the
entire network therefore must be reconfigured.

Network configuration files can only be uploaded, when no individual network element
indicates that there are faults in the configuration data!!! (See also point 6.4.)

5.8.1 Software from version 5.1.x

The reading out and uploading of configuration data is only possible, if the entire network is not in
operation. Partial uploads of the configuration data is now supported. Using the configuration data
contained in a saved file, the data of other control panels can be updated at a later point, for those
control panels that were not available at the time (e.g. in the case of expansion of the number of
control panels).

Partial commission or extension of the number of control panels is no possible without the
network being fully readable (see also point 6.2). It should be ensured that when extending
control panels in the network, that both neighbouring control panels must be operational.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 43 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.0 Commissioning a SecoNET network
Since the commissioning of a complex network with all the control panels is very difficult, one
possibility fort he process for commissioning has been described below.

6.1 Preparations
A graphical depiction of the complete network should be available. Based on this graphical
depiction, the number of Nodes in the entire network, as well as the number of nodes in the
individual sub-networks can be determined.
For every control panel an unambiguous label should have been assigned both for the programming
(project name) as well as for the Client (control panel) in the SecoNET network.
2 adapter cables for converting a 15 pin to a 9 pin Sub-D connection and a 9 pin to a 15 pin Sub-D
connection should also be at the ready. Using these cables it is possible to link the interfaces for
testing purposes.

6.2 Partial Commissioning

First of all an attempt should be made to configure the main Subnet. As a result it is possible to tell
whether all the control panels in this subnet have a connection. By expanding the network by
several Subnets, the configuration in the individual control panels on their communications card
will be overwritten. It should be noted that network data can only be written, when there is no red
cross appearing on the display in the Network View. If when writing the data a fault which has been
overlooked is detected, then the writing process is automatically interrupted and the defined
network data is lost. For this reason, prior to writing the network data, they should be saved as a
file on the Computers hard drive.

From version 5.1 of the software, there are special options available regarding the possibilities for
extending the network.

Saving the network configuration as a file in XML file format.

Configuration of parts of the whole network, if not all Subnets are operational.

Extended a network using the available saved network data file on the PC

Writing modified Nodes

Updating network data manually (has to be carried out after every modified writing of a
Node, in order for the changes to be passed on to a main control unit or a management
system!)

Virtual configuration Nodes

PreviewNetwork Window

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 44 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.2.1 Example 1 - Subnet - Extension
The initial situation is that there is a Subnet (NO. 10) with a main control unit (UZ 2) and a
subcontrol unit (UZ 4), with all control panels in the Subnet being reachable. A service interface has
been chosen as the communications interface with the PC (instead of SecoLOG). The network is
read and configured, and before the data are written to the EEPROMs, they are saved as a file on
the PC.

Basic configuration

Extension by one control panel

* open the saved SecoNET Network file in the "NetworkView" window
* Click on topology in the "PreviewNetwork" window (topology of the network is read and then
for the current Subnet)

synchronise

New Control Panel

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 45 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
Changing the current parameters

Write modified network data

Then update the network data

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 46 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.2.2 Example 2 - Subnet - Extension
The initial situation is that there is a Subnet (No. 1) with a main control unit (UZ 254), three
subcontrol units (UZ 3, UZ 6, UZ 2) and a configuration node. This arrangement should be
increased by a further subcontrol unit (UZ 7), with subcontrol unit 2 of the Subnet not being
available at this time.

A service interface (instead of SecoLOG on the main control unit) and a service interface on the
configuration Node (BMZ Integral with USI-4 module and special programming) are selected to act
as the communications interface with the PC.

UZ 6 UZ 7
Node 6 Node 7
Node ID 315439 Node ID 315412
B4 control panel B4 control panel

UZ 2
Node 2 SubNET 1
Node ID 315437 UZ 3
B4 control panel Node 3
Node ID 315412
B4 control panel

Service PC 1 UZ as virtual Node

PC (Service)

Main Control Panel:

UZ 254
------------------------
Node 4
Node ID 315426
Service Assistant
------------------------
Node 5
Node ID 315426
Main Control Panel

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 47 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
UZ 7 has been added in the following picture.

UZ 6
Node 6
Node ID 315439
B4 control panel

UZ 7
Node 7
Node ID 315412
B4 control panel

UZ 2
Node 2 Subnet 1
Node ID 315437 UZ 3
B4 control panel Node 3
Node ID 315412
B4 control panel

Service PC 1
UZ as virtual PC (Service)
Node

Main control panel:

UZ 254
------------------------
Node 4
Node ID 315426
Service Assistant
------------------------
Node 5
Node ID 315426
Main control panel

The individual steps of the configuration process can be seen in the illustrations that follow.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 48 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
Loading the original network file prior to extending the network

Reading the control panel to be added in the "PreviewNetwork" window

Synchronisation of the control panel to be added

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 49 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
Assigning the Node and Subcontrol unit address

Writing modified Nodes

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 50 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
Configuration complete

Before the new configuration can be saved, the entire network should once again be read and the
network data then updated.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 51 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.2.3 Making a Network smaller
The initial situation is that there is a Subnet (No. 1) with a main control unit (UZ 254), four
subcontrol units (UZ 3, UZ 6, UZ 2 and UZ 7) and a configuration node. A subcontrol unit (ZU 7)
should be removed.

UZ 6 UZ 7
Node 6 Node 7
Node ID 315439 Node ID 315412
B4 control panel B4 control panel

UZ 2
Node 2 Subnet 1
Node ID 315437 UZ 3
B4 control panel Node 3
Node ID 315412
B4 control panel

Service PC 1
UZ as virtual PC (Service)
Node

Main control panel:

UZ 254
------------------------
Node 4
Node ID 315426
Service Assistant
------------------------
Node 5
Node ID 315426
Main control panel

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 52 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1

1. Open the saved file for the entire network in the Network window.

2. Read the network topology in the "PreviewNetwork window with the control panel removed

3. Mark the control panel (by right clicking with the mouse) and remove it in the network Network
window

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 53 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.3 Virtual Configuration Node
The virtual configuration node is a control panel in its own right, which is not, however, displayed
in the network, and can therefore be added in any position in the Subnet. Consequently
configuration interfaces can be dispensed with. However the technician must have a portable BMZ
Integral at his disposal for this.

A special programming of the BMZ Integral is necessary for this.

The configuration node parameter must be marked.

This parameter can only be marked if at least one
interface has been programmed to ISP protocol.

6.4 Complete Commissioning

Only once all Subnets work without any problems, should the complete configuration (fine tuning
=> domains etc.) be carried out. Main control units and SecoLOG systems should then have already
been connected. Then a system test can be started.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 54 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.5 Testing and Fault finding

6.5.1 Reading the Topology

The "Read topology" function makes it easier to find communications faults. Only once the
topology has been checked should the normal reading process be commenced. Based on the Nodes
which are displayed, it is possible to check whether all devices are detected.
On the basis of data received from Port 0 and Port 1 it is possible to establish which communication
is faulty.

In this example you can see that

from Port 0 0A both the "x" and
the "y" cables and from Port 0 0B
both the "x"- and the "y" cables are
in full working order.

In this example you can see that

from Port 1 1A both the "x" and
the "y" cables and from Port 1 1B
both the "x"- and the "y" cables are
in full working order.

In this example a BMZ Integral C which is connected to

the SecoNET as a stub line is the problem. Only one
interface is used for this reason.

When reading in the topology, a wire break is displayed in

this instance.. Using the parameter setting it is possible to
inform the configuration that the "wire break" is an
intentional one. The "EOL" symbol (End of line) will then
appear in the configuration.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 55 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.5.2 Network Error Messages
Node Ghost: Node ID
If this message appears in the Network view, then several control panels have the same NodeID.
When reading in the network structure, different network structures can be displayed as a
consequence!

N3-Connection
This message indicates that there is a cable connection fault at the main control unit. The fault is
indicated in the form of a Subnet number, Node and a general Client number.

Subcontrol unit / Connection Fault

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 56 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
Network Fault
By each Integral there are two network error messages which can be displayed. One fault
message comes from the interface "xA" and the other from interface "xB". The shown network
number incluted the subnet-, node-and port adress number from the own central.

Example of a readed configuration with the network error numbers:

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

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

SubNet.Node.Port Net no.

SPT 0 1 2 => 19
5 = 0B (lPC)
GUE 0 = 0A (loop)

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

Subnet 0
4 = PC

SubNet.Node.Port Net no.

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)

SubNet.Node.Port Net no.

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

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 57 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.5.3 Error Message from virtual configuration nodes
If the SecoNET Connection Protocol is used instead of the SecoNET Repeater Protocol, then the
configuration node control panel will always indicate a SecoNET configuration fault.

Example:

MODAKT 980/20 Module active side

980 subcontrol unit 4, SPI device 13 (Slot 8),
20 Seconet configuration fault,
Fault in the SecoNET main control unit
(Solution: Configure SecoNET with the current
Network Assistant)
TZ: 4 Module: 8-3 subcontrol unit (not Seconet control panel no.) 4
Connection slot 8
SECONET KONFIG NOK SecoNET configuration fault

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 58 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.5.4 Fault arising from insufficient RAM on communications cards
The examples refer to the SecoNET network as shown in point 6.2.2
When the SecoNET link protocol and the remote access protocol are simultaneously activated, prior
to the configuration file being loaded into the control panel the following query is carried out by
Winloader:

If the response to the query is Yes and the RAM is less than 1 Mb, then the configuration will still
be uploaded into the control panel.

After the control panel has been started up, then the following error messages will appear on the
control panel.

Display Fault Display Fault

Fault during SW Failure of passive half
download Application fault 3
(RAM of the SPI
device is too small )

Failure of passive half Failure of passive half

Application fault 4

Failure of passive half Failure of passive half

Application fault 1 Application fault 5

Failure of active half

Application fault 2

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 59 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.5.5 Error messages on the main control unit

Display Error

Connection in Subnet 1, Node 2, Interface 0A (Port 0)

Connection of Subnet 1, Node 2, Node direct, Interface 0A to
Subnet 1, Node 2, Node direct

Connection in Subnet 1, Node 6, Interface 0A (Port 0)

Connection of Subnet 1, Node 2, Node direct, Interface 0A to
Subnet 1, Node 2, Node direct

Connection fault at both interfaces

6.5.6 Error messages on the sub control unit

Display Error
Network 2, connection sub net 0, node 0, interface 1A (Port
number = 1 + 1 = 2 to sub net 0, node 2

No connection to main central 1

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 60 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.5.7 Error messages on the centrals with 2 sub networks
1) Configuration => 1 Main central, 3 sub centrals and 2 sub networks

B6 C08 central 7 SW614

B5 Pinguin C01 SW614

5 = 0A (PC)

1 = 1A(loop) 0 = 0A (loop)

2 = 0B (loop)
SPT 5 = 0B (lPC)
GUE
4 = PC

3 = 1B(loop)
Sub net 7

Break connection, line "X" AND "Y

0 = 0A (8225)
A0/B0 programmed as SecoNET REPEATER => Node 2 in sub net 7
A1/B1 programmed as SecoNET LINK => Node 2 in sub net 8
Remark: by the example I have used in sub net 7 and 8 the same node no. for this 1 = 1A (loop)
board

2 = 0B (8227)
Main central Sub net 8
0 = 0A (loop)
0 = 0A (loop)
3 = 1B (loop)

1 = 1A (loop)

4 = PC card
modem
2 = 0B (loop)

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

Pinguin C07 z15 HighEnd

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 61 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
2.) Faultmessage table (example all lines => x and y

Network no. / Main central no. from To

8227 08.02.07/0B 08.07.07

8225 08.02.07/0A 08.04.07

7202 07.02.07/1A 07.01.07

7204 07.02.07/1B 07.00.07

Main central 1 Fault connection

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 62 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.6 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

SubNet.Node.Port Net no.

SPT 0 1 2 => 19
5 = 0B (lPC)
GUE 0 = 0A (loop)

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

Sub net 0
4 = PC

SubNet.Node.Port Net no.

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)

SubNet.Node.Port Net no.

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

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 63 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
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

6.6.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

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 64 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
6.6.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 !!!

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 65 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
7.0 Training Examples
The training examples are intended to explain the connection and functions of a sample SecoNET
network. In order to be able to depict examples that are as close to situations arising in practice
during commissioning, the following examples have been chosen.

7.1 Example 1 (Software Version pre 5.1)

The network consists of five Subnets. Of those, two are stub lines.

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
(MainNet)
LTS

BMZ 5 BMZ 3
Integral C Integral

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 66 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
7.1.1 Network Configuration
The following illustration shows the listing of a SecoNET network on the service PC. The
connecting lines show the connections of the routers from one Subnet to another. They are,
however, not shown in the same way as on the illustration on the PC.

Graphic depiction of a
Subnet loop

Node with Client

(Node 1 from Subnet 1)

Depiction of the Client

Graphical depiction of a
Router

Graphical depiction of a
RouterNode with Client

Graphical depiction of a
Maxnet Subnet

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.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 67 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
7.2 Example 2 (Software Version pre 5.1)
SecoNET Network with 11 control panels, 5 Subnets and a Service PC connection.

Subnet 5
(LINE)

BMZ 10 BMZ 1 N3 BMZ 2 N3 BMZ 7

Integral C Integral
Subnet 4
Integral Subnet 3 Integral C

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
BMZ 4
BMZ Integral unit 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_1-en.doc Version V 1.9 Page 68 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
7.2.1 Control Panel Configuration (only network cards)
A sample table for the connection of individual control panels in a SecoNET network.

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 x

1 INTEGRAL BMZ 9 B3-USI4

B3-USI4 to B0 BMZ 9 to A0 BMZ 9 - -

C C

INTEGRAL C B4-USI4 to B0 BMZ 9 to A0 BMZ 9 - -

1 INTEGRAL C BMZ 5 B4-USI4

1 INTEGRAL C BMZ 6 B4-USI4

2 MAXIMA UZ1

3 INTEGRAL C BMZ 7 B4-USI4

4 INTEGRAL BMZ 2 B3-USI4

5 INTEGRAL BMZ 1 B3-USI4

5 INTEGRAL C BMZ 10 B4-USI4

B3-LPI modules can also be used for communications between the Integral control panels.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 69 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
7.2.2 Network Structure
Description as per point 7.1.1.

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 70 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009
SecoNET - Technicians Part 1
15.0 List of Document Versions

VERSION DATE INFORMATION ABOUT CHANGES MADE

P 0.0 25.04.2001 Unofficial internal version for information purposes
P 0.1 21.12.2001 Extension of the internal version for information purposes
V 1.0 07.01.2002 First preliminary edition
V 1.1 18.01.2002 Extended preliminary edition
V 1.2 26.01.2002 First official edition
V 1.3 01.03.2002 Extended edition => Chapter 6
V 1.4 05.11.2002 Extension of point 1.1 Safety tips for servicing and maintenance
V 1.5 10.03.2005 Points 1.4, 2.2, 2.4, 4, 5.5, 5.6, 6.2, 6.3 appended
V1.6 13.04.2005 TimeMasterPriority appended
V1.7 09.06.2005 Chapter 4 (Note), 4.2 tables and chapter 6.5 appended
V1.8 08.02.2006 5.8 adapted and extended; 6.2, 6.2.2 extended; 6.5.3 Error Message
for Virtual Configuration Nodes
V1.9 30.02.2009 6.5.2 Advanced, 6.5.6 new, 6.5.7 new

Ing.
Gnter
Porcher
Austria,
Vienna
2009.07.3
0 16:04:09
+02'00'

File name: SecoNET_tech_1-en.doc Version V 1.9 Page 71 (71)

Doc. No. SPT/02:SecoNET_tech_1 SPT/G. Porcher 27.07.2009