Maintenance & Troubleshooting 10 - 9
The wearable terminal
does not accept scan
input.
Scanning application
is not loaded.
Verify that the unit is loaded with a scanning application. See
the System Administrator.
Unreadable bar code. Ensure the symbol is not defaced.
Distance between exit
window and bar code
is incorrect.
Ensure wearable terminal is within proper scanning range.
Wearable terminal is
not programmed for
the bar code.
Ensure the wearable terminal is programmed to accept the
type of bar code being scanned.
Wearable terminal is
not programmed to
generate a beep.
If a beep on a good decode is expected and a beep is not
heard, check that the application is set to generate a beep on
good decode.
Battery is low. If the scanner stops emitting a laser beam when the trigger is
pressed, check the battery level. When the battery is low, the
scanner shuts off before the wearable terminal low battery
condition notification.
Note: If the scanner is still not reading symbols, contact the
distributor or Zebra.
Wearable terminal goes
into IPL mode after cold
boot.
Headset adapter
without a headset is
connected to the
wearable terminal
during a cold boot.
Disconnect the headset adapter prior to performing a cold
boot.
Scanner trigger is held
down during a cold
boot.
Do not press trigger during a cold boot.
P1 or P2 key is held
down during a cold
boot.
Do not press the P1 or P2 key during a cold boot.
If all three LEDs are lit
solid.
Voice Only WT4090 is
in IPL mode.
Perform cold boot. See
Resetting the Wearable Terminal on
page 1-8
.
WLAN connection is lost
when the
wearable
terminal
is connected to
a host computer using
ActiveSync.
Microsoft security
feature prevents
connection to two
separate networks.
Disconnect from the WLAN network prior to connecting to a
host computer using ActiveSync.
Table 10-1
Troubleshooting the Wearable Terminal (Continued)
Problem Cause Solution
To Next Page
Loading...
