Fire Alarm & Emergency Communication System Limitations
While a life safety system may lower insurance rates, it is not a substitute for life and property insurance!
An automatic fire alarm system—typically made up of smoke
detectors, heat detectors, manual pull stations, audible warning
devices, and a fire alarm control panel (FACP) with remote notification capability—can provide early warning of a d eveloping fire. Such
a system, however, does not assure protection against property
damage or loss of life resulting from a fire.
An emergency communication system—typically made up of an
automatic fire alarm system (as described above) and a life safety
communication system that may include an autonomous control
unit (ACU), local operating console (LOC), voice communication,
and other various interoperable communication methods—can
broadcast a mass notification message. Such a system, however,
does not assure protection against property damage or loss of life
resulting from a fire or life safety event.
The Manufacturer recommends that smoke and/or heat detectors
be located throughout a protected premises following the
recommendations of the current edition of the National Fire
Protection Association Standard 72 (NFPA 72), manufacturer's
recommendations, State and local codes, and the
recommendations contained in the Guide for Proper Use of System
Smoke Detectors, which is made available at no charge to all
installing dealers. This document can be found at http://
www.systemsenso r.com/appguides/. A study by the Federal
Emergency Management Agency (an agency of the United States
government) indicated that smoke detectors may not go off in as
many as 35% of all fires. While fire alarm systems are designed to
provide early warning against fire, they do not guarantee warning o r
protection against fire. A fire alarm system may not provide timely or
adequate warning, or simply may not function, for a variety of
reasons:
Smoke detectors may not sense fire where smoke cannot reach
the detectors such as in chimneys, in or behind walls, on roofs, or
on the other side of closed doors. Smoke detectors also may not
sense a fire on another level or floor of a building. A second-floor
detector, for example, may not sense a first-floor or basement fire.
Particles of combustion or “smoke” from a developing fire may
not reach the sensing chambers of smoke detectors because:
• Barriers such as closed or partially closed doors, walls, chimneys, even wet or humid areas may inhibit particle or smoke
flow.
• Smoke particles may become “cold,” stratify, and not reach the
ceiling or upper walls where de tectors are located.
• Smoke particles may be bl o w n awa y fr om de t ec t ors by ai r ou tlets, such as air conditioning vents.
• Smoke particles may be drawn into air returns before reaching
the detector .
The amount of “smoke” present may be insuf ficient to alarm smoke
detectors. Smoke detectors are designed to alarm at various levels
of smoke density. If such density levels are not created by a developing fire at the location of detectors, the detectors will not go into
alarm.
Smoke detectors, even when working properly, have sensing limitations. Detectors that have photoelectronic sensing chambers tend
to detect smoldering fires better than flaming fires, which have little
visible smoke. Detectors that have ionizing-type sensing chambers
tend to detect fast-flaming fires better than smoldering fires.
Because fires develop in different ways and are often unpredi ctable
in their growth, neither type of detector is necessarily best and a
given type of detector may not provide adequate warning of a fire.
Smoke detectors cannot be expected to provide adequate warning
of fires caused by arson, children playing with matches (especially
in bedrooms), smoking in bed, and violent explosions (caused by
escaping gas, improper storage of flammable materials, etc.).
Heat detectors do not sense particles of combustion and alarm
only when heat on their sensors increases at a predetermined rate
or reaches a predetermined level. Rate-of-rise heat detectors may
be subject to reduced sensitivity over time. For this reason, the rateof-rise feature of each detector should be tested at least once per
year by a qualified fire protection specialist. Heat detectors are
designed to protect property, not life.
IMPORTANT! Smoke detectors must be i nstalled in the same
room as the control panel and in rooms used by the system for the
connection of alarm transmission wiring, communications, signaling, and/or power. If de tectors are not so located, a developing fire
may damage the alarm system, compromising its ability to report a
fire.
Audible warning devices such as bells, horns, strobes, speakers and displays may not alert people if these devices are located
on the other side of closed or partly open doors or are located on
another floor of a building. Any warning device may fail to alert people with a disability or those who have recently consumed drugs,
alcohol, or medication. Please note that:
• An emergency communication system may take priority over a
fire alarm system in the event of a life safety emergency .
• Voice messagi ng systems must be designed to me et intelligibility
requirements as defined by NFPA, local codes, and Authorities
Having Jurisdiction (AHJ).
• Language and instructional requirements must be clearly disseminated on any local displays.
• Strobes can, under certain circumstances, cause seizures in
people with conditions such as epilepsy.
• Studies have shown tha t ce rt ain people, even when they hea r a
fire alarm signal, do not respond to or comprehend the meaning
of the signal. Audib le devices, such as h orns and bell s, can have
different tonal patterns and frequencies. It is the property
owner's responsibility to conduct fire drills and other training
exercises to make people aware of fire alarm signals and
instruct them on the proper reaction to alarm signals.
• In rare instances, the sounding of a warning device can cause
temporary or permanent hearing loss.
A life safety system will not operate without any e lectrical power. If
AC power fails, the system will operate from standby batteries only
for a specified time and only if the batteries have been properly
maintained and replaced regularly.
Equipment used in the system may not be technically compat ible
with the control panel. It is essent ial to use only equi pment li sted for
service with your control panel.
Telephone lines needed to transmit alarm signals from a premises
to a central monitoring station may be out of service or temporarily
disabled. For added protection against telephone line failure,
backu
p radio transmission systems are recommended.
The most common cause of life safety system malfunction is inadequate maintenance. To keep the entire life safety system in excellent working order, ong oing maintenance is required per the
manufacturer's recommendations, and UL and NFPA standards. At
a minimum, the requirements of NFPA 72 shall be followed. Environments with large amounts of dust, dirt, or high air velocity require
more frequent maintenance. A maintenance agre ement should be
arranged through the local manufacturer's representative. Maintenance should be scheduled as required by Nat ional and /or lo cal fire
codes and should be performed by authorized professional life
safety system installers only. Adequate written records of all inspections should be kept.
Adherence to the following will aid in problem-free installation with long-term reliability:
WARNING - Several different sources of power can be connected to the fire alarm control panel. Disconnect all sources of
power before servicing. Control unit and associated equipment may
be damaged by removing and/or inserting cards, modules, or interconnecting cables while the unit is energized. Do not attempt to
install, service, or operate this unit until manuals are read and
understood.
CAUTION - System Re-acceptance Test after Software
Changes: To ensure proper system op eration, this product must be
tested in accordance with NFPA 72 after any programming operation or change in site-specific software. Re-acceptance testing is
required after any change, addition or deletion of system components, or after any modification, repair or adjustment to system
hardware or wiring. All components, circuits, system operations, or
software functions known to be affect ed by a change must be 10 0%
tested. In addition, to ensure that other operations are not inadvertently affected, at least 10% of initi ating devic es that are no t directly
affected by the change, up to a maximum of 50 devices, must also
be tested and proper system operation verified.
This system meets NFPA requirements for operation at 0-49º C/
32-120º F and at a relative humidity 93% ± 2% RH (non-condensing) at 32°C ± 2°C (90°F ± 3°F). However, the useful life of the system's standby batteries and the electronic components may be
adversely affected by extreme temperature ranges and humidity.
Therefore, it is recommended that this system and its peripherals
be installed in an environment with a normal room temperature of
15-27º C/60-80º F.
Verify that wire sizes are adequate for all initiating and indicating
device loops. Most devices cannot tolerate more than a 10% I.R.
drop from the specified device voltage.
Like all solid state electronic devices, this system may operate
erratically or can be damaged when subjected to lightning induced
transients. Although no system is completely immu ne from lightning
transients and interference, proper grounding will reduce susceptibility . Overhead or out side aerial wiring is not recommended, due to
an increased susceptibility to nearby lightning st rikes. Consult with
the Technical Se rvices Department if any problems are anticipated
or encountered.
Disconnect AC power and batteries prior to removing or inserting
circuit boards. Failure to do so can damage circuits.
Remove all electronic assemblies prior to any drilling, filing,
reaming, or punching of the enclosure. When possible, make all
cable entries from the sides or rear. Before making modifications,
verify that they will not interfere with battery, tr ansformer, or printed
circuit board location.
Do not tighten screw terminals more than 9 in-lbs. Over-tightening may damage threads, resulting in reduced terminal contact
pressure and difficulty with screw terminal removal.
This system contains static-sensitive components. Always
ground yourself with a proper wrist strap before handling any circuits so that static charges are removed from the body. Use static
suppressive packaging to protect electronic assemblies removed
from the unit.
Units with a touchscreen display should be cleaned with a dry,
clean, lint free/microfiber cloth. If additio nal cleaning is required,
apply a small amount of Isopropyl alcohol to the cloth and wipe
clean. Do not use detergents, solvents, or water for cleaning. Do
not spray liquid directly ont o th e dis p la y.
Follow the instructions in the installation, operating, and programming manuals. These instructions must be followed to avoid
damage to the control panel and associated equipment. FACP
operation and reliability depend upon proper installation.
Precau-D2-11-2017
FCC Warning
WARNING: This equipment generat es, uses, and can radi-
ate radio frequency energy and if not installed and used in
accordance with the instruction manual may cause interference to radio communications. It has been tested and foun d
to comply with the limits for class A computing devices pursuant to Subpart C of Part 15 of FCC Rules, which is
designed to provide reasonable protection against such
interference when devices are operated in a commercial
environment. Operation of this equipment in a residential
area is likely to cause interference, in which case the user
will be required to correct the interference at his or her own
expense.
Canadian Requirements
This digital apparatus does not exceed the Class A limits for
radiation noise emissions from digital apparatus set out in
the Radio Interference Regulations of the Canadian Department of Communications.
Le present appareil numerique n'emet pas de bruits radioelectriques depassant les limites applicables aux appareils
numeriques de la classe A prescrites dans le Reglement sur
le brouillage radioelectrique edicte par le ministere des
Communications du Canada.
LiteSpeed™ and Lite-Connect™ are trademarks; and Fire-Lite® Alarms, Honeywell®, and SWIFT® are registered trademarks of Honeywell International Inc.
Microsoft® and Windows® are registered trademarks of the Microsoft Corporation. Chrome™ and Google™ are trademarks of Google Inc. Firefox® is a registeredtrademark of The Mozilla Foundation.
In order to supply the latest features and functionality in fire alarm and life safety technology to our customers, we make frequent
upgrades to the embedded software in our products. To ensure that you are installing and programming the latest features, we
strongly recommend that you download the most current version of software for each product prior to commissioning any system.
Contact Technical Support with any questions about software and the appropriate version for a specific application.
Documentation Feedback
Your feedback helps us keep our documentation up-to-date and accurate. If you have any comments or suggestions about our online
Help or printed manuals, you can email us.
Please include the following information:
•Product name and version number (if applicable)
•Printed manual or online Help
•T opic Title (for online Help)
•Page number (for printed manual)
•Brief description of content you think should be improved or corrected
•Your suggestion for how to correct/improve documentation
Send email messages to:
FireSystems.TechPubs@honeywell.com
Please note this email address is for documentation feedback only. If you have any technical issues, please contact Technical
Services.
1.4: About this Manual..............................................................................................................................................................................................9
1.5: About the Mesh Network.................................................................................................................................................................................10
2.2.2: Federal Institute of Telecommunications ..................... ............................... .........................................................................................11
2.4: Magnetic Sensors.............................................................................................................................................................................................12
2.4.1: Mesh Formation Magnetic Sensor............................................................................. ...........................................................................12
2.4.2: Magnetic Sensor ......................................................... ..........................................................................................................................12
2.5: LED Indicators.................................................................................................................................................................................................12
2.6: Installing the Gateway .....................................................................................................................................................................................12
2.6.1: Before Installing .............................. .......................................................... .. .........................................................................................12
2.7: Mounting and Wiring.......................................................................................................................................................................................13
2.7.3: Gateway Powered by the SLC..............................................................................................................................................................15
2.7.4: Gateway Powered by an External, Regulated +24VDC Source...........................................................................................................15
2.8: Configuration and Programming .....................................................................................................................................................................16
2.8.1: Assign a Profile.....................................................................................................................................................................................16
2.8.2: Remove a Profile ..................................................................................................................................................................................17
Remove a Profile from a Gateway using SWIFT Tools.........................................................................................................................17
Remove a Profile from a Gateway without using SWIFT Tools............................................................................................................18
2.8.3: Create a Mesh Network ....................................... ............................. ....................................................................................................18
2.9.2: LED Patterns. ............................ ............................. ...............................................................................................................................22
2.9.3: Lock/Unlock the Gateway ....................................................................................................................................................................22
Lock/Unlock the Gateway Using SWIFT Tools.....................................................................................................................................22
Possible Wireless Mesh Overlap ................................................................................... .........................................................................23
Disabling Max Gateway Reporting .............................. ............................... ...........................................................................................26
2.9.5: Weak Link Trouble Reporting..............................................................................................................................................................27
Disable Trouble Reporting at the Gateway Using SWIFT Tools...........................................................................................................27
Collapse Mesh Network Using SWIFT Tools........................................................................................................................................28
Silence Mesh Network Using SWIFT Tools ..........................................................................................................................................29
3.2.2: Federal Institute of Telecommunications.............................................................................................................................................32
3.4: Magnetic Sensors.............................................................................................................................................................................................33
3.5: Display Driver LED Indicators........................................................................................................................................................................33
3.7.1: Assign a Profile.....................................................................................................................................................................................35
Restoring to Factory Default Without Using SWIFT Tools...................................................................................................................36
Restoring to Factory Default Using SWIFT Tools........................... ............................. .........................................................................36
3.9.1: Modes of Operation Not in a Mesh Network .......................................................................................................................................38
3.9.2: Modes of Operation as a Mesh Participant.......... .................................................................................................................................38
3.10.1: Annunciator Control Buttons and Visual Indicators ..........................................................................................................................39
RF Comm Loss.......................................................................................................................................................................................40
Trouble Wireless Mesh Formation In Progress......................................................................................................................................40
Trouble Class A Missing 2nd Link.........................................................................................................................................................40
System Normal .......................................................................................................................................................................................40
Trouble Weak Link Low Signal Strength...............................................................................................................................................40
Key Bus Trouble................. ............................ .......................................................... ..............................................................................40
Maximum Gateways...............................................................................................................................................................................41
RF Device No Answer............................................................................................................................................................................41
4.2.2: Federal Institute of Telecommunications ..................... ............................... .........................................................................................43
4.5: Configuration and Programming .....................................................................................................................................................................44
4.5.3: Restoring a Device to Factory Default .................................................................................................................................................45
Site Survey Mode....................................................................................................................................................................................47
6.2.2: Federal Institute of Telecommunications ..................... ............................... .........................................................................................52
6.3.2: Serial Communication Specification ....................................................................................................................................................53
Appendix A: SWIFT Tools............................................................................................................................................... 57
A.2: Launching SWIFT Tools.................................................................................................................................................................................57
A.2.1: Creating a New Jobsite ........................................................................................................................................................................57
A.2.2: Opening an Existing Jobsite ................................................................................................................................................................58
A.3: Connecting to the Gateway.............................................................................................................................................................................58
A.3.1: Accessing a Locked Gateway .................... ............................. ............................. ................................................................................58
A.3.2: Creating a New Password for a Gateway ............................................................................................................................................58
Appendix B: Site Survey................................................................................................................................................. 60
B.1: Conduct a Site Survey.....................................................................................................................................................................................60
B.1.1: Link Quality Test ........ ............................. ............................. ............................. ..................................................................................60
Basic Requirements of a Link Quality Test........... .......................................................... .......................................................................60
Conduct a Link Quality Test.............................. .......................................................... ...........................................................................60
Results of a Link Quality Test ................................................. ............................. ..................................................................................61
After a Link Quality Test........................................................................................................................................................................61
B.1.2: RF Scan Test .................... ............................ ........................................................ ................................................................................61
Conduct an RF Scan Test............... ............................. .......................................................... ..................................................................61
Status of an RF Scan Test... ............................ ............................. ............................. ..............................................................................61
B.1.3: Retrieving Site Survey Results .............. .......................................................... ....................................................................................62
Appendix C: Troubleshooting and Testing................................................................................................................... 63
C.2: Testing the Gateway and Devices ...................................................................................................................................................................64
C.2.1: Testing LED Indicators........................................................................................................................................................................64
C.3: Testing the Wireless Network .........................................................................................................................................................................64
Class A Compliance........................................ ............................. ............................. ..............................................................................65
C.3.2: History Events.................... .......................................................... ........................................................................................................65
Appendix D: LED Indicators........................................................................................................................................... 67
The SWIFT® Network Manual provides an overview of the following:
•Wireless fire alarm system
•Instructions for installing and configuring the wireless devices
•Information on monitoring the status of the wireless devices
•Removal and replacement procedures of the Wireless Gateway and Display Driver
•Testing, maintenance, and firmware upgrade information of the Wireless Gateway and Display Driver
1.2 Assumed Knowledge
This document is created with the assumption that all use rs are familiar with working on a PC and laptop for configuration purposes.
Installers should be familiar with the fire alarm and related service standards. The terminology and level of details of this document
reflect this assumption.
1.3 Additional References
The table below provides a list of documents referenced in this manual, as well as documents for selected other compatible devices.
Fire•Lite SLC Wiring Manual51309
ES-50X Series Fire Alarm Control PanelLS10129-000FL-E
ES-200X Series Fire Alarm Control PanelLS10131-000FL-E
MS-9200UDLS Fire Alarm Control Panel52750
MS-9600(UD)LS Fire Alarm Control Panel52646
ANN-80 Series Remote Fire Annunciator 52749
W-SD355 Wireless LiteSpeed Photo Detector with 4” BaseI56-4081
W-SD355T Wireless LiteSpeed Photo/Heat Detector with 4” BaseI56-4081
W-H355R Wireless LiteSpeed Rate Of Rise Heat Sensor with 4” BaseI56-4082
W-H355 Wireless LiteSpeed Fixed Heat Sensor with 4” BaseI56-4082
W-MMF Wireless Monitor ModuleI56-4083
W-CRF Wireless Relay ModuleI56-8503
W-BG12LX Wireless PullstationI56-426X
WAV-RL Red Wall AV BaseI56-6517
WAV-WL White Wall AV BaseI56-6517
WAV-CRL Red Ceiling AV BaseI56-6517
WAV-CWL White Ceiling AV BaseI56-6517
SWIFT Wireless AV BasesI56-6517
W-SYNC Wireless Sync ModuleI56-6518
MDL3 Sync ModuleI56-3157
HPFF8 NAC Expander53499
HPFF12 NAC Expander53576
Section 1: Overview
1.4 About this Manual
This manual correlates with SWIFT Tools version 4.0 (and higher) an d the programming features included in that release. Devices not
running the current version of the software will not have the same capabilities. Ensure the latest version of SWIFT Tools is installed for
proper functionality.
Systems running version 4.0 (and higher) will:
•require device tamper to remove a profile (return to factory default) with a 60 minute timeout.
•have option to enable/disable max gateway trouble reporting.
•require device tamper to upgrade the firmware on individual devices.
Systems running 4.0 (and higher) will not be able to:
•create profiles in the gateway without using SWIFT Tools.
All devices within the mesh network must be running the same firmware version. Refer to Appendix E, “Firmware Upgrade/Downgrade
Instructions” for more information.
Use of these products in combination with non-Honeywell products in a wireless mesh network, or to access, monitor, or control devices
in a wireless mesh network via the internet or another external wide area network, may require a separate license from Sipco, LLC. For
more information, contact Sipco, LLC or IntusIQ (Ipco), LLC at 8215 Roswell Rd, Building 900, Suite 950. Atlanta, GA 30350, or at
www.sipcollc.com or www.intusiq.com.
1.6 Abbreviations
The following table lists the abbreviations and their definitions used in this manual.C
AbbreviationDefinition
AHJAuthority Having Jurisdiction
ANSIAmerican National Standards Institute
dBmUnits of RF power (0dBm = 1mW)
FACPFire Alarm Control Panel
FCCFederal Communications Commission
ISM BandIndustrial, Scientific and Medical Radio Bands
LCDLiquid Crystal Display
LEDLight Emitting Diode
mAMilliampere
MHzMegahertz
NFPANational Fire Protection Association
PCPersonal Computer
RFRadio Frequency
SLCSignaling Line Circuit
UIUser Interface
ULUnderwriters Laboratories
W-DIS-DWireless Display Driver
W-GATEWireless Gateway
1.7 Cybersecurity Recommendations
•When using SWIFT Tools to update the firmware of the gateway or devices, ensure updates are performed in a secure location
where no eavesdropping on the wireless signals is possible.
•Ensure the PC running SWIFT Tools has full disk encryption. Full encryption of any backed-up data is also recommended.
•The wireless gateway should be secured in a location which is only accessible to authorized personnel.
•When any SWIFT gateway or device is decommissioned from service, return the equipment to the factory default state by removing
profiles.
The W-GATE is a device in a wireless fire system that acts as a bridge b etwe en fire ala rm control panels (FACPs) and wireless fire
devices. All wireless fire devices communicate with the gateway over the wireless network formed by the devices and the gateway.
The SWIFT Wireless Sensor Network includes a W-DIS-D (Wireless Display Driver). The W-DIS-D and an ANN-80-W are required for
the display of wireless-specific events. The W-DIS-D and ANN-80-W are explained in detail in Section 3.
NOTE: The W-DIS-D and ANN-80-W are not required for use with the ES-50X or ES-200X FACPs.
The gateway is powered by either the SLC loop or by any external +24VDC UL listed power supply. The gateway uses the LiteSpeed
protocol on the SLC to communicate with the panel and a proprietary wireless protocol to communicate with wireless fire devices. The
following graphic is an illustration of the components of the SWIFT Network.
Section 2: W-GATE Wireless Gateway
2.2 Agency Approvals
2.2.1 FCC
This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:
1.This device may not cause harmful interference, and
2.This device must accept any interference received, including interference that may cause undesired operation.
3.FCC ID: PV3WFSGW
WARNING: DO NOT MAKE CHANGES TO THE EQUIPMENT
CHANGES OR MODIFICA TIONS NOT EXPRESSLY A PPROVED BY THE MANUFACTURER COULD VOID THE USER’S
AUTHORITY TO OPERATE THE EQUIPMENT.
2.2.2 Federal Institute of Telecommunications
This device utilizes the Honeywell915 rev A radio module and complies with IFETEL standard(s).
IFT: RCPHOSW14-1983
2.3 Specifications
Following are the specifications of the wireless gateway.
External Supply Electrical Ratings18V-30V
SLC Electrical Ratings15V-30V
Maximum current when using the external supply40mA
Maximum current when using the SLC power supply24mA
Figure 2.2 LEDs and Mesh Formation Sensor on the W-GATE
LEDs
Mesh
Formation
Magnetic
Sensor
cover.wmf
magnetic
sensor
Maximum SLC Resistance50Ω
Minimum signal strength level needed at the receiver for a primary path with weak
link trouble reporting enabled.
Minimum signal strength level needed at the receiver for a secondary path or
primary path with weak link trouble reporting disabled.
Maximum ambient noise level-85dBm
Maximum RF Power Output+17dBm (Tx power level without antenna)
Radio FrequencyLower ISM Band (902 - 928MHz).
1 Ensure that the primary path signal strength level is within recommended guidelines to assure proper communication in the
mesh network.
-55dBm
Must be 18 dBm higher than the noise
floor down to a minimum of -80dBm
Gateway0°C-49°C / 32°F-120°F-10°C- 60°C / 14°F-140°F10 to 93% RH, Non-condensing
2.4 Magnetic Sensors
Magnets must have a holding strength of 10 lbs or greater. Use either the north or south pole of the magnet to activate sensors.
2.4.1 Mesh Formation Magnetic Sensor
The mesh formation magnetic sensor (refer to Figure 2.2) transitions the gateway in and out of mesh formation mode. The initial activation of the sensor puts the gateway in mesh formation mode (as long as it contains a profile). A subsequent activation of the magnetic
sensor transitions the gateway out of mesh formation and into the initial mesh restructuring and normal mode. The gateway can be
placed back into mesh formation mode by activating the magnet sensor once again. The LED next to the profile magnet sensor turns on
green for ½ a second when the sensor is activated..
2.4.2 Magnetic Sensor
The square magnetic sensor can be used to start a communication session with SWIFT Tools. See Section A.3 on page 58 for more information.
2.5 LED Indicators
The two LEDs on the gateway blink in the same pattern to allow the LED to be viewed from any angle. LED patterns are explained in
Appendix D.
2.6 Installing the Gateway
2.6.1 Before Installing
Choose a location for the gateway that is clean, dry , and vibration-free. The area should be readily accessible with suf ficient room to easily install and maintain the gateway. Metal obstructions impede the radio frequency communication and should be avoided. Carefully
unpack the system and inspect for shipping damage if any. All wiring must comply with the national and local codes for fire alarm systems.
WARNING: POLYPROPYLENE ELECTRICAL INSULATION MATERIAL
ENSURE THAT THE POLYPROPYLENE ELECTRICAL INSULATION MATERIAL COVERING THE PRINTED CIRCUIT
BOARD INSIDE THE GATEWAY IS NOT REMOVED OR TAMPERED WHILE INSTALLING OR CLEANING.
2.7.1 Mounting
The gateway has two major pieces, the cover and the mounting plate. The mou nting pla te is mounte d to the wall or c eiling, and f ield wi ring is connected to it. The cover contains the printed circuit board and is fastened to the mounting plate once the wiring is completed.
Mount the mounting plate directly to an electrical box on the ceiling or wall. The plate mounts directly to a 4˝ square (with and without
plaster ring), 4˝ octagon, 3 1/2˝octagon, single gang or double gang junction boxes. If an electrical box is not available, the mounting
plate can be mounted to any flat surface and the wiring can be connected via the knockout points in the mounting plate.
To mount the gateway:
1.Pull the wiring through the opening in the mounting plate.
2.Mount the mounting plate to the junction box or ceiling. See Figure 2.3 below.
3.Connect field wiring to the terminals, as described in Section 2.7.2.
4.Connect necessary jumpers where applicable, as described in Section 2.7.3.
5.To mount the cover, align the locating pins on the cover to the corresponding slots in the mounting plate. See Figure 2.4.
6.Secure the cover by tightening the mounting screws.
Figure 2.6 Wiring Connections: W-GATE Powered by the SLC
SLC out to next device (Class B)
or SLC return to FACP (Class A)
SLC in from FACP/device
jumpers
2.5.wmf
2.7.3 Gateway Powered by the SLC
To power the gateway using the signaling line circuit, connect the gateway as described in the table and graphic below:
Terminal
Pins
A5 and A7 SLC - (Common) & SLC Output +
A5 and A6 SLC - (Common) & SLC Input +
A4 and A5 Jumper selection to enable power from the SLC supply. (Insert Jumper when using SLC power.)
A3Unused
A1 and A2 Jumper selection to enable power from the SLC supply. (Insert Jumper when using SLC power.)
Description
NOTE: Use of the same wire gauge is recommended if there are multiple connections to the same terminal.
The gateway provides isolation of short circuits on the SLC in Class A (Style 6) installations. SLC connections are power-limited by the
panel. An interruption in the SLC that causes a loss of power at the gateway for more than 100ms may result in a trouble condition and
loss of fire protection provided by the wireless devices for approximately 15 minutes. Use of an external +24V power source (not SLC
power) is recommended for installations that require fire protection in the presence of short circuits, including Class A applications and
applications that use isolator modules. Refer to the SLC Wiring Manual for more information on wiring using isolators.
2.7.4 Gateway Powered by an External, Regulated +24VDC Source
To power the gateway using an exter nal, regulated +24VDC source, connect the gateway as described in the table and drawing below.
Terminal PinsDevices Powered
A5 & A7SLC Output
A5 & A6SLC Input
A4Unused
A2 & A3+24VDC input. Voltage range from +18VDC to +30VDC.
W-GATE Wireless GatewayConfiguration and Programming
+
+
-
-
+
-
Figure 2.7 Wiring Connections: W-GATE Powered by an External , Regu la te d +2 4 VDC Sou rc e
SLC in from FACP/device
External +24VDC Power
SLC out to next device (Class B)
or SLC return to FACP (Class A)
2.6.wmf
Figure 2.8 Selecting a Profile
assignprofile_select.jpg
NOTE: It is recommended to use the same wire gauge if there are multiple connections to the same terminal.
The gateway provides isolation of short circuits of the SLC in Class A (Style 6) installations. SLC connections are power-limited by the
panel. +24VDC must be power-limited by the source.
2.8 Configuration and Programming
To successfully configure and/or program the gateway:
1.Create a profile. A profile binds a gateway and the devices in a mesh network together. The profile will contain a mesh ID that is
used when forming the associations. All devices, including the gateway, require a common profile.
2.Assign a profile using SWIFT Tools. Assign the profile to every device that will be a part of the mesh. This will enable all the
devices that have that profile to form associative links when the mesh is formed .
3.Form the mesh. The mesh cannot be formed until the profile is assigned to the gateway and to its devices.
Perform the follow steps using SWIFT Tools.
2.8.1 Assign a Profile
To assign a profile to the gateway using SWIFT Tools:
1.Connect the W -USB device to your lap top. For more information on the W-USB adapter, refer to Section 6, “W-USB Ad apter”, on
page 52.
2.Launch SWIFT Tools. Refer to Appendix A for more information.
3.From the Home Screen, select the Create Mesh Network function.
4.Create a new profile or Import an existing profile as required.
5.Select and open the profile to be assigned to the gateway from the Name drop-down box in the Profile section.
6.Power on the gateway within approximately 20 feet of the laptop running SWIFT Tools.
7.Place the devices with batteries installed within 20 feet of the laptop, with a minimum of 3 feet between each device. If the devices
were inadvertently installed in the building prior to assigning them profiles, either remove them to bring them near the laptop or
bring the laptop near each of the installed devices in order to assign them the profile.
Configuration and ProgrammingW-GATE Wireless Gateway
Figure 2.9 Gateway Selection
communicator_show_4,jpg
Figure 2.10 Assign a Profile
assignprofile_confirm2.jpg
Figure 2.11 Operations Menu
operations.jpg
8.Ensure that the Scan On selection box in the Communicator W indow is checked.
9.Select the gateway from the Communicator Window on the right side of the Tools screen.
10. Click Assign.
The gateway is now included in the list of devices with a profile assigned. The LEDs on the gateway will turn on green for 10 seconds
after the profile has been received.
2.8.2 Remove a Profile
Remove a Profile from a Gateway using SWIFT Tools
1.Connect the W-USB adapter to your laptop. For more information on the W-USB device, refer to Section 6, “W-USB Adapter”, on
page 52.
2.Launch SWIFT Tools. Refer to Appendix A, “SWIFT Tools” for more information on launching the SWIFT Tools application.
3.From the Home Screen, select the Site Sur v ey , Create Mesh Network, or Diagnostics function.
4.Click Operations and select Set device to factory default.
5.The Reset Devices screen appears, displaying the gateway and other devices that have a profile assigned. Click to select the
gateway and click Reset to remove the profile.
W-GATE Wireless GatewayConfiguration and Programming
resetdevices.jpg
Figure 2.12 Reset Devices Screen
meshoptools.png
Figure 2.13 Gateways in Range Table
The profile is removed and the gateway is reset to factory default state. Refer to Section 4.5.3 on page 45 for information on returning
devices to the factory default state.
Remove a Profile from a Gateway without using SWIFT Tools
1.Start with the gateway powered off. The process is performed during start-up.
2.Power on the gateway using SLC power or external +24V. Refer to Sections 2.7.3 and 2.7.4 for more information.
3.Verify the gateway is in the profile modification state. The gateway is in the profile modification state when both the LEDs on the
gateway double blink yellow every second for ten seconds.
4.Activate both magnetic sensors on the gateway within ten seconds of start-up while the double yellow blink is active. If the ten
second window is missed, power down the gateway and repeat the process starting at step 1.
The LEDs on the gateway will blink green every second for five seconds indicating that the profile is removed.
NOTE: If a gateway has been locked using SWIFT Tools, the ability to remove a profile using magnets is no longer available.
2.8.3 Create a Mesh Network
To create a mesh network using the SWIFT Tools, perform the following steps.
1.Connect the W -USB device to your lap top. For more information on the W-USB adapter, refer to Section 6, “W-USB Ad apter”, on
page 52.
2.Launch SWIFT Tools. Refer to Appendix A for more information.
3.From the Home Screen, select the Create Mesh Network function.
4.Proceed to the second step of the Create Mesh Networ k function by clicking the arrow marked Next at the bottom of the screen.
5.Click to select the desired gateway displayed in the Gateways in Range table.
6.The Enter password for Gateway screen is displayed. Enter the password and follow the on-screen instructions. Note that, once
accessed, the login will be valid for only 30 minutes. For additional information, refer to “Lock/Unlock the Gateway” on page 22.
7.Click Start Mesh Formation.
8.A message is displa yed. C lic k Yes to proceed or click No to cancel.
9.The Mesh Formation screen is displayed indicating that the mesh formation is in progress.
Configuration and ProgrammingW-GATE Wireless Gateway
Figure 2.14 Completed Mesh Formation Screen
startmeshformation5.jpg
Figure 2.15 Completed Restructuring Screen
meshrestruct_end.jpg
• The Progress Status column indicates progress status of the selected gateway.
• The No. of Devices Joined column indicates the number of devices that are in the mesh network including the gateway.
• The Total Device Count Expected column indicates the number of devices expected to join including the gateway. This field is
editable. Click in to the field to edit the number of device count expected.
10. Once the expected count of devices have joined the mesh, a message is disp laye d to show that the Mesh formation is complete and
an option is given to choose to start mesh restructuring immediately or wait for any other devices to join.
11. Start Mesh Restructuring (by either waiting or clicking Start). Once Restructuring is initiated, the progress displays. When Mesh
Restructuring is complete, the following success message is shown. For further operating instructions, refer to Section 2.9,
“Operations”.
2.8.4 SLC Configuration
The gateway:
communicates with the control panel via the SLC.
is a LiteSpeed-only device.
does not support CLIP mode.
requires the use of an ANN-80-W for event details because FACPs have limited support for displaying all troubles from the
wireless device. Refer to the appropriate section below for configuration steps. (This does not apply to the ES-50X or ES-200X
Series panels.)
is only compatible with Gateway firmware version 2.1 or higher.
The gateway requires three consecutive SLC addresses for all FACPs except the ES Series, which requires only the one base address. Set
the base address using the rotary dials on the gateway prior to installa tion. Ensure the address and the next two addresses on the SLC
loop are available.
The base address uses the following configuration parameters:
•Module Type: Monitor Module
•Type Code Label:Wireless Gateway (for ES Series panels: Wireless = True)
The gateway does not cause any alarms at this address, but the SLC point is used for supervision of the gateway.
The base address +1 (not required with ES Series panels) uses the following configuration parameters:
•Module Type: Monitor Module
•Type Code Label:
Tamper
This address is a latching supervisory condition that goes active whenever a wireless detector in the mesh is removed from its base or a
module has its cover plate removed (tamper). This SLC point does not show the address of the tampered device. The ANN-80-W displays the device address information. The latching condition is cleared with a reset on the ANN-80-W.
The base address +2 (not required with ES Series panels) uses the following configuration parameters:
•Module Type: Monitor Module
•Type Code Label:
Trouble
This address is a latching or non-latching trouble condition, depending on the trouble event, that goes active whenever a wireless device
in the mesh is in a trouble condition. Refer to Section 3.10.3, “Event Messages”, on page 40 for the message displayed at the ANN-80-W
for the trouble event. Latching troubles are cleared with a reset on the ANN-80-W.
The specific address and trouble condition is displayed on the ANN-80-W.
NOTE: When a wireless relay, wireless AV base, or wireless sync module is in use, module device count must be limited to 99 modules
per loop. This includes wired and wireless modules that are on the same loop. The module address range must be within 1-99.
2.9 Operations
2.9.1 Modes of Operation
Start-up Mode
Start-up mode is a temporary mode of operation. During start-up mode a profile can be created or removed. The start-up period lasts for
10 seconds. If a particular unit contains a profile, the LEDs double blink yellow every second. If the unit does not contain a profile, the
LEDs double blink red every second.
During start-up, the gateway does not provide fire protection nor does it respond to the FACP. All the three SLC addresses will be an
INVALID RE PLY.
After start-up, the gateway proceeds to the factory default mode if no profile exists. In the presence of a profile, the gateway will proceed to mesh formation mode if it was previously part of a mesh network or normal mode if it was not previously part of a mesh network.
Factory Default Mode
Factory default mode is the initial mode of the gateway. In this mode, the gateway and peripheral devices do not provide any fire protection. The gateway does not communicate with wireless detectors or modules in factory default mode. The only wireless communication
in factory default mode is between the gateway and SWIFT Tools. SW IFT Tools must be within 20 feet of the gateway for proper communication. The gateway must be assigned a profile before continuing configuration.
The gateway reports “Factory Default” to the communicator display of SWIFT Tools.
The gateway’s base address will be normal and the supervisory point (base address + 1) will also be normal. The trouble point (base
address + 2) will indicate an open circuit.
Transitions back to Factory Default mode are not shown in the above diagram. However, any time the profile is removed from the gate-
way, it will return to Factory Default mode.
Profile Configured
The gateway enters the profile configured mode once a profile is assigned by SWIFT Tools. Profile configured mode is a temporary
mode before the gateway transitions to mesh formation or normal mode.
Mesh Formation
The gateway must have a profile before entering mesh formation mode. The gateway and the peripheral devices do not provide any fire
protection in this mode. The gateway enters mesh formation mode:
after creating a profile using the mesh formation sensor.
after activating the mesh formation sensor with a magnet when the gateway contains a profile.
automatically after start-up when the gateway was previously part of a mesh.
by a command from the SWIFT Tools application.
A gateway in mesh formation mode instructs all devices in the mesh to also transition to mesh format ion mode. The gateway and all
communicating devices search for new or lost devices with the same profile to join the network.
If the gateway automatically entered mesh formation after start-up, mesh formation will terminate 10 minutes after the last device has
joined or after all existing devices are recovered. If new devices are found or if mesh formation was initiated by the user, then mesh formation terminates after a period of 10 minutes without any new devices joining the mesh. At any point Mesh formation can be terminated by user interaction by activating the magnet sensor again or by using the SWIFT Tools application.
The gateway reports “Mesh Formation” to the communicator display of the SWIFT Tools application.
The gateway’s base address will be normal and the supervisory point (base address + 1) will also be normal. The trouble point (base
address + 2) will indicate an open circuit.
Initial Mesh Restructuring Mode
Initial mesh restructuring mode automatically runs after each mesh formation. The gateway and peripheral devices do not provide fire
protection during the initial mesh restructuring mode. Mesh restructuring analyzes signal strengths between devices. The gateway designates the primary and secondary communication paths between devices that provide a redundant path for all transmissions. Mesh
restructuring automatically terminates once all devices have a redundant communication path and signal strengths that meet the requirements of primary and secondary transmission paths. Any device that does not have a redundant path or meet the requirements for signal
strength will report a fault.
The gateway reports “Restructuring” to the communicator display of the SWIFT Tools application.
The gateway’s base address will be normal and the supervisory point (base address + 1) will also be normal. The trouble point (base
address + 2) will indicate an open circuit.
Normal Mode
Normal mode is the network’s standard operating state. The mesh network has been formed and is providing fire protection. The mesh
network will continuously search for additional devices with a matching profile to join the mesh. To avoid interference, the mesh network periodically checks for adjacent mesh networks created by Honeywell. The gateway reports “Normal” to the communicator display
of the SWIFT Tools application.
Rescue Mode
During normal mode, if an out-of-network device with a matching profile is discovered by the network, the gateway will trigger rescue
mode in all communicating devices. All devices in communication continue to provide fire protection during rescue mode but also
search for a lost or added device. Rescue mode automatic ally terminates 3 minutes after the last device is rescued and returns to normal
mode. The gateway does not report troubles during rescue mode but reports “Rescue” to the communicator display of the SWIFT Tools
application.
In addition to the initial mesh restructuring mode, mesh restructuring i s automati cally perform ed after any restoration of comm unication
to a device or to recover from a link failure (Class A fault). Mesh restructuring that occurs during normal mode does not generate a trouble message. During mesh restructuring, fire pro tection is provi ded by all devices that are participating in the mesh communication. The
gateway reports “Restructuring” to the communicator display of the SWIFT Tools application.
Bootloader Mode
The gateway enters the bootloader mode when its firmware is being updated using SWIFT Tools. The gateway does not communicate
with the F ACP during bootloader mode. The gateway reports “Bootloader” to th e communi cator dis play of the SWIFT Tools application.
Mesh Upgrade
Starting with version 3.0, firmware updates for the wireless mesh devices (detectors, monitor module, relay, etc.) can be broadcast over
the mesh network. Fire protection will not be provided during the upgrade process.
SWIFT tools will be used to initiate and monitor the upgrade process. During the upgrade process each device in the mesh will appear as
a no answer or invalid reply. Refer to Section E.4 on page 76 for more information on the mesh upgrade process.
Neighboring Network Scan
A Mesh network will identif y adja cent mesh networks for the purpose of avoiding communication collisions and for time synchronization to ensure end-to-end latency compliance. Fire protection will be provided during a neighboring network scan by all devices that are
participating in the mesh communication. The gateway reports “Neighboring Scan” to the communicator display of the SWIFT Tools
application.
2.9.2 LED Patterns
The LED indicator patterns are provided in Appendix D on page 67.
2.9.3 Lock/Unlock the Gateway
The gateway can be locked to prevent access to the magnetic sensors and to password-protect all wireless interactions. The lock function
can be performed by SWIFT Tools. When SWIFT Tools is used to lock the gateway, a password must be provided for all future interactions, including unlocking the gateway. If the gateway was previously loc ked with a password from SWIFT Tools, the previous password will be applied. Use this password for all future interactions with the SWIFT Tools application.
Lock/Unlock the Gateway Using SWIFT Tools
To lock/unlock the gateway:
1.Connect the W-USB device to your computer. For more information on the W-USB adapter, refer to Section 6.
2.Launch the SWIFT T ools applicati on. Refer to AppendixA, “SWIFT Tools” for more information.
3.From the Home Screen, select the Site Sur v ey , Create Mesh Network, or Diagnostics function.
4.Click Operations. The following screen is displayed.
5.Select Gateway Operations to lock/unlock the gateway. The Lock/Unlock Gateway screen displays the list of gateway/gateways
that are in the range of the W-USB adapter connected to your /Laptop.
6.Select desired gateway and click Lock or Unlock as required.
1.Click Lock. The Gateway Password screen is displayed.
2.Enter the verification password in the Verification Password field and click OK.
3.A Hall Sensor Activation window displays. The LED on the gateway blinks yellow indicating the gateway is waiting for
hall sensor activation.
4.Place a magnet on either of the gateway sensors within 120 seconds.
5.The LED blinks normal upon hall sensor activation. The gateway is locked and a confirmatory message is displayed.
• To unlock the gateway
1.Click Unlock. The Gateway Password screen is displayed.
2.Enter the verification password in the Verification Password field and click OK.
3.A Hall Sensor Activation window displays. On hall sensor activation, the LED on the gateway blinks yellow.
4.Place a magnet on either of the gateway sensors within 120 seconds.
5.The LED blinks normal upon hall sensor activation. The gateway is unlocked and a confirmatory message is displayed.
Password Reset
To reset the password, contact technical support.
2.9.4 Enable/Disable Max Gateway Trouble Reporting
This feature is used to determine if the permitted number of Honeywell SWIFT systems that can co-exist in range of each other without
reducing overall performance has been exceeded. The default setting is On (enabled).
Completed Wireless Network
Turning off the MAX GATEWAY trouble reporting in this case prevents subsequent installation attempts from causing a trouble on a
properly installed and commissioned system. When the wireless installation is completed and there are no possibilities of overlapping
systems, turn off MAX GATEWAY trouble reporting when all three of the following conditions are true:
1.The entire fire system installation has been com p leted.
2.There is no MAX GATEWAY trouble indication present in the completed system.
3.The system has been inspected, tested, and approved by the authority having jurisdiction.
Possible Wireless Mesh Overlap
Generally, only four SWIFT wireless mesh gateways, along wi th their associated devices, are permitted to be installed within an overlapping wireless region. The MAX GATEWAY trouble is generated when a fifth gateway mesh is detected and the maximum limit is
exceeded. When there is a MAX GATEWAY trouble present in the system, it is permit ted to turn of f MAX GATEWAY trouble reporting
after completing the following evaluation method with successful results. For the result to be successful, the signal strength between
devices in any one mesh must be at least 20 dB stronger than the signals seen from another mesh. If the 20 dB requirement is not met, or
if the evaluation cannot be performed due to access restrictions, the number of overlapping mesh systems must be reduced to four to
ensure the wireless system performs according to UL requirements. This could mean that additio nal mesh systems c annot be instal led in
the area.
Figure 2.21 Perform a Link Test with the Fifth Mesh
Mesh #1
Mesh #2
Mesh #5
Mesh #4
Mesh #3
NOTE: Signal strength is represented using negative numbers. So, 30 is 20 dB stronger than 50. Refer for Figure 2.23 for an example.
Evaluation Process
1.Locate all the SWIFT wireless mesh systems in the area. Access to all mesh gateways in the area and to the closest edge devices
between overlapping meshes is required and the SLC addresses of the edge devices must be known. The edge devices that must be
accessible are located at the ends of the dotted lines represented in Figures 2.21 and Figure 2.24. If location of devices or access to
them is not possible, the addition of a fifth wireless mesh is not permitted in this area.
2.Identify the devices on the edge of each mesh.
3.Find the closest edge device from each mesh to the closest edge of the new mesh. Except as noted in Figure 2.25, four pairs of
devices should be identified given there are five overlapping meshes in the area.
4.Perform a link test between each of the four device locations (Mesh 1 to Mesh 5, Mesh 2 to Mesh 5, Mesh 3 to Mesh 5, and Mesh 4
to Mesh 5) using a separate pair of test devices. Refer to Appendix B, “Site Survey” for instructions on how to perform a site
survey. Use SWIFT Tools to identify the signal strength/link quality for each of the four link tests and record these values.