RHINO™
24
5
5 TROUBLESHOOTING
CAUTION
The only internal components that personnel not belonging to Datalogic or
ARC technical support can add or replace by removing Rhino™'s cover
are PCMCIA cards as described in chapter 1.8.
Opening Rhino™ may damage internal components and causes warranty
loss.
Before sending Rhino™ to technical support, the Customer has the responsibility of saving
every data and every configuration that have been stored. Datalogic's only responsibility is
the recovery of the exact hardware configuration of Rhino™.
Problem Possible
Solution
Rhino™ does not respond to any
type of input (keyboard entry,
barcode scanning).
Wait some minutes, since the timeout of TCP/IP may
be waiting for a transaction occurred in an area with no
radio coverage (during such timeouts Rhino™ is
suspended). Timeout normally takes 2 minutes.
If problem persists, reset Rhino™ using the following
sequence:
CTRL+ALT+FUNC+BKSP
If problem still persists, switch Rhino™ off then switch
it on again.
Rhino™ is not on and the red LED
on keyboard is not on.
Ensure that Rhino™ is correctly powered.
Check fuse's integrity.
Rhino™ is not on despite the red
LED on keyboard goes off.
Contact the nearest Datalogic distributor for technical
assistance.
When rebooting Rhino™, an error
message appears:
"RADIO ERROR".
Check configuration correctness, since one of the
following conditions may have occurred:
-
some files may have been deleted
- an incorrect driver may have been loaded for the
Radio PCMCIA card mounted (please also refer to
the driver and DL Mobile Configurator™ manuals)
-
the radio may be broken
- WEP may have been enabled on CISCO card
without any previous activation of at least one WEP
key (please also refer to the driver's manual)
The boot seems to be correct, but
Rhino™ does not connect to the
wireless LAN or cannot reach the
host.
Check configuration correctness, since one of the
following conditions may have occurred:
-
Rhino™ is out of access point coverage area;
-
radio configuration files (SSID, Wep Encription,
safety parameters, etc.) may have been set
incorrectly (please also refer to the driver's
manual);
- TCP/IP configuration files may have been set
incorrectly (Rhino™ IP address, Subnet Mask,
Default Router, etc.)
- The configuration files of running application may
have been set incorrectly (DL-TCL, Web Client)
-
The radio may be broken or the antenna connector
is disconnected.
