[sane-devel] USB Boeder SmartScan on Debian Sarge
Rodolfo, It shows pretty clearly that you are missing the ps1fw.usb firmware file. A quick search of google revealed that this file should be on the CDRom that came with the scanner, and also it's available from the gt68xx-backend web page at: http://www.meier-geinitz.de/sane/gt68xx-backend/ Just search on that page for ps1fw.usb, and you'll find the link where you can grab the file from. Once you have the file, drop it into the /usr/share/sane/gt68xx directory. Hope that helps, Jim McQuillan j...@ltsp.org Rodolfo Medina wrote: Hi: I installed Sane on my Debian GNU/Linux system but apparently don't manage to make it work. After installing Sane with: `apt-get install sane', I did: # sane-find-scanner and got the following output: found USB scanner (vendor=0x05d8, product=0x4002, chip=GT-6801) at libusb:001:003 . Then I did: # scanimage -h , and: [gt68xx] Couldn't open firmware file (neither `/usr/share/sane/gt68xx/PS1fw.usb' nor `/usr/share/sane/gt68xx/ps1fw.usb'): No such file or directory scanimage: open of device gt68xx:libusb:001:003 failed: Invalid argument Type ``scanimage --help -d DEVICE'' to get list of all options for DEVICE. List of available devices: gt68xx:libusb:001:003 . Then I did: # scanimage -d gt68xx:libusb:001:003 --format tiff file.tif and: [gt68xx] Couldn't open firmware file (neither `/usr/share/sane/gt68xx/PS1fw.usb' nor `/usr/share/sane/gt68xx/ps1fw.usb'): No such file or directory scanimage: open of device gt68xx:libusb:001:003 failed: Invalid argument Could you Sane listers provide any help in order to make my USB Boeder SmartScan work? Thanks in advance, Rodolfo
[sane-devel] brightness/contrast/gamma LUT ideas?
Allan, I don't have an answer, but I'd like to comment that I sure could use such a feature. I'm using the Fujitsu fi-5120C scanner, as you know, because you helped me get it working. And so far, it's working really well. I did find one issue though. I'm scanning both sides of the page at the same time, and i've found that documents printed on 20lb paper are getting some bleed through. That is, the scan of the front is actually showing some of the stuff that is on the back of the page. Also, the scans come out looking somewhat dirty. Again, because I think light from the other side is bleeding through. I tried printing the same documents on 28lb paper, and the scans look beautiful, no bleeding is seen. This turns out to be a big issue, because when I scan the document printed on 20lb paper, the two images tarred together and compressed with bzip are taking about 2.7mb. While the same document printed on 28lb paper compresses down to about 900kb. HUGE difference in compressability. I'm thinking that if I could reduce the brightness of the light, it may not bleed through so badly. Thanks, Jim McQuillan j...@ltsp.org m. allan noah wrote: recent model fujitsu scanners dont have native brightness/contrast/gamma support, instead they use an 256x256 or 1024x256 bit look up table to convert the raw scan data before 8 bit output. while it is true that the 8bit square LUT could be done after scanning with no data loss, most command line front-ends dont do this, and the 10 bit lut has 'access' to more data that never gets out of the scanner, so i would like to extend the backend to provide at least brightness/contrast for these scanners. i need suggestions or pointers to code that i could use. what things i can find are far over my head, but i have a simple brightness adjustment that shifts the linear slope of the in-out function up or down, and a crude contrast setting that changes the slope of the function around the center of the table. i think both of these methods are likely too simplistic. anyone? allan
[sane-devel] brightness/contrast/gamma LUT ideas?
m. allan noah wrote: are you using lineart mode? the threshold option should help... No, i'm using Greyscale, because there's some shaded regions, and I really need the scanned document to look good. Jim. allan On Mon, 10 Jul 2006, Jim McQuillan wrote: Allan, I don't have an answer, but I'd like to comment that I sure could use such a feature. I'm using the Fujitsu fi-5120C scanner, as you know, because you helped me get it working. And so far, it's working really well. I did find one issue though. I'm scanning both sides of the page at the same time, and i've found that documents printed on 20lb paper are getting some bleed through. That is, the scan of the front is actually showing some of the stuff that is on the back of the page. Also, the scans come out looking somewhat dirty. Again, because I think light from the other side is bleeding through. I tried printing the same documents on 28lb paper, and the scans look beautiful, no bleeding is seen. This turns out to be a big issue, because when I scan the document printed on 20lb paper, the two images tarred together and compressed with bzip are taking about 2.7mb. While the same document printed on 28lb paper compresses down to about 900kb. HUGE difference in compressability. I'm thinking that if I could reduce the brightness of the light, it may not bleed through so badly. Thanks, Jim McQuillan j...@ltsp.org m. allan noah wrote: recent model fujitsu scanners dont have native brightness/contrast/gamma support, instead they use an 256x256 or 1024x256 bit look up table to convert the raw scan data before 8 bit output. while it is true that the 8bit square LUT could be done after scanning with no data loss, most command line front-ends dont do this, and the 10 bit lut has 'access' to more data that never gets out of the scanner, so i would like to extend the backend to provide at least brightness/contrast for these scanners. i need suggestions or pointers to code that i could use. what things i can find are far over my head, but i have a simple brightness adjustment that shifts the linear slope of the in-out function up or down, and a crude contrast setting that changes the slope of the function around the center of the table. i think both of these methods are likely too simplistic. anyone? allan
[sane-devel] Bleedthrough (was brightness/contrast/gamma LUT ideas?)
Martin Collins wrote: On Mon, 10 Jul 2006 19:55:23 -0400 Jim McQuillan j...@mcquil.com wrote: i've found that documents printed on 20lb paper are getting some bleed through. That is, the scan of the front is actually showing some of the stuff that is on the back of the page. ... I'm thinking that if I could reduce the brightness of the light, it may not bleed through so badly. Maybe, but I think you will get better results by using a black backing. It's a puzzle to me why so many scanners use white backing. Sorry, but I don't understand what you mean by 'black backing'. Could you please explain? Thanks, Jim. Martin
[sane-devel] saned with latest fujutsu backend broken
I've got a Fujitsu 5120C, and with M. Allan Noah's help and his latest fujitsu backend from cvs, it's working great, using scanimage to talk directly to the backend. But, if I use scanimage to connect to saned, it's not working. I get an 'Invalid argument' When running saned with 'SANE_DEBUG_FUJITSU=128' set, here's a few lines of output: [fujitsu] depth 1 [fujitsu] lines 6600 [fujitsu] pixels_per_line 5104 [fujitsu] bytes_per_line 638 [fujitsu] sane_get_parameters: finish [fujitsu] sane_read: start [fujitsu] read_from_scanner: start [fujitsu] read_from_scanner: ERROR side:0 want:4203144 room:528/65536 doing:0 done:7656 [fujitsu] sane_read: finish [fujitsu] sane_close: start [fujitsu] do_cancel: start [fujitsu] do_cancel: finish The complete logs can be found here: http://www.McQuil.com/saned_debug.txt http://www.McQuil.com/saned_debug_B.txt (scanimage with the -B option) The above test was with a SCSI connection (Adaptec 2906). But, I get very similar results when using USB. This is a test machine that I loaded Ubuntu dapper on last night, WITHOUT any sane packages. I then grabbed the latest from cvs (May 31, 2006 10:30pm EDT), and built/installed it. This only seems to be a problem when using saned, which I *really* need. Any pointers on how to resolve this issue? Thanks, Jim McQuillan j...@ltsp.org
[sane-devel] Fujitsu 5120C
On Tue, May 30, 2006 5:58 pm, m. allan noah wrote: On Tue, 30 May 2006, Jim McQuillan wrote: I'm trying to get a Fujitsu 5120C working with SANE. I've tried version 1.0.17 of the backends, and i've also tried a fresh checkout from cvs today (5/30/2006). use the cvs checkout. The scanner is detected just fine under both versions of the backends. I'm using a SCSI interface. When I try to scan with the scanimage command, I get: scanimage: sane_read: Invalid argument I turned on debugging with SANE_DEBUG_FUJITSU=128 and I see in the logfile: [fujitsu] sane_get_parameters: finish [fujitsu] sane_read: start [fujitsu] read_from_scanner: start [fujitsu] read_from_scanner: ERROR side:0 want:4203144 room:528/65536 doing:0 done:7656 [fujitsu] sane_read: finish [fujitsu] sane_close: start [fujitsu] do_cancel: start hmm- the issue is that 'room:528' part. what front-end are you using, and I'm using scanimage for my testing. Is there something else I should try? Ultimately, I'll be doing this with Python, but I figured I'd do my initial testing of the scanner with scanimage. I'll look at it later tonight, to see if another front end works. THanks, Jim McQuillan j...@ltsp.org why does it give us such a tiny buffer? we cannot request such a small piece from the scanner, we have to request whole scanlines. your scanning params must be such that a single line is larger than that? if you read the code, you will see this, right above that error message: /* this should never happen */ which tells you something: expect the unexpected :) So, is the fujitsu driver at a point, where I should expect the 5120C to work? I'm just trying to figure out if i'm looking at a driver problem, or a configuration problem on my end. yes- you have excellent timing, the backend has just been nearly completely re-written, and the 5120 should work quite well. the problem is your frontend. though there are some speed issues, which are hopefully about to be resolved... allan fujitsu backend maintainer Thanks, Jim McQuillan j...@ltsp.org -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Fujitsu 5120C
Allan, Ok, I tried using scanimage without saned, and it works ! I tried various scans, both color and bw, and it looks great. Now, I need to figure out how to get saned working with this backend. Thanks for your help. Jim McQuillan j...@ltsp.org m. allan noah wrote: On Tue, 30 May 2006, Jim McQuillan wrote: I'm trying to get a Fujitsu 5120C working with SANE. [fujitsu] sane_read: start [fujitsu] read_from_scanner: start [fujitsu] read_from_scanner: ERROR side:0 want:4203144 room:528/65536 doing:0 done:7656 [fujitsu] sane_read: finish [fujitsu] sane_close: start [fujitsu] do_cancel: start hmm- the issue is that 'room:528' part. what front-end are you using, and I'm using scanimage for my testing. ok, try the -B option to scanimage, just to see. i will look at your log now. hmm, looked at your log- the first transfer only gave us a buffer of 8188 bytes. the second even less, 528. i have never seen anything like that. 1. are you using saned? try it without and see if it works. 2. what os? allan
[sane-devel] Fujitsu 5120C
I'm trying to get a Fujitsu 5120C working with SANE. I've tried version 1.0.17 of the backends, and i've also tried a fresh checkout from cvs today (5/30/2006). The scanner is detected just fine under both versions of the backends. I'm using a SCSI interface. When I try to scan with the scanimage command, I get: scanimage: sane_read: Invalid argument I turned on debugging with SANE_DEBUG_FUJITSU=128 and I see in the logfile: [fujitsu] sane_get_parameters: finish [fujitsu] sane_read: start [fujitsu] read_from_scanner: start [fujitsu] read_from_scanner: ERROR side:0 want:4203144 room:528/65536 doing:0 done:7656 [fujitsu] sane_read: finish [fujitsu] sane_close: start [fujitsu] do_cancel: start If you'd like to see the entire file, it's at: http://www.McQuil.com/fujitsu_5120c.txt If you need any more info, i'm happy to provide it. So, is the fujitsu driver at a point, where I should expect the 5120C to work? I'm just trying to figure out if i'm looking at a driver problem, or a configuration problem on my end. Thanks, Jim McQuillan j...@ltsp.org
[sane-devel] Looking for a small business card sized scanner
Henning, I've attached the output of 'sane-find-scanner' and 'sane-find-scanner -v -v', both run as root. If you have any ideas of how to make this work with sane, i'd really appreciate it. Alternatively, if you know of any card-sized scanners that are well supported by sane, that would also be very useful for me. Thank you, Jim McQuillan j...@ltsp.org Henning Meier-Geinitz wrote: Hi, On 2006-01-19 16:40, Jim McQuillan wrote: I picked up a ScanShell 800N, but sadly, it doesn't appear to be supported by SANE. Google finds only 160 hits for ScanShell 800N. Either it's really new or it's rather uncommon. 3) Writing a new driver for the 800N Only the standard one: look at www.sane-project.org, section Contributing. found USB scanner (vendor=0x0a82, product=0x6605, chip=LM983x?) at libusb:004:006 0x0a82 seems to be used by Syscan. Run it as root to check if it's really a LM983x chip. Please also send the sane-find-scanner -v -v output as root. Bye, Henning -- next part -- # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try modprobe sg. found USB scanner (vendor=0x0a82 [Card Scanning Solutions], product=0x6605 [CSSN-SCANSHELL 800N], chip=LM9832/3) at libusb:004:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. -- next part -- This is sane-find-scanner from sane-backends 1.0.15 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try modprobe sg. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument
[sane-devel] Looking for a small business card sized scanner
Hello, I need a small scanner for scanning business cards and insurance cards. I picked up a ScanShell 800N, but sadly, it doesn't appear to be supported by SANE. I've got the results of various tests and below. Does anybody have any pointers for one of the following: 1) Making this 800N work with an existing driver 2) A different scanner that is good for scanning business cards 3) Writing a new driver for the 800N Any help will be greatly appreciated, because I REALLY don't want to put windows boxes at this customer. Thanks, Jim McQuillan j...@ltsp.org sane-find-scanner reports: found USB scanner (vendor=0x0a82, product=0x6605, chip=LM983x?) at libusb:004:006 scanimage -L reports: No scanners were identified. /proc/bus/usb/devices shows this: T: Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0a82 ProdID=6605 Rev= 1.00 S: Manufacturer=Card Scanning Solutions S: Product=CSSN-SCANSHELL 800N C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=16ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms Results of lsusb -v -v: Bus 004 Device 006: ID 0a82:6605 Syscan Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0a82 Syscan idProduct 0x6605 bcdDevice1.00 iManufacturer 64 iProduct 113 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol255 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 16 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0
