Section Commissioning

SECURITON SecuriPro® FAS T 137 807 E 1 / 121
 Copyright by Securiton
Technical Documentation Version Date Ind. Mod. No. Initials Approved
Version: EN 54 First issue 13.01.98 --- Ku / gsa ESD / bb
Applicability: Global Current 24.10.01 c bb / ksa Print
Chapter 7 Commissioning Ref. Doc. T 137 801 to T 137 807 Securiton / ksa
®
Structure of the technical documentation SecuriPro FAS T 137 801E to T 137 807E
®
The present technical documentation SecuriPro FAS is divided into 7 chapters. Each of these chapters consists
of a document numbered from T 137 801E for Chapter 1 General to T 137 807E for Chapter 7 Commissioning.
The documentation is subject to the change procedure, and the respective valid and current edition of the indivi-
dual document is indicated in the overall contents, Chapter 1 General, and in the respective document header with
an index. The respective current version can, if required, be requested from the manufacturer.
Information: T 137 807cE

is valid for the following software versions
The following documentation is valid for the following software versions, also see Section
7.2 Software compatibility.
ê SecuriWin Release Version: 01.03.00.004

(Deviations in procedure compared with R 01.04.00 are described separately in the corre-
sponding chapter.)
ê SecuriWin Release Version: 01.04.00.xxx, including
®
ê SecuriLine SecuriLine Diagnosis
®
ê SecuriLan Installation Tool
ê SecuriWin Big Map
ê SecuriWin Rev Moni
ê SecuriWin System Limit Checker
Contents Page
7 Commissioning.................................................................................. 6
7.1 General aspects of commissioning of the SecuriPro® system ..................................... 6
7.2 Current software versions for present documentation ................................................. 6
7.2.1 Software compatibility...............................................................................................................6
®
7.3 Preparation of the SecuriPro commissioning tools / software ................................... 7
7.3.1 Laptop requirements .................................................................................................................7
®
7.3.2 SecuriLine Panel and accessories (only for CH)...................................................................7
7.3.3 SecuriLine Tester STB01...........................................................................................................7
®
7.3.4 SecuriLine Monitor and accessories......................................................................................8
®
7.3.5 SLTA for SecuriLan and accessories .....................................................................................8
7.3.6 Various accessories...................................................................................................................8
7.3.7 SecuriWin software....................................................................................................................9
7.3.8 Installation of SecuriWin software ...........................................................................................9
7.3.9 Additional requirements ............................................................................................................9
7.3.10 Danger information relating to commissioning ......................................................................9
SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

®
2 / 121 SecuriPro FAS T 137 807 c E
7.4 Control values for the installation ................................................................................ 10

®
7.4.1 Preparation of the installation for commissioning of the SecuriPro system .................. 10
7.5 Commissioning or reading in the SecuriLine with the SecuriLine Panel Analysis ... 11
7.5.1 Introduction.............................................................................................................................. 11
Start screen of the Panel Analysis software ..................................................................................... 11
7.5.3 Commissioning of line (Panel Analysis) ............................................................................... 12
7.5.3.1 Commissioning with the Panel and the connecting cable SAK 91 ...................................................12
7.5.3.2 Commissioning with the SecuriLine Monitor via SCB 01/01A ..........................................................12
7.5.3.3 Start up line from terminal A .............................................................................................................13
7.5.3.4 Start up Line from terminal B............................................................................................................14
7.5.3.5 Start up Line only partially ................................................................................................................15
7.5.4 Line polling with the Panel ..................................................................................................... 15
7.5.5 Read out data from a detector EEPROM ............................................................................... 16
7.5.6 Troubleshooting ...................................................................................................................... 17
7.5.7 Send telegram manually ......................................................................................................... 19
7.5.7.1 LED control of the detectors .............................................................................................................19
7.5.7.2 Closing (opening) the stick in the SCU 81........................................................................................19
7.5.7.3 Reprogramming an SDI....................................................................................................................19
7.5.7.4 Resetting the priority data of a module.............................................................................................20
7.5.7.5 Controlling the COM 81 output .........................................................................................................20
7.5.7.6 Controlling the SOM 81 outputs .......................................................................................................20
7.5.7.7 Controlling the ROM 81 outputs .......................................................................................................20
7.5.7.8 Controlling the IOM 81 outputs.........................................................................................................20
7.5.7.9 Controlling the SDI 81/82 output ......................................................................................................20
7.5.7.10 Controlling the MDI 81/82 outputs ....................................................................................................20
7.5.7.11 Controlling the OCM 81 outputs .......................................................................................................20
7.5.7.12 Switching from digital to analogue status of the smoke channel in the SSD 530.............................20
7.5.7.13 Switching from digital to analogue status of the temperature channel in the UTD 530 ....................21
7.5.8 Addressing and polling in the control window .................................................................... 21
7.5.9 Priority data.............................................................................................................................. 21
7.5.10 List of priority data of all Line participants........................................................................... 21
7.5.11 HEX - binary conversion table for the priority data.............................................................. 24
7.5.12 Send telegrams as plain text .................................................................................................. 25
7.5.13 Create project file for importing the Line assignment (Panel Project)............................... 26
7.6 Preparation for commissioning of SecuriLAN (all devices) and MCB 02/02A ........... 28
7.6.1 SecuriLAN terminal assignment ............................................................................................ 28
7.6.2 Termination of the SecuriLAN................................................................................................ 28
7.6.2.1 Termination with 105 Ω resistor (not compliant with EN 54) ............................................................28
7.6.2.2 Termination with LCB 02 (according to EN 54) ................................................................................30
7.6.3 Preparation of the MCB 02/02A : ............................................................................................ 32
7.6.3.1 Visual inspection of the MCB 02/02A ...............................................................................................33
7.6.3.2 Equipping the IC for MCB 02/02A ....................................................................................................33

®
T 137 807 c E SecuriPro FAS 3 / 121
7.6.4 SCB 01/01A ...............................................................................................................................35

7.6.4.1 Mount SCB01/01A ........................................................................................................................... 35
7.6.4.2 Change SCB 01A to SCB 01 ........................................................................................................... 36
7.6.5 EDB 03 for line-monitored emergency alarm path (R 01.03.00.004 and R 01.04.00)..........36
7.6.5.1 EDB 03 connection .......................................................................................................................... 36
7.6.5.2 EDB 03 as replacement for EDB 01 / 02 ......................................................................................... 37
7.6.5.3 Programming emergency alarm path in SecuriWin ......................................................................... 37
7.6.5.4 Testing of emergency alarm path .................................................................................................... 38
7.6.6 Binding, download or startup? ...............................................................................................39
7.7 Functions and indicators on the MCB 02/02A.............................................................. 40
7.7.1 Mode switch and mode indicator ...........................................................................................40
7.7.2 7-Segment display....................................................................................................................40
7.7.3 Baud switch ..............................................................................................................................41
7.7.4 Errors at the comissioning......................................................................................................42
7.8 Start up MCU manually (with mode switch) ................................................................. 43
7.8.1 Startup in local mode...............................................................................................................43
7.8.2 Startup in "Global mode" ........................................................................................................44
7.8.3 Changing from global to local mode......................................................................................45
7.8.4 Indication of int. errors via 7-segment display and baud switch on MCB 02/02A.............46
7.8.4.1 Program error indication .................................................................................................................. 46
7.8.4.2 System error "H" .............................................................................................................................. 47
7.8.4.3 Overview of errors:........................................................................................................................... 47
7.8.4.4 Inherited errors "U" .......................................................................................................................... 47
7.8.4.5 Overview of the task errors .............................................................................................................. 48
7.8.4.6 Task errors 'L' .................................................................................................................................. 48
7.8.5 Error during start-up or during operation..............................................................................50
7.9 SecuriLine Tracer ........................................................................................................... 54
7.9.1 Introduction ..............................................................................................................................54
7.9.2 Starting up the SecuriLine Tracer ..........................................................................................54
7.9.3 Line Profile................................................................................................................................56
7.9.4 Load bin file ..............................................................................................................................56
7.9.5 View HEX data in plain text .....................................................................................................56
7.9.6 Saving a log file ........................................................................................................................56
7.9.7 Recording all telegrams...........................................................................................................57
7.9.8 Triggering on an individual address ......................................................................................57
7.9.9 Timeout .....................................................................................................................................57
7.9.10 BiPhase .....................................................................................................................................58
7.9.11 Addressing and initialization ..................................................................................................58
7.9.12 Slave type list ...........................................................................................................................59

®
7.10 SecuriLan installation .................................................................................................. 60

7.10.1 Introduction.............................................................................................................................. 60
7.10.2 Setting the baud rate of the SLTA.......................................................................................... 60
7.10.2.1 Setting for the SLTA 10 ....................................................................................................................61
7.10.2.2 Settings for the SLTA 2 ....................................................................................................................61
7.10.3 Start screen of the installation software ............................................................................... 62
7.10.4 Meaning of the icons used ..................................................................................................... 63
7.10.5 General settings/information on menu bar........................................................................... 64
7.10.5.1 Popup menu .....................................................................................................................................64
7.10.5.2 Quick Info .........................................................................................................................................64
7.10.5.3 Properties .........................................................................................................................................65
7.10.5.4 SLTA interface..................................................................................................................................65
7.10.5.5 Path ..................................................................................................................................................65
7.10.6 Binding ..................................................................................................................................... 66
7.10.6.1 Online Auto Binding..........................................................................................................................75
7.10.7 Unbinding ................................................................................................................................. 77
7.10.7.1 Online Auto Unbinding......................................................................................................................77
7.10.8 Rebinding in the case of LAN device or software replacement.......................................... 80
7.11 Download........................................................................................................................ 87
7.12 Startup from PC (installation tool) ................................................................................ 93
7.12.1 Introduction.............................................................................................................................. 93
7.12.2 Start screen of the installation tool for startup from PC ..................................................... 93
7.12.3 Icons used ................................................................................................................................ 93
7.12.4 Starting up the system in the global mode ........................................................................... 94
7.12.5 Starting up the system in the local mode ............................................................................. 96
7.12.6 Error indications on startup from PC .................................................................................... 98
7.13 Big Map ......................................................................................................................... 100
7.13.1 Introduction............................................................................................................................ 100
7.13.2 Start screen of Big Map ........................................................................................................ 100
7.13.3 Big Map operation ................................................................................................................. 100
7.14 RevMoni and RadioView (one-man detector tester) .................................................. 104
7.14.1 Introduction............................................................................................................................ 104
7.14.2 Description of the devices.................................................................................................... 104
7.14.2.1 PC with two serial ports ..................................................................................................................104
7.14.2.2 EGSTON mains adapter.................................................................................................................104
7.14.2.3 Radio modem FM 2 ........................................................................................................................105
7.14.2.4 Radio View .....................................................................................................................................105
7.14.2.5 Transceivers ...................................................................................................................................106

®
7.14.3 Connection of the devices ....................................................................................................107

7.14.3.1 Connect radio set and Radio View................................................................................................. 107
7.14.3.2 Connect radio set and radio modem to PC.................................................................................... 107
7.14.3.3 Connection of SLTA to PC ............................................................................................................. 108
7.14.4 Start screen (available windows during revision) ..............................................................108
7.14.5 Operation of the RevMoni .....................................................................................................109
7.14.5.1 Overview ........................................................................................................................................ 109
7.14.5.2 Create new revision project ........................................................................................................... 110
7.14.5.3 Opening an existing revision project .............................................................................................. 112
7.14.5.4 Starting the revision recording ....................................................................................................... 113
7.14.5.5 Switch detectors / zones to revision............................................................................................... 114
7.14.5.6 Control window of RadioView on the PC ....................................................................................... 115
7.14.5.7 Problems and Alert window............................................................................................................ 116
7.14.5.8 Debug window of RadioView on the PC (help tool) ....................................................................... 117
7.14.6 Print revision report ...............................................................................................................118
7.14.6.1 SecuriPro Logger (help tool) .......................................................................................................... 119
7.15 Abbreviations ............................................................................................................... 120
7.16 List of Figures .............................................................................................................. 121

®
7 Commissioning
7.1 General aspects of commissioning of the SecuriPro® system
®
The commissioning of the SecuriPro system includes the installation checks, the device configuration of
® ®
the SecuriLine according to the project specifications, the binding of the SecuriLan devices according
to the project specifications, the loading of the SecuriWin system software, startup of the system and te-
sting of the functions.
Suitable aids and tools whose application and use are described in the following sections of the present
documentation are available for commissioning.
®
The special devices of the commissioning set are required for commissioning a SecuriPro system.
® ®
• SecuriLine Monitor = Test and analysis tool for the SecuriLine
®
• SLTA (Lon-Talk Adapter) SecuriLan interface
In addition, the following aids are required for commissioning and are not part of the commissioning set:
® ®
• SecuriLine Panel or SecuriLine Tester STB01 = Commissioning tool for the SecuriLine
• RevMoni = Tool for one-man maintenance of the system with or without radio (not included in the
commissioning set; separate case tailored to the respective radio model).
• SecuriWin software with the system data
® ®
êSecuriLine Diagnosis tool (SecuriLine Tracer / Panel Analysis / Panel Project)
®
êSecuriLan Installation Tool
êBig Map
êRev Moni
• Laptop PC (Specifications see 7.3.1 Laptop requirements.
7.2 Current software versions for present documentation
Danger information
®
The software used for commissioning the SecuriPro systems is constantly being ad-
apted to the requirements and knowledge from practical experience. Consequently, the
present technical documentation T 137 807cE Issue 24.10.01 is binding only for the
following software versions.
7.2.1 Software compatibility
Release 01.03.00.004 Release 01.04.00.xxx

• SecuriWin R 01.03.00.004, including • SecuriWin R 01.04.00.xxx, including
• SecuriLine Diagnosis • SecuriLine Diagnosis
• Installations tool • Installations tool
• Big Map • Big Map
• Rev Moni • Rev Moni
• SystemLimit Checker • SystemLimit Checker
according to the software compatibility list according to the software compatibility list
T 139 238E T 139 284E
Information
With each software update, marked changes may occur in the operation and function
of the software. In this case, the technical documentation T 137 807E is replaced by a
current issue (date on 1st page and index from 2nd page).
Valid for software version V: 01.03.00.004 and V: 01.04.00.xxx, according to Section
7.2.

®
7.3 Preparation of the SecuriPro® commissioning tools / software

The following aids are required for commissioning.
7.3.1 Laptop requirements
• Min. Pentium II Processor, 266 MHz

• Min. 64 MB RAM (128 MB recommended)
• 100 MB free hard disk space
• Windows 95B, 98 SE or NT4.0 (Service pack 6)
• 2 serial ports
• 3.5" floppy disk drive
• CD-ROM drive
• Mouse
• 1 Standard printer installed
Fig. 1Laptop
®
7.3.2 SecuriLine Panel and accessories (only for CH)
®
The Panel is used for checking the SecuriLine installa-
tion, for testing for correct consecutive numbering of the
®
SecuriLine devices, for reading in the line assignment
and for testing the functions. The MCU 211 need not be
in operation. The Panel may be used only where no
CE test need be present for the device.
®
• SecuriLine connecting cable to Panel
Connecting cable with adapter board for connection of Mains cable to
®
the SecuriLine installation ring and 2 x 4 terminals for SecuriLine Panel Panel with CH
the Panel connection. plug
• 2 mains cables to Panel
230 VAC mains cable with Panel plug and CH plug
SecuriLine
connecting cable SAK 91
®
Fig. 2 SecuriLine Panel and accessories
7.3.3 SecuriLine Tester STB01
The SecuriLine Tester STB01 (not shown) is available
as an option in the commissioning set. The description
of the handling is included with the device and the
handling is not described in this document.

®
®
7.3.4 SecuriLine Monitor and accessories
The monitor is an interface adapter between the Securi-
®
Line in operation and a PC. Together with the SecuriLi-
®
ne Diagnosis tool, the detector addresses, detector and
module statuses and the priority data during normal ope-
ration can be recorded and saved by means of a PC, for
SECURILINE
analyzing a malfunction. For this purpose, however, the MONITOR
®
SecuriPro system must be completely in operation with
all software and customer data. Flat cable
With the monitor, the line assignment can be read in via SCB to Monitor
the SCB 01 /01A as with the Panel. For this purpose,
however, the MCB 02/02A must be connected.
®
• Flat cable SCB to monitor Fig. 3 SecuriLine Monitor and accessories
10-pin grey flat cable with plug, as connection between
®
debug interface SCB 01/01A and SecuriLine Monitor.
®
7.3.5 SLTA for SecuriLan and accessories
The Serial Lon-Talk Adapter SLTA from Echelon is used
®
for commissioning the SecuriLan .
Any SLTA present must be configured for the Securi-
® ®
Lan application, according to the SecuriPro manufac-
turer's data.
Ordering information:
- SLTA 10 MIP Mode, Model 73351 for FTT10; (repla- SLTA
cement model for SLTA/2); AC adapter Model 78020

(Europe)
- SLTA / 2, Model 73000, Network TP/FT-10 incl. AC
Cable with
adapter (only available in limited quantities) SecuriLan RJ 45
®
Supplier: ECHELON Corp. or from SecuriPro manu- Adapter plug
MCB to SLTA
facturer.
®
• SecuriLan Adapter
Fig. 4 SLTA and accessories
The adapter permits the connection of the SLTA to
®
the SecuriLan . Required for commissioning the Se-
®
curiLan .
• Cable with RJ45 plugs
Cable with RJ45 plugs as connection between Secu-
®
riLan adapter and SLTA.
7.3.6 Various accessories
• PC interface cable to monitor, Panel or SLTA

Standard 9-pin interface cable for alternative connec-
tion between PC and commissioning devices.
• SEA and DOM keys
®
Two standard SecuriPro keys for the indication and
control maps according to region of use.
Keys
SEA and DOM
PC-Interface cable for
Monitor / Panel or SLTA
Fig. 5 Various accessories

®
7.3.7 SecuriWin software

The SecuriWin software packet includes the system
planning, programming, commissioning, testing and
®
checking software for the SecuriPro systems.
Se
Information
n
The respective current release/version
cu i
ri W
of the SecuriWin software and the up-
grade are continuously made available
to the known users by the manufacturer
®
of the SecuriPro system.
Fig. 6 SecuriWin software on CD-ROM
7.3.8 Installation of SecuriWin software

From CD:
1. Insert CD in drive
2. Select CD drive
3. Open the following path by double clicking in each case:
ê ...\SecuriWin\ R010400\Setup.exe
4. Double click on "Setup.exe". The Setup program is automatically started. Various settings, such as
language of the SecuriWin and Com port, must be selected.
Information
So that the setup in english, french and italian works perfect, a standard printer must
be installed on the PC.
5. At the end of the setup, the following message appears: "SecuriWin has been successfully installed".
The PC may have to be rebooted.
Contents of the CD:
The contents of the CD differ depending on the unit sold
7.3.9 Additional requirements
• System software (customer data created with SecuriWin)

• Planning documents
®
• Technical documentation for SecuriPro
• Measuring device (V-A-Ω)
• Detector testers (test gas)
7.3.10 Danger information relating to commissioning
Danger information
During commissioning, the respective valid country-specific regulations and guidelines
must be noted and complied with.
The system components must be treated in an EMC-compatible manner
Furthermore, suitable measures must be taken to prevent unintentional actuation of fi-
re control installations, alarm media, extinguishing systems, etc.

®
7.4 Control values for the installation

®
SecuriLine
®
Owing to the FET in the SecuriLine modules and detectors, complete checking of the installation is pos-
®
sible only with the SecuriLine Diagnosis Tool. However, a prior control measurement of the GND line
makes it possible to check the maximum permitted line length. Also see Chapter 6 "Installation".
®
SecuriLan
Prior checking of the LON installation is possible only if the cable (wires) are connected by means of the
terminals of the participants. However, the terminals of the participants must be separated (pluggable
terminals).
® ®
Permitted line resistances in SecuriLine and SecuriLan
(1) (2) (3)

® ® ®
SecuriLine GND line SecuriLan LON 1 or 2 SecuriLan LON 1 or 2
Wire diameter Terminal U to Y Terminal E to F or N to O Terminal E to earth or N to
(SCB 01/01A). The termi- (MCB 02/02A). earth (MCB 02).
nals should be separated The terminals should be dis- The terminals should be dis-
from the SCB 01/01A before connected from all boards connected from all boards
the measurement before measurement, an before the measurement, an
ohmmeter is connected in ohmmeter is connected to
place of end-of-line resistor earth in place of an end-of-
1. line resistor.
0.6 mm Ø max. 70 Ω max. 245 Ω > 10 M Ω
0.8 mm Ø max. 60 Ω max. 225 Ω > 10 M Ω
Reason for other values:

(1) Higher values = Wire diameter smaller than the permitted 0.6 mm
ê Line length greater than the permitted 1000 or 1500 m
(2) Higher values = Wire diameter smaller than the permitted 0.6 mm
ê End-of-line resistor 2 absent
ê Line length greater than the permitted 1000 or 1500 m
Value below 105 Ω = short-circuit
(3) Lower value = Earth fault
®
7.4.1 Preparation of the installation for commissioning of the SecuriPro system
® ® ®
All SecuriStar fire detectors should be inserted and SecuriLine and SecuriLan participants should be
connected.
The installation should comply with the technical documentation Chapter 6 Installation T 137 806E and
should be checked according to the documentation Commissioning T 137 807E, Section 7.4.
The preparation of the required tools and software is performed in accordance with Sections 7.1, 7.2 and
7.3, Commissioning T 137 807E
The commissioning and further preparation should be performed acccording to the documentation
Commissioning T 137 807E, Sections 7.5 to 7.14.

®
7.5 Commissioning or reading in the SecuriLine with the SecuriLine Panel Analysis
7.5.1 Introduction
The Panel Analysis is a component of the SecuriLine Diagnosis Tool and is used for testing the Securi-
®
Line completely for correctness of the consecutive numbering, and of slave types and for checking the
electrician's installation without the system being in operation. It is also possible to read in the as-
signment of the existing line and to import it in the project tool.
Furthermore, the RIL wiring, actuation connections and address verification by means of LED actuation
can be checked thereby.
A detailed online help (F1) on operation is available in the SecuriLine Diagnosis Tool.
7.5.2 Start screen of the Panel Analysis software
d C1
y
e f z r s t u
B1
m
n
o
p
v q
k
x
l
j
Legend:
B1) Read out EEPROM data o) Voltage of 3rd wire (Ub); only with SCB01A
C1) Basic settings for COM port p) Total line current (data)
d) Open / close Com port q) Total current of 3rd wire (I Ub); only with SCB01A
e) Basic settings r) Control commands
f) Reset Panel Analysis s) Sending the control commands
g) Startup parameters for Terminal A/(B) t) Number of slaves (A) found
h) Starting the addressing u) Number of slaves (B) found
j) Switching off the line voltage v) Sticks (if present)
k) Polling the priority data w) Total slaves found
l) Stop/start running application x) No further modules or open circuit
m) Line start voltage (line out) y) Commissioning of line
n) Line end voltage (line in) z) Create project file for line import

®
7.5.3 Commissioning of line (Panel Analysis)

The SecuriLine can be read in using the Panel and the connecting cable SAK 91 or using the SecuriLine
monitor (via SCB 01/01A).
The SecuriLine can be started up from terminal A (Line Out) or from terminal B (Line in). It is also possi-
ble to start up only a part of the line.
7.5.3.1 Commissioning with the Panel and the connecting cable SAK 91
The SecuriLine can be put into operation using the Panel and the connecting cable without it being ne-
cessary for the MCB to be connected.
Line control board with connecting cable SAK 91 and Panel (front):
LED
a
LED
a1
b b1
Fig. 7 Connections of Panel and SAK 91
c i1
a / a1) Line Out (brown, white, pink) c) Interface connection

b / b1) Line In (grey, yellow, green) i1) Reset switch
1. Disconnect terminals SCB 01/01A (Line 1)

2. Connect terminals to line control board SAK 91 (a+b)
3. Connect line connecting cable to Panel (a1+b1)
4. Connect interface cable to Panel and PC
5. Switch on Panel; press the reset switch (i1)
6. Continue according to Section 7.5.3.3 "Start up line from terminal A" and subsequent sections
7.5.3.2 Commissioning with the SecuriLine Monitor via SCB 01/01A

If the SecuriLine is read in using the SecuriLine Monitor via SCB 01/01A, the installation must be instal-
led completely according to Section 7.6 and the MCB 02/02A must be in operation (mode 0).
1. Connect interface cable to SecuriLine monitor and PC
2. Connect flat cable (10-pin) to SecuriLine monitor and debug interface SCB 01 or SCB 01A (debug
2) (see Section 7.6.4, Fig. 18 + Fig. 19)
3. Close dip-fix 2 (SCB 01) or DIL switch 2 (SCB 01A) or set to OFF
4. Actuate reset pin on SCB 01/01A and then reset pin on MCB 02/02A
5. Continue according to Section 7.5.3.3 "Start up line from terminal A" and subsequent sections

®
7.5.3.3 Start up line from terminal A
1. Start "SecuriLine Diagnosis" program
2. Open the interface using the "ComPort/Open Port" menu (d) or the button
3. In the "Settings/Number of Repeats" menu (e), the number of repeats can be (automatically) set in
the case of timeout. The default setting is 3.
4. Switch on the line voltage with "START LINE" (terminal A) and start addressing the line.
After the start of addressing, the version of the SCB01/01A is first read out. It then takes a few se-
conds before the first detector is polled:
Software version SCB 01

Line voltage off
Line voltage on
Type poll
Release poll
Addressing the module
Close gate (FET)
Poll voltage and
current values
Addressing of module
complete
5. If the message "Timeout" appears, there were 3 unsuccessful attempts to address the next mo-
dule:
ê Line is interrupted
ê Module is faulty or not connected
Information
Timeout is also reported if no further detectors are found on the SCU81. If in this case
the line is completely read in, the voltage "UB Line" is entered.
The FET of the last module addressed is opened (gate open). The tool automatically switches on
the voltage at terminal B and addresses the remaining line from the back (terminal B).
This makes it possible to localize the error on the line. The line is now addressed in the same way
as 2 sticks. The number of modules found so far per stick is shown in the window "Result/Ring A
(turquoise) (t) or Ring B"green (u).
If the number of modules found in the "Result/Total" (w) window does not agree with the planned
number, further errors are present on the line. To eliminate the error, see Section 7.5.5 Trou-
bleshooting and readdress line according to point 4.
Any sticks found are automatically addressed and are entered in the fields "Stick 1 - 15" (v).

®
6. The line is correctly addressed if no more detectors are shown in the green field "Ring B"
and the last address agrees with the number of planned detectors.
7. In the "Line-Values" window (m,n,o,p+q), the voltages at the start of the line (UA Line) and the total
voltage of the line (I Line) are continuously displayed. Voltage UB Line is entered only after addres-
sing of the ring or startup from terminal B.
The values UB and I UB (3rd wire) are available only with the SCB 01A.
Example:
UA Line [V]: 27.9 (Line Out)
UB Line [V]: 25. 2 (Line In)
UB [V]: 25.3 (3rd wire)
I Line [mA]: 90.7 (Total current Line Data)
I UB [mA]: 69.9 (Total current 3rd wire)
• The voltage UB Line may not fall below 19 V

• UB Line = 0.0 V ê Line is not connected
• UA and UB Line = 0.0 V ê Possible short-circuit on the Line
• Current I over 120mA: ê Current consumption of an element or
detector is too high
8. The ongoing application can be stopped by activating "STOP" (l) and can be started again with
"RESUME" (l).
9. The line voltage can be switched off with "LINE OFF"
10. Disconnect terminals "Line Out" (a) and "Line In" (b) from the line control board and connect to
the SCB 01 again.
Information
Important: Connect "Line Out" and "Line In" correctly!
11. Check Line 2; repeat steps 1 - 10
7.5.3.4 Start up Line from terminal B

In order to start up the Line from terminal B:
1. Repeat steps 1 – 3 of Section 7.5.3.3
2. Click on the button

The following window appears:

®
3. Enter the number of modules present on the line (0 = all)
4. Activate the function "Terminal B"
5. Close the window with "OK"
The button indicates that the line is being started up from terminal B.
6. Click on the "START LINE" button
The Line is read in from terminal B.
7.5.3.5 Start up Line only partially

To start up only a part of the line (terminal A or B):
1. Repeat steps 1 – 3 of Section 7.5.3.3
2. Click on the button

3. Enter the number of modules you wish to start up
4. Activate the function "Terminal A" or "Terminal B"
5. Close the window with "OK"
The button indicates that the Line is being partially started up from terminal A or from
terminal B.
6. Click on the "START LINE" button

The Line is read in from the chosen terminal.
7.5.4 Line polling with the Panel

After the Line has been addressed, it can also be polled using Panel Analysis. This mode is used in par-
ticular to make measurements on the faulty detector by inputting the trigger address (function available
only in SCB 01), for example in the case of bi-phase errors.
However, it is possible just to check the priority data of the line before starting up the system.
1. With "POLLING" (k), the priority data of the Line are polled (polling interval = 200 ms)
2. By inputting the address in the "Trigger/Address" window and transmitting with "SEND", the data of
an individual detector can be polled. This function is activated only with the SCB 01.
3. The pollling can be stopped or started again with "STOP" / "POLLING".

®
7.5.5 Read out data from a detector EEPROM

The EEPROM memory range from address 0 to 127 can be read out from one or more mdoules using
the menu option "Special Orders / Read EEPROM" and can be saved in a file.
1. Read in Line according to Section 7.5.3.3
2. Open menu option "Special Orders / Read EEPROM"
3. In the "Address(es)" field, enter the addresses of the detectors whose EEPROM data are to be
read out.
For successive modules, input the first and last line addresses (separated by a hyphen), e.g. 3-9.
Individual modules and whole ranges can also be combined, and the individual modules/ranges
must be separated by a comma, e.g. 1,4,6,9-20,56,66-69
Information
The data are read out byte by byte and reading out takes a few minutes for 127
detectors. It is therefore expedient to read out only the data of the detectors which
are required.
4. Click on the field "Save as File"

5. Input "Filename" for the log file
6. With "Transmit", reading out of the data is started.
The data are listed on the Panel screen:
7. With "Back", the wndow is closed again

®
7.5.6 Troubleshooting
• Timeout between PC - SCB:

✘ No connection between PC and SCB
ê Check whether all cables are connected
✘ No Panel supply
ê Switch on mains switch
✘ Com port is not open
ê Open port via menu "Com Port/Port open"
✘ SCB is not in Panel mode
ê Close dip-fix/DIL switch 3 and reset SCB and MCB
• Timeout:
✘ Next slave does not log on

ê FET output of last slave addressed does not close
ê FET input of the slave addressed does not close
ê Address the line from the back using "START LINE" (terminal B)
The slave now found last should be the one which could not be addressed previously.
✘ Last detector on a stick
✘ Open circuit on the Line

ê Detector not correctly mounted
ê Wire in terminal broken off
ê Insulation clamped under
ê Different wire diameters clamped together (loose connection)
ê Wires incorrectly connected (pole reversal)
ê Detector may be faulty; replace detector
• Short Line:
✘ Short circuit on Line (data) after the module last addressed; line voltage is switched off
ê Check wiring
ê Measure GND resistance
ê Measure data – GND resistance (terminals); if, for example, 300 kohm = creeping short-circuit
ê Eliminate error and address Line again
✘ Current I Data is > 140 mA

ê Current consumption on the Line is too high
ê Check to determine the detector after which the limit is exceeded
Check default of profile setting; wiring of e.g. SDI 82 is incorrect
• Short Supply:
✘ Line short-circuit (3rd wire) after module last addressed; line voltage is switched off
ê Check wiring
Eliminate error and address Line again

®
• Parallel wiring:
✘ 2 detectors are wired parallel
ê Check wiring
ê Eliminate error and address Line again
• Voltage cut-out after addressing:

✘ Current consumption on the Line is too high
ê Possibly in the case of several SDI 82 (MCP 530/535), input open planned (emergency alarm is
triggered by SDI)
ê Snap in MCP so that the Line can be read in/addressed; change wiring later.
ê Use MCP with production date from beginning of August 99
• Panel Analysis does not function:

✘ Check whether mains switch on Panel is switched on
✘ COM port has not been opened or is incorrectly set
✘ Line voltage is not switched on (SCB)
ê Switch on line voltage with 'Start Line'
ê At terminal A (Line Out), measure voltage between Ub and GND (terminals S and U). Require-
ment = 27 V.
ê At terminal A, measure voltage between Data and GND (terminals T and U). Requirement = 29 V.
If no line voltage is present, the Panel should be sent with a repair note to Zollikofen (Repair Depart-
ment) for checking.

®
7.5.7 Send telegram manually

The control commands cannot be executed until the Line has been correctly addressed, i.e. all detectors
on the Line have been found (total (w) = number of planned detectors)
In order to send a telegram manually, the complete control command must be input. This means that
trailing zeros must also be included.
The figure below shows the mask for inputting a telegram:
The button for sending the telegram is active only when no further program functions are active.
For example, the button is not active during startup.
The most frequently used commands for controlling the SecuriLine are shown below. More information
appears in Telegram.doc.
The control commands are always transmitted with "SEND" (s)
"Address" (r) : xx ê Address of the slave to be controlled
7.5.7.1 LED control of the detectors
Address CmD SubCmd Data 1

XX 36 1 (0) Transmit
SubCmd: 1 Actuate the LED

0 Reset the LED
7.5.7.2 Closing (opening) the stick in the SCU 81

XX 34 1 (0) Transmit
Each stick must be opened and addressed separately.

SubCmd: 1 Open the stick
0 Close the stick
7.5.7.3 Reprogramming an SDI

XX 35 2 1 (0) Transmit
Data 1: 1 Reprogramming an SDI 81 to an SDI 82

0 Reprogramming an SDI 82 to an SDI 81
Information
This command is the only one which is also retained when there is no voltage supply to the
SDI 81/82.

®
7.5.7.4 Resetting the priority data of a module

XX 34 255 Transmit
The CmD command may change according to the module (see Telegram.doc). 34 applies e.g. to the modules SOM,KIM,ICM,
KSM, DSM.
7.5.7.5 Controlling the COM 81 output

XX 34 1(0) Transmit
SubCmd: 0: Output switched off
1: Output switched on
7.5.7.6 Controlling the SOM 81 outputs

XX 36 1-7(0) Transmit
SubCmd: 0: All outputs switched off
1: Output 1 switched on (LSB byte B0)
7: All outputs switched on
7.5.7.7 Controlling the ROM 81 outputs

XX 34 0 1-7(0) Transmit
Data1: 0: All outputs switched off
7: All outputs switched on
7.5.7.8 Controlling the IOM 81 outputs

7.5.7.9 Controlling the SDI 81/82 output

XX 34 1(0) 1(0) Transmit
7.5.7.10 Controlling the MDI 81/82 outputs

7.5.7.11 Controlling the OCM 81 outputs

7.5.7.12 Switching from digital to analogue status of the smoke channel in the SSD 530

XX 33 1 Transmit

®
7.5.7.13 Switching from digital to analogue status of the temperature channel in the UTD 530

XX 33 1 Transmit
7.5.8 Addressing and polling in the control window
Line voltage off

Software version SCB 01
Line voltage on
Type polling
Release polling
Addressing of module
Close gate (FET)
Display address, type and release
Timeout; 3 repeats
7.5.9 Priority data

If only one address is output as a command,
12 Transmit
the detector reports back with its priority data.
Tx: 010D01 ← Command from SCB

Rx: 020100 ← Answer in HEX of line module
7.5.10 List of priority data of all Line participants
Explanation of table
Byte MSB,B7 B6 B5 B4 B3 B2 B1 B0, LSB

Prior HEX 0 0-7
Prior BIN 0 0 0 0 0 0/1 0/1 0/1
Meaning X X X X X Input3 Input2 Input1
SDI 81
0 0-7
0 0 0 0 0 0/1 0/1 0/1
X X X X X Input3 Input2 Input1

®
SDI 82
0 0-7
0 0 0 0 0 0/1 0/1 0/1
X X X X X Input3 Input2 Input1
COM 81
0 0-4
0 0 0 0 0 0 0/1 0/1
X X X X X X Tam. sw. Input1
SSD 530
0-F 0-F
0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
Optic.flt. Vref fault Supply flt Gen. fault Unfilt. al. Alarm Prealarm Dust
ESD 530
0-F 0-F
0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
Optic.flt. Vref fault Supply flt Gen. fault Unfilt. al. Alarm Prealarm Dust
UTD 530/1 UTD 530/2 UTD 530/3
0-D 0-E
0/1 0/1 0 0/1 0/1 0/1 0/1 0
KS sens. UB sensor X Gen. fault Unfilt. al. Alarm Prealarm X
SCU 81
0 0-1
0 0 0 0 0 0 0 0/1
X X X X X X X Tamp.sw.
SOM 81
0-F 0-F
0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
Tamp.sw. Batt. stat. Sabo 3 Sabo 2 Sabo 1 Fuse 3 Fuse 2 Fuse 1
IOM 81
0 0-F
0 0 0 0 0/1 0/1 0/1 0/1
X X X X Tamp.sw. Input3 Input2 Input1

®
OCM 81
0 0-1
0 0 0 0 0 0 0 0/1
ROM 81
0 0-F
0 0 0 0 0/1 0/1 0/1 0/1
X X X X Tamp.sw. Input3 Input2 Input1
Information
Important: The inputs exist only in terms of software but are not present and the
ROM always reports back the priority data 07Hex!
KIM 731
0 0-F
0 0 0 0 0/1 0/1 0/1 0/1
X X X X Tamp.sw. Key Input2 Input1
ICM 731
0 0-F
0 0 0 0 0/1 0/1 0/1 0/1
X X X X Tamp.sw. Key Input2 Input1
MDI 81
The MDI 81 has three times 1 byte which reports back because it can have over 17 different states. Ex-
ample: If all lines are closed and only the tamper switch is open, the priority data reports back with
000001. (Alarm line 6 and fault line 3 = priority data 2004)
0-F 0-F
0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
Alarm-L8 Alarm-L7 Alarm-L6 Alarm-L5 Alarm-L4 Alarm-L3 Alarm-L2 Alarm-L1
0-F 0-F
0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
Fault-L8 Fault-L7 Fault-L6 Fault-L5 Fault-L4 Fault-L3 Fault-L2 Fault-L1
0 0-1
0 0 0 0 0 0 0 0/1

®
MDI 82
The MDI 81 has three times 1 byte which reports back because it can have over 17 different states. Ex-
ample: If all lines are closed and only the tamper switch is open, the priority data reports back with
000001. (Alarm line 6 and fault line 3 = priority data 2004)
0-F 0-F
0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
Alarm-L8 Alarm-L7 Alarm-L6 Alarm-L5 Alarm-L4 Alarm-L3 Alarm-L2 Alarm-L1
0-F 0-F
0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1
Fault-L8 Fault-L7 Fault-L6 Fault-L5 Fault-L4 Fault-L3 Fault-L2 Fault-L1
0 0-1
0 0 0 0 0 0 0 0/1
7.5.11 HEX - binary conversion table for the priority data
00 0000 0000 Examples:

01 0000 0001
02 0000 0010 14 0001 0100 SOM = Sabo2 / Fuse 3
03 0000 0011
04 0000 0100 2A 0010 1010 MDI = Alarm Line 6, 4, 2
05 0000 0101
06 0000 0110 31 0011 0001 SSD = Vref fault, general fault, dust
07 0000 0111
08 0000 1000 4C 0100 1100 ROM = not possible because 2nd nibble not assigned
09 0000 1001
0A 0000 1010 52 0101 0010
0B 0000 1011
0C 0000 1100 63 0110 0011
0D 0000 1101
0E 0000 1110 7F 0111 1111 SOM= Battery stat (all bits, sabo and security bits
0F 0000 1111 also set if the additional supply is absent)
10 0001 0000 80 1000 0000 SSD = Optical fault
20 0010 0000
30 0011 0000 91 1001 0001 ESD = Optical fault, general fault, dust
40 0100 0000
50 0101 0000 A3 1010 0011
60 0110 0000
70 0111 0000 BA 1011 1010
80 1000 0000
90 1001 0000 CC 1100 1100
A0 1010 0000
B0 1011 0000 D9 1101 1001
C0 1100 0000
D0 1101 0000 E7 1110 0111
E0 1110 0000
F0 1111 0000 F1 1111 0001

®
7.5.12 Send telegrams as plain text

The most important telegrams can also be sent directly in plain text.
1. Make a selection in the menu "Special Orders/Send telegram (Text)"

A window containing all modules of the Line read in and the commands predefined per module ap-
pears:
2. Click on the desired module under "Line configuration" or enter the line address under "Adr.".
3. Select a command under "Selection of commands"
4. The control command is transmitted with "SEND"
The list of the predefined telegrams in plain text can be supplemented by the user's own, frequently used
commands. Exact instructions in this context are to be found in the Online help of the LineDiagnosis
Tools under Adapt telegram list for plain text

®
7.5.13 Create project file for importing the Line assignment (Panel Project)
In the Panel Project, the data of the line participants found are entered. These data can be saved in a file
(*.c0x) and imported in the project tool.
1. Address Line 1 according to Section 7.5.3.3, Start up Line from terminal A.
Information
There must be no more errors on the line and the addressing must be performed
completely from terminal A, since otherwise the Line will be imported into the project
tool as 2 sticks!
2. Switch off line voltage with "LINE OFF"

3. In the start screen, change the "Panel Analysis to "Panel Project"
The following desktop appears:
MDI 82
A
F
B
After a line has been started up, all data are entered in the table apart from the columns "MCU positi-
on" and "Line Number".
A) MCU position number acc. to project D) Creation of the Project file

B) Number of Line read in E) Info if Project file has already been created
C) Filename (without extension) F) Info on whether Line was addressed as ring
or 2 sticks

®
In the window, the following information is displayed in the columns
MCU Position number of the MCU on which the Line is connected

Line Number of the Line which was read in
Ring/Stick • Modules on a ring are entered as 0;
• stick modules are numbered from 1 to 15 at the corresponding point
• If the Line cannot be completely addressed from "START LINE", a 16 is
entered for the stick from terminal A and a 17 for the stick from terminal B.
The Line is thus also imported as 2 sticks !
Address Line address
Loop The entry is always 0 except if an MDI81/82 is present, in which case the loops 1-8
are entered (see example above)
Type Slave type number (according to Telegram.doc)
Release Release number of the module
UA Line Voltage line start (Line Out)
UB Line Voltage line end (Line In)
I Line Current of the Line (data) for corresponding detector
UB Voltage of 3rd wire (only with SCB 01A)
I UB Current of 3rd wire (only with SCB 01A)
After the line has been read in, the first two columns are still empty. Before a project file is created,
the following entries must be made:
4. Enter Number of the MCU (position number according to project tool/device list) (A)
The MCU column is updated
5. Enter Line number of the Line read in (B)
The Line column is updated
6. Enter Filename without extension (D). Click on the "CREATE FILE" button to create the file. The ex-
tension is automatically added. Up to now, only Line 1 has been entered.
7. Address and read in Line 2 according to points 1-5
8. Use the same filenames as in Line 1 and input without extension (D). Click on the "CREATE FILE"
button to create the file. The extension is automatically added. Up to now, Lines 1 and 2 have been
entered in the file.
If a file with the same line assignment has already been created in point 6 or 8, the following warning
appears:
9. Close Com port via menu "ComPort / Close Port" or with the button.

®
7.6 Preparation for commissioning of SecuriLAN (all devices) and MCB 02/02A
7.6.1 SecuriLAN terminal assignment
Check terminal assignment on all LAN participants and measure resistance from device to device:
• SecuriLAN A (all devices):
A Gnd
B +24V
E NetA
F NetB
• SecuriLAN B (MCUs, MIC and LCB in FAS systems):
I Gnd
K +24V
N NetA
O NetB
• Emergency alarm path (connect only when the EDB 0x board is used)
G NAL+ (A)
H NAL- (B)
The emergency alarm path connects all MCU, MIC, ARB and SOM (SecuriLine!).
Connection of SOM 8x:
Te.5 NAL +
Te.6 NAL –
Jumpers J1 and J2 must be connected.
7.6.2 Termination of the SecuriLAN
Information
The start and end of the SecuriLAN (A+B) must be terminated. If the regulations ac-
cording to EN54 apply, the SecuriLan must be terminated with LCB 02 (FAS only). In
all other systems, the SecuriLan is terminated with resistors as usual.
7.6.2.1 Termination with 105 Ω resistor (not compliant with EN 54)

In FAS systems which do not comply with the regulations according to EN 54, and IAS systems (only
LAN A present), the SecuriLan must be terminated at the start and at the end with a 105 Ω resistor.
E F N O
105 105
LAN A LAN B
Fig. 8 End-of-line resistors

®
If repeaters (SLR 811, FTR 811 + 812) are used, the individual LAN segments must also be terminated
with resistors.
SLR 811:
MCU with
Repeater
LAN A
First or First or
MCB
last last
01/02
LAN-Device LAN-Device
SLR LAN A
811
Repeater Start/End of
Te. E LON A +/ B +
LAN segment
Te. F LON A -/ B - LAN Te. E
(Shield) Shield LAN Te. F
105R
LON A +/ B +
105R
LON A -/ B -
Fig. 9 Termination with SLR 811
FTR 811: FTR 812:
MCB DC IN
MCB Fiber
P2P P2P
P2P P2P CASE
-V
Svc
R Fiber
TxRx
+V
Net A
LAN A
Fiberoptic cable LAN A
Fiberoptic cable segment 1

Net A
LAN A
L Fiber
Rtr Svc
Svc A MCU 1
MCU 1
Pkt
Svc B
P2P = Point to
point device
P2P = Point to
MCB DC IN
point device P2P
MCB
TxRx
Fiber
Svc
LAN A
MCU 2
CASE R Fiber
-V
+V
Net A
Net A
LAN A
L Fiber
Rtr Svc
Svc A
MCU 2
Pkt
Svc B
MCB DC IN
TxRx
LAN A

MCB MCU 3
P2P
Fiber
P2P CASE
-V
Svc
R Fiber
+V
Net A
Net A
LAN A
L Fiber
Rtr Svc DC IN - +
Svc A MCB Te. 13 Te. 14
Pkt
P2P P2P
MCU MCU 3 Svc B
4
TxRx
LAN A
MCU MCU 4
End of LAN segment Connection MCB - Repeater 5
End of LAN segment Connection MCB - Repeater
LAN Te. E or N
CASE
LAN Te. F or O Te. 13 -V
Te. 14 LAN Te. E or N
+V LAN Te. F or O
105R LAN Te. E or N Net A LAN Te. E or N
Net A LAN Te. F or O
LAN Te. F or O 105R
105R
105R
Fig. 11 Termination with FTR 812

Fig. 10 Termination with FTR 811

®
7.6.2.2 Termination with LCB 02 (according to EN 54)

The LCB02 is used for monitoring of the SecuriLan for short-circuit and open circuit in conformity with the
standard and as the bus termination. 2 LCB 02 are required per FAS system. The LCB 02 must termi-
nate the total LAN at the start and end.
Information
If only the LAN A is connected in the case of the last participant on the LAN:
• The LAN B and the 24 V supply for LAN B up to this device or the LCB 02 must also
be laid
or
• the LAN A and the 24 V supply from LAN A to the last device must be led back with
LAN A and B connection..
Start of SecuriLan SecuriLan Devices (Example) End of SecuriLan

J 8 & 9 to 1 and 2 J 8 & 9 to 2 and 3
MIC PIM MCU MCU MIC ARB
J8 3 O O O O O O 3 J8
2 N
M
N
M
N
M
N
M
N
M
N
M
2
1
B
B
L L L L L L
K K K K K K
I I I I I I
J9 3 F F F F F F F F 3 J9
2 E E E E E E E E 2
A
A
1 D D D D D D D D 1
C C C C C C C C
LCB 02 B B B B B B B B LCB 02
A A A A A A A A
Reverse graphic
Fig. 12 Connection of LCB 02
The jumpers on the LCB 02 must be set as follows:
Jumper Function Pos.

J5 End-of-line resistor 1/2 St Rx Tx Er St Rx Tx Er
LAN A ON
J7 End-of-line resistor 1/2 J1 J9 J3 J8
LAN B ON J2 123 J4 123
J8 LAN B start 1/2
J9 LAN A start 1/2 Adress settings
J8 LAN B end 2/3
J9 LAN A end 2/3
J5 J7
123
123
The end-of-line resistors must be at positi-

on ON at the start and at the end on the
LCB.
A B C D E F I K L M N O
Fig. 13 LCB 02

®
If repeaters (SLR 811, FTR 811 + 812) are used, the individual LAN segments should be terminated as
follows:
SLR 811:
First or MCU with
last LCB
Repeater 02
LAN device LAN A
MCB First or
01/02 last
LAN device
SLR LAN A
LCB
02 811
Repeater
Te. E LON A +/ B +
Te. F LON A -/ B -
(Shield) Shield
105R
LON A +/ B +
LON A -/ B -
Fig. 14 LCB 02 with SLR 811
FTR 811: FTR 812:
MCB DC IN
LCB MCB LCB
P2P
P2P 02
Fiber
Svc
02 CASE R Fiber
-V
TxRx
+V
Net A
LAN A

Net A L Fiber
LAN A Rtr Svc

Svc A
MCU 1
P2P = Point to
Pkt
Svc B
P2P = Point to
point device MCU 1 point device
MCU MCB MCB DC IN

3 CASE
-V
+V
Fiber
Svc
R Fiber
P2P
Net A
TxRx
LAN A
Net A
LAN A
L Fiber
Rtr Svc
MCU 2
Svc A
Pkt
Svc B
MCU 2
MCB
P2P P2P Fiber
Svc
MCB DC IN
CASE R Fiber
-V
+V
Net A
Net A L Fiber
LAN A
TxRx
Rtr Svc
LAN A

Svc A
Pkt
Svc B
MCU 4 MCU 3
MCB DC IN - +
P2P P2P Fiber
Svc MCB Te. 13 Te. 14
CASE
-V
+V
R Fiber
P2P P2P
Net A
Net A L Fiber
LAN A
TxRx
Rtr Svc
Svc A
Pkt
Svc B
LAN A
MCU LCB MCU 5 MCU LCB MCU 4
6 02 5 02
Connection MCB - Repeater

Connection MCB - Repeater
CASE
Te. 13 -V
Te. 14 LAN Te. E or N
+V LAN Te. F or O
LAN Te. E or N Net A
LAN Te. F or O Net A 105R
105R
Fig. 16 LCB 02 with FTR 812
Fig. 15 LCB 02 with FTR 811

®
7.6.3 Preparation of the MCB 02/02A :
Information
From Release 01.04.00, only MCB 01/02 and MCB 01A/02A can be used for operation
of a system with one or more MCUs. At least one MCB 01A/02A must be present per
system.
Equipping plan:
Mains Watchdog
6 5 4 3 2 1
Discharge protection jumper Li-Battery
WDM
EARTH
WDR
WDA
for al IC's
GND
29V
_ Accu LO Accu. charge current
7 Gnd
+ HI REL300
8 24V
Option discarge protection +
DCC313 9 Gnd Accu
10 12V Batt
12V 24V Terminal 11&12 RAM
Norm supply.
Local 11 Gnd
Local alarm
Alarm 12 12/24V
13 Gnd 12V 24V Terminal 13&14
Various
Option EDB 0x
14 12/24V Various C 321
15 Gnd
Alarm
12V 24V Terminal 15&16
transmission16 12/24V
J304
500mA polyswitch fuse
(IC505)
IC505 / RAM1 J504
A Gnd
0,9A polyswitch fuse
J503 J200
B 24V (IC504)
SCB 01/01A MCB 02A
SecuriLan C Earth
2
A SHLD
D
IC504 / RAM2
E NET_A
IC400 / EPROM (MIP)
F NET_B
IC 402
Emergency G NAL+(A)
alarm path (IC503)
H NAL-(B)
IC503 / RAM3 J501
I Gnd
0,9A polyswitch fuse
K 24V Operation.
(IC503)
indicator
J502
SecuriLan L Earth
IC502 / EPROM
B M SHLD J500
Firmware (IC502)
N NET_A
IC 401 Mode
O NET_B
RTC
4
3
20 21 2 Baud
Jumper positions 1
22 23 Norm
J504: RAM1 Supply
Digital
inputs 24 25 SCB 01/01A FV166
J503: RAM2 Supply
J502: EEPROM Supply 1
26 27
Example *
Norm Batt
30 31 J500: EPROM Memory size

*
32 33 (4 MBit) 8 MBit
RS232
Digital J501: EEPROM Memory type
outputs 34 35
RAM 1 MBit
36 37 * Standard
IC Output
Example
ULN 2803A SRV
+ 12/24 V J402
K
LED yellow
A
Fig. 17 Equipping of MCB 02/02A

®
7.6.3.1 Visual inspection of the MCB 02/02A

➢ Check insertion of Elkos C 321 (see Fig. 17)
➢ Check insertion of LED 400 (anode and cathode (see Fig. 17)
If the Elkos or the LED has been incorrectly inserted, the MCB is replaced by another
MCB. The incorrectly equipped MCB is sent for repair with an appropriate note.
The components may only be changed by appropriately trained personnel.
7.6.3.2 Equipping the IC for MCB 02/02A
• Checking or inserting the ICs:

The following software compatibility list is applicable for all LAN participants
- IC 400 (neuron firmware (MIB), EPROM 512kB)
- IC 402 (Pal)
- IC 502 (firmware, EPROM (4MB) / 8MB)
- IC 503 (customer software, RAM 1MB)
These IC should already be correctly equipped when received from the factory.
Information
From Release 01.04.00 it is essential to use an 8 MB EPROM for the IC 502.
For R01.03.00, the 8 MB EPROM may also be used. However, the same EPROM types
should be fitted to all MCB.
Danger information
Important: The IC may be changed only after disconnection from the voltage; i.e. the
jumper J800 (Li battery) must also be set to "Norm".
• Insert Li battery.
Danger information
Important: Note polarity!

®
• Check or reconnect jumper:
- J504 (IC 505)
- J500 (IC 502, 8MB)
- J502, J503 (IC 503, 504)
- J501 (IC 503, RAM 1MB)
- J800 (Batt)
- J306
- J300, J301, J302 (24V)
• Open all dip-fix/DIL switches (baud)
• Check connection of power unit terminals
6 29V (red)
5 Earth (yellow-green)
4 Gnd (blue)
• Tear off label with neuron ID along the perforation and stick on the installation plan

®
7.6.4 SCB 01/01A

7.6.4.1 Mount SCB01/01A
limitation
Current-
Supply
120
12V
LO
HI
24V
S T U U
R
SecuriLine
Start
Connection
MCB 01/02
T = 50
WX Y Y
R
SecuriLine
End
Reset
Emergency
1234 alarm
1 2 3 4
Dip-Fix Test points. Debug
Fig. 18 SCB 01
limitation
Current
Supply
120
12V
LO
HI
24V
S T U U
R
SecuriLine
Supply 3rd wire present

Start
Flashes if communication running

Off, error, no voltage
Connection
MCB 01/02
Contiuously lit up error, no communication
Wire strap S>W

for 2 wire loop SecuriLine
T = 50 Lights up if
WX Y Y
emergency alarm
dyn RES NAL stat
R
SecuriLine
active
End
NAL
1234
ON
1 2
RX
TX
Trig
GND
OFF
DIL switch Test points Debug
Fig. 19 SCB 01A
1. Check IC (Pic) on the SCB 01/01A according to software compatibility list

2. Screw on 4 spacer pillars (in set) per SCB
3. Insert SCB for Line 1 in the lower slot (SCB01/01A-1; Fig. 17)
4. Dip-fix/DIL switches 1-4 on the SCB remain open/OFF (Fig. 18 + Fig. 19)

®
5. Insert SCB for Line 2 in the upper slot (SCB01/01A-2; Fig. 17)
6. Close dip-fix/DIL switch 4 on the SCB or set to ON (Fig. 18 + Fig. 19)
7. Fasten SCBs with 4 screws each (in set) on spacer pillars
8. Connect line connections to SCB
Information
Important: Do not interchange Line out and Line in
Information
To enable the line to be started up in pure 2-wire operation with the SCB 01A, a wire
bridge must be connected between the terminals S and W (see Fig. 19).
7.6.4.2 Change SCB 01A to SCB 01

The SCB 01A can be changed to SCB 01 by means of the DIL switch 1 (Fig. 19).
Valid settings:
• Release lower than R01.03.00: SCB 01

• Release 01.03.00: SCB 01 or SCB 01A
• Release 01.04.00 or higher: SCB 01A
7.6.5 EDB 03 for line-monitored emergency alarm path (R 01.03.00.004 and R 01.04.00)
For FAS systems, a line-monitored emergency alarm path is required for systems with more than 32
Detectors (EN 54 and VdS; note country-specific requirements). If LAN data processing is terminated
due to failure of an MCU the transmission unit and the alarm transmission units must be actuated.
7.6.5.1 EDB 03 connection
SOM 81 MIC 732 / 734 ARB 71/1 / 72

5 6 G H G H MIC 732 / 734
G H
6kOhm
6kOhm
S S
Master Slave
F
+ EDB 03 + EDB 03
GH
GH
- -
I
ge e
an ang
/or /or
wn wn
bro bro
ite ite
21 wh 21 wh
23 MCB 02/02A 23 MCB 02/02A
Fig. 20 EDB 03 connection

®
1. Specify one EDB 03 as master per system

Set the jumper M-S to M = Master
2. The remaining EDB 03 are operated as slaves
Set jumper M-S to S = Slave.
3. Connect white signal wire (emergency alarm) to input E 21 of the MCB
4. Connect brown/orange signal wire (fault) to input E 23 of the MCB
5. Terminate start and end of emergency alarm path with a 6 kohm resistor.
6. Test emergency alarm path according to Section 7.6.5.4 Testing of emergency alarm path
Important
During repairs, extension, conversion or software update, the emergency alarm path
must be tested again in each case!
7.6.5.2 EDB 03 as replacement for EDB 01 / 02

The EDB 03 can be used as a replacement for the EDB 01/02 during extensions/repair (up to
R 01.03.00.003). The mixing of EDB 01, 02 and 03 is not possible. All EDB 01/02 must be replaced by
EDB 03. The EDB 03 are operated as slaves. There is no line monitoring.
SOM 8x MIC 732 ARB 71 / 72 / 73

5 6 G H G H
S S
Slave Slave
EDB 03 EDB 03
MIC 732
F
+ + G H
G H
G H
- -
I
MCB 02/02A MCB 02/02A
Fig. 21 Replacement of EDB 01/02
1. Set jumper M-S to S = Slave for all EDB 03.
7.6.5.3 Programming emergency alarm path in SecuriWin
Important
For a system compliant with EN 54, a redundant AU and TU must be defined. The
programming is perfomed according to the document T 139 928E.

®
7.6.5.4 Testing of emergency alarm path

The emergency alarm path can be tested only if the following requirements are met:
• System is bound
• Download has been performed
• System has been started up according to Section 7.7.4 or 7.12 (in operation)
During normal operation, no emergency alarm can be triggered. In order to test the emergency alarm
path, the following procedure should be followed:
1. Switch MCB from mode level 4 (normal operation) to level 3 (line start)
The polling of the SecuriLine is stopped and, after about 10 s, the emergency alarm detection is acti-
vated. The emergency alarm detection at level 3 then attempts to reset an existing emergency alarm
every 10 s. If alarm triggering occurs at an unfavourable time, this is active only for a short time and
must be triggered again.
2. Triggering of emergency alarm
The emergency alarm can be triggered in various ways:
• Short-circuit jumper NAL on SCB 01 or NAL dyn. on SCB 01A
The emergency alarm is triggered and is reset after 10 s
• Attach dip-fix NAL stat on the SCB 01A
The emergency alarm remains triggered until the dip-fix is removed again.
• Spray automatic detector on the SecuriLine with test gas
The emergency alarm is triggered and is reset after 10 s
• Push manual button on SecuriLine
The emergency alarm remains actuated and can be reset again only in mode 4 (normal operati-
on). (Requirement for British Standard)
3. Switch MCB back to mode 4 (normal operation)

®
7.6.6 Binding, download or startup?

- Continue depending on the answer to the following questions:
YES NO
System bound?
Start
Installations Tool
- New devices?
YES see section on
- New firmware (Update)? Binding
(MCU, MIC, ARB, etc.) (7.10.6)
YES see section on

- Download? Download
(7.11)
YES see section on

- Start up MCU from PC? Start up MCU from PC
(7.12)
NO
- Start up MCU manually ?

see section
7.8

®
7.7 Functions and indicators on the MCB 02/02A

7.7.1 Mode switch and mode indicator
- The startup of the MCU is divided into 4 stages:
Switch position Description Indication on MIC display
Neutral state
0 Binding dark
Download
INIT
1 dark
Profile test
2 LAN is started up BB mode Lanstart
3 LINE is addressed BB mode Linestart
RUN
4 Menus
Operating mode
7.7.2 7-Segment display

The 7-segment display indicates the current operating state, it immediately being clear whether an error
is present or not.
7-Segment display Meaning / Error
flashes slowly MCU "operating"; relevant stage is being set up
bright; static No error in the switch-on stage displayed
flashes quickly Stage 1: - Profile error, e.g. line number = 3

or number of slaves > 127
- Profile absent (EPROM, download)
Stage 2: - LAN participants absent

- Not all LAN devices bound
Stage 3: Line participants absent

- Line not OK → check line again with Panel
and compare project data
Stage 4: - One of the front stages is not OK

®
7-Segment display Meaning / Error
Decimal point = flashes quickly, seg- Minor error (program error)

ments a - g; indicate normally
A minor error is present, e.g. if an impermissible data value
a occurs in a program segment. The relevant program segment
is then not executed in order to avoid further errors. Causes of
f b minor errors are, for example, incorrectly generated telegrams
g from an external system, impermissible entries in the profile,
incorrect data accesses by the operating software
e c
d
Decimal point = static, bright, segments Serious error (program error)

a - g = dark
A serious error is present, e.g. if the checksums of the profile
data are no longer correct. The further execution of the pro-
gram would lead to unpredictable results. Reasons for serious
errors are, for example, improper sequence in the commissio-
ning of a system, incorrectly set battery buffering for the me-
mory modules, deletion of data by static discharges on contact
with components.
7.7.3 Baud switch

The 4-pole baud switch is located on the circuit board MCU 02/02A, directly below the mode switch (see
Fig. 17). The baud switch can be used for triggering various functions which are very helpful in particular
during commissioning.
Switch Meaning
4 Indication list: open = no function, closed = next indication
3 System start mode: open = global (all MCUs), closed = local (own MCU)
2 ---
1 Debug function: open = normal

®
7.7.4 Errors at the comissioning
• No display (7-segment) of mode; yellow LED lights up:

✘ On upgrading to R01.04.00, jumper J 500 (for IC 502, 8 MB) was not changed over.
✘ Incorrectly set battery buffer for IC
✘ Jumper for battery (J 800) is not connected
✘ IC incorrectly equipped or poles interchanged
✘ Supply on MCB is not symmetrical (approx. 14.5 V each between earth/_ and earth/Gnd)
ê Check whether the temperature sensor for battery monitoring has been connected
ê The temperature sensor may be faulty
✘ 5 V supply (internally on the MCB) is faulty
ê Replace MCB
• Yellow LED on the MCB flashes constantly

✘ Unit is hard-offline
✘ IC 502, IC 400 or RAM is incorrectly equipped or poles have been interchanged
✘ Node ID/ Subnet incorrect
• Red LED of unit flashes constantly

✘ Unit is hard-offline
ê Remove IC 400 (power off !), install firmware of another unit, power on, reinstall original firmwa-
re (power off!)
• Red LED of the unit lights up continuously

ê Operate reset pin on unit
ê In units with a buzzer, the supply of the unit must now be removed and reconnected so that the
buzzer can be reset.
• The output voltage of the PSU is much too high/low or unstable

✘ Temperature sensor for battery monitoring is missing or faulty
ê Connect/change temperature sensor.
If no spare temperature sensor is available, a 2.2 kOhm resistor can be connected as an emer-
gency solution. The resistor may not be left on the PSU as a final solution!
• Relay (...) on the MCB "flickers"

✘ The output voltage of the PSU is much too high or unstable
ê Connect/change temperature sensor.

®
7.8 Start up MCU manually (with mode switch)

The system can be started up only if the following requirements are fulfilled:
• System has been bound
• Download has been peformed
The manual startup of the MCU is possible in two different ways:
- Local mode: Each MCU is started up individually (also possible in networks).
- Global mode: All highway participants MCU+SIB) are started up from a "Master" MCU.
In this document, a master MCU is defined as the MCU from which startup is performed; however, this
should not be confused with the MCU which performs the master MCU function during operation.
7.8.1 Startup in local mode

The local mode is used for starting up an individual MCU (1MCU + point-to-point devices, without
SIB 71) in the network for separately powering up each individual MCU.
• If the addressing and then the polling of a line are to be checked, the SecuriLine monitor can be con-
nected to the SCB 01/01A according to Section 7.9.2.
1. On the MCU, set the mode switch to "0"

2. Attach dip-fix/DIL switch 3 to the MCB02/02A
3. Switch on mains (220 V) and connect battery (commissioning)
ê wait until the yellow LED no longer flashes and the "0" is static on the 7-segment display.
4. Set MCU to mode "1"**
The initialization/testing of the profiles is carried out; wait until the display "1" is static.
If errors are ignored at stage "1", the system is brought into an undefinable state
5. Set MCU to mode "2" **
LAN devices are started up; wait until the display is static or flashes quickly.
The display flashes quickly, for example, if all devices have not yet been bound.
Lines are addressed; wait until the display is static or flashes quickly.
After the addressing, the line remains stationary and does not begin to poll until switched on to stage
"4".
The MCU is switched to the operating mode (Run)
This procedure takes about 1 minute for each MCU since all messages (e.g. basic states, such as
outputs switched on, etc.) are sent.
Poll lines; depending on the key switch position, the menus and/or the disarmings are displayed. If no
disarmings or faults are present and the key switch is switched off, the MIC display shows the date
and the time.
Information
** In modes 1-4, it is also possible to continue if the display is not static but the errors
according to Table 2 are present.
In principle, however, the problems should always be rectified immediately in the re-
spective stage.

®
7.8.2 Startup in "Global mode"

The global mode is used for starting up an entire network from an individual MCU.
The MCU from which startup is performed performs the function of the "Master" MCU during the startup.
The "Master" MCU can be freely determined but it is advisable to choose an MCU with an MIC in the
immediate vincinity.
1. On all MCUs, set the mode switch to "0"

2. All dip-fix/DIL switches of the baud switch must be opened/at OFF
3. Switch on mains (220 V) and connect battery (commissionng)
ê wait until the yellow LED no longer flashes and the "0" is displayed statically on the 7-segment
display.
4. Set "Master" MCU to mode "1"
The initialization of the profiles is carried out. Wait until "1" is displayed statically on all MCUs.
Since the other MCUs may be distributed in various rooms or on various floors, not all displays can be
checked. However, the startup of the relevant stage is complete for all MCUs as soon as the display
on the "Master" MCU is static. If an error is present, the display of the "Master" MCU flashes quickly.
The errors can be displayed according to Section 7.7.3.
Information
In the global mode, the mode switch is adjusted only on the "Master" MCU. On all other
MCUs, it always remains at "0" during the startup.

The LAN devices are started up. For all MCUs, with several point-to-point devices, the startup takes
longer. The following devices are displayed according to the error list in the next section.

The lines are addressed. After the addressing, no polling is performed.
The addressing takes [10 seconds to switch-on + number of detectors * 1.5 sec.].
In the event of a short-circuit or missing detector, the whole procedure can take up to 8 minutes,
depending on the method of addressing of the line.
Wait until the display shows "3" statically.

The MCUs are switched to the operating mode (Run).
First, an initialization is performed in the "Master" MCU. Then, the highway participant (MCU or SIB)
with the highest device number (see numbering of the bin files) is initialized or started up;
messages, such as basic states, output assignments, etc., of the currently processed MCU are sent
and the lines are polled. This takes about 1 min per MCU.

®
If the display shows "4" statically, the highway participant with the second highest, then with the third hig-
hest, etc. device number and finally the "Master" MCU are started up.
The startup of the "Master" MCU takes about 3 min.
Because of the staggered startup of the highway participants, communication faults of the devices not
yet started up are displayed on the MIC display. However, these can be acknowledged after all partici-
pants have been started up.
Depending on the key switch position, the menus and/or the disarming are displayed.
If no disarmings or faults are present and the key switch is switched off, the MIC display shows the date
and time.
Example of startup sequence of the MCUs:
MCU4 = "Master“-MCU; (B01, ..B15) = Bin-Files
MCU1 MCU2 MCU3 MCU4 MCU5 SIB71

(B01) (B02) (B03) (B04) (B05) (B15)
6. 5. 4. Start 3. 2.
End
Information
After the network has been completely started up, the mode switches are set to stage 4
on all MCUs. If for any reason an MCU is reset, it can start up again automatically.
7.8.3 Changing from global to local mode

The whole network has been started up in the global mode and is in operation.
If a change, for example, in the line of only one MCU is now necessary, this MCU can be changed to the
local mode and can be started up or switched off independently of the network.
The network continues to operate normally; a communication fault of the MCU-xx is detected.
1. In MCU-xx, attach dip-fix/DIL switch 3 or set to ON

2. Wait for about 10 sec (updating of the startup mode)
3. Set mode switch to the desired stage
MCU-xx can be switched off and started up again as desired by turning the mode switch.
Changes, for example to the line, can now be made.
4. Start up MCU-xx as described in Section 7.7.4, stepwise again to "4".
5. Wait until the display shows "4" statically.
6. Open dip-fix/DIL switch 3 or set to OFF
ê MCU-xx is switched back to the global mode.
Information
The mode switch of MCU-xx remains at stage "4"

®
7.8.4 Indication of int. errors via 7-segment display and baud switch on MCB 02/02A
Details of the errors in a mode (stage) can likewise be indicated by means of the 7-segment display, by
actuating the baud switch dip-fix/DIL switch 4 (see Fig. 17, Section 7.6.3) for about 1 s.
An error message consists in each case of 4 digits (Hex) and a preceding "H", "L" or "U" for error reco-
gnition (see Table below).
The error codes are displayed as running script. The format comprises a preceding code letter and an
error number, a distinction being made between the following error classes:
Error class Code letter Format Description
Task error ‘L’ 4-digit hex • Digits 1..2: Task number (see Table)
• Digits 3..4: Task error (see Table)
System error ‘H’ 4-digit hex • Digits 1...2: Device number (according to
proj. database
• Digits 3..4: Task error of the relevant device
(sum)
Inherited error ‘U’ 4-digit hex • Digits 1..2: Device number (according to
proj. database)
• Digits 3..4: Error of the relevant device
(see Table)
Example:
- Display flashes rapidly in mode 3
- Close baud switch dip-fix/DIL switch 4 for about 1 s (see Fig. 17, Section 7.6.3)
- The 7-segment display shows e.g. H 0.1.0.1. . . H 0.1.0.1. . .
ê Error according to list: Device 1, line 1 not closed
- Close baud switch dip-fix/DIL switch 4 again for about 1 s
ê If a further error occurs, e.g. H.0.3.1.0. .. H.0.3.1.0. .. appears
ê If no further error is present, mode 3 appears again flashing
7.8.4.1 Program error indication

If the main processor finds an internal error during the program runtime, this is entered in a nonvolatile
memory and indicated separately on the 7-segment display. A distinction is made between minor and se-
rious errors. In the case of minor errors, the program continues; in the case of serious errors, the pro-
gram is stopped (processor failure but no reset).
Type Indication
Minor error Decimal point = flashes quickly, segments a..g: indicate normally, everything
which is possible
Serious error Decimal point = continuously bright, segments a..g = dark
A minor error is present, for example, if an impermissible data value occurs in a program segment. The
relevant program segment is then not executed, in order to avoid further errors. Causes of minor errors
are, for example, incorrectly generated telegrams from an external system, impermissible entries in a
profile, incorrect data accesses by the operating software.
A serious error is present, for example, if the checksums of the profile data are no longer correct. The
further execution of the program would lead to unpredictable results. Reasons for serious errors are, for
example, improper sequence during the commissioning of a system, incorrectly set battery buffering for
the memory modules, deletion of data by static discharges on contact with components.

®
7.8.4.2 System error "H"

If a system with several MCUs is started up, the system errors can be displayed on the "Master" MCU.
For this purpose, the switch for startup mode must be at "global" (dip-fix/DIL switch 4 on all MCUs
open/OFF).
Example:
H0301 Device number 3 has a general error in the current mode.
H04FF Device number 4 does not respond in the current mode.
7.8.4.3 Overview of errors:
Error Description
01 General error in device. This may be discovered locally in the corresponding device
F0 Device cannot change to this mode (device may be in local mode)
F1 Device does not understand telegram
FF Device does not respond (timeout)
An error message consists in each case of 4 digits (Hex) and a preceding "H", "L" or "U" for error reco-
gnition (see Table above).
7.8.4.4 Inherited errors "U"

Inherited errors (errors from previous modes) are also indicated. In the mode giving rise to the error, the
error is indicated as before (as system error or task error). If the next mode is now selected, the display
flashes quickly. An inherited error can be displayed by means of the dip-fix/DIL switch 4 of the baud
switch (see Fig. 17).
The inherited errors are deleted on changing from mode 0 to mode 1.
Example:
U0301 Highway device number 3 had a general error in an earlier mode.
Overview of errors
Error Description
01 General error in device. This may be discovered locally in the corresponding device
F0 Device cannot change to this mode (device may be in local mode)
F1 Device does not understand telegram
FF Device does not respond (timeout)

®
7.8.4.5 Overview of the task errors
Task name Task num. Mode 1 Mode 2 Mode 3 Mode 4

SEDEVDRV (Security Device 01 --- --- --- ---
Driver)
SEDEVHAN (Security Device 02 --- --- --- ---
Handler)
SERDRV (Serial Driver) 03 --- --- --- ---
PROTOHAN (Protocol Handler) 04 --- --- --- ---
SERSCH (Serial Scheduler) 05 --- --- --- ---
SPIDRV (SPI Driver) 06 XX
SLVDRV (Slave Driver) 07 XX XX XX XX
DEVHAN (Device Handler) 08 XX --- XX XX
IOHAN (Input-Output Handler) 09 XX --- --- ---
LONHAN (LON Handler) 0A XX
BBMASTER (Blackbox Master) 0B --- --- --- ---
EEPROM (Profile description) 0C XX XX XX XX
UHREN (Clock management) 0D --- --- --- ---
SPEICHER (Memory manage- 0E XX --- --- ---
ment)
ALARM (AU/TU management) 0F XX --- --- ---
SPS (PLC management) 10 XX --- --- ---
MAPS (Map management) 11 XX --- --- ---
DET (Detector management) 12 XX --- --- ---
IN (Input management) 13 XX --- --- ---
OUT (Output management) 14 XX --- --- ---
IODRV (Input-Output Driver) 15 --- --- --- ---
7.8.4.6 Task errors 'L'
Error code in mode 1 (INIT)

Task name Task num. Task error
SPIDRV (SPI Driver) 06
SLVDRV (Slave Driver) 07 01 = Max. number of lines (pos. Dip Fix Line 1/2
closed/open)
02 = Line-1 max. number of slaves (> 127)
04 = Line-1 max. number of sticks (> 15)
08 = Line-2 max. number of slaves (> 127)
10 = Line-2 max. number of sticks (> 15)
Errors may be superposed (bit-by-bit).
IOHAN (Input-Output Handler) 09 01 = Signal missing from EP profile (e.g. contacts
in MCU, like LAN A, Comm.fault, etc.)
LONHAN (LON Handler) 0A 01 = Device missing
EEPROM (Profile description) 0C 01..80 = Profile checksum File-1..File-128
FF = Program checksum
UHREN (Clock management) 0D
SPEICHER (Memory manage- 0E
ment)
ALARM (AU/TU management) 0F 01 = max. number of AU/TU (see system limits)
SPS (PLC management) 10 01 = max. number of PLC modules (system limits)
02 = max. number of PLC references (system lim.)
MAPS (Map management) 11 01 = max. number of MAP (see system limits)
02 = max. number of menu options (system limits)
03 = max. number of project texts (system limits)
04 = max. number of CMD (see system limits)

®

DET (Detector management) 12 01 = Criteria
02 = max. number of DET (pos. several MCU on
the same DA)
03 = min. number of DET (pos. several MCU on
the same DA)
04 = max. number of DZ (see system limits)
05 = min. number of DZ (see system limits)
06 = max. number of DA (see system limits)
07 = min. number of DA (see system limits)
08 =
IN (Input management) 13 01 = max. number of IN (see system limits)
OUT (Output management) 14 01 = max. number of OUT (see system limits)
Error code in mode 2 (LANSTART)

SLVDRV (Slave Driver) 07 01 = LIF1 not startable.
10 = LIF2 not startable.
LONHAN (LON Handler) 0A
Error code in mode 3 (LINESTART)

SLVDRV (Slave Driver) 07 01 = Line-1 Physics d’ont match with profile
02 = Line-1 not startable
04 = Line-1 Open circuit (at any point)
08 = Line-1 Short-circuit (at any point)
10 = Line-2 Physics d’ont match with profile
20 = Line-2 not startable
40 = Line-2 Open circuit (at any point)
80 = Line-2 Short-circuit (at any point)
Error code in mode 4 (RUN)

SLVDRV (Slave Driver) 07 01 = Line-1 does not poll
10 = Line-2 does not poll

®
7.8.5 Error during start-up or during operation
• MCU cannot be started up in the global mode

✘ Dip-fix/DIL switch 3 (mode) is still closed
• When changing from level 3 to 4, the line does not start polling. However, level 3 does not gi-
ve an error. After startup at level 4, there is also no error and the MIC shows "NAL LIF" and
"overcurrent..". "Timeout" appears on the tracer.
✘ The line has a creeping short-circuit. There is no error at level 3 because the voltage is switched off
more than 2 s after addressing!
ê Check line with Panel
ê FET of last module closed?
ê Measure voltage at terminal B for min. 15 s after addressing; switch-off after how many se-
conds?
ê Measure GND for resistance
ê Measure data-GND resistance; if e.g. 300 kohm = creeping short-circuit
ê Default profile setting / wiring of e.g. SDI is incorrect
ê Eliminate error and perform addressing again
• Fault "NAL LIFx" after startup

✘ Detectors are in the alarm state after the line has been started up
ê Check MCP / detector (possibly with Panel)
ê Check profile settings/wiring of the MCP
• MCB input cannot be set to active/passive

✘ Dip-fix/DIL switch 1 (service functions) on MCB is closed
• If there are several MIC in the system, the indication/control reacts more slowly in one or more
MIC.
✘ PAL versions are not compatible
✘ Wires of the LAN have been interchanged (E/F)
• During operation, the 7-segment display on the MCB becomes dark and only the point lights
up continuously
✘ MCU type is incorrect / incompatible
ê Replace MCB with incorrect MCU type (new binding / download !); start up the system again
✘ Checksum of the profile data is incorrect
ê Full download of the profiles (bin files)
✘ Data were deleted by static discharge
ê Full download of the profiles (bin files)
• The MIC display does not function

✘ LCD cable incorrectly connected (+,-)
✘ No system has been assigned to the MIC (Proj.tool/Device list/Advanced)

®
• Not possible to input the installer code or another code on the MIC
✘ MIC not assigned to any system (from R01.03.00)
ê In Proj.tool/Device list/Function/Advanced, assign MIC to the system from which it is administe-
red
✘ No operators have been assigned to the various menus
ê In Proj.tool/Device list/Function/Operator, assign an operator to the menus
✘ Code profiles in RAM (MCB) are incorrect; only a partial download may have been performed when
the system was upgraded
ê Remove supply/battery on MCB;
ê Remove jumpers of the battery (J800) and of the two RAM IC 505 and IC504 (J504 + J503;
nearest the battery) for min. 10 s
ê Reinsert jumpers of the RAM and of the battery and connect supply/battery
ê Perform download
• Clock / date can be set but then remain at this value (MIC display)
✘ Trigger events and then check in the event memory whether the times are recorded
ê Times are in the event memory: Refresh/init problem of the LCD
ê Times are not recorded: IC RTC faulty ê Replace MCB
• During normal operation of the system, the alarm LED is not actuated when the detector is
triggered
✘ Detector may be faulty
ê To check with the Diagnosis Tool Analysis, trigger the LED after addressing using the corre-
sponding command
✘ The corresponding detector has been "exported" in the project, i.e. the detector number (detection
area) has been assigned to another MCU but the detector is not on line 1 or 2 of this MCU
• System fault "Mains failure"

✘ No mains voltage
✘ Temperature sensor (NTC) for battery monitoring has not been connected to the PSU
• System fault "Battery failure"

ê The evaluation is performed if the battery voltage is < 22 V.
✘ Batteries are no longer charged or are faulty
✘ Battery cable is not connected to MCB
✘ Cable/battery connection on MCB has a loose contact
• System fault "SPI error"

✘ SCB may be faulty or missing
✘ SCB is not correctly connected
✘ SCB - MCU interface may be faulty

®
• System fault "SI 304/305"

✘ Too many devices connected to the LAN (current consumption is > 1 A)
✘ LAN fuses (SI 304+305) have not yet been designed for 1 A (old MCBs)
• System fault "Earth fault"

ê The evaluation is performed if < 50 kOhm +/- to earth
✘ Check voltage at MCB supply terminals (29 V-earth and Gnd-earth must be symmetrical; approx.
14.5 V); temperature sensor must be connected on PSU.
✘ Earth wired to incorrect connection
✘ Ext. earth fault via cable screen
✘ Ext. earth fault via line wiring; cable screen has been wired directly to modules
✘ Earth fault via PC interface - serial cable (SecuriLine monitor, SIB71)
✘ Earth fault through measuring device (KO)
✘ Possible earth fault in quartz housing - Gnd (replace MCB)
✘ .......
• System fault "LIFx: Overcurrent data"

✘ Line end voltage Data at terminal B missing (line is automatically readdressed)
✘ Line was interrupted
✘ Detector was inserted in base again
• System fault "LIFx: Overcurrent Ub"

✘ Line end voltage Ub at terminal B missing
✘ 3rd wire interrupted
• System fault "LIFx: Overcurrent Data" and "Comm.fault: Det xxxx.xx" are shown simultane-
ously on the MIC display
ê The line end voltage is still present (line still polling)
✘ Detector was removed from the line/was faulty
ê The line end voltage falls briefly below 15 V, which is detected as a creeping open circuit. The
fault "LIFx: Overcurrent Data" can be reset.
ê "Comm.fault: Det xxxx.xx" can be reset only if the detector is inserted again and the line is re-
started.
• System fault "LIFx: Startup error"

✘ The line x cannot be started up
ê For details of the error, see task errors page 48, Error code in mode 3
• System fault "LIFx starting up"

✘ The line x is being readdressed and started up
• System fault "LAN channel x fault"

✘ LAN x of the logged-on MCU has an open circuit or is faulty

®
• System fault "previous HW device" or "next HW device"

✘ The next or previous highway device of the detected MCU is faulty
MCU 1 MCU 2 MCU 3 MCU 4

Position 1 Position 4 Position 6 Position 9
DA 00 DA 05 DA 08 DA 12
Message on MIC: 'disturbed' Message on MIC:

Comm. fault MCU Comm. fault
0599.16 xy 1299.15 xy
MCU 03 MCU 03
Fig. 22 Comm. fault MCU
• System fault "NAL fault"

✘ The emergency alarm path was interrupted/is not connected.
ê The connections of the EDB 03 are not connected to contacts 21 and 23 of the MCB.
ê The emergency alarm path has been interrupted on a device.
• System fault "NAL previous HW device" or "NAL next HW device"

✘ If, for example, the MCU 03 has "Comm.fault" as Fig. 22, the NAL for MCU 03 is triggered by one
of the two "adjacent" MCUs in the event of actuation of the MCB 03 (e.g. TU actuation of the ARB).
• System fault "NAL LIFx"

✘ During startup of the line x, an alarm (e.g. pushbutton) was triggered.
• System fault "MCU type incorrect"

✘ A scan is performed internally every 60 minutes to determine whether the valid MCU type is still
present. If the valid MCU type is absent, the fault "MCU type incorrect" is shown in the MIC display
after 4 hours.
If there is still no valid MCU type after 48 hours, the program stops, i.e. the system is no longer in
operation. The state can be eliminated only by a change of MCB, download and subsequent sy-
stem restart, and the MCU type is checked again.
ê Unbind MCB with the incorrect MCU type, replace, rebind, download and start up the system
again.

®
7.9 SecuriLine Tracer

7.9.1 Introduction
The SecuriLine Tracer is a component of the SecuriLine Diagnosis Tool and was developed for checking
the SecuriLine functions. It is ideal for recording the detector addressing during startup, for online chek-
king of the priority data, i.e. monitoring of the detector and module statuses, and for checking the beha-
viour of the reset commands from the SCB 01/01A.
Furthermore, the messages can be saved in datalog files. This makes it possible to analyze any pro-
blems which may occur.
Information
®
To be able to use the Tracer software, the SecuriPro system must be completely equip-
ped with all operating systems and software (LAN, SCB and MCB software and customer
data) (see software compatibility list)
The functions of the SecuriLine Tracer are described in detail in the online help of the tool.
7.9.2 Starting up the SecuriLine Tracer
1. Connect 9-pin PC cable to serial port of the laptop and the SecuriLine monitor box
2. Connect 10-pin flat cable to the SecuriLine monitor box and the SCB 01/01A debug interface (Line 1
or 2 depending on which line is to be recorded). See Fig. 18 + Fig. 19, Section 7.6.4
3. Start Tracer software.
The start screen of the SecuriLine Diagnosis Tool appears.
4. Open SecuriLine Tracer
5. Set up COM port connection via the ComPort / Settings menu or
6. Open COM port
The addressing is now recorded (on startup), followed by the polling of the line.

®
The following desktop appears:
for the addressing and subsequent polling:
a
b c h
Addressing
i e
Polling g
Legend:
a) Settings for Tracer g) Log file entries

b) Open / close COM port h) Online help (also with F1)
c) COM port settings i) Addressing of the line
d) Type of Tracer recording k) Polling of the line
e) Trigger address l) Info and status of the COM port
f) Last values of the address entered

®
7.9.3 Line Profile

The recorded line data are displayed in HEX code. If the HEX code and the meaning of the data are not
familiar, it is possible to view the line data in plain text.
For this purpose, the bin file of the corresponding line is imported into the SecuriLine Tracer.
7.9.4 Load bin file
1. Select "File / Load / BinFile / Line 1 or 2"
2. Set path in which the bin file is saved
7.9.5 View HEX data in plain text

1. Click with the mouse on the address which is to be viewed
In the "Text output" window, the master and slave data and the slave type and address are dis-
played in plain text.
2. The window is closed again by clicking on "Back"
7.9.6 Saving a log file

If the line data are to be recorded in a log file:
1. Select "Show only difference" in the "Display" field (d).
2. Input log file name (g)
or accept default "Tracer.Log" name
3. Select "Save as File" by clicking
The file size may be up to 960000 bytes, after which the data are overwritten starting from the begin-
ning.
Only data which change after the addressing and subsequent polling of the line are displayed and re-
corded.

®
7.9.7 Recording all telegrams

Select "Show all telegrams" (d) in the Display field
The "Save as File" selection must be removed. Otherwise the following warning appears:
7.9.8 Triggering on an individual address
1. Set filter to "Set trigger.." (e) in the Display field.

2. Input the desired address in decimal form at "..on address (dec)" (e).
3. Select "only difference" (e)

Only the difference between the input address is displayed.
7.9.9 Timeout
From time to time, a detector may not report back because it is carrying out its internal measurements. It
therefore reports back a t (timeout). Such timeouts can be neglected.

®
Information
If several timeouts follow directly in succession from the same line participant, a cable
break may be present before this detector.
7.9.10 BiPhase
A biphase error occurs if the time window of the square-wave pulse on the SecuriLine is outside the to-
lerance, i.e. the detector – MCB response is disturbed. This may have the following causes:
ê Double addressing of detectors (two detectors wired in parallel)

ê Cable problems or connection problems in the detector base
ê External EMC effects, for example from amplitude-modulated personal pagers
ê Faulty module
ê Short-circuit
7.9.11 Addressing and initialization

The table below shows an addressing sequence for an SSD 530 with the address 9 which is assigned.
Adr Master Slave Remark

0 0004 0434 04=Request for slave type, 34=SSD 530
0 0027 2704 27=Request for Release, 04=Release 4
0 000109 0109 01=Address number assignment, 09=address number
09 09201D 201D 20=Configuration command, 1D=0001 1101 Gen.fault/Unfil. al., Al,
dust
09 0922FF 22FF 22=Reset all priority data, FF=1111 1111= all
09 092100 2100 21=Configuration priority data, 00=Digital status
09 090301 0301 03=Close command of insulating FET, 01=close FET
Most commands are acknowledged by the slave (detector, module) with the same answer telegram.
If only the address of a specific slave is output by the SCB 01/01A, the slave reports back with its priority
data.
If, in the addressing and initialization mode, a specific slave type is expected at a specific address (ac-
cording to SecuriWin programming) and a different slave type reports back, the addressing stops.
ê The detector sequence must be compared with the project data and corrected until required and ac-
tual state agree.

®
7.9.12 Slave type list

The slave type is returned in the first line of a respective addressing sequence. If the line startup stops at
such a line, the software sequence must be compared with the hardware sequence.
Information
Details on the individual slave types appear in the document "Telegram.doc"
Data Type No. Type

0430 30 SDI 81
0431 31 COM 81
0432 32 MDI 81
0433 33 MDI 82
0434 34 SSD 530
0435 35 ESD 530
0436 36 SOM 81
0437 37 IOM 81
0438 38 OCM 81
0439 39 ROM 81
043A 3A KIM 731
043B 3B ICM 731
043C 3C SCU 81
043D 3D SDI 82
043E 3E UTD 530/1
043F 3F UTD 530/2
00440 40 UTD 530/3
0441 41 KSM 411P
0443 43 RDU 251
0444 44 DSM 25x
0445 45 LCM 81
0446 46 ROM 82
0450 80 STD 531
0451 81 SDI 81/1
0452 82 SDI 82/1
0453 83 SDI 83
0454 84 SCI 82
0455 85 SOM 82
0456 86 ROM 81/1
0457 87 ICM 731/1
0458 88 KIM 732
0459 89 KIM 732/1

®
7.10 SecuriLan installation

7.10.1 Introduction
The binding, the download and the startup from PC are performed using the installation tool.
Information
• The installation tool can run only under Windows 95B, 98 SE or NT 4.0 (Service pack
6).
• All functions of the installation tool are described in detail in the online help of the tool.
Work flow for Installations-Tool
Binding
Switch
LAN mode
Download
Fig. 23 Installation tool sequence
• Binding (see Section 7.10.6):

The SecuriLAN participants are connected to one another (binding) in terms of software and hardware
(project).
The MCU, SIB, MIC, FBM, OCB, ARB, PCM and PIM programmed in SecuriWin are assigned to the cor-
rect (hardware), with the uniquely assigned neuron ID, MCU, SIB, MIC, FBM, OCB, ARB, PCM and PIM.
If the neuron ID is entered in the project tool, auto binding is also possible.
• Download (see Section 7.11):
During the download, the project data (bin file) are loaded into the EPROM on the MCU and SIB.
However, it is essential that the system is bound.
• Startup from PC (see Section 7.12):
The entire system or only individual MCUs can be started up from a PC.
Information
The system must be completely bound to permit startup from PC!
7.10.2 Setting the baud rate of the SLTA

The SLTA functions at a baud rate of 19200 bps and at 38400 bps.
With the 38400 bps setting, the download time is reduced from 6 min to 4.5 min per MCU
The baud rate of the SLTA must be set manually on the device. The jumpers (in the housing) must be
reconnected in the SLTA 2 and the switches (outside) must be switched in the SLTA 10:

®
7.10.2.1 Setting for the SLTA 10

Set the dip switches 6 to 8 on the front of the SLTA 10 according to the following diagram:
Service LED
Service Pin NETWORK
CONFIGURATION
E/N F/O
1 2 3 4 5 6 7 8
Switch off Baud 38400 bps

Switch on
Fig. 24 SLTA 10
7.10.2.2 Settings for the SLTA 2
• Open the housing of the SLTA 2 (remove screws)
Important
EMC-sensitive components!
• Reconnect the jumpers of S 3 for the baud rate according to the following diagram:
SLTA 2 open
S2
Connection
S3 SecuriLAN
Accu
OFF
ON
DTE DCE
NC
Alert/ACK Buffered
Local Remote
Network enabled Network disabled
3 Wire 8 Wire
Autobauddisabled Autobaud enabled
Baud 38400 bps
Fig. 25 SLTA 2
• Close the SLTA housing again using the screws

®
7.10.3 Start screen of the installation software
a c d e f g h i k l m p q
b n o
a) Open project i) Neuron info

b) Start up SecuriLAN k) Assign device
c) Stop SecuriLAN l) Remove device assignment
d) Node Info SLTA m) Write data to net
e) Match project data n) Switch devices online
f) Match net data o) Profile test
g) Search for device (all) p) Download profile
h) ServicePin q) Startup from PC

®
General remark:
Occasionally, the following message appears on the screen:
Although this message is unpleasant, it has no effect on the operation of the program and can be
acknowledged with "Repeat".
7.10.4 Meaning of the icons used

General
Refresh project dialogue; match with the current data in the net
Write data to net
Project dialogue
(red): Planned device; SecuriLAN has not yet been connected
(green): Device bound and switched online
(red): Device bound but still offline
(grey): Device not yet bound, or unbound
(red): Device bound but not found
(green): Device bound but not found
Net dialogue
(grey): Device still in database but could not be addressed; unbound; device changed;
possibly hard offline
(red): Device found; offline
(green): Device found; online

®
7.10.5 General settings/information on menu bar

7.10.5.1 Popup menu
Highlighting a device in the project or net dialogue and pressing the left mouse key calls up a popup me-
nu with which commands can be directed executed.
Popup menus:
Project dialogue Net dialogue
The selection of the popup menu may vary depending on the condition of the highlighted device.
7.10.5.2 Quick Info
With SecuriLanâ â/Project/Quick Info or via the popup menu Quick Info, it is possible to display an
overview of the highlighted device.

®
7.10.5.3 Properties
General information about the device, relating to the Project, Library or Installation, is listed by means of
SecuriLanâ â/Project (or Net)/Properties or the popup menu Properties.
7.10.5.4 SLTA interface

The setting for the COM port (serial port) of the SLTA is defined in the SecuriWin Setup.
To change the setting of the COM port, make a selection in the Setup/SLTA Port menu.
7.10.5.5 Path
The paths for the library and project database are preset by the SecuriWin setup. Use this command
only if you have saved your project regularly in another directory.
With Setup/Path, the standard paths for the library and the project can be changed.

®
7.10.6 Binding
1. Connect LAN terminal (E/F) to the LAN adapter board and mount this on the LAN A connection of the
MCB.
ê In principle, the binding can be performed from any LAN device!
2. Connect connecting cable to adapter board and SLTA adapter (Echelon).
3. Connect 9-pin interface cable to PC and SLTA adapter.
4. Connect SLTA adapter to power supply unit and switch on (yellow LED lights up briefly).
5. Press reset key on SLTA adapter (yellow LED lights up briefly).
6. Switch on supply on all MCB 02/02A
7. Start "Installation-Tool" program..
8. Open the SecuriWin *.mdb file under the menu File/Open or with the button (a).
The following desktop appears
SecuriLan not yet con-

nected
Indicates that more devi-

ces have been assigned
Only the LAN participants programmed in SecuriWin are displayed.

®
9. Start up SecuriLAN
- Select the SecuriLan/Net Connection/Connect or click on the button (b).

The following message appears on the screen:
ê Check connection between PC and SLTA adapter

ê SLTA adapter is switched off or power supply unit not connected
ê "SecuriLine Tracer" or "Panel SecuriLine" program still open
- Close the window with "OK"
- Click on button (b)
The following screen appears:
Device not bound
SecuriLAN is bound

®
10. Search for devices
â/Net/Search for devices menu or click on

SecuriLanâ (g)
If the following window appears:
ê Check SecuriLAN - SLTA connection

ê SLTA adapter is not connected
ê SLTA adapter does not make contact on the MCB; check terminal block and if necessary
change
ê Check LAN wiring on all devices (disconnect terminals; measure resistance); terminals E/F
may be connected to +24V
ê Check firmware IC 400 (neuron)
- Acknowledge message with "OK" and search for devices again with (g)
The following display appears:
After confirmation with "OK", the nodes found are integrated

®
- The devices found on the SecuriLAN now appear in the net dialogue on the right:
These devices have not yet been assigned.
Devices were
found
During searching and binding, all devices except for the FO repeaters and LCB 02 are automatically
switched "offline"
Important
FO repeaters must never be switched "offline", since otherwise the devices
which are connected after the repeaters can no longer be found!
The FO repeaters and the LCB02 must not be bound! They are displayed in the net list
as information for the installer, but only if they were searched for specially using the
Service Pin.
- By means of the menu "Setup/ Net List", it is possible to determine whether all devices or devi-
ces of the same type are displayed in the net dialogue.
In large projects, a better overview is obtained if only identical devices, such as those chosen in the
project dialogue, are displayed.
11. Devices which have not yet been found are searched for with the "ServicePin".

®
Select menu "SecuriLan/ Net/ Service Pin" or click on the button (h).
The following appears:
In the specificed time, the "ServicePin" on the device must be short-circuited.
Information
The Service Pin is marked with SERV on all devices. Exception: MCB 02/02A (+, see
Fig. 17, Section 7.6.3)
This message appears on the screen:
The desired device :

✘ is not connected to the LAN
✘ has no supply
✘ has no EPROM mounted
✘ EPROM is incorrectly inserted (polarity)
✘ is hard offline (see Troubleshooting, Section 7.10.9)
ê Eliminate error and then search for device again with the "ServicePin"
If there is insufficient time to reach the Service Pin on the device during the search time, the Service
Pin time can be increased:
Make a selection in the menu "Setup/Service Pin Time"
Usually, a screen showing the neuron information appears after the search with the Service Pin.

®
This table contains all important information on the respective device.

The most important information is listed below:
Neuron parameters:
Neuron ID: This number is unique throughout the world and is assigned only to this device
Model No.: If a device was correctly recognized, it has a 0 or 1. If it contains a -1, the device
could not be recognized (see Troubleshooting, Section 7.10.9)
Channel: The channel number is always 1 for all devices except for certain repeaters. The
number may not be changed.
Net parameters:
Node No.: This is the identification number of a device within the respective project. It may oc-
cur only once in the same project and may contain values from 1 to 126
Subnet ID: This must always have the value 1; if another value is entered, this should be
changed to 1 (see Troubleshooting, Section 7.10.9)
Current neuron status:

Online: Device has been switched online
Hard offline: Device has been switched offline (also see Troubleshooting, Section 7.10.9)
Soft offline: Device cannot be recognized by the software.
If a device is "hard or soft offline", the "Switch online" button is active and the device can be swit-
ched "online" again therewith.

®
Current router status

This part of the window is active only if FO repeaters are present on the installation and these have
been searched for with the Service Pin (RCV). Any FO repeaters switched "offline" can be switched
online again with "Switch repeater".
Important
FO repeaters may never be switched "offline" since otherwise the devices which
are connected after the repeater can no longer be found!
The FO repeaters must not be bound! They are displayed in the net list as informa-
tion for the installer, but only if they have been searched for specially with the Ser-
vice Pin.
Neuron flags:
Error: Device is not connected on the LAN
New node: The device is bound for the first time on the LAN
Local node: Not used at present
Integrated: Device is present on the LAN
Identification The existing MCU type is compatible with the SecuriWin version
MCU
The remaining information can be neglected at present.

- The table can be closed with "OK".
In the start screen of the installation tool, the newly found device appears in the net dialogue. Occa-
sionally, the screen is not refreshed. This can be rectified by changing to another device in the pro-
ject dialogue and back again to the preceding device.
Point 11 must be repeated for each further device which is still missing.
12. Assign devices:
- Click on devices which are to be assigned to one another, first in the project dialogue and then in
the net dialogue
/Installation/Assign" menu or assign devices using the

- Select "SecuriLan button (k).

®
The assigned device is removed from the net dialogue and is marked with (red) in the project
dialogue.
The remaining devices are assigned in the same way.
Devices bound;
offline (red)
13. Write data to net

The devices are now bound only in the database (mdb file). This binding information must now be
entered in the neuron, i.e. written to the net.
- In the project dialoue, click on
/Installation/Write data to net" menu or click on the

- Select "SecuriLan button (m)
The following messages appear in succession:
Information
This procedure may take up to 3 minutes depending on the size of the project.

®
- After the data have been written to the net and the devices have been switched online and initiali-
zed, they are marked with (green) in the project dialogue.
If all devices have not been switched online:

- Select the "SecuriLan/Installation/Switch on devices" menu or switch online using the
button (n).
14. Download ?
In the case of a new installation or when changes are made in a project, a download must be per-
formed after the binding.
- For download, see Section 7.11
15. Exit program

If no download is performed, the SecuriLAN can be disconnected from the devices.
/Net Connection/Disconnect" menu or click on the

- Select the "SecuriLan button (c)
- The installation tool is closed using the "File/Exit" menu

®
7.10.6.1 Online Auto Binding

Autobinding can be carried out if the neuron ID is entered in the project tool.
1. Enter neuron ID
Enter the neuron ID in "Device list/General" in the project tool:
Exit the window with "Close"

2. Convert bin file
3. Save project and exit project tool
4. Start installation tool and open project as described under Section 7.10.6 Binding, points 1- 11.

®
5. Carry out autobinding
- In the project dialogue, click on

- Start the autobinding using the menu "SecuriLanâ/Installation/Online Auto Binding" or popup
menu "Online Auto Binding"
The following messages appear in succession for each device which has been bound:
The devices already bound are continuously updated in the project dialogue:
The icon (grey) changes to (red or green)
After successful autobinding, the data are automatically written to the net and the devices are swit-
ched online.
- The devices for which the autobinding could not be carried out appear in the following list:
In the case of these devices, the neuron ID entry is missing in the project tool or the entry is incorrect.
• Missing neuron ID entry:
- The device can be highlighted in the project and net dialogue and can be assigned with the
button (k)
ê The entry is missing but can still be included in any subsequent autobinding
• Incorrect neuron ID entry:
- Correct entry in the project tool and reconvert bin files
- Carry out autobinding again
6. Download or exit program
Download: See Section 7.11 Download, points 10 - 12
Exit program: See Section 7.10.6, Binding, Point 15

®
7.10.7 Unbinding
Information
When the binding information in the project tool is deleted (menu 'Options/Remove
binding'), only the data in the mdb file are deleted. The devices (hardware) have not
yet been unbound.
They must always be unbound beforehand individually using the installation tool or by
means of autounbinding.
To unbind an individual device:

1. Select the desired device in the project dialogue
2. Select the menu option 'SecuriLan/Installation/Remove assignment' or click on the icon
3. Select the menu option 'SecuriLan/Net/Search for devices' or click on the button
The unbound device is displayed in the net dialogue window
7.10.7.1 Online Auto Unbinding

In contrast to autobinding, autounbinding can always be carried out, i.e. even if no neuron ID was ente-
red in the project tool.
1. Start installation tool and open project as described under Section 7.10.6 Binding, Points 1 - 9.
2. Carry out autounbinding
- Highlight in the project dialogue

- Start the autounbinding using the menu "SecuriLanâ/Installation/Online Auto Unbinding" or po-
pup menu "Online Auto Unbinding"
Information
With autounbinding, the entries of the address tables of all devices are set to 0 (zero).

®
Devices already un-

bound
Devices switched
offline (red)
Devices which are in the process of being unbound are marked continuously with (grey) in
the project dialogue.
3. Open net dialogue
- Search for devices with button (g)

All unbound devices are listed:
4. Check entries in address table

- Highlight device in net dialogue
- Open the "Node information" window using the menu "SecuriLanâ/Net/Node Info" or popup me-
nu "Node Info".
- The domain and address table is opened with "Address table...":

®
After the unbinding, the values "000..0" are usually entered in all lines of the address table.
However, if this is not the case, as in the example, they are set manually to the values "000..0" as
follows:
- Click on the "Delete" button
- If the question is answered with "Yes", all entries of this table are set to "000..0"
- Close the address table with "OK"
Information
The address table may be deleted only in the case of an unbound device. Otherwise,
the entire binding data will be unusable!

®
7.10.8 Rebinding in the case of LAN device or software replacement
Information
Important: The device which is to be replaced (possibly faulty/hardware change)
should not yet be removed from the installation!
1. Connect LAN terminals (E/F) to the LAN adapter board and mount this on the LAN A connection of
the MCB.
ê In principle, the binding can be carried out from any LAN device!
2. Connect connecting cable to adapter board and SLTA adapter (Echelon)
3. Connect 9-pin interface cable to PC and SLTA adapter
4. Connect SLTA adapter to power unit and switch on (yellow LED lights up briefly)
5. Press Reset key on SLTA adapter (yellow LED lights up briefly)
6. Switch on supply on all MCB 02/02A
7. Start "Installation Tool" program..
8. Open the SecuriWin *.mdb file (contains the binding data) under the menu "File/Open project" or
with the button (a)
/Net connection/Connection" or click on the

- Select menu "SecuriLan button (b).
The device which is faulty or can no longer be addressed is marked with (red)
10. The device which is to be removed or replaced should be marked in the project dialogue
- Select menu "SecuriLanâ/Installation/Remove assignment" or click on the button (l).
11. Remove the device which is to be replaced or which is defective from the installation.
Information
Important: Remove the device supply beforehand
- Mount new device in the installation, reconnect the supply and actuate "ResetPin".

®
12. Search for new device
- Select menu "SecuriLan/Net/Search for device(s)" or click on the button (g)

The net dialogue window is opened again
The old device (grey) and the new device (red or green) are displayed.
If the device cannot be found:
13. Search for the new device with the "ServicePin"
- Select menu "SecuriLan/Net/Service Pin" or click on the button (h).

- Short-circuit "ServicePin" on the device.
ê If the device is not found, the message "Error 404" appears
If the device cannot be found even after repeated actuation of the "ServicePin":
✘ Check whether the supply and the LAN are connected
- The desired device :

ê is not connected to the LAN
ê has no supply
ê has no EPROM or an incorrect EPROM
ê EPROM is incorrectly inserted (polarity)
ê is hard offline (see Troubleshooting, Section 7.10.9)
✘ Eliminate error
ê Actuate reset pin and service pin in succession and then search for the device again with
the "Servicepin"
If the device is found, the screen with the neuron information appears
14. Highlight device which is no longer assigned
- Select menu "SecuriLanâ/Net/Delete node " or select popup menu and click on "Delete node"
Highlight and
delete device
The device is removed from the net dialogue

15. Click on the new device first in the project dialogue and then in the net dialogue
- Assign to one another with the menu "SecuriLanâ/Installation/Assign" or with the button
(p).
- Further devices which were replaced are assigned in the same way

®
16. Write data to net

The devices are now rebound only in the database (mdb file). This binding information must now be
entered in the neuron, i.e. written to the net.
- In the project dialogue, click on
- Menu "SecuriLan/Installation/Write data to net" or click on button (m)

The procedure is the same as that described under Section 7.10.6 Binding, Point 13
Information
If the new device is an MCU or an SIB7x, a download must be carried out according
to Section 7.11.
REFFORMATVERBINDEN
17. Exit program

If no download is performed, the SecuriLAN can be disconnected from the devices.
For procedure, see Section 7.10.6 Binding, Point 15.

®
• Installation tool cannot be started (protection error message.. or Server . xx )

✘ The tool cannot be used under Window 3.11
ê Install Windows 95
✘ SLServer. is still open
ê Close server with "End task" (Ctrl+Alt+Del); this may only function at the third attempt
• Error 107; project cannot be loaded

✘ The description of the project in the project tool is > 255 characters (R01.01.00); from R01.02.00,
this is automatically dealt with
✘ Binding data incorrect
✘ Wrong project was opened and started up
ê Delete binding data in menu "Options/Binding/Remove" in the project tool, save project and
open in installation tool again
• Error 110; SecuriLAN could not be connected

✘ Check connection between PC and SLTA adapter
✘ SLTA adapter is switched off or power unit is not connected
✘ "SecuriLine Tracer“ or "Panel Analysis" program is still open
ê Stop LAN and start up again
• Error 115; local node (SLTA) could not be addressed

No devices found:
✘ Check connecting cable between SecurILAN and SLTA adapter
ê Adapter does not make contact / loose contact with LAN connection (possibly faulty); check
terminals
✘ Check LAN wiring on all devices (disconnect terminals; measure resistance); terminals E/F may
be connected to +24 V
✘ Check firmware IC 400 (neuron)
• Too many / twice the number of devices (according to LAN startup)

✘ Not all devices have as yet been bound
✘ Devices which have not been planned are connected to the LAN
✘ mdb file with wrong binding information was loaded, e.g. the file of the test system with the same
system configuration but other hardware components (neuron ID)
ê Remove binding information in "SecuriPro project"
ê or delete the excess devices after starting up the LAN (see Section 7.10.8, step 14)
• Error 118; node could not be deleted
ê Search for devices with button (g); the net dialogue window is opened
ê Highlight device which is to be removed
ê The device can be removed using the menu "SecuriLanâ/Net/Delete node" or with the popup
menu "Delete node"

®
• Error 125; cannot search for devices

✘ Devices are no longer connected to the LAN
✘ Check whether connecting cable and adapter are connected
ê Search for devices again with button (g)

If the same message appears again:
ê Actuate reset pin and then SERV pin on the device (short-circuit)
ê Search for devices again with button (g)
• Error 128; error on integration of the nodes

✘ Node No. is > 127, subnet ID > 1 or node No. is present twice
ê Close installation tool and restart Windows and then installation tool
ê Open project and start up LAN
ê Open menu "SecuriLanâ/Neuron internal (SLTA)"
ê The entry for the node No. of the SLTA should be 127
If this node No. is incorrect, it should be set to 127
Check the node No. and subnet ID for all devices:
ê Highlight device in the project dialogue
ê Open with button (d) or popup menu and click on "Node Info" to open the "Node In-
formation" window
ê Check node No. and subnet ID and note for each device
If the values entered are incorrect, i.e. node No. is > 126 (127 is reserved for SLTA), subnet ID is
> 1 or a node No. occurs a second time:
ê Set subnet ID to 1
ê Set node No. to 1 or, if known, enter the correct node No.
ê Close "Node Information" window with "OK"; the node No. and subnet ID are corrected
Once all devices have been checked, write the data to the net as in Section 7.10.6, Point 13.
• Model No. -1
If the following message appears in the "Neuron ID" window, the device was detected as being pre-
sent but could not be reached in terms of hardware or software:

®
ê Actuate "Reset" pin and then "SERV" pin on the device (short-circuit)
ê Search for device again with "ServicePin"
If Model No. -1 still appears:
1. Disconnect SecuriLAN; exit "Installation Tool" program
2. Disconnect the LAN terminals (E/F) on the relevant device (disconnect from remaining LAN)
3. Connect LAN adapter board to the LAN1 connection and connect to the SLTA
4. Actuate reset pin and then SERV pin on the device (short-circuit)
5. Start "Installation Tool" program and open mdb file again
ê Usually, the device can be activated again in this manner
7. Reconnect the device to the remaining LAN participants on the LAN (without switching off the
LAN).
8. Search for the remaining LAN participants
9. Select menu "SecuriLan/Net/Search for devices" or click on the button (g)
If it was not possible to activate the device again individually, it should be unbound from the project
(see Section 7.10.8 Rebinding) and replaced by a new one
• Error 404; no service pin message obtained

ê Search for device again with "Service Pin"
If the device cannot be found even after repeated searching:
✘ Check whether the supply and the LAN are connected
The device searched for:
ê is not connected to the LAN
ê has no supply
ê has no EPROM
ê has an incorrectly inserted EPROM (polarity)
Eliminate error
ê Actuate reset pin and service pin in succession and then search for the device again with "Ser-
vicepin"

®
• Device is hard offline

LEDs on PIM, PCM or MIC all light up statically and the display on the MIC shows all dots ( ■ )
ê Actuate reset pin on the corresponding device
ê Highlight device in project dialogue, click on popup menu and click on Node Info
ê Switch button from hard offline to online and close window with "OK"
ê The MIC display becomes bright and LEDs begin to flash after a few seconds
The device is still hard offline:
1. Highlight device in the project dialogue and unbind with button (l)
2. Remove device supply
3. Remove firmware and replace by firmware of another device; e.g. for the MIC, use the firmwa-
re of a PCM, PIM, etc.
4. Switch on device suppy and then switch off again
5. Remove external firmware and use original firmware again
6. Switch on device supply
7. Search for device with button (g)
8. Highlight device in the project dialogue and net dialogue and assign with button (k)
9. Write data to net as described under Section 7.10.6 Binding; Point 13

®
7.11 Download
The download serves for writing the bin file data to the RAM (IC 503) of the MCU and the SIB 7x. This
function is possible only if the MCB 02/02A and the SIB 7x have been prepared for the download (see
Section 7.6.3.2) and the system is bound (see Section 7.10.6 Binding).
Information 1
The download is permitted only in mode 0 (IDLE state). Before the download, the
mode is checked and the system is automatically brought to mode 0 if it is not in this
state. After the download, the system is returned to the desired state.
The time for the download per MCU is now only 4.5 minutes. The baud rate of the
SLTA must be set at 38400 bps so that a fast download is possible (see Section
7.10.2, Setting the baud rate for SLTA).
Information 2
From R 01.04.00, the installation tool checks, before a download, whether valid
MCU types are present and whether they are compatible with the project. If the MCU
types agree with the project, a download can be performed. In the event of invalid or
incompatible types, the message 'Error 512: No valid MCU type found' appears (see
Section 7.11.1 ,Troubleshooting) and the procedure is stopped.
Information 3
From R 01.04.00, the firmware version for highway and point-to-point devices is
checked during the download and is displayed as a list. The versions can also be
requested via the menu "SecuriLan/Firmware version".
If the system was bound immediately before the download, i.e. the LAN is still switched on, it is possible
to continue with step 10. Otherwise, the LAN is started up as follows:
1. Connect LAN terminals (E/F) to the LAN adapter board and connect it to the LAN A connection of
the MCB.
In principle, the download can be performed from any LAN device!
5. Press reset key on SLTA adapter (yellow LED lights up briefly)
6. Start "Installation SecuriLan" program..

with button (a)
- Select menu "SecuriLan/Net connection/Connection" or click on button (b).

®
Devices bound;
online (green)
All devices have already been assigned, i.e. bound
Information
Devices must be switched on for the download.
9. Highlight a highway device or the whole project in the project dialogue

If only an individual device is highlighted, only the profile of this device is downloaded. If "Project:
xyz" is highlighted, a download is performed for all highway devices.
10. Start download
/Profiles and modes/Download profile(s)" or click on the

Select menu "SecuriLan but-
ton (p)

®
- Click on the "Download profile" button

The following window is opened:
Depending on the state of the system, it is brought to mode 0 before the download and is switched
back to the current mode afterwards.
- Activate the desired function button:
Download only different data:
Only those parts of the bin file which do not agree with the data already loaded will be downloa-
ded. A partial download is performed if changes were subsequently made in the project.
Download all data:
The entire bin file is loaded into RAM.
If a system is being put into operation for the first time or an upgrade to a higher release version
is being performed, a complete download should always be carried out.
- Click on the Next button
The operating states are changed in succession, the MCU types and the firmware versions are
polled, the profile or profiles is or are loaded and then the profile or profiles is or are checked and
the system is started up again depending on the results.

®
In the event of a complete download, the following screen appears:
Information
A complete download takes about 4.5 min per MCU if the SLTA was set at a baud
rate of 38400 bps (see Section 7.10.2).
In the current window, the state of the download is indicated by the following information:
Neuron ID: This number is unique worldwide and is assigned only to this device
Filename: Name of the current bin file
File size Size of the total bin file which has been downloaded
Last error Error display with status "Error"
File index: Size of the data already transmitted
Status: Status of use. The following statuses are possible:
- Busy: Normal status during the download
- Error Download could not be performed or could be performed only to xx %
Process: Indicates the downloaded data by means of a moving bar
Transfer run- Transmission is in progress
ning:
The download can be stopped at any time with "Stop". The "Install" window is displayed again.

®
The download (and possibly the startup) is terminated if the following message appears:
The mode in which the system exists after the download is displayed.
- Acknowledge the window with "OK"
11. With "Back", the program returns to the start screen of the "Installation Tool".
If you have carried out only a download without automatic startup of the system, continue with Sec-
tion 7.12, Startup from PC.
12. Exit program

Once the data for all MCU have been downloaded, the "Installation Tool" can be closed as descri-
bed in Section 7.10.6, Point 15.

®
• Download not possible

✘ Device is not switched "online"; data have not been written to the net
✘ MCU not highlighted
✘ No RAM present
ê Disconnect power to MCU, pull out EPROM (IC 503), install RAM, reconnect jumper according
to Section 7.6.3.2 and connect supply again
✘ Bin and mdb files have different filenames, do not agree or are not present
• Download aborts (error message e0110008)
✘ RAM still contains incorrect data
ê Switch off supply (220V and battery) and pull out Li battery jumper (J800) for about
10 seconds; switch on supply again, connect battery and insert jumper; perform download
✘ Bin file is not correctly converted
ê Convert relevant MCU in SecuriWin again
• Error 405, highway timeout during download

✘ Pull-up resistor over IC 401 is not soldered on (old MCB circuit boards)
✘ Neuron firmware IC 400 is incorrect
✘ Subnet ID is > 1; node No. is > 126
• Error 430, profiles cannot be opened

✘ Device not yet bound
• Error 512; no valid MCU type found

✘ The MCU types found are not compatible with the planned data
From Release 01.04.00, only MCB 01/02 and MCB 01A/02A can be used for operating a system
with one or more MCUs. At least one MCB 01A/02A must be present per system.
ê Disconnect SecuriLAN and exit "Installation Tool" program

ê Replace MCB

®
7.12 Startup from PC (installation tool)

7.12.1 Introduction
With the installation tool, a completely bound system can be started up from PC in the global or local
mode. Problems and errors encountered during the startup or mode change are communicated in a se-
parate dialogue window and the startup may be aborted.
7.12.2 Start screen of the installation tool for startup from PC
The start screen illustrated shows the state after opening of the project and starting up of the SecuriLAN
or after the binding and download.
c A q
Legend:
A) System bound and switched online
c) SecuriLan started up
q) Startup from PC
7.12.3 Icons used
(grey) Mode 0: Idle (download profile)
(dark red) Mode 1: Init (test profile)
(red) Mode 2: Lanstart (start SecuriLan)
(dark green) Mode 3: Linestart (start SecuriLine)
(light green) Mode 4: Run (normal operation)

(red) All modes: Detail error
(red) All modes: Error on this device

®
7.12.4 Starting up the system in the global mode

If the system was bound immediately before the startup from PC and a download performed, i.e. the
LAN is still switched on, it is possible to continue with step 11. Otherwise, start up the LAN as follows
1. Connect LAN terminals (E/F) to the LAN adapter board and connect this to the LAN connection of
the MCB.
In principle, the startup from PC can be performed from any LAN device!
5. Press reset key on SLTA adapter (yellow LED lights up briefly)
6. Start "Installation Tool" program

with the button
- Select menu "SecuriLan/Net connection/Connection" or click on the button (b) .

After the SecuriLan has been started up, the project dialogue window containing the devices which
have been bound and switched online appears:
9. The devices can be started up in the global mode (all) or local mode (individually):
• Global mode: In the project dialogue, Project: xyz must be highlighted
Information
Global mode:
The system must be completely bound so that it can be started up from PC!
Dip-fix/DIL switch 3 on the MCB may not be closed.

®
10. Open the window for "Startup from PC" with the button
The following screen showing the current mode of the MCU/SIB appears:
B C D E F G H J K
Legend:
B) MCU and SIB operating state visually G) Current operating state

C) Name of the device according to project H) Mode switch
D) Unique neuron ID of the device J) Starting the mode change
E) Node number of device K) Polling the current operating state
F) Device position according to project
Any errors are reported with an error code and can be displayed as plain text using the "Detail" but-
ton. Also see Section 7.12.6, Error indications during startup from PC. It may not be possible to
continue the startup before the errors have been eliminated.
If the system is started up after the binding /download, it is in mode 0 (grey/idle).
If the system has already been put into operation, mode 4 (light green/Run) should be displayed.
However, the pointer of the mode switch is at position 0 (idle).
11. Click on the "Start" button if the devices are not already in mode 0
All devices are switched to mode 0 (idle).
12. Drag mode switch with the mouse to "Mode 1 INIT"
The profiles are initialized.

®
During switching, the following screen is active:
The operating states are changed continuously per device and displayed on screen.
The display changes to dark red and Init.
13. Drag mode switch with the mouse to "Mode 2 LANSTART"
The LAN devices are started up.
Missing devices are indicated as an error. See Section 7.12.6.
The operating states change to light red and Lanstart
14. Drag mode switch with the mouse to "Mode 3 LINESTART"
The lines are addressed. After the addressing, no polling is carried out as yet.
The addressing takes [10 seconds to switching on + number of detectors * 1.5 sec].
For error indication and error elimination, see Section 7.12.6.
Once all lines have been addressed, the operating states are displayed in dark green and Linestart
is shown.
15. Drag mode switch with the mouse to "Mode 4 RUN"
The MCUs are switched to the operating mode (Run).
The devices are started up in the order in which they are listed in the project dialogue.
The operating states are displayed in light green and Run is shown if all devices have been started
up.
16. The startup application is exited using the "Close" button.
7.12.5 Starting up the system in the local mode

If an MCU on a system in the normal mode is to be switched locally to mode 0 and then started up again,
steps 1 – 8 of the preceding section should first be performed.
If the system was bound immediately before the startup from PC and a download performed, i.e. the
LAN is still switched on, it is possible to continue with step 9.
1. Steps 1- 8 Connect LAN and startup, see preceding section
10. The devices can be started up globally (all) or locally (individually):
• Local mode: In the project dialogue, the device which is to be started up individually must be
highlighted

®
11. Open the window for "Startup from PC" with the button
The following screen showing the current mode of the device appears:
If the system is started up after the binding / download, it is in mode 0 (grey/idle).
If the system has already been put into operation, mode 4 (light green/Run) should be displayed.
However, the point of the mode switch is at position 0 (idle).
12. Click on the "Start" button if the device is not already in mode 0.
The device is switched to mode 0 (idle).
13. Drag mode switch with the mouse to "Mode 1 INIT"

The profiles are initialized.
For error messages, see Section 7.12.6
The display changes to dark red and Init.
14. Drag mode switch with the mouse to "Mode 2 LANSTART"
The LAN devices are started up.
Missing devices are indicated as an error. See Section 7.12.6.
The operating state changes to light red and Lanstart
15. Drag mode switch with the mouse to "Mode 3 LINESTART"
The lines are addressed. After the addressing, no polling is carried out as yet.
The addressing takes [10 seconds to switching on + number of detectors * 1.5 sec].
Once all lines have been addressed, the operating states are displayed in dark green and Linestart
is shown.
16. Drag mode switch with the mouse to "Mode 4 RUN"
The device is switched to the operating mode (Run).
For error indication and error elimination, see Section 7.12.6
The operating state is displayed in light green and Run is shown if the device has been started up.
17. The startup application is exited using the "Close" button.
18. Highlight next device which is to be started up locally and repeat steps 11 – 18 or exit installation
tool application

®
7.12.6 Error indications on startup from PC

If errors are found during startup, they are displayed on the screen and shown in plain text in a separate
dialogue box.
This section shows only the way in which the errors are displayed. Specific error messages are also
shown.
The errors are also listed in Sections 7.8.4 to 7.8.4.5.
• General aspects of error indications

If an error is found in a stage during the startup, an error list containing the error codes and the brief
description appears. All devices which have an error are marked with in the window.
Each error can be displayed individually by clicking on the "Details" button:

®
The "Server error" window shows the details for each error:
Ø Error code: Analogous to error list in Sections 7.8.4 to 7.8.4.6
Ø Mode: Mode in which the error occurs
Ø Date/Time Current date/time when the error occurred
Ø Node ID: Node number of the device on which the error was found
Ø Description: Brief description of the error
• Error 406 in mode 1 (Init)

During change to mode 1, the following error message appears: "Error 406: Command has been
rejected (device number x)". The device x could not change to mode 1.
After the error message has been confirmed with "OK", the faulty MCU is highlighted with .
✘ Dip fix 2 (local mode) in device x is closed

ê Open dip fix 2
ê Drag mode switch with the mouse to position 0 (idle) and click on the "Start" button. All devices
are switched back to mode 0.
ê Set mode switch to position 1 (Init) again and click on "Start". All devices are switched to mode
1. The further startup should be performed according to Section 7.12.4

®
7.13 Big Map

7.13.1 Introduction
With the Big Map, the MIC of a system planned as a first one can be simulated and operated on the PC.
The operation is performed, as in a real MIC, under menu control via key and code input. Only the lamp
test function is not possible via the Big Map.
7.13.2 Start screen of Big Map
l a c g h
b d e f i k
Legend:
a) Switching SecuriLan on / off g) Display for list polling (information)

b) Settings for event memory h) Big Map menu (analogous to MIC menu)
c) Start recordings for event memory i) Key field for key and code input
d) Stop recordings for event memory k) LED indicators and labelling (analogous to MIC)
e) Trigger test alarm by input DZ/DA/Det l) Recording of the event messages
f) Big Map display (analogous to MIC display)
7.13.3 Big Map operation
1. Connect LAN terminals (E/F) to the LAN adapter board and connect this to the LAN A connection of
the MCB.
In principle, the Big Map can be started up from any LAN device!
5. Press Reset key on SLTA adapter (yellow LED lights up briefly)
6. Start "Big Map" program.

®
7. Open the SecuriWin *.mdb file) under the menu "File/Open project" or with the button
8. Set Com port via "Setup/SLTA" menu. The default setting is the same as the selection in the Secu-
riWin setup
Ø Select "SecuriLan/Net connection/Connect" menu or click on the button (a).

The SecuriLan is started up and the devices are searched for. The following message appears:
After the window has been acknowledged with "OK", the data highway are started up and the sy-
stem status read. The conditions under which an LED is not indicated after startup are shown:
The Big Map start screen appears. The window of the event messages is still empty.
10. Set size of event memory.
The setting can be made only if the recording of the event memory is stopped.
Ø Stop recording with button

Ø Open "Events/Settings" menu. The following window appears:
Ø Input max. number of telegrams which are to be recorded. (Maximum value = 1,000,000)
Ø Select display of the recording for the telegrams in the event memory:
Plain text: Only time, date and plain text appear in the event memory
Plain text and binary: In addition to time, date and plain text, telegrams are recorded as code in
the event memory

®
11. Start recording for event memory again with button
12. The key/code must be input for operating the Big Map
Ø Press the right mouse key at any point in the MIC73x window (except in the field for the display).
In the context menu, select the "Key on" command to activate the key switch.
In the context menu, select the "Input code" command.
A window with the code keyboard appears in the MIC73x:
Ø Input code with the mouse or via PC keyboard and finish with the "Asterisk" key.
The access authorization is checked. If the code is correct, the MIC menu appears.
Ø In the event of an incorrect code input, the following message appears:
Input code again and finish with "Asterisk" key.
13. The Big Map can now be operated via the menus
Ø By clicking on the menu option, the submenus, if present, are displayed or the command exe-
cuted.
Ø In a submenu, it is possible to change one level higher with the button or directly to the top
level with .
Ø If a menu option cannot be performed in Big Map, the following message appears:

®
14. Trigger test alarm via the Big Map

Ø Via the menu "Test / Event triggering", a window "Triggering settings" is opened in which the
detection area/detector zone/detector number can be entered and the events alarm, fault and sa-
botage can be selected for which the test alarm is to be triggered:
Ø The command is sent using the "Activate" button

Ø Further alarms can be sent by overwriting the "Activation settings" and activating again.
Ø The window can be closed again with "Cancel"
Ø The triggered alarm or alarms is or are displayed on the Big Map and in the MIC display and the
LED on the system. Via the Big Map menu, the alarms can be reset with "Reset system" or by
acknowledging the individual alarms.
15. Stop recording of the event memory and save
Ø Stop recording with the button

Ø Via the "File / Save as" menu, the recordings of the event memory which have been made so
far can be saved.
Ø The file extension is "*.ene"
16. Disconnect SecuriLan with

Ø You will be asked whether the event messages are to be deleted

®
7.14 RevMoni and RadioView (one-man detector tester)

7.14.1 Introduction
The RevMoni software is used for checking the installation and correct planning of the detectors and for
maintenance of a SecuriPro system.
The following tasks can be performed with RevMoni:
Ø Listing of the maintainable detectors:
All detectors of the system are listed by zones and areas.
This makes it possible to check all customer texts, the assignment of the detector type and the
maintenance criterion.
Restriction: Only maintainable detectors are listed.
Ø Checking of the cabling during commissioning:
With the aid of the maintenance messages by radio, correct positioning of the detectors can be chek-
ked. Consequently, wiring errors can be recognized.
Ø Maintenance with RadioView:
With the aid of maintenance messages by radio, it is ensured that the correct detector was main-
tained. The maintenance messages are correctly sorted, i.e. are listed inthe triggered sequence and
can be printed out.
Ø Maintenance without RadioView:
With the aid of report recording, the PC software records the maintenance. The intermediate state is
shown on the PC. The operation of the maintenance circuit can be triggered as usual via the MIC,
from another PC with Big Map or from the RevMoni program.
7.14.2 Description of the devices
In order to use the RevMoni program, the following devices are required:
• PC with two serial ports; two 9-pin interface cables
• SLTA incl. connecting cable
• Radio modem incl. connecting cable (tailored to the respective radio model)
• Radio View
• 2 radio units ZODIAC P2200, Motorola GP 340 or Maycom MH 446
• Mains adapter EGSTON, DC12V
Information
A case with the required devices is provided per radio model. The radio modem is specially
tailored to this radio.
The radio modem FM2, RadioView and radios can be omitted if it is not possible to use radio, e.g. in ba-
sements with air-raid shelters. The maintenance can be switched from an MIC. The recording via the PC
nevertheless operates.
7.14.2.1 PC with two serial ports
The PC or laptop used must be equipped with two serial ports.
Com port 1 is preset for the SLTA and Com port 2 for the radio modem (depending on the choice of the
Com port for the SLTA in the SecuriWin installation).
7.14.2.2 EGSTON mains adapter
The EGSTON power unit supplied (DC 12V / 1A) is used on the one hand for charging the battery in
RadioView and on the other hand for operating the radio modem FM2

®
7.14.2.3 Radio modem FM 2

The radio modem "FM2" is specially tailored to the respective radios of the "RevMoni" software and is
connected to the serial port of the PC by an uncrossed, 9-pin cable.
The radio modem does not have its own voltage supply and should be operated with the mains adapter
supplied (DC 12V "EGSTON").
7.14.2.4 Radio View
d
a c
b
Legend:
a) On / off key / background lighting c) Send key / Refresh
b) Send keys d) Display
Ø Charge batteries:
Before commissioning of the Radio View, the batteries should be charged. For this purpose, the po-
wer unit supplied should be connected to the RadioView charging jack. The charging time is about
12 hours. The red LED next to the charging jack indicates that charging is in progress. During char-
ging, the charge status can be checked but the RadioView cannot be permanently switched on.
Ø Connect Radio View:
See next Section 7.14.3
Ø Switch on Radio View:

✸" (asterisk) until the following appears in the display:
Switch on RadioView by pressing the key "✸
On switching on, the battery voltage under load is measured and is shown in the form of a bar.
If the battery is flat, "BATT EMPTY" is displayed on switching on. If the voltage falls below the mini-
mum battery voltage, the device switches off automatically.
After a successful switch-on routine, the RadioView is ready for receiving data telegrams.

®
Ø Radio interruption:
If there is a radio interruption, RadioView indicates it acoustically and periodically displays the text
"POOR RECEIVING AREA", followed by the previous current display.
Radio interruption is indicated if no valid telegram has been received for about 20 seconds (e.g. if the
maximum range of the radios has been exceeded).
In this state, the 4 send keys F1, F2, F3, "new" are not active.
Ø Receiving a data telegram:
On receiving a valid and error-free telegram, the latter is displayed and is indicated by a beep tone.
In the event of faults in the radio channel or poor radio reception, telegrams containing errors may be
transmitted. These are indicated by a double beep tone. As a result of this, individual characters can
be displayed only incompletely, if at all.
The situation can be remedied by searching for a better receiving area.
Ø Sending a data telegram:
With the keys F1, F2, F3, "new", the predefined telegrams are transmitted to PC. Sending is confir-
med with a beep tone.
Ø Display illumination:
✸" (asterisk). The il-
The background illumination is switched on and off by briefly pressing the key "✸
lumination switches off automatically after about 2 minutes.
Ø Switching off:
✸ " (asterisk) until "POWER OFF" appears on the display.
Press the key "✸
Ø Reset:
If it is no longer possible to switch off the device, a software reset can be performed by connecting
the charger supply.
A hardware reset is also possible: For this purpose, the device has to be opened and the jumper
"Batt On" next to the battery must be removed.
7.14.2.5 Transceivers
At present, the transceivers of the brands ZODIAC P2200, Motorola GP 340 and Maycom MH 446 can
be used. The following is applicable for all devices (note initialization for Maycom):
Ø Settings:
ØBoth transceivers must be set to the same channel.
ØThe "VOL" regulator should be set to the 12 o'clock position and "SQ" to the 9 o'clock position.
ØA noise must be audible in the loudspeaker of the transceivers
Ø Send check:
With the RevMoni PC software running and the status message "Connecting RadioView ..." in the
"Message Window", sending of the telegram can be heard every 2 seconds (every 10 seconds in
normal operation)
Ø Initialization for Maycom MH 446 during operation with modem:
Ø Keep UP and SC keys depressed simultaneously and switch on the device
Ø "Act t59" appears on the display. Press FUNC and hold; press UP key until TSQ disappears from
the display.
Ø Set channel with UP/DN

®
7.14.3 Connection of the devices

Diagram:
Detectors
Bus SecuriLAN SecuriLine
MCU
;
SLTA
Protocol printer
6
: ;
Radio units
Radio modem
„RadioView“
Service-LapTop
Fig. 26 Overview of RevMoni
7.14.3.1 Connect radio set and Radio View

1. In the case of the Zodiac and Maycom radio sets, insert the spiral cable of Radio View into the
jacks"MIC / SPK". In the case of the Motorola model, the special cable is screwed on sideways.
Ø RadioView and radio set must be completely charged to ensure optimum duration of use.
2. ✸" (asterisk). Keep the key depressed until the display
Switch on RadioView by pressing the key "✸
shows "RadioView Version....".
3. On the radio set, set the regulator "VOL" to 12 o'clock position and "SQ" to 9 o'clock position.
7.14.3.2 Connect radio set and radio modem to PC

1. Connect 9-pin interface cable to "COM-Port 2" * of the PC and to the radio modem FM2
* The Com port connections for the SLTA and radio modem can be changed via the "System opti-
ons" menu
2. In the case of the Zodiac and Maycom radio sets, insert the spiral cable of the radio modem into the
jacks "MIC / SPK". In the case of the Motorola model, the special cable is screwed on sideways.
3. Connect supply cable of the radio modem laterally to the jack - + on the radio set
(only Zodiac and Motorola)
4. Connect supply unit (EGSTON) to the radio modem
5. On the radio set, set the regulator "VOL" to 12 o'clock position and "SQ" (not present in Motorola)
to 9 o'clock position
6. Check whether both radio sets are set to the same channel

®
7.14.3.3 Connection of SLTA to PC

1. Connect LAN terminals (E/F) to the LAN adapter board and connect this to the LAN A connection of
the MCB.
In principle, the operation of the RevMoni can be carried out from any LAN device!
3. Connect 9-pin interface cable to "COM-Port 1" * of the PC and to SLTA adapter
* The Com port connections with the SLTA and radio modem can be changed via the "System opti-
ons" menu
4. Connect SLTA adapter to power unit (Echelon) and switch on (yellow LED lights up briefly)
7.14.4 Start screen (available windows during revision)
a b c d f g h k i
e
Legend:
a) Create new revision project f) RadioView Debug window (help tool)
b) Open existing revision project g) RadioView brief information window
c) Start up RevMoni h) Main operation window
d) Exit/stop the revision (recordings) i) SecuriPro Logger (help tool)
e) Print the revision log k) Window for alarm/fault during revision

®
7.14.5 Operation of the RevMoni

7.14.5.1 Overview
Start
programm
A:
Selection from
Menu + Toolbar
Create new Load existing

Load existing
Revision project Revision log
Revision project
(Recording) (A:)
(A:)
Ready for revision/

View and print View and print
Create and edit
report report
joblist
in case of errors
Start
recording with
password check
Logger: Save and print
Viewing of the
of the telegrams
telegrams
in case of errors
Run: Display of alerts:
Revision (Sabotage, alarms,
recording faults)
long time with

no error
RadioView
debug window
Stop run /
interrupt run:
Save recording?

®
7.14.5.2 Create new revision project

If a revision project has never yet been created for a system, it must first be produced.
In large systems with many detectors, this may take up to 15 minutes. It is therefore expedient to create
the revision project in advance.
For this purpose, the project must be converted in the project tool. The "*.mdb file" and the "*.p01 file"
must be in the same directory.
1. Start "RevMoni" program
2. Open menu via "File / Create New Revision project" or button

The "System Options / SecuriLAN" window appears.
3. Click on "Search" to select the "*.mdb file" via the project path.
Ø The "*.mdb file" and "p01 file" are entered in the "database" and "usertexts" fields.
Ø In the information bar at the bottom edge of the window, the display changes from "Error, not all
Files are loaded" to "OK, all Files are loaded"
4. The path of the revision data is displayed in the "System Options / General" window.
The "FullRev.prj" file is in the subdirectory "RevisionData". The "RevisionData" directory is auto-
matically created in the path which was selected in the "SecuriLAN" window.
The options, the paths of the names and the last revision database are saved in the file "Full-
Rev.prj". It is the so-called "Revision project".
Ø If it is wished to repeat a revision with the already created job list, it is only necessary to open the
"Revision".prj file.
Ø If several revision projects are created in the same "*mdb file", the name will differ from "Full-
Rev.prj"; e.g. Vollrevision.prj, TeilrevisionXY.prj, etc.

®
The individual recordings of revision sessions are also present in the "RevisionData" directory, e.g.
"FullRev-26_05_99-0.REV".
Ø If the recordings are repeated on the same date, the file is automatically incremented, e.g. "Full-
Rev-26_05_00-1.REV"
Ø If it is wished to analyze a revision again and/or print it as a report, the corresponding "Revisi-
on.REV" must be opened.
5. In the "System Options / RadioView" window, the setting of the Com port for Radio View, as set in
Section 7.14.3.1, is visible. The setting can be changed if necessary.
6. The revision list is created by clicking on "OK"
Ø In large systems with many detectors, this may take up to 15 minutes.
The complete list of all detectors which can be switched during revision is automatically compiled; i.e.
detectors of a zone which have a "revision slot".
The list can be viewed sorted by zones or by detectors by means of the drop down arrow. Thus, the
planned customer texts can be checked and a quick overview of the system is obtained.
7. For further procedure, see Section 7.14.5.3 , Point 4

®
7.14.5.3 Opening an existing revision project
1. Start "RevMoni" program

2. Open menu via "File / Load existing Revision project" or button
The "System Options /General" window appears
The following options can be selected:

• "Create a new revision project"
Not active at present.
• "Open an existing revision project"
This option is recommended if a revision list has already been created and if the mdb file has
not been modified since.
• "Open the last revision project"
The last revision project (since the last opening of this program) is opened.
• "Open an existing revision database (to show and report)"
The revision recordings are opened. The report can be printed again.
3. Select option "Open an existing revision project" and click on "OK"

The next window "System Options / (General, SecuriLAN, Radio View)" is opened.
Incorrect path data can be changed or the path data can be accepted with "OK".
The revision list is loaded, and the windows "Automatic creation of the revision list" and "Next revision
step" appear.
4. Click on "Edit job list" button
In the "Job No" column, it is possible to define the sequence in which the listed objects appear on
RadioView under the menu option "List" and can be switched during revision.
The objects without a job number ("NO") are not shown on RadioView but can still be operated from
the PC.
If a radio is used with the RadioView, it is advisable to define the job list according to the actual loca-
tions
Both individual detectors and whole zones can be selected.

®
Ø In the "Object" column, double click on the detector or the zone which is to be switched first du-
ring revision.
In the "JobNo" column, the corresponding detector or zone is allocated job number 1.
Ø Select next detector/zone for the job list; repeat until all detectors/zones are defined for this list.
In large systems, it may be expedient to define several smaller job lists, i.e. to create revision pro-
jects. This makes it possible, for example, for individual areas of a building to be separately main-
tained. For this purpose, a new revision project should be created under a new name under the
same mdb file.
Particularly in the case of intrusion alarm systems, the detectors which switch on/off continuously
(e.g. motion detectors) must be switched individually during revision. Otherwise, it may be difficult
to switch back a whole zone from revision to the required state.
7.14.5.4 Starting the revision recording
1. Start RevMoni by clicking on the button
2. Input code for installer or for any operator
The access is protected by the installer code and a freely chosen further code. The ident "00" for the
installer code has already been allocated and cannot be modified.
If the code test is negative, access is denied. The process can be repeated by clicking on the "Run"
button again.
3. Start the server by clicking on the "Start Server" button
During the server startup (background program for LAN access), the PC should not be operated (e.g.
do not click with the mouse), since otherwise error messages may appears from the server itself.

®
If the process becomes stuck for a long time, it can be ended with "Stop".
After 30 seconds without a change, the status bar shows an indication from the timeout monitor. In
rare cases, it is necessary to exit the "SLSERVER.EXE" process via the task manager or even to re-
boot the PC.
7.14.5.5 Switch detectors / zones to revision
If the start process has proceeded smoothly, the "SecuriLON Server Access" window is closed after the
server has been started, and the main operation window "Next Revision Step" automatically appears.
The following entries are present in the function list:

• "RevTime"
The time of the first active revision message of the zone/detector is displayed.
• "Object"
Listing of the detectors/zones by "Area/Zone/Detector number" or "Area/Zone/--"
• "Type"
Type of detector.

®
• "Text"
Detector text/zone text
• "Status"
"REV" display if the detector/zone is switched to revision
• "Send"
Button for starting the revision circuit.
The button is active only if an object is selected in the grid (list) by clicking with the mouse.
The function list serves for viewing the detectors switched to revision, but revision switching opera-
tions can also be performed via this form.
Ø The revisions can be switched on/off with the "Send" button RadioView, via the MIC menu or
with the BigMap (on a PC other than RevMoni).
Ø Any number of detectors/zones can be switched to revision via the active window.
(During switching with RadioView, only one revision switching operation is active at a time. If,
for example, a zone has already been switched to revision with the RadioView indication and
control map and it is desired to switch the next group to revision, the first revision switching
operation of the first group is first automatically switched off.)
1. In the function list, click on the detector/zone which is to be switched to revision.
2. The telegram is sent using the "Send" button.
3. Click on detector/zone for which the revision is to be switched off and transmit the command with
"Send".
7.14.5.6 Control window of RadioView on the PC
After the server has been started up, contact with the "RadioView“ indication and control map is also
established and a further window for the current operating state is displayed:
Except for the bottom display line, the display in the active window "RadioView Message" agrees with
that of "RadioView" in the "Run" menu.
• Upper part of window:
The detectors which have triggered a revision message are displayed. In each case the last
message is displayed.
Ø In the first line, the detector number and the status message "Active" or "Passive" are dis-
played; i.e. if the detector is switched on or off. This is followed by a number which reveals
how many detectors have already been revised in the selected zone. (1/11 = 1 detector of
11 was revised)

®
Ø In the second line, the detector type is shown.

Ø The third line shows the customer text of the detector.
Ø In the fourth line, the zone text is displayed.
• Bottom part of window:
Exceptional messages are displayed in the lower window.
• Information displays:
Ø "Key pressed"
This display makes it possible to check the connection between RadioView and the PC. As
soon as a key on RadioView is pressed, for example the following information is obtained:
"Key pressed: 1 (11) [7]
The key 1 (left key) of RadioView was pressed. The number in square brackets is a conse-
cutive number to enable repeated pressing of the same key to be detected.
Ø "RadioView Type"
The information about the RadioView’ version is sent by radio telegram to the PC software.
The information "RadioView Type 4/20/3 Ver 1.3" indicates that the RadioView used has a
4-line display of 20 characters per line and three function keys. The version of the Radio-
View software is 1.3.
7.14.5.7 Problems and Alert window
In this window, alarms and faults which occur during revision are displayed on the PC.

®
7.14.5.8 Debug window of RadioView on the PC (help tool)

In the debug window, all functions which can be performed via the RadioView indication and control map
are displayed individually as a separate window for information. No manipulations can be made.
1. Open the debug window via the menu "View / RadioView_Debug_Window"

a b c d f
e g
Legend:
a) Version of RadioView map e) Display number of key command
b) Last revision message f) Exception list
c) Revision project g) Options menu (not yet implemented)
d) List of detectors to be switched h) Key fields
• Display number of key command:

The RadioView reports this number when a key is pressed.
Display number 10 represents the exceptions window. At present, this exception message is dis-
played only once without it being necessary to acknowledge this information
Active window:
The respective active window is displayed with a red field behind the display number.
The PC software will send this image next to the RadioView
• Key fields:
If a key was pressed, the key field has a "brown-yellow" background for 2-3 seconds.
Assignment of functions of the keys:
Ø "Key field 0"
Pressing this key should not trigger any function in RadioView
Ø "Key field 1"
Pressing this key should trigger a message to the PC but RadioView may not change the
image.
Ø "Key field 2"
Jump back to last proper window (only implemented in RadioView Vers 10.0)

®
Ø "Key fields 11-255"

When a key is pressed, this image number is next requested.
In der RadioView Version 1.3, this triggers a telegram.
Ø "Key field without number" (bottom right)
Apart from the exception in display number 13 (change of direction of polling), an image re-
fresh is requested with this key.
• Menu options
Ø Menu
Further submenus are displayed by means of the "Menu" function
Ø Opt
The "Opt" menu option is currently not available
Ø List
With "List", the revision list can be called up
Ø RevOn / RevOff
The detector displayed in the window has not yet been switched to revision/has been swit-
ched to revision
Ø Next
The next detector in the revision list will be displayed
7.14.6 Print revision report

The log of the revision performed can be printed with the function report in German, French, Italian and
English.
The report can be printed with the Windows default printer

As a test, any test text can be printed with Winword using the printer toolbar key.
At the same time, the report is also stored as an unformatted ASCII file in the current directory
"..\RevisionData as File "LAST_REPORT.TXT"".

®
7.14.6.1 SecuriPro Logger (help tool)

The logger is a help tool for RevMoni and records the highway telegrams which are received and sent.
The recording is shown in hexadecimal representation as well as in plain text.
Information
This help tool is not an LON analyzer since not all telegrams can be received.
The logger merely serves for checking on the PC whether the revision telegram was sent
or received.
In addition, the translation into plain text is also not complete.
Ø The recordings can be printed via the menu "File / Print Logger ASCII File"
Ø and can be saved as a text file via the menu "File / Save Logger ASCII File as..".

®
7.15 Abbreviations
AD values Analogue-digital values
ARB Alarm Routing Board
BIN Binary number system
BiPhase Coding method on SecuriLine
Button Switching area
Byte 8 bits
Cmd Command
COM Command Module
COM Port Serial port
Command Fail Communication error
Logfile Long-term data recording
DEC Decimal number system
DipFix Short-circuit selector switch
EMC Electromagnetic compatibility
ESD Extinction Light Smoke Detector
FBM Fire Brigade Map
FET Field effect transistor
HEX Hexadecimal number system
ICM Indications and Control Map
IOM Input Output Module
KIM Keyswitch and Indications Map
LAN Local Area Network
LIF Line interface
LED Light emitting diode
MCB Main Control Board
MCU Main Control Unit
MDI Multi Detector Interface
MIC Main Indications and Control Map
Neuron ID Address number allocated uniquely worldwide in the Echelon bus system
Nibble ½ byte
OCB Open Collector Board
OCM Open Collector Module
PIM Partial Indications Map
Prior data Prioritized data
Release Revision number
ROM Relay Output Module
SCB Stick Control Board
SCU Stick Control Unit
SDI Single Detector Interface
Service-Pin Commissioning pin for finding an LAN module during binding
SLTA Serial LON-Talk-Adapter
SOM Siren Output Module
SPI Synchronous Parallel Interface (MCB-SCB interface)
SSD Scattered Light Smoke Detector
SubCmd Subcommand
TimeOut Time exceeded in answering a line module
Trigger Defined recording point
UTD Universal Temperature Detector

®
7.16 List of Figures

Fig. 1Laptop ................................................................................................................................................7
®
Fig. 2 SecuriLine Panel and accessories ..................................................................................................7
®
Fig. 3 SecuriLine Monitor and accessories................................................................................................8
Fig. 4 SLTA and accessories ......................................................................................................................8
Fig. 5 Various accessories ..........................................................................................................................8
Fig. 6 SecuriWin software on CD-ROM ......................................................................................................9
Fig. 7 Connections of Panel and SAK 91 ..................................................................................................12
Fig. 8 End-of-line resistors ........................................................................................................................28
Fig. 9 Termination with SLR 811 ...............................................................................................................29
Fig. 10 Termination with FTR 811 .............................................................................................................29
Fig. 11 Termination with FTR 812 .............................................................................................................29
Fig. 12 Connection of LCB 02 ...................................................................................................................30
Fig. 13 LCB 02 ..........................................................................................................................................30
Fig. 14 LCB 02 with SLR 811 ....................................................................................................................31
Fig. 15 LCB 02 with FTR 811 ....................................................................................................................31
Fig. 16 LCB 02 with FTR 812 ....................................................................................................................31
Fig. 17 Equipping of MCB 02/02A .............................................................................................................32
Fig. 18 SCB 01 ..........................................................................................................................................35
Fig. 19 SCB 01A........................................................................................................................................35
Fig. 20 EDB 03 connection........................................................................................................................36
Fig. 21 Replacement of EDB 01/02 ...........................................................................................................37
Fig. 22 Comm. fault MCU..........................................................................................................................53
Fig. 23 Installation tool sequence ..............................................................................................................60
Fig. 24 SLTA 10 ........................................................................................................................................61
Fig. 25 SLTA 2 ..........................................................................................................................................61
Fig. 26 Overview of RevMoni ..................................................................................................................107

Section Commissioning

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Section Commissioning

Diunggah oleh

Hak Cipta:

Format Tersedia

SECURITON SecuriPro® FAS T 137 807 E 1 / 121

Version: EN 54 First issue 13.01.98 --- Ku / gsa ESD / bb

Applicability: Global Current 24.10.01 c bb / ksa Print

Information: T 137 807cE

ê SecuriWin Release Version: 01.03.00.004

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.4 Control values for the installation ................................................................................ 10

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.6.4 SCB 01/01A ...............................................................................................................................35

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.10 SecuriLan installation .................................................................................................. 60

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.14.3 Connection of the devices ....................................................................................................107

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.2 Current software versions for present documentation

7.2.1 Software compatibility

Release 01.03.00.004 Release 01.04.00.xxx

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.3 Preparation of the SecuriPro® commissioning tools / software

7.3.1 Laptop requirements

• Min. Pentium II Processor, 266 MHz

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

cement model for SLTA/2); AC adapter Model 78020

7.3.6 Various accessories

• PC interface cable to monitor, Panel or SLTA

Fig. 5 Various accessories

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.3.7 SecuriWin software

7.3.8 Installation of SecuriWin software

7.3.9 Additional requirements

• System software (customer data created with SecuriWin)

7.3.10 Danger information relating to commissioning

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.4 Control values for the installation

(1) (2) (3)

Reason for other values:

(3) Lower value = Earth fault

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.5.2 Start screen of the Panel Analysis software

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.5.3 Commissioning of line (Panel Analysis)

a / a1) Line Out (brown, white, pink) c) Interface connection

1. Disconnect terminals SCB 01/01A (Line 1)

7.5.3.2 Commissioning with the SecuriLine Monitor via SCB 01/01A

1. Connect interface cable to SecuriLine monitor and PC

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

7.5.3.3 Start up line from terminal A

1. Start "SecuriLine Diagnosis" program

Software version SCB 01

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

• The voltage UB Line may not fall below 19 V

11. Check Line 2; repeat steps 1 - 10

7.5.3.4 Start up Line from terminal B

2. Click on the button

SECURITON AG Alpenstrasse 20 CH - 3052 Zollikofen Switzerland

3. Enter the number of modules present on the line (0 = all)

4. Activate the function "Terminal B"

5. Close the window with "OK"

7.5.3.5 Start up Line only partially

2. Click on the button

3. Enter the number of modules you wish to start up

4. Activate the function "Terminal A" or "Terminal B"

5. Close the window with "OK"

6. Click on the "START LINE" button