[sane-devel] support for Canon MG8150

Sun Oct 31 19:41:20 UTC 2010

I tried to use the device over ethernet and this seems to work better:

Quoting Gernot Hassenpflug <aikishugyo at gmail.com>:

> On Mon, Nov 1, 2010 at 2:19 AM,
> <ralph.gauges at bioquant.uni-heidelberg.de> wrote:
>> Hi,
>>
>> I recently bought a new multifunction device from Canon (MG8150) and as
>> usually there are no linux drivers for the device from the manufacturer.
>>
>> So the question now is, how could I be of help  
>> tgauges at delilah:~/workspace/sane_devel/backends.git$ scanimage -L
device `pixma:MG8100_000000C8E622' is a CANON Canon MG8100 series  
multi-function peripheral
gauges at delilah:~/workspace/sane_devel/backends.git$ 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
o eventually get this device

I also scanned a real image and that also worked. I haven't tried to  
change any settings yet.

So after adding the lines you suggested, scanning over ethernet seems  
to work while scanning via USB does not work yet.
Somehow when using the USB connection, the device is recognized as an  
MX870 while over ethernet it is correctly recognized as an MG8100  
device.

Ah, I have made a small mistake, I changed the wrong ID, maybe it is  
to late already.
Now I fixed the ids again and the device is recognized as an MG8100  
device over USB as well, but I still get the I/O error.

So right now, scanning over ethernet works, but over USB it doesn't work yet.
Since the driver seems to be able to talk to the device, this is  
likely something small.

What can I do to track down the USB problem and what tests can I run  
to make sure the device works as expected? Is there a standard set of  
tests to run?

Thanks

Ralph

>> running under linux.
>> I have never written any device drivers, but I know C/C++ and I am fairly
>> familiar with linux, so if you tell me what I can do to help, I will try.
>
> Hi,
>
> At the moment there is no specific support for the new devices, so you
> are most welcome to help. As there already exists code that might be
> able to support these devices without any (or not much) development
> please try the following, using the CVS sane-backends code.
>
> You can try adding the definitions near the end of pixma_mp150.c where
> similar definitions exist, like this:
>
>   /* Latest devices (2010) Generation 4 CIS/CCD */
>   DEVICE ("Canon PIXMA MP280",  "MP280",  MP280_PID,  1200, 638, 877,
> PIXMA_CAP_CIS),
>   DEVICE ("Canon PIXMA MG5100", "MG5100", MG5100_PID, 1200, 638, 877,
> PIXMA_CAP_CIS),
>   DEVICE ("Canon PIXMA MG6100", "MG6100", MG6100_PID, 2400, 638, 877,
> PIXMA_CAP_CIS),
>   DEVICE ("Canon PIXMA MG6200", "MG6200", MG6200_PID, 2400, 638, 877,
> PIXMA_CAP_CIS),
>   DEVICE ("Canon PIXMA MG8100", "MG8100", MG8100_PID, 4800, 638, 877,
> PIXMA_CAP_CCD | PIXMA_CAP_TPU),
>
> and the USB ids near the start of the file under the existing ones,   
> like this:
>
> #define MP280_PID 0x1746
> #define MG5100_PID 0x1748
> #define MG5200_PID 0x1749
> #define MG6100_PID 0x174a
> #define MG8100_PID 0x174b
>
> Compile and then see if the device can work at all. Note the MG
> devices are sold under different names in different parts of the
> world, so the last 2 digits above are simply 00 to denote the family.
>
> (other new device USB ids given here for reference)
> Regards,
> Gernot
> --
> ISP Asahi-Net: http://asahi-net.jp/en/
> No.1 in Japan by customer satisfaction
> (Nikkei News, 7 July 2010)
>