Symbol XR440 - Revision history

Redfern3141: Undo revision 5894 by StevenCollins (talk) - spam & advertising edits

2014-06-30T22:02:40Z

Undo revision 5894 by StevenCollins (talk) - spam & advertising edits

StevenCollins at 19:20, 24 November 2011

2011-11-24T19:20:23Z

Matt: Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

2010-11-26T19:43:09Z

Reverted edits by Amesycyxa (Talk); changed back to last version by Kyle

Amesycyxa at 23:14, 23 November 2010

2010-11-23T23:14:49Z

Kyle at 17:58, 29 November 2007

2007-11-29T17:58:58Z

Kyle: New page: Category:developerDocCategory:EngineDocCategory:userDoc ==Introduction== The XR440 is manufactured by Motorola. It is a general purpose reader that can read Class 1 Gen 2 tags...

2007-11-07T00:39:42Z

New page: Category:developerDoc Category:EngineDoc Category:userDoc ==Introduction== The XR440 is manufactured by Motorola. It is a general purpose reader that can read Class 1 Gen 2 tags...

New page

[[Category:developerDoc]][[Category:EngineDoc]][[Category:userDoc]]

==Introduction==
The XR440 is manufactured by Motorola. It is a general purpose reader that can read Class 1 Gen 2 tags.

;Model Number:
XR440
;Network Protocol:
Bit Encoded Messages over TCP & HTTP over TCP
;Communication:
10/100 BaseT Ethernet – RJ45
;Antennas:
4 read points (4 transmit points, 4 receive points)
;General Purpose I/O:
N/A
==Basis of Virtual Reader==
The implementation of the virtual reader is based on the testing of an actual hardware reader. Testing was done using wireshark to capture the client-reader communication. This input output was then emulated.
===Documentation===
*[http://support.symbol.com/support/browse.do?WidgetName=BROWSE_PRODUCT&TaxoName=SG_SupportGoals&BROWSE_PRODUCT.isProductTaxonomy=true&BROWSE_PRODUCT.NodeId=SG_XR440_1_2&BROWSE_PRODUCT.thisPageUrl=%2Fproduct%2Fproducts.do&id=m4&BROWSE_PRODUCT.TaxoName=SG_SupportGoals&NodeType=leaf&NodeName=XR440&document=DT_PRODUCTMANUALS_1_1&BROWSE_PRODUCT.NodeType=leaf&NodeId=SG_XR440_1_2&AppContext=AC_ProductPage&param_document=sp| product manuals for the Symbol XR440]
===Client Tools===
The main client tools used for testing this program:
;BEA 2.2
:[[BEA]] is a commercial edgeware application. It communicates with the alien reader via "on demand" mode using the bit encoded messages over TCP. The new version of BEA (version 3.0), also has an option to use autonomous mode, which uses HTTP over TCP.
;Logic Alloy 1.0.10
:[[Logic Alloy]] ALE Server is an open source edgeware application. It uses HTTP to communicate with the reader.
;TagCentric
:[[TagCentric]] is an open source edgeware application that communicates with the alien reader HTTP.
;Motorola Showcase
:Motorola Showcase is a client tool provided by Motorola to use with their readers. It runs on .NET and communicates with the reader mainly using HTTP, but it is possible to get tags using the bit encoded messages.
;Web Browser
:Because the reader uses an HTTP interface, it is possible to use a simple web browser as a client to issue most commands.
==Reader Design==
This section will give a brief overview of how the hardware reader operates for the purposes of emulation.
===Communication===
The Symbol XR440 uses two methods for communication. The default port for HTTP is port 80, and the default port for bit-encoded messages is 3000.
====HTTP over TCP====
The main method for communicating with the reader is via HTTP over TCP. Almost all functionality can be accessed in this way.

The general syntax of an HTTP command is:

<pre>http://IP[:PORT]/cgi-bin/PROXY/oper=COMMAND[&PARAM=VAL]*</pre>

where

*[ ] indicate option items
*IP is a host name (can be of the form www.reader.com, or of 192.168.1.100)
*PORT is the port. If omitted, port 80 is assumed
*PROXY is either:
#loginProxy for commands dealing with logging into the Web-based admin console
#coreProxy for commands dealing with the backend, such as setting the date and time
#dataProxy for commands that interact with the host, such as getting tags
*COMMAND is the command to execute, such as "setDateTime" or "queryTags"
*PARAM=VALis a name-value pair of arguments. Each argument is separated by an ampersand. There can be 0 or more name-value pairs.

For example, to get tags, this command would be sent:

<code><pre>http://192.168.0.1/cgi-bin/dataProxy?oper=queryTags&raw=1</pre></code>

The resulting tag read looks like this:
<code><pre><Matrics>
<EventGroup>
<TagList>
<Tag raw='300833B2DDD9014035050000' time='46bb8b06' RPL='1'/>
</TagList>
</EventGroup>
</Matrics></pre></code>

====Byte Stream Messages====
In addition to the HTTP interface, the XR440 also supports a byte stream protocol. This interface is primarily for getting tags in an "on-demand" (i.e. polling) way. For example, the client will send the reader a command to "get tags", and the reader will respond with a tag list. Because the bit-encoded messages are smaller, they are more efficient to send over a network, and thus this protocol is a better choice than sending "queryTags" HTTP commands for polling the reader.

=====Structure of Byte Protocol Message=====
The general structure of a bit encoded message is the following:
*Byte 0 - Start of Frame (value is 0x01)
*Byte 1 - Node Address (Obsolete, value is 0x04)
*Byte 2 - Packet length, excluding the Start of Frame, but including CRC bytes
*Byte 3 - Command
*Bytes 4-N - Data
*Byte N+1 - LSB of CRC
*Byte N+2 - MSB of CRC

The reader will always respond with a similarly structured response message that echoes the command of the incoming message. In the case of the Read Full Field Command (22h), there are two response packets -- a Tag Data Packet, and a Final Packet.

===Memory Model===
The memory model for the Symbol reader is fairly simple. Tags are in one of three states: Visible, Invisible, or Unknown. Once a tag is read, it transitions from the Unknown state to the Visible state. If the tag goes outside the view of the antenna, it transitions to the invisible state. Then, if the re-enters the antenna's field of view, it transitions back to the Visible state. If the tag is in the Invisible state, and a purge command is called, it goes back to being unknown. The reader also generates events at each of these transitions.

When a client queries the reader using http, it can specify whether or not it wants the invisible tags by using the "invis" parameter.

===Getting Tags===

====On Demand====

====Autonomous Mode====

===Login===

==Supported Features==
So far, the only supported features are the following byte stream commands

*Get Parameter Block Command(24h)
*Ge Reader Status Command(14h)
*Read Full Command(22h)
*Set Parameter Block Command(23h)

In addition, it is only possible to read from antenna 1.

==Unsupported Features & Bugs==

@@ Line 1: / Line 1: @@
 [[Category:developerDoc]][[Category:EmulatorDoc]][[Category:userDoc]]
@@ Line 15: / Line 7: @@
 XR440
 ;Network Protocol:
-Bit Encoded Messages over TCP &amp; HTTP over TCP
+Bit Encoded Messages over TCP & HTTP over TCP
 ;Communication:
 /100 BaseT Ethernet – RJ45
@@ Line 25: / Line 17: @@
 The implementation of the virtual reader is based on the testing of an actual hardware reader.  Testing was done using wireshark to capture the client-reader communication.  This input output was then emulated.
 ===Documentation===
-*[http://support.symbol.com/support/browse.do?WidgetName=BROWSE_PRODUCT&amp;TaxoName=SG_SupportGoals&amp;BROWSE_PRODUCT.isProductTaxonomy=true&amp;BROWSE_PRODUCT.NodeId=SG_XR440_1_2&amp;BROWSE_PRODUCT.thisPageUrl=%2Fproduct%2Fproducts.do&amp;id=m4&amp;BROWSE_PRODUCT.TaxoName=SG_SupportGoals&amp;NodeType=leaf&amp;NodeName=XR440&amp;document=DT_PRODUCTMANUALS_1_1&amp;BROWSE_PRODUCT.NodeType=leaf&amp;NodeId=SG_XR440_1_2&amp;AppContext=AC_ProductPage&amp;param_document=sp| product manuals for the Symbol XR440]
+*[http://support.symbol.com/support/browse.do?WidgetName=BROWSE_PRODUCT&TaxoName=SG_SupportGoals&BROWSE_PRODUCT.isProductTaxonomy=true&BROWSE_PRODUCT.NodeId=SG_XR440_1_2&BROWSE_PRODUCT.thisPageUrl=%2Fproduct%2Fproducts.do&id=m4&BROWSE_PRODUCT.TaxoName=SG_SupportGoals&NodeType=leaf&NodeName=XR440&document=DT_PRODUCTMANUALS_1_1&BROWSE_PRODUCT.NodeType=leaf&NodeId=SG_XR440_1_2&AppContext=AC_ProductPage&param_document=sp| product manuals for the Symbol XR440]
 ===Client Tools===
 The main client tools used for testing this program:
 ;BEA 2.2
-:[[BEA]] is a commercial edgeware application.  It communicates with the alien reader via &quot;on demand&quot; mode using the bit encoded messages over TCP.  The new version of BEA (version 3.0), also has an option to use autonomous mode, which uses HTTP over TCP.
+:[[BEA]] is a commercial edgeware application.  It communicates with the alien reader via "on demand" mode using the bit encoded messages over TCP.  The new version of BEA (version 3.0), also has an option to use autonomous mode, which uses HTTP over TCP.
 ;Logic Alloy 1.0.10
 :[[Logic Alloy]] ALE Server is an open source edgeware application.  It uses HTTP to communicate with the reader.
@@ Line 47: / Line 39: @@
 The general syntax of an HTTP command is:
-&lt;pre&gt;http://IP[:PORT]/cgi-bin/PROXY/oper=COMMAND[&amp;PARAM=VAL]*&lt;/pre&gt;
+<pre>http://IP[:PORT]/cgi-bin/PROXY/oper=COMMAND[&PARAM=VAL]*</pre>
 where
-*&lt;b&gt;[ ]&lt;/b&gt; indicate option items
+*<b>[ ]</b> indicate option items
-*&lt;b&gt;IP&lt;/b&gt; is a host name (can be of the form www.reader.com, or of 192.168.1.100)
+*<b>IP</b> is a host name (can be of the form www.reader.com, or of 192.168.1.100)
-*&lt;b&gt;PORT&lt;/b&gt; is the port.  If omitted, port 80 is assumed
+*<b>PORT</b> is the port.  If omitted, port 80 is assumed
-*&lt;b&gt;PROXY&lt;/b&gt; is either:
+*<b>PROXY</b> is either:
 #loginProxy for commands dealing with logging into the Web-based admin console
 #coreProxy for commands dealing with the backend, such as setting the date and time
 #dataProxy for commands that interact with the host, such as getting tags
-*&lt;b&gt;COMMAND&lt;/b&gt; is the command to execute, such as &quot;setDateTime&quot; or &quot;queryTags&quot;
+*<b>COMMAND</b> is the command to execute, such as "setDateTime" or "queryTags"
-*&lt;b&gt;PARAM=VAL&lt;/b&gt;is a name-value pair of arguments.  Each argument is separated by an ampersand.  There can be 0 or more name-value pairs.
+*<b>PARAM=VAL</b>is a name-value pair of arguments.  Each argument is separated by an ampersand.  There can be 0 or more name-value pairs.
 For example, to get tags, this command would be sent:
-&lt;code&gt;&lt;pre&gt;http://192.168.0.1/cgi-bin/dataProxy?oper=queryTags&amp;raw=1&lt;/pre&gt;&lt;/code&gt;
+<code><pre>http://192.168.0.1/cgi-bin/dataProxy?oper=queryTags&raw=1</pre></code>
 The resulting tag read looks like this:
-&lt;code&gt;&lt;pre&gt;&lt;Matrics&gt;
+<code><pre><Matrics>
-&lt;EventGroup&gt;
+<EventGroup>
-&lt;TagList&gt;
+<TagList>
-&lt;Tag raw='300833B2DDD9014035050000' time='46bb8b06' RPL='1'/&gt;
+<Tag raw='300833B2DDD9014035050000' time='46bb8b06' RPL='1'/>
-&lt;/TagList&gt;
+</TagList>
-&lt;/EventGroup&gt;
+</EventGroup>
-&lt;/Matrics&gt;&lt;/pre&gt;&lt;/code&gt;
+</Matrics></pre></code>
 ====Byte Stream Messages====
-In addition to the HTTP interface, the XR440 also supports a byte stream protocol.  This interface is primarily for getting tags in an &quot;on-demand&quot; (i.e. polling) way.  For example, the client will send the reader a command to &quot;get tags&quot;, and the reader will respond with a tag list.  Because the bit-encoded messages are smaller, they are more efficient to send over a network, and thus this protocol is a better choice than sending &quot;queryTags&quot; HTTP commands for polling the reader.
+In addition to the HTTP interface, the XR440 also supports a byte stream protocol.  This interface is primarily for getting tags in an "on-demand" (i.e. polling) way.  For example, the client will send the reader a command to "get tags", and the reader will respond with a tag list.  Because the bit-encoded messages are smaller, they are more efficient to send over a network, and thus this protocol is a better choice than sending "queryTags" HTTP commands for polling the reader.
 =====Structure of Byte Protocol Message=====
@@ Line 92: / Line 84: @@
 The memory model for the Symbol reader is fairly simple.  Tags are in one of three states: Visible, Invisible, or Unknown.  Once a tag is read, it transitions from the Unknown state to the Visible state.  If the tag goes outside the view of the antenna, it transitions to the invisible state.  Then, if the re-enters the antenna's field of view, it transitions back to the Visible state.  If the tag is in the Invisible state, and a purge command is called, it goes back to being unknown.  The reader also generates events at each of these transitions.
-When a client queries the reader using http, it can specify whether or not it wants the invisible tags by using the &quot;invis&quot; parameter.
+When a client queries the reader using http, it can specify whether or not it wants the invisible tags by using the "invis" parameter.
 ===Getting Tags===
@@ Line 112: / Line 104: @@
 In addition, it is only possible to read from antenna 1.
-==Unsupported Features &amp; Bugs==
+==Unsupported Features & Bugs==

← Older revision		Revision as of 17:58, 29 November 2007
Line 1:		Line 1:
−	[[Category:developerDoc]][[Category:~~EngineDoc~~]][[Category:userDoc]]	+	[[Category:developerDoc]][[Category:EmulatorDoc]][[Category:userDoc]]

	==Introduction==		==Introduction==

@@ Line 35: / Line 35: @@
 The Symbol XR440 uses two methods for communication.  The default port for HTTP is port 80, and the default port for bit-encoded messages is 3000.
 ====HTTP over TCP====
-The main method for communicating with the reader is via <span class="plainlinks">[http://www.shoppharmacycounter.com/t-dietpillsonline.aspx <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">diet pills</span>] HTTP over TCP.  Almost all functionality can be accessed in this way.
+The main method for communicating with the reader is via HTTP over TCP.  Almost all functionality can be accessed in this way.
 The general syntax of an HTTP command is:
@@ Line 67: / Line 67: @@
 ====Byte Stream Messages====
-In addition to the HTTP interface, the XR440 also supports a byte stream protocol.  This interface is primarily for getting tags in an "on-demand" (i.e. polling) way.  For example, the client will send the reader a command to "get tags", and the reader will respond with a tag list.  Because the bit-encoded messages are smaller <span class="plainlinks">[http://www.supplementstoweightloss.com/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">weight loss pills</span>], they are more efficient to send over a network, and thus this protocol is a better choice than sending "queryTags" HTTP commands for polling the reader.
+In addition to the HTTP interface, the XR440 also supports a byte stream protocol.  This interface is primarily for getting tags in an "on-demand" (i.e. polling) way.  For example, the client will send the reader a command to "get tags", and the reader will respond with a tag list.  Because the bit-encoded messages are smaller, they are more efficient to send over a network, and thus this protocol is a better choice than sending "queryTags" HTTP commands for polling the reader.
 =====Structure of Byte Protocol Message=====