Difference between revisions of "LLRP XML Messages"
From RifidiWiki
(New page: This page contains a collection of example XML Messages that can be sent to an LLRP Reader. =ADD_ROSPEC= ==Message 1== ===Description=== ===Message=== ==Message 2== ===Description==...) |
(→ADD_ROSPEC) |
||
| Line 2: | Line 2: | ||
=ADD_ROSPEC= | =ADD_ROSPEC= | ||
| + | The ROSpec (Reader Operation Specification) defines how a reader should read tags. | ||
==Message 1== | ==Message 1== | ||
===Description=== | ===Description=== | ||
| + | This is a simple rospec with a null start and stop triggers. It has one AISpec with a null stop trigger. In order to execute this rospec, you will need to send an ENABLE_ROSPEC, and a START_ROSPC. In addition, you will need to set up reporting parameters using a SET_READER_CONFIG | ||
===Message=== | ===Message=== | ||
| + | <pre> | ||
| + | <Message from_ip="127.0.0.1" from_port="39640" to_ip="127.0.0.1" to_port="5084"> | ||
| + | <ADD_ROSPEC Version="1" MessageID="0"> | ||
| + | <ROSpec> | ||
| + | <ROSpecID>1</ROSpecID> | ||
| + | <Priority>0</Priority> | ||
| + | <CurrentState>Disabled</CurrentState> | ||
| + | <ROBoundarySpec> | ||
| + | <ROSpecStartTrigger> | ||
| + | <ROSpecStartTriggerType>Null</ROSpecStartTriggerType> | ||
| + | </ROSpecStartTrigger> | ||
| + | <ROSpecStopTrigger> | ||
| + | <ROSpecStopTriggerType>Null</ROSpecStopTriggerType> | ||
| + | <DurationTriggerValue>1000</DurationTriggerValue> | ||
| + | </ROSpecStopTrigger> | ||
| + | </ROBoundarySpec> | ||
| + | <AISpec> | ||
| + | <AntennaIDs>1</AntennaIDs> | ||
| + | <AISpecStopTrigger> | ||
| + | <AISpecStopTriggerType>Null</AISpecStopTriggerType> | ||
| + | <DurationTrigger>1000</DurationTrigger> | ||
| + | </AISpecStopTrigger> | ||
| + | <InventoryParameterSpec> | ||
| + | <InventoryParameterSpecID>2</InventoryParameterSpecID> | ||
| + | <ProtocolID>EPCGlobalClass1Gen2</ProtocolID> | ||
| + | </InventoryParameterSpec> | ||
| + | </AISpec> | ||
| + | </ROSpec> | ||
| + | </ADD_ROSPEC> | ||
| + | </Message> | ||
| + | </pre> | ||
==Message 2== | ==Message 2== | ||
===Description=== | ===Description=== | ||
===Message=== | ===Message=== | ||
| + | |||
=SET_READER_CONFIG= | =SET_READER_CONFIG= | ||
==Message 1== | ==Message 1== | ||
===Description=== | ===Description=== | ||
===Message=== | ===Message=== | ||
Revision as of 18:29, 6 December 2007
This page contains a collection of example XML Messages that can be sent to an LLRP Reader.
Contents
ADD_ROSPEC
The ROSpec (Reader Operation Specification) defines how a reader should read tags.
Message 1
Description
This is a simple rospec with a null start and stop triggers. It has one AISpec with a null stop trigger. In order to execute this rospec, you will need to send an ENABLE_ROSPEC, and a START_ROSPC. In addition, you will need to set up reporting parameters using a SET_READER_CONFIG
Message
<Message from_ip="127.0.0.1" from_port="39640" to_ip="127.0.0.1" to_port="5084">
<ADD_ROSPEC Version="1" MessageID="0">
<ROSpec>
<ROSpecID>1</ROSpecID>
<Priority>0</Priority>
<CurrentState>Disabled</CurrentState>
<ROBoundarySpec>
<ROSpecStartTrigger>
<ROSpecStartTriggerType>Null</ROSpecStartTriggerType>
</ROSpecStartTrigger>
<ROSpecStopTrigger>
<ROSpecStopTriggerType>Null</ROSpecStopTriggerType>
<DurationTriggerValue>1000</DurationTriggerValue>
</ROSpecStopTrigger>
</ROBoundarySpec>
<AISpec>
<AntennaIDs>1</AntennaIDs>
<AISpecStopTrigger>
<AISpecStopTriggerType>Null</AISpecStopTriggerType>
<DurationTrigger>1000</DurationTrigger>
</AISpecStopTrigger>
<InventoryParameterSpec>
<InventoryParameterSpecID>2</InventoryParameterSpecID>
<ProtocolID>EPCGlobalClass1Gen2</ProtocolID>
</InventoryParameterSpec>
</AISpec>
</ROSpec>
</ADD_ROSPEC>
</Message>
