Re: [sane-devel] Canon MG7150

[Rolf Bensch]

Hi Gert,

I just committed the patch to SANE git sources and updated all relevant
doc files.

Many thanks for your help.

Cheers,
Rolf


Am 16.05.2014 11:09, schrieb Gert Cauwenberg:
> Hello Rolf,
> 
> Confirmed - with the patch all resolutions work correctly.
> 
> Thank you,
> 
> Gert
> 
> 
> 2014-05-15 18:45 GMT+02:00 Rolf Bensch  >:
> 
> Hi Gert,
> 
> Attached patch should fix your problem.
> 
> Please report anyway, so that I can patch SANE sources.
> 
> Cheers,
> Rolf
> 
> 
> Am 15.05.2014 09:34, schrieb Gert Cauwenberg:
> > Scanning with resolutions from 75 up to 600dpi works fine.
> > At 1200dpi it does scan, it does produce an image with the
> expected size
> > - but the image 'wraps around' - half of the original takes up the
> whole
> > scanwidth, and then the second half is overlayed.
> > At 600 dpi: http://imgur.com/69DqOt0
> > At 1200 dpi: http://imgur.com/KanArkn
> >
> > At 2400 dpi the same effect occurs, but now 4 times. Seems like the
> > software somewhere expects a 600 dpi image?
> >
> > On this device all settings are controlled via touch screen, so
> I'm not
> > sure what 'buttons' I should press - or how I am to run scanimage
> -A at
> > the exact moment the screen is touched. Anyway, whenever I run
> scanimage
> > -A I get the same output:
> >
> > [sanei_debug] Setting debug level of pixma to
> > 11.
> >
> > [pixma] pixma is compiled with pthread
> > support.
> >
> > [pixma] pixma version
> > 0.17.4
> >
> > [pixma] Scanner model found: Name MG7100(Canon PIXMA MG7100 Series)
> > matches MG7100 series
> > [pixma] pixma_collect_devices() found Canon PIXMA MG7100 Series at
> > bjnp://7DCF6900.local:8612
> > [pixma] pixma_open(): Canon PIXMA MG7100 Series
> >
> > (...)
> >
> >   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
> >
> >
> >
> > 2014-05-14 19:17 GMT+02:00 Rolf Bensch  
> > >>:
> >
> > Hi Gert,
> >
> > Am 14.05.2014 11:15, schrieb Gert Cauwenberg:
> > > Hello,
> > >
> > > Since yesterday I'm the owner of a Canon MG7150 all-in-one,
> and of
> > > course I wanted to get it working under linux.
> > > I'm running Ubuntu 14.04, which comes with sane backends
> 1.0.23. With
> > > that version the scanner doesn't get detected - quite
> understandably
> > > after looking at the source. I then installed sane backends
> 1.0.24,
> > > with the scanner connected via wifi.
> > >
> > > And ... good news!
> > >
> > > scanimage -L detects the scanner, and using the 'simple scan'
> > > application I was able to scan an image.
> > >
> >
> > Many thanks for your report.
> >
> > You can install xsane. It's an easy to use gui.
> >
> > > If there is anything more that I should test, let me know.
> >
> > Please check and report all scan resolutions up to 2400 dpi.
> >
> > And please check and report button support.
> >
> > How to check button support:
> > (1) Press any button.
> > (2) Check output from 'scanimage -A'.
> > (3) Repeat (1) and (2) with all other buttons.
> >
> > The response from scanimage should contain useful data like this:
> >
> >   Buttons:
> > --button-update
> > Update button state
> > --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
> >
> > If you don't get any data here, enable debug output with 'export
> > SANE_DEBUG_PIXMA=11'. Then the response should look like this:
> >
> >   Buttons:
> > --button-update
> > Update button state
> > [pixma] INTR T=1.654 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] 

[sane-devel] Fwd: Re: scanbd occasionally ignores scanner button presses

[Wilhelm]

Hi Milan,

Am 16.05.2014 09:38, schrieb Milan Knížek:
> Hello devs!
> 
> I have setup scanbd to poll CanoScan 9000F button presses (Arch Linux,
> x86_64, sane-git from 2013-07-08, scanbd 1.3.1), scanbd.service and
> scanbm.socket are run through systemd unit files.
> 
> It usually works just fine, but randomly scanbd completely ignores the
> button presses - usually, it does not even help to switch the scanner
> off/on. The only reliable solution so far is to restart the
> scanbd.service.
> 
> I increased the debug level to 3 and watched syslog for messages when
> scanbd operates normally and when it ignores the presses. I could not
> find anything unusual in the messages. Scanbd continues to send lot of
> repeated messages (like in normal state), but pressing a button does not
> log any messages anymore.
> 
> I have yet to confirm it by further testing, but it seems that I can
> trigger the "stale" status of the scanbd by repeatedly pressing the
> scanner button (e.g. the PDF merge button, which does not really scan
> anything) in a quick sequence.
> 
> Is this a known behaviour? How can I debug it further?

not as far as I know.

> 
> Is there any SIGNAL I could send to scanbd process to refresh itself
> without the need to restart scanbd.service?

Try to send SIGUSR1 to stop all polling and then SIGUSR2 to restart all
polling.

> 
> At the moment, I implemented a workaround by killing (SIGKILL) the
> scanbd process every time the button is pressed and restarting
> scanbd.service (at the end of the action script).
> 
> regards,
> Milan
> 


-- 
Wilhelm
w.me...@unix.net


-- 
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] scanbd occasionally ignores scanner button presses

[Milan Knížek]

Hello devs!

I have setup scanbd to poll CanoScan 9000F button presses (Arch Linux,
x86_64, sane-git from 2013-07-08, scanbd 1.3.1), scanbd.service and
scanbm.socket are run through systemd unit files.

It usually works just fine, but randomly scanbd completely ignores the
button presses - usually, it does not even help to switch the scanner
off/on. The only reliable solution so far is to restart the
scanbd.service.

I increased the debug level to 3 and watched syslog for messages when
scanbd operates normally and when it ignores the presses. I could not
find anything unusual in the messages. Scanbd continues to send lot of
repeated messages (like in normal state), but pressing a button does not
log any messages anymore.

I have yet to confirm it by further testing, but it seems that I can
trigger the "stale" status of the scanbd by repeatedly pressing the
scanner button (e.g. the PDF merge button, which does not really scan
anything) in a quick sequence.

Is this a known behaviour? How can I debug it further?

Is there any SIGNAL I could send to scanbd process to refresh itself
without the need to restart scanbd.service?

At the moment, I implemented a workaround by killing (SIGKILL) the
scanbd process every time the button is pressed and restarting
scanbd.service (at the end of the action script).

regards,
Milan

-- 
http://milan-knizek.net/
About linux and photography (Czech only)
O linuxu a fotografování




-- 
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