On 16/05/2013 16:27, Aaron Silver wrote:
> Thank you for responding so quickly!
>
> My main desktop is a Windows 7 machine, so usbsniff, and SnoopyPro and
> such haven't worked for me. I did get USBLyzer working, and I can make
> the log files from that available.
>
> Since the file is 13M I figured I'd make it available for you to download:
>
> https://docs.google.com/file/d/0BzGkOUvLpLAEUndRc3RJT0NWNmM/edit?usp=sharing
>
> I had the scanner unplugged from the USB port, I started the log, I
> plugged in the scanner, then initiated a full color preview, and then
> stopped the log.
>
> Any more questions please feel free to ask, and thank you very much
> for any help you can provide!
>
> Aaron Silver
>
Hello,
I have downloaded the file. I don't know what I can extract from
it, since it is a format my dev scripts don't handle. It'll take me
quite some time to figure out something.
Regards,
Stef
>
> On Wed, May 15, 2013 at 3:38 PM, Stef <stef.dev at free.fr
> <mailto:stef.dev at free.fr>> wrote:
>
> On 15/05/2013 00:54, Aaron Silver wrote:
>
> I've got a Mustek A3 1200S flatbed scanner that I'd like to
> use with XSANE. The sane-find-scanner reported the USB ID as
> 0x055f and the Device ID as 0x0502. It thought the scanner had
> a GL848+ chip, but when I opened the case I see a chip with
> GL128 stamped on it.
>
> I had USBlyzer listen while I did a couple of scans (one full
> A3 size, and one of the lower half of the page), but I don't
> know what the next step is or how to take it. If someone can
> walk me through it I'd be happy to do as much of the work as I
> can, but I'm also willing (and some would say very able) to
> play dumb monkey and feed someone knowledgeable the
> information they ask for.
>
> Thanks in advance,
>
> Aaron Silver
>
>
>
>
>
> Hello,
>
> I can't find the datasheet for this chip, so I can't really
> tell how different it is from already supported genesys chip. But
> even with the datasheet, it is not convenient to develop without a
> test scanner. A few seconds test can turn in a few hours (even
> days) long, because of getting code changes applied remotely, then
> executed and getting debug information back. Programming for these
> scanner involve quite a lot of trial and error, even if you have
> the datasheet.
>
> However, you can still post an usb snoop log of a color
> preview scan, just to get some idea on how this scanner work.
>
> Regards,
> Stef
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130516/cef97b3b/attachment.html>
