plustek: Thread: Canon LiDe20

Hi!

I've tried setting this option, but look like it keeps re-calibrating
every time.

Sane backend 1.0.13
Plustek 0.46
Xsane 0.91 I believe

Debug  output shows:

cacheCalData yes

Otherwise the scanning quality is good, no other problems found. Good
work!

Thanks,
A.

P.S. Is there any way to re-set the scanner programmatically? I hit
"cancel" in Xsane once, which froze the thing to death, had to re-boot
the whole system to revive it.

>> Another problem is that the scanner takes some seconds before
scanning,
>> with the carriage going up and down (with a bit noise), and then it
scans
>> the image. Can I do something to avoid that?

> No, because this is needed for calbration. To avoid every time
recalibration,
> you can try the option:
> option cacheCalData 1

Hi, if it is true (see sane-develop mlist) the driver for the LiDE is 
"again" broken;
it seem to have been okay in v. 1.0.13; I ignore if this is corect 
because under suse 9.0 we got that version, and the scanner only worked 
once, then it refuses to scan.
My partner has migrated from her suse t odebian sarge now, and now she 
must use w$ to run the LiDE20, as long as the driver is not repaired.
Note: the author also seem to be changing from home, so it's frustrating 
ans she is desperate to use w$ for 'only' the scanner.

Maybe some new contributors/maintainers can help a little bit for doing 
something to fix the problem.

I'm unfortunately not developper.

Aldo.

Hi,

the driver is not broken! It seems that with some LiDE20 the
latest version have problems, but not with all of them. In SANE
CVS the driver has been "repaired" and should work now correctly...

On Saturday 27 August 2005 23:11, ####@####.#### wrote:
> Hi, if it is true (see sane-develop mlist) the driver for the LiDE is
> "again" broken;
> it seem to have been okay in v. 1.0.13; I ignore if this is corect
> because under suse 9.0 we got that version, and the scanner only worked
> once, then it refuses to scan.
> My partner has migrated from her suse t odebian sarge now, and now she
> must use w$ to run the LiDE20, as long as the driver is not repaired.
> Note: the author also seem to be changing from home, so it's frustrating
> ans she is desperate to use w$ for 'only' the scanner.

What do you mean with "the author seem to be changing from home"?
I'm the author, I'm here ;) So where's the problem?

> Maybe some new contributors/maintainers can help a little bit for doing
> something to fix the problem.
>
> I'm unfortunately not developper.
>
> Aldo.

Ciao,
Gerhard