Handheld Data Format Requirements General
Product Reference Guide 499
Code 39-Pharmacode (Code 32)
• Check character must be included in label data
• Label length including start, stop and check characters and excluding pre-
fix character must meet requirements imposed by the main scanner’s
fixed or variable label length control for this symbology type.
• Start and stop characters “*” must be included in label
• Prefix must be an ASCII character ‘p’
• Example: ‘p*123456789*’
Interleaved 2 of 5 (I 2 of 5)
• Check character must be included in label data
• Label length including check characters and excluding prefix character
must meet requirements imposed by the main scanner’s fixed or variable
label length control for this symbology type.
• Prefix must be an ASCII character ‘i’
• Example: ‘*i0123456789’
Codabar
• Check character must be included in label data
• Label length including check character and excluding prefix character
must meet requirements imposed by the main scanner’s fixed or variable
label length control for this symbology type.
• Prefix must be an ASCII character ‘%’
• Start stop character sets must meet the matching requirement set forth by
the scanner configuration item CI_CBAR_START_STOP_CHAR_MATCH
• Start stop character sets s must be of the form ABCD/ABCD and must be
included in the label
• Example: ‘%s$99.95s’
Code 128
• Prefix must be an ASCII character ‘#’
• Label length excluding prefix character must meet requirements imposed
by the main scanner’s fixed or variable label length control for this sym
-
bology type.
• Function characters may be transmitted as a hexadecimal value 8x. Where
x correlates to function characters 1 thru 4 as follows:
•x80 = function code 1
•x81 = function code 2
•x82 = function code 3
•x83 = function code 4
• For Code128 programming labels the format is of the general form ‘#/
82nnnnn/r ‘ - /82 is hexadecimal 82 and /r is carriage return
• Example: ‘#Code_128.Test’
MSI Plessey
• Check character must be included in label data
To Next Page
Loading...
