Intermec IV7 Basic Reader Interface Programmer's Reference Manual (BRI version - Page 95

ACCESSCMD, Purpose, Syntax, Examples

Get Intermec IV7 PDF manuals and user guides View all Intermec IV7 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 95 highlights

Chapter 4 - BRI Commands • When the command executes successfully, the tag responses as follows: # Bits Details Header 1 0 Data variable 0 or more RN 16 handle CRC-16 16 • When the command executes unsuccessfully, the tag responses as follows: # Bits Details Header 1 1 Error Code 8 error code RN 16 handle CRC-16 16 • If the tag reply takes longer than T1, the reply uses the extended preamble as if TRext=1 regardless of the TRext value in the Query that initiated the inventory round. • If the tag reply occurs within T1, the reply uses the preamble as determined by TRext in the Query that initiated the inventory round. ACCESSCMD Purpose: Syntax: Examples: This command sends a custom tag access command to a tag and reports the resulting tag response. The ACCESSCMD is a data field that can be used in a READ command. The result displays the hexadecimal value of the response with the handle and CRC16 bits stripped. The result data is left justified. That is, the most significant (left most) bit of the command field represents the first bit to be transmitted to the tag. READ [flex_query_selector] ACCESSCMD(, , )=H [TAGTYPE=] [WHERE ] [PASSWORD=] = The number of bits in the command excluding the handle and the CRC-16. = The number of bits expected in the successful response to the command. This length does not include the handle and CRC-16. = The maximum number of milliseconds that the tag takes to respond to the command. For a standard EPCC1G2 write operation, this value is 20 indicating that the tag responds within 20 milliseconds. Intermec readers currently support a maximum wait time of about 33 milliseconds. When this value is zero, the reader expects the tag to respond within T1 with the preamble as specified in the Query that started the inventory round. When this value is non-zero, the reader expects the tag to respond with the extended preamble as if TRext=1. = The command data. The reader appends the tag's handle and the CRC-16. The command data is left justified. That is, the most significant (left most) bit of the command field represents the first bit to be transmitted to the tag. Example 1 Basic Reader Interface Programmer Reference Manual 83

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
Chapter 4 — BRI Commands
Basic Reader Interface Programmer Reference Manual
83
•
When the command executes successfully, the tag responses as follows:
•
When the command executes unsuccessfully, the tag responses as follows:
•
If the tag reply takes longer than T1, the reply uses the extended preamble as if
TRext=1 regardless of the TRext value in the Query that initiated the inventory
round.
•
If the tag reply occurs within T1, the reply uses the preamble as determined by
TRext in the Query that initiated the inventory round.
ACCESSCMD
Purpose:
This command sends a custom tag access command to a tag and reports the
resulting tag response. The ACCESSCMD is a data field that can be used in a READ
command.
The result displays the hexadecimal value of the response with the handle and CRC-
16 bits stripped. The result data is left justified. That is, the most significant (left
most) bit of the command field represents the first bit to be transmitted to the tag.
Syntax:
READ [flex_query_selector] ACCESSCMD(<command_length>,
<response_length>, <milliseconds>)=H<command> [TAGTYPE=<tagtype
list>] [WHERE <data condition>] [PASSWORD=<"access_password">]
<command_length> = The number of bits in the command excluding the handle
and the CRC-16.
<response_length> = The number of bits expected in the successful response to the
command. This length does not include the handle and CRC-16.
<milliseconds> = The maximum number of milliseconds that the tag takes to
respond to the command. For a standard EPCC1G2 write operation, this value is 20
indicating that the tag responds within 20 milliseconds. Intermec readers currently
support a maximum wait time of about 33 milliseconds. When this value is zero, the
reader expects the tag to respond within T1 with the preamble as specified in the
Query that started the inventory round. When this value is non-zero, the reader
expects the tag to respond with the extended preamble as if TRext=1.
<command> = The command data. The reader appends the tag's handle and the
CRC-16. The command data is left justified. That is, the most significant (left most)
bit of the command field represents the first bit to be transmitted to the tag.
Examples:
Example 1
Header
Data
RN
CRC-16
# Bits
1
variable
16
16
Details
0
0 or more
handle
Header
Error Code
RN
CRC-16
# Bits
1
8
16
16
Details
1
error code
handle