plustek: Canon D646Uex
Subject:
Re: Canon D646Uex
From:
Gerhard Jaeger ####@####.####
Date:
5 Feb 2003 12:21:07 -0000
Message-Id: <200302051310.12363.gerhard@gjaeger.de>
Hi Tim,
On Montag, 3. Februar 2003 21:30, Tim Thomson wrote:
[SNIPSNAP]
> Cool, should I post there, or do they hang out here as well? Their list
> has been quiter the last couple of months.
I've no idea wether those guys are here or not, at least one them who cares
for the N1240U support is sometimes around...
[SNIPSNAP]
> > 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?
Seems so :-(
> Or is it just not talking the way it expects a 650 to talk?
No, it works at least at that stage with all LM983x devices (except the
LM9830)
>
> 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.
When looking closer at the D646 stuff you'll see in function init_engine()
that the usb logs shows up something like
14 CTL 40 04 85 00 - a9 bc 02 00
14 CTL c0 0c 84 0c - d1 bc 01 00
This looks to me like code for a GeneSysLogic USB-parallelport bridge...
Which means, that the 646 is like the 630u...
You might ask the maintainer there...
Good luck
Gerhard
