[sane-devel] Canon LiDE 25 scanner

2005-09-29 Thread Gerhard Jaeger 
Hi Stephan,

On Wednesday 28 September 2005 23:27, Stephan February wrote:
 hello
 
 On Wednesday 28 September 2005 22:23, Gerhard Jaeger wrote:
  hmmm, I thought my last mail was quite clear!
  I don't think it's necessary to snoop the USB traffic - it's necessary to
  find out the correct clock values...
 
 Armed with Gerard's suggestion, I have been playing around with the timings 
 and motor speed settings for my Canon LiDE 25.

thanks for that.

 Here is a motor/timing setting which currently works well for me, and without 
 the previous annoying grinding noises. It also looks like my problems with 
 saned are related to previously reporting timing issues when network 
 scanning. The latter I've confirmed by doing a saned scan via localhost.
 
 Please comment if you see anything obviously wrong or dangerous here 'cause I 
 really just fiddled until I was satisfied.

if it's working, everything is fine ;)

 
  snip 
 
 { MODEL_CANON1200, 8, 51, 9,
/* Motor settings (PWM and PWM_Duty) */
/* =75dpi   =100dpi  =150dpi  =200dpi  =300dpi  */
{{ 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 },
 
/* =400dpi  =600dpi  =800dpi  =1200dpi =2400dpi */
{ 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }},
/* Color mode MCLK settings */
{ 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0 },
{ 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0 },
/* Gray mode MCLK settings */
{ 7.0, 7.0, 6.0, 6.0, 6.0, 6.0, 6.0,  6.0,  6.0,  6.0 },
{ 6.5, 6.5, 6.0, 6.0, 6.0, 6.0, 8.0, 12.0, 12.0, 12.0 }
 },

just wondering, why the MCLKs are that high - ain't the scans too slow?

  snip 
 
 ... and ...
 
  snip 
 /** Canon LiDE25 */
 static HWDef Hw0x04A9_0x2220 =
 {
 0.80,   /* dMaxMotorSpeed (Max_Speed) */
 0.200,  /* dMaxMoveSpeed (Max_Speed)  */
 0.0,/* dHighSpeed */
  snip 
 
 If I were to create a patch, would it be better if an entirely new section 
 for 
 the LiDE25 was created e.g.?
 
   .
   .
  { MODEL_LIDE25, 8, 51, 9,
/* Motor settings (PWM and PWM_Duty) */

I'll do that and submitt it to CVS today...


Thanks again for that work.
Gerhard

[sane-devel] Canon LiDE 25 scanner

2005-09-28 Thread Luke Kendall 
I read the thread CanoScan LiDE 25 that finished on Mon Jul 18 06:24:08 UTC 
2005.

I've just bought one of these and found I couldn't get it to work under
SuSE 9.2 (though I saw a review of MandrakeMove that seemed to indicate
it worked with no special effort there).

I have the scanner working okay under MacOS X, so although I can't
easily run Windows to snoop any useful info for you, if you can point
me at a tool I can use under MacOS X to gather any info for you, I'd be
happy to try (and to try any Linux experiments).  My experince under
SuSE was similar to the poster - scanimage -L reported no supported
devices, but sane-find-scanner sees it and gets the manufacturer and
model info correct.

luke

[sane-devel] Canon LiDE 25 scanner

2005-09-28 Thread Henning Meier-Geinitz 
Hi,

On Wed, Sep 28, 2005 at 09:25:29PM +1000, Luke Kendall wrote:
 I read the thread CanoScan LiDE 25 that finished on Mon Jul 18 06:24:08 UTC 
 2005.

Please also read the current thread about this scanner:
http://lists.alioth.debian.org/pipermail/sane-devel/2005-September/014791.html

Bye,
  Henning

[sane-devel] Canon LiDE 25 scanner

2005-09-28 Thread Luke Kendall 
On 28 Sep, Stephan February wrote:
  I managed to get this scanner working using the development snapshot from 
 the  
  27th Sept 05.  
   
  http://www.sane-project.org/snapshots/ 
   
  I'm still having some issues with it though. e.g. remote scanning via saned 
 is  
  broken for some reason, and it emits really alarming noises upon starting a  
  scan. 

Thanks for the tip.  I'll give it a try on the weekend and see how I go.

Is there an equivalent to usbsnoop for Linux and Mac?  Then I could
compare the command sequences and report any differences to the list.

luke

[sane-devel] Canon LiDE 25 scanner

2005-09-28 Thread Gerhard Jaeger 
On Wednesday 28 September 2005 16:03, Luke Kendall wrote:
 On 28 Sep, Stephan February wrote:
   I managed to get this scanner working using the development snapshot from 
  the  
   27th Sept 05.  

   http://www.sane-project.org/snapshots/ 

   I'm still having some issues with it though. e.g. remote scanning via 
  saned is  
   broken for some reason, and it emits really alarming noises upon starting 
  a  
   scan. 
 
 Thanks for the tip.  I'll give it a try on the weekend and see how I go.
 
 Is there an equivalent to usbsnoop for Linux and Mac?  Then I could
 compare the command sequences and report any differences to the list.
 
hmmm, I thought my last mail was quite clear!
I don't think it's necessary to snoop the USB traffic - it's necessary to find 
out
the correct clock values...

Ciao,
Gerhard

[sane-devel] Canon LiDE 25 scanner

2005-09-28 Thread Stephan February 
On Wednesday 28 September 2005 22:23, Gerhard Jaeger wrote:
 hmmm, I thought my last mail was quite clear!
 I don't think it's necessary to snoop the USB traffic - it's necessary to
 find out the correct clock values...


Thanks Gerhard

I'm assuming you're referring to this email:

http://lists.alioth.debian.org/pipermail/sane-devel/2005-September/014600.html

I'm going to try your suggestions now. Will keep the list posted.

Cheers
Stephan

[sane-devel] Canon LiDE 25 scanner

2005-09-28 Thread Stephan February 
hello

On Wednesday 28 September 2005 22:23, Gerhard Jaeger wrote:
 hmmm, I thought my last mail was quite clear!
 I don't think it's necessary to snoop the USB traffic - it's necessary to
 find out the correct clock values...

Armed with Gerard's suggestion, I have been playing around with the timings 
and motor speed settings for my Canon LiDE 25.
Here is a motor/timing setting which currently works well for me, and without 
the previous annoying grinding noises. It also looks like my problems with 
saned are related to previously reporting timing issues when network 
scanning. The latter I've confirmed by doing a saned scan via localhost.

Please comment if you see anything obviously wrong or dangerous here 'cause I 
really just fiddled until I was satisfied.

 snip 

{ MODEL_CANON1200, 8, 51, 9,
   /* Motor settings (PWM and PWM_Duty) */
   /* =75dpi   =100dpi  =150dpi  =200dpi  =300dpi  */
   {{ 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 },

   /* =400dpi  =600dpi  =800dpi  =1200dpi =2400dpi */
   { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }, { 8, 31, 1 }},
   /* Color mode MCLK settings */
   { 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0 },
   { 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0, 9.0 },
   /* Gray mode MCLK settings */
   { 7.0, 7.0, 6.0, 6.0, 6.0, 6.0, 6.0,  6.0,  6.0,  6.0 },
   { 6.5, 6.5, 6.0, 6.0, 6.0, 6.0, 8.0, 12.0, 12.0, 12.0 }
},
 snip 

... and ...

 snip 
/** Canon LiDE25 */
static HWDef Hw0x04A9_0x2220 =
{
0.80,   /* dMaxMotorSpeed (Max_Speed) */
0.200,  /* dMaxMoveSpeed (Max_Speed)  */
0.0,/* dHighSpeed */
 snip 

If I were to create a patch, would it be better if an entirely new section for 
the LiDE25 was created e.g.?

  .
  .
 { MODEL_LIDE25, 8, 51, 9,
   /* Motor settings (PWM and PWM_Duty) */
  .
  .

Cheers
Stephan