[sane-devel] Multiple Scanner Support

[Joel Penner]

Hi. I'm currently using multiple scanners for a project where I have flowers
scanned a few times an hour to make videos of the desiccation process. I'm
currently in Germany where I've managed to get three scanners running off of
one iBook, but at home I have eight scanners strewn across multiple old
computers. My original idea was to have all the scanners running off of one
computer, but issues with drivers conflicting with each other in addition to
poorly programmed drivers which use over half of the CPU's resources while
scanning presented problems. I've been using the included software packages
where possible, and VueScan when not. I've experimented a bit with SANE. I
was wondering what people thought about the possibility of running multiple
scanners off of one computer. Does SANE support this? And I've been using
solely PPC Macs running either 10.4 or 10.5 so far.

You can find some videos of my project here:

http://www.flickr.com/photos/featheredtar/sets/72157611634807864/

Thanks,

Joel
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Multiple Scanner Support

[Joel Penner]

Thanks. Here I'm using a CanoScan 5600F (the Mac driver of which is kind of
unstable, and the shipped program horribly bloated!,) an Epson Perfection
V33 (a bad scanner!,) and a CanoScan 3200 (which I'm using with VueScan,
it's proven to be very stable.) At home I have another CS 5600F, two CS LiDE
20s, a CS 5000, an Agfa Snapscan e20 and e50, and a really good Epson
scanner, the name of which I forget. I could VNC the computer to find out,
but I'm on my cell phone data connection right now...

The issue of resource hogging isn't common. So far I've only starkly
experienced it with the CS 5600Fs. It's unfortunate that such an amazing
scanner has to have such a shoddy Mac backend/driver. Hopefully the eventual
SANE backend will be better!

Similar to your idea, initially I tried running multiple instances of
VueScan, but because the specific scanners weren't specified to each
instance, they presumably conflicted, causing the different instances
to occasionally crash. How would one give explicit device names to each
copy? I am very comfortable with OS GUIs, but unfortunately have done almost
no programming.

- Joel

On Thu, Jul 14, 2011 at 2:05 AM, m. allan noah  wrote:

> Neat videos!
>
> The answer to your question depends on the scanner, and the driver (we
> call them backends).
>
> 1. Some scanners are really dumb and require the host software to do
> lots of processing to get a usable image. You could certainly stagger
> the scans so that two scanners were never in use at the same time.
>
> 2. Some backends are written to only talk to one scanner, and may not
> play well if two scanners are open from within the same application.
> It might be possible to avoid this by running multiple copies of the
> app, and giving explicit device names to each copy.
>
> What scanners are you using now?
>
> allan
>
> On Wed, Jul 13, 2011 at 7:53 PM, Joel Penner 
> wrote:
> > Hi. I'm currently using multiple scanners for a project where I have
> flowers
> > scanned a few times an hour to make videos of the desiccation process.
> I'm
> > currently in Germany where I've managed to get three scanners running off
> of
> > one iBook, but at home I have eight scanners strewn across multiple old
> > computers. My original idea was to have all the scanners running off of
> one
> > computer, but issues with drivers conflicting with each other in addition
> to
> > poorly programmed drivers which use over half of the CPU's resources
> while
> > scanning presented problems. I've been using the included software
> packages
> > where possible, and VueScan when not. I've experimented a bit with SANE.
> I
> > was wondering what people thought about the possibility of running
> multiple
> > scanners off of one computer. Does SANE support this? And I've been using
> > solely PPC Macs running either 10.4 or 10.5 so far.
> > You can find some videos of my project here:
> >
> > http://www.flickr.com/photos/featheredtar/sets/72157611634807864/
> > Thanks,
> > Joel
> > --
> > sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
> >
>
>
>
> --
> "The truth is an offense, but not a sin"
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110714/0d07d30f/attachment-0001.html>

[sane-devel] Using scanimage's -device option to specify one of two identical scanners

[Joel Penner]

I have two CanoScan 9000f scanners that I'm using for a time-lapse scanner
photography project. How do I tell two instances of scanimage to each use
their own 9000f scanner on the same raspberry pi using the -device flag?
Using sane-find-scanner to find an ID of connected scanners generates the
same ID for both, non-surprisingly.
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Using scanimage's -device option to specify one of two identical scanners

[Joel Penner]

When I run scanimage -L, I get a pixma-derived device name that's identical
for both. Is there another way that I would find the device name that would
include the serial number if the backend supports this?

How would I go about forcing the device name via udev or something like it?
Is there an online tutorial, video, or forum posting that would guide me
through this?

Thanks Allan.

Joel


On Thu, Feb 20, 2014 at 6:06 AM, m. allan noah  wrote:

> Some scanners have a serial number which can be seen by software. Some
> sane backends use that serial as part of the device name. If your
> scanners or the pixma backend don't support this, you will have to
> find another way. Perhaps forcing the device name using udev or
> whatever Linux is using this week.
>
> allan
>
> On Thu, Feb 20, 2014 at 1:47 AM, Joel Penner 
> wrote:
> > I have two CanoScan 9000f scanners that I'm using for a time-lapse
> scanner
> > photography project. How do I tell two instances of scanimage to each use
> > their own 9000f scanner on the same raspberry pi using the -device flag?
> > Using sane-find-scanner to find an ID of connected scanners generates the
> > same ID for both, non-surprisingly.
> >
> > --
> > sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>
>
>
> --
> "The truth is an offense, but not a sin"
>
> --
> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20140220/874f4139/attachment.html>

[sane-devel] Using scanimage's -device option to specify one of two identical scanners

[Joel Penner]

Using lsusb -t I get this feedback:

pi at raspberrypi ~ $ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
|__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
|__ Port 3: Dev 11, If 0, Class=vend., Driver=usbfs, 480M

I do notice how sane-find-scanner returns the bus/port data:

sudo 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.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan]) at
libusb:001:011
found USB scanner (vendor=0x0424, product=0xec00) at libusb:001:003

How would I use the libusb:001:011 identifier for the 9000f with scanimage?
If I try to tell scanimage to use one of those with the -device option, I
get this feedback:

pi at raspberrypi ~/sambashare $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib scanimage
--progress --verbose --batch --format=tiff --resolution=2400 -x 240 -y 135 *-d
libusb:001:011* --batch-start=11 > /home/pi/sambashare/myco%5d.tif
scanimage:* open of device libusb:001:011 failed: Invalid argument*
pi at raspberrypi ~/sambashare $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib scanimage
--progress --verbose --batch --format=tiff --resolution=2400 -x 240 -y 135 *-d
libusb:001:003* --batch-start=11 > /home/pi/sambashare/myco%5d.tif
scanimage:* open of device libusb:001:003 failed: Invalid argument*


- Joel

On Thu, Feb 20, 2014 at 5:33 PM, Olaf Meeuwissen
wrote:

>
> m. allan noah writes:
>
> > Some scanners have a serial number which can be seen by software. Some
> > sane backends use that serial as part of the device name. If your
> > scanners or the pixma backend don't support this, you will have to
> > find another way. Perhaps forcing the device name using udev or
> > whatever Linux is using this week.
>
> It just so happens that I've been looking at this about three weeks ago
> for a third party backend.  The scanners this backend should support
> have varying degrees of serial number support:
>
>  - not at all
>  - at the USB level only
>  - at the device protocol level only
>  - at both USB and device protocol level only
>
> I wanted/needed to be able to support all of the above, even the case
> where there is *no* serial number support at all.  With libusb-1.0 this
> is possible (at least on a recent enough Linux system) using the
>
>   libusb_get_bus_number()
>
> and
>
>   libusb_get_device_address()
>
> API.  When using libusb-1.0.12 or later you can also use
>
>   libusb_get_port_number()
>
> With a USB device hooked up to my machine, lsusb -t shows:
>
>   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
>   |__ Port 5: Dev 26, If 0, Class=Vendor Specific Class, Driver=, 480M
>
> Inserting a USB hub between the two, this changes to:
>
>   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
>   |__ Port 5: Dev 27, If 0, Class=Hub, Driver=hub/4p, 480M
>   |__ Port 4: Dev 28, If 0, Class=Vendor Specific Class, Driver=,
> 480M
>
> The device number (Dev) changes every time you reconnect the USB cable
> (or power cycle the device) but bus and port numbers don't change (but
> they might upon a reboot).
>
> > On Thu, Feb 20, 2014 at 1:47 AM, Joel Penner 
> wrote:
> >> I have two CanoScan 9000f scanners that I'm using for a time-lapse
> scanner
> >> photography project. How do I tell two instances of scanimage to each
> use
> >> their own 9000f scanner on the same raspberry pi using the -device flag?
> >> Using sane-find-scanner to find an ID of connected scanners generates
> the
> >> same ID for both, non-surprisingly.
>
> 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
>
> --
> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20140222/596a953b/attachment.html>

[sane-devel] Using scanimage's -device option to specify one of two identical scanners

[Joel Penner]

With both 9000f scanners connected, it's:

pi at raspberrypi ~/sambashare2 $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib
scanimage -L
device `pixma:04A91908' is a CANON Canoscan 9000F multi-function peripheral
device `pixma:04A91908' is a CANON Canoscan 9000F multi-function peripheral
pi at raspberrypi ~/sambashare2 $



On Sun, Feb 23, 2014 at 7:01 AM, m. allan noah  wrote:

> What is the output of scanimage -L
>
> allan
>
> On Sun, Feb 23, 2014 at 12:15 AM, Joel Penner 
> wrote:
> > Using lsusb -t I get this feedback:
> >
> > pi at raspberrypi ~ $ lsusb -t
> > /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
> > |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
> > |__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
> > |__ Port 3: Dev 11, If 0, Class=vend., Driver=usbfs, 480M
> >
> > I do notice how sane-find-scanner returns the bus/port data:
> >
> > sudo 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.
> >   # Also you need support for SCSI Generic (sg) in your operating system.
> >   # If using Linux, try "modprobe sg".
> >
> > found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan]) at
> > libusb:001:011
> > found USB scanner (vendor=0x0424, product=0xec00) at libusb:001:003
> >
> > How would I use the libusb:001:011 identifier for the 9000f with
> scanimage?
> > If I try to tell scanimage to use one of those with the -device option, I
> > get this feedback:
> >
> > pi at raspberrypi ~/sambashare $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib
> scanimage
> > --progress --verbose --batch --format=tiff --resolution=2400 -x 240 -y
> 135
> > -d libusb:001:011 --batch-start=11 > /home/pi/sambashare/myco%5d.tif
> > scanimage: open of device libusb:001:011 failed: Invalid argument
> > pi at raspberrypi ~/sambashare $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib
> scanimage
> > --progress --verbose --batch --format=tiff --resolution=2400 -x 240 -y
> 135
> > -d libusb:001:003 --batch-start=11 > /home/pi/sambashare/myco%5d.tif
> > scanimage: open of device libusb:001:003 failed: Invalid argument
> >
> >
> > - Joel
> >
> > On Thu, Feb 20, 2014 at 5:33 PM, Olaf Meeuwissen <
> olaf.meeuwissen at avasys.jp>
> > wrote:
> >>
> >>
> >> m. allan noah writes:
> >>
> >> > Some scanners have a serial number which can be seen by software. Some
> >> > sane backends use that serial as part of the device name. If your
> >> > scanners or the pixma backend don't support this, you will have to
> >> > find another way. Perhaps forcing the device name using udev or
> >> > whatever Linux is using this week.
> >>
> >> It just so happens that I've been looking at this about three weeks ago
> >> for a third party backend.  The scanners this backend should support
> >> have varying degrees of serial number support:
> >>
> >>  - not at all
> >>  - at the USB level only
> >>  - at the device protocol level only
> >>  - at both USB and device protocol level only
> >>
> >> I wanted/needed to be able to support all of the above, even the case
> >> where there is *no* serial number support at all.  With libusb-1.0 this
> >> is possible (at least on a recent enough Linux system) using the
> >>
> >>   libusb_get_bus_number()
> >>
> >> and
> >>
> >>   libusb_get_device_address()
> >>
> >> API.  When using libusb-1.0.12 or later you can also use
> >>
> >>   libusb_get_port_number()
> >>
> >> With a USB device hooked up to my machine, lsusb -t shows:
> >>
> >>   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
> >>   |__ Port 5: Dev 26, If 0, Class=Vendor Specific Class, Driver=,
> 480M
> >>
> >> Inserting a USB hub between the two, this changes to:
> >>
> >>   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
> >>   |__ Port 5: Dev 27, If 0, Class=Hub, Driver=hub/4p, 480M
> >>   |__ Port 4: Dev 28, If 0, Class=Vendor Specific Class,
> Driver=,
> >> 4

[sane-devel] Using scanimage's -device option to specify one of two identical scanners

[Joel Penner]

Great clarification, it's very interesting stuff. Thanks a lot. I got
another pi to use with the second 9000f; other combinations of scanners on
a single pi should be more successful.

- Joel


On Sun, Feb 23, 2014 at 5:31 PM, Olaf Meeuwissen
wrote:

>
> Joel Penner writes:
>
> > With both 9000f scanners connected, it's:
> >
> > pi at raspberrypi ~/sambashare2 $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib
> > scanimage -L
> > device `pixma:04A91908' is a CANON Canoscan 9000F multi-function
> peripheral
> > device `pixma:04A91908' is a CANON Canoscan 9000F multi-function
> peripheral
> > pi at raspberrypi ~/sambashare2 $
>
> The "pixma:04A91908" bit is what you pass to scanimage's --device-name
> option.  This is then used by the pixma backend to decide which device
> it should use.  Unfortunately, this backend is not (yet) able to tell
> the two devices apart.
>
> >> On Sun, Feb 23, 2014 at 12:15 AM, Joel Penner 
> >> wrote:
> >> > Using lsusb -t I get this feedback:
> >> >
> >> > pi at raspberrypi ~ $ lsusb -t
> >> > /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
> >> > |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/3p, 480M
> >> > |__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
> >> > |__ Port 3: Dev 11, If 0, Class=vend., Driver=usbfs, 480M
>
> So the USB layer has no problems telling your two devices apart.  One
> reason that many backends do not want to expose the Dev part of this
> output is that it changes every time you reconnect or power-cycle your
> scanner.  That leads to changing device names, something that confuses
> many users.  The pixma backend is one of those backends and it has opted
> to exposo a device name that does *not* changes across reconnections,
> power-cycling and system reboots.  It does so at the expense of not
> supporting two or more devices of the same make.
>
> >> > I do notice how sane-find-scanner returns the bus/port data:
> >> >
> >> > sudo sane-find-scanner
> >> > found USB scanner (vendor=0x04a9 [Canon], product=0x1908 [CanoScan])
> at
> >> > libusb:001:011
> >> > found USB scanner (vendor=0x0424, product=0xec00) at libusb:001:003
> >> >
> >> > How would I use the libusb:001:011 identifier for the 9000f with
> >> > scanimage?
>
> This would require changes to the pixma backend code.  It could for
> example add support for "pixma:libusb:001:011" style device name,
> possibly as aliases for "pixma:04A91908".  That way, user with only one
> device don't have to bother with the changing device names, but users
> like yourself with more than one would be able to pick one or the other
> with the libusb "alias".
>
> The drawback of this is that it would show twice as many device names as
> are connected.
>
> >> > If I try to tell scanimage to use one of those with the -device
> option, I
> >> > get this feedback:
> >> >
> >> > pi at raspberrypi ~/sambashare $ sudo LD_LIBRARY_PATH=/usr/lib/:/lib
> >> scanimage
> >> > --progress --verbose --batch --format=tiff --resolution=2400 -x 240 -y
> >> 135
> >> > -d libusb:001:011 --batch-start=11 >
> /home/pi/sambashare/myco%5d.tif
> >> > scanimage: open of device libusb:001:011 failed: Invalid argument
>
> This tells scanimage to look for a libusb SANE backend.  Such a backend
> does not exist so you get the invalid argument error.
>
> Hope this clarifies,
> --
> Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS CORPORATION
> FSF Associate Member #1962   Help support software freedom
>  http://www.fsf.org/jf?referrer=1962
>
> --
> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20140223/6507a002/attachment.html>

[sane-devel] Sane Problem Canoscan 5600F

[Joel Penner]

What were the results from modifying and testing the genesys backend to
fully support the 5600f?

Thanks,

Joel


On Thu, Mar 13, 2014 at 12:38 AM, Stef  wrote:

> On 06/03/2014 12:01, Rowan Liddane wrote:
>
>> xsane
>> [genesys] WARNING: Your scanner is not fully supported or at least
>> [genesys]  had only limited testing. Please be careful and
>> [genesys]  report any failure/success to
>> [genesys]  sane-devel at lists.alioth.debian.org. Please provide as
>> many
>> [genesys]  details as possible, e.g. the exact name of your
>> [genesys]  scanner and what does (not) work.
>>
>> Hi,
>> I added the Canon Canoscan 5600F to the rules file and got the messages
>> above.
>>
>> I also got a box that said "genesys :libusb:0011004 invalid arguement"
>>
>> Its is a great scanner if I can get it running. The Caon site does not
>> provide a Linux  driver for this scanner and I thought genesys migth pick
>> it up.
>>
>> Cheers
>>
>> Rowan
>>
>>
>>  Hello,
>
> I don't have this model, and it isn't close enough to other ones I
> have so I cannot finish support for it in the genesys backend. But if you
> want, I can help you modify and test the backend to fully support this
> GL847 based scanner.
>
> Regards,
> Stef
>
> --
> sane-devel mailing list: sane-devel at 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-request at lists.alioth.debian.org
>
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Hour/minute/second wildcards for scanimage file name?

[Joel Penner]

I am trying to use the --batch flag with a HP ScanJet 2200c. The batch
function doesn't work because scanimage tries to start the second scan
before the scanner head has fully gone back to its original position.
Because of this scanimage receives a busy signal while the head is
retracting and the batch scan operation stops. I was thinking of making a
simple scanimage + wait 10 seconds script to get around this limitation.
Are there date/time (hour/minute) wildcard characters for scanimage that I
could use to differentiate the files in this manually created batch?

Alternatively, is there a way to modify the plustek backend to wait for a
few seconds before trying to start the next scan?

Thanks,
Joel
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Hour/minute/second wildcards for scanimage file name? - ADDENDUM

[Joel Penner]

Hi all. I found out how to add a time stamp wildcard in a shell script, so
don't mind that part of my question. I still would be interested in knowing
how to fix the plustek backend.

- Joel
-- next part --
An HTML attachment was scrubbed...
URL: