[sane-devel] Canon MF4140
Dennis Lou
dlou99 at yahoo.com
Sun Aug 31 02:15:50 UTC 2008
Nicolas,
I told Bob to move the USB PID macro and device entry from pixma_imageclass.c to pixma_mp730.c and see if that works.
He did that but then he wasn't able to see the scanner any more. Any ideas?
-Dennis
----- Original Message ----
From: Bob Dronski <dronski at gmail.com>
To: Dennis Lou <dlou99 at yahoo.com>
Cc: sane-devel at lists.alioth.debian.org
Sent: Saturday, August 30, 2008 8:49:24 AM
Subject: Re: [sane-devel] Canon MF4140
So much for the lark....
scanimage -L no longer finds the scanner after the patch. Now I am working off of a newer build than you are (7-20-CVS), but I only changed the 2 files by hand, and when changing back, it was once again able to find the device.
bob
On Aug 25, 2008, at 12:18 AM, Dennis Lou wrote:
Just on a lark, can you try commenting out the MF4100 PID and device entry from pixma_imageclass.c and add it to pixma_mp730.c? Here's the patch:
Index: pixma_imageclass.c
===================================================================
RCS file: /cvsroot/sane/sane-backends/backend/pixma_imageclass.c,v
retrieving revision 1.4
diff -u -r1.4 pixma_imageclass.c
--- pixma_imageclass.c 25 Jun 2008 20:54:16 -0000 1.4
+++ pixma_imageclass.c 25 Aug 2008 05:17:37 -0000
@@ -78,7 +78,7 @@
#define MF3110_PID 0x2660
#define MF3200_PID 0x2684
#define MF6500_PID 0x2686
-#define MF4100_PID 0x26a3
+//#define MF4100_PID 0x26a3
#define MF4600_PID 0x26b0
#define MF4010_PID 0x26b4
@@ -612,7 +612,7 @@
DEV ("Canon imageCLASS MF3110", MF3110_PID, 600, 640, 877, PIXMA_CAP_ADF),
DEV ("Canon imageCLASS MF3240", MF3200_PID, 600, 640, 877, PIXMA_CAP_ADF),
DEV ("Canon MF6500 Series", MF6500_PID, 600, 640, 877, PIXMA_CAP_ADF),
- DEV ("Canon imageCLASS MF4150", MF4100_PID, 600, 640, 877, PIXMA_CAP_ADF),
+// DEV ("Canon imageCLASS MF4150", MF4100_PID, 600, 640, 877, PIXMA_CAP_ADF),
DEV ("Canon imageCLASS MF4690", MF4600_PID, 600, 640, 877, PIXMA_CAP_ADF),
DEV ("Canon imageCLASS MF4010", MF4010_PID, 600, 640, 877, PIXMA_CAP_ADF),
DEV (NULL, 0, 0, 0, 0, 0)
Index: pixma_mp730.c
===================================================================
RCS file: /cvsroot/sane/sane-backends/backend/pixma_mp730.c,v
retrieving revision 1.7
diff -u -r1.7 pixma_mp730.c
--- pixma_mp730.c 22 Feb 2008 21:40:32 -0000 1.7
+++ pixma_mp730.c 25 Aug 2008 05:17:37 -0000
@@ -69,6 +69,7 @@
#define MP740_PID 0x264c /* Untested */
#define MP710_PID 0x264d
#define MP730_PID 0x262f
+#define MF4100_PID 0x26a3
enum mp730_state_t
{
@@ -638,5 +639,6 @@
DEVICE ("Canon MultiPASS MP710", MP710_PID, 1200, 637, 868, 0),
DEVICE ("Canon MultiPASS MP730", MP730_PID, 1200, 637, 868, PIXMA_CAP_ADF),
DEVICE ("Canon MultiPASS MP740", MP740_PID, 1200, 637, 868, PIXMA_CAP_ADF),
+ DEVICE ("Bob's MF4150", MF4100_PID, 600, 640, 877, PIXMA_CAP_ADF),
DEVICE (NULL, 0, 0, 0, 0, 0)
};
----- Original Message ----
From: Bob Dronski <dronski at gmail.com>
To: Dennis Lou <dlou99 at yahoo.com>
Sent: Saturday, August 23, 2008 1:20:22 PM
Subject: Re: [sane-devel] Canon MF4140
Got a couple more. 150dpi color from the bottom of the scan and 300 dpi b/w along the left edge.
This enough to get you started?
bob
On Sat, Aug 23, 2008 at 3:07 PM, Bob Dronski <dronski at gmail.com> wrote:
Dennis,
Parallels, the scanner, and USB sniffer are a bit temperamental together. I've been playing, and I have one greyscale log so far. If the log got too big, I apologize. LIke I said, it was really tricky. I'll continue to play to get some more stuff out for you
bob
On Sat, Aug 23, 2008 at 2:34 PM, Dennis Lou <dlou99 at yahoo.com> wrote:
For the first one, empty is fine. Later, might want to try different colors of paper. But I'm guessing that the protocol will be similar enough to another existing supported scanner that it probably might not be necessary.
-Dennis
----- Original Message ----
From: Bob Dronski <dronski at gmail.com>
To: Dennis Lou <dlou99 at yahoo.com>
Sent: Saturday, August 23, 2008 7:09:55 AM
Subject: Re: [sane-devel] Canon MF4140
dumb quick question--I'll try to look it up, but I figured I'd check with you as well. Is it better to scan an empty flatbed or put a doc on it? I don't know what data would be easier to work with (or if it makes a difference)
Otherwise, I'm hooked up to parallels and am functioning. I'll start w/ an empty bed and go from there.
bob
On Fri, Aug 22, 2008 at 1:16 PM, Dennis Lou <dlou99 at yahoo.com> wrote:
Well, I'm very confident somebody can do something with the logs and get it working. Whether that person is me depends (that was my first time doing a scanner). But even if that person is not me, the SANE guys are pretty smart from what I've seen and consumer-grade scanners seem pretty well understood at this point.
Especially if the protocol isn't much more complicated than the MF4270, then I'm pretty sure I can get something going.
BTW, where are you located? I'm in the Silicon Valley.
-Dennis
----- Original Message ----
From: Bob Dronski <dronski at gmail.com>
To: Dennis Lou <dlou99 at yahoo.com>
Sent: Friday, August 22, 2008 10:40:15 AM
Subject: Re: [sane-devel] Canon MF4140
Dennis,
I've got a crazy day or two ahead of me. I'm going to really try to get you something tonight or tomorrow.
Do you think the odds will be good to get the driver working if I get you the data (and I presume a few more dumps)?
Just trying to prioritize my time. If you're not sure, I need to get it to you ASAP, as I only have through thursday to return easily. If you're pretty confident, I'll believe in you and not worry about the date.
take care,
bob
On Aug 22, 2008, at 12:15 AM, Dennis Lou wrote:
Great, thanks!
1. Unplug the device
2. Install the Canon drivers
3. Install a USB sniffer. I used SniffUSB v1.7 because my VM is Win2k. You can certainly do better if you are running a more recent version of Windows.
4. Plug in the device and direct it to the virtual machine (select the device from the "Device" menu in VMWare)
5. Start the USB sniffer (on mine, there are four possible devices/subdevices; I select "Canon MF4200 Series" and click the "Install" button)
6. If you are using XP or Win2k, click Start->Programs->Accessories->WindowsImaging then File->Acquire
7. Pick 75 DPI, grayscale and select a small area to scan, preferably full width and minimal height then hit "Scan".
8. Save the log file. In SniffUSB 1.7, this means clicking the "Uninstall" button, copying the log file somewhere else, then clicking the "Delete" button.
9. Repeat steps 5-8 (possibly step 4 if your setup is as finicky as mine) using different color and dpi settings and different areas.
10. Send me and/or the SANE list the log file(s).
Thanks again for your help.
-Dennis
----- Original Message ----
From: Bob Dronski <dronski at gmail.com>
To: Dennis Lou <dlou99 at yahoo.com>
Sent: Thursday, August 21, 2008 2:47:26 PM
Subject: Re: [sane-devel] Canon MF4140
Dennis,
May have missed the message. Sorry.
Yes, I have a MacBookPro running parallels I can use to sniff for you. As I haven't done this before, please tell me what to do.
Thanks,
bob
On Thu, Aug 21, 2008 at 4:32 PM, Dennis Lou <dlou99 at yahoo.com> wrote:
Hi Bob,
I sent you a private email regarding this but apparently you didn't get it.
I wrote the Imageclass section and Allan is correct. Your all-in-one shares the same Windows front-end stuff from Canon as mine. But beyond that, I have no idea whether the base USB communications protocol is the same or not. What's really needed are USB snoop logs, preferably from a Windows scan. Can you run Parallels or Bootcamp into Win2k or higher?
-Dennis
--
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/20080830/8fa08599/attachment.htm
More information about the sane-devel
mailing list