Kodak i1440 Paper Jam

[Eric PengParticipant Topics - 1Replies - 1Total Posts - 2]

Hi,

I’m developing a TWAIN scanning application for Kodak i1440 scanner. I downloaded some free TWAIN libraries (C++ Twain Wrapper from CodeGuru, CTwain Library & EZTwain Classic from Dosadi) for survey, and I encountered a problem.

When paper jamed the DS’s dialog will display a message tell user paper jam has happend. I remove the paper in the autofeeder and press ok to continue the job, then the sample app stop any response. I have to use Process Manager to terminate the app and restart the scan job.

I use the Kodak Scan Validation Tool to test this problem, it works fine.

Does anybody has any idea to solve this problem?

Thanks in advance.

Eric

[gabeParticipant Topics - 9Replies - 583Total Posts - 592]

what does the sample app (in code) do when the paperjam?

If I had to guess (and I do without some code to look at) I would say that it sounds like your messageloop, are you updating your internal twState variable and then not processing messages from the source?

.

[Eric PengParticipant Topics - 1Replies - 1Total Posts - 2]

gabe,

Thanks for your reply.

I’ve test following TWAIN Libraries:
1. A C++ Wrapper for TWAIN by Rajiv Ramachandran (http://www.codeproject.com/KB/audio-video/twaintest.aspx)
2. Dosadi’s CTwain Library (http://www.dosadi.com/ctwain.htm) and EZTwain Pro 3.0 (http://www.dosadi.com/eztwain3.htm)

I run the program in debug mode. After paper jamed, when app. call DG_CONTROL/DAT_PENDINGXFERS/MSG_ENDXFER triplet, it won’t return, and the app stop response.

I’ve test TWAIN toolkit’s Twack_32 and it runs well. But it use plain Win32 SDK and I can’t find out the difference. 🙁

[gabeParticipant Topics - 9Replies - 583Total Posts - 592]

if you look at the Twain.log in %temp% when you run a program that does what you want and compare it to the log from your program you can often see what triplets were called differently.

.

[jadams3243Participant Topics - 1Replies - 3Total Posts - 4]

Hi Eric,

I am curious to know if you had success to resolve this issue with Kodak. We have a new custom applicaton and we are experiencing the same exact problem with a Kodak i640 scanner. We have tested successfully with Canon, Panasonic, and Fujistu, but the application locks with Kodak.
Same scenario, paper jam or no paper in feeder locks that application. Any suggestions? Any help would be greatly appreciated.

Jim

[HOHXPParticipant Topics - 2Replies - 34Total Posts - 36]

I’ve experinced same problem also, ALL other brands works OK, Canon, Panasonic, Avision, Ricoh, Konica Minolta, HP, Fujitsu and more. ONLY ther Kodak drivers acts strange on a paper jam. Hopefully a Kodak developer is watching and will test their drivers with 3rd party applications, not just their own and fix this issue. Customers of ours has been i contact with Kodak but they just say like “No problems with our applications so it must be a problem with your application”. I DO think this is a bug or a srange behaviour in Kodak drivers. Also to my knowledge it is only some of them, not on all Kodak scanners. If a Kodak engineer reads this, post some information on how to handle paper jams.
HOH

[jadams3243Participant Topics - 1Replies - 3Total Posts - 4]

We finally did get resolution to this issue and found that we had two problems. One was in our code and one was in the Kodak driver. I will discuss this with our programmers and see if we can get a detailed description of the solution up very soon. Just wanted to let you know that we spoke with the Kodak engineers and they verified there was a problem with the “old” driver.

[HOHXPParticipant Topics - 2Replies - 34Total Posts - 36]

Can you post an e-mail adr to the Kodak engineers ?

[jadams3243Participant Topics - 1Replies - 3Total Posts - 4]

Hi,
I didn’t actually speak with Kodak. We ended up using a consulting company with great Twain knowledge. They had the contacts at Kodak. The company we used is JFL Peripherals.

[HOHXPParticipant Topics - 2Replies - 34Total Posts - 36]

Hello,

I still have this problem on i1440 and i620 but runs OK on several other scanners like i1320 Plus, 4500. Do you have any information how to solve this ?
Seems like Kodak drivers acts different between models. Strange.

Regards

[Author]

Posts