[sane-devel] Canon imageCLASS MF4370dn

[Nicolas Martin]

Commit is already done for MF4370/MF4380 (both have same pid) so you can
give a try with the latest git. 
Try first with usb to check if the scanner works, then with network, and
let us know.

nicolas


________________________________________________________________________
> From: Nicolas Martin <nicolas0martin at gmail.com>
> To: Adrian Sandor <aditsu at yahoo.com>
> Cc: sane-devel <sane-devel at lists.alioth.debian.org>
> Sent: Sun, October 18, 2009 7:36:13 PM
> Subject: Re: [sane-devel] Canon imageCLASS MF4370dn
> 
> Le samedi 17 octobre 2009 à 19:22 -0700, Adrian Sandor a écrit :
> > Oh, in order to be able to use it on the network, I should connect
> it
> > to USB first? That's funny.
> That's not what is meant when asking for the usb pid. 
> 
> We ask you the usb pid because both usb and network part of the pixma
> backend use the usb pid to identify the scanner model (pixma backend
> supports more than 50 different models), then the Pixma protocol,
> initially designed for usb, can be used "off the shelf", as Louis
> Lagendijk implemented it, encapsulated into the bjnp (Canon) network
> protocol.
> 
> So not a funny thing here, but rather ingenious and efficient, as a
> Pixma scanner supported for usb can be used directly with network
> bjnp,
> no additional or specific code needed.
> 
> Concerning the ImageClass MF4370dn device, it looks like it shares the
> same usb pid as MF4380dn, for which I've just committed the
> declaration
> in the pixma backend, following some exchanges with Raimondo who
> initiated a thread about this some days ago. MF4380dn is supported
> (confirmed for usb), and there's great chance that MF4370dn will be
> supported too with the same code. 
> 
> Louis: 
> if the network support fails, I'm just wondering whether the DES name
> for this model is set correctly, the usb signature (from the USB
> snoop)
> was reported to be: "Canon  MF4360-4390" so a bit different from what
> was seen before. Is the DES name detected displayed in the backend
> logs
> to check for that ?
> 
> Nicolas
> 
> 
> > Well, here's some information from lsusb:
> > 
> > Bus 002 Device 006: ID 04a9:26ec Canon, Inc.
> > Device Descriptor:
> >  bLength                18
> >  bDescriptorType        1
> >  bcdUSB              2.00
> >  bDeviceClass            0 (Defined at Interface level)
> >  bDeviceSubClass        0
> >  bDeviceProtocol        0
> >  bMaxPacketSize0        64
> >  idVendor          0x04a9 Canon, Inc.
> >  idProduct          0x26ec
> >  bcdDevice            1.00
> >  iManufacturer          1 Canon Inc.
> >  iProduct                2 MF4360-4390
> >  iSerial                3 SJF980221406D
> >  bNumConfigurations      1
> > 
> > Let me know if you need more details.
> > 
> > Thanks
> > Adrian
> > 
> > 
> > 
> >
> ______________________________________________________________________
> > From: Nicolas Martin <nicolas0martin at gmail.com>
> > To: Adrian Sandor <aditsu at yahoo.com>
> > Cc: sane-devel at lists.alioth.debian.org
> > Sent: Sun, October 18, 2009 3:45:16 AM
> > Subject: Re: [sane-devel] Canon imageCLASS MF4370dn
> > 
> > This model is not supported bu Sane 1.0.20, but currently working on
> > adding the ImageClass MF4380dn to the pixma backend, and should be
> > available soon in Sane git. 
> > 
> > In the meantime, could you supply the usb vid:pid of this model ? 
> > You can read it with a 
> > 
> > $ /usr/sbin/lsusb
> > 
> > nicolas
> > 
> > Le samedi 17 octobre 2009 à 10:58 -0700, Adrian Sandor a écrit :
> > > Hi, I've just bought <subject>, how can I set it up for scanning
> > over
> > > the network?
> > > I'm using sane-backends 1.0.20, and I added bjnp://192.168.1.11 in
> > > pixma.conf (that's the ip address of the device), but scanimage -L
> > > says:
> > > [pixma] udp_command: no data received (recv): Connection
> > > refused[pixma] udp_command: no data received (recv): Connection
> > > refused[pixma] udp_command: no data received (recv): Connection
> > > refused[pixma] Cannot read scanner make & model:
> > > Also, if I run scanimage as root, it dies with a segmentation
> fault.
> > > 
> > > Thanks
> > > Adrian
> > > 
> > > 
> > > --
> > > 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 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