[sane-devel] CanoScan LiDE 25

[Gerhard Jaeger]

Hi,

On Wednesday 28 September 2005 03:49, Stephan wrote:
> 
> Thanks Henning
> 
> On Wednesday 28 September 2005 03:47, Henning Meier-Geinitz wrote:
> > [...]
> >
> > I don't know if that makes any difference but have you tried the
> > development version of SANE (e.g. a CVS snapshot) yet? The plustek
> > backend has been changed since incooperation of this patch.
> >
> 
> I've just tried with the development version, and I can acquire an image from 
> the commandline using scanimage. e.g.
> 
>   #scanimage -x 200 -y 290 --resolution=100 -d plustek:libusb:002:011\
>   > --format pnm > /tmp/outfile.pnm
> 
> However under remote scanning saned still locks up after what sounds like "a) 
> motor initialization and b)turning the lamp on".
> 
> I still also get some rather annoying (possibly damaging?) grinding noises 
> from the motor when using scanimage. 
> Could you maybe point me in the right direction where I might tweak the code 
> for the motor controls a little?
> 

I thought, that this issue + solution has been already sent to the list!
Anyway, again for the records:

As I don't have such a device, the motorclock fine-tuning needs to be done
by a volunteer who owns the LiDE25 - in the meantime, there are at least
3 people, equipped with such a device and the necessary instructions, but I got
no feedback with the correct motor settings. So it's maybe up to somebody else
to do the work (you Stephan? ;)

- get the latest CVS version of SANE
- open the file backend/plustek-usbdevs.c
- find the line: "static HWDef Hw0x04A9_0x2220 =" around line-nr 2308
  * here you could tweak the values for dMaxMotorSpeed and dMaxMoveSpeed
- find the line "{ MODEL_CANON1200, 8, 51, 3," around line-nr 2575
  * here you cloud tweak the MCLK settings for the various resolutions 
    and scanmodes (color 8+16bit, gray 8+16bit)
- after changing something, to the following:
  touch backend/plustek.c
  make all install

First you should check the preview scans (all modes), they will be
performed @ 75dpi - here you sould tweak the MCLK settings. If they seem 
to work okay, you should scan a portion of the image which is somewhere 
in the middle of the scanbed to see if the sensor movement is correct.
If not, tweak the MotorSpeed values.

After that go and do scans @ 100, 150, 200, 300, 400, 600, 800, 1200 and 2400dpi,
to see if the MCLKs are okay...
Any questions so far? Please ask!

Quite a lot of annyoing work, but needs to be done AND please don't forget to send
us the results! 

TIA for helping out
Gerhard