[sane-devel] New Epson Perfection 1650 scanner

khk@khk.net khk@khk.net
Fri, 13 Sep 2002 10:09:06 -0400 (EDT)

First let me say this: Thank you for providing all the information
I usually have to ask for :-)

> I am new to SANE, so please excuse some of my ignorance.
> I have a new Epson Perfection 1650 scanner and I am trying to use it
> with a 2.4.19 kernel and the sane-backends-1.08 package. I have
> uncommented the line: "usb /dev/usb/scanner0" line in
> /usr/local/etc/sane.d/epson.conf. I have also included USB scanner
> support as a kernel module.
> /usr/local/bin/sane-find-scanner reports:
> sane-find-scanner: found USB scanner (vendor = 0x04b8, product =
> 0x0110) at device /dev/usb/scanner0
> sane-find-scanner: found USB scanner (vendor = 0x04b8, product =
> 0x0110) at device /dev/usbscanner
> I have set permissions to 666 on /dev/usb/scanner0
> If I run /usr/local/bin/scanimage -L the program just hangs.
> /usr/local/bin/scanimage -d epson also hangs.
> The software that cane with the scanner is identified as applying  the
> the 1250/1650 series. This worries me as the 1250 is reported as  being
> unsupported.

The two models are totally different beasts. The 1650 is supported and
uses EPSON's ESC-I command set, whereas the 1250 uses the NS983x chip
with it's command set.

> Is there a problem with recently produced models of this scanner or
> should I go back to reading the documentation.

I am not aware of any problems, and usually the scanners get better
the longer they are on the market.

Do you have a second installation of Sane on your system (e.g. files
in /etc/sane.d or in /usr/lib/sane)? This can cause the problems you
are seeing.

Do you have link /dev/scanner to a USB device? If so,
then remove it.

Is the scanner connected via a USB hub? If so, then try to connect
it directly to the USB interface on your computer.

Do you have a different USB cable that you can try?

If this still does not help, then comment out (or remove)
all other backends in dll.conf.

If this still does not give you a working system, then it's time to
create a log file:
Type this in a terminal window:
xsane > /tmp/scan.log 2>&1

If this does not give you any output in the file /tmp/scan.log, then it's
not my problem :-) If you do see information in this file, please email
it to me.

Karl Heinz