Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Micropdf417 barcode newbie

Status
Not open for further replies.

mcgyvr

Programmer
Aug 19, 2008
8
Need to start producing labels for our products with a 2d barcode using Micropdf417 symbology. I have no idea where to start. I tried using programs like zebra designer and wasp labeler but am having difficulties with getting the proper "encoding". Reminder I am a total newbie with no knowledge of zpl programming or anything past making a simple linear barcode (39)using the supplied design programs. Wasp labeler seems to be the best as it includes the ASCII character set described later in this topic.
I have 2 pieces of data that need to be included in the barcode
example
A product code: A1B2C3DAAA
Unique serial ID: TRMMI9GXH001 (this needs to be serialized so the next label will be TRMMI9GXH002

I' really stuck with how to get the proper encoding correct and entered.
I have been told my label should encode the data as follows
[)>{RS}06{GS}11PA1B2C3DAAA{GS}STRMMI9GXH001{RS}{EOT}
Where {RS} and {GS} and {EOT} are ASCII characters.

First question is what is "[)>" is that the ASCII "SOH" code or do I simply type it in as written?

I also need human readable data of the code and serial number next to the barcode.

I assume I should break this up into substrings and then use text linked to the substring to create the human readable portion. But I'm mainly stuck with how you get the encoding correct. It seems if I try it in 3 different programs I get 3 different barcodes.

Help...
 
A full description of the MicroPDF417 symbology is available in the (100+ page) specification document ISO/IEC 24728:2006(E) "Micro PDF417 bar code symbology specification", which may be purchased from ISO.

A detailed description is far too complex to be included here (and doing so would probably contravene the copyright on the ISO documentation), so the following is only a brief overview.

Generation of PDF417 and Micro PDF417 bar codes is done in two main stages: High-level and Low-level encoding.

High level
----------
• Convert the input data to a sequence of code word values.

The data may be converted using one or more compaction modes:
Text (default)
Byte
Numeric
An algorithm determines the most efficient switching between modes.

• If the required number of data code word columns (which must be in the range 1->30) has not been specified, calculate an appropriate value to give a suitable row : column ratio (e.g. 1.8 : 1).

• If the required error correction level (which must be in the range 0->8) has been specified, check that the symbol capacity is large enough.

If the EC level has not been specified, calculate the recommended minimum value.

• Calculate and add any necessary Padding code words.

• Calculate Error Correction code words.
This uses generator polynomials and Galois Field arithmetic (so not for the faint-hearted!).

Low level
---------
• Split Data and Error Correction code words into rows.

• For each row:
calculate & add Left/Right Row Indicator code words
add Start and End row characters

• Transform each encapsulated row into a series of symbol characters (bar-space sequences).
How this is done depends on the capabilities of the target printer.
For example, consider 'chunks' of bar-space sequences as 'mini-characters' (using a suitable font), or generate raster images to represent the sequences.


It may be the case, of course, that your printer supports all of the above (semi-)automatically, or that the printer vendor provides a suitable library to enable generation of the appropriate sequences.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top