On Tue, Nov 2, 2010 at 5:29 AM, Louis Lagendijk <louis at lagendijk.xs4all.nl> wrote: > On Sun, 2010-10-31 at 19:51 +0100, >> > 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 >> > > > Please check the USB-ids, if it is incorrect network scanning will work > (as long as the device id is unique) as the network code gets the > device-id from the definition in mp150.c where it does the lookup by the > name of the device read over the ethernet connection. For USB it works > the other way round....SO if the the id is incorrect network scanning > will work, while usb scanning fails > > best regards, Louis (author of the BJNP stuff)
Hi, yes, please confirm the USBid, I took the above ones from the Japanese MG8100 series driver, but do not have the device myself. Best regards, Gernot Hassenpflug