[sane-devel] PIXMA MG7150 test

Kiligolo kiligolo_robobert at hotmail.fr
Wed Sep 23 14:45:38 UTC 2015


Le Wednesday 23 September 2015, 12:00:02 sane-devel-
request at lists.alioth.debian.org a écrit :
> > Hello,
> >
> > 
> >
> > I have a Canon PIXMA MG7150. It has an usb port but it's connected to 
my 
> > computer via wifi.
> >
> > 
> >
> > The scanner is detected automatically and i can use scanimage -d pixma 
--
> > format=tiff > image.tiff.
> > However I usually scan with the scanner buttons and the tactile screen
> > (I'm  not going to do 9000 two-way trips to scan a file) but the
> > --button- controlled option doesn't work (the scanner detects my 
computer
> > but doesn't start the scan) so I can't send the output directly to my
> > computer.>
> > 
> >
> > The default resolution (75dpi) is too low for me to read the tiff image,
> > so I  tested the other ones listed on the scanner screen (600, 300 and
> > 150)  with>
> > the --resolution option :
> >  - 150dpi doesn't work. The output file is corrupteed. scanimage output :
> > [bjnp] bjnp_recv_data: could not read response payload (select timed
> > out): 
> > Success!
> > [bjnp] bjnp_recv_data: could not read response payload (select timed
> > out): 
> > Success!
> > [bjnp] bjnp_write: ERROR: scanner data left = 0xee4 = 3812
> > [bjnp] bjnp_recv_header:ERROR, Received response has cmd code 235, 
> > expected 33
> > [bjnp] Could not read response to command!
> > [bjnp] bjnp_write: ERROR: scanner data left = 0xee4 = 3812
> > [bjnp] bjnp_recv_header:ERROR, Received response has cmd code 241, 
> > expected 33
> > [bjnp] Could not read response to command!
> > scanimage: sane_read: Error during device I/O
> >
> > 
> >  - 300dpi works but it takes 5 minutes instead of 10 seconds
> >  - 600dpi doesn't work. The output file is cut (the lower part of the
> >sheet is >
> > missing). scanimage ouptut :
> > [bjnp] bjnp_recv_data: could not read response payload (select timed
> > out): 
> > Success!
> > scanimage: sane_read: Error during device I/O
> >
> >  
> > 
> 
> First a few questions:
> - What is the version of sane-backends that you are using?
> - Did you try button controlled scanning over USB? The bjnp code
> replaces the USB interface when the network scanning is used, but as it
> is more complex and less tested than the standard USB code, we like you
> to test with USB first, so we know where to look for the issues: in the
> pixma backend or in the network code.
> 
> I don't recall ever testing button controlled scanning with scanimage,
> so I don't know how that works. I doubt if the resolution received from
> the scanner is used by scanimage. @Rolf, can you please comment?
> 
> Button controlled scanning is not used very often, so even if the 
> scanner is supported by the backend, the parsing of the buttons may
> still be incorrect. 
> @Rolf Bensch, can you please comment, you know the backend much better
> than I do, I only wrote the BJNP network code.
> 
> For button controlled scanning I would anyhow recommend setting up
> scanbd as that will allow setting the scanner up to continuously poll
> the scanner and initiate a scan with the parameters entered on the
> scanner and store the result on the computer as often as you press one
> of the scan buttons. That will save you many trips from the computer to
> the scanner, as you can scan whenever you press a button and the
> computer is on
> 
> Best regards, Louis

Hello,

I am using sane 1.0.24.

USB test :
I linked my sanner to my computer via USB and I disabled the computer wifi.
The scanner is detected by "scanimage -L" and I can scan with "scanimage --
format=tiff > image.tiff".
I can scan with 75 (default), 150, 300 and 600dpi resolutions. 1200dpi (which 
is not proposed by the scanner screen) takes about five minutes and output a 
corrupted image.
When I type "scanimage --format=tiff --batch --button-controlled=yes " it 
says :
Scanning -1 pages, incrementing by 1, numbering from 1
Scanning page 1
So I start the scan from the scanner (I set the output location to Local (USB) 
and press the COLOR button), the scanner says "Please wait..." for a while but 
scanimage does nothing.

WIFI test :
I did the wifi test again, just to make sure (truth is, in the last test, I 
typed "--resolution 300" instead "--resolution=300").
75, 150, 300 and 600dpi work fine, I don't have any errors anymore. But with 
the 600dpi resolution the scanner seems to stop and then start its engine 
several times during the scan, and the time to send the image to my computer 
is longer than when I use windows. Maybe it's possible to send the image 
during the scan.

SCANBD test :
I tried to set up scanbd with the help of the archlinux wiki (https://
wiki.archlinux.org/index.php/Scanner_Button_Daemon), but I get this 
("journalctl -u scanbd"):

sept. 23 16:31:25 some-pc systemd[1]: Started Scanner button polling 
Service.
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: debug on: level: 
7
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: dropping privs 
to uid nobody
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: dropping privs 
to gid scanner
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: drop privileges 
to gid: 96
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: Running as 
effective gid 96
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: drop privileges 
to uid: 99
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: Running as 
effective uid 99
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: dbus_init
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: dbus match 
type='signal',interface='org.freedesktop.Hal.Manager'
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: 
SANE_CONFIG_DIR=/etc/scanbd/sane.d
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: sane version 1.0
sept. 23 16:31:25 some-pc scanbd[5342]: /usr/sbin/scanbd: Scanning for 
local-only devices
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: 
start_sane_threads
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: start dbus 
thread
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: udev init
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: get udev 
monitor
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: timeout: 500 ms
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: udev fd is non-
blocking, now setting to blocking mode
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: start udev 
thread
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: Iteration on 
dbus call
sept. 23 16:31:30 some-pc scanbd[5342]: /usr/sbin/scanbd: udev thread 
started
sept. 23 16:31:31 some-pc scanbd[5342]: /usr/sbin/scanbd: Iteration on 
dbus call
sept. 23 16:31:32 some-pc scanbd[5342]: /usr/sbin/scanbd: Iteration on 
dbus call
sept. 23 16:31:33 some-pc scanbd[5342]: /usr/sbin/scanbd: Iteration on 
dbus call
...


I changed the user to daemon (there's no saned user on my system) : 

sept. 23 16:35:36 some-pc systemd[1]: Started Scanner button polling 
Service.
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: debug on: level: 
7
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: dropping privs 
to uid daemon
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: dropping privs 
to gid scanner
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: drop privileges 
to gid: 96
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: Running as 
effective gid 96
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: drop privileges 
to uid: 2
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: Running as 
effective uid 2
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: dbus_init
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: dbus match 
type='signal',interface='org.freedesktop.Hal.Manager'
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: 
SANE_CONFIG_DIR=/etc/scanbd/sane.d
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: sane version 1.0
sept. 23 16:35:36 some-pc scanbd[5389]: /usr/sbin/scanbd: Scanning for 
local-only devices
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: 
start_sane_threads
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: start dbus 
thread
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: Not Primary 
Owner (-1)
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: Name Error 
(Connection ":1.168" is not allowed to own the service "de.kmu
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: udev init
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: get udev 
monitor
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: udev fd is non-
blocking, now setting to blocking mode
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: start udev 
thread
sept. 23 16:35:42 some-pc scanbd[5389]: /usr/sbin/scanbd: udev thread 
started


In either case my scanner doesn't see my computer.


Many thanks.



More information about the sane-devel mailing list