Re: [sane-devel] PIXMA MG7150 test
Le Wednesday 23 September 2015, 12:00:02 sane-devel- requ...@lists.alioth.debian.org a écrit : > > Hello, > > > > > > > > I have a Canon PIXMA MG7150. It has an usb port but it's connected to my > > computer via wifi. > > > > > > > > The scanner is detected automatically and i can use scanimage -d pixma -- > > format=tiff > image.tiff. > > However I usually scan with the scanner buttons and the tactile screen > > (I'm not going to do 9000 two-way trips to scan a file) but the > > --button- controlled option doesn't work (the scanner detects my computer > > but doesn't start the scan) so I can't send the output directly to my > > computer.> > > > > > > The default resolution (75dpi) is too low for me to read the tiff image, > > so I tested the other ones listed on the scanner screen (600, 300 and > > 150) with> > > the --resolution option : > > - 150dpi doesn't work. The output file is corrupteed. scanimage output : > > [bjnp] bjnp_recv_data: could not read response payload (select timed > > out): > > Success! > > [bjnp] bjnp_recv_data: could not read response payload (select timed > > out): > > Success! > > [bjnp] bjnp_write: ERROR: scanner data left = 0xee4 = 3812 > > [bjnp] bjnp_recv_header:ERROR, Received response has cmd code 235, > > expected 33 > > [bjnp] Could not read response to command! > > [bjnp] bjnp_write: ERROR: scanner data left = 0xee4 = 3812 > > [bjnp] bjnp_recv_header:ERROR, Received response has cmd code 241, > > expected 33 > > [bjnp] Could not read response to command! > > scanimage: sane_read: Error during device I/O > > > > > > - 300dpi works but it takes 5 minutes instead of 10 seconds > > - 600dpi doesn't work. The output file is cut (the lower part of the > >sheet is > > > missing). scanimage ouptut : > > [bjnp] bjnp_recv_data: could not read response payload (select timed > > out): > > Success! > > scanimage: sane_read: Error during device I/O > > > > > > > > First a few questions: > - What is the version of sane-backends that you are using? > - Did you try button controlled scanning over USB? The bjnp code > replaces the USB interface when the network scanning is used, but as it > is more complex and less tested than the standard USB code, we like you > to test with USB first, so we know where to look for the issues: in the > pixma backend or in the network code. > > I don't recall ever testing button controlled scanning with scanimage, > so I don't know how that works. I doubt if the resolution received from > the scanner is used by scanimage. @Rolf, can you please comment? > > Button controlled scanning is not used very often, so even if the > scanner is supported by the backend, the parsing of the buttons may > still be incorrect. > @Rolf Bensch, can you please comment, you know the backend much better > than I do, I only wrote the BJNP network code. > > For button controlled scanning I would anyhow recommend setting up > scanbd as that will allow setting the scanner up to continuously poll > the scanner and initiate a scan with the parameters entered on the > scanner and store the result on the computer as often as you press one > of the scan buttons. That will save you many trips from the computer to > the scanner, as you can scan whenever you press a button and the > computer is on > > Best regards, Louis Hello, I am using sane 1.0.24. USB test : I linked my sanner to my computer via USB and I disabled the computer wifi. The scanner is detected by "scanimage -L" and I can scan with "scanimage -- format=tiff > image.tiff". I can scan with 75 (default), 150, 300 and 600dpi resolutions. 1200dpi (which is not proposed by the scanner screen) takes about five minutes and output a corrupted image. When I type "scanimage --format=tiff --batch --button-controlled=yes " it says : Scanning -1 pages, incrementing by 1, numbering from 1 Scanning page 1 So I start the scan from the scanner (I set the output location to Local (USB) and press the COLOR button), the scanner says "Please wait..." for a while but scanimage does nothing. WIFI test : I did the wifi test again, just to make sure (truth is, in the last test, I typed "--resolution 300" instead "--resolution=300"). 75, 150, 300 and 600dpi work fine, I don't have any errors anymore. But with the 600dpi resolution the scanner seems to stop and then start its engine several times during the scan, and the time to send the image to my computer is longer than when I use windows. Maybe it's possible to send the image during the scan. SCANBD test : I tried to set up scanbd with the help of the archlinux wiki (https:// wiki.archlinux.org/index.php/Scanner_Button_Daemon), but I get this ("journalctl -u scanbd"): sept. 23 16:31:25 some-pc systemd[1]: Started Scanner button polling Service. sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: debug on: level: 7 sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: dropping privs to uid nobody sept. 23 16:31:25 some-pc scanbd[5342]:
Re: [sane-devel] Xsane (canon MG6450)
Hi Lovro, Your scanner wasn't fully supported by the backend version 1.0.24. 1200dpi scans don't work. Everthing else should work with scans up to 600 dpi. Please test all options with your favourite frontend. I prefer xsane. If you might get problems with 1.0.24, you won't get around to install Sane 1.0.25 from git. The brightness of the scan result depends on the scan settings. Please try the sliders in xsane and watch the results in the preview window. Hope this helps. Cheers, Rolf Am 19.09.2015 um 21:45 schrieb lovrolu: > I have already installed SANE (through my distribution's package > manager) and confirmed that it works with my scanner. I'm on Fedora 22 > running GNU/Linux, kernel release 4.1.6-201.fc22.x86_64. > > Running `scanimage -V` from the shell returns > > scanimage (sane-backends) 1.0.24; backend version 1.0.24 > > I'm not sure but I think the git version of SANE is 1.0.25. Since 1.0.24 > works just fine (from the tests I've done -- the reason I would like to > help out is to confirm that it *fully* works as expected on 1.0.24) I'm > not sure if upgrading to 1.0.25 is worthwhile, at least currently. > > I have also installed the official driver from Canon. Scans produced > using Canon's driver are a bit brighter but this is probably just to > different default settings. Since it was just a quick test I didn't > bother too much customizing the brightness level but I might do that if > required. > > Anyway, I wanted to know if there's a test suite that SANE offers that I > could run or some kind of a procedure I could go through to verify that > SANE *fully* works as expected with my scanner (and with this particular > version of SANE I have)? > > If you think I should use the latest version of SANE I can probably do > that but most likely not right away. However, I would like to try out > 1.0.24 first, if possible. > > Have a nice day, > Lovro > >> Hi Lovro, >> >> The MG6400 Series scanner is supported by the git version of Sane: >> http://www.sane-project.org/lists/sane-backends-cvs.html#S-PIXMA . >> >> You can check the latest code with your scanner. Please install Sane > >from git as described in README.linux: >> http://www.sane-project.org/docs.html . >> >> Many thanks for your help. >> >> Cheers, >> Rolf >> >> Am 18.09.2015 um 22:55 schrieb lovrolu: >>> Since quite some time has passed and it looks like OP either gave up or >>> had some difficulties, I thought I would chime in and help out since I >>> just got mine today. >>> >>> http://www.sane-project.org/sane-backends.html#S-PIXMA lists PIXMA >>> MG6450's status as "untested". I would like to resolve this. Could >>> someone point me in the right direction? What am I to do as a tester? >>> >>> Lovro > -- 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] PIXMA MG7150 test
On Wed, Sep 23, 2015 at 11:45 PM, Kiligolowrote: > Le Wednesday 23 September 2015, 12:00:02 sane-devel- > requ...@lists.alioth.debian.org a écrit : /../ > I linked my sanner to my computer via USB and I disabled the computer wifi. > The scanner is detected by "scanimage -L" and I can scan with "scanimage -- > format=tiff > image.tiff". > I can scan with 75 (default), 150, 300 and 600dpi resolutions. 1200dpi (which > is not proposed by the scanner screen) takes about five minutes and output a > corrupted image. Hi, Just a comment: This is already fixed more than a year ago, so if you need this then you can install the source, or wait for 1.0.25 to be released and be available in your distribution. Changelog entry: 2014-05-08 Rolf Bensch * backend/pixma_mp150.c: fix MG7100 image data post processing @ high resolutions > 600dpi. * doc/descriptions/pixma.desc, doc/sane-pixma.man: Canon Pixma MG7100 Series scanner is working, reported by Gert Cauwenberg. * backend/pixma.h, doc/descriptions/pixma.desc: Pixma backend version 0.17.8 /../ Regards, Gernot Hassenpflug -- 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] Avision AVA5
Hello! Is device idVendor=0638, idProduct=0ad7 supported anyway ? Device info in attachment. new high speed USB device using ehci_hcd and address 3 New USB device found, idVendor=0638, idProduct=0ad7 New USB device strings: Mfr=1, Product=2, SerialNumber=0 Product: USB2.0 Scanner Manufacturer: Hewlett-Packard bash-4.1# lsusb -D /dev/bus/usb/001/003 Device: ID 0638:0ad7 Avision, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0638 Avision, Inc. idProduct 0x0ad7 bcdDevice1.00 iManufacturer 1 Hewlett-Packard. iProduct2 USB2.0 Scanner iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 3 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x0001 Self Powered -- 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