[sane-devel] Backend for plustek Opticbook 3600
Le jeudi 14 janvier 2010 17:47:41 Chris Berry, vous avez ?crit : Ok quick update, I have managed to get the lamp on during scans! The reason it was failing is because reg[0x01] was hard coded to CIS type and this is a CCD scanner. Hopefully this means that all I have to do is polish up the remaining register values at init time. Currently the light is on when the scan head moves down but turns itself off immediately before it comes back, is this normal behaviour for the genesys driver? Chris Hello, nice job. Do you get any picture data ? I don't think that the genesys backend switch off lamp after you scan on purpose. The planned behaviour is to switch off CCD only when the defined waiting time has elapsed. Maybe what you are seeing is the power saving function kicking in and switching off light by modifying GPIOs (see gl841_save_power function in genesys_gl841.c). While this doesn't hurt for CIS scanners, CCD may have to warm up each time they light on. So this behaviour might not be desirable. Regards, Stef
[sane-devel] Backend for plustek Opticbook 3600
Hi Stef, in the course of trying to get the lamp working I was playing with the settings and after I removed my changes the lamp functions as i expected too so that issue is resolved. If my understanding is correct the code should select whether to set cis or not based on the variable in genesys_driver.c. As it is currently hard coded I will try and put an if statement in to select based on the /* Is this a CIS scanner? */ sane boolean. I am still not getting any picture data, after observing some of the front end logs I see that the windows driver only writes to *FRONT END* addresses 0x00 - 0x07, but the genesys driver is writing to 0x00 - 0x09 and many others (0x20, 0x24 etc...). I am guessing this is very bad for the recovery of data from the DAC. I will attach a new genesys log and a windows sniff to the project website today and maybe some pictures. As usual any pointers are greatly appreciated Thanks Chris On 01/15/2010 01:10 PM, stef wrote: Le jeudi 14 janvier 2010 17:47:41 Chris Berry, vous avez ?crit : Ok quick update, I have managed to get the lamp on during scans! The reason it was failing is because reg[0x01] was hard coded to CIS type and this is a CCD scanner. Hopefully this means that all I have to do is polish up the remaining register values at init time. Currently the light is on when the scan head moves down but turns itself off immediately before it comes back, is this normal behaviour for the genesys driver? Chris Hello, nice job. Do you get any picture data ? I don't think that the genesys backend switch off lamp after you scan on purpose. The planned behaviour is to switch off CCD only when the defined waiting time has elapsed. Maybe what you are seeing is the power saving function kicking in and switching off light by modifying GPIOs (see gl841_save_power function in genesys_gl841.c). While this doesn't hurt for CIS scanners, CCD may have to warm up each time they light on. So this behaviour might not be desirable. Regards, Stef -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
[sane-devel] What device does Xerox Phaser 6180MFP use ? See output here..
Hi all, I am absolutely new to Linux, but anyway I have been in contact with the mantainer of xerox_mfp backend. He suggested to ask on this mailing list, if somebody knows a compatible driver, or can do something about my problem: I bought a Xerox Phaser 6180MFP lately, but I cannot use the scanner under Linux because it is not listed and stated as compatible on sane-project.org. But I tried to 1. run sane-find-scanner which gave me the USB ID... 2. found USB ID's (vendor and manufacturer) and added them in HEX to xerox_mfp.conf 3. tried SANE_DEBUG_XEROX_MFP=9 scanimage -L which did not work: --- Amiga-SAM:~# SANE_DEBUG_XEROX_MFP=9 scanimage -L [sanei_debug] Setting debug level of xerox_mfp to 9. [xerox_mfp] sane_init: Xerox backend (build 10) 0xbffacbe8, 0x10006610 [xerox_mfp] sane_xerox_mfp_get_devices: 0xbffacc18, 0 [xerox_mfp] list_one_device: libusb:004:007 [xerox_mfp] dev_open: open 0x101065b8 [xerox_mfp] :: dev_command(INQUIRY[0x12], 70) [xerox_mfp] dev_request: sanei_usb_read_bulk: Error during device I/O [xerox_mfp] dev_command: dev_request: Error during device I/O [xerox_mfp] dev_close: closing dev 0x101065b8 [xerox_mfp] list_one_device: dev_inquiry(libusb:004:007): Error during device I/O No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). Output shows that driver was not able to communicate with device, probably is if offline or it is not compatible driver. Are you sure scanner is turned on, check lamp is lighting. --- 4. ran sane-find-scanner -v -v . The maintainer of Xerox_mfp suggested to post this output (partwise) here, TO ASK YOU WETHER SOMEBODY KNOWS WHAT DEVICE THIS REALLY IS as Xerox scanners are mainly rebranded products: device descriptor of 0x0550/0x0090 at 004:006 (Xerox Phaser 6180MFP-N) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0550 idProduct 0x0090 bcdDevice 1.00 iManufacturer 1 (Xerox) iProduct 2 (Phaser 6180MFP-N) iSerialNumber 3 (GPX117884) bNumConfigurations1 configuration 0 bLength 9 bDescriptorType 2 wTotalLength 62 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 2 mA interface 0 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 0 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x85 (in 0x05) bmAttributes 3 (interrupt) wMaxPacketSize8 bInterval 11 ms bRefresh 0 bSynchAddress 0 interface 1 altsetting 0 bLength9 bDescriptorType4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass7 bInterfaceSubClass 1 bInterfaceProtocol 2 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x84 (in 0x04) bmAttributes 2 (bulk) wMaxPacketSize512 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 (bDeviceClass = 0) checking for GT-6816 ... this is not a GT-6816 (bcdUSB = 0x200) checking for GT-8911 ... this is not a GT-8911 (check 2, bcdUSB = 0x200) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255) checking for MA-1015 ... this is not a
[sane-devel] What device does Xerox Phaser 6180MFP use ? See output here..
On Fri, Jan 15, 2010 at 3:52 PM, Dipl.Geogr.G.Birkenfeld gerobirkenfeld at web.de wrote: Hi all, ?I am absolutely new to Linux, but anyway I have been in contact with the mantainer of xerox_mfp backend. He suggested to ask on this mailing list, if somebody knows a compatible driver, or can do something about my problem: I bought a Xerox Phaser 6180MFP lately, but I cannot use the scanner under Linux because it is not listed and stated as compatible on sane-project.org. But I tried to 1. run sane-find-scanner which gave me the USB ID... 2. found USB ID's (vendor and manufacturer) and added them in HEX to xerox_mfp.conf 3. tried SANE_DEBUG_XEROX_MFP=9 scanimage -L which did not work: [snip] If there is no driver available, what informations are needed to develop one, and, if it is possible is there anybody to out there to take tasks ? The usb interface looks simple enough, very few endpoints. Can you get a trace of the windows driver making a small black and white scan using this tool: http://www.pcausa.com/Utilities/UsbSnoop/ Then zip the log, and send it to the list. Perhaps someone will recognize the protocol. There are individuals on this list who will write and/or modify drivers. Some do this for free or for hardware donation, others do it for payment. allan -- The truth is an offense, but not a sin
No subject
subdirectories under /usr/local (including manual pages) so unless you already have a local installation of SANE this should not interfere with the system installation. Hope that helps you, Gernot
No subject
gured out the root of the problem you are having.br br At high resolutions the V500#39;s supported resolution list for the TPU in= the X and Y directions are completely different. The highest common resolu= tion in both directions is 1600 dpi. iscan, in the interest of usability, h= ides this complexity from you and attempts to compensate by doing some scal= ing behind your back. However, due to a bug in its image processing library= it refuses to process such large images. Hence the error you are getting w= hich happens to be the same as before, but with a different root cause.br br You should be able to scan with scanimage or XSANE, but will have to keep i= n mind that unlike iscan, these frontends do not hide the resolution mess f= rom you, and you will have to specify a different X and Y resolution when s= canning at higher resolutions. The end result is that your images will come= out stretched in one direction or the other. You will have to rescale your= images manually using the Gimp or another tool. I would personally recomme= nd using the Image Magick command line tools in a script to automate the sc= anning and scaling process, if that is possible with your workflow.br br If you can scan a colour image with a width greater than 11,000 pixels usin= g scanimage, then you are definitely using the modified code. With iscan it= is uncertain due to all the things it tries to do behind your back.br br Looking at the information I have, the maximum width you could possibly get= out of the V500#39;s TPU is 17,280 pixels @ 6400 dpi. This definitely req= uires the code modification and editing of the fs-blacklist as I instructed= you before.br br br I hope all this made some sense.br Let me know if you can get it to work.divdiv/divdiv class=3Dh5br= br Happy scanning,br -- br Alesh Slovak =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Linux Team -- AVASYS Co= rporationbr a href=3Dmailto:alesh.slovak at avasys.jp target=3D_blankalesh.slovak at av= asys.jp/a =A0 =A0 =A0 =A0 =A0a href=3Dhttp://avasys.jp; target=3D_blan= khttp://avasys.jp/abr /div/div/blockquote/divbr --0015174c0f74ac7d9e04828b681c--
