Hi all,

> That not withstanding, the snapscan backend sources show that a
> fair bit of the structure of the INQUIRY command's reply is already
> known. This is the command I would expect to show different replies
> for both models.

They do, but up to now I only have the data of three different 
scanners. The 2480/2580 can send more inquiry data than normally 
requested by the snapscan backend. The backend ususally requests 120 
bytes, the epson windows driver requests 138 bytes. I suspect that 
the value to look at is at offset 137. I've attached a few dumps of 
inquiry data from a 2480 and a 2580.

I'll add some code to request the additional inquiry data to the 
snapscan backend. If some people volunteer for tests we can get a 
more solid base for the distinction.

> The backend checks (via that evil binary-only library :-() with the
> hardware if a download is necessary and only downloads if
> necessary. If you power-cycle your scanner, you'll find that it
> will take some time even with the epkowa backend before you can use
> the scanner.

The snapscan backend does the same thing. However, the delay Julien is 
referring to results from the test_unit_ready/request_sense command 
after the firmware upload. Some Epson scanners report DEVICE_BUSY 
with some unusual large timeouts. I guess that the epkowa backend 
limits or ignores this value.

/Oliver
-------------- next part --------------
 2580 before firmwar upload
 00: 06 00 02 02 49 00 00 00 45 50 53 4F 4E 20 20 20   ....I...EPSON
 10: 45 50 53 4F 4E 20 53 63 61 6E 6E 65 72 20 20 20   EPSON Scanner
 20: 30 31 31 30 20 00 00 00 02 21 00 00 00 00 00 00   0110 ....!......
 30: 04 B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00   .260..............
 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 60: 54 75 65 20 46 65 62 20 32 35 20 32 30 30 33 20   Tue Feb 25 2003
 70: 30 39 3A 35 38 00 00 00 00 00 00 00               09:58.......

 2580 after firmware upload:
 00: 06 00 02 02 49 00 00 00 45 50 53 4F 4E 20 20 20   ....I...EPSON
 10: 45 50 53 4F 4E 20 53 63 61 6E 6E 65 72 31 20 20   EPSON Scanner1
 20: 31 2E 31 34 20 BD 40 48 00 00 29 B8 29 B8 00 00   1.14 275@H..)270)270..
 30: 09 60 00 01 15 17 00 00 00 00 00 00 00 00 00 00   .`..............
 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 60: 46 72 69 20 41 70 72 20 20 32 20 32 30 30 34 20   Fri Apr  2 2004
 70: 31 35 3A 34 37 00 00 00 00 00 00 80 FA 80 8F 93   15:47......?372?217?
 80: 97 00 00 00 00 00 00 00 00 2F 01                  ?......../.
 
 same 2580, after shading / image data
 00: 06 00 02 02 49 00 00 00 45 50 53 4F 4E 20 20 20   ....I...EPSON
 10: 45 50 53 4F 4E 20 53 63 61 6E 6E 65 72 31 20 20   EPSON Scanner1
 20: 31 2E 31 34 20 BD 40 48 00 00 02 7C 02 7C 03 6F   1.14 275@H...|.|.o
 30: 09 60 00 01 0A 05 00 00 00 00 00 00 00 00 00 00   .`..............
 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 60: 46 72 69 20 41 70 72 20 20 32 20 32 30 30 34 20   Fri Apr  2 2004
 70: 31 35 3A 34 37 00 00 00 00 00 00 ED E1 DA 87 8C   15:47......355341332??
 80: 8F 00 00 00 00 00 00 00 00 2F 01                  217......../.

 2480 after firmware upload
 00: 06 00 02 02 49 00 00 00 45 50 53 4F 4E 20 20 20   ....I...EPSON
 10: 45 50 53 4F 4E 20 53 63 61 6E 6E 65 72 31 20 20   EPSON Scanner1
 20: 31 2E 31 34 20 BD 40 48 00 00 02 7C 02 7C 03 6F   1.14 275@H...|.|.o
 30: 09 60 00 01 0A 05 00 00 00 00 00 00 00 00 00 00   .`..............
 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   ................
 60: 46 72 69 20 41 70 72 20 20 32 20 32 30 30 34 20   Fri Apr  2 2004
 70: 31 35 3A 34 37 00 00 00 00 00 00 F1 E2 DE 82 88   15:47......361342336??
 80: 8B 00 00 00 00 00 00 00 00 07 01                  ?..........
From [email protected]  Mon Aug 15 17:48:16 2005
From: [email protected] (Henning Meier-Geinitz)
Date: Mon Aug 15 17:51:04 2005
Subject: [sane-devel] Re: Getting Mustek 1200 UB Plus scanner working
In-Reply-To: <[email protected]>
References: <[email protected]>
Message-ID: <[email protected]>

Hi,

On Sun, Aug 14, 2005 at 04:45:18PM -0400, Martin wrote:
> I copied the firmware file to "/opt/gt68xx/sbfw.usb"
> and edited the file "gt68xx.conf"

Ok.

> ----------------
> # Mustek ScanExpress 1200 UB Plus:
> override "mustek-scanexpress-1200-ub-plus"
> firmware "/opt/gt68xx/SBfw.usb"
> ----------------

First, above of that there must be "usb 0x05d8 0x4002".

Second, mind the capitalization of the firmware (SBfw.usb in config
file, sbfw.usb in directory). Only the latest SANE version will ignore
the case.

Third: Is the scanner detected by sane-find-scanner? If not, either
your kernel has no USB support, /proc/bus/usb is not mounted or SANE
is build without libusb support.

> and copied it to "cp gt68xx.conf /etc/sane.d/"

gt68xx.conf should alread exist in /etc/sane.d/ if you use SANE from
your distribution.

> and then ran "/usr/bin/sane-find-scanner -v"
> 
> but my scanner was not found.

See above. This is most probably not a SANE problem because
sane-find-scanner just asks the kernel about the USB devices.

> 1) What dev port does the system look at to find my scanner, and, do I have 
> to mount it?

SANE uses libusb and that library looks at all USB devices connected
to the system. Devices are usually located in /proc/bus/usb/ . This
file system must be mounted (see man sane-usb).

> 2) From some other reading I did, does a module need to be loaded, such as, 
> (or something similar)?
> 
> insmod /lib/modules/2.4.20-31.9/kernel/drivers/usb/scanner.o vendor=0x055f 
> product=0x0006

The scanner module is not needed anymore. You just need kernel USB
support.

What's the output of "cat /proc/bus/usb/devices" and
"sane-find-scanner -v -v"?

Bye,
  Henning

Reply via email to