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

Understanding ACCESS and KILL Passwords

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 116 highlights

Chapter 4 - BRI Commands Consider the third example: This READ command reads the entire string field of the first example. The command stops reading after 20 characters. READ STR(18,20) "abcdefghijklmnopqrst" OK> Consider the fourth example: This READ command reads 25 characters from tag memory. The WRITE command in the first example wrote 20 ASCII characters up to location 37. The characters from 38 to 42 were not changed by that WRITE command. They may not represent printable ASCII. Characters that are not printable ASCII are returned as hex characters in the form \xnn. Suppose the characters on the tag are a period (.) followed by two carriage-return and line-feed characters. For example: READ STR(18,25) "abcdefghijklmnopqrst.\x0d\x0a\x0d\x0a" OK> Consider the fifth example: Smaller sections of this same data could be read out with this command: READ STR(18,5) "abcde" OK> Understanding ACCESS and KILL Passwords EPC Global Gen 2 tags contain a security feature that is controlled by the password values stored in memory bank 0. These ACCESS and KILL passwords that are contained in the EPC Global Gen 2 tags are 4 bytes in length: • ACCESS passwords control how data is read or written to EPC Global Gen 2 tags. The ACCESS password is stored in the second 4 bytes of memory bank 0 and can be specified using the syntax HEX(0:4,4). • KILL passwords are used by the KILLTAG command to kill an EPC Global Gen 2 tag. The KILL password is stored in the first 4 bytes of memory bank 0 and can be specified using the syntax HEX(0:0,4). By default, the passwords in memory bank 0 are set to 0. When the password values contain a 0, the tags can be read and written by the PROTECT command. The READ, WRITE, PROTECT, and KILLTAG commands each have an option for specifying a password. Once the ACCESS and KILL passwords have been set in a tag, the ability to read, write, protect, and kill tags requires the use of a password to complete the operation. For ACCESS passwords, there are different rules in regards to read and write operations once the access password has been set. 104 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
104
Basic Reader Interface Programmer Reference Manual
Consider the third example:
This READ command reads the entire string field of the first example. The
command stops reading after 20 characters.
READ STR(18,20)<CRLF>
“abcdefghijklmnopqrst”<CRLF>
OK><CRLF>
Consider the fourth example:
This READ command reads 25 characters from tag memory. The WRITE command
in the first example wrote 20 ASCII characters up to location 37. The characters
from 38 to 42 were not changed by that WRITE command. They may not represent
printable ASCII. Characters that are not printable ASCII are returned as hex
characters in the form \x
nn
. Suppose the characters on the tag are a period (.)
followed by two carriage-return and line-feed characters. For example:
READ STR(18,25)<CRLF>
“abcdefghijklmnopqrst.\x0d\x0a\x0d\x0a”<CRLF>
OK><CRLF>
Consider the fifth example:
Smaller sections of this same data could be read out with this command:
READ STR(18,5)<CRLF>
“abcde”<CRLF>
OK><CRLF>
Understanding ACCESS and KILL Passwords
EPC Global Gen 2 tags contain a security feature that is controlled by the password
values stored in memory bank 0. These ACCESS and KILL passwords that are
contained in the EPC Global Gen 2 tags are 4 bytes in length:
•
ACCESS passwords control how data is read or written to EPC Global Gen 2
tags. The ACCESS password is stored in the second 4 bytes of memory bank 0
and can be specified using the syntax
HEX(0:4,4)
.
•
KILL passwords are used by the KILLTAG command to kill an EPC Global Gen 2
tag. The KILL password is stored in the first 4 bytes of memory bank 0 and can
be specified using the syntax
HEX(0:0,4)
.
By default, the passwords in memory bank 0 are set to 0. When the password values
contain a 0, the tags can be read and written by the PROTECT command. The
READ, WRITE, PROTECT, and KILLTAG commands each have an option for
specifying a password.
Once the ACCESS and KILL passwords have been set in a tag, the ability to read,
write, protect, and kill tags requires the use of a password to complete the operation.
For ACCESS passwords, there are different rules in regards to read and write
operations once the access password has been set.