It is very probable that this scanner is relabeled and not a genuine
Epson, because it looks vry different to the others. It looks very cheap
for me.
Till
Karl Heinz Kremer wrote:
> This does not look good. Assuming that your Sane is working (and
> because you've got the other scanners to work, I think this is
> a safe assumption), this scanner does not "speak" ESC-I (the
> EPSON scanner control language).
>
> It does not even react correctly to the "Reset" command (ESC-@).
> So it's definitely not supported by the EPSON backend. I still
> think that it's very likely a NS983x based scanner that could
> be supported by the Plustek backend.
>
> Does anybody know a good test that does not require to open
> the cover and will detect an NS983x chip.
>
> Karl Heinz
>
>
> On Tue, Aug 20, 2002 at 03:07:58AM +0200, Till Kamppeter wrote:
>
>>Here is the contents of "scan.log":
>>
>>[sanei_debug] Setting debug level of epson to 128.
>>[epson] sane_init: sane-backends 1.0.8
>>[epson] sane_init, >usb /dev/usb/scanner0<
>>[epson] sane_init, >usb /dev/usb/scanner0<
>>[epson] attach(usb /dev/usb/scanner0)
>>[epson] SANE Epson Backend v0.2.21 - 2002-04-22
>>[epson] attach(usb /dev/usb/scanner0)
>>[epson] attach: opening usb /dev/usb/scanner0
>>[epson] send buf, size = 2
>>[epson] buf[0] 1b .
>>[epson] buf[1] 40 @
>>[epson] error in receive - status = 5
>>[epson] receive buf, expected = 1, got = -1
>>[epson] get_identity_information()
>>[epson] send buf, size = 2
>>[epson] buf[0] 1b .
>>[epson] buf[1] 49 I
>>[epson] ident failed
>>[epson] sane_get_devices()
>>
>>It took around five minutes until it came out, but than all came out at
>>once. Then, perhaps 10 seconds later xsane showed the window telling
>>that it didn't find any device.
>>
>>My /etc/sane.d/dll.conf contains only
>>
>>net
>>epson
>>
>>My /etc/sane.d/epson.conf
>>
>>usb /dev/usb/scanner0
>>
>> Till
>>
>>
>>Karl Heinz Kremer wrote:
>>
>>>YOu can try to get some debugging output:
>>>
>>>export SANE_DEBUG_EPSON=128
>>>
>>>Then run your frontend and redirect the output:
>>>xsane > /tmp/scan.log 2>&1
>>>
>>>This should tell us if the scanner does actually communicate with
>>>the backend.
>>>
>>>BTW: the desc files in doc/description are only used to generate
>>>the "Supported Scanners" page at www.mostang.com.
>>>
>>>Karl Heinz
>>>
>>>
>>>On Tue, Aug 20, 2002 at 02:02:09AM +0200, Till Kamppeter wrote:
>>>
>>>
>>>>When I use the "epson" backend for the Perfection 660, after some
>>>>minutes of waiting I get
>>>>
>>>> [ epson ] error in receive - status = 5
>>>> [ epson ] ident failed
>>>>
>>>>on the console from which I have started "xsane".
>>>>
>>>>I have already added the new models to doc/description/epson.desc and
>>>>recompiled sane-backends. Are other modifications needed?
>>>>
>>>> Till
>>>>
>>>>
>>>>Karl Heinz Kremer wrote:
>>>>
>>>>
>>>>>On Mon, Aug 19, 2002 at 10:56:01PM +0200, Till Kamppeter wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Has anyone any idea how to get the Perfection 660 working? Does it need
>>>>>>any parameters in /etc/sane.d/epson.conf? Is it a relabeled scanner
>>>>>>form another manufacturer, so that it scans with another driver? Or is
>>>>>>it an absolute "Paperweight", a "winscanner".
>>>>>
>>>>>
>>>>>Try the Plustek backend. It is based on the Perfection 1250, which also
>>>>>is supported by the Plustek backend.
>>>>>
>>>>>Karl Heinz
>>>>>
>>>>
>>>>
>>
>
