[sane-devel] HP5590 and scanbd button recognition

[Cesello]

Ops a missing important info:

The patch is for hp5590.c in the git repo 
https://gitlab.com/sane-project/backends.git
tag RELEASE_1_0_25.
I've choose that version  because is the last in debian stable.

Damiano




On 13/03/2018 20:56, Ilia Sotnikov wrote:
> Excellent, thanks Damiano! As a quick step you could send the patch over to 
> the DL and I’ll adapt it if needed. Or you could create a merge request, 
> which would be more elegant though require additional steps.
> ---
>  Ilia Sotnikov
>
>> On Mar 13, 2018, at 21:29, Cesello  wrote:
>>
>> Hi Ilia and Jared
>> I'm just registered to this ML to propose my patch to this back end
>> driver made in the past weekend.
>> And I see someone have my same problem :)
>> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
>> upgraded my system to debian 9 and
>> discovered that scanbd does not works anymore with my scanner. I really
>> need this functionality so I've made
>> modifications to hp5590.c code to export the options .
>> Is a first attempt and the backend called by scanbd threads makes
>> buttons quite  responsive
>> without using a self polling thread.
>> I've made a patch file for debian 9  stable version package (yes but the
>> real patch is for hp5590.c only)
>> If you are interested I can send it (or tell me if I have to release
>> into the repo directly I'm new user here :))
>>
>> Damiano
>>
>>> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>>> Hi,
>>> backend author here - it shouldn't be too much of effort to expose
>>> button status so scanbd can use it. Though haven't gone thru its
>>> documentation to understand requirements. As a technical insight -
>>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>>> button status.
>>> However, I'll seek for a volunteer to test a change as I don't have
>>> access to HW currently.
>>>
>>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>>  wrote:
 Please try the old scanbuttond-backend for this type of scanner - it
 should work. The HP sane backend sadly doesn't support the buttons on
 this scanner.

 Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>> Main question: does the HP 5590 support button presses or am I just 
>> setting this up incorrectly?
>>
>> I'm been successful using scanbd with SANE backends to get scanning 
>> working over my network and locally on the host machine, but I can't 
>> seem to get it to recognize button presses, either running scanbd in 
>> foreground or background.
>>
>> For past testing, it seems that actions defined in scanbd.conf are used 
>> to tie to the backend options? From searching /var/log/syslog, I 
>> expected to track button presses or get some sort of trigger feedback, 
>> and I didn't think I needed an action set up for it.
>>
>> Any help on this one would be much appreciated. Thanks.
>>
>> Jared H
>>
> After a bit more research, it looks like doing this with the SANE backend 
> for HP 5590 is not possible. scanbd is used to tie custom actions to the 
> options available on the scanner. In this case, none of the 10 options 
> seem to return values. They all look to be ones that I designate from 
> some client software.
>
> scanbd: found active option[1] tl-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[2] tl-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[3] br-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[4] br-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[5] mode (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[6] source (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[7] resolution (type: 1) for device 
> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
> (type: 0) for device hp5590:libusb:001:008
> scanbd: found active option[9] wait-for-button (type: 0) for device 
> hp5590:libusb:001:008
> scanbd: found active option[10] preview (type: 0) for device 
> hp5590:libusb:001:008
>
> In this case, it looks like I will have to try the old scanbuttond 
> backends for this, or see if there are optional enhancements for the SANE 
> hp5590 backend.
>
> Jared
>
 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-request at lists.alioth.debian.org
>>>
>>
>> -- 
>> sane-devel mailing list: sane-devel@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>> to 

[sane-devel] HP5590 and scanbd button recognition

[Cesello]

Hi Ilia et all
attached to this message is the patch (hope mailman engine does not
strip it out :))
Basically exports all missing options as buttons and fix a small problem
I've found interacting with scanbd.
I've tested during the weekend and last days (as real user , I missed
this feature for two months after debian upgrade)
and it seems to work.
Sometime the buttons are less responsive (it depends from scheduled
calls to options made by scanbd)
Probably a better approach could be a separate polling thread (maybe a
next version :))
but for now is quite usable.
I've tested with normal sane application too and with scanbm (for
network scanning and desktop shared scanner)
and no problems at all
Sorry for some erratic indentation.. I've used a
"week-end-found-bad-editor" that mixed up tab and blank spaces

Let me know
Happy PI Day ;)

Damiano

On 13/03/2018 20:56, Ilia Sotnikov wrote:
> Excellent, thanks Damiano! As a quick step you could send the patch over to 
> the DL and I’ll adapt it if needed. Or you could create a merge request, 
> which would be more elegant though require additional steps.
> ---
>  Ilia Sotnikov
>
>> On Mar 13, 2018, at 21:29, Cesello  wrote:
>>
>> Hi Ilia and Jared
>> I'm just registered to this ML to propose my patch to this back end
>> driver made in the past weekend.
>> And I see someone have my same problem :)
>> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
>> upgraded my system to debian 9 and
>> discovered that scanbd does not works anymore with my scanner. I really
>> need this functionality so I've made
>> modifications to hp5590.c code to export the options .
>> Is a first attempt and the backend called by scanbd threads makes
>> buttons quite  responsive
>> without using a self polling thread.
>> I've made a patch file for debian 9  stable version package (yes but the
>> real patch is for hp5590.c only)
>> If you are interested I can send it (or tell me if I have to release
>> into the repo directly I'm new user here :))
>>
>> Damiano
>>
>>> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>>> Hi,
>>> backend author here - it shouldn't be too much of effort to expose
>>> button status so scanbd can use it. Though haven't gone thru its
>>> documentation to understand requirements. As a technical insight -
>>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>>> button status.
>>> However, I'll seek for a volunteer to test a change as I don't have
>>> access to HW currently.
>>>
>>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>>  wrote:
 Please try the old scanbuttond-backend for this type of scanner - it
 should work. The HP sane backend sadly doesn't support the buttons on
 this scanner.

 Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
>> Main question: does the HP 5590 support button presses or am I just 
>> setting this up incorrectly?
>>
>> I'm been successful using scanbd with SANE backends to get scanning 
>> working over my network and locally on the host machine, but I can't 
>> seem to get it to recognize button presses, either running scanbd in 
>> foreground or background.
>>
>> For past testing, it seems that actions defined in scanbd.conf are used 
>> to tie to the backend options? From searching /var/log/syslog, I 
>> expected to track button presses or get some sort of trigger feedback, 
>> and I didn't think I needed an action set up for it.
>>
>> Any help on this one would be much appreciated. Thanks.
>>
>> Jared H
>>
> After a bit more research, it looks like doing this with the SANE backend 
> for HP 5590 is not possible. scanbd is used to tie custom actions to the 
> options available on the scanner. In this case, none of the 10 options 
> seem to return values. They all look to be ones that I designate from 
> some client software.
>
> scanbd: found active option[1] tl-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[2] tl-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[3] br-x (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[4] br-y (type: 2) for device 
> hp5590:libusb:001:008
> scanbd: found active option[5] mode (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[6] source (type: 3) for device 
> hp5590:libusb:001:008
> scanbd: found active option[7] resolution (type: 1) for device 
> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
> (type: 0) for device hp5590:libusb:001:008
> scanbd: found active option[9] wait-for-button (type: 0) for device 
> hp5590:libusb:001:008
> scanbd: found active option[10] preview (type: 0) for device 
> hp5590:libusb:001:008
>
> In this case, it looks like I will have to try the old scanbuttond 
> 

Re: [sane-devel] How can I help with Canon Maxify MB2000 series testing?

[Patrick Roncagliolo]

Hi,

I tested pixma version 0.17.46 thru USB. It works.

However, after updating from your PPa, I'm not able to discover my printer
on the network. pixma.conf seems to be ignored, no matter if I set the IP
and multiple port combinations (8610, 8611, 8612, but whit wireshark I see
only requests as broadcast on ports 8610 8612). What could have been
changed? Any hints about some dumb things that I can have forgotten since
last configuration?

Il giorno dom 11 mar 2018 alle ore 12:26 Rolf Bensch 
ha scritto:

> Hi Patrick,
>
> I just added button support for your scanner.
>
> If you're fetching the sources from git you can start testing now.
> Otherwise you must wait 'til tomorrow to get the update from my ppa.
>
> Button support is basicly implemented in standard frontends. You should
> use gscan2pdf to get best results. Or if you're familiar programming
> bash scripts, you can use scanbd
> (https://sourceforge.net/projects/scanbd/). If you like I can provide my
> pixma scripts.
>
> Hope this helps.
>
> Cheers,
> Rolf
>
> Am 05.02.2018 um 12:44 schrieb Patrick Roncagliolo:
> > Feedback on MB2350 button support:
> >
> >> SANE_DEBUG_PIXMA=11 scanimage -A
> >
> > Buttons:
> > --button-update
> > Update button state
> > --button-1  [0] [read-only]
> > Button 1
> > --button-2  [0] [read-only]
> > Button 2
> > --original  [0] [read-only]
> > Type of original to scan
> > --target  [0] [read-only]
> > Target operation type
> > --scan-resolution  [0] [read-only]
> > Scan resolution
> >
> > I noticed that when scanimage is listening for button control, if I go
> > Home->Scan->PC on the scanner touch panel, I see as available target of
> > the scan:
> > - "patrick patrick-desktop"  (if connected by lan)
> > - "Locale (USB)" (if connected by USB)
> >
> > Then, If I press the green color scan button, the pixma backend behaves
> > differently:
> > LAN: logs four rows of data
> > USB: among a low-rate burst of most-zeros logs and warnings, a different
> > line appears when i press the button
> >
> > Note that the two rows "00 00 00 00 01 01 01 01  01 00 01 01 01 01 02
> > 02" appear when I press SCAN in both USB and LAN mode.
> >
> > After pressing the scan button, the scanner displays the message
> > "scanning..." for approx 20 seconds, without any sign of flatbed
> > activity, then returns to the scan UI page without any errors. scanimage
> > continues to listen.
> >
> >> SANE_DEBUG_PIXMA=11 scanimage -d "pixma:MB2300_192.168.1.5"
> > --format=jpeg -p --mode Color --resolution 75 --button-controlled=yes
> >
> > [pixma]  Button-controlled scan mode is enabled.
> > [pixma]  To proceed, press 'SCAN' or 'COLOR' button. To cancel,
> > press 'GRAY' or 'END' button.
> > [pixma] INTR T=4.634 len=64
> >  <<< I PRESSED THE BUTTON >>>
> > [pixma]  :00 00 00 00 01 01 01 01  01 00 01 01 01 01 02 02
> > [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]  0020:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]  0030:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> >
> >> SANE_DEBUG_PIXMA=11 scanimage -d "pixma:04A91779_21CEAB" --format=jpeg
> > -p --mode Color --resolution 75 --button-controlled=yes
> >
> > [pixma]  Button-controlled scan mode is enabled.
> > [pixma]  To proceed, press 'SCAN' or 'COLOR' button. To cancel,
> > press 'GRAY' or 'END' button.
> > [pixma] INTR T=0.768 len=32
> > [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]
> > [pixma] WARNING:send_time() disabled!
> > [pixma] INTR T=1.024 len=32
> > [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]
> > [pixma] WARNING:send_time() disabled!
> > [pixma] INTR T=2.688 len=32
> > [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]
> > [pixma] WARNING:send_time() disabled!
> > [pixma] INTR T=11.136 len=32
> >   <<< I PRESSED THE BUTTON >>>
> > [pixma]  :00 00 00 00 01 01 01 01  01 00 01 01 01 01 02 02
> > [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]
> > [pixma] INTR T=13.696 len=32
> > [pixma]  :00 00 00 01 00 00 00 00  00 00 00 00 00 00 00 00
> > [pixma]  0010:00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
> >
> >
> >
> >
> > Il giorno dom 4 feb 2018 alle ore 18:54 Patrick Roncagliolo
> > > ha scritto:
> >
> > Hi Rolf,
> > MB2350 supports only one-side scan ADF. I used USBPcapCMD.exe to get
> > a USB log from windows (Wireshark on Windows do not support direct
> > USB port capturing AFAIK).
> > I sent you .pcap files of one-sheet and two-sheets scans from Win.
> >
> > Il giorno dom 

Re: [sane-devel] HP5590 and scanbd button recognition

[Wilhelm Meier]

Hi together,

if this is a patch for scanbd and the old scanbuttond backends included
there, please send the patch to this list. I'll be happy to integrate it
into scanbd.

Thanks,
 Wilhelm

Am 13.03.2018 um 19:29 schrieb Cesello:
> Hi Ilia and Jared
> I'm just registered to this ML to propose my patch to this back end
> driver made in the past weekend.
> And I see someone have my same problem :)
> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
> upgraded my system to debian 9 and
> discovered that scanbd does not works anymore with my scanner. I really
> need this functionality so I've made
> modifications to hp5590.c code to export the options .
> Is a first attempt and the backend called by scanbd threads makes
> buttons quite  responsive
> without using a self polling thread.
> I've made a patch file for debian 9  stable version package (yes but the
> real patch is for hp5590.c only)
> If you are interested I can send it (or tell me if I have to release
> into the repo directly I'm new user here :))
> 
> Damiano
> 
> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>> Hi,
>> backend author here - it shouldn't be too much of effort to expose
>> button status so scanbd can use it. Though haven't gone thru its
>> documentation to understand requirements. As a technical insight -
>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>> button status.
>> However, I'll seek for a volunteer to test a change as I don't have
>> access to HW currently.
>>
>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>  wrote:
>>> Please try the old scanbuttond-backend for this type of scanner - it
>>> should work. The HP sane backend sadly doesn't support the buttons on
>>> this scanner.
>>>
>>> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
> Main question: does the HP 5590 support button presses or am I just 
> setting this up incorrectly?
>
> I'm been successful using scanbd with SANE backends to get scanning 
> working over my network and locally on the host machine, but I can't seem 
> to get it to recognize button presses, either running scanbd in 
> foreground or background.
>
> For past testing, it seems that actions defined in scanbd.conf are used 
> to tie to the backend options? From searching /var/log/syslog, I expected 
> to track button presses or get some sort of trigger feedback, and I 
> didn't think I needed an action set up for it.
>
> Any help on this one would be much appreciated. Thanks.
>
> Jared H
>
 After a bit more research, it looks like doing this with the SANE backend 
 for HP 5590 is not possible. scanbd is used to tie custom actions to the 
 options available on the scanner. In this case, none of the 10 options 
 seem to return values. They all look to be ones that I designate from some 
 client software.

 scanbd: found active option[1] tl-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[2] tl-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[3] br-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[4] br-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[5] mode (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[6] source (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[7] resolution (type: 1) for device 
 hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
 (type: 0) for device hp5590:libusb:001:008
 scanbd: found active option[9] wait-for-button (type: 0) for device 
 hp5590:libusb:001:008
 scanbd: found active option[10] preview (type: 0) for device 
 hp5590:libusb:001:008

 In this case, it looks like I will have to try the old scanbuttond 
 backends for this, or see if there are optional enhancements for the SANE 
 hp5590 backend.

 Jared

>>>
>>> --
>>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>>  to sane-devel-request at lists.alioth.debian.org
>>
>>
> 
> 


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] HP5590 and scanbd button recognition

[Ilia Sotnikov]

Excellent, thanks Damiano! As a quick step you could send the patch over to the 
DL and I’ll adapt it if needed. Or you could create a merge request, which 
would be more elegant though require additional steps.
---
 Ilia Sotnikov

> On Mar 13, 2018, at 21:29, Cesello  wrote:
> 
> Hi Ilia and Jared
> I'm just registered to this ML to propose my patch to this back end
> driver made in the past weekend.
> And I see someone have my same problem :)
> I've used hp5590 scanner with scanbuttond for years. Some week ago I've
> upgraded my system to debian 9 and
> discovered that scanbd does not works anymore with my scanner. I really
> need this functionality so I've made
> modifications to hp5590.c code to export the options .
> Is a first attempt and the backend called by scanbd threads makes
> buttons quite  responsive
> without using a self polling thread.
> I've made a patch file for debian 9  stable version package (yes but the
> real patch is for hp5590.c only)
> If you are interested I can send it (or tell me if I have to release
> into the repo directly I'm new user here :))
> 
> Damiano
> 
>> On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
>> Hi,
>> backend author here - it shouldn't be too much of effort to expose
>> button status so scanbd can use it. Though haven't gone thru its
>> documentation to understand requirements. As a technical insight -
>> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
>> button status.
>> However, I'll seek for a volunteer to test a change as I don't have
>> access to HW currently.
>> 
>> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>>  wrote:
>>> Please try the old scanbuttond-backend for this type of scanner - it
>>> should work. The HP sane backend sadly doesn't support the buttons on
>>> this scanner.
>>> 
>>> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
> Main question: does the HP 5590 support button presses or am I just 
> setting this up incorrectly?
> 
> I'm been successful using scanbd with SANE backends to get scanning 
> working over my network and locally on the host machine, but I can't seem 
> to get it to recognize button presses, either running scanbd in 
> foreground or background.
> 
> For past testing, it seems that actions defined in scanbd.conf are used 
> to tie to the backend options? From searching /var/log/syslog, I expected 
> to track button presses or get some sort of trigger feedback, and I 
> didn't think I needed an action set up for it.
> 
> Any help on this one would be much appreciated. Thanks.
> 
> Jared H
> 
 After a bit more research, it looks like doing this with the SANE backend 
 for HP 5590 is not possible. scanbd is used to tie custom actions to the 
 options available on the scanner. In this case, none of the 10 options 
 seem to return values. They all look to be ones that I designate from some 
 client software.
 
 scanbd: found active option[1] tl-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[2] tl-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[3] br-x (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[4] br-y (type: 2) for device 
 hp5590:libusb:001:008
 scanbd: found active option[5] mode (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[6] source (type: 3) for device 
 hp5590:libusb:001:008
 scanbd: found active option[7] resolution (type: 1) for device 
 hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
 (type: 0) for device hp5590:libusb:001:008
 scanbd: found active option[9] wait-for-button (type: 0) for device 
 hp5590:libusb:001:008
 scanbd: found active option[10] preview (type: 0) for device 
 hp5590:libusb:001:008
 
 In this case, it looks like I will have to try the old scanbuttond 
 backends for this, or see if there are optional enhancements for the SANE 
 hp5590 backend.
 
 Jared
 
>>> 
>>> --
>>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>> to sane-devel-request at lists.alioth.debian.org
>> 
>> 
> 
> 
> -- 
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-requ...@lists.alioth.debian.org

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] HP5590 and scanbd button recognition

[Cesello]

Hi Ilia and Jared
I'm just registered to this ML to propose my patch to this back end
driver made in the past weekend.
And I see someone have my same problem :)
I've used hp5590 scanner with scanbuttond for years. Some week ago I've
upgraded my system to debian 9 and
discovered that scanbd does not works anymore with my scanner. I really
need this functionality so I've made
modifications to hp5590.c code to export the options .
Is a first attempt and the backend called by scanbd threads makes
buttons quite  responsive
without using a self polling thread.
I've made a patch file for debian 9  stable version package (yes but the
real patch is for hp5590.c only)
If you are interested I can send it (or tell me if I have to release
into the repo directly I'm new user here :))

Damiano

On 07/03/2018 14:01, hostcc at gmail.com (Ilia Sotnikov) wrote:
> Hi,
> backend author here - it shouldn't be too much of effort to expose
> button status so scanbd can use it. Though haven't gone thru its
> documentation to understand requirements. As a technical insight -
> there is hp5590_read_buttons() function in hp5590_cmds.c that reads
> button status.
> However, I'll seek for a volunteer to test a change as I don't have
> access to HW currently.
>
> On Wed, Mar 7, 2018 at 12:40 AM, Wilhelm Meier
>  wrote:
>> Please try the old scanbuttond-backend for this type of scanner - it
>> should work. The HP sane backend sadly doesn't support the buttons on
>> this scanner.
>>
>> Am 06.03.2018 um 15:46 schrieb Jared Hedegaard:
 Main question: does the HP 5590 support button presses or am I just 
 setting this up incorrectly?

 I'm been successful using scanbd with SANE backends to get scanning 
 working over my network and locally on the host machine, but I can't seem 
 to get it to recognize button presses, either running scanbd in foreground 
 or background.

 For past testing, it seems that actions defined in scanbd.conf are used to 
 tie to the backend options? From searching /var/log/syslog, I expected to 
 track button presses or get some sort of trigger feedback, and I didn't 
 think I needed an action set up for it.

 Any help on this one would be much appreciated. Thanks.

 Jared H

>>> After a bit more research, it looks like doing this with the SANE backend 
>>> for HP 5590 is not possible. scanbd is used to tie custom actions to the 
>>> options available on the scanner. In this case, none of the 10 options seem 
>>> to return values. They all look to be ones that I designate from some 
>>> client software.
>>>
>>> scanbd: found active option[1] tl-x (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[2] tl-y (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[3] br-x (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[4] br-y (type: 2) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[5] mode (type: 3) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[6] source (type: 3) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[7] resolution (type: 1) for device 
>>> hp5590:libusb:001:008 scanbd: found active option[8] extend-lamp-timeout 
>>> (type: 0) for device hp5590:libusb:001:008
>>> scanbd: found active option[9] wait-for-button (type: 0) for device 
>>> hp5590:libusb:001:008
>>> scanbd: found active option[10] preview (type: 0) for device 
>>> hp5590:libusb:001:008
>>>
>>> In this case, it looks like I will have to try the old scanbuttond backends 
>>> for this, or see if there are optional enhancements for the SANE hp5590 
>>> backend.
>>>
>>> Jared
>>>
>>
>> --
>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>  to sane-devel-request at lists.alioth.debian.org
>
>


-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] problem to get SANE work with Hewlett Packard HP Scanjet N6310 scanner

[István Ákos Mórocz]

dear SANE developers,

i am trying to get an HP Scanjet N6310 up & running with linux/SANE
and with Vuescan, so far without success for the last couple of years.
i bought the device back in 2014 in the US and i don't know if it
features any special chip, firmware or whatever, but so much for sure:
it doesn't do a beep with SCANIMAGE, SANE or VUESCAN using SANE 1.0.27
under Slackware 14.2, although it is detected with lsusb and scanimage
-L, and even with XSANE if initiated jointly with an operational
Fujitsu ScanSnap scanner; obviously this will still not work for the
N6310, it just makes it show up in the XSANE GUI.

some years ago i got this N6310 running with some combination of
Vuescan/win8/VMware/Slackware but this is not the case anymore since
all the version changes in the past, and meanwhile i anyway try to go
the direct route using linux pure for all software i use.

i recently re-started to discuss this problem here :

  https://www.linuxquestions.org/questions/showthread.php?p=5830512#post5830512


i will be eagerly waiting for your feedback !  bye, pisti

--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] [janitorial] Alioth → GitLab Migration Update

[Olaf Meeuwissen]

Hi all,

A good month ago, Olaf Meeuwissen wrote:

> Hi all,

So I thought I'd give you an update ;-)

> I have started work on some of the issues on the migration milestone I
> created on GitLab[1].  Of course you can follow what's going on on the
> milestone directly (or the board[2]) but I figured I'd post an update.
>
>   [1]: https://gitlab.com/sane-project/ops/milestones/1
>   [2]: 
> https://gitlab.com/sane-project/ops/boards?milestone_title=Alioth%20%E2%86%92%20GitLab%20Migration

# As for the board, I've been trying out the sane-project *group* board
# as opposed to the ops *project* board so you should now look at
#
#  https://gitlab.com/groups/sane-project/-/boards?milestone_title=%23started
#
# to get a picture of the current state.

> For starters, both the sane-backends and sane-frontends repositories
> on Alioth are now *read-only* and will no longer receive any updates.
> The developers should push to the corresponding repositories at
> GitLab.com from now on.
>
> Pushes to the Alioth repositories will now fail with an error message
> telling you how to switch your local checkout.
>
> # The website project will follow once we have a site set up on the
> # GitLab infra-structure.  In the mean time, all these changes have
> # been reflected in the site's pages.

The website project has followed suit and the Alioth repository is now
read-only.  This completes the transfer of *all* of the SANE project's
git repositories from Alioth to GitLab.com.

> All SANE project members on Alioth have received invitations to join the
> project on GitLab.com and a bit shy of half have already accepted.  The
> rest will get another nudge soon.  Please note that only project members
> can push to GitLab.com.

On this front, close to three quarters of the Alioth members have now
joined (or declined to join) the project on GitLab.com.  The remaining
five have received several nudges by now and any outstanding invitations
will be closed after 2018-03-21 00:00 UTC.

# The initial invitation was issued on 2018-02-01, BTW.

> Release artifacts, [...]

Nothing changed in this department.

> In the mean time, I'm also looking at the possibility of migrating the
> Tracker items we have at Alioth[5].  It doesn't look easy, but someone
> at GitLab.com (the Director of Strategic Partnerships) has contacted me
> with an offer to help.  I'm not holding my breath but any help in this
> area is welcome.
>
>   [5]: https://gitlab.com/sane-project/ops/issues/10

I have been poking around in the FusionForge source code that powers
Alioth and found an interesting commit that may make migrating Alioth
issues a breeze.  Well, almost at least.  I'm waiting for the Alioth
maintainers to apply a patch so I can test.  Details are in the issue
linked to above.

> If there is anything you think that's missing from the milestone[1] or
> find fault with any of the attached release artifacts[3][4], feel free
> to submit a new issue[6].  You don't have to be a SANE Project member.
> Simply login to GitLab.com[7] and create a new issue[6].
>
>   [6]: https://gitlab.com/users/sign_in
>   [7]: https://gitlab.com/sane-project/ops/issues/new

This stands without change.

> Next up on my list is the website[8].
>
>   [8]: https://gitlab.com/sane-project/ops/issues/7

This issue has been closed after a good deal of mucking about with the
links in the webpages so they would work on Alioth and GitLab.  While
working on this and testing stuff, I even got myself black-listed and
could not browse the site on Alioth for a while :-/
There is now a static SANE Project website that you can visit on

  https://sane-project.gitlab.io/website/

It should be identical to the one on Alioth.  The Scanner Search
Engine[9] will break as soon as Alioth goes off-line, though.

 [9]: https://sane.alioth.debian.org/cgi-bin/driver.pl

I have asked[10] Allan to make the project's domain (sane-project.org)
point to the GitLab hosted website.

 [10]: https://gitlab.com/sane-project/ops/boards?=

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join

-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org