Owner manual

Advanced Tag Operations
Level 2 API 43
The /reader/tagop/protocol parameter selects the RFID Tag Protocol to use and can
affect the semantics of the command, as some commands are not supported by
some protocols.
Embedded TagOp Invocation
TagOps may also be executed as a side effect of an Advanced Reading operation. When a
SimpleReadPlan is created with a TagOp specified in the tagOp parameter the following
behavior results:
The specified operation will be executed on each tag as each tag is found during the
Advanced Reading operation.
The specified operation will be performed on the same antenna the tag was read on
during the overall read operation.
The rules of the Advanced Reading operation and specified ReadPlan apply.
Note
Embedded TagOps are only supported with Gen2 (ISO18000-6C) protocol
tags and when connected to readers of type SerialReader and
RQLReader type M6.
Note
In previous versions of the API this functionality required the use of
Level 3
API operations. Those operations should no longer be used.
Embedded TagOp Success/Failure Reporting
Current reader functionality (May 2011) does not provide a means to report the success
or failure of an embedded tagop for each invocation, except for ReadData operations
where the presence or absence of the data is an implicity indicator. Summary success/
failure information is available through the following
/reader/tagReadData parameters:
/reader/tagReadData/tagopSuccess
/reader/tagReadData/tagopFailures
Note
Depending on the Gen2
Tag Contention Settings used the operations
Succeeded/Failed counts can be misleading since in Session 0, for example,
the tag may respond many times during an inventory round and the
command may be attempted many times. This would result in counts higher
than the actual number of unique tags the operation succeeded or failed on.
These counters are reset to zero at the beginning of each Reading operation and behave
as follows:.