Hyfire Manual
Hyfire Manual
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.
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:
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
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.
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.
-30°C to 55°C
and
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.
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.
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:
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.
• 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.
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.”
• IT Cabling
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.
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
• 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.
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 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.
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 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.
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 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.
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.
Spare secondary power cell compatible with all hybrid wireless devices.
HFW-SB-01
(sold in packs of 10) (not compatible with audio-visual devices)
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.
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.
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.
a. Fixed – A standard “Fixed Temperature” Detector operating in the 58°C - 64°C zone.
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.
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).
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)
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.
LIGHT INTENSITY
SWITCH SELECTOR
Selected switch level Flash rate switch indicator Light intensity switch selector
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.
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.
150m 150m
250m
1400m
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.
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 -
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)
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.
• 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.
• 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:
– 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.
– 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.
• 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.
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
• 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.
• 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.
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.
Primary battery level for device with analogue loop address 138 is low
Secondary battery level for device with analogue loop address 138 is low
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 that the radio PCB and the analogue PCB are not synchronised and a
“LOAD” command must be carried out
• RF Device programming
• FCP configuration
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.
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.
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
FAULT RELAY
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.
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.
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.
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.
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
Termination Details
Main Monitoring } Monitoring circuit for external power supply – not used if
Backup Monitoring } using +24V from the associated Fire Control Panel
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
Sounder EOL Resistor + } As defined by the Conventional Fire Control Panel or the
Sounder EOL Resistor – } associated Sounder Control Card
Maximum current (I) consumption of the Conventional Expander Module is ≤ 30mA (@24V dc)
- + FAULT RELAY
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.
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)
Press
This will start the Installation Wizard for the Wirelex software. With the Wizard started the following window will
appear:
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.
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:-
a. b.
c. d.
e. f.
g.
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”.
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.
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
(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”
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.
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.
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.
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.
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.
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
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.
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:
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.
The window will close and the user will be directed back to the “Configuration” tab for adding further devices (if
required).
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.
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:
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.
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.
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).
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.
The output can be selected as a constant or switching output by changing the mode in the drop down window:
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.
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.
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:
Select
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)
On completion of programming, the user is advised that programming is complete by the appearance of a
further sub-window:
Press :
(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.
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.
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:
The next step is to carry out a LOAD command 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.
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.
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.
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):
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:
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”:.
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.
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:
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:
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.
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:
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 ( ):
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:
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
It is advisable that all power cells – Standby / Reserve and Main / Primary are changed should this fault occur.
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
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.
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 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.
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.
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.
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:
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:
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.
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.
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
:
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)”:
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):
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
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.
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
SAME LAYER
Expander Module
Expander Module
COMBINATION
Expander Module
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):
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.
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
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.
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.
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.
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”
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:
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:
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.
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.
Open the Wirelex Configuration Tool. To access this utility, select the “Tools” option and at the drop down
window select “FireClone Utility”:
Select “Settings”. This will give the User the option to select the correct COM Port for this utility:
The User is now ready to clone the installed Central Node and save a copy of the system configuration file to
his/her 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:
Pressing will close this warning window and the original sub-window will now indicate where the file
has been saved on the computer:
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:
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”:
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:
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:
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.
A small window will open indicating that that programming is taking place and progress of the programming:
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:
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:
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.
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
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:
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)
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.
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.
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.
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:
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.
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)
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.
Press . The new device has now assumed the same parameters as the previous device including the
same analogue loop address
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.
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).
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.