User Manual

Scorpion I IIIAR Reader
10

Copyright 2001
RF Code, Inc.
Problem Analysis
This is a brief list of potential problems, with possible solutions, that may be
encountered while using the Scorpion I Reader. If the problem cannot be
resolved using this remedy chart, please call the distributor from which you
obtained the Scorpion I System for help in resolving the problem.
Condition Symptom Remedy
There are no tags being
read at the reader
!
The reader power light is off
!
Plug in the reader power pack
!
Turn on the reader power switch
There are no tags being
read at the reader.
!
The reader power light is on
!
The reader detect light is flashing
on and off at a regular interval
!
The reader is in standby mode and
needs to be configured and
enabled for operation.
There are no tags being
read at the reader.
!
The reader has power but is
unresponsive to system
communications or remote restart
commands.
!
Verify the LAN is connected and
the Client Bridge can be “Pinged”
There are no tags being
read at the reader. The
reader has been
configured and enabled.
!
The reader power light is on
!
The reader detect light is not
flashing
!
The system is receiving the “status”
message from the reader.
!
Verify the antennas are attached to
the reader and / or move the tags
closer to the reader.
!
Change the range setting on the
reader to a longer range to see the
available tags.
!
Verify the communication medium
between the reader and the
computer is operational.
!
Verify that the configured group
code is the same as the tags being
read.
!
Verify the computer program is
setup correctly to receive tag IDs.
Tag IDs do not drop off
the computer display
when the tags are moved
away from the reader
!
The ¼ wave helical antenna(s) are
installed on the reader
!
Change the reader’s range setting
to a shorter range.
!
Verify that the data path from the
reader to the computer is
functional
The Scorpion I Reader
reports erratic tag
movement in Exception
mode.
!
Reports normal tag information
while in Continuous mode.
!
Verify that the tag timeout time is
configured 25% larger than the
transmission interval from the tag.