I need a Data Matrix code with the following Content: ]d201040689860218662110114644
Why does Lightburn change the Content to
]d1]d201040689860218662110114644
How do i avoid Lightburn to add ]d1?
I need a Data Matrix code with the following Content: ]d201040689860218662110114644
Why does Lightburn change the Content to
]d1]d201040689860218662110114644
How do i avoid Lightburn to add ]d1?
How are you doing this? Can you take a screenshot of where you’re seeing this?
I’ve tested LB with your text and it’s working as expected for me.
Here’s a screenshot of the result I get in LB. When I scan this I get back your original text without any additional characters.
What are you using to scan the code?
GS1 Barcode Scanner App
I’ve tried it with three different Android apps and all of them read it correctly. I can only assume that the app you’re using is at fault. I’d suggest trying it with a different app to confirm.
Do you use a normal DMC reader? A GS1-DMC is not a normal DMC.
You need a DMC reader that shows control characters.
GS1-DMC always start with ]d2
Normal-DMC always start with ]d1.
Thats why it is essential, that there is no ]d1 added.
All the reader apps I’ve tried are non-specific barcode readers and probably know nothing about GS1. I would expect them to read the full text string that’s encoded into the DMC image without attempting to interpret any characters as control characters. In my tests I have not seen any additional characters such as “]d1” added to the beginning of the encoded text string. This is why I suspect the app you’re using to be the cause of the prepended “]d1”.
Normal DMC-Readers hide Control Characters. Thats why you dont see them. But they are there.
It seems likely that the library used by LightBurn for DM generation is not configured to generate GS1 compliant bar codes or LighBurn does not expose the required flags to do so.
Let’s ask @adammhaile for comment.
There is a checkbox in the barcode dialogue regarding processing of control characters but I’m not sure exactly what it does to the generated image.
I agree though, that we need someone that’s more knowledgable in this realm to join in the conversation.
GS1 barcodes is exactly what that toggle is for. See this section of the docs:
Sorry, I meant toggle/switch rather than checkbox! Hopefully your answer will help the OP.
Correct. Because ]d1
is not a control character that LightBurn knows about.
Per the GS1 control code spec that I found when implementing this, it was basically just non-printable ASCII characters… since you can’t type those we needed a way to resolve normal text to them. Take a look at this: https://www.asciitable.com/
So, for example, if you want to include RS
(record separator) you would type it into the barcode tool as <RS>
and then have “Process Control Characters” checked.
That’s it. So it should work with GS1 control codes, it just might not work with the format that you are used to. I found many, many different entry formats and just picked the one that seemed most common… and the one that another customer at the time gave me as an example.
By definition in ISO/IEC 16022 GS1 DataMatrix uses a special start sequence to differentiate GS1 DataMatrix from other ISO/IEC Data Matrix symbols. This is achieved by using the Function 1 Symbol Character (FNC1) in the first position of the data encoded. It enables scanners to process the information according to the GS1 System Rules.
The FNC1 (codeword 232) has two separate uses in GS1 DataMatrix:
â– Start character.
■Separator character to separate element strings that are not in the predefined list (see Table ‎2‑3 ).
In accordance with ISO/IEC 15424 - Data Carrier Identifiers (including Symbology Identifiers), the Symbology Identifier is the first three characters transmitted by the scanner indicating symbology type. For a GS1 DataMatrix the symbology identifier is ]d2.
Source: GS1 DataMatrix Guideline | GS1
Hmm, ok. The customer I spoke with before said it worked for what he needed, but his use case must have been slightly different.
I’ll take a look at those docs more and see what I can do… probably can get you a beta build next week. I’ll need your help confirming it all works as needed as I have no way to actually test it with a scanner.
Do you have some news regarding a beta build for me?
No, sorry. I haven’t had a change to finish it and the week was short with the holiday. I will plan to get something sorted for the next 1.7 release, if possible.