User manual

4 - 8
After a push operation, the
ReM web interface displays
the scanner with a “Discon-
nected” status.
You may have downloaded
the wrong file to the scanner.
For example:
• A configuration file for an
incorrect interface was
pushed to the scanner.
(For example, you pushed
a configuration file for USB
interface but the scanner is
connected on RS232.)
• A configuration file for one
model was pushed to
another model.
• A file was pulled from
MS2400 (with scale) and
then the same file was
inadvertently pushed to the
same scanner (without
scale).
Reconfigure the scanner for the correct
interface: USB IBM (full speed) or
RS232.
Perform a new Find. If ReM can still
find the scanner, you can try pushing
the correct configuration file.
If ReM cannot connect with the scan-
ner, you must manually download the
correct configuration using another soft-
ware like MetroSet2.
First stop the ReM client agent, then
use MetroSet2 to download the correct
configuration to the scanner. Close
MetroSet2 and restart the client agent.
MetroSet2 can be downloaded from
www.honeywellaidc.com at no addi-
tional cost.
Flashing a co-processor-
boot over a RS232 interface
on a MS2400 scanner does
not show the correct co-pro-
cessor-boot firmware num-
ber on successful flash.
This situation is caused by a
problem with the file
ScannerConfigUtility.dll.
ReM uses its own Scanner-
ConfigUtility.dll which may
be conflicting with another
application’s version of this
file (such as C:\Win-
dows\system32\Scanner-
ConfigUtility.dll).
Flash the co-processor-boot on a USB
interface.
You are using a JavaPOS or
OPOS application that is not
receiving bar code data.
The scanner has not been
properly configured.
For OPOS applications: Run the Profile
Wizard.
For JavaPOS applications: Manually
read the bar codes for STX, ETX prefix/
suffix, and Nixdorf ID.
Symptoms Possible Causes Solution