[sane-devel] Canon mf3110 and CanoScan 4400f
Aleksandr Charkov
alcharkov at riseup.net
Mon Sep 7 13:15:25 UTC 2009
I think it's same result and btw size of image is wrong (same as
previous image).
Nicolas Martin wrote:
> Good, we have now the appropriate protocol for mf3110.
>
> Now, the point is image encoding.
>
> I've just committed a change for trying to solve this or help
> investigate, could you get the latest git update, rebuild Sane, and give
> another try.
>
> Nicolas
>
> Le jeudi 03 septembre 2009 à 13:55 +0300, Aleksandr Charkov a écrit :
>
>> Hi,
>> it's now scanning and creating files. But colors are not nice, maybe
>> because i didn't made
>> properly configuration. I send you log and scanned book cover.
>>
>>
>> Nicolas Martin wrote:
>>
>>> Not sure you are running the git version for now.
>>>
>>> You probably ended with 2 versions of Sane on your system, the git one
>>> being in /usr/local may not be active, if you have another one in /usr
>>> coming from your distribution.
>>>
>>> You probably need to recompile Sane using the
>>> --prefix=/usr --sysconfdir=/etc in the ./configure statement.
>>> Check instructions on how to compile Sane on this blog:
>>> http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html
>>>
>>> Also, could you get the log trace as before, using the 2 statements I
>>> gave you hereunder, it will be easy to check whether it uses the
>>> expected protocol now:
>>>
>>> $ export SANE_DEBUG_PIXMA=11
>>> $ scanimage -T 2> someLogfile
>>>
>>> Nicolas
>>>
>>> Le lundi 31 août 2009 à 18:13 +0300, Aleksandr Charkov a écrit :
>>>
>>>
>>>> I don't know how exactly sane works, so I did this:
>>>>
>>>> downloaded git sane-backends, compiled it, installed with 'make install'
>>>> and ran it '/usr/local/bin/scanimage -T 2> mf3110.log'
>>>> Am I did right?
>>>>
>>>> Also, between this two messages: 'reading one scanline, 1920 bytes...'
>>>> and 'Error during device I/O';
>>>> scanner end to scan and waiting about 2 minutes.
>>>>
>>>> Nicolas Martin wrote:
>>>>
>>>>
>>>>> Thanks for this snoop.
>>>>> So first thing to do is to move mf3110 from imageclass to mp730 part of
>>>>> the pixma backend, and see how it goes from there.
>>>>>
>>>>> I've just committed this first change, could you update your git reposit
>>>>> and give another try, then send me back the log trace as you did
>>>>> previously
>>>>>
>>>>> Nicolas
>>>>>
>>>>> Le samedi 29 août 2009 à 14:56 +0300, Aleksandr Charkov a écrit :
>>>>>
>>>>>
>>>>>
>>>>>> Hello,
>>>>>> here it is
>>>>>>
>>>>>> Nicolas Martin wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> So it turns out that MF3110 does not use exactly the same Pixma protocol
>>>>>>> as other ImageClass devices.
>>>>>>>
>>>>>>> In order to go further into analysis, could you get a USB Snoop trace
>>>>>>> using SnoopyPro on Windows: You can record a log trace using
>>>>>>> SnoopyPro.exe, that you can download from sourceforge.net:
>>>>>>>
>>>>>>> http://sourceforge.net/projects/usbsnoop/
>>>>>>>
>>>>>>> Read instructions on SnoopyPro.exe, then try to record a scan session.
>>>>>>>
>>>>>>> => Select the device corresponding to the scanner, using its USB address
>>>>>>> 04a9:0x2660
>>>>>>>
>>>>>>> There will be ~4 devices holding this address.
>>>>>>> The scanner should be the one indicated by: "MF3110 ser"
>>>>>>>
>>>>>>> You can recognize that it's the correct one, if you look at the frame
>>>>>>> counter in SnoopyPro, it should increment only when MF3110 is scanning.
>>>>>>> This is important ... in order to avoid having huge log files filled up
>>>>>>> with useless data!
>>>>>>>
>>>>>>> Also, choose a **small** area to scan, otherwise, there will be huge
>>>>>>> amount of data.
>>>>>>>
>>>>>>> Then, Save As ... the file (in menu), zip the log and send it back to
>>>>>>> me.
>>>>>>>
>>>>>>> Nicolas
>>>>>>>
>>>>>>> Le jeudi 27 août 2009 à 19:46 +0300, Aleksandr Charkov a écrit :
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hello,
>>>>>>>> here is zipped log file.
>>>>>>>>
>>>>>>>> Nicolas Martin wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> mf3110 is declared in the pixma backend, as an ImageClass device, so
>>>>>>>>> running this protocol. But it has never been tested yet.
>>>>>>>>>
>>>>>>>>> In order to see if this is the adequate pixma protocol to use for this
>>>>>>>>> device, could you first send a log trace using the following commands:
>>>>>>>>>
>>>>>>>>> $ export SANE_DEBUG_PIXMA=11
>>>>>>>>> $ scanimage -T 2> someLogfile
>>>>>>>>>
>>>>>>>>> Zip and send back the someLogfile you'll get.
>>>>>>>>>
>>>>>>>>> Nicolas
>>>>>>>>>
>>>>>>>>> Le mardi 25 août 2009 à 16:00 +0300, Aleksandr Charkov a écrit :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>> I have two scanners, mf3110 and 4400f and computer with Debian. So I
>>>>>>>>>> know that 4400f unsupported and i tested it, it's true.
>>>>>>>>>> I tested mf3110 scanner quickly and it's scanning, but it didn't
>>>>>>>>>> transfer scanned data to hard disk (it showing something about i/o error).
>>>>>>>>>> So I want to collaborate with sane developers to improve this two
>>>>>>>>>> scanners, if you of course give me useful information.
>>>>>>>>>> Thank you!
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>>>>>>>>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>>>>>>>>>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>>>>>>>>> to sane-devel-request at lists.alioth.debian.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.jpg.zip
Type: application/zip
Size: 48653 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090907/feb6ed62/attachment-0001.zip>
More information about the sane-devel
mailing list