BarTender-Specific Data Matrix Issue: Data After Embedded EOT (0x04) Is Not Encoded or Decoded, While Other Labeling Software Works Correctly
Hello,
We are using BarTender 2022 to create a Data Matrix ECC 200 label that complies with the Hyundai/Kia H/KMC supplier barcode standard.
We need to encode both an assembly part number and its component part number in a single Data Matrix symbol:
- Assembly part number:
52905X9210 - Customer component part number:
52910X9210
Under the H/KMC multi-part format, each record has its own header and trailer. The second record is placed after the first record, separated by a # character.
text
[First record header and data]
[GS][RS][EOT]
#
[Second record header and data]
[GS][RS][EOT]
Can BarTender 2022 encode an embedded ASCII EOT byte (0x04) in the middle of a Data Matrix ECC 200 payload while preserving all bytes that follow it?
The same H/KMC multi-record barcode structure has already been successfully implemented using other barcode-labeling software.
Our company has used BarTender as its primary label-design and printing software for approximately 10 years. However, among the software solutions we have tested, this issue occurs only when the barcode is generated using BarTender.
Other programs can successfully generate the required structure, including the embedded EOT byte followed by the `#` separator and the second record:
[GS][RS][EOT]#[Second record header and data]
The resulting labels are accepted and decoded correctly by the customer's H/KMC validation system.
Therefore, the required H/KMC structure itself is valid and technically feasible. This appears to be a BarTender-specific behavior involving the handling of an embedded EOT (`0x04`) followed by additional payload data.
Because our label templates, printing environment, and production processes have been built around BarTender for the past 10 years, replacing the software would have a significant operational impact. We would therefore appreciate a detailed technical investigation and, if applicable, a configuration change, workaround, hotfix, or product update that would allow BarTender to preserve and encode all bytes following the embedded EOT.
Please sign in to leave a comment.
Comments
0 comments