[sane-devel] Canon LiDE 80 (2nd try)

[Pierre Willenbrock]

Hi Stefan,

(more text inline)

Stefan Lucke schrieb:
> On Tuesday 05 February 2008, Stefan Lucke wrote:
>> Hi,
>>
>> I've seen there is some progress on lide 90 and I want to step in and
>> like to ask if there could be done something for my LiDE 80 too.
>> I cloned the canon_lide_60_model entry
>>
>> -- scanimage with debug messages : --
>> [sanei_debug] Setting debug level of genesys to 255.
>> [genesys] SANE Genesys backend version 1.0 build 9 from sane-backends 1.0.18-cvs
>> [genesys] sane_init: authorize != null
>> [genesys] sane_init: little endian machine
>> [genesys] sane_init: reading config file `genesys.conf'
>> [genesys] sane_init: config file line 1: trying to attach `usb 0x04a9 0x2214'
> ..
>> [genesys_gl841] gl841_bulk_write_register (elems = 104)
>> [genesys_gl841] reg[0x01] = 0xa0
>> [genesys_gl841] reg[0x02] = 0x38
>> [genesys_gl841] reg[0x03] = 0x5f
>> [genesys_gl841] reg[0x04] = 0x10
>> [genesys_gl841] reg[0x05] = 0x40
>> [genesys_gl841] reg[0x06] = 0x18
>>
>> -- I modified this, debug message is written before ..bulk_write..() . --
>>
>> [genesys_gl841] gl841_bulk_write_register: failed while writing command: Invalid argument
>> scanimage: open of device genesys:libusb:001:017 failed: Invalid argument
>> [genesys] sane_exit: start
>> [genesys] sane_exit: exit
> 
> Some further info:
> I placed some win98 logfiles at http://lucke.in-berlin.de/lide-80/ .
> 
> During my search in the list history, I found a test program in this mail:
> http://lists.alioth.debian.org/pipermail/sane-devel/2006-October/017930.html

I must admit, i totally forgot about that.. lectures where starting at
that time at my university.

> 
> Using the following stripped down version of usbsnoop-300dpi_color.c,
> helped to get rid of the sudden disconnect from below.
> -- snip --
> set_write_register(0x6b, 0x0c);
> set_write_register(0x06, 0x10);

first, try if either of the following is enough to get past writing
register 0x06:
set_write_register(0x6b, 0x08);
set_write_register(0x6b, 0x04);

put that write to 0x6b into gl841_init, before the /* Write initial
registers */, and make sure the other places where 0x6b is written
preserve the needed bits. That may get scanimage to o further with a
freshly plugged in scanner.

Regards,
  Pierre

> -- snip --
> 
> Both lines are required!
> (Note: disconnect has timestamp earlier than USBDEVFS message).
> 
> Even with turned off LED and some motor sound (movement in the wrong
> direction ??), scanimage produced some pnm files.
> 
> To be continued, but I really need some help, as I've no idea 
> about scanner hardware.
> 
>> -- dmesg output (kernel 2.6.23.13): --
>> [ 5298.424302] usb 1-7: new high speed USB device using ehci_hcd and address 17
>> [ 5298.480244] usb 1-7: OK: device descriptor read/64, error 0, mp 64 (0 0)
>> [ 5298.491202] usb 1-7: configuration #1 chosen from 1 choice
>> [ 5312.035169] usb 1-7: usbfs: USBDEVFS_CONTROL failed cmd scanimage rqt 64 rq 4 len 2 ret -71
>> [ 5312.035148] usb 1-7: USB disconnect, address 17
>> [ 5312.188163] usb 1-7: new high speed USB device using ehci_hcd and address 18
>> [ 5312.244105] usb 1-7: OK: device descriptor read/64, error 0, mp 64 (0 0)
>> [ 5312.255079] usb 1-7: configuration #1 chosen from 1 choice
>