XR400 Customer Release Notes

For Software Release Version 1.3.0

Customer Release Notes for Version 1.3.0 released 09-02-05

Contents
Introduction
Software Download
XR400 Software Upgrade
New Features
Differences From The AR400
Open Issues
Questions
Disclaimer

Introduction
The Customer Release Notes are designed for the Symbol Technologies XR400 system end-user. The Customer
Release Notes contain new features, major bug fixes, and a list open issues (not resolved at the time of the
release).
The following support documents are available at: http://www.symbol.com/manuals
• XR400 Integrator Guide (PN: 72E-71466-xx), Appendix B: includes the firmware upgrade procedure
• XR400 Interface Control Guide (provides a description of the XR400 Host Computer interfaces)
• XR400 Customer Release Notes for Software Release version 1.3.0

Software Download
The version 1.3.0 software update package (XR400_Rel_1-3-0.zip) includes the files required to update the
XR400 RFID Reader. Please note that an FTP server is required in order to upgrade the readers.
The software download is available at: http://devzone.symbol.com
The XR400 Firmware Upgrade Procedure is provided in the XR400 Integrator Guide (PN: 72E-71466-xx) see
Appendix B: “XR400 Firmware Upgrade Procedure to obtain the upgrade procedure.
Note: The entire software update bundle must be used. Do NOT mix the update files with previous releases.

Version File Date Size

1.3.0 XR400_Rel_1-3-0.zip September 05 3 MB

For additional information see:

XR400 Integrator Guide

XR400 Customer Release Notes

Page 1 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0
Contents of the XR400_Rel_1-3-0.zip file:

IMAGE TYPE VERSION FILE NAME RELEASE DATE

Application 1.3.0 FlashUpdateUtility.dll 9/1/2005

Application 1.3.0 Osupdxr400.exe 9/1/2005

Text 1.3.0 Response.txt 9/1/2005

Data Partition 1.0.1 XR4xxc42Data64H002.hex 9/1/2005

Partition Table 1.0.1 XR4xxc42PTbl64H002.hex 9/1/2005

Monitor 1.0.7 XR4xxc42MonH100007.bin 9/1/2005

Operating System 1.1.3 XR4xxc42OsH0101003.bin 9/1/2005

Application Server 1.3.0 XR4xxc42AppH125.hex 9/1/2005

Platform 1.13.0 XR4xxc42PlatH130.hex 9/1/2005

Important Notes:

• The DSP Firmware, DSP Loader, FPGA and Application Server software are all in one file
(XR4xxc42PlatH130.hex).

• Gen2 is not supported in this release

• The directory structure and partition sizes used in the earlier version (version 1.2.3) of the Application Server
have been changed. The reader code has been moved to the \Platform folder (from the \Application folder) in
order to be consistent with other Symbol devices. The \Application folder now contains a sample application
that uses the C API.

Page 2 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0

XR400 Software Upgrade

The version 1.3.0 software update package includes the files required to update the XR400 RFID Reader. Please
note that an FTP server is required in order to upgrade the readers.

The XR400 Integrator Guide (PN: 72E-71466-xx) provides the detailed XR400 reader firmware upgrade
procedures using the web based Admin Console.

There are two methods to update the reader firmware:

• Update Method 1, Use a LAN
• Update Method 2, Direct Connect Over the Ethernet Port

Method 1 is typically used when there are a number of readers connected to a LAN. Method 2 is typically used to
update a single reader using an Ethernet crossover cable.

There are six different types of firmware. Each type performs unique changes to the current settings and each can
be upgraded independently. Current firmware and tools can be found on the Symbol FTP site. Available firmware
versions include:
• DSP Version
• DSP Loader Version
• Monitor Version
• OS Version
• Application Server Version
• FPGA Version

Prerequisites
The following items are required to perform the update procedure:
• XR400 Integrator Guide (PN: 72E-71466-xx) available at: http://www.symbol.com/manuals
• XR400 reader with power supply
• Laptop (or other host computer)
• If using Method 1 (LAN update procedure) a Cat5 Ethernet cable is required.
• If using Method 2 (direct connect update procedure) a Cat5 Crossover cable is required.
• Serial cable (optional)
• ar400ftp tool.exe (if an FTP server is unavailable on the host computer)

Notes: The DSP Loader, DSP code, Application Server and FPGA code are all in the Platform partition.

Not all of the files are updated every release. Read the release notes for information about which files were
changed. Unlike the AR400 upgrade, there is not a specific order necessary when installing these files.

Page 3 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0

New Features (from release 1.1.8 of Application Server)

1. The “Tag Write” and “Tag Kill” features have been added.
2. The serial console can be accessed by typing “ARC” or “AdvancedReaderConsole” (previous release).
3. The user can revert to “Factory Defaults” by holding the reset button pressed for 5 to 7 seconds. “Factory
Defaults” implies that all previous password information as well as all previous configuration information is lost.
4. The reader software now resides in the \Platform partition. The \Application partition is blank except for a
sample executable that displays tags read by the reader.
5. The sizes of the \Platform and \Data partitions have changed. For this revision, all the partitions must be
reloaded.
6. The C API library has been added, along with a sample application (XRRFIDSample.exe in \Application.
7. Auto-enable default is set to15 minutes, the previous default value was set to 1 minute.

Differences From The AR400

Feature differences from the AR400

No. Feature Difference
1 The default tag format is RAW when using
the XML over HTTP interface.
2 The command numbers in the serial console
are different from the AR400.
3 The Serial Console can be entered by typing
“ARC” instead of “AdvancedReaderConsole”.
4 The XR400 uses a different TagTracker
“rasm5dll.dll” file. The turnaround time of
TagTracker sending the read commands is
important. With the AR400, TagTracker sends
an extra packet after receiving a read
response that is not required for the XR.
5 On the XR400, in the “Version Control” page,
the “FTP Server” field contains the path
(without a trailing slash). On the AR400, the
path and filename have to be specified.
6 The FPGA code, the DSP code and the
Reader Application code are all bundled
together into one executable on the XR400
(advReaderServer.exe).
Frequency User Impact / Workaround
Always Applications may have to be modified to use
the RAW tag format. Also, a new version of the
Java test tool must be used for testing the XML
interface.
Always For users that have set up automated scripts to
interact with the RS232 serial console the new
command numbers may cause problems with
the automated scripts that require changes to
interfaces and may generate support questions.
Always This simplifies user command entry. Typing
“AdvancedReaderConsole” still works the way
it did previously.
Always The reader response time is improved due to
the decreased load on TagTracker.
Always Simplifies user command entry.
Always Simplifies use.

Page 4 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0
Feature differences from the AR400
No. Feature Difference
7 The concept of the different flash file
partitions on the XR400 is different from the
AR400.
8 Read Tag User Data option is not provided by
the XML over HTTP interface. It is provided
over the Bytestream interface.
9 Periodic scan information is not displayed on
the Scan Control page. This is different from
the AR400.
10 Conveyer Belt is used on the XR400 instead
of Rapid Read used on the AR400.
11 The motion detector setting has been moved
to the Read Point Class instead of the reader
configuration.
12 The serial port interface to control the reader
using Bytestream protocol is not implemented
at the time.
13 There is no “Setup Wizard”.
14 Separate Read Points in combined group is
not implemented at the time.
15 System log is discarded after
shutdown/reboot.
16 Disable HTTP is not honored until reboot.
17 The XR400 has a different response to the
“PurgeAllTags” command. AR400 sends the
number of tags purged, XR400 only says that
the command is initiated. Also, if events are
enabled, the XR400 does not purge tags for
which events are outstanding (have not been
queried by the host).
18 Unlike the AR400, the time of the next
periodic scan is not displayed.
Frequency User Impact / Workaround
Always The flash file partitions were changed to make
the XR400 compatible with the other Symbol
Windows CE based products
Always No workaround. Will be provided in the next
release.
Always Since the time for the next scan is not
displayed, the user does not know when the
reader is going to scan next. Typically this will
only affect lab and test scenarios. In normal
production mode the scan time period is set up
and the web page is not continuously
monitored.
Always Use the Conveyer Belt instead of Rapid Read.
The Conveyer Belt does not have a mode
feature.
Always Set the motion detector from the Read Point
Class.
Always Use a RS232 to Ethernet adapter.
Always This was not a useful feature on the AR400, so
it was not carried over to the XR400.
Always A very small number of applications need this
feature. No workaround.
Always Log is not saved for troubleshooting.
Always Need to reboot to disable HTTP.
Always If all tags are purged, there may be some tags
that have not been queried by the host which
will also get purged. The XR400 does not purge
tags that have not been queried by the host.
This is a safety mechanism that prevents the
loss of tags that have not been transferred to
the host.
Always There is no periodic scan displayed.
Page 5 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0
Open Issues
The Customer Release Notes provide the user with known issues, and a listing of feature updates that have not been
implemented. This list is an aid, but it not a complete listing of every issue.
Open Issues
App/Tag Issue
Reads/etc
1 Application The reader application does not
support DNS.
2 Application An SNMP trap with a different
Enterprise ID is sometimes sent
out.
3 Application A “DSP error 0X5010” message
may appear in the system log.
This does not appear to affect
the reader in any way.
4 Application If an application is started from
a telnet session to the reader, a
CTRL-C does not kill it.
5 Application Backspace on serial console
appears to work. However, it
does not effect the input data.
6 Application Flash usage is only monitored
for the Application, Platform,
and Data partitions.
7 Interface Telnet does not have any
security.
8 Interface FTP supports username
“anonymous” with any
password, no other username is
supported.
9 Interface Use care entering the “host
notification link”. Certain invalid
addresses may be erroneously
accepted as valid.
10 Interface A space in the FTP path will
prevent the image from loading.
11 Interface If the reader hostlink is set to its
own address, it hangs the http.
12 System The IP address on the serial
console is not updated when
the user is already logged in
from the serial console and the
IP address changes.
13 System The reader clock can drift by
about 1.5 minutes per day
Frequency User Impact / Workaround
Always Specify the IP address instead of the
hostname in the Version Control page.
Always The SNMP listener should disregard traps with
a different Enterprise ID.
Always No effect on reader.
Always Start another telnet session and use the “kill”
command in to stop the application.
Always Press “Enter” and re-enter the command or
parameter.
Always Do not to save log files or other large files in
any folder except for the Application, Platform
or Data folders.
Always A telnet session does not require a username
and password. Telnet can be turned off from
the Communication Settings web interface
page.
Always Users must log in using “anonymous” the
username. FTP can be turned off from the
Communications Settings web interface page.
Always This may happen if an application on the
invalid link returns an “Ack” to the reader when
the reader queries the port on the specified IP
address.
Always Confirm that a space is not used in the FTP
path.
Always Confirm that the reader hostlink is not set to its
own address.
Always Log out and then log back in for the reader to
display the correct IP address.
Always This happens if the reader is not synchronized
using NTP.
Page 6 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0

Open Issues
App/Tag Issue Frequency User Impact / Workaround
Reads/etc
14 System There is no ethStat command in Always The standard “netstat” and “route” commands
either the serial console or via are available when using a telnet session to
the web. the reader.
15 System The configuration file is erased Always This occurs (in release 1.3.0) whenever the
during upgrade. Static IP users Application folder is updated.
must use a serial interface to
the reader to correctly set the
DHCP flag in order to access
the reader.
16 System When importing a Config.xml Always The XR400 continues to operation in exactly
file (that has motion enabled), the same way as the AR400, with the
the motion detector is enabled. exception of not having any feedback on the
However, there is no indication web interface. This will be provided in the next
from the console. release.
17 System The antenna fault message may Always No negative consequences. No action
contain some random required.
characters.
18 System The XR400 firmware upgrade Always Do not upgrade XR400 readers that have
erases the configuration already been upgraded.
information even if the upgrade
version is the same. This is
different from the AR400
update. The AR400 update
does not erase the configuration
information if the upgrade
version is the same.
19 System The LEDs do not light for long Always This is not a problem with the XR400 and no
periods of time during an action required.
upgrade, the unit may appear to
be not working when actually
there is no problem.
20 System The XR400 OS sends SNMP Always The Enterprise ID field is different when the
traps that do not correspond to reader first powers up.
the ‘Matrics’ MIB structure.
Some SNMP listeners may not
interpret the extra messages
correctly and/or stop listening.
21 System The backspace in the serial Always User needs to press “Enter” and re-enter the
console is not honored. command. This will be fixed in the next
release.
22 System The WIN-CE web server is Always No action required. No negative
active, but is not utilized. When consequences.
the applications web server is
active, the system reports an
error in the log.
23 System The timestamp is missing from Always No action required. No negative
the serial log entries in the consequences.
access log.

Page 7 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0
Open Issues
App/Tag Issue
Reads/etc
24 System The log is not persisted over a
reboot.
25 System The bytestream configuration
may conflict with the
autonomous configuration. The
two configurations may be set
concurrently (but this is not
recommended), the auto enable
setting may also have an effect.
26 System If the bytestream socket
communication is interrupted, a
reboot may be required before a
re-connect is accepted.
27 System The reader requires a reboot
after a software upgrade.
28 Tag Read Unless the tag user data is
exactly 26 characters long, it is
reported as invalid.
29 Tag Read When using Tag Tracker,
several messages may appear
that indicate an unsupported or
unexpected command.
30 Tag Read The event/tag data is not
persisted over an upgrade.
31 Tag read The hex value of the timestamp
in the queryTags or
queryEvents response is
incorrect by 1 hour.
Frequency User Impact / Workaround
Always No action required. The log information is lost
after a reboot.
Always Do not use the bytestream and XML interfaces
concurrently.
Always This happens because the reader is always
waiting for commands over the bytestream
interface. If it does not get any message, it
keeps listening, which keeps the socket open.
Always No action required. No negative
consequences.
Always Confirm that the user data is exactly 26
characters long.
Always This is not a problem with the XR400 and no
action required.
Always Query the reader before an upgrade. The
event/tag data (in the reader memory) is lost
during an upgrade. In addition the reader does
not read any tags during the 15 minutes it
takes to upgrade.
Always This could be a daylight savings time issue.
The ASCII value of the timestamp is correct,
and that should be used.
Page 8 of 9
 XR400 Customer Release Notes
For Software Release Version 1.3.0

Questions
For sales related enquiries, contact Symbol Technologies Inc. at 301 610-6100 (Monday-Friday 8:30 a.m. – 5:00
p.m. EST): http://www.symbol.com/rfid
For technical assistance please call Symbol at 800-653-5350 (24x7 support line):
http://www.symbol.com/services/howto/howto_contact_us.html

Disclaimer
While Symbol Technologies Inc. has committed its best efforts to providing accurate information in this document,
we assume no responsibility for any inaccuracies that may be contained herein, and we reserve the right to make
changes to this document without notice.

Symbol Technologies, Inc.

One Symbol Plaza
Holtsville, New York 11742-1300
http://www.symbol.com

72E-75062-02
Revision A - September 2005

Page 9 of 9