plustek: Thread: Genius Colorpage Vivid III

Hi

I have a parport Genius Colorpage Vivid III and I tried the plustek
backend with it, but it doesn't work. The resulting images are
terrible. Searching the list I found a mail [1] from 2 years ago
describing the same problem. 

I would like to know the status of this project, if it's still under
active development. I can provide some samples and debugging information
and some help in solving this issue.

Regards

--
A. Monteiro


[1] http://www.linuxhacker.org/cgi-bin/ezmlm-cgi/3/2280

On Monday 28 November 2005 06:50, Maria Del Monte wrote:
> Hi
> 
> I have a parport Genius Colorpage Vivid III and I tried the plustek
> backend with it, but it doesn't work. The resulting images are
> terrible. Searching the list I found a mail [1] from 2 years ago
> describing the same problem. 
> 
> I would like to know the status of this project, if it's still under
> active development. I can provide some samples and debugging information
> and some help in solving this issue.
> 
> Regards
> 

Hi,

the project is still maintained, but as I don't have a Genius Vivid III
available here on my desk, I could not improve the driver - sorry. I tried
to get one of those devices via eBay, but had no success so far :(

I guess the calibration stuff need to be setup correctly.

Gerhard

On Wednesday 30 Nov 2005 07:26, Gerhard Jaeger wrote:
> On Monday 28 November 2005 06:50, Maria Del Monte wrote:
> > Hi
> >
> > I have a parport Genius Colorpage Vivid III and I tried the plustek
> > backend with it, but it doesn't work. The resulting images are
> > terrible. Searching the list I found a mail [1] from 2 years ago
> > describing the same problem.
> >
> > I would like to know the status of this project, if it's still under
> > active development. I can provide some samples and debugging information
> > and some help in solving this issue.
> >
> > Regards
>
> Hi,
>
> the project is still maintained, but as I don't have a Genius Vivid III
> available here on my desk, I could not improve the driver - sorry. I tried
> to get one of those devices via eBay, but had no success so far :(
>
> I guess the calibration stuff need to be setup correctly.
>
> Gerhard
>
>
Hi,

I also have one of these and tried to get it working under linux sometime ago, 
I tried to capture the data sent to the scanner in windows, but the capture 
program could not manage it.

I would be interested in getting it working, I have done some programming and 
used an i2c capture device with my Adaptec AVC-2410 video capture card and 
have  now added support for the card to the ivtv project, with some 
programming assistance from someone with a different Adaptec card.

Is there a similar method of capturing data (using a separate computer to 
capture the data) for the parallel port so I could get the data that way?

Best Regards

Trev

On Wednesday 30 November 2005 13:17, Trev Jackson wrote:
> On Wednesday 30 Nov 2005 07:26, Gerhard Jaeger wrote:
> > On Monday 28 November 2005 06:50, Maria Del Monte wrote:
> > > Hi
> > >
> > > I have a parport Genius Colorpage Vivid III and I tried the plustek
> > > backend with it, but it doesn't work. The resulting images are
> > > terrible. Searching the list I found a mail [1] from 2 years ago
> > > describing the same problem.
> > >
> > > I would like to know the status of this project, if it's still under
> > > active development. I can provide some samples and debugging information
> > > and some help in solving this issue.
> > >
> > > Regards
> >
> > Hi,
> >
> > the project is still maintained, but as I don't have a Genius Vivid III
> > available here on my desk, I could not improve the driver - sorry. I tried
> > to get one of those devices via eBay, but had no success so far :(
> >
> > I guess the calibration stuff need to be setup correctly.
> >
> > Gerhard
> >
> >
> Hi,
> 
> I also have one of these and tried to get it working under linux sometime ago, 
> I tried to capture the data sent to the scanner in windows, but the capture 
> program could not manage it.
> 
> I would be interested in getting it working, I have done some programming and 
> used an i2c capture device with my Adaptec AVC-2410 video capture card and 
> have  now added support for the card to the ivtv project, with some 
> programming assistance from someone with a different Adaptec card.
> 
> Is there a similar method of capturing data (using a separate computer to 
> capture the data) for the parallel port so I could get the data that way?
> 
> Best Regards
> 
> Trev

Hmmm,

I'm not sure if either WINE or VMWare might be an option to do this tracking
here. Probably VMWARE + a tweaked Linux parport driver might do the trick...

My 2 cents
Gerhard

On Wednesday 30 Nov 2005 14:00, Gerhard Jaeger wrote:
> On Wednesday 30 November 2005 13:17, Trev Jackson wrote:
> > On Wednesday 30 Nov 2005 07:26, Gerhard Jaeger wrote:
> > > On Monday 28 November 2005 06:50, Maria Del Monte wrote:
> > > > Hi
> > > >
> > > > I have a parport Genius Colorpage Vivid III and I tried the plustek
> > > > backend with it, but it doesn't work. The resulting images are
> > > > terrible. Searching the list I found a mail [1] from 2 years ago
> > > > describing the same problem.
> > > >
> > > > I would like to know the status of this project, if it's still under
> > > > active development. I can provide some samples and debugging
> > > > information and some help in solving this issue.
> > > >
> > > > Regards
> > >
> > > Hi,
> > >
> > > the project is still maintained, but as I don't have a Genius Vivid III
> > > available here on my desk, I could not improve the driver - sorry. I
> > > tried to get one of those devices via eBay, but had no success so far
> > > :(
> > >
> > > I guess the calibration stuff need to be setup correctly.
> > >
> > > Gerhard
> >
> > Hi,
> >
> > I also have one of these and tried to get it working under linux sometime
> > ago, I tried to capture the data sent to the scanner in windows, but the
> > capture program could not manage it.
> >
> > I would be interested in getting it working, I have done some programming
> > and used an i2c capture device with my Adaptec AVC-2410 video capture
> > card and have  now added support for the card to the ivtv project, with
> > some programming assistance from someone with a different Adaptec card.
> >
> > Is there a similar method of capturing data (using a separate computer to
> > capture the data) for the parallel port so I could get the data that way?
> >
> > Best Regards
> >
> > Trev
>
> Hmmm,
>
> I'm not sure if either WINE or VMWare might be an option to do this
> tracking here. Probably VMWARE + a tweaked Linux parport driver might do
> the trick...
>
> My 2 cents
> Gerhard
>
Hi Gerhard

When I did the i2c monitoring I used the parallel port on a second computer to 
monitor a two wire bus on my video capture card.  I thought I would modify 
the same software (lmilk-0.20 which is released under GNU GPL 2.0) to allow 
me to capture the parallel port data.

I thought I would make up a special cable to connect the computer to the 
scanner with a buffer chip interfacing to the parallel port on a second 
computer to allow me to capture the data.

I have not read through the plustek_pp code yet and so would be gratful if you 
would let me know which pins on the parallel port I need to monitor so I can 
sort out lmilk first and worry about doing something with the data later.

Best Regards

Trev

On Wednesday 30 November 2005 19:17, Trev Jackson wrote:
> On Wednesday 30 Nov 2005 14:00, Gerhard Jaeger wrote:
> > On Wednesday 30 November 2005 13:17, Trev Jackson wrote:
> > > On Wednesday 30 Nov 2005 07:26, Gerhard Jaeger wrote:
> > > > On Monday 28 November 2005 06:50, Maria Del Monte wrote:
> > > > > Hi
> > > > >
> > > > > I have a parport Genius Colorpage Vivid III and I tried the plustek
> > > > > backend with it, but it doesn't work. The resulting images are
> > > > > terrible. Searching the list I found a mail [1] from 2 years ago
> > > > > describing the same problem.
> > > > >
> > > > > I would like to know the status of this project, if it's still
> > > > > under active development. I can provide some samples and debugging
> > > > > information and some help in solving this issue.
> > > > >
> > > > > Regards
> > > >
> > > > Hi,
> > > >
> > > > the project is still maintained, but as I don't have a Genius Vivid
> > > > III available here on my desk, I could not improve the driver -
> > > > sorry. I tried to get one of those devices via eBay, but had no
> > > > success so far
> > > >
> > > > :(
> > > >
> > > > I guess the calibration stuff need to be setup correctly.
> > > >
> > > > Gerhard
> > >
> > > Hi,
> > >
> > > I also have one of these and tried to get it working under linux
> > > sometime ago, I tried to capture the data sent to the scanner in
> > > windows, but the capture program could not manage it.
> > >
> > > I would be interested in getting it working, I have done some
> > > programming and used an i2c capture device with my Adaptec AVC-2410
> > > video capture card and have  now added support for the card to the ivtv
> > > project, with some programming assistance from someone with a different
> > > Adaptec card.
> > >
> > > Is there a similar method of capturing data (using a separate computer
> > > to capture the data) for the parallel port so I could get the data that
> > > way?
> > >
> > > Best Regards
> > >
> > > Trev
> >
> > Hmmm,
> >
> > I'm not sure if either WINE or VMWare might be an option to do this
> > tracking here. Probably VMWARE + a tweaked Linux parport driver might do
> > the trick...
> >
> > My 2 cents
> > Gerhard
>
> Hi Gerhard
>
> When I did the i2c monitoring I used the parallel port on a second computer
> to monitor a two wire bus on my video capture card.  I thought I would
> modify the same software (lmilk-0.20 which is released under GNU GPL 2.0)
> to allow me to capture the parallel port data.
>
> I thought I would make up a special cable to connect the computer to the
> scanner with a buffer chip interfacing to the parallel port on a second
> computer to allow me to capture the data.
>
> I have not read through the plustek_pp code yet and so would be gratful if
> you would let me know which pins on the parallel port I need to monitor so
> I can sort out lmilk first and worry about doing something with the data
> later.
>
> Best Regards
>
> Trev

Hi Trev,

in the end the whole port is used! Data is written always as
8bit to the device. The other direction depends on the mode,
the port is set to. In EPP, also the data port is used, while SPP
uses 4 status lines.

HTH,
Gerhard

> >
> > Hmmm,
> >
> > I'm not sure if either WINE or VMWare might be an option to do this
> > tracking here. Probably VMWARE + a tweaked Linux parport driver might do
> > the trick...
> >
> > My 2 cents
> > Gerhard
>
> Hi Gerhard
>
> When I did the i2c monitoring I used the parallel port on a second computer
> to monitor a two wire bus on my video capture card.  I thought I would
> modify the same software (lmilk-0.20 which is released under GNU GPL 2.0)
> to allow me to capture the parallel port data.
>
> I thought I would make up a special cable to connect the computer to the
> scanner with a buffer chip interfacing to the parallel port on a second
> computer to allow me to capture the data.
>
> I have not read through the plustek_pp code yet and so would be gratful if
> you would let me know which pins on the parallel port I need to monitor so
> I can sort out lmilk first and worry about doing something with the data
> later.
>
> Best Regards
>
> Trev
>
Hi

I'm sorry to report I am having a few problems capturing the data.

The hardware adapter I built is causing sufficient interference to cause 
problems setting up the scanner although the driver does recognize there is a 
scanner there and the printer connected to the scanner works 100% (under 
windows).

I am now concentrating on using WINE, but have so far been having problems 
installing the scanner software, I will however continue trying.

I don't have a copy of VMWARE.

Best Regards

Trev

>
> Hi
>
> I'm sorry to report I am having a few problems capturing the data.
>
> The hardware adapter I built is causing sufficient interference to cause
> problems setting up the scanner although the driver does recognize there is
> a scanner there and the printer connected to the scanner works 100% (under
> windows).
>
> I am now concentrating on using WINE, but have so far been having problems
> installing the scanner software, I will however continue trying.
>
> I don't have a copy of VMWARE.
>
> Best Regards
>
> Trev
>
Hi everyone

I thought I would give a progress report.

I have sort of made some progress, I couldn't get Wine to recognise the 
scanner, so I am now trying QEMU.

I have had to use the CVS version for the parallel port to work, however the 
Windows scanner driver is still not recognizing the scanner.

I have however enabled the debug option on the parallel port driver and have 
captured the data to and from the scanner on loading the driver.

QEMU uses /dev/parport0 and I just need to figure out what is going wrong with 
the data, port reporting it is in the wrong mode or whatever.  Unless it is a 
speed problem hopefully I should be able to sort this out.

I haven't done any parallel port programming so first I need to figure out 
what bits do what, then hopefully I should be able to work out what the data 
below means, this is the start of the capture, which is actually 1216 lines 
long.

addr=0x00 is data
addr=0x01 is status
addr=0x02 is control

parallel: read addr=0x02 val=0x0c
parallel: write addr=0x02 val=0x0c
parallel: write addr=0x00 val=0xaa
parallel: read addr=0x00 val=0xaa
parallel: read addr=0x02 val=0x0c
parallel: write addr=0x02 val=0x08
parallel: write addr=0x02 val=0x0c
parallel: read addr=0x01 val=0xff
parallel: read addr=0x01 val=0xff
parallel: read addr=0x02 val=0x0c
parallel: write addr=0x02 val=0x08
parallel: write addr=0x02 val=0x0c
parallel: read addr=0x01 val=0xff
parallel: write addr=0x02 val=0xc8
parallel: read addr=0x02 val=0x08
parallel: read addr=0x02 val=0x08
parallel: read addr=0x02 val=0x08
parallel: write addr=0x02 val=0xcc
parallel: read addr=0x02 val=0x0c
parallel: read addr=0x01 val=0xff
parallel: read addr=0x02 val=0x0c
parallel: read addr=0x02 val=0x0c
parallel: read addr=0x02 val=0x0c

Best Regards

Trev

Hi

I just thought I would send another progress report.

I am trying to capture data from my scanner by using the Windows scanner 
driver on Windows 98 under Qemu running on Linux.

Qemu does not currently support ECP.

The linux kernel parport_pc driver is buggy and doesn't support ECP properly, 
so adding ECP to Qemu using the current driver setup (/dev/parport0) doesn't 
look promising.

I have tweaked the code to display the extra addresses used by the extended 
parallel port, although currenly no data is written, the Windows "check if 
scanner attached" code produces the following captured data - top only:

parallel: read addr=0x37a val=0x0c
parallel: write addr=0x37a val=0x0c
parallel: write addr=0x378 val=0xaa
parallel: read addr=0x378 val=0xaa
parallel: read addr=0x37a val=0x0c
parallel: write addr=0x37a val=0x08
parallel: write addr=0x37a val=0x0c
parallel: read addr=0x379 val=0xff
parallel: read addr=0x379 val=0xff
parallel: read addr=0x37a val=0x0c
parallel: write addr=0x37a val=0x08
parallel: write addr=0x37a val=0x0c
parallel: read addr=0x379 val=0xff
parallel: write addr=0x37a val=0xc8
parallel: read addr=0x37a val=0x08
parallel: read addr=0x37a val=0x08
parallel: read addr=0x37a val=0x08
parallel: write addr=0x37a val=0xcc
parallel: read addr=0x37a val=0x0c
parallel: read addr=0x379 val=0xff
parallel: read addr=0x37a val=0x0c
parallel: read addr=0x37a val=0x0c
parallel: read addr=0x37a val=0x0c
parallel_test: write addr=0x77a val=0x3a
parallel_test: write addr=0x77a val=0x7a
parallel: read addr=0x378 val=0xaa
parallel: read addr=0x37a val=0x0c
parallel: write addr=0x37a val=0xc4
parallel: write addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: read addr=0x378 val=0x00
parallel: write addr=0x378 val=0x69

I believe I either need to get the linux kernel parport_pc code working or 
sort out how to use DMA addressing in Qemu with the parallel port.

Hopefully I will eventually get there!

Best Regards

Trev

Hi,

On Thursday 15 December 2005 22:41, Trev Jackson wrote:
> Hi
> 
> I just thought I would send another progress report.
> 
> I am trying to capture data from my scanner by using the Windows scanner 
> driver on Windows 98 under Qemu running on Linux.
> 
> Qemu does not currently support ECP.
> 
> The linux kernel parport_pc driver is buggy and doesn't support ECP properly, 
> so adding ECP to Qemu using the current driver setup (/dev/parport0) doesn't 
> look promising.
> 
> I have tweaked the code to display the extra addresses used by the extended 
> parallel port, although currenly no data is written, the Windows "check if 
> scanner attached" code produces the following captured data - top only:
> 
> parallel: read addr=0x37a val=0x0c
> parallel: write addr=0x37a val=0x0c
> parallel: write addr=0x378 val=0xaa
> parallel: read addr=0x378 val=0xaa
> parallel: read addr=0x37a val=0x0c
> parallel: write addr=0x37a val=0x08
> parallel: write addr=0x37a val=0x0c
> parallel: read addr=0x379 val=0xff
> parallel: read addr=0x379 val=0xff
> parallel: read addr=0x37a val=0x0c
> parallel: write addr=0x37a val=0x08
> parallel: write addr=0x37a val=0x0c
> parallel: read addr=0x379 val=0xff
> parallel: write addr=0x37a val=0xc8
> parallel: read addr=0x37a val=0x08
> parallel: read addr=0x37a val=0x08
> parallel: read addr=0x37a val=0x08
> parallel: write addr=0x37a val=0xcc
> parallel: read addr=0x37a val=0x0c
> parallel: read addr=0x379 val=0xff
> parallel: read addr=0x37a val=0x0c
> parallel: read addr=0x37a val=0x0c
> parallel: read addr=0x37a val=0x0c
> parallel_test: write addr=0x77a val=0x3a
> parallel_test: write addr=0x77a val=0x7a
> parallel: read addr=0x378 val=0xaa
> parallel: read addr=0x37a val=0x0c
> parallel: write addr=0x37a val=0xc4
> parallel: write addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: read addr=0x378 val=0x00
> parallel: write addr=0x378 val=0x69
> 
> I believe I either need to get the linux kernel parport_pc code working or 
> sort out how to use DMA addressing in Qemu with the parallel port.
> 
> Hopefully I will eventually get there!
> 

forget about ECP - we don't need that, the Plustek-Backend does not and 
probably won't ever support ECP, it's okay to check EPP or SPP.

You might want to sync your work with the detect code in the backend,
it could be found in plustek-pp_detect.c. The read/write stuff to the 
control register is simply used to initiate read or write sequences.
The definitions are found in plustek-pp_hwdefs.h

HTH
Gerhard