Technical information

AccuLazr™ AL5010 Product Line Manual Troubleshooting 123
08-AL5010_Troubleshooting_R20.doc Accu-Sort Systems, Inc.
System Counters Log View
You can display a number of values and counters that indicate whether the
AL5010 is configured and operating properly by clicking the System
Counters button. You can also enter DISPCOUNTERS in the command field
and click Send.
Scan Rate and Belt Speed System Counters
Description
Scan Rate This is the total number of scans/second that the AL5010 is reading.
Note the this number does NOT take into account “laser toggling” if
it is enabled. If “laser toggling” is enabled, the effective scan rate for
any laser is half of this value.
Belt
Speed
(tracking) Speed of the belt (in ft/min) as measured by the
tachometer.
Bar Code Counters
Bar Code
Counters
Description
Triggers Total number of packages based on the trigger signal. In
self-trigger mode, this will match the number of good reads.
Good Reads Total number of bar codes read and transmitted. If the
AL5010 is set up to read multiple bar codes each trigger,
this counter is incremented for each bar code read.
No Reads Total number of bar codes that were not read.
Mult Codes Total number of instances where more bar codes of a
specific type were read than expected. This counter will also
increment, regardless of whether the AL5010 is configured
to report “multiple codes” as an error.
Match Codes Total number of bar codes that matched any of the Match
Code criteria.
Bad ModChk Total number of bar codes that were rejected due to an
invalid Mod Check.
Error Counters
Error Counters Description
Xfter Ovrflw Transfer Overflow. This counts the number of codes that
were lost due to an overflow in the transfer buffer between
the Decode/DSP processor and the AL5010/ARM
processor.
Xfer BadLen Transfer Bad Length. Number of codes in the transfer buffer
than contained an invalid length, indicating some sort of
memory corruption.
QData@TX Queue Data at Transmit (non-tracking). This counter
indicates that the AL5010 had not completed processing all
of the scan data at the user specified transmit time. This will
only happen if the “transmit time” parameter is set to a value
other than zero. This does not necessarily indicate an error,
but does indicate that either the transmit time is too short or
the AL5010 is seeing a lot of data which may be the result of
too much background noise.
QData@Trig Queue Data at Trigger (non-tracking). This counter
indicates that the AL5010 had not completed processing all
of the scan data prior to the start of the next trigger. This
typically can only happen when the “transmit time”
parameter is set to zero; although it can also happen in
conjunction with a Force Transmit. As with the Queue Data
at Transmit counter, this does not necessarily indicate an
error, but it likely indicates that the AL5010 is seeing a lot of
data which may be the result of too much background noise.