Datalogic Falcon 4420 48-Key Quick Reference page 46

Troubleshooting
Problem
During data
communication, no data
was transmitted, or
transmitted data was
incomplete.
The Falcon does not accept
scan input.
The UPC/EAN extension
(supplemental label) is not
always scanned.
44
Possible Cause
The Falcon was removed from
the dock or unplugged from host
PC during communications.
Incorrect cable configuration.
Communication software was
incorrectly installed or config-
ured.
The scanning window is dirty.
The scanning application is not
loaded.
Unreadable bar code.
Distance between exit window
and bar code is incorrect.
The Falcon is not programmed
for that symbology.
The Falcon is not programmed
to generate a beep.
Battery is low.
Laser beam only crosses over
base of UPC/EAN label.
Solution
Replace the terminal in the dock, or replace the serial
cable, and retransmit.
See your System Administrator.
Perform setup as described in the PRG.
Carefully wipe the scanning window with a soft, clean
cloth. Do not use abrasive cleaners.
Verify that the unit is loaded with a scanning applica-
tion. See your System Administrator.
Be sure the symbol is not defaced.
Be sure you are within proper scanning range.
Be sure the terminal is programmed to accept the type
of bar code you are scanning. Try using
on maximum defaults, as described in "Programming
Parameters" in the Falcon 4400 PRG.
If you are expecting a beep on a good decode and
don't hear one, check that the application is set to gen-
erate a beep on good decode.
> Settings > System > Decoding > Gen-
Tap
eral > Audio
OR
Scan the appropriate bar code from the PRG.
If the scanner stops emitting a laser beam when you
press the trigger, check your battery level. Refer to the
PRG.
Note: If the scanner is still not reading sym-
bols, contact your distributor or Datalogic.
Read Verification
Set the
0528) to a value lower than the
the base label. See the PRG.
4400 Series with Windows Mobile ®
®
Falcon
FF3A
to turn
for extensions (parameter
Read Verification
for