100% found this document useful (1 vote)
2K views211 pages

Hyfire Manual

The document provides installation and programming instructions for a wireless fire alarm system. It contains details on the central node, expander modules, detectors, sounders and other devices. Wiring diagrams and programming steps are included to integrate the wireless devices with the system.

Uploaded by

Ceban Dumitru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
2K views211 pages

Hyfire Manual

The document provides installation and programming instructions for a wireless fire alarm system. It contains details on the central node, expander modules, detectors, sounders and other devices. Wiring diagrams and programming steps are included to integrate the wireless devices with the system.

Uploaded by

Ceban Dumitru
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 211

WIRE TO WIRELESS INTERFACES

(INC. STATIC TRANSLATOR)


ENGINEERS MANUAL

PE-0041-A Page 1 of 211 Issue Date: 21st May 2012


INDEX

SECTION 1 – PRE_INSTALLATION INFORMATION


INTRODUCTION………………………………………………………………………………………….. Page 7
PURPOSE………………………………………………………………………………………………..… Page 8
CE MARKING…………………………………………………………………………………………….... Page 8
SYSTEM DESIGN AND PLANNING………………………………………………………………..… Page 8
PERSONNEL………………………………………………………………………………………………. Page 8
GENERAL…………………………………………………………………………………………..….… Page 8
FIELD DEVICE SUPPLY AND SUPPORT………………………………………………………..….. Page 8
INSTALLATION GUIDE…………………………………………………………………………………. Page 9
HOW TO USE THIS GUIDE……………………………………………………………………. Page 9
RELATED DOCUMENTS…………………………………………………………………………….… Page 9
WARNINGS AND CAUTIONS……………………………………………………………………….… Page 9
PRE-INSTALLATION CHECKLIST………………………………………………………………….… Page 10
SOME DO’S AND DON’TS…………………………………………………………………………..… Page 10
INSTALLATION………………………………………………………………………………………..… Page 11
CHECK THE CENTRAL NODE / FIELD DEVICE FOR DAMAGE…………………..………..… Page 11
WHAT TO DO IF YOUR CENTRAL NODE / FIELD DEVICE IS DAMAGED OR SUSPECT.. Page 11
RADIO SIGNAL PERFORMANCE AND STABILITY……………………………………………...… Page 12
BACK BOX FIXING……………………………………………………………………………………… Page 13
WALL ALIGNMENT……………………………………………………………………………… Page 13
MOUNTING PROCEDURE………………………………………………….………………… Page 13
CENTRAL NODE AND EXPANDER MODULE DIMENSIONS…….…………………….… Page 13
CABLE INSTRUCTIONS……………………………………………………………………………….. Page 14
DETECTION LOOP CABLING TERMINATIONS……………………………………………………. Page 14
WIRELESS DEVICE TABLE………………………………………………………..…………………. Page 15
BATTERIES……………………………………………………………………………..………………. Page 19
DEVICE DIL SWITCH…………………………………………………………………………………… Page 19
GENERIC DEVICE INDICATION AND SETTINGS…………………………………………………. Page 19
INDIVIDUAL CHILD DEVICE GUIDANCE……………………………………………………………… Page 20
SENSORS………………………………………….…………………………………………………….… Page 20
INPUT/OUTPUT MODULE INDICATIONS ...………….……………………….……………………. Page 21
WALL SOUNDER…..…………………………………………………………………..……………….. Page 22
SOUNDER BASE………………………………………………………………………………………… Page 22
WALL SOUNDER BEACON……..………………………………………………………………..…… Page 23
SOUNDER BEACON BASE……………………………………………………………………………. Page 24
BEACON…………………………………………………………………………………………………. Page 25
VOICE SOUNDER/ANNUNCIATOR………………………………………………….……………….. Page 26
BEAM DETECTOR……………………………………………………………………………………….. Page 27

PE-0041-A Page 2 of 211 Issue Date: 21st May 2012


SECTION 2 – CENTRAL NODE INSTALLATION / LOCAL PROGRAMMING
INTRODUCTION…………………………………………………………………………………………. Page 30
RANGE BETWEEN CENTRAL NODE / EXPANDER MODULE AND FIELD DEVICE….………. Page 32
MAXIMUM THEORETICAL RANGE…………………………………………………………………… Page 32
FEATURES……………………………………………………………………………………………….. Page 33
SPECIFICATION…………………………………………………………………………………………. Page 33
WIRING CONNECTIVITY……………………………………………………………………………….. Page 34
TRANSLATOR MODULE MENU……………………………………………………………………… Page 35
TRANSLATOR MODULE MENU STRUCTURE……………………………………………………. Page 38
TRANSLATOR MODULE PUSH BUTTON OPERATION………………………..………………… Page 39
SETUP PROCEDURE……………………………………………………………………………………. Page 39
TRANSLATOR MODULE PRELIMINARY PROGRAMMING………….…………………………... Page 39
WIRELESS DEVICE START ADDRESS…….……………………………………………………….. Page 40
NOTIFIER / HONEYWELL PROTOCOL DEVICE START ADDRESS…………………………….. Page 40
WIRELESS FIELD DEVICE PROGRAMMING…..…………………………………………………… Page 41
TRANSLATOR MODULE LED INDICATIONS……………..………………………………………… Page 42
TRANSLATOR MODULE LCD INDICATIONS...................…….…………………………………… Page 42
TRANSLATOR MODULE PROGRAMMING……………………….…………………………………. Page 43
PROGRAMMING PROCEDURE…………………………..…………………………………. Page 43
PUSH BUTTON AND LED INDICATIONS………………..…………………………………. Page 43
MENU STRUCTURE AND GUIDES…………………………..………………………………. Page 43
INITIAL TRANSLATOR MODULE CONFIGURATION……………………………………………. Page 43
TRANSLATOR MODULE POWER UP………………………………………………………………… Page 43
LOOP DEVICE CONFIGURATION…………………………………………………………………….. Page 44
FIELD DEVICE POWER CELLS……………………………………….………………………………... Page 44
FIELD DEVICE CONFIGURATION……………………………………………………………………... Page 44

SECTION 3 –WIRELESS EXPANDER MODULE INSTALLATION GUIDELINES


INTRODUCTION …………………………………………………………………………………………. Page 47
SPECIFICATION………………………………………………………………………………………….. Page 47
CABLING TERMINATION – MONITORED POWER SUPPLY UNIT .........………………………. Page 48
CABLING TERMINATION – NON-MONITORED POWER SUPPLY UNIT ...……………………. Page 49
PROGRAMMING………………………………………………………………………………………… Page 49
EXPANDER MODULE CONFIGURATION AND TOPOLOGY……………………………………. Page 50

SECTION 4 – WIRELESS CONVENTIONAL EXPANDER MODULE INSTALLATION GUIDELINES


INTRODUCTION……………………………………………………………………………………….. Page 53
SPECIFICATION……………………………………………………………………………………….. Page 53
CONVENTIONAL EXPANDER MODULE FRONT PCB TERMINATIONS……………………… Page 54
CABLING TERMINATION – MONITORED POWER SUPPLY UNIT……………………………. Page 55
CABLING TERMINATION – NON MONITORED POWER SUPPLY UNIT………………………. Page 56

PE-0041-A Page 3 of 211 Issue Date: 21st May 2012


PE-0041-A Page 4 of 211 Issue Date: 21st May 2012
SECTION 5 – SOFTWARE
INTRODUCTION……………………………………………………………………………………….. Page 59
LOADING SOFTWARE…………………………………………………………………………..……. Page 60
START SYSTEM CONFIGURATION…………………………………………..…………………..… Page 66
ADDING FIELD DEVICES TO THE TRANSLATOR MODULE..............……….....…….......…… Page 70
ADDING A MULTI-CRITERIA DETECTOR………………………………………………………..... Page 70
ADDING AN OPTICAL SMOKE DETECTOR……………………………………………........……. Page 72
ADDING A THERMAL DETECTOR………………………………………………………….....…….. Page 74
ADDING A MANUAL CALL POINT…………………………………………………………………… Page 76
ADDING AN INPUT MODULE……………………………………………………………………....… Page 78
ADDING A MAINS POWERED OUTPUT MODULE…………………………………………...…… Page 80
ADDING A SOUNDER/SOUNDER BEACON/BASE SOUNDER/BASE SOUNDER BEACON Page 82
ADDING A VOICE SOUNDER / ANNUNCIATOR………………………………………………….. Page 84
ADDING A BATTERY POWERED OUTPUT MODULE………………………………………...….. Page 87
ADDING A BEACON……………………………………………………………………………………. Page 89
ADDING A BEAM DETECTOR.................................................................................................... Page 91
PROGRAMMING THE TRANSLATOR MODULE AND ASSOCIATED DEVICES………………. Page 93
PROGRAMMING FIELD DEVICES………………………………………………………………….… Page 99
THE LOAD PROCESS…………………………………………………………………………….…….. Page 102
THE W2W TABLE………………………………………………………………………………....……. Page.104
ADDITIONAL WIRELEX FACILITIES…………………………………………………………………. Page 108
USE OF STATUS TAB……………………………………………………………………………..…… Page 108
EXAMPLES OF DISPLAYED FAULTS……………………………………………………………….. Page 112
TAMPER FAULT……………………………………………………………………………..…. Page 112
SECONDARY POWER CELL DISCHARGE……………………………………………..… Page 112
SUBSTITUTION ATTEMPT………………………………………………………….………. Page 113
NO RADIO LINK / NO LINK………………………………………………………………… Page 113
GENERAL FAULT………………………………………………………………………..……. Page 114
USE OF RF LINK QUALITY TAB…………………………………………………………………… Page 116
LINK QUALITY TAB – CHILD DEVICE SECTION………………………………………… Page 117
LINK QUALITY HISTORY GRAPH…………………………………………………………………... Page 118
ZOOM IN ON RF GRAPH…………………………..……………………………………….. Page 119
RETURN TO NORMAL GRAPH VIEW……………………………………………………………… Page 119
SYSTEM CONFIGURATION CODE HEXADECIMAL-DECIMAL CONVERSION TABLE…… Page 120

PE-0041-A Page 5 of 211 Issue Date: 21st May 2012


SECTION 6 – WIRELESS EXPANDER MODULES
INTRODUCTION………………………………………………………………………………………. Page 128
ADDING AN EXPANDER MODULE TO AN UNPROGRAMMED TRANSLATOR MODULE… Page 129
ADDING AN EXPANDER MODULE TO A PROGRAMMED TRANSLATOR MODULE……… Page 138
ADDING ADDITIONAL EXPANDER MODULES………………………………………………….. Page 140
DAISY CHAIN………………………………………………………………………………… Page 141
SAME LAYER………………………………………………………………………………… Page 143
COMBINATION……………………………………………………………………………… Page 144
SECTION 7 – ADDITIONAL SOFTWARE APPLICATIONS
INTRODUCTION………………………………………………………………………………….…… Page 147
RF ANALYZE UTILITY………………………………………………………….………………….... Page 148
FIRECLONE UTIILITY………………………………………………………………………..……… Page 151
DOWNLOAD THE CONFIGURATION FILE………………………………………………. Page 151
UPLOAD THE CONFIGURATION FILE…………………………………………………… Page 155
VOICE ANNUNCIATOR (ORPHEY) UTILITY…..………………………………………………….. Page 164
SECTION 8 – MAINTENANCE VISITS
INTRODUCTION……………………………………………………………………………………… Page 169
CONNECT COMPUTER TO AN EXISTING SYSTEM…………………………………………….. Page 169
REPLACING / CHANGING A FIELD / CHILD DEVICE.…………………………………………… Page 173
TRANSLATOR MODULE FIELD DEVICE…………………………………………………. Page 173
EXPANDER MODULE FIELD DEVICE…………………………………………………….. Page 174

PE-0041-A Page 6 of 211 Issue Date: 21st May 2012


SECTION 1 – PRE_INSTALLATION INFORMATION
INTRODUCTION………………………………………………………………………………………….. Page 7
PURPOSE………………………………………………………………………………………………..… Page 8
CE MARKING…………………………………………………………………………………………….... Page 8
SYSTEM DESIGN AND PLANNING………………………………………………………………..… Page 8
PERSONNEL………………………………………………………………………………………………. Page 8
GENERAL…………………………………………………………………………………………..….… Page 8
FIELD DEVICE SUPPLY AND SUPPORT………………………………………………………..….. Page 8
INSTALLATION GUIDE…………………………………………………………………………………. Page 9
HOW TO USE THIS GUIDE……………………………………………………………………. Page 9
RELATED DOCUMENTS…………………………………………………………………………….… Page 9
WARNINGS AND CAUTIONS……………………………………………………………………….… Page 9
PRE-INSTALLATION CHECKLIST………………………………………………………………….… Page 10
SOME DO’S AND DON’TS…………………………………………………………………………..… Page 10
INSTALLATION………………………………………………………………………………………..… Page 11
CHECK THE CENTRAL NODE / FIELD DEVICE FOR DAMAGE…………………..………..… Page 11
WHAT TO DO IF YOUR CENTRAL NODE / FIELD DEVICE IS DAMAGED OR SUSPECT.. Page 11
RADIO SIGNAL PERFORMANCE AND STABILITY……………………………………………...… Page 12
BACK BOX FIXING……………………………………………………………………………………… Page 13
WALL ALIGNMENT……………………………………………………………………………… Page 13
MOUNTING PROCEDURE………………………………………………….………………… Page 13
CENTRAL NODE AND EXPANDER MODULE DIMENSIONS…….…………………….… Page 13
CABLE INSTRUCTIONS……………………………………………………………………………….. Page 14
DETECTION LOOP CABLING TERMINATIONS……………………………………………………. Page 14
WIRELESS DEVICE TABLE………………………………………………………..…………………. Page 15
BATTERIES……………………………………………………………………………..………………. Page 19
DEVICE DIL SWITCH…………………………………………………………………………………… Page 19
GENERIC DEVICE INDICATION AND SETTINGS…………………………………………………. Page 19
INDIVIDUAL CHILD DEVICE GUIDANCE……………………………………………………………… Page 20
SENSORS………………………………………….…………………………………………………….… Page 20
INPUT/OUTPUT MODULE INDICATIONS ...………….……………………….……………………. Page 21
WALL SOUNDER…..…………………………………………………………………..……………….. Page 22
SOUNDER BASE………………………………………………………………………………………… Page 22
WALL SOUNDER BEACON……..………………………………………………………………..…… Page 23
SOUNDER BEACON BASE……………………………………………………………………………. Page 24
BEACON…………………………………………………………………………………………………. Page 25
VOICE SOUNDER/ANNUNCIATOR………………………………………………….……………….. Page 26
BEAM DETECTOR……………………………………………………………………………………….. Page 27

PE-0041-A Page 7 of 211 Issue Date: 21st May 2012


INTRODUCTION

The Hyfire wire to wireless intelligent Central Node allows for the extension of an existing, or newly installed,
analogue fire detection system, on many different protocols, with wireless devices with minimum interruption to
the end user. There are two discrete Central Node wireless interfaces that can be installed:
• Translator Module - This interface is added to an analogue fire detection loop. The digital Information
passed from this interface to the Fire Control Panel (FCP) provides all the information normally available
with analogue devices – fault monitoring, analogue values, Cause and Effect control, disablements, etc.
• Conventional Expander Module – This interface allows a “conventional zone” of wireless devices, both
trigger and alarm devices, to be added to:
o An analogue detection system using a protocol that is non-compatible with the Translator
Module. This is achieved by using a Zone Monitor Unit and Sounder Control Card of the same
protocol as the analogue detection loop.
o A Conventional FCP using a free fire detection zone and radial Sounder circuit or breaking in to
an existing zone.
Geographic coverage can be increased by the use of additional wireless Expander Module. The Expander
Module is powered from a locally installed 24Vdc Power Supply Unit (PSU). Field devices can be directly
associated with the Central Node and Expander Module. However, the maximum number of devices in a
“Central Node cluster” cannot exceed 32 devices (see page 51 for a graphic example of a cluster).
Notes:
• The Translator Module and Conventional Expander Module are referred to as “the Central Node”
throughout this manual except where differences occur – the device is then referred to by its complete
name.
• The Expander Module is referred to as “the Expander” throughout this manual.
• Power is applied to the Translator Module when the Translator Module is wired directly to an existing fire
detection loop with associated wireless field devices connected on a secure wireless network.
• Power is supplied from an external source for the Conventional Expander Module. This can be from:
o A stand-alone 24Vdc monitored Power Supply Unit.
o 24Vdc from its associated FCP.
This section details:
a. The requirements for installing the equipment on to a site including all necessary precautions to ensure
that a system functions with high integrity.
b. Operating parameters of the devices and how / where they can be amended.

PE-0041-A Page 8 of 211 Issue Date: 21st May 2012


PURPOSE

The purpose of this manual is to provide the user with all recommended procedure
descriptions and full technical details for the successful installation and commissioning
of the Central Node on to a compatible FCP. Procedures described in this manual
include appropriate warnings and cautions to guide the user towards adopting safe and
methodical work practices during the installation and commissioning phases.

CE MARKING
This equipment is CE Marked to show that it conforms to the requirements of the
following European Community Directives:

• Electromagnetic Compatibility Directive 89/336/EEC (and the amending Directives


92/31/EEC, 93/68/EEC)
• Low Voltage Directive 73/23/EEC (and the amending Directive 93/68/EEC)

SYSTEM DESIGN AND PLANNING


It is assumed that the system, of which the Central Node is a part, has been designed by a competent fire alarm
system designer in accordance with the requirements of EN54 Part 14 and any other local codes of practice
that are applicable.

PERSONNEL
Installation and commissioning of this product must be carried out only by suitably qualified electrical personnel.
Engineers must have attended a HYFIRE training course for the Central Node and associated devices.

GENERAL
The Central Nodes are designed to be used with the HYFIRE range of wireless Detectors, Manual Call Points,
Input Modules, Output Modules, Audio and Audio-Visual devices. They can additionally be used with
compatible analogue devices

FIELD DEVICE SUPPLY AND SUPPORT


The Central Node supports the full range of HYFIRE field devices and accessories. For details on support of
these products contact:

Sterling Safety Systems

Tel: 01926 485 282


Fax: 01926 485 550
Email: [email protected]
Web: www.sterlingsafety.co.uk

PE-0041-A Page 9 of 211 Issue Date: 21st May 2012


INSTALLATION GUIDE
HOW TO USE THIS GUIDE
This Installation Guide is intended to provide an installation engineer with simple guidelines on how to install the
Central Node safely. For each stage in the installation and commissioning procedures, a brief description is
given of its purpose, complete with drawings, flow diagrams and / or other graphics to make the instructions
easy to follow.

RELATED DOCUMENTS
The guide does not describe any of the FCP installation, operating or configuration stages. For more
information refer to the FCP series of manuals.

WARNINGS AND CAUTIONS


Where appropriate, this guide and the remainder of the manual includes advisory
warnings and cautions to remind you to consider safety at all times, especially when
following the procedures described in this manual.

You are alerted to any areas where a risk of damage to static-sensitive devices if the
recommended procedures described in this manual are not followed. An example of
anti-static caution is provided to the left of this paragraph.

PE-0041-A Page 10 of 211 Issue Date: 21st May 2012


PRE-INSTALLATION CHECK LIST
Before installing the Central Node, you must first ensure that the following criteria have been met. Failure to do
this may not only result in damage to the equipment, but may also cause problems when commissioning the
equipment or adversely affect its performance. For information on pre-installation requirements for wireless field
devices please refer to specific equipment installation instructions.

SOME DO’S AND DON’TS


Before selecting a location for the Central Node and wireless devices, DO make sure that:

a. The operating ambient temperature is in the recommended


range:

-30°C to 55°C

and

b. The relative humidity is between:

5% and 95% (@40°C)

c. The Central Node has been manufactured with an ingress protection rating
of IP65. This allows for the unit to be mounted externally should the
application require it.

Note: Glands used to terminate cables, when the Central Node is used in
an external environment, need to have the appropriate levels of ingress
protection for the application.

d. DO NOT locate the Central Node where there are high levels of vibration
or shock.

e. DO NOT site the Central Node where there would be restricted access to
the internal equipment and cabling/wiring connections.

PE-0041-A Page 11 of 211 Issue Date: 21st May 2012


INSTALLATION
The Central Node is relatively simple to install providing the recommended procedures described in this manual
are followed.

Follow all installation instructions described in this manual. These instructions must be fully
understood and the manufacturer’s recommendations followed to avoid damage to the FCP and
associated equipment.

CHECK THE CENTRAL NODE / FIELD DEVICE FOR DAMAGE


Before attempting to install the Central Node and field devices, you should do the following:

After removing the Central Node / field device from its packaging, and before you
proceed with installing it in its chosen location, check for any damage that may
have occurred whilst in transit.
Note: In the unlikely event that the Central Node / field device has been
damaged, then you MUST NOT fit it but return it to Sterling Safety Systems. The
procedure for returning faulty items is detailed in the paragraph:

WHAT TO DO IF YOUR CENTRAL NODE / FIELD DEVICE IS DAMAGED OR SUSPECT

If you are satisfied that none of the supplied items have been damaged you can
now proceed with the installation procedure. This manual addresses the
recommended installation methods of the Central Node.

To prevent unnecessary damage to the electronic components, it is


recommended that the electronics are removed from the housing prior to fixing of
the back-box. Refer to page 13 (BACK BOX FIXING) for details.

WHAT TO DO IF THE CENTRAL NODE / FIELD DEVICE IS DAMAGED OR SUSPECT


If you have problems regarding the quality of the Central Node / field devices, follow the procedure below:

• DO NOT continue with the installation but contact Sterling Safety Systems for advice
on what to do next.
• Similarly, if the product is found to be faulty during installation contact Sterling Safety
Systems immediately.
To aid us, you are requested to:
a. Quote the unique batch reference number which can be found on
packaging, main chassis or inside the back box.
b. Note all the details relevant to your complaint, date of receipt,
packaging condition, etc. and forward this to Sterling Safety Systems.

• Where the product needs to be returned to Sterling Safety Systems, you are
requested to use the original packaging, or suitable anti-static equivalent, wherever
possible.

PE-0041-A Page 12 of 211 Issue Date: 21st May 2012


RADIO SIGNAL PERFORMANCE AND STABILITY
To achieve acceptable and reliable radio communication with the field wireless devices,
positioning of the Central Node is important. Please observe the following procedure:

Using the Radio Survey and Test Kit (HFW-STK-01) (available from Sterling Safety
Systems) undertake a comprehensive radio survey to establish the location that
provides the best coverage of the devices to be installed.

NOTE: Please see literature supplied with test equipment for correct operation.

To comply with the requirements of EN54-25 “….the results of any surveys should be
recorded and kept with the commissioning documentation.”

If possible avoid fixing or mounting the unit close to the following:

• Equipment that utilises large electrical currents

• Large metal objects or structures

• Fluorescent lighting fittings

• Metal ceiling structures

• IT Cabling

NOTE: 1. If installing multiple Central Nodes or Expanders on to a system, there


should be a separation of at least 2 metres between devices.

2. The Central Node / Expander should be installed such that the


antennae are pointing down and to the right. The LCD screen should be
easily readable if installed in this aspect.

3. The Central Node / Expander should ideally be located no less


than 2 – 2.5 metres from floor level.

PE-0041-A Page 13 of 211 Issue Date: 21st May 2012


BACK BOX FIXING
WALL ALIGNMENT
To prevent distortion, the Central Node back box MUST be installed on the wall as flat
as possible.
Failure to comply with this requirement will result in the misalignment of the internal and
external screw fixings. This will affect the IP rating of the module allowing the ingress of
contamination and/or moisture.
MOUNTING PROCEDURE
When a suitable location has been found for installing the Central Node, proceed as
follows:

Remove the front PCB assembly from the enclosure – this is held in place by two spring
fasteners. Remove the two antennae followed by the rear PCB assembly – secured by
three screws.

Using a suitable-sized drill bit (4mm) drill the required number of holes.

Prepare apertures (20mm knockouts) required for cable access.

Screw the back box to the wall using all fixing holes and appropriate-sized roundhead
Notes: screws. (DO NOT use countersunk screws).
All dimensions are in
millimetres. Remount the rear PCB assembly, fixing with the three screws. On completion, refit the
Fixing hole diameters two wire antennae in to the terminations on the rear PCB assembly.
are 4mm.
Ensure the ribbon cable, between the front and rear PCBs, is securely attached.
Remount the front PCB on completion

CENTRAL NODE AND EXPANDER MODULE EXTERNAL DIMENSIONS

(All dimensions are in millimetres)

PE-0041-A Page 14 of 211 Issue Date: 21st May 2012


CABLE INSTRUCTIONS
All wiring should comply with current IEE wiring regulations (BS7671) or the applicable local wiring regulations.
Note also the requirements of EN54-14 for cabling and interconnection of a fire detection and alarm system.
Use the following rules when installing cables:
• Cables should be brought into the enclosure through the 20mm knockouts provided on the top or
top/back face of the back box.

• Ensure that all openings in the back box are closed before connecting power to the FCP.

(NOTE: If more knockouts than required have been removed, the holes should be
blocked with blanking glands (ensuring the blanking covers maintain the Ingress
Protection rating). This is to prevent access to hazardous voltages.

• Electrical cable tails should be of sufficient length to connect to the appropriate termination points at
the commissioning stage

• Cables should be screened and terminated in appropriate glands to meet local wiring codes and to
preserve the integrity of the screen connection. The cable screen is to be clamped inside the cable
gland, which must be fitted with a continuity link between the incoming and outgoing cables.

DETECTION LOOP CABLING TERMINATIONS


The diagram below indicates the detection loop cable connections for the Translator Module.
Loop out +
Loop in +
Loop out -
Loop in -

PE-0041-A Page 15 of 211 Issue Date: 21st May 2012


WIRELESS DEVICE TABLE

PART NUMBER GRAPHIC BASIC DESCRIPTION

Intelligent hybrid wire to wireless Translator Module – complete with 2 in


HFW-W2W-01 number ¼ Wave 868MHz Aerials. IP65 rating when appropriate glands
fitted.

Intelligent wire to wireless Conventional Expander Module – complete with


HFW-CEM-02 2 in number ¼ Wave 868MHz Aerials. IP65 rating when appropriate glands
fitted.

Intelligent wireless Expander Module. Complete with 2 in number ¼ Wave


HFW-EM-01 868MHz Aerials. IP65 with appropriate glands (Requires 24Vdc PSU). For
use with a Central Node.

Intelligent wireless optical Smoke Detector c/w mounting base and power
HFW-PA-01
cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless Heat Detector c/w mounting base and power cells. For
HFW-TA-01
use with all wireless Central Nodes and Expanders.

Intelligent wireless Multi-criteria Detector c/w mounting base and power


HFW-MA-01
cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless Reflective Beam Detector. Can be used at a range of


HFW-RBD-01
up to 100metres. For use with all wireless Central Nodes and Expanders.

Intelligent wireless Manual Call Point c/w surface mounting box and power
HFW-CP-01
cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless IP65 Manual Call Point c/w surface mounting box and
HFW-CP-IP-01
power pack. For use with all wireless Central Nodes and Expanders.

PE-0041-A Page 16 of 211 Issue Date: 21st May 2012


PART NUMBER GRAPHIC BASIC DESCRIPTION

Intelligent wireless single channel input module c/w power cells. For use
HFW-IM-01
with all wireless Central Nodes and Expanders.

Intelligent wireless single channel Output Module. For use with the hybrid
HFW-OM-01
wire to wireless Translator Module and Expanders. Requires 24Vdc PSU

Intelligent wireless single channel Output Module providing Normally Open


or Closed contacts. Additionally provides a stand-alone 12/ 24V dc
HFW-BOM-01
output (up to 20mA). For use with the hybrid wire to wireless Translator
Module and Expander Modules.

Intelligent wireless Voice Sounder/Annunciator that provides synchronous


voice with a selection of up to three messages (maximum duration 32
HFW-VSK-01 seconds). The messages can be bespoke for the site. Voice file format is
*.wav and must have a sample rate of 16KHz and have an 8 bit length.
For use with all wireless Central Nodes and Expanders.

Intelligent wireless wall mounted Sounder (Red) 100dB(A) complete with


HFW-WSR-01
power cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless wall mounted Sounder (White) complete with power


HFW-WSW-01
cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless IP65 wall mounted Sounder (Red) complete with power
HFW-WSR-IP-01
cells. For use with all wireless Central Nodes and Expanders.

HFW-WSW-IP- Intelligent wireless IP65 wall mounted Sounder (white) complete with
01 power cells. For use with all wireless Central Nodes and Expanders.

PE-0041-A Page 17 of 211 Issue Date: 21st May 2012


PART NUMBER GRAPHIC BASIC DESCRIPTION

Intelligent wireless wall mounted Sounder Beacon (red) complete with


HFW-SBR-01
power cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless wall mounted Sounder Beacon (white) complete with


HFW-SBW-01
power cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless IP65 wall mounted Sounder Beacon (red) complete with
HFW-SBR-IP-01
power cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless IP65 wall mounted Sounder Beacon (white) complete


HFW-SBW-IP-01
with power cells. For use with all wireless Central Nodes and Expanders.

Intelligent wireless wall mounted Beacon (red) complete with power cells.
HFW-BR-01
For use with all wireless Central Nodes and Expanders.

Intelligent wireless wall mounted Beacon (red LED and white plastic
HFW-BW-01 surround) complete with power cells. For use with all wireless Central
Nodes and Expanders.

Intelligent wireless (IP65) wall mounted Beacon (red) complete with power
HFW-BR-IP-01
cells. For use with all wireless Central Nodes and Expanders.

HFW-STK-01 Hybrid wireless Survey and Test Kit

Spare primary power cell compatible with all hybrid wireless devices. (sold
HFW-PB-01 in packs of 10). Also used as secondary power cell in Audio-Visual
devices.

PE-0041-A Page 18 of 211 Issue Date: 21st May 2012


PART NUMBER GRAPHIC BASIC DESCRIPTION

Spare secondary power cell compatible with all hybrid wireless devices.
HFW-SB-01
(sold in packs of 10) (not compatible with audio-visual devices)

Intelligent wire to wireless replacement Wall Sounder key - used to open


HF-SKEY-01 the housing of Hyfire Sounder (HFW-WS*-01) and Sounder Beacon
(HFW-SB*-01)(available in packs of 10)

Intelligent wire to wireless replacement Hyfire Manual Call Point


HF-CKEY-01
(HFW-CP-01) test key (available in packs of 10)

PE-0041-A Page 19 of 211 Issue Date: 21st May 2012


BATTERIES
The majority of wireless devices are powered from onboard power cells – the primary cell (CR123A) is a 1.2Ah
cell and the secondary cell (CR2032) is a 240mAh cell.

(Note: The secondary cell in HFW-WS*-01, HFW-SB*-01, HFW-VS-01, HFW-WS*-IP-01,


HFW-SB*-IP-01 and HFW-B*-01 devices, is a CR123 and not a CR2032)

The field device can be transported with the secondary cell fitted (only where the secondary cell is a CR2032
type) – this will not drain the cell as the device only becomes active when the primary cell is fitted. If power is
removed from a wireless Central Node for a significant period of time, the power cells should be removed from
any associated field device - with no return handshake from the wireless Central Node, the field device will
suspect a problem and will instigate a higher rate of handshakes until communication is restored. If this does
not happen, it will increase its power in an attempt to re-establish a link with the wireless Central Node. This
will reduce the life expectancy of the power cells resulting in earlier replacement.

DEVICE DIL SWITCH


Each wireless device is fitted with a two position DIL switch. The normal operating position is for the switch to
be in the 1 position. The ON position is used when programming the device. The DIL switch ON position can
also be used by an Installation / Commissioning engineer when installing a device to check its radio integrity –
this is only possible after the device has been programmed on to the wireless Central Node or Expander.
Leaving the switch in the ON position will cause the Fire Control Panel to generate a fault suggesting the device
cannot be communicated with. Returning the switch to the 1 position will clear this fault. (Clearing the fault on
the Fire Control Panel may require additional actions to be carried out by the Installation/Commissioning
engineer).

GENERIC DEVICE INDICATION AND SETTINGS


Detector Address: This indicates the digital address given to the device – NOT the loop address. This cannot
be altered.

The following parameters can only be changed using the Wirelex software:

Supervisory Signal Period: The default time for all devices, except Audio-Visual devices and the wireless
Output Modules, is 1 minute. (The default time for Audio-Visual devices and wireless Output Modules is 7
seconds).

Supervision Period: This is a health check period between the wireless Central Node, Expanders and
associated field child devices. The default for all child devices is 3 minutes. This can be changed to 1.5
minutes, 9 minutes or 15 minutes. If changing this parameter, care should be taken that local standards and
codes of practice are adhered to. (Variations from local standards and codes of practice will need to be detailed
on Project Commissioning paperwork).

NOTE: If field devices are programmed on to the wireless Central Node, the devices will be programmed
on with default parameters.

PE-0041-A Page 20 of 211 Issue Date: 21st May 2012


INDIVIDUAL CHILD DEVICE GUIDANCE

DETECTORS
Sensitivity (Optical and Multi-criteria Detectors): The default sensitivity for the smoke channel is
“NORMAL”. This can be altered to “LOW” or “HIGH” depending on the installation.

LED Indication:
a. Fire: If this indication is unchecked, the device LED will not indicate (glow RED) if there is a fire
activation signal received at the Detector. This is default checked.
b. Battery Discharge: If this indication is unchecked, the device LED will not indicate (glow RED) if
there is a battery discharge signal received at the Detector.

Smoke Channel (Multi-criteria Detector): This process can be isolated in this device if the Detector is
required to work with the Thermal Channel only

Thermal Channel (Thermal and Multi-criteria Detector): This process can be isolated in these devices. The
device will now function with the Smoke channel only.

There are three modes of operation for this parameter:

a. Fixed – A standard “Fixed Temperature” Detector operating in the 58°C - 64°C zone.

b. High Temperature – A standard “Rate of Rise” Detector with a ceiling of 78°C.

c. A1R – A Rate of Rise Detector with a ceiling of 55°C.

This mode of operation should be used if the expected Rate of Rise of the Detector will be too
slow for the device to operate correctly. It is a combination of the first two modes of operation.

Note: Care must be taken that when learning a Multi-Criteria Detector on to the associated Fire Control Panel
with either channel isolated, the device will still learn on as a wireless Multi-Criteria Detector.

PE-0041-A Page 21 of 211 Issue Date: 21st May 2012


INPUT / OUTPUT MODULE INDICATIONS
The Input & Output Modules have processes that can only be altered using the Wirelex software:
Supervisory circuits (Input Module):
a. Do not supervise tamper sensor: If this box is checked and the front cover of the Input Module
is removed activating the tamper switch, this indication will not be passed to the wireless Central
Node. This process is default unchecked.
LED Indication:
a. Fire: If this indication is unchecked, the device LED will not indicate (glow RED) if there is a fire
activation signal received at the Input Module. This process is default checked.
b. Battery Discharge: If this indication is unchecked, the device LED will not indicate (glow RED)
if there is a battery discharge signal received at the Input Module. This process is default
checked.
Supervisory circuits (Externally Powered Output Module):
a. Do not use front tamper: The Output Module has a front tamper spring fitted. If the front cover
is removed, the Output Module will pass a tamper fault to the wireless Central Node and onward
to the associated Fire Control Panel. If this indication is checked, this will not happen. This
process is default unchecked.
b. Do not supervise supply voltage: If there is a problem with the device power supply, the
device will forward a signal to the wireless Central Node and on to the associated FCP. The
Output Module LED will flash RED with an interval of 0.1 seconds ON/2 seconds OFF. If this
indication is checked, this will not happen. This process is default unchecked.
The LED will illuminate ONLY if the “Low Power Supply” box is checked. This indication is
default checked.
c. The Output relay can be set at either “Normally closed” or “Normally Open” depending on the
operation required.
Supervisory circuits (Battery Powered Output Module):
a. External fault input: This process is disabled in this application.
b. LED Indication: If either the primary or secondary battery reaches a discharge state, the device
LED will illuminate either GREEN (secondary cell) or RED (primary cell). Flash interval is 0.5
seconds ON / 0.5 seconds OFF. This process is default checked.
c. The Output relay can be selected in one of four options as:
a. “Normally closed”
b. “Normally Open”
c. “Pulsed (3sec)
d. “Switching”.
d. Voltage output 12 / 24V: A selectable 12V / 24V output available to the installer to power a
stand-alone ancillary device. If the “Activate output” box is unchecked, this option is not
available. This option can be either a constant output or switching output (selectable). This
option is default unchecked.
NOTE: A wireless Remote Indicator learns on as a Battery Output Module. If using a Remote
Indicator the Voltage Output option must be checked else the Remote Indicator will not operate
in the event of an activation.

PE-0041-A Page 22 of 211 Issue Date: 21st May 2012


WALL SOUNDER
The wireless Wall Sounder has an audio output of 100dBs (+0dBs / - 6dBs). By removing the radio PCB
protective cover, using a small bladed screwdriver (preferably insulated) the sound output potentiometer can be
adjusted.
The Wall Sounder has three tone options:

SND Switch Frequency Descriptio KAC Main


Rate
Pattern Position (Hertz) n Tone Application
1 2
Alternating ON OFF 990 & 650 2Hz (250ms-250ms) Tone 6 BS Fire tone
Continuous OFF ON 990 Steady Tone 8 BS Fire tone
ON ON 1Hz (500ms On/500ms General
Intermittent 990 Tone 18
OFF OFF Off) Purpose

SOUNDER BASE
The wireless Sounder Base has an audio output of 90.1 – 92.4 dB(A). This can be adjusted by using the
relevant DIL switch. The device has 32 tone options that are selected via DIL switches (see drawing below)
(Common tone options are shown in the table below).

No.  Tone  Description  Switch 


23456 
1  LF Sweep  800‐1000Hz @0.5s  11111 
2  Alternative Warble  800/960Hz @ 2Hz  11110 
3  Warble tone  800/1000Hz @ 0.5s  11101 
6  LF Back‐up Alarm  800Hz 150ms on/off  11010 
8  LF Continuous Tone BS5839  800 Hz cont  11000 
10  Intermittent Tone  970Hz  625ms on/off  10110 
11  Continuous Tone  970Hz cont  10101 
17  Interrupted Tone  800Hz 0.5s on / off  01111 
18  ISO 8201 LF BS5839 Pt 1 1988  970Hz 500ms on / 500ms off  01110 
19  Interrupted Tone Medium  1000Hz @0.25s on / off  01101 
21  Continuous Tone  1000Hz continuous  01011 
31  FP 1063.1 – Telecom  Alternating tone 800/970Hz @2Hz  00001 

PE-0041-A Page 23 of 211 Issue Date: 21st May 2012


WALL SOUNDER BEACON
The Wireless Wall Sounder Beacon has a selectable audio output of 89-90dB or 99-100 dB (there is a 1dB
variation depending on tone pattern selected). The preferred output is selected via the 4 position DIP switch
situated under the top PCB:

HI – LO VOLUME SELECTION

TONE SELECTION

The Sounder Beacon has various tone options that can be set according to the Tone Selection switch positions:
(see diagram above and table below)

SND Switch Freq. Descriptio KAC Main


Rate
Pattern Position (Hertz) n Tone Application
1 2 3
Alternating ON OFF ON 990 & 650 2Hz (250ms-250ms) Tone 6 BS Fire tone
Continuous ON ON ON 990 Steady Tone 8 BS Fire tone
1Hz (500ms On/500ms Tone General
Intermittent OFF OFF ON 990
Off) 18 Purpose
Sweep, 0.5s silent, Dutch Fire
Whoop ON ON OFF 300 - 1200 Tone 7
repeat Tone
Sweep, 0.5s silent, Dutch Fire
Whoop OFF ON ON 300 - 1200 Tone 7
repeat Tone
Odd 2
ON OFF OFF 1200 - 500 Sweep (DIN) Tone 8 DIN Tone
Tone
Odd 2
OFF OFF OFF 1200 - 500 Sweep (DIN) Tone 8 DIN Tone
Tone
Odd 2
OFF ON OFF 1200 - 500 Sweep (DIN) Tone 8 DIN Tone
Tone

Tone selection switches are numbered 1-3 from the left. The 4th DIL switch is the switch for setting the audio
output level – switch in the OFF position gives 90dB output, switch in the ON position gives 100dB output.
(OFF position for all switches is when the high side of the switch is closest to the numbers).
The light output of the Beacon is >1Cd with a flash rate of 1Hz. The flash rate cannot be adjusted.

PE-0041-A Page 24 of 211 Issue Date: 21st May 2012


SOUNDER BEACON BASE
The wireless Sounder Beacon Base has an audio output of 90.1 – 92.4 db(A). This can be adjusted by using
the relevant DIL switch (see drawing below). The device has 32 tone options that are selected via DIL switches
(see drawing below) (Common tone options are shown in the table below).

No.  Tone  Description  Switch 23456 


1  LF Sweep  800‐1000Hz @0.5s  11111 
2  Alternative Warble  800/960Hz @ 2Hz  11110 
3  Warble tone  800/1000Hz @ 0.5s 11101 
6  LF Back‐up Alarm  800Hz 150ms on/off  11010 
8  LF Continuous Tone BS5839  800 Hz cont  11000 
10  Intermittent Tone  970Hz  625ms on/off  10110 
11  Continuous Tone  970Hz cont  10101 
17  Interrupted Tone  800Hz 0.5s on / off  01111 
18  ISO 8201 LF BS5839 Pt 1 1988  970Hz 500ms on / 500ms off  01110 
19  Interrupted Tone Medium  1000Hz @0.25s on / off  01101 
21  Continuous Tone  1000Hz continuous 01011 
31  FP 1063.1 – Telecom  Alternating tone 800/970Hz @2Hz  00001 

PE-0041-A Page 25 of 211 Issue Date: 21st May 2012


BEACON
The wireless Beacon provides the installer with the option of a shallow wireless Beacon with a selectable light
output of >0.5Cd or >1Cd with a flash rate of 0.5Hz or 1Hz (user selectable).

FLASH RATE SWITCH


SELECTOR

LIGHT INTENSITY
SWITCH SELECTOR

Switch - hi level Switch - low level

Selected switch level Flash rate switch indicator Light intensity switch selector

Hi Level 0.5 Hz >1Cd (6mA)

Lo Level 1 Hz >0.5Cd (3mA)

When selecting the device flash rate and light intensity rate, projected battery life must be taken in to account –
setting the flash rate to high and setting the device with a high intensity will change the battery lifetime.

Due to the inherent nature of the communication process between the wireless Central Node and the field
devices, it is NOT possible to pulse wireless Audio-Visual devices through the “Cause and Effects” at the Fire
Control Panel. (e.g. If an installation has been programmed at the Fire Control Panel such that Audio-Visual
devices in the non-danger area are to be pulsed, wireless Audio-Visual devices cannot be used).
When installing Audio-Visual devices, the Installation Engineer should note that the distance from its associated
wireless Central Node or Expander may be less than if the device is a Detector or Manual Call Point. The
differential is not significant but care should be taken at the design / survey phase to ensure that this is taken in
to account.

PE-0041-A Page 26 of 211 Issue Date: 21st May 2012


VOICE SOUNDER / ANNUNCIATOR
The Voice Sounder provides the installer with a device that can be programmed with 1 message of up to 32
seconds duration.
NOTE: Fire Control Panels that support this device do not allow the selection of different voice
messages. This is a future improvement of the system.
The voice message must be in *.wav format with a frequency of 16 KHz and a Pulse Code Modulation of 8 bits.
Using the Wirelex Configuration Tool, the following parameters can be altered:
• Power output – this can be amended in 3dB steps to a maximum attenuation of 9dBs
• Two-tone pre-amble – this can be disabled if required (ensure compliance with local standards if
altering this parameter)

RS232 PORT

2-PIN LOUDSPEAKER
OUTPUT CONNECTOR

Refer to Section 7 on the procedure to follow to load messages in to the Voice Annunciator.
Note: The associated wireless Central Node can only support a maximum of 16 output devices (Audio
devices, Audio-Visual devices, Voice Annunciators, Battery Powered Output Modules and externally
powered Output Modules) of the 32 devices that can be programmed in the wireless Central Node
cluster.

PE-0041-A Page 27 of 211 Issue Date: 21st May 2012


BEAM DETECTOR
The wireless Beam Detector is a reflective Beam that provides the installer with the option of providing high
level Beam protection. The Beam Detector has been designed to cover distances to approximately 100 metres.
When learning a Beam Detector on to a compatible Fire Control Panel, the device learns on as a Smoke
Detector.
The primary method of powering the wireless Beam Detector is to use CR123 batteries. However, there is an
option to power the Beam Detector from an external power source.
To align the Beam Detector to its associated Reflector Plate, a Class 2 red laser is utilised with vertical and
horizontal adjustment wheels to correctly place the detection beam (the laser is only powered on during the
installation phase).
Device parameters can be altered using the Wirelex Configuration Tool (see page 77 for further details)

PE-0041-A Page 28 of 211 Issue Date: 21st May 2012


INTELLIGENT WIRELESS TRANSLATOR MODULE
INSTALLATION AND PROGRAMMING GUIDELINES

PE-0041-A Page 29 of 211 Issue Date: 21st May 2012


SECTION 2 – CENTRAL NODE INSTALLATION / LOCAL PROGRAMMING
INTRODUCTION…………………………………………………………………………………………. Page 30
RANGE BETWEEN CENTRAL NODE / EXPANDER MODULE AND FIELD DEVICE….………. Page 32
MAXIMUM THEORETICAL RANGE…………………………………………………………………… Page 32
FEATURES……………………………………………………………………………………………….. Page 33
SPECIFICATION…………………………………………………………………………………………. Page 33
WIRING CONNECTIVITY……………………………………………………………………………….. Page 34
TRANSLATOR MODULE MENU……………………………………………………………………… Page 35
TRANSLATOR MODULE MENU STRUCTURE……………………………………………………. Page 38
TRANSLATOR MODULE PUSH BUTTON OPERATION………………………..………………… Page 39
SETUP PROCEDURE……………………………………………………………………………………. Page 39
TRANSLATOR MODULE PRELIMINARY PROGRAMMING………….…………………………... Page 39
WIRELESS DEVICE START ADDRESS…….……………………………………………………….. Page 40
NOTIFIER / HONEYWELL PROTOCOL DEVICE START ADDRESS…………………………….. Page 40
WIRELESS FIELD DEVICE PROGRAMMING…..…………………………………………………… Page 41
TRANSLATOR MODULE LED INDICATIONS……………..………………………………………… Page 42
TRANSLATOR MODULE LCD INDICATIONS...................…….…………………………………… Page 42
TRANSLATOR MODULE PROGRAMMING……………………….…………………………………. Page 43
PROGRAMMING PROCEDURE…………………………..…………………………………. Page 43
PUSH BUTTON AND LED INDICATIONS………………..…………………………………. Page 43
MENU STRUCTURE AND GUIDES…………………………..………………………………. Page 43
INITIAL TRANSLATOR MODULE CONFIGURATION……………………………………………. Page 43
TRANSLATOR MODULE POWER UP………………………………………………………………… Page 43
LOOP DEVICE CONFIGURATION…………………………………………………………………….. Page 44
FIELD DEVICE POWER CELLS……………………………………….………………………………... Page 44
FIELD DEVICE CONFIGURATION……………………………………………………………………... Page 44

PE-0041-A Page 30 of 211 Issue Date: 21st May 2012


INTRODUCTION
The choice of wireless Central Node is dependent on the associated Fire Control Panel (FCP):
• Vega Protocol Use a Vega Translator Module
• Analogue FCP using a supported protocol Use the associated Translator Module
• Analogue FCP using protocol other than above Use a Conventional Expander Module
• Conventional FCP Use a Conventional Expander Module.
The wireless Central Node provides a simple way of expanding a pre-existing, or new hard-wired system, using
the wireless Central Node, Expanders (if required) and its associated range of wireless devices.

To program the Translator Module:


• Set detection loop Start Address
• Set System Code
• Set Radio Channel
• Initialise Translator Module
• Program the field devices on to the Translator Module
• Auto-learn the FCP with the wireless field devices
• Program the FCP Cause and Effects (if necessary)
• Program the associated Graphics Interface (if fitted)
Programming of the Translator Module is relatively straightforward. It can be carried out locally at the
Translator Module or using the Wirelex Configuration Tool.
The Translator Module is loop-powered. Child device loading is limited to 32 wireless devices – a mix of
initiating and alarm devices.

To program the Conventional Expander Module


• If connecting to an analogue FCP using a different protocol:
o Power on the Conventional Expander Module(CEM) from its external 24V dc supply
o Connect and terminate correctly the Zone Monitor Unit (or equivalent) at the Conventional
Expander Module
o Connect and terminate correctly the Sounder Control Card (or equivalent) at the
Conventional Expander Module
o Set system code on the Conventional Expander Module using the Wirelex software
o Set radio channel on the Conventional Expander Module using the Wirelex software
o Program the Conventional Expander Module using the Wirelex software
o Program field devices on to the Conventional Expander Module
o Auto-learn the analogue FCP
o Program the analogue FCP Cause and Effects (if required)
o Program the associated Graphics Interface (if fitted)

PE-0041-A Page 31 of 211 Issue Date: 21st May 2012


• If connecting to a Conventional FCP:
o Power on the Conventional Expander Module from its external 24V dc supply
o Connect and terminate the required detection Zone at the Conventional Expander Module
o Connect and terminate correctly the radial Sounder circuit at the Conventional Expander
Module
o Set system code of the Conventional Expander Module using the Wirelex software
o Set radio channel of the Conventional Expander Module using the Wirelex software
o Add field devices to the Conventional Expander Module using the Wirelex software
o Program Conventional Expander Module
o Program field devices
o Program Conventional Expander Module

PE-0041-A Page 32 of 211 Issue Date: 21st May 2012


RANGE BETWEEN CENTRAL NODE / EXPANDER MODULE AND FIELD DEVICE
The maximum distance between the wireless Central Node, Expander(s) and field devices is mainly affected by
the fabric / structure of the building – a timber frame construction will give coverage over greater distances than
if the wireless Central Node or Expander is used in a building constructed of a heavy ferrite core or one using
reinforced concrete. The maximum distance in open air is:

Central Node Field Device Expander Module Field Device

150m 150m

250m

MAXIMUM THEORETICAL RANGE


If a wireless system were to be configured with the maximum number of layers (6) of wireless Central Node and
Expanders, the maximum distance that could be achieved between the wireless Central Node and the
Expander is:
Note: this distance is in open air

Interface Expander 1 Expander 2 Expander 3 Expander 4 Expander 5 Field Device

250m 250m 250m


250m 250m 150m

1400m

PE-0041-A Page 33 of 211 Issue Date: 21st May 2012


FEATURES
• Simple and full integration into hard-wired systems.
• The application of wired and wireless devices allows a fast adaptation to the changes on site.
• A maximum of 6 Translator Modules can be connected to a single fire detection loop.
• A maximum of two Conventional Expander Modules can be used per detection zone
• For each wireless Central Node cluster up to 32 analogue addressable devices (initiating and alarm
devices) can be connected. It should be noted that each wireless Central Node can only support a
maximum of 16 output devices (Audio-Visual devices, Audio devices and Output Modules) within the 32
devices in the cluster.
NOTE: The Conventional Expander Module does not currently support Powered Output Modules
and / or Battery Output Modules
• Multi-channel frequency operation.
• Main battery life: - 3 to 5 years typical (field devices).
• Backup battery life: - 2 months typical (field devices).
• Low battery alarm (field devices).
• Immediate transmission signals from field devices: Alarm, Fault and Tamper.
• Transmission of status and analogue values.
SPECIFICATION
• Colour: White
• Dimensions: 120 x 160 x 51 (without antennae)
• Operating Frequency: 868 - 870 MHz
• Radiation power: 5dBm (3mW)
• Modulation Type: Frequency Shift Keying (FSK)
• Number of frequency channels: 7
• Power supply voltage: 15 – 40Vdc (Translator Module)
10 - 27Vdc (Conventional Expander Module)
• Current consumption: 20mA (Translator Module)
30mA (@24Vdc in alarm) (Conventional Expander Module)
• Operating temperature: -30°C to +50°C

INSTALLATION
It is recommended that the wireless Central Node, and subsequent Expanders, if fitted, be mounted at a height
from the ground of approximately 2 – 2.5 metres in an orientation such that the vertical antenna is pointing
towards the ground; the horizontal antenna is pointing to the right. Installation in any other aspect may affect
system integrity and performance.

PE-0041-A Page 34 of 211 Issue Date: 21st May 2012


WIRING CONNECTIVITY

The figure below shows the location of the push-buttons (on the Translator Module) used during the
programming process. It also indicates the location of the Translator Module LEDs - the use of these LEDs is
explained throughout this manual. Detection loop connectivity is also shown:

LOOP OUTPUT +
LOOP OUTPUT -

LOOP INPUT +
LOOP INPUT -

DIODE LIGHT (LED) DIODE LIGHT (LED)


DL3 DL4

DIODE LIGHT (LED) DIODE LIGHT (LED)


DL2 DL5

DIODE LIGHT (LED) DIODE LIGHT (LED)


DL1 DL6

PUSHBUTTON P1
Exit out of a sub-menu. Allows the user to exit from a menu if do
not want to accept changes made.
PUSHBUTTON P2
To enter into a menu. Allows the user to enter sub-menus or to
confirm changes made to system parameters or devices.
PUSHBUTTON P3
To navigate through menus. To change system parameters
(increase)
PUSHBUTTON P4
To navigate through menus. To change system parameters
(decrease)

PE-0041-A Page 35 of 211 Issue Date: 21st May 2012


TRANSLATOR MODULE MENU
• BLANK ( ): This is the normal operating level. In this condition the Translator Module is connected
to the loop and working and is fault free – or it has had power removed from it.

NOTE: When the Translator Module LCD screen is active, the Fire Control Panel will go in to fault showing
“DISCONNECTED FAULTS” for all the devices attached to that particular Translator Module. When the
LCD screen is blank, the faults will disappear and full operational integrity is restored.

• LOOP ( ): This menu contains the parameters required to correctly interface the Translator Module
and associated child device on to the fire detection loop.

• LOOP START ADDRESS ( ): Enter this sub-menu to change the starting Fire Control Panel address
for the Translator Module (Vega protocol) and associated radio field devices.

Note: For HBS and Notifier protocol Translator Modules, this menu option sets the loop start
address for Sensor devices.

• LOOP MODULE ADDRESS ( ) (for Honeywell and Notifier protocol Translator Modules): Enter this
sub-menu to change the starting loop detection address for field Module devices – Manual Call Points,
Audio-Visual devices, Input Modules and Output Modules.

• CLEAR PROGRAMMING GAPS ( ): If devices have been deleted from the program and gaps have
been created in the addressing sequence, this command removes those gaps. Care must be taken when
using this command as Fire Control Panel detection loop addressing for some devices will change.

NOTE: This command is only present in Vega protocol Translator Modules.

• RF PROGRAMMING ( ): This menu contains all the parameters related to the Translator Module.

• TRANSLATOR ( ): This sub-menu changes the RF parameters necessary for the correct functioning
of the Translator Module.

• SYSTEM CODE ( ): The System Code is a number in the 0-255 range. Change the System Code
value using the P3/P4 pushbuttons and confirm by pressing the P2 pushbutton. To store the changes, it is
necessary to initialise the Translator Module.

• RF CHANNEL ( ): The RF channel is a number in the 1-7 range. Translator Modules with different RF
channels will not interfere with each other. Change the RF Channel value using the P3 / P4 pushbuttons
and confirm the change by pressing the P2 pushbutton. To store the changes, it is necessary to initialise
the Translator Module.

• INITIALIZE ( ): Use this sub-menu to store the updated System Code and / or RF channel into the
Translator Module memory. After confirming with the P2 pushbutton the new values will be used.

PE-0041-A Page 36 of 211 Issue Date: 21st May 2012


NOTE 1: After the Initialise process, all RF devices previously linked to the Translator Module will need
to be re-programmed!!! (This process is only used during initial installation).
NOTE 2: If using multiple Translator Modules in a single installation, care should be taken that each
Translator Module employs a different System Code and site diversity is employed to ensure the zone
inter-visibility for each radio channel is kept to a minimum.
NOTE 3: The internal system encryption is set up during this process and is relayed to all associated
devices. If an initialisation is carried out, this encryption will be changed and the Translator Module will
not communicate with the associated devices.
• RESET ( ): Use this sub-menu to perform a soft reset of the Translator Module. After confirming with
the P2 pushbutton all the RF devices linked to the Translator Module will be reset from an existing fire and
fault condition. This action is used to assist engineers on site with diagnosing soft faults or hard faults – soft
faults will clear after a RESET command; hard faults will re-appear making the fault-finding process quicker.

• LOAD CONFIGURATION ( ): Use this sub-menu to load the system configuration from the RF PCB
in to the Translator Module Processor PCB. After confirming the request with the P2 pushbutton, the
Translator loads the configuration and performs a reset procedure. This is used when programming a
Translator Module using the Wirelex Software Configuration Tool.

• DETECTOR ADDRESS ( ): Enter this sub-menu in order to add or delete wireless sensor devices:
– POINT DETECTORS ( ): Enter this sub-menu in order to add or delete wireless Detectors
– BEAM DETECTORS ( ): Enter this sub-menu in order to add or delete wireless Beam
Detectors

• INPUT DEVICES ( ): Enter this menu to add or delete Input devices other than Detectors:

– INPUT MODULES ( ): Enter this sub-menu in order to add or delete a Radio Input Module.

– CALL POINTS ( ): Enter this sub-menu in order to add or delete a Radio Call Point.

• OUTPUT DEVICES ( ): Enter this menu in order to add or delete output devices:

– EXTERNALLY POWERED OUTPUT MODULE ( ): Enter this sub-menu in order to add or


delete an externally powered wireless Output Module.

– SOUNDERS ( ): Enter this sub-menu in order to add or delete a wireless Sounder, Sounder
Base, Sounder Beacon or Sounder Beacon Base.

– BATTERY POWERED OUTPUT MODULE ( ): Enter this menu in order to add or delete a
battery powered wireless Output Module.

– BEACON ( ): Enter this menu in order to add or delete a wireless Beacon.

– VOICE SOUNDER ( ): Enter this menu to add or delete a wireless Voice Sounder.

• INFO ( ): This is the sub-menu that contains the information about the RF devices.

• ADD DEVICE ( ): Select one of these menus in order to add a new radio device to the Translator
Module. After confirming with pushbutton P2, the LCD will display the “link” indication and LED DL4 will turn
on. Follow the instructions as indicated in the “Device Programming” paragraph.

PE-0041-A Page 37 of 211 Issue Date: 21st May 2012


• DEL DEVICE ( ): Select one of these menus in order to delete a radio device from the Translator.
Press pushbutton P2 to enter the menu. Scroll through the devices listed using pushbuttons P3/p4 until the
FCP loop address required is displayed. Press pushbutton P2 to delete the device. will be
displayed. Press P2 to confirm deletion (the LCD will display if no devices are available for
deletion).

• LIST ( ): Use this sub-menu in order to retrieve the information about devices linked to the
Translator Module. The information available to the user is the Translator Module and wireless field device
address along with the device type.

• PROTOCOL ( or or or ): This option indicates the protocol the Translator


Module is configured with. Pressing P2 when one of the legends is visible on the LCD screen will display
three digits indicating the Translator Module firmware.

PE-0041-A Page 38 of 211 Issue Date: 21st May 2012


TRANSLATOR MODULE MENU STRUCTURE

(only in Notifier or Honeywell variants)


(not present in Notifier or Honeywell variants)

If the indication appears when programming field devices, check the Start Address (Sensors/Modules
( / )) is set to a value no higher than the last protocol supported loop address

PE-0041-A Page 39 of 211 Issue Date: 21st May 2012


PE-0041-A Page 40 of 211 Issue Date: 21st May 2012
TRANSLATOR MODULE PUSH BUTTON OPERATION
Local programming of the Translator Module is carried out using the four pushbuttons (P1-P4) mounted on the
main Translator Module PCB (the one with the LCD screen). The selected / proposed action will be shown on
the LCD screen. The Translator Module menu flow chart is shown on page 38. The push button functions are
detailed on pages 35 - 37.
There are limitations to locally programming the Translator Module using the pushbuttons. The Commissioning
Engineer is not able to change the operational parameters of the field devices and must use the default values.
SETUP PROCEDURE
Procedure for programming the associated wireless devices on to an analogue detection loop is as follows:

• Connect the Translator Module to the FCP via the detection loop cabling (see loop connectivity on page 34).
• Program the Translator Module RF parameters.
• Program the field devices on to the Translator Module.
• Program the Fire Control Panel.
TRANSLATOR MODULE PRELIMINARY PROGRAMMING
• Power on the Translator Module by connecting it to the detection loop. The LCD display will illuminate
initially then go blank. If there is a problem with the initialisation, a
indication will be displayed. Should this happen, power down the Translator Module, wait
approximately 20 seconds and then re-apply power. If this does not clear the problem, the Translator
Module should be exchanged.
• Using P3/P4 pushbuttons scroll to the menu; select by pressing P2. Select the Translator menu ( )
by pressing P2. Scroll to the option pressing P2 to enter. A three digit number will appear that can be
altered by pressing the P3/P4 pushbuttons – this is a decimal representation of the system code – the
system code can be a number between 0 - 255. When a code has been selected, press P2 to confirm. A
small house symbol ( ) will appear next to . This indicates that the system will need to be initialised
for the new system code to be stored in the Translator Module’s non-volatile memory.
(NOTE: Translator Modules with different channels will not interfere with each other. Careful selection of
system codes and initial operating channels should be taken when installing a multi Translator Module
system. It is advisable to select a different radio channel and a different system code for each Translator
Module).
• Using P3/P4 pushbuttons scroll down until the Channel option ( ) appears. Press P2 to enter this option.
A number will appear in the range 1 - 7. Using the P3/P4 pushbuttons select the radio channel required for
the Translator Module. Press P2 to confirm. A small house symbol ( ) will appear next to . This
indicates that the system will need to be initialised for the new system radio channel to be stored in the
Translator Module’s non-volatile memory.
The System Code and Radio Channel must not be the same for all Translator Modules on a fire detection loop
or within a complete installation – the number of system codes available is sufficient for an installer to comply
with this requirement. In the majority of systems, the Radio Channel chosen will have little effect. However, in a
small number of systems, during the commissioning procedure it may become evident that one of the channels
has a large amount of interference, or traffic from another system or source, and this can then be avoided by
selection of a different channel. If the system is left operating on the noisy channel, it will still operate but the
battery life of the field devices may be reduced due to the system dealing with the excess noise.
NOTE: There is a utility available on the associated software that will assist the engineer with assessing the
background RF environment. For more information on this utility refer to Section 7 of this manual. Before using
the Translator Module, the engineer will need to program the operational radio channel for the Translator
Module and all devices associated with the Translator Module cluster.

PE-0041-A Page 41 of 211 Issue Date: 21st May 2012


• Save the changes made to the Translator Module selecting the Initialisation ( ) option. During the
initialisation process, the symbol will be seen on the Translator Module LCD display. This indicates
the Translator Module is processing and storing the System Code and Radio Channel selected. If the
initialisation succeeds will be displayed, else will be displayed.

• Program the Translator Module Start Address. The Start Address is the detection loop address assigned to
the Translator Module in the FCP. All radio field devices will be contiguously addressed when programmed
on to the Translator Module.

• Proceed with wireless field device programming (see WIRELESS FIELD DEVICE PROGRAMMING page
41)

• On completion of all device programming, press P3/P4 buttons and scroll to the menu, press P2 and
scroll through the listed devices using P3/P4 pushbuttons. This indicates that all devices have been learnt
on to the Translator Module successfully and are ready to be programmed on to the FCP.
(Note: If using the Wirelex Configuration Tool to program the system, the menu will only display the
Translator Module address until the command is carried out).

• On completion, exit from all Translator Module menus pressing P1 push-button until the LCD display is
blank.

WIRELESS DEVICE START ADDRESS


Using P3/P4 keys scroll up/down until is displayed. Press P2 key to confirm. Use P3/P4
push-buttons and scroll to (Start Address). Press P2 to select this option. Using P3/P4 push-buttons, set
the start address for the Translator Module. Confirm the value pressing P2. On completion press P1
push-button to exit (The devices will be addressed contiguously from the address set in this action). The Start
Address will be assigned to the Translator Module. All field devices will be assigned to contiguous addresses.
e.g. 1 Translator Module + 2 Manual Call Points on Fire Detection Loop 1 with Translator Module start address
= 110.
Translator Address Address Seen at Control Panel
Translator Module address 110 110
Manual Call Point 1 address 111 111
Manual Call Point 2 address 112 112
NOTIFIER / HONEYWELL PROTOCOL DEVICE START ADDRESS
Within the Notifier / Honeywell protocols, Sensors and Modules are controlled in different menus. To that end,
the start address will need to be set for both options.

Using P3 / P4 keys scroll up/down until is displayed. Press P2 key to confirm. Use P3 / P4
push-buttons to scroll to (Sensor Start Address). Press P2 to select. Using P3 / P4 push-buttons, set the
start address for the first Sensor associated with this particular Translator Module. Confirm the value pressing
P2. After pressing P2 the screen will drop back to display . All devices will be addressed contiguously
from this address.
Use P3 / P4 push-buttons scrolling down to display the word (Module Start Address). Press P2 to select.
Using P3 / P4 push-buttons set the start address for the first module on the system – this will always be the
Translator Module. On completion press P1 push-button to exit (The remaining modules will be addressed
contiguously from the address set in this action). All field devices will be assigned to contiguous addresses.

PE-0041-A Page 42 of 211 Issue Date: 21st May 2012


WIRELESS FIELD DEVICE PROGRAMMING
(NOTE:- Prior to commencing any device programming, ensure the Primary (CR123A) and Secondary
(CR2032) power cells are available. The secondary cell is fitted to the device with the positive (+) side
uppermost. This must be fitted prior to any programming, and must be fitted with the switch in the 1 position.
The primary and secondary power cells in Audio-Visual devices and the Battery Powered Output Module are
CR123A types).
On the wireless device being programmed set the jumper into the ON position before proceeding any further.
To add a device, use the P3/P4 keys and scroll up/down until is displayed. Confirm using the P2 key. Use
P3/P4 key to select the appropriate menu:
( for Detectors, for input devices, for output devices) (If adding an Input device or an Output
device, select the correct device first before proceeding).
Use P3/P4 key to select . Confirm using the P2 key.
The display will show the “link” ( ) indication and LED DL4 will turn on. Insert the primary power cell and
wait until the RF device LED indicator has blinked RED 4 times (to indicate the device has powered on and is
entering in to programming mode).
Switch the RF device jumper from ON to the 1 position. The RF device LED will flash GREEN (showing that
initial programming is completed), which is followed by the LED blinking RED for a short period of time. The
device will then flash GREEN two more times before extinguishing.
The Translator Module LCD screen will display the address assigned to the device and DL4 LED will turn off.
Programming for that device is now complete.
(Note: if the device is not placed or put back in to its base / back-box within 20 seconds of completion of device
programming, a fault indication will appear on the Translator Module LCD screen (the analogue loop address
for that device and a spanner symbol indicating a “Tamper” fault)).
Press P1 push-button to return to the device menu. Repeat the above for all devices that are to be added on to
that particular Translator Module.
On completion of programming all field devices on to the Translator Module, the Translator Module and field
devices can now be programmed on to the associated Fire Control Panel as if they were normal hardwired
devices. The devices can be learnt on to the Fire Control Panel using the “Autolearn” process.

PE-0041-A Page 43 of 211 Issue Date: 21st May 2012


TRANSLATOR MODULE LED INDICATIONS
The following table shows the possible fault display on the LCD screen of the Translator Module according to
the events generated by wireless field devices and Expanders (if fitted):
DL1: blinks when the Translator Module is being polled by the FCP.
DL2: indicates a system fault condition. This is to be investigated using the Wirelex software tool
DL3: illuminates constantly to indicate that a wireless device has reached a low power level threshold, e.g. the
primary power cell should be replaced – the LCD will display the analogue loop address of the affected device.
DL4: illuminates when the Translator Module is searching for a radio device.
DL5: illuminates and the device type is displayed on the Translator Module when interrogated locally
DL6: not used

TRANSLATOR LCD DISPLAY INDICATIONS

Primary battery level for device with analogue loop address 138 is low

Secondary battery level for device with analogue loop address 138 is low

Wait indication. The Translator Module is performing a time consuming action

When carrying out changes to the system, a confirmation of action is requested

The last action performed has been completed successfully

A wireless device has gone in to a fire condition

The Translator Module is radio linking to a field / child device

Indicates a fault with a device and is accompanied by the device analogue address – this
icon normally appears if the associated field device is in a tamper condition

Indicates a problem with a child Expander associated with the Translator Module (The n
will be a number between 1 and 7)
Indicates there is an error in communication between the front processor PCB and the
rear radio PCB. The ribbon cable connecting the two PCBs should be checked for
correct insertion
Indicates a fatal error with the Translator Module. Or the last action has generated an
error

This indicates there are no more loop addresses available

This indicates that the radio PCB and the analogue PCB are not synchronised and a
“LOAD” command must be carried out

PE-0041-A Page 44 of 211 Issue Date: 21st May 2012


TRANSLATOR MODULE PROGRAMMING
PROGRAMMING PROCEDURE
The following step-by-step procedure should be used to program the Translator Module:

• Initial Translator Module configuration

• Translator Module Cluster configuration

• RF Device programming

• Translator Module configuration load

• FCP configuration

PUSH BUTTON AND LED LOCATIONS


For the location and use of the Translator Module’s indication LEDs and control push buttons refer to the
illustration on page 34.

MENU STRUCTURE AND GUIDES


For a comprehensive overview of the system menus and structure refer to the descriptions and illustrations on
pages 35 - 38.

INITIAL TRANSLATOR MODULE CONFIGURATION


This section covers the set up of the main Translator Module properties.

Note: When the buttons on the front of the Translator Module are being used to configure the system,
communication with the FCP will be lost and therefore a “LOOP DISCONNECTED FAULT” indication will be
displayed on the FCP. This fault will clear on completion of programming.

TRANSLATOR MODULE POWER UP


To configure the Translator Module it is necessary to be connected to a live fire detection loop. Connect the fire
detection loop cabling as per page 34 and apply power to the loop. The Translator Module LCD screen will
illuminate initially then go blank.

If the Translator Module does not initialise correctly, a indication will be displayed. Should this happen,
power down the Translator Module, wait 20 seconds and re-apply power. If this does not clear the problem, the
Translator Module should be exchanged.

NOTE: If there is a requirement to program the system prior to attending site and a FCP is not available, it is
possible to power on the Translator Module from a stand-alone 24V dc Power Supply Unit. Programming of all
devices can then be carried out using the local programming buttons or using the Wirelex software. On
completion of all programming, the Translator Module can be powered down and the device power cells should
be removed – all programming will be retained in the non-volatile memory of the Translator Module and child
devices.

PE-0041-A Page 45 of 211 Issue Date: 21st May 2012


LOOP DEVICE CONFIGURATION
The wireless devices on the system will each take an analogue detection loop address on the FCP - one for
each field device and one for each Translator Module. (Expanders do NOT take a detection loop address –
they are transparent to the FCP).

FIELD DEVICE POWER CELLS


Prior to commencing any device programming, ensure the field device primary power cell (CR123A) and
secondary power cells (CR2032) are available. The secondary power cell is fitted to the device with the
positive (+) side upper most. This must be fitted prior to any programming.
Power cells for field devices should not be fitted until immediately prior to programming. Fitting cells prior to this
may foreshorten cell longevity.

FIELD DEVICE CONFIGURATION


The Translator Module and wireless devices can now be learnt onto the system in the same way as normal
analogue wired devices from the front of the Fire Control Panel or configured using the Fire Control Panel
configuration tool. (Refer to the Fire Control Panel manual for further details).
All wireless field devices should be configured to an appropriate device type, in the same way an analogue
device is configured.

PE-0041-A Page 46 of 211 Issue Date: 21st May 2012


INTENTIONALLY BLANK

PE-0041-A Page 47 of 211 Issue Date: 21st May 2012


WIRELESS EXPANDER MODULE
INSTALLATION GUIDELINES

PE-0041-A Page 48 of 211 Issue Date: 21st May 2012


SECTION 3 –WIRELESS EXPANDER MODULE INSTALLATION GUIDELINES
INTRODUCTION …………………………………………………………………………………………. Page 47
SPECIFICATION………………………………………………………………………………………….. Page 47
CABLING TERMINATION – MONITORED POWER SUPPLY UNIT .........………………………. Page 48
CABLING TERMINATION – NON-MONITORED POWER SUPPLY UNIT ...……………………. Page 49
PROGRAMMING………………………………………………………………………………………… Page 49
EXPANDER MODULE CONFIGURATION AND TOPOLOGY……………………………………. Page 50

INTRODUCTION
The Expander is used to extend the geographic range of a Central Node in order to program wireless field
devices that would otherwise have received too weak a radio signal to work efficiently.
A maximum of 7 Expanders can be connected to one Central Node. It should be noted that only a maximum of
32 devices can still be programmed on to the Central Node – adding Expanders does not increase the number
of field devices that can be associated with a Central Node.
Each Expander receives a digital address from the Central Node in order to be identified. Examples of this
addressing can be seen on pages 50 / 51.
An Expander requires an external power source (EN54 battery backed PSU) of 24Vdc. It should be noted that
the Expander will function correctly with an input voltage of 10 – 27Vdc.

SPECIFICATION
• Multi-channel frequency operation.
• Immediate transmission signals from field devices: Alarm, Fault and Tamper.
• Transmission of status and analogue values.
• Colour: White
• Dimensions: 116 x 107 x 65 (without an antenna)
• Operating Frequency: 868 - 870 MHz
• Radiation power: 0.01 - 3mW
• Modulation Type: Frequency Shift Keying (FSK)
• Number of frequency channels: 7
• Power supply voltage: 10 - 27Vdc
• Current consumption ≤15mA (@ 24Vdc)
• Operating temperature: -30°C to +55°C

PE-0041-A Page 49 of 211 Issue Date: 21st May 2012


CABLING TERMINATION - MONITORED POWER SUPPLY UNIT (PSU)
The diagram indicates the connections required to connect a monitored PSU to an Expander.

Maximum current (I) consumption of the Expander is ≤ 15mA (@24V dc)

FAULT RELAY

To connect the EM to a monitored 24V D.C. PSU:

Connect the +24V PSU output to the +and –connections of the Expander

Connect the MM and BM connector of the Expander to the PSU controlled relay as indicated (In this scenario, it
is assumed that the PSU fault relay opens when reporting a fault)

Fit a small jumper link between the “+” terminal and the “MM” terminal.

The “MM” and “BM” Expander inputs monitor the primary and the backup power supply voltage levels.

PE-0041-A Page 50 of 211 Issue Date: 21st May 2012


CABLING TERMINATION - NON-MONITORED POWER SUPPLY UNIT (PSU)
The diagram below indicates the connections required to connect a non-monitored PSU to an EM.

Maximum current consumption of the Expander is ≤ 15mA (@24V dc).

NOTE: If using a non-monitored PSU (as above), care must be taken that the system conforms to local
standards and codes of practice.

PROGRAMMING
The Expander can ONLY be programmed using the Wirelex Configuration Tool software supplied with the
Central Node.

The Expander and associated devices should be programmed in accordance with Section 6.

To use the Wirelex Configuration Tool, connect a laptop computer to the RS232 connector on the Expander
front PCB - a standard RS232 cable is to be used.

PE-0041-A Page 51 of 211 Issue Date: 21st May 2012


EXPANDER MODULE CONFIGURATION AND TOPOLOGY
Expanders are used in association with a Central Node:- one Central Node can communicate to a maximum of
seven Expanders:

This configuration employs the maximum number of Expanders (7). Each Expander can have field devices
associated with it.

There can be no more than 3 Expanders on one layer due to the digital addressing employed by the Central
Node to recognise each Expander.

A Central Node cluster (as shown above) can have a maximum of 32 field devices associated with it.

The “…n:” is the digital sub-address given to a wireless field device and forms part of the unique identifier for
that device.

PE-0041-A Page 52 of 211 Issue Date: 21st May 2012


An alternative configuration is shown below:

This configuration employs a MAXIMUM of six layers of wireless Interfaces (the top layer is always a Central
Node (as shown above). This is due to the digital addressing employed between the Central Node and the
Expanders.

The “…n:” is the digital sub-address given to a wireless field device and forms part of the unique identifier for
that device.

PE-0041-A Page 53 of 211 Issue Date: 21st May 2012


WIRELESS
CONVENTIONAL EXPANDER MODULE
INSTALLATION GUIDELINES

PE-0041-A Page 54 of 211 Issue Date: 21st May 2012


SECTION 4 – WIRELESS CONVENTIONAL EXPANDER MODULE INSTALLATION GUIDELINES
INTRODUCTION……………………………………………………………………………………….. Page 53
SPECIFICATION……………………………………………………………………………………….. Page 53
CONVENTIONAL EXPANDER MODULE FRONT PCB TERMINATIONS……………………… Page 54
CABLING TERMINATION – MONITORED POWER SUPPLY UNIT……………………………. Page 55
CABLING TERMINATION – NON MONITORED POWER SUPPLY UNIT………………………. Page 56

INTRODUCTION
The Conventional Expander Module is used to provide:
• A conventional zone of wireless alarm and detection devices when connected to a Conventional Fire
Control Panel (wireless Battery Powered Output Modules and externally powered Output Modules cannot
be used with the Conventional Expander Module)
• A conventional zone of wireless alarm and detection devices when connected to a non-supported protocol
Fire Control Panel via a Sounder Control Card (alarm devices) and a Zone Monitor Unit (detection devices),
or equivalent.
Standard child Expanders can be used with this device up to a maximum of 7. Configuration of the
Conventional Expander Module can only be achieved using the Wirelex Configuration Tool.
It should be noted that a maximum of 32 devices can programmed on to the Conventional Expander Module –
adding Expanders does not increase the number of field devices that can be associated with this device.
Each Expander receives a digital address from the Conventional Expander Module in order to be identified.
Examples of this addressing can be seen on pages 50 - 51.
A Conventional Expander Module requires an external power source (EN54 battery backed PSU) of 24Vdc.

SPECIFICATION
• Multi-channel frequency operation.
• Immediate transmission signals from field devices: Alarm, Fault and Tamper.
• Colour: White
• Dimensions: 116 x 107 x 65 (without an antenna)
• Operating Frequency: 868 - 870 MHz
• Radiation power: 0.01 - 3mW
• Modulation Type: Frequency Shift Keying (FSK)
• Number of frequency channels: 7
• Power supply voltage: 10 - 27Vdc
• Current consumption ≤30mA (@ 24Vdc)
• Operating temperature: -30°C to +55°C

PE-0041-A Page 55 of 211 Issue Date: 21st May 2012


CONVENTIONAL EXPANDER MODULE FRONT PCB TERMINATIONS
The schematic below indicates the terminations at the Conventional Expander Module

Termination Details

Power Supply + } Connect external +24V dc power supply


Power Supply – }

Main Monitoring } Monitoring circuit for external power supply – not used if
Backup Monitoring } using +24V from the associated Fire Control Panel

Zone Alarm Resistor + } As defined by the Fire Control Panel


Zone Alarm Resistor – }

Zone EOL Resistor + } As defined by the Conventional Fire Control Panel or the
Zone EOL Resistor - } Zone Monitor Unit

Zone Line + } Connections from the required zone of a Conventional Fire Control
Zone Line - } Panel or the associated Zone Monitor Unit

Sounders Line + } Connections to a radial Sounder circuit from a Conventional


Sounders Line - } Fire Control Panel or from a Sounder Control Card

Sounder EOL Resistor + } As defined by the Conventional Fire Control Panel or the
Sounder EOL Resistor – } associated Sounder Control Card

PE-0041-A Page 56 of 211 Issue Date: 21st May 2012


CABLING TERMINATION - MONITORED POWER SUPPLY UNIT
The diagram indicates the connections required to connect a monitored Power Supply Unit to a Conventional
Expander Module.

Maximum current (I) consumption of the Conventional Expander Module is ≤ 30mA (@24V dc)

- + FAULT RELAY

To connect the Conventional Expander Module to a monitored 24V D.C. PSU:

Connect the +24V PSU output to the +and –connections of the Conventional Expander Module

Connect the MM and BM connector of the Conventional Expander Module to the PSU controlled relay as
indicated (In this scenario, it is assumed that the PSU fault relay opens when reporting a fault)

Fit a small wire jumper link between the “+” terminal and the “MM” terminal.

The “MM” and “BM” Conventional Expander Module inputs monitor the primary and the backup power supply
voltage levels.
PE-0041-A Page 57 of 211 Issue Date: 21st May 2012
PE-0041-A Page 58 of 211 Issue Date: 21st May 2012
CABLING TERMINATION - NON-MONITORED POWER SUPPLY UNIT
The diagram below indicates the connections required to connect a non-monitored Power Supply Unit to a
Conventional Expander Module.

Maximum current consumption of the Conventional Expander Module is ≤ 30mA (@24V dc).

- +

NOTE: If using a non-monitored PSU (as above), care must be taken that the system conforms to local
standards and codes of practice.

PROGRAMMING
The Conventional Expander Module can ONLY be programmed using the software supplied.

The Conventional Expander Module and associated devices should be programmed in accordance with Section
5.
To use the Wirelex Configuration Tool, connect a laptop computer to the RS232 connector on the Conventional
Expander Module front PCB - a standard RS232 cable is to be used.

PE-0041-A Page 59 of 211 Issue Date: 21st May 2012


THE WIRELEX CONFIGURATION TOOL -
INSTALLATION AND PROGRAMMING
GUIDELINES

PE-0041-A Page 60 of 211 Issue Date: 21st May 2012


SECTION 5 – SOFTWARE
INTRODUCTION……………………………………………………………………………………….. Page 59
LOADING SOFTWARE…………………………………………………………………………..……. Page 60
START SYSTEM CONFIGURATION…………………………………………..…………………..… Page 66
ADDING FIELD DEVICES TO THE TRANSLATOR MODULE..............……….....…….......…… Page 70
ADDING A MULTI-CRITERIA DETECTOR………………………………………………………..... Page 70
ADDING AN OPTICAL SMOKE DETECTOR……………………………………………........……. Page 72
ADDING A THERMAL DETECTOR………………………………………………………….....…….. Page 74
ADDING A MANUAL CALL POINT…………………………………………………………………… Page 76
ADDING AN INPUT MODULE……………………………………………………………………....… Page 78
ADDING A MAINS POWERED OUTPUT MODULE…………………………………………...…… Page 80
ADDING A SOUNDER/SOUNDER BEACON/BASE SOUNDER/BASE SOUNDER BEACON Page 82
ADDING A VOICE SOUNDER / ANNUNCIATOR………………………………………………….. Page 84
ADDING A BATTERY POWERED OUTPUT MODULE………………………………………...….. Page 87
ADDING A BEACON……………………………………………………………………………………. Page 89
ADDING A BEAM DETECTOR.................................................................................................... Page 91
PROGRAMMING THE TRANSLATOR MODULE AND ASSOCIATED DEVICES………………. Page 93
PROGRAMMING FIELD DEVICES………………………………………………………………….… Page 99
THE LOAD PROCESS…………………………………………………………………………….…….. Page 102
THE W2W TABLE………………………………………………………………………………....……. Page.104
ADDITIONAL WIRELEX FACILITIES…………………………………………………………………. Page 108
USE OF STATUS TAB……………………………………………………………………………..…… Page 108
EXAMPLES OF DISPLAYED FAULTS……………………………………………………………….. Page 112
TAMPER FAULT……………………………………………………………………………..…. Page 112
SECONDARY POWER CELL DISCHARGE……………………………………………..… Page 112
SUBSTITUTION ATTEMPT………………………………………………………….………. Page 113
NO RADIO LINK / NO LINK………………………………………………………………… Page 113
GENERAL FAULT………………………………………………………………………..……. Page 114
USE OF RF LINK QUALITY TAB…………………………………………………………………… Page 116
LINK QUALITY TAB – CHILD DEVICE SECTION………………………………………… Page 117
LINK QUALITY HISTORY GRAPH…………………………………………………………………... Page 118
ZOOM IN ON RF GRAPH…………………………..……………………………………….. Page 119
RETURN TO NORMAL GRAPH VIEW……………………………………………………………… Page 119
SYSTEM CONFIGURATION CODE HEXADECIMAL-DECIMAL CONVERSION TABLE…… Page 120

PE-0041-A Page 61 of 211 Issue Date: 21st May 2012


INTRODUCTION

This section explains the facilities available to an engineer when using the Wirelex Configuration Tool :
• The Wirelex Configuration Tool has been designed to allow an Installation / Commissioning Engineer to
program wireless radio detection/initiation and alarm devices prior to programming a Fire Control Panel.
• If a wireless system has Expanders associated with it, these can ONLY be programmed using the Wirelex
Configuration Tool.
• If the parameters of field devices need to be amended away from the default settings, this can ONLY be
carried out using the Wirelex Configuration Tool.
• There are additional applications built in to the Wirelex Configuration Tool that allows a Fire Alarm Engineer
to:
Analyse the background RF environment
Change out a faulty Central Node / Expander(s) without having to reprogram the associated
field devices – as long as the program contained within the modules can still be read.
Program Voice Annunciators with bespoke Voice Messages
• The Wirelex Configuration Tool allows a Fire Alarm Engineer to interrogate an existing system to diagnose
reported faults.
• The Central Node contains an “Events Log” that can be downloaded using the Wirelex Configuration Tool.
This can then be forwarded (if requested) to further analyse the fault and provide the engineer with a
corrective solution.
• The “RF History” of a device can be downloaded using the Wirelex Configuration Tool for off-site analysis (if
required)

PE-0041-A Page 62 of 211 Issue Date: 21st May 2012


LOADING SOFTWARE
Computer requirements:
Compatible Operating Systems: Windows XP/2000
Disk space: 50MB
Minimum Processor speed: Pentium 233MHz
Minimum RAM: 64MB
The Wirelex software is provided on a CD.
Insert the CD in to the laptop drive. The following window will appear:

Press
This will start the Installation Wizard for the Wirelex software. With the Wizard started the following window will
appear:

PE-0041-A Page 63 of 211 Issue Date: 21st May 2012


This will install the software in to a default folder on the computer. If there are other versions of Wirelex
software active on the destination computer, new installations of software will overwrite current software. It is
preferable to place each version in to a different folder:

It can also be modified by selecting . Once the destination folder is correct, press .
The following window will appear:

This will add a line to the Start-up Menu so that the application can be selected from the computer main menu.
As before, it is preferable to re-name the Start Menu folder in order to avoid conflicts with previously installed
Wirelex software.

PE-0041-A Page 64 of 211 Issue Date: 21st May 2012


This can be altered if required. Once the folder name is correct, press
The following Window will appear:

Checking the box for “Create a desktop icon”, a shortcut icon will appear on the Desktop window allowing the
application to be accessed direct from the Desktop.
Checking the “Create a Quick Launch icon” will place a small icon on to the taskbar area reserved for
favourite/often used applications.
Checking the “Install TUSB3410 Driver for RF-RS232 Interface” an additional driver (relating to a future,
currently unavailable, upgrade) will be installed. Once personal choices have been made, press
The following example shows all icons checked along with windows that will be displayed should this option be
chosen:-

This window provides a précis of the information just entered by the user. Selecting will start the
installation process and display the following:-

PE-0041-A Page 65 of 211 Issue Date: 21st May 2012


Note: The information above the scrolling bar will change depending on the driver being installed at the time. If
the option for installing the TUSB3410 driver was not selected, proceed to page 65

PE-0041-A Page 66 of 211 Issue Date: 21st May 2012


If installing the TUSB3410 Driver, the following windows will appear prior to the Wirelex software installation
completing:
(Press when directed to complete the installation of the TUSB3410 Driver correctly)

a. b.

c. d.

e. f.

g.

PE-0041-A Page 67 of 211 Issue Date: 21st May 2012


On completion of the TUSB3410 Driver being installed, the Wirelex software will complete its installation and
the following window will appear:

Click the box.


Remove the CD from the CD drive and store in a safe place. The CD is not required to run this application
once installed on to a computer.

PE-0041-A Page 68 of 211 Issue Date: 21st May 2012


START SYSTEM CONFIGURATION
1. Connect the computer to the Central Node via a standard 9 pin RS232 Serial Cable
2. Open the Wirelex software by double clicking the cursor over the Wirelex icon located on the
computer desktop.
The default connection within the software is to connect through COM Port 1. If this needs to be changed:
a. From the tool bar at the top of the window, select “Options” then “Settings”

b. Select the correct COM port for the RS232 connection - there is an algorithm within the software that will
only display the COM ports available on the connected computer (see example below)

Whilst this window is open, the user should uncheck the “Open last system when starting the program”
option. This will ensure that each time the application opens, the software will open with a “blank canvas”.

PE-0041-A Page 69 of 211 Issue Date: 21st May 2012


PE-0041-A Page 70 of 211 Issue Date: 21st May 2012
On the right hand side of the “Program settings” window in the LOG FILE area, the following boxes should be
checked:
“Enter protocol log-file (“protocol.txt”) – this will allow the Event Log to be saved as a *.txt file.
“Enter log-file RSSI” this will allow the RSSI Log File to be saved as necessary.
“Small icons” selection: Selecting this option will cause the icons seen in the “Configuration” tab to be
smaller. (The installer will be prompted to restart the application if this option is selected):

Press
A wireless fire detection system can now be built.
Prior to proceeding with the software, the Central Node needs to be configured with a unique System Code,
Radio Channel and Start Address.
This information will be transferred to the Wirelex Configuration Tool when requested by the installer.
At the Main Menu page, select the “Configuration” tab. Right click on the word “System” in the
“Radiosystem topology” box. A drop down window will appear:

Highlight and select “Add Central Node”. This will open another window with two options.

PE-0041-A Page 71 of 211 Issue Date: 21st May 2012


If the system being built / programmed is on to a supported protocol Fire Control Panel, select “SGW2W”(the
Translator Module acronym)(see left hand figure below). If the system being built is on to a non-supported
protocol analogue Fire Control Panel or on to a Conventional Fire Control Panel, select “SGXWE” (the
Conventional Expander Module acronym) (see right hand figure below):

Press for the Central Node required and one of the following windows will appear:
SGW2W SGXWE

Note: The “Expander Address” cannot be changed. This is a digital address assigned by the system for future
identification within the microcell environment.
The only parameter that may be changed is the “Child Expanders’ Supervision Period”.
SGW2W SGXWE

PE-0041-A Page 72 of 211 Issue Date: 21st May 2012


If selecting a Conventional Expander Module, care should be taken to ensure that the supporting power supply
is monitored. If using an external power supply, the two boxes marked “Main PS control” and
“Standby PS control” should be checked. If the power for the Conventional Expander Module is supplied
from its supporting Fire Control Panel, theses boxes are to be unchecked. Once all parameters are as
required, press to confirm the Central Node settings.
Note: Programming devices on to either Central Node is identical. For the purposes of this manual, the
example system built uses a Translator Module (SGW2W). Where there are variations with the Conventional
Expander Module (SGXWE), these will be highlighted in the relevant sections
A new Translator Module has now been added to the System configuration and the related icon appears in the
Radiosystem topology tree - the associated chart has been updated to reflect the addition of the Translator
Module. Under the word “System” an icon graphic of the Translator Module will appear.

(If building a system employing multiple Central Nodes, it is recommended that each Module be assigned a
different operational channel and different system code. There are seven operational channels available).
Each Central Node system requires a new Wirelex Configuration Tool file – two Central Nodes cannot be added
to one file.
To add comments (device location, FCP detection loop address, etc), highlight the Central Node and right click
the mouse. A small menu box will appear. Select “Comments”

PE-0041-A Page 73 of 211 Issue Date: 21st May 2012


A “User’s Comments” box will now appear (shown below). A maximum of 31 alphanumeric characters can
now be entered.

On completion press to return to the main window.


(Tip: An alternative quicker method is to double click the mouse in the associated field device Comments box –
this will present the user with the above window)
(Tip: Put the full/abbreviated location in here and if possible the FCP detection loop address, e.g. Grd Flr Office
L1 D22. This is useful when transferring the information to the FCP Configuration Tool or if entering the
information direct at the FCP)
NOTE: The comments that are entered above are only stored in the software configuration on the computer –
they are not transferred to the Translator Module when a “Program SGW2W” is performed. The comments
information are not transferred to the associated Fire Control Panel.

PE-0041-A Page 74 of 211 Issue Date: 21st May 2012


ADDING FIELD (CHILD) DEVICES TO THE CENTRAL NODE
This section details adding a child device of each type to the Central Node. As each device is added to the
Central Node, the device parameters that can be amended are detailed and explained.
ADDING AN OPTICAL SMOKE DETECTOR
To add an Optical Smoke Detector to the Central Node, right click the mouse over the Translator icon selecting
“Add child device”

A window with the list of selectable child devices now appears. Select the device and quantity required; press
on completion.

A window will appear allowing the engineer to amend the device operating parameters. If the device quantity is
> 1, only the first device address will appear in the parameter window but all devices of the type selected will
have the same operational parameters.

PE-0041-A Page 75 of 211 Issue Date: 21st May 2012


PE-0041-A Page 76 of 211 Issue Date: 21st May 2012
The sensitivity of the smoke channel can be amended from its default of “Normal” to “High” or “Low”.

Un-checking the “LED Indication” boxes – “Fire” and “Battery discharge” – will stop the device LED
indicating if there is a fire activation or when the batteries reach a discharge state. The default for these
indications is to remain checked and it is recommended that these two indications are left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins” by
changing the level in the “Supervision period” window.

On completion of parameter/process changing press .


The window will close and the user will be directed back to the “Configuration” tab for adding
further devices (if required). The “Configuration” window will now be updated to reflect the addition of an
Optical Smoke Detector. The device will show the following information in the columns:
Device: Shows device type icon and abbreviated ID
Address: Indicates digital address NOT the analogue loop address
Type: Indicates the device type
Partition: This will always be 1 – all fire devices learn in to Partition 1
Prog: This will initially show “-(radio!)” indicating that the device should be programmed
Comments: Allows the user to insert up to 31 alphanumerics

PE-0041-A Page 77 of 211 Issue Date: 21st May 2012


ADDING A MULTICRITERIA DETECTOR
To add a Multi-Criteria Detector to the Central Node, right click the mouse over the Central Node icon selecting
“Add child device”

A window with the list of selectable child devices now appears.

Select the device and quantity required; press on completion. If the device quantity is > 1, only the
first device address will appear in the parameter window below but all devices of the type selected will have the
same operational parameters.
A window will appear allowing the engineer to amend the device operating parameters.

PE-0041-A Page 78 of 211 Issue Date: 21st May 2012


The default mode of operation for the Multi-Criteria Detector is “A1R”.

PE-0041-A Page 79 of 211 Issue Date: 21st May 2012


This can be changed to “Fixed” or “High Temperature” by changing the “Thermo channel Type”. The
sensitivity of the smoke channel can be amended from its default of “Normal” to “High” or “Low”.

Un-checking the “LED Indication” boxes – “Fire” and “Battery discharge” – will disable the device LED from
flashing if there is a fire activation or when the batteries reach a discharge state. The default for these
indications is to remain checked and it is recommended that these two indications are left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins” by
changing the level in the “Supervision period” window.

On completion of parameter/process changing press .


The window will close and the user will be directed back to the “Configuration” tab for adding further devices (if
required). The “Configuration” window will now be updated to reflect the addition of a Multi-Criteria Detector.

PE-0041-A Page 80 of 211 Issue Date: 21st May 2012


ADDING A THERMAL DETECTOR
To add a Thermal Detector to the Central Node, right click the mouse over the Central Node icon selecting:
“Add child device”

A window with the list of selectable child devices now appears. Select Thermal Detector and quantity required;
press on completion.

A window will appear allowing the engineer to amend the device operating parameters. If the device quantity is
> 1, only the first device address will appear in the parameter window but all devices of the type selected will
have the same operational parameters.

PE-0041-A Page 81 of 211 Issue Date: 21st May 2012


PE-0041-A Page 82 of 211 Issue Date: 21st May 2012
The default mode of operation for the Thermal Detector is “A1R”. This can be changed to “Fixed” or
“High Temperature” by changing the “Thermo channel Type”.
Un-checking the “LED Indication” boxes – “Fire” and “Battery discharge” – will disable the device LED if
there is a fire activation or when the batteries reach a discharge state. The default for these indications is to
remain checked and it is recommended that these two indications are left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins” by
changing the level in the “Supervision period” window.

On completion of parameter / process changing press .


The window will close and the user will be directed back to the “Configuration” tab for adding further devices (if
required). The “Configuration” window will now be updated to reflect the addition of a Thermal Detector.

PE-0041-A Page 83 of 211 Issue Date: 21st May 2012


ADDING A BEAM DETECTOR
To add a Beam Detector to the Central Node, right click the mouse over the Central Node icon selecting “Add
child device”

A window with the list of selectable child devices now appears.

Select Beam Detector and quantity required; press on completion. If the device quantity is > 1, only
the first device address will appear in the parameter window but all devices of the type selected will have the
same operational parameters.
A window will appear with the device parameters

PE-0041-A Page 84 of 211 Issue Date: 21st May 2012


PE-0041-A Page 85 of 211 Issue Date: 21st May 2012
Un-checking the “LED Indication” boxes – “Fire” and “Battery discharge” – will disable the device LED if there is
a fire activation or when the batteries reach a discharge state. The default for these indications is to remain
checked and it is recommended that these two indications are left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins” by
changing the level in the “Supervision period” window.
Device Power Supply: Select from internal batteries (4 x CR123A) or from an external 9 – 27Vdc. If using an
external PSU care should be taken to ensure the PSU is monitored correctly in accordance with EN54
requirements.
Fault if ray reflection from external items: If this is checked, the Beam Detector will indicate a fault if the beam
is deflected from its reflector sheet by an alien object, e.g. a decorative mobile, light fitting, etc.
Sensitivity (threshold): The sensitivity of the Beam can be altered from its default setting to be more or less
sensitive depending on the requirements of the installation.

On completion of changing the Beam Detector operational parameters, press .


The parameter window will close and the “Configuration” tab will be updated to include a Beam Detector:

PE-0041-A Page 86 of 211 Issue Date: 21st May 2012


ADDING A MANUAL CALL POINT
To add a Manual Call Point to the Central Node, right click the mouse over the Translator icon selecting “Add
child device”

A window with the list of selectable child devices now appears.

Select Manual Call Point and quantity required; press on completion. If the device quantity is > 1,
only the first device address will appear in the parameter window but all devices of the type selected will have
the same operational parameters.
A window will appear allowing the engineer to amend the device operating parameters.

PE-0041-A Page 87 of 211 Issue Date: 21st May 2012


PE-0041-A Page 88 of 211 Issue Date: 21st May 2012
Un-checking the “LED Indication” boxes – “Fire” and “Battery discharge” – will stop the device LED indicating if
there is a fire activation or when the batteries reach a discharge state. The default for these indications is to
remain checked and it is recommended that these two indications are left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins” by
changing the level in the “Supervision period” window.

On completion of parameter/process changing press .


The window will close and the user will be directed back to the “Configuration” tab for adding further devices (if
required). The “Configuration” will be updated to include a wireless Manual Call Point

PE-0041-A Page 89 of 211 Issue Date: 21st May 2012


ADDING A WATERPROOF (IP RATED) MANUAL CALL POINT
To add a Waterproof Manual Call Point to the Central Node, right click the mouse over the Central Node icon
selecting “Add child device”

A window with the list of selectable child devices now appears.

Select “Weatherproof Manual Call Point” and quantity required; press on completion. If the device
quantity is > 1, only the first device address will appear in the parameter window but all devices of the type
selected will have the same operational parameters.
A window will appear allowing the engineer to amend the device operating parameters:

PE-0041-A Page 90 of 211 Issue Date: 21st May 2012


PE-0041-A Page 91 of 211 Issue Date: 21st May 2012
Un-checking the “LED Indication” boxes – “Fire” and “Battery discharge” – will stop the device LED
indicating if there is a fire activation or when the batteries reach a discharge state. The default for these
indications is to remain checked and it is recommended that these two indications are left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins” by
changing the level in the “Supervision period” window.

On completion of parameter/process changing press .


The window will close and the user will be directed back to the “Configuration” tab for adding further devices (if
required). The “Configuration” will be updated to include a Waterproof Manual Call Point

PE-0041-A Page 92 of 211 Issue Date: 21st May 2012


ADDING A WIRELESS INPUT MODULE
To add a Wireless Input Module to the Central Node, right click the mouse over the Translator icon selecting
“Add child device”

A window with the list of selectable child devices now appears:

Select “Input Module” and quantity required; press on completion. If the device quantity is > 1, only
the first device address will appear in the parameter window but all devices of the type selected will have the
same operational parameters.
A window will appear allowing the engineer to amend the device operating parameters.

PE-0041-A Page 93 of 211 Issue Date: 21st May 2012


PE-0041-A Page 94 of 211 Issue Date: 21st May 2012
The wireless Input Module has a tamper spring mounted on the device PCB. If the device cover is removed, a
fault will be reported at the Central Node and ultimately back at the FCP. If there is a requirement to NOT
monitor a tamper fault, the check box next to “Do not supervise tamper sensor” should be checked. The
default for this process is for the check box to be un-checked
Un-checking the “LED Indication” boxes – “Fire” and “Battery discharge” – will stop the device LED indicating if
there is a fire activation or when the batteries reach a discharge state. The default for these indications is to
remain checked and it is recommended that these two indications are left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins” by
changing the level in the “Supervision period” window.

On completion of parameter/process changing press .

The window will close and the user will be directed back to the “Configuration” tab for adding further devices (if
required).

PE-0041-A Page 95 of 211 Issue Date: 21st May 2012


ADDING A MAINS POWERED OUTPUT MODULE
To add a Wireless Mains Powered Output Module to the Translator Module, right click the mouse over the
Translator Module icon selecting “Add child device”

A window with the list of selectable child devices now appears. Select “SGMC (Output Module)” and quantity
required; press on completion.

If the device quantity is > 1, only the first device address will appear in the parameter window but all devices of
the type selected will have the same operational parameters.
A window will appear allowing the engineer to amend the device operating parameters.

PE-0041-A Page 96 of 211 Issue Date: 21st May 2012


PE-0041-A Page 97 of 211 Issue Date: 21st May 2012
The wireless Mains Powered Output Module has a tamper spring mounted on the device PCB. If the device
cover is removed, a fault will be reported back at the Translator Module and ultimately back at the FCP. If there
is a requirement to NOT monitor a tamper fault, the check box next to “Do not use front tamper” should be
checked. The default for this process is for the check box to be un-checked.
Similarly, if the power supply voltage is NOT monitored, the box next to “Do not supervise supply voltage”
should be checked. The default for this process is for the check box to be un-checked.
Un-checking the “LED Indication” box – “Low Power Supply” – will stop the device LED indicating if there is
a problem with its associated power supply. The default for this indication is to remain checked and it is
recommended that this indication be left in the default state.
The “Supervisory Signal period” should be left at the default value of 1 minute.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins”
by changing the level in the “Supervision period” window.
The “Relay type” can be changed from “Normally Closed” to “Normally Open” depending on the
requirement of the installation. The default for this process is “Normally Closed”.

On completion of parameter/process changing press .


The window will close and the user will be directed back to the “Configuration” tab for adding further devices (if
required).

PE-0041-A Page 98 of 211 Issue Date: 21st May 2012


ADDING A WALL SOUNDER / SOUNDER BEACON / BASE SOUNDER / BASE SOUNDER BEACON
To add a Wireless Sounder / Sounder Beacon / Base Sounder / Base Sounder Beacon to the Central Node,
right click the mouse over the Central Node icon selecting: “Add child device”

A window with the list of selectable child devices now appears. Select “Sirena-R (Sounder)” and quantity
required; press on completion.

A window will appear allowing the engineer to amend the device operating parameters:

PE-0041-A Page 99 of 211 Issue Date: 21st May 2012


Un-checking the “LED Indication” box – “Battery discharge” – will stop the device LED indicating if the
batteries reach a discharge state. The default for this indication is to remain checked and it is recommended
that this indication be left in the default state.

The wireless Sounder / Sounder Beacon has a tamper spring mounted on the device. If the device is removed
from its base, an indication is sent to the associated Central Node and ultimately to the FCP. If there is a
requirement to NOT monitor this process, the check box “Do not supervise tamper detector”, should be
checked. The default for this process is for the check box to be un-checked.

The “Supervisory Signal period” should be left at the default value of 7 seconds. If the device quantity is > 1,
only the first device address will appear in the parameter window but all devices of the type selected will have
the same operational parameters.

The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins”
by changing the level in the “Supervision period” window.

On completion of parameter/process changing press . The window will close and the user will be
directed back to the “Configuration” tab for adding further devices (if required).

The above procedure should be followed if adding a wireless Base Sounder / Base Sounder Beacon or Wall
Sounder Beacon.

PE-0041-A Page 100 of 211 Issue Date: 21st May 2012


ADDING A VOICE SOUNDER / ANNUNCIATOR
To add a Wireless Voice Sounder to the Central Node, right click the mouse over the Central Node icon
selecting “Add child device”

A window with the list of selectable child devices now appears. Select “(Voice Annunciator RTR)” and
quantity required; press on completion.

A window will appear allowing the engineer to amend the device operating parameters. If the device quantity is
> 1, only the first device address will appear in the parameter window but all devices of the type selected will
have the same operational parameters.

PE-0041-A Page 101 of 211 Issue Date: 21st May 2012


PE-0041-A Page 102 of 211 Issue Date: 21st May 2012
Un-checking the “LED Indication” box – “Battery discharge” – will stop the device LED indicating if the
batteries reach a discharge state. The default for this indication is to remain checked and it is recommended
that this indication be left in the default state.
The “Supervisory Signal period” should be left at the default value of 7 seconds.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins”
by changing the level in the “Supervision period” window.
The wireless Voice Sounder has a tamper spring mounted on the base of the device that will activate if the
device is moved from its installed position. If the device is moved, an indication is sent to the associated
Central Node and ultimately to the FCP. If there is a requirement to NOT monitor this process, the check box
“Do not supervise wall tamper detector” should be checked. The default state for this process is that the
box is unchecked. It is recommended that this process be left in the default state.
When the Voice Sounder is activated, prior to transmitting the voice message, a two-tone signal is emitted.
This can be disabled so that only the voice message is produced. This disablement is carried out by checking
the box marked “ Do not reproduce double-tone signal before sounding”. The default state for this process
is that the box is unchecked.
The nominal output signal power of the Voice Sounder is 0.75W. This signal level can be attenuated by a factor
-3dB, -6dB or -9dB. This is changed by moving the slider on the box marked “Attenuation of output signal
power”
It is possible to connect an auxiliary (external) input to the Voice Sounder using the termination block located on
the Voice Sounder PCB.

Termination Block for connecting an


External Input on to the Voice Sounder

The external input can be used to activate real-time voice messages. To enable this process, the check box
marked “Reproduce signal from aux. input “GO/CHS” must be checked. The default state for this process is
that the box is unchecked.
The auxiliary input audio level can be changed by moving the slider on the box marked
“Pre-amplification of signal “GO/CHS”.
On completion of parameter/process changing press .
The window will close and the user will be directed back to the “Configuration” tab for adding further devices
(if required).

PE-0041-A Page 103 of 211 Issue Date: 21st May 2012


ADDING A BATTERY POWERED OUTPUT MODULE / REMOTE INDICATOR
To add a Battery Powered Output Module or Remote Indicator ( both devices learn on with the same product
code) to the Translator Module, right click the mouse over the Central Node icon selecting “Add child device”

A window with the list of selectable child devices now appears. Select “SGMCB100 (Battery Output Module)”
and quantity required; press on completion.

A window will appear allowing the engineer to amend the device operating parameters. If the device quantity is
> 1, only the first device address will appear in the parameter window but all devices of the type selected will
have the same operational parameters.

PE-0041-A Page 104 of 211 Issue Date: 21st May 2012


PE-0041-A Page 105 of 211 Issue Date: 21st May 2012
Un-checking the “LED Indication” box – “Battery discharge” - will stop the device LED indicating if the
batteries reach a discharge state. The default for this indication is to remain checked and it is recommended
that this indication be left in the default state.
The “Period of control signals transmission” should be left at the default value of 7 seconds.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins”
by changing the level in the “Supervision period” window.
The “External fault input” is, by default checked. This will monitor a fault from an external source. In this
application this process is not used and should be left disabled.
The relay output of the Module can be changed to one of four variants depending on the site application. This
is altered by changing the parameter in the “Relay output” window.
There is a stand-alone voltage output providing the installer with an option of 12V or 24V. The required output
can be chosen by selecting 12V or 24V at the window.
Note: If adding a wireless Remote Indicator Module, the voltage output must be made active and the 24V
output must be selected

The output can be selected as a constant or switching output by changing the mode in the drop down window:

On completion of parameter / process changing press .

PE-0041-A Page 106 of 211 Issue Date: 21st May 2012


The window will close and the user will be directed back to the “Configuration” tab for adding further devices
(if required).

PE-0041-A Page 107 of 211 Issue Date: 21st May 2012


ADDING A BEACON
To add a Wireless Beacon to the Central Node, right click the mouse over the Central Node icon selecting
“Add child device”

A window with the list of selectable child devices now appears. Select “Beacon” and quantity required. Press
on completion.

A window will appear allowing the engineer to amend the device operating parameters. If the device quantity is
> 1, only the first device address will appear in the parameter window but all devices of the type selected will
have the same operational parameters.

PE-0041-A Page 108 of 211 Issue Date: 21st May 2012


PE-0041-A Page 109 of 211 Issue Date: 21st May 2012
The wireless Beacon has a tamper spring mounted on the device that will activate if the device is removed from
its base. If the tamper is activated, an indication is sent to the associated Central Node and ultimately to the
FCP. If there is a requirement to NOT monitor this process, the check box “Do not supervise tamper
detector” should be checked. The default state for this process is that the box is unchecked. It is
recommended that this process be left in the default state.
The “Supervisory Signal period” should be left at the default value of 7 seconds.
The “Supervision period” would normally be left unchanged. This can be changed from the default “3 mins”
by changing the level in the “Supervision period” window.
Un-checking the “LED Indication” box – “Battery discharge” – will stop the device LED indicating if the
batteries reach a discharge state. The default for this indication is to remain checked and it is recommended
that this indication be left in the default state.

On completion of parameter / process changing press .


The window will close and the user will be directed back to the “Configuration” tab for adding further devices
(if required)

PE-0041-A Page 110 of 211 Issue Date: 21st May 2012


The above configuration displays one type of each child device available in the Hyfire wireless product range.
The maximum number of devices that can be added to a system is 32 with a maximum of 16 output devices
contained within the 32 devices. If an attempt is made to add more than this number, the software will prevent
this happening by displaying one of two warning messages:
1. If >32 Devices are added: The example below indicates that a further 30 devices are required to be added to
the Central Node:

The software will allow the number 30 to be entered (above left). When is selected, a warning
message (above right) will appear to warn the installer that this number of devices is not possible –

2. If > 16 output devices are to be added. The example below is attempting to add a further 13 Voice Sounders:

The software will allow 13 to be entered (above left). When is pressed, a warning message will
appear (above right) to warn the installer that this is an invalid action.

PE-0041-A Page 111 of 211 Issue Date: 21st May 2012


PROGRAMMING THE TRANSLATOR MODULE AND ASSOCIATED DEVICES
When the system architecture is complete and all child devices have been added the following will be seen at
the “Configuration” tab:

The Central Node and its associated devices will need to be programmed. Right click over the Translator icon
selecting the “Program SGW2W” option from the drop down menu:

The following window may appear:-

PE-0041-A Page 112 of 211 Issue Date: 21st May 2012


This is quite normal - when the software application is initially opened a new system is virtually built through the
software; the software allocates a random system code to this Central Node. The code that is generated by the
software will be different to the code generated by the Central Node when it is powered on. This results in a
conflict when the PC is finally connected to the Central Node. The solution is as follows:
Right-click the Central Node icon in the “Radiosystem topology” area selecting
“Restore TRANSLATOR to factory settings(clear)” option

A further sub-window will appear:

Select

PE-0041-A Page 113 of 211 Issue Date: 21st May 2012


To ensure that the engineer REALLY wants to clear the Central Node, a further confirmation sub-window will
appear:

Select and the following sub-window will appear indicating that a cleaning routine is taking place and
the Central Node is being reset to factory settings:

On completion of the cleaning process, a further sub-window will appear. This confirms to the engineer that the
Central Node is now ready for programming. Press

(The cleaning process ensures that the Central Node and associated Expanders will be ready to accept the
PE-0041-A Page 114 of 211 Issue Date: 21st May 2012
new program that has just been created)

PE-0041-A Page 115 of 211 Issue Date: 21st May 2012


Right-click the Central Node icon in the “Radiosystem topology” area selecting the “Program SGW2W”
option:

A sub-window appears indicating that Central Node programming is taking place:

On completion of programming, the user is advised that programming is complete by the appearance of a
further sub-window:

Press :

PE-0041-A Page 116 of 211 Issue Date: 21st May 2012


On completion of programming, the Central Node will become BOLD in appearance. This indicates that the
software application and the radio PCB are synchronised. In the “Prog.” column a “+” sign will appear to further
indicate that programming is complete:

(For info - this indicates that although the Central Node has been programmed, the child devices still need to be
programmed). The Central Node needs to be programmed first prior to programming Expander Modules that
have been configured on to the system.

PE-0041-A Page 117 of 211 Issue Date: 21st May 2012


PROGRAMMING CHILD DEVICES
Child devices can only be programmed via its associated radio interface - Central Node or Expander Module.
With the computer connected to the relevant Central Node, right click the mouse over the first associated child
device. Select:
“Local Programming (RS232) > Program child device”.

Once selected a sub-window will appear indicating that the Central Node has started the connection process
and is searching for the device to be programmed:

Ensure the Secondary Battery (CR2032) is fitted first, while the switch is in the 1 position.
Move the programming switch on the back of the device to the ON position. Insert the Primary Battery
(CR123A) into the device. When the primary battery is installed, the child device LED will flash RED four times
indicating the device is in programming mode. When the four RED flashes have been seen, move the
programming switch back to the 1 position. The device LED will now flash GREEN twice to indicate initial
programming is complete. The device may continue flashing RED followed by two GREEN flashes prior to
extinguishing. This is normal and should not be a cause for concern.

PE-0041-A Page 118 of 211 Issue Date: 21st May 2012


On the Wirelex Configuration Tool, a sub-window will appear indicating programming is complete:

Press
The child device icon will now become bold and the content of the “Prog.” Column will change from showing
“–(radio)!” to a “+” indication:

This indicates that the device is now learnt on to the RF Printed Circuit Board (PCB) of the Central Node (this is
the rear PCB (secured to the Central Node back-box by three screws) fitted within the Central Node housing)
and can now be controlled through the Wirelex Configuration Tool.
Repeat for the remainder of the child devices on the Central Node. When all devices have been programmed,
the “Configuration” tab will show the following:

PE-0041-A Page 119 of 211 Issue Date: 21st May 2012


Carry out one final programming of the Central Node by right clicking on the Central Node icon selecting
“Program SGW2W”:

The next step is to carry out a LOAD command at the Translator Module.

PE-0041-A Page 120 of 211 Issue Date: 21st May 2012


THE LOAD PROCESS
The next action is extremely important!
When programming the system using the Wirelex Configuration Tool, all steps/actions carried out to this point
are between the Translator Module and the field devices via the rear PCB (the RF PCB). By performing a
LOAD command at the Translator Module, this information is transferred to the front PCB, where further
processing takes place allowing the wireless field devices, including the Translator Module to be recognised by
the associated FCP. The front PCB acts as the interface between the FCP and the wireless field devices.
After carrying out all the above steps, the next actions are carried out at the Translator Module.

The Translator Module LCD screen should be displaying and the centre yellow LED will be flashing to
indicate that a LOAD command needs to be carried out.
At the Translator Module, using the P3/P4 buttons, scroll up/down until is displayed in the LCD window.
Select using the P2 button.
Use P3/P4 to scroll up/down until is displayed.
Select using the P2 button.
Using the P3/P4 buttons, scroll through until is displayed.
Press the P2 button. will be displayed. Confirm using the P2 button.
If correct, will be displayed.
Press the P1 button until the LCD display is blank.
NOTE: Only after the system has been loaded in to the Translator Module CPU (located on the front PCB) will the
system function correctly with the FCP.

Prior to accessing further information on the installed system – Events, Status, Link Quality, etc – the system
file must now be saved. If the system is not saved and an attempt is made to access the system information by
checking the “Turn on data exchange” option in the “Events” tab, the following prompt will appear:

Press (above left) and save the file on the computer (above right). Once the file has been saved full
access to the diagnostic information is now available.

PE-0041-A Page 121 of 211 Issue Date: 21st May 2012


To see all the Events that have occurred within the system infrastructure, check then uncheck “Turn on data
exchange”. Select . All events will now be displayed:

On completion of the Event Log scrolling through, check “Turn on data exchange” again.

This now links the computer to the Translator Module allowing system information to be dynamically passed.
It should be noted that unless the Translator Module is connected to a computer, the date information in
Column 1 will be incorrect.
Now it is possible to control the whole system from the laptop PC via the Translator Module.

PE-0041-A Page 122 of 211 Issue Date: 21st May 2012


SYSTEM PROPERTIES WINDOW
The Central Node properties can be interrogated after downloading, or from the outset, by accessing the
“SYSTEM PROPERTIES” window. This window will also give access to the system “W2W Table” – point of
conversion from digital to analogue. As well as viewing the system code and radio channel, other parameters
can be viewed.
To gain access to the window is achieved two ways:
• OPENING THE SOFTWARE AND BUILDING A SYSTEM INITIALLY
With the software open select “FILE”. From the drop-down window select “NEW SYSTEM”. A window will
open with the system parameters revealed:

The above window shows the system code and the operational radio channel allocated by the software. The
first two most significant bits (left-most bits) of the system code can be changed and the operational radio
channel can be changed if required. It should be noted that the operating frequency band can also be altered
from 868MHz to 434MHz. Care should be taken to ensure that the correct frequency band is allocated to
ensure compliance with local or national regulations.
The “External Jamming Criterion” allows the installer to define the system parameters for checking if there are
external influences active that could affect the integrity of the system:
• The “Turn on definition” should be checked. This will allow the system to check external RF
radiating equipment is not generating signals that can block the wireless communication.
• The level in the “Level un. RSSI” should be left at the default value of 30. Care must be taken to
ensure that this level is not set to high or low compromising the ability of the system to perform
report correctly – if too low, the system will report a spurious RF signal as jamming even if it is not;
set too high, communication between the Central Node and the device may be lost before the
jamming report is activated.
• The figure in the “Duration, sec.” should be left at the default value of 5 seconds. If the suspect
“jamming signal” is present for longer than the time detailed, the jamming criteria is satisfied and a
fault is generated at the Central Node Event Log.

PE-0041-A Page 123 of 211 Issue Date: 21st May 2012


THE W2W TABLE
The W2W table is the process used to interface the digital aspect of the system with the analogue aspect of the
system, i.e. how the analogue detection loop identifies the child devices and generates the associated analogue
detection loop device addresses. This table can be found by highlighting the “Configuration” tab, right click
on the word “System” in the “Radiosystem topology” area; select “Properties”:

The following window will be displayed:

Highlight the “SGW2W Table” tab. (or SGXWE Table if using a Conventional Expander Module). This will
display the W2W table. The engineer will now be able to see all the devices loaded on to the Central Node and
associated Expanders (if fitted)(It is not possible to maximize the window to display all 32 devices):

PE-0041-A Page 124 of 211 Issue Date: 21st May 2012


The columns shown overleaf are:
Position: This is the order the devices are learnt on to the associated FCP. Using the vertical scroll bar on
the right hand side, it can be seen that this column shows a maximum of 32 devices – the
maximum number that can be associated with a Central Node micro-cell/cluster.
Expander: This column indicates if a device is on the Central Node (Expander 0) or an Expander Module
(Expander 1 – 7).
Detector: This column indicates the digital address that has been given to a device. If there are Expander
Modules associated with the Central Node, the same number will appear to indicate the location
of that device on the associated Expander Module. The previous column should be read in
conjunction with this column to determine the complete digital address for a child device.
Type: This column indicates the type of device that should be found at this address.
Comments: This column and cell will only have information in if the “Comments” cell in the “Configuration”
tab has been used for the child devices.

If the system configuration has been altered, e.g. devices removed, there may be gaps in the table. These will
appear either as a series of hash marks (###) or as a gap:

This can lead to incorrect identification of devices at the FCP. To overcome this, on completion of the LOAD
process, the following action may need to be followed. Anywhere in the table, right click with the mouse.
The following window will be displayed:

Highlight the “Clean table” option.

PE-0041-A Page 125 of 211 Issue Date: 21st May 2012


This will cause a warning window to be displayed:

Select . This will cause the table to blank:

The devices are still present on the system; it is only the W2W table that has gone blank.
Right click in the blank table and highlight “Automatically fill the table”:.

PE-0041-A Page 126 of 211 Issue Date: 21st May 2012


The devices will now re-appear in a logical order starting with the devices on the Central Node followed by
devices on Expander 1, Expander 2, etc:

NOTE: It is recommended that this process is only carried out during the initial commissioning of the
system. If this process is carried out on an existing system, the associated FCP may display incorrect
device text, incorrect device types and the System Cause and Effects may not function correctly.
W2W TABLE ADDRESS VERSUS FIRE CONTROL PANEL LOOP ADDRESS

Care should be taken when determining the analogue loop address of the Translator Module and its associated
devices from the W2W Table. If read incorrectly, when carrying out diagnostic or corrective maintenance on a
wireless device, remedial work may be carried out on the wrong device.

The following details how to determine the loop address for wireless field devices when looking at the W2W
Table for different protocols.

Prior to interrogating the W2W Table to determine the analogue loop detection address of the wireless devices,
the W2W Table should be set up correctly such that devices on the Translator Module are first followed by
devices on Expander Module 1, Expander Module 2, Expander Module 3, etc. If a Translator Module or
Expander Module is being used as a radio bridge and has no direct devices associated with it, there will be no
sign of that interface in the W2W Table – the first interface with devices should be listed first.

If devices have been added to the Translator Module followed by Expander Module 2 then Expander Module 1
followed by more devices on the Translator Module, the “Clean and Fill” procedure detailed previously should
be carried out first.

PE-0041-A Page 127 of 211 Issue Date: 21st May 2012


VEGA PROTOCOL

The Vega Protocol allows for a maximum of 240 devices to be connected to an analogue detection loop. When
interrogating the W2W Table, the analogue loop address of the Translator Module needs to be identified. This
can only be done from the Translator Module itself. In the following example, it is assumed that the Translator
Module analogue loop address is 25.
From the W2W Table we can see that the system consists of the following devices:

It can be seen that the first five devices are directly associated with the Translator Module and the final device
is associated with Expander Module 1.

Knowing that the Translator Module has an address of 25 would indicate that the devices indicated in the table
above have the following analogue loop address:

Assuming that the devices are listed contiguously, a quick way to determine the analogue loop address of a
device is:

Translator Module Loop Address + Position Number = Analogue Loop Address

PE-0041-A Page 128 of 211 Issue Date: 21st May 2012


HOCHIKI PROTOCOL

The Hochiki Protocol allows for a maximum of 127 devices to be connected to an analogue detection loop.
When interrogating the W2W Table, the analogue loop address of the Translator Module needs to be identified.
This can only be done from the Translator Module itself. In the following example, it is assumed that the
Translator Module analogue loop address is 25.
From the W2W Table we can see that the system consists of the following devices:

It can be seen that the first five devices are directly associated with the Translator Module and the final device
is associated with Expander Module 1.

Knowing that the Translator Module has an address of 25 would indicate that the devices indicated in the table
above have the following analogue loop address:

Assuming that the devices are listed contiguously, a quick way to determine the analogue loop address of a
device is:

Translator Module Loop Address + Position Number = Analogue Loop Address

PE-0041-A Page 129 of 211 Issue Date: 21st May 2012


NOTIFIER / HONEYWELL PROTOCOL

The Notifier CLIP protocol and the Honeywell protocol allows for a maximum of 198 devices on an analogue
detection loop – 99 Module type devices and 99 Sensor type devices. The Translator Module takes a Module
type address on these protocols. When interrogating the W2W Table, the analogue loop address of the
Translator Module needs to be identified. This can only be done from the Translator Module itself – at the
Translator Module on these protocols, the Module start address is the address the Translator Module takes with
all other modules being contiguously addressed. The Sensor start address shows the first address a Sensor
takes with all other Sensors being contiguously addressed above that. In the following example, it is assumed
that the Module analogue loop address is 25 and the Sensor analogue loop address is 15
From the W2W Table we can see that the system consists of the following devices:

It can be seen that the first five devices are directly associated with the Translator Module and the final device
is associated with Expander Module 1.

Knowing that the Translator Module has a Module address of 25, this would indicate that the devices indicated
in the table above have the following analogue loop address:

It can be seen that the Sensor and Module start addresses do not have to be the same. It can also be seen
that the first Module takes the next free address after the Translator Modle but the first Sensor takes the start
address detailed.

PE-0041-A Page 130 of 211 Issue Date: 21st May 2012


ADDITIONAL DIAGNOSTIC INFORMATION
The two remaining tabs – “Status” and “Link Quality” – provide additional information for the engineer:
a. Graphic display of RF quality of each child device.
b. Graphic display of RF quality history.
c. Fault and fire indication in a partition.
d. Fire and status indication of each device.
e. Power output attenuation control.
f. Communication control between the Central Node and associated Expanders.

USE OF STATUS TAB


Select the “Status” tab. The following window will be displayed:

The legend on the right hand side displays various alarm/fault/status indications.
In the “Global status” area, the system indicates all global partitions active on the system. In this application,
the only partition displayed will be Partition 1 – fire devices will only be seen in this partition. If the devices are
fault free and are not in a fire state, the box beneath number 1 will appear dark grey indicating all devices are in
a standard quiescent state. When holding the computer mouse icon over the same box, the interfaces (Central
Node / Expander(s)) associated with this system will be displayed. The indications in the lower right hand box
will normally be blank – apart from “Status” where “Norm” is displayed - indicating the system is fault free:

PE-0041-A Page 131 of 211 Issue Date: 21st May 2012


Holding the mouse over the SGW2W in the “Local Status” box will bring up the Translator Module status:

Hovering the mouse icon over the square in this box will display all devices associated with the particular
interface:

The lower right legend will also change and will indicate if there are any devices in fire or fault and if there are
issues with the power to the interface.
If a device is in FAULT, the square under the number 1 in both the “Global status” and “Local status” areas
will turn orange ( ):

PE-0041-A Page 132 of 211 Issue Date: 21st May 2012


Hovering the mouse over the orange box in the “Local status” area, will cause the indications in the “Partition
1” table to alter and will indicate the problem – but not the device:

If a device is in a FIRE state, the same box will turn red in colour ( ):

If there are devices in FAULT and FIRE, the highest priority message (FIRE) will be indicated by the colour of
the box but both reports will be indicated in the “Partition 1” table:

PE-0041-A Page 133 of 211 Issue Date: 21st May 2012


Double tapping the box under the number 1 in the “Local status” area will open a further page that will provide
more detail about device status. If local partition 1 is indicating any other colour than light grey ( ) (indicating
no devices are attached to that interface) or dark grey ( ) (indicating that the interface is in a normal quiescent
state), double-clicking over the coloured square will open another window:

By left clicking over a device, its status will appear in the right hand box titled “Status of devices:”
POSSIBLE DEVICE TYPES
SG100: - Smoke Detector

SG350: - Heat Detector

SG200: - Multicriteria Detector

SGBD100: Beam Detector

SGCP100: Manual Call Point

SGWCP100: Weatherproof Call Point

SGRS100: Audio-Visual device

SGMC100: Ext. Powered Output Module

SGMI100:- Input Module

SGVA100:- Voice Sounder

SGMCB100:- Battery Output Module


If the device status is correct, “Norm” will be displayed.
SGBE100: Beacon

PE-0041-A Page 134 of 211 Issue Date: 21st May 2012


PE-0041-A Page 135 of 211 Issue Date: 21st May 2012
If the device is in fault, the associated icon will have an ORANGE box over it. An ORANGE box will also
appear adjacent to Global Partition 1 and local partition 1. By left clicking the device, a fault indication will
appear in the “Status of devices” box:

PE-0041-A Page 136 of 211 Issue Date: 21st May 2012


If there is a “FIRE” activation the associated boxes will have a RED square over/adjacent them. By following
the same process as above, an engineer will be able to verify the child device has activated:

By pressing , the engineer will be returned to the Status page.

PE-0041-A Page 137 of 211 Issue Date: 21st May 2012


If there are a number of faults or fires on the same Central Node or Expander, the highest priority report will be
indicated at the “Global status” and “Local status” areas of the “Status” tab – this will be shown by the
normally grey box being RED in colour. A double left click on this box will open the “Status of devices”
window. This will show the status of all devices directly associated with this Central Node or Expander. A
single left click on the reporting device will cause the status area of the window to update and show the actual
fault or alarm associated with that device:

PE-0041-A Page 138 of 211 Issue Date: 21st May 2012


EXAMPLES OF DISPLAYED FAULTS
I. TAMPER FAULT (BODY IS OPENED!)
The comment shown in the box titled “Status of devices” indicates that the child device has been removed
from its base / back-box and is now in a tamper condition. Check the device to ensure it is seated correctly and
when this has been confirmed, carry out a RESET command and this fault will clear. Alternatively waiting for
the next handshake between the Interface and the field device will update the system and the fault will clear
automatically:

II. SECONDARY (STANDBY/RESERVE) BATTERY DISCHARGE


The comment shown in the box titled “Status of devices” indicates that the Secondary or Standby power cell
has fallen below the voltage threshold for that cell. The cell should be replaced at the earliest opportunity.
When the cell has been changed, perform a RESET command and the fault will clear.

It is advisable that all power cells – Standby / Reserve and Main / Primary are changed should this fault occur.

PE-0041-A Page 139 of 211 Issue Date: 21st May 2012


III. SUBSTITUTION ATTEMPT
The comment shown in the box titled “Status of devices” indicates that a device has been introduced to the
system that has the same address – comparable with a hard-wired “Double Address Fault”.

This will happen if an apparently faulty device is removed from the system and replaced with a new device.
However, if the batteries from the old device are still in place, the removed device retains in its memory the
digital address originally prescribed to it by the Translator Module and will try to regain communication with the
Translator Module. Removing the batteries from the faulty device and carrying out a “RE-INITIATE CHILD
DEVICE” on the new device will eliminate this fault.
IV. NO RADIO LINK / NO LINK

This fault occurs if:


a. A device is out of range of its associated Central Node or Expander. By moving the device back in to
range and performing a RESET command, this fault will disappear.
b. If the batteries within the device have both discharged and the previous warnings about battery
discharge have been ignored. By replacing both cells in the device, and performing a RESET command, this
fault will disappear
NOTE: This fault will only appear after the time interval set in the “SUPERVISION PERIOD” parameter when
adding the device to the system.

PE-0041-A Page 140 of 211 Issue Date: 21st May 2012


V. GENERAL FAULT

This fault occurs for a number of reasons:


a. The programming switch has been moved to the “ON” position after the device has been programmed.
b. The device processing has gone faulty and the expected information has not been received at the
Central Node. The Central Node then informs the system and a fault is generated. This is often accompanied
by the central YELLOW LED on the Translator Module constantly glowing. The device LED may also be
flashing RED/GREEN intermittently. The engineer will need to investigate this fault with a laptop computer and
will need to check the Events Log, the “Status” tab and to isolate the fault further, the “Link Quality” tab – the
Link Quality tab will indicate the wrong analogue value if the digital processing is incorrect. The device will
need to be changed out and returned for further technical investigation.
c. After replacing a suspect power cell. When a power cell is replaced, the device will re-establish
communication with its associated Central Node. During this period “GENERAL FAULT” will be indicated.
At the FCP, this fault will be displayed as a “FATAL FAULT”
To clear this fault, the FCP will need a “PROCESSOR RESET” carried out.
All the above faults will also be displayed in the Event Log – this is accessed by pressing the “Events” tab on
the software. An example of the faults as seen in the Events Log is shown below:

PE-0041-A Page 141 of 211 Issue Date: 21st May 2012


USE OF RF LINK QUALITY TAB
Select the “Link Quality tab” on the Wirelex Configuration Tool. The following window will be displayed:

Expanders: The Central Node and associated Expanders in the cluster are displayed here. Highlighting the
Expander you wish to investigate will display the associated child devices in the right-hand area. Right clicking
the cursor over the highlighted Translator/Expander will give two further options that will reveal in turn further
options for each:

The “Automatic Power Control in the System” option allows the engineer to turn on / off the automatic power
attenuation facility within the Translator cluster. This is normally left on as the system uses complex algorithms
to determine the best power level between the Central Node / Expander(s) and the associated child devices.
Turning this off causes all devices to work at maximum power levels. This can result in an increased level of RF
noise causing communication with some devices to be lost. This will also reduce the expected battery life

The “Sending Signal Levels Between All Expanders” option allows the engineer to turn on/off the
communication between the Central Node and any Expander(s) fitted. If Expander(s) are employed within the
microcell/cluster, this option must be turned on. This allows all information to pass freely between the Central
Node and Expander(s) within the cluster so that all device faults, tamper faults, fire activations can be seen
when interrogating/testing the system through the Wirelex Configuration Tool.

PE-0041-A Page 142 of 211 Issue Date: 21st May 2012


LINK QUALITY TAB – CHILD DEVICE SECTION
In the Child device section of the page, the following information is displayed:

Device: The device type is displayed in the first column.


Address: The device address is displayed in the next column. This address is allocated to the device by
the associated Translator / Expander. This is the system digital address and NOT the allocated detection loop
address.
Quality, RSSI: Received Signal Strength Indication (RSSI) is a measurement of the power present in
a received radio signal. The signal level from each RF modem is displayed here – the value to the left of the
oblique is from the Primary modem, the figure to the right is the value from the Secondary modem. This level is
measured in Standard Units. Only one value will be indicated here – left or right. The other value will be zero.
Quality, dB: The signal level here is shown as a dB level.
Mark: This is an indication of the link quality based on a five point rating scale:
QUALITY MARK LINK INDICATION
2 Fail – no connection or very weak. Link margin is ≤ 10dBs
3 Not good – Link margin is between 11 - 20dBs
4 Good – robust communication with a link margin between 21 - 30dBs
5 Excellent – Robust communication with a link margin ≥ 31dBs
Comments: This is the comment added about device location at the “Configuration” tab
Link: This indicates the last time communication between the field device and its associated Central Node /
Expander took place. This indication will increment in 4 second intervals. For all devices, except wireless
Audio-Visual devices, this will increase to approximately 1 minute and return to zero. For the Audio-Visual
devices this will increment to approximately 8 seconds before returning to zero.

PE-0041-A Page 143 of 211 Issue Date: 21st May 2012


LINK QUALITY HISTORY GRAPH
By highlighting a single device, moving the cursor over it and right clicking, two options are displayed:

Show History: Selecting this option will display the RF link quality graph (shown below)
(Shortcut - By double-clicking the device the RF link quality history graph will be displayed)
The different colours indicate the Mark
Quality:
GREEN – 5
YELLOW – 4
ORANGE – 3
PINK -2

The Orange dot indicates that the


Secondary Modem signal was stronger
than the Primary Modem signal for this
particular reading – this does not indicate
that there is a problem with the device
only that during that particular time frame
the signal seen at the Secondary Modem
was stronger – this is caused by vagaries
in radio propagation

The GREEN waveform indicates the RF link quality history for each device. The graph will provide the user
with as many as 8192 segments. This is the equivalent of a sample every 5 seconds over a 12 hour period.
Clean History: This will clean all RF link quality information – resetting the graph.

PE-0041-A Page 144 of 211 Issue Date: 21st May 2012


ZOOM IN ON RF HISTORY GRAPH
The user can zoom in on specific areas within the graph for better analysis of the RF Quality history. This is
achieved by holding down the left mouse button, creating a box by moving from top left to bottom right around
the interested area and then releasing the left mouse button.

The graph will now zoom in on that area providing the user with an enhanced view. This can be repeated until
the area is clear enough for the user to anlayse the information.
Once the desired level of analysis has been reached, holding the cursor over the area will produce a box giving
an indication of the segment number under investigation along with a dB level.

RETURN TO NORMAL GRAPH VIEW


To return to the normal screen level, the user must make a further box moving the cursor from bottom right to
top left whilst holding down the left control on the mouse – this will return the graph to its normal appearance.

PE-0041-A Page 145 of 211 Issue Date: 21st May 2012


SYSTEM CONFIGURATION CODE HEXADECIMAL-DECIMAL CONVERSION TABLE
The System Configuration Code is a code assigned to the Central Node when it is powered on. It forms part of
the encryption process employed by the Central Node - the system code seen at the Translator Module LCD
display is a decimal interpretation of a hexadecimal code, ranging from 01 to ff. The table shows all
hexadecimal codes and the decimal equivalents.
Decimal Hexadecimal Decimal Hexadecimal Decimal Hexadecimal Decimal Hexadecimal Decimal Hexadecimal
1 1 52 34 103 67 154 9A 205 CD
2 2 53 35 104 68 155 9B 206 CE
3 3 54 36 105 69 156 9C 207 CF
4 4 55 37 106 6A 157 9D 208 D0
5 5 56 38 107 6B 158 9E 209 D1
6 6 57 39 108 6C 159 9F 210 D2
7 7 58 3A 109 6D 160 A0 211 D3
8 8 59 3B 110 6E 161 A1 212 D4
9 9 60 3C 111 6F 162 A2 213 D5
10 0A 61 3D 112 70 163 A3 214 D6
11 0B 62 3E 113 71 164 A4 215 D7
12 0C 63 3F 114 72 165 A5 216 D8
13 0D 64 40 115 73 166 A6 217 D9
14 0E 65 41 116 74 167 A7 218 DA
15 0F 66 42 117 75 168 A8 219 DB
16 10 67 43 118 76 169 A9 220 DC
17 11 68 44 119 77 170 AA 221 DD
18 12 69 45 120 78 171 AB 222 DE
19 13 70 46 121 79 172 AC 223 DF
20 14 71 47 122 7A 173 AD 224 E0
21 15 72 48 123 7B 174 AE 225 E1
22 16 73 49 124 7C 175 AF 226 E2
23 17 74 4A 125 7D 176 B0 227 E3
24 18 75 4B 126 7E 177 B1 228 E4
25 19 76 4C 127 7F 178 B2 229 E5
26 1A 77 4D 128 80 179 B3 230 E6
27 1B 78 4E 129 81 180 B4 231 E7
28 1C 79 4F 130 82 181 B5 232 E8
29 1D 80 50 131 83 182 B6 233 E9
30 1E 81 51 132 84 183 B7 234 EA
31 1F 82 52 133 85 184 B8 235 EB
32 20 83 53 134 86 185 B9 236 EC
33 21 84 54 135 87 186 BA 237 ED
34 22 85 55 136 88 187 BB 238 EE
35 23 86 56 137 89 188 BC 239 EF
36 24 87 57 138 8A 189 BD 240 F0
37 25 88 58 139 8B 190 BE 241 F1
38 26 89 59 140 8C 191 BF 242 F2
39 27 90 5A 141 8D 192 C0 243 F3
40 28 91 5B 142 8E 193 C1 244 F4
41 29 92 5C 143 8F 194 C2 245 F5
42 2A 93 5D 144 90 195 C3 246 F6
43 2B 94 5E 145 91 196 C4 247 F7
44 2C 95 5F 146 92 197 C5 248 F8
45 2D 96 60 147 93 198 C6 249 F9
46 2E 97 61 148 94 199 C7 250 FA
47 2F 98 62 149 95 200 C8 251 FB
48 30 99 63 150 96 201 C9 252 FC
49 31 100 64 151 97 202 CA 253 FD
50 32 101 65 152 98 203 CB 254 FE
51 33 102 66 153 99 204 CC 255 FF

PE-0041-A Page 146 of 211 Issue Date: 21st May 2012


PE-0041-A Page 147 of 211 Issue Date: 21st May 2012
INTENTIONALLY BLANK

PE-0041-A Page 148 of 211 Issue Date: 21st May 2012


SECTION 6 – WIRELESS EXPANDER MODULES
INTRODUCTION………………………………………………………………………………………. Page 128
ADDING AN EXPANDER MODULE TO AN UNPROGRAMMED CENTRAL NODE………..… Page 129
ADDING AN EXPANDER MODULE TO A PROGRAMMED CENTRAL NODE………...……… Page 138
ADDING ADDITIONAL EXPANDER MODULES………………………………………………….. Page 140
DAISY CHAIN………………………………………………………………………………… Page 141
SAME LAYER………………………………………………………………………………… Page 143
COMBINATION……………………………………………………………………………… Page 144

INTRODUCTION
To increase the area of coverage for a Translator Module, a signal booster module, known as an EXPANDER
MODULE, is available. This device is used:
• To increase the range of coverage for wireless devices
• To overcome obstacles affecting radio signal integrity, e.g. decorative mobile ☺
• To link buildings together negating the requirement for containment between the buildings –
trenches, catenary wires, underground ducting, etc.
A maximum of seven Expander Modules can be associated / linked with a Central Node (see pages 50 – 51).
Care must be taken when adding Expander Modules that the correct programming sequence for the system is
followed – deviations from this can result in lost devices or even lost Expander Modules from the expected
system.
An Expander Module, and associated devices, can only be added to a Central Node using the Wirelex software.
It is not possible to “locally” program an Expander in the same way a Translator Module can.

PE-0041-A Page 149 of 211 Issue Date: 21st May 2012


ADDING AN EXPANDER MODULE TO AN UNPROGRAMMED CENTRAL NODE
Open the Wirelex software connecting the computer to the Central Node RS232 termination block using a
standard 9-pin serial cable. Select the “Configuration” tab. Right click on “System” and from the drop-down
window select “Add Central Node”:

In the window that appears select the correct Central Node for the application pressing once
selected:

The Central Node parameter window will open. Press to be returned to the “Configuration” tab:

PE-0041-A Page 150 of 211 Issue Date: 21st May 2012


PE-0041-A Page 151 of 211 Issue Date: 21st May 2012
When all wireless child devices that are to be directly associated with the Central Node have been added, right
click on the Central Node icon and from the drop down window that appears select “Add SGWE”:

A window will appear with the parameters for the Expander. If the associated power supply is being monitored
ensure the two boxes marked “Main PS control” and “Standby PS control” are checked. If the power supply
is not being monitored, the two boxes should be unchecked:

Once the parameters have been selected, press to be returned to the “Configuration” tab.
Wireless child devices should now be added to the Expander:

PE-0041-A Page 152 of 211 Issue Date: 21st May 2012


When the system architecture has been completed, the system will now need to be programmed.
Programming of the system should always start with the Central Node. At the “Configuration” tab, right click
on the Central Node and from the drop down window select “Program SGW2W”:

The following window may appear indicating that the Central Node parameters for the device the computer is
connected to differs from the parameters in the software:

Press and the User will be returned to the “Configuration” tab. Right click on the Central Node
selecting “Restore to factory settings (clear)” from the drop down window that appears:

This will clear the internal memory of the Central Node but will not delete the configuration compiled earlier.

PE-0041-A Page 153 of 211 Issue Date: 21st May 2012


PE-0041-A Page 154 of 211 Issue Date: 21st May 2012
Before the cleaning process starts a window will appear warning the User that the system parameters the
computer is connected to differs from the expected:

A further warning window will appear to confirm that the User wants to proceed with this process:

Press the button and the process will start with a progress window displayed followed by a
completion window:

The Central Node has now been cleaned. The process for programming the Central Node should now be
repeated.

PE-0041-A Page 155 of 211 Issue Date: 21st May 2012


At the “Configuration” tab right click on the selected Central Node selecting “Program SGW2W” from the
drop down window that appears:

Programming will commence and a window will appear indicating programming progress followed by a window
indicating programming completion:

Press and the user will be returned to the “Configuration” tab. The User should note the difference
in the appearance of the font for the word “SGW2W” it will now be bold. The icon for the Central Node will also
be deeper in appearance as compared to the Expander (“SGWE”) that is yet to be programmed.

The child devices directly associated with the Central Node should now be programmed as previously detailed

PE-0041-A Page 156 of 211 Issue Date: 21st May 2012


(see page 102)

PE-0041-A Page 157 of 211 Issue Date: 21st May 2012


On completion of programming all the child devices directly associated with the Central Node, the Expander
should now be programmed. The programming lead should be moved from the Central Node to the Expander
that is to be programmed. Right click on the Expander in question (in this example SGWE1). A drop down
window will appear. Select “Program SGWE”:

:
The following window may appear indicating that the Expander has different operational parameters to those
expected:

Press . The warning window will disappear. Right click on SGWE again. From the drop down
window that appears, highlight “Restore SGWE to factory settings (clear)”:

PE-0041-A Page 158 of 211 Issue Date: 21st May 2012


A further warning window will now appear informing the User that the system the computer is connected to has
different system parameters and should the action proceed:

Selecting will open another window requesting the User to confirm the action should proceed:

The cleaning process of the Expander will now commence. A window indicating progress will appear (below
left) followed by a completion window (below right):

Press to be returned to the main “Configuration” tab

PE-0041-A Page 159 of 211 Issue Date: 21st May 2012


The action of programming the Expander should now be repeated. Right click on the relevant Expander. From
the drop-down window that appears select “Program SGWE”:

Programming will commence and a progress window will be displayed followed by a programming completion
window:

Press to be returned to the main “Configuration” tab. The User will now see that the Expander
icon is the same density as for the Central Node:

The child devices directly associated with this Expander should now be programmed

PE-0041-A Page 160 of 211 Issue Date: 21st May 2012


To complete programming of the Expander to ensure the system functions correctly, the following further
programming process will need to be completed.
Right click on the Expander that has just been programmed. From the drop down window that appears select
“Program SGWE”:

A window will appear indicating progress of the programming followed by another window showing
programming is complete:

On completion press . The User will now be returned to the “Configuration” tab. The programming
lead should now be moved back to the Central Node for the final step.

PE-0041-A Page 161 of 211 Issue Date: 21st May 2012


The final step is to carry out a final programming of the Central Node. Right click on “SGW2W” selecting
“Program SGW2W” from the drop down window:

A window will appear to show progress of programming (below left) followed by a window indicating completion
(below right):

A “LOAD” command should now be carried out locally at the associated Central Node (see page 105).

NOTE: If the Central Node is a Conventional Expander Module, programming is complete when the final
Central Node programming has been carried out. A “LOAD” command does not need to be carried out on a
Conventional Expander Module

ADDING AN EXPANDER MODULE TO A PROGRAMMED CENTRAL NODE


If a system has already been installed and there is an operational requirement to add an Expander to the
system, the methodology is the same as described in pages 129 - 138

PE-0041-A Page 162 of 211 Issue Date: 21st May 2012


INTENTIONALLY BLANK

PE-0041-A Page 163 of 211 Issue Date: 21st May 2012


ADDING ADDITIONAL EXPANDER MODULES
If adding additional Expanders, these can be added in three ways – daisy chain from the previous Expander or
on the same layer as another Expander, or a combination of the two.
DAISY CHAIN

Central Node Expander Module Expander Module

SAME LAYER

Central Node Expander Module

Expander Module

Expander Module

COMBINATION

Central Node Expander Module Expander Module Expander Module

Expander Module

PE-0041-A Page 164 of 211 Issue Date: 21st May 2012


DAISY CHAIN
When adding Expanders in a daisy chain format, the following process should be followed. Deviation from this
may result in incorrect reporting of faults and fires from trigger devices and no activation of alarm devices.
Open the Wirelex software and whilst connected to the Central Node via the RS232 port, add a Central Node
(plus child devices) and first Expander (plus child devices) as detailed at pages 129 - 138. DO NOT CARRY
OUT ANY PROGRAMMING. The Wirelex “Configuration” tab should appear as follows:

To add an additional Expander in a “daisy chain format”, right click on “SGWE 1” selecting “Add SGWE” from
the drop down menu:

This will open up the Expander properties window (see page 130). Ensure the system parameters are correct.
Press on completion. The following window will be displayed showing the additional Expander
(SGWE 2):

PE-0041-A Page 165 of 211 Issue Date: 21st May 2012


If devices are to be added to this Expander – in this instance a Thermal Heat Detector - these should be added
as previously detailed. When all devices have been added, the following window should be displayed:

The following steps should be taken to ensure that all components of the system are programmed correctly:
Program Central Node
Program Central Node devices
(Transfer lead to Expander 1)
Program Expander “SGWE 1”
Program Expander “SGWE 1” child devices
(Transfer lead to Expander 2)
Program Expander “SGWE 2”
Program Expander “SGWE 2” child devices
(Transfer lead to Expander 1)
Program Expander “SGWE 1”
(Transfer lead to Central Node)
Program Central Node

On completion of the programming sequence a “LOAD” command (see page 105) should be carried out at the
Central Node (only if the Central Node is a Translator Module). The whole system can now be displayed and
controlled with the computer connected to the Central Node as previously indicated.

Should any further Expander Modules need to be added to extend the “daisy chain” further, the same process
described above should be followed. The maximum number of Expander Modules that can be added in a
“daisy chain” is 5 creating a maximum of 6 layers.

PE-0041-A Page 166 of 211 Issue Date: 21st May 2012


SAME LAYER
If adding a second, or third, Expander on to the same layer – in this instance to the Central Node, the following
process should be followed. Open the Wirelex software. With the computer connected to the Central Node,
add a Central Node (plus child devices), then add the first Expander (plus child devices). The “Configuration”
tab should display the following:

To add another Expander on to the same layer as the first Expander, right click on “SGW2W” in the
“Radiosystem topology” area selecting “Add SGWE” from the drop-down window. When added the
“Configuration” tab will display the following:

From the above window, the difference in the topology of the above system and a “Daisy Chain” system can be
seen. The difference in the digital address of the Expanders should also be noted. The programming
sequence for this system is:
Program Central Node
Program Central Node devices
(Transfer lead to Expander 1)
Program Expander “SGWE 1”
Program Expander “SGWE 1” child devices
(Transfer lead to Expander 2)
Program Expander “SGWE 2”
Program Expander “SGWE 2” child devices
(Transfer lead to Central Node)
PE-0041-A Page 167 of 211 Issue Date: 21st May 2012
• Program Central Node

PE-0041-A Page 168 of 211 Issue Date: 21st May 2012


COMBINATION
There may be a requirement to add Expander Modules in a combination of the previous two sequences – this
could be used in an installation with multiple buildings, for example.
Open the Wirelex software. With the computer connected to the Central Node, add a Central Node and child
devices (if applicable)) and two Expander Modules (plus child devices (If applicable)) in a daisy chain as
previously described.
(For this system, Expander Module “SGWE 1” has no child devices) A second Expander Module will now be
added to Expander Module 1 (SGWE 3)
The “Configuration” tab will display the following:

Right click on Expander, “SGWE 1”, selecting “Add SGWE” from the drop down window. Ensure all
operational parameters are correct before selecting . On completion the following window will be
displayed:

It can be seen from the above image that the system is a combination of the DAISY CHAIN system and the
SAME LAYER system.

PE-0041-A Page 169 of 211 Issue Date: 21st May 2012


Programming of the system should be carried out as follows:

• Program Central Node

Program Central Node devices

(Transfer lead to Expander 1)

Program Expander “SGWE 1”

(Transfer lead to Expander 2)

Program Expander “SGWE 2”

Program Expander “SGWE 2” child devices

(Transfer lead to Expander 3)

Program Expander “SGWE 3”

Program Expander “SGWE 3” child devices

Program Expander “SGWE 3”

(Transfer lead to Expander 2)

Program Expander “SGWE 2”

(Transfer lead to Expander 1)

Program Expander “SGWE 1”

(Transfer lead to Central Node)

Program Central Node

On completion, carry out a LOAD command (see page 105) at the Central Node (if it is a Translator Module).
As before, it will now be possible to control the whole system with the computer connected to the Central Node.

The three processes detailed above should be used in isolation, or in combination, when adding numerous
Expanders to a system. The process is logical and must be followed to avoid “losing” part of the system and
prolonging the programming process.

PE-0041-A Page 170 of 211 Issue Date: 21st May 2012


INTENTIONALLY BLANK

PE-0041-A Page 171 of 211 Issue Date: 21st May 2012


SECTION 7 – ADDITIONAL SOFTWARE APPLICATIONS
INTRODUCTION………………………………………………………………………………….…… Page 147
RF ANALYZE UTILITY………………………………………………………….………………….... Page 148
FIRECLONE UTIILITY………………………………………………………………………..……… Page 151
DOWNLOAD THE CONFIGURATION FILE………………………………………………. Page 151
UPLOAD THE CONFIGURATION FILE…………………………………………………… Page 155
VOICE ANNUNCIATOR (ORPHEY) UTILITY…..………………………………………………….. Page 164

INTRODUCTION
To assist an installation there are two additional software applications available on the Wirelex Configuration
Tool CD:
• RF ANALYZE UTILITY
This allows the engineer to assess the background RF environment for all seven operational
channels. This can assist the Commissioning Engineer to correctly allocate a “clean” RF channel
during initial installation for a Central Node and associated devices.
• FIRECLONE UTILITY
The “Fireclone” utility allows the User to take a copy of the configuration contained within a
wireless interface (Central Node or Expander)
If the Central Node or Expander suffers an electrical failure or other fatal failure, this saved copy can
be uploaded to the replacement without the need to re-program the associated child wireless
devices.
• VOICE ANNUNCIATOR (ORPHEY) UTILITY
This utility assists the installer in programming the Voice Annunciator (HFW-VSK-01) with voice
messages. These messages can be pre-loaded prior to installation.
This section details how to access and use these utilities.

PE-0041-A Page 172 of 211 Issue Date: 21st May 2012


RF ANALYZE UTILITY

Connect a computer to the Central Node using a standard RS232 cable. To access this facility, select the
“Tools” option and at the drop down window select “RF Analyze Utility”

This will bring up the following window:

The engineer will need to ensure that the “Port” displayed is the same one that the RS232 lead is connected to
(if using a PC with a serial port, the default for this is COM Port 1). If COM Port 1 is not the correct port, select
the correct port from the options displayed in the drop down window – there are only a choice of 8 ports that
can be selected. The “Connect” box should also be checked:

PE-0041-A Page 173 of 211 Issue Date: 21st May 2012


NOTE: Ensure that no other application is open that uses the same port else information will not be
transferred.
The “868MHz” channels should be selected for analysis. It is advisable to check all seven channels in the first
instance:

After analyzing the above radio environment, the User should start to de-select “busy” channels leaving clearer
channels for analysis:

As can be seen from the above screenshot, the chosen channel (Channel 7) appears to be the least busy. This
signal screen can be saved for future analysis. This is carried out by checking the “Save to log file” box:

PE-0041-A Page 174 of 211 Issue Date: 21st May 2012


PE-0041-A Page 175 of 211 Issue Date: 21st May 2012
To display this log file, click on the “Show log file” button. The RSSI Log File will display a log file for each
channel that has been selected – in the example only channel 7 has been saved:

Two alternative buttons will now be displayed – “Clear log file” and “Show RSSI”. If the first option is
selected, a warning window will be displayed to confirm this action:

If “YES” is selected the log file will be deleted and a further comment box will be displayed indicating that the
RSSI Log File could not be found:

Selecting “Show RSSI” will take the User back to the active screen.

PE-0041-A Page 176 of 211 Issue Date: 21st May 2012


The RSSI Log file is a dynamic file – each time “Show log file” is selected, the amount of readings recorded is
increased

PE-0041-A Page 177 of 211 Issue Date: 21st May 2012


FIRECLONE UTILITY

This utility allows the User to take a copy of a Central Node configuration. In the event of a fatal failure of a
Central Node or Expander Module, this copy can be uploaded to the new Central Node or Expander Module
without the need to re-program the associated field devices.

Although the Fireclone utility transfers the system configuration, the Loop Address of the Translator Module
and associated devices is NOT transferred. The Start Address should be recorded and this can then be
transferred to the new Translator Module.

To read the Loop Start Address access the “LOOP” menu, press P2, SA will appear, press P2, the Loop
Address will now appear. Record and press P1 until the LCD is blank. On completion, the Fireclone process
can now proceed.

DOWNLOAD THE CONFIGURATION FILE

Open the Wirelex Configuration Tool. To access this utility, select the “Tools” option and at the drop down
window select “FireClone Utility”:

A small window will open entitled “FireClone”:

PE-0041-A Page 178 of 211 Issue Date: 21st May 2012


PE-0041-A Page 179 of 211 Issue Date: 21st May 2012
Before commencing a clone of the installed Central Node, the User needs to ensure that the computer is talking
to the Central Node, ensure the correct COM Port is selected. Left clicking on the word “Options” will reveal a
drop-down window with one option “Settings”:

Select “Settings”. This will give the User the option to select the correct COM Port for this utility:

When the right COM Port has been selected, press :

The User is now ready to clone the installed Central Node and save a copy of the system configuration file to
his/her computer.

PE-0041-A Page 180 of 211 Issue Date: 21st May 2012


To start the process, click on the left hand smaller window that has a GREEN arrow pointing away from a
wireless interface (Central Node or Expander) towards a computer.

Note: Prior to clicking the sub-window, hovering the mouse over this sub-window will reveal the words
“Create image from an existing system”

Save the file in to a folder on the computer – if there is more than one Central Node on site, and each Central
Node interface configuration is being “Firecloned”, a separate file will be required for each interface. Press
on completion
The Fireclone process will now start. Progress will be seen initially in the “Running” box followed by
completion levels in the “Progress” bar:

PE-0041-A Page 181 of 211 Issue Date: 21st May 2012


PE-0041-A Page 182 of 211 Issue Date: 21st May 2012
When the copy is complete, a small window will appear indicating this:

Pressing will close this warning window and the original sub-window will now indicate where the file
has been saved on the computer:

PE-0041-A Page 183 of 211 Issue Date: 21st May 2012


UPLOADING A COPY OF THE CONFIGURATION FILE
When a file needs to be uploaded to a replacement Central Node, the following process should be followed.
Open the Wirelex Configuration Tool selecting the “Tools” option. A drop down window will appear allowing
the user to select the “Fireclone” utility:

When the Fireclone utility is selected, a small sub-window will appear. Hover the mouse over the right smaller
window with a RED arrow that indicates a transfer from a computer to a Central Node. A small message will
appear (see below left):

Clicking on this window will open another window allowing the user to select the required file for uploading:

PE-0041-A Page 184 of 211 Issue Date: 21st May 2012


Highlight the file for downloading pressing when correct.

PE-0041-A Page 185 of 211 Issue Date: 21st May 2012


The following window may appear initially indicating that the Central Node already has some information on:

If is selected, the process will stop. Selecting the option will start the Fireclone upload. As part
of the upload process, the Central Node will be cleaned prior to the file copy being uploaded. Upload progress
will be indicated in the “Progress” and “Running” bars:

When the upload is complete a small window will appear to indicate “End of copy”:

Pressing will close this small warning window.

PE-0041-A Page 186 of 211 Issue Date: 21st May 2012


The “Fireclone” sub-window will display two lines of text indicating where the file has been copied from

The “Fireclone” window can now be closed.


The information is now stored in the radio PCB of the new Central Node. In order for the Fire Control Panel to
correctly process the field device information, the following process should now be carried out:
Ensure that the “Configuration” tab is selected in the Wirelex Configuration Tool. Highlight “System” and
from the drop down window that appears, select “Add Central Node”:

A smaller window will open allowing the engineer to select the correct Central Node for the system (Translator
Module (SGW2W) or Conventional Expander Module (SGXWE)). Select the Central Node option:

PE-0041-A Page 187 of 211 Issue Date: 21st May 2012


PE-0041-A Page 188 of 211 Issue Date: 21st May 2012
The Central Node parameter page will now open:

Pressing will add a Translator Module under the word “System”. Right click on “System”. From
the drop down window that appears select “Collect all system properties”:

The computer will now connect to the Central Node in an attempt to download all system properties. The
following window will appear:

Select and the system will start to be downloaded.

PE-0041-A Page 189 of 211 Issue Date: 21st May 2012


If there are Expanders on the system and they are powered on and communicating with the Central Node, the
configuration of each Expander will also be downloaded.

Each Expander will take approximately 3 minutes to read - a window indicating progress will appear:

On completion of reading all Expanders attached to the Central Node, a small window will appear indicating that
the system has been read correctly:

The system interfaces (Central Node and associated Expanders) will now need to be programmed.

PE-0041-A Page 190 of 211 Issue Date: 21st May 2012


Right click on “SGW2W” selecting “Program SGW2W” from the drop down window that appears:

A small window will open indicating that that programming is taking place and progress of the programming:

A window will appear indicating programming is complete:

PE-0041-A Page 191 of 211 Issue Date: 21st May 2012


To program each Expander, right click on “SGWE” selecting “Program SGWE”:

A window will appear reminding the user that the Expander must have been programmed previously and must
be powered on for this operation to be carried out successfully:

Selecting will start the remote programming of the Expander. A small window will appear indicating
progress and time remaining for the operation to complete:

PE-0041-A Page 192 of 211 Issue Date: 21st May 2012


On completion a small window will appear indicating the success of the operation:

On completion of programming all Expanders, a final programming of the Central Node should take place.
Right click on “SGW2W” selecting “Program SGW2W” from the drop down window that appears:

A small window will appear indicating progress of the programming:

PE-0041-A Page 193 of 211 Issue Date: 21st May 2012


On completion of all programming a further window will appear indicating this process is complete:

In order for the configuration file to be brought forward, a “LOAD” command should be carried out at the
Translator Module.
At the Translator Module, use P3/P4 buttons scrolling through until is displayed. Press P2. will be
displayed. Press P2; will be displayed. Scroll up using P3/P4 buttons until is displayed. Press
P2. will be displayed. Press P2. This completes the LOAD command. To confirm the LOAD command
is complete, the word will be displayed on the Translator Module LCD screen.
Ensure that the Loop Address recorded earlier is now transferred to the new Translator Module. This can be
checked by carrying out the following process:

Use the up/down buttons (P3/P4) to scroll through to the required Loop Address. When the correct address
has been reached, press P2 to confirm the change.

This completes the Fireclone process.

NOTE: To ensure the system is fully backed-up, a Fireclone should be carried out at the Central Node and
each Expander associated with the Central Node

PE-0041-A Page 194 of 211 Issue Date: 21st May 2012


VOICE ANNUNCIATOR (ORPHEY) UTILITY
To program voice messages in to the wireless Voice Sounder, there is a utility available on the Wirelex
software.
NOTE: Before commencing the programming process, power on the Voice Sounder by inserting the supplied
batteries in the correct orientation.

To open the utility, left click on “Tools” and select “Orphey utility” (see below)

This will open the utility and allow an installer to program Hyfire Voice Annunciator devices with bespoke
messages – each device will need to be programmed.
(Note: the voice message must be in a *.wav format, 16KHz 8bit format)
The window below will appear:

From this page, select the “Programming” option.

PE-0041-A Page 195 of 211 Issue Date: 21st May 2012


The following page will be revealed. If the Voice Sounder is not connected to the computer, a drawing of a
RS232 lead will be displayed and a warning will be shown. Select the correct COM port for communication
between the computer and the device.

Connect the Voice Sounder to the computer using a RS232 lead and the displayed picture will change from a
lead to a representation of Voice Sounder (see below).
To start the programming process, the location of the sound files to be imported must be identified. Select the
correct location by clicking on the icon highlighted (below left). The sound files will need to be located from the
computer hard drive (example below right)

The sound files should now be detailed in the window on the left of the screen.
(The image above is an example and may be appear differently on other computers)

PE-0041-A Page 196 of 211 Issue Date: 21st May 2012


Identify the sound file that will be loaded in to the Voice Sounder dragging it to the “Message 1” box in the
“Computer” section.

This section will be updated with the message title and the expected duration of the message. If required, the
audio message can now be played back by clicking on the small sounder icon (bottom middle icon). The
maximum time duration of audio messages that can be transferred is 32 seconds.

To transfer the message from the computer to the Voice Sounder, click the computer mouse over the small
icon, centre screen, containing three arrows pointing to the right.

PE-0041-A Page 197 of 211 Issue Date: 21st May 2012


A small warning message will be displayed asking the user to confirm that the message should be written in to
the device. Select .

When the transfer commences, an additional process will appear in the “Orphey-R” section indicating time
remaining for the transfer:

At the Voice Sounder a small surface mounted LED will glow RED indicating that a data transfer is taking place.
On completion of the download, the “Device Memory” table will be updated and the sound files will be
displayed.

PE-0041-A Page 198 of 211 Issue Date: 21st May 2012


The messages can now be tested by clicking on the Speaker icon in the “Device memory”. The programming
process needs to be completed for each device to be used.

PE-0041-A Page 199 of 211 Issue Date: 21st May 2012


INTENTIONALLY BLANK

PE-0041-A Page 200 of 211 Issue Date: 21st May 2012


SECTION 8 – MAINTENANCE VISITS
INTRODUCTION……………………………………………………………………………………..… Page 169
CONNECT COMPUTER TO AN EXISTING SYSTEM…………………………………………….. Page 169
REPLACING / CHANGING A FIELD / CHILD DEVICE.…………………………………………… Page 173
CENTRAL NODE FIELD DEVICE………………..…………………………………………. Page 173
EXPANDER MODULE FIELD DEVICE…………………………………………………….. Page 174
INTRODUCTION
During site maintenance visits, an engineer may be tasked to take readings of an existing radio system to
ensure the radio integrity of the system is still intact. If the building layout has changed, some devices may
need to be added or deleted from the Central Node or an Expander may need to be added to incorporate
further devices in a new extension to the building or to add devices for a temporary building (e.g. Portacabins)
during sports events, corporate hospitality, etc.

CONNECTING COMPUTER TO A LIVE SYSTEM


Open the Wirelex software selecting the “Configuration” tab. Right click on the “System” icon, a small
window will appear. Highlight and select the “Collect all system properties” option.

A small window will appear to remind the user that the system code of the current software program is different
to the system code of the connected Central Node:

Select .
PE-0041-A Page 201 of 211 Issue Date: 21st May 2012
PE-0041-A Page 202 of 211 Issue Date: 21st May 2012
A small window will now appear to indicate that the computer is now linked to the Central Node and is
downloading the configuration from its Non Volatile Memory:

If there are Expanders on the system the computer will automatically link through the Central Node to the
Expanders and read the configuration contained within them:

Note: All Expanders should be powered on and be in communication with the Central Node:

On completion of reading all wireless interfaces, a small window will appear to indicate completion.

PE-0041-A Page 203 of 211 Issue Date: 21st May 2012


PE-0041-A Page 204 of 211 Issue Date: 21st May 2012
Press .

Before proceeding further, the system configuration file should now be saved on the computer. On completion
select the “Events” tab checking the “Turn on data exchange” box.

This box should then be unchecked and the small box showing “Get all” should be clicked:

This will start to download all events connected with this particular system:

PE-0041-A Page 205 of 211 Issue Date: 21st May 2012


On completion of the event download, check the “Turn on data exchange” box again. The computer is now
dynamically linked to the Central Node. All future events will now be recorded with real time date/time stamps
until the computer is disconnected.

The Wirelex Configuration Tool can now be used as a diagnostic aide allowing the user to analyse signal levels
between devices and Central Nodes or Expanders; investigate the status of devices; remotely control device
LEDs; investigate system traffic levels, etc.

PE-0041-A Page 206 of 211 Issue Date: 21st May 2012


REPLACING / CHANGING A FIELD / CHILD DEVICE
If a child device is suspected of being faulty, that device can be changed with a replacement device without
deleting the original device from the system.

Having downloaded an existing system (see page 169), the initial action of the engineer is to remove the
suspect device(s) from its installed position and remove the primary power cell from the device. This will turn
the device off and will eliminate the possibility of a “Child device substitution attempt” (see page 120) fault
appearing in the Central Node Event Log.

Identify the suspect device at the Central Node or Expander Module (in the following example, there are two
suspect devices – one on the Central Node (a Smoke Detector) and one on the Expander Module (a Heat
Detector)

CENTRAL NODE FIELD DEVICE

Right clicking on the device, the User will be presented with a drop down window. Select
“Local programming (RS232)”, at which point a further window will appear with three options. The centre
option should be selected “Re-initiate child device”:

The Central Node will initiate a search pattern for the child device:

At this point, the secondary power cell should be inserted in to the new device and the programming switch
moved from the 1 position to the ON position.

PE-0041-A Page 207 of 211 Issue Date: 21st May 2012


Insert the primary power cell in the new device. The Smoke Detector LED will blink RED 4 times (to indicate
the device has powered on and entered programming mode). On completion, move the Smoke Detector
programming switch from the ON position to the 1 position. The Smoke Detector LED will flash GREEN twice
(showing that initial programming is completed). The following window will now be displayed on the computer:

Press . The new device has now assumed the same parameters as the previous device including the
same analogue loop address

No further action is required.

EXPANDER MODULE FIELD DEVICE

Right clicking on the suspect device in the Expander configuration will show a drop down window with one
additional option as compared to the Central Node:

To replace a device directly associated with an Expander, the User has two options:

1. The computer is still connected to the Central Node. The User should select
“Remote programming (through SGW2W)” followed by “Reinitiate child device” repeating the
process detailed above for changing a device on a Central Node.

PE-0041-A Page 208 of 211 Issue Date: 21st May 2012


2. The computer is connected to the Expander directly associated with the child device. The User should
select “Local programming (RS232)” followed by
“Reinitiate child device” repeating the process detailed above for changing a device on a Central
Node.

Press . The device may then flash RED for a short period of time. The device will then flash GREEN
two more times before extinguishing.
The device has now been changed and should be put back in to its installed position. This is all that is required
of the engineer to change a device.
(Some engineers may choose to carry out a “Program SGW2W / SGXWE” process followed by a “LOAD”
command at the Translator Module itself. This is only necessary if a NEW device is added to the existing
system).
The above process can be carried out if there is a requirement to change a device on an Expander. The
process is very similar. Download the whole program (following the procedure detailed in page 169). When all
the information is available to the engineer, the process to replace a device on an Expander is the same as for
replacing a device on a Central Node – the only difference is if the engineer is connected to the Central Node or
to the Expander. If the computer is connected to the Expander, the procedure detailed above is to be followed.
If the computer is connected to the Central Node, then a remote replacement process should be followed.
Ensure the device is removed from its installed position and that the power cells are removed. Unpack the new
device inserting the Secondary power cell in to the device and moving the device “Programming” switch to the
“ON” position.
At the Wirelex software, ensure the “Configuration” tab is displayed and that the required EM is highlighted in
the “Radiosystem topology” area. Highlight the device to be changed in the “Child device” area. Right click
on the device highlighting “Remote programming (through SGW2W / SGXWE)” and “Re-initiate device”
(see image overleaf).

PE-0041-A Page 209 of 211 Issue Date: 21st May 2012


INTENTIONALLY BLANK

PE-0041-A Page 210 of 211 Issue Date: 21st May 2012


For technical support concerning this product, please contact
Sterling Safety Systems: -

Tel: 01926 485282

Email: [email protected]

“Please visit the Sterling Safety Systems website for further information relating to the Hybrid Radio Module and
associated devices:

www.sterlingsafety.co.uk

Your feedback is vital for the continuing development of our offerings. If you have any comments relating to this
manual, products or services please contact [email protected] to register your feedback.

PE-0041-A Page 211 of 211 Issue Date: 21st May 2012

You might also like