[sane-devel] Canoscan 8800F]
Hello Kurt, I am concerned about this part of the log file: [pixma] pixma_open(): Canoscan 8800F [pixma] WARNING:pixma_write(): count(0) != len(16) [pixma] OUT T=3.054 len=-1 [pixma] :ef 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] ERROR: EIO It looks as though the scanner is not responding even at the start of the operation. Maybe you can try setting more debug options to 255: DEBUG_SANE DEBUG_SANE_SANEI_USB SANE_DEBUG_DLL And then send me the log file (or a link to it). I don't know what changes there might be that Canon has made in firmware perhaps, but maybe there is some other problem unrelated to the scanner itself that can be determined from the raw USB communications. You might also try sane-test (see man page) to test your sane installation, and set SANE_DEBUG_TEST to 255 for that. Best regards, Gernot Hassenpflug
[sane-devel] Scan server = saned + xinetd?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grant : I've had a scan server set up for a while which uses saned via xinetd. Is there a simpler way to set up a scan server with fewer permissions to grant? The configuration seems a lot more complex than my printer server which has only cupsd.conf config on the server and client.conf config on the client. That's partly because the CUPS daemon is running independently and continuously. With a xinetd + saned setup, xinetd is listening for requests and starts saned every time it gets a request on port 6566. You could try a setup where you have saned running independently, just like cupsd, without xinetd. I use Gentoo and they don't have a saned initscript in /etc/init.d for some reason. Because normally you don't want to have saned running all the time. It shouldn't be too hard to write one based on an existing init.d script. Note that with saned your scan server still communicates with a local USB device. That is, saned is the scan server's SANE frontend of choice. The client then uses the SANE net backend (via the client's SANE frontend of choice) to talk to the server. I noticed that /etc/sane.d/* has network ability, but that's for communicating with a network scanner directly, right? Depends on what * stands for ;-) How about /etc/sane.d/epkowa.conf and /etc/sane.d/epson2.conf? epkowa.conf contains fairly extensive documentation on the use of its 'net' keyword. This is used to setup network scanners (w/o the use of a scan server), that is, a direct network connection. The epson2.conf seems to follow a similar approach and seems to support automatic discovery of network scanners. I'm not familiar with the epson2 backend's internals, though. I tried to set up network scanning with epkowa and my Epson Artisan 710 but I couldn't get it to work, I think because I don't know which port to define on the scanner's IP. Does anyone have any suggestions for that? First of all, you need the (binary-only, non-free) iscan-network-nt package installed. Second, you need to follow the instructions in /etc/sane.d/epkowa.conf WRT configuring a network scanner. There is no need to specify a port number, the default (1865) should do. Follow the instructions in the product manual to determine/assign the IP address of the device. Is iscan-network-nt available for free? I had assumed iscan-network-nt was included in Gentoo's iscan package but I must have been wrong. Does anbody here know if there is an ebuild available? If not, I'll file a bug with Gentoo. Free of charge? Yes. Free-as-in-freedom? No. AVASYS Corporation does not bundle the non-free (as in freedom) extensions for the epkowa backend with Image Scan! for Linux. Note that with this setup your SANE frontend of choice communicates with the device via the epkowa backend over a network connection. Neither saned nor the SANE net backend are involved. If that still does not make things work, your client machine's network setup (or a router somewhere on the way to the device) may be blocking the network traffic. Darned firewalls. Another reason we are aware of is the epson2 backend getting in the way. Disabling that in /etc/sane.d/dll.conf may help. FWIW, the epson2 backend may also support the device's network interface but that will not work with Image Scan! for Linux. As Alesh pointed out earlier, iscan only caters to the epkowa backend. Could the epson2 backend work via net even though the Artisan 710 is listed as unsupported on the SANE website? You'd have to ask the epson2 backend maintainer. Alessandro? Hope this helps, - -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvwgiIACgkQt5qrxaZLMnKYwACghiRiPvc10aWhlyJbF4TMuoSd 9p8An3BdeeuMBu+UTG2n7DTQvFYG95dH =SHTq -END PGP SIGNATURE-
[sane-devel] Epson Stylus SX410 is not recognized although it is listed as supported
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 m. allan noah : That seems more complete, but now we have to wait for someone with more experience with epson protocol I guess I qualify ;-) As Chris mentioned, the call to esci_set_color_correction_coefficients is definitely not right. The odd thing is that it gets called at all. Looking at the code for 1.0.21 (and git master), there is no way that this command should get called. Digging a bit further, this has been fixed in http://git.debian.org/?p=sane/sane-backends.git;a=commitdiff;h=e75d6e5e0cb223beb47b6756c56c4798082fe9d1 which is in 1.0.21. Looks like the other person is using a snapshot from before that. Hope this helps, - -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvwi5EACgkQt5qrxaZLMnJhiwCgtwBsX6t2ndHf28Yda5pPU2Z+ EYoAnjwgnmNBNb36r7zNyCAu6xNndWIZ =adin -END PGP SIGNATURE-
[sane-devel] Epson Artisan 710 support
On 05/15/2010 04:47 AM, Grant wrote: With regards to the horizontal lines, could you send me a sample scan off-list? Preferably a fairly small area exhibiting the problem scanned at a high resolution in a lossless format, like PNG. I don't want to go hunting for the problem if it is difficult to spot. Also, to avoid any image processing, please make sure to use scanimage to do the scan. I'll email you directly right now. Thanks for the samples. I've never seen this particular problem before. I'll have to take a crack at seeing if I can reproduce this to make 100% sure it's not an issue with your hardware. You'll have to hang tight before I can find an Artisan 710 and some free time to investigate. Happy scanning, -- Alesh SlovakLinux Team -- AVASYS Corporation alesh.slovak at avasys.jp http://avasys.jp
[sane-devel] scanimage works, xsane does not
Hi, Sorry if I am not very knowledgeable; I installed scanimage and sane on a Mac running 10.6 and it works from command line. (http://www.ellert.se/twain-sane/) But xsane, which I installed from MacPorts, which took many hours of compiling things, does not find any devices, even though I can scan and view images using the command line. ImageCapture on the mac works as well (ie it finds the scanner). So I am pretty sure the problem must be with xsane. Here is some output edr:~ goossens$ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], chip=LM9832/3) at libusb:003:004-04a9-220e-ff-00 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. edr:~ goossens$ scanimage -L device `plustek:libusb:003:004-04a9-220e-ff-00' is a Canon CanoScan N1240U/LiDE30 flatbed scanner
[sane-devel] Pixma height constraint for ADF
On Thu, May 13, 2010 at 8:46 AM, Zeev Lieber zeev.lieber at gmail.com wrote: I just tried the git version of SANE with my new Canon imageCLASS MF4350d. Everything works fine, except for one thing: I cannot scan legal-size documents via the ADF. Running scanimage -h showed that the y parameter is bound by the value of 297mm (A4), which is correct for flatbed, but not for the ADF. So I quickly hacked pixma_imageclass.c replacing the height constraints (1052 instead of 877 for Legal), and also pixma_sane_options.c to force the default back to 297mm. This did the trick for me, but clearly is not a good solution in general, and doesn't work with xsane (only command line). Also, pixma_sane_options.c seems to be auto-generated, but I couldn't find the script that generated it, so I just did my changes in the .c file itself. I'm not familiar with the architecture enough to suggest what a good solution would be. Is there a nice way to support different constraints for different document sources? Or maybe just disable the checking of height constraint for ADF altogether? If you tell me what it is, and it's not too complicated I could contribute a patch for this. Almost certainly the adf does have some upper limit of length it will scan. Not a physical limit, but a logical one in the firmware. If you can figure out what that limit is (trial and error, or using the windows software) then you should be able to code the br_y option's limits to a longer value when using the ADF. I don't know if there is other code to change, perhaps one of the pixma authors will discuss. allan -- The truth is an offense, but not a sin
[sane-devel] list of RECENT supported scanners
This is a useful idea, it comes up on this list every 6 months or so. But no one has done the legwork to make it happen. I do note when a model is discontinued from fujitsu, but that is the only backend of mine where i know enough about the equipment to do so! allan On Sat, May 15, 2010 at 7:32 AM, Y P yellow.penguin at edpnet.be wrote: Hi, although I find the SANE project something very very useful and nice, I miss something: the list of scanners that are supported doesn't mention the manufacturing year, so the result is that sometimes you think ow yeah this is a supported scanner while in fact you have to think Ow ch... this scanner doesn't longer exist and/or isn't longer in the shops: isn't there a way to provide information about the fabrication year so that people no longer searches for 10 year old products while they do believe it's something new ? Just my fifty cents! Labrador -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] (no subject)
Can you ad this please.
# Brother scanners
ATTRS{idVendor}==04f9, ENV{libsane_matched}=yes
Mvh
IngmarAlm
ingmaralm at hotmail.com
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100517/56d4a8cb/attachment.htm
[sane-devel] Epson Artisan 710 support
With regards to the horizontal lines, could you send me a sample scan off-list? Preferably a fairly small area exhibiting the problem scanned at a high resolution in a lossless format, like PNG. I don't want to go hunting for the problem if it is difficult to spot. Also, to avoid any image processing, please make sure to use scanimage to do the scan. I'll email you directly right now. Thanks for the samples. I've never seen this particular problem before. I'll have to take a crack at seeing if I can reproduce this to make 100% sure it's not an issue with your hardware. You'll have to hang tight before I can find an Artisan 710 and some free time to investigate. Thanks Alesh. I previously owned an Artisan 700 and it developed the same problem partway through the time I owned it. I remember upgrading the epkowa backend a couple times, so the problem may have been introduced by one of the upgrades. Do you know which version of the epkowa backend was the first to support the 710? Gentoo's package tree has 2.11.0 and 2.21.0. 2.21.0 exhibits the problem, but 2.11.0 doesn't seem to support the 710. I'd like to try the first version that supported the 710. - Grant
[sane-devel] scanimage works, xsane does not
Just a guess since you didn't mention working around following. Macports is installed under /opt's and only looks for its libraries under /opts. I think those twain-sane packages are self-contained packages. So probably when you compiled xsane from Macports it pulled in the older sane-backends-1.0.20 from Macports as well. Can't offer the exact fix for getting Macports to use external libraries but recommend pinging the Macport maintainer of sane-backends to update to 1.0.21. That would be simplest. Chris On Mon, May 17, 2010 at 1:22 AM, Darren Goossens goossens at rsc.anu.edu.auwrote: Hi, Sorry if I am not very knowledgeable; I installed scanimage and sane on a Mac running 10.6 and it works from command line. (http://www.ellert.se/twain-sane/) But xsane, which I installed from MacPorts, which took many hours of compiling things, does not find any devices, even though I can scan and view images using the command line. ImageCapture on the mac works as well (ie it finds the scanner). So I am pretty sure the problem must be with xsane. Here is some output edr:~ goossens$ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x220e [CanoScan], chip=LM9832/3) at libusb:003:004-04a9-220e-ff-00 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. edr:~ goossens$ scanimage -L device `plustek:libusb:003:004-04a9-220e-ff-00' is a Canon CanoScan N1240U/LiDE30 flatbed scanner -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100517/1348f090/attachment-0001.htm
[sane-devel] OCR with Xsane?
I'm new to Linux, specifically Xubuntu. I've progressed in Xsane at least enough to be able to scan and perform other basic operations. I can also produce PDF files out of the scanned images. This is not OCR, however. I need to know how to get the OCR component of Xsane to work--assuming it exists and that it's included in my package--and how to output the result into a file. If there is a different Linux program I should be using, please let me know. _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1 -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100517/ee910c93/attachment.htm
[sane-devel] Canoscan 8800F]
Gernot, This is the stderr output of scanimage with DEBUG_SANE, DEBUG_SANE_SANEI_USB, and SANE_DEBUG_DLL all set to 255: http://acm.poly.edu/~kurt/scanimage_all255.txt Here is the stderr output of scanimage -d test with SANE_DEBUG_TEST set to 255: http://acm.poly.edu/~kurt/scanimage_-d_test.txt thanks, -kurt On Mon, May 17, 2010 at 01:09:23AM +0900, Gernot Hassenpflug wrote: Hello Kurt, I am concerned about this part of the log file: [pixma] pixma_open(): Canoscan 8800F [pixma] WARNING:pixma_write(): count(0) != len(16) [pixma] OUT T=3.054 len=-1 [pixma] :ef 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] ERROR: EIO It looks as though the scanner is not responding even at the start of the operation. Maybe you can try setting more debug options to 255: DEBUG_SANE DEBUG_SANE_SANEI_USB SANE_DEBUG_DLL And then send me the log file (or a link to it). I don't know what changes there might be that Canon has made in firmware perhaps, but maybe there is some other problem unrelated to the scanner itself that can be determined from the raw USB communications. You might also try sane-test (see man page) to test your sane installation, and set SANE_DEBUG_TEST to 255 for that. Best regards, Gernot Hassenpflug
[sane-devel] Canoscan 8800F]
DEBUG_SANE_SANEI_USB is not a proper variable. should be SANE_DEBUG_SANEI_USB allan On Mon, May 17, 2010 at 9:25 PM, Gernot Hassenpflug aikishugyo at gmail.com wrote: On Tue, May 18, 2010 at 7:14 AM, Kurt Rosenfeld hardware at ee.ccny.cuny.edu wrote: Gernot, This is the stderr output of scanimage with DEBUG_SANE, DEBUG_SANE_SANEI_USB, and SANE_DEBUG_DLL all set to 255: http://acm.poly.edu/~kurt/scanimage_all255.txt Here is the stderr output of scanimage -d test with SANE_DEBUG_TEST set to 255: http://acm.poly.edu/~kurt/scanimage_-d_test.txt thanks, -kurt On Mon, May 17, 2010 at 01:09:23AM +0900, Gernot Hassenpflug wrote: Hello Kurt, I am concerned about this part of the log file: [pixma] pixma_open(): Canoscan 8800F [pixma] WARNING:pixma_write(): count(0) != len(16) [pixma] OUT ?T=3.054 len=-1 [pixma] ?:ef 20 00 00 00 00 00 00 ?00 00 00 00 00 00 00 00 [pixma] ? ERROR: EIO It looks as though the scanner is not responding even at the start of the operation. Maybe you can try setting more debug options to 255: Hi, looks like exactly the same. I thought we would see the raw USB operations now but apparently not: what I wanted to see was the USB attachment and configuration URBs. Since no I/O is possible at all, maybe the attachment or configuration is not going well. Q to the list: Are there any other DEBUG variables that can be set to see this kind of information? Otherwise, I recommend doing a USB snoop on a Windows machine (which I understand you do not have available) so I can try to see what if any differences there are to my scanner. No-one else has reported trouble using the 8800F, but I have no idea if Canon made different variations that require some tuning of the communication protocol. Regards, Gernot -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
