Plustek ST24

hi all
recently i've discover that in backend/gensys_devices.c is
placed sort
of values for ST24.
iv done small change in backend/gensys_devices.c:728 from
COLOR_ORDER_BGR to COLOR_ORDER_RGB  and in same file at line
726 value
0,8,16 to 0,18,30.
that gives correct colors on my plustek st 24 and good
correction of ccd
line-distance. Sadly only for resolution
600dpi which has wrong number of engine steps what can leads
to damange
of hardware. For simple workaround i limited y size  of scan
area to 1/4
of nominal size but its givs 600dpi x150dpi :/.
If sobody have any ideas how can i correct number of steps
for
resolutions larger then  150 dpi plz msg me.
Also i have fears that corect number of steps dosnt resolve
problem with
ccd line distance in resolutions difirent then 600 dpi(for
150 dpi those
values are difirent 2,18,32 perhaps).
Any ideas are welcome 

ps. sorry for my bad anglish ;) its 03:00 am and anglish
isnt my native
lang :>




-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

Le samedi 25 novembre 2006 03:02, Tymoteusz.Drozd a écrit :
> hi all
> recently i've discover that in backend/gensys_devices.c
is placed sort
> of values for ST24.
> iv done small change in backend/gensys_devices.c:728
from
> COLOR_ORDER_BGR to COLOR_ORDER_RGB  and in same file at
line 726 value
> 0,8,16 to 0,18,30.
> that gives correct colors on my plustek st 24 and good
correction of ccd
> line-distance. Sadly only for resolution
> 600dpi which has wrong number of engine steps what can
leads to damange
> of hardware. For simple workaround i limited y size  of
scan area to 1/4
> of nominal size but its givs 600dpi x150dpi :/.
> If sobody have any ideas how can i correct number of
steps for
> resolutions larger then  150 dpi plz msg me.
> Also i have fears that corect number of steps dosnt
resolve problem with
> ccd line distance in resolutions difirent then 600
dpi(for 150 dpi those
> values are difirent 2,18,32 perhaps).
> Any ideas are welcome 
>
> ps. sorry for my bad anglish ;) its 03:00 am and
anglish isnt my native
> lang :>

	Hello,

	the only way I know to find steps values and other settings
is to record USB 
activity under windows. Then study it to understand what's
going on. I use 
usbsniff and a few custom scripts to turn raw logs in
'higher level' format 
with genesys registers values and slope tables decoded.
	I can send them to you if you wish, or I can try them on a
ST24 sniffed log 
to see if they need to be  adapted.

Regards,
	Stef

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

On Thursday 30 November 2006 06:48, Stéphane VOLTZ wrote:
[SNIPSNAP]
> 	Hello,
> 
> 	the only way I know to find steps values and other
settings is to record USB 
> activity under windows. Then study it to understand
what's going on. I use 
> usbsniff and a few custom scripts to turn raw logs in
'higher level' format 
> with genesys registers values and slope tables decoded.
> 	I can send them to you if you wish, or I can try them
on a ST24 sniffed log 
> to see if they need to be  adapted.
>
Hi Stef,

would you mind to put those files to the experimental CVS?
Or anyway send me those too - I think I will find some time
during
xmas holidays to play around with my ST24 and/or
OpticFilm...

TIA
Gerhard


-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

Le jeudi 30 novembre 2006 07:19, Gerhard Jaeger a écrit :
> On Thursday 30 November 2006 06:48, Stéphane VOLTZ
wrote:
> [SNIPSNAP]
>
> > 	Hello,
> >
> > 	the only way I know to find steps values and
other settings is to record
> > USB activity under windows. Then study it to
understand what's going on.
> > I use usbsniff and a few custom scripts to turn
raw logs in 'higher
> > level' format with genesys registers values and
slope tables decoded.
> > 	I can send them to you if you wish, or I can try
them on a ST24 sniffed
> > log to see if they need to be  adapted.
>
> Hi Stef,
>
> would you mind to put those files to the experimental
CVS?
> Or anyway send me those too - I think I will find some
time during
> xmas holidays to play around with my ST24 and/or
OpticFilm...
>
> TIA
> Gerhard

	Hello,

	I'll add a few comments in them, and send them to you soon
(this week-end). 
They are currently tuned for the hp2400, I have to annotate
places that might 
have to be changed for the ST24.

Regards,
	Stef

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

On Friday 01 December 2006 06:52, Stéphane VOLTZ wrote:
> Le jeudi 30 novembre 2006 07:19, Gerhard Jaeger a
écrit :
> > On Thursday 30 November 2006 06:48, Stéphane VOLTZ
wrote:
> > [SNIPSNAP]
> >
> > > 	Hello,
> > >
> > > 	the only way I know to find steps values and
other settings is to record
> > > USB activity under windows. Then study it to
understand what's going on.
> > > I use usbsniff and a few custom scripts to
turn raw logs in 'higher
> > > level' format with genesys registers values
and slope tables decoded.
> > > 	I can send them to you if you wish, or I can
try them on a ST24 sniffed
> > > log to see if they need to be  adapted.
> >
> > Hi Stef,
> >
> > would you mind to put those files to the
experimental CVS?
> > Or anyway send me those too - I think I will find
some time during
> > xmas holidays to play around with my ST24 and/or
OpticFilm...
> >
> > TIA
> > Gerhard
> 
> 	Hello,
> 
> 	I'll add a few comments in them, and send them to you
soon (this week-end). 
> They are currently tuned for the hp2400, I have to
annotate places that might 
> have to be changed for the ST24.

That sounds good to me, thanks.
Gerhard



-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

	Hello,

	here's the mentioned scripts. There are 2 main ones:
	- decode.sh  : turns raw usb log in higher level form
	- cmd.sh : turns the output of the decoding in high level
status dumps

	The first script uses a swarm of little awk scripts that
handle a little step 
of decoding each. At the end, there shoudn't be any lines
'URB .....' 
remaining if everything has been decoded. In case any are
left, they're 
meaning has to be understood so that the scripts can handle
them. Usually the 
left over are custom button or power saving handling. If
needed, they can be 
filtered out as shown in decode.sh .

	The second script parses the high level output and builds a
in memory status 
of the scanner. Each time a motor start is found (motor
start is use as 
a 'commit'), the whole status (slope tables, analog fronted
and registers) is 
dumped. It allow to compare the debugging output of the
backend with the 
expected status of the scanner. This filters out the many
useless registers 
writing/reading done by drivers.

	All scripts keeps data, so logs may be huge, but you can
then rebuild 
pictures of scans from the recorded data. which help
understanding what the 
scanner is doing. Doing such his explained in 
http://perso.modulonet.fr/~stefdev/sane/gl646-wip03.odt

	I'll be out for a couple of day, so I will answer any
question/point when 
I'll be back.

Regards,
	Stef
-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org

Stéphane VOLTZ napisa³(a):
> 	Hello,
>
> 	here's the mentioned scripts. There are 2 main ones:
> 	- decode.sh  : turns raw usb log in higher level form
> 	- cmd.sh : turns the output of the decoding in high
level status dumps
>
> 	The first script uses a swarm of little awk scripts
that handle a little step 
> of decoding each. At the end, there shoudn't be any
lines 'URB .....' 
> remaining if everything has been decoded. In case any
are left, they're 
> meaning has to be understood so that the scripts can
handle them. Usually the 
> left over are custom button or power saving handling.
If needed, they can be 
> filtered out as shown in decode.sh .
>
> 	The second script parses the high level output and
builds a in memory status 
> of the scanner. Each time a motor start is found (motor
start is use as 
> a 'commit'), the whole status (slope tables, analog
fronted and registers) is 
> dumped. It allow to compare the debugging output of the
backend with the 
> expected status of the scanner. This filters out the
many useless registers 
> writing/reading done by drivers.
>
> 	All scripts keeps data, so logs may be huge, but you
can then rebuild 
> pictures of scans from the recorded data. which help
understanding what the 
> scanner is doing. Doing such his explained in 
> http://perso.modulonet.fr/~stefdev/sane/gl646-wip03.odt
>
> 	I'll be out for a couple of day, so I will answer any
question/point when 
> I'll be back.
>
> Regards,
> 	Stef
>   
Ok  thx!  i will work on it 

-- 
sane-devel mailing list: sane-devellists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/sane-d
evel
Unsubscribe: Send mail with subject "unsubscribe
your_password"
             to sane-devel-requestlists.alioth.debian.org