Scan to Folder - Issue or poorly designed system?

[ivanivanov]

Why about if you scaned 500-600 pages using build job. If jamed in the last pages need scaned again. It hapened so many time and it`s so bad. Why Toshiba is doing so well, need scaned only the pages jamed in the document feeder and continue?????

[KO]

It is a poorly designed system.  We just received our copier and already I'm dreading the next years of the lease.

If my scan job has different size pages which end up being a mix of document feeder and glass scanning, when it jams on page 19 I cannot just throw the previous pages into the doc feeder because some are receipts or small pages that won't go through the doc feeder.

I am forced to cancel the job and start over.  Not fun.

[JoeDaft]

How about using ‘Job Build’ and doing 20 pages at a time?

[vlotta]

Reloading the whole scan doesn't re-image all the pages. It merely counts the number of pages that had already been scanned and starts imaging the pages after it sends the amount of pages that were already imaged. So if the system knows that it has the image of the pages prior to the jam then why send them through again just to be counted. As for the scanner being reliable I agree but unfortunately the situation that I am referring to will always have jamming issues and previous MFP’s from competitors allowed the user to resolve the jam and then continue scanning without adding all the pages back in. This seems like a Xerox process not industry. It would be great if the customer could have the final decision on turning off this function if they wished to.

[JoeDaft]

I can see your point however I feel it is designed correctly.

Bearing in mind the DADF is very reliable and jams should be rare I feel most people would be more confident reloading the whole scan so all pages are imaged.

It could be dangerous only scanning the remaining few incase a critical page is missed. Xerox or any manufacturer wouldn’t want to risk this.

At 139ipm that extra minute or two rescanning the full file is worth spending to guarantee the file is complete.

[vlotta]

That seems like a poorly designed system. So if I’m scanning 150 pages and it jams on page 145 with this system I would have to re-scan all 145 pages again instead of just the 5 remaining pages. Is there a setting to bypass this?

Also as I was testing this it seems as the machine doesn't actually scan a new image of the previous pages it only sends them through the feeder and counts them and then starts scanning the image of the pages after it sends through the correct amount of pages that was sent prior to the jam. With that being the case the machine is keeping the image of the pages prior to the jam in the system so why make us re scan or send through the doc feeder all the previous pages if they aren't being scanned?

How i tested this. Numbered 6 pages. Damaged page 3 so it would jam. Started the scan, and when page 3 jammed i pulled it out and only added it back to the doc feeder. Resumed the scan. It finished and sent me the file with the image of Page 1,2,5,6 It didn't rescan the first two pages after clearing the jam which would have been page 3 and 4 it used the image of the original first two pages and only sent page 3 and 4 through the feeder to count them. 

With that being the case I can't see any reason why to resend the pages before the jam back through, this is a waste of time.

The issue with why this isn't acceptable is that I am scanning big files that I receive from my clients. They have mixed sizes and quality of pages as they are sending me all their receipts and bank statements for the year. I have always and will always have paper jams due to the quality of paper I receive but with my previous machine ( a competitors machine ) I didn't  have to send the pages that were already scanned back through. With this system I have to be able to scan the complete package completely without any jams or I will not be able to finish the file. 

[MSPTestAccount]

Thank you vlotta for using the Customer Support Forum.

This response is to help answer your questions regarding the design of the device and the 'Scan to email' and 'Scan to folder' processes and contributed from our Escalated Support Specialist:

After investigation I am writing to inform you that the device is behaving as per design. When a Jam occurs in the Document Feeder when scanning, ALL originals will need to be loaded back into the document feeder (as the message dictates) and scanned through again.

You will notice in both possible messages that appear on the machine “Re-sort and reload ALL the originals” and/or “Re-order and reload ALL the originals” are displayed.

When you resume the scan, the machine knows how many pages were scanned already, if you scan LESS than that amount that was already scanned, the message to re-order or re-scan will continue to re-appear, because it is waiting for the correct amount to be scanned in again.

We hope this helps you.

[vlotta]

Altalink C8045 scan to folder issue. When scanning to folder if the documents that I am scanning gets jammed in the doc feeder the system allows you to remove the jam and then either continue or cancel job. If you hit continue and finish the job the system will ask you again if you want to continue or cancel it will not send the job. We have been told that you need to re insert all the previous scanned papers back into the doc feeder when you click continue. When testing this it did work but this should not be the case. With this set up if you are scanning 150 pages and it jams on page 145 you would have to re scan all 145 pages. This is either a issue or poorly designed system. I'm hope it is an issue and not how it was designed. 

Also this is not the case if you scan to email. If it jams during scan to email all you need to do is clear the jam and continue with the job where it left off.