On Tue, Apr 3, 2018 at 10:24 PM, wrote:
Hi,
I' m just switch a PC system from Windows to Linux including an old Canon Lide
90 Scanner. I saw in Tour mailing list an old thread from 2008. Guillaume
Gastebois and Pierre Willenbrock started at this time
On Tue, Apr 3, 2018 at 10:24 PM, wrote:
> Hi,
> I' m just switch a PC system from Windows to Linux including an old Canon
> Lide 90 Scanner. I saw in Tour mailing list an old thread from 2008.
> Guillaume Gastebois and Pierre Willenbrock started at this time the
>
Hi,
I' m just switch a PC system from Windows to Linux including an old Canon Lide
90 Scanner. I saw in Tour mailing list an old thread from 2008. Guillaume
Gastebois and Pierre Willenbrock started at this time the development but did
not finished it. I want to start a new attempt but all
On Fri, Mar 12, 2010 at 11:03 PM, Mark J. Small msmall at eastlink.ca wrote:
Hi everybody,
I've looked through the lists for info about sane with a Canon LiDE 90. ?It
looks like Guillaume Gastebois was working hard on it in 2008, but got bogged
down in undocumented details.
Is there any
Hi everybody,
I've looked through the lists for info about sane with a Canon LiDE 90. It
looks like Guillaume Gastebois was working hard on it in 2008, but got bogged
down in undocumented details.
Is there any hope that this will ever work? I don't have the coding skills to
help.
Just like me, after seacrching for a simple, fast, cheap and relaiable
(LED's instead of normal fluorescent light) scaner for linux, and after
seing a scaned dinonsour in this mailing list :) using the canon LiDE
90, I decided to buy this model (a month ago), but since I don0t use
windows for
I did the same today and was hoping to get it running in Kubuntu. Just
posting to let you smart guys know that some of us ordinary users are very
interested in what you are doing. Keep up the good work and when you are
ready for more testers let us know. Thanks for your hard work.
Marc
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080412/037335de/attachment.htm
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
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 :
Hello,
Hi Guillaume,
Sorry for not answering sooner.
Guillaume Gastebois schrieb:
Hello,
Selon Pierre Willenbrock :
Guillaume Gastebois schrieb:
Hello,
Yesterday I added CCD_CANONLIDE90 in genesys.c. I did two
successive scans
(result on
Pierre Willenbrock schrieb:
Now for the real reason i am answering: I did play around with my
scanner, trying to get the shading calibration to work only on the white
strip. The trick was to do a real scan over the white strip, not just
sampling a single line over and over again. This is
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 first one gives a bright image (1_test1.txt), the second a dark image
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
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 first one gives a bright image (1_test1.txt), the second a dark image
(3_test1.txt). Which log seeems to be the
Hello,
You can find attached a patch which works like my original code (with
different contrast and calibration between 2 scans...).
I removed controversed comments (sorry).
I see in some case that my scanner locks writing : [genesys]
sanei_genesys_read_register (0x41, 0xf4) completed and to
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 comments (sorry).
Thanks for the patch. I see that you added DAC_CANONLIDE90 at one place.
This is
Ralf Haueisen schrieb:
I tried again, an now not even pressing a button help.
What code do you need, and how can i get it?
Please try the patch from Guillaume Gastebois.
Regards,
Pierre
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 comments (sorry).
Thanks for the patch. I see that you
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
different contrast and calibration between 2 scans...).
I removed controversed comments (sorry).
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
different contrast and calibration between 2 scans...).
I removed controversed comments
Hi Guillaume,
Pierre Willenbrock schrieb:
Guillaume Gastebois schrieb:
Pierre Willenbrock schrieb:
But this seems to be basically working. Please send your changes leading
to a usable scan, so i can integrate them.
For now, my code is ugly. I only modified lide60 to lide90. But you can
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 inverse video et moteur ne stoppe pas ?? la fin du
scan
+0e : ne reconnait plus la position home
+10 : mieux
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 inverse video et moteur ne stoppe pas ?? la fin du
scan
+0e : ne reconnait plus la
Hi,
It's just because they come from temporary code from a French person. As
I'm french to, I'll translate for you ;)
(I'll not translate word by word, cause image ? la con means something
like fucking picture)
+02 : image ?? la con et inverse video
dirty inverted picture
+0a : image ?? la
.
Ralf
-Urspr?ngliche Nachricht-
Von: Pierre Willenbrock pierre at pirsoft.dnsalias.org
Gesendet: 19.03.08 16:54:14
An: Volker Grabsch vog at notjusthosting.com
CC: sane-devel at lists.alioth.debian.org
Betreff: Re: [sane-devel] Canon LiDE 90
Volker Grabsch schrieb:
On Wed, Mar
at lists.alioth.debian.org
Betreff: Re: [sane-devel] Canon LiDE 90
Hi.
I just downloaded the current version from the CVS, an applied the patches.
But sane does not find the scanner.
sane-find-scanner is ok, but scanimage not. in /etc/sane.d/genesys.conf I
have added the ID of the scanner.
I tried
Ralf Haueisen schrieb:
Hi.
I just downloaded the current version from the CVS, an applied the patches.
But sane does not find the scanner.
sane-find-scanner is ok, but scanimage not. in /etc/sane.d/genesys.conf I
have added the ID of the scanner.
I tried everything as root, so
I tried again, an now not even pressing a button help.
What code do you need, and how can i get it?
-Urspr?ngliche Nachricht-
Von: Pierre Willenbrock pierre at pirsoft.dnsalias.org
Gesendet: 19.03.08 17:53:48
An: sane-devel at lists.alioth.debian.org
Betreff: Re: [sane-devel] Canon
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 inverse video et moteur ne stoppe
pas ?? la fin
Guillaume Gastebois schrieb:
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 inverse
Hello,
I do the test again with :
0x71] = 0x05; /*RS signal seems to be not used.*/
0x72] = 0x07; /*CP signal seems to be not used.*/
0x73] = 0x09; /*CP signal seems to be not used.*/
0x75] = 0x01; /*clock 1 bitmap*/
0x76] = 0xff; /*clock 1 bitmap*/
0x79] = 0x3f; /*clock 3 bitmap*/
0x7c] = 0x1e;
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://ggastebois.free.fr/lide90_snoop/10_test0.tar
I forgot that there is a switch-on-bit for that, too: bit0
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. What
Guillaume Gastebois schrieb:
Hello,
I'm back.
Today I made two tests : one with un commenting line 1159 and adding
regs 0x71, 0x72, 0x73, 0x75, 0x76, 0x79, 0x7c, 0x7d, 0x7f in
gl841_init_registers.
Result is a totally black image
(http://ggastebois.free.fr/lide90_snoop/04_test1.tar).
Hello,
I'm back.
Today I made two tests : one with un commenting line 1159 and adding
regs 0x71, 0x72, 0x73, 0x75, 0x76, 0x79, 0x7c, 0x7d, 0x7f in
gl841_init_registers.
Result is a totally black image
(http://ggastebois.free.fr/lide90_snoop/04_test1.tar).
The other is with un commenting line
Guillaume Gastebois schrieb:
Hello,
I modified these registers. But the scanner locks writting continiously :
[genesys] sanei_genesys_read_register (0x41, 0xf4) completed.
I modified 0x1a=0x24 and 0x1d=0x02 in Genesys_Sensor. In log I see
0x1d=0x02 but 0x1a=0x00 ??
For the missing
Hi,
Guillaume Gastebois schrieb:
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
Hi,
Guillaume Gastebois schrieb:
Hello,
I updated from CVS and modified flag GENESYS_FLAG_DARK_WHITE_CALIBRATION
in GENESYS_FLAG_DARK_CALIBRATION.
Summary of current modifications :
genesys_devices.c : see attachment
genesys_gl841.c : added SCAN_FLAG_DISABLE_LAMP (line 4461),
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 seems to be not
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 black level
information.(This really needs a better api..)
I commited a prerequisite for shading calibration
Hello,
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
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 better api..)
How to do
Guillaume Gastebois schrieb:
Hello,
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
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
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,
I modified lines 4596 and 4712 and
Guillaume Gastebois schrieb:
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
Hi,
i am sorry, i actually wanted 450, but didn't realize until just now. I
missed that the
Hello,
OK, I'll try this tonight. What is the best : WITH or WITHOUT
SCAN_FLAG_DISABLE_LAMP ?
Regards
Guillaume
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
Guillaume Gastebois schrieb:
Hello,
I made two tests today :
test 1 : too bright/too dard = 10/65525 WITH flag :
Guillaume Gastebois schrieb:
Hello,
OK, I'll try this tonight. What is the best : WITH or WITHOUT
SCAN_FLAG_DISABLE_LAMP ?
Not using SCAN_FLAG_DISABLE_LAMP is a bit counter productive when trying
to get black levels on a white-only calibration area.
Regards,
Pierre
Regards
Guillaume
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 tonight. What is the best : WITH
Guillaume Gastebois schrieb:
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
Okay, results look good so far:
[genesys_gl841] gl841_offset_calibration: first set:
Guillaume Gastebois schrieb:
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
Looks a lot better. The offset*.pnm actually show a
Hello,
I made two tests today :
test 1 : too bright/too dard = 10/65525 WITH flag :
SCAN_FLAG_DISABLE_LAMP. Result can bee found on :
http://ggastebois.free.fr/lide90_snoop/18_test1.tar
test 2 : too bright/too dard = 10/65525 WITHOUT flag :
SCAN_FLAG_DISABLE_LAMP. Result can bee found on :
Guillaume Gastebois schrieb:
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).
Please try with bit 4+5 of frontend setup register 1 set to 3:
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 schrieb:
Hello,
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 Gastebois
Pierre Willenbrock schrieb:
Guillaume Gastebois schrieb:
Hello,
You can find all of that on :
http://ggastebois.free.fr/lide90_snoop/no_shading.tar
What seems strange in calibration ?
The minimum/maximum values retrieved from the scans do not scale with
the offset values, but in a
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 calibration :
with shading :
Guillaume Gastebois schrieb:
Hello,
You can find all of that on :
http://ggastebois.free.fr/lide90_snoop/no_shading.tar
What seems strange in calibration ?
The minimum/maximum values retrieved from the scans do not scale with
the offset values, but in a rather random manner. The
Pierre Willenbrock schrieb:
Guillaume Gastebois schrieb:
Hello,
I see that reg[2] was like 0x07. So INVOP was still set !!!
I comment out offset_calibration in genesys_flatbed_calibration, set
reg[2] to 0x03, and I get a black image with a gray vertical line in the
middle !!!
I try to
Hello,
OK, I'll try it tonight.
How do I cleanly remove shading_calibration ?
Regards
Guillaume
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
Pierre Willenbrock schrieb:
Guillaume Gastebois schrieb:
Hello,
I see that reg[2] was like 0x07. So INVOP was still set !!!
I
Guillaume Gastebois schrieb:
Hello,
OK, I'll try it tonight.
How do I cleanly remove shading_calibration ?
The code for the actual calibration is in genesys.c, line 3362:
/* shading calibration */
to line 3414, before
/* send gamma tables if needed */
Regards
Guillaume
Hi.
I've something quite good (not inverted ;) ) ...
But I did not commented those lines, but removed
GENESYS_FLAG_DARK_WHITE_CALIBRATION in canon_lide_60_model structure,
and set register[2] to 0x03
(See files : http://home.tsleg.com/saneLiDE90/saturated/ )
Hello,
So. I tryed your patch with and without shading calibration :
with shading : same as bevor but calibration is now 4s long (see
http://ggastebois.free.fr/lide90_snoop/no_shading.jpg and
http://ggastebois.free.fr/lide90_snoop/no_shading.txt)
without shading : image with some vertical
Hi,
I've made some progress ...
I changed :
/* CANOLIDE35 */
{1200,
/*TODO: find a good reason for keeping all three following variables*/
87,/*(black) */
87,/* (dummy) */
0,/* (startxoffset) */
10400,/*sensor_pixels */
sane at tsleg.com a ?crit :
Where do I set this ? (which parameter of which struct ?)
Sorry ... I found where to set this.
Hello,
I inverted colors with gimp. Sorry I forget this operation.
Selon postmaster postmaster at tsleg.com:
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 :
Hello,
I
Guillaume Gastebois schrieb:
Hello,
I modified registers 10-1d with :
{0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00, 0xff, 0x24, 0x00,
0x00, 0x04},
and now the led is really white (red green and blue by moving eyes).
Led calibration seems to be good.
But calibration is
Hello,
I see that reg[2] was like 0x07. So INVOP was still set !!!
I comment out offset_calibration in genesys_flatbed_calibration, set
reg[2] to 0x03, and I get a black image with a gray vertical line in the
middle !!!
I try to reenable offset_calibration and I get :
Guillaume Gastebois schrieb:
Hello,
I see that reg[2] was like 0x07. So INVOP was still set !!!
I comment out offset_calibration in genesys_flatbed_calibration, set
reg[2] to 0x03, and I get a black image with a gray vertical line in the
middle !!!
I try to reenable offset_calibration
Hello,
I modified registers 10-1d with :
{0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00, 0xff, 0x24, 0x00,
0x00, 0x04},
and now the led is really white (red green and blue by moving eyes).
Led calibration seems to be good.
But calibration is always 60s long.
I need help.
Thanks
Hi guys,
I gess I have an answer of my question ;)
I just bought a Canon LiDE 90 and can't make it work ... I will try to
make a backend, but I wanted to be sure that nobody was doing it ...
Is there anybody working on it ?
Do you think I could help for anything ? Can I download anywhere
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 calibration are dumped there.
What are /* Start of white
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,
Why
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
On Saturday 09 February 2008 18:59:47 sane at tsleg.com wrote:
Hi all,
I just bought a Canon LiDE 90 and can't make it work ... I will try to
make a backend, but I wanted to be sure that nobody was doing it ...
Is there anybody working on it ?
Yes, just look into the archive, e.g. even
Hello,
Why calibration is so long (~50/60s) ?
What are /* Start of white strip in mm (y) */ and /* Start of black mark
in mm (x) */ in genesys_devices.c ?
Regarding the log file you said :
W ! 0x23 ! 0x050 ! dac value rgb(offset value)
W ! 0x2b ! 0x028 ! pga gain rgb
But on debug, I see that
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 calibration are dumped there.
What are /* Start of white strip in mm (y) */ and /* Start of black
Guillaume Gastebois schrieb:
Hello,
I need a little bit more informations befor testing (sorry for my poor
knowledge
in scanner)
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
I don't know why the image colors are reversed, but it may be worth
trying to flip the sign bits
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, 0x8b, 0x20, 0x06, 0x00,
0xff, 0x24, 0x00, 0x00, 0x04}
Guillaume Gastebois schrieb:
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, 0x8b, 0x20, 0x06, 0x00,
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, 0x8b, 0x20, 0x06, 0x00,
0xff, 0x24, 0x00, 0x00, 0x04}
regs_0x52_0x5e : {0x02, 0x04, 0x02,
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, 0x8b, 0x20, 0x06, 0x00,
0xff, 0x24, 0x00, 0x00, 0x04}
regs_0x52_0x5e : {0x02, 0x04, 0x02, 0x04, 0x02, 0x04, 0x0a, 0x71, 0x55,
OK, but via which register is it programmed. I find nothing in GL842 datasheet
for frontend.
regards
Guillaume
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
Guillaume Gastebois schrieb:
Hello,
OK,
I open my LiDE 90 (very hard not all to destroy...).
I find these IC's :
On Friday 01 February 2008 09:18:20 Guillaume Gastebois wrote:
OK, but via which register is it programmed. I find nothing in GL842 datasheet
for frontend.
check for register 0x04
Layout:
Bit 7 |Bit 6 |Bit 5 Bit 4 |Bit 3 Bit 2 |Bit 1 Bit 0
LINEART |BITSET |AFEMOD[1:0] |FILTER[1:0]
Guillaume Gastebois schrieb:
OK, but via which register is it programmed. I find nothing in GL842 datasheet
for frontend.
regards
Guillaume
the analog frontend is programmed through the serial interface accessed
by address registers 0x50(FERDA)/0x51(FEWRA) and data registers
Hello,
OK,
I open my LiDE 90 (very hard not all to destroy...).
I find these IC's :
GL842 (Genesys well known scanner chip)
GLT44016P (SO40 RAM)
BU6574 (TSSOP20 )
VHC175 (TSSOP16 quad flip flop)
VHC08 (TSSOP16 quad and)
LB1940 (TSSOP20
Guillaume Gastebois schrieb:
Hello,
OK,
I open my LiDE 90 (very hard not all to destroy...).
I find these IC's :
GL842 (Genesys well known scanner chip)
GLT44016P (SO40 RAM)
BU6574 (TSSOP20 )
VHC175 (TSSOP16 quad flip flop)
VHC08 (TSSOP16 quad
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 stay
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
last register write to 0x10-0x15 before receiving
Hello,
Thank you Pierre.
I did all what you do : commenting the code in
genesys_flatbed_calibration (Offset/Gain calibration commented out too),
added OPTICAL_FLAG_DISABLE_SHADING to the flags in
gl841_init_optical_regs_scan
analog frontend is so :
{0x00, 0x21, 0x00, 0x00},
{0x02,
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
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 else.
It sits in gl841_slow_back_home, genesys_gl841.c:3581-3597. You need to
Guillaume Gastebois schrieb:
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 else.
It sits in gl841_slow_back_home,
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
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 else.
It sits in gl841_slow_back_home, genesys_gl841.c:3581-3597. You need
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 on :
Guillaume Gastebois schrieb:
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
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.
/40/50
usb 0x04a9 0x2213
# Canon LiDE 60
usb 0x04a9 0x1900
-Urspr?ngliche Nachricht-
Von: Guillaume Gastebois guillaume.gastebois at free.fr
Gesendet: 31.12.07 01:49:51
An: sane-devel at lists.alioth.debian.org
Betreff: [sane-devel] Canon LiDE 90
Hello,
I'm sorry to disturb
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
1 - 100 of 120 matches
Mail list logo