On Thursday 04 November 2010 22:03:19 Gerhard Jäger wrote:
> Hi Stefan,
>
> On Tuesday 27 July 2010 00:00:52 Stefan Champailler wrote:
> > On Monday 26 July 2010 19:52:33 Gerhard Jaeger wrote:
> > > well I've two different N650U and they both work with the old
> > > settings and I had nobody like you wiht a N656 to test that's all...
> > >
> > > Anyway thanks for testing, I'll commit (is it the same wording as for
> > > CVs?) the patch ASAP.
> >
> > Hey not so fast ! I've tested successfully by changing one of the value.
> > Now, I didn't check other values. Maybe there's a setting that is better.
> > For example, the "sound" of the scanner is a bit different than before,
> > it sounds less "silent". Therefore I believe there's probably an optimum
> > to look for. So before committing, it might be worth make some more
> > trial and error and maybe actually understand the meaning of the value.
> > Don't you think ?
>
> any news on that? Can you confirm the settings?
ooops RL caught me... But thanks to your mail, I've made some tests tonight.
Excerpts of the code (plustek-usbdevs.c) :
/** Canon N650U/N656U */
static HWDef Hw0x04A9_0x2206 =
{
/* 0.86 / 0.243 : original values
dMaxMotorSpeed / dMaxMoveSpeed / --resolution option passed to
bin/scanimage --resolution
0.76 / 0.243 / 200dpi grinding
0.85 / 0.243 / 200dpi heavy grinding
0.80 / 0.233 / 200dpi heavy grinding
0.86 / 0.242 / 200dpi ultra heavy grinding -> don't scan
0.75 / 0.242 / 200dpi heavy grinding
0.74 / 0.241 / 200dpi heavy grinding
0.77 / 0.243 / 200dpi heavy grinding
0.43 / 0.243 / 200dpi heavy grinding
0.86 / 0.200 / 200dpi ultra heavy grinding -> don't scan
0.86 / 0.244 / 200dpi ultra heavy grinding -> don't scan
0.86 / 0.243 / 200dpi ultra heavy grinding -> don't scan
0.86 / 0.244 / 200dpi ultra heavy grinding -> don't scan
0.76 / 0.243 / 200dpi grinding
0.77 / 0.243 / 200dpi heavy grinding
0.78 / 0.243 / 200dpi heavy grinding
0.79 / 0.243 / 200dpi heavy grinding
0.80 / 0.243 / 200dpi heavy grinding
0.81 / 0.243 / 200dpi heavy grinding
0.81 / 0.243 / 600dpi low grinding (my guess : 200 dpi is not a godd
idea)
0.82 / 0.243 / 600dpi low grinding
0.82 / 0.242 / 600dpi low grinding
0.85 / 0.242 / 600dpi low grinding
0.86 / 0.243 / 600dpi really heavy grinding -> no scan
0.85 / 0.243 / 600dpi low grinding --> sounds almost normal (although I
don't know what normal is :-))
0.85 / 0.240 / 600dpi small grinding
So what does this all mean ? I've made several tests and for some reason, the
200 dpi resolution is really not a good idea on my scanner : I can't get rid
of the noise (it scans but it makes a very creepy noise)
When using 600 dpi resolution, then the scanner behaves much better. I have
some very light grinding but the scan always completes... Except when
MaxMotorSpeed is set to 0.86. This seems to be a threshold value (even at 200
dpi). When this is set, most of the time the scanner don't even scan (the
"head" doesn't move up the page)
The maxMoveSpeed doesn't seem very important : changing it doesn't affect the
behaviour in a significant way in my tests.
I wonder what I could do now ? Because what I've found is that the working
values for maxMotorSpeed are not the same depending on the resolution... And
according to the way the parameter tables are set, this doesn't seem to be the
way the code was meant to work.
I'll sleep on it and start over tomorrow evening
stF
>
> TIA
> Gerhard
--
Timeo Danaos et dona ferentes
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
