Re: [sane-devel] Problem with Canon MX370 scanner
Hello, Ubuntu 14.04 still comes with backend version 1.0.23, which doesn't support that scanner. You need to install the git version of sane. Follow these instructions: http://www.sane-project.org/README.linux Greetings from Germany Matthias On 22.05.2014 05:41, Nicolás Santisteban wrote: Hello, I have a problem with a Canon MX370 scanner. When I do 'sudo sane-find-scanners': -- # 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. could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error # No USB scanners found. If you expected something different, make sure that # you have loaded a kernel driver for your USB host controller and have setup # the USB system correctly. See man sane-usb for details. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. -- If I do it without 'sudo' I get a bunch of 'Access denied (insufficient permissions)' and then the 'Pipe error' thing. But it does recognize it when I do 'scanimage -L': -- device `pixma:04A91759' is a CANON Canon PIXMA MX370 Series multi-function peripheral -- I tried 'scanimage -x 100 -y 100 --format=tiff image.tiff' and this is what I get: -- scanimage: open of device pixma:04A91759_0031B6 failed: Operation not supported -- This is the output of 'dmesg|tail' after I connect the scanner: -- [115728.429416] delay: estimated 177, actual 88 [122971.328219] delay: estimated 177, actual 88 [131619.960568] usb 1-1.3: new high-speed USB device number 14 using ehci-pci [131620.054490] usb 1-1.3: New USB device found, idVendor=04a9, idProduct=1759 [131620.054493] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [131620.054494] usb 1-1.3: Product: MX370 series [131620.054495] usb 1-1.3: Manufacturer: Canon [131620.054497] usb 1-1.3: SerialNumber: 0031B6 [131620.057862] usblp 1-1.3:1.1: usblp0: USB Bidirectional printer dev 14 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1759 [131620.059559] usblp 1-1.3:1.2: usblp1: USB Bidirectional printer dev 14 if 2 alt 0 proto 2 vid 0x04A9 pid 0x1759 -- My system is Ubuntu 14.04 LTS. Does anyone have any idea on whats going on? Thanks in advance. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] MX375 no recovery from ADF empty when scan started
Hallo Rolf, I can't notice any change of behavior here. To make sure, that I use the patched version, I manually deleted all libsane*. See log attached. And the scan does not start, if I insert paper during the timeout countdown. The scanner beeps, so the firmware detects the inserted paper. But the scan does not start. Grüße Matthias On 20.05.2014 22:44, Rolf Bensch wrote: Hi Matthias, Am 20.05.2014 17:49, schrieb Matthias Peter Walther: Hallo Rolf, sorry to bother you again. But here is another bug with my MX375. No problem. If I start an ADF-scan while the ADF is empty, the scanner does not recover and needs to be restarted by hand. Attached patch should fix this. The patch is based on recent git code. [...] I mean scanning ADF without paper in it is stupid, but it should not crash the device :) It's not stupid. Maybe you started the job and forgot to put the paper into the ADF. Then the job should start scanning if you put the paper into the ADF *before* timeout counted down to 0 and aborts the job. Please test, if scanning starts if you put paper into the ADF during timeout counts down. Cheers, Rolf mpw@Server1:~$ export SANE_DEBUG_PIXMA=11 mpw@Server1:~$ scanimage --source Automatic Document Feeder --batch=test%02d.pnm [sanei_debug] Setting debug level of pixma to 11. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.8 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:010 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:010 [pixma] pixma_open(): Canon PIXMA MX370 Series Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 [pixma] Reader task id=140139417962240 (threaded) [pixma] Reader task started [pixma] [pixma] pixma_scan(): start [pixma] line_size=1914 image_size=2009700 channels=3 depth=8 [pixma] dpi=75x75 offset=(0,0) dimension=638x1050 [pixma] gamma_table=0x18c9f10 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] ADF page count: 0 [pixma] OUT T=2.851 len=288 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 3c 63 6d 64 20 78 6d 6c 6e [pixma] 0030:73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f 2f 77 [pixma] 0040:77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e 73 2f [pixma] 0050:63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f 6d 6d [pixma] 0060:6f 6e 2f 22 3e 3c 69 76 65 63 3a 63 6f 6e 74 65 [pixma] 0070:6e 74 73 3e 3c 69 76 65 63 3a 6f 70 65 72 61 74 [pixma] ... [pixma] [pixma] IN T=2.857 len=365 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 0d 0a 3c 63 6d 64 20 78 6d [pixma] 0030:6c 6e 73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f [pixma] 0040:2f 77 77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e [pixma] 0050:73 2f 63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f [pixma] 0060:6d 6d 6f 6e 2f 22 3e 0d 0a 09 3c 69 76 65 63 3a [pixma] 0070:63 6f 6e 74 65 6e 74 73 3e 0d 0a 09 09 3c 69 76 [pixma] ... [pixma] [pixma] XML message sent to scanner: ?xml version=1.0 encoding=utf-8 ?cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;ivec:contentsivec:operationStartJob/ivec:operationivec:param_set servicetype=scanivec:jobID0001/ivec:jobIDivec:bidi1/ivec:bidi/ivec:param_set/ivec:contents/cmd [pixma] XML response back from scanner: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; ivec:contents ivec:operationStartJobResponse/ivec:operation ivec:param_set servicetype=scan ivec:responseOK/ivec:response ivec:response_detail/ ivec:jobID0001/ivec:jobID /ivec:param_set /ivec:contents /cmd [pixma] OUT T=2.858 len=390 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 3c 63 6d 64 20 78 6d 6c 6e [pixma] 0030:73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f 2f 77 [pixma] 0040:77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e 73 2f [pixma] 0050:63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f 6d 6d [pixma] 0060:6f 6e 2f 22 20 78 6d 6c 6e 73 3a 76 63 6e 3d 22 [pixma] 0070:68 74 74 70 3a 2f 2f 77 77 77 2e 63 61 6e 6f 6e [pixma] ... [pixma] [pixma] IN T=2.861 len=510 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 0d 0a 3c 63 6d 64 20 78 6d [pixma] 0030:6c 6e 73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f [pixma] 0040:2f 77 77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e [pixma] 0050:73 2f 63 6d
Re: [sane-devel] MX375 no recovery from ADF empty when scan started
Hallo Rolf, one fixed, one to go. An empty ADF still crashes the device. But it starts scanning now, if I insert paper before the timeout runs out. I created logs for both issues. Grüße Matthias On 21.05.2014 17:27, Rolf Bensch wrote: Hi Matthias, I created a new patch1. This should fix both issues. I also added a new debug output to check paper empty code. Cheers, Rolf Am 21.05.2014 09:51, schrieb Matthias Peter Walther: Hallo Rolf, I can't notice any change of behavior here. To make sure, that I use the patched version, I manually deleted all libsane*. See log attached. And the scan does not start, if I insert paper during the timeout countdown. The scanner beeps, so the firmware detects the inserted paper. But the scan does not start. Grüße Matthias On 20.05.2014 22:44, Rolf Bensch wrote: Hi Matthias, Am 20.05.2014 17:49, schrieb Matthias Peter Walther: Hallo Rolf, sorry to bother you again. But here is another bug with my MX375. No problem. If I start an ADF-scan while the ADF is empty, the scanner does not recover and needs to be restarted by hand. Attached patch should fix this. The patch is based on recent git code. [...] I mean scanning ADF without paper in it is stupid, but it should not crash the device :) It's not stupid. Maybe you started the job and forgot to put the paper into the ADF. Then the job should start scanning if you put the paper into the ADF *before* timeout counted down to 0 and aborts the job. Please test, if scanning starts if you put paper into the ADF during timeout counts down. Cheers, Rolf mpw@Server1:~/sane$ SANE_DEBUG_PIXMA=4 scanimage --source Automatic Document Feeder --batch=test%02d.pnm [sanei_debug] Setting debug level of pixma to 4. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.8 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:013 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:013 [pixma] pixma_open(): Canon PIXMA MX370 Series Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 [pixma] Reader task id=140410587653888 (threaded) [pixma] Reader task started [pixma] [pixma] pixma_scan(): start [pixma] line_size=1914 image_size=2009700 channels=3 depth=8 [pixma] dpi=75x75 offset=(0,0) dimension=638x1050 [pixma] gamma_table=0x14bef30 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] ADF page count: 0 [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 9 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 8 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 7 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 6 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 5 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 4 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 3 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 2 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 1 sec. [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 0 sec. [pixma] *mp150_scan* no paper in ADF * [pixma] pixma_scan() failed EPROTO [pixma] read_image():reader task closed the pipe:0 bytes received, 2009700 bytes expected [pixma] Reader task terminated: EPROTO scanimage: sane_read: Error during device I/O Scanned page 1. (scanner status = 9) [pixma] pixma_close(): Canon PIXMA MX370 Series mpw@Server1:~/sane$ SANE_DEBUG_PIXMA=4 scanimage test.pnm [sanei_debug] Setting debug level of pixma to 4. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.8 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:013 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:013 [pixma] pixma_open(): Canon PIXMA MX370 Series [pixma] Reader task started [pixma] Reader task id=139789599786752 (threaded) [pixma] [pixma] pixma_scan(): start [pixma] line_size=1914 image_size=1678578 channels=3 depth=8 [pixma] dpi=75x75 offset=(0,0) dimension=638x877 [pixma] gamma_table=0x6d4f30 source=0 [pixma] threshold=127 threshold_curve=0 [pixma] ADF page count: 0 [pixma] No response yet. Timed out in 8 sec. slow timeout, probably due to debug, between each line the sane sleeps for 20-30 seconds. [pixma] No response yet. Timed out in 7 sec. [pixma] No response yet. Timed out in 6 sec. [pixma] No response yet. Timed out in 5 sec. [pixma] No response yet
Re: [sane-devel] Pixma: ADF paper empty patch for Canon Pixma MX???
Hallo Rolf, I didn't know that the order of the flags matters. It works now, thanks for that hint! Bye Matthias On 18.05.2014 18:15, Rolf Bensch wrote: Hi Matthias, Am 17.05.2014 18:56, schrieb Matthias Peter Walther: Hallo Rolf, I'm sorry, I couldn't reply earlier. I had some issues with my pc, hdd crash. I pulled the patch from the git and I can't get higher resolutions than 75 anymore while using the ADF. It resets the resolution back to 75 all the time. But the out-of-paper issues works great and the scaner recovers perfectly from the error state now. OK Could you look into that resolution issue please? === $ scanimage --resolution 300 --batch=test%02db.pnm --source Automatic Document Feeder You need to reorder the options of scanimage. 'scanimage --help' tells me: Usage: scanimage [OPTION]... [...] --source Flatbed|Transparency Unit [Flatbed] Selects the scan source (such as a document-feeder). Set source before mode and resolution. Resets mode and resolution to auto values. [...] My scanner has a transparent unit and no document feeder, but the handling is the same. [...] $ scanimage --source Automatic Document Feeder --resolution 300 --batch=test%02db.pnm should work. Cheers, Rolf -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] MX375 no recovery from ADF empty when scan started
Hallo Rolf, sorry to bother you again. But here is another bug with my MX375. If I start an ADF-scan while the ADF is empty, the scanner does not recover and needs to be restarted by hand. Basically there are two commands to demonstrate it: scanimage --source Automatic Document Feeder --batch=test%02d.pnm # without paper in ADF scanimage test.pnm #fails I attached a log for you. Maybe you'll have the time to take a look into it. I mean scanning ADF without paper in it is stupid, but it should not crash the device :) Greetings from Münster Matthias mpw@Server1:~$ export SANE_DEBUG_PIXMA=11 mpw@Server1:~$ scanimage --source Automatic Document Feeder --batch=test%02d.pnm [sanei_debug] Setting debug level of pixma to 11. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.8 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:011 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:011 [pixma] pixma_open(): Canon PIXMA MX370 Series Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 [pixma] Reader task started [pixma] [pixma] pixma_scan(): start [pixma] line_size=1914 image_size=2009700 channels=3 depth=8 [pixma] dpi=75x75 offset=(0,0) dimension=638x1050 [pixma] gamma_table=0x198aeb0 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] ADF page count: 0 [pixma] Reader task id=139964097533696 (threaded) [pixma] OUT T=3.155 len=288 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 3c 63 6d 64 20 78 6d 6c 6e [pixma] 0030:73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f 2f 77 [pixma] 0040:77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e 73 2f [pixma] 0050:63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f 6d 6d [pixma] 0060:6f 6e 2f 22 3e 3c 69 76 65 63 3a 63 6f 6e 74 65 [pixma] 0070:6e 74 73 3e 3c 69 76 65 63 3a 6f 70 65 72 61 74 [pixma] ... [pixma] [pixma] IN T=3.161 len=365 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 0d 0a 3c 63 6d 64 20 78 6d [pixma] 0030:6c 6e 73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f [pixma] 0040:2f 77 77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e [pixma] 0050:73 2f 63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f [pixma] 0060:6d 6d 6f 6e 2f 22 3e 0d 0a 09 3c 69 76 65 63 3a [pixma] 0070:63 6f 6e 74 65 6e 74 73 3e 0d 0a 09 09 3c 69 76 [pixma] ... [pixma] [pixma] XML message sent to scanner: ?xml version=1.0 encoding=utf-8 ?cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;ivec:contentsivec:operationStartJob/ivec:operationivec:param_set servicetype=scanivec:jobID0001/ivec:jobIDivec:bidi1/ivec:bidi/ivec:param_set/ivec:contents/cmd [pixma] XML response back from scanner: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; ivec:contents ivec:operationStartJobResponse/ivec:operation ivec:param_set servicetype=scan ivec:responseOK/ivec:response ivec:response_detail/ ivec:jobID0001/ivec:jobID /ivec:param_set /ivec:contents /cmd [pixma] OUT T=3.162 len=390 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 3c 63 6d 64 20 78 6d 6c 6e [pixma] 0030:73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f 2f 77 [pixma] 0040:77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e 73 2f [pixma] 0050:63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f 6d 6d [pixma] 0060:6f 6e 2f 22 20 78 6d 6c 6e 73 3a 76 63 6e 3d 22 [pixma] 0070:68 74 74 70 3a 2f 2f 77 77 77 2e 63 61 6e 6f 6e [pixma] ... [pixma] [pixma] IN T=3.164 len=510 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 0d 0a 3c 63 6d 64 20 78 6d [pixma] 0030:6c 6e 73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f [pixma] 0040:2f 77 77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e [pixma] 0050:73 2f 63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f [pixma] 0060:6d 6d 6f 6e 2f 22 0d 0a 78 6d 6c 6e 73 3a 76 63 [pixma] 0070:6e 3d 22 68 74 74 70 3a 2f 2f 77 77 77 2e 63 61 [pixma] ... [pixma] [pixma] XML message sent to scanner: ?xml version=1.0 encoding=utf-8 ?cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/;ivec:contentsivec:operationVendorCmd/ivec:operationivec:param_set servicetype=scanivec:jobID0001/ivec:jobIDvcn:ijoperationModeShift/vcn:ijoperationvcn:ijmode1/vcn:ijmode/ivec:param_set/ivec:contents/cmd
Re: [sane-devel] Pixma: ADF paper empty patch for Canon Pixma MX???
Hallo Rolf, I'm sorry, I couldn't reply earlier. I had some issues with my pc, hdd crash. I pulled the patch from the git and I can't get higher resolutions than 75 anymore while using the ADF. It resets the resolution back to 75 all the time. But the out-of-paper issues works great and the scaner recovers perfectly from the error state now. Could you look into that resolution issue please? === $ scanimage --resolution 300 --batch=test%02db.pnm --source Automatic Document Feeder [sanei_debug] Setting debug level of pixma to 4. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.8 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:008 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:001:008 [pixma] pixma_open(): Canon PIXMA MX370 Series Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 [pixma] Reader task started [pixma] Reader task id=14058523264 (threaded) [pixma] [pixma] pixma_scan(): start [pixma] line_size=1914 image_size=2009700 channels=3 depth=8 [pixma] dpi=75x75 offset=(0,0) dimension=638x1050 [pixma] gamma_table=0x24e6ea0 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] ADF page count: 0 [pixma] Current status: paper=1 cal=0 lamp=0 busy=0 [pixma] No paper in ADF. Timed out in 9 sec. [pixma] No paper in ADF. Timed out in 8 sec. [pixma] No paper in ADF. Timed out in 7 sec. [pixma] No paper in ADF. Timed out in 6 sec. [pixma] No paper in ADF. Timed out in 5 sec. [pixma] No paper in ADF. Timed out in 4 sec. [pixma] No paper in ADF. Timed out in 3 sec. [pixma] No paper in ADF. Timed out in 2 sec. [pixma] No paper in ADF. Timed out in 1 sec. [pixma] No paper in ADF. Timed out in 0 sec. [pixma] pixma_scan() failed ENO_PAPER [pixma] read_image():reader task closed the pipe:0 bytes received, 2009700 bytes expected [pixma] Reader task terminated: ENO_PAPER scanimage: sane_read: Document feeder out of documents Scanned page 1. (scanner status = 7) [pixma] pixma_close(): Canon PIXMA MX370 Series === Grüße Matthias On 08.05.2014 20:30, Rolf Bensch wrote: Hi All, I just committed a 'ADF paper empty' patch for Canon Pixma MX??? scanners to git. It has been successfully tested with MX375. Please report any further problems. Cheers, Rolf -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Canon MX430 / MX510 / MX925 - does not recover when ADF out of paper
Hello Rolf, I'm sorrry, that this took so long time, but I replaced my pc and restarted from zero. That's why I used the wrong library version last time. But I think there are still issues. I scanned 3 pages. And if I cause a paper input error for example by holding it back with my hand, I can press cancel and OK on the scanner, restart scanimage and it will work. This seems to be fixed now. But: The pages have the wrong aspect ratio, they are far too long. And the resolution-parameter is ignored. I scanned with 300dpi and the images have just around 2MB and are of low quality. I don't know why, but with patch1-5 it worked better. Did you change something or did you just sum up the patches? I'm still unsure, if it's a problem with my setup... Gr??e Matthias On 21.04.2014 17:07, Rolf Bensch wrote: Hi Matthias, You don't use lastest Sane code. [pixma] pixma version 0.17.0 should be [pixma] pixma version 0.17.6! Please check your installation (as described in README.linux). Cheers, Rolf Am 21.04.2014 16:23, schrieb Matthias Peter Walther: Hallo Rolf, I'm sorry I couldn't answer earlier. That patch screwed it, no scans possible. Gr??e Matthias On 03.04.2014 20:47, Rolf Bensch wrote: Hi All, It seems that ADF out of paper issue is fixed now. Please test attached final patch, which is based on latest git sources. Please confirm that this patch fixes ADF out of paper issue for your particular scanner. I'll commit this patch and some document updates after your confirmation. Many thanks for your help. Cheers, Rolf Am 02.04.2014 20:54, schrieb Matthias Peter Walther: Hello Rolf, here the requested logfile. Bye Matthias On 26.03.2014 17:22, Rolf Bensch wrote: Hi Matthias, I prepared a patch for the stopped the 2nd paper by hand issue. The patch is based on patch4. Please revert this patch: pixma_common.c.patch4. With this patch my system has too fast timeouts, and without this patch the timeouts take 1 sec. Please try to fix this by yourself. On the other hand there are no timeouts when everything is working as expected. Cheers, Rolf Am 23.03.2014 14:54, schrieb Matthias Peter Walther: Hello Rolf, I created three more logs. And the timeouts are not fixed. In fact it's gotten even worse, scanimage is captured in an (infinite(?)) loop of timeouts of which each loop takes several minuites. Watch log 3rd_try. Bye Matthias On 21.03.2014 18:21, Rolf Bensch wrote: Hi Matthias, I need a new log file for this issue: And in the debug level 11 Iog I stopped the 2nd paper by hand. Scanner and sane aborts. But after removing the paper and pressing ok on the device, nothing happens anymore. and the 2nd patch is for this issue: By the way. The timeouts in the sane logs are still rediculous. When it counts down, between each line it waits up the 40 seconds and not the amount of seconds it says in the log. and please test normal ADF scanning again. Cheers, Rolf Am 21.03.2014 00:16, schrieb Matthias Peter Walther: Hello, I'm not sure if I did this right. I installed the two patches shipped with your last email and used this command: $ export SANE_DEBUG_PIXMA=11 $ scanimage -x 100 -y 100 test.png 2 Scanimage_Debug_11_patch1+2+3new+4+Pressed_cancel_after_device_started.txt After the scanner started, I pressed cancel on the device. Is this what you need? Bye Matthias Am 20.03.2014 18:05, schrieb Rolf Bensch: Hi Matthias, Please don't mix different testings in one log file and at the same time. Please keep them in mind and let us go step by step. I assume that normal ADF scanning works with new patch 3. Am 19.03.2014 19:46, schrieb Matthias Peter Walther: Standard debug level 4 scan, the last 1 mm is still missing. As this seems to be firmware related, I think sane won't be able to change this. The linux binary has the same problem. And I tested it in windows with IrfanView. The last mm is still missing under windows, too. I think this is a firmware issue? I guess the ADF hardware needs the last 1mm for the paper detector. Maybe you just set the maximum height of an adf page to that last line it scans. That is 870 pixels @75 dpi. I won't do so. What's when you want to scan a 14 sheet or A5 format? Please set the used paper size in the frontend. Then you can also crop left and right ADF frame. And in the debug level 11 Iog I stopped the 2nd paper by hand. Scanner and sane aborts. But after removing the paper and pressing ok on the device, nothing happens anymore. I see this error in the log file: cancelled by hardware. The problem is that the scan process has not been closed and the scanner cannot be initialised for a new scan session because the previous is still active in the scanner. To fix this I need the exact position in the code where cancelled by hardware is detected. Please create a new log file with usb messages with attached patch pixma_mp150.c.patch4
[sane-devel] Canon MX430 / MX510 / MX925 - does not recover when ADF out of paper
Hallo Rolf, I'm sorry I couldn't answer earlier. That patch screwed it, no scans possible. Gr??e Matthias On 03.04.2014 20:47, Rolf Bensch wrote: Hi All, It seems that ADF out of paper issue is fixed now. Please test attached final patch, which is based on latest git sources. Please confirm that this patch fixes ADF out of paper issue for your particular scanner. I'll commit this patch and some document updates after your confirmation. Many thanks for your help. Cheers, Rolf Am 02.04.2014 20:54, schrieb Matthias Peter Walther: Hello Rolf, here the requested logfile. Bye Matthias On 26.03.2014 17:22, Rolf Bensch wrote: Hi Matthias, I prepared a patch for the stopped the 2nd paper by hand issue. The patch is based on patch4. Please revert this patch: pixma_common.c.patch4. With this patch my system has too fast timeouts, and without this patch the timeouts take 1 sec. Please try to fix this by yourself. On the other hand there are no timeouts when everything is working as expected. Cheers, Rolf Am 23.03.2014 14:54, schrieb Matthias Peter Walther: Hello Rolf, I created three more logs. And the timeouts are not fixed. In fact it's gotten even worse, scanimage is captured in an (infinite(?)) loop of timeouts of which each loop takes several minuites. Watch log 3rd_try. Bye Matthias On 21.03.2014 18:21, Rolf Bensch wrote: Hi Matthias, I need a new log file for this issue: And in the debug level 11 Iog I stopped the 2nd paper by hand. Scanner and sane aborts. But after removing the paper and pressing ok on the device, nothing happens anymore. and the 2nd patch is for this issue: By the way. The timeouts in the sane logs are still rediculous. When it counts down, between each line it waits up the 40 seconds and not the amount of seconds it says in the log. and please test normal ADF scanning again. Cheers, Rolf Am 21.03.2014 00:16, schrieb Matthias Peter Walther: Hello, I'm not sure if I did this right. I installed the two patches shipped with your last email and used this command: $ export SANE_DEBUG_PIXMA=11 $ scanimage -x 100 -y 100 test.png 2 Scanimage_Debug_11_patch1+2+3new+4+Pressed_cancel_after_device_started.txt After the scanner started, I pressed cancel on the device. Is this what you need? Bye Matthias Am 20.03.2014 18:05, schrieb Rolf Bensch: Hi Matthias, Please don't mix different testings in one log file and at the same time. Please keep them in mind and let us go step by step. I assume that normal ADF scanning works with new patch 3. Am 19.03.2014 19:46, schrieb Matthias Peter Walther: Standard debug level 4 scan, the last 1 mm is still missing. As this seems to be firmware related, I think sane won't be able to change this. The linux binary has the same problem. And I tested it in windows with IrfanView. The last mm is still missing under windows, too. I think this is a firmware issue? I guess the ADF hardware needs the last 1mm for the paper detector. Maybe you just set the maximum height of an adf page to that last line it scans. That is 870 pixels @75 dpi. I won't do so. What's when you want to scan a 14 sheet or A5 format? Please set the used paper size in the frontend. Then you can also crop left and right ADF frame. And in the debug level 11 Iog I stopped the 2nd paper by hand. Scanner and sane aborts. But after removing the paper and pressing ok on the device, nothing happens anymore. I see this error in the log file: cancelled by hardware. The problem is that the scan process has not been closed and the scanner cannot be initialised for a new scan session because the previous is still active in the scanner. To fix this I need the exact position in the code where cancelled by hardware is detected. Please create a new log file with usb messages with attached patch pixma_mp150.c.patch4. And please scan a small area @ 75 dpi, not a whole page. This reduces log file size. The same bug comes, if you interrupt the scan with ctrl + C (scanimage). The printer continues pulling pages, but does not recover after it has finished. That works correctly with the binary. If I recover the scanner with the binary driver, that requires up to three attempts. During the first and often the second, it searches the scanner for 2 minuites and aborts then. After that the second failure the scanner works prefectly again. Maybe it's just a timeout in the devices firmware? I assume that this is the same problem as above. By the way. The timeouts in the sane logs are still rediculous. When it counts down, between each line it waits up the 40 seconds and not the amount of seconds it says in the log. Maybe pixma_common.c.patch4 will fix this. I had to zip the logs, cause they are larger than 100 KB and the mailing list server doesn't accept that. Last question: Is it possible to autodetect if adf has paper and autoswitch the input method? Some scanner
[sane-devel] Canon MX430 / MX510 / MX925 - does not recover when ADF out of paper
Hello Rolf, here the requested logfile. Bye Matthias On 26.03.2014 17:22, Rolf Bensch wrote: Hi Matthias, I prepared a patch for the stopped the 2nd paper by hand issue. The patch is based on patch4. Please revert this patch: pixma_common.c.patch4. With this patch my system has too fast timeouts, and without this patch the timeouts take 1 sec. Please try to fix this by yourself. On the other hand there are no timeouts when everything is working as expected. Cheers, Rolf Am 23.03.2014 14:54, schrieb Matthias Peter Walther: Hello Rolf, I created three more logs. And the timeouts are not fixed. In fact it's gotten even worse, scanimage is captured in an (infinite(?)) loop of timeouts of which each loop takes several minuites. Watch log 3rd_try. Bye Matthias On 21.03.2014 18:21, Rolf Bensch wrote: Hi Matthias, I need a new log file for this issue: And in the debug level 11 Iog I stopped the 2nd paper by hand. Scanner and sane aborts. But after removing the paper and pressing ok on the device, nothing happens anymore. and the 2nd patch is for this issue: By the way. The timeouts in the sane logs are still rediculous. When it counts down, between each line it waits up the 40 seconds and not the amount of seconds it says in the log. and please test normal ADF scanning again. Cheers, Rolf Am 21.03.2014 00:16, schrieb Matthias Peter Walther: Hello, I'm not sure if I did this right. I installed the two patches shipped with your last email and used this command: $ export SANE_DEBUG_PIXMA=11 $ scanimage -x 100 -y 100 test.png 2 Scanimage_Debug_11_patch1+2+3new+4+Pressed_cancel_after_device_started.txt After the scanner started, I pressed cancel on the device. Is this what you need? Bye Matthias Am 20.03.2014 18:05, schrieb Rolf Bensch: Hi Matthias, Please don't mix different testings in one log file and at the same time. Please keep them in mind and let us go step by step. I assume that normal ADF scanning works with new patch 3. Am 19.03.2014 19:46, schrieb Matthias Peter Walther: Standard debug level 4 scan, the last 1 mm is still missing. As this seems to be firmware related, I think sane won't be able to change this. The linux binary has the same problem. And I tested it in windows with IrfanView. The last mm is still missing under windows, too. I think this is a firmware issue? I guess the ADF hardware needs the last 1mm for the paper detector. Maybe you just set the maximum height of an adf page to that last line it scans. That is 870 pixels @75 dpi. I won't do so. What's when you want to scan a 14 sheet or A5 format? Please set the used paper size in the frontend. Then you can also crop left and right ADF frame. And in the debug level 11 Iog I stopped the 2nd paper by hand. Scanner and sane aborts. But after removing the paper and pressing ok on the device, nothing happens anymore. I see this error in the log file: cancelled by hardware. The problem is that the scan process has not been closed and the scanner cannot be initialised for a new scan session because the previous is still active in the scanner. To fix this I need the exact position in the code where cancelled by hardware is detected. Please create a new log file with usb messages with attached patch pixma_mp150.c.patch4. And please scan a small area @ 75 dpi, not a whole page. This reduces log file size. The same bug comes, if you interrupt the scan with ctrl + C (scanimage). The printer continues pulling pages, but does not recover after it has finished. That works correctly with the binary. If I recover the scanner with the binary driver, that requires up to three attempts. During the first and often the second, it searches the scanner for 2 minuites and aborts then. After that the second failure the scanner works prefectly again. Maybe it's just a timeout in the devices firmware? I assume that this is the same problem as above. By the way. The timeouts in the sane logs are still rediculous. When it counts down, between each line it waits up the 40 seconds and not the amount of seconds it says in the log. Maybe pixma_common.c.patch4 will fix this. I had to zip the logs, cause they are larger than 100 KB and the mailing list server doesn't accept that. Last question: Is it possible to autodetect if adf has paper and autoswitch the input method? Some scanner are able to do that. Please keep this in mind. Cheers, Rolf -- next part -- [sanei_debug] Setting debug level of pixma to 4. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.6 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:002:004 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:002:004 [pixma] pixma_open(): Canon PIXMA MX370 Series Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 [pixma] Reader task
[sane-devel] Canon MX370 / MX430 / MX510 / MX925 - Button Support
Hello, Canon replyed me, that this shall be not possible. I think we'll have to stop here? I think the hardware would be capable of supporting buttons, but it would require a firmware change of the device mostly. That's to heavy I fear. Here a copy of the reply in german: == Sehr geehrter Herr Walther, vielen Dank f?r Ihre Anfrage zur Scanfunktion mir Ihrem PIXMA MX375. Eine M?glichkeit der Scan to PC Funktion zu nutzen besteht mit diesem Ger?t aus softwaretechnischen Gr?nden nicht. Wir bitten Sie, uns nachzusehen, dass wir Ihnen keine anderen Informationen geben k?nnen und hoffen, Sie schenken uns weiterhin Ihr Vertrauen. Vielen Dank, dass Sie den ?Service Support? der Firma Canon kontaktiert haben. Wir hoffen, dass unsere Informationen hilfreich f?r Sie sind. F?r weitere Fragen stehen wir Ihnen jederzeit gern zur Verf?gung. Mit freundlichen Gr??en [Name entfernt] Canon Services Support == Regards, Matthias On 21.03.2014 21:33, Matthias Peter Walther wrote: I asked the canon support, if it's possible under Windows. I will inform you about their answer. On 21.03.2014 18:40, Rolf Bensch wrote: Hi Matthias, Sorry I cannot find any button related data in the log file. Therefore your scanner has no button support. Unless you may find button support on a Windows machine or with binary. Then please sniff the usb communication (e.g. with wireshark) and send the log file to me. Cheers, Rolf Am 21.03.2014 00:03, schrieb Matthias Peter Walther: Hello, I tested every button. As far as I understand, the device has 4 Operation modes. The choice of the operating mode may influence the button behavior. I set it to scanner, after I tried out the four buttons for the four different operation modes. The results as attachment. Gr??e MPW Am 20.03.2014 16:52, schrieb Rolf Bensch: Hi Matthias, Please test all buttons and look if the debug output will change. The code says that some scanners ask to set the time when byte 3 is set. Cheers, Rolf Am 19.03.2014 00:31, schrieb Matthias Peter Walther: Hello, I think it works. That would be so cool. Thank you so much for your work on this and with the adf, too! I'll try out scanbd later. Do I have to do further code changes or is scanbd supposed to work just like that with that single additional line? Is it capable of detecting different buttons? So that it would be possible to sort the scans into different directories by different buttons? That would be so awesome. I pressed the button '9' on the dialpad. I think the menu buttons doesn't work, but the numbers do. Bye Matthias Am 18.03.2014 23:13, schrieb Rolf Bensch: Hi, If you like, please test button support for your scanner. If button support is working, you can use scanbd to control scanning via your scanner's buttons. You can find more infos about this in the mailing lists archive, e.g. here: http://sane.10972.n7.nabble.com/template/NamlServlet.jtp?macro=search_pagenode=3query=scanbddays=0sort=date To enable button support, add one single line with your scanner-pid in file pixma_mp150.c in function handle_interrupt() between lines 927 and 928, e.g. || s-cfg-pid == MX370_PID Test procedure: (1) 'export SANE_DEBUG_PIXMA=11' (2) press any button (3) check output from 'scanimage -A' You should see something like this: Buttons: --button-update Update button state [pixma] INTR T=1.670 len=32 [pixma] :00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] 0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] --button-1 int [1] [read-only] Button 1 --button-2 int [0] [read-only] Button 2 --original int [0] [read-only] Type of original to scan --target int [4] [read-only] Target operation type --scan-resolution int [0] [read-only] Scan resolution Please report your results. Cheers, Rolf
[sane-devel] Canon MX430 / MX510 / MX925 - does not recover when ADF out of paper
Hello, I'm not sure if I did this right. I installed the two patches shipped with your last email and used this command: $ export SANE_DEBUG_PIXMA=11 $ scanimage -x 100 -y 100 test.png 2 Scanimage_Debug_11_patch1+2+3new+4+Pressed_cancel_after_device_started.txt After the scanner started, I pressed cancel on the device. Is this what you need? Bye Matthias Am 20.03.2014 18:05, schrieb Rolf Bensch: Hi Matthias, Please don't mix different testings in one log file and at the same time. Please keep them in mind and let us go step by step. I assume that normal ADF scanning works with new patch 3. Am 19.03.2014 19:46, schrieb Matthias Peter Walther: Standard debug level 4 scan, the last 1 mm is still missing. As this seems to be firmware related, I think sane won't be able to change this. The linux binary has the same problem. And I tested it in windows with IrfanView. The last mm is still missing under windows, too. I think this is a firmware issue? I guess the ADF hardware needs the last 1mm for the paper detector. Maybe you just set the maximum height of an adf page to that last line it scans. That is 870 pixels @75 dpi. I won't do so. What's when you want to scan a 14 sheet or A5 format? Please set the used paper size in the frontend. Then you can also crop left and right ADF frame. And in the debug level 11 Iog I stopped the 2nd paper by hand. Scanner and sane aborts. But after removing the paper and pressing ok on the device, nothing happens anymore. I see this error in the log file: cancelled by hardware. The problem is that the scan process has not been closed and the scanner cannot be initialised for a new scan session because the previous is still active in the scanner. To fix this I need the exact position in the code where cancelled by hardware is detected. Please create a new log file with usb messages with attached patch pixma_mp150.c.patch4. And please scan a small area @ 75 dpi, not a whole page. This reduces log file size. The same bug comes, if you interrupt the scan with ctrl + C (scanimage). The printer continues pulling pages, but does not recover after it has finished. That works correctly with the binary. If I recover the scanner with the binary driver, that requires up to three attempts. During the first and often the second, it searches the scanner for 2 minuites and aborts then. After that the second failure the scanner works prefectly again. Maybe it's just a timeout in the devices firmware? I assume that this is the same problem as above. By the way. The timeouts in the sane logs are still rediculous. When it counts down, between each line it waits up the 40 seconds and not the amount of seconds it says in the log. Maybe pixma_common.c.patch4 will fix this. I had to zip the logs, cause they are larger than 100 KB and the mailing list server doesn't accept that. Last question: Is it possible to autodetect if adf has paper and autoswitch the input method? Some scanner are able to do that. Please keep this in mind. Cheers, Rolf -- next part -- [sanei_debug] Setting debug level of pixma to 11. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.6 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:002:020 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:002:020 [pixma] pixma_open(): Canon PIXMA MX370 Series [pixma] Reader task started [pixma] Reader task id=139924564408064 (threaded) [pixma] [pixma] pixma_scan(): start [pixma] line_size=885 image_size=261075 channels=3 depth=8 [pixma] dpi=75x75 offset=(0,0) dimension=295x295 [pixma] gamma_table=0xf677b0 source=0 [pixma] threshold=127 threshold_curve=0 [pixma] ADF page count: 0 [pixma] OUT T=3.459 len=288 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 3c 63 6d 64 20 78 6d 6c 6e [pixma] 0030:73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f 2f 77 [pixma] 0040:77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e 73 2f [pixma] 0050:63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f 6d 6d [pixma] 0060:6f 6e 2f 22 3e 3c 69 76 65 63 3a 63 6f 6e 74 65 [pixma] 0070:6e 74 73 3e 3c 69 76 65 63 3a 6f 70 65 72 61 74 [pixma] ... [pixma] [pixma] IN T=3.484 len=365 [pixma] :3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31 [pixma] 0010:2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 75 74 [pixma] 0020:66 2d 38 22 20 3f 3e 0d 0a 3c 63 6d 64 20 78 6d [pixma] 0030:6c 6e 73 3a 69 76 65 63 3d 22 68 74 74 70 3a 2f [pixma] 0040:2f 77 77 77 2e 63 61 6e 6f 6e 2e 63 6f 6d 2f 6e [pixma] 0050:73 2f 63 6d 64 2f 32 30 30 38 2f 30 37 2f 63 6f [pixma] 0060:6d 6d 6f 6e 2f 22 3e 0d 0a 09 3c 69 76 65 63 3a [pixma] 0070:63 6f 6e 74 65 6e 74 73 3e 0d 0a 09 09 3c 69 76
[sane-devel] Canon MX370 / MX430 / MX510 / MX925 - Button Support
I asked the canon support, if it's possible under Windows. I will inform you about their answer. On 21.03.2014 18:40, Rolf Bensch wrote: Hi Matthias, Sorry I cannot find any button related data in the log file. Therefore your scanner has no button support. Unless you may find button support on a Windows machine or with binary. Then please sniff the usb communication (e.g. with wireshark) and send the log file to me. Cheers, Rolf Am 21.03.2014 00:03, schrieb Matthias Peter Walther: Hello, I tested every button. As far as I understand, the device has 4 Operation modes. The choice of the operating mode may influence the button behavior. I set it to scanner, after I tried out the four buttons for the four different operation modes. The results as attachment. Gr??e MPW Am 20.03.2014 16:52, schrieb Rolf Bensch: Hi Matthias, Please test all buttons and look if the debug output will change. The code says that some scanners ask to set the time when byte 3 is set. Cheers, Rolf Am 19.03.2014 00:31, schrieb Matthias Peter Walther: Hello, I think it works. That would be so cool. Thank you so much for your work on this and with the adf, too! I'll try out scanbd later. Do I have to do further code changes or is scanbd supposed to work just like that with that single additional line? Is it capable of detecting different buttons? So that it would be possible to sort the scans into different directories by different buttons? That would be so awesome. I pressed the button '9' on the dialpad. I think the menu buttons doesn't work, but the numbers do. Bye Matthias Am 18.03.2014 23:13, schrieb Rolf Bensch: Hi, If you like, please test button support for your scanner. If button support is working, you can use scanbd to control scanning via your scanner's buttons. You can find more infos about this in the mailing lists archive, e.g. here: http://sane.10972.n7.nabble.com/template/NamlServlet.jtp?macro=search_pagenode=3query=scanbddays=0sort=date To enable button support, add one single line with your scanner-pid in file pixma_mp150.c in function handle_interrupt() between lines 927 and 928, e.g. || s-cfg-pid == MX370_PID Test procedure: (1) 'export SANE_DEBUG_PIXMA=11' (2) press any button (3) check output from 'scanimage -A' You should see something like this: Buttons: --button-update Update button state [pixma] INTR T=1.670 len=32 [pixma] :00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] 0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] --button-1 int [1] [read-only] Button 1 --button-2 int [0] [read-only] Button 2 --original int [0] [read-only] Type of original to scan --target int [4] [read-only] Target operation type --scan-resolution int [0] [read-only] Scan resolution Please report your results. Cheers, Rolf
[sane-devel] Canon MX430 / MX510 / MX925 - does not recover when ADF out of paper
Hallo Rolf, that one screwed it. The scanner scans the first page, starts loading the second one and aborts. See the attached log. I inserted 3 papers as usual. The image size is 638x1050 (standard resolution, I think that is 75 or 150(?)). The image is in relation much higher than wide as a standard German DinA4 paper now, but the filled/scanned area is exact the same, last 1mm is still missing and the rest is plain, digital white. I think there might be a maximum hight the firmware of the scanner can handle in adf mode. How can we smartly test that? Or do we have to do that by hand? There's another adf related iussue: If something goes wrong with the hardware/pulling in of the papers, sane aborts and gets status 9. The only way to get the device out of this and to work again, is to restart the device or to once load the binary and close it. Could you look into there, if there is a command to reset the scanner somehow? See second log attached, tested with patch1+2 only. Bye Matthias Am 18.03.2014 22:39, schrieb Rolf Bensch: Hi, Am 18.03.2014 00:16, schrieb Matthias Peter Walther: scan passes through, and it is possible to do multiple scans in a row. Also tested with resolution 300. This is a good message. Two issues: - image is too width (binary detects page width somehow automatically) It seems so, but binary does! Binary image is 2479 pixels wide and pixma has 2552 pixels. It seems that binary crops image width to hide ADF frame and pixma doesn't. - image not high enough, last 1-1.5 mm of the page are missing. But this is the same with the binary package from canon. See that white stripe at the end. It seems that ADF cannot scan whole page length. Binary crops here, too. Pixma saves the expected image height of 3508 pixels. You can investigate this behaviour @ 75 dpi, if you like. Otherwise you can set the scan size (x, y positions and width, height) in the frontend to crop ADF frames by yourself. I prepared a new patch with these fixes (based on patch 2): (1) remove s-param-adf_pageid to avoid doubled coded functions. (2) all ADF scanners support 14 legal paper size in ADF mode, but only A4 in flatbed mode. Please test this patch again and try to use it in your productive work. If everything is OK, I'll commit this patch and we can close the ADF paper empty issue. Many thanks for your help. Cheers, Rolf
[sane-devel] Canon MX370 / MX430 / MX510 / MX925 - Button Support
Hello, I think it works. That would be so cool. Thank you so much for your work on this and with the adf, too! I'll try out scanbd later. Do I have to do further code changes or is scanbd supposed to work just like that with that single additional line? Is it capable of detecting different buttons? So that it would be possible to sort the scans into different directories by different buttons? That would be so awesome. I pressed the button '9' on the dialpad. I think the menu buttons doesn't work, but the numbers do. Bye Matthias Am 18.03.2014 23:13, schrieb Rolf Bensch: Hi, If you like, please test button support for your scanner. If button support is working, you can use scanbd to control scanning via your scanner's buttons. You can find more infos about this in the mailing lists archive, e.g. here: http://sane.10972.n7.nabble.com/template/NamlServlet.jtp?macro=search_pagenode=3query=scanbddays=0sort=date To enable button support, add one single line with your scanner-pid in file pixma_mp150.c in function handle_interrupt() between lines 927 and 928, e.g. || s-cfg-pid == MX370_PID Test procedure: (1) 'export SANE_DEBUG_PIXMA=11' (2) press any button (3) check output from 'scanimage -A' You should see something like this: Buttons: --button-update Update button state [pixma] INTR T=1.670 len=32 [pixma] :00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] 0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] --button-1 int [1] [read-only] Button 1 --button-2 int [0] [read-only] Button 2 --original int [0] [read-only] Type of original to scan --target int [4] [read-only] Target operation type --scan-resolution int [0] [read-only] Scan resolution Please report your results. Cheers, Rolf -- next part -- [sanei_debug] Setting debug level of pixma to 11. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.6 [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:002:019 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA MX370 Series at libusb:002:019 [pixma] pixma_open(): Canon PIXMA MX370 Series [pixma] INTR T=3.759 len=32 [pixma] :00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] 0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] [pixma] INTR T=4.015 len=32 [pixma] :00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] 0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] [pixma] pixma_close(): Canon PIXMA MX370 Series All options specific to device `pixma:04A91759_61B4A4': Scan mode: --resolution auto||75|150|300|600|1200dpi [75] Sets the resolution of the scanned image. --mode auto|Color|Gray|Lineart [Color] Selects the scan mode (e.g., lineart, monochrome, or color). --source Flatbed|Automatic Document Feeder [Flatbed] Selects the scan source (such as a document-feeder). Set source before mode and resolution. Resets mode and resolution to auto values. --button-controlled[=(yes|no)] [no] When enabled, scan process will not start immediately. To proceed, press SCAN button (for MP150) or COLOR button (for other models). To cancel, press GRAY button. Gamma: --custom-gamma[=(auto|yes|no)] [yes] Determines whether a builtin or a custom gamma-table should be used. --gamma-table auto|0..255,... Gamma-correction table. In color mode this option equally affects the red, green, and blue channels simultaneously (i.e., it is an intensity gamma table). --gamma auto|0.299988..5 [2.2] Changes intensity of midtones Geometry: -l auto|0..216.069mm [0] Top-left x position of scan area. -t auto|0..297.011mm [0] Top-left y position of scan area. -x auto|0..216.069mm [216.069] Width of scan-area. -y auto|0..297.011mm [297.011] Height of scan-area. Buttons: --button-update Update button state --button-1 int [0] [read-only] Button 1 --button-2 int [0] [read-only] Button 2 --original int [0] [read-only] Type of original to scan --target int [0] [read-only] Target operation type --scan-resolution int [0] [read-only] Scan resolution Extras: --threshold auto|0..100% (in steps of 1) [inactive] Select minimum-brightness to get a white point --threshold-curve auto|0..127 (in steps of 1) [inactive] Dynamic threshold curve, from light to dark, normally 50-65
[sane-devel] Fwd: Re: Canon MX430 / MX510 / MX925 - does not recover when ADF out of paper
Hello, scan passes through, and it is possible to do multiple scans in a row. Also tested with resolution 300. Two issues: - image is too width (binary detects page width somehow automatically) - image not high enough, last 1-1.5 mm of the page are missing. But this is the same with the binary package from canon. See that white stripe at the end. (image cut out for mailinglist) Gr??e Matthias Am 17.03.2014 21:39, schrieb Rolf Bensch: Hi, As you can see on the log file, the backend doesn't start a new scan after page 3 has been scanned. Due to this the scanner cannot handle the scan commands and a timeout raises. I prepared a patch with a new adf state variable. This patch is based on the latest git sources and patch1. Please test the patch and create a new log file. Cheers, Rolf Am 17.03.2014 21:03, schrieb Matthias Peter Walther: Hello All, I had some trouble to apply the new patch, but Rolf helped me to fix it. Here comes the result with git + patch pixma_mp150.c.patch1, 3 pages in ADF. It works correct, but the timeout at the end acts weird. In the log it counts down 8 7 6...but between each line it pauses around 15-20 seconds. This scan took ages! The log comes as attachment. Bye Matthias Am 15.03.2014 20:16, schrieb Rolf Bensch: Hi All, Now we have Matthias on board with his MX375. Please don't use the old patches. I started changing code in pixma.c where we might get problems with other scanners, e.g. with the Imageclass sub-backend. So, we should find a fix which affects pixma_mp150.c only. We should start at the beginning. Please use attached patch with latest code from git. I added some additional debug outputs to show the status of adf scanning. Please create a debug file with 'export SANE_DEBUG_PIXMA=4'. I also added TODO comments as hints for possible fixes. Cheers, Rolf Am 14.03.2014 22:41, schrieb Matthias Peter Walther: Hallo Rolf, thanks for your quick reply. I'm from Germany too, by the way. But to keep this conformed, I'm gonna answer you in english. If I understood your posts correctly, you want me to use patch 3+4. Patch 5 is only for the feature to initiate a scan from the device. Which is nice, but I will look into that later. So I pulled my git-sane-backend-repo and patched it: mpw at Server0:~/sane$ patch -p1 attachment-0003.bin patching file sane-backends/backend/pixma.c mpw at Server0:~/sane$ patch -p1 attachment-0004.bin patching file sane-backends/backend/pixma_mp150.c Hunk #2 succeeded at 1397 (offset -12 lines). Hunk #3 succeeded at 1439 (offset -12 lines). Hunk #4 succeeded at 1493 (offset -12 lines). Hunk #5 succeeded at 1560 (offset -12 lines). Hunk #6 succeeded at 1568 (offset -12 lines). Hunk #7 succeeded at 1580 (offset -12 lines). I think the offset is related to the age of the patch. After installing, I check the ldconfig: $ sudo ldconfig -v | grep libsane /sbin/ldconfig.real: Kann ?stat()? f?r ?/lib/i686-linux-gnu? nicht aufrufen: Datei oder Verzeichnis nicht gefunden /sbin/ldconfig.real: Kann ?stat()? f?r ?/usr/lib/i686-linux-gnu? nicht aufrufen: Datei oder Verzeichnis nicht gefunden /sbin/ldconfig.real: Pfad ?/usr/local/lib? mehrfach angegeben /sbin/ldconfig.real: Pfad ?/lib/x86_64-linux-gnu? mehrfach angegeben /sbin/ldconfig.real: Pfad ?/usr/lib/x86_64-linux-gnu? mehrfach angegeben libsane.so.1 - libsane.so.1.0.25 libsane.so.1 - libsane.so.1.0.22 /sbin/ldconfig.real: Es ist nicht m?glich, den Status (stat()) der Datei /usr/lib/x86_64-linux-gnu/libsoftokn3.so zu lesen: Datei oder Verzeichnis nicht gefunden libsane.so.1 - libsane.so.1.0.22 libsane-canon_mfp.so.1 - libsane-canon_mfp.so.1.0.9 This looks good, I think I had 1.0.24 from last october before. Okay, I tried a scan then: $ scanadf scanadf: sane_read: Error during device I/O Error during device I/O Scanned 0 pages $ This did not work before, either. Maybe my sane-frontend is too old? I have the original one from Ubuntu 12.04.4. $ scanadf --version scanadf (sane-frontends) 1.0.14 Next try, scanimage: $ scanimage --source Automatic Document Feeder -p --batch Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 Scanned page 1. (scanner status = 5) Scanning page 2 scanimage: sane_read: Document feeder out of documents Scanned page 2. (scanner status = 7) mpw at Server0:~/sane$ ls attachment-0003.bin attachment-0004.bin out1.pnm sane-backends This is a first success. But as you can see in the output of ls, it stores only the first page, the second is lost. Or is there something wrong with my scanimage-command? BTW: Can you please change Automatic Document Feeder to simply ADF, that would be much more comfortable to type :) So thanks for your patch, I think it's almost perfect. I just need to store the 2nd page. Please let me know, if you need more detailed debugging output. Will you commit this two patches to the git repository? Gr??e
[sane-devel] Canon MX430 / MX510 / MX925 - does not recover when ADF out of paper
Hello All, I had some trouble to apply the new patch, but Rolf helped me to fix it. Here comes the result with git + patch pixma_mp150.c.patch1, 3 pages in ADF. It works correct, but the timeout at the end acts weird. In the log it counts down 8 7 6...but between each line it pauses around 15-20 seconds. This scan took ages! The log comes as attachment. Bye Matthias Am 15.03.2014 20:16, schrieb Rolf Bensch: Hi All, Now we have Matthias on board with his MX375. Please don't use the old patches. I started changing code in pixma.c where we might get problems with other scanners, e.g. with the Imageclass sub-backend. So, we should find a fix which affects pixma_mp150.c only. We should start at the beginning. Please use attached patch with latest code from git. I added some additional debug outputs to show the status of adf scanning. Please create a debug file with 'export SANE_DEBUG_PIXMA=4'. I also added TODO comments as hints for possible fixes. Cheers, Rolf Am 14.03.2014 22:41, schrieb Matthias Peter Walther: Hallo Rolf, thanks for your quick reply. I'm from Germany too, by the way. But to keep this conformed, I'm gonna answer you in english. If I understood your posts correctly, you want me to use patch 3+4. Patch 5 is only for the feature to initiate a scan from the device. Which is nice, but I will look into that later. So I pulled my git-sane-backend-repo and patched it: mpw at Server0:~/sane$ patch -p1 attachment-0003.bin patching file sane-backends/backend/pixma.c mpw at Server0:~/sane$ patch -p1 attachment-0004.bin patching file sane-backends/backend/pixma_mp150.c Hunk #2 succeeded at 1397 (offset -12 lines). Hunk #3 succeeded at 1439 (offset -12 lines). Hunk #4 succeeded at 1493 (offset -12 lines). Hunk #5 succeeded at 1560 (offset -12 lines). Hunk #6 succeeded at 1568 (offset -12 lines). Hunk #7 succeeded at 1580 (offset -12 lines). I think the offset is related to the age of the patch. After installing, I check the ldconfig: $ sudo ldconfig -v | grep libsane /sbin/ldconfig.real: Kann ?stat()? f?r ?/lib/i686-linux-gnu? nicht aufrufen: Datei oder Verzeichnis nicht gefunden /sbin/ldconfig.real: Kann ?stat()? f?r ?/usr/lib/i686-linux-gnu? nicht aufrufen: Datei oder Verzeichnis nicht gefunden /sbin/ldconfig.real: Pfad ?/usr/local/lib? mehrfach angegeben /sbin/ldconfig.real: Pfad ?/lib/x86_64-linux-gnu? mehrfach angegeben /sbin/ldconfig.real: Pfad ?/usr/lib/x86_64-linux-gnu? mehrfach angegeben libsane.so.1 - libsane.so.1.0.25 libsane.so.1 - libsane.so.1.0.22 /sbin/ldconfig.real: Es ist nicht m?glich, den Status (stat()) der Datei /usr/lib/x86_64-linux-gnu/libsoftokn3.so zu lesen: Datei oder Verzeichnis nicht gefunden libsane.so.1 - libsane.so.1.0.22 libsane-canon_mfp.so.1 - libsane-canon_mfp.so.1.0.9 This looks good, I think I had 1.0.24 from last october before. Okay, I tried a scan then: $ scanadf scanadf: sane_read: Error during device I/O Error during device I/O Scanned 0 pages $ This did not work before, either. Maybe my sane-frontend is too old? I have the original one from Ubuntu 12.04.4. $ scanadf --version scanadf (sane-frontends) 1.0.14 Next try, scanimage: $ scanimage --source Automatic Document Feeder -p --batch Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 Scanned page 1. (scanner status = 5) Scanning page 2 scanimage: sane_read: Document feeder out of documents Scanned page 2. (scanner status = 7) mpw at Server0:~/sane$ ls attachment-0003.bin attachment-0004.bin out1.pnm sane-backends This is a first success. But as you can see in the output of ls, it stores only the first page, the second is lost. Or is there something wrong with my scanimage-command? BTW: Can you please change Automatic Document Feeder to simply ADF, that would be much more comfortable to type :) So thanks for your patch, I think it's almost perfect. I just need to store the 2nd page. Please let me know, if you need more detailed debugging output. Will you commit this two patches to the git repository? Gr??e aus M?nster Matthias Am 14.03.2014 19:31, schrieb Rolf Bensch: Hi Matthias, Please read this thread: http://lists.alioth.debian.org/pipermail/sane-devel/2014-March/032138.html. Cheers, Rolf Am 12.03.2014 21:11, schrieb Matthias Peter Walther: Hello, I'm new to this, but I'm gonna try my luck. I own a Canaon MX375 all-in-one. The PIXMA-backend has this annoying adf-empty-bug. Is there any information I could provice to help to fix this? The binary driver from canon.uk works with their gui-frontend only and I'd like to get it working on a headless system. Thanks for any comments. Bye Matthias Walther -- next part -- mpw at Server0:~$ SANE_DEBUG_PIXMA=4 scanimage -b test%02.pnm --source Automatic Document Feeder [sanei_debug] Setting debug level of pixma to 4. [pixma] pixma is compiled with pthread support
[sane-devel] Fixing PIXMA MX360/370 ADF empty bug
Hello, I'm new to this, but I'm gonna try my luck. I own a Canaon MX375 all-in-one. The PIXMA-backend has this annoying adf-empty-bug. Is there any information I could provice to help to fix this? The binary driver from canon.uk works with their gui-frontend only and I'd like to get it working on a headless system. Thanks for any comments. Bye Matthias Walther
