plustek@linuxhacker.org

On Thursday 24 October 2002 05:55, Gerhard Jaeger wrote:
>On Donnerstag, 24. Oktober 2002 11:31, Gene Heskett wrote:
>[SNIP]
>
>> From the clues here, where most have reported it went dead in
>> the middle of a scan, no light, no motor, no nothing and the
>> carriage is left sitting in mid-scan, darned near the only thing
>> this old troubleshooter with 50 years of experience in
>> electronics can believe is that the PSU died.
>
>But if the PSU dies, this can be checked easily! Or is that PSU a
> built-in one? All my Merlin scanners (Plustek, HP, Musktek) used
> have an extra PSU outside the device. So it's possible to replace
> it quickly.

Its an inline box, at least for the 1250u's.  So yes, its easily 
replaced, but when you goto the purchase point and ask for a PSU, 
you are suddenly a green tentacles monster from the Andromeda 
Cluster or something.  So while its theoreticly easy to do, finding 
the PSU unit is going to be a bit of a chore, basicly its made out 
of un-obtainium unless you take the whole scanner too.

>> I do know that my scanner makes a lot more noise in some modes
>> using the plustek backend compared to the noise it makes when
>> using the epson GT-7200 backend from iscan, which BTW I've yet
>> to be able to fully compile, it always barfs on the iscan gui
>> here.  Anyway, the increased noise level would tend to make me
>> think the motor is being driven both harder, and possibly a bit
>> out of phase.
>
>This noise can be corrected by finding out the correct values
> experimental. The tables inside plustek-devs.c define different
> ranges for clock-divider, PWM and PWM-duty:
>
>The EPSON currently used the following table:
>
>{ MODEL_NOPLUSTEK_1200, 1, 48, 6,
>    /* Motor settings (PWM and PWM_Duty) */
>    /* <=75dpi    <=100dpi    <=150dpi   <=200dpi  <=300dpi  */
>    {{ 1, 48 }, { 1, 48 }, { 1, 48 }, { 1, 48 }, { 1, 48 },
>    /* <=400dpi   <=600dpi   <=800dpi   <=1200dpi  <=2400dpi */
>    {2, 48 }, { 8, 48 }, { 2, 48 }, { 1, 48 }, { 1, 48 }},
>    /* Color mode MCLK settings */
>    { 2.0, 2.0, 2.0, 2.0, 2.0, 4.0, 4.0, 4.0, 5.5, 5.5 },
>    /* Gray mode MCLK settings */
>     { 5.0, 5.0, 5.0, 5.0, 5.0, 6.0, 6.0, 6.0, 6.0, 6.0 }
>},
>
>It think at least the 1200 dpi values may need to be corrected,
>but as long as I don't have any test device, I need some
> feedback...

Unforch, the last time I started a 1200dpi scan, it filled up a 
partition & I had to go get a fresh hard drive before I could fully 
recover.  I was playing with kooka, the gocr manager.  Anyway, 
there is now 106 gigs in this machine.  But I still made /root too 
small I think, so some of the older drive is gonna get 
repartitioned.  But I'm busy the next 3 weeks out of state, so it 
can wait.  I may even shut the machines down as the missus will 
also be headed to her sisters for the duration.  So my setiathome 
rank will probably go down the toilet.

> Maybe we can realize the plan to meet Reinhard in
> November to torture his 1250 ;-)

Sounds like a plan :-)

>Cheers
>  Gerhard

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.18% setiathome rank, not too shabby for a WV hillbilly