<div dir="ltr"><div><div>With both 9000f scanners connected, it's:</div><div><br></div><div>pi@raspberrypi ~/sambashare2 $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib scanimage -L<br></div><div>device `pixma:04A91908' is a CANON Canoscan 9000F multi-function peripheral</div>
<div>device `pixma:04A91908' is a CANON Canoscan 9000F multi-function peripheral</div><div>pi@raspberrypi ~/sambashare2 $</div></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Feb 23, 2014 at 7:01 AM, m. allan noah <span dir="ltr"><<a href="mailto:kitno455@gmail.com" target="_blank">kitno455@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What is the output of scanimage -L<br>
<span class="HOEnZb"><font color="#888888"><br>
allan<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Sun, Feb 23, 2014 at 12:15 AM, Joel Penner <<a href="mailto:joelcpenner@gmail.com">joelcpenner@gmail.com</a>> wrote:<br>
> Using lsusb -t I get this feedback:<br>
><br>
> pi@raspberrypi ~ $ lsusb -t<br>
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M<br>
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M<br>
> |__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M<br>
> |__ Port 3: Dev 11, If 0, Class=vend., Driver=usbfs, 480M<br>
><br>
> I do notice how sane-find-scanner returns the bus/port data:<br>
><br>
> sudo sane-find-scanner<br>
><br>
> # sane-find-scanner will now attempt to detect your scanner. If the<br>
> # result is different from what you expected, first make sure your<br>
> # scanner is powered up and properly connected to your computer.<br>
><br>
> # No SCSI scanners found. If you expected something different, make sure<br>
> that<br>
> # you have loaded a kernel SCSI driver for your SCSI adapter.<br>
> # Also you need support for SCSI Generic (sg) in your operating system.<br>
> # If using Linux, try "modprobe sg".<br>
><br>
> found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan]) at<br>
> libusb:001:011<br>
> found USB scanner (vendor=0x0424, product=0xec00) at libusb:001:003<br>
><br>
> How would I use the libusb:001:011 identifier for the 9000f with scanimage?<br>
> If I try to tell scanimage to use one of those with the -device option, I<br>
> get this feedback:<br>
><br>
> pi@raspberrypi ~/sambashare $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib scanimage<br>
> --progress --verbose --batch --format=tiff --resolution=2400 -x 240 -y 135<br>
> -d libusb:001:011 --batch-start=110000 > /home/pi/sambashare/myco%5d.tif<br>
> scanimage: open of device libusb:001:011 failed: Invalid argument<br>
> pi@raspberrypi ~/sambashare $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib scanimage<br>
> --progress --verbose --batch --format=tiff --resolution=2400 -x 240 -y 135<br>
> -d libusb:001:003 --batch-start=110000 > /home/pi/sambashare/myco%5d.tif<br>
> scanimage: open of device libusb:001:003 failed: Invalid argument<br>
><br>
><br>
> - Joel<br>
><br>
> On Thu, Feb 20, 2014 at 5:33 PM, Olaf Meeuwissen <<a href="mailto:olaf.meeuwissen@avasys.jp">olaf.meeuwissen@avasys.jp</a>><br>
> wrote:<br>
>><br>
>><br>
>> m. allan noah writes:<br>
>><br>
>> > Some scanners have a serial number which can be seen by software. Some<br>
>> > sane backends use that serial as part of the device name. If your<br>
>> > scanners or the pixma backend don't support this, you will have to<br>
>> > find another way. Perhaps forcing the device name using udev or<br>
>> > whatever Linux is using this week.<br>
>><br>
>> It just so happens that I've been looking at this about three weeks ago<br>
>> for a third party backend. The scanners this backend should support<br>
>> have varying degrees of serial number support:<br>
>><br>
>> - not at all<br>
>> - at the USB level only<br>
>> - at the device protocol level only<br>
>> - at both USB and device protocol level only<br>
>><br>
>> I wanted/needed to be able to support all of the above, even the case<br>
>> where there is *no* serial number support at all. With libusb-1.0 this<br>
>> is possible (at least on a recent enough Linux system) using the<br>
>><br>
>> libusb_get_bus_number()<br>
>><br>
>> and<br>
>><br>
>> libusb_get_device_address()<br>
>><br>
>> API. When using libusb-1.0.12 or later you can also use<br>
>><br>
>> libusb_get_port_number()<br>
>><br>
>> With a USB device hooked up to my machine, lsusb -t shows:<br>
>><br>
>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M<br>
>> |__ Port 5: Dev 26, If 0, Class=Vendor Specific Class, Driver=, 480M<br>
>><br>
>> Inserting a USB hub between the two, this changes to:<br>
>><br>
>> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M<br>
>> |__ Port 5: Dev 27, If 0, Class=Hub, Driver=hub/4p, 480M<br>
>> |__ Port 4: Dev 28, If 0, Class=Vendor Specific Class, Driver=,<br>
>> 480M<br>
>><br>
>> The device number (Dev) changes every time you reconnect the USB cable<br>
>> (or power cycle the device) but bus and port numbers don't change (but<br>
>> they might upon a reboot).<br>
>><br>
>> > On Thu, Feb 20, 2014 at 1:47 AM, Joel Penner <<a href="mailto:joelcpenner@gmail.com">joelcpenner@gmail.com</a>><br>
>> > wrote:<br>
>> >> I have two CanoScan 9000f scanners that I'm using for a time-lapse<br>
>> >> scanner<br>
>> >> photography project. How do I tell two instances of scanimage to each<br>
>> >> use<br>
>> >> their own 9000f scanner on the same raspberry pi using the -device<br>
>> >> flag?<br>
>> >> Using sane-find-scanner to find an ID of connected scanners generates<br>
>> >> the<br>
>> >> same ID for both, non-surprisingly.<br>
>><br>
>> Hope this helps,<br>
>> --<br>
>> Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION<br>
>> FSF Associate Member #1962 Help support software freedom<br>
>> <a href="http://www.fsf.org/jf?referrer=1962" target="_blank">http://www.fsf.org/jf?referrer=1962</a><br>
>><br>
>> --<br>
>> sane-devel mailing list: <a href="mailto:sane-devel@lists.alioth.debian.org">sane-devel@lists.alioth.debian.org</a><br>
>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel</a><br>
>> Unsubscribe: Send mail with subject "unsubscribe your_password"<br>
>> to <a href="mailto:sane-devel-request@lists.alioth.debian.org">sane-devel-request@lists.alioth.debian.org</a><br>
><br>
><br>
<br>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
"The truth is an offense, but not a sin"<br>
<br>
</div><div class="HOEnZb"><div class="h5">--<br>
sane-devel mailing list: <a href="mailto:sane-devel@lists.alioth.debian.org">sane-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel</a><br>
Unsubscribe: Send mail with subject "unsubscribe your_password"<br>
to <a href="mailto:sane-devel-request@lists.alioth.debian.org">sane-devel-request@lists.alioth.debian.org</a><br>
</div></div></blockquote></div><br></div>