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
Wilhelm,
I wasn't sure what you meant with
Wilhelm Meier-2 wrote
> So please change the bool-expression in this if() to trueand test, please.
So I commented the outer if statementand recompiled. That's working now for
all buttons.
Thanks a lot for your efforts!
Kind regards,
Rainer
--
View t
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
Am 31.03.2015 um 15:43 schrieb RainerF:
> Wilhelm,
>
> thank you for taking the time to look into these issues. Following your
> advise I had a look into the source code and tried to understand, what
> happens in case, when e.g. button 3 is pressed and compared the logs
> with the information by p
this line is printed in the logging data. The backend seems to work properly
as well. Its just a guess: either there is no value change for button 1 and
4 or the values are not numerical. (?)
I assume the hardware is ok as well, because I used the old scanbuttend with
Debian Wheezy so far, and ther
Am 31.03.2015 um 15:43 schrieb RainerF:
> Wilhelm,
>
> thank you for taking the time to look into these issues. Following your
> advise I had a look into the source code and tried to understand, what
> happens in case, when e.g. button 3 is pressed and compared the logs
> with the information by p
Wilhelm,
thank you for taking the time to look into these issues. Following your
advise I had a look into the source code and tried to understand, what
happens in case, when e.g. button 3 is pressed and compared the logs with
the information by pressing e.g. button 4 (log file excerpt - see below)
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
13 matches
Mail list logo
