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