You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche Barcode misreads

asked on March 21, 2014

We have a client that we have been working with for quite a long time that has been seeing an alarming high rate of barcode misreads on their scanning stations.  They currently scan thousands of documents a day and each and every one of them is separated by what we refer to as a "Batch Header Sheet". You will find a few samples attached to this post as "fig1 Redacted.pdf".  During the scan process into Quick Fields it is checked against 6 document classifications, once classified, it runs a process on the Batch Header sheet to pull information from up to three more barcodes, uses that information to perform a Realtime look-up against a SQL database to fill more indexing information, which is then used to sort and name the document.  

 

The issue occurs during the barcode reads, many times the barcode is not picked up which of course causes more issues down stream.  The issue started occurring when we moved the client from Laserfiche 7 to 8.  During that upgrade they also placed new scanning stations and Kodak scanners.  Their current scanning stations are Dell Pcs with dual core 3.2Ghz i5 CPUs, 4GB memory, 64bit Windows 7, and the scanners are Kodak i1420s and i4600s.

 

So here is the process that we took to test this issue and the results which seem to show two patterns.

 

Process 1.  I used their machine named CoCd10765 and confirmed all scanner settings, firmware versions, and LF versions. This PC has a Kodak i4600 attached directly to it and is linked into Quick Fields via Scan Connect and ISIS driver.  The staff gave me a sample set of documents which included 95 pages and 20 documents all divided by batch header sheets.  When I scanned the documents twice stopping between each set I ended up with the following:

 

Process 1 results:
40 documents with the possibility of 4 barcode reads per document.
Total possible barcode reads: 4x40 = 160
Total actual misreads: 12
Percentage of misreads: 7.5%

 

Ran this test a few more times and each time it might misread a different barcode here and there but many misreads stayed the same from test to test.

 

Process 2. I used their machine named CoCd10765 and confirmed LF versions.  This PC has a Kodak i4600 attached directly to it.  I used Kodak's Scan Validation Tool (SVT) to scan the same 20 documents, at the same DPI, ithresholding, and aggressive cropping settings, in the same order they were scanned earlier.  I then used Universal Capture as my scan source for Quick Fields.  When I scanned the documents twice stopping between each set I ended up with the following:

 

Process 2 results:
40 documents with the possibility of 4 barcode reads per document.
Total possible barcode reads: 4x40 = 160
Total actual misreads: 6
Percentage of misreads: 3.75%

 

Ran this test a few more times and each time the misreads stayed the same from test to test.

 

Process 3. This time I scanned them into a Kodak i1420 scanner attached to another machine.  I used Kodak's Scan Validation Tool (SVT) to scan the same 20 documents, at the same DPI, ithresholding, and aggressive cropping settings, in the same order they were scanned earlier.  I then moved those .tif files to their machine named CoCd10765.  I then used Universal Capture as my scan source for Quick Fields.  When I scanned the documents twice stopping between each set. I ended up with the following:

 

Process 3 results:
40 documents with the possibility of 4 barcode reads per document.
Total possible barcode reads: 4x40 = 160
Total actual misreads: 0
Percentage of misreads: 0%

 

I than ran this test over and over again until I had scanned 300 documents and my misread rate with still 0%.

 

This made me believe that it was an issue with the Kodak i4600 scanners so I began talking to the project manager from their IT group.  They expressed that the i1420 was misreading also but not as much as the i4600.  They attributed this pattern to the fact that the i4600s were used more often than the i1420.  Taking this extra piece of information into account we started looking very deeply at the Batch Headers that I was using verses the misread logs they captured for each scanning station.  We noticed another pattern, the longer/wider the barcode is the more it misread across any of the scanners.  So we did the following process to continue testing.

 

Process 4.  Took 100 new documents with much wider barcodes and used Kodak's Scan Validation Tool (SVT) to scan them into the Kodak i1420 scanner attached to another machine. Again at the same DPI, ithresholding, and aggressive cropping settings as they were used earlier.  Moved those .tif files to their machine named CoCd10765.  Used Universal Capture as my scan source for Quick Fields.  When I scanned the documents I ended up with the following:

 

Process 4 results:
100 documents with the possibility of 4 barcode reads per document.
Total possible barcode reads: 4x100 = 400
Total actual misreads: 4
Percentage of misreads: 1%


Additional notes:  
-During testing the documents were always scanned in the same order.
-During earlier testing we tried different manufactures of paper for the Batch Header sheets – No noticeable difference.
-During earlier testing we tried different printers – No noticeable difference.

 

Updates:
Since running these tests misreads have gotten worse.  I tried adding image enhancements, smooth and despeckle to the barcode process in the Quick Fields session.  This actually made the misreads worse.

 

The two patterns I am seeing:
-The misreads are more frequent on the Kodak i4600s.
-Barcodes that are longer/wider have a better chance of misreading.

 

At this point we are reaching out to Kodak and of course Laserfiche to get any help possible to correct this issue.

 

One thing that we thought of was the type of barcode that is used on the batch header sheets.  It is barcode 39 and is a font that is used to create the batch header sheets.  A Kodak rep explained that there are much better barcodes to use, and also each printer could space the barcode slightly differently because it is a font and not a rasterized image during the print.

 

So what is the best barcode to use?  I don't believe that is really the issue here, there is something else going on, but a test that I would like to try next is to use a different/better barcode to see if the misreads drop.

 

Other specs:
Quickfields: 9.0.0.460
Barcode: 9.1.0.0
Scan Connect 8.3

Kodak i4600: 1.1.11212.10001


 

 

0 0

Answer

SELECTED ANSWER
replied on March 21, 2014

I don't have a great answer but maybe some ideas and questions:

 

I can't speak to the Kodak scanners however.  Every one of our client uses a Canon DR series scanner.  

 

Most if not all of our client use Code 3 of 9 tall text font.  This font has stars on either side just like yours but the barcode is shorter (height).  They usually try to keep it size 12 pt or above.

 

From your sample picture it seems to me that the barcodes are very dark.  Have they been bolded?  Does the Kodak scanner have an auto brightness detection setting?  Even if yes or no try bumping the brightness of the scanner up a bit.  Again I am not certain but to me they look quite dark.  Also the clarity of the barcode looks iffy (just to my eyes).  Maybe it is the scanner.  Do you have a non Kodak scanner to try?  

 

Do you have a barcode reader that is not Quick Fields?  Like a wand or a hand held scanner of some type?  Curious if you hit those barcodes with another reader do you get a result.

 

Finally is your barcode in Quick Fields set as separate ones (separate boxes for each barcode) or one barcode that reads everywhere?  If they are all separate boxes, is there enough wiggle room for skews/paper movement?

 

I'd upload the font we use but it looks like Answers does not allow that file type.  Here's a pic.

 

 

Any problems our clients have had with reading are either traced to a dirty/poor scanner quality or the barcode being dark/printed poorly.  It can be finicky but we've always found a happy center with settings to get things reading. Unfortunately it has a lot to do with the hardware.

3 0

Replies

replied on May 12, 2014

Tony

Thanks for the reply.  A laser printer is used to produce the split sheets and they are scanned at no less than 300Dpi with iThresholding.

 

Over the last 6 weeks I have been able to reduce the misreads greatly.  There were two things that contributed to the clean up.

 

1.) Bold Barcodes - I went down this path because of Chris Ayre's post above.  Seems that the barcodes did have a "bold" attribute added to them in the source .xml that is used to create them.  I pulled that off and the misreads reduced greatly.  Not perfect but about 15 a day per scanner.  I found this strange and here is why...Those have been like that since LF/QF version 7 and never had an issue reading then.  I even pulled split sheets back from 4 years ago and they are bold and scanned fine, but with that said I am not going to look a gift horse in the mouth.

 

2.) Multizone Barcodes - This one I just stumbled on to while working on the last 15 misreads a day.  Again the pattern would follow the longer barcodes.  To be honest I was on a remote session pulling what hair I have left out and just needed to make some kind of change.  So I took a barcode that has three zones and broke out the zone that misread the most into a separate barcode with a single zone.  I told the client to run the scans again while I watched.  To my amazement hundreds of pages were scanned without a single misread. 

 

Over the last few days we have only seen 1 or 2 total misreads across all of their scanning stations.  I looked at each of those and they were a scanner quality issue.  They looked terrible...So I would clean and calibrate the scanner and scan again.  Each time the document would read fine the second time.

 

John

 

John

 

Last Friday after I rebuilt all of the classification

 

 

 

 

1 0
replied on March 21, 2014

Example of barcode misread

Example of Case Number Misread.PNG
0 0
replied on March 26, 2014

Chris,

 

Thanks for the reply, the bar-codes aren't bold.  The set I placed as a sample were scanned on our copier here so that is probably why they might look that way.

 

We do have bar-code guns and they read the printed bar-codes great.  In fact when the scanner misses the bar-code the scanner operator uses the bar-code gun to read the bar-code to fill the field.

 

They are all separate zones and yep they have plenty of wiggle room to capture the appropriate bar-code.

 

The scanners are cleaned before each batch which accounts to more than 10 cleanings a day right now.

 

Pretty lost with this one.

0 0
replied on April 7, 2014

Anyone from Laserfiche want to jump into this and help discuss?

0 0
replied on April 8, 2014

 

If you look closely at the barcode you will see there are some issues with the image. The way barcodes work is it calculates the lines and breaks and turns that into data. If the scan causes inadvertent breaks or connects unconnected lines, the barcode will not be read correctly.

 

Sometimes the image enhancement "smooth" can help (be sure to grow and shrink by the same amount to keep from permanently affecting the lines), but the issue here is in the scan quality.

1 0
replied on April 7, 2014

Chris where did you get that barcode font from?

0 0
replied on May 5, 2014

In case this hasn't already been resolved...

 

Are these barcodes printed from an inkjet or laser printer?

What resolution are they scanned at (200, 240 300)?

If less than 300 have they tried scanning at 300dpi?

 

Based on the sample images, like others have stated, the barcodes aren't very "clean" in the resulting scan. You want a high contrast solid black/white not blurred like the screenshots show.

To achieve this, I wouldn't limit configuring the scan settings (threshold/contrast etc) for the i4600 to be the same as the i1420 except for dpi. With most every Kodak scanner I setup to use iThresholding, I'll set "Contrast" to "-12" to get a cleaner higher contrast image.

I'd compare the barcodes as scanned from the i1420 with the i4600 by zooming in very close and then adjust settings on the i4600 till the barcodes are visually close. There ideally shouldn't be any "bleeding" of one barcode line into another.

You may also want to check into running a calibration on the i4600.

 

 

 

 

0 0
replied on January 30, 2015

The misreads haven't been solved yet and I am still having issues getting documents to scan without issue.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.