Getting Started with LLRP in RIFIDI - Revision history

Bppause: /* Reader Configuration */

2014-12-05T15:17:09Z

‎Reader Configuration

Bppause: /* Reader Configuration */

2014-12-05T15:07:23Z

‎Reader Configuration

Bppause: /* How to Override RoSpec */

2014-12-05T15:04:44Z

‎How to Override RoSpec

Bppause: /* Reader Configuration */

2014-12-05T15:02:32Z

‎Reader Configuration

Bppause: /* How to Override RoSpec */

2014-12-05T15:02:12Z

‎How to Override RoSpec

Bppause: /* How to Override DefaultReader and RoSpec */

2014-12-05T15:00:16Z

‎How to Override DefaultReader and RoSpec

Bppause at 14:59, 5 December 2014

2014-12-05T14:59:19Z

Bppause at 14:57, 5 December 2014

2014-12-05T14:57:01Z

Bppause at 14:55, 5 December 2014

2014-12-05T14:55:45Z

Show changes

Bppause at 15:51, 2 December 2014

2014-12-02T15:51:18Z

@@ Line 6: / Line 6: @@
 This sets the reader configuration when a reader session connects such as enabling Event Types, AccessReportSpec, GPIO, TagReportContent.
-The defaults should support most if not all requireed configurations but one can override when creating the reader adapter configuration by setting the following property
+The defaults should support most if not all requireed configurations hence no need to override theses values but one can override when creating the reader adapter configuration by setting the following property
 *ReaderConfigPath: The path of an optional .llrp file which can be used to configure the reader when the session starts. Simply create a “SET_READER_CONFIG” command in LLRP Commander (URL), and export the resulting XML into the desired file.

@@ Line 4: / Line 4: @@
 http://www.gs1.org/gsmp/kc/epcglobal/llrp
 =Reader Configuration=
-This sets the reader configuration when a reader session connects.
+This sets the reader configuration when a reader session connects such as enabling Event Types, AccessReportSpec, GPIO, TagReportContent.
 The defaults should support most if not all requireed configurations but one can override when creating the reader adapter configuration by setting the following property

← Older revision		Revision as of 15:04, 5 December 2014
Line 149:		Line 149:


−	=How to Override RoSpec=	+	=How to Override Default RoSpec=
	One may want to override the default ROSpec to be able to access extended Reader and LLRP features (example Vendor Extensions, GPIO Triggers etc..)		One may want to override the default ROSpec to be able to access extended Reader and LLRP features (example Vendor Extensions, GPIO Triggers etc..)

@@ Line 10: / Line 10: @@
 *ReaderConfigPath: The path of an optional .llrp file which can be used to configure the reader when the session starts. Simply create a “SET_READER_CONFIG” command in LLRP Commander (URL), and export the resulting XML into the desired file.
-Please refer to user guide for more details [[
+Please refer to user guide for more details [[User%27s_Guide]]
 Default Configuration:

@@ Line 150: / Line 150: @@
 =How to Override RoSpec=
 One may want to override the default ROSpec to be able to access extended Reader and LLRP  features (example Vendor Extensions, GPIO Triggers etc..)
 One can override teh default ROSpec by using the following LLRP command.

@@ Line 149: / Line 149: @@
-=How to Override DefaultReader and RoSpec=
+=How to Override RoSpec=
-To override the default RoSpec and Reader configuration for a llrp reader please refer to the user guide llrp section for necessary step
+To override the default RoSpec for a llrp reader please refer to the user guide llrp section for necessary step
 One may want to override the default ROSpec to be able to access extended Reader and LLRP  features (example Vendor Extensions, GPIO Triggers etc..)
@@ Line 163: / Line 163: @@
 * executecommand LLRP_1 1 LLRP_ADD_ROSPEC_File_1 -1
 This sequence of commands will look at the file “myrospec.llrp” in the ./config directory and craft a ROSpec out of it. All existing ROSpecs will be deleted, and the new ROSpec will be sent, enabled and started. The parameters of how the ROSpec is configured are completely up to you. If you need help crafting a ROSpec, try LLRP Commander.
 =How to Validate Impinj LLRP Configuration=

@@ Line 81: / Line 81: @@
 The file "default.llrp" in the "config" folder of rifidi is a good starting ROSpec to build off of, as the antennas are already configured there.  Attached is a version of that with the regular start/stop triggers replaced with GPI ones.  It may serve for what you need, though you might have to adjust the "GPIEvent" and "GPIPortNum" values (and the timeout on the stop trigger).
 Example Default ROSpec Configuration:
@@ Line 156: / Line 147: @@
 </pre>
 One may want to override the default ROSpec to be able to access extended Reader and LLRP  features (example Vendor Extensions, GPIO Triggers etc..)
@@ Line 171: / Line 164: @@
 This sequence of commands will look at the file “myrospec.llrp” in the ./config directory and craft a ROSpec out of it. All existing ROSpecs will be deleted, and the new ROSpec will be sent, enabled and started. The parameters of how the ROSpec is configured are completely up to you. If you need help crafting a ROSpec, try LLRP Commander.
 =GPIO=

@@ Line 78: / Line 78: @@
 https://code.google.com/p/fosstrak/wiki/LlrpMain
-default Configuration
+=ROSpec default Configuration=
 The file "default.llrp" in the "config" folder of rifidi is a good starting ROSpec to build off of, as the antennas are already configured there.  Attached is a version of that with the regular start/stop triggers replaced with GPI ones.  It may serve for what you need, though you might have to adjust the "GPIEvent" and "GPIPortNum" values (and the timeout on the stop trigger).
@@ Line 91: / Line 91: @@
 That link shows how to use Impinj rshell to pull the config directly off of the reader.  ONE CAN compare the ADD_Rospec VIA rshell to the ADD_Rospec expected to be configured vua Rifidi .  This should be easier than LLRP Commander.
-Default ROSpec Configuration:
+Example Default ROSpec Configuration:
 <pre>

@@ Line 1: / Line 1: @@
+=LLRP Standards=
 The LLRP standards doc has a good overview of how they work:
 http://www.gs1.org/gsmp/kc/epcglobal/llrp
 The LLRP commander project for eclipse is a good way to configure LLRP rospecs without having to go through Rifidi:
 https://code.google.com/p/fosstrak/wiki/LlrpMain
+= default Configuration =
 The file "default.llrp" in the "config" folder of rifidi is a good starting ROSpec to build off of, as the antennas are already configured there.  Attached is a version of that with the regular start/stop triggers replaced with GPI ones.  It may serve for what you need, though you might have to adjust the "GPIEvent" and "GPIPortNum" values (and the timeout on the stop trigger).
+=How to Override DefaultReader and RoSpec=
-To override the default configuration for a llrp reader please refer to the user guide
+To override the default RoSpec and Reader configuration for a llrp reader please refer to the user guide llrp section for necessary step
+=How to Validate Impinj LLRP Configuration=
 Follow these steps To validate which llrp configuration is active on Impinj reader
@@ Line 19: / Line 20: @@
 That link shows how to use Impinj rshell to pull the config directly off of the reader.  ONE CAN compare the ADD_Rospec VIA rshell to the ADD_Rospec expected to be configured vua Rifidi .  This should be easier than LLRP Commander.
-With GPIO
+=GPIO=
 Basically, you will need to use the LLRP "from file" command instead of the regular LLRP-Configure command in order to use the GPIO triggers (the rifidi user doc will show how to use this command).  The triggers themselves will look like this: