Thank you Ralph! 

Yeah, this might be a bit of an undertaking.

Maybe I'll start by figuring out the best capture method for the USB traffic.

I usually use the scanner currently on a windows guest running under KVM/QEMU on Linux. Any suggestions?

Regards, Erik

Sent from my iPhone

On Sep 30, 2024, at 00:36, Ralph Little <[email protected]> wrote:


Hi,

On Sun, Sep 29, 2024 at 5:47 PM Erik Beck of Tahoma <[email protected]> wrote:
It might actually be based on a GL126 and an AD9826; Here's some string
analysis:

data1.hdr: DRV_U_GL126_A31
data1.hdr: AD13719F-9FE1-46C2-AB8B-716B5F256BF8:ScndrvU_GL126_A31
data1.hdr: Ver:1.0.0.5_ (12/08/2014)_(## GL126_Plustek_A120
12clk,AD9826) PRODUCT.dat: AsicID = GL126


AFAIK, the GL126 scanner-on-a-chip doesn't have a publicly available datasheet.
That makes is quite difficult to figure out how to support it.

The easiest method for getting a basic scan is to capture traffic, and replicate it back to the scanner.
The harder part though is to figure out how to extract the details necessary to determine how scan area is determined etc which vary with each scan.
To do a good job, you also need to figure out how to do calibration to an acceptable degree to get a decent scan.
This typically involves taking test scans from a target area outside of the normal scan area, formulating adjustment tables, feeding them back to the scanner, and iterating until an acceptable result is obtained.

It's not for the faint of heart that's for sure.

Cheers,
Ralph

Reply via email to