[sane-devel] Help decoding Minolta Dimage Scan Dual II USB protocol

[Giovanni Cappellotto]

You’re right, I was using avision.

Thanks for the suggestion, I guess I could try that.

Last time I was hacking the avision backed, I remember the source code had
a lot of additional complexity because it was supporting tens of different
scanners. Supposedly some changes for supporting a particular scanner broke
the support for Minolta Dimage.

I’m wondering if you have docs or other resources I can use to reverse
engineer the scanner protocol from the logs I can collect from the original
windows driver.

For instance I think I identified 3 different endpoints looking at the
sniffer logs, but I’m not sure their meaning. 0x01 seems some kind of
command endpoint, 0x83 receives and sends a lot of information, 0x82
receives and responds with zeroes and seems like an endpoint used to
complete a command.

Maybe I can share the full log I collected and get help to recreate a
backend specific for Minolta Dimage?

On Wed, Nov 23, 2022 at 12:40 PM Ralph Little <skelband at gmail.com> wrote:

> Hi,
>
> On Wed, Nov 23, 2022 at 6:31 AM Giovanni Cappellotto <potomak84 at gmail.com>
> wrote:
>
>> Hello,
>>
>> In 2017 I used sane on Mac OS X to scan films using a Minolta Dimage Scan
>> Dual II. When I used sane again in 2020 it didn't work anymore. I tried to
>> contribute to the project to fix the backend for my scanner. I was able to
>> successfully scan a single frame at a time, but I lacked the knowledge to
>> completely fix the issue.
>>
>
> If you are using SANE then there are currently some issues when scanning
> via USB on MacOS related to forking + libusb. Hopefully we can sort this
> out soon.
>
> When you successfully scanned in 2017, you would most likely have been
> using the avision backend since this is an avision device.
> You could try again with SANE and generate some diagnostic output and send
> that to us by setting SANE_DEBUG_AVISION=10 environment variable.
>
> If it is related to the fork/libusb issue, you could try the fix that
> someone suggested here:
> https://gitlab.com/sane-project/backends/-/issues/153#note_1144447613
>
> Cheers,
> Ralph
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/sane-devel/attachments/20221123/29a8aae7/attachment.htm>