<div dir="ltr"><div dir="ltr">Hi,<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 2, 2024 at 6:38 AM Ove Laurum <<a href="mailto:laurum.tech@gmail.com">laurum.tech@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello.<div><br></div><div>I am new to sane but hope to find some guidance on how I can help adding this printer to sane supported devices.</div><div><br></div><div>I am trying to use a scanner "Avision AV50F plus" on Linux (Ubuntu).</div><div>I do not see it listed as a supported scanner by sane.</div><div>Also after installing xsane it is not recognised, see command line output at the end of the mail.</div><div>The scanner works fine on Windows with Avision driver and SW and Button Manager SW.</div><div>I have attached screenshots from Windows Device Manager.</div><div>I also attached a photo of the circuit board of the scanner as well as a pdf product sheet of the scanner.</div><div><br></div><div>I would be grateful for any advice on:</div><div>a: has anybody else tried, failed, succeeded in adding support, if so what is your experience?</div><div>b: what is the recommended process for me to follow?</div><div>c: how do I know if this can be added to an existing backend, or if I need to write a new backend.</div><div>d: any advice on how to trace the driver/scanner communication on windows to reverse engineer the protocol?</div><div></div><div><br></div></div></blockquote><div><br></div><div>Many Avision devices use a specific prococol supported by the avision backend.</div><div>It might be worthwhile adding the identity of this scanner to the backend and having a look at the diagnostic output set using the SANE_DEBUG_AVISION environmental variable set to some highish number (e.g. 50). Early on, IIRC, the backend queries the device for capabilities. If the device gives some kind of proper response to this request then that would be the best place to start.</div><div><br></div><div>But it is not for the faint of heart.</div><div><br></div><div>Cheers,</div><div>Ralph<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>Looking forward to contributing to sane.</div><div>Kind regards </div><div>Ove.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div>Command Line Output:</div><div><br></div><div>$ sudo sane-find-scanner<br><br> # sane-find-scanner will now attempt to detect your scanner. If the<br> # result is different from what you expected, first make sure your<br> # scanner is powered up and properly connected to your computer.<br><br> # No SCSI scanners found. If you expected something different, make sure that<br> # you have loaded a kernel SCSI driver for your SCSI adapter.<br><br>found possible USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan], chip=GL848+) at libusb:001:004<br>found possible USB scanner (vendor=0x0638 [AVISION], product=0x2b6a [AV50F Plus]) at libusb:001:003<br> # Your USB scanner was (probably) detected. It may or may not be supported by<br> # SANE. Try scanimage -L and read the backend's manpage.<br><br> # Not checking for parallel port scanners.<br><br> # Most Scanners connected to the parallel port or other proprietary ports<br> # can't be detected by this program.<br><br></div><div>$ sudo scanimage -L<br>device `genesys:libusb:001:004' is a Canon LiDE 220 flatbed scanner<br><br></div><div>$ lsusb<br>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet<br>Bus 001 Device 003: ID 0638:2b6a Avision, Inc. AV50F Plus<br>Bus 001 Device 004: ID 04a9:190f Canon, Inc. CanoScan LiDE 220<br>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br></div></div>
</blockquote></div></div>