plustek: Canon D646Uex
Subject:
Re: Canon D646Uex
From:
Tim Thomson ####@####.####
Date:
3 Feb 2003 20:45:29 -0000
Message-Id: <20030203203047.GB10768@ripcord.co.nz>
Cheers for the reply.
On Mon, Feb 03, 2003 at 07:10:12PM +0100, Jaeger, Gerhard wrote:
> On Montag, 3. Februar 2003 01:31, Tim Thomson wrote:
> > I haven't seen any sane backend that supports this yet, and am wondering
> > if anyone has made any progress getting it to work?
>
> there's only the source-forge stuff available so far...
Cool, should I post there, or do they hang out here as well? Their list
has been quiter the last couple of months.
> > How hard would it be to get this CCD scanner going, as opposed to a CIS
> > one? Is there much more involved?
>
> Well the Lide20 and also the 650 is supported although the picture
> quality is not that good...
Is the Lide20's quality going to get much better (ie, are people working
on it, or have they got stuck?). I need to figure out whether to try and
upgrade by tonight :)
> What can you do:
> - Download SANE-1.0.10 sources
> - check file backend/plustek-devs.c for the canoscan 650 entries
> esp. in the "Settings" Table. Duplicate the entry and simply
> replace product id by the one of the 646.
> - recompile and install SANE
>
> This simply uses the settings of the 650, it might work...
Heh, I actually tried this yesterday, with no luck. I just replaced all
the 2206's with 220B's. Sound OK, or should I actually add new entries?
(did that in both plustek-devs.c and plustek-usb.c).
After setting the debug level to 10, I get this with a scanimage -L
...
[plustek] usbDev_open(auto,)
[plustek] Autodetection...
[plustek] Found device at >/dev/usbscanner0<
[plustek] Device >/dev/usbscanner< ignoring
[plustek] Device >/dev/usb/scanner0< ignoring
[plustek] Vendor ID=0x04A9, Product ID=0x220B
[plustek] usbio_DetectLM983x
[plustek] UIO error
[plustek] This is not a LM9831 or LM9832 chip based scanner.
[plustek] open failed: -1
[plustek] sane_get_devices (0xbffff8b8, 0)
...
Bad news?
Or is it just not talking the way it expects a 650 to talk?
I tried this also with the 630u driver in 1.0.9, with no luck either.
It thought it found it, but I don't think it has autodetection code, so
just saw the product ID's matched. Trying to scan did not work at all.
The canonscanner.sf.net people have a ct program on their cvs, which has
a version for the 646U, but it only gives me this:
# ./canon-test-D646U
Starting conversation with the scanner
sizeof(init_data1)=2552
Looking at the examples, there should be more. I haven't looked at the
source yet, to see where it is bombing out.
Thanks for any help,
Tim.
