Difference between revisions of "Getting Started with LLRP in RIFIDI"
From RifidiWiki
| Line 1: | Line 1: | ||
| − | + | =LLRP Standards= | |
The LLRP standards doc has a good overview of how they work: | The LLRP standards doc has a good overview of how they work: | ||
http://www.gs1.org/gsmp/kc/epcglobal/llrp | http://www.gs1.org/gsmp/kc/epcglobal/llrp | ||
| + | =Configuration= | ||
The LLRP commander project for eclipse is a good way to configure LLRP rospecs without having to go through Rifidi: | 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 | 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). | 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 | 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. | 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. | ||
| − | + | =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: | 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: | ||
Revision as of 15:51, 2 December 2014
Contents
LLRP Standards
The LLRP standards doc has a good overview of how they work: http://www.gs1.org/gsmp/kc/epcglobal/llrp
Configuration
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 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
https://support.impinj.com/hc/en-us/articles/202756548-Get-LLRP-Configuration-with-RShell-VIDEO-
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.
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:
<llrp:ROSpecStartTrigger>
<llrp:ROSpecStartTriggerType>GPI</llrp:ROSpecStartTriggerType>
<llrp:GPITriggerValue>
<llrp:GPIPortNum>1</llrp:GPIPortNum>
<llrp:GPIEvent>1</llrp:GPIEvent>
<llrp:Timeout>0</llrp:Timeout>
</llrp:GPITriggerValue>
</llrp:ROSpecStartTrigger>
<llrp:ROSpecStopTrigger>
<llrp:ROSpecStopTriggerType>GPI_With_Timeout</llrp:ROSpecStopTriggerType>
<llrp:DurationTriggerValue>0</llrp:DurationTriggerValue>
<llrp:GPITriggerValue>
<llrp:GPIPortNum>1</llrp:GPIPortNum>
<llrp:GPIEvent>0</llrp:GPIEvent>
<llrp:Timeout>0</llrp:Timeout>
</llrp:GPITriggerValue>
</llrp:ROSpecStopTrigger>
