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

2008-02-13 Thread Reinhard Biegel
On Tuesday, 12. February 2008, Stefan Lucke wrote:
  Register 0x6b is very different between GL841/2 and GL843. But the
  documentation around the pins controlled with 0x6b is a bit lacking.

 So we need to write reserved I/O bits, (0x6b) need to write to undefined
 gamma addresses (0x5b/5c - 0x0c00). Thats really magic. Both areas
 are defined for GL843 but not for GL841/2.

Indeed, very strange.

@Gerhard Jaeger: Were did you get the bcdValues from? Can we trust them?

Is there a possibility that there is a GL841b revision of the chip with 
lower bcdValue but being derived from GL843?

Regards,
Reinhard



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

2008-02-12 Thread Reinhard Biegel
On Monday, 11. February 2008, Pierre Willenbrock wrote:
 Did someone post the bcdDevice value of a LiDE 80? GL841 goes up to
 3.0.5, as someone said, and GL842 begins with 3.0.6

bcdDevice of mine is 0302.

Reinhard



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

2008-02-11 Thread Reinhard Biegel
  You are talking about writes like:

 I guess YES.

Yes, I do.

 Now I found the right one AND the right time: Before doing the reset ;-).

 So now I've the initial motor movement with LED blinking and a scan
 movement with green LED.

 But no (strange) data arrives.


I tried your diff, but I get the known 'invalid argument error'.

Regards,
Reinhard

Debug output of scanimage:

[genesys_gl841] gl841_init
[genesys_gl841] gl841_init_registers
[genesys_gl841] gl841_setup_sensor
[genesys_gl841] gl841_init_registers complete
[genesys] sanei_genesys_write_register (0x60, 0x06) completed
[genesys] sanei_genesys_write_register (0x61, 0x13) completed
[genesys] sanei_genesys_write_register (0x62, 0x55) completed
[genesys] sanei_genesys_write_register (0x63, 0x02) completed
[genesys] sanei_genesys_write_register (0x64, 0x34) completed
[genesys] sanei_genesys_write_register (0x65, 0x04) completed
[genesys_gl841] gl841_set_buffer_address_gamma: setting address to 0x0c000
[genesys] sanei_genesys_write_register (0x5c, 0x00) completed
[genesys] sanei_genesys_write_register (0x5b, 0x0c) completed
[genesys_gl841] gl841_set_buffer_address_gamma: completed
[genesys_gl841] gl841_bulk_write_data_gamma writing 128 bytes
[genesys_gl841] genesys_bulk_write_data:gamma wrote 128 bytes, 0 remaining
[genesys_gl841] genesys_bulk_write_data_gamma: completed
[genesys] sanei_genesys_write_register (0x0e, 0x00) completed
[genesys] sanei_genesys_write_register (0x6b, 0x0c) completed
[genesys] sanei_genesys_write_register (0x6e, 0x6d) completed
[genesys] sanei_genesys_write_register (0x6c, 0x00) completed
[genesys_gl841] gl841_bulk_write_register (elems = 104)
[genesys_gl841] reg[0x01] = 0xa0
[genesys_gl841] reg[0x02] = 0x38
...
[genesys_gl841] reg[0x6b] = 0x02
[genesys_gl841] reg[0x6e] = 0x6d
[genesys_gl841] gl841_bulk_write_register: failed while writing command: 
Invalid argument
scanimage: open of device genesys:libusb:001:010 failed: Invalid argument




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

2008-02-11 Thread Reinhard Biegel
Am Monday, 11. February 2008 schrieb Stefan Lucke:
  ...
  [genesys_gl841] reg[0x6b] = 0x02
  [genesys_gl841] reg[0x6e] = 0x6d
  [genesys_gl841] gl841_bulk_write_register: failed while writing command:
  Invalid argument
  scanimage: open of device genesys:libusb:001:010 failed: Invalid argument

 At that moment, I guess you'll see messages like:
   new high speed USB device using ehci_hcd and address nn
 via dmesg.

Hi,
Yes, thats right.

Changing the write to reg 0x6b from 0x0c to 0x08 fixes that. 
Scanner is producing noisy image now.

Do I see right that the two bits (0x04 and 0x08 of register 0x6b) affect two 
pins which are marked as 'reserved' in the datasheet? They are only 
documented for GL843.

After scanning I have to replug the scanner, otherwise I get an error message 
telling me the document feeder is jammed. Curiously, if I set 
SANE_DEBUG_GENESYS, there comes up another error about a failed bulk_write.

Also I noticed that the LED isn't continuously illuminated. In one half it's 
continuous, but in the other there are small gaps (about 1mm) with about 4mm 
spacing between. In the middle there are a few with bigger spacing.

 Which way is your scanner connected ?
Directly to the computer, no hubs.

Regards,
Reinhard



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

2008-02-06 Thread Reinhard Biegel

Am Wednesday, 6. February 2008 schrieb Stefan Lucke:
 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.

Hi,

I played around some time ago with the LiDE 80. IIRC I got the motor working 
by adjusting its base resolution (2400 instead of 1200 or something). But I'm 
not shure it it was the only thing.

Regards,
Reinhard Biegel



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

2008-02-06 Thread Reinhard Biegel
Am Wednesday, 6. February 2008 schrieb Stefan Lucke:

 Do you have some old sources of your changes ?

 Playing with motor settings doesn't make a difference (at the moment).

Sorry, I trashed the sources because I messed something up and then nothing 
was working any more. I planed to start over again but had no time to do so.

As far as I remember I simply set the registers as it is done by the windows 
driver after pluggin in the scanner and then I replaced them step by step 
with existing sane calls.

Ohi just remember there was something that had to be called at any price 
but didn't find any documentation about that. I'm going to look for that in 
my logs.

Regards,
Reinhard