Honeywell International Inc. WFSRM Manuale Utente
42
SWIFT™ Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000NF-E:C 5/8/2015
Wireless Devices
Device Operations
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.
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 180 seconds before it can be removed with a system reset. Once the event is
removed, the device reports a “NO ANSWER” or “INVREP” until the device is restored or the
point is removed from the database.
event is active for 180 seconds before it can be removed with a system reset. Once the event is
removed, the device reports a “NO ANSWER” or “INVREP” 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 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.
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 fol-
lowing color patterns that denote the battery status.
•
lowing color patterns that denote the battery status.
•
Green - All the four batteries are installed and fresh. The device has a minimum one year of
normal operation.
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.
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.
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.
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 “NO ANSWER”, “NO ANS”, or “INVREP” message at
the FACP. Follow the steps in “Mesh Formation Mode” on page 40 to have a device join the mesh.
the FACP. Follow the steps in “Mesh Formation Mode” on page 40 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 “INIT MODE” or “INIT” during a device initial-
ization condition.
of performing fire protection. This is the case for mesh networks that are still forming or going
through initial restructuring. The panel displays “INIT MODE” or “INIT” during a device initial-
ization condition.
3.6.4 Background Events
The following conditions are not considered a trouble, supervisory, or alarm condition. These
events are stored in the history of the NFS2-3030 FACP only.
events are stored in the history of the NFS2-3030 FACP only.
Pre-Class A Fault
A device will report a pre-Class A event when it first identifies a single connection path condition.
If the connection path is not restored or replaced with another viable connection path within 180
seconds, a Class A fault condition will be reported. The history event reports this condition as
“PRE-CLASS A FAULT”.
If the connection path is not restored or replaced with another viable connection path within 180
seconds, a Class A fault condition will be reported. The history event reports this condition as
“PRE-CLASS A FAULT”.
Device Drop
A device will report a device drop if it has lost complete communication with the mesh network. If
the device does not recover in 180 seconds or less, a “NO ANSWER” or “INVREP” trouble is
reported for the address. The history event will report as a “DEVICE DROPPED”.
the device does not recover in 180 seconds or less, a “NO ANSWER” or “INVREP” trouble is
reported for the address. The history event will report as a “DEVICE DROPPED”.
Weak Link
When weak link reporting is enabled by the gateway and disabled in the FACP, then all weak link
conditions will be entered as background events in history. The history event is reported as a
“WEAK LINK FAULT” or “WEAK” for a device that is in the weak link condition.
conditions will be entered as background events in history. The history event is reported as a
“WEAK LINK FAULT” or “WEAK” for a device that is in the weak link condition.