On 12/10/2012 09:03, Mohammad-Reza Nabipoor wrote:
> Dear Yury
> The 'Frontend' in Genesys_Frontend refers to Analogue Front End (AFE) IC.
> Genesys_Frontend structure contains some data (e.g. offset) for the
> WM8196 (that, "is a 16-bit analogue front end/digitiser IC which
> processes and digitises the analogue output signals from CCD sensors
> or Contact Image Sensors (CIS)").
> As mentioned in WM8196 datasheet, it has "Programmable gain" and
> "Programmable offset adjust", so we can set these parameters in the
> Genesys_Frontend structure. (And, there are two other entries in the
> Genesys_Frontend that I don't understand them, yet! --> can anyone
> help me?).
>
> Yury, as I mentioned in my first email, I am not sure that my scanner
> is a ST28(!); can you help me to understand it? please check your
> scanner VID/PID and compare them with 0x07b3/0x0802.
>
> Regards,
> Mohammad-Reza
>
>
>
> ----- Original Message -----
> From: Yury Tarasievich <yury.tarasievich at gmail.com>
> To: "sane-devel at lists.alioth.debian.org"
> <sane-devel at lists.alioth.debian.org>
> Cc:
> Sent: Friday, 12 October 2012, 9:34
> Subject: Re: [sane-devel] Problem with developing a new backend for
> Plustek OpticPro ST28
>
> On 10/12/2012 07:57 AM, Stef wrote:
> > these hardware information can help us to
> > find how close to another scanner a specific
> > model is. Since the ST24 is an unsupported GL646
> > scanner, it is not as helpful as it could have
> > been. Even when hardware is known, you'll have
> > to know exactly how they are wired to adapt the
> > backend without to have to look at the windwos
> > usb snoop logs.
> ...
> > add support, look at the various exchanges in
> > the mailing list on adding support for the
> > plustek Opticbook 3600 between me and Chris
> > Berry . This scanner is the same kind of target
>
> Thank you, of course. And please, guys, include me in CC for the
> eventually produced sources for ST28.
>
> Mohammad-Reza, for ST28 (being added) to be recognized, you'll need to
> add the USB IDs both to genesys_devices.c (genesys_usb_device_list
> structure) and to genesys.conf.in.
>
> One mighty source of confusion for Genesys backends writers is, I
> believe, the frontend concept and the corresponding Genesys_Frontend
> structure. (It is for me :)
> I gave it a brief re-look right now. I still don't understand this
> part of the genesys source code. How exactly one is supposed to
> "program" something like ILX569 sensor, which is only controlled by
> the appropriate clocking signal (from GL841, to be sure). Or WM8196
> DAC coupled to it, which is, too, clocked only? (I'm looking at their
> datasheets)
>
> Yury
>
> -- sane-devel mailing list: sane-devel at lists.alioth.debian.org
> <mailto:sane-devel at lists.alioth.debian.org>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
> <mailto:sane-devel-request at lists.alioth.debian.org>
>
>
Hello,
I have added a doxygen configuration file in doc/ . After
./configure, you can cd to doc/ and run 'doxygen doxygen-genesys.conf',
it will create a genesys-html/ subdirectory with html documentation. It
should help you understand of to use the frontend struct.
Regards,
Stef
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20121102/001dec9a/attachment.html>
