plustek: Re: Epson 1250Photo Patches
Subject:
Re: Epson 1250Photo Patches
From:
Peter Much ####@####.####
Date:
28 Jul 2002 23:48:29 -0000
Message-Id: <20020728225735.A88524@disp.oper.dinoex.org>
Hi Gerhard,
glad to read You!
I tried to get onto the mailinglist, but it wants me to send
a confirmation to a nonexistent host - those guys obviousely
haven't read RFC821/2 and do not know how to use the Envelope-
Sender (or, precisely, how *NOT* to use it), with the result that
UUCP-connected sites cannot participate in these lists. So,
I will now just post to the list and see how to follow it on
the web.
-------------------
On Sat, Jul 27, 2002 at 12:41:11PM +0200, Jaeger, Gerhard wrote:
! zunächst mal danke für die Patches. Das Problem der 43-1 Version
! war ein Bug in der switchLamp Routine, deshalb hat das Teil das falsche
! Register samt Makse zurückgeliefert und natürlich die Lmape nicht
! mehr geschaltet!
! Mit dem .conf switch enableTPA wäre es möglich gewesen für den
! "Photo" die TPA Einheit zu aktivieren.
I think I did change this option, but this seemed not to change
anything.
! Ich habe gerade die Version 43-3 aufs Netz gelegt, kannst Du das mach
! durchchecken!
! Denk bitte daran, "enableTPA" zu benutzen
Wow, great, thank You!
Yes, this works now:
* add the Capabilities for Transparency and Negative in the
plustek-devs.c file for the device.
* "Negative" does switch the lamp correctly, "Transparency" doesn't
-> it is missing in usb_swichLamp()!
---------------------------
But I have a much more severe problem now, where I am quite clueless
on where to begin tuning:
My motor tends to walk BACKWARDS some lines or some inches in the
midst of a scan. Accordingly, the scan then contains duplicate
parts. This happens randomly, most often at 300 dpi, and gets
worse the warmer the machine is. Sometimes it is very difficult
to detect, as only few scanlines are duplicate, sometimes half of
the page is duplicated (and the other half missing). And sometimes
the machine locks up completely while the motor hums and the
lamp does not move.
I tried to reproduce this with the windows driver, and couldn't.
Now as I see, that 9832 chip also does the lowlevel motor
control, so the specific device characteristics of the motor have
to be represented in the parameters loaded into the 9832.
This looks to me like certain timing issues for the motor
pulses are not set optimal.
But where can this be tuned?
rgds,
PMc
