date:20161024

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

2016-10-24 Thread matt clark

More testing - checking permissions to the scanner:

[matt@localhost sane.d]$ lsusb
Bus 002 Device 005: ID 04a9:174b Canon, Inc.  (plus others)
[matt@localhost sane.d]$ ls -l /dev/bus/usb/002/005
crw-rw-r-- 1 root lp 189, 132 Oct 25 15:47 /dev/bus/usb/002/005

It looks like root and group "lp" have read write access to the
scanner.  So I added both me and the "saned" user is in the lp group.
But I still can't get scanimage -L to pick up the USB connection
without sudo access.

Don't know if this is useful extra info or not!

On Tue, Oct 25, 2016 at 3:31 PM, matt clark  wrote:
> Hi again, after the last test I reinstalled sane without the scanbd
> bits, want to see if I can get this working without it.  The output
> from the command above is at http://pastebin.com/1h6gDTQV
>
> It looks from that as though sane is picking up both the network
> connection to the scanner/printer and the USB connection.  Not sure if
> that helps diagnose?  If I run the same command without sudo access it
> doesn't pick up the USB version.
>
> Cheers
> Matt
>
> On Tue, Oct 25, 2016 at 3:12 PM, matt clark  wrote:
>> Hi Rolf, thanks for replying - sorry I missed it last week.  The
>> response to that command (running as su) is
>>
>> scanimage: no SANE devices found
>>
>> I am guessing it's something wrong with the scanbd setup since I can
>> see that it's installed using the /usr/local/etc/scanbd/sane.d config
>> file.  The only line that is not commented out in my
>> /etc/sane.d/saned.conf file is
>>
>> localhost
>>
>> Would appreciate your thoughts.
>>

-- 
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] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

2016-10-24 Thread matt clark

Hi again, after the last test I reinstalled sane without the scanbd
bits, want to see if I can get this working without it.  The output
from the command above is at http://pastebin.com/1h6gDTQV

It looks from that as though sane is picking up both the network
connection to the scanner/printer and the USB connection.  Not sure if
that helps diagnose?  If I run the same command without sudo access it
doesn't pick up the USB version.

Cheers
Matt

On Tue, Oct 25, 2016 at 3:12 PM, matt clark  wrote:
> Hi Rolf, thanks for replying - sorry I missed it last week.  The
> response to that command (running as su) is
>
> scanimage: no SANE devices found
>
> I am guessing it's something wrong with the scanbd setup since I can
> see that it's installed using the /usr/local/etc/scanbd/sane.d config
> file.  The only line that is not commented out in my
> /etc/sane.d/saned.conf file is
>
> localhost
>
> Would appreciate your thoughts.
>
> On Wed, Oct 19, 2016 at 9:13 PM, Rolf Bensch  wrote:
>> Hi Matt,
>>
>> Sorry for the late response.
>>
>> The command line must run without
>> 'SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d'. Maybe you don't have the
>> user rights to access your scanner via USB. Please try following:
>> (1) push any button
>> (2) sudo su -c "SANE_DEBUG_PIXMA=11 scanimage -A"
>>
>> Please send me the complete log response.
>>
>> Cheers,
>> Rolf
>>
>> Am 13.10.2016 um 23:29 schrieb matt clark:
>>> Hi Rolf, the "buttons" section in the code shows this:
>>>
>>>   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
>>>
>>> None of the binary code you mentioned.  Does this mean there is no
>>> sane support for the buttons?  Note that I had to use the command
>>> SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
>>> scanimage -A to make it work.  I pushing both buttons, and sending it
>>> via USB (yes it's connected) and the "localhost saned" option which is
>>> I assume sending via network.
>>>
>>> On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch  wrote:
 Hi Matt,

 Have you tested that your scanner resp. the backend sends data @ a push
 button event?

 Please test on the console:
 (1) push any button
 (2) $ SANE_DEBUG_PIXMA=11 scanimage -A
 (3) check the response; I'm especially interested in following lines:

   Buttons:
 --button-update
 Update button state
 [pixma] INTR T=1.343 len=32
 [pixma]  :00 20 00 00 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]
 --button-1  [1] [read-only]
 Button 1
 --button-2  [0] [read-only]
 Button 2
 --original  [0] [read-only]
 Type of original to scan
 --target  [2] [read-only]
 Target operation type
 --scan-resolution  [0] [read-only]
 Scan resolution

 Please repeat (1) ... (3) for all scan buttons.

 Maybe you need to test your scanner USB connected to the pc. I haven't
 tested push buttons wireless yet.

 If you don't get lines starting with [pixma], your scanner has no button
 support from SANE.

 If you get lines starting with [pixma] with more data as shown above (I
 have a different scanner) and without data output below at the
 parameters --button-1 ... --scan-resolution, what I suppose, then please
 send me your "Buttons:" logs and I'll fix the backend code.

 Hope this helps.

 Cheers,
 Rolf

 Am 13.10.2016 um 13:23 schrieb Wilhelm:
> Oh, mixed the values ...
>
>  action btest {
>  filter = "^button.*"
>  numerical-trigger {
>  from-value = 0
>  to-value   = 1
>  }
>  desc   = "Scan to file"
>  script = "test.script"
>  }
>
>
> Am 13.10.2016 um 11:16 schrieb Wilhelm:
>> Matt, you need something like this in your config:
>>
>> action btest {
>> filter = "^button.*"
>> numerical-trigger {
>> from-value = 1
>> to-value   = 0
>> }
>> desc   = "Scan to file"
>> script = "test.script"
>> }
>>
>> --
>>  Wilhelm
>>
>> Am 13.10.2016 um 09:09 schrieb matt clark:
>>> Thanks Wilhelm.  I had changed that while trying to debug the

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

2016-10-24 Thread matt clark

Hi Rolf, thanks for replying - sorry I missed it last week.  The
response to that command (running as su) is

scanimage: no SANE devices found

I am guessing it's something wrong with the scanbd setup since I can
see that it's installed using the /usr/local/etc/scanbd/sane.d config
file.  The only line that is not commented out in my
/etc/sane.d/saned.conf file is

localhost

Would appreciate your thoughts.

On Wed, Oct 19, 2016 at 9:13 PM, Rolf Bensch  wrote:
> Hi Matt,
>
> Sorry for the late response.
>
> The command line must run without
> 'SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d'. Maybe you don't have the
> user rights to access your scanner via USB. Please try following:
> (1) push any button
> (2) sudo su -c "SANE_DEBUG_PIXMA=11 scanimage -A"
>
> Please send me the complete log response.
>
> Cheers,
> Rolf
>
> Am 13.10.2016 um 23:29 schrieb matt clark:
>> Hi Rolf, the "buttons" section in the code shows this:
>>
>>   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
>>
>> None of the binary code you mentioned.  Does this mean there is no
>> sane support for the buttons?  Note that I had to use the command
>> SANE_CONFIG_DIR=/usr/local/etc/scanbd/sane.d SANE_DEBUG_PIXMA=11
>> scanimage -A to make it work.  I pushing both buttons, and sending it
>> via USB (yes it's connected) and the "localhost saned" option which is
>> I assume sending via network.
>>
>> On Fri, Oct 14, 2016 at 7:16 AM, Rolf Bensch  wrote:
>>> Hi Matt,
>>>
>>> Have you tested that your scanner resp. the backend sends data @ a push
>>> button event?
>>>
>>> Please test on the console:
>>> (1) push any button
>>> (2) $ SANE_DEBUG_PIXMA=11 scanimage -A
>>> (3) check the response; I'm especially interested in following lines:
>>>
>>>   Buttons:
>>> --button-update
>>> Update button state
>>> [pixma] INTR T=1.343 len=32
>>> [pixma]  :00 20 00 00 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]
>>> --button-1  [1] [read-only]
>>> Button 1
>>> --button-2  [0] [read-only]
>>> Button 2
>>> --original  [0] [read-only]
>>> Type of original to scan
>>> --target  [2] [read-only]
>>> Target operation type
>>> --scan-resolution  [0] [read-only]
>>> Scan resolution
>>>
>>> Please repeat (1) ... (3) for all scan buttons.
>>>
>>> Maybe you need to test your scanner USB connected to the pc. I haven't
>>> tested push buttons wireless yet.
>>>
>>> If you don't get lines starting with [pixma], your scanner has no button
>>> support from SANE.
>>>
>>> If you get lines starting with [pixma] with more data as shown above (I
>>> have a different scanner) and without data output below at the
>>> parameters --button-1 ... --scan-resolution, what I suppose, then please
>>> send me your "Buttons:" logs and I'll fix the backend code.
>>>
>>> Hope this helps.
>>>
>>> Cheers,
>>> Rolf
>>>
>>> Am 13.10.2016 um 13:23 schrieb Wilhelm:
 Oh, mixed the values ...

  action btest {
  filter = "^button.*"
  numerical-trigger {
  from-value = 0
  to-value   = 1
  }
  desc   = "Scan to file"
  script = "test.script"
  }


 Am 13.10.2016 um 11:16 schrieb Wilhelm:
> Matt, you need something like this in your config:
>
> action btest {
> filter = "^button.*"
> numerical-trigger {
> from-value = 1
> to-value   = 0
> }
> desc   = "Scan to file"
> script = "test.script"
> }
>
> --
>  Wilhelm
>
> Am 13.10.2016 um 09:09 schrieb matt clark:
>> Thanks Wilhelm.  I had changed that while trying to debug the problem,
>> not sure why this would be a problem.  Have reverted to the
>> scanbd.conf from source, with modifications to sane.d directory and
>> comment out the unnecessary manufacturer scanner.d profiles.  revised
>> config is attached - apologies for the length of code.
>>
>> ---
>>
>> /*
>>  * $Id: scanbd.conf 213 2015-10-05 06:52:50Z wimalopaan $
>>  *
>>  *  scanbd - KMUX scanner button daemon
>>  *
>>  *  Copyright (C) 2008 - 2015  Wilhelm Meier (wilhelm.me...@fh-kl.de)
>>  *
>>  *  This program is free software; you can redistribute it and/or modify
>>  *  it under the terms of the GNU

Re: [sane-devel] Ubuntu 16.04.1 vs CanoScan Lide 220

2016-10-24 Thread csola48

2016-10-21 17:33 keltezéssel, csola48 írta:
> My system:
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=16.04
> DISTRIB_CODENAME=xenial
> DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS
> version: Ubuntu 4.4.0-45.66-generic 4.4.21
> sane 1.0.14-1
> sane-utils, libsane-common, libsane 1.0.26-git20160712-xenial0
> xsane, xsane common 0.999-3ubuntu1
> simple-scan 3.20.0-0ubuntu1
>
> The scanner indicates input/output error... Not working... :(
> The scanner stays on the sheet's bottom and is frozen off...
>
>
Dear Stef !

New debugs:

export SANE_DEBUG_GENESYS=255
export SANE_DEBUG_GENESYS_LOW=255
export SANE_DEBUG_GENESYS_GL124=255
scanimage -d genesys --resolution 75 --preview --mode Color 2>debug.log

[sanei_debug] Setting debug level of genesys to 255.
[genesys] SANE Genesys backend version 1.0 build 2511 from
sane-backends 1.0.26git
[genesys] SANE Genesys backend built with libusb-1.0
[genesys] sane_init: authorize != null
[genesys] sane_init: little endian machine
[genesys] probe_genesys_devices start
[genesys] attach: start: devp != NULL, may_wait = 0
[genesys] attach: trying to open device `libusb:001:005'
[genesys] attach: device `libusb:001:005' successfully opened
[genesys] attach: found Canon flatbed scanner LiDE 220 at libusb:001:005
[genesys] attach completed
[genesys] probe_genesys_devices: 1 devices currently attached
[genesys] probe_genesys_devices completed
[genesys] sane_genesys_init completed
[genesys] sane_open: start (devicename = `')
[genesys] sane_open: empty devicename, trying `libusb:001:005'
[genesys] init_options start
[genesys] init_options completed
[sanei_debug] Setting debug level of genesys_low to 255.
[sanei_debug] Setting debug level of genesys_gl124 to 255.
[genesys_gl124] gl124_init start
[genesys_low] sanei_genesys_asic_init start
[genesys_low] sanei_genesys_asic_init: value=0x00
[genesys_low] sanei_genesys_asic_init: device is USB2.0
[genesys] sanei_genesys_create_gamma_table: size = 256, maximum =
65535, gamma_max = 65535, gamma = 2.1
[genesys] sanei_genesys_create_gamma_table: completed
[genesys] sanei_genesys_create_gamma_table: size = 256, maximum =
65535, gamma_max = 65535, gamma = 2.1
[genesys] sanei_genesys_create_gamma_table: completed
[genesys] sanei_genesys_create_gamma_table: size = 256, maximum =
65535, gamma_max = 65535, gamma = 2.1
[genesys] sanei_genesys_create_gamma_table: completed
[genesys_low] sanei_genesys_read_gl847_register(0x06)=0x00
[genesys_low] sanei_genesys_asic_init: device is cold
[genesys_gl124] gl124_boot start
[genesys_low] sanei_genesys_write_gl847_register (0x0e, 0x01) completed
[genesys_low] sanei_genesys_write_gl847_register (0x0e, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x36, 0x01) completed
[genesys_low] sanei_genesys_read_gl847_register(0x33)=0x00
[genesys_low] sanei_genesys_write_gl847_register (0x33, 0x01) completed
[genesys_low] sanei_genesys_read_hregister(0x100)=0xf0
[genesys_low] sanei_genesys_read_gl847_register(0x00)=0x95
[genesys_gl124] gl124_cold_boot: reported version for genesys chip is 0x95
[genesys_gl124] gl124_init_registers start
[genesys_gl124] gl124_init_registers completed
[genesys_low] sanei_genesys_write_gl847_register (0x01, 0xa2) completed
[genesys_low] sanei_genesys_write_gl847_register (0x02, 0x90) completed
[genesys_low] sanei_genesys_write_gl847_register (0x03, 0x10) completed
[genesys_low] sanei_genesys_write_gl847_register (0x04, 0x03) completed
[genesys_low] sanei_genesys_write_gl847_register (0x05, 0x80) completed
[genesys_low] sanei_genesys_write_gl847_register (0x06, 0x58) completed
[genesys_low] sanei_genesys_write_gl847_register (0x09, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x0a, 0xc0) completed
[genesys_low] sanei_genesys_write_gl847_register (0x0b, 0x2a) completed
[genesys_low] sanei_genesys_write_gl847_register (0x0c, 0x12) completed
[genesys_low] sanei_genesys_write_gl847_register (0x11, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x12, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x13, 0x0f) completed
[genesys_low] sanei_genesys_write_gl847_register (0x14, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x15, 0x80) completed
[genesys_low] sanei_genesys_write_gl847_register (0x16, 0x10) completed
[genesys_low] sanei_genesys_write_gl847_register (0x17, 0x04) completed
[genesys_low] sanei_genesys_write_gl847_register (0x18, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x19, 0x01) completed
[genesys_low] sanei_genesys_write_gl847_register (0x1a, 0x30) completed
[genesys_low] sanei_genesys_write_gl847_register (0x1b, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x1c, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x1d, 0x01) completed
[genesys_low] sanei_genesys_write_gl847_register (0x1e, 0x10) completed
[genesys_low] sanei_genesys_write_gl847_register (0x1f, 0x00) completed
[genesys_low] sanei_genesys_write_gl847_register (0x20, 0x15)

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

Re: [sane-devel] [Scanbd] Set up for Canon PIXMA multifunction scanner - no button response

Re: [sane-devel] Ubuntu 16.04.1 vs CanoScan Lide 220

4 matches

Site Navigation

Mail list logo

Footer information