[sane-devel] Is a model supported or not ?

[Nicolas Lécureuil]

Hi

i have a small question because for the Canon 4400F, if i look in the 
code of the genesys backend ( backend/genesys_devices.c ) i can see:


static Genesys_Model canon_4400f_model = {
  "canon-canoscan-4400f",/* Name */
  "Canon",/* Device vendor string */
  "Canoscan 4400f",/* Device model name */
  GENESYS_GL843,
  NULL,

  { 4800, 2400, 1200, 600, 400, 300, 200, 150, 100, 0},
  { 4800, 2400, 1200, 600, 400, 300, 200, 150, 100, 0},
  {16, 8, 0},/* possible depths in gray mode */
  {16, 8, 0},/* possible depths in color mode */

  SANE_FIX (6.0),/* Start of scan area in mm  (x) */
  SANE_FIX (13.00),/* Start of scan area in mm (y) */
  SANE_FIX (217.9),/* Size of scan area in mm (x) 5148 
pixels at 600 dpi*/

  SANE_FIX (315.0),/* Size of scan area in mm (y) */

  SANE_FIX (3.0),/* Start of white strip in mm (y) */
  SANE_FIX (0.0),/* Start of black mark in mm (x) */

  SANE_FIX (8.0),/* Start of scan area in TA mode in mm 
(x) */
  SANE_FIX (13.00),/* Start of scan area in TA mode in 
mm (y) */
  SANE_FIX (217.9),/* Size of scan area in TA mode in mm 
(x) */
  SANE_FIX (250.0),/* Size of scan area in TA mode in mm 
(y) */


  SANE_FIX (40.0),/* Start of white strip in TA mode in 
mm (y) */


  SANE_FIX (0.0),/* Size of scan area after paper sensor 
stops

   sensing document in mm */
  SANE_FIX (0.0),/* Amount of feeding needed to eject 
document

   after finishing scanning in mm */

  0, 24, 48,/* RGB CCD Line-distance correction 
in line number */

  /* 0 38 76 OK 1200/2400 */
  /* 0 24 48 OK [100,600] dpi */

  COLOR_ORDER_RGB,/* Order of the CCD/CIS colors */

  SANE_FALSE,/* Is this a CIS scanner? */
  SANE_FALSE,/* Is this a sheetfed scanner? */
  CCD_CS4400F,
  DAC_G4050,
  GPO_CS4400F,
  MOTOR_G4050,
  GENESYS_FLAG_NO_CALIBRATION |
  GENESYS_FLAG_LAZY_INIT |
  GENESYS_FLAG_OFFSET_CALIBRATION |
  GENESYS_FLAG_STAGGERED_LINE |
  GENESYS_FLAG_SKIP_WARMUP |
  GENESYS_FLAG_DARK_CALIBRATION |
  GENESYS_FLAG_FULL_HWDPI_MODE |
  GENESYS_FLAG_HALF_CCD_MODE |/* actually quarter CCD 
mode ... */

  GENESYS_FLAG_CUSTOM_GAMMA,
  GENESYS_HAS_SCAN_SW | GENESYS_HAS_FILE_SW | GENESYS_HAS_COPY_SW,
  100,
  100
};


and other that tend to show the model is supported.


but in ./descriptions/genesys.desc we have:

:model "CanoScan 4400F"
:url "/unsupported/canon-4400.html"
:interface "USB"
:usbid "0x04a9" "0x2228"
:status :unsupported
:comment "GL843 based, to be added to genesys backend"

--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] CanoScan 4400F

[Nicolas Lécureuil]

Hi,

I just tried my Canon 4400F with xsane.

As a user it claims that there is no device but starting xsane as root 
makes the scanner to react " small impulse " but xsane does not start.


# scanimage -L
device `genesys:libusb:003:005' is a Canon Canoscan 4400f flatbed 
scanner



Looking at the genesys backend source code show that the Canon 4400F is 
supposed to work ( if i understand it correctly ).


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] CanoScan 4400F (again)

[Nicolas Lécureuil]

Hello, I've 4400F scanner and see that you have it in unsupported list
but with 'GL843 based, to be added to genesys backend' description.
So, what I need to do to help to develop it, do I need to send usb logs
to you folks or to develop driver by myself?

--
Aleksandr Charkov


Hi,

i just got this scanner too. I am interested in testing /helping to have 
it working too.


--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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 of test.log?
>
> allan
>
> On Mon, Apr 20, 2015 at 7:45 PM, Nicolas Marchildon
>  wrote:
> > 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 Marchildon
> >>  wrote:
> >> > 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 black writing, that would help.
> >> >>
> >> >>
> >> >> I'll do that tomorrow. I have attached what I plan to scan. I assume
> a
> >> >> large font is going to make it easier to spot.
> >> >
> >> >
> >> > I cut the bottom of the sheet off in an attempt to reduce file size,
> but
> >> > it's slightly bigger. I can't go lower than 150 dpi.
> >> >
> >> > https://drive.google.com/file/d/0B1s3C34oDHi5UkowLTVaZDZsSVk/view
> >>
> >>
> >>
> >> --
> >> "well, I stand up next to a mountain- and I chop it down with the edge
> >> of my hand"
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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 Marchildon
>  wrote:
> > 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 black writing, that would help.
> >>
> >>
> >> I'll do that tomorrow. I have attached what I plan to scan. I assume a
> >> large font is going to make it easier to spot.
> >
> >
> > I cut the bottom of the sheet off in an attempt to reduce file size, but
> > it's slightly bigger. I can't go lower than 150 dpi.
> >
> > https://drive.google.com/file/d/0B1s3C34oDHi5UkowLTVaZDZsSVk/view
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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 black writing, that would help.
>
>
> I'll do that tomorrow. I have attached what I plan to scan. I assume a
> large font is going to make it easier to spot.
>

I cut the bottom of the sheet off in an attempt to reduce file size, but
it's slightly bigger. I can't go lower than 150 dpi.

https://drive.google.com/file/d/0B1s3C34oDHi5UkowLTVaZDZsSVk/view
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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
> 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 black writing, that would help.


I'll do that tomorrow. I have attached what I plan to scan. I assume a
large font is going to make it easier to spot.


rgb.pdf
Description: Adobe PDF document


rgb.odg
Description: application/vnd.oasis.opendocument.graphics
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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: start
[canon_dr] sane_cancel: finish
^Cscanimage: received signal 2
scanimage: aborting
[sanei_debug] Setting debug level of canon_dr to 25.
[canon_dr] sane_init: start
[canon_dr] sane_init: canon_dr backend 1.0.49, from sane-backends 1.0.25git
[canon_dr] sane_init: finish
[canon_dr] sane_get_devices: start
[canon_dr] sane_get_devices: reading config file canon_dr.conf
[canon_dr] sane_get_devices: looking for 'scsi CANON CR'
[canon_dr] sane_get_devices: looking for 'scsi CANON DR'
[canon_dr] sane_get_devices: setting "duplex-offset" to 840
[canon_dr] sane_get_devices: setting "vendor-name" to CANON
[canon_dr] sane_get_devices: setting "model-name" to DR-2080C
[canon_dr] sane_get_devices: setting "version-name" to 
[canon_dr] sane_get_devices: setting "padded-read" to 1
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1601'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1602'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1603'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1604'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1606'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1607'
[canon_dr] sane_get_devices: setting "duplex-offset" to 432
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1608'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1609'
[canon_dr] sane_get_devices: setting "duplex-offset" to 840
[canon_dr] sane_get_devices: setting "vendor-name" to CANON
[canon_dr] sane_get_devices: setting "model-name" to DR-2050C
[canon_dr] sane_get_devices: setting "version-name" to 
[canon_dr] sane_get_devices: setting "padded-read" to 1
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x160a'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x160b'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x160c'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x160f'
[canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1614'
[canon_dr] sane_get_devices: setting "duplex-offset" to 400
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1617'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1618'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x161a'
[canon_dr] sane_get_devices: setting "duplex-offset" to 400
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x161b'
[canon_dr] sane_get_devices: setting "duplex-offset" to 400
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x161d'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1620'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1622'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1623'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1624'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1626'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x162b'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1638'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1639'
[canon_dr] sane_get_devices: setting "extra-status" to 1
[canon_dr] sane_get_devices: setting "duplex-offset" to 400
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x163e'
[canon_dr] sane_get_devices: setting "extra-status" to 1
[canon_dr] sane_get_devices: setting "duplex-offset" to 400
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x163f'
[canon_dr] sane_get_devices: setting "duplex-offset" to 400
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1640'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1641'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1646'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1648'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x164a'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x164b'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x164c'
[canon_dr] sane_get_devices: config option "buffer-size" (800) is > 2097152, scanning problems may result
[canon_dr] sane_get_devices: setting "buffer-size" to 800
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x164f'
[canon_dr] sane_get_devices: config option "buffer-size" (800) is > 2097152, scanning problems may result
[canon_dr] sane_get_devices: setting "buffer-size" to 800
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1650'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1651'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1652'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1654'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1657'
[canon_dr] sane_get_devices: looking for 'usb 0x1083 0x1658'
[canon_dr] attach_one: start
[canon_dr] attach_one: looking for 'libusb:002:011'
[canon_dr] connect_fd: start
[canon_dr] 

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

ocal/lib/sane/libsane-artec.so.1.0.25
7fb4973cf000-7fb4975cf000 ---p 00013000 fd:00 1207586
 /usr/local/lib/sane/libsane-artec.so.1.0.25
7fb4975cf000-7fb4975d rw-p 00013000 fd:00 1207586
 /usr/local/lib/sane/libsane-artec.so.1.0.25
7fb4975d-7fb4975d8000 rw-p  00:00 0
7fb4975d8000-7fb4975ef000 r-xp  fd:00 1207590
 /usr/local/lib/sane/libsane-artec_eplus48u.so.1.0.25
7fb4975ef000-7fb4977ef000 ---p 00017000 fd:00 1207590
 /usr/local/lib/sane/libsane-artec_eplus48u.so.1.0.25
7fb4977ef000-7fb4977f rw-p 00017000 fd:00 1207590
 /usr/local/lib/sane/libsane-artec_eplus48u.so.1.0.25
7fb4977f-7fb4977f6000 rw-p  00:00 0
7fb4977f6000-7fb4977fd000 r-xp  fd:00 1207594
 /usr/local/lib/sane/libsane-as6e.so.1.0.25
7fb4977fd000-7fb4979fc000 ---p 7000 fd:00 1207594
 /usr/local/lib/sane/libsane-as6e.so.1.0.25

Le mar. 31 mars 2015 à 12:30, m. allan noah  a écrit :

> 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, 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 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 Marchildon
> >>  wrote:
> >> > 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. 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 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 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.alioth.debian.org/cgi-bin/mailman/listinfo/sane
> -devel
> >> >> >> Unsubscribe: Send mail with subject "unsubscribe your_password"
> >> >> >>  to sane-devel-requ...@lists.alioth.debian.org
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > "well, I stand up next to a mountain- and I chop it down with the
> >> >> > edge
> >> >> > of my hand"
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> "well, I stand up next to a mountain- and I chop it down with the
> edge
> >> >> of my hand"
> >>
> >>
> >>
> >> --
> >> "well, I stand up next to a mountain- and I chop it down with the edge
> >> of my hand"
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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 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 Marchildon
>  wrote:
> > 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. 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 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 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.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> >> >> Unsubscribe: Send mail with subject "unsubscribe your_password"
> >> >>  to sane-devel-requ...@lists.alioth.debian.org
> >> >
> >> >
> >> >
> >> > --
> >> > "well, I stand up next to a mountain- and I chop it down with the edge
> >> > of my hand"
> >>
> >>
> >>
> >> --
> >> "well, I stand up next to a mountain- and I chop it down with the edge
> >> of my hand"
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

Re: [sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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. 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 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 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.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> >> Unsubscribe: Send mail with subject "unsubscribe your_password"
> >>  to sane-devel-requ...@lists.alioth.debian.org
> >
> >
> >
> > --
> > "well, I stand up next to a mountain- and I chop it down with the edge
> > of my hand"
>
>
>
> --
> "well, I stand up next to a mountain- and I chop it down with the edge
> of my hand"
>
-- 
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] UsbSnoop for Canon DR-C225

[Nicolas Marchildon]

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.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
 to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] Samsung multi-function SL-C460W printer

[Nicolas Boullis]

Hi,

For what it?s worth, I just had the opportunity to test a SL-C460W 
multi-function printer with sane?s xerox_mfp back-end.
As far as I can see, it seems to work correctly on my laptop, as long as 
it is on AC power.
The output of sane-find-scanner -v -v is attached to this e-mail (I 
stripped the parts about non-relevant USB devices).
This device is currently shown as untested on 
  http://www.sane-project.org/sane-mfgs.html#Z-SAMSUNG
Please tell me if there?s anything I should test.

Note that when my laptop is on battery, it does not work at all. The USB 
device apparently gets disconnected/reconnected whenever I try to use 
it. Running "scanimage -L" sometimes shows the scanner, sometimes not. I 
guess it is a power-management problem, possibly unrelated to the 
xerox_mfp driver.

Cheers,

-- 
Nicolas Boullis
-- next part --
This is sane-find-scanner from sane-backends 1.0.22

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/sg0... failed to open (Invalid argument)
checking /dev/sg1... failed to open (Invalid argument)
checking /dev/sg2... failed to open (Invalid argument)
checking /dev/sg3... failed to open (Invalid argument)
checking /dev/sg4... failed to open (Invalid argument)
checking /dev/sg5... failed to open (Invalid argument)
checking /dev/sg6... failed to open (Invalid argument)
checking /dev/sg7... failed to open (Invalid argument)
checking /dev/sg8... failed to open (Invalid argument)
checking /dev/sg9... failed to open (Invalid argument)
checking /dev/sga... failed to open (Invalid argument)
checking /dev/sgb... failed to open (Invalid argument)
checking /dev/sgc... failed to open (Invalid argument)
checking /dev/sgd... failed to open (Invalid argument)
checking /dev/sge... failed to open (Invalid argument)
checking /dev/sgf... failed to open (Invalid argument)
checking /dev/sgg... failed to open (Invalid argument)
checking /dev/sgh... failed to open (Invalid argument)
checking /dev/sgi... failed to open (Invalid argument)
checking /dev/sgj... failed to open (Invalid argument)
checking /dev/sgk... failed to open (Invalid argument)
checking /dev/sgl... failed to open (Invalid argument)
checking /dev/sgm... failed to open (Invalid argument)
checking /dev/sgn... failed to open (Invalid argument)
checking /dev/sgo... failed to open (Invalid argument)
checking /dev/sgp... failed to open (Invalid argument)
checking /dev/sgq... failed to open (Invalid argument)
checking /dev/sgr... failed to open (Invalid argument)
checking /dev/sgs... failed to open (Invalid argument)
checking /dev/sgt... failed to open (Invalid argument)
checking /dev/sgu... failed to open (Invalid argument)
checking /dev/sgv... failed to open (Invalid argument)
checking /dev/sgw... failed to open (Invalid argument)
checking /dev/sgx... failed to open (Invalid argument)
checking /dev/sgy... failed to open (Invalid argument)
checking /dev/sgz... failed to open (Invalid argument)
  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

searching for USB scanners:
checking /dev/usb/scanner... failed to open (Invalid argument)
checking /dev/usb/scanner0... failed to open (Invalid argument)
checking /dev/usb/scanner1... failed to open (Invalid argument)
checking /dev/usb/scanner2... failed to open (Invalid argument)
checking /dev/usb/scanner3... failed to open (Invalid argument)
checking /dev/usb/scanner4... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner5... failed to open (Invalid argument)
checking /dev/usb/scanner7... failed to open (Invalid argument)
checking /dev/usb/scanner8... failed to open (Invalid argument)
checking /dev/usb/scanner9... failed to open (Invalid argument)
checking /dev/usb/scanner10... failed to open (Invalid argument)
checking /dev/usb/scanner11... failed to open (Invalid argument)
checking /dev/usb/scanner12... failed to open (Invalid argument)
checking /dev/usb/scanner13... failed to open (Invalid argument)
checking /dev/usb/scanner14... failed to open (Invalid argument)
checking /dev/usb/scanner15... failed to open (Invalid argument)
checking /dev/usbscanner... failed to open (Invalid argument)
checking /dev/usbscanner0... failed to open (Invalid argument)
checking /dev/usbscanner1... failed to open (Invalid argument)
checking /dev/usbscanner2... failed to open (Invalid argument)
checking /dev/usbscanner3... failed to open (Invalid argument)
checking /dev/usbscanner4... failed to open (Invalid argument)
checking /dev/usbscanner5... failed to open (Invalid argument)
checking /dev/usbscanner6... failed to open (Invalid argument)
checking /dev/u

[sane-devel] Troubles with PIXMA MX870 and USB

[Nicolas Martin]

To scan in Duplex ADF mode, you need to set 2 pages to scan in Xsane.
Otherwise, it will stop at the first page.

Did you try that ?

Nicolas

Le lundi 31 janvier 2011 ? 12:08 +0100, Stephan Ritscher a ?crit :
> Hi folks,
> 
> I just got a new Canon Pixma MX870, but it doesn't work completely,
> yet.
> 
> Let me start with my setup. I run Gentoo with kernel 2.6.36-gentoo-r5
> on an Intel(R) Core(TM)2 Duo CPU T9300. I use the latest sane-backends
> from GIT and sane-frontends-1.0.14.
> 
> I want to run the scanner in two different configurations - via
> wireless network and via usb. I'll start with the wireless setup.
> 
> First of all, it recognizes my printer - kind of. My router (EasyBox
> 803) resolves all ip addresses in the local network as "localhost" and
> thereby confuses SANE.
> # /usr/libexec/cups/backend/bjnp
> network bjnp://localhost:8611 "Canon MX870 series" "Canon
> MX870 series localhost"
> 
> "MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:TXT01,BJNP2;MDL:MX870
>  series;CLS:PRINTER;DES:Canon MX870 
> series;VER:1.030;STA:10;FSI:04;HRI:EU;MSI:DAT,E3,HFSF;PDR:4;"
> If I add the line "bjnp://192.168.2.101:8612"
> to /etc/sane.d/pixma.conf, scanimage and other applications recognize
> my scanner and work properly. I attached the log file corresponding to
> # export SANE_DEBUG_PIXMA=3
> # scanimage -T 2> scan-net.log
> ADF is working, too, but I didn't get "ADF Duplex" running (Xsane
> scans one page and then stops - is this supposed to work, anyways?).
> Now trying USB cable, I removed the extra line
> from /etc/sane.d/pixma.conf. After attaching the USB cable, I get
> # dmesg -c
> usb 2-2.1: new high speed USB device using ehci_hcd and
> address 8
> usblp0: USB Bidirectional printer dev 8 if 1 alt 0 proto 2 vid
> 0x04A9 pid 0x1743
> scsi7 : usb-storage 2-2.1:1.2
> usblp1: USB Bidirectional printer dev 8 if 3 alt 0 proto 2 vid
> 0x04A9 pid 0x1743
> scsi 7:0:0:0: Direct-Access CanonMX870 series 0103
> PQ: 0 ANSI: 2
> sd 7:0:0:0: Attached scsi generic sg2 type 0
> sd 7:0:0:0: [sdb] Attached SCSI removable disk
> I also attached the gzipped output of
> # lsusb -v > lsusb.log
> Now I ran
> # scanimage -T 2> scan-usb.log
> The scanner makes some noises, but the command returns immediately.
> Xsane fails with "Error during read: Error during device I/O".
> 
> In some forum I read that unloading ehci_hcd helps. Thus I tried
> # sudo rmmod ehci_hcd
> # scanimage -T 2> scan-usb2.log
> The scanner shows "Processing... Please wait momentarily.", but makes
> no noises of activity. Since scanimage gets stuck, I terminated it
> with kill -9. The "Processing..." message only disappears on
> unplugging the USB connection.
> 
> Do you have any suggestions?
> 
> Best regards
> Stephan Ritscher
> 
> --
> 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

[sane-devel] diffs sent to support MP810, MP960, Canoscan 9000F

[Nicolas Martin]

I checked that it currently compiles with gcc 4.4.3, but this statement
gies a warning message telling %llu is not supported. 

If this is not advisable to leave PRIu64 here, for compatibility with
all systems, then we will need to remove it. 

Nicolas

Le lundi 17 janvier 2011 ? 02:17 +0900, Gernot Hassenpflug a ?crit :
> On Sun, Jan 16, 2011 at 7:58 PM, m. allan noah  wrote:
> > Is PRlu64 C89? If not, you will have to drop that change. Someday sane
> > will use C99 :)
> 
> Hi Allan,
> 
> Nicolas already added the PRIu64 to the pixma backend, so I guess it
> is okay. I think it is C90, but have not checked myself.
> 
> Regards,
> Gernot
> 
> --
> 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

[sane-devel] Canon Image Class MF4150 scanner with Automatic Docment Feeder as Source

[Nicolas Martin]

Well, for all "ImageClass" MFPs, the maximum width and height scan is
currently set to 640 x 877 pixels at 75 dpi, this corresponds to:

640 / 75 * 2.54 cm = 21,67 cm in width
877 / 75 * 2.54 cm = 29,70 cm in height

Those values are set in the backend, file pixma_imageclass.c, at the end
of the file, separately for each model supported in this file. There's a
line corresponding to MF4150.

Although never tested, you could try to change those values to bigger
ones corresponding to A3, and see if the scanner accepts them :

This would be, a size like : 877 x 1280 instead of 640 x 877 

DEV ("Canon imageCLASS MF4150", "MF4100", MF4100_PID, 600, 877, 1280,
PIXMA_CAP_ADF)

Let us know then.

N

Le dimanche 09 janvier 2011 ? 14:52 +0100, Tomas Pospisek a ?crit :
> On Wed, 5 Jan 2011, Mohammed Rashid wrote:
> 
> > I am using Canon Image Class MF4150 scanner with Automatic Docment Feeder 
> > as Source. My OS is
> > OpenSuSE 11.2. But I am unable to the get the whole image. From bottom I am 
> > missing few lines.
> > How can set the A3 etc??
> 
> Could this be the same problem as this one here? :
> 
> 
> http://lists.alioth.debian.org/pipermail/sane-devel/2010-December/027876.html
> 
> *t
> 
> 
> --
> 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

[sane-devel] still segmentation fault on MP900, MP950

[Nicolas Martin]

Hopefully, code and declarations for those 2 old models, MP900 and
MP950, is not part of the git version, probably this is from a test
version you're currently using for debugging. 

Those 2 Pixma models are more than 5 years old, so probably not
strategic to have them supported for the next Sane release, as nobody
asked for support to these models, since I'm working on the pixma
backend.

Let us know anyway when this issue will be fixed, and when these models
will be ready for support.

Nicolas

Le dimanche 09 janvier 2011 ? 17:13 +0900, Gernot Hassenpflug a ?crit :
> Hi,
> 
> I did not have time to invetigate segmentation problems on the MP900,
> MP950 before now. They still exist.
> With SANE_DEBUG_PIXMA set to 11, I get the following output from
> running xsane (sane-find-scanner finds the scanner also, no problem):
> 
> ...
> [pixma] scanner discovery finished...
> [pixma] pixma_open(): Canon PIXMA MP900
> [pixma] OUT  T=3.637 len=16
> [pixma]  :f3 20 00 00 00 00 00 00  00 00 00 00 00 00 00 0c
> [pixma]
> [pixma] IN   T=3.641 len=2
> [pixma]  :15 15
> [pixma]
> [pixma] WARNING: result len=2 expected 20
> [pixma]  :15 15
> [pixma] INTR T=3.671 len=16
> [pixma]  :00 00 00 00 00 00 00 00  00 00 00 00 40 00 00 00
> [pixma]
> Segmentation fault
> 
> It only occurs with these two models of scanners as far as I can tell.
> 
> My OS uname details:
> 
> Linux 2.6.32-5-686-bigmem #1 SMP Fri Dec 10 16:59:53 UTC 2010 i686 GNU/Linux
> 
> Using SANE CVS
> 
> Best regards,
> Gernot

[sane-devel] Schedule for release of sane-backends 1.0.22

[Nicolas Martin]

Hi,

Thanks for this pointer, very interesting and commented

So we have to be double careful when using memcpy though, even if it
acts faster than its cousin memmove !

Nicolas

Le samedi 08 janvier 2011 ? 09:43 +0100, Julien BLACHE a ?crit :
> Nicolas Martin  wrote:
> 
> Hi,
> 
> > What is weird here, is that the effect of overlap in memcpy does not
> > seem to produce the same effect on different systems !
> 
> Using memcpy() on overlapping memory areas is undefined behaviour per
> spec.
> 
> glibc has several memcpy() implementations optimized for different
> hardware capabilities. A recent implementation for Atom/Core2 CPUs
> performs the copy from tail to head (giving a nice 4x/5x speedup on
> these CPUs), which breaks with overlapping memory areas.
> 
> Using memmove() is the correct way to handle overlapping areas, as
> documented.
> 
> See <http://lwn.net/Articles/414467/> for more (links/comments).
> 
> HTH,
> 
> JB.
> 

[sane-devel] Schedule for release of sane-backends 1.0.22

[Nicolas Martin]

Thanks Dustin for your feedback. 

The issue of memmove vs memcpy appears in the last phase of image
processing, to reduce the scanned line width, in order to get an exact
scanned area width, and get rid of the Pixma modulo 32 line width.

Il this case, the cropped line is copied above the scanned line, that
explains the overlap situation, but the cropped line is always smaller,
so no risk of buffer overflow.

When the width is an exact multiple of 32, the cropped and original
lines are exactly identical. 

What is weird here, is that the effect of overlap in memcpy does not
seem to produce the same effect on different systems !
Looks some systems have memcpy to copy correctly above the original
line, but not others. 

Anyway, the memmove here handles correctly the overlap situation, so
this issue should be solved now.

Nicolas

Le vendredi 07 janvier 2011 ? 00:46 -0500, Dustin DeWeese a ?crit :
> After pulling commit e72c0f548eebfae0171ab8a2e2a74174c1bd96ae, the pixma 
> backend works correctly with my MX850; there is no corruption, even on 
> widths indivisible by 32.
> 
> Thanks!
> 
> - Dustin DeWeese
> 
> On 01/06/2011 04:19 PM, Nicolas Martin wrote:
> > AFAIK, I've currently only heard about this pending issue for the pixma
> > backend, reported by Dustin DeWeese:
> >
> > https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=312874&group_id=30186
> >
> > Maybe Dustin could give us more info about his current test status,
> > using the latest git ?
> >
> > Nicolas
> >
> >
> > Le jeudi 06 janvier 2011 ? 21:03 +0100, Tomas Pospisek a ?crit :
> >> On Wed, 5 Jan 2011, Julien BLACHE wrote:
> >>
> >>> "m. allan noah"  wrote:
> >>>
> >>> I also have a report for the AV120 (#548731).
> >>>
> >>>> I've not heard from Nicholas.
> >>> The pixma fix is still in work, IIRC we should hear back from Gernot in
> >>> the coming weeks.
> >> I think Gernot has confirmed that the one-line fix does fix the machines
> >> he has access to. It does also fix my own pixma mp600. We do not know
> >> though about generation 1 machines.
> >>
> >> Aren't we waiting for Nicholas' word on the issue?
> >> *t
> >>
> >> --
> >> 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
> >
> 

[sane-devel] Schedule for release of sane-backends 1.0.22

[Nicolas Martin]

AFAIK, I've currently only heard about this pending issue for the pixma
backend, reported by Dustin DeWeese: 

https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=312874&group_id=30186

Maybe Dustin could give us more info about his current test status,
using the latest git ?

Nicolas


Le jeudi 06 janvier 2011 ? 21:03 +0100, Tomas Pospisek a ?crit :
> On Wed, 5 Jan 2011, Julien BLACHE wrote:
> 
> > "m. allan noah"  wrote:
> >
> > I also have a report for the AV120 (#548731).
> >
> >> I've not heard from Nicholas.
> >
> > The pixma fix is still in work, IIRC we should hear back from Gernot in
> > the coming weeks.
> 
> I think Gernot has confirmed that the one-line fix does fix the machines 
> he has access to. It does also fix my own pixma mp600. We do not know 
> though about generation 1 machines.
> 
> Aren't we waiting for Nicholas' word on the issue?
> *t
> 
> --
> 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

[sane-devel] maximum image size for a scan for Canon pixma backend

[Nicolas Martin]

Le vendredi 31 d?cembre 2010 ? 14:11 +0900, Gernot Hassenpflug a ?crit :
> On Fri, Dec 31, 2010 at 8:11 AM, Gernot Hassenpflug
>  wrote:
> > On Fri, Dec 31, 2010 at 8:05 AM, Nicolas Martin
> >  wrote:
> >> Le vendredi 31 d?cembre 2010 ? 02:55 +0900, Gernot Hassenpflug a ?crit :
> >>> On Fri, Dec 31, 2010 at 2:50 AM, Robert Krawitz  
> >>> wrote:
> >>> > On Fri, 31 Dec 2010 02:41:10 +0900, Gernot Hassenpflug wrote:
> >>> >> On Fri, Dec 31, 2010 at 2:19 AM, Gerard Klaver  >>> >> xs4all.nl> wrote:
> >>> >>> On Fri, 2010-12-31 at 01:29 +0900, Gernot Hassenpflug wrote:
> >>> >>>> Dear all,
> >>> >>>> I have been involved in trying to support the Canoscan 9000F, and the
> >>> >>>> testing community has grown to about 15 individuals. A few of them
> >>> >>>> have programming knowledge and tonight one individual send in
> >>> >>>> corrected code to handle the final hurdle: correctly aligning the
> >>> >>>> sub-images in the 9600dpi TPU mode. So the scanner is now supported
> >>> >>>> for all modes.
> >>> >>>>
> >>> >>>> However, for large images at both 4800dpi and 9600dpi modes, it seems
> >>> >>>> the max size of the image is limited in some way, so that only a
> >>> >>>> section of the desired image is delivered. Is this something that can
> >>> >>>> be set in the individual driver files (like pixma_mp150.c) or in some
> >>> >>>> of the generic pixma driver .c or .h files (which I do not want to
> >>> >>>> touch if possible)? I don't see a problem in the linesize or
> >>> >>>> dimensions, only in the image_size value seen by [pixma] debugging
> >>> >>>> output.
> >>> >>>>
> >>> >>>> Best regards,
> >>> >>>> Gernot Hassenpflug
> >>> >>>>
> >>> >>>> --
> >>> >>>> 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
> >>> >>>
> >>> >>> One possible solution (if not yet done), is to check the declaration 
> >>> >>> of
> >>> >>> the  image_size parameter, for a 9600 dpi A4 scan (color) size is 
> >>> >>> about
> >>> >>> 550 000 000 000 bytes. (long long is needed)
> >>> >>
> >>> >> Hi, thank you for that. I see that image_size is currently declared as
> >>> >> "unsigned". I imagine that changing the declaration will need to be
> >>> >> checked in all places where the calculations using image_size are
> >>> >> done, or not?
> >>> >>
> >>> >> Currently, from the report I obtain from a test user, a 4800x4800dpi 
> >>> >> image with
> >>> >>
> >>> >> dimensions: 32824 px (width) * 47248 px (height)
> >>> >>
> >>> >> should have a image_size of 4652605056 bytes (W*H*3 for channel number)
> >>> >>
> >>> >> whereas the actual image_size used is 357637760 bytes (approximately
> >>> >> 341.1 MiB). I am still trying to ascertain whether for some reason the
> >>> >> wrong calculation for image_size might have been made, but certainly
> >>> >> the width and height are correctly there.
> >>> >
> >>> > 32824 * 47248 * 3 - 357637760 = 4294967296
> >>> >
> >>> > which is exactly 2^32.  So that suggests exactly the problem described
> >>> > above.
> >>>
> >>> Ah! I suspected it was that, but forgot I had to take the difference
> >>> to get this number. Fantastic! Well, that sounds like somewhat of a
> >>> issue then for the SANE Canon maintainer to comment on. I guess this
> >>> issue had to come up eventually.
> >>
> >> Should be possible to extend the image size in pixma backend by
> >> declaring uint64_t instead of unsigned the following variables:
> >>
> >> image_byte_r

[sane-devel] maximum image size for a scan for Canon pixma backend

[Nicolas Martin]

Le vendredi 31 d?cembre 2010 ? 02:55 +0900, Gernot Hassenpflug a ?crit :
> On Fri, Dec 31, 2010 at 2:50 AM, Robert Krawitz  wrote:
> > On Fri, 31 Dec 2010 02:41:10 +0900, Gernot Hassenpflug wrote:
> >> On Fri, Dec 31, 2010 at 2:19 AM, Gerard Klaver  >> xs4all.nl> wrote:
> >>> On Fri, 2010-12-31 at 01:29 +0900, Gernot Hassenpflug wrote:
> >>>> Dear all,
> >>>> I have been involved in trying to support the Canoscan 9000F, and the
> >>>> testing community has grown to about 15 individuals. A few of them
> >>>> have programming knowledge and tonight one individual send in
> >>>> corrected code to handle the final hurdle: correctly aligning the
> >>>> sub-images in the 9600dpi TPU mode. So the scanner is now supported
> >>>> for all modes.
> >>>>
> >>>> However, for large images at both 4800dpi and 9600dpi modes, it seems
> >>>> the max size of the image is limited in some way, so that only a
> >>>> section of the desired image is delivered. Is this something that can
> >>>> be set in the individual driver files (like pixma_mp150.c) or in some
> >>>> of the generic pixma driver .c or .h files (which I do not want to
> >>>> touch if possible)? I don't see a problem in the linesize or
> >>>> dimensions, only in the image_size value seen by [pixma] debugging
> >>>> output.
> >>>>
> >>>> Best regards,
> >>>> Gernot Hassenpflug
> >>>>
> >>>> --
> >>>> 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
> >>>
> >>> One possible solution (if not yet done), is to check the declaration of
> >>> the  image_size parameter, for a 9600 dpi A4 scan (color) size is about
> >>> 550 000 000 000 bytes. (long long is needed)
> >>
> >> Hi, thank you for that. I see that image_size is currently declared as
> >> "unsigned". I imagine that changing the declaration will need to be
> >> checked in all places where the calculations using image_size are
> >> done, or not?
> >>
> >> Currently, from the report I obtain from a test user, a 4800x4800dpi image 
> >> with
> >>
> >> dimensions: 32824 px (width) * 47248 px (height)
> >>
> >> should have a image_size of 4652605056 bytes (W*H*3 for channel number)
> >>
> >> whereas the actual image_size used is 357637760 bytes (approximately
> >> 341.1 MiB). I am still trying to ascertain whether for some reason the
> >> wrong calculation for image_size might have been made, but certainly
> >> the width and height are correctly there.
> >
> > 32824 * 47248 * 3 - 357637760 = 4294967296
> >
> > which is exactly 2^32.  So that suggests exactly the problem described
> > above.
> 
> Ah! I suspected it was that, but forgot I had to take the difference
> to get this number. Fantastic! Well, that sounds like somewhat of a
> issue then for the SANE Canon maintainer to comment on. I guess this
> issue had to come up eventually.

Should be possible to extend the image size in pixma backend by
declaring uint64_t instead of unsigned the following variables:

image_byte_read (in pixma.c), 
image_size (in pixma.h)
cur_image_size (in pixma_common.h)

Debug statements should also to be adjusted, %llu instead of %u in the
different format strings, although this gives a compilation warning
anyway, as the gcc compile statement uses the -pedantic flag. 

Unless someone has a better solution for sprintf 64 bits integers ?

Anyway, could you give a try on 9000F with those changes ?

Nicolas

[sane-devel] Pixma MP600 broken by 1430217e1919801fa6418c36589cc4360e5f1779

[Nicolas Martin]

2010/11/30 Gernot Hassenpflug 

> On Tue, Nov 30, 2010 at 5:53 AM, Nicolas Martin
>  wrote:
> > Le lundi 29 novembre 2010 ? 19:54 +0100, Tomas Pospisek a ?crit :
> >> On Mon, 29 Nov 2010, Tom?? Posp??ek wrote:
> >>
> >> [...]
> >>
> >> The same patch seems also to have broken Canon Pixma MP160 [1] and Pixma
> >> MP780 [2].
> >
> > Could you try first to change, in the current git version of Sane, the
> > following line in backend/pixma_mp150.c, at line 683:
> >
> >  if (s->cfg->pid == MP460_PID || s->cfg->pid == MP510_PID)
> >pixma_set_be32 (s->param->x - s->param->xs, data + 0x08);
> >
> > Take out the if condition, and leave only the second line:
> >
> >pixma_set_be32 (s->param->x - s->param->xs, data + 0x08);
>
>
> Hi Nicolas,
> That is quite strange. This is one of the patches which I believe I
> submitted during testing of various scanners, including the MP760/780.
> The MP460 and MP510 required a new addition (condition) which only
> have applied to them (for now) and no other devices, so I do not
> understand exactly how this affects unrelated devices. Unfortunately I
> now no longer have any of these machines, but I will compare the code
> I still have.
> Regards,
> Gernot Hassenpflug
>


Originaly, the patch provided by Christian Scholtz for fine cropping
adjustment, and uploaded in January 2010, was designed and tested on gen 3
devices, but I guess not on gen 2 devices, and was probably not working for
any gen 2 devices.
You probably noticed it when testing MP460 and MP510, that's why you fixed
the above line
(s->param->x - s->param->xs instead of s->param->x) but added a restriction
for those 2 models.
I'm just guessing here this fix is necessary for any gen 2 device as well.

nicolas
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20101130/b79419b8/attachment-0001.htm>

[sane-devel] Pixma MP600 broken by 1430217e1919801fa6418c36589cc4360e5f1779

[Nicolas Martin]

Le lundi 29 novembre 2010 ? 22:08 +0100, Tomas Pospisek a ?crit :
> I will, however I ask you to please bear with me until in a few days when 
> I'll be able to test the scanner again.

Ok

[sane-devel] Pixma MP600 broken by 1430217e1919801fa6418c36589cc4360e5f1779

[Nicolas Martin]

Le lundi 29 novembre 2010 ? 19:54 +0100, Tomas Pospisek a ?crit :
> On Mon, 29 Nov 2010, Tom?? Posp??ek wrote:
> 
> [...]
> 
> The same patch seems also to have broken Canon Pixma MP160 [1] and Pixma 
> MP780 [2].

Could you try first to change, in the current git version of Sane, the
following line in backend/pixma_mp150.c, at line 683:

  if (s->cfg->pid == MP460_PID || s->cfg->pid == MP510_PID)
pixma_set_be32 (s->param->x - s->param->xs, data + 0x08);

Take out the if condition, and leave only the second line:

pixma_set_be32 (s->param->x - s->param->xs, data + 0x08);

Then recompile/reinstall/retry

In this file, you'll see a lot of commented "PDBG" statements, could you
uncomment those, and take a debug level = 5 log trace:

$ export SANE_DEBUG_PIXMA=5
$ scanimage -T 2> /tmp/logfile

You should get a /tmp/logfile, please send it back, it could be checked
when it fails, and compare the output values with those from MP610,
which works.

nicolas

[sane-devel] NO scanner is now recognized. :(

[Nicolas Martin]

Could you describe a little bit more what was the issue with grayscale
scan on MX310 ?

BTW, B&W is currently not supported on this model, some more details
about how you were proceeding would be useful to step further.

Nicolas

Le lundi 27 septembre 2010 ? 14:36 -0400, m. allan noah a ?crit :
> I don't see any indication that grayscale or binary modes have been
> added to the MX310 (pixma) backend. It is possible that the backend
> only exposes the actual capabilites of the scanner.- hopefully one of
> the pixma authors can comment further.
> 
> allan
> 
> On Mon, Sep 27, 2010 at 1:07 AM, Mr Fair Go  wrote:
> >>> I compiled and installed the latest sane-backends-1.0.21 and tried to
> >>> use it with a Canon DR-2010C scanner,
> >
> > G'day!
> >
> > I have a Canon  MX310 which was scanning OK, but only in colour.  There was
> > some sort of bug in Greyscale and B&W.  I attempted to "compile and install"
> > the newer sane backends also, but as a newbie I clearly did something wrong,
> > because now none of my Linux scanning software will find the Canon or any
> > other scanner (I have 3).  I even uninstalled and reinstalled SANE and
> > gscan2pdf via the Package Manager, but still "
> >
> > Can someone point me to a very basic Linux how-to that explains for a newbie
> > exactly how to "compile and install" with Linux?  Everything I look at
> > assumes I have more knowledge about "compiling" than I actually have.
> >
> > Running LinuxMint 9 (Isadora) which is built on Ubuntu, for nearly a year
> > now.  Up to this point upgrading and installing packages via Package Manager
> > has been adequate for my needs, but the newer version is not available this
> > way, thus I attempted the more challenging route, but can not find
> > "instructions" anywhere.
> >
> > Thanks
> >
> > Mr Fair Go
> >
> >
> > (They call me "Mr Fair Go")
> > http://mrfairgo.com
> > fairgohomes.com.au -->a Fair Go for aspiring homeowners, sellers, investors,
> > renovators.
> > fairgocom.net.au -->a Fair Go for Getting Your Life & Privacy Back!
> > eservers.com.au -->Professional Internet Hosting
> >
> >
> > On Mon, Sep 27, 2010 at 1:12 PM, Ori Koren  wrote:
> >>
> >> On Sat, Sep 25, 2010 at 8:28 PM, Simon Matter 
> >> wrote:
> >> >> Hi,
> >> >>
> >> >> I compiled and installed the latest sane-backends-1.0.21 and tried to
> >> >> use it with a Canon DR-2010C scanner,
> >> >> but the scanner is not recognized (by scanadf -L, or scanimage -L).
> >> >> sane-find-scanner and lsusb can see the device.
> >>
> >> 
> >>
> >> >> Am I missing some option in one of the config files?
> >>
> >> 
> >>
> >> >> I am using an ubuntu 8.04.3. The libusb-0.1-4, libusb-dev versions are
> >> >> both 2:0.1.12-8
> >> >
> >> > What about permissions? Did you try as root also? And is the backend in
> >> > question enabled in your sane config?
> >> >
> >>
> >> OK, it's working now.
> >> The thing that was missing was to add "canon_dr" to /etc/sane.d/dll.conf
> >>
> >> > Simon
> >>
> >> Thanks,
> >> Ori
> >>
> >> --
> >> 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
> >
> >
> > --
> > 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
> >
> 
> 
> 

[sane-devel] question about SANE backend fill_buffer function

[Nicolas Martin]

Le mardi 07 septembre 2010 ? 19:47 +0900, Gernot Hassenpflug a ?crit :
> Dear all,
> 
> I am working on the pixma backend for Canon devices (variation:
> pixma_mp150.c), and have a question about registration of pixels in
> the y dimension.
> 
> Each backend I believe has variations on a _fill_buffer
> function called between _scan and <>_finish_scan.
> 
> The function reads sections of data from the scanner, and processes it
> line by line. Thus, pixels can be reorganized in the x-dimension.
> 
> I am not sure if the amount of data read at once is controllable.
> 
> I now have a problem where the pixels also need to be rearranged
> vertically. In particular, the first half of a line corresponds to the
> second half of a line much further along in the data.
> 
> Is there any backend that has support for such processing, that I can
> look at for help? Or have I misunderstood what can be done with the
> current mp150_fill_buffer function in pixma_mp150.c?
> 
Yes, as I answered you, the pixma_mp150 implements a vertical shift
reassembling that is needed by the CCD devices, as they produce scans
with vertically shifted color planes. Maybe you can just use this, or
use some modified version.

Nicolas

[sane-devel] scanner is no longer recognized over network

[Nicolas Martin]

[net] sane_open: net_open
[net] sane_open: remote open failed
scanimage: open of device net:192.168.0.102:pixma:04A91709 failed: Access to
resource has been denied
[net] sane_exit: exiting
What about the xinet (or inet ?) configuration you are using on the server:
is the user/group used for saned allowed to use the scanner on usb ?

Nicolas
2010/7/28 Seb 

> [update]
>
> I changed the clients' /etc/sane.d/net.conf to point exclusively to the
> IP address of the SANE server:
>
> 192.168.0.102
>
> and now the clients detect the scanner, but cannot use it:
>
> ---<cut here---start--->---
> $ scanimage -L
> device `net:192.168.0.102:pixma:04A91709' is a CANON Canon PIXMA MP150
> multi-function peripheral
>
> $ SANE_DEBUG_NET=255 scanimage -d 'net:192.168.0.102:pixma:04A91709' >
> /tmp/test.pnm
> [sanei_debug] Setting debug level of net to 255.
> [net] sane_init: authorize = 0x405920, version_code = 0x7fffdb391efc
> [net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from
> sane-backends 1.0.21
> [net] sane_init: Client has little endian byte order
> [net] sane_init: searching for config file
> [net] sane_init: trying to add 192.168.0.102
> [net] add_device: adding backend 192.168.0.102
> [net] add_device: backend 192.168.0.102 added
> [net] sane_init: trying to add [::1]
> [net] add_device: adding backend [::1]
> [net] add_device: error while getting address of host [::1]: Name or
> service not known
> [net] sane_init: trying to add localhost
> [net] add_device: adding backend localhost
> [net] add_device: backend localhost added
> [net] sane_init: done reading config
> [net] sane_init: evaluating environment variable SANE_NET_HOSTS
> [net] sane_init: evaluating environment variable SANE_NET_TIMEOUT
> [net] sane_init: done
> [net] sane_open("192.168.0.102:pixma:04A91709")
> [net] sane_open: host = 192.168.0.102, device = pixma:04A91709
> [net] sane_open: device found in list
> [net] sane_open: device not connected yet...
> [net] connect_dev: trying to connect to 192.168.0.102
> [net] connect_dev: [0] connection succeeded (IPv4)
> [net] connect_dev: sanei_w_init
> [net] connect_dev: net_init (user=sluque, local version=1.0.3)
> [net] connect_dev: freeing init reply (status=Success, remote
> version=1.0.3)
> [net] connect_dev: done
> [net] sane_open: net_open
> [net] sane_open: remote open failed
> scanimage: open of device net:192.168.0.102:pixma:04A91709 failed: Access
> to resource has been denied
> [net] sane_exit: exiting
> [net] net_avahi_cleanup: stopping thread
> [net] net_avahi_cleanup: done
> [net] sane_exit: closing dev 0x2361170, ctl=-1
> [net] sane_exit: closing dev 0x235ec50, ctl=6
> [net] sane_exit: finished.
> ---<cut here---end->---
>
> Seb
>
>
>
> On Tue, 27 Jul 2010 21:24:35 -0500,
> Seb  wrote:
>
> > Hi, My partner is about to strangle me because she can no longer scan
> > on our Canon Pixma MP150.  Following updates to Debian sid SANE
> > packages several weeks ago, this scanner is only seen on the machine
> > with the server.  We have 3 computers in a home network (on a router):
>
> > 192.168.0.100 192.168.0.101 192.168.0.102
>
>
> > The SANE server (saned) is on the last one, and in that computer I
> > have /etc/sane.d/net.conf:
>
> > [::1] localhost
>
>
> > /etc/sane.d/saned.conf:
>
> > 192.168.0.100/24 [::1] localhost
>
>
> > /etc/services does include the line:
>
> > sane-port 6566/tcp sane saned # SANE network scanner daemon
>
>
> > /etc/inetd.conf also has the line:
>
> > sane-port stream tcp nowait saned:saned /usr/sbin/saned saned
>
>
> > In this computer I get:
>
> > $ SANE_DEBUG_NET=255 scanimage -L [sanei_debug] Setting debug level of
> > net to 255.  [net] sane_init: authorize = 0x405920, version_code =
> > 0x7fff7ff4261c [net] sane_init: SANE net backend version 1.0.14
> > (AF-indep+IPv6) from sane-backends 1.0.21 [net] sane_init: Client has
> > little endian byte order [net] sane_init: searching for config file
> > [net] sane_init: trying to add [::1] [net] add_device: adding backend
> > [::1] [net] add_device: error while getting address of host [::1]:
> > Name or service not known [net] sane_init: trying to add localhost
> > [net] add_device: adding backend localhost [net] add_device: backend
> > localhost added [net] sane_init: done reading config [net] sane_init:
> > evaluating environment variable SANE_NET_HOSTS [net] sane_init:
> > evaluating environment variable SANE_NET_TIMEOUT [net] sane_init: done
> &g

[sane-devel] Canon MF8030c

[Nicolas Martin]

I think this one rocks.

But it still shows the same new protocol used here ;-(
Maybe there's not too much changes to add to the actual ImageClass
protocol, but I need first to have a deeper look at the messages, then
change the code for it if I can get to understand what the frames mean.
So I cannot propose this immediately, but I'll have a look on that.

Nicolas


Le lundi 26 juillet 2010 ? 12:40 +0200, Mickael Profeta a ?crit :
> Hi Nicolas,
> 
> > I'm very skeptical if we can come to some success using the current
> > ImageClass protocol, I'm afraid a rewrite of this new protocol is
> > necessary. With understanding of new messages, how they are formated
> > and of the data they content, this requires having access to a real
> > device for testing. 
> > 
> > But first, if you could produce this alternate usb snoop, this may
> > help, 
> 
> My friend send me a new log, hopefully more interesting. As it is much
> bigger, I put it on a website:
> 
> http://www2.alezan.org/download/USBLog1_2600710.zip
> 
> 
> Tell me if it is useable and if you find good news ;-)
> 
> Regards,
> 
> Mike

[sane-devel] Canon MF8030c

[Nicolas Martin]

Le samedi 24 juillet 2010 ? 00:00 +0200, Mickael Profeta a ?crit :
> Hmm, that's funny indeed. Maybe to clarify, I do not know if it is
> related or not. The scanner has two modes, "distant scan" and "connected
> to a computer". Not quite sure of the translation. I attach a new log
> in "computer" mode under windows, but I fear the log is incomplete,
> even if the scan was ok. 
> 
> I compile your modified version of pixma_imageclass.c and attach a new
> log (scan.log). The scanner has the same behaviour as before.
> 
> Hope you could find some clue.

Well, the attached usb snoop you last sent is unfortunately even worse
and totally unusable, only a few bytes exchanged are shown here.

I'm very skeptical if we can come to some success using the current
ImageClass protocol, I'm afraid a rewrite of this new protocol is
necessary. With understanding of new messages, how they are formated and
of the data they content, this requires having access to a real device
for testing. 

But first, if you could produce this alternate usb snoop, this may
help, 

Regards, 
Nicolas

[sane-devel] Canon MF8030c

[Nicolas Martin]

Le vendredi 23 juillet 2010 ? 16:45 +0200, Mickael Profeta a ?crit :
> Hi,
> 
> Thanks for these explanations.
> 
> I received thoses log that I compress using gzip. I am surprised it is
> binary files, is it ok?
> 
> Tell me if we should do some other tests with different parameters.
> 
> Thanks for help
> 
> Mike
> 
Well, the logs are partially usable, the first one fails probably before
the image data is sent from the scanner (Broken pipe), and the second
does just show only the very beginning of a scan sequence.

However, what is very curious, is that the first log shows the Pixma
dialect used here is different from all the ones implemented in the
pixma backend. 
But the first scanimage log you sent (which fails when image data is
about to be sent by scanner) uses the ImageClass Pixma dialect, so I
guess this model understands 2 different Pixma protocols ! Canon seems
to have reinvented the wheel again !

However, there's something we could try, as the MF8030 seems to
understand at least part of the ImageClass dialect:
The ImageClass file uses in fact 2 different ways to read image data, so
I've change a little bit the pixma_imageclass.c file to try an alternate
way. Could you try it, place the attached file in directory:
sane-backends/backend 
to replace the file already existing, recompile/reinstall, and take
another scanimage log as you sent in your first message.

Nicolas
-- next part --
A non-text attachment was scrubbed...
Name: pixma_imageclass.c
Type: text/x-csrc
Size: 19035 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100723/dacf4aca/attachment-0001.c>

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Note sure either what it means, but after some googling, it looks linked to
some versions of kernel

Did you try to modprobe -r the modules usblp and usb_storage ?

Nicolas

2010/7/22 Nicolas Martin 

> Not sure either wha
>
> 2010/7/22 Matthias Pannek 
>
> On Thu, 22 Jul 2010 07:45:52 +0200
>> Nicolas Martin  wrote:
>>
>> > > Yeah, i can try it with via USB. Any special parameter needed for
>> > > that?
>> >
>> > Nothing special, test it the same way as you did with network
>> > connexion.
>> > USB might require you to set some perms or udev rule tweak, so that
>> > you can scan as normal user (often usb perms are natively given only
>> > to root).
>>
>> I could scan.but there is a problem with usblp:
>>
>> $ scanimage -L
>> device `pixma:04A91743_3052EF' is a CANON Canon PIXMA MX870
>> multi-function peripheral
>>
>> $ scanimage -T
>> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
>> scanimage: acquiring RGB frame, 8 bits/sample
>> scanimage: reading one scanline, 1914 bytes...  FAIL Error: Error
>> during device I/O
>>
>> $ dmesg |tail -1
>> [ 5880.817977] usb 2-1.5: usbfs: interface 1 claimed by usblp while
>> 'scanimage' sets config #1
>>
>> I found many threads about this, but not sure what's wrong :(
>>
>> > In the meantime, I'll commit those first changes for MX870, this will
>> > be easier then to investigate the ADF empty issue
>>
>> Thanks :-)
>>
>> Matthias
>>
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100722/4ab9d9f5/attachment.htm>

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Not sure either wha

2010/7/22 Matthias Pannek 

> On Thu, 22 Jul 2010 07:45:52 +0200
> Nicolas Martin  wrote:
>
> > > Yeah, i can try it with via USB. Any special parameter needed for
> > > that?
> >
> > Nothing special, test it the same way as you did with network
> > connexion.
> > USB might require you to set some perms or udev rule tweak, so that
> > you can scan as normal user (often usb perms are natively given only
> > to root).
>
> I could scan.but there is a problem with usblp:
>
> $ scanimage -L
> device `pixma:04A91743_3052EF' is a CANON Canon PIXMA MX870
> multi-function peripheral
>
> $ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...  FAIL Error: Error
> during device I/O
>
> $ dmesg |tail -1
> [ 5880.817977] usb 2-1.5: usbfs: interface 1 claimed by usblp while
> 'scanimage' sets config #1
>
> I found many threads about this, but not sure what's wrong :(
>
> > In the meantime, I'll commit those first changes for MX870, this will
> > be easier then to investigate the ADF empty issue
>
> Thanks :-)
>
> Matthias
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100722/595ca4c2/attachment.htm>

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Le jeudi 22 juillet 2010 ? 00:05 +0200, Matthias Pannek a ?crit :
> On Wed, 21 Jul 2010 20:23:16 +0200
> Nicolas Martin  wrote:
> 
> > Yes, there was an error in the limiting to 600 dpi formula, hopefully,
> > should be fixed in the new file attached.
> 
> Works fine now.
Ok
> 
> > So I've canceled any Pixma protocol change here, do you have the
> > possibility to try the same with a usb cable ?
> 
> Yeah, i can try it with via USB. Any special parameter needed for that?

Nothing special, test it the same way as you did with network
connexion. 
USB might require you to set some perms or udev rule tweak, so that you
can scan as normal user (often usb perms are natively given only to
root).

In the meantime, I'll commit those first changes for MX870, this will be
easier then to investigate the ADF empty issue

Nicolas

[sane-devel] Canon MF8030c

[Nicolas Martin]

You can use Snoopypro.exe to get a usb snoop on Windows, this is a very
old program, but hopefully, still working on Vista.

Download from Snoopypro from sourceforge.net here:

http://sourceforge.net/projects/usbsnoop/

Read and follow exactly the instructions in SnoopyPro.exe, then try to
record a scan session.

 => Select the device corresponding to the scanner, using its USB
address 04A9:2707

There will be ~4 devices holding this address.
The scanner should be the one indicated by: "MF8030 ser"

You can recognize that it's the correct one, if you look at the frame
counter in SnoopyPro, it should increment only when MF8030 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 mercredi 21 juillet 2010 ? 21:13 +0200, Mickael Profeta a ?crit :
> Le Wed, 21 Jul 2010 20:25:39 +0200,
> Nicolas Martin  a ?crit :
> 
> > Do you have the possibility to get a Windows usb snoop log using
> > SnoopyPro.exe, to check if the protocol this model uses is a Pixma
> > one ?
> > 
> > I can give you instructions on how to do this if needed. 
> 
> 
> I do not have direct access to the scanner, but if you give reasonnable
> simple instructions, I think my friend can do this. And yes, there is a
> windows machine which can be connected with usb cable. 
> 
> Thanks for your answer, and if you can send me some instructions, I'll
> try to get that.
> 
> Mike
> 
> --
> 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

[sane-devel] Canon MF8030c

[Nicolas Martin]

Do you have the possibility to get a Windows usb snoop log using
SnoopyPro.exe, to check if the protocol this model uses is a Pixma one ?

I can give you instructions on how to do this if needed. 

Nicolas

Le mercredi 21 juillet 2010 ? 14:09 +0200, Mickael Profeta a ?crit :
> Le Wed, 21 Jul 2010 12:56:33 +0200,
> Mickael Profeta  a ?crit :
> 
> > Hi!
> > 
> > I am in touch with a friend who bought a Canon MF8030c
> > scanner/printer. I try to make the scanner work in usb. 
> 
> Hi, 
> 
> I forget to tell you what's happening when you start a scan. The scanner
> starts, the screen of the scanner writes "read" and then it hangs, no
> data on the computer.
> 
> Thanks for help.
> 
> Mike
> 
> --
> 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

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Le mercredi 21 juillet 2010 ? 00:03 +0200, Matthias Pannek a ?crit :

> 600 DPI scan works perfectly, but 1200 and 2400 crashes with "Floating
> point exception". 601 DPI seems to work too.
> 
> Logs are cash.log and strace.log

Yes, there was an error in the limiting to 600 dpi formula, hopefully,
should be fixed in the new file attached.

> 
> I tested a scan with an empty ADF but the scanner is still stuck after
> that.

And this makes me wonder if this is due to the Pixma protocol, or to the
network exchanges.

So I've canceled any Pixma protocol change here, do you have the
possibility to try the same with a usb cable ?

Nicolas

-- next part --
A non-text attachment was scrubbed...
Name: pixma_mp150.c
Type: text/x-csrc
Size: 49991 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100721/da776c96/attachment-0001.c>

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Ok, I try to imitate best the net traffic seen in Windows that you sent
in the file traffic.txt on 18/7. But I made a mistake with the xml
messages, so here is another try. The changes are to see if the scanner
recovers from adf empty (again, seen from the Pixma dialog exchanged in
the net logs) and also, limit the scan to 600dpi.

let us know about the results

Nicolas

Le mardi 20 juillet 2010 ? 20:28 +0200, Matthias Pannek a ?crit :
> On Tue, 20 Jul 2010 02:12:20 +0200
> Matthias Pannek  wrote:
> 
> > Flatbed scan is still working, but ADF not.
> > 
> > Here a log:
> > http://files.pannek.de/sane/adf.log
> 
> Tried it again with the last pixma_mp150.c and it's working again,
> so it should be a problem with the new version.
> 
> Thanks,
> Matthias
> 
> --
> 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: pixma_mp150.c
Type: text/x-csrc
Size: 50071 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100720/f06c4a61/attachment-0001.c>

[sane-devel] Canon MP700 support (partially OK)

[Nicolas Martin]

Le lundi 19 juillet 2010 ? 23:11 +0900, Gernot Hassenpflug a ?crit :
> Dear list,
> 
> I'm currently testing a Canon PIXUS all-in-one MP700 which is similar
> in structure to the MP710 I had until recently (power failed, thrown
> out).
> 
> I am using CVS, as shown by "scanimage -V":
> 
> scanimage (sane-backends) 1.0.22git; backend version 1.0.22
> 
> 
> Results:
> 
> 
> Here the apparent capabilities as exposed to Xsane & scanimage:
> 
> Modes: Color & Grayscale (no lineart, i.e. B/W)
> 
> Resolutions: 75, 150, 300, 600, 1200 dpi (appears to be correct for
> max resolution for this device)
> 
> I could successfully test color all resolutions. 300dpi I went up to
> A4 size, then 600 & 1200 half a page and 1/4 page to save time. All
> worked flawlessly.
> 
> For Grayscale, I could work perfectly with all resolutions *except* 1200 dpi.
> 
> Problem: for 1200dpi, the scanner starts to scan, perhaps 0.5 cm
> movement, and then it hangs, light dimly on, and power button no
> longer responds. With scanimage I can use Ctrl-C to cancel the scan
> and the scanner recovers properly:
> 
> ^Cscanimage: received signal 2
> scanimage: trying to stop scanner
> scanimage: sane_read: Operation was cancelled
> 
> Looking at the partial image scanned at 1200dpi shows that it is
> probably not in the right format, as there are diagonal stripes to be
> seen (the image as such is not recognizable).
> 
> I had a look at pixma_mp730.c and it is not clear to me if this is a
> known error or owing to untested resolution & mode perhaps? I can
> state from memory that I did not have this issue with the MP710 which
> seems to follow the same protocol.
> 
> On the other hand, the man page for the pixma protocol lists the
> Multipass MP700 and 730 rather than PIXMA MP700 & 730, so perhaps
> there is some slight difference between the models depending on where
> they are sold? PIXMA, PIXUS, Multipass...?
> 
> Logs:
> 
> 
> The log is too large to attach here, so I am sending a tgz version to Nicolas.
> 
> The log shows that suddenly the scan values become "ff" and in fact
> the USB logs with SANE_DEBUG_PIXMA=21 shows that the last line does
> not complete scanning, but immediately goes to some kind of error.
> This repeats (see below) until I press Ctrl-C and cancel the scan.
> Recovery is good and I can use the scanner without having to power it
> off and on again.
> 
> [pixma]  3d70:86 80 7b 6f 6a 6a 6d 72  7a 78 7a 78 74 77 7f 7e
> [pixma]  3d80:7e 75 6d 69 6e 77 78 7a  79 75 74 76 7d 7d 80 7b
> [pixma]  3d90:75 70 6d 71 78 78 7a 78  79 7c 82 83 84 77 75 6f
> [pixma]  3da0:6b 70 75 78 7a 76 74 6f  73 77 79 72 6d 54 3a 35
> [pixma]  3db0:30 30 ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
> [pixma]  3dc0:ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
> [pixma]  3dd0:ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
> [pixma]  3de0:ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
> [pixma]  3df0:ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
> [pixma]  3e00:ff ff ff ff ff ff
> [pixma]
> [pixma] OUT  T=7.369 len=10
> [pixma]  :d4 20 00 00 00 00 00 c0  04 00
> [pixma]
> [pixma] IN   T=7.372 len=6
> [pixma]  :06 06 00 00 00 00
> [pixma]
> [pixma] OUT  T=7.475 len=10
> [pixma]  :d4 20 00 00 00 00 00 c0  04 00
> [pixma]
> [pixma] IN   T=7.478 len=6
> [pixma]  :06 06 00 00 00 00
> [pixma]
> [pixma] OUT  T=7.581 len=10
> [pixma]  :d4 20 00 00 00 00 00 c0  04 00
> [pixma]
> [pixma] IN   T=7.584 len=6
> [pixma]  :06 06 00 00 00 00
> 
> Any comments and things to try most welcome,
> 
> Regards,
> Gernot Hassenpflug

Unless I'm wrong, 1200 dpi is not offered basically by Canon's drivers
on their Pixma models, so I guess the scanner may or may not work
correctly using these resolutions. MP700 is also a rather old model, and
it looks performances at greater resolutions have been improved somehow,
on more recent models. 

However, sudden change in scanned data ressembles to some hardware
discrepancy, did you try maybe with another computer, is this
reproducible ? 

Nicolas

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Le dimanche 18 juillet 2010 ? 23:25 +0200, Matthias Pannek a ?crit :
> On Sun, 18 Jul 2010 21:34:59 +0200
> Nicolas Martin  wrote:
> 
> > Slightly modified again file pixma_mp150.c (new attached) to add:
> > 
> > - maximum 600 dpi for generation 4 scanners in ADF/ADF duplex mode
> > - try to fix ADF empty scanner hanging. Not sure this will fix it, but
> > worth a try. Could you send back the scanimage.log you get now when
> > ADF is empty.
> 
> Done, but can't access the scanner.
> 
> [pixma] bjnp_open_tcp: Can not connect to scanner: Connection refused
> [pixma] pixma_connect() failed EINVAL
> [pixma] pixma_open() failed EINVAL
> [pixma] pixma_close(): Canon PIXMA MX870
> scanimage: open of device pixma:MX870_canon.saberhage failed: Invalid
> argument
> 
> Not sure what's wrong :(
> 
> Logfiles:
> http://files.pannek.de/sane/failed.zip
> 
But the fail occurs before it reaches any of yesterday's modifications!

Did you try to set back the last pixma_mp150.c file I sent on 16 July ?

Nicolas

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Slightly modified again file pixma_mp150.c (new attached) to add:

- maximum 600 dpi for generation 4 scanners in ADF/ADF duplex mode
- try to fix ADF empty scanner hanging. Not sure this will fix it, but
worth a try. Could you send back the scanimage.log you get now when ADF
is empty.

Nicolas

Le dimanche 18 juillet 2010 ? 16:30 +0200, Matthias Pannek a ?crit :
> On Sun, 18 Jul 2010 15:44:50 +0200
> Nicolas Martin  wrote:
> 
> > I've just added some lines to force max scan when using ADF to 600
> > dpi, even if higher resolution is selected in the frontend. 
> > To be tested.
> 
> Good :-)
> 
> > Strange, this Wireshark log show the Pixma protocol dialog is very
> > short, as in the pixma backend.
> > Unless something else is requested by the frontend, so could you get a
> > scanimage log in the same situation, with ADF empty, so that I can
> > compare both logs.
> 
> ADF-Log:
> http://files.pannek.de/sane/adf.zip
> 
> First ADF-Scan without paper: adf.log + wire.log
> After that, the scanner is stuck with "Processing..."
> 
> Second ADF-Scan without paper: adf2.log + wire2.log
> The scanner itself is ready again.
> 
> Third ADF-Scan: adf3.log +wire3.log
> Nothing happens, but scanner is still usable via Display.
> 
> 
> Thanks,
> Matthias

-- next part --
A non-text attachment was scrubbed...
Name: pixma_mp150.c
Type: text/x-csrc
Size: 50101 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100718/b551124a/attachment-0001.c>

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Le dimanche 18 juillet 2010 ? 00:04 +0200, Matthias Pannek a ?crit :
> On Sat, 17 Jul 2010 21:17:44 +0200
> Nicolas Martin  wrote:
> 
> > Problem is, I don't see yet a solution to exit from this pitfall, need
> > to think it over. 
> 
> Ok.
> 
> > 
> > > ADF: Working until 600 DPI, i tried it with 1200 DPI and i just got
> > > a "Error during read: Error during device I/O". Error and the
> > > scanner stuck with a "Processing..." message until Power off/on.
> > > (I know, max ADF resolution is 600 DPI)
> > 
> > Could you take a log of this 1200 dpi sequence, normally, even if an
> > error arises, the scan sequence should be fulfilled until the end, so
> > maybe there's something else wrong here.
> > 
> > In the meantime, I can add a simple a test for this model, to limit
> > ADF scan to 600 dpi.
> 
> Good idea. 
> 
> Here the log:
> http://files.pannek.de/sane/1200dpi.zip
> 
> If you need a (big) log from an successful 600 dpi scan:
> http://files.pannek.de/sane/600dpi.zip

The log show clearly that although the 1200 dpi parameter is accepted by
the scanner, the "ready" bit never comes up (like in the 600 dpi scan),
and the scan fails after the 60s timeout.

I've just added some lines to force max scan when using ADF to 600 dpi,
even if higher resolution is selected in the frontend. 
To be tested.
 
> 
> > is not executed. I will propose a fix for that to be tested.
> 
> Thanks.
> 
> > Point is, I did not have yet any windows usb snoops for those
> > particular cases, to confirm how the Canon driver behaves in those
> > error situations. 
> 
> Can i help somehow?
> 
> I have a Wireshark-log while running Windows in a VM using Canon
> Scangear.
> There is a info box while scanning without a document in the feeder and
> i clicked two times "OK" (without a document in it):
> http://files.pannek.de/sane/traffic.zip

Strange, this Wireshark log show the Pixma protocol dialog is very
short, as in the pixma backend.
Unless something else is requested by the frontend, so could you get a
scanimage log in the same situation, with ADF empty, so that I can
compare both logs.

Nicolas

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Le samedi 17 juillet 2010 ? 17:36 +0200, Matthias Pannek a ?crit :
> On Sat, 17 Jul 2010 14:44:00 +0200
> Nicolas Martin  wrote:
> 
> > Matthias, before I commit the changes and update the docs, did you try
> > the ADF and ADF duplex features, and do they work fine ? (remember to
> > set 2 pages to scan per sheet of paper in ADF when in duplex mode)
> 
> First test was "ADF Duplex" but I forgot to set the page-count to 2,
> then the printer stopped after 1 page but the paper was still in the
> feeder. (waiting for the "reverse feeder")
> 
> After that the scanner/printer worked fine via the Display, but I
> couldn't connect to the scanner.
> 
> ERROR:
> [pixma] pixma_collect_devices() found Canon PIXMA MX870 at
> bjnp://canon.saberhagen:8612 [pixma] pixma_open(): Canon PIXMA MX870
> [pixma] sanei_bjnp_open(bjnp://canon.saberhagen:8612, 16843009):
> [pixma] bjnp_allocate_device(bjnp://canon.saberhagen:8612)[pixma]
> udp_command: Sending UDP command to 10.0.0.101:8612 [pixma]
> bjnp_open_tcp: Can not connect to scanner: Connection refused [pixma]
> pixma_connect() failed EINVAL [pixma] pixma_open() failed EINVAL
> [pixma] pixma_close(): Canon PIXMA MX870
> scanimage: open of device pixma:MX870_canon.saberhage failed: Invalid
> argument
> 
> Scanimage logfiles:
> http://files.pannek.de/sane/scanimage2.zip
> 
> Nmap scan report for canon.saberhagen (10.0.0.101)
> Host is up (0.0051s latency).
> Not shown: 9992 closed ports
> PORT STATE SERVICE
> 137/udp  open  netbios-ns
> 138/udp  open|filtered netbios-dgm
> 500/udp  open|filtered isakmp
> 3702/udp open|filtered unknown
> 5353/udp open  zeroconf
> 8611/udp open  unknown
> 8612/udp open  unknown
> 8613/udp open  unknown
> MAC Address: 00:1E:8F:99:BD:B7 (Canon)
> 
> I turned the power off and onsame problem. Then i unplugged the
> scanner for ~10 seconds and it worked again.
> 
Actually, this looks logical the way duplex adf scanning is implemented
in Sane, as the scanner seems to be locked until it receives its start
sequence, then two scan sequences for recto and verso, and then an end
of scan sequence to finish. Here, it received a start, and only a single
scan sequence. And no end of scan sequence.
>From there, the scanner seems to refuse any new network connection, as
it did not finish completely the current one. So any attempts afterwards
to detect and reconnect to the scanner seem to fail.

Problem is, I don't see yet a solution to exit from this pitfall, need
to think it over. 

> Now for the test (xsane):
> Flatbed: working fine (preview/scan/cancel/) up to 2400 DPI.
> 
Ok.

> ADF: Working until 600 DPI, i tried it with 1200 DPI and i just got a
> "Error during read: Error during device I/O". Error and the scanner
> stuck with a "Processing..." message until Power off/on.
> (I know, max ADF resolution is 600 DPI)

Could you take a log of this 1200 dpi sequence, normally, even if an
error arises, the scan sequence should be fulfilled until the end, so
maybe there's something else wrong here.

In the meantime, I can add a simple a test for this model, to limit ADF
scan to 600 dpi.

> 
> ADF without a paper in the feeder: Error message "Error during read:
> Document feeder out of documents". But the scanner itself is stuck with
> the "Processing..." screen. After 5 minutes still at processing, seems
> there is no timeout for this. The abort key don't work, so only Power
> off/on helps again.

I think this is because when there's no paper in ADF, the end of scan
sequence (especially for generation 4 which uses an XML encapsulation)
is not executed. I will propose a fix for that to be tested.
Point is, I did not have yet any windows usb snoops for those particular
cases, to confirm how the Canon driver behaves in those error
situations. 

> 
> ADF Duplex 600 DPI (page count 2):  working fine without a problem.
> 
Ok, nominal cases work, but some tweaks are apparently needed when error
conditions are met. So let's see how we can improve that.

Nicolas

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Sounds good then ;-)

Matthias, before I commit the changes and update the docs, did you try
the ADF and ADF duplex features, and do they work fine ? (remember to
set 2 pages to scan per sheet of paper in ADF when in duplex mode)

Louis, nice to read from you, hope you spent good holidays, and congrats
to the Netherlands who played the soccer final in South Africa!

Nicolas


Le samedi 17 juillet 2010 ? 13:51 +0200, Matthias Pannek a ?crit :
> On Sat, 17 Jul 2010 12:12:36 +0200
> Louis Lagendijk  wrote:
> 
> > This looks like a case where the scanner messed up internally. What
> > happens when you take it of the power for 30 seconds or so and
> > reconnect?
> 
> I tried anything on the hardware (restart, ..), but it was my faul :/
> 
> > > So could you try to get the same log file with scanimage -T , there
> > > may be something in there showing where the bjnp dialog blocks.
> > > Could you double check also if it's not a firewall issue for the 4
> > > bjnp ports ? 
> > > 
> > Looking at the traces, BJNP works as expected, so I do not believe
> > that the firewall may be blocking. A detailed trace withv ONLY pixma
> > logging would be nice though. Sanei and usb logging make only for
> > more noise and are irrelevant as you are using BJNP anyhow, so only:
> > export SANE_DEBUG_PIXMA=11
> > before the actual scanning
> 
> Sorry, i think there was an old dependency on the sane-backends package
> of my distribution because it was installed again :-( Used the patched
> git version again and every works fine now :-)
> 
> Thanks again,
> Matthias
> 
> --
> 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

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Le vendredi 16 juillet 2010 ? 23:46 +0200, Matthias Pannek a ?crit :
> On Fri, 16 Jul 2010 21:51:08 +0200
> Nicolas Martin  wrote:
> 
> > Ok, so ready for a test ?
> 
> Sure :-)
> 
> > Then, replace the file sane-backends/backend/pixma_mp150.c with the
> > one I've attached. I've just added a declaration for the MX870 in
> > there.
> 
> Done.
> 
> > Then give a try. Be careful if you have a webcam attached, it may mess
> > up the detection and better disable in this case the v4l backend
> > in /etc/sane.d/dll.conf
> 
> Ok.
> 
> > Zip send back the result of scanimage.log to check how it's going.
> 
> Here is the Zip:
> http://files.pannek.de/sane/scanimage.zip

This look satisfactory at first glance, the Pixma dialog is confirmed to
be a generation 4 format here.

> 
> pannek at veerle ~ $ scanimage -L
> device `pixma:MX870_canon.saberhage' is a CANON Canon PIXMA MX870
> multi-function peripheral
> 
> pannek at veerle ~ $ scanimage -T
> scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
> scanimage: acquiring RGB frame, 8 bits/sample
> scanimage: reading one scanline, 1914 bytes...  PASS
> scanimage: reading one byte...  PASS
> scanimage: stepped read, 2 bytes... PASS
> scanimage: stepped read, 4 bytes... PASS
> scanimage: stepped read, 8 bytes... PASS
> scanimage: stepped read, 16 bytes...PASS
> scanimage: stepped read, 32 bytes...PASS
> scanimage: stepped read, 64 bytes...PASS
> scanimage: stepped read, 128 bytes...   PASS
> scanimage: stepped read, 256 bytes...   PASS
> scanimage: stepped read, 512 bytes...   PASS
> scanimage: stepped read, 1024 bytes...  PASS
> scanimage: stepped read, 2048 bytes...  PASS
> scanimage: stepped read, 2047 bytes...  PASS
> scanimage: stepped read, 1023 bytes...  PASS
> scanimage: stepped read, 511 bytes...   PASS
> scanimage: stepped read, 255 bytes...   PASS
> scanimage: stepped read, 127 bytes...   PASS
> scanimage: stepped read, 63 bytes...PASS
> scanimage: stepped read, 31 bytes...PASS
> scanimage: stepped read, 15 bytes...PASS
> scanimage: stepped read, 7 bytes... PASS
> scanimage: stepped read, 3 bytes... PASS
> 
> Played a little bit with skanlite and it worked nice, but after a
> successful 1200 DPI scan  I restarted the client and now I only see a
> "No device found" message : (
> 
> pannek at veerle ~ $ scanimage -L
> 
> No scanners were identified. If you were expecting something different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> 
So could you try to get the same log file with scanimage -T , there may
be something in there showing where the bjnp dialog blocks. Could you
double check also if it's not a firewall issue for the 4 bjnp ports ? 

Nicolas

[sane-devel] Canon PIXMA MX870

[Nicolas Martin]

Ok, so ready for a test ?

Let's assume MX870 is a somehow a MX860, and uses the generation 4 Pixma
protocol.

First, download the latest Sane git version. You should get a
sane-backends folder.

Then, replace the file sane-backends/backend/pixma_mp150.c with the one
I've attached. I've just added a declaration for the MX870 in there.

./configure with the correct options, make, install.
Help here for that:
http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html


Then give a try. Be careful if you have a webcam attached, it may mess
up the detection and better disable in this case the v4l backend
in /etc/sane.d/dll.conf

Use the following commands to get logs:

$ export SANE_DEBUG_SANEI_USB=255
$ export SANE_DEBUG=255
$ export SANE_DEBUG_PIXMA=11

$ scanimage -L  2> scanimage1.log 


$ scanimage -T  2> scanimage2.log 

Zip send back the result of scanimage.log to check how it's going.

Nicolas


Le vendredi 16 juillet 2010 ? 09:24 +0200, Matthias Pannek a ?crit :
> Hello,
> 
> i'm a owner of a PIXMA MX870 and it would be really nice to have Sane
> support for this scanner :-(
> 
> The MX870 should be a slightly modified MX860 (who is supported right
> now).
> 
> I'm not sure about the bjnp-Protocol, because there is no TCP port 8612
> open on this device. But the devices uses UDP 8612 for communication.
> 
> Host is up (0.00045s latency).
> Not shown: 131060 closed ports
> PORT STATE SERVICE
> 80/tcp   open  http
> 139/tcp  open  netbios-ssn
> 137/udp  open  netbios-ns
> 138/udp  open|filtered netbios-dgm
> 500/udp  open|filtered isakmp
> 3702/udp open|filtered unknown
> 5353/udp open  zeroconf
> 8611/udp open  unknown
> 8612/udp open  unknown
> 8613/udp open  unknown
> MAC Address: 00:1E:8F:99:BD:xx (Canon)
> 
> Here a tcpdump of a Preview-scan using Windows in a VM:
> http://files.pannek.de/log.txt
> 
> Here a tcpdump after the start of xsane:
> http://files.pannek.de/xsane.txt
> 
> There is communication between sane and my scanner.
> 
> This is the "Printer Identiy":
> %"E at zr
> e
> !BmBJNP0UUMFG:Canon;CMD:MultiPass 2.1,IVEC;MDL:MX870
> series;CLS:IMAGE;DES:Canon MX870 series;
> 
> Thank you,
> Matthias
> 
> 
> --
> 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: pixma_mp150.c
Type: text/x-csrc
Size: 49567 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100716/58632411/attachment-0001.c>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

I took a look at the process list you sent, but difficult for me to tell
which one is involved with the usb port used by the Pixma device, as I
don't know anything about 50% of them, and the names do not help too
much to know what they are used for. 

Unfortunately, no other idea for the moment, on how to locate this
process, which seems to lock the usb port.

Nicolas

Le mercredi 14 juillet 2010 ? 09:13 +, twain43 at hotmail.com a ?crit :
> Morning,
> here are some results, along with the steps I took to obtain them:
> 1. Uninstalled the canon printer from System Preferences, trashed the
> drivers and killed the "UFR II Backgrounder" service;
> 2. Make uninstalled all frontends and backends (I'm keeping the
> source, just in case);
> 3. Rebooted;
> 4. Pulled down yesterday's git snapshot, added the "ugly pixma patch",
> modded the NDEBUG statements for pixma files;
> 5. Compiled and installed both frontends and backends;
> 6. Ran Activity Monitor and kept it on the background;
> 7. Ran scanimage in Terminal as superuser, while using Activity
> Monitor to save the list of running processes and daemons at the
> moment of the test.
> 
> Not posting the usual pixma and all-export logs, since they read as
> usual.
> Instead, I'm attaching Activity Monitor's log: maybe you'll spot
> something more than I didAFAICS, there's nothing wrong: the only
> two suspicious processes are TWAINBridge and Image Capture Extension.
> The first one appears as soon as I connect the printer to the USB, and
> can't be killed, so I'm guessing it must be OS-related. I killed the
> second one and rerun the scantest, but got no different log results.
> 
> Hope you can spot something more out of it.
> 
> Twain28
> 
> 
> __
> From: twain43 at hotmail.com
> To: nicolas0martin at gmail.com
> Date: Tue, 13 Jul 2010 14:32:44 +
> CC: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> 
> I'm not a Mac expert myself, but I'll poke around things and see what
> I can do
> 
> Twain28
> 
> 
> __
> Date: Tue, 13 Jul 2010 10:35:51 +0200
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
> 
> The "process" here under is probably not an application, but runs in
> background, it may be a printing daemon or service started after boot,
> which locks access to the usb port. 
> I really know nothing about Mac OS X, to help you find it, maybe stop
> a printing service would help.
>  
> Nicolas
> 
> 
> 2010/7/13 
> I'm running the command from terminal at system boot, so there
> really should not be anything else openis there some way
> to check this, anyway, so that I might be sure of it?
> Thank you for your patience
> 
> Twain28
> 
> 
> __
> Date: Mon, 12 Jul 2010 18:45:03 +0200 
> 
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> 
> CC: sane-devel at lists.alioth.debian.org 
> 
> 
> 
> Well, not exactly something new, the 2 logs are somehow
> equivalent, but one gives a little bit more details:
> [pixma] en1 is not a valid IPv4 interface, skipping...
> [pixma] en1 is IPv4 capable, sending broadcast..
> [pixma] scanner discovery finished...
> [pixma] pixma_open(): Canon imageClass MF6500
> [sanei_usb] sanei_usb_open: trying to open device
> `libusb:005:002-04a9-2686-00-00'
> usb_os_open: 04a9:2686
> usb_os_open(USBDeviceOpenSeize): another process has device
> opened for exclusive access
> usb_set_configuration: called for config 1
> USB error: usb_set_configuration(SetConfiguration): device not
> opened for exclusive access
> [sanei_usb] sanei_usb_open: libusb complained:
> usb_set_configuration(SetConfiguration): device not opened for
> exclusive access
> usb_os_close: 04a9:2686
> [pixma] pixma_connect() failed EINVAL
> [pixma] pixma_open() failed EINVAL
> [pixma] pixma_close(): Canon imageClass MF6500
> scanimage: open of device pixma:04A92686 failed: Invalid
> argument
>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

The "process" here under is probably not an application, but runs in
background, it may be a printing daemon or service started after boot, which
locks access to the usb port.
I really know nothing about Mac OS X, to help you find it, maybe stop a
printing service would help.

Nicolas

2010/7/13 

> I'm running the command from terminal at system boot, so there really
> should not be anything else openis there some way to check this, anyway,
> so that I might be sure of it?
> Thank you for your patience
>
> Twain28
>
> --
> Date: Mon, 12 Jul 2010 18:45:03 +0200
>
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
>
>
> Well, not exactly something new, the 2 logs are somehow equivalent, but one
> gives a little bit more details:
> [pixma] en1 is not a valid IPv4 interface, skipping...
> [pixma] en1 is IPv4 capable, sending broadcast..
> [pixma] scanner discovery finished...
> [pixma] pixma_open(): Canon imageClass MF6500
> [sanei_usb] sanei_usb_open: trying to open device
> `libusb:005:002-04a9-2686-00-00'
> usb_os_open: 04a9:2686
> usb_os_open(USBDeviceOpenSeize): *another process has device opened for
> exclusive access*
> usb_set_configuration: called for config 1
> USB error: usb_set_configuration(SetConfiguration): device not opened for
> exclusive access
> [sanei_usb] sanei_usb_open: libusb complained:
> usb_set_configuration(SetConfiguration): device not opened for exclusive
> access
> usb_os_close: 04a9:2686
> [pixma] pixma_connect() failed EINVAL
> [pixma] pixma_open() failed EINVAL
> [pixma] pixma_close(): Canon imageClass MF6500
> scanimage: open of device pixma:04A92686 failed: Invalid argument
> And I think we're back to a few messages ago in this thread, so first,
> could you locate this other process (maybe printer ?) which locks the usb
> device, and stop it ?
>
> Nicolas
>
> 2010/7/12 
>
> Ditto: here are the new logs.
> Something new sprouted out, at their very endhope it's useful.
>
>
> Twain28
>
> --
> Non sei a casa? Accedi a Messenger dal 
> Web.<http://www.messenger.it/web/default.aspx>
>
> --
> 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
>
>
>
> --
> Non sei a casa? Accedi a Messenger dal 
> Web.<http://www.messenger.it/web/default.aspx>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100713/e8b28038/attachment.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Well, not exactly something new, the 2 logs are somehow equivalent, but one
gives a little bit more details:

[pixma] en1 is not a valid IPv4 interface, skipping...
[pixma] en1 is IPv4 capable, sending broadcast..
[pixma] scanner discovery finished...
[pixma] pixma_open(): Canon imageClass MF6500
[sanei_usb] sanei_usb_open: trying to open device
`libusb:005:002-04a9-2686-00-00'
usb_os_open: 04a9:2686
usb_os_open(USBDeviceOpenSeize): *another process has device opened for
exclusive access*
usb_set_configuration: called for config 1
USB error: usb_set_configuration(SetConfiguration): device not opened for
exclusive access
[sanei_usb] sanei_usb_open: libusb complained:
usb_set_configuration(SetConfiguration): device not opened for exclusive
access
usb_os_close: 04a9:2686
[pixma] pixma_connect() failed EINVAL
[pixma] pixma_open() failed EINVAL
[pixma] pixma_close(): Canon imageClass MF6500
scanimage: open of device pixma:04A92686 failed: Invalid argument
And I think we're back to a few messages ago in this thread, so first, could
you locate this other process (maybe printer ?) which locks the usb device,
and stop it ?

Nicolas

2010/7/12 

> Ditto: here are the new logs.
> Something new sprouted out, at their very endhope it's useful.
>
>
> Twain28
>
> --
> Non sei a casa? Accedi a Messenger dal 
> Web.<http://www.messenger.it/web/default.aspx>
>
> --
> 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 --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100712/b37b6dc8/attachment-0001.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Be careful so to change all the NDEBUG statements contained in the files.
Yes, the idea here was to rename NDEBUG to NDEBUGPIXMA
If the log you sent include all of these changes, probably means this was
not the root cause to the backend dumbness on Mac OS X ...
FYI, someone reported recently the MF6550 to work fine with the pixma
backend, tested on Ubuntu, so we really need to crack this weird Mac OS X
behavior here, if we want step further.

Nicolas

2010/7/12 

> Ehm...sorry everybody, been out of town a few weeks, couldn't get my hands
> on the mailI'm back to the testing board.
>
> I just read your posts, and wanted to sum up the steps to take. Do please,
> correct me if I'm wrong:
> 1. Change backends/pixma_common.h around line 57 from "#ifdef NDEBUG" to
> "#ifdef NDEBUGBL".
> 2. Same thing for backends/pixma.c line 70.
> 3. compile, install and test.
>
> @Nicolas: if I understood your post below, you're suggesting I use "#ifdef
> NDEBUGPIXMA", instead of the aboveam I right?
>
>
> Twain28
>
> > Subject: Re: [sane-devel] Testing on Canon MF6580PL
> > From: nicolas0martin at gmail.com
> > To: chris at cnpbagwell.com
> > CC: twain43 at hotmail.com; sane-devel at lists.alioth.debian.org
> > Date: Mon, 28 Jun 2010 21:24:10 +0200
>
> >
> > That's good clue indeed.
> >
> > Also might be better to change the NDEBUG flag in the pixma code to
> > something more restrictive, like NDEBUGPIXMA
> >
> > Or ... simply to reconsider this conditional code here and there, as it
> > was helpful at the time the pixma driver was standalone and not included
> > into Sane as backend, but is now pretty useless, as pixma logs are
> > handled directly with Sane flags.
> >
> > Nicolas
> >
> > Le lundi 28 juin 2010 ? 12:17 -0500, Chris Bagwell a ?crit :
> > > Oh, OK. So one part of the problem is that pixma debug messages
> > > aren't showing up.
> > >
> > > Can the tester verify as a separate task if scanning is working with
> > > twain-sane version of libusb though? It seems it may be working now?
> > >
> > > On debug output part, I see pixma is using some custom stuff to
> > > disable when NDEBUG is present. Seems pretty easy that externally
> > > included header defines NDEBUG that pixma is including but not
> > > sanei_debug.h.
> > >
> > > A quick test of that theory is to modify the file
> > > backends/pixma_common.h around line 57 and change "#ifdef NDEBUG" to
> > > "#ifdef NDEBUGBL". Also, similar change needed at
> > > backends/pixma.c line 70.
> > >
> > > Can
> > >
> > > On Mon, Jun 28, 2010 at 11:46 AM, Nicolas Martin
> > >  wrote:
> > > Point is, for whatever reason, Pixma debug logs do not show up
> > > even when setting SANE_DEBUG_PIXMA to a correct level, only
> > > SANE_DEBUG and SANE_DEBUG_SANEI_USB produce logs, as showed up
> > > in the logs twain43 is providing.
> > >
> > > Just trying to figure out why this happens when compiled in
> > > this environment.
> > >
> > > Nicolas
> > >
> > >
> > > 2010/6/28 Chris Bagwell chris at cnpbagwell.com
> > >
> > > I've been fading in and out of this thread so
> > > I do not have total history of your logs.
> > >
> > > Loooking at only this log, it seems to show
> > > scanner working correctly while in test mode.
> > > Can you do same debug logs but while doing an
> > > actual scan? Does that work now with the
> > > patched libusb from twain-sane (does it
> > > generate a good pnm file)?
> > >
> > > Chris
> > >
> > >
> > >
> > >
> >
> >
>
> --
> Personalizza il tuo Messenger con nuove e divertenti 
> emoticon<http://www.pimpit.it/windowslive.html>
>
> --
> 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 --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100712/d0faefa3/attachment.htm>

[sane-devel] Canon PIXMA MX350

[Nicolas Martin]

Le dimanche 04 juillet 2010 ? 23:14 +0200, Guenther Hutzl a ?crit :
> On 07/04/2010 08:32 PM, Nicolas Martin wrote:
> > As far as I understand, you are using your scanner with Ethernet or Wifi
> > connection. And it tries to communicate with an IP address, but in
> > message, we can read both:
> >
> > Failed to open device 'pixma:MX350_192.167.1.88': Invalid argument.
> >
> >   
> Sorry, I think this was actually a typo in my post. I had to manually
> type the error message because it was in a popup requestor and no text
> that I could cut and paste. It should rather read 192.168.1.88.
> 
> Anyhow the sanner seems to work reliably as long as I don't use the adf.
> When using the adf sometimes the printer is not accessible any more and
> I have to disconnect it from the power and reconnect. I think you can
> commit the code to the repository as you suggested already. I will try
> to create some usb trace soon. Probably you see something from a trace
> of a scan via the adf that would help resolve the final problems.
> 
> Thank you.
> 
> G?nther.

Current state of code for MX350 is now committed.

What would help to understand the issue with adf would be to have logs
of the pixma backend in both situations, no issue, and when the issue
happens.

To get a scan log, use the following commands when you are to run your
frontend program:

$ export SANE_DEBUG_PIXMA=11
$   2>  scanimage.log

Where  is the actual frontend scanning program you are using.

You should get a scanimage.log file (text file) that contains the
backend logs.

BTW, could you give some precisions when you experience this issue:

- how many pages in adf ?
- do all pages in adf get scanned correctly, and then, printer gets
disabled ?
- Only the printer gets unaccessible, or also the scanner ?
- Is there any message or status shown on the MX350 display ? 

Nicolas

[sane-devel] Canon PIXMA MX350

[Nicolas Martin]

As far as I understand, you are using your scanner with Ethernet or Wifi
connection. And it tries to communicate with an IP address, but in
message, we can read both:

Failed to open device 'pixma:MX350_192.167.1.88': Invalid argument.

and 

scanimage: open of device pixma:MX350_192.168.1.88 failed: Invalid
argument

192.167.x.x is surely a wrong address due to a typo, so I don't know how
your scanner is configured, does it use dhcp to get its address, or is
it static ? Maybe this is to double check, both in the scanner and
in /etc/sane.d/pixma.conf

If you still encounter this problem, you could also try to check if the
situation is the same with usb.

In the meantime, I'll commit the successful changes for the Pixma MX350,
thanks to your feedback.

Nicolas

Le dimanche 04 juillet 2010 ? 19:13 +0200, Guenther Hutzl a ?crit :
> Unbelievable! Power cycling was the answer. I have unplugged the printer
> from the power (pulled the power plug) and waited for about 30sec. Then
> I reconnected the printer and switched it on again. Now I can scan like
> a charm.
> 
> But probably we should try to diagnose this problem a little further. I
> will see if I can reproduce it. Does this happen to other canon printers
> as well?
> 
> Thanks,
> 
> G?nther.
> 
> On 07/04/2010 06:54 PM, Guenther Hutzl wrote:
> > Yes, I have, if you mean pressing the power button on the printer which
> > switches is on/off. I should have said that in my previous post. I have
> > not yet tried to disconnect it from the power and wait a few seconds or
> > so. I will try that but I doubt it will help.
> >
> > Thanks for the answer.
> >
> >   
> 
> --
> 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

[sane-devel] Canon PIXMA MX350

[Nicolas Martin]

Le dimanche 04 juillet 2010 ? 01:33 +, John a ?crit :
> Guenther Hutzl  googlemail.com> writes:
> 
> > 
> > On 07/02/2010 10:19 PM, John wrote:
> > > If you haven't got it working yet, you might try the canon drivers for 
> > > the 
> MX350 
> > > from:
> > > http://software.canon-europe.com/products/0010836.asp
> > >
> > > Using the rpms from that source I have text printing partly working over 
> > > wireless which is more than I could do before.  Haven't tried the scanner 
> yet 
> > > but scanner drivers are included in the bundle.
> > >
> > > --john
> 
> > >   
> > Hello!
> > 
> > Thanks for the hint. I will try that driver when I have time. I did not
> > yet work on the usb snoop trace. But I will soon. I will soon have
> > access to a windows XP pc so I can do the trace then. It would help me
> > if anyone could point me to some documentation about how to produce
> > useful traces. I did not find any post here, but I may have searched
> > wrong. I will post the trace results here when I have them ready in the
> > next weeks or so.
> > 
> > Guenther.
> > 
> >
> As a last resort I read the guide that comes in the driver bundle from Canon. 
>  
> Had to then uninstall everything and make changes to SELinux and the Firewall 
> before reinstalling.  Unbelievable.  It searched and found my wireless MX350 
> and 
> set it up in Cups.  It prints photos and text and mixed content as it should. 
>  
> It also scans but as per the guide the only app that sees the scanner is GIMP.
> 
> Sure don't understand why Canon doesn't have the linux stuff on their US web-
> site.  At least I couldn't find it.  Of course my wife says I can't see 
> things 
> any more unless they are moving.  After 49 years I guess she knows me pretty 
> good.
> 
> This may not be of any help resolving your problem but thought I would let 
> you 
> know how my situation turned out.
> 
> --john  
> 
Interesting pointer.

Canon has issued a new version of their printing driver (3.30), that
includes now a network backend (cnijnet) additionally to the classic usb
(cnijusb) 
Also, the scangear package seems to include code for network scanners
too. 
Try to run scangear (or scangearmp), this is the main frontend provided
by Canon for scanning.

This Linux software from Canon is developed by the Canon-asia teams, and
each worldwide Canon region is autonomous to propose its own product
lines and support. That's why you might find this Canon Linux software
on the Asian or European site, but not the US one.

Nicolas

[sane-devel] Ubuntu 10.4 32 & 64 bit Platform - Canon MF6550 Scanner - sane via any frontend "Hangs" at 1st data transfer

[Nicolas Martin]

Yep, this one is perfect ;-)

Thanks

Nicolas

Le samedi 03 juillet 2010 ? 15:13 -0500, Ron Parker a ?crit :
> results after "git pull" and rebuild. Look better!
> 
> Ron
> 
> - Original Message -
> From: "Nicolas Martin" 
> To: "Ron Parker" 
> Cc: sane-devel at lists.alioth.debian.org
> Sent: Saturday, July 3, 2010 3:30:12 PM GMT -05:00 US/Canada Eastern
> Subject: Re: [sane-devel] Ubuntu 10.4 32 & 64 bit Platform - Canon MF6550 
> Scanner - sane via any frontend "Hangs" at 1st data transfer
> 
> Thanks Ron for this log, it shows the MF6550 is working as expected.
> 
> By the way, this revealed a little weakness in the backend (see the
> messages in the log: "Inefficient skip buffer. Should be 75" that I
> should have fixed now, with the latest commit I've just pushed. 
> 
> So could you update your git files, give another try exactly as you did
> this one, and catch another scanimage.log, this one should not contain
> this warning message anymore.
> 
> Nicolas
> 
> Le samedi 03 juillet 2010 ? 10:40 -0500, Ron Parker a ?crit :
> > scanimage.log 
> > 
> > - Original Message -
> > From: "Nicolas Martin" 
> > To: "Ron Parker" 
> > Sent: Friday, July 2, 2010 3:32:16 PM GMT -05:00 US/Canada Eastern
> > Subject: Re: Fwd: [sane-devel] Ubuntu 10.4 32 & 64 bit Platform - Canon 
> > MF6550 Scanner - sane via any frontend "Hangs" at 1st data transfer
> > 
> > Ron, 
> > 
> > Thanks for your message, unfortunately, the log you sent me is the
> > actual scanned image, not the scan log. 
> > 
> > Maybe you omitted in the scanimage statement the 2 before the >
> > You must run scanimage, after the export statement, like this: 
> > 
> > scanimage 2> scanimage.log
> > 
> > scanimage.log should be a text file.
> > 
> > Could you try again to get it ?
> > 
> > Nicolas
> > 
> > Le vendredi 02 juillet 2010 ? 09:53 -0500, Ron Parker a ?crit :
> > > (Log file too big for the list) Compression still leaves a file of over 
> > > 1MB
> > > 
> > > Success so far.
> > > 
> > > The commands below are what I abstracted from the web page you referred
> > > me to. After building and loading the latest back-end library, a command
> > > line scan produced the log file that you requested. (Attached).
> > > 
> > > Additional scans with gscan2pdf, simplescan, and xsane all produced
> > > acceptable one page results. I cranked up the resolution to 300 dpi for
> > > one page, and there was no mis-behavior. My final test in this set was a
> > > multipage (via gscan2pdf) 150 dpi from the sheet feeder.The resultant
> > > PDF looked good.
> > > 
> > > re: maintaining this configuration. Will ubuntu offer me an update to
> > > the backend library via the package mechanism? Or, have I detached this
> > > library from ubuntu package management by building a custom and later
> > > release of the library?
> > > 
> > > Any other tests that you would like me to run? (How do I kill the env
> > > variable created by EXPORT?)
> > > 
> > > Ron
> > > 
> > > 
> > > #http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html
> > > cd /usr/src
> > > git clone git://git.debian.org/sane/sane-backends.git
> > > cd sane-backends
> > > 
> > > #If you want later to update your git directory with the latest version
> > > #available from the public Sane git repository, in order to build the
> > > latest #Sane code, you just need to enter the following command, from
> > > the sane-#backends directory:
> > > # #$ git pull
> > > # make sure usb dev lib is installed
> > > 
> > > apt-get install libusb-dev
> > > 
> > > #This will download the latest changes to the files in your directory
> > > sane-backends.
> > > 
> > > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
> > > 
> > > #This will choose /usr/lib/sane as SANE lib directory, /etc/sane.d as
> > > SANE #config files dir, and /var/lock/sane as state directory: The ones
> > > that are #used by Mandriva and Ubuntu.
> > > 
> > > make
> > > make install
> > > 
> > > echo '# libusb device nodes : change permissions to 666'
> > > >/etc/udev/rules.d/mylibsane.rules echo 'SUBSYSTEM=="usb",
> > > ENV{DEVTYPE}=="usb_device", MODE="0666"'
> > > >>/etc/udev/rules.d/mylibsane.rules
> > > 
> > > scanimage -V
> > > # Shows version . Should be GTEQ 1.0.21
> > > # Actual value in this test was 1.0.22 (1Jul2010)
> > > 
> > > scanimage -L
> > > # Shows Scanner
> > > # pixma_find_scanners() found 1 devices
> > > # device `pixma:04A92686_1665JDVj' is a CANON Canon imageClass
> > > MF6500 multi-function peripheral
> > 
> > 
> 
> 

[sane-devel] Ubuntu 10.4 32 & 64 bit Platform - Canon MF6550 Scanner - sane via any frontend "Hangs" at 1st data transfer

[Nicolas Martin]

Thanks Ron for this log, it shows the MF6550 is working as expected.

By the way, this revealed a little weakness in the backend (see the
messages in the log: "Inefficient skip buffer. Should be 75" that I
should have fixed now, with the latest commit I've just pushed. 

So could you update your git files, give another try exactly as you did
this one, and catch another scanimage.log, this one should not contain
this warning message anymore.

Nicolas

Le samedi 03 juillet 2010 ? 10:40 -0500, Ron Parker a ?crit :
> scanimage.log 
> 
> - Original Message -
> From: "Nicolas Martin" 
> To: "Ron Parker" 
> Sent: Friday, July 2, 2010 3:32:16 PM GMT -05:00 US/Canada Eastern
> Subject: Re: Fwd: [sane-devel] Ubuntu 10.4 32 & 64 bit Platform - Canon 
> MF6550 Scanner - sane via any frontend "Hangs" at 1st data transfer
> 
> Ron, 
> 
> Thanks for your message, unfortunately, the log you sent me is the
> actual scanned image, not the scan log. 
> 
> Maybe you omitted in the scanimage statement the 2 before the >
> You must run scanimage, after the export statement, like this: 
> 
> scanimage 2> scanimage.log
> 
> scanimage.log should be a text file.
> 
> Could you try again to get it ?
> 
> Nicolas
> 
> Le vendredi 02 juillet 2010 ? 09:53 -0500, Ron Parker a ?crit :
> > (Log file too big for the list) Compression still leaves a file of over 1MB
> > 
> > Success so far.
> > 
> > The commands below are what I abstracted from the web page you referred
> > me to. After building and loading the latest back-end library, a command
> > line scan produced the log file that you requested. (Attached).
> > 
> > Additional scans with gscan2pdf, simplescan, and xsane all produced
> > acceptable one page results. I cranked up the resolution to 300 dpi for
> > one page, and there was no mis-behavior. My final test in this set was a
> > multipage (via gscan2pdf) 150 dpi from the sheet feeder.The resultant
> > PDF looked good.
> > 
> > re: maintaining this configuration. Will ubuntu offer me an update to
> > the backend library via the package mechanism? Or, have I detached this
> > library from ubuntu package management by building a custom and later
> > release of the library?
> > 
> > Any other tests that you would like me to run? (How do I kill the env
> > variable created by EXPORT?)
> > 
> > Ron
> > 
> > 
> > #http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html
> > cd /usr/src
> > git clone git://git.debian.org/sane/sane-backends.git
> > cd sane-backends
> > 
> > #If you want later to update your git directory with the latest version
> > #available from the public Sane git repository, in order to build the
> > latest #Sane code, you just need to enter the following command, from
> > the sane-#backends directory:
> > # #$ git pull
> > # make sure usb dev lib is installed
> > 
> > apt-get install libusb-dev
> > 
> > #This will download the latest changes to the files in your directory
> > sane-backends.
> > 
> > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
> > 
> > #This will choose /usr/lib/sane as SANE lib directory, /etc/sane.d as
> > SANE #config files dir, and /var/lock/sane as state directory: The ones
> > that are #used by Mandriva and Ubuntu.
> > 
> > make
> > make install
> > 
> > echo '# libusb device nodes : change permissions to 666'
> > >/etc/udev/rules.d/mylibsane.rules echo 'SUBSYSTEM=="usb",
> > ENV{DEVTYPE}=="usb_device", MODE="0666"'
> > >>/etc/udev/rules.d/mylibsane.rules
> > 
> > scanimage -V
> > # Shows version . Should be GTEQ 1.0.21
> > # Actual value in this test was 1.0.22 (1Jul2010)
> > 
> > scanimage -L
> > # Shows Scanner
> > # pixma_find_scanners() found 1 devices
> > # device `pixma:04A92686_1665JDVj' is a CANON Canon imageClass
> > MF6500 multi-function peripheral
> 
> 

[sane-devel] Canon PIXMA MX350

[Nicolas Martin]

Could you try to recompile Sane with the attached file.

Place it in sane-backends/backend to replace current git one, and
recompile/reinstall Sane.

Nicolas

Le samedi 03 juillet 2010 ? 15:33 +0200, Guenther Hutzl a ?crit :
> > If you can provide the USB pid for this model, we could try a quick
> > test, as there's some chance that this model behaves like a MX340 or
> > MX330, which are already supported. To get this, simply issue a lsusb ,
> > the usb pid should be in the list shown.
> >
> >
> >   
> This is the output of lsusb for the MX350:
> 
> Bus 001 Device 002: ID 04a9:1742 Canon, Inc.
> 
> Is this enough for a first try of do you need lsusb -v output?
> 
> I will use your instructions how to use snoopypro when I have the
> windows PC available.
> 
> Thanks,
> 
> Guenther.
> 
> 
> --
> 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: pixma_mp150.c
Type: text/x-csrc
Size: 49403 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100703/7dd15a52/attachment-0001.c>

[sane-devel] Canon PIXMA MX350

[Nicolas Martin]

Le samedi 03 juillet 2010 ? 09:05 +0200, Guenther Hutzl a ?crit :
> On 07/02/2010 10:19 PM, John wrote:
> >
> > If you haven't got it working yet, you might try the canon drivers for the 
> > MX350 
> > from:
> >
> > http://software.canon-europe.com/products/0010836.asp
> >
> > Using the rpms from that source I have text printing partly working over 
> > wireless which is more than I could do before.  Haven't tried the scanner 
> > yet 
> > but scanner drivers are included in the bundle.
> >
> > --john
> >
> >
> >
> >
> >
> > --
> > 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
> >
> >   
> Hello!
> 
> Thanks for the hint. I will try that driver when I have time. I did not
> yet work on the usb snoop trace. But I will soon. I will soon have
> access to a windows XP pc so I can do the trace then. It would help me
> if anyone could point me to some documentation about how to produce
> useful traces. I did not find any post here, but I may have searched
> wrong. I will post the trace results here when I have them ready in the
> next weeks or so.
> 
> Guenther.
> 

If you can provide the USB pid for this model, we could try a quick
test, as there's some chance that this model behaves like a MX340 or
MX330, which are already supported. To get this, simply issue a lsusb ,
the usb pid should be in the list shown.

Here are some instructions for using SnoopyPro.exe
You can get this free utility SnoopyPro.exe from sourceforge.net:

http://sourceforge.net/projects/usbsnoop/

Read instructions on SnoopyPro.exe, then try to record a scan session
(you must be in under an administrative user account to do that).
Actually, these are the instructions to follow for a snoop:

1. Run SnoopyPro.exe from whereever you have saved it.
2. Open up the USB devices window with F2.
3. Choose 'Unpack Drivers' from the 'File' menu.
4. Choose 'Install Service' from the 'File' menu.
5. Locate the device you want to sniff.
6. Right-click on it and choose 'Install and Restart'.
7. Wait for the magic to happen...

=> Select the device corresponding to the scanner, it will have usb
address: 04A9:
There might be ~4 devices holding this address.
The scanner should be the one indicated by: "MX350 ser"

You can recognize that it's the correct one, if you look at the frame
counter in SnoopyPro, it should increment only when the scanner is
working. 
This is important ... in order to avoid having huge log files filled up
with useless data!

Select a **small** scan area to scan (still to get a small log file)
using the Windows scanning tool (scangear), and start scanning with the
duplex ADF.

Then, Save As ... the file (in SnoopyPro menu), zip the log and send it
back

Nicolas

[sane-devel] Ubuntu 10.4 32 & 64 bit Platform - Canon MF6550 Scanner - sane via any frontend "Hangs" at 1st data transfer

[Nicolas Martin]

Goods news then, thanks Ron for your report ;-)

Looks like your attachment (I suppose the scan log) has been suppressed
from this email (maybe size is too big), so could you retry to get a
smaller one by running these commands: 

$ export SANE_DEBUG_PIXMA=11

$ scanimage -x 100 -y 100 1> /dev/null 2> scanimage.log

Zip or tar.gz the scanimage.log file you get, and send it me back.
I would like to keep it as reference, for easier pixma backend
maintenance.
In the meantime, I'll update the docs for this model.

Concerning Ubuntu 10.04: I don't know if they'll stay with the current
sane lib 1.0.20, or upgrade it. But generally, Ubuntu ships with latest
stable Sane lib (1.0.20 at time 10.04 was released, now 1.0.21)
So I'm afraid you'll probably need to live for a while with the Sane git
version until a Sane 1.0.22 version is released, and then get ships with
Ubuntu.
However, the pixma backend is now very mature, and I'm rather prudent
when adding changes, to keep stability and backwards compatibility. 
You can either install Sane git over Ubuntu's Sane (be careful to keep
the same directories when building the ./configure statement)
Or you could also create your own Sane package with checkinstall, and
install it with dpkg so that it gets included in package management.

NB: export statements are attached to your terminal session, and get
killed when you logout or close terminal.

Nicolas



Le vendredi 02 juillet 2010 ? 09:54 -0500, Ron Parker a ?crit :
> (Attachment Suppressed)
> 
> Success so far.
> 
> The commands below are what I abstracted from the web page you referred
> me to. After building and loading the latest back-end library, a command
> line scan produced the log file that you requested. (Attached).
> 
> Additional scans with gscan2pdf, simplescan, and xsane all produced
> acceptable one page results. I cranked up the resolution to 300 dpi for
> one page, and there was no mis-behavior. My final test in this set was a
> multipage (via gscan2pdf) 150 dpi from the sheet feeder.The resultant
> PDF looked good.
> 
> re: maintaining this configuration. Will ubuntu offer me an update to
> the backend library via the package mechanism? Or, have I detached this
> library from ubuntu package management by building a custom and later
> release of the library?
> 
> Any other tests that you would like me to run? (How do I kill the env
> variable created by EXPORT?)
> 
> Ron
> 
> 
> #http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html
> cd /usr/src
> git clone git://git.debian.org/sane/sane-backends.git
> cd sane-backends
> 
> #If you want later to update your git directory with the latest version
> #available from the public Sane git repository, in order to build the
> latest #Sane code, you just need to enter the following command, from
> the sane-#backends directory:
> # #$ git pull
> # make sure usb dev lib is installed
> 
> apt-get install libusb-dev
> 
> #This will download the latest changes to the files in your directory
> sane-backends.
> 
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
> 
> #This will choose /usr/lib/sane as SANE lib directory, /etc/sane.d as
> SANE #config files dir, and /var/lock/sane as state directory: The ones
> that are #used by Mandriva and Ubuntu.
> 
> make
> make install
> 
> echo '# libusb device nodes : change permissions to 666'
> >/etc/udev/rules.d/mylibsane.rules echo 'SUBSYSTEM=="usb",
> ENV{DEVTYPE}=="usb_device", MODE="0666"'
> >>/etc/udev/rules.d/mylibsane.rules
> 
> scanimage -V
> # Shows version . Should be GTEQ 1.0.21
> # Actual value in this test was 1.0.22 (1Jul2010)
> 
> scanimage -L
> # Shows Scanner
> # pixma_find_scanners() found 1 devices
> # device `pixma:04A92686_1665JDVj' is a CANON Canon imageClass
> MF6500 multi-function peripheral
> 
> --
> 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

[sane-devel] Ubuntu 10.4 32 & 64 bit Platform - Canon MF6550 Scanner - sane via any frontend "Hangs" at 1st data transfer

[Nicolas Martin]

Sending here, answer posted in bug tracker, with adequate formatting.

Message:
The Sane lib 1.0.20 released with Ubuntu 10.04 does did have some
declarations for the MF65xx series, but was untested, due to lack of
testers.

Until recently, some guy tried to use its MF6580 under MacOSX, he sent
me some usb snoops and I've added a few changes in the git version for
this model. 

Unfortunately, we ran then into big troubles trying to test that on Mac
OS X, getting messed up with twain-sane and Darwin libusb ;-(

So if you are running Ubuntu, I would recommend you install the git Sane
lib 
and give a fresh try with it. 
You can get help for that with the following blog post:
http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html

Then, get a logtrace as follows:

$ export SANE_DEBUG_PIXMA=11

$ scanimage   2> scanimage.log 

Send back the scanimage.log file you'll get, for analysis.

Note: On Ubuntu 10.04, you'll probably get into trouble with
permissions, so create a file /etc/udev/rules.d/mylibsane.rules and put
the following content into it:

# libusb device nodes : change permissions to 666
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"

Then, either restart udev, or reboot before trying to run scanimage as
non root user.

Nicolas

Le mercredi 30 juin 2010 ? 16:27 -0500, Ron Parker a ?crit :
> @
> https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=312616&group_id=30186
> 
> I said:
> 
> "I am new to linux scanning, but have looked at the work being done
> for CANON imageclass MF6550 for a year or so. The backends releasd
> with Ubuntu 10.4 seems to be "almost" there.
> 
> Using the XSANE frontend, for example, The scanner model is properly
> identified, and the GUI allows me to request a regular scan or preview
> scan. 
> 
> SYMPTOM: When a (flatbed) scan is initiated, the scan head appears to
> make a registration move, then makes a full 14 inch pass of the
> scanning bed, and then returns to its home position.
> 
> The UBUNTU system "locks" as though it is waiting for a data transfer
> handshake that never happens. No image is returned. This is good for
> ONE attempt. subsequent attempts to scan result in error messages.
> Disconnecting and reconnecting the scanner from the system is not
> sufficient to "clear" the hang. The ubuntu system must be reset.
> 
> So, I am able to recognize the scanner, activate one pass of the scan
> head, and then nothing. I tried this initially under 10.4 (32 bit) and
> after migrating my systems to 64 bit repeated the test with the same
> result.
> 
> I  see that the scanner project wants testers for this model of
> scanner. I would be happy to help, but I will need some hints (e.g.
> where log files might be created. What command I should use to see
> sane process status, a command line option that would isolate and test
> the backend before we bring in GUI frontends to the mix.)
> 
> Ron "
> 
> PS
> 
> Following advice by Nicholas, I am submitting this to the DEV list,
> building an ubuntu library from the "git', and will try to capture
> some test results this evening.
> 
> 
> cd /usr/src
> git clone git://git.debian.org/sane/sane-backends.git
> cd sane-backends
> apt-get install libusb-dev
> ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
> make
> make install
> 
> 
> 
> --
> 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

[sane-devel] [PATCH] Add support for the Canon Pixma MX340

[Nicolas Martin]

THX a lot for your feedback & tests, I'll add your patch to the pixma
backend and update docs.

Nicolas

Le mercredi 30 juin 2010 ? 21:15 -0500, Dan McGee a ?crit :
> It behaves just like the MX330, so more or less a duplication of those
> references worked for this scanner. This has been tested and used
> successfully on the actual device.
> 
> Signed-off-by: Dan McGee 
> ---
>  backend/pixma_mp150.c   |7 +++
>  doc/descriptions/pixma.desc |6 ++
>  doc/sane-pixma.man  |2 +-
>  3 files changed, 14 insertions(+), 1 deletions(-)
> 
> diff --git a/backend/pixma_mp150.c b/backend/pixma_mp150.c
> index c9db8f3..52e038f 100644
> --- a/backend/pixma_mp150.c
> +++ b/backend/pixma_mp150.c
> @@ -148,6 +148,9 @@
>  #define MX320_PID 0x1736/* untested */
>  #define MX330_PID 0x1737
>  
> +/* PIXMA 2010 vintage */
> +#define MX340_PID 0x1741
> +
>  /* Generation 4 */
>  #define MP250_PID 0x173a
>  #define MP270_PID 0x173b
> @@ -1214,6 +1217,7 @@ mp150_check_param (pixma_t * s, pixma_scan_param_t * sp)
>  s->cfg->pid == MX860_PID ||
>  s->cfg->pid == MX320_PID ||
>  s->cfg->pid == MX330_PID ||
> +s->cfg->pid == MX340_PID ||
>  s->cfg->pid == MX7600_PID )
> &&
>  sp->source == PIXMA_SOURCE_FLATBED)
> @@ -1605,6 +1609,9 @@ const pixma_config_t pixma_mp150_devices[] = {
>   * Not sure if anything's going wrong here, leaving as is
>DEVICE ("Canon PIXMA MX860", "MX860", MX860_PID, 2400, 638, 880, 
> PIXMA_CAP_CIS | PIXMA_CAP_ADFDUP),*/
>  
> +  /* PIXMA 2010 vintage */
> +  DEVICE ("Canon PIXMA MX340", "MX340", MX340_PID, 1200, 638, 1050, 
> PIXMA_CAP_CIS | PIXMA_CAP_ADF),
> +
>/* Generation 4: CIS */
>DEVICE ("Canon PIXMA MP640", "MP640", MP640_PID, 4800, 638, 877, 
> PIXMA_CAP_CIS),
>DEVICE ("Canon PIXMA MP560", "MP560", MP560_PID, 2400, 638, 877, 
> PIXMA_CAP_CIS),
> diff --git a/doc/descriptions/pixma.desc b/doc/descriptions/pixma.desc
> index aafd88d..543d817 100644
> --- a/doc/descriptions/pixma.desc
> +++ b/doc/descriptions/pixma.desc
> @@ -237,6 +237,12 @@
>  :status :complete
>  :comment "Flatbed and ADF scan. All resolutions supported (up to 1200DPI)"
>  
> +:model "PIXMA MX340"
> +:interface "USB"
> +:usbid "0x04a9" "0x1741"
> +:status :complete
> +:comment "Flatbed and ADF scan. All resolutions supported (up to 1200DPI)"
> +
>  :model "PIXMA MX700"
>  :interface "USB Ethernet"
>  :usbid "0x04a9" "0x1729"
> diff --git a/doc/sane-pixma.man b/doc/sane-pixma.man
> index a09ea9c..a026041 100644
> --- a/doc/sane-pixma.man
> +++ b/doc/sane-pixma.man
> @@ -27,7 +27,7 @@ PIXMA MP600, MP600R, MP610, MP620, MP630, MP640, MP710
>  .br
>  PIXMA MP800, MP800R, MP810, MP830, MP960, MP970, MP980, MP990
>  .br
> -PIXMA MX300, MX310, MX330, MX700, MX850, MX860, MX7600
> +PIXMA MX300, MX310, MX330, MX340, MX700, MX850, MX860, MX7600
>  .br
>  MultiPASS MP700, MP730, PIXMA MP750 (no grayscale)
>  .br

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

That's good clue indeed.

Also might be better to change the NDEBUG flag in the pixma code to
something more restrictive, like NDEBUGPIXMA

Or ... simply to reconsider this conditional code here and there, as it
was helpful at the time the pixma driver was standalone and not included
into Sane as backend, but is now pretty useless, as pixma logs are
handled directly with Sane flags.

Nicolas

Le lundi 28 juin 2010 ? 12:17 -0500, Chris Bagwell a ?crit :
> Oh, OK.  So one part of the problem is that pixma debug messages
> aren't showing up.
> 
> Can the tester verify as a separate task if scanning is working with
> twain-sane version of libusb though?  It seems it may be working now?
> 
> On debug output part, I see pixma is using some custom stuff to
> disable when NDEBUG is present.  Seems pretty easy that externally
> included header defines NDEBUG that pixma is including but not
> sanei_debug.h.
> 
> A quick test of that theory is to modify the file
> backends/pixma_common.h around line 57 and change "#ifdef NDEBUG" to
> "#ifdef NDEBUGBL".  Also, similar change needed at
> backends/pixma.c line 70.
> 
> Can 
> 
> On Mon, Jun 28, 2010 at 11:46 AM, Nicolas Martin
>  wrote:
> Point is, for whatever reason, Pixma debug logs do not show up
> even when setting SANE_DEBUG_PIXMA to a correct level, only
> SANE_DEBUG and SANE_DEBUG_SANEI_USB produce logs, as showed up
> in the logs twain43 is providing.
>  
> Just trying to figure out why this happens when compiled in
> this environment.
>  
> Nicolas
> 
> 
> 2010/6/28 Chris Bagwell chris at cnpbagwell.com
> 
> I've been fading in and out of this thread so
> I do not have total history of your logs.
> 
> Loooking at only this log, it seems to show
> scanner working correctly while in test mode.
> Can you do same debug logs but while doing an
> actual scan?  Does that work now with the
> patched libusb from twain-sane (does it
> generate a good pnm file)?
> 
> Chris
> 
> 
> 
> 

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Point is, for whatever reason, Pixma debug logs do not show up even when
setting SANE_DEBUG_PIXMA to a correct level, only SANE_DEBUG and
SANE_DEBUG_SANEI_USB produce logs, as showed up in the logs twain43 is
providing.

Just trying to figure out why this happens when compiled in this
environment.

Nicolas

2010/6/28 Chris Bagwell chris at cnpbagwell.com

>
>> I've been fading in and out of this thread so I do not have total history
>> of your logs.
>>
>> Loooking at only this log, it seems to show scanner working correctly
>> while in test mode.  Can you do same debug logs but while doing an actual
>> scan?  Does that work now with the patched libusb from twain-sane (does it
>> generate a good pnm file)?
>>
>> Chris
>>
>>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100628/10fd4e0a/attachment-0001.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

I think you omitted to send the zipped logs with your previous message ?

Nicolas

Le mardi 22 juin 2010 ? 11:14 +, twain43 at hotmail.com a ?crit :
> Took longer than usual, but I did as you recommended.
> 1. Built the libusb version linked and installed it;
> 2. Exported only PIXMA and scanimaged. Log in the attached zip file;
> 3. Exported LIBUSB and SANEI USB debug. Log in the attached zip file;
> 
> No news, I'm a fraid.
> 
> Twain28
> 
> 
> __
> Date: Fri, 18 Jun 2010 11:22:08 -0500
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: chris at cnpbagwell.com
> To: twain43 at hotmail.com
> CC: nicolas0martin at gmail.com; sane-devel at lists.alioth.debian.org
> 
> Here is a suggestion.  Since twain-sane binary seems to work better
> for you, perhaps it has a patched version of libusb that works around
> some OSX bug.  Try comping and installing its version of libusb such
> that your git sane-backends links to it:
> 
> http://www.ellert.se/PKGS/libusb-2009-09-10/src/libusb-2009-09-10-svn-macosx.tar.gz
> 
> If you compile and install with --prefix=/usr/local then be sure and
> add LDFLAGS=-L/usr/local/lib CPPFLAGS=-I/usr/local/include to your
> sane configure command line.
> 
> After that, if its still failing then turn on USB debug options.
> 
> export LIBUSB_DEBUG 255
> export SANE_DEBUG_SANEI_USB 255
> 
> Chris
> 
> On Fri, Jun 18, 2010 at 8:14 AM,  wrote:
> I'm a bit lost too
> If you find somethign else we have not yet tried, just let me
> know, and I'll see what I can do: for the moment, the only
> thing I can think of is trying to clean every bit of SANE on
> my sys and try recompiling and installing with the latest
> development snapshotsbut I guess they're of no use, if the
> Pixma module has not changed
> 
> Twain28
> 
> > Subject: RE: [sane-devel] Testing on Canon MF6580PL
> > From: nicolas0martin at gmail.com
> > To: twain43 at hotmail.com
> > CC: sane-devel at lists.alioth.debian.org
> > Date: Thu, 17 Jun 2010 22:16:45 +0200
> > 
> > Running a bit out of ideas why it behaves like this and why
>     logs do not
> > come out from the backend. 
> > Probably something runs differently on MacOS, but I cannot
> figure out
> > what exactly.
> > 
> > Nicolas
> > 
> > Le jeudi 17 juin 2010 ? 16:47 +, twain43 at hotmail.com a
> ?crit :
> > > Already tried.
> > > 100% same log (see cut-paste below). :(
> > > 
> > 
> > 
> > 
> 
> 
> __
> nome.cognome @... Verifica la disponibilit? sui NUOVI domini
> 
> --
> 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
> 
> 
> 
> __
> Il tuo mondo MSN a portata di clic. Scarica IE8 per MSN
> --
> 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

[sane-devel] Canon PIXMA MX350

[Nicolas Martin]

PIXMA MX350 is not yet declared in the Sane pixma backend, so it won't
be detected.

Do you have the possibility to get a USB Snoop trace using Snoopypro.exe
on windows (I can give you the procedure if you want, this is simple, or
you can look at some other messages in the Sane-devel mailing list where
I explain this) so that I can figure out how to declare it in the
backend ?

Nicolas


Le lundi 21 juin 2010 ? 23:47 +0200, Guenther Hutzl a ?crit :
> Hello!
> 
> I have a Canon PIXMA MX350 Multifunction device and found out that the
> scanner in this model is not yet supported by the sane-pixma driver. Is
> there anybody out there who could help me getting it to work with my
> scanner?
> 
> I am running gentoo linux and I use sane-backends-1.0.21. Could anyone
> please tell me what patches I need to make to the code to at least try
> if the scanner just works with the existing driver? At the moment the
> scanner is not recognized although the printer is detected in the network:
> 
> [pixma] eth0 is IPv4 capable, sending broadcast..
> [pixma] Found scanner at ip address: 192.168.1.88
> [pixma] Scanner at bjnp://192.168.1.88:8612 detected, but it was added
> before, good!
> [pixma] Found scanner at ip address: 192.168.1.88
> [pixma] Scanner at bjnp://192.168.1.88:8612 detected, but it was added
> before, good!
> [pixma] Found scanner at ip address: 192.168.1.88
> [pixma] Scanner at bjnp://192.168.1.88:8612 detected, but it was added
> before, good!
> [pixma] Found scanner at ip address: 192.168.1.88
> [pixma] Scanner at bjnp://192.168.1.88:8612 detected, but it was added
> before, good!
> [pixma] Found scanner at ip address: 192.168.1.88
> [pixma] Scanner at bjnp://192.168.1.88:8612 detected, but it was added
> before, good!
> [pixma] pixma_find_scanners() found 0 devices
> 
> I am running linux only so I cannot make usb traces but I have a vmware
> player virtual machine running with Windows XP if that helps in creating
> usb traces. I also have access to a macbook if one can do usb traces
> using a mac.
> 
> Any help is appreciated. Thanks in advance,
> 
> Guenther.
> 
> 
> --
> 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

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Running a bit out of ideas why it behaves like this and why logs do not
come out from the backend. 
Probably something runs differently on MacOS, but I cannot figure out
what exactly.

Nicolas

Le jeudi 17 juin 2010 ? 16:47 +, twain43 at hotmail.com a ?crit :
> Already tried.
> 100% same log (see cut-paste below). :(
> 

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

So complete different behaviour here than on Linux.

And does the scanimage > foo.pnm with the same export statement give more
information ?

2010/6/17 

> Here's the pixma trace logbut I'm afraid it reports nothing more than
> it did last time
>
> Twain28
>
> --
>
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

So now, are you able to get a log trace with [pixma] statements, using only
the export SANE_DEBUG_PIXMA=11 statement, and a scanimage -T or a scanimage
> foo.pnm ?

The purpose is to get a trace to know where an error is encountered. Without
it, I'm afraid we will not be able to investigate too far

Nicolas

2010/6/17 

> Small footnote: I actually noticed TwainSANE's PrefPane now displays some
> drivers in two copiesdon't know if this affects or not the usage, but
> maybe it's important.
>
>
> Twain28
>
> --
> Il tuo mondo MSN a portata di clic. Scarica IE8 per 
> MSN<http://events.it.msn.com/internet-explorer-8>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100617/c698dfc4/attachment.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

There's been no change to the git rep on 14th or 15th concerning the pixma
backend, changes affect only other backends. Latest changes to pixma backend
was on June 8

But to be sure, you could try to download the 14 June git image and test
with it.
Just go to the Web page:
http://git.debian.org/?p=sane/sane-backends.git;a=shortlog
and download the corresponding snapshot you want.

Nicolas


2010/6/17 

> Nope, I can't...could that log's result be related to something in the
> daily snapshot of 14th of June?
> Right now, I'm using the patch over the snapshot dated 15th June. Is there
> a way to recover back the first snapshot, so that I can test it?
> (attaching today's log, just in case: gets stuck at some point, no PASS
> statements)
>
> Twain28
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100617/8612d741/attachment.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Meaning, you cannot get again the log you sent on 14 June, here attached ?
2010/6/16 

> SorryI had misunderstood your question:
> scanimage -T
> simply reports
> "scanimage: open of device pixma:04A92686_1569EE8o0016 failed: Invalid
> argument"
>
>
> Twain28
>
> --
> From: twain43 at hotmail.com
> To: nicolas0martin at gmail.com
> Date: Wed, 16 Jun 2010 15:38:23 +
>
> CC: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
>
> I think I do
> Same result happens using both basic user and with "sudo su" before
> command.
> command issued: scanimage -T 2>nameofthe.log
>
> Twain28
>
> --
> Date: Wed, 16 Jun 2010 16:09:54 +0200
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
>
> Failing at the very beginning of the scan here.
>
> At this point, do you have the
>
> scanimage  -T
>
> command running correctly ? i.e., with the PASS statements ?
>
> 2010/6/16 
>
> Done so.
> Here's the log. No cuts here, I just quit terminal after a few minutes of
> wait. No wheezing sounds from the scanner.
> (Sorry about the previous log-cut: things got a bit messy...I have only 2gb
> free space, and they suddently went clogged by the log's massive
> tempfileit's actually a miracle I managed to send even those few
> lines)
> Hope you can make something out of this new log (hence the name).
>
> Twain28
>
> --
> Date: Wed, 16 Jun 2010 15:07:07 +0200
>
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
>
> So now, could you install the git version, and the patched file I sent you,
> and give another try ?
>
> BTW, you cut too much of the previous log trace, it shows only the very
> beginning of the scanning dialog
>
> Nicolas
>
> 2010/6/16 
>
> Done.
> 1: make uninstalled sane development version;
> 2: reinstalled TwainSANE interface (2.9) + its preference pane (0.9), then
> SANE backends (1.0.21-git 2010-01-17) and libusb (0.1.13 beta 2009-09-10) as
> per TwainSANE website;
> 3: ran the usual logtest, with the three exports;
> 4. cut the over 500MB logfile as soon as it started looping.
> You find the snipped log attached.
>
> Seems to me things are "back to normal"
>
>
> Twain28
>
> --
> From: twain43 at hotmail.com
> To: nicolas0martin at gmail.com
> Date: Wed, 16 Jun 2010 12:07:32 +
>
> CC: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
>
> The only thing I can think of to get back that log result is to reinstall
> the TwainSane interface and backends
> I'll try uninstalling all and get back to them
>
> Twain28
>
> --
> Date: Wed, 16 Jun 2010 13:59:56 +0200
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
>
> You mean you cannot get anymore the same log that you produced and sent us
> 12 days ago, on June 4 ?
>
> Nicolas
>
> 2010/6/16 
>
> Today's log.
> I manually deleted the printer from both System Preferences and
> /Library/Printers, then tried again. No actual change.
> Is there something else I could try?
>
>
> Twain28
>
>
> --
> nome.cognome @... Verifica la disponibilit? sui NUOVI 
> domini<https://signup.live.com/signup.aspx?mkt=it-it&rollrs=12&lic=1>
>  --
> Un mondo di personalizzazioni per Messenger, PC e cellulare, scaricale
> gratis! <http://www.pimpit.it/>
>
>
>
> --
> nome.cognome @... Verifica la disponibilit? sui NUOVI 
> domini<https://signup.live.com/signup.aspx?mkt=it-it&rollrs=12&lic=1>
>
> --
> 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
>
>
>
> --
> Importa i tuoi contatti di Facebook. Chiacchiera su 
> Messenger!<http://www.windowslive.it/importaAmici.aspx>
> --
> Importa i tuoi contatti di Facebook. Chiacchiera su 
> Messenger

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Another strangeness here. I can read this from this log:

libusb/darwin.c usb_bulk_transfer: USB pipe is an interrupt pipe. Timeouts
will not be used.
meaning that Darwin libusb still does not handle interrupt timeouts.

So I don't yet understand how the previous scanimage -T could work !

2010/6/16 Nicolas Martin 

> Failing at the very beginning of the scan here.
>
> At this point, do you have the
>
> scanimage  -T
>
> command running correctly ? i.e., with the PASS statements ?
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100616/63fb23c8/attachment.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Failing at the very beginning of the scan here.

At this point, do you have the

scanimage  -T

command running correctly ? i.e., with the PASS statements ?

2010/6/16 

> Done so.
> Here's the log. No cuts here, I just quit terminal after a few minutes of
> wait. No wheezing sounds from the scanner.
> (Sorry about the previous log-cut: things got a bit messy...I have only 2gb
> free space, and they suddently went clogged by the log's massive
> tempfileit's actually a miracle I managed to send even those few
> lines)
> Hope you can make something out of this new log (hence the name).
>
> Twain28
>
> --
> Date: Wed, 16 Jun 2010 15:07:07 +0200
>
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
>
> So now, could you install the git version, and the patched file I sent you,
> and give another try ?
>
> BTW, you cut too much of the previous log trace, it shows only the very
> beginning of the scanning dialog
>
> Nicolas
>
> 2010/6/16 
>
> Done.
> 1: make uninstalled sane development version;
> 2: reinstalled TwainSANE interface (2.9) + its preference pane (0.9), then
> SANE backends (1.0.21-git 2010-01-17) and libusb (0.1.13 beta 2009-09-10) as
> per TwainSANE website;
> 3: ran the usual logtest, with the three exports;
> 4. cut the over 500MB logfile as soon as it started looping.
> You find the snipped log attached.
>
> Seems to me things are "back to normal"
>
>
> Twain28
>
> --
> From: twain43 at hotmail.com
> To: nicolas0martin at gmail.com
> Date: Wed, 16 Jun 2010 12:07:32 +
>
> CC: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
>
> The only thing I can think of to get back that log result is to reinstall
> the TwainSane interface and backends
> I'll try uninstalling all and get back to them
>
> Twain28
>
> --
> Date: Wed, 16 Jun 2010 13:59:56 +0200
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
>
> You mean you cannot get anymore the same log that you produced and sent us
> 12 days ago, on June 4 ?
>
> Nicolas
>
> 2010/6/16 
>
> Today's log.
> I manually deleted the printer from both System Preferences and
> /Library/Printers, then tried again. No actual change.
> Is there something else I could try?
>
>
> Twain28
>
>
> --
> nome.cognome @... Verifica la disponibilit? sui NUOVI 
> domini<https://signup.live.com/signup.aspx?mkt=it-it&rollrs=12&lic=1>
>  --
> Un mondo di personalizzazioni per Messenger, PC e cellulare, scaricale
> gratis! <http://www.pimpit.it/>
>
>
>
> --
> nome.cognome @... Verifica la disponibilit? sui NUOVI 
> domini<https://signup.live.com/signup.aspx?mkt=it-it&rollrs=12&lic=1>
>
> --
> 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 --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100616/5d9f530b/attachment-0001.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

So now, could you install the git version, and the patched file I sent you,
and give another try ?

BTW, you cut too much of the previous log trace, it shows only the very
beginning of the scanning dialog

Nicolas

2010/6/16 

> Done.
> 1: make uninstalled sane development version;
> 2: reinstalled TwainSANE interface (2.9) + its preference pane (0.9), then
> SANE backends (1.0.21-git 2010-01-17) and libusb (0.1.13 beta 2009-09-10) as
> per TwainSANE website;
> 3: ran the usual logtest, with the three exports;
> 4. cut the over 500MB logfile as soon as it started looping.
> You find the snipped log attached.
>
> Seems to me things are "back to normal"
>
>
> Twain28
>
> --
> From: twain43 at hotmail.com
> To: nicolas0martin at gmail.com
> Date: Wed, 16 Jun 2010 12:07:32 +
>
> CC: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
>
> The only thing I can think of to get back that log result is to reinstall
> the TwainSane interface and backends
> I'll try uninstalling all and get back to them
>
> Twain28
>
> --
> Date: Wed, 16 Jun 2010 13:59:56 +0200
> Subject: Re: [sane-devel] Testing on Canon MF6580PL
> From: nicolas0martin at gmail.com
> To: twain43 at hotmail.com
> CC: sane-devel at lists.alioth.debian.org
>
> You mean you cannot get anymore the same log that you produced and sent us
> 12 days ago, on June 4 ?
>
> Nicolas
>
> 2010/6/16 
>
> Today's log.
> I manually deleted the printer from both System Preferences and
> /Library/Printers, then tried again. No actual change.
> Is there something else I could try?
>
>
> Twain28
>
>
> --
> nome.cognome @... Verifica la disponibilit? sui NUOVI 
> domini<https://signup.live.com/signup.aspx?mkt=it-it&rollrs=12&lic=1>
>  --
> Un mondo di personalizzazioni per Messenger, PC e cellulare, scaricale
> gratis! <http://www.pimpit.it/>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100616/c399fd4f/attachment-0001.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

You mean you cannot get anymore the same log that you produced and sent us
12 days ago, on June 4 ?

Nicolas

2010/6/16 

> Today's log.
> I manually deleted the printer from both System Preferences and
> /Library/Printers, then tried again. No actual change.
> Is there something else I could try?
>
>
> Twain28
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100616/703fc0f5/attachment.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Not sure.

Canon printer SW may have locked the USB port.
Could you ty to disable printing at least for a test ?

2010/6/15 

> Rebooted, run as root. Log reads indentical.
>
> regarding allan's question: do canon's printer drivers count as "software"?
> If so, yesbut I really see no means of uninstalling them.
>
>
> Twain28
>
> --
> Importa i tuoi contatti di Facebook. Chiacchiera su 
> Messenger!
>
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Sounds like you cannot get to same state as you were on June 4.
Did you try to reboot the Hackintosh ?
Did you try to run these commands as root ?

2010/6/15 

> New log. Same result. Tried plugging/unplugging before: nothing changed.
>
> Twain28
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Looks this time, your scanner is locked by some other application.
Maybe you should try to unplug/replug it ?

[pixma] scanner discovery finished...

[pixma] pixma_open(): Canon imageClass MF6500

[sanei_usb] sanei_usb_open: trying to open device
`libusb:005:002-04a9-2686-00-00'

usb_os_open: 04a9:2686

usb_os_open(USBDeviceOpenSeize): another process has device opened for
exclusive access

usb_set_configuration: called for config 1

USB error: usb_set_configuration(SetConfiguration): device not opened for
exclusive access

[sanei_usb] sanei_usb_open: libusb complained:
usb_set_configuration(SetConfiguration): device not opened for exclusive
access

usb_os_close: 04a9:2686

[pixma] pixma_connect() failed EINVAL

[pixma] pixma_open() failed EINVAL

[pixma] pixma_close(): Canon imageClass MF6500

scanimage: open of device pixma:04A92686 failed: Invalid argument




2010/6/15 
>
> And here's the log with the patched and recompiled version.
> This time, something different sprouted out: pixma arguments!
> Hope this helps.
>
> Twain28
-- next part --
An HTML attachment was scrubbed...
URL: 

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

But there's nothing in this log !

Something looks wrong with your installation, so could you try to get a
scanimage log as you did formerly, like the one sent on 4 June ?

Nicolas

2010/6/15 

> Here's the log. I attached the pnm file too, just in case
> This time, pixma statements got through.
>
>
> Twain28
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100615/468bb7e9/attachment.htm>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Yes ... the interesting log with [pixma] statements was send to your
console !

This little image filled up with 0s is strange, to understand what's
going on, could you try to get another log with the following commands:

export SANE_DEBUG_PIXMA=11

scanimage  2> scanimage.log  1> foo.pnm

You should get hopefully the [pixma] statements now into scanimage.log

Could you send this file back

Nicolas


Le lundi 14 juin 2010 ? 09:41 +, twain43 at hotmail.com a ?crit :
> Dialing scanimage > foo.pnm produces a blank, 32kb file.
> 
> I'm attaching it, along with today's log. 
> The log is obtained dialing the 3 export commands, as the last one
> wasbut again contains no [pixma] statements, which is kind of
> strange
> 
> Indeed the log reads good, but I should point out that after your
> patch, the scanner makes no longer wheezing noises (kind of "preparing
> to acquire images" signal, IMHO), as it did before. So maybe something
> is still missing
> 
> Twain28
> 

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

This log looks good indeed ;-)

A suggestion: did you try

scanimage > foo.pnm

and look what you get in foo.pnm ?

PS: the previous log did not contain the [pixma] statements, meaning you
may have omitted one of the 3 export commands to enter before running
the scanimage -T . Could you try again, and send me the corresponding
log, I would like to keep it as reference. TIA.

Nicolas

Le vendredi 11 juin 2010 ? 09:58 +, twain43 at hotmail.com a ?crit :
> Here's the new log, after recompilation with your hack. 
> I attached it all, zipped, since its end looked somewhat promising, to
> me.  ;)
> 
> Twain28

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

I don't know the current status of Darwin libusb against usb interrupts,
but it used to not support timeouts in older versions, which makes pixma
backend unusable for some PIXMA models. 

Looking at the Darwin libusb 1.13 source files, comments show this may
be working now, but not sure (source code still contains a message about
timeouts not being supported). 

Anyway, I added a while back a very ugly hack in the pixma backend, that
used to work for some PIXMA devices (use a read bulk instead of a read
interrupt) but it may fail with others. 
What I can propose to you is to give a try without this hack, to check
if this is better now with the current Darwin libusb. 

So please replace your current git file:
sane-backends/backend/pixma_io_sanei.c with the one I've attached,
recompile/reinstall, and give another try as you did just previously
(with the 3 exports statements). 
And send back the new scanimage.log you'll get.

Nicolas

Le jeudi 10 juin 2010 ? 09:29 +, twain43 at hotmail.com a ?crit :
> Here's the new log, obtained following your instruction.
> I'm on Mac OS X 10.5.8, Libusb 0.1.13 beta 2009-09-10 (got from TWAIN
> SANE project page).
> Crossing my fingers for a miracle
> 
> Twain28

-- next part --
A non-text attachment was scrubbed...
Name: pixma_io_sanei.c
Type: text/x-csrc
Size: 14922 bytes
Desc: not available
URL: 
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100610/1fe9556a/attachment-0001.c>

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Just looked at the logs (only the beginning is interesting for me), but
it fails at the same point even after having fixed the checksums
(although the scanner did not seem to care they were misplaced)

But one thing surprises me: in the usb dialogs, I don't see any USB
Interrupt messages like in the Windows snoop, only Bulk ones are
present. 

And I remember one important point: running the pixma backend on a Mac
is not sure it will work, because the Darwin libusb library on Mac does
not implement USB Interrupts :-( 
Some PIXMA/Imageclass models can cope with that, but others not. And I'm
afraid we might be here in this pitfall. Do you confirm running it on
MacOS ? Which version of MacOS and Darwin libusb ?

To be sure, could you try taking some additional USB logs this time,
just record the first 30 seconds it's fine (the 50K log you sent is
enough for debug) with these commands:

export SANE_DEBUG_SANEI_USB=255
export SANE_DEBUG=255
export SANE_DEBUG_PIXMA=11
scanimage -T 2> scanimage.log

and send back the logs

Nicolas


Le mercredi 09 juin 2010 ? 15:32 +, twain43 at hotmail.com a ?crit :
> UhmI have to point out the log I attached a minute ago reports
> just the first lines of the original one: over 300mb in less than 2
> minutes
> 
> Twain28
> 
> 
> __
> Il tuo mondo MSN a portata di clic. Scarica IE8 per MSN
> --
> 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

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Just Committed a few bunch of modifications to latest git. 

Could you give a try with it, and get another scanimage -T logfile as
you did previously: 

export SANE_DEBUG_PIXMA=11
scanimage -T  2> scanimage.log

We will see how it behaves from there

Nicolas

Le lundi 07 juin 2010 ? 09:20 +, twain43 at hotmail.com a ?crit :
> Ok, here's the log, obtained following the instructions provided. I'm
> also posting the steps I went through, just in case I missed
> something:
> 1. Fired up Canon's scan interface on Win Vista and selected a very
> small area to acquire;
> 2. Started Snoopypro, unpacked the driver, installed the service,
> selected the correct USB device, then install-rebooted the logger;
> 3. Back to the Canon's interface, I issued the "Scan" command. The
> logger instantly started capturing.
> 
> You find the log attached, zipped. You were right: the thing took over
> 2 megs of log for a very small area!
> 
> Hope this helps narrowing out things.
> 
> Twain28
> 
> 
> __
> nome.cognome @... Verifica la disponibilit? sui NUOVI domini

[sane-devel] [PATCH] po/fr: updates

[Nicolas Martin]

Just browsed quickly through the French sentences, and saw a small
typo: 

courier 

correct writing is with 2 r

courrier



Le dimanche 06 juin 2010 ? 00:55 +0200, Yann E. MORIN a ?crit :

>  
>  #: ../include/sane/saneopts.h:445
> -#, fuzzy, no-c-format
> +#, no-c-format
>  msgid "Email button"
> -msgstr "Attendre le bouton"
> +msgstr "Bouton 'courier ?lectronique'"
>  
>  #: ../include/sane/saneopts.h:446
> -#, fuzzy, no-c-format
> +#, no-c-format
>  msgid "Fax button"
> -msgstr "Attendre le bouton"
> +msgstr "Bouton 'Fax'"

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

You can use Snoopypro.exe to get a usb snoop on Windows, this is a very
old program, but hopefully, still working on Vista.

Download from Snoopypro from sourceforge.net here:

http://sourceforge.net/projects/usbsnoop/

Read and follow exactly the instructions in SnoopyPro.exe, then try to
record a scan session.

 => Select the device corresponding to the scanner, using its USB
address 04A9:2686

There will be ~4 devices holding this address.
The scanner should be the one indicated by: "MF6580 ser"

You can recognize that it's the correct one, if you look at the frame
counter in SnoopyPro, it should increment only when MF6580 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 samedi 05 juin 2010 ? 08:28 +, twain43 at hotmail.com a ?crit :
> I'm running SANE on a Hackintosh, so the answer to you both is a
> definite Yes. ;)
> 
> If you explain me how to obtain the usb snoop on Windows (I'm assuming
> it'd be the fastest way), I'll do it on monday, as soon as I get back
> to office, and post back.
> 
> Twain28
> 
> 
> __
> Importa i tuoi contatti di Facebook. Chiacchiera su Messenger!

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Thanks for the log.
I'm wondering whether this model acts like the MF4600 series, giving the
point where the scan sequence fails.

Do you have the possibility to run a Windows PC with this scanner, to
get a usb snoop (I can explain you how this is pretty easy) ?

Nicolas

Le vendredi 04 juin 2010 ? 16:40 +, twain43 at hotmail.com a ?crit :
> Ok, moderator rejected the monsterfile.
> I'm attaching a stripped down logfile: I left the first error
> messages: they kinda loop 'till the end.
> Hope this helps.
> 
> Twain28
> 
> 
> 
> __

[sane-devel] Testing on Canon MF6580PL

[Nicolas Martin]

Looks this will require some logs to be taken first.

Turn debugging on this way in order to grab some additional data.
Run scanimage after some export commands:

export SANE_DEBUG_PIXMA=11

scanimage -T  2> scanimage.log 

Send back the scanimage.log file you'll get.

Nicolas

Le jeudi 03 juin 2010 ? 21:03 +, twain43 at hotmail.com a ?crit :
> Hello there!
> 
> Had already tried that: scanner makes wheezy noises and seems to
> prepare for duty, 0 byte file gets actually generated, but then all
> stops.
> Is there some special configuration I have to try?
> 
> Twain28
> 
> 
> __
> Un mondo di personalizzazioni per Messenger, PC e cellulare, scaricale
> gratis!
> --
> 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

[sane-devel] Canon MF3110 Problem

[Nicolas Martin]

Unfortunately, the pixma backend you're using, probably coming with your
Linux distribution, is too old (0.15.0), MF3110 was declared but under
an incorrect Pixma class of protocol, so trying here to use a wrong
Pixma protocol (as seen in the d420 message, wrong length). 

This has been fixed since then in Sept 2009 (changed protocol class), so
please install the latest version of git Sane, and hopefully, your
MF3110 should then run out of the box ... or let us know.

Nicolas 

Le jeudi 25 mars 2010 ? 22:02 +0900, Gernot Hassenpflug a ?crit :
> On Thu, Mar 25, 2010 at 9:47 PM, forum at coolpixx.de  
> wrote
> > Ok now I hope it's right
> 
> Perfect! I hope Nicolas Martin will give his opinion also, since he is
> working on the pixma backend and I do not have experience with the
> ImageCLASS devices but will take a look.
> 
> Regards,
> Gernot
> 
> --
> 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

[sane-devel] MP210 or PIXMA MP210 under Slackware13.0 not working...

[Nicolas Martin]

Le samedi 06 mars 2010 ? 18:04 -0800, Bradley D. Thornton a ?crit :
> Hi Nicolas :)
> 
> Nicolas Martin wrote:
> > AFAIK, the Pixma protocol, which MP210 uses, is different from the one
> > implemented in canon630u, and I guess MP210 won't be able to work with
> > that backend.
> 
> Yes you are correct there ;)  Although it does pick up the scanner in 
> the canon630u.conf file.

And MP210 should not be declared here, so this is maybe an issue due to
Slackware, as Sane packages do not ship with that.
> 
> >  
> >
> > FYI, the pixma.conf file is only for network Pixma models, that use
> > Canon's bjnp network protocol, and you can set in this file the scanner
> > ip, if it does not get autodetected by the pixma backend.
> >   
> 
> So, which conf file holds the data for the device? i.e., 
> 'pisma:04A91721_F32369'

The usb pids are hold directly in the pixma backend, this is because the
Canon Pixma protocol exists in fact in about 10 different flavours, the
pixma backend supports currently 67 different Pixma/I-Sensys/ImageClass
models, and different code is used according to the model group. Each
time a new model is added, a check must be done to see which Pixma
protocol is involved. So adding a new model requires a recompilation of
the backend. 

Nicolas

> > Good to read about your success!
> >   
> 
> And thank you too. Looking forward to doing a write up at SlackWiki for 
> this :)
> 
> > Regards
> > Nicolas
> >
> > Le samedi 06 mars 2010 ? 04:20 -0800, Bradley D. Thornton a ?crit :
> >   
> >> Hey thanks Nicolas!
> >>
> >> Slackware 13.0 ships with 1.0.19, and in the Slackware-current 
> >> repository there were packages for 1.0.20, which broke everything until 
> >> I upgraded lib4vl and installed libjpeg, then everything sprung to life.
> >>
> >> There was (I think a man page) that explained that canon630u worked with 
> >> the MP210, but I'm guessing there's a difference between the PIXMA MP210 
> >> and the other, which was autodetected.
> >>
> >> I removed the autodetected MP210 in canon630u and added 'pixma' in 
> >> dll.conf - even though the pixma.conf file was already there.
> >>
> >> There's still nothing in my pixma.conf file, which has me scratching my 
> >> head, but xsane is totally rocking now :)
> >>
> >> I'm not sure if I would have had permission problems as an unpriv'd user 
> >> or not, but from the get go I added the unpriv'd uid to the following in 
> >> /etc/group: plugdev, and scanner, among others.
> >>
> >> I d/l'd a script from a friend to detect and set perms, and placed it in 
> >> /etc/rc.d/rc.local, but again, I don't know if that was really needed to 
> >> help since the scanner still didn't work until I upgraded to sane-1.0.20 
> >> with the two other libraries.
> >>
> >> I'm going to set up an old dummy box to check and see exactly where the 
> >> device will start working, by beginning immediately with the upgrade of 
> >> the backend and libs, and then take it from there so I can do a write up 
> >> for the next poor soul who finds himself in the same pickle as I was in 
> >> too :)
> >>
> >> Thanks for all your work on this project and your support as well!
> >>
> >> Kindest regards,
> >>
> >> Bradley.
> >>
> >> Nicolas Martin wrote:
> >> 
> >>> MP210 is well supported by Sane (should be OK with 1.0.20, but better
> >>> install Sane git and recompile now that you're here), I don't know which
> >>> version of Sane ships with Slackware 13.0, but the MP210 is a Pixma
> >>> model, and uses the Sane pixma backend to operate. NOT canon630u.
> >>>
> >>> After browsing quickly through the thread you're indicating, here are
> >>> some pointers to help you set up your Pixma:
> >>>
> >>> - be sure the pixma backend is enabled in dll.conf
> >>> - check the version of Sane you're using. MP210 is supported since Sane
> >>> 1.0.20, but better install Sane git as you'll benefit from latest
> >>> enhancements and fixes
> >>> - check the usb perms. This is is a recurring issue, so first try under
> >>> root to have your scanner recognized and handled. If it works with root,
> >>> then go ahead with a normal user account, and check the perms the
> >>> scanner gets for r & w, you can use the udev rul

[sane-devel] MP210 or PIXMA MP210 under Slackware13.0 not working...

[Nicolas Martin]

AFAIK, the Pixma protocol, which MP210 uses, is different from the one
implemented in canon630u, and I guess MP210 won't be able to work with
that backend. 

FYI, the pixma.conf file is only for network Pixma models, that use
Canon's bjnp network protocol, and you can set in this file the scanner
ip, if it does not get autodetected by the pixma backend.

Good to read about your success!

Regards
Nicolas

Le samedi 06 mars 2010 ? 04:20 -0800, Bradley D. Thornton a ?crit :
> Hey thanks Nicolas!
> 
> Slackware 13.0 ships with 1.0.19, and in the Slackware-current 
> repository there were packages for 1.0.20, which broke everything until 
> I upgraded lib4vl and installed libjpeg, then everything sprung to life.
> 
> There was (I think a man page) that explained that canon630u worked with 
> the MP210, but I'm guessing there's a difference between the PIXMA MP210 
> and the other, which was autodetected.
> 
> I removed the autodetected MP210 in canon630u and added 'pixma' in 
> dll.conf - even though the pixma.conf file was already there.
> 
> There's still nothing in my pixma.conf file, which has me scratching my 
> head, but xsane is totally rocking now :)
> 
> I'm not sure if I would have had permission problems as an unpriv'd user 
> or not, but from the get go I added the unpriv'd uid to the following in 
> /etc/group: plugdev, and scanner, among others.
> 
> I d/l'd a script from a friend to detect and set perms, and placed it in 
> /etc/rc.d/rc.local, but again, I don't know if that was really needed to 
> help since the scanner still didn't work until I upgraded to sane-1.0.20 
> with the two other libraries.
> 
> I'm going to set up an old dummy box to check and see exactly where the 
> device will start working, by beginning immediately with the upgrade of 
> the backend and libs, and then take it from there so I can do a write up 
> for the next poor soul who finds himself in the same pickle as I was in 
> too :)
> 
> Thanks for all your work on this project and your support as well!
> 
> Kindest regards,
> 
> Bradley.
> 
> Nicolas Martin wrote:
> > MP210 is well supported by Sane (should be OK with 1.0.20, but better
> > install Sane git and recompile now that you're here), I don't know which
> > version of Sane ships with Slackware 13.0, but the MP210 is a Pixma
> > model, and uses the Sane pixma backend to operate. NOT canon630u.
> >
> > After browsing quickly through the thread you're indicating, here are
> > some pointers to help you set up your Pixma:
> >
> > - be sure the pixma backend is enabled in dll.conf
> > - check the version of Sane you're using. MP210 is supported since Sane
> > 1.0.20, but better install Sane git as you'll benefit from latest
> > enhancements and fixes
> > - check the usb perms. This is is a recurring issue, so first try under
> > root to have your scanner recognized and handled. If it works with root,
> > then go ahead with a normal user account, and check the perms the
> > scanner gets for r & w, you can use the udev rules if your distribution
> > uses them to tweak the usb devices perms.
> > - take some logs to see in more depth what's going on:
> > $ export SANE_DEBUG_PIXMA=11
> > $ scanimage -L
> > $ scanimage -T
> > These commands will become your friends.
> >
> > Hope it helps, good luck, and feel free to post if you need more help.
> >
> > Nicolas
> >
> > Le vendredi 05 mars 2010 ? 17:33 -0800, Bradley D. Thornton a ?crit :
> >   
> >> Hello.
> >>
> >> I've been having some difficulties in setting up my PIXMA MP210 scanner 
> >> under Slackware 13.0.
> >>
> >> I could really use some help here, and to save a long, drawn out 
> >> explanation here covering everything I've been wrestling with over the 
> >> last two days, There is a very detailed thread I've posted here:
> >>
> >> http://www.linuxquestions.org/questions/slackware-14/problems-setting-up-scanner-in-slackware-13.0-793324/
> >>
> >> Basically, my scanner is being detected as an MP210 just fine, but it's 
> >> using the canon630u.conf, and there wasn't any pixma.conf in 
> >> /etc/sane.d/, although there is a pixma entry in dll.conf as well as a 
> >> canon630u entry.
> >>
> >> Any assistance would be greatly appreciated. This has me pulling my hair 
> >> out :)
> >>
> >>
> >> 
> >
> >
> >   
> 

[sane-devel] MP210 or PIXMA MP210 under Slackware13.0 not working...

[Nicolas Martin]

MP210 is well supported by Sane (should be OK with 1.0.20, but better
install Sane git and recompile now that you're here), I don't know which
version of Sane ships with Slackware 13.0, but the MP210 is a Pixma
model, and uses the Sane pixma backend to operate. NOT canon630u.

After browsing quickly through the thread you're indicating, here are
some pointers to help you set up your Pixma:

- be sure the pixma backend is enabled in dll.conf
- check the version of Sane you're using. MP210 is supported since Sane
1.0.20, but better install Sane git as you'll benefit from latest
enhancements and fixes
- check the usb perms. This is is a recurring issue, so first try under
root to have your scanner recognized and handled. If it works with root,
then go ahead with a normal user account, and check the perms the
scanner gets for r & w, you can use the udev rules if your distribution
uses them to tweak the usb devices perms.
- take some logs to see in more depth what's going on:
$ export SANE_DEBUG_PIXMA=11
$ scanimage -L
$ scanimage -T
These commands will become your friends.

Hope it helps, good luck, and feel free to post if you need more help.

Nicolas

Le vendredi 05 mars 2010 ? 17:33 -0800, Bradley D. Thornton a ?crit :
> Hello.
> 
> I've been having some difficulties in setting up my PIXMA MP210 scanner 
> under Slackware 13.0.
> 
> I could really use some help here, and to save a long, drawn out 
> explanation here covering everything I've been wrestling with over the 
> last two days, There is a very detailed thread I've posted here:
> 
> http://www.linuxquestions.org/questions/slackware-14/problems-setting-up-scanner-in-slackware-13.0-793324/
> 
> Basically, my scanner is being detected as an MP210 just fine, but it's 
> using the canon630u.conf, and there wasn't any pixma.conf in 
> /etc/sane.d/, although there is a pixma entry in dll.conf as well as a 
> canon630u entry.
> 
> Any assistance would be greatly appreciated. This has me pulling my hair 
> out :)
> 
> 

[sane-devel] Canon ImageCLASS MF4350d, Ubuntu 8.04, scanner not found

[Nicolas Martin]

Le lundi 01 f?vrier 2010 ? 00:24 -0500, Michael DeBusk a ?crit :
> On 01/30/2010 05:36 AM, Nicolas Martin wrote:

> The black and the white were fine. I had trouble with the gray on the
> color scan because gray on an inkjet isn't really gray. I had better
> luck with a DVD cover I had nearby.

Yes, an inkjet print is scattered, more especially if you printed it in
colour.
But Xsane gray pipette uses the luminance of the selected pixel/zone to
trim contrast/brightness and gamma, not directly the actual pixel color.

> > Let us know if everything goes right with the results you get, so
> > that I can update the documentation for this device.
> 
> All went well once I got the scanner to wake up. I had to turn it off
> and on. Even hitting the buttons didn't get its attention (lights came
> on, but scanner still didn't wake up).
> 
> Thank you all for your help.
> 
Thanks for your feedback, I'll update Sane documentation ASAP for this
device.

Nicolas

[sane-devel] Canon ImageCLASS MF4350d, Ubuntu 8.04, scanner not found

[Nicolas Martin]

Le samedi 30 janvier 2010 ? 05:22 -0500, Michael DeBusk a ?crit :
> I take it that that counts as "working" now. Is there anything I can do
> to add additional useful information to this thread?
> 
Try to scan an image with Xsane. 
Adjust the colors using the 3 pipettes tool (white/black/gray) in the
preview window.
Let us know if everything goes right with the results you get, so that I
can update the documentation for this device.

Nicolas

[sane-devel] Canon ImageCLASS MF4350d, Ubuntu 8.04, scanner not found

[Nicolas Martin]

MF43x0d models, have started to be supported in the git development
version of Sane a few months ago. That's why they are not supported by
Sane 1.0.19 nor 1.0.20, they're only supported by Sane git for now.
 
First, install the git Sane version, you can get help for that in the
blog post below:
http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html

MF4370/4380 and 4350 share apparently the same usb pid, so there's great
chance MF4350 will work too, although yet untested.

If you don't get the MF4350 to work with Sane git, then check this is
not due to a perms issue (try as root) then take a logtrace as follows:

$ export SANE_DEBUG_SANEI_USB=255
$ export SANE_DEBUG=255
$ export SANE_DEBUG_PIXMA=11

$ scanimage -T 2> scanimage.log 

Send back the scanimage.log file you'll get, for a deeper analysis.

Nicolas


Le samedi 30 janvier 2010 ? 03:17 -0500, Michael DeBusk a ?crit :
> I bought a Canon ImageCLASS MF4350d yesterday after learning that the
> manufacturer has a Linux driver for it. I didn't realize it was only a
> PRINTER driver, and that they ignored the scanner.
> 
> On my installation of Ubuntu 8.04:
> 
> "xsane" returns "no devices available."
> 
> "sane-find-scanner" returns:
> found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26ee
> [MF4320-4350]) at libusb:005:004
> 
> "scanimage -L" returns:
> No scanners were identified.
> 
> "scanimage --version" returns:
> scanimage (sane-backends) 1.0.19; backend version 1.0.19
> 
> A check of sane-backends-1.0.20 shows no support for my scanner. It
> appears that sane-backends-1.0.21cvs supports the MF4380dn and the
> MF4370dn, both of which share a manual with my MF4350d. Is it possible
> that the development version supports my scanner without "realizing" it?
> 
> Is there something I can do to assist the developers in adding support
> for my scanner? I'm not a programmer, but I follow directions well.
> 
> Thank you.
> 

[sane-devel] cropping added to pixma_mp150 backend

[Nicolas Martin]

I've just tried the files you sent with an MP610 and Xsane, but at the
moment, I could not scan completely, scanning hangs during data
transfer. 
Don't know yet why this happens, I noticed you used some older pixma
backend files, so would it be possible that you add these changes to the
current git version files instead ? 

In the meantime, I'll try to understand where this issue happens. 
That's a big challenge to keep a backward compatibility with all models
supported in the pixma backend: the file pixma_mp150.c now supports 46
different Pixma models (all using almost the same protocol), that have
been issued by Canon since several years. 

Nicolas

Le dimanche 10 janvier 2010 ? 18:17 +0100, Dr. Christian Scholz a
?crit :
> I have added a few lines to the pixma mp150 backend that crop the scan 
> lines in order to match exactly the selected scan area. pixma_mp150.c 
> and pixma.h are modified and contained in the attached tgz archive. 
> Cropping is switched on by defining the variable MYCROP in pixma.h. 
> Sorry for communicating that enhancement using this mail, I am not 
> familiar with the standard method.
> 
> By the way: I am achieving good scan results with my Canon MX860 if 
> setting gamma to 2.0.
> 
> Enhancements of pixma_mp150 I am interested in:
> - color management respectively color correction in backend
> - more configuration options, e.g. for initial gamma and for providing 
> the path to the scanner icc profile,
> - 48bit color depth
> 
> Best wishes for 2010
> 
> Christian Scholz
> --
> 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

[sane-devel] Scan from command-line

[Nicolas Martin]

man convert
man ImageMagick

http://www.google.com/search?q=linux+convert+image+format

man mail

echo . | mail -s "Document1" -a   

With this little stuff, you should be able to build your own script.

Nicolas

Le dimanche 10 janvier 2010 ? 12:07 +0100, Josu Lazkano a ?crit :
> Hello, I solve it. I use those two command and it works:
> 
> scanimage --mode Color > Desktop/document.pnm
> scanimage --mode Color --format=tiff > Desktop/document.tiff
> 
> The problem is that both images are huge, 11.4MB. Is possible to
> convert to JPEG this the scanner utility?
> 
> Thanks for all.
> 
> 2010/1/9 Josu Lazkano 
> Hello, I just installed Sane and configure my scanner. I want
> make a script that works this way:
> 
> ./scan Document1
> 
> This will send a mail to an specific sender with the subject
> Document1 with an image scanned.
> 
> How can I scan a document from the comman-line? I need to
> configure scanner options?
> 
> I am new on this, I jut used the x-window program.
> 
> Thanks for all and best regards..
> 
> -- 
> Josu Lazkano
> 
> 
> 
> -- 
> Josu Lazkano
> --
> 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

[sane-devel] Problem with Canon MP270

[Nicolas Martin]

Could you try first the same commands under root, so that we can check
whether this is a perms issue or not:

$ sudo -i
# scanimage -T

Nicolas

Le samedi 09 janvier 2010 ? 11:08 +0100, Christian Kolhaupt a ?crit :
> Hello,
> 
> im trying to get the canon mp270 running. Printing works without
> problem, but SANE doesn't detect my scanner.
> 
> I've installed GIT und the newest Version of SANE. 
> 
> In lib/udev/rules.d, lib32/udes/rules.d, lib64/udev/rules.d ist a file
> 40-libsane.rules and it contains the line
> 
> # Canon PIXMA MP270
> ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="173b", MODE="0664",
> GROUP="scanner", ENV{libsane_matched}="yes"
> 
> Can anyone help me? Perhaps a Problem with the amd64-Version?
> 
> thx a lot
> ---
> System: Ubuntu 9.10 amd64 
> 
> $ scanimage -V
> scanimage (sane-backends) 1.0.21cvs; backend version 1.0.21
> 
> $ scanimage -T
> scanimage: no SANE devices found
> 
> $ scanimage -L
> No scanners were identified. If you were expecting something
> different,
> check that the scanner is plugged in, turned on and detected by the
> sane-find-scanner tool (if appropriate). Please read the documentation
> which came with this software (README, FAQ, manpages).
> 
> $ lsusb
> Bus 001 Device 004: ID 04a9:173b Canon, Inc. 
> 
> --
> 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

[sane-devel] Canon PIXMA MX330 working, with -x auto and -y auto bug; data here

[Nicolas Martin]

Le mercredi 09 d?cembre 2009 ? 16:05 -0800, qm at sonic.net a ?crit :
> > So let me know if I understand clearly:
> >
> > - MX330 works with the pixma backend. It was not yet declared in Sane
> > 1.0.20, but is declared in Sane git for a while now, with the proper usb
> > pid. If you install Sane git, MX330 should work out of the box.
> > No issue for MX330 on that side, I'll update the docs and supported
> > devices list for MX330.
> 
> I wondered about that.  I didn't see git.  Sorry, and yes, that is good.
Thx
> 
> > - There's an error with scanimage/pixma backend when setting explicitly
> > -x or -y options to "auto". This is the same for all pixma devices, so
> > probably something the pixma backend rejects for now, and that needs to
> > be checked.
> 
> Yes, but as has been discussed already by now, we're not sure if those
> features are actually supported, and some seem to be sure they are not. 
> The confusion comes in because the Microsoft XP MX330-packaged scanning
> software does do autodetect of a sort (when you specify "picture", it
> takes all picture-looking things and makes a seperate cropped file for
> each, and does a pretty darn good job of it without cutting too much or
> too little), so presumably that's software driven by the program in the
> computer, not in the scanner/multifunction device.
Yep, that's probably performed by the Canon software, roughly equivalent
to a Sane frontend.
Remember that you can use Gimp with Sane, scan from Gimp, then use
Gimp's powerful tools to process your images as desired.
> 
> >
> > Is there any other point I would have missed ?
> 
> No, apparently the documentation was more outdated than git, so we're good
> once that's done.  If I had known this existed back in the summer, I would
> have had many more months of not having to run VMWARE with XP in it,
> crashing my computer so much ...
Doc in 1.0.20 was reflecting the pixma backend state at that time. Each
time a new device is added, documentation is (normally) updated
accordingly. 
Good idea, I'll add a few words in the pixma man page, so as to invite
people to install the git version in case of trouble with a new model.

Nicolas

[sane-devel] Canon PIXMA MX330 working, with -x auto and -y auto bug; data here

[Nicolas Martin]

Pixma devices do not autodetect paper size width, so I guess the best
way to use the -x option as auto is to omit it. In this case, the max
value for page width will be used. 

Nicolas

Le mardi 08 d?cembre 2009 ? 15:43 -0500, m. allan noah a ?crit :
> In fact, the auto paper length detection of the epjitsu backend uses
> 0, though the fujitsu backend uses a separate --ald option. your
> choice.
> 
> allan
> 
> On Sun, Dec 6, 2009 at 12:57 PM, m. allan noah  wrote:
> > standard says:
> >
> > Backends must attach a unit of either pixels (SANE_UNIT_PIXEL) or
> > millimeters (SANE_UNIT_MM) to these options. The unit of all four
> > options must be identical.
> >
> > I dont think 'auto' qualifies as either of those units. Try stating
> > that 0 or -1 is auto.
> >
> > allan
> >
> > On Sun, Dec 6, 2009 at 8:45 AM, Nicolas Martin  > gmail.com> wrote:
> >> Le dimanche 06 d?cembre 2009 ? 10:50 +0100, Nicolas Martin a ?crit :
> >>> - There's an error with scanimage/pixma backend when setting explicitly
> >>> -x or -y options to "auto". This is the same for all pixma devices, so
> >>> probably something the pixma backend rejects for now, and that needs to
> >>> be checked.
> >>
> >> Just tried  with another scanner (Canon N656U handled by the plustek
> >> backend) and got the same message when setting scanimage -x option to
> >> "auto"
> >>
> >> Looking more deeply at scanimage.c source code, I notice this:
> >>
> >> In main():
> >>
> >> ...
> >>case 'x':
> >>  window_val_user[0] = 1;
> >>  parse_vector (&window_option[0], optarg, &window_val[0], 1);
> >>  break;
> >>
> >>case 'y':
> >>  window_val_user[1] = 1;
> >>  parse_vector (&window_option[1], optarg, &window_val[1], 1);
> >>  break;
> >>
> >>case 'l':   /* tl-x */
> >>  process_backend_option (device, window[2], optarg);
> >>  break;
> >> ...
> >>
> >> So here, (x, y) and (l, t) do not use obviously the same functions to be
> >> processed.
> >>
> >> Then, looking in parse_vector():
> >>
> >> ...
> >>  /* read value */
> >>  str = parse_scalar (opt, str, &value);
> >> ...
> >>
> >> and finally in parse_scalar():
> >>
> >> v = strtol (str, &end, 10);
> >>
> >> if (str == end)
> >>  {
> >>fprintf (stderr,
> >>   "%s: option --%s: bad option value (rest of option: %s)\n",
> >>   prog_name, opt->name, str);
> >>exit (1);
> >>  }
> >>
> >>
> >> So if -x value is "auto", the strtol will fail, and trig the error
> >> message:  scanimage: option --x: bad option value (rest of option: auto)
> >>
> >> More evidence of that if I enter the scanimage command like this:
> >>
> >> $ scanimage --format pnm -x foo  > output.pnm
> >> scanimage: option --x: bad option value (rest of option: foo)
> >>
> >> In conclusion: the -x auto limitation seems to be due to scanimage.
> >>
> >> => And now the questions, before changing anything:
> >>
> >> - Is there any reason for that, should the -x auto and -y auto options
> >> be valid ?
> >> - Does this need to be fixed, or is it working as designed ?
> >> - Should we process (x, y) values as (l, t) are processed ?
> >>
> >> All suggestions welcome.
> >>
> >> Nicolas
> >>
> >>
> >>
> >> --
> >> 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
> >>
> >
> >
> >
> > --
> > "The truth is an offense, but not a sin"
> >
> 
> 
> 

[sane-devel] Canon PIXMA MX330 working, with -x auto and -y auto bug; data here

[Nicolas Martin]

Le dimanche 06 d?cembre 2009 ? 10:50 +0100, Nicolas Martin a ?crit :
> - There's an error with scanimage/pixma backend when setting explicitly
> -x or -y options to "auto". This is the same for all pixma devices, so
> probably something the pixma backend rejects for now, and that needs to
> be checked.

Just tried  with another scanner (Canon N656U handled by the plustek
backend) and got the same message when setting scanimage -x option to
"auto"

Looking more deeply at scanimage.c source code, I notice this:

In main():

...
case 'x':
  window_val_user[0] = 1;
  parse_vector (&window_option[0], optarg, &window_val[0], 1);
  break;

case 'y':
  window_val_user[1] = 1;
  parse_vector (&window_option[1], optarg, &window_val[1], 1);
  break;

case 'l':   /* tl-x */
  process_backend_option (device, window[2], optarg);
  break;
...

So here, (x, y) and (l, t) do not use obviously the same functions to be
processed.

Then, looking in parse_vector():

...
  /* read value */
  str = parse_scalar (opt, str, &value);
...

and finally in parse_scalar():

v = strtol (str, &end, 10);

if (str == end)
  {
fprintf (stderr,
   "%s: option --%s: bad option value (rest of option: %s)\n",
   prog_name, opt->name, str);
exit (1);
  }


So if -x value is "auto", the strtol will fail, and trig the error
message:  scanimage: option --x: bad option value (rest of option: auto)

More evidence of that if I enter the scanimage command like this:

$ scanimage --format pnm -x foo  > output.pnm
scanimage: option --x: bad option value (rest of option: foo)

In conclusion: the -x auto limitation seems to be due to scanimage. 

=> And now the questions, before changing anything: 

- Is there any reason for that, should the -x auto and -y auto options
be valid ?
- Does this need to be fixed, or is it working as designed ?
- Should we process (x, y) values as (l, t) are processed ?

All suggestions welcome.

Nicolas

[sane-devel] Canon PIXMA MX330 working, with -x auto and -y auto bug; data here

[Nicolas Martin]

So let me know if I understand clearly:

- MX330 works with the pixma backend. It was not yet declared in Sane
1.0.20, but is declared in Sane git for a while now, with the proper usb
pid. If you install Sane git, MX330 should work out of the box.
No issue for MX330 on that side, I'll update the docs and supported
devices list for MX330.

- There's an error with scanimage/pixma backend when setting explicitly
-x or -y options to "auto". This is the same for all pixma devices, so
probably something the pixma backend rejects for now, and that needs to
be checked.

Is there any other point I would have missed ?

Nicolas