[sane-devel] Canon MF8200C Series
Troels Thomsen
troels.pil.thomsen at gmail.com
Fri Nov 7 09:55:08 UTC 2014
MF8230 Scanner-driver is really good now through USB. (I'll test with
ethernet another day.)
I've found two corner-cases.
1)
When choosing 3 copies from ADF in XSane, but putting 4 copies in the
scanner (!) :
- 3 pages are scanned correctly
- All 4 pages goes through the ADF, and printer is waiting for something.
- After 30 sec or so, it breaks with a beep and prints "error occured" in
the display.
No other intervention is required (you *can* break it on the scanner gui) -
and scanner is not in bad-mode as we previously experienced.
So I'm OK with this.
2)
In xsane, if you choose two copies , from Flatbed (!) the scanner really
scans twice at 300 dpi.
At 600 dpi (and e.g. 75 dpi) it ends with EBUSY, see below, and a pop-up in
XSane.
Personally I'm OK with this, I don't know if we should do anything.
I don't know if this is a valid use-case. If not - it could also be subject
to input parameter validation in XSane or sane-backend.
How does this work on other scanners?
<cut>
[pixma] IN T=723.027 len=14
[pixma] 00000000:06 06 03 01 00 41 03 00 41 10 00 01 00 66
[pixma]
[pixma] Current status: paper=1 cal=0 lamp=16
[pixma] Current status: paper=1 cal=0 lamp=16
[pixma] *iclass_finish_scan***** abort session *****
[pixma] OUT T=723.027 len=10
[pixma] 00000000:ef 20 00 00 00 00 00 00 00 00
[pixma]
[pixma] IN T=723.037 len=2
[pixma] 00000000:06 06
[pixma]
[pixma] pixma_read_image():completed
[pixma] Reader task terminated
(this is all perfectly normal - now the next scan starts)
[pixma] Reader task started
[pixma]
[pixma] pixma_scan(): start
[pixma] line_size=15360 image_size=107765760 channels=3 depth=8
[pixma] dpi=600x600 offset=(0,0) dimension=5120x7016
[pixma] [pixma] Reader task id=-1249522880 (threaded)
gamma_table=0x95d087c source=0
[pixma] threshold=127 threshold_curve=0
[pixma] ADF page count: 0
[pixma] Setting non-blocking mode
[pixma] raw_width = 5120
[pixma] OUT T=723.910 len=10
[pixma] 00000000:f3 20 00 00 00 00 00 00 0c 00
[pixma]
[pixma] IN T=723.917 len=14
[pixma] 00000000:06 06 03 01 00 41 03 00 41 10 00 01 00 66
[pixma]
[pixma] Current status: paper=1 cal=0 lamp=16
[pixma] Current status: paper=1 cal=0 lamp=16
[pixma] *iclass_scan***** start scanning *****
[pixma] OUT T=723.917 len=10
[pixma] 00000000:db 20 00 00 00 00 00 00 00 00
[pixma]
[pixma] IN T=723.927 len=2
[pixma] 00000000:14 14
[pixma]
[pixma] pixma_scan() failed EBUSY
[pixma] Reader task terminated: EBUSY
[pixma] read_image():reader task closed the pipe:0 bytes received,
107765760 bytes expected
[pixma] pixma_close(): Canon i-SENSYS MF8200C Series
2014-11-07 9:54 GMT+01:00 Troels Thomsen <troels.pil.thomsen at gmail.com>:
>
> Sorry for the delay.
> It turns out, that the MF8230 has max resolution 300dpi from ADF and 600
> dpi from Platen Glass, see attached screenshots.
> So there is no work here - except possibly to error this condition and
> abort operation.
>
> I'll check again to see, if everything else seems to be working. I think
> it does.
>
> /Troels
>
>
>
> See attached
>
>
>
>
>
>
>
> 2014-09-17 9:15 GMT+02:00 Rolf Bensch <rolf at bensch-online.de>:
>
>> Hi Troels,
>>
>> For my understanding: Can you do multiple scanimage scans without
>> power-cycling the device between two single scans?
>>
>> Cheers,
>> Rolf
>>
>>
>> Am 11.09.2014 um 22:52 schrieb Troels Thomsen:
>> >
>> > Hi,
>> >
>> > Attached is log of two pages scanned with adf at 600 dbp. Device is
>> > freshly power-cycled before this trace.
>> > Xsane hangs until I break it with Ctrl+C in the terminal.
>> > From the look of the logfile, it seems like no real image data is
>> > transmitted. Only the
>> > OUT T=60.552 len=11
>> > [pixma] 00000000:d4 60 00 00 00 00 00 00 04 00 06
>> > [pixma]
>> > [pixma] IN T=60.569 len=8
>> > [pixma] 00000000:06 06 00 00 00 00 00 00
>> > sequence is seen.
>> >
>> >
>> > Also attached is the xsane log for scanning with flatbed at 600 dpi.
>> > Data is shown in window in xsane, but an error-box is displayed, and
>> > logfile seems to end with a EBUSY.
>> >
>> > Oddly, imho, scanimage just ends like this:
>> >
>> >
>> > [pixma]
>> > [pixma] IN T=17.647 len=7680
>> > [pixma] 00000000:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] 00000010:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] 00000020:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] 00000030:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] 00000040:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] 00000050:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] 00000060:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] 00000070:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>> > [pixma] ...
>> > [pixma]
>> > [pixma] IN T=17.647 len=8
>> > [pixma] 00000000:f1 f0 ee f1 ed ee eb e3
>> > [pixma]
>> > [pixma] OUT T=17.647 len=11
>> > [pixma] 00000000:d4 60 00 00 00 00 00 00 04 00 06
>> > [pixma]
>> > [pixma] IN T=17.656 len=8
>> > [pixma] 00000000:06 06 28 00 00 00 00 00
>> > [pixma]
>> > [pixma] OUT T=17.678 len=10
>> > [pixma] 00000000:f3 20 00 00 00 00 00 00 0c 00
>> > [pixma]
>> > [pixma] IN T=17.688 len=14
>> > [pixma] 00000000:06 06 03 01 00 41 03 00 41 10 00 01 00 66
>> > [pixma]
>> > [pixma] Current status: paper=1 cal=0 lamp=16
>> > [pixma] Current status: paper=1 cal=0 lamp=16
>> > [pixma] OUT T=17.688 len=10
>> > [pixma] 00000000:f3 20 00 00 00 00 00 00 0c 00
>> > [pixma]
>> > [pixma] IN T=17.696 len=14
>> > [pixma] 00000000:06 06 03 01 00 41 03 00 41 10 00 01 00 66
>> > [pixma]
>> > [pixma] Current status: paper=1 cal=0 lamp=16
>> > [pixma] Current status: paper=1 cal=0 lamp=16
>> > [pixma] *iclass_finish_scan***** abort session *****
>> > [pixma] OUT T=17.696 len=10
>> > [pixma] 00000000:ef 20 00 00 00 00 00 00 00 00
>> > [pixma]
>> > [pixma] IN T=17.706 len=2
>> > [pixma] 00000000:06 06
>> > [pixma]
>> > [pixma] pixma_read_image():completed
>> > [pixma] Reader task terminated
>> > [pixma] pixma_close(): Canon i-SENSYS MF8200C Series
>> >
>> > I.e. NO error when using scanimage, but EBUSY when using XSane !?!?
>> >
>> >
>> >
>> > /Troels
>> >
>> >
>> > 2014-09-11 19:18 GMT+02:00 Rolf Bensch <rolf at bensch-online.de
>> > <mailto:rolf at bensch-online.de>>:
>> >
>> > Hi Troels,
>> >
>> > Am 09.09.2014 um 23:11 schrieb Troels Thomsen:
>> > > Hi Rolf
>> > >
>> > > patch new1 seems to work!
>> > >
>> > > regarding ADF its mixed:
>> > > At 150 dpi it scans pages, but colors are a bit psycedelic.
>> Bacground
>> > > should be white.
>> >
>> > You need to do some gamma settings. It's easier to use xsane here.
>> >
>> > > At 600 dpi it fails, and scanner hangs.
>> > >
>> >
>> > It seems that your scanner doesn't finish the scan correctly @ any
>> > resolution. I saw an unsupported paper status.
>> >
>> > Please restart your scanner and test 600 dpi directly. And please
>> try a
>> > multi page ADF scan after you repowered your scanner.
>> >
>> > Please send new log files. Then I'll patch this next weekend.
>> >
>> > Cheers,
>> > Rolf
>> >
>> > > /Troels
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > 2014-09-03 21:15 GMT+02:00 Rolf Bensch <rolf at bensch-online.de
>> <mailto:rolf at bensch-online.de>
>> > > <mailto:rolf at bensch-online.de <mailto:rolf at bensch-online.de>>>:
>> > >
>> > > Hi Troels,
>> > >
>> > > OK, based on recent git code I prepared a new patch.
>> > >
>> > > With this patch I revert last patch2 and try to fix scan end
>> detection.
>> > >
>> > > If this patch is working for flatbed, please test ADF
>> scanning.
>> > >
>> > > Please send me a log file from ADF scanning, whatever it's
>> running or
>> > > not. If ADF gets stuck, please send me an ADF log file from
>> windows.
>> > >
>> > > Cheers,
>> > > Rolf
>> > >
>> > >
>> > > Am 31.08.2014 <tel:31.08.2014> <tel:31.08.2014
>> > <tel:31.08.2014>> um 09:31 schrieb Troels Thomsen:
>> > > >
>> > > > I have done a lot of testing with scan areas of 5 by 5
>> milimeters, and
>> > > > that gives a false picture of what works and what does not.
>> (slightly
>> > > > different behaviour on BJNP and USB)
>> > > > Sorry
>> > > >
>> > > > Let's go back to usb and scanning large areas:
>> > > >
>> > > > Patch 1 (usb vid/pid) works, but scanner hangs in
>> "scanning".
>> > > >
>> > > > Patch 2 (generation 1), makes scanning fail as seen in
>> logfile of
>> > > > previous post.
>> > > >
>> > > >
>> > > > I've tested with git revision of ~ 1 august , and of today,
>> and picture
>> > > > is the same. Patch 2 makes it fail.
>> > > >
>> > > > Could it be that it's not a classic generation 1 or
>> generation 2, but a
>> > > > mix somehow?
>> > > >
>> > > >
>> > > > /Troels
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > 2014-08-30 12:55 GMT+02:00 Rolf Bensch <
>> rolf at bensch-online.de <mailto:rolf at bensch-online.de>
>> > <mailto:rolf at bensch-online.de <mailto:rolf at bensch-online.de>>
>> > > > <mailto:rolf at bensch-online.de <mailto:rolf at bensch-online.de
>> >
>> > <mailto:rolf at bensch-online.de <mailto:rolf at bensch-online.de>>>>:
>> > > >
>> > > > Hi Troels,
>> > > >
>> > > > Am 30.08.2014 <tel:30.08.2014> <tel:30.08.2014
>> > <tel:30.08.2014>> <tel:30.08.2014 <tel:30.08.2014>
>> > > <tel:30.08.2014 <tel:30.08.2014>>> um 06:44 schrieb Troels
>> > Thomsen:
>> > > > > It seems that there is a problem with mf8230 usb
>> scanning.
>> > > > >
>> > > > > I'm pretty sure I did the testing with the patches I
>> got,
>> > > but now
>> > > > when I
>> > > > > pull from git, it fails.
>> > > > > Was anything added/changed recently in pixma backend,
>> > that could
>> > > > > influence mf8230?
>> > > >
>> > > > I did a smarter implementation for setting the
>> generation
>> > > version = 1.
>> > > > But it's working, as you can see in the log file.
>> > > >
>> > > > Are you sure that you disconnected the LAN interface
>> while
>> > > testing USB?
>> > > > And can you scan via LAN only?
>> > > >
>> > > > If this doesn't help, please go back to the debugged
>> Sane
>> > > version and
>> > > > patch the files again. Please send me a working log
>> file.
>> > > >
>> > > > Cheers,
>> > > > Rolf
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20141107/5130a372/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: win_xp_platen_glass.png
Type: image/png
Size: 25108 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20141107/5130a372/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: win_xp_adf.png
Type: image/png
Size: 25551 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20141107/5130a372/attachment-0003.png>
More information about the sane-devel
mailing list