User Guide

Reader Manager Guide Page 58 of 62 40-10-006-DOC 15/09/2006
This command line execution must always be run in the directory where the ReaderManager.py file
resides, which on Windows is <Python>\Lib\ReaderManager\.
The connection names given in this example must exactly match the name that appears in the
Connection menu, including case. If the connection name contains spaces, it must be surrounded by
quotes as shown.
13.3 Trouble shooting AVR problems
When reporting problems with a Reader, it is important to be able to say what the version of software is
used for the ReaderManager, the ReaderServer, and if using an AVR series reader, the firmware.
To find out, select the Help/About Reader Manager menu item. It should open a window that contains
multiple application version numbers, depending on the kind of reader being used.
In this example, the top two lines show the version numbers of the currently installed ReaderManager
and ReaderServer applications. The next line shows the version of the reader that is currently connected.
If it is a local ReaderServer, as in this example, the version number will be the same as the installed
ReaderServer. Finally, the embedded reader firmware version is shown if it is an AVR Series reader.
If the numbers do not appear as expected, shutdown the ReaderManager, turn the reader off, then on
and restart the application. Then try this procedure again. Starting A Local ReaderServer Problem
When the ReaderServer is started, a log file is generated. It is called reader.log and is saved in the
<PythonPath>\Lib\ReaderServer\DTRHF\ directory.
If there is no problem, the log file is not shown, but if there is a problem, it is automatically shown to the
user after timing out.
For example, a typical log file for a successful connection would look like this:
Magellan Monitor Server started on port 8023
Incoming monitor connection from 127.0.0.1:1296 on channel 1900
While an unsuccessful start could generate an error message like this:
An error has occurred. Please copy this message and submit with a problem
report
Traceback (most recent call last):
File "DTRHF.py", line 17, in ?
ApplicationEntry(tagName) # run the main application entry point
File "../DTR\DTRApplication.py", line 223, in ApplicationEntry
application._Initialise()
File "../DTR\DTRApplication.py", line 78, in _Initialise
Globals.serial.Enable()
IOError: Unable to open serial port : Access is denied.
Sometimes the final line of this error report can give a clue as to the nature of the problem. In the above
example, another application had opened the serial port, so the ReaderServer was unable to gain access
to it.
In an error message is received and you believe it indicates a bug or some problem whose nature is not
clear, send the error message in an email to your technical support contact.