[sane-devel] ScanExpress A3 USB scanner Gt68xx backend
Dear All, we want to change GT68xx backend in a way that it will work with ScanExpress A3 USB scanner better than before, who can help us that from where we should start? I don't know why GT68xx backend work with some devices good but it has a basic functionality for ScanExpress A3 USB. Thanks alot -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080209/b34309ec/attachment.htm
[sane-devel] Canon LiDE 80 (2nd try)
On Friday 08 February 2008, Reinhard Biegel wrote: Am Wednesday, 6. February 2008 schrieb Reinhard Biegel: Ohi just remember there was something that had to be called at any price but didn't find any documentation about that. I'm going to look for that in my logs. Hi again, I wanted to capture some logs today. But I had to find out that Canon doen't even provide drivers for 64bit Vista, which i set up some days ago. *goingcrazy* As far as I remember there was a bulk write to gamma address space during initialisation which wrote data beyond the end of gamma table in the logs. When saying 'beyond' I'm refering the GL841 datasheet. You are talking about writes like: set_write_register(0x5b, 0x0c) set_write_register(0x5c, 0x00) set_register(0x28) buf_prepaccess(0x0080,BULK_OUT) Data: 01 00 82 00 80 00 00 00 Index: 0 BULK(128) 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0x36, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xb6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0xf6, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 0x18, 0x76, 5b/5c build address 0x0c 00, whereas gamma address is defined as 10bit. I tried a few of them, but without luck. Without writing beyond the end the motors only made ugly noise, but when writing there the initial motor movement (forward-backward-forward...) took place (not the same speed as with windows drivers, either little bit slower or faster, don't remember). Running scanimage alone still produces the ugly motor sound. When I use testprog (mentioned earlier) ahead, scanimage is moving scanhead a back and forward and starts (now with LED on [green]) moving for a complete scan. The only thing which works (standalone) is recognition of home position (thats a hand polished diff): Index: backend/genesys_gl841.c === RCS file: /cvsroot/sane/sane-backends/backend/genesys_gl841.c,v retrieving revision 1.19 diff -p -U 3 -r1.19 genesys_gl841.c --- backend/genesys_gl841.c 3 Feb 2008 10:34:20 - 1.19 +++ backend/genesys_gl841.c 8 Feb 2008 19:51:09 - @@ -2023,6 +2076,9 @@ HOME_FREE: 3 r = sanei_genesys_get_address (reg, 0x69); r-value = 0; +r = sanei_genesys_get_address (reg, 0x6b); +r-value |= 1; /* LiDE 80: turn on motor home sensor */ + r = sanei_genesys_get_address (reg, 0x6a); r-value = (fast_slope_steps 1) + (fast_slope_steps 1); @@ -3475,6 +3552,12 @@ gl841_slow_back_home (Genesys_Device * d wait_until_home); memset (local_reg, 0, sizeof (local_reg)); + + /* LiDE 80: ensure that home sensor is powered on for reading ;-) */ + sanei_genesys_read_register (dev, 0x6b, val); + val |= 1; + sanei_genesys_write_register (dev, 0x6b, val); + val = 0; status = sanei_genesys_get_status (dev, val); if (status != SANE_STATUS_GOOD) -- Stefan Lucke
[sane-devel] Canon LiDE 90
Hello, Why calibration is so long (~50/60s) ? What are /* Start of white strip in mm (y) */ and /* Start of black mark in mm (x) */ in genesys_devices.c ? Regarding the log file you said : W ! 0x23 ! 0x050 ! dac value rgb(offset value) W ! 0x2b ! 0x028 ! pga gain rgb But on debug, I see that these two registers are never written. Another thing : when scaning in color the leds are blue Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, I need a little bit more informations befor testing (sorry for my poor knowledge in scanner) Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org: I don't know why the image colors are reversed, but it may be worth trying to flip the sign bits in Genesys_Frontend. If that does nothing, we need to handle that in code(or i am missing some setting of the gl841). The other thing you have seen is the half-resolution mode, used for greater speed when doing lower(i.E. not full) resolutions. How do you explain yhat with half resolution the image seems to be grayscale and without it seems to be lineart ? If you look closely, you see that the image is not exactly lineart. When doing half resolution, the sensitivity of the scanner sensor changes, and thus needs a different afe setup. That should be handled gracefully by the offset/gain calibration, once those are working. Subsidary question : what is the small white (perhaps black) rectangle in the middle up off page (for calibration) ? That may be a small metal clamp holding the glass or the calibration strip. That is the black(i.E. white) part at the very top. Under this small rectangle I have a vertical more clear line(same height). Is it because I need to tweek calibration area (without this small rectangle) ? To summarize, it is a good idea to have bit 4 on, bit 5 is the half resolution switch. I'd put 0x10 into the 0x6c gpio register. As for the calibration area, you will need to change some code: * comment out genesys_gl841.c:4220:(line numbers may differ) status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/ * the same for genesys_gl841.c:4821: status = gl841_feed(dev, 280);/*feed to white strip. canon lide 35 only.*/ When I comment out these lines the result is very bad (sample http://ggastebois.free.fr/lide90_snoop/toto_10_0_0_comment.jpg) then you can try what happens when you turn on the led_calibration and the coarse_gain_calibration. offset_calibration needs a bit more changes. i think i am having the code needed lying around somewhere. essentially, the offset calibration needs to be done with leds off. the shading calibration does need even more changes. Where to find led_calibration, coarse_gain_calibration ? How to turn them on ? For personnal information : what is shading calibration They are called by genesys_flatbed_calibration, i think i requested to comment them out earlier. OK, sorry, I did that some days ago. My last mail and sample images were WITH led_calibration and coarse_gain_calibration. There are three things to calibrate for: 1) the mapping from sensor voltages to numbers, to not lose color space by clipping lower brightness to 0 or higher brightness to 65535. ideally, you don't ever see 0 or 65535 from the afe. This is mainly the job of offset/gain calibration, but the led-exposure is a factor to this. 2) the color intensities relative to each other. We try to get each colored LED to lead to similar voltages in the sensor during its exposure. This is calibrated by led_calibration 3) Variations between the sensor cells. each sensor cell has it's own sensitivity and black voltage, so there needs to be a per-pixel-correction. This is done by shading_calibration. Additionally, the shading_calibration is by-color, so this is the place where we map each color channel to the correct range, as the led_calibration is not that exact. Additionally, if you can't get the afe to switch the sign, you need to do that in the calibration functions(i.E. 65535-value). Only in calibration function ? For now, that should be enough. We are not interested in the actual output image, yet. Regards, Pierre Regards Guillaume Regards, Pierre Regards Guillaume
[sane-devel] Canon LiDE 90
Hi Guillaume, Guillaume Gastebois schrieb: Hello, Why calibration is so long (~50/60s) ? It is probably failing. Should take about 3-5 seconds. Look at the logs, the calculated averages and calibration are dumped there. What are /* Start of white strip in mm (y) */ and /* Start of black mark in mm (x) */ in genesys_devices.c ? Those are configuration values for calibration steps. I don't know if any of these are currently used or if the values are hardcoded. I think the start-of-black-mark is used to detect the beginning of the document area for some gl646 scanners. The start-of-white-strip was once used in shading calibration. Currently, the shading calibration is setup for a calibration area looking like this: home position + ! black area + ! white area + The border between black area and white area is autodetected per pixel, as the border is usually not straight. You scanner seems to offer only a white area, so we will need to do shading calibration differently. My current idea is this: * always gather data on a white area * for black data, reduce the led exposure time to the minimum(0x101, those registers cannot be set to 0. per byte.). * for white data, use the normal exposure times I tried something like this for offset calibration, to see if there is any difference between white area+0x101 exposure time and black area+normal exposure time. There was no difference in the final images, and i think the resulting calibration was the same as well. Regarding the log file you said : W ! 0x23 ! 0x050 ! dac value rgb(offset value) W ! 0x2b ! 0x028 ! pga gain rgb But on debug, I see that these two registers are never written. 0x23 and 0x2b are merely convenience registers. Writing to 0x23 and 0x2b is equivalent to a write to each of 0x20-0x22 and 0x28-0x2a. For cis-sensors, there is only one channel used, so we could get away with only two registers writes(for the correct channel or 0x23/0x2b), but this won't work for ccd-sensors. Another thing : when scaning in color the leds are blue I'd expect a shade of white, perhaps blueish. my scanner does a magentaish white. You may also see the single colors when quickly moving your eyes relatively to the scanner. Regards, Pierre
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'karl-heinzbaumbach at arcor.de' 2. Manufacturer (e.g. Mustek): 'Epson Stylus DX 4050' 3. Model name (e.g. ScanExpress 1200UB): 'All in One' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '' 6. Product id (e.g. 0x0002): '' 7. Chipset (e.g. lm9831): '' 8. Comments (e.g. similar to Mustek 1234): '' 9. Data (e.g. sane-find-scanner -v -v): ''
[sane-devel] scg
I have a Sun Ultra 2 running Solaris 8 in 64-bit mode. My scanner is a Microtek Scanmaker E3 with a SCSI Interface I have the Scanner connected to a second SCSI card (sbus). (Not the built-in one) When I run probe-scsi-all, ok probe-scsi-all Target 4scanner/sbus at 1f,0/dma at 3,81000/esp at 3,8000 Unit 0 I downloaded the general scsi driver: scg-sparc-sol2.7 and copied it to /kernel/drv/scg Downloaded SCHILYscg.sparc.tar.Z uncompress SCHILYscg.sparc.tar.Z tar xpvf SCHILYscg.sparc.tar pkgadd -d ./ SCHILYscg Answered 'No' when asked to overwrite /kernel/drv/scg For 64-bit: Downloaded scg-sparcv9-sol2.7.beta and copied it to /kernel/drv/sparcv9/scg Did a reconfiguration reboot: reboot -- -r After I did the reconfiguration reboot, I did a # modinfo | grep scg Got nothing. Tried /opt/csw/bin/sane-find-scanner: # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. One thing I am wondering about is /kernel/drv/scg.conf I tried changing it to the following: # # Copyright (c) 1992, by Sun Microsystems, Inc. # #ident @(#)sd.conf1.1 95/05/03 J. Schilling name=scg class=scsi target=4 lun=0; # I am wondering if this is correct. # ./sane-find-scanner -v This is sane-find-scanner from sane-backends 1.0.18 # 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/scg0a... failed to open (Invalid argument) checking /dev/scg0b... failed to open (Invalid argument) checking /dev/scg0c... failed to open (Invalid argument) checking /dev/scg0d... failed to open (Invalid argument) checking /dev/scg0e... failed to open (Invalid argument) checking /dev/scg0f... failed to open (Invalid argument) checking /dev/scg0g... failed to open (Invalid argument) checking /dev/scg1a... failed to open (Invalid argument) checking /dev/scg1b... failed to open (Invalid argument) checking /dev/scg1c... failed to open (Invalid argument) checking /dev/scg1d... failed to open (Invalid argument) checking /dev/scg1e... failed to open (Invalid argument) checking /dev/scg1f... failed to open (Invalid argument) checking /dev/scg1g... failed to open (Invalid argument) checking /dev/scg2a... failed to open (Invalid argument) checking /dev/scg2b... failed to open (Invalid argument) checking /dev/scg2c... failed to open (Invalid argument) checking /dev/scg2d... failed to open (Invalid argument) checking /dev/scg2e... failed to open (Invalid argument) checking /dev/scg2f... failed to open (Invalid argument) checking /dev/scg2g... failed to open (Invalid argument) checking /dev/sg/0... failed to open (Invalid argument) checking /dev/sg/1... failed to open (Invalid argument) checking /dev/sg/2... failed to open (Invalid argument) checking /dev/sg/3... failed to open (Invalid argument) checking /dev/sg/4... failed to open (Invalid argument) checking /dev/sg/5... failed to open (Invalid argument) checking /dev/sg/6... failed to open (Invalid argument) cannot stat `/dev/scsi/scanner/' (No such file or directory) Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
[sane-devel] scg SCSI Driver for Solaris
Hello, I have a Sun Ultra 2 running Solaris 8 in 64-bit mode. My scanner is a Microtek Scanmaker E3 with a SCSI Interface I have the Scanner connected to a second SCSI card (sbus). (Not the built-in one) When I run probe-scsi-all, ok probe-scsi-all Target 4scanner /sbus at 1f,0/dma at 3,81000/esp at 3,8000 Unit 0 I downloaded the general scsi driver (From ftp.berlios.de): scg-sparc-sol2.7 and copied it to /kernel/drv/scg Downloaded SCHILYscg.sparc.tar.Z uncompress SCHILYscg.sparc.tar.Z tar xpvf SCHILYscg.sparc.tar pkgadd -d ./ SCHILYscg Answered 'No' when asked to overwrite /kernel/drv/scg For 64-bit part of it: Downloaded scg-sparcv9-sol2.7.beta and copied it to /kernel/drv/sparcv9/scg Did a reconfiguration reboot: reboot -- -r After I did the reconfiguration reboot, I did a # modinfo | grep scg Got nothing. Tried /opt/csw/bin/sane-find-scanner: # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. One thing I am wondering about is /kernel/drv/scg.conf I tried changing it to the following: # # Copyright (c) 1992, by Sun Microsystems, Inc. # #ident @(#)sd.conf1.1 95/05/03 J. Schilling name=scg class=scsi target=4 lun=0; # I am wondering if this is correct. # ./sane-find-scanner -v This is sane-find-scanner from sane-backends 1.0.18 # 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/scg0a... failed to open (Invalid argument) checking /dev/scg0b... failed to open (Invalid argument) checking /dev/scg0c... failed to open (Invalid argument) checking /dev/scg0d... failed to open (Invalid argument) checking /dev/scg0e... failed to open (Invalid argument) checking /dev/scg0f... failed to open (Invalid argument) checking /dev/scg0g... failed to open (Invalid argument) checking /dev/scg1a... failed to open (Invalid argument) checking /dev/scg1b... failed to open (Invalid argument) checking /dev/scg1c... failed to open (Invalid argument) checking /dev/scg1d... failed to open (Invalid argument) checking /dev/scg1e... failed to open (Invalid argument) checking /dev/scg1f... failed to open (Invalid argument) checking /dev/scg1g... failed to open (Invalid argument) checking /dev/scg2a... failed to open (Invalid argument) checking /dev/scg2b... failed to open (Invalid argument) checking /dev/scg2c... failed to open (Invalid argument) checking /dev/scg2d... failed to open (Invalid argument) checking /dev/scg2e... failed to open (Invalid argument) checking /dev/scg2f... failed to open (Invalid argument) checking /dev/scg2g... failed to open (Invalid argument) checking /dev/sg/0... failed to open (Invalid argument) checking /dev/sg/1... failed to open (Invalid argument) checking /dev/sg/2... failed to open (Invalid argument) checking /dev/sg/3... failed to open (Invalid argument) checking /dev/sg/4... failed to open (Invalid argument) checking /dev/sg/5... failed to open (Invalid argument) checking /dev/sg/6... failed to open (Invalid argument) cannot stat `/dev/scsi/scanner/' (No such file or directory) cannot stat `/dev/scsi/processor/' (No such file or directory) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. Thanks, stephen Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
[sane-devel] Visioneer 6100 usb
I have spent hours trying to get this scanner to work with Ubuntu. Can anyone please help me? Thanks! ,-._,-. \/)(\/ (:o:) (!)
