Dear Mr. Pierre,
I have problem with CanoScan LiDE 100 to work with ubuntu. The reason behind
my worry is I have purchased these scanners( more than 5000 pieces) for
school at very remote places but found not working. I got your references
from the community and would appeal to help me.
Pls he
guillaume.gastebois at free.fr schrieb:
> Hello,
>
> I'm back with my LiDE 90. No more significant result since month. I don't
> know where to find.
> Just a little question. I see in windows snoop that inversion bit is set in
> frontend, not in sane.
> Is it possible that this inversion has an
Hello,
I'm back with my LiDE 90. No more significant result since month. I don't know
where to find.
Just a little question. I see in windows snoop that inversion bit is set in
frontend, not in sane.
Is it possible that this inversion has an effect on calibration and scanning
(different full sc
guillaume.gastebois at free.fr schrieb:
> Hello,
>
> It seems that in Windows snoop calibration of LiDE 90 is done with
> half CCD even if scanning is in full sensor resolution.
> Is it so in sane ?
>
> If not, is it usefull to implement it ? Where to do that ?
To be on the safe side, all calib
Hello,
It seems that in Windows snoop calibration of LiDE 90 is done with half CCD
even if scanning is in full sensor resolution.
Is it so in sane ?
If not, is it usefull to implement it ? Where to do that ?
Regards
Guillaume
Hi,
guillaume.gastebois at free.fr schrieb:
> Hello,
> Thank you for answer Pierre.
> Some questions again !
>
>> Hi Guillaume,
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> I'm back with my LiDE 90 !
>>>
>>> I see in my windows logs the following sequence for gpios (reg 0x6C) :
>>> 02
>>> 1
Hello,
Thank you for answer Pierre.
Some questions again !
>Hi Guillaume,
>Guillaume Gastebois schrieb:
>> Hello,
>>
>> I'm back with my LiDE 90 !
>>
>> I see in my windows logs the following sequence for gpios (reg 0x6C) :
>> 02
>> 12
>> 0e
>> 1a
>> 0a
>> 0e/3e (3e for half ccd log) (seems to b
Hi Guillaume,
Guillaume Gastebois schrieb:
> Hello,
>
> I'm back with my LiDE 90 !
>
> I see in my windows logs the following sequence for gpios (reg 0x6C) :
> 02
> 12
> 0e
> 1a
> 0a
> 0e/3e (3e for half ccd log) (seems to be scanning moment)
> 0e
> 0a
> 0e/3e (3e for half ccd log)
> 02
>
> With
Hello,
I'm back with my LiDE 90 !
I see in my windows logs the following sequence for gpios (reg 0x6C) :
02
12
0e
1a
0a
0e/3e (3e for half ccd log) (seems to be scanning moment)
0e
0a
0e/3e (3e for half ccd log)
02
With tests I identifies GPIO11 as home switch (with 1 scanner doesn't see home
p
> Hello,
>
> OK, if i understand test values you proposed gives :
>
> 0xf f0 3f
> bit of 0x79! 0x78 !0x77! 0x79
> 0 1 2 3 4 5 6 7!0 1 2 3 4 5 6 7!0 1!0 1 2 3 4 5 6...
> 1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1
> ___
>
Hello,
OK, if i understand test values you proposed gives :
0xf f0 3f
bit of 0x79! 0x78 !0x77! 0x79
0 1 2 3 4 5 6 7!0 1 2 3 4 5 6 7!0 1!0 1 2 3 4 5 6...
1 1 1 1 1 1 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1
___
|__|
Guillaume Gastebois schrieb:
> Hello,
>
> No progress on 2400dpi. DPIHW is 2400 and dpiset 600 for a 300dpi scan.
> Don't know where to look yet for that problem !
I'd try to get a log from a 2400dpi scan from windows and compare.
> about byte nibbles modifying reg_0x79 from 0x3f to 0x3e (very f
Hello,
No progress on 2400dpi. DPIHW is 2400 and dpiset 600 for a 300dpi scan.
Don't know where to look yet for that problem !
about byte nibbles modifying reg_0x79 from 0x3f to 0x3e (very few
contrasted image) or 0x40(black image) gives me bad images !!!
What is effect of this register on clk3
Guillaume Gastebois schrieb:
> Hello,
>
> I remember that LiDE 90 is a 2400DPI scanner. And I did nothing in code to
> port
> that. I backend ready for 2400dpi (I think so regarding portion of code) ?
I am not sure, as there could not happen any testing. But in theory, it
should work. In the fu
Hello,
I remember that LiDE 90 is a 2400DPI scanner. And I did nothing in code to port
that. I backend ready for 2400dpi (I think so regarding portion of code) ?
I write 2400 dpi in genesys_sensor for lide 90. But how to know pixel number for
CCD sensor ?
After writing 2400 dpi in sensor, I get
Hi,
Guillaume Gastebois schrieb:
> Hello,
>
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> Me again !
>>>
>>> I'm trying to find what are GPIO14,13,12 and 11 for.
>>>
>>> I find GPIO11=home switch and must be 0.
>>> I thought I found GPIO14 was half CCD but by adding :
>>> /* gpio part. here:
Hello,
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> Me again !
>>
>> I'm trying to find what are GPIO14,13,12 and 11 for.
>>
>> I find GPIO11=home switch and must be 0.
>> I thought I found GPIO14 was half CCD but by adding :
>> /* gpio part. here: for canon lide 90 */
>> if (dev->model->gpo_typ
Guillaume Gastebois schrieb:
> Hello,
>
> Me again !
>
> I'm trying to find what are GPIO14,13,12 and 11 for.
>
> I find GPIO11=home switch and must be 0.
> I thought I found GPIO14 was half CCD but by adding :
> /* gpio part. here: for canon lide 90 */
> if (dev->model->gpo_type == GPO_CANONLID
Guillaume Gastebois schrieb:
> Hello,
>
> Me again !
>
> I'm trying to find what are GPIO14,13,12 and 11 for.
>
> I find GPIO11=home switch and must be 0.
> I thought I found GPIO14 was half CCD but by adding :
> /* gpio part. here: for canon lide 90 */
> if (dev->model->gpo_type == GPO_CANONLID
Hello,
Me again !
I'm trying to find what are GPIO14,13,12 and 11 for.
I find GPIO11=home switch and must be 0.
I thought I found GPIO14 was half CCD but by adding :
/* gpio part. here: for canon lide 90 */
if (dev->model->gpo_type == GPO_CANONLIDE90)
{
r = sanei_genesys_get_address (reg, 0x6c);
Guillaume Gastebois schrieb:
> Hello,
>
> I see in genesys_gl841.c line 2503 :
>
> /* gpio part. here: for canon lide 35 */
>
> r = sanei_genesys_get_address (reg, 0x6c);
> if (half_ccd)
> r->value &= ~0x80;
> else
> r->value |= 0x80;
>
> Does it mean that for LiDE 35 GP
Hello,
I see in genesys_gl841.c line 2503 :
/* gpio part. here: for canon lide 35 */
r = sanei_genesys_get_address (reg, 0x6c);
if (half_ccd)
r->value &= ~0x80;
else
r->value |= 0x80;
Does it mean that for LiDE 35 GPIO16 is half CCD IO ? Because in LiDE 90, I
identif
> -Urspr?ngliche Nachricht-
> Von: "Kent Whitten"
> Gesendet: 27.11.07 21:22:03
> An: Ralf Haueisen
> Betreff: Sorry I can't hit the sane lis from here.
>
> I caught these on the LiDE 90 with a catc analyzer. They are set a bunch of
> times, but always to the same values.
>
> Kent
>
23 matches
Mail list logo
