Honeywell International Inc. WFSSM Manuale Utente
SWIFT® Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000SK-E:B 11/9/2017
27
Operations
WSK-WGI Wireless System Gateway
2.9.10 Trouble MessagesDistributed Firmware Updates
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:
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.
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:
Phase 1 - Mesh upgrade preparation:
Trouble Message
Type
Description
Course of Action
RF JAMMING or
JAMMING
JAMMING
Non-latching
The gateway is being overloaded
with RF energy and is unable to
receive messages from other
devices.
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.
gateway and remove them or relocate the gateway.
SOFTWARE MISMATCH
or SOFTWARE
or SOFTWARE
Non-latching
Software mismatch between the
application code for the RF
processor and the SLC processor.
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.
update the processors as necessary for compatibility.
RF MESH FORMING or
RF MESH
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.
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.
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
or RF MESH
Non-latching
The gateway contains a profile but
has not formed a mesh.
has not formed a mesh.
RF MESH REFORMING or
RF MESH
RF MESH
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.
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.
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.
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.
gateway before a mesh can be formed.
ADDRESS FAULT or
ADDR FAULT
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.
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.
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 Silent Knight
wireless systems being exceeded.
is compromised due to the
installation limits of Silent Knight
wireless systems being exceeded.
Investigate for overlapping or adjacent wireless
systems produced by Silent Knight. 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 Silent Knight wireless
system.
systems produced by Silent Knight. 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 Silent Knight wireless
system.
RF DEVICE NO ANSWER
or DEV NO ANS
or DEV NO ANS
Latching trouble; remains
active for the first 90
seconds before it can be
cleared with a system
reset.
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.
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.
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
!
CAUTION: NO FIRE PROTECTION
DURING THE UPDATE, THE MESH NETWORK WILL NOT PROVIDE FIRE PROTECTION.
DURING THE UPDATE, THE MESH NETWORK WILL NOT PROVIDE FIRE PROTECTION.