|
Canon MF4140
Canon MF4140 (Laserprinter/Scanner/Fax)
"found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3 [MF4100]) at libusb:002:002" but scanimage -L fails
Found on the net: http://ubuntuforums.org/showthread.php?t=878966 - by adding "SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="26a3", MODE="0664", GROUP="scanner" to libsane.rules the thing should run: "device `pixma:04A926A3_SDF680281822B' is a CANON Canon imageCLASS MF4150 multi-function peripheral"
but it doesn't (backends 1.0.19). Any ideas (hacks, workarounds, modifying pixma backend?)
Greetings, Daniel Stender
--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
You must verify that udev is running, do "ps -A | grep udev" in a
console. It must give something like : 1049 ? 00:00:00 udevd
Then you can verify that the user who try to use the scanner belong to
the scanner group. Do "grep scanner /etc/* " in a console, it must give
something like : /etc/group:scanner::93:root,users
Daniel Stender a écrit :
> Canon MF4140 (Laserprinter/Scanner/Fax)
>
> "found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3 [MF4100]) at libusb:002:002" but scanimage -L fails
>
> Found on the net: http://ubuntuforums.org/showthread.php?t=878966 - by adding "SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="26a3", MODE="0664", GROUP="scanner" to libsane.rules the thing should run: "device `pixma:04A926A3_SDF680281822B' is a CANON Canon imageCLASS MF4150 multi-function peripheral"
>
> but it doesn't (backends 1.0.19). Any ideas (hacks, workarounds, modifying pixma backend?)
>
> Greetings, Daniel Stender
>
>
>
--
Jean-Nicolas Gautier
28, rue Pelletier
1030 Schaerbeek
Tél.: 02/ 742 09 92
GSM : 0494/ 84 14 59
Please, consider your environmental responsibility before printing this email.
--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
First of all, thanks to the both of you for replying. I really want
to keep this unit, and I was worried when I heard nothing for a few
days.
Well, I did find a copy of libsane.rules in my build and it DID have
the listing Daniel mentioned. I manually moved the file into the
empty udev folder. But udev doesn't seem to be running
12947 ttys001 0:00.00 grep udev
Where would I find it? Did I have to do something special in the build?
Thanks,
bob
On Aug 20, 2008, at 9:56 AM, Jean-Nicolas Gautier wrote:
> You must verify that udev is running, do "ps -A | grep udev" in a
> console. It must give something like : 1049 ? 00:00:00 udevd
> Then you can verify that the user who try to use the scanner belong to
> the scanner group. Do "grep scanner /etc/* " in a console, it must
> give
> something like : /etc/group:scanner::93:root,users
>
>
> Daniel Stender a écrit :
>> Canon MF4140 (Laserprinter/Scanner/Fax)
>>
>> "found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3
>> [MF4100]) at libusb:002:002" but scanimage -L fails
>>
>> Found on the net: http://ubuntuforums.org/showthread.php?t=878966 -
>> by adding "SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="26a3",
>> MODE="0664", GROUP="scanner" to libsane.rules the thing should run:
>> "device `pixma:04A926A3_SDF680281822B' is a CANON Canon imageCLASS
>> MF4150 multi-function peripheral"
>>
>> but it doesn't (backends 1.0.19). Any ideas (hacks, workarounds,
>> modifying pixma backend?)
>>
>> Greetings, Daniel Stender
>>
>>
>>
>
> --
> Jean-Nicolas Gautier
> 28, rue Pelletier
> 1030 Schaerbeek
>
> Tél.: 02/ 742 09 92
> GSM : 0494/ 84 14 59
>
> Please, consider your environmental responsibility before printing
> this email.
>
>
> --
> sane-devel mailing list: sane-devel@...
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request@...
--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
 Re: Canon MF4140
Jean-Nicolas,
There seems to be a lot of confusion.
Daniel seems to also have the same unit but must be having separate
problems from me. He is NOT answering for me.
Let me repeat my situation.
I am running on Mac 10.5. I have used both Mattias Ellert's pre-built
binaries for mac, as well as building the sane package myself.
This is from sane-find-scanner.
found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3
[MF4100]) at libusb:003:004-04a9-26a3-00-00
And scanimage -L reports
device `pixma:04A926A3_SDF7Z0155773B' is a CANON Canon imageCLASS
MF4150 multi-function peripheral
When I attempt to execute scanimage -T, it tries to read the first
scanline and freezes.
Now udev is definitely NOT running on my machine. the GREP output is
misleading, because it shows my GREP process looking for the term
udev. If I export the output of ps -A to a file, udev does not exist.
But as I said, there IS a /usr/local/etc/udev/rules.d/libsane.rules
that exists and it has the proper listing for the 4150. I had to
manually move the .rules file as it was created in my build but didn't
transfer to /usr/local/etc/udev/rules.d/ that did already exist.
So my question is, When/how does udev get created? Should it be
created by the build? Might I have used the wrong parameters in the
configure command?
I used ./configure --prefix=/usr/local --sysconfdir=/usr/local/etc
Does this make things clearer?
bob
On Aug 21, 2008, at 1:42 AM, Jean-Nicolas Gautier wrote:
> Hello,
> I don't understand, do you have line called udevd when you type ps -
> A in a concole?
> What is your distribution (ubuntu, suse,mandriva, ...)?
> Personally (a slackware distribution) I have a file called "rc.udev"
> in folder /etc/rc.d ; this file must be executable in order to start
> udev at boot.
> Do you have this file somewhere in /etc/* ? You can check if the
> file is executable by doing ls -l /path/to/your/file . It must give
> something like :
> -rwxr-xr-x 1 root root 3920 2008-05-07 14:50 /etc/rc.d/rc.udev*
>
>
> Bob Dronski a écrit :
>> First of all, thanks to the both of you for replying. I really
>> want to keep this unit, and I was worried when I heard nothing for
>> a few days.
>>
>> Well, I did find a copy of libsane.rules in my build and it DID
>> have the listing Daniel mentioned. I manually moved the file into
>> the empty udev folder. But udev doesn't seem to be running
>>
>> 12947 ttys001 0:00.00 grep udev
>>
>> Where would I find it? Did I have to do something special in the
>> build?
>>
>> Thanks,
>> bob
>>
>>
>> On Aug 20, 2008, at 9:56 AM, Jean-Nicolas Gautier wrote:
>>
>>
>>> You must verify that udev is running, do "ps -A | grep udev" in a
>>> console. It must give something like : 1049 ? 00:00:00 udevd
>>> Then you can verify that the user who try to use the scanner
>>> belong to
>>> the scanner group. Do "grep scanner /etc/* " in a console, it
>>> must give
>>> something like : /etc/group:scanner::93:root,users
>>>
>>>
>>> Daniel Stender a écrit :
>>>
>>>> Canon MF4140 (Laserprinter/Scanner/Fax)
>>>>
>>>> "found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3
>>>> [MF4100]) at libusb:002:002" but scanimage -L fails
>>>>
>>>> Found on the net: http://ubuntuforums.org/showthread.php?t=878966
>>>> - by adding "SYSFS{idVendor}=="04a9", SYSFS{idProduct}=="26a3",
>>>> MODE="0664", GROUP="scanner" to libsane.rules the thing should
>>>> run: "device `pixma:04A926A3_SDF680281822B' is a CANON Canon
>>>> imageCLASS MF4150 multi-function peripheral"
>>>>
>>>> but it doesn't (backends 1.0.19). Any ideas (hacks, workarounds,
>>>> modifying pixma backend?)
>>>>
>>>> Greetings, Daniel Stender
>>>>
>>>>
>>>>
>>>>
>>> --
>>> Jean-Nicolas Gautier
>>> 28, rue Pelletier
>>> 1030 Schaerbeek
>>>
>>> Tél.: 02/ 742 09 92
>>> GSM : 0494/ 84 14 59
>>>
>>> Please, consider your environmental responsibility before
>>> printing this email.
>>>
>>>
>>> --
>>> sane-devel mailing list: sane-devel@...
>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel>>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>> to sane-devel-request@...
>>>
>>
>>
>>
>>
>
> --
> Jean-Nicolas Gautier
> 28, rue Pelletier
> 1030 Schaerbeek
>
> Tél.: 02/ 742 09 92
> GSM : 0494/ 84 14 59
>
> Please, consider your environmental responsibility before printing
> this email.
>
--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
On Thu, Aug 21, 2008 at 10:41 AM, Bob Dronski < dronski@...> wrote:
> Jean-Nicolas,
>
> There seems to be a lot of confusion.
>
> Daniel seems to also have the same unit but must be having separate
> problems from me. He is NOT answering for me.
>
> Let me repeat my situation.
> I am running on Mac 10.5. I have used both Mattias Ellert's pre-built
> binaries for mac, as well as building the sane package myself.
>
> This is from sane-find-scanner.
> found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3
> [MF4100]) at libusb:003:004-04a9-26a3-00-00
>
> And scanimage -L reports
> device `pixma:04A926A3_SDF7Z0155773B' is a CANON Canon imageCLASS
> MF4150 multi-function peripheral
>
> When I attempt to execute scanimage -T, it tries to read the first
> scanline and freezes.
>
> Now udev is definitely NOT running on my machine. the GREP output is
> misleading, because it shows my GREP process looking for the term
> udev. If I export the output of ps -A to a file, udev does not exist.
>
> But as I said, there IS a /usr/local/etc/udev/rules.d/libsane.rules
> that exists and it has the proper listing for the 4150. I had to
> manually move the .rules file as it was created in my build but didn't
> transfer to /usr/local/etc/udev/rules.d/ that did already exist.
>
> So my question is, When/how does udev get created? Should it be
> created by the build? Might I have used the wrong parameters in the
> configure command?
> I used ./configure --prefix=/usr/local --sysconfdir=/usr/local/etc
udev is a linux-only device manager thing. it is only used by sane to
set permissions on devices so that non-root users can scan. therefore,
all users that have difficulty scanning should try as root user first.
if root cannot scan, permissions (and hence, udev) are likely NOT the
problem.
i see no evidence that this backend supports this scanner, other than
similarity of name to other, supported models. It might require only a
minor tweak to a config file, or it might take a completely new
backend, depending on how similar it is to existing models.
allan
--
"The truth is an offense, but not a sin"
--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
Allan,
Thanks for clearing up the udev confusion. I guess that's why I had a
problem finding info on it.
I do understand that my model may not be supported. But according to
the pixma help page
---------------
The following models may use the same Pixma protocol as those listed
above, but have not yet been reported to work (or not). They are
declared in the backend so that they get recognized and activated.
Feedback in the Sane-dev mailing list welcome.
PIXMA MP740
ImageCLASS MF3110, MF3240, MF4150
ImageCLASS MF5630, MF5650, MF5730, MF5750, MF5770, MF8170c
--------------
So I was attempting to follow the recommendations. Hopefully Nicolas
might be able to tell me if it's worth pursuing upon his return. I
have until next Thursday to return the unit.
bob
On Aug 21, 2008, at 9:51 AM, m. allan noah wrote:
> On Thu, Aug 21, 2008 at 10:41 AM, Bob Dronski < dronski@...>
> wrote:
>> Jean-Nicolas,
>>
>> There seems to be a lot of confusion.
>>
>> Daniel seems to also have the same unit but must be having separate
>> problems from me. He is NOT answering for me.
>>
>> Let me repeat my situation.
>> I am running on Mac 10.5. I have used both Mattias Ellert's pre-
>> built
>> binaries for mac, as well as building the sane package myself.
>>
>> This is from sane-find-scanner.
>> found USB scanner (vendor=0x04a9 [Canon Inc.], product=0x26a3
>> [MF4100]) at libusb:003:004-04a9-26a3-00-00
>>
>> And scanimage -L reports
>> device `pixma:04A926A3_SDF7Z0155773B' is a CANON Canon
>> imageCLASS
>> MF4150 multi-function peripheral
>>
>> When I attempt to execute scanimage -T, it tries to read the first
>> scanline and freezes.
>>
>> Now udev is definitely NOT running on my machine. the GREP output is
>> misleading, because it shows my GREP process looking for the term
>> udev. If I export the output of ps -A to a file, udev does not
>> exist.
>>
>> But as I said, there IS a /usr/local/etc/udev/rules.d/libsane.rules
>> that exists and it has the proper listing for the 4150. I had to
>> manually move the .rules file as it was created in my build but
>> didn't
>> transfer to /usr/local/etc/udev/rules.d/ that did already exist.
>>
>> So my question is, When/how does udev get created? Should it be
>> created by the build? Might I have used the wrong parameters in the
>> configure command?
>> I used ./configure --prefix=/usr/local --sysconfdir=/usr/local/etc
>
> udev is a linux-only device manager thing. it is only used by sane to
> set permissions on devices so that non-root users can scan. therefore,
> all users that have difficulty scanning should try as root user first.
> if root cannot scan, permissions (and hence, udev) are likely NOT the
> problem.
>
> i see no evidence that this backend supports this scanner, other than
> similarity of name to other, supported models. It might require only a
> minor tweak to a config file, or it might take a completely new
> backend, depending on how similar it is to existing models.
>
> allan
> --
> "The truth is an offense, but not a sin"
--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
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@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
Thanks. The first log was probably sufficient, but the ensuing ones will probably make good supporting data should it be needed.
I took a look and indeed it is similar to existing code. As a matter of fact, I'm still deciding whether it's more similar to the MF4270 or the MP730. One of the key diffs between the MF4270 is the checksumming; in yours, it just puts a checksum at the end like other Pixmas while mine is weird in that it puts the inverse at the end and the regular checksum before it.
Anyway, I'll dig into it more tomorrow. If you don't mind, I'm also cc'ing the list and attaching an abridged version of the log for posterity and in case anyone else wants to weigh in on the protocol.
-Dennis
URB cmd/len: data
----------------------
... [init stuff]
6 b-wr 10: f3 20 00 00 00 00 00 00 0c 00
7 b-rd 14: 06 06 03 01 00 41 03 00 41 00 03 00 00 74
8 b-wr 10: f3 20 00 00 00 00 00 00 0c 00
9 b-rd 14: 06 06 03 01 00 41 03 00 41 00 03 00 00 74
10 b-wr 20: cf 60 00 00 00 00 00 00 0a 00 01 00 00 00 00 00
00 00 00 ff
11 b-rd 2: 06 06
12 b-wr 20: cf 60 00 00 00 00 00 00 0a 00 01 00 00 00 00 00
00 00 00 ff
13 b-rd 2: 06 06
14 b-rd 20: cf 60 00 00 00 00 00 00 0a 00 01 00 00 04 00 00
00 00 00 fb
15 b-rd 2: 06 06
16 b-wr 10: db 20 00 00 00 00 00 00 00 00
17 b-rd 2: 06 06
18 b-wr 20: dd 20 00 00 00 00 00 00 0a 00 01 00 00 00 00 00
00 00 00 ff
19 b-rd 2: 06 06
20 b-wr 56: de 20 00 00 00 00 00 00 2e 00 00 00 00 00 10 4b
10 4b 00 00 00 00 00 00 00 00 00 00 02 80 00 00
00 20 04 08 00 00 00 00 00 7f ff 00 00 81 00 00
00 00 00 00 00 00 00 9d
21 b-rd 2: 06 06
22 b-wr 10: f3 20 00 00 00 00 00 00 0c 00
23 b-rd 14: 06 06 03 01 00 41 03 00 41 00 03 00 00 74
24 b-wr 10: f3 20 00 00 00 00 00 00 0c 00
25 b-rd 14: 06 06 03 01 00 41 03 00 41 00 03 00 00 74
26 b-wr 11: d4 20 00 00 00 00 00 00 00 00 06
27 b-rd 8: 06 06 00 00 00 00 00 00
28 b-wr 11: d4 20 00 00 00 00 00 00 04 00 06
29 b-rd 8: 06 06 00 00 00 00 02 80
... [scan data]
156 b-wr 11: d4 20 00 00 00 00 00 00 04 00 06
157 b-rd 8: 06 06 38 00 00 00 00 00
158 b-wr 10: f3 20 00 00 00 00 00 00 0c 00
159 b-rd 14: 06 06 03 01 00 41 03 00 41 00 03 00 00 74
160 b-wr 10: f3 20 00 00 00 00 00 00 0c 00
161 b-rd 14: 06 06 03 01 00 41 03 00 41 00 03 00 00 74
162 b-wr 10: ef 20 00 00 00 00 00 00 00 00
163 b-rd 2: 06 06
164 b-wr 20: cf 60 00 00 00 00 00 00 0a 00 01 00 00 00 00 00
00 00 00 ff
165 b-rd 2: 06 06
166 b-wr 10: f3 20 00 00 00 00 00 00 0c 00
167 b-rd 14: 06 06 03 01 00 41 03 00 41 00 03 00 00 74
----- Original Message ----
From: Bob Dronski < dronski@...>
To: Dennis Lou < dlou99@...>
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
--
sane-devel mailing list: sane-devel@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: 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@...> To: Dennis Lou < dlou99@...> 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@...> 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@...> 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
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@...> 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@...> To: Dennis Lou < dlou99@...> 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@...> To: Dennis Lou < dlou99@...> 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@...> 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@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
Some parts of this message have been removed.
Learn more about Nabble's security policy.
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@...> To: Dennis Lou < dlou99@...> Cc: sane-devel@...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@...> To: Dennis Lou < dlou99@...> 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@...> 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@...> 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
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@...> 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@...> To: Dennis Lou < dlou99@...> 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@...> To: Dennis Lou < dlou99@...> 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@...> 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@...
http://lists.alioth.debian.org/mailman/listinfo/sane-develUnsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request@...
|
|
Re: Canon MF4140
Moving the USB PID to pixma_mp730.c and adding a line declaration at
the end of this file (in pixma_mp730_devices[]) should be enough to have
the scanner detected by scanimage. Don't forget to remove both from
pixma_imageclass.c
Bob, if you don't succeed doing this, please activate the trace logs to
see what's going on:
$ export SANE_DEBUG_PIXMA=20
$ scanimage -T -vv
Nicolas
Le samedi 30 août 2008 à 19:15 -0700, Dennis Lou a écrit :
> 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@...>
> To: Dennis Lou < dlou99@...>
> Cc: sane-devel@...
> 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 MF4 |
