[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Wed, 2012-10-31 at 08:47 -0400, m. allan noah wrote:

> >> If you change the stuff, do you mind also changing the option-type of
> >> button-1/-2 to SANE_TYPE_BUTTON (it is actually SANE_TYPE_INT)?
> >>
> > I am still looking at this. For now I have been able to wrap my brain
> > around how to read a button option. Do I understand you correctly that a
> > get operation on a button returns an integer. The documentation does
> > only state that a button has no value. I see that some backends do
> > return a value for type button, others don't. GIven the docuemntation I
> > am not sure. I will wait for others to comment before I make changes
> > (they would be fairly simple).
> >
> >> Is anyone aware of similar operation (setting one option for querying
> >> another) in other backends (in that case I would consider updating
> >> scanbd to suppport such a schema as well)?
> >>
> > For the pixma backend they are not required anymore
> >
> >
> > kind regards, Louis
> >
> 
> Sounds like a good change. Unfortunately, the sane standard is a
> little weak on buttons, so backend authors have to guess. I would say
> that button/event reading code should not expect the type to be
> SANE_TYPE_BUTTON, as some sensors will be able to give integer values.
> 
> allan
Hello all,
Strictly speaking accoding to the sane abi doc (sane.ps) buttons do not
have a value (Page 20: An option of this type has no value. Instead,
setting an option of this type has an option-specific side effect.
 
Page 21: SANE_TYPE_BUTTON, SANE_TYPE_GROUP: the option size is ignored

If a BUTTON can RETURN a value, we need to correct both places:
P20 only talks about SETTING a value, but does not discuss GETTING the
button, but P21 seems to suggest that reading is pointless.

to me this looks as if the button-type is only meant to SET a (boolean)
option and never can be read. But then it has only a subset of
characteristics of the BOOL type (it is actually a boolean with implicit
encoding: leaving it out indicates a false, sending the option, but no
value, means a true, yes I come from a background where ASN.1 is used). 

To me it still looks as if a boolean or integer encoding are  most
appropriate. So I prefer to leave the buttons as integers (although they
are now strictly speaking booleans, as I moved the original and target
parameters to own options

Comments?

Kind regards, Louis

[sane-devel] Canon Mx 700 - Scanbuttons

[m. allan noah]

On Wed, Oct 31, 2012 at 4:51 PM, Louis Lagendijk  wrote:
> On Wed, 2012-10-31 at 08:47 -0400, m. allan noah wrote:
>
>> >> If you change the stuff, do you mind also changing the option-type of
>> >> button-1/-2 to SANE_TYPE_BUTTON (it is actually SANE_TYPE_INT)?
>> >>
>> > I am still looking at this. For now I have been able to wrap my brain
>> > around how to read a button option. Do I understand you correctly that a
>> > get operation on a button returns an integer. The documentation does
>> > only state that a button has no value. I see that some backends do
>> > return a value for type button, others don't. GIven the docuemntation I
>> > am not sure. I will wait for others to comment before I make changes
>> > (they would be fairly simple).
>> >
>> >> Is anyone aware of similar operation (setting one option for querying
>> >> another) in other backends (in that case I would consider updating
>> >> scanbd to suppport such a schema as well)?
>> >>
>> > For the pixma backend they are not required anymore
>> >
>> >
>> > kind regards, Louis
>> >
>>
>> Sounds like a good change. Unfortunately, the sane standard is a
>> little weak on buttons, so backend authors have to guess. I would say
>> that button/event reading code should not expect the type to be
>> SANE_TYPE_BUTTON, as some sensors will be able to give integer values.
>>
>> allan
> Hello all,
> Strictly speaking accoding to the sane abi doc (sane.ps) buttons do not
> have a value (Page 20: An option of this type has no value. Instead,
> setting an option of this type has an option-specific side effect.
>
> Page 21: SANE_TYPE_BUTTON, SANE_TYPE_GROUP: the option size is ignored
>
> If a BUTTON can RETURN a value, we need to correct both places:
> P20 only talks about SETTING a value, but does not discuss GETTING the
> button, but P21 seems to suggest that reading is pointless.
>
> to me this looks as if the button-type is only meant to SET a (boolean)
> option and never can be read. But then it has only a subset of
> characteristics of the BOOL type (it is actually a boolean with implicit
> encoding: leaving it out indicates a false, sending the option, but no
> value, means a true, yes I come from a background where ASN.1 is used).
>
> To me it still looks as if a boolean or integer encoding are  most
> appropriate. So I prefer to leave the buttons as integers (although they
> are now strictly speaking booleans, as I moved the original and target
> parameters to own options
>
> Comments?
>

My comment is that the SANE_TYPE_BUTTON does not describe a hardware
button. It describes a software button, like 'eject paper' or some
such.

allan
-- 
"The truth is an offense, but not a sin"

[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Sun, 2012-10-28 at 06:15 +0100, Wilhelm wrote:
> Am 27.10.2012 19:34, schrieb Louis Lagendijk:
> > On Sat, 2012-10-27 at 12:25 -0400, m. allan noah wrote:
> >>> I finally found some time to dig into the backend to see what it does
> >>> and how to use it (too many other things to do and been ill for a
> >>> while). I now understand how things work.
> >>>
> >>> The button-1 and button-2 options are set when sane_control_option() is
> >>> called for option button_update with action SANE_ACTION_SET_VALUE.
> >>> SANE_ACTION_SET_VALUE button_update is used to poll the scanner and set
> >>> button-1 and button-2. But scanbd does not support
> >>> SANE_ACTION_SET_VALUE.
> >>>
> >>
> >> The sane standard does not really cover the proper implementation of
> >> buttons, but I would say that the mechanism you described is weird,
> >> and should be changed. Reading the value of the button should do
> >> whatever is required to get the value from the scanner.
> >
> > I agree, it took me a while to get my brain around it. Sending a setting
> > command for one option to initiate a read cache action is funny indeed.
> >
> > But do we not run the risk that changes will break other applications
> > that rely on the current, weird behavior?
> >
> >> It should not
> >> be required to set another option to update the value of the button.
> >> In the case where the value for all buttons is requested in one
> >> command to the scanner, the backend should cache the values as
> >> required. The fujitsu backend uses this scheme, perhaps the code could
> >> be adapted.
> >
> > Well, the caching is done when button_update is set. It should indeed be
> > sufficient to read the buttons and cache the result at that point in
> > time.
> > I will adapt the code accordingly, but leave the button_update stuff in
> > so we do not break anything for other users.
> 
> Does that mean, that reading the button value will reflect the button 
> changes in the future *without* setting the button-update option?
> 
I have the changes in my local git repository and will push these
shortly after some more testing.

Yes, the button status is now updated directly when the option is read.
I have actually (as suggested by Allan) implemented a caching mechanism
that caches all options and where where all options are e-read when an
option is read a second time.
 
> If you change the stuff, do you mind also changing the option-type of 
> button-1/-2 to SANE_TYPE_BUTTON (it is actually SANE_TYPE_INT)?
> 
I am still looking at this. For now I have been able to wrap my brain
around how to read a button option. Do I understand you correctly that a
get operation on a button returns an integer. The documentation does
only state that a button has no value. I see that some backends do
return a value for type button, others don't. GIven the docuemntation I
am not sure. I will wait for others to comment before I make changes
(they would be fairly simple). 

> Is anyone aware of similar operation (setting one option for querying 
> another) in other backends (in that case I would consider updating 
> scanbd to suppport such a schema as well)?
> 
For the pixma backend they are not required anymore


kind regards, Louis

[sane-devel] Canon Mx 700 - Scanbuttons

[m. allan noah]

On Wed, Oct 31, 2012 at 8:26 AM, Louis Lagendijk  wrote:
> On Sun, 2012-10-28 at 06:15 +0100, Wilhelm wrote:
>> Am 27.10.2012 19:34, schrieb Louis Lagendijk:
>> > On Sat, 2012-10-27 at 12:25 -0400, m. allan noah wrote:
>> >>> I finally found some time to dig into the backend to see what it does
>> >>> and how to use it (too many other things to do and been ill for a
>> >>> while). I now understand how things work.
>> >>>
>> >>> The button-1 and button-2 options are set when sane_control_option() is
>> >>> called for option button_update with action SANE_ACTION_SET_VALUE.
>> >>> SANE_ACTION_SET_VALUE button_update is used to poll the scanner and set
>> >>> button-1 and button-2. But scanbd does not support
>> >>> SANE_ACTION_SET_VALUE.
>> >>>
>> >>
>> >> The sane standard does not really cover the proper implementation of
>> >> buttons, but I would say that the mechanism you described is weird,
>> >> and should be changed. Reading the value of the button should do
>> >> whatever is required to get the value from the scanner.
>> >
>> > I agree, it took me a while to get my brain around it. Sending a setting
>> > command for one option to initiate a read cache action is funny indeed.
>> >
>> > But do we not run the risk that changes will break other applications
>> > that rely on the current, weird behavior?
>> >
>> >> It should not
>> >> be required to set another option to update the value of the button.
>> >> In the case where the value for all buttons is requested in one
>> >> command to the scanner, the backend should cache the values as
>> >> required. The fujitsu backend uses this scheme, perhaps the code could
>> >> be adapted.
>> >
>> > Well, the caching is done when button_update is set. It should indeed be
>> > sufficient to read the buttons and cache the result at that point in
>> > time.
>> > I will adapt the code accordingly, but leave the button_update stuff in
>> > so we do not break anything for other users.
>>
>> Does that mean, that reading the button value will reflect the button
>> changes in the future *without* setting the button-update option?
>>
> I have the changes in my local git repository and will push these
> shortly after some more testing.
>
> Yes, the button status is now updated directly when the option is read.
> I have actually (as suggested by Allan) implemented a caching mechanism
> that caches all options and where where all options are e-read when an
> option is read a second time.
>
>> If you change the stuff, do you mind also changing the option-type of
>> button-1/-2 to SANE_TYPE_BUTTON (it is actually SANE_TYPE_INT)?
>>
> I am still looking at this. For now I have been able to wrap my brain
> around how to read a button option. Do I understand you correctly that a
> get operation on a button returns an integer. The documentation does
> only state that a button has no value. I see that some backends do
> return a value for type button, others don't. GIven the docuemntation I
> am not sure. I will wait for others to comment before I make changes
> (they would be fairly simple).
>
>> Is anyone aware of similar operation (setting one option for querying
>> another) in other backends (in that case I would consider updating
>> scanbd to suppport such a schema as well)?
>>
> For the pixma backend they are not required anymore
>
>
> kind regards, Louis
>

Sounds like a good change. Unfortunately, the sane standard is a
little weak on buttons, so backend authors have to guess. I would say
that button/event reading code should not expect the type to be
SANE_TYPE_BUTTON, as some sensors will be able to give integer values.

allan
-- 
"The truth is an offense, but not a sin"

[sane-devel] Canon Mx 700 - Scanbuttons

[Wilhelm]

Am 27.10.2012 19:34, schrieb Louis Lagendijk:
> On Sat, 2012-10-27 at 12:25 -0400, m. allan noah wrote:
>>> I finally found some time to dig into the backend to see what it does
>>> and how to use it (too many other things to do and been ill for a
>>> while). I now understand how things work.
>>>
>>> The button-1 and button-2 options are set when sane_control_option() is
>>> called for option button_update with action SANE_ACTION_SET_VALUE.
>>> SANE_ACTION_SET_VALUE button_update is used to poll the scanner and set
>>> button-1 and button-2. But scanbd does not support
>>> SANE_ACTION_SET_VALUE.
>>>
>>
>> The sane standard does not really cover the proper implementation of
>> buttons, but I would say that the mechanism you described is weird,
>> and should be changed. Reading the value of the button should do
>> whatever is required to get the value from the scanner.
>
> I agree, it took me a while to get my brain around it. Sending a setting
> command for one option to initiate a read cache action is funny indeed.
>
> But do we not run the risk that changes will break other applications
> that rely on the current, weird behavior?
>
>> It should not
>> be required to set another option to update the value of the button.
>> In the case where the value for all buttons is requested in one
>> command to the scanner, the backend should cache the values as
>> required. The fujitsu backend uses this scheme, perhaps the code could
>> be adapted.
>
> Well, the caching is done when button_update is set. It should indeed be
> sufficient to read the buttons and cache the result at that point in
> time.
> I will adapt the code accordingly, but leave the button_update stuff in
> so we do not break anything for other users.

Does that mean, that reading the button value will reflect the button 
changes in the future *without* setting the button-update option?

If you change the stuff, do you mind also changing the option-type of 
button-1/-2 to SANE_TYPE_BUTTON (it is actually SANE_TYPE_INT)?

Is anyone aware of similar operation (setting one option for querying 
another) in other backends (in that case I would consider updating 
scanbd to suppport such a schema as well)?

Thanks,

-- 
Wilhelm

[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Sat, 2012-10-27 at 12:25 -0400, m. allan noah wrote:
> > I finally found some time to dig into the backend to see what it does
> > and how to use it (too many other things to do and been ill for a
> > while). I now understand how things work.
> >
> > The button-1 and button-2 options are set when sane_control_option() is
> > called for option button_update with action SANE_ACTION_SET_VALUE.
> > SANE_ACTION_SET_VALUE button_update is used to poll the scanner and set
> > button-1 and button-2. But scanbd does not support
> > SANE_ACTION_SET_VALUE.
> >
> 
> The sane standard does not really cover the proper implementation of
> buttons, but I would say that the mechanism you described is weird,
> and should be changed. Reading the value of the button should do
> whatever is required to get the value from the scanner. 

I agree, it took me a while to get my brain around it. Sending a setting
command for one option to initiate a read cache action is funny indeed.

But do we not run the risk that changes will break other applications
that rely on the current, weird behavior? 

> It should not
> be required to set another option to update the value of the button.
> In the case where the value for all buttons is requested in one
> command to the scanner, the backend should cache the values as
> required. The fujitsu backend uses this scheme, perhaps the code could
> be adapted.

Well, the caching is done when button_update is set. It should indeed be
sufficient to read the buttons and cache the result at that point in
time.
I will adapt the code accordingly, but leave the button_update stuff in
so we do not break anything for other users.

Thanks for your valuable feedback
Louis

[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Wed, 2012-09-26 at 07:58 +0200, Wilhelm wrote:
> Am 25.09.2012 19:54, schrieb Nelson:
> >>> On Sat, 2012-08-11 at 20:22 +0200, Louis Lagendijk wrote:
> >>>
>  hello Nelson/ list,
> >>>
> >>> As I was working on the scan button support, I found out that my
> >>> multi-function (MP980) does support IPv6 (I completely forgot). So I
> >>> have added IPv6 support for the pixma backend. The changes for button
> >>> support and IPv6 are now in git. Please test
> >>> Kind regards, Louis
> >>>
> >>>
> >>> --
> >>> 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
> >>
> >> Hey Louis,
> >> very good job. My scanner works now by using the buttons.
> >>
> >> --
> >> 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
> > Hey Louis,
> > by using sane-backend(last git) with comandline, my scanner works with the 
> > buttons. E.g. scanimage buttoncontrolled=yes 
> >
> >
> > But scanbd can't read the buttonstatus. It's a bug or not implemented? All 
> > the options are available, but scanbd shows no action by using the buttons.
> 
> just to clearify: scanbd can read the buttons (e.g. a button-option with 
> name "button-1") but the value of this particular option never changes 
> when the user presses a button. A quick look in to the pixma 
> backend-sources suggests that querying the button values isn't supported 
> ... ?

I finally found some time to dig into the backend to see what it does
and how to use it (too many other things to do and been ill for a
while). I now understand how things work. 

The button-1 and button-2 options are set when sane_control_option() is
called for option button_update with action SANE_ACTION_SET_VALUE.
SANE_ACTION_SET_VALUE button_update is used to poll the scanner and set
button-1 and button-2. But scanbd does not support
SANE_ACTION_SET_VALUE.
 
My patch from a week ago was not correct as it ignores how the buttons
are supposed to be used. I am looking into the best way to solve this.

I need to check, but I seem to recall that there is an indication in the
USB protocol that indicates what option (save, pdf, attach to email etc)
was chosen. If this is true, I may try to add an option for that as
well.

Kind regards, Louis

[sane-devel] Canon Mx 700 - Scanbuttons

[m. allan noah]

> I finally found some time to dig into the backend to see what it does
> and how to use it (too many other things to do and been ill for a
> while). I now understand how things work.
>
> The button-1 and button-2 options are set when sane_control_option() is
> called for option button_update with action SANE_ACTION_SET_VALUE.
> SANE_ACTION_SET_VALUE button_update is used to poll the scanner and set
> button-1 and button-2. But scanbd does not support
> SANE_ACTION_SET_VALUE.
>

The sane standard does not really cover the proper implementation of
buttons, but I would say that the mechanism you described is weird,
and should be changed. Reading the value of the button should do
whatever is required to get the value from the scanner. It should not
be required to set another option to update the value of the button.
In the case where the value for all buttons is requested in one
command to the scanner, the backend should cache the values as
required. The fujitsu backend uses this scheme, perhaps the code could
be adapted.

allan
-- 
"The truth is an offense, but not a sin"

[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Fri, 2012-10-19 at 07:55 +0200, Nelson wrote:
> > 
> > Am 25.09.2012 19:54, schrieb Nelson:


> Hey list/Louis,
> 
> here is installation of scanbd with my config. I'm not sure whether the 
> installation works.
> 
> Thanks to list,
> Nelson
> 
hello Nelson
I have cooked up a quick patch that should add button reading support to
the pixma backend. I have not yet been able to  test it. I hurt my arm
this weekend so will not be able to test it quickly as I originally
planned. I will not commit it to git until it is tested. Please feel
free to test and report. I use the control_option routine to trigger a
read of the status from the scanner as normally that is not done. 
The patch is not yet complete (the mapping of the buttons needs to be
changed to match the one used in setting the buttons) but it should be
possible to get some results.

Regards, Louis

P
-- next part --
A non-text attachment was scrubbed...
Name: button-options.patch
Type: text/x-patch
Size: 767 bytes
Desc: not available
URL: 

[sane-devel] Canon Mx 700 - Scanbuttons

[Nelson]

> 
> Am 25.09.2012 19:54, schrieb Nelson:
 On Sat, 2012-08-11 at 20:22 +0200, Louis Lagendijk wrote:
 
> hello Nelson/ list,
> I finally managed to find some time to work on the bjnp button scan
> support for the pixma backend. I got it working, although I am not
> really sure that it does not contain faults in some corner cases. As we
> are pretty close to the 1.0.23 release of sane, I will not yet commit
> the changes to git. It took me quite a while to figure out how the
> protocol works, so it has taken quite some time before I got something
> working.
> 
> Please let me know if you are in a hurry to test before the 1.0.23
> release is done. If so, I can mail you a patch to apply on top of the
> current git. I have only tested this with xsane, as I did not have time
> to setup scanbd, sorry. It anyhow looks as if sane and printing (bjnp
> backend for cups) can access the device at the same time: I could print
> a page while xsane was waiting for a button to be pressed. When the
> printjob was done, I was able to press the scan button again.
> 
> Louis
> P.s. I will push my changes to git as soon as 1.0.23 is released
 
 As I was working on the scan button support, I found out that my
 multi-function (MP980) does support IPv6 (I completely forgot). So I
 have added IPv6 support for the pixma backend. The changes for button
 support and IPv6 are now in git. Please test
 Kind regards, Louis
 
 
 --
 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
>>> 
>>> Hey Louis,
>>> very good job. My scanner works now by using the buttons.
>>> 
>>> --
>>> 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
>> Hey Louis,
>> by using sane-backend(last git) with comandline, my scanner works with the 
>> buttons. E.g. scanimage buttoncontrolled=yes 
>> 
>> 
>> But scanbd can't read the buttonstatus. It's a bug or not implemented? All 
>> the options are available, but scanbd shows no action by using the buttons.
> 
> just to clearify: scanbd can read the buttons (e.g. a button-option with name 
> "button-1") but the value of this particular option never changes when the 
> user presses a button. A quick look in to the pixma backend-sources suggests 
> that querying the button values isn't supported ... ?
> 
>> 
>> Kind regards?
>> Nelson
>> 
> 
> 
> -- 
> Wilhelm
> 
> 
> -- 
> 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
Hey list/Louis,

here is installation of scanbd with my config. I'm not sure whether the 
installation works.

Thanks to list,
Nelson

-- next part --
A non-text attachment was scrubbed...
Name: scanbd_install.tgz
Type: application/octet-stream
Size: 46072 bytes
Desc: not available
URL: 

[sane-devel] Canon Mx 700 - Scanbuttons

[Wilhelm]

Am 25.09.2012 19:54, schrieb Nelson:
>>> On Sat, 2012-08-11 at 20:22 +0200, Louis Lagendijk wrote:
>>>
 hello Nelson/ list,
 I finally managed to find some time to work on the bjnp button scan
 support for the pixma backend. I got it working, although I am not
 really sure that it does not contain faults in some corner cases. As we
 are pretty close to the 1.0.23 release of sane, I will not yet commit
 the changes to git. It took me quite a while to figure out how the
 protocol works, so it has taken quite some time before I got something
 working.

 Please let me know if you are in a hurry to test before the 1.0.23
 release is done. If so, I can mail you a patch to apply on top of the
 current git. I have only tested this with xsane, as I did not have time
 to setup scanbd, sorry. It anyhow looks as if sane and printing (bjnp
 backend for cups) can access the device at the same time: I could print
 a page while xsane was waiting for a button to be pressed. When the
 printjob was done, I was able to press the scan button again.

 Louis
 P.s. I will push my changes to git as soon as 1.0.23 is released
>>>
>>> As I was working on the scan button support, I found out that my
>>> multi-function (MP980) does support IPv6 (I completely forgot). So I
>>> have added IPv6 support for the pixma backend. The changes for button
>>> support and IPv6 are now in git. Please test
>>> Kind regards, Louis
>>>
>>>
>>> --
>>> 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
>>
>> Hey Louis,
>> very good job. My scanner works now by using the buttons.
>>
>> --
>> 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
> Hey Louis,
> by using sane-backend(last git) with comandline, my scanner works with the 
> buttons. E.g. scanimage buttoncontrolled=yes 
>
>
> But scanbd can't read the buttonstatus. It's a bug or not implemented? All 
> the options are available, but scanbd shows no action by using the buttons.

just to clearify: scanbd can read the buttons (e.g. a button-option with 
name "button-1") but the value of this particular option never changes 
when the user presses a button. A quick look in to the pixma 
backend-sources suggests that querying the button values isn't supported 
... ?

>
> Kind regards?
> Nelson
>


-- 
Wilhelm

[sane-devel] Canon Mx 700 - Scanbuttons

[Nelson]

>> On Sat, 2012-08-11 at 20:22 +0200, Louis Lagendijk wrote:
>> 
>>> hello Nelson/ list,
>>> I finally managed to find some time to work on the bjnp button scan
>>> support for the pixma backend. I got it working, although I am not
>>> really sure that it does not contain faults in some corner cases. As we
>>> are pretty close to the 1.0.23 release of sane, I will not yet commit
>>> the changes to git. It took me quite a while to figure out how the
>>> protocol works, so it has taken quite some time before I got something
>>> working. 
>>> 
>>> Please let me know if you are in a hurry to test before the 1.0.23
>>> release is done. If so, I can mail you a patch to apply on top of the
>>> current git. I have only tested this with xsane, as I did not have time
>>> to setup scanbd, sorry. It anyhow looks as if sane and printing (bjnp
>>> backend for cups) can access the device at the same time: I could print
>>> a page while xsane was waiting for a button to be pressed. When the
>>> printjob was done, I was able to press the scan button again.
>>> 
>>> Louis
>>> P.s. I will push my changes to git as soon as 1.0.23 is released 
>> 
>> As I was working on the scan button support, I found out that my
>> multi-function (MP980) does support IPv6 (I completely forgot). So I
>> have added IPv6 support for the pixma backend. The changes for button
>> support and IPv6 are now in git. Please test
>> Kind regards, Louis
>> 
>> 
>> -- 
>> 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
> 
> Hey Louis,
> very good job. My scanner works now by using the buttons. 
> 
> -- 
> 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
Hey Louis,
by using sane-backend(last git) with comandline, my scanner works with the 
buttons. E.g. scanimage buttoncontrolled=yes 


But scanbd can't read the buttonstatus. It's a bug or not implemented? All the 
options are available, but scanbd shows no action by using the buttons. 

Kind regards?
Nelson

[sane-devel] Canon Mx 700 - Scanbuttons

[Nelson]

> Am 29.08.2012 09:21, schrieb Nelson:
>> Am 17.05.2012 12:13, schrieb Louis Lagendijk:
 On Thu, 2012-05-17 at 07:46 +0200, Nelson wrote:
>> Hey mailing list,
> 
>> how can I use the scan buttons of the mx700 with lan connection?  If
>> I work on usb pursuing all the best.  Even the buttons.  When I run
>> the printer / scanner on lan work the buttons not to scan.
>> 
>> greets
>> candyman
> 
> 
> 
 Hi,
 Right now you can't. I wrote the network layer for the pixma backend,
 and at the time could not figure out the button stuff. It is the only
 part of the network stuff that does NOT work.
 
 And as nobody ever asked, I never got around to look into that anymore.
 I will put it on my TODO list to look into it again when I can find some
 time
>>> 
>>> As the author of the scanner button daemon (scanbd) I would be interested 
>>> too in this functionality :-)
>>> 
 
 Kind regards, Louis
 
 
>>> 
>>> 
>>> --
>>> Wilhelm
>>> 
>>> 
>>> --
>>> 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
>> 
>> Hey Wilhelm,
>> is there a way to test the new sanecode with scanbuttond? Or must you 
>> something to program?
> 
> Well, I don't own such device ...
> 
> Is there any other way to test the stuff?
> 
> 
> -- 
> Wilhelm
> 
I have an mx700 and i have installed the sane-backend 1.0.24. When i type 
"scanimage --button-controled=yes" wait the scanner of the colorbutton. Also it 
works. 
What can i do?

[sane-devel] Canon Mx 700 - Scanbuttons

[Wilhelm]

Am 29.08.2012 09:21, schrieb Nelson:
> Am 17.05.2012 12:13, schrieb Louis Lagendijk:
>>> On Thu, 2012-05-17 at 07:46 +0200, Nelson wrote:
> Hey mailing list,

> how can I use the scan buttons of the mx700 with lan connection?  If
> I work on usb pursuing all the best.  Even the buttons.  When I run
> the printer / scanner on lan work the buttons not to scan.
>
> greets
> candyman



>>> Hi,
>>> Right now you can't. I wrote the network layer for the pixma backend,
>>> and at the time could not figure out the button stuff. It is the only
>>> part of the network stuff that does NOT work.
>>>
>>> And as nobody ever asked, I never got around to look into that anymore.
>>> I will put it on my TODO list to look into it again when I can find some
>>> time
>>
>> As the author of the scanner button daemon (scanbd) I would be interested 
>> too in this functionality :-)
>>
>>>
>>> Kind regards, Louis
>>>
>>>
>>
>>
>> --
>> Wilhelm
>>
>>
>> --
>> 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
>
> Hey Wilhelm,
> is there a way to test the new sanecode with scanbuttond? Or must you 
> something to program?

Well, I don't own such device ...

Is there any other way to test the stuff?


-- 
Wilhelm

[sane-devel] Canon Mx 700 - Scanbuttons

[Nelson]

Am 17.05.2012 12:13, schrieb Louis Lagendijk:
>> On Thu, 2012-05-17 at 07:46 +0200, Nelson wrote:
 Hey mailing list,
>>> 
 how can I use the scan buttons of the mx700 with lan connection?  If
 I work on usb pursuing all the best.  Even the buttons.  When I run
 the printer / scanner on lan work the buttons not to scan.
 
 greets
 candyman
>>> 
>>> 
>>> 
>> Hi,
>> Right now you can't. I wrote the network layer for the pixma backend,
>> and at the time could not figure out the button stuff. It is the only
>> part of the network stuff that does NOT work.
>> 
>> And as nobody ever asked, I never got around to look into that anymore.
>> I will put it on my TODO list to look into it again when I can find some
>> time
> 
> As the author of the scanner button daemon (scanbd) I would be interested too 
> in this functionality :-)
> 
>> 
>> Kind regards, Louis
>> 
>> 
> 
> 
> -- 
> Wilhelm
> 
> 
> -- 
> 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

Hey Wilhelm,
is there a way to test the new sanecode with scanbuttond? Or must you something 
to program?

[sane-devel] Canon Mx 700 - Scanbuttons

[Nelson]

> On Sat, 2012-08-11 at 20:22 +0200, Louis Lagendijk wrote:
> 
>> hello Nelson/ list,
>> I finally managed to find some time to work on the bjnp button scan
>> support for the pixma backend. I got it working, although I am not
>> really sure that it does not contain faults in some corner cases. As we
>> are pretty close to the 1.0.23 release of sane, I will not yet commit
>> the changes to git. It took me quite a while to figure out how the
>> protocol works, so it has taken quite some time before I got something
>> working. 
>> 
>> Please let me know if you are in a hurry to test before the 1.0.23
>> release is done. If so, I can mail you a patch to apply on top of the
>> current git. I have only tested this with xsane, as I did not have time
>> to setup scanbd, sorry. It anyhow looks as if sane and printing (bjnp
>> backend for cups) can access the device at the same time: I could print
>> a page while xsane was waiting for a button to be pressed. When the
>> printjob was done, I was able to press the scan button again.
>> 
>> Louis
>> P.s. I will push my changes to git as soon as 1.0.23 is released 
> 
> As I was working on the scan button support, I found out that my
> multi-function (MP980) does support IPv6 (I completely forgot). So I
> have added IPv6 support for the pixma backend. The changes for button
> support and IPv6 are now in git. Please test
> Kind regards, Louis
> 
> 
> -- 
> 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

Hey Louis,
very good job. My scanner works now by using the buttons. 

[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Sat, 2012-08-11 at 20:22 +0200, Louis Lagendijk wrote:

> hello Nelson/ list,
> I finally managed to find some time to work on the bjnp button scan
> support for the pixma backend. I got it working, although I am not
> really sure that it does not contain faults in some corner cases. As we
> are pretty close to the 1.0.23 release of sane, I will not yet commit
> the changes to git. It took me quite a while to figure out how the
> protocol works, so it has taken quite some time before I got something
> working. 
> 
> Please let me know if you are in a hurry to test before the 1.0.23
> release is done. If so, I can mail you a patch to apply on top of the
> current git. I have only tested this with xsane, as I did not have time
> to setup scanbd, sorry. It anyhow looks as if sane and printing (bjnp
> backend for cups) can access the device at the same time: I could print
> a page while xsane was waiting for a button to be pressed. When the
> printjob was done, I was able to press the scan button again.
> 
> Louis
> P.s. I will push my changes to git as soon as 1.0.23 is released 

As I was working on the scan button support, I found out that my
multi-function (MP980) does support IPv6 (I completely forgot). So I
have added IPv6 support for the pixma backend. The changes for button
support and IPv6 are now in git. Please test
Kind regards, Louis

[sane-devel] Canon Mx 700 - Scanbuttons

[Nelson]

> On Thu, 2012-05-17 at 12:13 +0200, Louis Lagendijk wrote:
>> On Thu, 2012-05-17 at 07:46 +0200, Nelson wrote:
 Hey mailing list,
>>> 
 how can I use the scan buttons of the mx700 with lan connection?  If
 I work on usb pursuing all the best.  Even the buttons.  When I run
 the printer / scanner on lan work the buttons not to scan.
 
 greets 
 candyman
>>> 
>>> 
>>> 
>> Hi,
>> Right now you can't. I wrote the network layer for the pixma backend,
>> and at the time could not figure out the button stuff. It is the only
>> part of the network stuff that does NOT work.
>> 
>> And as nobody ever asked, I never got around to look into that anymore.
>> I will put it on my TODO list to look into it again when I can find some
>> time
> hello Nelson/ list,
> I finally managed to find some time to work on the bjnp button scan
> support for the pixma backend. I got it working, although I am not
> really sure that it does not contain faults in some corner cases. As we
> are pretty close to the 1.0.23 release of sane, I will not yet commit
> the changes to git. It took me quite a while to figure out how the
> protocol works, so it has taken quite some time before I got something
> working. 
> 
> Please let me know if you are in a hurry to test before the 1.0.23
> release is done. If so, I can mail you a patch to apply on top of the
> current git. I have only tested this with xsane, as I did not have time
> to setup scanbd, sorry. It anyhow looks as if sane and printing (bjnp
> backend for cups) can access the device at the same time: I could print
> a page while xsane was waiting for a button to be pressed. When the
> printjob was done, I was able to press the scan button again.
> 
> Louis
> P.s. I will push my changes to git as soon as 1.0.23 is released 
> 
> 
> 
> 
> -- 
> 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

It is not in a hurry, but if you send me the patch, I can help you test for 
something.

greets 
Nelson

[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Thu, 2012-05-17 at 12:13 +0200, Louis Lagendijk wrote:
> On Thu, 2012-05-17 at 07:46 +0200, Nelson wrote:
> > > Hey mailing list,
> > 
> > > how can I use the scan buttons of the mx700 with lan connection?  If
> > > I work on usb pursuing all the best.  Even the buttons.  When I run
> > > the printer / scanner on lan work the buttons not to scan.
> > > 
> > > greets 
> > > candyman
> > 
> > 
> > 
> Hi,
> Right now you can't. I wrote the network layer for the pixma backend,
> and at the time could not figure out the button stuff. It is the only
> part of the network stuff that does NOT work.
> 
> And as nobody ever asked, I never got around to look into that anymore.
> I will put it on my TODO list to look into it again when I can find some
> time
hello Nelson/ list,
I finally managed to find some time to work on the bjnp button scan
support for the pixma backend. I got it working, although I am not
really sure that it does not contain faults in some corner cases. As we
are pretty close to the 1.0.23 release of sane, I will not yet commit
the changes to git. It took me quite a while to figure out how the
protocol works, so it has taken quite some time before I got something
working. 

Please let me know if you are in a hurry to test before the 1.0.23
release is done. If so, I can mail you a patch to apply on top of the
current git. I have only tested this with xsane, as I did not have time
to setup scanbd, sorry. It anyhow looks as if sane and printing (bjnp
backend for cups) can access the device at the same time: I could print
a page while xsane was waiting for a button to be pressed. When the
printjob was done, I was able to press the scan button again.

Louis
P.s. I will push my changes to git as soon as 1.0.23 is released 

[sane-devel] Canon Mx 700 - Scanbuttons

[Wilhelm]

Am 17.05.2012 12:13, schrieb Louis Lagendijk:
> On Thu, 2012-05-17 at 07:46 +0200, Nelson wrote:
>>> Hey mailing list,
>>
>>> how can I use the scan buttons of the mx700 with lan connection?  If
>>> I work on usb pursuing all the best.  Even the buttons.  When I run
>>> the printer / scanner on lan work the buttons not to scan.
>>>
>>> greets
>>> candyman
>>
>>
>>
> Hi,
> Right now you can't. I wrote the network layer for the pixma backend,
> and at the time could not figure out the button stuff. It is the only
> part of the network stuff that does NOT work.
>
> And as nobody ever asked, I never got around to look into that anymore.
> I will put it on my TODO list to look into it again when I can find some
> time

As the author of the scanner button daemon (scanbd) I would be 
interested too in this functionality :-)

>
> Kind regards, Louis
>
>


-- 
Wilhelm

[sane-devel] Canon Mx 700 - Scanbuttons

[Louis Lagendijk]

On Thu, 2012-05-17 at 07:46 +0200, Nelson wrote:
> > Hey mailing list,
> 
> > how can I use the scan buttons of the mx700 with lan connection?  If
> > I work on usb pursuing all the best.  Even the buttons.  When I run
> > the printer / scanner on lan work the buttons not to scan.
> > 
> > greets 
> > candyman
> 
> 
> 
Hi,
Right now you can't. I wrote the network layer for the pixma backend,
and at the time could not figure out the button stuff. It is the only
part of the network stuff that does NOT work.

And as nobody ever asked, I never got around to look into that anymore.
I will put it on my TODO list to look into it again when I can find some
time

Kind regards, Louis

[sane-devel] Canon Mx 700 - Scanbuttons

[Nelson]

> Hey mailing list,

> how can I use the scan buttons of the mx700 with lan connection?  If I work 
> on usb pursuing all the best.  Even the buttons.  When I run the printer / 
> scanner on lan work the buttons not to scan.
> 
> greets 
> candyman


-- next part --
An HTML attachment was scrubbed...
URL: