HP Point of Sale rp5000 HP USB Barcode Scanner Programming Reference Guide - Page 103

Rules Hierarchy in Bar Codes, Scan Data Transmission

Get HP Point of Sale rp5000 PDF manuals and user guides View all HP Point of Sale rp5000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 103 highlights

Advance Data Formatting Rules Hierarchy (in Bar Codes) The order of programming individual rules is important.The most general rule should be programmed last. All programmed rules are stored in a buffer. As they are programmed, they are stored at the "top" of a rules list. If three rules have been created, the list would be configured as follows: Third Rule Second Rule First Rule When data is scanned, the rules list is checked from top to bottom to determine if the criteria matches (and therefore, if the actions should occur). Input is modified into the data format specified by the first matching set of criteria it finds. Be sure that your most general rule is the last one programmed. For example, if the THIRD rule states: When scanning a bar code of any length, send all data, then send the ENTER key. And the SECOND rule states: When scanning a Code 128 bar code of length 12, send the first four characters, then send the ENTER key, then send all remaining data. If a Code 128 bar code of length 12 were scanned, the THIRD rule would be in effect. The SECOND rule would appear to not function. Note also that ADF rules are actually created when you use the standard data editing functions. Scan options are entered as ADF rules, and the hierarchy mentioned above also applies to them. For the HP USB Barcode Scanner, this applies to prefix/suffix programming in the parameter Scan Data Transmission Format. Programming Reference Guide 4-7

  • 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
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
Advance Data Formatting
Programming Reference Guide
4–7
Rules Hierarchy (in Bar Codes)
The order of programming individual rules is important.The most
general rule should be programmed last.
All programmed rules are stored in a buffer. As they are
programmed, they are stored at the “top” of a rules list. If three
rules have been created, the list would be configured as follows:
Third Rule
Second Rule
First Rule
When data is scanned, the rules list is checked from top to bottom
to determine if the criteria matches (and therefore, if the actions
should occur). Input is modified into the data format specified by
the first matching set of criteria it finds. Be sure that your most
general rule is the last one programmed.
For example, if the THIRD rule states:
When scanning a bar code of any length, send all data,
then send the ENTER key.
And the SECOND rule states:
When scanning a Code 128 bar code of length 12, send the
first four characters, then send the ENTER key, then send
all remaining data.
If a Code 128 bar code of length 12 were scanned, the THIRD
rule would be in effect. The SECOND rule would appear to not
function.
Note also that ADF rules are actually created when you use the
standard data editing functions. Scan options are entered as ADF
rules, and the hierarchy mentioned above also applies to them.
For the HP USB Barcode Scanner, this applies to prefix/suffix
programming in the parameter
Scan Data Transmission
Format
.