[sane-devel] HP 2400, GL646 and genesys
Le lundi 28 mai 2007, Shug Boabby a ?crit?: Hi all, My scanner is not supported, but the support page http://www.sane-project.org/cgi-bin/driver.pl?manu=Hewlett +Packardmodel=2400 says GL646 based, to be added to genesys backend. If I understand correctly, this support has been added to the latest genesys backend. http://www.sane-project.org/man/sane-genesys.5.html Is there a way of telling sane to use the genesys backend for this scanner? Or if anyone else has any comments on this scanner, please let me know. Thanks and kind regards, Shug Hello, the HP2400 isn't supported. The man page doesn't tell so (but HP2300 is supported). Adding support for it wouldn't be difficult for me, but I'd need to have one to test on. There were also a few people that expressed interest in doing it themselves. I gave them the scripts I use and some information on how to do it, but nothing came up yet. Regards, Stef
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'tonym at hcrimaging.com' 2. Manufacturer (e.g. Mustek): 'Canon' 3. Model name (e.g. ScanExpress 1200UB): 'DR-7580' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x04a9' 6. Product id (e.g. 0x0002): '0x160b' 7. Chipset (e.g. lm9831): 'unknown' 8. Comments (e.g. similar to Mustek 1234): 'The Canon DR-7580 and DR-9080c are essentially the same scanner. The difference is that the 7580 is BW and the 9080c is color. This is generally driven by ISIS (Pixtran / Captiva ) drivers in Windows and is a high-speed document imaging scanner. http://www.captivasoftware.com/products/pixtran.asp Captiva was at first hopeful they could help with a Linux solution but finally stopped returning my calls. This scanner has both USB 2.0 and SCSI interfaces. Document scanning is one area that Linux lacks and if someone can get these scanners working I have a programmer waiting to write a GPL scanning frontend for document imaging.' 9. Data (e.g. sane-find-scanner -v -v): 'device descriptor of 0x04a9/0x160b at 005:005 bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x160B bcdDevice 3.04 iManufacturer 1 ((null)) iProduct 2 ((null)) iSerialNumber 3 ((null)) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 98 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass0 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 1 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 1 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bDeviceClass = 0) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 0, bInterfaceClass = 0) checking for GT-8911 ... this is not a GT-8911 (check 1, bDeviceClass = 0, bInterfaceClass = 0) checking for MA-1017 ... this is not a MA-1017 (bcdUSB = 0x200) checking for MA-1015 ... this is not a MA-1015 (bDeviceClass = 0) checking for MA-1509 ... this is not a MA-1509 (bDeviceClass = 0) checking for LM983[1,2,3] ... this is not a LM983x (bDeviceClass = 0, bInterfaceClass = 0) checking for GL646 ... this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 0) checking for GL646_HP ... this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 0) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 0) checking for GL841 ... this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 0) checking for ICM532B ... this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 0) checking for PV8630/LM9830 ... this is not a PV8630/LM9830 (bcdUSB = 0x200) checking for M011 ... this is not a M011 (bDeviceClass = 0) checking for RTS8822L-01H ... this is not a RTS8822L-01H (bNumEndpoints = 2) checking for rts8858c ... this is not a rts8858c (bcdUSB = 0x200) checking for SQ113 ... this is not a SQ113 (bInterfaceClass = 0) Couldn't determine the type of the USB chip (result from sane-backends 1.0.18) found USB scanner (vendor=0x04a9, product=0x160b) at libusb:005:005 '
[sane-devel] canon DR series in SANE
tony et al: i have had some relatively high-level contacts with canon corporate a few months back about getting the docs required to write a driver for the DR series scanners. I think their management is a little confused about the idea of anyone doing such work for free. i have a feeling that the basics of the scanner protocol could be reverse engineered from windows USB traces, but it would be much easier with docs. if you want, you could try contacting some of their folks and asking for linux support. contact me directly, and i will give you an ear to bend :) allan On 6/1/07, cgi-mailer at kundenserver.de cgi-mailer at kundenserver.de wrote: === == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'tonym at hcrimaging.com' 2. Manufacturer (e.g. Mustek): 'Canon' 3. Model name (e.g. ScanExpress 1200UB): 'DR-7580' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x04a9' 6. Product id (e.g. 0x0002): '0x160b' 7. Chipset (e.g. lm9831): 'unknown' 8. Comments (e.g. similar to Mustek 1234): 'The Canon DR-7580 and DR-9080c are essentially the same scanner. The difference is that the 7580 is BW and the 9080c is color. This is generally driven by ISIS (Pixtran / Captiva ) drivers in Windows and is a high-speed document imaging scanner. http://www.captivasoftware.com/products/pixtran.asp Captiva was at first hopeful they could help with a Linux solution but finally stopped returning my calls. This scanner has both USB 2.0 and SCSI interfaces. Document scanning is one area that Linux lacks and if someone can get these scanners working I have a programmer waiting to write a GPL scanning frontend for document imaging.' 9. Data (e.g. sane-find-scanner -v -v): 'device descriptor of 0x04a9/0x160b at 005:005 bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x160B bcdDevice 3.04 iManufacturer 1 ((null)) iProduct 2 ((null)) iSerialNumber 3 ((null)) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 98 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass0 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 1 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 1 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bDeviceClass = 0) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 0, bInterfaceClass = 0) checking for GT-8911 ... this is not a GT-8911 (check 1, bDeviceClass = 0, bInterfaceClass = 0) checking for MA-1017 ... this is not a MA-1017 (bcdUSB = 0x200) checking for MA-1015 ... this is not a MA-1015 (bDeviceClass = 0) checking for MA-1509 ... this is not a MA-1509 (bDeviceClass = 0) checking for LM983[1,2,3] ... this is not a LM983x (bDeviceClass = 0, bInterfaceClass = 0) checking for GL646 ... this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 0) checking for GL646_HP ... this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 0) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 0) checking for GL841 ... this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 0) checking for ICM532B ... this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 0) checking for PV8630/LM9830 ... this is not a PV8630/LM9830 (bcdUSB = 0x200) checking for M011 ... this is not a M011 (bDeviceClass = 0) checking for RTS8822L-01H ... this is not a RTS8822L-01H (bNumEndpoints = 2) checking for rts8858c ... this is not a rts8858c (bcdUSB = 0x200) checking for SQ113 ... this is not a SQ113 (bInterfaceClass = 0) Couldn't determine the type of the USB chip (result from sane-backends 1.0.18) found USB
[sane-devel] pixma / mp160
Hi there, i have written a mail to the author and maintainer of the pixma support in sane a few months ago, but got no reply. Now I have seen that something has been done on the pixma drivers, therefore I wanna come back with my interest in this list. The fact is, that I have a Canon Pixma MP160. Printing is working fine with TurboPrint and i would really be happy if scanning would do either. I've seen that there is basic support for this scanner now, but far from beeing complete, so I hope that i can help you in some way. I am NOT a developer, so i may not help in coding, but maybe I can help you with trying new versions, tracing usb-communication etc. Just let me know, if there is a way to help you and point me to the proper places, where documentation can be found. Thanks and Best Regards Patrick
[sane-devel] XSane Segmentation fault
Le jeudi 31 mai 2007, Luis P. Mendes a ?crit?: Hi, I'm running Slackware 11.0 and I am not able to use XSane. The problem is: $ xsane lp: Operation not permitted parport_pc: Operation not permitted Segmentation fault I've tried to solve this issue and I think I am close. But now I need help from you. $ scanimage --version scanimage (sane-backends) 1.0.18; backend version 1.0.18 Only as root, I can: # scanimage -L device `epson:/dev/usb/scanner0' is a Epson CC-570L flatbed scanner The ids are ok: # cat /etc/sane.d/epson.conf | grep -v '^#' usb 0x4b8 0x802 usb /dev/usb/scanner0 If I type: $ scanimage -d epson:/dev/usb/scanner0 P4 # SANE data follows 632 877 everything is okay. I can scan papers from command line like, for example: $ scanimage -d epson:/dev/usb/scanner0 --resolution 300 image.tiff But if I omit the -d option: $ scanimage --resolution 300 image.tiff lp: Operation not permitted parport_pc: Operation not permitted Segmentation fault The error I get seems the same as the one above mentioned when I try xsane. So, logic tells me that I should pass some parameter to xsane in order for this to work. How can I do it? Or, what else should I do to solve this issue? Luis Hello, enabling SANE backend loading debug with: export SANE_DEBUG_DLL=255 Then running 'scanimage --resolution 300 image.tiff' would certainly give a hint on whatever backend that would be trying to access the parrallel port. Regards, Stef
