Intermec IF2 Basic Reader Interface Programmer's Reference Manual (BRI version - Page 84

HEXmemory_bank:address, length on Example 6

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

Page 84 highlights

Chapter 4 - BRI Commands Here are two example responses to this WRITE command. In this example, both fields were correctly written: WROK WROK OK> In this example, the second write (writing FINE starting at address 30) failed: WROK WRERR OK> Example 6: WRITE TAGID STRING(18,4)="GOOD",STRING(30,4)="FINE" This WRITE command presents two command parameters that can be used with the WRITE command. Normally, TAGID is associated with the READ command or a . However, you might want to know which tags have been written. Specifying TAGID on the command line causes the BRI response to return the tag identifier for each tag that is written. The BRI command shown above writes the data GOOD starting at address 18 and FINE starting at address 30 and responds with the tag identifier of any tags written, followed by WROK for the successfully written fields, followed by OK> when the last write has completed. If an error occurs during the write command, the BRI returns WRERR for the field that was not successfully written. If no tags are seen matching the data condition, the BRI returns NOTAGOK> In this example response, there was an error writing FINE to the tag: H1234567890ABCDEF WROK WRERR OK> In the this example response, a privilege error was encountered and no data was written to the tag: H1234567890ABCDEF PVERR PVERR OK> Note: The INT, HEX, and STRING data types in the [WRITE FIELD] parameters in the some of the previous examples do not include the optional memory_bank parameter that applies only to EPCglobal Class 1 Gen 2 tags. For help understanding the memory bank, see the description of the memory_bank parameter on "HEX(memory_bank:address, length)" on page 24. 72 Basic Reader Interface Programmer Reference Manual

  • 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
72
Basic Reader Interface Programmer Reference Manual
Here are two example responses to this WRITE command.
In this example, both fields were correctly written:
WROK WROK<CRLF>
OK><CRLF>
In this example, the second write (writing
FINE
starting at address 30) failed:
WROK WRERR<CRLF>
OK><CRLF>
Example 6:
WRITE TAGID STRING(18,4)=“GOOD”,STRING(30,4)=“FINE”
This WRITE command presents two command parameters that can be used with
the WRITE command. Normally, TAGID is associated with the READ command or
a <DATA CONDITION>. However, you might want to know which tags have been
written. Specifying TAGID on the command line causes the BRI response to return
the tag identifier for each tag that is written.
The BRI command shown above writes the data
GOOD
starting at address 18 and
FINE
starting at address 30 and responds with the tag identifier of any tags written,
followed by
WROK
for the successfully written fields, followed by OK><CRLF> when
the last write has completed. If an error occurs during the write command, the BRI
returns WRERR for the field that was not successfully written. If no tags are seen
matching the data condition, the BRI returns NOTAG<CRLF>OK><CRLF.
One other write error that can occur is a privilege error. This error is caused by a
reader attempting to write to tags that it does not own. Each reader that has
privileges enabled is only capable of writing to owned tags. If a privilege error is
encountered, the BRI returns PVERR in place of WRERR.
Here are three example responses to this WRITE command.
In this example response, both fields were successfully written:
H1234567890ABCDEF WROK WROK<CRLF>
OK><CRLF>
In this example response, there was an error writing
FINE
to the tag:
H1234567890ABCDEF WROK WRERR<CRLF>
OK><CRLF>
In the this example response, a privilege error was encountered and no data was
written to the tag:
H1234567890ABCDEF PVERR PVERR<CRLF>
OK><CRLF>
Note:
The INT, HEX, and STRING data types in the [WRITE FIELD] parameters in
the some of the previous examples do not include the optional
memory_bank
parameter that applies only to EPCglobal Class 1 Gen 2 tags. For help
understanding the memory bank, see the description of the
memory_bank
parameter
on
“HEX(memory_bank:address, length)” on page 24
.