Hmm, I finally had some time to look at this log, and the scanner is
sending entirely black data. This might be a calibration problem, or
it might be that the scanner does not support grayscale. Perhaps you
could try a color scan?
allan
On Mon, Apr 20, 2015 at 8:12 PM, m. allan noah wrote:
> hmm
test.log.gz
https://drive.google.com/file/d/0B1s3C34oDHi5eGJYSk9pY25wYVk/view
Le lun. 20 avr. 2015 à 20:12, m. allan noah a écrit :
> hmm, can you try to get a debugging log like so:
>
> SANE_DEBUG_CANON_DR=35 scanimage --resolution 100 > test.pnm 2>test.log
>
> then send me a compressed version
hmm, can you try to get a debugging log like so:
SANE_DEBUG_CANON_DR=35 scanimage --resolution 100 > test.pnm 2>test.log
then send me a compressed version of test.log?
allan
On Mon, Apr 20, 2015 at 7:45 PM, Nicolas Marchildon
wrote:
> Duplex & resolution appear to be interpreted, since the num
Duplex & resolution appear to be interpreted, since the number of files and
scanning speed varies, but the ouput is always a black image.
Tried combinations of:
scanimage --resolution {100,600} {,--mode Color} {,--source "ADF Duplex"}
--batch
Le lun. 6 avr. 2015 à 21:40, m. allan noah a écrit
I have attached a patch which will hopefully improve the situation. I
have guessed at most of the parameters, and so we might have to
experiment. Please apply this to a current git repo, and try some
scans, simplex, duplex, color, gray, etc.
allan
On Wed, Apr 1, 2015 at 9:57 AM, Nicolas Marchildo
Le mar. 31 mars 2015 à 21:56, Nicolas Marchildon a
écrit :
> Can you get another usb log from windows, but this time with a low
>> resolution, color duplex scan, of only the top of the paper? If the
>> front side could have RGB written in those colors, and the back side
>> could be blank or have
Le mar. 31 mars 2015 à 20:55, m. allan noah a écrit :
> The image format from this machine is nothing like that from the
> DR-C125, and our attempt to descramble it using the same functions fails.
Oh, that's sad.
> Can you get another usb log from windows, but this time with a low
> resolutio
I went back and extracted the image data from your windows log. The
image format from this machine is nothing like that from the DR-C125,
and our attempt to descramble it using the same functions fails. Can
you get another usb log from windows, but this time with a low
resolution, color duplex scan
Le mar. 31 mars 2015 à 17:41, m. allan noah a écrit :
> SANE_DEBUG_CANON_DR=25 scanimage --resolution 150 > foo.pnm 2> drc225.log
>
See attached. The command hangs after the glibc error. Ctrl-c prints:
^Cscanimage: received signal 2
scanimage: trying to stop scanner
[canon_dr] sane_cancel: star
$ /usr/local/bin/scanimage --version
scanimage (sane-backends) 1.0.25git; backend version 1.0.25
$ sudo /usr/local/bin/scanimage -L
device `canon_dr:libusb:002:011' is a CANON DR-C225 scanner
$ sudo /usr/local/bin/scanimage --format=tiff >image.tiff
*** glibc detected *** /usr/local/bin/scanimage
How about this:
SANE_DEBUG_CANON_DR=25 scanimage --resolution 150 > foo.pnm 2> drc225.log
and send that log file.
allan
On Tue, Mar 31, 2015 at 5:33 PM, Nicolas Marchildon
wrote:
> $ /usr/local/bin/scanimage --version
> scanimage (sane-backends) 1.0.25git; backend version 1.0.25
>
> $ sudo /us
The log looks very similar to the DR-C125. Can you try building a
current sane-backends git snapshot, and try the code? You might have
to run as root user until we get the permissions sorted out.
allan
On Tue, Mar 31, 2015 at 9:31 AM, Nicolas Marchildon
wrote:
> After few attempts (reboot, locke
After few attempts (reboot, locked device, etc.), I managed to sniff only
the device. The device is "connected" to the VirtualBox instance.
https://drive.google.com/file/d/0B1s3C34oDHi5QTFyMDdmVVNaNTA/view
Le mar. 31 mars 2015 à 07:20, m. allan noah a écrit :
> my scripts currently don't handle
This is on Windows XP. For some reason, I was not capturing anything until
I included the USB hub *and* the scanner. Is the log worthless?
Le lun. 30 mars 2015 à 21:33, m. allan noah a écrit :
> Your log has the packets from two different devices in it, or
> something else strange is going on. W
my scripts currently don't handle having this kind of mixed data in
one log. I could update them I suppose, but it would be easier to get
a smaller log- can you try bypassing the hub when making the log?
Connect the scanner directly to the machine?
allan
On Mon, Mar 30, 2015 at 10:06 PM, Nicolas
Your log has the packets from two different devices in it, or
something else strange is going on. What OS was this captured on?
allan
On Mon, Mar 30, 2015 at 9:15 PM, m. allan noah wrote:
> have you tried to use a recent sane-backends git snapshot? I would be
> interested to see a debugging log
have you tried to use a recent sane-backends git snapshot? I would be
interested to see a debugging log of sane trying to make a scan.
allan
On Mon, Mar 30, 2015 at 9:08 PM, Nicolas Marchildon
wrote:
> Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's
> CaptureOnTouch and Usb Snif
Scanning a blank page at 150 dpi, 24 bit, simplex, using Canon's
CaptureOnTouch and Usb Sniffer from
http://www.pcausa.com/Utilities/UsbSnoop/
58 MB log
https://drive.google.com/file/d/0B1s3C34oDHi5ZzFqd3E4Nk5uekE/view
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.al
18 matches
Mail list logo
