Code128 Barcode With Ascii 005 In It Seguir

0
Avatar
Legacy Poster

Hello,

 

I am trying to create a barcode for out wrist mount terminals to scan so they don't have to type certain control character sequences which helps them to navigate through our WMS software.  There are multiples that I need to be able to do, but form now I am attempting to do the one we use the most often and that is <ctrl>E.  When I check on the terminal what the Key code is when a <ctrl>E is pressed I can see that it is the ASCII 005 or <<ENQ>>.  When I add this control code to the barcode in Bartender, I get a barcode that looks right, however when I print it out, the scanner will not scan the barcode.  I have tried many different scanners and I know that the scanner will scan a Code128 barcode as we use them everyday.  I am not sure what is wrong with this barcode so I am looking for help with this.  Has anyone done anything like this before?  I need help!

 

Thanks,

Wade

8 comentarios

0
Avatar
Ian Cummings
Moderador
Acciones de comentarios Permalink

A CTRL+E does not equal an <ENQ> control code.  A <ENQ> control code is just that, an <ENQ> control code.  This is a keyboard scan code like a function key that does not have a ASCII value equivalent.  Instead you should configure your barcode scanners to substitute a value (or value combination) with the CTRL+E output that you want.

0
Avatar
Legacy Poster
Acciones de comentarios Permalink

I am not sure what you are talking about as far as the equivalence of <ctrl>E and <<ENQ>>, but I do know that I have been doing this for years with our current wireless terminals.  The hex value of <ctrl>E is "0005"  which when I look in a ASCII table hex 05 is <<ENQ>>.  Our current barcodes will not work with the new terminals we are demoing for some reason.  In the current barcodes we have printed "[hex 05]", which will give me a <ctrl>E as keyboard input.  My terminal vendor spoke with someone at Zebra about how to get the barcode to work and they created a barcode with <<ENQ>> in it and this barcode works.  I am trying to create the same barcode that Zebra created with B-coder(which i don't own) and I am trying to do it with Bartender(which I do own).  How can I make the barcode scanable when it just contains <<ENQ>> in it?  Am I going to have to get rid of Bartender and go to this B-coder product to do it?  Please help.

0
Avatar
Ian Cummings
Moderador
Acciones de comentarios Permalink

BarTender supports anything that is possible in Code 128 - you don't need to use a different software.  The <ENQ> value is supported in Code 128 in code set A only with a value of 69 (see the following chart: http://en.wikipedia.org/wiki/Code_128#Bar_code_widths).  In BarTender you can encode an <ENQ> value into a data source by clicking on the Omega symbol button, selecting the "Control Codes" tab and then double clicking the <ENQ> item to insert it.  If this does the job for what you want in your terminal input then great.  I would imagine that this is all the B-coder software is doing also.

0
Avatar
Legacy Poster
Acciones de comentarios Permalink

I have tried putting the <<ENQ>> into the barcode using the Omega symbol and that did not work.  I have tried using code set auto and code set A for the Code128 barcode and neither worked.  I am not sure what you mean by "The <ENQ> value is supported in Code 128 in code set A only with a value of 69 (see the following chart: http://en.wikipedia....Bar_code_widths)."?  I see that <<ENQ>> is in the table with a value of 69, but i am not sure what to do with this.  I attached a print screen of the barcode properties that I created.  Is there something I need to change?

 

0
Avatar
Ian Cummings
Moderador
Acciones de comentarios Permalink

From what I can see that will encode and <ENQ> control code into the barcode.  The wiki reference stuff was just for your info -- you don't need to do anything with it.  If the goal was to encode <ENQ> into the barcode then chances are it did indeed work.  However, is that really what is required?  Maybe the sample you have in encoding something else?  Do you have a printed image of the "working" barcode for us to view?

0
Avatar
Legacy Poster
Acciones de comentarios Permalink

Attached is the barcode I received from the vendor.  This really does not seem like it should be this hard.

0
Avatar
Ian Cummings
Moderador
Acciones de comentarios Permalink

I took a screen capture of the barcode you sent in the doc and pasted it above the barcode I have in BarTender.  As you can see, the bar/space elements in both match and thus are the same barcode.  When scanned in the result will be the same.

0
Avatar
Legacy Poster
Acciones de comentarios Permalink

Thanks for all your help!  I got it figured out.  It was so simple, if I would have just realized what I was doing in the beginning, that all could have been avoided.  I was scanning the new barcode with our old terminals and expecting it to work.  I tried the new barcode with the demo terminals and it works just fine.  Sorry for the inconvenience and thank you so much for your help!

Iniciar sesión para dejar un comentario.