Honeywell International Inc. WFSPS Manuale Utente

Pagina di 64
28
SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000NF-E:E 11/9/2017
FWSG FlashScan Wireless System Gateway
Operations
2.9.10  Trouble Messages
Events History Messages
NFS2-3030
NCA-2
Onyxworks
NFS2-640
NFS-320
Type
Description
Course of Action
RADIO JAMMING
JAM
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.
INCOMPAT SOFT
IN SFT
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.
MESH IS 
FORMING
MS FRM
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.
MESH NOT 
FORMED
NOMESH
Non-latching
The gateway contains a profile but 
has not formed a mesh.
RESTRUCTURING RSTRCT
Non-latching
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.
PROFILE MISSING PR MIS
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.
NO WIRELESS 
DEVS
NO DEV
Non-latching
The gateway is functional but is not 
in communication with any 
wireless devices.
Verify the desired wireless devices are in range, have 
matching profiles assigned, have fresh batteries, and 
are not in the tampered condition. Initiate “Mesh 
Formation mode” to actively search for devices.
ADDRESS FAULT
ADRFLT
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.
MAX GATEWAYS
MAX GW
Non-latching
Wireless communication reliability 
is compromised due to the 
installation limits of Notifier 
wireless systems being exceeded 
or system latency is compromised 
due to the lack of mesh-to-mesh 
synchronization.
Utilize SWIFT Tools to retrieve additional information 
required for detecting faults and making corrections. 
Investigate for overlapping or adjacent wireless 
systems produced by Notifier. Reduce the instances 
of overlap by removing systems, or devices in the 
overlapping region. Refer to Section 2.9.7 on th
installation limits for the Notifier wireless system. 
RF DEV NO 
ANSWER
RF DEV
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
NFS2-3030
Description
PR
A profile has been received, assigned by either SWIFT Tools or a distributor device.
PC
A profile has been created.
Table 2.2  Events History Messages