Hello,
    On 12/29/05, Parag N(????) <panem...@gmail.com> wrote:
> Hello Pierre,
>
> On 12/28/05, Pierre Willenbrock <pie...@pirsoft.dnsalias.org> wrote:
> > Parag N(????) schrieb:
> > > Hello,
> > >
> > >
> > > In version 1.0.17 Genesys_Frontend for HP 2400 was written as
> > > -  {{0x00, 0x03, 0x05, 0x02}
> > > -   , {0x00, 0x00, 0x00}
> > > -   , {0xc0, 0xc0, 0xc0}
> > > -   , {0x07, 0x07, 0x07}
> > > -   , {0x00, 0x00, 0x00}
> > > which i replaced with
> > > +  {{0x00, 0x31, 0x1f, 0x13}
> > > +   , {0x08, 0x02, 0x16}
> > > +   , {0x20, 0x80, 0x10}
> > > +   , {0x80, 0x00, 0x00}
> > > +   , {0x01, 0xff, 0x00}
> > >
> > Typically the .sign part is identical for all color channels.
> >
> > >   Also i found you mentioned reset register which is not present in
> > > structure declaration.
> > Writes to the reset register lead to a reset of the frontend.
> > >  But i am not getting what to send for which frontend registers are
> > > played with during
> > >  calibration?
> >
> > Sorry, i was not very clear.
> >
> >
> > I wanted to know which frontend registers are written to in your windows
> > log. Some registers always get the same values, while others are set to
> > varying values during calibration. I am guessing this frontend is
> > incompatible with the current implementation.
> >
> > I get these information for my scanner:
> >
> > [0x01] = 0x03d
> > [0x02] = 0x008
> > [0x03] = 0x000
> > [0x05] = 0x005
> > [0x06] = 0x000
> > [0x08] = 0x019
> > [0x09] = 0x006
> > [0x20] = 0x0e1
> > [0x21] = 0x0e1
> > [0x22] = 0x0e1
> > [0x24] = 0x000
> > [0x25] = 0x000
> > [0x26] = 0x000
> > [0x28] = 0x093
> > [0x29] = 0x093
> > [0x2a] = 0x093
> >
> > Actually, the windows driver keeps the gain and offset constant for my
> > scanner.
> >
>   here i am attaching my windows USB log + linux debug log where after
> modification(i already mailed to list) + new frontend structre from my
> windows log is
>  [0x01] = 0x000
>  [0x02] = 0x031
>  [0x03] = 0x01f
>  [0x04] = 0x013
>  [0x06] = 0x008
>  [0x08] = 0x002
>  [0x09] = 0x016
>  [0x20] = 0x020
>  [0x21] = 0x080
>  [0x22] = 0x010
>  [0x24] = 0x080
>  [0x25] = 0x000
>  [0x26] = 0x000
>  [0x28] = 0x001
>  [0x29] = 0x0ff
>  [0x2a] = 0x093
>
>    Please kindly tell me why head is not moving back as i make it to
> scanner 1755 lines instead its default 3510 which exceeds. I then have
> to disconnect scanner then only genesys debug message logging stops.
>
         I want to know relationship between scanning no. of lines. In
genesys backend for HP 2400 i got no. of lines to scan are 3510. does
that mean scanner has to scan 1755 lines from start to other end and
then remaining 1755 from other end to start ?
regards,
Parag.
From ar...@ptic.pl  Thu Dec 29 12:22:37 2005
From: ar...@ptic.pl (ar...@ptic.pl)
Date: Thu Dec 29 12:29:42 2005
Subject: [sane-devel] [genesys driver - Plustek ST24] prescan impressions
Message-ID: <43b3d50d.4000...@ptic.pl>

Hi

I just to try scan witch sane-backends-1.0.17 on this scanner
(Plustek ST24). I do prescan with xsane:
- scanner do prescan only for half area---xsane fill full area
- prescan was greenish (scan too)
I do above in gray/color mode, 8/16bpp.

So, If I could help in anything, please tell me how can I do this.

Artur Pierscinski


Reply via email to