Interfacing Paging Systems

Transcription

1 Release 3 Interfacing Paging Systems ESPA Interface Module BSL-333 Protecting life, environment and property... P-ESPA/EE Rev. A

2 COPYRIGHT This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose. and its subsidaries assume no reponsibility for any errors that may appear in the publication, or for damages arising from the information in it. No information in this publication should be regarded as a warranty made by Autronica Fire and Security. The information in this publication may be updated without notice. Product names mentioned in this publication may be trademarks. They are used only for identification.

3 Table of Contents Table of Contents 1. Introduction About the Handbook The Reader Terms About the ESPA Interface Module Description AutroSafe Software Requirements ESPA Service Pack Overview Typical Application SMS Messages Specifications BSL-333 Module Dimensions Indicators and Buttons Dip-switches Overview Installation and Cable Connections Overview Installing the Programs on the Computer Installing the Serial Port Communication Board EAU Jumper Settings Connections on Terminal Blocks X1 and X2 (if used) Mounting the Board Installing the BSL-333 Module General Mounting onto the Standard Mounting Rail Inside the Cabinet Mounting on an External DIN-rail Cable Connections Overview Connection between EAU-321 and Port 1 on the BSL-333 module Connection between the computer (configuration) and Port 1 on the BSL-333 module Connection between the computer (test) and Port 2 on the BSL-333 module Quick Reference Guide What you need to know about the paging system Basic Information Special Issues Page 1

4 Table of Contents 6. About the BSL-333-Configuration Introduction AutroCom formatted Configuration Configuration principles Short Description of the BSL-333 Configuration Tables Example of BSL-333 Configuration Planning the BSL-333 Configuration Display Size Fire System Events to Page Receivers to be Paged Priority Queue Multiple Receivers for one Event Receiver Priorities Technical alarms Introduction AutroSafe Config Common Configuration of the BSL-333 Module Selective Configuration Configuring the AutroSafe System Introduction Configuring the AutroSafe System Connecting the Cable Downloading the AutroSafe Configuration Preparing the BSL-333-module Introduction Setting Dip-switches Connecting the Cable Setting Baudrates Entering Executive Mode (EXE) Setting Parameters / KD485 Configuration Program Leaving Executive Mode (EXE) Configuring the Customized Setup of the BSL-333-module Introduction Configuring the BSL-333 module Loading BSL-333 Configuration using AutroCom Test Program Setting up Communication The AutroSafe Emulator Editing the BSL-333 Configuration Sending the BSL-333 Configuration Testing the BSL-333 Configuration Verifying the Customised Setup of the BSL-333-module Introduction Verification Procedure Page 2

5 Table of Contents 11. Verifying the paging functionality with a complete system setup Introduction Verification Procedure Interfacing Off-site GSM Telephones (SMS Messages) Introduction Cable Connections Configuration for AutroTel Module BSL Troubleshooting Self Monitoring Quick system overview AutroSafe communication Pager communication Check wiring BSL-333 program not executing properly AutroCom problems on the AutroSafe side Testing ESPA output from BSL Testing ESPA input to Paging System BSL-333- Configuration Tables The Settings table The Events table The Receivers table Func/state for the Events table Search order for the Events table Display Texts Dynamic <..> fields in Display Texts Considerations for Display Texts Appendix Verifying the Communication between AutroSafe and the BSL-333 Module using the default BSL-333 Configuration Introduction Preparations AutroSafe Configuration Verification Procedure Default BSL-333 Configuration Screw Terminals on the BSL-333 Module Character sets for AutroSafe ESPA 7-Bit character set (ISO 646) GSM SMS character set (GSM 03.38) Reader s Comments...81 Page 3

6 Introduction 1. Introduction 1.1 About the Handbook This handbook provides the information necessary to successfully interface the AutroSafe Interactive Fire Alarm system to on-site wireless pagers, using the ESPA Interface Module BSL-333 and one port on the Serial Port Communication Board EAU-321. The interface to off-site GSM telephones requires the additional AutroTel Module BSL-334. Information on this equipment is included in a separate chapter (Interfacing Off-site GSM Telephones SMS Messages). 1.2 The Reader The handbook is intended to be used by trained service and technical personnel with great knowledge of: AutroSafe functionality AutroSafe Configuration Data (output from the AutroSafeConfiguration Tool, configuration files) 1.3 Terms The ESPA Interface Module BSL-333 is referred to as the BSL-333 module throughout the handbook. Pager is synonymous with the terms pocket receiver, receiver and pocket pager. AutroCom is AutroSafe s interface to 3rd party equipment. AutroSafeConfig is the configuration data which is downloaded to the AutroSafe system by means of the AutroSafe Configuration Tool. Page 4

7 About the ESPA Interface Module 2. About the ESPA Interface Module 2.1 Description The ESPA Interface Module BSL-333 is an RS-232 interface module used to interface on-site wireless pagers or off-site GSM telephones using BSL-334 ESPA to SMS Interface. The ESPA Interface Module supports a large number of paging systems with ESPA protocol. The following AutroCom events can be paged: fire alarms prealarms faults technical alarms from I/O units Texts from AutroSafe may include the name of a Detection Zone and Tag Names (point information), plus general fault texts. The type of message to be transmitted to each pager is configurable, as well as the number of pagers the messages are transmitted to. Typically, a system will be configured to transmit all types of messages to some pagers, and only fire alarm messages to other pagers. The same type of pagers must be used within a system. A large number of pagers or group numbers can be used. (The BSL-333 module has a configurable memory of 2000 bytes (characters). This is not divided into fixed tables, but rather reflects the user s configuration. This means that there is no fixed limit on how many pocket receivers that can be configured.) The module is connected to the AutroSafe via the AutroCom protocol. ESPA Interface Module BSL AutroSafe Software Requirements The use of ESPA Interface Module requires AutroSafe software version or newer. Page 5

8 About the ESPA Interface Module 2.3 ESPA Service Pack The ESPA Service Pack (AS-ESPASERVPACK) includes the necessary programs, cables and documentation. The CD-ROM, including; The KD485 Configuration Program for baud rate settings AutroCom Test Program for loading the BSL-333 Configuration The Pager Tester (testing ESPA out of BSL-333 and ESPA into paging system) Documentation in pdf-format: the handbook AutroSafe - Interfacing Paging Systems and the data sheet for the BSL-333 module. Cables Communication Cable XJA-036 is used between the computer and Port 1 on the BSL-333 module. Communication Cable XJA-037 is used between the computer and Port 2 on the BSL-333 module. 2.4 Overview ALARM 19:23 AUTROSAFE SelfVerify Fault Function Disabled Function Delayed Fire Brig. Signalled More Events Power Testing Fire Brig. Disabled Fire Brig. Fault System Fault Alarms Disabled Alarms Fault Serial Port Communication Board EAU-321 Mute Panel ESPA Interface Module Silence Alarms Reset BSL C i 0 Pager AutroSafe BS-320 / BC-320 panels Paging System AutroTel Module BSL-334 Page 6

9 About the ESPA Interface Module 2.5 Typical Application The drawing below shows a typical application of the BSL-333 module. ESPA Interface Module BSL-333 PORT 1 PORT 2 AutroSafe Serial Port Communication Board EAU-321 TX (5) RX (3) GND (9) TX RX P1 GND Protocol Converter P2 GND RXA TXA Cable shield GND TX RX Paging System Power Supply 7-35V DC Power - Input Cable shield is optional for RS SMS Messages As an alternative to pager, a GSM telephone can be used. To be able to send SMS messages to GSM telephones additional equipment is required: AutroTel Module BSL-334. This unit provides ESPA interface (input) and can transmit SMS via a built-in GSM telephone. Refer to Interfacing Off-site GSM Telephones SMS Messages, chapter 12. ALARM 19:23 AUTROSAFE SelfVerify Fault Function Disabled Function Delayed Fire Brig. Signalled More Events Power Testing Fire Brig. Disabled Fire Brig. Fault System Fault Alarms Disabled Alarms Fault Serial Port Communication Board EAU-321 ESPA Interface Module Mute Panel Silence Alarms Reset BSL C 0 i AutroTel Module BSL-334 GSM Telephone AutroSafe BS-320 / BC-320 panels Page 7

10 About the ESPA Interface Module 2.7 Specifications BSL-333 Module Mounting Ports Interface Options RS-232 Mounted on rail. DIN-rail enclosure with removable screw terminals; fits 35mm symmetric rails Two asynchronous ports, TX & RX signals only. port 1 is RS232; port 2 is RS232. Receiver threshold + 1.5V typ. Receiver Rin 5kΩ typ. TX o/p ±8V typ (3k load). Power supply + 7V to + 35V DC. + 12V DC Input power approx. constant at 1-2 watts (startup current mA) depending on model. At startup, the supply voltage must reach 7V in <1 sec. Isolation 64V PK, tested at >1000V AC RMS, 1 second. Environmental Operating temperature 0 to +50C. Storage temperature -25C to + 70C. Relative humidity (operating and storage) 0 to 90%, non-condensing. EMC compliance Emissions EN (94), immunity EN (95). Dimensions 29mm (W) x 113mm (H) x 100mm (L) approximately in rail-mounted position, including screw terminals. 2.8 Dimensions The drawing below shows the dimensions of the BSL-333 module. Page 8

11 About the ESPA Interface Module 2.9 Indicators and Buttons ESPA Module BSL-333 2TX 2RX 1TX 1RX EXE PWR The BSL-333 module has the following indicators and buttons: 2TX: Red LED - Send (TX) Port 2 (to pager). Blinking light (0,5 second intervals) indicates that signals are being sent. 2RX: Red LED - Receive (RX) Port 2 (to pager). Blinking light (0,5 seconds intervals) indicates that signals are being received. 1TX: Red LED - Send (TX) Port 1 (to EAU-321 AutroSafe). Blinking light (3 seconds intervals) indicates that signals are being sent. 1RX: Red LED - Receive (RX) Port 1 (to EAU-321 AutroSafe). Blinking light (3 seconds intervals) indicates that signals are being received. EXE: Red LED Executive Mode (when setting parameters) o Blinking light (1 second intervals) when green button has been pressed. o Normal operation: EXE Lights steady while a message is sent to the paging system PWR: Yellow LED Steady light indicates Power ON. Green Executive Mode button. Used to enter Executive Mode (when setting parameters). Grey rotary switch (default factory settings - 0) Dip-switches Overview For ESPA installations, all dip-switches are to be set in OFF position. Top View of BSL-333 Module (front side) 4 ON Dip-switch block (rear side) Page 9

12 Installation and Cable Connections Overview 3. Installation and Cable Connections Overview 3.1 Installing the Programs on the Computer The ESPA Protocol Interface CD (AS-ESPACD) includes The KD485 Configuration Program AutroCom Test Program The Pager Tester Make sure that these programs are installed on your service computer. Insert the CD-ROM and install the programs one by one. Note: The use of one computer with one serial port is described in this handbook. Note that it is possible to use several computers at the same time (if several serial ports / computers are available). Page 10

13 Installation and Cable Connections Overview 3.2 Installing the Serial Port Communication Board EAU Jumper Settings The table below gives an overview of the jumper settings for the Serial Port Communication Board EAU-321. I/O header Port 3 and 4 Port 4 Port 3 J5 Port 1 Port 2 I/O header Port 1 and 2 J6 J8 J9 J10 J11 J7 Address jumpers Serial Port Communication Board EAU-321 Jumpers J5 and J6: J5 and J6 must be set to interrupt 2 and 5. TX RX CT DC DS R Jumpers J8 (interrupt) J8 must be set to interrupt 7 and R R Jumpers J9, J10 and J11 (interrupt) All ports must be set to interrupt R Jumper J7 (board address) Jumper in position A and B must be set to In. This setting applies to all communication boards. Gives board address 100h. C B A Page 11

14 Installation and Cable Connections Overview Connections on Terminal Blocks X1 and X2 (if used) NC RI 2 CTS 2 RTS 2 DSR 2 NC RI 1 CTS 1 RTS 1 DSR X GND DTR 2 TXD 2 RXD 2 DCD 2 GND DTR 1 TXD 1 RXD 1 DCD 1 Port 2 Port Mounting the Board Terminal Block X2 Terminal Block X1 The Serial Port Communication Board, EAU-321 is to be mounted onto the LON Interface Board EAU-310* (if the system is a distributed system) or directly onto the Processor Board EAC-300 (if the system is a standalone system). The board can be mounted inside any BS-310/320 panel or BC-320 Controller. However in a distributed system the board should preferably be mounted inside the Booting Panel. * The illustration below shows how to mount the EAU-321 board onto the LON Interface Board, EAU-310 inside a system unit (Fire Alarm Control Panel or Controller). Processor Board, EAC-300 LON Interface Board, EAU-310 (Reference: Dwg. no. UD-706) Serial Port Communication Board, EAU-321 Page 12

15 Installation and Cable Connections Overview 3.3 Installing the BSL-333 Module General The paging system should be placed in the same room. Normally, RS232 distance limitations apply i.e. maximum 15 metres. If longer distances are required shielded cable is recommended. (Port 2 is isolated, i.e. there are no problems with grounding) Mounting onto the Standard Mounting Rail Inside the Cabinet The module is connected to the AutroSafe via one RS232 port on the Serial Port Communication Board, EAU-321 (EAU-321 supports up to 2 AutroCom links). The BSL-333 module can be mounted and plugged onto the standard mounting rail inside the Fire Alarm Control Panel / Controller. The module is powered from AutroSafe s 24V DC power. If the module is to be mounted onto the standard mounting rail inside the cabinet, the dip-switch on the module must be pointing to the left when the module is to be inserted. Snap the left side of the fastener onto the mounting rail (1), then press the module slightly inwards (2) until the right side fastens Mounting on an External DIN-rail Alternatively, the module can also be placed on an external DIN-rail and powered with an external 24V DC. Page 13

16 Installation and Cable Connections Overview 3.4 Cable Connections Overview Connection between EAU-321 and Port 1 on the BSL-333 module Port 1 on the BSL-333 module is used for the cable connection from AutroSafe, while Port 2 is used for the connection to the paging system. There are two alternative ways of connecting the RS232 Serial Interface Cables. Alternative A: Connection to EAU-321 directly If there is no free space inside the AutroSafe cabinet for the screw connector, connect directly to the flat cable connector on EAU-321 with cable XBA-055. The used pins are in the top row. Communication Cable XBA-055 is used between the Serial Communication Board EAU-321 and Port 1 on the BSL-333 module. Page 14

17 Installation and Cable Connections Overview Alternative B: Connection by means of the screw connector (X1 and X2) This alternative may be suitable in larger systems where several ports are to be used. Note that the screw connector is not standard. Connect the cable from the Serial Port Interface Board EAU-321 (inside the AutroSafe BS-320) to the connector (Port 1) on the BSL-333 module. Connect the cable from the connector (Port 2) on the BSL-333 module to the paging system (the connector for connection to the paging system may vary depending on the type of paging system) Connection between the computer (configuration) and Port 1 on the BSL-333 module Communication Cable XJA-036 (test purposes) is used between the computer and Port 1 on the BSL-333 module when AutroCom Test Program is to be used. Connector BSL-333 to Port 1 Page 15

18 Installation and Cable Connections Overview Connection between the computer (test) and Port 2 on the BSL-333 module Communication Cable XJA-037 (test purposes) is used between the computer and Port 2 on the BSL-333 module when PagerTest Program is to be used. Connector computer to BSL-333, Port 2 Page 16

19 ALARM Fire ext.. acktivat ed Fire vent. activ. Fire Br ig. r ecvd. More Alarms Power Prewarning Early warning Fault System fa ult F unctio n disa bled Test ALARM Fire ext.. acktivat ed Fire vent. activ. Fire Brig. recvd. More Alarms Power Prewarning Early warning Fault System fa ult Function disabled Test ALARM Fire ext.. acktivat ed Fire vent. activ. Fire Brig. recvd. More Alarms Power Prewarning Early wa rning Fault System fault Function disabled Test Silence buz zer Sile nce so unde rs Re set Silence buz zer Sile nce sounde rs Re set Silence buz zer Sile nce so unde rs Re set C? C? Self Verify Self Verify C? Self Verify ALARM Fire e xt.. a cktivat ed Fire ve nt. activ. Fire Brig. re cvd. Mor e Alar ms Power Prewarning Early warning Fau lt Sys tem fau lt Fun ction disa bled Tes t Silence buzzer Silence sounders Rese t C? Self Verify Quick Reference Guide 4. Quick Reference Guide This chapter outlines all the necessary steps to successfully interface AutroSafe to a paging system. Chapter / procedure 15 5 Verifying the communication between AutroSafe and the BSL-333 module using the default configuration of the BSL-333 module (page 73) Planning related to the paging system that is to be used (page 18) 6 Getting familiar with the BSL-333 Configuration (page 20) 7 Configuring the AutroSafe system (page 30) 8 Preparing the BSL-333 module (page 34) 9 Configuring the customised setup of the BSL-333 module (page 38) Verifying the customised setup of the BSL-333 module (page 45) Verifying the paging functionality with a complete system setup (page 47) EAU-321 BSL-333 AutroSafeConfig BSL-333 BSL-333 BSL-333 BSL-333 Paging System Remarks Before customizing the configuration of the BSL Module, it is possible to verify that the cabling and communication between AutroSafe and the BSL-333 module is successful and that BSL-333 operates correctly with AutroSafe. This verification is based on the default configuration of the BSL-333 module. Information about the paging system you must be aware of before commissioning (basic information and special issues). Information about the BSL-333 Configuration. The procedure deals with the configuration of the AutroSafe Interactive Fire Alarm System. The AutroSafe Configuration Tool is used for this purpose. The BSL-333 is delivered with a standard setup (parameter settings) from the factory. This chapter provides information on the necessary preparations of the module. The KD-485 Configuration Program is used for this purpose. The procedure deals with the setup related to the paging system that is to be used. The AutroCom Test Program is used for this purpose. The procedure verifies that the customised setup is successful. The Pager Tester program is used for this purpose. The procedure provides information on how to verify the paging functionality with a complete system setup. The AutroSafe system is used to activate various events, i.e. fire alarms, prealarms, fault messages, texts etc. Page 17

20 What you need to know about the paging system 5. What you need to know about the paging system 5.1 Basic Information To avoid possible problems caused by wrong settings or preparations on the paging system, it is important to know the following basic information about the paging system that is to be used, including: RS232 Hardware What type of port is used: D-Sub, 9 or 25 pins, screw terminals, RJ- 45? Get the pin-out! (You may have to make test cables from your PC to this plug). Does the serial interface have LEDs or similar that can be used to monitor operation? RS232 line settings Autronica recommends 9600 baud, 8 bits, No parity, 1 stop bit. (The original ESPA protocol defined 1200 baud, 7 bits, Even parity, 2 stop bits. This is not well suited for today s long display texts, or the use of international character sets). The receiver s display Total number of characters in one message The line length of the display (used for word wrap ). BSL-333 can make display texts that are close to 100 characters long. Displays shorter than 32 characters will require special considerations when setting up all DZ/point texts in AutroSafe Config to make the information useful on a small display. Use of receiver group numbers Most paging systems have the possibility to page groups. This means that BSL-333 only have to send a single paging call to reach a number of receivers, which gives fast system response. If possible, plan to use group numbers for receivers with identical pagings. Number plan for the receivers Some paging systems uses hidden prefixes to the receiver numbers. BSL-333 can use receiver numbers of any length, and the numbers are entered as text so it is possible to use letters as part of the numbers. Page 18

21 What you need to know about the paging system ESPA Beep codes suitable for Alarm, Pre-alarm and Faults. A Beep Code is a numeric code between 1 and 9. Character set for national characters BSL-333 uses an 8-bit Windows character set internally, which can represent all (Western) European characters. If the Paging system uses an older 7-bit national character set, it is necessary to get a conversion table. (see typical national character sets in Appendix here). Some older receivers have displays that support only UPPER case letters. 5.2 Special Issues Identical pagings Some paging systems accept more than one paging call at a time. They are then often set up to ignore identical pagings. If possible, have the paging system set up so that it will send ALL pagings even if they are identical. (This may not be a problem during normal operation, but if you are testing with a single Manual CallPoint, you risk that you loose repeated alarms inside the paging system.) Queuing of status messages Paging systems that store multiple calls can store the status of a call for a period (say one minute) after it has been paged. During this period the paged call blocks internal table space, so that the interface may reject new pagings. BSL-333 will not read such status, and internal tables should be freed up as quickly as possible. Page 19

22 About the BSL-333-Configuration 6. About the BSL-333-Configuration 6.1 Introduction The main configuration allows each installation to tune the behaviour regarding: What events to page How the event is presented in the receiver Which receivers will be paged for each type of event The configuration is written in a symbolic, software version independent, format. The configuration is handled by the AutroCom Test Program. Configuration data is sent to the BSL-333 module as one AutroCom message per Config text line. 6.2 AutroCom formatted Configuration Each line of Config represents one line (or part of a line) of a table. The general layout is: <TableId[Index]>;<Value1>;<Value2>; // Comment Each <ValueN> is encoded as <FieldName=Value> Example: Receiver table. Receivers[1]; Address=123; Events=1,2; //Technical staff Receivers[2]; Address=345; Events=2,3,4; //Mr. Smith The Config messages will be parsed by BSL-333 when they arrive. If they contain unknown text, BSL-333 will send a Fault message to the AutroSafe panel display. Page 20

23 About the BSL-333-Configuration 6.3 Configuration principles The Config is based on three assumptions: Messages from the Fire system are sent to just a few persons. They have identical pocket receivers. There is a lot of ESPA equipment out there, all slightly different. Some systems configure pager brands and model numbers, and the ESPA behavior is then hard-coded based on brand knowledge. The BSL-333 can be configured for the various ESPA properties directly. The texts presented on displays must be in a local language. The texts will be different for each installation, depending on the size of the displays used. The BSL-333 allows texts to be modified during commissioning, thus giving each customer what he wants! The system is delivered with model texts in English. Page 21

24 About the BSL-333-Configuration 6.4 Short Description of the BSL-333 Configuration Tables The BSL-333 Configuration consists of a number of tables (a plain text file), including: The Settings Table The Events Table The Receivers Table Each table consists of a number of lines. Each table line can be configured using one of more text lines. A short overview of the fields in each table is included below. For detailed information on each field in the BSL-333 Configuration Tables, refer to separate chapter (chapter 14). Table The Settings Table Fields Settings[1]; Char8=ÆØÅæøå; Settings[1]; Char7=[/]{ }; Settings[1]; Alphabet=7; Upper=0; Settings[1]; DisplaySize=120; LineLength=12; The table has only one line. The Events Table Events[1]; Func=05; State=A; Events[1]; Priority=1; Beeps=3; Transm=3; Events[1]; Text=*Fire Alarm* <DZ>; Each Event consists of two parts: The identification of the event, which is implemented very close to the AutroCom protocol s messages The expression of the event, which is how the pocket receiver will behave when paged with this event. These values are close to the ESPA protocol. The Receivers Table // Owner: N.N. Receivers[1]; Address=100; Events=0; OZ=0; There is one line in the Receivers table for each pocket receiver that shall be notified about events in the Fire System. Page 22

25 About the BSL-333-Configuration 6.5 Example of BSL-333 Configuration Config is a plain text file. // Config for BSL-333 ESPA Interface // // // // General settings // Settings[1]; Char8=ÆØÅæøå; Settings[1]; Char7=[/]{ }; Settings[1]; Alphabet=7; Upper=0; Settings[1]; DisplaySize=120; LineLength=12; // Events causing wireless paging: // // - Detector statuses Events[1]; Func=05; State=A; Events[1]; Priority=1; Beeps=3; Transm=3; Events[1]; Text=*Fire Alarm* <DZ>; Events[2]; Func=05; State=P; Events[2]; Priority=2; Beeps=2; Transm=1; Events[2]; Text=FirePreAlarm <DZ>; Events[3]; Func=05; State=Y; Events[3]; Priority=2; Beeps=2; Transm=1; Events[3]; Text=FireEWarning <DZ>; // - Fault messages Events[4]; Func=03; Events[4]; Priority=3; Beeps=1; Transm=1; Events[4]; Text=FireSysFault Unit= <UI> Message= <CL>. <RE>; // - Internal faults in the BSL-333 Events[5]; Func=00; Number=1; Events[5]; Priority=3; Beeps=1; Transm=1; Events[5]; Text=Pager Status AutroSafe communication <ST=FAULT,OK>; // - Technical alarms from inputs: Events[6]; Func=34; Number=0; Events[6]; Priority=2; Beeps=2; Transm=1; Events[6]; Text=Techn. Alarm <UI> Status=<ST=OFF,ON>; // // List of pocket receivers, with event filter // // Owner: N.N. Receivers[1]; Address=100; Events=0; OZ=0; // Owner: N.N. Receivers[2]; Address=002; Events=1,4; OZ=1; The index [1] of each table line is actually a tag that need not be sequentially increasing line by line. The [1] tag of the Events table is referenced by each line in the Receivers table, Events=1,4; This means that you can e.g. delete Events[3] (early warning) without having to re-configure the Receivers table. Also, if an Event is not referenced by any Receiver, it will not cause paging, but it can be left in the table for possible future use. (When the BSL-333 Configuration is loaded, every new, unknown tag will cause allocation of next free memory address. Skipping tag values does not reserve memory unnecessarily). Page 23

26 About the BSL-333-Configuration 6.6 Planning the BSL-333 Configuration Display Size Decide what display size is to be used. A regular fire alarm message consists of a prefix text like Fire Alarm followed by a DZ text of max. 34 characters (plus an optional point tag of max. 24 characters). A Fault message consist of a prefix text, the name of the faulty unit (34 chars), followed by a Class and a Reason text each max. 40 characters, for a total of some 120 characters. The display formatting will suppress trailing spaces, so the text will usually be more like characters. Today s high-end receivers can typically receive messages up to 120 characters, in which case the display layout is non-critical. If smaller displays are to be used, for example 16 or 32 characters, it s possible to use shorter prefix texts, and the text information from AutroSafe can also be configured to have a fixed length. In this way a Fault message can present useful pieces of all texts involved. Another important property of the pager displays is the character set (alphabet) it can present. ESPA specified originally English only characters, while most brands have implemented ways to show (European) national characters. Check the details for the transmitter/receivers you select Fire System Events to Page The following events can be configured to start paging: Detector status Fire Alarm, Pre-Alarm, (Early Warning) Fire events are paged as quickly as possible. It is not possible to wait for DZ level alarms with coincidence or delays. Faults Point faults, system faults Internal faults of the BSL-333 Technical alarms (FPE response inputs) Along with the event you configure how it shall be paged (display text, priority etc.). Page 24

27 About the BSL-333-Configuration Receivers to be Paged The system has a list of pocket receivers. Each receiver is related to one or more of the events that can start paging. This means that for each event occurring, zero, one or more receivers are informed. There is even an advanced option where receivers can be grouped by OZ (Operation Zone), that is, be informed only by events on points in limited geographical areas (buildings) Priority Queue The Pager Queue holds events that are ready to be paged, sorted on arrival time and event (ESPA) priority. The queue length is 30 in the current version. If the queue becomes full, the most recent, lowest priority entry will be thrown away (lost). The recommended Config uses the following priorities: First Alarms and PreAlarms, then Faults. In a fire situation, typically one or more PreAlarms will be followed by real Fire Alarms. Faults are of little interest during a real Fire, as Faults occur as a side effect of the fire. If a system is configured with different priorities on Alarm and PreAlarm, or lower priority EarlyWarning is used, there is a chance that the Page Queue can hold e.g. a PreAlarm and an Alarm from the same point at the same time. The Alarm will then be paged first, and it s confusing to later page the (older) PreAlarm on the same point, so it will be deleted Multiple Receivers for one Event BSL-333 can be configured so that multiple receivers are notified about the same event. But sending say 10 SMS messages takes considerable time, maybe a minute or more. The system must respond quickly in situations where a low priority event is followed by a high priority event a few seconds later. This is solved by storing the active receiver in each Page Queue entry. Every time a message has been sent to a single receiver, the Page Queue is re-evaluated to find the most important entry. If the current entry has been replaced by a high priority entry, the new entry will be paged to all it s receivers, then removed from the queue. The previous entry, still in queue, will then finish paging it s remaining receivers. Page 25

28 About the BSL-333-Configuration Receiver Priorities The Receivers table is always searched in the sequence given by the Config; always starting with the first entry (the [index] value is not used here; if [1] is last it will be paged last). This means that the first receiver should be the person that needs the fire system s information fastest (in the normal case we talk about just seconds in difference here, but again, a SMS system could have noticeable delays). 6.7 Technical alarms Introduction Technical Alarm means that when a digital input changes state, some text is sent to one or more pagers. AutroSafe has no inputs called Technical Alarms. But it s possible to use Fire Protection Equipment units in the BN320/x product range, as they have an input monitoring capability. As long as a FPE is not Activated by AutroSafe, the input can change without any nasty side effects (Activated units have timeouts on the monitoring inputs causing AutroSafe FAULTs!). The Technical Alarm paging can be used to: Report status of units controlled by AutroSafe, e.g. fans starting or fire doors closing. Any BN-320/x can be monitored. Report status of units used only as inputs. BN-320/4 Standard Control Unit will be the best choice here. Note also that BN-320/4 has a second input, which can be used to generate FAULTS related to the connected equipment. As the BN-320/x units are loop units, they are not allowed to generate many events in a short time. It s not possible to use them as a door bell! Page 26

29 About the BSL-333-Configuration AutroSafe Config Regular FPEs are ADD ed to a loop, then assigned an Activation Group in AutroSafe Config. This is described in standard AutroSafe documentation. Input only FPEs that are to be used as pure Technical Alarms must also be ADD ed to a loop, but shall have no Activation Group. You will get a warning when generating the Config, which you can ignore (this capability is by design). Note that the BN320/x units have input filtering. A change of the input s state is reported after a configurable time. If the input returns to its previous state within this time, nothing is reported. This time is called Normal Monitoring Timer in BN-320/4 (it s the first of 3 timer settings for all of them). In addition to the configurable time, the unit s software adds 2 seconds minimum filter time Common Configuration of the BSL-333 Module To monitor all FPEs you add the following to the BSL-333 Config file: // - Technical Alarms (FPE inputs) Events[6]; Func=34; Number=0; Events[6]; Priority=2; Beeps=3; Transm=1; Events[6]; Text=Techn. Alarm <UI> <ST=OFF,ON>; (You must use a free tag-no for Events[<tag-no>] ). If you want alarm messages only when the inputs go ON, change the display text to..<st=,on>.. (that is, take away the word OFF, but leave the comma ; ). Page 27

30 About the BSL-333-Configuration Selective Configuration Depending on the installations number of FPEs, and how many of them shall cause paging, you may have to do more selective configuration of the BSL-333. Selective configuration can also be used to give more meaningful status texts, like door <ST=OPEN,CLOSED>, motor <ST=STOPPED,STARTED> etc. To obtain a selective configuration you must add each FPE input to the Config as a separate Event. Due to a limitation in the Receivers table s Events=, you must select Event <tag-no> in one of two ways: If all technical alarms shall go to the same receivers, use <tag-no> above 31. The Receivers then all be configured as Events=,31 Only the Config memory size limits the number of FPEs added this way. If selected technical alarms shall go to selected receivers, use <tag-no> below 31. Each Receiver can then have settings like Events=,10, Events=,11, and so on. Max 25 FPEs can be handled like this (30 minus normal alarm events). The FPEs are distinguished by the Number parameter of the Events[] entry. AutroSafe Config assigns this number automatically when you ADD a FPE. To find it, select the FPE unit in AutroSafe Config, and look at the top of the right pane. In the example below, Number is 1. This particular FPE is then referenced in BSL-333 Config like this: Events[32]; Func=34; Number=1; Example: All specified technical alarms go to Receiver[2] //... // Main Door status Events[32]; Func=34; Number=1; Events[32]; Priority=2; Beeps=3; Transm=1; Events[32]; Text=Door Alarm <UI> <ST=OPEN,CLOSED>; // // Fan status Events[33]; Func=34; Number=2; Events[33]; Priority=2; Beeps=3; Transm=1; Events[33]; Text=Fan Alarm <UI> <ST=STOPPED,STARTED>; // // List of pocket receivers, with event filter // Receivers[1]; Address=999; Events=0; OZ=0; Receivers[2]; Address=001; Events=1,2,3,31; OZ=0; Page 28

31 About the BSL-333-Configuration Example: Selected alarms to selected pagers. Event[10] goes to Receiver[2], and so on. //... // Main Door status Events[10]; Func=34; Number=1; Events[10]; Priority=2; Beeps=3; Transm=1; Events[10]; Text=Door Alarm <UI> <ST=OPEN,CLOSED>; // // Fan status Events[11]; Func=34; Number=2; Events[11]; Priority=2; Beeps=3; Transm=1; Events[11]; Text=Fan Alarm <UI> <ST=STOPPED,STARTED>; // // List of pocket receivers, with event filter // Receivers[1]; Address=999; Events=0; OZ=0; Receivers[2]; Address=001; Events=1,2,3,10; OZ=0; Receivers[3]; Address=002; Events=1,2,3,11; OZ=0; Example: Some alarms with custom texts, the remaining ones shall use a standard text ON/OFF. //... // Main Door status Events[10]; Func=34; Number=1; Events[10]; Priority=2; Beeps=3; Transm=1; Events[10]; Text=Door Alarm <UI> <ST=OPEN,CLOSED>; // // Fan status Events[11]; Func=34; Number=2; Events[11]; Priority=2; Beeps=3; Transm=1; Events[11]; Text=Fan Alarm <UI> <ST=STOPPED,STARTED>; // // All remaining inputs Events[12]; Func=34; Number=0; Events[12]; Priority=2; Beeps=3; Transm=1; Events[12]; Text=Techn. Alarm <UI> <ST=OFF,ON>; // // List of pocket receivers, with event filter // Receivers[1]; Address=999; Events=0; OZ=0; Receivers[2]; Address=001; Events=1,2,3,10,12; OZ=0; Receivers[3]; Address=002; Events=1,2,3,11,12; OZ=0; Advanced Display Texts for Technical Alarms A Technical Alarm will be most important when it goes active. You have the option to inform the receivers even when it goes inactive, but you may want to use a more polite language. You can use several <ST=.> fields within one text. Try for example: Events[12]; Text=Fan <ST=Info,Alarm> <UI> <ST=Stopped,STARTED>; It will generate the texts (differences underlined): Fan Alarm Main Building Fan STARTED Fan Info Main Building Fan Stopped Page 29

32 Fire ext.. acktivated Fire vent. activ. Fire Brig. recvd. Power Prewarning Early warning Fault System fault Function disabled Test More Alarms Silence buzzer Silence sounders Reset Configuring the AutroSafe System 7. Configuring the AutroSafe System 7.1 Introduction ALARM Cable XJA C 0? Self Verify AutroSafeConfig The procedure deals with the configuration of the AutroSafe Interactive Fire Alarm System. The AutroSafe Configuration Tool is used for this purpose. The chapter includes the following: Configuring the AutroSafe System Connecting the cable for downloading Downloading the AutroSafe Configuration 7.2 Configuring the AutroSafe System The necessary configuration of the AutroSafe includes the following: From the Main Menu in AutroSafe Configuration Tool, click on View and select System (System View). In the Tree View on the left side of the screen, click on the Panel (BS-320) where the AutroCom Serial is to be added. Note: Make sure that the selected panel is actually the one where the Serial Port Communication Board EAU-321 is mounted. Right-click the mouse and select Add. Page 30

33 Configuring the AutroSafe System In the popup menu that appears, write the name of unit to be added, and state the number of units to be added (if necessary). Click on AutroCom Serial in the Entity window, then click on the Add button. In the Tree View, click on the AutroCom Serial (in this example named AUTROCOM_SERIAL_Pager). Page 31

34 Configuring the AutroSafe System Select port number, 1 or 2. Verify the parameter settings (baud rate to baud, 8 bits, none parity, 1 stopbit). Set the AutroCom Type to SERIAL_SLIDING_WINDOW in the drop-down box to the right. From the Main Menu, click on View and select Operation View. In the Tree View on the left side of the screen, click on the top level OZ (Operation Zone) that is, if there are several Operation Zones in the AutroSafe system. Right-click the mouse and select Connect. In the popup menu that appears, select the Pager (in this example we have given the Unit this name), then click on the Connect button. In the Tree View, verify that the AutroCom Serial (in this example, Pager) is connected to the correct OZ (Operation Zone). Page 32

35 Configuring the AutroSafe System 7.3 Connecting the Cable A cable (XJA-033 Communication Cable EAU-321 / Computer) is used for the connection between the computer and the EAU-321 board inside the Fire Alarm Control Panel (the Booting Panel in a distributed system). Connect the ribbon cable to the EAU-321 Board (Port 4 is dedicated for downloading of configuration files), connection J4 (P4) (the upper left ribbon cable connector), with the red wire pointing down. Connect the other end of the cable to one of the serial ports on the computer. 7.4 Downloading the AutroSafe Configuration The AutroSafe Configuration can be downloaded to all system units in a distributed system from a single Fire Alarm Control Panel (the one which is defined as the Booting Panel (System ID=01). To download the configuration, you have to use the ConfigDownload Tool. For detailed information on the Configuration and Commissioning Procedure for AutroSafe, refer to the Commissioning Handbook. NOTE: When the downloading is completed and the system is running (normal operation), a fault warning will occur as the paging system at this stage is still not connected (i.e. no paging system connected to AutroCom Serial). Page 33

36 Preparing the BSL-333-module 8. Preparing the BSL-333-module 8.1 Introduction Cable XJA-036 BSL-333 The BSL-333 is delivered with a standard setup (parameter settings) from the factory. This chapter provides information on this standard setup. The KD-485 Configuration Program is used for this purpose (chapter 3.1). The preparation of the BSL-333 module includes the following: Setting dip-switches Connecting the cable Entering Executive Mode Setting parameters 8.2 Setting Dip-switches The illustration below shows the dip-switch settings on the BSL-333 module. All dip-switches must be set in position OFF. The rotary switch on the front panel must be set to 0. Top View of BSL-333 Module (front side) 4 ON (rear side) Page 34

37 Preparing the BSL-333-module 8.3 Connecting the Cable Before entering Executive Mode (EXE) and setting the required parameters, the necessary cabling must be done. Consult the cable drawing below. Connect the cable from the 24V DC power source to the connector 7 and 8 (Port 1) on the BSL-333 module. Connect the test cable from the computer's serial port to the connector (Port 1) on the BSL-333 module. Communication Cable XJA-036 is used between the computer and Port 1 on the BSL-333 module. NOTE: If port 1 on the BSL-333 is connected to AutroSafe, the cable has to be disconnected before doing the necessary parameter settings via the computer. BSL-333 Test cable XJA-036 Power Cable Page 35

38 Preparing the BSL-333-module 8.4 Setting Baudrates If the standard baudrates are correct, go directly to Configuring the Customised Setup of the BSL-333 module, chapter Entering Executive Mode (EXE) The BSL-333 module must be electronically configured before it can be used. Configuration must be done via Port 1, which has to be set to Executive Mode. To enter Executive Mode, press and hold down the green Executive Mode button on the front panel approximately 5 seconds until the EXE indicator starts blinking, then release it. A few seconds later (approximately 3-4 seconds), the red EXE indicator will blink rapidly (1second ON / 1 second OFF), and you can start the configuration program KD485. ESPA Module BSL-333 2TX 2RX 1TX 1RX EXE PWR EXE Indicator Green Executive Mode Button Page 36

39 Preparing the BSL-333-module Setting Parameters / KD485 Configuration Program The parameter settings for Port 1 (AutroSafe) and Port 2 (Paging system) are done by means of the KD485 Configuration Program, which is delivered with the BSL-333 module. Make sure that the BSL-333 module is in Executive Mode. The EXE indicator should be blinking rapidly. If not, communication is not established, and you must repeat the procedure described in the previous section (Entering Executive Mode). Start KDCFG.EXE, and the Configuration Menu will appear on screen. Verify that Mode is set to OFF (on the right uppermost side). Not to be used Set the baud rate for Port 1 (AutroSafe) to baud, 8 bits, none parity, 1 stopbit, (which is the default setup of AutroSafe). Note that these parameters can be changed for AutroSafe by means of the AutroSafe Configuration Tool. Choose RX Xon/Xoff disabled Choose TX Xon/Xoff disabled Set the appropriate parameters for Port 2 (Paging system) according to the requirements. Recommended: baud, 8 bits, none parity, 1 stopbit. Click on the highlighted button marked Update KD485 and the message Writing new KD485 Configuration will appear on screen. When the message disappears, and the Update KD485 button no longer is highlighted, all parameters have been set and the configuration is completed. NOTE: If you later want to check the port settings, simply start the KDCFG.EXE again. It will read out the actual settings from the BS-333 module before displaying the configuration window Leaving Executive Mode (EXE) To leave Executive Mode, press the green Executive Mode button on the front panel or turn the power OFF/ON. Page 37

40 Configuring the Customized Setup of the BSL-333-module 9. Configuring the Customized Setup of the BSL-333-module 9.1 Introduction Computer with AutroCom Test Program Cable XJA-036 BSL-333 The procedure deals with the setup (parameter settings) related to the paging system that is to be used. The AutroCom Test Program is used for this purpose (chapter 3.1). This chapter includes the following: Connecting the cable (refer to previous chapter 8.3.) Configuring the BSL-333 module Loading the BLS-333 Configuration using the AutroCom Test Program Setting up the communication Using the AutroSafe Emulator (in the tools menu / AutroCom Test Program) to: o Edit the BSL-333 Configuration file (if necessary) o Send the BSL-333 Configuration o Test the BSL-333 Configuration Page 38

41 Configuring the Customized Setup of the BSL-333-module 9.2 Configuring the BSL-333 module The configuration of the BSL-333 module is described in detail in chapter 6. The necessary tables are included in chapter 14.1, 14.2 and The configuration deals with the following tables: Table The Settings Table Fields Settings[1]; Char8=ÆØÅæøå; Settings[1]; Char7=[/]{ }; Settings[1]; Alphabet=7; Upper=0; Settings[1]; DisplaySize=120; LineLength=12; The table has only one line. The Events Table Events[1]; Func=05; State=A; Events[1]; Priority=1; Beeps=3; Transm=3; Events[1]; Text=*Fire Alarm* <DZ>; Each Event consists of two parts: The identification of the event, which is implemented very close to the AutroCom protocol s messages The expression of the event, which is how the pocket receiver will behave when paged with this event. These values are close to the ESPA protocol. The Receivers Table // Owner: N.N. Receivers[1]; Address=100; Events=0; OZ=0; There is one line in the Receivers table for each pocket receiver that shall be notified about events in the Fire System. Page 39

42 Configuring the Customized Setup of the BSL-333-module 9.3 Loading BSL-333 Configuration using AutroCom Test Program AutroSafe Panel AutroCom via EAU-321 AutroCom Link BSL-333 ESPA Interface Module External Link Wireless Paging System with ESPA interface PC with AutroCom Test AutroComTest is a communication test program that has some additional functionality that is used here. It is used to send Config into BSL-333, and it can generate data messages for FireAlarm, Fault etc. so that the paging functionality can be tested. Connect the PC to BSL-333s port 1 (or the RJ-45 Config port) Make sure that BSL-333 is in operation mode (NOT executive mode) Start AutroComTest.exe The program s main window is a protocol trace window. It will show that BSL-333 sends Log_on_request every 10 seconds. The very first time this program is run, you may have to set up communication parameters, see below. Page 40

43 Configuring the Customized Setup of the BSL-333-module 9.4 Setting up Communication Select the Settings menu entry, then sub-entry Com Port and Protocol The Protocol is Serial Sliding Window. The default AutroCom port settings are shown; adjust them if necessary. Finish by pressing the OK button. The main window will show the Log-on-request messages within 10 seconds. Page 41

44 Configuring the Customized Setup of the BSL-333-module 9.5 The AutroSafe Emulator Select the menu entry Tools, then sub-entry AutroSafe Emulator. A new window appears. Wait some 20 seconds while RESET and INIT phases are simulated, and the text Entering OPERATION appears. You will see the LOGON attempts from BSL-333 during this period. (The screenshot shows a situation where the Paging System is not connected). Page 42

45 Configuring the Customized Setup of the BSL-333-module Editing the BSL-333 Configuration If necessary, the BSL-333 Config text file can be edited using any editor, for example Notepad. To test and modify it quickly, you can also edit it directly in the AutroSafe Emulator. Read your Config by selecting the File menu, sub-entry Open (alternatively, click the button). A standard Windows File dialog appears, where you can navigate directories and select a file. If you have used the program before, the name of the file you used last will come up pre-selected. You can now edit the text. It will be saved automatically when you click Send Config Sending the BSL-333 Configuration Click the Send Config button. The Config is transferred line by line in just a few seconds. The screen field Free Bytes is updated continuously. A successful transfer gives this status: If BSL-333 is unhappy with the Config, an error indication is returned: You then must navigate to line 10, and inspect the 3 rd value. The problem above was provoked by: Settings[1]; DisplaySize=120; LineLength=12; xxx (If there are multiple problems, the screen will show the last one when the transfer is finished.) NOTE: The line counter ignores lines that are completely empty. Put a // comment on all lines without any text! Page 43

46 Configuring the Customized Setup of the BSL-333-module Testing the BSL-333 Configuration As soon as a valid Config has been transferred to BSL-333, you can test and verify that the desired events from AutroSafe will generate paging calls. (At this point you must have a functioning communication with the Paging System. The trace below shows what happens when the Paging System is plugged in). All messages in the trace that starts with BSL-333: have been returned from BSL-333, and shown internal status from it. The example shown a Fire Alarm from the point with Unit ID 1. The name of the Detection Zone that appears in the display text is an artificial text. Note that the display text is formatted in columns that fits into the display, so some spaces have been removed, and some added. If necessary, go back to Edit Config and repeat the send/test procedure. Page 44

47 Fire ext.. acktivated Fire vent. activ. Fire Brig. recvd. Power Prewarning Early warning Fault System fault Function disabled Test More Alarms Silence buzzer Silence sounders Reset Verifying the Customised Setup of the BSL-333-module 10. Verifying the Customised Setup of the BSL-333-module 10.1 Introduction Computer with Pager Test Program ALARM Cable XBA-055 BSL-333 Cable XJA C 0? Self Verify The procedure verifies that the customised setup is successful. The Pager Tester is used for this purpose. This chapter includes the following: Connecting the cables (refer to chapter and 3.4.3) Verifying the customised setup of the BSL-333 module 10.2 Verification Procedure It is possible to test the BSL-333 without having a working paging system. Connect a PC to BSL-333 port 2. Run the PagerTest.exe program. Open the serial port with correct settings: Select the Receive tab: Page 45

48 Verifying the Customised Setup of the BSL-333-module Click the button Start ESPA Receiving. You will see a number of Receiving : Poll messages, and whenever something is to be paged, a decoded message. Page 46

49 Fire ext.. acktivated Fire vent. activ. Fire Brig. recvd. Power Prewarning Early warning Fault System fault Function disabled Test More Alarms Silence buzzer Silence sounders Reset Verifying the paging functionality with a complete system setup 11. Verifying the paging functionality with a complete system setup 11.1 Introduction ALARM EAU C 0 Cable XBA-055 BSL-333 Paging System? Self Verify The procedure provides information on how to verify the paging functionality with a complete system setup. The AutroSafe system is used to activate various events, i.e. fire alarms, prealarms, fault messages, texts etc. NOTE: Before activating events by means of the AutroSafe Interactive Fire Alarm System, disable: the signal to the Fire Brigade sounders voice alarms other audible / visual indicators output controls activating fire doors and ventilation The procedure includes the following: Connecting the cable between AutroSafe and Port 1 on the BSL- 333 module (refer to chapter 3.4.1) Connecting the cable between Port 2 on the BSL-333 module and the paging system (Normally the cable is delivered with the paging system. BSL-333 has screw connectors). Verifying the complete system setup (refer to Verification Procedure on next page). Page 47

50 Verifying the paging functionality with a complete system setup 11.2 Verification Procedure NOTE: Before activating events by means of the AutroSafe Interactive Fire Alarm System, disable: the signal to the Fire Brigade sounders voice alarms other audible / visual indicators output controls activating fire doors and ventilation Verify that the following AutroCom events can be paged: o fire alarms o prealarms o faults o technical alarms from I/O units Verify that the display on the different pagers show the correct information (name of a Detection Zone and Tag Names /point information, plus general fault texts). Verify that each pager receives the correct type of message according to what has been configured. Verify group identity (number plan for the pagers) according to what has been configured. Verify that the Beep Codes are correct according to what has been configured for Alarm, Prealarm and Faults. Page 48

51 Interfacing Off-site GSM Telephones (SMS Messages) 12. Interfacing Off-site GSM Telephones (SMS Messages) 12.1 Introduction To be able to send SMS messages to GSM telephones additional equipment is required: AutroTel Module BSL-334. This module provides ESPA interface (input) and can transmit SMS via a built-in GSM telephone Cable Connections The test cable XJ-A037 (Port2 to PC) can be used directly. Communication Cable XJA-037 is used between the BSL-334 module and Port 2 on the BSL-333 module. Connector computer to BSL-333, Port 2 Page 49

52 Interfacing Off-site GSM Telephones (SMS Messages) 12.3 Configuration for AutroTel Module BSL-334 The standard BSL-333 Configuration must be modified as follows: Modify Settings[1]; Alphabet=G // G = GSM characters Modify Settings[1]; DisplaySize=96 // Max 96 chars to BSL-334 Remove Settings[1]; LineLength // Let telephone do word wrap Go through all Events[]; and set Transm=1 // GSM has reliable transmission IMPORTANT: Go through all Events[] and make certain that no display text message starts with a *. You can for example insert a (space) in front of the *. (SMS messages starting with * is displayed as an empty message.) At the same time, also remove any line break characters like - (hyphen) and (bar), as a GSM telephone does word-wrap locally according to it s own display size and font. (It is possible to use the (bar) as a new-line control to improve readability, especially in the Fault messages.) Page 50

53 Troubleshooting 13. Troubleshooting 13.1 Self Monitoring The Wireless Pager functionality involves a number of hardware boxes and wires that may fail. AutroSafe Panel AutroCom via EAU-321 AutroCom Link BSL-333 ESPA Interface Module External Link Wireless Paging System with ESPA interface The BSL-333 implementation tries to monitor and report as much problems as possible. Hardware in fault Monitored by Reporting AutroSafe EAU-321 serial board Monitored by AutroSafe software. Detected within 10 seconds. Fault on AutroSafe panel, Communication error Loss of communication RS232 wiring from As above As above EAU-321 to BSL-333 Monitored by BSL-333. Sends message to selected pagers: Pager status: AutroSafe Communication FAULT BSL-333 hardware AutroSafe, as above AutroSafe panel, as above Page 51

54 Troubleshooting As the BSL-333 is located inside the AutroSafe cabinet, it s most likely that hardware problems occur on the outside of BSL-333. BSL-333 then can use AutroSafe s panel for fault reports. Hardware in fault Monitoring Reporting RS232 wiring to Wireless Pager System Monitored by BSL-333 software. Detected within 10 seconds. Fault indicated on AutroSafe panel, Communication error Protocol Converter Fault, Data 1, 1, 15 or Data 1, 2, 9 (separate table) Wireless Pager System As above As above box Wireless Pager system internal tests, can give busy status or transmitter failure Fault on AutroSafe panel, Communication error Protocol Converter Fault, Data 1, 2, 2 table) (separate AutroSafe displays information of Protocol Converter Fault. Data explanation. Value 1 Value 2 Value 3 Error type: 1 = Communication problem Pager Application status 1 = No Communication at all (startup problem) 2 = Transmission problem after a period of working communication. 3 = Pager Queue Full. Too many fire system events in a short time. Status of low level communication with Pager transmitter 1 = Transmission failed due to checksum error 2 = Pager BUSY. (Try again later) 3 = Message rejected due to unknown information field/value. 8 = ACK Timeout. Pager system ignored message. (polling works) 9 = Paging system does not respond to polling (broken wire? power down?) 15 = System power up status; there has been no contact with pager after startup. Example: Communication error Protocol Converter Fault Data System power up status, there has been no contact with pager after startup No communication Communication problem Page 52

55 Troubleshooting 13.2 Quick system overview The LEDs of the BSL-333 Module gives immediate info: AutroSafe communication 1RX should flash at least every 3 seconds, indication data received from EAU-321. If constantly dark, check wiring. Also refer to Missing communication, chapter If flashing, but problems, the port settings (baudrate etc.) may be the problem. 1TX should flash at least every 3 seconds, indicating transmission from BSL-333 to AutroSafe. If constantly dark, the ESPA program inside BSL-333 is not executing properly. The self-monitoring of the AutroCom link by AutroSafe and BSL-333 is based on messages sent one way, and acknowledges going the other way. Thus, both data paths must be OK before the link is reported OK. In the case where wiring is OK, but port settings (baudrate etc.) is wrong, both ends will transmit periodically, causing both 1RX and 1TX to flash in a normal rate. For advanced debugging, see separate chapter on AutroCom faultfinding Pager communication 2RX should flash at least every 0.5 seconds, indicating that the pager system responds to polling by BSL-333. If constantly dark, there could either be a wiring problem, or a port settings problem. 2TX should flash at least every 0.5 seconds, indicating transmission from BSL-333 to the pager system. If constantly dark, the ESPA program inside BSL-333 is not executing properly. The self-monitoring of the AutroCom link by BSL-333 is based on polling messages sent one way, and acknowledges going the other way. Thus, both data paths must be OK before the link is reported OK. In the case where wiring is OK, but port settings (baudrate etc.) is wrong, only BSL-333 will transmit periodically, causing only 2TX to flash in a normal rate. For advanced debugging, see separate chapter on Paging system faultfinding. Page 53

56 Troubleshooting Check wiring A classic problem with RS232 links is that the RX and TX signals are connected RX-RX and TX-TX. Plain wire breaks (bad contacts) are also possible, of course. It s easy to verify RS232 signals using a Voltmeter, see below. NOTE: Measure the RX and TX signals at both ends of a link! All RS232 TX (output) signals should be NEGATIVE in the range 6V to 12V, with 8V as typical and you may even see 3V to 5V on some portable PCs. The voltage does not change much on a multimeter during data transmissions (which temporarily goes to PLUS 6V to 12V). A TX signal can t drive much current, and the voltage may drop a little (one or more Volts) when connected to a RX input. A non connected RS232 RX (input) is typically below 0.5 V, and fluctuates when read. Note GND connections on the BSL-333 Module. All 3 GNDs are isolated from each other inside the BSL-333 Module. You must connect each of them to the proper external system, and do NOT strap them together nor share GND from another box. This applies also to voltage measurements; they are valid only relative to the same port s GND signal, no other! BSL-333 program not executing properly This is an abnormal situation. Return the BSL-333 to the factory. NOTE: The BSL-333 Module can accidentally be configured into ADE fixed program mode different from Off. In this case the BSL-333 Module will be running a built-in level converter program, which basically receives on one port, and sends on the other, possibly converting baudrates and/or electric interface. The port 1 LEDs and port 2 LEDs flashes in pairs RX/TX. Run KDCFG.EXE and check the ADE setting before giving up the unit! Page 54

57 Troubleshooting 13.3 AutroCom problems on the AutroSafe side AutroSafe Panel AutroCom via EAU-321 AutroCom Link BSL-333 ESPA Interface Module External Link Wireless Paging System with ESPA interface PC with AutroCom Test Verify communication AutroCom starts running during the Start initialization operation. That is, it is running when the AutroSafe display shows Panel is not initialized. When AutroCom is running it sends a message $0BxxGxxxx every two seconds. This is easy to verify with the AutroCom Test program, or a plain Windows HyperTerminal. Page 55

58 Troubleshooting Missing communication AutroSafe expects the external computer to log on within a few seconds after startup. If no logon occurs, the AutroSafe display gives a Fault warning, Other faults, with the name text of the AutroCom link (name as entered in AS Config). Press AutroSafe s ENTER button on this message, and you will see fault info Loss of communication. The fact that this error message is generated indicates that configuration and serial hardware is present in AutroSafe. Missing communication can have several reasons: Wrong port set up in AutroSafe Config. Re-check the port numbering plan EAU-321 not set up correctly. Check that the flat cable running from EAU-321 is connected on port 1/2 and is turned correctly (red line close to pin 1 in connector, up on EAU-321, down on screws). Check that all jumpers are correct: See drawing on next page. Communication parameter (baud rate etc.) mismatch between AutroSafe and the external computer. This will show up in the AutroCom test program as garbage characters appearing with 2 seconds bursts. Page 56

59 Troubleshooting The table below gives an overview of the jumper settings for the Serial Port Communication Board EAU-321. I/O header Port 3 and 4 Port 4 Port 3 J5 Port 1 Port 2 I/O header Port 1 and 2 J6 J8 J9 J10 J11 J7 Address jumpers Serial Port Communication Board EAU-321 Jumpers J5 and J6: J5 and J6 must be set to interrupt 2 and 5. TX RX CT DC DS R Jumpers J8 (interrupt) J8 must be set to interrupt 7 and R R Jumpers J9, J10 and J11 (interrupt) All ports must be set to interrupt R Jumper J7 (board address) Jumper in position A and B must be set to In. This setting applies to all communication boards. Gives board address 100h. C B A Page 57

60 Troubleshooting Connections on Terminal Blocks X1 and X2 (if used) NC RI 2 CTS 2 RTS 2 DSR 2 NC RI 1 CTS 1 RTS 1 DSR X GND DTR 2 TXD 2 RXD 2 DCD 2 GND DTR 1 TXD 1 RXD 1 DCD 1 Port 2 Port 1 Terminal Block X2 Terminal Block X1 Page 58

61 Troubleshooting Verify configuration AutroSafe Panel AutroCom via EAU-321 AutroCom Link BSL-333 ESPA Interface Module External Link Wireless Paging System with ESPA interface PC with AutroCom Test Hyperterminal Test Program AutroSafe writes some trace during system start-up to the serial port on the EAC-300 that is used for loading of AutroSafe Config. The port runs on 9600 baud, 8 bit, no parity, 1 stop bit. Run a standard Windows HyperTerminal connected to this port. (Uses the same connections as used when downloading AutroSafeConfig). Hardware detection takes place immediately after system restart. You will find two lines of text describing the status of possible AutroCom channels. As the AutroSafe system starts up, more text is written to the terminal port. Among the printout here you will find a line [autrocom99-p1] Data protocol running [autrocom38-p1] shows both the Unit_ID of the channel (38), plus the port number of EAU-321 (P1). Unit_ID is the number you will find in AS Config when you select an AutroCom entry and inspect the details in the right part of the screen. (The number is assigned dynamically). This text indicates that the AutroCom configuration and EAU-321 hardware is present. Page 59

62 Troubleshooting Note also that the external system sends system info fields in its LOGON message, it will show up here, thus making it easy to get version info etc. from BSL-333. If AutroCom start-up is aborted for some reason, it will be printed here. Page 60

63 Troubleshooting 13.4 Testing ESPA output from BSL-333 AutroSafe Panel AutroCom via EAU-321 AutroCom Link BSL-333 ESPA Interface Module External Link Wireless Paging System with ESPA interface PC with PagerTest (receive) It s possible to test the BSL-333 without having a working Paging System. Connect a PC to BSL-333 port 2 Run the PagerTest.exe program. Open the serial port with correct settings: Page 61

64 Troubleshooting Select the Receive tab: Click the button Start ESPA Receiving. You will see a number of Receiving : Poll messages, and whenever something is to be paged, a decoded message. Page 62

65 Troubleshooting 13.5 Testing ESPA input to Paging System AutroSafe Panel AutroCom via EAU-321 AutroCom Link BSL-333 ESPA Interface Module External Link Wireless Paging System with ESPA interface PC with PagerTest (send) It s possible to test the Paging System stand-alone. This is very useful to verify the baud-rate etc. (when communication problems), and that the number plan of the pocket receivers is correct (when functional problems). Connect a PC to the Paging System Run the PagerTest.exe program. Open the serial port with correct settings (see screenshot in the previous pages) Page 63

66 Troubleshooting Select the Send tag: Click the button Poll Pager. You will see the text Sending: 2<ENQ>, followed by a Receiving: message. If there is a noticeable delay, and the text is Fault Timeout, it means that the Paging System did not answer, and there must be either a wiring or baud-rate problem. Page 64

67 Troubleshooting As soon as Polling works, you can start sending messages to the pocket receivers. Fill in the Pager Address field, and enter a suitable display text. Then click the button Send Message To Pager. Normally the response is Receiving: <ACK>, which means positive acknowledge. You may also get negative acks: 1<NAK> means a transmission error (bit-error). 2<NAK> means busy try later. 3<NAK> means that the message was received OK, but the content is not understood. Page 65

68 BSL-333- Configuration Tables 14. BSL-333- Configuration Tables 14.1 The Settings table The Settings table has only one line. Settings[1]; Char8=ÆØÅæøå; Settings[1]; Char7=[/]{ }; Settings[1]; Alphabet=7; Upper=0; Settings[1]; DisplaySize=120; LineLength=12; Field (Example) Values Explanation Char8 ÆÅØæøå Char8 is used together with Char7 for character (alphabet) translation between a PC s 8-bit international character set and a pager s 7-bit national character set. See tables in Appendix for various European languages. Char8 must hold characters with ASCII value between 0xC0(À) and 0xFF(ÿ). Example value: Norwegian national characters Char7 [/]{ } Char7 contains the 7-bit character that is to be used for the characters defined in Char8. The first char in Char8 is replaced by the first char in Char7, and so on. Note the example; Char8 and Char7 are put on separate lines, and then it s easy to se a one-to-one translation result. Example value: Norwegian character generator locations Alphabet Upper Main control of Character set translation: 8 - No translation. 8-bit Windows character set used. 7 - The pager receiver uses a 7-bit character set. All 8-bit characters are changed to their 7-bit counterpart (accents removed, e.g. À into A ). In addition, national characters are translated according to the Char8 + Char7 settings. G - GSM character set. To be used with the BSL-334 ESPA-to-SMS interface. Gives some national characters see appendix. Additional control over 7-bit Character set 0 - No change of character set. 1 - Lower case letters a..z are changed to upper case letters A..Z. May be needed by some older receivers with 14-segment displays. DisplaySize 120 This is the size of the largest display message the receiver can handle. If the text produced by BSL-333 becomes longer than this value, the message will be set to this size. Page 66

69 BSL-333- Configuration Tables If the text produced by BSL-333 is shorter, just the actual text is sent. Some older paging systems requires an exact number of characters, say 16. LineLength 12 The physical display of a receiver is usually divided into lines. To make text more easy to read, BSL-333 can word-wrap the text so that words start on a new line if they are too long for the previous one. If this field is left out (or set to 0), no word-wrap takes place. Also, if the wrapped text becomes longer than DisplaySize due to the added spaces, no word-wrap will take place. Special characters: A hyphen - can be inserted in a text to divide the text across two lines in a controlled way. Example: Communicat-ion. A vertical bar can be used as a newline character. Example:... Message= makes Message start on a new line. Page 67

70 BSL-333- Configuration Tables 14.2 The Events table Each Event consists of two parts: The identification of the event, which is implemented very close to the AutroCom protocol s messages The expression of the event, which is how the pocket receiver will behave when paged with this event. These values are close to the ESPA protocol. Events[1]; Func=05; State=A; Events[1]; Priority=1; Beeps=3; Transm=3; Events[1]; Text=*Fire Alarm* <DZ> <UI>; Field (Example) Values Explanation Func 05 AutroCom: The AutroCom message (function number) that will be monitored. See the Func/State table below for values. State A AutroCom: A character sub-field in the monitored AutroCom message. See the Func/State table below for values. If the field is left out, or set to 0, it will match ALL states. Number 1 AutroCom: A numeric sub-field in the monitored AutroCom message. Alternative name of the State field. Priority 1 ESPA: Priority of the pager call. The priority is used both internally in the BSL-333, and in the pager system. 1 = Alarm 2 = High 3 = Normal Beeps 5 ESPA: Beep coding. Depending on the pager brand, this can either be number of beeps, or it can be an index into a table of pre-set beep patterns. This code may also be used to control a vibrator in the receiver. Values are 1 to 9. Transm 3 ESPA: Number of radio transmissions. The radio transmission from the paging system s transmitter to the pocket receivers may be lost due to noise from other electric systems, or the user being in a location with poor antennae coverage. To improve reliability, high priority pagings should also be set up with 2 or 3 radio (re-) transmissions. Type 3 ESPA: Call Type. 3 = Standard Call, this is the usual value for Display paging. 4 = (ascom Telecourier: Alarm Call) Text *Fire Alarm* <DZ> <UI> ESPA: Display Message. The display text consists of a fixed background text, with dynamic fields in brackets < > that will be replaced with actual texts/numbers for each paged event. See separate description. Page 68

71 BSL-333- Configuration Tables 14.3 The Receivers table There is one line in the Receivers table for each pocket receiver that shall be notified about events in the Fire System. // Owner: N.N. Receivers[1]; Address=100; Events=0; OZ=0; Field (Example ) Values Explanation Address 100 ESPA: Call address. The pocket receiver s address in the paging system. The address is stored as a variable length text: - the address can be any number of digits, e.g. a telephone number when used with BSL-334 GSM/SMS - the address can contain letters, used by some pagers for group addresses. Events 0 1,2,4 OZ 0 2,3 Paging requirement: A list of Events that this receiver shall know about. This way some pagers receive just fire-/pre-alarms, while others also can receive fault messages. The values are the index (tag) of Event table entries; i.e. the numbers inside the Events[..] brackets. - A value of 0 (or left out) means page all events. Paging requirement: Limit paged events to those occurring in specified OZs only. Can be used to create e.g. per-building pagings. (Used in very large systems). Note: Grouping by OZ only works for the Fire alarm events. The OZs listed here must be the closest owner of a point; it s not possible to select OZs in the middle of a deeper hierarchy. - A value of 0 (or left out) means page all OZs. Page 69

72 BSL-333- Configuration Tables 14.4 Func/state for the Events table The Events table has a flexible framework to be able to handle various information in a systematic way, but only a limited number of combinations have been implemented. The table below shows the valid combinations between Func, State and display text <..>. The format of the <..> fields are described in a separate table. Func State / DisplayText Comment number 05 A *Fire Alarm* <DZ> <UI> Point message: Fire Alarm 05 P FirePreAlarm <DZ> <UI> Point Message: Prealarm 05 Y FireEWarning <DZ> <UI> Point Message: Early Warning (normally not used) 05 any Point Message: Any other letter letter from the OP_EqPointMsg s AlarmState 03 0 (zero or empty) FireSysFault Unit= <UI> Message= <CL>: <RE> 03 P,D FireSysFault Unit= <UI> Message= <CL>: <RE> 00 1 Pager Status AutroSafe communicat-ion <ST=FAULT,OK> 34 0 (zero or empty) 34 Unit Id no Techn. Alarm <UI> Status=<ST=OFF,ON> any parameter can be used for special purposes! Unit message: Fault message. Any fault presented on AuroSafe s display can be paged with fault texts in the local language. - Normally sent only to technical staff pagers. Unit message: Fault message. The P and D states refer to Point and DZ respectively. - Use of these states are optional, but can be used to give point faults to pagers monitoring only point alarms. BSL-333 internal message(s): It may be nice to know if AutroSafe and/or the AutroCom link is operative. FPE message: Inputs of FPE units can be used as Technical Alarms. FPE Message: If a system has many FPEs, and just a few of them shall cause paging, it s possible to create one event for each of them, and identify the FPE by entering it s Unit Id number in the Number field. In this case the status text can vary also, e.g <ST=CLOSED,OPEN>, <ST=COLD,HOT> Search order for the Events table As indicated above, it s possible to enter one function several times in the Events table. The table will be searched from the top downwards until a match is found. It s possible to enter one or more specific func/state combinations, followed by an entry with empty state (Empty means match all ). This feature can be used to separate Point faults from all faults, or to have dedicated texts for some Technical Alarms, and let the remaining alarms share a common text. Page 70

73 BSL-333- Configuration Tables 14.5 Display Texts Dynamic <..> fields in Display Texts. Example display text: *Fire Alarm* <DZ> <UI> The dynamic fields can be used like this. Func Field Comment 05 <DZ> Point status messages: Detection Zone name text. Up to 34 characters, fetched from AutroSafe <UI> General Unit Id. Name (name tag) of point, FPE, or any System unit in Fault. Up to 24 characters, fetched from AutroSafe. 03 <CL> Fault Class text. Up to 40 characters, fetched from AutroSafe (in it s menu language). 03 <RE> Fault Reason text Up to 40 characters, fetched from AutroSafe (in it s menu language). Note that a Reason has meaning only together with its Class <ST=..> Status text. Any length, fetched from BSL-333 config. A status is a numeric value, starting with 0, then 1, Func 00: (internal faults) 0=FAULT, 1= OK Func 34: (FPE input) 0=Off (input open), 1= On (input closed) To give meaningful texts (in local language), it s possible to make a list of texts. Example: <ST=CLOSED,OPEN> can be used for FPE statuses off and On in Text=Door <UI> is <ST=CLOSED,OPEN>; If a certain status shall NOT cause paging, use an empty text (just comma, ). Example: <ST=FAULT,> <ST=,OPEN> Length modifier for dynamic fields: When working with small displays it can be desirable to control the width of each field. All dynamic fields that receive texts from AutroSafe can be forced to a preset length using the syntax <XX:NN>. For example <DZ:15> or <CL:10>.<RE:20>. This way some info can be given from all fields. Page 71

74 BSL-333- Configuration Tables Considerations for Display Texts Display texts must be edited per installation due to: Local language. Each country should make a Config master in its own language that can be re-used in future installations. Customer s other use of pagers. A paging system can be controlled from a number of sources like telephones, Nurse Call systems, intercoms, plus numerous technical alarms. The customer may have some requirements regarding how each sub-system shall identify its messages. (The standard BSL-333 config contains the word Fire in all messages.) Size of display. The start word(s) of a message should give useful information that fits into one (physical) display line. The standard BSL-333 config contains texts that fit within 12 characters. Page 72

75 Fire ext.. acktivated Fire vent. activ. Fire Brig. recvd. Power Prewarning Early warning Fault System fault Function disabled Test More Alarms Silence buzzer Silence sounders Reset Self Verify Appendix 15. Appendix 15.1 Verifying the Communication between AutroSafe and the BSL-333 Module using the default BSL-333 Configuration Introduction Before customizing the configuration of the BSL Module, it is possible to verify that the cabling and communication between AutroSafe and the BSL-333 module is successful so that BSL-333 operates correctly with AutroSafe. The verification procedure is based on the default configuration of the BSL-333 Module, which is downloaded at the factory. The procedure requires a computer and the ESPA service pack (AS-SERVPACK). ALARM C 0 BSL-333 Computer with ESPA Test Program? The procedure is done by activating a fire alarm or fault from an easily accessable detector or manual callpoint. NOTE: Before activating a fire alarm or fault, disable: the signal to the Fire Brigade sounders voice alarms other audible / visual indicators output controls activating fire doors and ventilation The verification procedure is successful when the message on the computer screen is identical to the message shown on the Fire Alarm Control Panel s display. Typically, this will be the name of the detection zone (Tag Name) Preparations AutroSafe Configuration Note that the AutroSafe system must be configured according to the specific installation and the AutroCom type for the serial port must be set to SlidingWindow. Refer to chapter 7. Page 73

76 Appendix Verification Procedure Connect the BSL-333 to AutroSafe s EAU-321 board. No custom BSL-333 Config is loaded yet! (If this test is run after a custom BSL-333 Config has caused problems: Load the standard English Config found on the BSL-333 installation CD-ROM). Connect a computer to BSL-333 s port 2 using the test cable XJA On the computer, start the PagerTest program. o Select the COM port where the XJA-037 cable is connected. o Fill in communications parameters: Default BSL-333 settings from factory are 9600 baud, 8 bit, no parity, 1 stop bit. Click on the PagerTest program s Receive tab. The check-box Pagings only must be active. Click the button Start Espa Receiving. Do an action in AutroSafe that shall cause paging. o Either cause a fire alarm from a Manual CallPoint (may not be possible in a running system) - or o make a detector fault by removing a Detector nearby. The AutroSafe panel will show a Fire or a Fault after a short time. Note the DZ name of the Manual CallPoint or the Detector. Observe the message shown on computer screen (PagerTest). The message on the computer screen should be identical to the message shown on the Fire Alarm Control Panel s display. Page 74

77 Appendix <Detection Zone Name> Message on computer screen: Message on Fire Alarm Control Panel s display: FIRE ALARMS 1 <Detection Zone Name> 2 CANTEEN 3 WORKSHOP 19:23 Total: 3 Comments to the trace (in this example): Pager address is 999. This is default in the standard English Config for BSL-333 The Pager Text is readable; you will find the FireAlarm or Fault lead text, followed by related texts from AutroSafe. Fault texts will be in AutroSafe s local language. (The texts are formatted for a default display size of 12 characters; you can make the texts prettier by changing the PagerTest s field Display Length to 12.) Page 75