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

Using AND/OR Logic in Data Conditions, Data Fields Supported by Different Tag Types

Page 42 highlights

Chapter 3 - Understanding BRI Programming Elements In this example, INT(0,1) specifies that an integer of one byte length starting at address 0 of the tag memory will be compared with integer value of one as specified by =1. You can use the keyword NOT in the data condition when you use native tag selector logic. If a data condition contains NOT, the matching tags are not selected. All data conditions are processed from left to right. The following example applies only to ISO 18000-6B tags because it contains the > operator. Suppose you want to implement the following expression where data is the integer values at address 18: 100 < data < 200 You can specify this condition using this selector logic: WHERE INT(18,1) > 100, NOT INT(18,1) > 199 The first condition selects all ISO 18000-6B tags whose data at address 18 is greater than 100. The second condition then unselects all tags whose data at address 18 is greater than 199. This data condition sequence implements the specified expression. Using AND/OR Logic in Data Conditions WHERE [ ] AND [ ] OR... where: is one of the data types described in "Data Field Definitions" on page 22. is one of the operators described in the following table, "Operators for AND/OR Logic Data Conditions." is one of the constants described in "Constants" on page 22. It should be noted that WHERE clauses are only allowed when the TAGTYPE attribute is set to a single tag type. WHERE clauses are not allowed in operations involving multiple air protocols. Wildcards may also not be used if TAGTYPE has more than a single value. The data in the WHERE clause conditions depends on the TAGTYPE used. Data Fields Supported by Different Tag Types Tag Type G1/ISO6BG1 G2/ISO6BG2 ICODE119 UCODE119 or V119 EPCC1G2 Data Field HEX, INT, STRING HEX, INT, STRING HEX, INT, STRING HEX, INT, STRING BIT, HEX, INT, STRING 30 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 3 — Understanding BRI Programming Elements
30
Basic Reader Interface Programmer Reference Manual
In this example,
INT(0,1)
specifies that an integer of one byte length starting at
address 0 of the tag memory will be compared with integer value of one as specified
by
=1
.
You can use the keyword NOT in the data condition when you use native tag
selector logic. If a data condition contains NOT, the matching tags are not selected.
All data conditions are processed from left to right.
The following example applies only to ISO 18000-6B tags because it contains the
>
operator. Suppose you want to implement the following expression where
data
is the
integer values at address 18:
100 <
data
< 200
You can specify this condition using this selector logic:
WHERE INT(18,1) > 100, NOT INT(18,1) > 199
The first condition selects all ISO 18000-6B tags whose data at address 18 is greater
than 100. The second condition then unselects all tags whose data at address 18 is
greater than 199. This data condition sequence implements the specified expression.
Using AND/OR Logic in Data Conditions
WHERE [<
Data Field
> <
Operator
> <
Constant
>] AND [<
Data Field
>
<
Operator
> <
Constant
>] OR...
where:
<
Data Field
>
is one of the data types described in
“Data Field Definitions” on
page 22
.
<
Operator
>
is one of the operators described in the following table, “Operators
for AND/OR Logic Data Conditions.”
<
Constants
>
is one of the constants described in
“Constants” on page 22
.
It should be noted that WHERE clauses are only allowed when the TAGTYPE
attribute is set to a single tag type. WHERE clauses are not allowed in operations
involving multiple air protocols. Wildcards may also not be used if TAGTYPE has
more than a single value.
The data in the WHERE clause conditions depends on the TAGTYPE used.
Data Fields Supported by Different Tag Types
Tag Type
Data Field
G1/ISO6BG1
HEX, INT, STRING
G2/ISO6BG2
HEX, INT, STRING
ICODE119
HEX, INT, STRING
UCODE119
or V119
HEX, INT, STRING
EPCC1G2
BIT, HEX, INT, STRING