Appendix C: Troubleshooting And Testing; C.1: Troubleshooting - Johnson Controls SWIFT Instruction Manual

Appendix C: Troubleshooting and Testing

C.1 Troubleshooting
Problem
Class A fault condition Device has a single parent connection, and is
missing the redundant class A connection.
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.
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.
Duplicate address/ Two or more wireless devices on the same
Illegal address mesh 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 A device does not connect to the
not find all devices gateway/mesh network
Mesh restructuring does The gateway/mesh network appears to be
not end stuck in mesh restructuring
Devices drop during A device drop event is indicated in history.
operation
SWIFT™ Smart Wireless Integrated Fire Technology Manual — P/N LS10036-000JC-E:C 5/8/2015
Description Action
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.
Toggle mesh formation to trigger a mesh restructuring
routine to re-evaluate the trouble condition after taking
action.
A jammed device will automatically remove itself from
the mesh network after reporting the jamming. The
device will attempt to self-heal 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.
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.
Change the address of the device(s) to avoid duplication
and error.
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.
Use SWIFT Tools or panel history to investigate for the
presence of walkie talkie interference or unstable
devices (dropping and joining). Walkie talkie
interference will prohibit restructuring from fully
executing. Devices joining a mesh will delay the
restructuring event.
Device drop is the predecessor to a No Answer/Invalid
reply 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.
55