Lexmark X864 Forms and Bar Code Technical Reference - Page 162

B 26 78 33 57, hex 1D, decimal 29, hex 2C, MaxiCode Block Call method

Get Lexmark X864 PDF manuals and user guides View all Lexmark X864 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 162 highlights

2 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: a Esc & x 3 W (block bar code PCL call, with 3 following command bytes) b 0002 (the MaxiCode symbology identifier) c 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: - 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 data block above is either: - Gs: hex 1D, decimal 29 - comma: hex 2C, decimal 44 Any other separator characters should produce an error on the page. 3 MaxiCode Separator Change (add a second separator character) In the past, for all modes, the input data had to start with a label-number field and number-of-labels field. Both fields were one digit in length, and were terminated with either a comma or group separator. This required parsing only the label-number field, a single separator, and a number-of-labels field: For example: 1 Gs 1 or 1 , 1, Now, a second separator is required for this PCL block call, and is placed after the number-of-labels field. For a valid MaxiCode with any encodable data, this would always be the case anyway. If the 4-byte Structured Append is specified alone, then the Forms and Bar Code Card should print a valid MaxiCode symbol that is empty (no data). Depending on the scanner used, it may not produce a valid scan. If an old-style 3-byte Structured Append is specified alone, then the Forms and Bar Code Card should throw an error. Deviations 159

  • 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
Deviations
159
2
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:
a
Esc & x 3 W (block bar code PCL call, with 3 following command bytes)
b
0002 (the MaxiCode symbology identifier)
c
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:
–
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 data block above is either:
–
Gs:
hex 1D, decimal 29
–
comma:
hex 2C, decimal 44
Any other separator characters should produce an error on the page.
3
MaxiCode Separator Change (add a second separator character)
In the past, for all modes, the input data had to start with a label-number field and
number-of-labels field. Both fields were one digit in length, and were terminated with either a
comma or group separator.
This required parsing only the label-number field, a single separator, and a number-of-labels
field: For example:
1 Gs 1
or
1 , 1,
Now, a second separator is required for this PCL block call, and is placed after the
number-of-labels field. For a valid MaxiCode with any encodable data, this would always be
the case anyway.
If the 4-byte Structured Append is specified alone, then the Forms and Bar Code Card should
print a valid MaxiCode symbol that is empty (no data). Depending on the scanner used, it
may not produce a valid scan.
If an old-style 3-byte Structured Append is specified alone, then the Forms and Bar Code
Card should throw an error.