Version 1.3.1 - Revision history

Bppause at 15:24, 19 November 2012

2012-11-19T15:24:45Z

Matt at 05:38, 5 March 2012

2012-03-05T05:38:36Z

Matt at 05:38, 5 March 2012

2012-03-05T05:38:24Z

Matt: /* Changes in 1.3.1 */

2012-03-04T22:36:35Z

‎Changes in 1.3.1

Matt: /* LLRP Bug Fixed */

2012-03-04T22:35:36Z

‎LLRP Bug Fixed

Matt: /* Changes in 1.3.1 */

2012-03-03T03:51:41Z

‎Changes in 1.3.1

Matt at 03:50, 3 March 2012

2012-03-03T03:50:09Z

Matt: New page: ==Version 1.3== Be sure to check out the changelog in Version1.3 if you haven't seen it already! ==Changes in 1.3.1== ===New subscriber mode added=== A new subscriber mode was add...

2012-03-03T03:49:55Z

New page: ==Version 1.3== Be sure to check out the changelog in Version1.3 if you haven't seen it already! ==Changes in 1.3.1== ===New subscriber mode added=== A new subscriber mode was add...

New page

==Version 1.3==

Be sure to check out the changelog in [[Version1.3]] if you haven't seen it already!

==Changes in 1.3.1==

===New subscriber mode added===

A new subscriber mode was added so that a tag showing up on different antennas or different readers which has previously been seen before the timeout on other antennas or readers that are all in the same readzone will NOT create a new arrival event. For instance, in the old system:

A readzone was defined for reader LLRP_1 and antennas 1, 2, and 3. Tag A shows up on antenna 1, generating an arrival event. Then, the tag leaves antenna 1 and moves to antenna 3. Under the old system, a new arrival event would be generated at antenna 3. If you wish, you can set it so that a new arrival event does not get generated. The same thing will happen if multiple readers are specified for the same readzone and the tag shows up on a new reader.

===GPIO support added for LLRP===

LLRP added GPIO support now, so you can test GPI ports and set GPO ports on an LLRP reader from within a RifidiApp.

===Performance increased for the default ReaderConfig for LLRP===

The performance for the ReaderConfig for LLRP has been increased by default. For deployments the ADD_ROSPEC_From_File command is still recommended, but the diagnostic capabilities of the PUSH readerconfig of the LLRP are now improved.

@@ Line 25: / Line 25: @@
 ==Links==
 Javadocs:
-http://www.rifidi.org/javadoc/edge1.3.1/
+http://www.transcends.co/www/javadoc/edge1.3.1/

@@ Line 23: / Line 23: @@
 Occasionally certain tags (particularly non-standard tags) would show up from the LLRP arrival queue in binary instead of hexidecimal.  This has now been fixed and all LLRP tags should now display correctly.
-===Links===
+==Links==
 Javadocs:
 http://www.rifidi.org/javadoc/edge1.3.1/

← Older revision		Revision as of 05:38, 5 March 2012
Line 22:		Line 22:

	Occasionally certain tags (particularly non-standard tags) would show up from the LLRP arrival queue in binary instead of hexidecimal. This has now been fixed and all LLRP tags should now display correctly.		Occasionally certain tags (particularly non-standard tags) would show up from the LLRP arrival queue in binary instead of hexidecimal. This has now been fixed and all LLRP tags should now display correctly.
		+
		+	===Links===
		+	Javadocs:
		+	http://www.rifidi.org/javadoc/edge1.3.1/

@@ Line 17: / Line 17: @@
 ===Performance increased for the default ReaderConfig for LLRP===
-The performance for the ReaderConfig for LLRP has been increased by default.  For deployments the ADD_ROSPEC_From_File command is still recommended, but the diagnostic capabilities of the PUSH readerconfig of the LLRP are now improved.
+The performance of the ROSpec submitted by the ReaderConfig in PUSH mode for LLRP has been increased by default.  For deployments the ADD_ROSPEC_From_File command is still recommended, but the diagnostic capabilities of the PUSH ReaderConfig of the LLRP are now improved.
 ===LLRP Bug Fixed===
 Occasionally certain tags (particularly non-standard tags) would show up from the LLRP arrival queue in binary instead of hexidecimal.  This has now been fixed and all LLRP tags should now display correctly.

← Older revision		Revision as of 22:35, 4 March 2012
Line 21:		Line 21:
	===LLRP Bug Fixed===		===LLRP Bug Fixed===

−	Occasionally certain tags (particularly non-standard tags) would show up from the LLRP arrival queue in ~~Binary~~ instead of hexidecimal. This has now been fixed and all LLRP tags should now display correctly.	+	Occasionally certain tags (particularly non-standard tags) would show up from the LLRP arrival queue in binary instead of hexidecimal. This has now been fixed and all LLRP tags should now display correctly.

← Older revision		Revision as of 03:51, 3 March 2012
Line 18:		Line 18:

	The performance for the ReaderConfig for LLRP has been increased by default. For deployments the ADD_ROSPEC_From_File command is still recommended, but the diagnostic capabilities of the PUSH readerconfig of the LLRP are now improved.		The performance for the ReaderConfig for LLRP has been increased by default. For deployments the ADD_ROSPEC_From_File command is still recommended, but the diagnostic capabilities of the PUSH readerconfig of the LLRP are now improved.
		+
		+	===LLRP Bug Fixed===
		+
		+	Occasionally certain tags (particularly non-standard tags) would show up from the LLRP arrival queue in Binary instead of hexidecimal. This has now been fixed and all LLRP tags should now display correctly.

@@ Line 1: / Line 1: @@
 ==Version 1.3==
-Be sure to check out the changelog in [[Version1.3]] if you haven't seen it already!
+Be sure to check out the changelog in [[Version 1.3]] if you haven't seen it already!
 ==Changes in 1.3.1==