Quick Start Guide

Page | 29
© 2018 Intelligent Automation, Inc.
7 Troubleshooting
Problem: A link is generating too many false alarms (i.e., false positives)
Possible Solutions:
Do not position either end of a link close to human activity that should not trigger the fence.
Moving close to either node may trigger the link, even if not physically in between the two
nodes. Try adjusting the location of one or both of the nodes.
Make sure the link does not try to pass through any highly RF reflective/absorptive materials
(metal, cinder block, etc.). If so, move one or both ends of the link to avoid the obstruction.
Note that RF signals will bounce off of nearby hard surfaces (metal, sides of buildings, etc.), so
the region of sensitivity may be larger than simply the straight line between two nodes.
Similarly, nearby moving metallic objects (moving cars, opening doors, etc.) may trigger the link.
If this is not desired, try slightly repositioning one or both ends of the link.
Problem: A link is not triggering when it should (i.e., false negatives)
Possible Solutions:
Just as nearby reflective objects may cause false alarms (see above), it is also possible that these
objects could prevent some actual triggers by spreading the RF energy over too wide an area.
Try slightly repositioning one or both ends of the link.
Problem: The system is non-responsive (i.e., no triggers)
Possible Solutions:
Make sure all of the deployed ARGUS GUARDIAN nodes are powered on. If node is
unresponsive, its battery are probably discharged replace with fully charged battery.
Make sure the Gateway node is plugged in. If you unplug and replug the gateway, it may take
several minutes for the nodes to rejoin the network.
If the USB cable was jostled during operation, the serial connection to the Gateway Node may
have been lost. Try shutting down the ARGUS GUARDIAN software, unplug and re-plug the USB
cable, and then restart the ARGUS GUARDIAN software.
Click on the link health button to view status of links. If link status labels displays 0 (zero), reset
all nodes and the user interface.