On Wed, 2013-02-06 at 22:27 +0100, Rolf Bensch wrote:
Hi Matthias,
Many thanks for your patch. I just committed your patch to git.
I have no idea about BJNP. Please open a new thread about this issue
here in the ml, and/or search for a BJNP maintainer in ChangeLog.
Cheers,
Rolf
Gents
Hello Louis,
thank's for your quick response. Here the debug output. I think you are
only interestet at the portion near the Button-Update.
The scanner is connectet via WLAN and first i press COLOR and then at my
PC scanimage -A
Buttons:
--button-update
Update button state
Hi Matthias,
Super! Please send me the same logs for all buttons, one by one. Then
I'll prepare the next patch. By now you can ignore the timeout.
Some programs use --button-1 to scan a page and --button-2 to end a
scan session. For my scanner I'm using all buttons for --button-1
except button
Hi Rolf,
The MG6250 has a small Display. All Buttons are normaly invisible. The
device only illuminate the buttons, which can be used in the actual
context.
3 Buttons are under the display. 5 Buttons are for up, down, right, left
and in the middle OK. Then we have a home and a return Button.
Hi Matthias,
I prepared a 2nd patch for pixma_mp150.c. This should fix the timeout
problem and sets --button-1, --button-2 and --target. This patch
is based on the first patch.
Please test the patched version with enabled debug messages: 'export
SANE_DEBUG_PIXMA=21' and test both buttons (BLACK
Hi Rolf,
great now i see a reaction at the debug output. Seems that Button1 ist
BLACK and Button2 ist COLOR. I found no reaction if scanner is opened
or closed. In some cases FOTO, PDF target is set.
1. Autom. Scan - BLACK
[pixma] INTR T=1.391 len=32
[pixma] :00 00 00 01 00 00 00 00
Hello Rolf,
with the patch2 we have reaction on the scan-bottons. But Button1 is
triggered periodical without pressing any button. I have analysed the
interrupt data and find out, which bytes for the buttons and options are. I
have made some modifications to pixma_mp150.c. In the code i have
Hi Matthias,
Many thanks for your patch. I just committed your patch to git.
I have no idea about BJNP. Please open a new thread about this issue
here in the ml, and/or search for a BJNP maintainer in ChangeLog.
Cheers,
Rolf
Am 06.02.2013 18:17, schrieb Matthias Thon:
Hello Rolf,
with the
Hi Matthias,
You still are using the old Sane backend 1.0.23.
Please setup the symbolic links as described in README.linux and check
the version again:
$ scanimage -V
scanimage (sane-backends) 1.0.24git; backend version 1.0.24
^^
Cheers,
Am Dienstag, den 05.02.2013, 13:13 +0100 schrieb Matthias Thon:
Hello Rolf,
guess i set the test environment now well. scanimage -V- shows now:
If i start scanimage -A i can choose as destination on the MG6250
root at matze-buero (my sane-pc). Then i choose JPEG A4 600dpi and press
Am Dienstag, den 05.02.2013, 13:22 +0100 schrieb Matthias Thon:
Hi Rolf,
forgot the output of scanimage -V. Here the cpature:
root at matze-buero:/usr/lib/x86_64-linux-gnu# scanimage -V
scanimage (sane-backends) 1.0.24git; backend version 1.0.24
root at
Hi Matthias,
Please test the scanner first on the USB interface. If this is working,
we can go ahead with scanning via LAN (bjnp).
Cheers,
Rolf
Am 05.02.2013 13:17, schrieb Matthias Thon:
Am Dienstag, den 05.02.2013, 13:13 +0100 schrieb Matthias Thon:
Hello Rolf,
guess i set the test
Hello Rolf,
i have tested with USB connection. But the result is equal. Here the output
of scanimage:
regards Matthias
root at matze-Satellite-C660:/usr/local/src/sane-backends-git/sane-backends#
scanimage -V
scanimage (sane-backends) 1.0.24git; backend version 1.0.24
root at
Hi Rolf,
sorry for that last mail, i forgot to turn of the WLAN. I send new debug
infromations in a few minutes.
regards Matthias
-- next part --
An HTML attachment was scrubbed...
URL:
Hi Rolf,
now hopefully the right debug information. Now after starting scanimage -A
, it waits for the button information. I try different buttons (black,
color) Changed before from JPEG to PDF or TIFF but scanimage waits till
timeout. See the output.
regards Matthias
root at
Hi Matthias,
Are you sure that you are using the latest version from git? You should
get this line: [pixma] pixma version 0.17.1
But, it seems that you get data from the scanner now.
Please enable these debug levels: 'export SANE_DEBUG_PIXMA=21' and
'export SANE_DEBUG_SANEI_USB=255'.
You only
Hi Matthias,
Sorry for my last email relating to USB and LAN. I mixed the emails up
in my daily digest. Please set me to cc if you send a response to the list.
Anyway, it seems that your scanner answers the USB interrupt request and
the post process data handling sticks in setting your scanner's
Hi Rolf,
here the dump with the higher Debug-Levels. I interrupt after pressing the
COLOR Scan-Button and the second timout.
regards Matthias
Width of scan-area.
-y auto|0..297.011mm [297.011]
Height of scan-area.
Buttons:
--button-update
Update button state
Hi Matthias,
I prepared a first patch for your button problem. This should fix
receiving USB interrupts.
Please fetch latest Sane 1.0.24 from git: 'git clone
git://git.debian.org/sane/sane-backends.git'. git creates a new folder
sane-backends. Please read sane-backends/README.linux how to
Am Sonntag, den 03.02.2013, 13:09 +0100 schrieb Matthias Thon:
Hello Rolf,
ihave checked your informations. The MG6250 doesn't have a target
option. Only the two buttons.I have tryed many cases on the MG but the
value of the buttons stay's at value 0. Normaly i have conncted the
printer
Hi Matthias,
Please (1) activate debug messages with 'export SANE_DEBUG_PIXMA=11',
(2) push one of your scanners's buttons and
(3) read the button status with 'scanimage -A'.
You should receive something similar like this:
...
Buttons:
--button-update
Update button state
[pixma]
Hello Rolf,
with both (LAN/USB) connections, i get no such messages {pixma] in the
Buttons: section. I've tried different buttons (PDF, JPEG...BLACK,
COLOR).
Attached output and error output after pressing COLOR SCAN Button.
regards Matthias
Am Sonntag, den 03.02.2013, 20:49 +0100 schrieb Rolf
-- next part --
An embedded message was scrubbed...
From: Matthias Thon t...@tenoch.de
Subject: Re: [sane-devel] scanbd Canon MG6250
Date: Fri, 01 Feb 2013 19:37:26 +0100
Size: 31450
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130202/3d75cbdf
Hi Matthias,
To discover the communication between Sane and scanbd try 'scanimage
-A'. Press a button and start 'scanimage -A' again. Repeat this until
you'll have the codes for all buttons.
For my CS9000F I get data for --button-1, --button-2 *and* --target.
Please have a look to my posting
Hello,
i've tried to use scanbd with my MG6200 Series device. He finds button-1
and button-2 option. But the value is still 0.
I have try Scan - BlackWhite or Scan - Color.
Is there a way to see more detailed the communication between scanbd and
the device? (more then with debug level 7)
Hello,
i've tried to use scanbd with my MG6200 Series device. He finds
button-1 and button-2 option. But the value is still 0.
I have try Scan - BlackWhite or Scan - Color.
Is there a way to see more detailed the communication between scanbd and
the device? (more then with debug level 7)
Am 01.02.2013 16:59, schrieb Matthias Thon:
Hello,
i've tried to use scanbd with my MG6200 Series device. He finds
button-1 and button-2 option. But the value is still 0.
I have try Scan - BlackWhite or Scan - Color.
Is there a way to see more detailed the communication between scanbd and
27 matches
Mail list logo
