On Fri, Jun 8, 2012 at 2:12 PM, Daniel Beer <dlbeer at gmail.com> wrote: > At Fri, 8 Jun 2012 13:57:50 +0900, Gernot Hassenpflug wrote: >> Thanks for the response, that sounds excellent.
Hi Daniel, > Wireshark can be used to view the files, if that helps. OK. Should be fine. Usually I use a perl script created by the SANE developers, which can give the "plain" output of the commands, and there are some associated programs that can then "build" an image from the sniffed data. But here luckily the issue is not that the protocol is completely unknown, simply that some modes are not yet supported. >> Can you also check the USB ID of the scanner (vendor id and product >> id) for confirmation (otherwise I can get it from the Windows driver >> files myself). > > The ID in the desc file is correct (04a9:1746). This device is mostly > working with the latest git version, but the highest resolution that > works is 600 dpi, and the first scan after power-on usually fails > because SANE doesn't wait for the warm-up (I think). I see, that is easier then. But we have to check---could be a command block bit is incorrect also. I would still appreciate if you can send me the sniffs for the lower-resolution working modes (in color, grayscale and B/W), that way I can make sure the working modes match what is implemented, and then check for differences in the >600dpi modes. Best regards Gernot Hassenpflug
