Honeywell WFSPS Wireless Pull Station User Manual SWIFT
Honeywell International Inc. Wireless Pull Station SWIFT
Exhibit D Users Manual per 2 1033 b3
| Download: |  |
| Mirror Download [FCC.gov] | |
| Document ID | 3767407 |
| Application ID | Hurd4Hqa12RKNJjkJcu3wQ== |
| Document Description | Exhibit D Users Manual per 2 1033 b3 |
| Short Term Confidential | No |
| Permanent Confidential | No |
| Supercede | No |
| Document Type | User Manual |
| Display Format | Adobe Acrobat PDF - pdf |
| Filesize | 365.67kB (4570894 bits) |
| Date Submitted | 2018-03-02 00:00:00 |
| Date Available | 2018-08-01 00:00:00 |
| Creation Date | 2017-11-09 09:18:18 |
| Producing Software | Acrobat Distiller 17.0 (Windows) |
| Document Lastmod | 2017-11-09 09:48:30 |
| Document Title | SWIFT.book |
| Document Creator | FrameMaker 2017 |
| Document Author: | e654944 |
Farenhyt™ Series SWIFT® Smart Wireless Integrated Fire Technology Instruction Manual Document LS10036-000FH-E Rev: B 11/9/2017 ECN: 17-408 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 developing 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.systemsensor.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 or 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 detectors are located. • Smoke particles may be blown away from detectors by air outlets, such as air conditioning vents. • Smoke particles may be drawn into air returns before reaching the detector. The amount of “smoke” present may be insufficient 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 unpredictable 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 installed 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 detectors 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 messaging systems must be designed to meet 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 that certain people, even when they hear a fire alarm signal, do not respond to or comprehend the meaning of the signal. Audible devices, such as horns and bells, 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 electrical 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 compatible with the control panel. It is essential to use only equipment listed 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, backup 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, ongoing 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 agreement should be arranged through the local manufacturer's representative. Maintenance should be scheduled as required by National and/or local fire codes and should be performed by authorized professional life safety system installers only. Adequate written records of all inspections should be kept. Limit-D2-2016 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Installation Precautions 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 operation, 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 affected by a change must be 100% tested. In addition, to ensure that other operations are not inadvertently affected, at least 10% of initiating devices that are not 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 (noncondensing) 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 immune from lightning transients and interference, proper grounding will reduce susceptibility. Overhead or outside aerial wiring is not recommended, due to an increased susceptibility to nearby lightning strikes. Consult with the Technical Services 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, transformer, 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. 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-D1-9-2005 FCC Warning WARNING: This equipment generates, uses, and can radiate 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 found 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. Farenhyt™ is a trademark; and eVance®, Honeywell®, Silent Knight® 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 registered trademark of The Mozilla Foundation. ©2017 by Honeywell International Inc. All rights reserved. Unauthorized use of this document is strictly prohibited. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Software Downloads 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 Topic 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. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Table of Contents Section 1: Overview .......................................................................................................................................................... 8 1.1: Purpose ..............................................................................................................................................................................................................8 1.2: Assumed Knowledge .........................................................................................................................................................................................8 1.3: Additional References........................................................................................................................................................................................8 1.4: About the Mesh Network...................................................................................................................................................................................8 1.5: Abbreviations .....................................................................................................................................................................................................9 Section 2: WIDP-WGI Wireless System Gateway ......................................................................................................... 10 2.1: Description.......................................................................................................................................................................................................10 2.2: Agency Approvals............................................................................................................................................................................................10 2.2.1: FCC.......................................................................................................................................................................................................10 2.2.2: Federal Institute of Telecommunications .............................................................................................................................................10 2.3: Specifications...................................................................................................................................................................................................10 2.3.1: Environmental Specifications...............................................................................................................................................................11 2.4: Magnet Sensors................................................................................................................................................................................................11 2.4.1: Profile Magnetic Sensor .......................................................................................................................................................................11 2.4.2: Mesh Formation Magnetic Sensor........................................................................................................................................................11 2.5: LED Indicators.................................................................................................................................................................................................11 2.6: Installing the Gateway .....................................................................................................................................................................................11 2.6.1: Before Installing ...................................................................................................................................................................................11 2.7: Mounting and Wiring.......................................................................................................................................................................................12 2.7.1: Mounting...............................................................................................................................................................................................12 2.7.2: Wiring ...................................................................................................................................................................................................13 2.7.3: Gateway Powered by the SLC..............................................................................................................................................................14 2.7.4: Gateway Powered by an External, Regulated +24VDC Source...........................................................................................................14 2.8: Configuration and Programming .....................................................................................................................................................................15 2.8.1: Configuration and Programming Without Using SWIFT Tools ..........................................................................................................15 Create a New Profile...............................................................................................................................................................................15 Assign a Previously Created Profile Using a Distributor .......................................................................................................................16 Remove a Profile ....................................................................................................................................................................................16 Create a Mesh Network ..........................................................................................................................................................................16 2.8.2: Configuration and Programming Using SWIFT Tools ........................................................................................................................16 Assign a Profile.......................................................................................................................................................................................16 Remove a Profile ....................................................................................................................................................................................17 Create a Mesh Network ..........................................................................................................................................................................18 2.8.3: Profile Distribution ...............................................................................................................................................................................18 After Creating a Profile...........................................................................................................................................................................18 Activating the Profile Magnetic Sensor..................................................................................................................................................19 2.8.4: SLC Configuration................................................................................................................................................................................19 2.9: Operations........................................................................................................................................................................................................19 2.9.1: Modes of Operation ..............................................................................................................................................................................19 Start-up Mode .........................................................................................................................................................................................19 Factory Default Mode.............................................................................................................................................................................20 Profile Configured ..................................................................................................................................................................................20 Mesh Formation ......................................................................................................................................................................................20 Initial Mesh Restructuring Mode ............................................................................................................................................................20 Normal Mode..........................................................................................................................................................................................20 Rescue Mode...........................................................................................................................................................................................20 Mesh Restructuring Mode ......................................................................................................................................................................20 Bootloader Mode ....................................................................................................................................................................................21 Mesh Upgrade.........................................................................................................................................................................................21 Neighboring Network Scan ....................................................................................................................................................................21 2.9.2: LED Patterns.........................................................................................................................................................................................21 2.9.3: Lock/Unlock the Gateway ....................................................................................................................................................................21 Lock/Unlock the Gateway Using SWIFT Tools.....................................................................................................................................21 Password Reset .......................................................................................................................................................................................22 2.9.4: Weak Link Trouble Reporting..............................................................................................................................................................22 Disable Trouble Reporting at the Gateway Using SWIFT Tools ...........................................................................................................22 2.9.5: Collapse Network Command................................................................................................................................................................22 Collapse Mesh Network Using SWIFT Tools........................................................................................................................................23 2.9.6: Silence Network Command..................................................................................................................................................................23 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Table of Contents Silence Mesh Network Using SWIFT Tools ..........................................................................................................................................23 2.9.7: Multiple Wireless Sensor Network Installation Restrictions................................................................................................................24 2.9.8: Multiple Wireless Sensor Network Synchronization ...........................................................................................................................24 Trouble Reporting for Multiple Mesh Synchronization .........................................................................................................................24 Verification of Synchronization..............................................................................................................................................................25 Disable Synchronization Fault reporting ................................................................................................................................................26 2.9.9: Avoiding RF Interference .....................................................................................................................................................................26 2.9.10: Trouble MessagesDistributed Firmware Updates ..............................................................................................................................27 ................................................................................................................................................................................................................28 Section 3: Wireless Devices ........................................................................................................................................... 29 3.1: Description.......................................................................................................................................................................................................29 3.2: Agency Approvals............................................................................................................................................................................................30 3.2.1: FCC.......................................................................................................................................................................................................30 3.2.2: Federal Institute of Telecommunications .............................................................................................................................................30 3.3: Specifications...................................................................................................................................................................................................30 3.4: Installing, Mounting, and Wiring Devices.......................................................................................................................................................30 3.5: Configuration and Programming .....................................................................................................................................................................31 3.5.1: Assigning Profiles.................................................................................................................................................................................31 Assigning a Profile to a Device (Detector or Module) Using a Gateway or Distributor........................................................................31 Assigning a Profile Using SWIFT Tools................................................................................................................................................32 3.5.2: Distributor Mode ..................................................................................................................................................................................33 Converting a Device into a Distributor...................................................................................................................................................33 Converting a Distributor Back into a Device..........................................................................................................................................33 3.5.3: Mesh Formation....................................................................................................................................................................................33 Repeater ..................................................................................................................................................................................................33 3.5.4: Restoring a Device to Factory Default .................................................................................................................................................33 Removing Profiles Without Using SWIFT Tools...................................................................................................................................33 Removing a Profile Using SWIFT Tools ...............................................................................................................................................34 3.6: Device Operations ...........................................................................................................................................................................................35 3.6.1: Modes of Operation ..............................................................................................................................................................................35 Factory Default Mode.............................................................................................................................................................................35 Site Survey Mode....................................................................................................................................................................................35 Profile Assigned Mode ...........................................................................................................................................................................35 Bootloader Mode ....................................................................................................................................................................................35 Distributor Mode.....................................................................................................................................................................................35 Mesh Participant Modes .........................................................................................................................................................................35 3.6.2: LED Indicators......................................................................................................................................................................................36 3.6.3: Trouble Conditions ...............................................................................................................................................................................36 Trouble Conditions with Fire Protection ................................................................................................................................................36 Trouble States without Fire Protection ...................................................................................................................................................36 Section 4: W-SYNC Wireless Synchronization Module ............................................................................................... 38 4.1: Description.......................................................................................................................................................................................................38 4.2: Wiring ..............................................................................................................................................................................................................38 4.2.1: FACP ....................................................................................................................................................................................................38 4.2.2: HPFF8/HPFF12 ....................................................................................................................................................................................39 Section 5: USB Adapter .................................................................................................................................................. 40 5.1: Introduction......................................................................................................................................................................................................40 5.2: Agency Approvals...........................................................................................................................................................................................40 5.2.1: FCC.......................................................................................................................................................................................................40 5.2.2: Federal Institute of Telecommunications .............................................................................................................................................40 5.3: Specifications...................................................................................................................................................................................................40 5.3.1: Electrical Specifications .......................................................................................................................................................................40 5.3.2: Serial Communication Specification ....................................................................................................................................................40 5.3.3: Mechanical Specifications ....................................................................................................................................................................40 5.3.4: Environmental Specifications...............................................................................................................................................................41 5.4: Driver Installation............................................................................................................................................................................................41 Appendix A: SWIFT Tools............................................................................................................................................... 44 A.1: Description......................................................................................................................................................................................................44 A.2: Launching SWIFT Tools.................................................................................................................................................................................44 A.2.1: Creating a New Jobsite ........................................................................................................................................................................45 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Table of Contents A.2.2: Opening an Existing Jobsite ................................................................................................................................................................45 Appendix B: Site Survey................................................................................................................................................. 47 B.1: Conduct a Site Survey.....................................................................................................................................................................................47 B.1.1: Link Quality Test .................................................................................................................................................................................47 Basic Requirements of a Link Quality Test............................................................................................................................................47 Conduct a Link Quality Test...................................................................................................................................................................47 Results of a Link Quality Test ................................................................................................................................................................48 After a Link Quality Test........................................................................................................................................................................48 B.1.2: RF Scan Test ........................................................................................................................................................................................48 Conduct an RF Scan Test........................................................................................................................................................................48 Status of an RF Scan Test .......................................................................................................................................................................48 B.1.3: Retrieving Site Survey Results ............................................................................................................................................................49 Appendix C: Troubleshooting and Testing................................................................................................................... 51 C.1: Troubleshooting ..............................................................................................................................................................................................51 C.2: Testing the Gateway and Devices ...................................................................................................................................................................52 C.2.1: Testing LED Indicators........................................................................................................................................................................52 C.3: Testing the Wireless Network .........................................................................................................................................................................52 C.3.1: Network Topology ...............................................................................................................................................................................53 Parent-Child Devices ..............................................................................................................................................................................53 Orphan Devices.......................................................................................................................................................................................53 Class A Compliance................................................................................................................................................................................53 C.3.2: History Events......................................................................................................................................................................................53 C.3.3: Network Snapshots ..............................................................................................................................................................................53 C.3.4: Network Statistics ................................................................................................................................................................................53 C.3.5: Device Attributes .................................................................................................................................................................................53 Appendix D: LED Indicators ........................................................................................................................................... 55 Appendix E: Firmware Upgrade/Downgrade Instructions........................................................................................... 59 E.1: W-USB Adapter Upgrade Procedure...............................................................................................................................................................59 E.2: Gateway Firmware Upgrade/Downgrade Procedure ......................................................................................................................................59 E.3: Device Firmware Upgrade/Downgrade Procedure .........................................................................................................................................60 Index ................................................................................................................................................................................. 61 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Section 1: Overview 1.1 Purpose 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 • Testing, maintenance, and firmware upgrade information of the Wireless Gateway 1.2 Assumed Knowledge This document is created with the assumption that all users 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. IFP-2100/ECS Fire Alarm Control Panel LS10143-001SK-E IFP-300/ECS Fire Alarm Control Panel LS10145-001SK-E IFP-75 Fire Alarm Control Panel LS10147-001SK-E WIDP-PHOTO Wireless Photo Detector I56-4273 WIDP-ACCLIMATE Wireless Acclimate Detector I56-4273 WIDP-HEAT-ROR Wireless Rate Of Rise Heat Detector I56-4274 WIDP-HEAT Wireless Fixed Heat Detector I56-4274 WIDP-MONITOR Wireless Monitor Module I56-4275 WIDP-RELAY Wireless Relay Module I56-4276 WIDP-PULL-DA Wireless Pullstation I56-6562 B210W Wireless Detector Base I56-4064 WAV-RL Red Wall AV Base I56-6517 WAV-WL White Wall AV Base I56-6517 WAV-CRL Red Ceiling AV Base I56-6517 WAV-CWL White Ceiling AV Base I56-6517 W-SYNC Wireless Sync Module I56-6518 MDL3 Sync Module I56-3157 HPFF8 NAC Expander 53499 HPFF12 NAC Expander 53576 1.4 About the Mesh Network 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. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Abbreviations Overview 1.5 Abbreviations The following table lists the abbreviations and their definitions used in this manual. Abbreviation Definition AHJ Authority Having Jurisdiction ANSI American National Standards Institute dBm Units of RF power (0dBm = 1mW) FACP Fire Alarm Control Panel FCC Federal Communications Commission ISM Band Industrial, Scientific and Medical Radio Bands LCD Liquid Crystal Display LED Light Emitting Diode mA Milliampere MHz Megahertz NFPA National Fire Protection Association PC Personal Computer RF Radio Frequency SLC Signaling Line Circuit UI User Interface UL Underwriters Laboratories WIDP-WGI Wireless Gateway SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Section 2: WIDP-WGI Wireless System Gateway 2.1 Description The WIDP-WGI is a device in a wireless fire system that acts as a bridge between fire alarm 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 gateway is powered by either the SLC loop or by any external +24VDC UL listed power supply. The gateway uses the IDP 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. FACP wireless mesh network SLC wired SLC devices WIDP-WGI Gateway SWIFT Tools USB adapter Figure 2.1 SWIFT Network 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 MODIFICATIONS NOT EXPRESSLY APPROVED 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. Specifications Data External Supply Electrical Ratings 18V-30V SLC Electrical Ratings 15V-30V Maximum current when using the external supply 40mA Maximum current when using the SLC power supply 24mA Maximum SLC Resistance 50Ω Minimum signal strength level needed at the receiver for a primary path with weak -55dBm link trouble reporting enabled. 10 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Magnet Sensors WIDP-WGI Wireless System Gateway Minimum signal strength level needed at the receiver for a secondary path or primary path with weak link trouble reporting disabled. Must be 18 dBm higher than the noise floor down to a minimum of -80dBm1 Maximum ambient noise level -85dBm1 Maximum RF Power Output +17dBm (Tx power level without antenna) Radio Frequency Lower ISM Band (902 - 928MHz). Ensure that the primary path signal strength level is within recommended guidelines to assure proper communication in the mesh network. 2.3.1 Environmental Specifications System Operating Temperature StorageTemperature Humidity Gateway 0°C-49°C / 32°F-120°F -10°C- 60°C / 14°F-140°F 10 to 93% RH, Non-condensing 2.4 Magnet Sensors 2.4.1 Profile Magnetic Sensor The profile magnetic sensor (refer to Figure 2.2) is used to create a unique profile upon start-up. It can also be used to start profile distribution for a gateway that contains a profile. The LED next to the profile magnet sensor turns on green for ½ a second when the sensor is activated. 2.4.2 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. The Mesh formation magnetic sensor can also be used to create a profile on start-up for a gateway that does not already contain a profile. Mesh Formation Magnetic Sensor Profile Magnetic Sensor cover.wmf LEDs Figure 2.2 LEDs and Magnetic Sensors on the WIDP-WGI 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 sufficient 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. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 11 WIDP-WGI Wireless System Gateway Mounting and Wiring 2.7 Mounting and Wiring WARNING: FORMEX SHEET ENSURE THAT THE FORMEX SHEET 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 mounting plate is mounted to the wall or ceiling, and field wiring 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. 2.2.wmf locating pin locating pin locating pin Figure 2.3 Mounting Plate for Wireless Gateway 12 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Mounting and Wiring WIDP-WGI Wireless System Gateway locating pin 2.3.wmf locating pin locating pin Figure 2.4 Attaching Cover to Mounting Plate 2.7.2 Wiring • All wiring must be installed in compliance with the National Electrical Code and the local codes having jurisdiction. • 12-18 AWG is recommended. For wiring connections: 1. Strip about 3/8” of insulation from the end of the wire. 2. Slide the stripped end of the wire under the appropriate terminal and tighten the screw. A7 - SLC Out+/In+ A6 - SLC In+/Out + A5 - SLC- (Common) A4 - SLC Power Select 2 A3 - Power +24VDC A2 - Power Ground 2.4.wmf NOTE: Do not loop the wire under the screw terminals. A1 - SLC Power Select 1 Figure 2.5 WIDP-WGI Mounting Plate - Terminal Layout SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 13 WIDP-WGI Wireless System Gateway Mounting and Wiring 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 Description 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.) Unused Jumper selection to enable power from the SLC supply. (Insert Jumper when using SLC power.) SLC out to next device (Class B) or SLC return to FACP (Class A) SLC in from FACP/device +- 2.5.wmf A3 A1 and A2 jumpers Figure 2.6 Wiring Connections: WIDP-WGI Powered by the SLC 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. 2.7.4 Gateway Powered by an External, Regulated +24VDC Source To power the gateway using an external, regulated +24VDC source, connect the gateway as described in the table and drawing below. Terminal Pins SLC Output A5 & A6 SLC Input A4 A2 & A3 A1 14 Devices Powered A5 & A7 Unused +24VDC input. Voltage range from +18VDC to +30VDC. Use only power-limited device circuits. Unused SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Configuration and Programming WIDP-WGI Wireless System Gateway ++ External +24VDC Power SLC in from FACP/device 2.6.wmf SLC out to next device (Class B) or SLC return to FACP (Class A) Figure 2.7 Wiring Connections: WIDP-WGI Powered by an External, Regulated +24VDC Source 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. Distribute the profile. Distribute 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 distributed to its devices. These steps may be performed with or without using SWIFT Tools. 2.8.1 Configuration and Programming Without Using SWIFT Tools This section explains the configuration of the gateway using only a magnet and a screw driver. For configuration instructions using SWIFT Tools, refer to Section 2.8.2. There are two ways to provide a gateway with a profile without using SWIFT Tools. Create a new profile using the gateway. Assign a previously created profile to the gateway using a distributor. Create a New Profile To create a unique profile in the gateway without using SWIFT Tools: 1. Start with the gateway powered off. The profile creation 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. Ensure that the gateway is in the factory default state. If the gateway is in the factory default state, both the LEDs on the gateway will double blink red every second for ten seconds. If the LEDs are yellow, refer to “Remove a Profile” on page 16. 4. Activate either magnetic sensor with a magnet within ten seconds of starting up the gateway while the double red blink is active on the gateway. Refer to Section 2.4, “Magnet Sensors” for further information on activating magnetic sensors. The LED next to the magnetic sensor emits a red light for one second when it is activated. If the ten second window is missed, power down the gateway and repeat the process starting at step 1. A profile has been created successfully; the LEDs on the gateway will light green and stay on steady for ten seconds. The profile has been created containing a mesh ID and a default password. The default password is ‘12345678’ and is needed if the gateway is locked by the FACP and later accessed by SWIFT Tools. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 15 WIDP-WGI Wireless System Gateway Configuration and Programming Assign a Previously Created Profile Using a Distributor Instead of creating a new profile, an existing profile can be distributed by a device with an existing profile. To distribute the existing profile: 1. Ensure that the gateway or other mesh device with the profile is set for distribution. Refer to Section 2.8.3, “Profile Distribution” or Section 3.5.2, “Distributor Mode”. 2. Bring the profile distributor within 20 feet of the gateway. 3. 10 seconds after the initial start-up, the LEDs on the gateway switch from a double red blink to a single red blink. The single red blink indicated the gateway is ready. 4. Use a magnet to activate either of the magnetic sensors. The LED will blink a single red every half-second indicating that it is searching for a profile. When the profile is successfully received from the distributor, the LEDs on the gateway will turn on green steady for five seconds. Remove a Profile To remove a profile from a gateway: 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. Create a Mesh Network The gateway communicates with all devices in range that have a common profile and establishes communication links with all the devices. This creates a mesh network. Once a device joins the mesh, that device acts as a repeater for devices out of the range of the gateway. All devices must be in their final mounting locations prior to initiating the mesh formation. The mesh formation is initiated by the gateway upon user activation and terminated by the gateway when all possible devices join the network or when terminated by the user. To form a mesh network, ensure that the gateway is powered on and contains a profile. (Refer to Section 2.5 on page 11 for information on how the gateway indicates its status). Activate the “Mesh Formation” magnet sensor on the gateway. Refer to Figure 2.2 for sensor location. The gateway will then transition to the mesh formation mode and establish communication with all the devices containing a common profile. The blink pattern on the gateway indicates that it is in mesh formation mode. At this stage, both the LEDs on the gateway will blink twice every 7 seconds. • The first blink is green and the second blink is red when the gateway is acting as a profile distributor and forming the mesh. • The first blink is green and the second blink is yellow when the gateway is only forming the mesh. Mesh formation typically takes one minute for each device in the mesh. Mesh formation automatically terminates 10 minutes after the last device joins the mesh. Mesh formation can be terminated manually by the user by again activating the mesh formation magnetic sensor. Once the mesh formation is complete, the network automatically transitions to restructure the mesh. For operating instructions, refer to Section 2.9, “Operations”. 2.8.2 Configuration and Programming Using SWIFT Tools Assign a Profile assignprofile_select.jpg To assign a profile to the gateway using SWIFT Tools: 1. Connect the W-USB adapter device to your laptop. For more information on the USB adapter, refer to Section 5, “USB Adapter”, on page 40. 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. Figure 2.8 Selecting a Profile 16 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Configuration and Programming Power on the gateway within approximately 20 feet of the laptop running SWIFT Tools. Ensure that the Scan On selection box in the Communicator Window is checked. Select the gateway from the Communicator Window on the right side of the Tools screen. communicator_show_4,jpg 6. 7. 8. WIDP-WGI Wireless System Gateway Figure 2.9 Gateway Selection Click Assign. assignprofile_III.png 9. Figure 2.10 Assign a Profile 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. Remove a Profile To remove a profile from a gateway using the SWIFT Tools application: 1. Connect the W-USB adapter to your laptop. For more information on the USB adapter, refer to Section 5, “USB Adapter”, on page 40. 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 Survey, Create Mesh Network, or Diagnostics function. 4. Click Operations and select Set device to factory default. Figure 2.11 Operations Menu 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 Device to remove the profile. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 17 Configuration and Programming resetdevices.jpg WIDP-WGI Wireless System Gateway Figure 2.12 Reset Devices Screen The profile is removed and the gateway is reset to factory default state. Create a Mesh Network meshoptools.png To create a mesh network using the SWIFT Tools, perform the following steps. 1. Connect the W-USB adapter to your laptop. For more information on the USB adapter, refer to Section 5, “USB Adapter”, on page 40. 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 Network function by clicking the arrow marked Next at the top of the screen. 5. Click to select the desired gateway displayed in the Gateways in Range table and then click Start Mesh Formation. Figure 2.13 Gateways in Range Table While the mesh is formed, SWIFT Tools helps track the number of devices that have joined the mesh and view the progress. Mesh formation terminates 10 minutes after the last device joins the mesh. In addition, mesh formation can be manually terminated by clicking the Start Mesh Restructuring button. Once mesh formation is complete, the network automatically transitions to restructure the mesh. For further operating instructions, refer to Section 2.9, “Operations”. 2.8.3 Profile Distribution There are two ways to initiate profile distribution from the gateway. • Automatically after creating a profile if the profile was not created by SWIFT Tools • Activating the profile-creating magnetic sensor when the gateway has a profile. After Creating a Profile Profile distribution is automatically enabled from the gateway after creating a profile using either magnetic sensor upon the gateway’s start-up. The profile distribution automatically terminates after 10 minutes. 18 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Operations WIDP-WGI Wireless System Gateway Activating the Profile Magnetic Sensor Activating the profile magnetic sensor (refer to Figure 2.2) when the gateway has a profile will put the gateway in a mode of distributing the profile to any device that requests a profile. The gateway’s LED pattern will be altered when it is distributing a profile for easy identification. Profile distribution will automatically terminate after 10 minutes. For more information on gateway LED patterns, refer to Section 2.5 on page 11. 2.8.4 SLC Configuration The gateway: communicates with the control panel via the SLC. is only compatible with Gateway firmware version 2.1 or higher. occupies one module SLC address. Set the address using the rotary dials on the gateway prior to installation. 6 7 8 9 10 6789 11 4 12 3 13 1 0 1514 10 ONES TENS SLC-setaddtph.wmf Figure 2.14 Address Rotary Switches The SLC point uses the following configuration parameters: • Module Type: Monitor • Type Code Label: RF GATEWAY • FlashScan Type: RF GATEWAY A gateway does not initiate alarms but the point is used for event reporting. NOTE: When a wireless relay, wireless AV base, or wireless sync module is in use, module device count must be limited to 109 modules per loop. This includes wired and wireless modules that are on the same loop. The module address range must be within 1-109. 2.9 Operations 2.9.1 Modes of Operation Mesh Restructuring Start-up Factory Default Profile Configured Mesh Formation Initial Mesh Restructuring Mesh Upgrade in Progress Normal Mode Neighboring Network Scan Mesh Upgrade Preparation Rescue Mode Fire Protection Provided Figure 2.15 Gateway 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. 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. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 19 WIDP-WGI Wireless System Gateway Operations 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. SWIFT 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 a “NO PROFILE” trouble to the FACP. The gateway reports “Factory Default” to the communicator display of SWIFT Tools. Transitions back to Factory Default mode are not shown in the above diagram. However, any time the profile is removed from the gateway, it will return to Factory Default mode. Profile Configured The gateway enters the profile configured mode once a profile is assigned by SWIFT Tools or a distributor; or after creating a profile using the magnetic sensor. Profile configured mode is a temporary mode before the gateway transitions to mesh formation or normal mode. The gateway does not provide fire protection in the profile configured mode. While in the profile configured mode, the gateway reports a “RF MESH NOT FORMED” or “RF MESH” trouble to the FACP. The gateway reports “Profile Assigned” to the communicator display of the SWIFT Tools application. 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 formation 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 a “RF MESH FORMING” or “RF MESH” trouble when it is mesh formation mode with additional devices in the mesh. The gateway reports “Mesh Formation” to the communicator display of the SWIFT Tools application. 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 a “RF MESH FORMING” or “RF MESH” trouble to the FACP. The gateway reports “Restructuring” to the communicator display of the SWIFT Tools application. 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 automatically 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. Mesh Restructuring Mode In addition to the initial mesh restructuring mode, mesh restructuring is automatically performed after any restoration of communication 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 protection is provided by all devices that are participating in the mesh communication. The gateway reports “Restructuring” to the communicator display of the SWIFT Tools application. 20 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Operations WIDP-WGI Wireless System Gateway Bootloader Mode The gateway enters the bootloader mode when its firmware is being updated using SWIFT Tools. The gateway does not communicate with the FACP during bootloader mode. The gateway reports “Bootloader” to the communicator display 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 2.9.10 for more information on the mesh upgrade process. Neighboring Network Scan A Mesh network will identify adjacent 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 55. 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 locked 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 adapter to your computer. For more information on USB adapter, refer to Section 5. 2. Launch the SWIFT Tools application. Refer to Appendix A, “SWIFT Tools” for more information. 3. From the Home Screen, select the Site Survey, Create Mesh Network, or Diagnostics function. 4. Click Operations. The following screen is displayed. Figure 2.16 Operations Menu Select Gateway Operations to lock/unlock the gateway. The Lock/Unlock gateway screen appears, displaying the gateway that is locked. lock_unlcok_gateway.png 5. Figure 2.17 Lock/Unlock Screen 6. Select desired gateway and click Lock or Unlock as required. • Lock - The Lock Gateway screen is displayed. Create a password and click Lock. The gateway is locked. • Unlock - The Enter password for Gateway screen is displayed. Enter the password and click Unlock. The gateway is unlocked. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 21 WIDP-WGI Wireless System Gateway Operations Password Reset To reset the password, contact technical support. 2.9.4 Weak Link Trouble Reporting The SWIFT Network uses two paths of communication for each device. To establish the link between devices as a viable communication path, the signal strengths must meet the limits provided in Section 2.3. The SWIFT Network implements a higher threshold for primary connections to provide an extra layer of robustness and immunity from interference. A weak link trouble condition is initiated for any device that does not have at least one connection at the primary threshold. This is an optional setting that can be disabled to ignore the weak link trouble condition. The trouble can be disabled at the gateway. Disable Trouble Reporting at the Gateway Using SWIFT Tools selcomm.png To disable trouble reporting at the gateway through SWIFT Tools: 1. Connect the W-USB adapter to your computer. For more information on the USB adapter, refer to Section 5. 2. Launch the SWIFT Tools application. Refer to Appendix A, “SWIFT Tools” for more information. 3. From the Home Screen, select the Diagnostics function. 4. Select the desired gateway from the communicator panel. Figure 2.18 Communicator Panel Click View Mesh. Click Advanced Functions. A drop-down list is displayed. advfuncdrop.wmf 5. 6. Figure 2.19 Advanced Functions Options Click Weak links troubles (On). The Report weak links troubles screen is displayed. advfuncdrop.wmf 7. Figure 2.20 Report Weak Links Troubles Option 8. Click Turn off reporting. The trouble reporting is now disabled. 2.9.5 Collapse Network Command The collapse command is a diagnostic function to break the mesh network. All devices will retain the profile information but will be removed from the mesh. The mesh can be reformed by activating mesh formation. 22 CAUTION: FIRE PROTECTION DISABLED FIRE PROTECTION FROM WIRELESS DEVICES IS DISABLED WHEN A COLLAPSE NETWORK COMMAND IS ISSUED. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Operations WIDP-WGI Wireless System Gateway Collapse Mesh Network Using SWIFT Tools advfuncdrop.wmf To collapse the mesh network using the SWIFT Tools: 1. Connect the W-USB adapter to your computer. For more information on the USB adapter, refer to Section 5. 2. Launch the SWIFT Tools application. Refer to Appendix A, “SWIFT Tools” for more information on launching the SWIFT Tools application. 3. From the Home Screen, select the Diagnostics function. 4. Select a Gateway from the communicator panel. 5. Click View Mesh. The mesh is displayed. 6. Click Advanced Functions on top of the mesh display. A drop-down list is displayed. Figure 2.21 Advanced Functions Options Click Collapse Mesh. The Collapse mesh network screen is displayed. collapsemeshnetwork.jpg 7. Figure 2.22 Collapse Mesh Network Option Click Yes. The gateway password screen displays. Enter the verification password in the Gateway Password screen. The network is now collapsed and a confirmation message is displayed as shown below. collapsemeshnetworkconfirm.jpg 8. 9. Figure 2.23 Collapse Mesh Network Confirmation 2.9.6 Silence Network Command The silence network command is a diagnostic function to turn off all radio communication from the wireless devices for a set amount of time. All devices will retain the profile information but will be removed from the mesh. The devices will not send or receive any wireless communication until the set time expires or the device is rebooted. The mesh network can be reformed at the end of the silence period or after the device is restarted. CAUTION: FIRE PROTECTION DISABLED FIRE PROTECTION FROM WIRELESS DEVICES WILL BE DISABLED WHEN A SILENCE COMMAND IS ISSUED. Silence Mesh Network Using SWIFT Tools To silence the mesh network: 1. Connect the W-USB adapter to your computer. For more information on the USB adapter, refer to Section 5. 2. Launch the SWIFT Tools application. Refer to Appendix A, “SWIFT Tools” for more information. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 23 WIDP-WGI Wireless System Gateway From the Home Screen, select the Diagnostics function. Select a Gateway from the communicator panel. Click View Mesh. The mesh is displayed. Click Advanced Functions on top of the mesh display. A drop-down list is displayed. advfuncdrop.wmf 3. 4. 5. 6. Operations Figure 2.24 Advanced Functions Options Click Silence Devices. The Silence mesh network screen is displayed. Select the time interval to silence the wireless devices from the dropdown list and click Yes. 9. Enter the Verification Password in the Gateway Password screen. The network is silenced and confirmation is displayed as shown below. silencemeshnetwork.jpg 7. 8. silencemeshconfirm.jpg Figure 2.25 Silence Mesh Network Screen Figure 2.26 Silence Mesh Network Confirmation Message 2.9.7 Multiple Wireless Sensor Network Installation Restrictions The SWIFT Network technology shares the RF spectrum with other Honeywell Wireless Sensor Network systems. Honeywell has established a limit of 4 overlapping networks to avoid congestion in the RF spectrum. If the 4 network limit is exceeded, a system trouble will be generated by the system that detects 4 or more adjacent networks. To resolve this trouble, the instances of overlap need to be removed. Refer to Appendix C:, "Troubleshooting and Testing" for suggestions on removing overlap between wireless networks. The trouble will be self-restoring up to 36 hours after the condition is resolved. To expedite the trouble resolution, transition the network that is reporting the trouble in and out of mesh formation mode. 2.9.8 Multiple Wireless Sensor Network Synchronization Installations that deploy multiple mesh networks with one or more wireless initiating devices in one network activating one or more wireless output devices in another network must be in synchronization to meet the alarm latency of 10 seconds. Mesh network synchronization is an automatic process for any networks that are in an overlapping condition. Mesh network synchronization will occur after the initial mesh restructuring. Trouble Reporting for Multiple Mesh Synchronization A trouble will be generated for any overlapping networks with insufficient signal strength for reliable synchronization communication. Reliable communication for mesh synchronization requires a minimum of two devices in each network to be in range of each other. 24 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Operations WIDP-WGI Wireless System Gateway This trouble is shown as a “mesh to mesh sync trouble” under the “More Info” dialog box in the Communicator pane. For more specific information, retrieve network statistics. Figure 2.27 Mesh Synchronization Trouble Reporting Verification of Synchronization The status of the mesh synchronization routine and time remaining for the routine will be indicated by SWIFT Tools. Figure 2.28 Mesh Synchronization Verification SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 25 WIDP-WGI Wireless System Gateway Operations The state of the trouble condition will be indicated by SWIFT Tools as well as the FACP. Mesh Statistics in the diagnostics screen of SWIFT Tools will provide further details regarding the condition of overlap and recommendations. Figure 2.29 Mesh Synchronization Verification Trouble Disable Synchronization Fault reporting The trouble generation of a synchronization fault may be disabled for any installation that does not require mesh-to-mesh synchronization. Mesh-to-mesh synchronization is not required for installations that utilize only wireless input types (detectors, monitor modules, pull stations) with no wireless output device types (relay, AV base, sync module). Mesh-to-mesh would not be required for installations that utilize only wireless output devices types with no wireless input device types. Mesh-to-mesh synchronization would not be required for installations where the mesh networks are not operating in a co-operative manner, i.e. the output devices of a particular mesh network will not be controlled by the events of another mesh network. This will be applicable for mesh networks that are in separate zones with no dependencies on each other. To disable the mesh synchronization fault reporting use SWIFT Tools (add the instructions here, process yet to be determined. It will be similar to the weak link trouble reporting). 2.9.9 Avoiding RF Interference The SWIFT wireless mesh network uses radio frequency hopping spread spectrum technology to communicate in the 900 MHz ISM band (902MHz to 928MHz). Other commercial and industrial products also operate in this band. If two-way radios or other wireless communication devices are used during the installation process, it is recommended that they be kept at least 4 feet away from the Farenhyt wireless devices or that they operate on a different frequency band to ensure rapid mesh formation. A properly installed SWIFT wireless mesh network with primary link reporting enabled will be highly immune to RF interference from other wireless products even when they are nearby. The use of the weak link reporting feature is highly recommended. If the system is installed in a controlled environment where other 900 MHz ISM band devices will not be present, the primary link reporting feature may be disabled to permit greater distances between installed devices if required. The SWIFT wireless mesh network will be able to automatically detect and avoid certain types of in-band channel interference (often caused by two-way radios) by using an alternate channel set. The system will log detection and avoidance of this kind of interference in the gateway history as “Walkie Talkie Mode” Entry or Exit. 26 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Operations WIDP-WGI Wireless System Gateway 2.9.10 Trouble MessagesDistributed Firmware Updates Trouble Message Type Description Course of Action RF JAMMING or JAMMING Non-latching The gateway is being overloaded with RF energy and is unable to receive messages from other devices. Identify any RF emitters in close proximity of the gateway and remove them or relocate the gateway. SOFTWARE MISMATCH or SOFTWARE Non-latching Software mismatch between the application code for the RF processor and the SLC processor. Use SWIFT Tools to identify the mismatch, and update the processors as necessary for compatibility. RF MESH FORMING or RF MESH Non-latching The gateway and attached devices are searching for additional devices to join the mesh. The wireless system is not able to provide fire protection during this time. Wait until all desired wireless devices are communicating and are members of the mesh network. Once all desired devices are in the mesh network, the mesh forming mode can be terminated by the user by activating the Mesh formation magnetic sensor or by using the SWIFT Tools. If no action is taken, this mode will automatically exit 10 minutes after the last device joins. RF MESH NOT FORMED or RF MESH Non-latching The gateway contains a profile but has not formed a mesh. To form a mesh, refer to, "Create a Mesh Network". RF MESH REFORMING or Non-latching RF MESH The gateway is performing the initial identification and assignment of optimal communication paths for the mesh network. The wireless system is not able to provide fire protection during this time. No action needed. The duration of this event correlates to the number of devices in the mesh. A fully loaded mesh may take up to 5 minutes to restructure. NO PROFILE Non-latching The gateway is in the factory default state and is not providing fire protection. A profile needs to be created or assigned to the gateway before a mesh can be formed. ADDRESS FAULT or ADDR FAULT Non-latching There is either a device in the mesh set to address 0 or there is a duplicate address used for another wireless module at the address of the gateway. The offending device (detector or module set at address 0 or module at the same address as the gateway) will be indicating the LED pattern for address fault. Find and resolve that device. RF OVERLAP Non-latching Wireless communication reliability is compromised due to the installation limits of Farenhyt wireless systems being exceeded. Investigate for overlapping or adjacent wireless systems produced by Farenhyt. Reduce the instances of overlap by removing systems, or devices in the overlapping region. Refer to Section 2.9.7 on the installation limits for the Farenhyt wireless system. RF DEVICE NO ANSWER or DEV NO ANS Latching trouble; remains active for the first 90 seconds before it can be cleared with a system reset. A wireless device that was part of the mesh has dropped from the mesh. The trouble is reported at the FACP 90 seconds after the device drops from the mesh. Initiate a system reset at the FACP at least 3 minutes after the trouble was initiated to clear. If the device was intentionally removed, no further action is needed. If the device was not intentionally removed, refer to panel history or active panel troubles to investigate the cause of the disturbance. Table 2.1 Trouble Messages Starting with version 3.0 and higher, firmware updates for devices in the mesh network can be distributed via the mesh network from the gateway. SWIFT Tools is required to initiate the firmware upgrade procedure. Refer to Appendix E for firmware upgrade instructions. An entire mesh network of devices can be upgraded assuming certain preconditions are met: all devices are running application code version 3.0 or higher, there are no active “low battery” troubles, there are no active “class A” connectivity fault conditions, the mesh is in “normal mode”. Failure to meet the preconditions will be indicated via SWIFT Tools, and must be remedied before the mesh upgrade can continue. CAUTION: NO FIRE PROTECTION DURING THE UPDATE, THE MESH NETWORK WILL NOT PROVIDE FIRE PROTECTION. All wireless points associated with the mesh network will be indicating a “no answer” trouble or “invalid reply”. There are two phases to the mesh upgrade procedure. Phase 1 - Mesh upgrade preparation: SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 27 WIDP-WGI Wireless System Gateway Operations SWIFT Tools must stay in communication with the gateway during the mesh upgrade preparation phase. The user will initiate the upgrade process via SWIFT Tools, and SWIFT Tools will proceed to automatically update the SLC application code of the gateway, the RF application code of the gateway, and transfer the new device application code to the gateway. The user may cancel the process at any point during the mesh upgrade preparation. Mesh upgrade preparation can take 5 to 15 minutes depending on the number of downloads that are needed. Phase 2 - Mesh upgrade in progress: The gateway will distribute the new application image to the mesh network of devices during this phase. SWIFT Tools is not required to be in communication during this phase, but will provide indication of the progress of the upgrade when it is in communication. The distribution of the new application image may take up to 90 minutes depending on the number of devices in the mesh network. The gateway will automatically execute mesh formation at the completion of the mesh upgrade. Any devices that did not successfully complete the upgrade will need to be upgraded individually. 28 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Section 3: Wireless Devices 3.1 Description The SWIFT Network consists of the following devices: WIDP-PHOTO - Wireless Photoelectric Smoke Detector -FCC ID: AUBWFSSD The wireless photoelectric smoke detector is powered by four CR123A batteries. It has a sensor head to detect smoke and LEDs to indicate the activation and trouble status. WIDP-ACCLIMATE - Wireless Acclimate Detector FCC ID: AUBWFSSD The wireless Acclimate detector is powered by four CR123A batteries. It has a sensor head to detect smoke and LEDs to indicate activation and trouble status. WIDP-HEAT-ROR - Wireless Rate of Rise Heat Detector FCC ID: AUBWFSSD The rate of rise heat detectors are powered by four CR123A batteries. The detectors have LEDs to indicate the activation and trouble status. WIDP-HEAT - Wireless 135° Fixed Heat Detector FCC ID: AUBWFSSD The fixed heat detectors are powered by four CR123A batteries. The detectors have LEDs to indicate the activation and trouble status. WIDP-MONITOR - Wireless Addressable Monitor Module FCC ID: AUBWFSMM The wireless monitor module is powered by four CR123A batteries. It can be connected to a switch within three feet of its location or wired directly to the pull station. The module has LEDs to indicate the activation and trouble status. WIDP-RELAY - Wireless Addressable Relay Module FCC ID: AUBWFSRM The wireless relay module is powered by four CR123A batteries. It provides the system with a dry-contact output for activating a variety of auxiliary devices, such as fans, dampers, control equipment, etc. Addressability allows the dry contact to be activated, either manually or through panel programming, on a select basis. The module has an LED to indicate the activation and trouble status. WIDP-PULL-DA - Wireless Addressable Pull Station FCC ID: xxxxx The wireless pull station is powered by four CR123A batteries. The module has an LED to indicate the activation and trouble status. The pull station will occupy one module address. • Type Code Label: Monitor • FlashScan Type: RF MONITOR WAV-RL, WAV-WL, WAV-CRL, WAV-CWL - Wireless Addressable AV bases FCC ID: xxxx The wireless AV base is powered by eight CR123A batteries. Four of the CR123A batteries are used to power the notification element and four of the CR123A batteries are used to power the radio communication element. The module has an LED to indicate the activation and trouble status. The module requires a non-compact wall or ceiling System Sensor L-series notification device (ordered separately). A notification device with an audible component must be set to a non-coded setting (i.e. continuous or Temp3). The base address set by the code wheels on the AV base will require the following configuration: • Type Code Label: Relay • FlashScan Type: RF RELAY Base+1 address will use the following configuration: • Type Code Label: Control • FlashScan Type: Control Wireless related trouble events described in Section 3.6.3 will be indicated at the base address. Open circuit at the base+1 address will indicate a missing notification device. Short circuit at the base+1 address will indicate a incorrectly configured or faulted notification device. Both module points will be used to drive the output of the AV unit to the desired pattern below: Base Address Base+1 Address Notification Pattern OFF OFF Off ON OFF Strobe Only (Audible Silenced) ON ON Strobe & Audible active OFF ON Magnet Test mode (Strobe & audible activate when magnet is placed on the unit) NOTE: To configure an audible/visual unit to silence only the audible component with a signal silence command, configure both addresses to activate for the alarm condition, the base address shall be non-silenceable and the base+1 shall be silenceable with the appropriate resound settings. W-SYNC - Wireless Addressable Sync Module FCC ID: xxxx The wireless sync module is 24VDC externally powered and requires 4 supplemental CR123A batteries. The module has an LED to indicate the activation and trouble status. The wireless sync module will occupy two consecutive SLC module addresses. Base address set by the code wheels on the sync module will use: • Type Code Label: Relay • FlashScan Type: RF RELAY SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 29 Wireless Devices Agency Approvals Base+1 address will use: • Type Code Label: Control • FlashScan Type: Control Wireless related trouble events described in Section 3.6.3 will be indicated at the base address. The end of line supervision of the monitor input and the power monitoring of the external 24VDC supply will be indicated at the base+1 address. The following table indicates the output state. Base Address Base+1 Address Control Output Signal Low (inactive) Synchronization Output Signal OFF OFF Low (inactive) ON OFF High (active) Strobe Only (Audible Silenced) ON ON High (active) Strobe & Audible active OFF ON High (active) Magnet Test mode NOTE: 1. To configure a NAC circuit, with audible and visual units, to silence only the audible component with a signal silence command, configure both addresses to activate for the alarm condition. The base address shall be non-silenceable and the base+1 shall be silenceable with the appropriate resound settings. 2. When the sync module is being used for delivering only the synchronization signal (i.e. applications with the MDL3), it is recommended to leave the base address point constantly active to eliminate any delay in initial synchronization. NOTE: When a wireless relay, wireless AV base, or wireless sync module is in use, module device count must be limited to 109 modules per loop. This includes wired and wireless modules that are on the same loop. The module address range must be within 1-109. For more information on the LED indicators, refer to Section 3.6.2. 3.2 Agency Approvals 3.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. 2. This device must accept any interference received, including interference that may cause undesired operation. WARNING: DO NOT MAKE CHANGES TO THE EQUIPMENT. CHANGES OR MODIFICATIONS NOT EXPRESSLY APPROVED BY THE MANUFACTURER COULD VOID THE USER’S AUTHORITY TO OPERATE THE EQUIPMENT. 3.2.2 Federal Institute of Telecommunications This device utilizes the Honeywell915 rev A radio module and complies with IFETEL standard(s). IFT: RCPHOSW14-1983 3.3 Specifications The following are the specifications for the wireless devices. Specification Radio Frequency Data Lower ISM Band (902-928 MHz) Maximum power output +17dBm Minimum signal strength level needed at the receiver for a primary path with weak link trouble reporting enabled. -55dBm Minimum signal strength level needed at the receiver for a secondary path or primary path with weak link trouble reporting disabled. Must be 18 dBm higher than the noise floor down to -80dBm Maximum ambient noise level -85dBm Minimum battery life 2 years (where the activation of a wireless device is used for fire purposes only) Table 3.1 Wireless Device Specifications 3.4 Installing, Mounting, and Wiring Devices For information on installing the wireless devices, refer to the documents referenced in Section 1.3 on page 8. 30 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Configuration and Programming Wireless Devices 3.5 Configuration and Programming Device configuration starts with assigning a profile. 3.5.1 Assigning Profiles To assign a profile, the device must be in a factory default state. A single red light flashes on the LED confirming that the device is in the default state. To restore the device to factory default state, refer to Section 3.5.4, “Restoring a Device to Factory Default”. There are two methods to assigning a profile. Assigning a Profile to a Device (Detector or Module) Using a Gateway or Distributor A gateway that has a profile can be used to distribute that profile to other devices. The gateway must be in distributor mode before it can distribute a profile. For more information on converting a gateway to a distributor, refer to Section 2.8.3. A device with a profile can be used to distribute the profile. To put a device into distributor mode, refer to topic, “Converting a Device into a Distributor” on page 33. Distribute a Profile from a Gateway/Distributor to a Detector To transfer a profile from a gateway/distributor to a detector: 1. Bring the detector within 20 feet of the gateway/distributor. 2. Insert one or more batteries to power on the detector. Ensure the detector is in factory default state. The LED on the detector will single-blink or double-blink red confirming that it is in the factory default state. 3. Activate the magnet test switch shown in the figure below. (The base with the integral tamper magnet or another magnet can be used to do this.) Once the magnet sensor has been activated, the LED blinks red every half second indicating that it is requesting a profile. If the profile is successfully received, the green LED turns on steady for 10 seconds. If the profile is not received within 1 minute, the LED blinks red every ten seconds indicating that it has stopped requesting a profile. LED LED Magnet test switch magnetdet.wmf Tamper magnet Figure 3.1 Magnetic Sensor on a Detector Distribute a Profile from a Gateway/Distributor to a Module To transfer a profile from a gateway/distributor to a module: 1. Bring the module within 20 feet of the gateway/distributor. 2. Insert one or more batteries to power on the module. Ensure the module is in factory default state. If the module is in factory default state, the LED blinks red once. 3. Toggle the state of the tamper condition to instruct the module to request a profile. To toggle the tamper condition state, start with the faceplate (with integral magnet) removed. 4. Quickly replace then remove the faceplate from the module to momentarily activate the magnetic tamper sensor on the module. Do not attach the mounting screws for the faceplate during this step. The LED blinks red every half second indicating that it is requesting a profile. The green LEDs turn on steady for ten seconds indicating that the profile has been assigned. If the profile is not received within 1 minute, the LED blinks red every ten seconds indicating that it has stopped requesting a profile. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 31 Wireless Devices Configuration and Programming magnetmon. wmf Magnetic sensor Figure 3.2 Magnetic Sensor on a Module Assigning a Profile Using SWIFT Tools assignprofile_select.jpg To assign a profile to the device using the SWIFT Tools application, do the following: 1. Connect the W-USB adapter to your computer. For more information on the USB adapter, refer to Section 5. 2. Launch the SWIFT Tools application. Refer to Appendix A, “SWIFT Tools” 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. Figure 3.3 Creating or Importing a Profile Power on the device within approximately 20 feet of the laptop running SWIFT Tools. Ensure that the Scan On selection box is checked. Select the device from the Communicator panel. assignprofile.png 6. 7. 8. Figure 3.4 Selecting a Device 32 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Configuration and Programming Click Assign. assignprofile2.png 9. Wireless Devices Figure 3.5 Assigning a Profile The device is now included in the list of devices with a profile assigned. When the profile is assigned, the green LEDs turn on steady for 10 seconds. 3.5.2 Distributor Mode Converting a Device into a Distributor NOTE: Only a device with a profile can be used as a distributor. To turn a device into a distributor: 1. Power up the device with one battery installed. 2. Ensure that the device is in the profile modification mode. If the device is in profile modification mode, the yellow LED will blink once every 5 seconds. The profile modification mode times out if the device has not received a command in one minute. 3. Alternate the SLC address wheel between 0-1-0-1. To turn the SLC address wheel, use a flathead screwdriver to adjust the rotary switches on the device to: 1. Set the address to 0. 2. Change the address to 1. 3. Change the address back to 0. 4. Change the address back to 1. NOTE: The green LED blinks every half second when the device is functioning as a distributor. Converting a Distributor Back into a Device To return a distributor device back to a network device, replace the batteries and provide a proper SLC address. A normal device requires four batteries for proper operation. It is recommended to use fresh batteries after the distributor mode. 3.5.3 Mesh Formation To add a device to a mesh, refer to the topic, "Create a Mesh Network". To form a mesh network, ensure that the gateway is powered on and contains a profile. Activate the mesh formation (refer to Figure 2.2) magnetic sensor on the gateway. Repeater The SWIFT Network does not require the use of a dedicated repeater as all wireless devices act as repeaters. When the repeater function is needed in a location where no specific fire function is required, a wireless monitor module or another device can be installed to act as a repeater. 3.5.4 Restoring a Device to Factory Default Removing Profiles Without Using SWIFT Tools A device can be restored to factory default state: 1. Start with the device powered off. The process is performed during start-up. 2. Power on the device by inserting a single battery into any slot in the device. The LEDs will blink yellow twice every five seconds for one minute after inserting the battery. 3. Alternate the SLC address wheel between 0-159-0. To turn the SLC address wheel, use a flathead screwdriver to adjust the rotary switches on the device to: 1. Set the address to 0. 2. Change the address to 159 (tens set to 15, ones set to 9). SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 33 Wireless Devices Change the address back to 0. 6 7 8 9 10 6789 11 4 12 3 13 1 0 1514 10 ONES TENS SLC-setaddtph.wmf 3. Configuration and Programming Figure 3.6 Address Rotary Switches NOTE: The above illustration depicts the rotary switches being set at address 35 (rotary switch on 'TENS' set at 3 and rotary switch on 'ONES’ set at 5. Ensure that the code wheel address pattern is toggled within 1 minute of inserting the battery. After the address wheel pattern is set, the LEDs in the device blink green five times followed by a single or double red blink confirming that the device has been reverted back to factory default condition. Removing a Profile Using SWIFT Tools To remove a profile in a device using SWIFT Tools: 1. Connect the W-USB adapter to your computer. For more information on the USB adapter, refer to Section 5. 2. Launch the SWIFT Tools application. Refer to Appendix A, “SWIFT Tools” for more information on launching the SWIFT Tools application. 3. From the Home Screen, select the Site Survey, Create Mesh Network, or Diagnostics function. 4. Click Operations and select Set device to factory default. Figure 3.7 Operations Menu Tamper and place powered-on devices that are to be reset in range of the W-USB. The Reset Devices screen appears, displaying the gateway and other devices that have a profile assigned. Click to select the desired device and click Reset Device to remove the profile. Figure 3.8 Reset Devices Screen resetdevices.jpg 5. 6. The profile is removed and the device is reset to the factory default state. 34 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Device Operations Wireless Devices 3.6 Device Operations 3.6.1 Modes of Operation Factory Default Mode In this mode, the devices are not associated with the gateway. A profile must be assigned to associate the device with the gateway. For further information on assigning a profile, refer to “Assigning a Profile to a Device (Detector or Module) Using a Gateway or Distributor” on page 31. A device cannot perform any fire protection in the factory default state. In default mode, the devices will be viewable in the communicator window of SWIFT Tools with the state displayed as “Factory Default”. A device in factory default can be used for site survey. Site Survey Mode A site survey assesses and qualifies a site for installing a SWIFT network. The site survey view in SWIFT Tools gives the Radio Frequency (RF) assessment of the site. The tool reports the suggested device spacing based on the data collected during the site survey. This helps to improve the reliability and performance of a SWIFT network in the wireless fire alarm system. A device cannot perform any fire protection in the site survey mode. A device that is ready to enter site survey will indicate “pending site survey” in the communicator section of SWIFT Tools. A device in site survey will not communicate with SWIFT Tools and will be listed as “offline” in the communicator section. For more information on performing a site survey, refer to Appendix B. Profile Assigned Mode In this mode, devices are associated with the gateway but are not active participants in the mesh network. A device that is not in the tampered state can join a mesh network in formation or during rescue mode. For further information on mesh formation, refer to “Mesh Formation Mode” on page 35. For more information on rescue mode, refer to “Rescue Mode” on page 35. A device with an assigned profile can also be used to distribute profiles. Refer to Section 3.5.2. Devices are not enabled for fire protection until they become part of a mesh network. A device will show a or no answer/missing at the FACP. In this mode, devices are viewable in the communicator window of SWIFT Tools. If the device has a profile and is in the tampered state, it will indicate a status as “Profile Assigned-Tamper”. A non-tampered device will indicate “active scan” as it searches for a mesh network. Bootloader Mode In this mode, a device is ready for an update. It cannot participate in a mesh network and cannot provide fire protection. The device is viewable in the communicator window of SWIFT Tools with the status “Bootloader”. To remove a device from bootloader mode, refer to Appendix C. Distributor Mode In this mode, a device is functioning as a profile distributor. The device cannot participate in a mesh network and cannot provide fire protection while it is in distributor mode. A device in distributor mode will be used as a mobile unit to share the profile with other devices. The distributing device will be available in the communicator window of the SWIFT Tools with the status “Distributor”. For more information, refer to Section 3.5.2. Mesh Participant Modes Devices that are in the mesh network no longer communicate directly with SWIFT Tools. SWIFT Tools must communicate with the gateway for status information on a device that has joined a mesh. The gateway will respond to the FACP for the device at the address set with the SLC rotary address wheels. Mesh Formation Mode In this mode, a device is an active participant in a mesh that is forming. The LED will blink green then yellow every 6 seconds. The device cannot perform any fire protection in this state. The device responds to its SLC address with an “INITIALIZING” trouble. For further information on mesh formation mode, refer to “Section 3.5.3”. Initial Mesh Restructuring Mode In this mode, the mesh network is formed and is in the process of establishing stronger communication paths. The LED will blink yellow every 6 seconds. The device cannot perform any fire protection in this state. The device responds to its SLC address with a “INITIALIZING” trouble. Normal Mode In normal mode, the mesh network is formed and provides fire protection. The LED will blink every 18 seconds. The LED flash can be disabled by panel configuration. If a device is in trouble, it is indicated by the trouble messages. Rescue Mode In rescue mode, a devices is an active participant of a mesh network. It will search and retrieve any device that has lost communication with the network. Rescue mode is indicated by an LED blink every 12 seconds. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 35 Wireless Devices Device Operations 3.6.2 LED Indicators The two LEDs on the devices blink in the same pattern to allow the LEDs to be viewed from any angle. The LED indicators are provided in Appendix D on page 55. 3.6.3 Trouble Conditions The following trouble conditions are unique to the battery powered RF devices. Trouble Conditions with Fire Protection The devices (on an only) indicate the following trouble conditions with a single yellow LED blink every 14 seconds. The wireless device will still perform fire protection during the following trouble states. Low Battery The low battery event denotes: • The device has a minimum of one week power left to perform the required operations. Or • One (or more) of the batteries is missing or dead. The low battery event is a latching condition. To clear the low battery event, tamper the device and replace all four batteries. When a device is tampered, it drops out of the mesh network and attempts to rejoin as soon as the batteries are replaced and the tamper event is cleared. If the device has dropped from the mesh prior to the tamper event, a system reset has to be issued to clear the low battery trouble. The panel displays “LOW BATTERY” or “LOW BATT” during a low battery condition. Weak Link The weak link trouble denotes a connection of insufficient primary parent link signal strength. To resolve a weak link, reduce the distance between devices, place them away from obstructions, or add a repeater. Tamper the device when moving it to a new location. Restart mesh formation after a repeater is installed or after a device has been relocated and the tamper condition is cleared. Terminate mesh formation once the devices have joined the mesh or allow mesh formation to timeout. Restructuring will automatically start and the gateway will reevaluate the link connectivity between all devices and select suitable signal paths. Weak link trouble reporting can be disabled at the FACP or at the gateway for installations not requiring primary link connectivity. Refer to Section 2.9.4 for more information on disabling weak link trouble reporting. Refer to the troubleshooting section for more information on resolving a weak link condition. The panel displays “WEAK LINK” for a device that is in the weak link condition. Class A Fault The Class A fault denotes a single connection path from the device. The wireless system is a Class A system requiring two communication paths for normal operations. To remedy the Class A fault, ensure adequate device spacing. The use of a repeater may be required. The wireless mesh is a self-healing network. If the trouble is not cleared within 5 minutes, additional actions may be required. Refer to the troubleshooting section for tips on resolving Class A fault conditions. The panel will display “RF CLASS A” during a Class A fault condition. Trouble States without Fire Protection Jamming Jamming occurs when a device is overloaded with an interfering RF signal but is able to send outgoing messages. A jamming event is detected after 20 seconds of exposure to the jamming signal. In the event of jamming, the device will drop from the mesh network. The panel displays “RF JAMMING” during a jamming condition. Duplicate Address Two wireless devices on the same mesh network that are set to the same address will report a duplicate address trouble at the FACP. The gateway will respond to the panel with the device type of the first device to join. The panel displays “DBL ADDR” during a duplicate address condition. Tamper A tamper trouble indicates that a detector is not firmly attached to its base or the cover plate is not properly attached to a module. The tamper condition is annunciated in the following ways: Device Indication The yellow LED on the device turns on steady for 4 seconds followed by a blink pattern of yellow, yellow, red every 15 seconds immediately after the tamper condition. Panel Indication Devices that are in the tampered condition report a latching trouble event. The event is active for 90 seconds before it can be removed with a system reset. Once the event is removed, the device reports a “TAMPER” until the device is restored or the point is removed from the database. Clearing the Tamper To clear the tamper, • For a detector, ensure that the magnet has not been removed from the base and the detector is locked together with its base. • For a module, ensure that there is a magnet in the cover plate and it is securely fastened to the device in the correct orientation. Once the tamper event is cleared, the LEDs in the device turn on steady for 2.5 seconds, in the following color patterns that denote the battery status. 36 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Device Operations Wireless Devices • • Green - All the four batteries are installed and fresh. The device has a minimum one year of normal operation. Yellow - All the four batteries are installed, and one or more is no longer fresh. This device has between a minimum of 1 month and 1 year of operation. • Red - One or more of the batteries are low in power and/or the device has a minimum of one week of operation. After the device displays the current battery condition, it attempts to join the mesh network in the rescue mode or normal mode. This is indicated by a double yellow blink every 3.4 seconds. If a device does not find its mesh in the rescue mode, it searches for its mesh under formation. This is indicated by a double yellow blink every 20 seconds. No Answer A device that is not in the mesh, displays a “MISSING” message at the FACP. Follow the steps in “Mesh Formation Mode” on page 35 to have a device join the mesh. Device Initialization A device reports a device initialization trouble when it is part of a mesh network but is not capable of performing fire protection. This is the case for mesh networks that are still forming or going through initial restructuring. The panel displays “INITIALIZING” during a device initialization condition. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 37 Section 4: W-SYNC Wireless Synchronization Module 4.1 Description The wireless synchronization module works with wireless AV base models WAV-RL, WAV-WL, WAV-CRL and WAV-CWL to provide audio and visual synchronization of a wireless notification appliance to a wired notification appliance. Synchronization is only available with notification appliances that use the System Sensor synchronization protocol. The W-SYNC also provides wireless control and monitoring of a Notification Appliance Circuit (NAC) expander or power supply. It does not support the “whoop” pattern. The wireless synchronization module operates from 24VDC power with supplemental battery support. A trouble will be generated at the panel if batteries are not installed or at a low battery level. Synchronization is not available during supplemental battery operation. For more information on the W-SYNC, refer to Document I56-6518 that ships with the product. 4.2 Wiring The W-SYNC may be wired to compatible FACPs using an MDL3 Sync Module or the HPFF8/HPFF12 NAC Expanders. 4.2.1 FACP Wire the W-SYNC to the FACP as shown below. The synchronized output wiring must be contained in the common enclosure of modules or wired in conduit in enclosures mounted within 20 feet of each other MDL3 Class B (Style Y) NACs HORN CONTOL ZONE 1 OUT to next device or EOL B- - ZONE 1 IN ZONE 2 OUT to next device or EOL B- - ZONE 2 IN NAC SLAVE IN SLAVE IN SLAVE OUT NAC 1 NAC 2 B+ B+ Slave Class A (Style Z) NACs HORN CONTOL ZONE 1 OUT B- - ZONE 1 IN ZONE 2 OUT ZONE 2 IN NAC SLAVE IN SLAVE IN SLAVE OUT B+ A+ A- ELR* 24VDC C Trouble Contacts (if provided) NC synchronized output *Note: If the power supply has trouble contacts to be monitored, install ELR supplied with W-SYNC on the power supply. If not, install ELR on W-SYNC. 1 Class A (Style Z) Zone MDL3 NAC 3 UL-Listed power supply 2 Class B (Style Y) Zones Slave to next device ELR* W-SYNC to next device to next MDL3’s NAC SLAVE IN terminals (4 MDL3 modules max.) Figure 4.1 W-SYNC Wiring to FACP 38 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Wiring W-SYNC Wireless Synchronization Module 4.2.2 HPFF8/HPFF12 When using the HPFF8 or HPFF12 to power the W-SNYC module, set the dipswitches on the HPFF8/HPFF12 as follows: • SW1- OFF • SW2- OFF • SW3- OFF • SW4- OFF • SW5- ON • SW6- OFF Wire the W-SYNC to the HPFF8/12 as follows): ELR NC N/C COMM N/O AC FAIL N/C COMM N/O TROUBLE TB2 W-SYNC TB3 REF+ REF– + IN SIGNAL 1 – IN + OUT – OUT + IN HPFF8/HPFF12 power supply trouble input synchronized output + OUT – OUT SIGNAL 2 – IN TB4 TB1 A+ BATT+ BATT– A– 1L1 1L2 2L1 2L2 3L1 3L2 4L1 4L2 24VDC Power Figure 4.2 W-SYNC Wiring to HPFF8/HPFF12 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 39 Section 5: USB Adapter 5.1 Introduction The W-USB is a software interface that can be connected to a PC (running SWIFT Tools) through a USB port. It communicates with the RF devices using the same frequencies as the mesh protocol. This device is powered directly by the USB port. The LED gives an indication of power and initialization status. Color Red Yellow Blue Description Device has power but is not initialized or the driver is missing. Device is initialized and ready. Device is updating or failed to load properly. Complete the update or repower the device. If problems persist, contact technical support. usb.wmf The W-USB has an adjustable USB connector to facilitate connection by reducing the size when connected to a laptop/tablet. Figure 5.1 USB Adapter 5.2 Agency Approvals 5.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. FCC ID: PV3WFSADPT WARNING: DO NOT MAKE CHANGES TO THE EQUIPMENT. CHANGES OR MODIFICATIONS NOT EXPRESSLY APPROVED BY THE MANUFACTURER COULD VOID THE USER’S AUTHORITY TO OPERATE THE EQUIPMENT. 5.2.2 Federal Institute of Telecommunications This device utilizes the Honeywell915 rev A radio module and complies with IFETEL standard(s). IFT: RCPSYWU14-1829 5.3 Specifications 5.3.1 Electrical Specifications • • Operating voltage: 4.3 VDC - 5.5 VDC (5VDC typical) Supply current: 25 mA - 85 mA (33 mA typical) 5.3.2 Serial Communication Specification • USB standard 2.0 5.3.3 Mechanical Specifications • • • • • 40 USB Connector type A Length with connector closed: 3 in. (76.2 mm) Length with connector open: 3.8 in. (96.2 mm) Thickness on connector side: 0.5 in (13 mm) Thickness on antenna side: 0.3 in. (8.4 mm) SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Driver Installation • • USB Adapter Width: 1.2 in. (31.2 mm) Weight: 0.7 oz. (19.5 g) 5.3.4 Environmental Specifications • • • Humidity: 10%RH - 93%RH, non-condensing Maximum operating temperature: 32°F - 122°F (0°C - 50°C) Storage temperature: 14°F - 140°F (-10°C - 60°C) 5.4 Driver Installation NOTE: Install SWIFT Tools before attempting to install the driver. devcemanager6b.jpg To install a driver: 1. Insert the adapter into the PC. The adapter is detected and is displayed in the Computer Management screen as a SWIFT USB Communication Device. Figure 5.2 Computer Management Screen Right click on SWIFT USB Communication Device and select Update Driver Software. devcemanager8.jpg 2. Figure 5.3 Update Driver Software SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 41 USB Adapter Select the Browse my computer for driver software option. devcemanager9.jpg 3. Driver Installation Figure 5.4 Browse Computer for Driver Software The Browse dialog box appears. Click Browse. Navigate to the folder: C:\Program Files\Honeywell\Device Driver. Click Next. devcemanager10.jpg 4. Figure 5.5 Browse Folder for Driver Software 42 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Driver Installation The confirmation message displays when the driver software is updated successfully. devcemanager11.jpg 5. USB Adapter Figure 5.6 Driver Software Update Confirmation devcemanager7.jpg The newly installed device will now display on the computer management screen under Ports. Figure 5.7 New Communications Port devcemanager13.jpg If SWIFT Tools detects an incompatible USB adapter connected, it will prompt a message to update the USB adapter firmware. Figure 5.8 Incompatible Adapter Message If you gets this error message, update the USB Adapter through the Firmware Update feature in the Operations section of SWIFT Tools. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 43 Appendix A: SWIFT Tools A.1 Description SWIFT Tools is a standalone desktop Windows® application. It is a configuration and maintenance tool for the gateway and devices of the SWIFT Network. Site surveys, device configurations, and diagnostic functions are all part of SWIFT Tools. SWIFT Tools can be installed on a PC or a laptop and communicates with the gateway and wireless devices through USB-based user interface. Connect the W-USB adapter to the computer to invoke the SWIFT Tools application. At any point, only one instance of SWIFT Tools can run on a laptop or PC. SWIFT Tools has the following utilities: Site Survey view Creating Mesh Network Diagnostic view SWIFT Tools works in a wireless environment with the gateway and devices within a range of approximately 20 feet. SWIFT Tools is designed for systems running Microsoft Windows. Minimum system requirements are listed below. Component Minimum Requirement Operating System Windows 7 and Windows 8 (32 bit and 64 bit) Hard Drive 20 GB hard drive space with minimum 1GB free space on hard disk. RAM Minimum 512MB RAM Processor speed 1GHz minimum (2.4 GHz recommended) Processor, 512K Cache Regional Settings English (United States) Table A.1 System Requirements A.2 Launching SWIFT Tools start_fh.wmf To launch SWIFT Tools, 1. Click Start, point to All Programs, click SWIFT Tool, and then SWIFT Tool. The following screen is displayed. Alternatively, SWIFT Tools can be opened through a shortcut located on the desktop. Figure A.1 SWIFT Tools Start Screen 44 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Launching SWIFT Tools Click Start Using. The SWIFT Tools screen is displayed. You can create a new jobsite or open an existing one. swifttools.wmf 2. SWIFT Tools Figure A.2 SWIFT Tools Screen A.2.1 Creating a New Jobsite homepage_xls.wmf To create a new jobsite: 1. Click Create from the PC Tools screen. 2. Enter the name of the new jobsite in the Jobsite Name field. 3. Enter the Location/Description if any, and click Create. 4. The Create Project dialog box opens. Navigate to the desired folder location where the project will be saved. 5. Click Save. The jobsite is created and the following screen is displayed. From this screen a site survey may be conducted, a mesh network may be created, and troubleshooting may be performed. Click the Start button for the desired function. Figure A.3 Home Screen For more information on performing a site survey, refer to Appendix B. To create a mesh network, see page 18. For help with diagnostics, refer to Appendix C. A.2.2 Opening an Existing Jobsite To open an existing jobsite: 1. Click Open from the PC Tools screen. 2. Navigate to the folder containing the jobsite file. Select to highlight the file and click Open. The existing jobsite is opened and the following screen is displayed. From this screen a site survey may be conducted, a mesh network may be created, and troubleshooting may be performed. Click the Start button for the desired function. For more information on performing a site survey, refer to Appendix B. To create a mesh network, see page 18. For help with diagnostics, refer to Appendix C. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 45 Notes 46 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Appendix B: Site Survey A site survey is recommended to assess and qualify the site prior to installing a SWIFT network. The site survey consists of a link quality test and RF scan test. After both tests are completed, the results of the site survey can be obtained using SWIFT Tools. The information provided by SWIFT Tools is used for site qualification, maximum device spacing identification, and configuring the network. This helps to improve the reliability and performance of the wireless network in the wireless fire alarm system. B.1 Conduct a Site Survey B.1.1 Link Quality Test A link quality test is a quick and repeatable test that provides immediate feedback on device connectivity. The link quality test sends data from one device to another to test for data loss and measure the signal strength. In a link test, the device addresses are set in the range of 001 to 150. A minimum of two devices are needed to conduct a link quality test. A link test is conducted between two or more devices. The link test starts when a device that is in the “pending site survey” state has its tamper condition cleared. The device will send a burst of data to the next address lower than its own address. The lower addressed device will automatically return the link quality test results for display using the device LEDs. For example, clearing the tamper condition on a detector set to address 2 (D002) will make the detector enter the link quality test. D002 will send a burst of data to a device at address 001 (either detector or module). The device at address 001 will measure the signal strength and count the data received in the burst and return the information to D002. The results of the test will be displayed at D002. The test can be repeated by tampering D002 to return it to the “pending site survey” mode and then clearing the tamper. Basic Requirements of a Link Quality Test To conduct a link test: two or more devices (detectors) are required. devices must be in factory default state. The LEDs on the device will blink single or double red to confirm it is in the factory default state. Refer to Section 3.5.4 on page 33 for more information on setting the device to factory default state. device addresses can bet set in the range of 1 to 150. Conduct a Link Quality Test To conduct a link quality test: 1. Remove the batteries from the devices that will be used for the site survey and set the SLC address. To set an SLC address, use a flathead screwdriver to adjust the rotary switches on the device. 1. For the first device used in a site survey, set the SLC address to 001. 2. For each subsequent device, use the next highest SLC address (up to address 150). For example, the first device was set to 001, set the second device to 002, and the third device to 003, etc. 2. Bring the first device (001) to the first location to conduct the test. 3. Insert one battery into the device. Inserting more than one battery deters the device from entering the site survey mode. The device is ready for site survey mode if the LED blinks yellow every 5 seconds. 4. Clear the tamper condition to proceed with the test. To clear the tamper condition on a detector, insert the detector into the base and twist to lock the detector completely into the base. To clear the tamper condition on a module, attach the faceplate to the module. When the tamper is cleared, the LEDs on the device starts blinking yellow every ½ second for approximately 20 seconds. The results appear in approximately 20 seconds and the LEDs on the first device change to solid red. This is due to the absence of a lower-addressed device with which to form a pair. This result is expected from the 1st device when a link quality test is performed. 5. Bring the second device (002) to the second location and insert one battery into the device. The device is ready for site survey mode if the LED blinks yellow every 5 seconds. 6. Clear the tamper condition to proceed with the test. To clear the tamper condition on a detector, insert the detector into the base and twist to lock the detector completely into the base. To clear the tamper condition on a module, attach the faceplate to the module. When the tamper is cleared, the LEDs on the device starts blinking yellow every 1/2 second for approximately 20 seconds. The results appear in approximately 20 seconds. 7. Repeat for subsequence devices. 8. The device will conduct a link test to the next lowest address; in this case device 001. The result of the link test from 002 to 001 is displayed by the LEDs on device 002. Refer to Table B.1 below. 9. Once the link test is complete between 002 and 001, continue for address 003, 004, etc. for all devices that will be used in the site survey. This test may be repeated any number of times. For devices addressed to 101 or higher, the test must be repeated, if desired, within five minutes of the last concluded test or the devices will start an RF scan test. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 47 Site Survey Conduct a Site Survey Results of a Link Quality Test The following table explains the LED patterns before and during a link quality test. Pattern LED Results & Description Site survey pending State Double blink every 5 seconds Red Device is tampered, ready and waiting to start a site survey link quality test Link quality test in progress Single blink every ½ seconds Yellow Transmission of data to another device. Link quality test complete On steady Red Failure - no data received Link quality test complete Single blink every 5 seconds Red Poor - partial data received or signal strength measured lower than the acceptable limit for a primary or secondary link (-81dBm or lower) Link quality test complete 2 blinks every 5 seconds Green Marginal - all data received at a signal strength acceptable for a secondary link but not for a primary link (-66dBm to -80dBm) Link quality test complete 3 blinks every 5 seconds Green Good - all data received at a signal strength acceptable for a secondary link and marginally acceptable for a primary link (-51dBm to -65dBm) Link quality test complete 4 blinks every 5 seconds Green Excellent - all data received at a signal strength acceptable for a primary link (-50dBm or better) Table B.1 LED Patterns of Link Quality Test Results The LED pattern for a link quality test will continue to be displayed until the device is tampered or the batteries die for a device that is addressed 100 or lower. For devices addressed 101 to 150, the result will be displayed until the device starts the RF Scan. To repeat the link quality test, toggle the tamper state. To toggle the tamper state on a detector, twist the detector in the base counterclockwise as if removing the detector from the base, then twist it back in clockwise to lock it in. To toggle the tamper state on a module, remove the faceplate and then reconnect it. Once the device is tampered, it will return to the pending site survey state. Once the tamper is cleared, the link quality test will be restarted. Only the results for the last link quality test are retained. After a Link Quality Test Retrieve the link quality test results for devices 001-100. To retrieve the site survey results, refer to the topicB.1.3, "Retrieving Site Survey Results"at the end of this section. For devices 101-150, wait to retrieve the link quality results until the device starts an RF Scan test. B.1.2 RF Scan Test A Radio Frequency scan test is conducted to assess and measure the background noise and interference from other wireless systems if any, in the site. The RF Scan test can be conducted individually or following the link quality test. An RF Scan test will be conducted for any device with an SLC address set between 101 and 150 at the end of a Link Quality Test. Conduct an RF Scan Test To conduct an RF scan test, follow the same procedure for a link quality test. However, the device addresses for an RF scan test must start at 101 and have the subsequent devices address set as 102, 103, etc. Each device will conduct the link quality test as described above, then transition to the RF scan test 5 minutes after the last link quality test is performed to or from that device. If several devices are being tested, it is possible that some devices will start and complete the link test and progress to the RF scan test while other devices are finishing the link quality test. The RF Scan test may take up to 70 minutes. The time remaining and the test status are displayed at the device using the LEDs. The LED patterns are shown below. Status of an RF Scan Test State Pattern In Progress- 70 minutes remaining 7 short blinks every 30 seconds In Progress- 60 minutes remaining 6 short blinks every 30 seconds In Progress- 50 minutes remaining 5 short blinks every 30 seconds In Progress- 10 minutes remaining 1 short blink every 30 seconds RF Scan Test Complete On Steady LED Status Red Bad Green Good Red Bad Green Good Red Bad Green Good Red Bad Green Good Red Bad Green Good Table B.2 RF Scan Test Status - LED Pattern 48 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Conduct a Site Survey Site Survey B.1.3 Retrieving Site Survey Results To retrieve the site survey results: 1. Return the device to “Pending Site Survey” or “Factory Default” mode. This is done by tampering devices that have completed a link quality test or by rebooting devices that have completed an RF scan test. CAUTION: SITE SURVEY RESULTS WILL BE REPLACED DO NOT CLEAR THE TAMPER ON A DEVICE THAT IS IN THE “PENDING SITE SURVEY” STATE OR THE EXISTING RESULTS WILL BE REPLACED. 2. 3. 4. Plug the USB adapter into the laptop/PC where SWIFT Tools has been installed. Bring the devices within a range of approximately 20 feet from the USB adapter connected to the laptop/PC. Logon to SWIFT Tools and retrieve the data. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 49 Notes 50 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Appendix C: Troubleshooting and Testing C.1 Troubleshooting Problem Description Action Class A fault condition Device has a single parent connection, and is missing the redundant class A connection. If a suitable parent is available, the background mesh restructuring routine should self-heal the network. If the network does not self-heal after ten minutes, reduce spacing between devices or utilize SWIFT Tools for suggested repeater placement to add stronger parents. Activate mesh formation to trigger a mesh restructuring routine to reevaluate the trouble condition after taking action. Jamming Jamming occurs when a device is overloaded with an interfering RF signal and is unable to process incoming messages, but is able to report the condition to its parents. A jammed device will automatically remove itself from the mesh network after reporting the jamming. The device will attempt to selfheal and recover into the network. Identify any possible sources of the jamming signal and see if the spacing from the device to the jamming source can be increased to an acceptable range. A site survey RF scan test can be used to categorize the jamming signal. Low battery One or more of the four batteries are missing/dead and/or the device has a minimum of one week of operation remaining. To clear the low battery event, tamper the device and replace all four batteries. When a device is tampered, it drops out of the mesh network and attempts to rejoin as soon as the batteries are replaced and the tamper event is cleared. Once a low battery trouble is indicated there is a minimum of one week of operation before the device is non-functional. Duplicate address/ Illegal address Two or more wireless devices on the same mesh Change the address of the device(s) to avoid duplication and error. network that are set to the same address report a duplicate address trouble. An address set to zero will report an illegal address. Mesh formation does not find all devices A device does not connect to the gateway/mesh network Verify the device has a profile. Verify that the profile matches the profile in the gateway. Two different profiles may use the same mesh ID. Remove and re-profile the device to guarantee the correct profile. Verify the device is powered and the tamper condition is cleared. Check the device spacing and the range from the device to the mesh. A site survey link test can be used to verify connectivity from one location to another. Mesh restructuring does The gateway/mesh network appears to be stuck not end in mesh restructuring Use SWIFT Tools to investigate for the presence of interference such as Walkie talkie/ RFID reader or unstable devices (dropping and joining). Interference such as Walkie talkie/ RFID reader will prohibit restructuring from fully executing. Devices joining a mesh will delay the restructuring event. Devices drop during operation A device drop event is indicated in history. Device drop is the predecessor to a Missing trouble. Inspect the area for any changes to the environment that could block radio communication. Use a site survey RF Scan to check for any interference and use a site survey link test to check the connectivity from the device to its closest neighbor. Max gateway trouble reported The number of Honeywell SWIFT systems that can co-exist in range of each other has been exceeded. Use the network statistics provided by SWIFT Tools to identify the interfering networks and the nature of the fault. The networks will be listed by a unique number; this is not the serial number of the gateway. One or more of the systems will need to be powered down to clear the fault. Where possible, maximize the number of devices on a mesh network to reduce the number of total mesh networks; i.e. use one mesh network with 50 devices instead of two mesh networks with 25 each. Restructure the layout of the mesh networks to group devices and the gateway to avoid overlap. It may take 36 hours for the fault to clear. This can be expedited by toggling the state of mesh formation. Device does not rejoin the mesh after battery replacement Device is an invalid reply/no answer after replacing the batteries. Verify the tamper condition is cleared. Use mesh formation to have the device rejoin the mesh network. Low battery and tamper are both latching conditions. Ensure a reset has been initiated to clear those events. Low battery trouble reported after battery replacement Low battery trouble is still indicated after replacement. Use the network statistics provided in SWIFT Tools to see the battery voltage measured for each individual battery. Verify that each battery is present and at a suitable voltage level. The low battery trouble is a latching trouble, ensure a reset has been initiated since the replacement. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 51 Troubleshooting and Testing Problem Testing the Gateway and Devices Description Action Site survey does not find a link Solid red results for the link test Verify the addresses of the devices used during the test. The lower addressed device must complete its link test before the device at the next higher address starts the link test. Verify the devices are in range of each other. SWIFT Tools does not import site survey data Selecting the device in the communicator in SWIFT Tools does not have an effect The device does not have any site survey results to be imported. It has not found a link during the link test and/or it has not collected any data for an RF Scan. Device or gateway is not communicating to SWIFT Tools says device/gateway is out of SWIFT Tools range Verify the device or gateway is powered on and in a state that supports SWIFT Tools communication. For instance, a device in the mesh network does not communicate to SWIFT Tools. It communicates to the gateway. A device that has completed a site survey does not communicate to SWIFT Tools until it returns to the pending site survey state or factory default state. Move the Adapter in range of gateway/devices. Scan does not find any devices Verify at least one device is in range of SWIFT Tools, the USB adapter is connected, and the scan is on. SWIFT Tools processes the messages faster with multiple devices in range. If only one device is in range it can take up to 1 minute for the scan to detect the device. All devices are out of range Verify the device is in the pending site survey mode or factory default mode. The device will not communicate with SWIFT Tools while it is in site survey mode. Site survey devices are not displayed in the communicator of SWIFT Tools. FACP reports Missing for the gateway Gateway is not communicating with the panel Verify the gateway is set to a valid address. FACP reports Missing for the wireless devices FACP does not recognize the detectors Verify using SWIFT Tools that the devices are part of the mesh network. Device does not receive A profile request has been initiated but timed out a profile before receiving a profile Ensure the gateway or distributor is still in distributor mode. Ensure the device is in range of the gateway or distributor. If there are multiple devices in range, the might be interfering with the profile transfer. Move the distributor and device to a different area or shut down the peripheral devices. Application download fails SWIFT Tools failed to finish a download Verify the number of devices in range of the USB adapter during the download does not exceed the recommended limit of 10 devices. Verify the device is in range and powered on during the download process. Device is in bootloader Device/Gateway is indicating the LED pattern for bootloader and it is indicated as being in bootloader in the communicator of SWIFT Tools. The device failed to load or initialize the application. Reboot the device. If it is still in bootloader, the application will need to be updated using SWIFT Tools. If problem persists, contact technical support. C.2 Testing the Gateway and Devices The gateway must be tested after installation and be part of a periodic maintenance program. The testing methods must satisfy the Authority Having Jurisdiction (AHJ). The gateway provides optimum performance when tested and maintained in compliance with NFPA 72 ordinances. C.2.1 Testing LED Indicators For more information on LED indicators, refer to Appendix D, “LED Indicators”, on page 55. C.3 Testing the Wireless Network Using the SWIFT Tools application, users can: • Diagnose and troubleshoot the wireless network and connectivity of the devices. • Monitor the wireless network topology, quality of the communication links between the devices, live and historical event reports for troubleshooting purposes. • View the parent-child relationship and the signal strength between the two devices, and identify the device that has lost the communication link with the wireless network. In addition, SWIFT Tools: • Communicates with the gateway to retrieve live information about the connectivity and status of the devices. • Stores the wireless network data such as network map, parent-child information, device information, history events, and network statistics. The SWIFT Tools application allows retrieval of the following information for diagnosing and troubleshooting purposes. • Network Topology 52 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Testing the Wireless Network • • • • Troubleshooting and Testing History of Events Network Snapshots Network Statistics Device Attributes C.3.1 Network Topology Parent-Child Devices The parent-child relationship between the devices in the wireless network is displayed using the directional arrows. Orphan Devices A device that is not linked with any other device in the wireless topology is an orphan device. The device is represented as an orphan device due to one of the following reasons: • The device was originally a part of the wireless network and was dropped. • When the network topology was retrieved, the device detail was not retrieved. • The network connections are saturated and parent-child connection with the device is not established. Class A Compliance Each device must comply with Class A guidelines. Every device must have two parent devices to be compliant with the Class A guidelines. NOTE: The device image in SWIFT Tools is altered to depict that it does not meet the required guidelines. NOTE: Class A guidelines are not applicable to the gateway. Selecting a device from the graphical representation and clicking either left or right allows you to view the following details. The Network Topology window allows you to click either left or right on any connected or orphan device. C.3.2 History Events History events of the wireless network can be retrieved and viewed using SWIFT Tools for troubleshooting purposes. This report provides information on when the device gets connected with the wireless network, mode change, and slot change details. C.3.3 Network Snapshots Network snapshots can be retrieved and viewed using SWIFT Tools for troubleshooting purposes. The network snapshot helps to analyze how the wireless network is functioning over a period of time. C.3.4 Network Statistics Network statistics of the wireless network can be retrieved and viewed using SWIFT Tools for troubleshooting purposes. The network statistics provide information on the attributes and RSSI of a device. The attributes provide information on the retransmission count and device re-join events. The retransmission count is the number of times a device retransmits the wireless signal. The device re-join events is the number of times the devices get disconnected from the wireless network and get connected with the wireless network. The RSSI of a device displays the parent-child relationship between the devices. C.3.5 Device Attributes Device attributes can be retrieved and viewed using SWIFT Tools for troubleshooting purposes. The attributes of a device such as low indication, removal indication, level, tamper fault, and others are retrieved. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 53 Notes 54 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Appendix D: LED Indicators The LED indicator patterns for the wireless gateway and wireless devices are shown in the tables below. Figure D.1 Gateway LED Patterns LED Pattern 20M 20M Condition Action Required Bootloader normal Device is ready to update Bootloader Firmware update New application code is being downloaded Mesh formation Gateway is forming the mesh and looking for devices that are not in the mesh Mesh formation with profile distribution Gateway is forming the mesh and looking for devices that are not in the mesh. The gateway is also distributing a profile to any device that requests a profile Profile removed Gateway has returned to the factory default state Solid Profile accepted Gateway is now profile assigned Solid Mesh update in progress/Mesh update -parent node Gateway is updating the mesh/Parent nodes are updating child nodes Normal mode/ background mesh restructuring Normal operation of the gateway Normal mode/ background mesh restructuring with profile distribution Normal operation of the gateway. The gateway is also distributing a profile to any device that requests a profile Rescue mode Gateway and the mesh network are searching for any device that is not in the mesh network with the same profile Rescue mode with profile distribution Gateway and the mesh network are searching for any device that is not in the mesh network with the same profile. The gateway is also distributing a profile to any device that requests a profile 10 Wait until all devices join the mesh and then terminate mesh formation Wait until all devices join the mesh and then terminate mesh formation or wait until the gateway automatically terminates mesh formation 18 3M 12 3M 12 10 Profile assigned; pending magnetic sensor activations 5M 5M Gateway is starting up with a profile Activate both magnetic sensors simultaneously within 10 seconds to remove a profile 1st mesh restructuring Mesh is formed and initializing Ensure all devices in the mesh have a valid address 1st mesh restructuring with profile distribution Mesh is formed and initializing. The gateway is also distributing a profile to any device that requests a profile. Legend Example: Two blinks in this pattern Number of blinks LED color Interval between blink patterns Duration of LED state Indicates value is approximate First blink is green, Second is yellow 20M 7 seconds between blink patterns Will transition to next state after approximately 20 minutes All units are in seconds. Minute is indicated by “M”. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 ledgate1_3.0.wmf 18 55 Figure D.2 Gateway LED Patterns (Continued) LED Pattern Condition Action Required Normal mode The gateway is in the mesh and may be in trouble Refer to the FACP to identify the trouble and possible solution Normal mode with profile distribution The gateway is in the mesh and is also distributing a profile to any device that requests a profile. The gateway may be in trouble Refer to the FACP to identify the trouble and possible solution 18 18 3M Gateway and the mesh are searching for any device that is not in the mesh network with the same profile. The gateway may be in trouble Rescue mode with profile distribution Gateway and the mesh are searching for any device that is not in the mesh network with the same profile. The gateway is also distributing a profile to any device that requests a profile. The gateway may be in trouble 12 12 Address zero trouble The gateway address is set to zero Mesh update ready Received command from SWIFT Tools to start a firmware update Gateway is starting up without a profile Factory default; pending magnetic sensor activation 10 Waiting for a profile Gateway is in factory default mode Solid 10 60 Searching for a 0.5 profile Gateway is in factory default mode and requesting a profile from a distributor or another gateway Normal mode/ background mesh restructuring Gateway is in the mesh 18 Normal mode/ background mesh restructuring with profile distribution Gateway is in the mesh. The gateway is also distributing a profile to any device that requests a profile 12 Rescue mode Gateway and the mesh network are searching for any device that is not in the mesh network with the same profile Rescue mode with profile distribution Gateway and the mesh network are searching for any device that is not in the mesh network with the same profile. The gateway is also distributing a profile to any device that requests a profile 12 Legend Example: Number of blinks Two blinks in this pattern First blink is green, Second is yellow LED color Interval between blink patterns Duration of LED state Indicates value is approximate All units are in seconds. Minute is indicated by “M”. 56 Use SWIFT Tools to assign a profile or activate magnetic sensor to search for a profile Gateway is creating a profile 18 3M Activate either magnetic sensor within 10 seconds to create a profile Create profile 3M Ensure all devices in the mesh have a valid address 20M 7 seconds between blink patterns Will transition to next state after approximately 20 minutes ledgate2_3.0.wmf 3M Rescue mode SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Figure D.3 Device LED Patterns LED Pattern Condition Action Required Bootloader normal Device is ready to update Use SWIFT Tools to initiate download Slot request rejected Device is not permitted into the mesh Confirm device count and software version Mesh forming Device is part of the mesh and looking for devices that are not in the mesh Sustained tamper Device is tampered Bootloader firmware update New application code is being downloaded Profile removed Device has returned to the factory default mode Profile received Device now has a profile assigned Battery check: all batteries are fresh Maximum battery life remaining in device Distributor mode Device is distributing its profile to other devices which requested a profile. Active/Alarm state Device has been activated Rescue mode Device is in the mesh and looking for lost devices Normal mode or tested walktest Device is in the mesh or it has been tested in a walktest. Mesh update -parent node The gateway is updating parent nodes in the mesh 20M Ensure detector is seated in the base and the module has the faceplate on 15 Solid 10 Solid 2.5 0.5 3M 12 18 Solid 10 Mesh update idle Mesh updating Solid Devices that are included in mesh update are complete and waiting for the whole mesh to finish updating Green and yellow flicker pattern indicates that data packets are being received by the device. Self test fail Device has failed internal self diagnostics. Active/Alarm state Device has been activated Low battery cut-off Device is functioning. Restart the device. If problem persists, contact technical support Replace batteries Example: Legend Two blinks in this pattern Number of blinks LED color Interval between blink patterns Duration of LED state Indicates value is approximate All units are in seconds. Minute is indicated by “M”. First blink is green. Second is yellow 20M 7 seconds between blink patterns Will transition to next state after approximately 20 minutes SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 leddev1_3.0.wmf 57 LED Indicators Figure D.4 Device LED Patterns (Continued) LED Pattern Condition Action Required 3M Device is in the mesh and looking for lost devices Device may be in trouble Refer to the panel to identify the trouble and possible solution Profile modification Device has a profile and can be set as a distributor or have profile removed Use SLC address dials to enter desired mode. Battery Check: all batteries present Minimum of 6 months battery life remaining Searching for mesh (in rescue mode) Profile is assigned and device is searching for the mesh. Ensure the mesh is in rescue mode or wait for timeout to search mesh in formation mode. Searching for mesh (in formation mode) Profile is assigned and device is searching for the mesh Ensure the mesh is in formation mode 1st mesh restructuring Mesh is formed and initializing Normal mode Device is in the mesh and may be in trouble Refer to the FACP to identify the trouble and possible resolution. Tamper entry Device has just been tampered Ensure detector is seated in the base and the module has a faceplate Discovered mesh Device discovered the mesh Normal mode Device is in the mesh Rescue mode Device is in the mesh and looking for lost devices Battery Check: weak Less than 6 months battery life left or not all 4 batteries are present Active/Alarm state Device has been activated Waiting for a profile Device is in factory default mode Searching for a profile Device is in factory default mode and requesting a profile from a distributor or gateway 60 12 Solid 2.5 90 25 5M Rescue mode 18 Solid Solid 18 5M 12 Solid 2.5 Ensure all 4 batteries are present or replace the batteries Use SWIFT Tools to assign a profile or activate magnetic sensor to search for a profile. 10 0.5 Pending site survey Legend Device is in factory default mode and is ready to enter site survey mode Example: Interval between blink patterns Duration of LED state Indicates value is approximate All units are in seconds. Minute is indicated by “M”. 58 Two blinks in this pattern Number of blinks LED color Clear the tamper condition within 1 minute to enter site survey mode First blink is green. Second is yellow 20M 7 seconds between blink patterns Will transition to next state after approximately 20 minutes leddev2_3.0.wmf 1M SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Appendix E: Firmware Upgrade/Downgrade Instructions To ensure proper system operation, this product must be tested in accordance with NFPA 72 after any programming operation or change in site-specific software. E.1 W-USB Adapter Upgrade Procedure The following procedure provides firmware upgrade instructions for the W-USB adapter. Ensure the latest version of SWIFT Tools is installed. SWIFT Tools and firmware can be downloaded from www.farenhyt.com. There are multiple .bin files with the zip file. Save the files to a folder. 1. Insert the W-USB adapter into the PC. 2. Launch SWIFT Tools and navigate to the home screen and select either Site Survey, Create Mesh Network, or Diagnostics. 3. SWIFT Tools will detect the connected USB adapter and will show an incompatibility message. Click on the OK button to dismiss the message. 4. Click on the Operations icon and navigate to Operations > Firmware Update > USB Adapter. 5. Click Browse and navigate to the folder with the saved firmware. Select the file named “USBAdaptorVx.xxx.bin”. 6. 7. Click Update. The progress status box will show “Updating,” followed by “Updated”. Once the firmware update process completes SWIFT tools displays a message indicating that the W-USB adapter has been successfully upgraded. E.2 Gateway Firmware Upgrade/Downgrade Procedure The following procedure provides firmware upgrade and download instructions for the gateway. Ensure the latest version of SWIFT Tools is installed. SWIFT Tools and firmware can be downloaded from www.farenhyt.com. There are multiple .bin files with the zip file. Save the files to a folder. 1. Launch SWIFT Tools and navigate to the home screen and select either Site Survey, Create Mesh Network, or Diagnostics. 2. Ensure gateway is in range of W-USB adapter and the PC running SWIFT Tools. 3. Click on the Extras icon and navigate to Extras > Firmware Update > Wireless Devices. 4. Go to the Gateway area of the upgrade. The gateway has two microprocessors that need to be upgraded. 5. Under “Select RF app update file”, click on the Browse button. 6. Navigate to the folder with the saved firmware. Select the “WSG_RF_xx.xx.xx.bin” file. 7. Select the gateway and click the Update button on the bottom of the screen. 8. Follow the window prompts. The download should take approximately 4 minutes to complete. 9. Click the refresh button at the bottom of the window and Remove before starting the next download. Repeat the same steps for the SLC app file. 10. Under the “Select SLC app update file”, click on the Browse button. 11. Navigate to the folder with the saved firmware. Select the “WSG_SLC_xx.xx.xx.bin” file. SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 59 Firmware Upgrade/Downgrade Instructions Device Firmware Upgrade/Downgrade Procedure 12. Select the gateway and click the Update button on the bottom of the screen. 13. Follow the window prompts. The download should take approximately 4 minutes to complete. E.3 Device Firmware Upgrade/Downgrade Procedure The following procedure provides firmware upgrade and download instructions for the wireless devices. Ensure the latest version of SWIFT Tools is installed. SWIFT Tools and firmware can be downloaded from www.farenhyt.com. There are multiple .bin files with the zip file. Save the files to a folder. 1. If the device is current in a mesh network, power down the gateway. Devices can only be updated when they are in direct communication with SWIFT Tools. 2. Launch SWIFT Tools and navigate to the home screen and select either Site Survey, Create Mesh Network, or Diagnostics. 3. Ensure devices are in range of W-USB adapter and the PC running SWIFT Tools. 4. Click on the Extras icon and navigate Extras > Firmware Update > Wireless Devices. 5. Go to the Detectors and Modules area of the upgrade. 6. 7. Under “Select the update file”, click on the Browse button. Navigate to the folder with the saved firmware. Select the “WDV_RF_xx.xx.xx.bin” file. The application file for a device is the same for all detector types and module types. 8. Select the devices and click the Update button on the bottom of the screen. Only permitted devices with a matching hardware revision and device type will be selectable. Multiple devices can be selected, and they will be updated sequentially. 9. Follow the window prompts. The download should take approximately 4 minutes to complete. 10. Repeat until all devices in the mesh are operating with the same firmware version. 60 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Index abbreviations 9 additional references 8 assign profile 31, 35 assumed knowledge 8 attributes 53 bootloader 21, 35 Class A compliance 53 class A fault 36 clear tamper 36 collapse network command 22 configuration 15 configure profile 20 CR123A batteries 29 create profile 15 creating jobsite 45 detector assign profile 31 transfer profile 31 device attributes 53 bootloader 35 distributor 35 factory default 35 initial mesh restructuring mode 35 LED indicators 36 mesh formation 35 mesh participant 35 network snapshots 53 network statistics 53 normal mode 35 profile assigned 35 rescue mode 35 site survey 35 device indication 36 device initialization 37 device operations 35 device spacing 47 devices 29 Class A compliance 53 configuration and programming 31 installing 30 orphan 53 parent-child 53 disable trouble reporting 22 distributor 35 distributor mode 33 dongle 40 duplicate address 36 event reporting 19 existing profile 16 factory default 20, 33, 35 gateway 10 bootloader 21 collapse network 22 configuration 15 create mesh network 16 description 10 disable trouble reporting 22 existing profile 16 factory default 20 initial mesh restructuring 20 LED indicators 11 lock/unlock 21 mesh formation 18, 20 mesh restructuring 20 mesh upgrade 21 mounting 12 neighboring network scan 21 new profile 15 normal mode 20 password reset 22 power 14 profile configure 20 profile distribution 18 programming 15 remove profile 16 rescue mode 20 restrictions 24 RF interference 26 silence network 23 SLC configuration 19 SLC connections 14 specifications 10 start-up 19 weak link trouble 22 wiring 13 LED indicators 11, 15, 16, 36 link quality test 47 procedure 47 requirements 47 lock 21 low battery 36 magnetic sensor 11, 16, 18, 19, 33 mesh formation 16, 18, 20, 33, 35 mesh network 16, 19 mesh participant 35 mesh restructuring 20 mesh upgrade 21 modes of operation 19, 35 module assigning profiles 31 batteries 29 module configuration 31 module installation 30 monitor module 29 mounting 12 neighboring network 21 neighboring network scan 21 network installation restrictions 24 network limit 24 network snapshots 53 network statistics 53 network topology 53 no answer 37 normal mode 20, 35 opening jobsite 45 operations 19 orphan devices 53 overlapping networks 24 heat detector 29 panel indication 36 parent-child devices 53 password reset 22 profile assigned 35 configure 20 create new 15 remove 17, 33 removing 16 profile distribution 18 programming 15 pull station 29 initial mesh restructuring 20 initial mesh restructuring mode 35 initialization 37 installing devices 30 interference 26 isolator modules 14 jamming 37 jobsite new 45 open 45 jumper 12 related documents 8 remove profile 16, 17, 33 repeater 36 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 61 Index rescue mode 20, 35 restrictions 24 installation 24 RF interference 26 RF scan test 48 status 48 RF spectrum 24 rotary switches 34 sensor magnetic 16 silence network command 23 site survey 35, 47 SLC configuration 19 SLC connections 14 smoke detector 29 specifications 10, 40 spectrum 26 RF 24 spread 26 spread spectrum 26 start-up 19 SWIFT Tools 44, 52 tamper 36 clear 36 testing 52 transfer profile 31 transmission 20 trouble condition 20, 22 trouble reporting disable 22 troubleshooting 51 unlock 21 upgrade mesh 21 USB adapter 40 specifications 40 walkie talkie mode 26 weak link 36 trouble reporting 22 WIDP-WGI 10 specifications 10 wireless devices 29 wireless gateway 10 wiring 13 62 SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 Manufacturer Warranties and Limitation of Liability Manufacturer Warranties. Subject to the limitations set forth herein, Manufacturer warrants that the Products manufactured by it in its Northford, Connecticut facility and sold by it to its authorized Distributors shall be free, under normal use and service, from defects in material and workmanship for a period of thirty six months (36) months from the date of manufacture (effective Jan. 1, 2009). The Products manufactured and sold by Manufacturer are date stamped at the time of production. Manufacturer does not warrant Products that are not manufactured by it in its Northford, Connecticut facility but assigns to its Distributor, to the extent possible, any warranty offered by the manufacturer of such product. This warranty shall be void if a Product is altered, serviced or repaired by anyone other than Manufacturer or its authorized Distributors. This warranty shall also be void if there is a failure to maintain the Products and the systems in which they operate in proper working conditions. MANUFACTURER MAKES NO FURTHER WARRANTIES, AND DISCLAIMS ANY AND ALL OTHER WARRANTIES, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THE PRODUCTS, TRADEMARKS, PROGRAMS AND SERVICES RENDERED BY MANUFACTURER INCLUDING WITHOUT LIMITATION, INFRINGEMENT, TITLE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. MANUFACTURER SHALL NOT BE LIABLE FOR ANY PERSONAL INJURY OR DEATH WHICH MAY ARISE IN THE COURSE OF, OR AS A RESULT OF, PERSONAL, COMMERCIAL OR INDUSTRIAL USES OF ITS PRODUCTS. This document constitutes the only warranty made by Manufacturer with respect to its products and replaces all previous warranties and is the only warranty made by Manufacturer. No increase or alteration, written or verbal, of the obligation of this warranty is authorized. Manufacturer does not represent that its products will prevent any loss by fire or otherwise. Warranty Claims. Manufacturer shall replace or repair, at Manufacturer's discretion, each part returned by its authorized Distributor and acknowledged by Manufacturer to be defective, provided that such part shall have been returned to Manufacturer with all charges prepaid and the authorized Distributor has completed Manufacturer's Return Material Authorization form. The replacement part shall come from Manufacturer's stock and may be new or refurbished. THE FOREGOING IS DISTRIBUTOR'S SOLE AND EXCLUSIVE REMEDY IN THE EVENT OF A WARRANTY CLAIM. Warn-HL-08-2009.fm SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000FH-E:B 11/9/2017 63 Honeywell Silent Knight 12 Clintonville Road Northford, CT 06472-1610 203.484.7161 www.silentknight.com LS10036-000SK-E | B | mm/yy ©2017 Honeywell International Inc.
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : Yes XMP Toolkit : Adobe XMP Core 5.6-c015 84.159810, 2016/09/10-02:41:30 Format : application/pdf Title : SWIFT.book Creator : e654944 Create Date : 2017:11:09 09:18:18Z Creator Tool : FrameMaker 2017 Modify Date : 2017:11:09 09:48:30Z Producer : Acrobat Distiller 17.0 (Windows) Document ID : uuid:04135e8d-fde6-479f-81f1-141f3e98b875 Instance ID : uuid:72eeb896-b572-40c8-a79e-dadef92f19de Page Mode : UseOutlines Page Count : 64 Author : e654944EXIF Metadata provided by EXIF.tools