Bar Code Processing Examples
The following table shows examples of stripping and prefix/suffix configurations. The examples assume that the scanner is configured to transmit an AIM identifier.
| Symbology |
|
|
| |
|
|
|
|
|
|
| All | Intrlv 2 of 5 (]IO) | Code93 | ||
|
|
|
|
|
|
Enable | Enabled | Enabled | Enabled | Enabled | Disabled |
|
|
|
|
|
|
Min length | 1 | 4 | 1 | 1 |
|
|
|
|
|
|
|
Max length | all | all | all | 10 |
|
|
|
|
|
|
|
Strip Code ID | Enabled | Enabled | Disabled | Enabled |
|
|
|
|
|
|
|
Strip Leading | 3 | 0 | 3 | 3 |
|
|
|
|
|
|
|
Strip Bar Code Data |
| ‘*123’ | ‘1*’ | ‘456’ |
|
|
|
|
|
|
|
Strip Trailing | 0 | 0 | 3 | 3 |
|
|
|
|
|
|
|
Prefix | ‘aaa’ | ‘bbb’ | ‘ccc’ | ‘ddd’ |
|
|
|
|
|
|
|
Suffix | ‘www’ | ‘xxx’ | ‘yyy’ | ‘zzz’ |
|
|
|
|
|
|
|
Provided that the wedge is configured with the above table, following are examples of scanned bar code data and results of these manipulations.
Bar Code Symbology | Raw Scanner Data | Resulting Data |
|
|
|
]C11234567890123 | bbb1234567890xxx | |
|
|
|
]C111234567890123 | bbb11234567890xxx | |
|
|
|
]C1123 | < rejected > (too short) | |
|
|
|
]E01234567890987 | ccc]E04567890yyy | |
|
|
|
]E01231234567890987 | ccc]E0234567890yyy | |
|
|
|
]E01234 | ccc]E0yyy | |
|
|
|
I2/5 | ]I04444567890987654321 | < rejected > (too long) |
|
|
|
I2/5 | ]I04444567890123 | ddd7890zzz |
|
|
|
I2/5 | ]I0444 | dddzzz |
|
|
|
I2/5 | ]I022245622 | ddd45zzz |
|
|
|
]G0123456 | < rejected > (disabled) | |
|
|
|
]G0444444 | < rejected > (disabled) | |
|
|
|
]A01234567890 | aaa4567890www | |
|
|
|
]A41231234567890 | aaa1234567890www | |
|
|
|
]A4 | < rejected > (too short) | |
|
|
|
Rejected bar codes generate a bad scan beep. In some cases, the receipt of data from the scanner triggers a good scan beep (from the external scanner), and then the rejection of scanned bar code data by the processing causes a bad scan beep on the same data.
8 - 34