Lexmark MX722 Forms and Bar Code Card P4.2 Technical Reference - Page 139

MaxiCode block call method, MaxiCode separator change, <Esc>s24800T1

Page 139 highlights

Lexmark Confidential until announced Appendix F - Deviations 139 1,1,01234567...... where 1,1, represents the structured append and 01234567.... represents the rest of the MaxiCode data structure. The HP BarDIMM Pro specification version 3.0 and later is consistent with this PCL data stream calling sequence: (s24800T1,1,x,01234567..... where x is either a 2 or 3, corresponding to MaxiCode Mode 2 or Mode 3. Mode 2 encodes numeric-only data, and Mode 3 allows a reduced amount of alphanumeric data. The mode of the MaxiCode is specified within the input data after the typeface command 24800T. If the two extra bytes (Mode 2 or 3 plus a separator) are included in the input data, then the BCE shows an error. Users must add more parsing that examines input data: • Byte 5 for either a 2 or 3 • Byte 6 for a separator character If the extra bytes are found, then remove them, and pass the four structured append bytes and the rest of the input data to the BCE. This method still allows existing HP-coded data streams to work on HP BarDIMM Pro, while allowing Forms and Bar Code Card to work correctly. MaxiCode block call method The minimum amount of input data to invoke a MaxiCode starts with this command: 1B 26 78 33 57 00 02 This command includes the following: • Esc & x 3 W (block bar code PCL call, with 3 following command bytes) • 0002 (the MaxiCode symbology identifier) • One or more of these data blocks (one per MaxiCode symbol): - 1B 26 79 34 57 - 31 1D 31 1D - 31 2C 31 2C These data blocks include the following: - Esc & y 4 W (data bar code PCL call, with 4 following data bytes) - 1 GS 1 GS or 1, 1, A valid MaxiCode data separator for the previous data block is either of the following: - Group separator-29 decimal (1D hexadecimal) - Comma- 44 decimal (2C hexadecimal) Any other separator characters produce an error on the page. MaxiCode separator change A valid MaxiCode with any encodable data requires a second separator for the PCL block call, and is placed after the number-of-labels field. If the four-byte structured append is specified alone, then Forms and Bar Code Card prints a valid MaxiCode symbol that is empty. Depending on the scanner used, Forms and Bar Code Card may not produce a valid scan. If an outdated three-byte structured append is specified alone, then Forms and Bar Code Card shows an error.

  • 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

1,1,01234567
......
where
1,1,
represents the structured append and
01234567
....
represents the
rest of the MaxiCode data structure.
The HP BarDIMM Pro specification version 3.0 and later is consistent with this PCL data stream calling sequence:
<Esc>(s24800T1,1,
x
,01234567
.....
where
x
is either a 2 or 3, corresponding to MaxiCode Mode 2 or
Mode 3.
Mode 2 encodes numeric-only data, and Mode 3 allows a reduced amount of alphanumeric data.
The mode of the MaxiCode is specified within the input data after the typeface command
24800T
. If the two
extra bytes (Mode 2 or 3 plus a separator) are included in the input data, then the BCE shows an error.
Users must add more parsing that examines input data:
Byte 5 for either a 2 or 3
Byte 6 for a separator character
If the extra bytes are found, then remove them, and pass the four structured append bytes and the rest of the
input data to the BCE. This method still allows existing HP-coded data streams to work on HP BarDIMM Pro,
while allowing Forms and Bar Code Card to work correctly.
MaxiCode block call method
The minimum amount of input data to invoke a MaxiCode starts with this command:
1B 26 78 33 57
00 02
This command includes the following:
Esc
& x 3 W (block bar code PCL call, with 3 following command bytes)
0002 (the MaxiCode symbology identifier)
One or more of these data blocks (one per MaxiCode symbol):
1B 26 79 34 57
31 1D 31 1D
31 2C 31 2C
These data blocks include the following:
Esc
& y 4 W (data bar code PCL call, with 4 following data bytes)
1 GS 1 GS or 1, 1,
A valid MaxiCode data separator for the previous data block is either of the following:
Group separator—29 decimal (1D hexadecimal)
Comma— 44 decimal (2C hexadecimal)
Any other separator characters produce an error on the page.
MaxiCode separator change
A valid MaxiCode with any encodable data requires a second separator for the PCL block call, and is placed
after the number-of-labels field.
If the four-byte structured append is specified alone, then Forms and Bar Code Card prints a valid MaxiCode
symbol that is empty. Depending on the scanner used, Forms and Bar Code Card may not produce a valid scan.
If an outdated three-byte structured append is specified alone, then Forms and Bar Code Card shows an error.
Lexmark Confidential until announced
Appendix F - Deviations
139