[sane-devel] Kodak i30 Initialisation
Hi, i'm trying to use a Kodak i30 Sheetfeed-Scanner, which is an AVISION OEM Scanner, thus should be working with the avision backend. I'm currently running Debian Testing with sane 1.0.14-12 and libsane 1.0.25-4. When trying to scan, the scanner gets stuck with some IO Errors: env SANE_DEBUG_AVISION=7 scanimage > scan.pnm 2> /tmp/debug.log: ... [avision] try to read status to clear the FIFO [avision] avision_usb_status: timeout 500, 1 retries [avision] ==> (bulk read) going down ... [avision] <== (bulk read) got: 0, status: 0 [avision] ==> (interrupt read) going down ... [avision] <== (interrupt read) got: 0, status: 0 [avision] === Got error 9 trying to read status. === [avision] wait_ready: test unit ready failed (Error during device I/O) However sane-find-scanner and scanimage -L seem fine (when the scanner is not blocked): found USB scanner (vendor=0x040a [KODAK ], product=0x6001 [i30 SCANNER]) at libusb:007:003 could not fetch string descriptor: Pipe error could not fetch string descriptor: Pipe error [avision] attach: "KODAK" - "i30 Scanner" not yet in whitelist! [avision] attach: You might want to report this output. [avision] attach: To: r...@exactcode.de (the Avision backend author) device `avision:libusb:007:003' is a Kodak i30 sheetfed scanner When running Windows 7 in a VM and assigning the scanner to it, the scanner works of course. The Suprising part is, that after using the scanner in the VM it works with SANE flawlessly as well until the next power cycle... So there seems to be something wrong with scanner initialisation. Can somebody give me a hint how to find this issue? Maybe sniff the usb traffic of the windows driver? (I've never done this, so maybe someone can help) Other ideas are welcome as well... Regards Sebastian -- 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] Scanbd, Sane and Samsung SCX-3200
Hi Janne, Am 26.05.2017 um 14:03 schrieb Janne Paalijarvi: > Hello, > > I am developing support for scan button for my Samsung SCX-3200 series. > In fact, I actually already wrote some code at: > > https://github.com/usvi/random/tree/master/c/scanbuttond/samsung > > Funnily, I have had not time before these few days to actually try to > set everything to work for testing. > > Now, when I installed scanbd for my test Ubuntu from Ubuntu > repositories, I realized that it uses extensively Sane backends. So, my > question is: Should I actually try to write a backend extension for the > Sane backend I am using (xerox_mfp)? Is it the way of the future that > Scanbd actually polls/queries devices via Sane? I wrote scanbd in order to use the sane-backend, because at the time of starting with scanbd, scanbuttond seems quite dead. I incorporated scanbuttond-backends "as-is" to support scanners that didn't had querying support in sane-backends. So - in short - up to my view it would be best to make the snae-backend for your scanner working ... HTH, Wilhelm -- 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] Sane-backends is open for development
Hi Rolf, Rolf Bensch writes: > Hi Allan, > > If I'm checking the version with scanimage, I get this back: > > $ scanimage -V > scanimage (sane-backends) 1.0.27git; backend version 1.0.27 > > Maybe the backend version should also show 1.0.27git? The backend version bit shows whatever sane_init gets back as the version of the backend. In most situations that will be the dll backend but you could set up your system to have scanimage use a specific backend directly. So for the pixma backend that becomes 1.0.17, if I got my maths right. This is compliant with the SANE spec. You're supposed to return the *backend* version in the sane_init() call. The *backend* version is defined in section 4.1: SANE version control also includes a minor version number and a build revision. While control of these numbers remains with the implementor of a backend, the recommended use is as follows. The minor version is incremented with each official release of a backend. The build revision is increased with each build of a backend. So a backend could even return something like 1.5.123, as long as the major version matches the major version of the SANE API it provides. There is actually quite a bit of misunderstanding of the use of version numbers in sane-backends but that's a long story. It involves package version, SANE API version, dynamic library versioning as well as backend versions. The problem is that people tend to assume it's all the same thing while in fact they are all very different and mostly independent. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- 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
