[sane-devel] Adding Scanner to Backend Configuration
Le mercredi 23 mai 2007, gmurray at cloudnet.com a ?crit?: Hugh wrote: I wanted to know if anyone would like to look at them. I would like to see the filtered output. Please post/send me a url. In the initial URBS there seemed to be a lot of unnecessary data sent. In the first 1393 URB numbers, there is a block of 0x0200 bytes that is resent to the device 312 times. The block is constant, except for the first byte. Sending the block to the device returns an URB with just 1 byte. That byte becomes the first byte of the 0x0200 byte block in the next resend. Mysterious, but interesting. regards, Gerald For me it is a bulk read on endpoint 0x83. Which is consistent with the lsusb output. The windows driver sends out a useless buffer of 512 bytes, while the actual data is the one byte read back. With a modified 'parse1.awk' that doesn't skip this, the USB log look like: URB 8 bulk_out len 4 wrote 0x01 0x46 0x01 0x00 URB 9 bulk_in len 1 read 0x08 URB10 bulk_out len 5 wrote 0x00 0x02 0x01 0x00 0x01 URB11 bulk_out len 5 wrote 0x00 0x02 0x01 0x00 0x00 URB12 bulk_out len 5 wrote 0x00 0x01 0x01 0x00 0x00 URB13 bulk_out len 5 wrote 0x00 0x01 0x01 0x00 0x28 URB14 bulk_out len 5 wrote 0x00 0x90 0x01 0x00 0x4f URB15 bulk_out len 5 wrote 0x00 0x92 0x01 0x00 0xff URB16 bulk_out len 4 wrote 0x01 0x91 0x01 0x00 URB17 bulk_in len 1 read 0x00 URB18 bulk_out len 5 wrote 0x00 0x93 0x01 0x00 0x00 URB19 bulk_out len 5 wrote 0x00 0x91 0x01 0x00 0x1f URB20 bulk_out len 5 wrote 0x00 0x95 0x01 0x00 0x1f URB21 bulk_out len 5 wrote 0x00 0x97 0x01 0x00 0x1f URB22 bulk_out len 5 wrote 0x00 0x9b 0x01 0x00 0x00 URB23 bulk_out len 5 wrote 0x00 0x9c 0x01 0x00 0x07 . URB37 bulk_out len 5 wrote 0x00 0x99 0x01 0x00 0x28 URB38 bulk_out len 5 wrote 0x00 0x9a 0x01 0x00 0x03 URB39 bulk_out len 5 wrote 0x00 0x80 0x01 0x00 0x10 URB40 bulk_out len 5 wrote 0x00 0x8d 0x01 0x00 0x00 URB41 bulk_out len 5 wrote 0x00 0x8d 0x01 0x00 0x04 URB42 bulk_out len 4 wrote 0x01 0x8b 0x01 0x00 URB43 bulk_in len 1 read 0x00 URB44 bulk_out len 4 wrote 0x01 0x8b 0x01 0x00 URB45 bulk_in len 1 read 0x00 These look single register read/write for me: first byte read/write flag, second is register index, then a LSB register count. Then there is the value written, or a bulk in for the value read (on endpoint 83). There read/write flag of value 0x02, 0x04 and 0x05. 0x05 is for data reading. When processed with custom scripts it gives a pseudo code like this: write(0x8d,1)=0x00 write(0x8d,1)=0x04 read_reg(0x8b,1)=0x00 read_reg(0x8b,1)=0x00 write(0x85,1)=0x00 write(0x87,1)=0x00 write(0x88,1)=0x70 read_reg(0x8b,1)=0x00 read_reg(0x8b,1)=0x00 write(0x85,1)=0x03 write(0x87,1)=0x00 write(0x88,1)=0x28 read_reg(0x8b,1)=0x00 read_reg(0x8b,1)=0x00 write(0x85,1)=0x06 write(0x87,1)=0x00 write(0x88,1)=0x28 read_reg(0x00,1)=0x40 read_reg(0x01,1)=0x28 read_reg(0x02,1)=0x00 read_reg(0x03,1)=0x00 read_reg(0x04,1)=0x0c read_reg(0x05,1)=0x00 . . all values from 0x00 to 0xFE, look like a 255 registers ASIC . read_reg(0xfd,1)=0x00 read_reg(0xfe,1)=0x00 write(0x60,1)=0x15 write(0x10,1)=0x05 write(0x9b,1)=0x01 read_reg(0x46,1)=0x08 write(0x80,1)=0x12 write(0x11,1)=0x25 write(0x9b,1)=0x01 read_reg(0x46,1)=0x08 read_reg(0x46,1)=0x08 read_reg(0x46,1)=0x08 write(0x80,1)=0x12 write(0x11,1)=0x25 write(0x01,1)=0x28 write(0x04,1)=0x0c write(0x05,1)=0x00 write(0x06,1)=0x00 write(0x01,1)=0x29 write(0x71,1)=0x01 URB 595 bulk_out len 5 wrote 0x02 0x30 0x01 0x00 0x11 write(0x71,1)=0x16 write(0x72,1)=0x01 Does it look familiar to anyone ? What ASIC could it be ? Regards, Stef
[sane-devel] Saned problem
Hi all, I have a very peculiar problem since my upgrade to Debian Etch. I can't access my scanner properly. On the server, to which the scanner is connected, when I run scanimage -L as root, it works fine: # scanimage -L device `epson:libusb:001:002' is a Epson CX3600 flatbed scanner However doing the same as user, doesn't detect the scanner. Then I tried to run saned in debug mode (saned -d) after killing inetd daemon, and then I can detect the scanner not only as user, but also over the network. Please advice! I don't understand what is going on here: - saned works: it detects the scanner correctly in debug mode. - inetd is installed correctly: I can detect my scanner this way, albeit only as root. No idea what else can be wrong here. I don't have a /etc/sane.d/saned.users file, so that is also not an issue. Regards, Wouter van Marle
[sane-devel] Formulardaten
I have removed the circuit board and tried to reveal the chip used in the Lide 70 scanner. I hope this will help development of backend for this scanner. Regards/ Greggan http://www.nabble.com/file/p10760511/lide70large.jpg cgi-mailer wrote: === == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'ajschult at verizon.net' 2. Manufacturer (e.g. Mustek): 'Canon' 3. Model name (e.g. ScanExpress 1200UB): 'CanoScan LiDE 70' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x04a9' 6. Product id (e.g. 0x0002): '0x2225' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): 'Circuitry is covered by a metal plate that is welded on.' 9. Data (e.g. sane-find-scanner -v -v): 'Output from cat /proc/bus/usb/devices T: Bus=08 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=2225 Rev= 0.00 S: Manufacturer=Canon S: Product=CanoScan C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms' -- 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 -- View this message in context: http://www.nabble.com/Formulardaten-tf3218519.html#a10760511 Sent from the SANE - Dev mailing list archive at Nabble.com. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070523/e29e6b39/attachment.htm
[sane-devel] Microtek ArtixScan DI 2020
Has anyone worked on or been working on a backend for this scanner??? USB 2.0. ADF Flatbed Scanner etc... I've been looking into it and I know the web page says its unsupported. It is a fairly new Scanner. I started to mess around with it myself but I'm not sure I can write the backend!! It seems to me that when I plug it in and look at the Vendor ID's, 2 of them goto Microtek, and 1 of them goes to genesys.. Does this mean there is a genesys chip inside of the scanner and they manufactured the device and Microtek is the Seller?? Anyways, if anyone has done any work for the backend for this scanner let me know, or if you have any information that could help me produce a backend for this scanner a little quicker let me know. Thanks. Scott
[sane-devel] Microtek ArtixScan DI 2020
On Wed, 2007-05-23 at 13:05 -0400, scott lorberbaum wrote: Has anyone worked on or been working on a backend for this scanner??? USB 2.0. ADF Flatbed Scanner etc... I've been looking into it and I know the web page says its unsupported. It is a fairly new Scanner. I started to mess around with it myself but I'm not sure I can write the backend!! It seems to me that when I plug it in and look at the Vendor ID's, 2 of them goto Microtek, and 1 of them goes to genesys.. Does this mean there is a genesys chip inside of the scanner and they manufactured the device and Microtek is the Seller?? Anyways, if anyone has done any work for the backend for this scanner let me know, or if you have any information that could help me produce a backend for this scanner a little quicker let me know. Thanks. Scott Try sane-find-scanner -v -v for more information, and output lsusb -v -v add information to http://www.meier-geinitz.de/tinc?key=rDoQ7lrjformname=adddev so more information is added to the unsupported list -- m.vr.gr. Gerard Klaver
[sane-devel] Formulardaten
El Wed, 23 de May de 2007, a las 02:33:29AM -0700, Greggan dijo: I have removed the circuit board and tried to reveal the chip used in the Lide 70 scanner. I hope this will help development of backend for this scanner. Regards/ Greggan http://www.nabble.com/file/p10760511/lide70large.jpg It seems that the main controller is: PHILIPS CP2155BE S60865.1 ZSG0631DY Jonathan Bravo
[sane-devel] Xsane Windows Port V0.991 Copy mode language selection
Hi, I have tried the above version and I think I lost some hairs about it...the scanner is connected to a linux machine and is working well over the net, but if I try to use the copy mode from the Windows machine, it always give me a 'Pipe broken' error. I fiddled around with net use, ghostscriptghostview but without success. Anyone tried already and got it working? Any clues appreciated. Second, I tried to change german GUI language to english, but also without success. As workaround I copied another .mo file into the de subfolder which worked, but I could find a english language file. Thanks for any help in advance, regards, Ikke
[sane-devel] BlackWidow 9636 HiRes
Hullo and thank you for your quick response. I have the above named scanner, which I do not wish to get rid of, but I cannot find a driver for it that will enable me to run it on Windows XP Pro. Any help or advice would be very much appreciated. Regards Mike Holder -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070523/ab719891/attachment.htm
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'scott at collectionsga.com' 2. Manufacturer (e.g. Mustek): 'microtek' 3. Model name (e.g. ScanExpress 1200UB): 'artixscanDI 2020' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x5da' 6. Product id (e.g. 0x0002): '0x202e' 7. Chipset (e.g. lm9831): 'm012' 8. Comments (e.g. similar to Mustek 1234): 'Believe the chipset in this scanner is m012 but not totally certain... If so then it's a toshiba chip and is simliar to the microteck scanmaker 8700' 9. Data (e.g. sane-find-scanner -v -v): 'sane-find-scanner -v -v device descriptor of 0x05da/0x202e at 002:012 bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 3 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x05DA idProduct 0x202E bcdDevice 0.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 0 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) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 trying to find out which USB chip is used checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x200) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 0) checking for GT-8911 ... this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 0) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 0) checking for MA-1015 ... this is not a MA-1015 (bcdUSB = 0x200) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x200) checking for LM983[1,2,3] ... this is not a LM983x (bDeviceClass = 255, bInterfaceClass = 0) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 0) checking for GL646_HP ... this is not a GL646_HP (bDeviceClass = 255, bInterfaceClass = 0) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceSubClass = 0x3) checking for GL841 ... this is not a GL841 (bDeviceClass = 255, bInterfaceClass = 0) checking for ICM532B ... this is not a ICM532B (check 1, bDeviceClass = 255, bInterfaceClass = 0) checking for PV8630/LM9830 ... this is not a PV8630/LM9830 (bDeviceClass = 255) checking for M011 ... this is not a M011 (bcdUSB = 0x200) checking for RTS8822L-01H ... this is not a RTS8822L-01H (bDeviceClass = 255) checking for rts8858c ... this is not a rts8858c (bDeviceClass = 255) checking for SQ113 ... this is not a SQ113 (bDeviceClass = 255) Couldn't determine the type of the USB chip (result from sane-backends 1.0.18) found USB scanner (vendor=0x05da, product=0x202e) at libusb:002:012 device descriptor of 0x05da/0x202e at 002:011 bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 3 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x05DA idProduct 0x202E bcdDevice 0.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 0 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) wMaxPacketSize64 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7
[sane-devel] Saned problem
Hi, Wouter van Marle wrote: However doing the same as user, doesn't detect the scanner. looks as if the usb device doesn't have the correct access rights. I'm not sure where it's mounted on debian, either /proc/bus/usb/aaa/bbb where aaa and bbb are the values in epson:libusb:aaa:bbb or /dev/usb/aaa/bbb regards -- jochen
[sane-devel] BlackWidow 9636 HiRes
the sane project (and this mailing list) is dedicated to the creation of drivers for scanners primarily on unix-like operating systems. While there is some code to build sane for windows, it is not as well tested, and there is no mention of this model in our database. there is only one black widow model listed, the BW4800SP, which is a rebadged Artec AT3. allan On 5/23/07, Michael Owen Holder moholder at ic24.net wrote: Hullo and thank you for your quick response. I have the above named scanner, which I do not wish to get rid of, but I cannot find a driver for it that will enable me to run it on Windows XP Pro. Any help or advice would be very much appreciated. Regards Mike Holder -- 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 -- The truth is an offense, but not a sin
