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,
> On Thu, Jul 03, 2008 at 02:52:22PM -0700, Donald Endres wrote:
>> >I got the attachment from
>> > http://lists.alioth.debian.org/pipermail/sane-devel/2008-March/021440.html
>> > ( is that the newest version ? ) and I will try to reproduce your
>> > work.
>
> Same for me. :-)
>
>
Hello,
>
> looks like:
>
> http://lists.alioth.debian.org/pipermail/sane-devel/2007-November/020199.html
>
> was the last attempt to get:
>
> http://www.sane-project.org/unsupported/canon-lide-90.html
>
> to work.
>
>
> I have a disposable one to play with... Can anyone suggest a plan of
>
/lide90_snoop/lide90_2400dpi_216x7.c
I don't see big differences....
> 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 !
&
Hello,
I work on, but don't know when It'll be good working.
> I want to ask if anyone can tell me if there is any hope to have
> support in sane for this model of scanner. Thanks in advance.
>
> 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
___
|__|
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
Hello,
In genesys backend, we can find :
typedef struct
{
u_int8_t reg[4];
u_int8_t sign[3];
u_int8_t offset[3];
u_int8_t gain[3];
u_int8_t reg2[3];
} Genesys_Frontend;
but in WM8199 regs don't have the same name.
For me registers addresses are :
reg[0]=0x01,reg[1]=0x02,reg[2]=0
(don't know how to determine)
SANE_Int power_mode_count; (don't know how to determine)
Genesys_Motor_Slope slopes[2][3]; (don't know how to determine)
} Genesys_Motor;
>Guillaume Gastebois schrieb:
>> Hello,
>>
>> I remember that LiDE 90 is a 2400DPI sca
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
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 :
>&
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);
Hello,
>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 &=
Hello again,
By writing 0x6c=0x12 I have no more power-up problem and pressing
buttons have no more effect on stopping head. Oufff
I tryed with 0x1a=24 and 0x16=02 : black image.
Remaining problem : nibbles and calibration.
Regards.
Guillaume
Guillaume Gastebois a ?crit :
> He
Hello,
Today : regression
I tryed to remove lide 35 gpio sequence and to write 0x6b=0x6b & 0x03.
The result was : the motor try to move the head to home (but head is
still home position). When I press a button, the scanner make a scan and
... don't stop at the end. I see that pressing a b
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
Hello,
I write again about LiDE 90 because I had no answers since my last mail.
Does people who test my patch have results...
Please see my last mail. I did any progress since it.
Regards
Guillaume
Hello,
Selon Pierre Willenbrock :
> Guillaume Gastebois schrieb:
>> > Hello,
>> >
>> > Yesterday I added CCD_CANONLIDE90 in genesys.c. I did two successive scans
>> > (result on http://ggastebois.free.fr/lide90_snoop/25_test1.zip).
>> > The f
Hello,
Yesterday I added CCD_CANONLIDE90 in genesys.c. I did two successive scans
(result on http://ggastebois.free.fr/lide90_snoop/25_test1.zip).
The first one gives a bright image (1_test1.txt), the second a dark image
(3_test1.txt). Which log seeems to be the best for calibration ? (in
3_test1.
Hello,
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> Pierre Willenbrock a ?crit :
>>> Guillaume Gastebois schrieb:
>>> > Hello,
>>> >
>>> > You can find attached a patch which works like my original code (with
>>>
Hello,
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
> > Hello,
> >
> > You can find attached a patch which works like my original code (with
> > different contrast and calibration between 2 scans...).
> >
> > I removed controversed comm
Hello,
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
> > Hello,
> >
> > You can find attached a patch which works like my original code (with
> > different contrast and calibration between 2 scans...).
> >
> > I removed controversed comm
" and to unlock I have
to push one of the 4 buttons !! Idea about that ?
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Hi Guillaume,
>
> Pierre Willenbrock schrieb:
>> Guillaume Gastebois schrieb:
>>> Pierre Willenbrock schrieb:
>>>> But this s
Hello,
> > Volker Grabsch schrieb:
> > > > On Wed, Mar 19, 2008 at 03:24:45PM +0100, Pierre Willenbrock wrote:
>> > > >> + ,
>> > > >> + /* CANONLIDE90 */
>> > > >> + {
>> > > >> +/*
>> > > >> +00 :
>> > > >> +02 : image ?? la con et inverse video
>> > > >> +0a : image ?? la con et in
)
Pierre Willenbrock a ?crit :
> Hi,
>
> Guillaume Gastebois schrieb:
>> Hello,
>>
>>
>>> What about only setting register 0x7f? that one should do something
>>> without needing to setup reg 0x1a.
>> Not better I think. Result :
>> http://g
Hello,
> What about only setting register 0x7f? that one should do something
> without needing to setup reg 0x1a.
Not better I think. Result :
http://ggastebois.free.fr/lide90_snoop/10_test0.tar
>
> I didn't expect reg[0x1a]=0x24 to work without setting the corresponding
> clock bit masks. Wha
line 1159 and without adding regs 0x71,
0x72, 0x73, 0x75, 0x76, 0x79, 0x7c, 0x7d, 0x7f in gl841_init_registers.
Result is a totally black image too
(http://ggastebois.free.fr/lide90_snoop/04_test2.tar).
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>>
e one week holidays !
regards
Guillaume
Pierre Willenbrock a ?crit :
> Hi,
>
> Guillaume Gastebois schrieb:
>> Hello,
>>
>>> So, we need to check what parts of the clocking we need to setup
>>> differently.
>>>
>>> Candidates:
>>>
>
Hello,
>
> So, we need to check what parts of the clocking we need to setup
> differently.
>
> Candidates:
>
> reg sane windows
> 0x1a 0x00 0x24 enable clock 3,4 manual output, invert clock 4
> 0x1d 0x04 0x02 just a smaller toggle "shoulder".
> 0x71 0x00 0x05 RS signal seem
cations !!!
Pierre Willenbrock a ?crit :
> Pierre Willenbrock schrieb:
>> Hi,
>>
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> So, what's the next step ? Re-enabling shading ?
>> Yes, but only after the shading-calibration is able to get
Hello,
Selon Pierre Willenbrock :
> Hi,
>
> Guillaume Gastebois schrieb:
> > Hello,
> >
> > So, what's the next step ? Re-enabling shading ?
>
> Yes, but only after the shading-calibration is able to get black level
> information.(This really needs a bett
Hello,
So, what's the next step ? Re-enabling shading ?
Do you think that last modification "for (i = 150; i..." is necessary ?
Is it time to fine tune registers 52... ?
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
&g
Hello,
Yep, I write "for (j = 150; j" instead of "for (i = 150; i."
Now second set seems good. Result is on :
http://ggastebois.free.fr/lide90_snoop/20_test1.tar
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
Hello,
I modified lines 4596 and 4712 and reenable SCAN_FLAG_DISABLE_LAMP flag.
Result can be found on : http://ggastebois.free.fr/lide90_snoop/19_test1.tar
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> OK, I'll try this
Hello,
OK, I'll try this tonight. What is the best : WITH or WITHOUT
SCAN_FLAG_DISABLE_LAMP ?
Regards
Guillaume
Selon Pierre Willenbrock :
> Guillaume Gastebois schrieb:
> > Hello,
> >
> > I made two tests today :
> >
> > test 1 : to
:
http://ggastebois.free.fr/lide90_snoop/18_test2.tar
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> I try both {0x00, 0x3f, 0x03, 0x26}, and {0x00, 0x3f, 0x00, 0x26},
>> you can find result under :
>> http://ggastebois.
Hello,
I try both {0x00, 0x3f, 0x03, 0x26}, and {0x00, 0x3f, 0x00, 0x26},
you can find result under :
http://ggastebois.free.fr/lide90_snoop/17_test1.tar
and http://ggastebois.free.fr/lide90_snoop/17_test2.tar
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schr
Hello,
You can find the result of this test here :
http://ggastebois.free.fr/lide90_snoop/no_shading_2bright_2dark.tar
The calibration is about 25s long.
Resulting image is bad (as befor).
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Pierre Willenbrock schrieb:
>> Guillaume
Hello,
You can find all of that on :
http://ggastebois.free.fr/lide90_snoop/no_shading.tar
What seems strange in calibration ?
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> So. I tryed your patch with and without shading cal
lines (but ve can see the
dinausore). Calibration is 4s long (see
http://ggastebois.free.fr/lide90_snoop/shading.jpg and
http://ggastebois.free.fr/lide90_snoop/shading.txt)
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Pierre Willenbrock schrieb:
>> Guillaume Gastebois schrieb:
Hello,
OK, I'll try it tonight.
How do I cleanly remove shading_calibration ?
Regards
Guillaume
Selon Pierre Willenbrock :
> Pierre Willenbrock schrieb:
> > Guillaume Gastebois schrieb:
> >> Hello,
> >>
> >> I see that reg[2] was like 0x07. So I
piece (in calibration area). So calibration is better with black area !!
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> I modified registers 10-1d with :
>>
>> {0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00,
Hello,
I inverted colors with gimp. Sorry I forget this operation.
Selon postmaster :
> Hi,
>
>
> How did you get this one :
> http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_comment.jpg ??
>
> Colors are not inverted ...
>
>
> Guillaume Gastebois a ?crit :
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Hi Guillaume,
>
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> Why calibration is so long (~50/60s) ?
>
> It is probably failing. Should take about 3-5 seconds. Look at the logs,
> the calculated averages and cali
Hello,
You can find my modified files for LiDE90 on :
http://ggastebois.free.fr/lide90_snoop/sources/
With them you will bee able to scan images (very poor quality) in
reversed video (???) and with a calibration during 60s (!!!)
Regards
Guillaume
sane at tsleg.com a ?crit :
> Hi guys,
>
> I
Hello,
I forget in my last mail (I'm hill today. It's not good for
concentration...) : You can find a scanimage log on :
http://ggastebois.free.fr/lide90_snoop/scanimage.log.
Regards
Guillaume
Pierre Willenbrock a ?crit :
> Hi Guillaume,
>
> Guillaume Gastebois schrieb:
Hello,
Pierre Willenbrock a ?crit :
> Hi Guillaume,
>
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> Why calibration is so long (~50/60s) ?
>
> It is probably failing. Should take about 3-5 seconds. Look at the logs,
> the calculated averages and calibrat
these two registers are never written.
Another thing : when scaning in color the leds are blue
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> I need a little bit more informations befor testing (sorry for my poor
>> knowledge
>&g
Hello,
I need a little bit more informations befor testing (sorry for my poor knowledge
in scanner)
Selon Pierre Willenbrock :
> I don't know why the image colors are reversed, but it may be worth
> trying to flip the sign bits in Genesys_Frontend. If that does nothing,
> we need to handle that
Hello,
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> It's a little bit better with these values.
>> In Genesys_Sensor I have :
>> regs_0x08_0x0b : {0x00, 0x21, 0x00, 0x00}
>> regs_0x10_0x1d : {0x02, 0x8b, 0x02, 0x8b, 0x02,
(http://ggastebois.free.fr/lide90_snoop/UsbSnoop_a4_200dpi.log) ?
I very appreciate your help.
Regards
Guillaume
P.S : attached a sample image with my values.
Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> OK, but via which register is it programmed. I find nothing in GL842
>&
OK, but via which register is it programmed. I find nothing in GL842 datasheet
for frontend.
regards
Guillaume
Selon Pierre Willenbrock :
> Guillaume Gastebois schrieb:
> > Hello,
> >
> > OK,
> > I open my LiDE 90 (very hard not all to destroy...).
> > I fi
?crit :
> Guillaume Gastebois schrieb:
>> >But you can ignore led-calibration for now, that is not essential when
>> >debugging the backend. Just make sure the exposure settings in
>> >Genesys_Sensor.regs_0x10_0x1d are good, for example from an usb log the
>>
>But you can ignore led-calibration for now, that is not essential when
>debugging the backend. Just make sure the exposure settings in
>Genesys_Sensor.regs_0x10_0x1d are good, for example from an usb log the
>last register write to 0x10-0x15 before receiving actual scanned data.
>If those sta
rfect !
>Guillaume Gastebois schrieb:
>> Hello,
>>
>> OK, my motor moves !
>
>Cool.
>
>>
>> But, someting doesn't work during initialisation : I get floating >point
>> error !
>>
>> I modified genesys_gl841.c for instrument
Hello,
OK, my motor moves !
But, someting doesn't work during initialisation : I get floating point
error !
I modified genesys_gl841.c for instrumentation and genesys_devices.c
(genesys_sensor section) in accordance to my windows usb snoop log (see
attacement).
SANE_DEBUG_GENESYS_GL841=255 s
>Guillaume Gastebois schrieb:
>> Hello,
>>
>> I tried with : SANE_DEBUG_GENESYS_GL841=255 scanimage
>> --device-name=genesys:libusb:001:005 > toto.pnm
>>
>> Result can be found in attachement.
>>
>> It locks on last line and did nothing els
Hello,
I tried with : SANE_DEBUG_GENESYS_GL841=255 scanimage
--device-name=genesys:libusb:001:005 > toto.pnm
Result can be found in attachement.
It locks on last line and did nothing else.
Thank you for help because I'm blocked.
Guillaume
-- next part --
An embedded an
Hello,
I can't make led on and motor move with my LiDE 90.
I modify CVS with replacing all LiDE 60 "0x221c" with "0x199" pid of
LiDE 90.
scanimage -L returns my LiDE 90, but SANE_DEBUG_GENESYS=255 scanimage
--device-name=genesys:libusb:001:005 > toto.pnm
gives me a log looping indefinitelly o
Hello,
I write few days ago about canon mp110 and it's chipset OASIS OA-1000. Has
anyone the datasheet of this component ? I can't find it.
Thank you
Guillaume
Thank you Ralf,
But LiDE 60 PID only appears 2 times in genesys_devices.c and 1 time in
genesys.conf.in I still change them and no result (scanimage -L return LiDE 90
but can't move or turn on led with scanimage >toto.pnm!!)
For help I did a usbsnoop and with a usbsnoop2libusb.pl a .c file. M
Hello,
Thank you for answer, but I had modified my genesys.conf :
# Canon LiDE 35/40/50
usb 0x04a9 0x2213
# Canon LiDE 60
usb 0x04a9 0x221c
# Canon LiDE 90
usb 0x04a9 0x1900
No other idea, because with scanimage nothong happends (no light, no
moves...)
Guillaume
Hello,
I'm sorry to disturb you, but I can't do someting with my LiDE 90. You
seems to be more advanced than me. (I'm under Mandriva 2008)
Thats what I do :
cvs -d:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/sane login
cvs -z3 -d:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/sane
Hello,
I have no result with LiDE 90. I take sane-backends CVS, and genesys in
experimental branch. Modified genesys_devices.c as followed.
scanimage -l gives me :
"device `genesys:libusb:001:019' is a Canon LiDE 90 flatbed scanner"
but scanimage -d genesys:libusb:001:019 > toto.pnm
did noting
Hello,
Has someone standalone scaning program or modified genesys backend for
test. Because I successless try to modifying the backend. I can make tests.
Guillaume
66 matches
Mail list logo
