[sane-devel] Epson2 backend and ADF
Am 19.08.2013 02:56, schrieb Olaf Meeuwissen: > > Michael Koltan writes: > >> Am 03.08.2013 05:28, schrieb Olaf Meeuwissen: >>> >>> Olaf Meeuwissen writes: >>>> Precompiled binaries are available from: >>>> >>>> http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX >> >> The binaries didn't install because of a missing dependency, > > Which one? > Asking the question was to solve it. The missing dependency was ltdl3 and when I looked at the filename which explicitely stated, that it was compiled for ltdl3 I devined, that there is probably a binary for ltdl7. This installs flawlessly. >> but I was >> able to compile a deb-package for wheezy (after turning off the tests). >> But it didn't work correctly, and searching the error drove me nearly >> crazy until I realized, I was fighting with a hardware problem, not a >> software problem. After solving the problem with the adf, the epkowa >> driver now works perfectly without any changes! Thank you very much. > > Care to explain the hardware problem briefly? In fact there were two problems. First: The transport belt of the ADF gets slightly stuck when it is not used for several days. It is easy to solve this if you just move it some centimeters, but we didn't realize this for weeks. I had the suspicion, that I was fighting against a hardware problem, so I made a second mistake: Since we own two GT-1+ I put the ADF from one scanner to the other without realizing, that there is some rail installed at the scanner (not the ADF) to guide the paper. So the scanner did some very funny things with the paper. Installing the ADF back to the first scanner and slightly moving the transport belt before scanning worked miracles after weeks of frustration. > >> I am now trying to change the epson2 driver accordingly; since the >> epkowa driver supports the nifty feature to determine automatically the >> scan area for paper from the adf I will try to incorporate this in the >> epson2 driver. > > Why bother if you can just use the epkowa driver? > # I'm solliciting user input here. I can think of a few reasons myself > # but I'd like to back them up with user feedback. > First of all, I think, sane should work out of the box and that you shouldn't have to install third party modules. Most users will give up frustrated when they install sane, get their scanner working somehow (with the epson2 backend) and then realize, that features are missing. Most users won't google around and search if there is another backend they might install. I would think that at that point about 90% of the users are giving up. This is bad advertising for open source software. Secondly I'm not sure how long Epson will provide the epkowa backend for newer versions of linux. There is always a chance, that it will disappear. And then I have at least one of the virtues of a good programmer: I'm lazy. If I have fixed the epson2 backend, further updates will require much less work. And programming is much more fun (if you aren't stuck with hardware problems) than searching for additional packages on the internet. Thanks again for your help Michael
[sane-devel] Epson2 backend and ADF
Am 03.08.2013 05:28, schrieb Olaf Meeuwissen: > > Olaf Meeuwissen writes: >> Precompiled binaries are available from: >> >>http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX > The binaries didn't install because of a missing dependency, but I was able to compile a deb-package for wheezy (after turning off the tests). But it didn't work correctly, and searching the error drove me nearly crazy until I realized, I was fighting with a hardware problem, not a software problem. After solving the problem with the adf, the epkowa driver now works perfectly without any changes! Thank you very much. I am now trying to change the epson2 driver accordingly; since the epkowa driver supports the nifty feature to determine automatically the scan area for paper from the adf I will try to incorporate this in the epson2 driver. Thanks and greetings Michael
[sane-devel] Epson2 backend and ADF
This is a lot more work than I thought. I had the backend working perfectly right. But after rebooting, the scanner did constantly hang after sending the feed command (0x16) and then requesting the extended status (ESC-f). Has somebody a suggestion what the cause of this may be? As to the questions of Olaf: I upgraded in two steps, first from from lenny to squeeze. I compiled iscan-2.29.1 with the epkowa backend 1.0.15 in squeeze. The compilation worked, although some test failed. But the backend then produced an errormessage which I don't have anymore, but I think it was the same as on wheezy (see below). After that I decided just to upgrade to wheezy and check, if the newest epson2 driver would be working. It didn't. The I recompiled iscan, but the backend gives the errormessage: "scanimage: open of device epkowa failed: Access to resource has been denied". Then I decided to fix the epson2 backend instead of the epkowa backend, because alread on lenny the epkowa backend didn't work 100% correctly. Duplex worked fine, but there was a problem when scanning simplex (I don't remember what it was, but I think it didn't scan the last sheet). So on lenny I had to switch between 1.0.15 and 1.0.19 of the epkowa driver for simplex respective duplex, because the 1.0.19 backend failed on duplex. I'll try again on the weekend to fix the epson2 driver - I think I miss just one tiny bit of the puzzle... Greetings -- Michael Koltan Schongauerweg 61 79110 Freiburg 0761 / 76 78 033
[sane-devel] Epson2 backend and ADF
Am 30.07.2013 01:35, schrieb Olaf Meeuwissen: > Michael Koltan writes: > >> Hi there, >> >> I'm using an Epson GT-1+ Scanner with an ADF; after upgrading to the >> latest debian version the epkowa backend I used stopped working, > > Which Debian versions? From squeeze to wheezy? > What iscan and iscan-data package versions do you have installed? > > In what way did it stop working? Were there any indications as to why > it stopped working? What have you tried to get it to work again? > Hi Olaf, thank you for your reply. I get back to you with the exact informations on Thursday - I do this for a social project where I volunteer once a week, so I don't have the errormessage and the version info at the moment. Greetings Michael
[sane-devel] Epson2 backend and ADF
Hi there, I'm using an Epson GT-1+ Scanner with an ADF; after upgrading to the latest debian version the epkowa backend I used stopped working, so I started patching the epson2 backend to get it working with my scanner and ADF. I found quite a number of bugs regarding the ADF in the driver, which I think I have mostly fixed now and will eventually publish as a patch. But for the last fix I need some information from you guys. The problem occurres when scanning duplex: The backside of the last page does not get scanned because the scanner reports that the adf is out of paper after scanning the front side. This in itself is not a big problem: I just have to track while scanning duplex whether I am on a front page or a back page and ignore the out of paper status when the next page to scan is a back page. My question however is: Does anyone of you know if all epson scanners with adf behave this way? Then I may write a general fix for this problem. Or is this a bug in the GT-1+ firmware and other scanners report out of paper after scanning the last back page in duplex mode (which would make a lot more sense)? Then I would have to mark this as a specifig GT-1+ fix. Or is there an additional status flag that offers information if there is still an unscanned backpage inside the scanner? It would be great if you could help me with this. And, by the way: To whom do I send the patches when I have a stable version of the driver? Thanks in advance Michael
