User manual

4 - 6
The broadcast.log is
recording heartbeats but not
broadcasts.
The log hasn’t received a
broadcast yet. Under ReM
default operation, broadcast
information is sent only once
an hour. (A “Disconnected”
status will also generate a
broadcast.)
Wait one hour for the broadcast entry to
be sent.
Or, since scanners also send broadcast
information upon being powered up,
you can try power cycling the scanner.
Scanner status shows the
scanner is connected but the
model number is listed as
“Not Retrieved”.
The connected status means
the client agent is processing
the scanner heartbeats.
However, the scanner model
is not being displayed
because the client agent has
not yet received a broadcast
entry.
Configuration or update
operation fails.
The incorrect scanner model
may have been selected dur-
ing ReM installation on the
client.
Uninstall then reinstall ReM client agent
with the correct scanner model (see
page 2-5).
The targeted scanner has a
different serial number than
the last scanner ReM found
at that location.
Perform a new Find then repeat the
desired operation.
There is already another
operation in progress on the
scanner.
Wait until the first operation has com-
pleted then start your operation again.
Yo u r jpos.xml file may be
corrupted.
Verify the data in C:\Program
Files\JPOSScanner\jpos.xml.
If it is incorrect, uninstall then re-install
the ReM client agent to repair it.
Honeywell does not recommend modi-
fying jpos.xml manually.
The scanner is connected at
the proper port (USB/
RS232) and sends heart-
beat, broadcast and
scanned bar code informa-
tion but you receive an Error
102 when you perform any
operation like a pull.
Error 102 is caused by an
extra character added before
or after a port number entry
in jpos.xml, which may be
corrupted.
Symptoms Possible Causes Solution