Code 128 Misreading? S’abonner

0
Avatar
Legacy Poster

Hi there,

We are using BarTender to print 8 digits serial number of our products on stickers,

We use code 128 and for years we had no problems getting the desired number to be scanned from the stickers.

Recently we observed two cases in which the serial number was scanned and a different number printed on the PC i.e the input from the barcode scanner was different from the right number which was printed on the sticker (for example if the number start with 14567....the PC recieved the number 04567....  - the 1 was replaced by 0, or in other case about 3 digits were replaced.)

When I tried to reproduce the problem the correct number was scanned  without any problems. meaning the right number was printed on the sticker)

Although I've notice the some areas of the bars are erased (usually horizontal lines erased at the bottom of the bars)

 

My questions are:

1. Do you know of any issues of barcode misreading , I mean not that the number is not read at all but it read wrongly, and if so what in the printing of such code can lead to these errors.

2. I know the code 128 has a check digit (which is marked as enabled by default on the BarTender SW. Is a regular barcode scanner 'knows' how to verify the content according to the check digit (We use Argox scanner AS-8150). is such error is possible if the check digit verification is enabled?

3. What do you recommend us to do in order to investigate this issue and understand the source of the errors?

 

Thanks!

Gil

 

4 commentaires

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Just to confirm, out of a larger print job which had correctly serialized numbers encoded into the barcode you found a couple of instances where the number was incorrect?  I take it then when viewing the pattern of the bars used to represent the barcode the faulty barcodes looked visibly different to their adjacent (correct) brethren?

 

Based on the limited info I have here, I would guess that the barcodes, unto themselves are correct.  Meaning you are scanning correctly what is printed, and it is what is printed that is wrong.

 

A check digit is part of the symbology and cannot be changed.  If the check digit didn't add up your scanner would either not read the code or report an error.  It sounds like your scanner is doing neither and so the code is good, all be it incorrect.

 

I would suspect that your printer suffered from a glitch in its memory during the print job, which resulted in the corruption in the data of what was printed.  Make sure the printer is updated to its latest firmware version, and/or give it a factory default reset for good measure in order to limit/eradicate the possibility of this happening again in the future.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Hi Ian,
Thank you for your fast response!
I just wanted to make myself clear- the issue we observed is that the serial numbers are printed correctly (most of the times the barcode reads them as expected), but in rare cases the barcode scans the same correct number but reads it as different number. (It looks like it is some of interuption that causes the error- this is what I try to figure out- what can cause a code that was acanned correctly many times, to suddenly be read as different number, if I understand you correctly the check digit verification reduces the chances for such errors to almost zero)
Please help me figure the mistory...
0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

It is possible that one of your scanners is configured differently.  I have ran into this problem before and it was a scanner that was not set up to read full Ascii.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Hi Slickson,
Thanks for your response.
I think it is possible that the scanner is configured differently, the thing is that the problem is inconsistent ,i.e. the same scanner that read wrongly the serial number from the sticker, when trying to reproduce the problem with the same scanner and the same sticker, it reads the number correctly (no change has been made to the configuration of the scanner)
could it be that some circumstantial settings caused the number to be read differently, when you've ran to this problem was is repeated or rarely happening with the scanner?
Thanks,
Gil

Vous devez vous connecter pour laisser un commentaire.