GS1 AI syntax with GS separators

[xjpf]

How to make Data Matrix with this message?

0102900285850353215EtQT"cSm,oH1{GS}91EE09{GS}92/kklRSOz6PDV69t9tX6Rmh+zmIx01fCo+2FZVYbAyd4=

Should look like this:

(but this one doesnt have fnc1)

[xjpf]

Tried to split input data like this and encode using the gs1datamatrix encoder:

gtin   = '02900285850353'
smth   = 'EE09'
serial = '5EtQT"cSm,oH1'
tail   = '/kklRSOz6PDV69t9tX6Rmh+zmIx01fCo+2FZVYbAyd4='

data   = f"(01){gtin}(21){serial}(91){smth}(92){tail}"

Got a Data Matrix, but the problem is that ALL delimeters are FNC1, while need those to be GS (ASCII 29).

Is it possible to encode GS as the AI separator in the message?

[terryburton]

Aside: Your initial symbol is malformed since it does not contain FNC1 in first character position which required for GS1 Data Matrix barcodes (i.e. containing AI element string syntax).

What you require is to use the gs1datamatrix encoder with the input (01)02900285850353(21)5EtQT"cSm,oH1(91)EE09(92)/kklRSOz6PDV69t9tX6Rmh+zmIx01fCo+2FZVYbAyd4=.

BWIPP will generate a symbol that contains FNC1 separators within the internal message data, as this is the correct (canonical) thing to do. Readers shall pass the FNC1 separator codewords as GS characters to the host.

More detail is provided here.

[xjpf]

Sorry forgot to mention, that I'm using exactly the gs1datamatrix encoder.

And if you scan generated picture I've added, you'll find out that there is 3 FNC bytes:

• One as the header - Perfect
• Two as AI delimiters - Delimiters should be GS, not FNC1

[terryburton]

The use of the GS character as an element separator is tolerated precisely because the barcode reader transfer protocol is to transmit the non-data FNC1 separator characters as GS (ASCII 29), and therefore the receiver is none the wiser as to whether a (canonical) non-data FNC1 character or a regular ASCII GS character was used in the message encoded within the barcode symbol.

FNC1 is the the canonical separator and BWIPP will not allow you to do otherwise without manually driving the encoding using the regular datamatrix encoder with the parse and parsefnc options:

^FNC10102900285850353215EtQT"cSm,oH1^GS91EE09^GS92/kklRSOz6PDV69t9tX6Rmh+zmIx01fCo+2FZVYbAyd4=

However, this method is error prone. So my advice is to leave it to BWIPP to do the right thing, as per the documentation.