Filter
Top Products
Troubleshooting
44 Falcon
®
4400 Series with Windows Mobile
®
During data
communication, no data
was transmitted, or
transmitted data was
incomplete.
The Falcon was removed from
the dock or unplugged from host
PC during communications.
Replace the terminal in the dock, or replace the serial
cable, and retransmit.
Incorrect cable configuration. See your System Administrator.
Communication software was
incorrectly installed or config-
ured.
Perform setup as described in the PRG.
The Falcon does not accept
scan input.
The scanning window is dirty. Carefully wipe the scanning window with a soft, clean
cloth. Do not use abrasive cleaners.
The scanning application is not
loaded.
Verify that the unit is loaded with a scanning applica-
tion. See your System Administrator.
Unreadable bar code. Be sure the symbol is not defaced.
Distance between exit window
and bar code is incorrect.
Be sure you are within proper scanning range.
The Falcon is not programmed
for that symbology.
Be sure the terminal is programmed to accept the type
of bar code you are scanning. Try using
FF3A to turn
on maximum defaults, as described in “Programming
Parameters” in the Falcon 4400 PRG.
The Falcon is not programmed
to generate a beep.
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.
Tap > Settings > System > Decoding > Gen-
eral > Audio
OR
Scan the appropriate bar code from the PRG.
Battery is low. 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 PSC Inc.
The UPC/EAN extension
(supplemental label) is not
always scanned.
Laser beam only crosses over
base of UPC/EAN label.
Set the
Read Verification for extensions (parameter
0528) to a value lower than the
Read Verification for
the base label. See the PRG.
Problem Possible Cause Solution