[sane-devel] HP scanjet 2400
Hello, there was a patch (by Luke) recently that allowed warming up to work for the HP2400. The following function in execution path to fix is gl646_search_start_position() . A way to do it is to run the backend with all the debug, and compare this output with what it does under windows. Then correct the function until the picture scanned to locate the start of scanning area matches the one from windows USB log. From time to time I upgrade the document at http://stef.dev.free.fr/sane/genesys with informations on the genesys backend and how to modify it. It explains also how to work with windows USB logs. The next major hurdle one has to overcome for the 2400 if the creation of the slope tables that drive the stepper motor. The HP2300 and MD6471 code uses an 'old' method with some magic constants to generate slope tables matching those in logs, but gl841 based scanners code uses a newer and better function that is based on the start and cruise speed needed. There must also be some register tweaking to do, but this is easy (places testing for a HP2300 will give you hints) to do with a simple compare to windows log. Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Le mardi 11 septembre 2007, Christian Arnold a ?crit?: F7Y24 Hello, how did you find that IC1 and IC3 are genesys part ? I am quite lost finding them (while also found that link to the Canon D1250U2, which seems an interesting thing to dig). Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Le lundi 10 septembre 2007, Christian Arnold a ?crit?: St?phane VOLTZ schrieb: Hello, I installed and have a quick look to the driver. Nothing definitive. For the firmware, you effectively only have to record what happens when you un- and replug the powercable. Regards, Stef Hi! I have recorded the replug of the power cable. Logs: - Compressed: http://files.arctic-media.de/log-replugged/usbsnoop.zip [ 904 KB] - Uncompressed http://files.arctic-media.de/log-replugged/usbsnoop.log [36,53 MB] The present status never (5 minutes?) changed to yes in the list, so I clicked uninstall and waited until log size wasn't increasing anymore. Regards Christian Hello, I don't see any bulk write that could be a firmware download in the log. I don't know what chip it could be. Opening the scanner may be your best option. Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Le dimanche 9 septembre 2007, Christian Arnold a ?crit?: St?phane VOLTZ schrieb: before opening the scanner, could you look at the driver's files under windows ? They may have some informations in it about the hardware (files name, strings in dll or other files). If you want a look at the driver files, you can download them directly from Canon. German: http://de.software.canon-europe.com/files/soft6081/software/S3315dex.exe Englisch: http://software.canon-europe.com/files/soft6079/software/S3315enx.exe The S3315**x.exe is a zip file, just like the SetupSG.exe inside it. One interesting hint would be finding if it loads a firmware or not. You may record USB activity with usb snoop of the unplugging/replugging (with also powering it off) of your scanner. If there are some big bulk out write, this should be a firmware download. How do I do this? The same way I recorded the previous log? This time with un- and replugging the powercable? Regards Christian Hello, I installed and have a quick look to the driver. Nothing definitive. For the firmware, you effectively only have to record what happens when you un- and replug the powercable. Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Hello, after digging a little more, I can't recognize a GL646 from the usbsnoop log. When looking at the 3000f driver, it looks really close to the 3200f. I think it is the way that should be explored. The USB descriptor is really close, the PID of the 3200f is the one following the 3000f. Driver wise, they are also really close. One interesting hint would be finding if it loads a firmware or not. You may record USB activity with usb snoop of the unplugging/replugging (with also powering it off) of your scanner. If there are some big bulk out write, this should be a firmware download. Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Hi! Thanks for helping! I tried to open the case of the scanner. I was really gently and I couldn't open it! I used a plectrum but in the front there has to be another locking. Maybe i'll try again tomorrow, then I'll be able to tell you, what chips are in that scanner! Regards Christian Hello, before opening the scanner, could you look at the driver's files under windows ? They may have some informations in it about the hardware (files name, strings in dll or other files). Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Le mardi 4 septembre 2007, St?phane VOLTZ a ?crit?: Le mardi 4 septembre 2007, Christian Arnold a ?crit?: St?phane VOLTZ schrieb: Hello, my tool of choice to record USB traffic under windows is SniffUSB (you can grab it at http://stef.dev.free.fr/sane/outils/index.html). Record a simple session under windows, like doing a color preview. Once you have made a usbsnoop.log , and compressed it, you can put somewhere or even send it to me directly. I'll have a look at it to see if it is really a GL646 based scanner. The http://www.sane-project.org/unsupported/canon-3000.html doesn't give a definitive answer, like the log will do. Regards, Stef Hi! I recorded a colorpreview. About 33 MB of information was put into the logfile. You can grab it uncompressed from http://files.arctic-media.de/usbsnoop.log or zip-compressed (4,78 MB) from http://files.arctic-media.de/usbsnoop.zip Hope my scanner has a Genesys chip inside! Regards Christian Hello, I've run my decoding scripts on it. It looks a genesys chip (some register and ata write are recognized), but it isn't a GL646 one, nor a GL841. Some registers index aren't known for any of those. Maybe a newer genesys GLxxx chip ? Regards, Stef Hum, after further digging, and infding some mail in the list, it may still be a GL646 but behind a different chip (GL660?). I'll look into it more deeply. Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Le mardi 4 septembre 2007, Christian Arnold a ?crit?: St?phane VOLTZ schrieb: Hello, my tool of choice to record USB traffic under windows is SniffUSB (you can grab it at http://stef.dev.free.fr/sane/outils/index.html). Record a simple session under windows, like doing a color preview. Once you have made a usbsnoop.log , and compressed it, you can put somewhere or even send it to me directly. I'll have a look at it to see if it is really a GL646 based scanner. The http://www.sane-project.org/unsupported/canon-3000.html doesn't give a definitive answer, like the log will do. Regards, Stef Hi! I recorded a colorpreview. About 33 MB of information was put into the logfile. You can grab it uncompressed from http://files.arctic-media.de/usbsnoop.log or zip-compressed (4,78 MB) from http://files.arctic-media.de/usbsnoop.zip Hope my scanner has a Genesys chip inside! Regards Christian Hello, I've run my decoding scripts on it. It looks a genesys chip (some register and ata write are recognized), but it isn't a GL646 one, nor a GL841. Some registers index aren't known for any of those. Maybe a newer genesys GLxxx chip ? Regards, Stef
[sane-devel] Will the CanonScan 3000 Series be supported?
Le lundi 3 septembre 2007, Christian Arnold a ?crit?: Hello! How do I record this log? I'm pretty shure that the CanoScan 3000 Series should work after some coding with the genesys drivers, because of this SANE unsupported device information page http://www.sane-project.org/unsupported/canon-3000.html It seems not many sane-users have this scanner. But I have and I am willing to make it supported! If you need any information from the scanner, tell me and I try to provide it! Hope it'll work someday! Regards Christian Hello, my tool of choice to record USB traffic under windows is SniffUSB (you can grab it at http://stef.dev.free.fr/sane/outils/index.html). Record a simple session under windows, like doing a color preview. Once you have made a usbsnoop.log , and compressed it, you can put somewhere or even send it to me directly. I'll have a look at it to see if it is really a GL646 based scanner. The http://www.sane-project.org/unsupported/canon-3000.html doesn't give a definitive answer, like the log will do. Regards, Stef
[sane-devel] Experimental lexmark backend inclusion in regular CVS
Le jeudi 30 ao?t 2007, Fred Odendaal a ?crit?: Stef, I can't build the backend with the latest CVS checkout of the experimental code. Here is the error message I get: gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -D_REENTRANT -I/usr/include/gphoto2 -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DPATH_SANE_LOCK_DIR=/usr/local/var/lock/sane -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=lexmark-x1100 -DLIBDIR=/usr/local/lib/sane lexmark-x1100.c -fPIC -DPIC -o .libs/lexmark-x1100.o In file included from ../include/sane/sanei_backend.h:29, from lexmark-x1100.c:60: ../include/sane/sanei_debug.h:88: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_debug.h:106: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token In file included from lexmark-x1100.c:60: ../include/sane/sanei_backend.h:110: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:111: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:112: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:114: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:115: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:117: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:118: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:119: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:121: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:122: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:123: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:124: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token ../include/sane/sanei_backend.h:125: error: expected '=', ',', ';', 'asm' or '__attribute__' before '-' token lexmark-x1100.c: In function 'x1100_usb_bulk_write': lexmark-x1100.c:186: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c:186: error: (Each undeclared identifier is reported only once lexmark-x1100.c:186: error: for each function it appears in.) lexmark-x1100.c:186: warning: implicit declaration of function 'x1100_call' lexmark-x1100.c: In function 'x1100_usb_bulk_read': lexmark-x1100.c:204: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'sanei_lexmark_x1100_open_device': lexmark-x1100.c:275: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'sanei_lexmark_x1100_search_home_fwd': lexmark-x1100.c:631: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'sanei_lexmark_x1100_search_home_bwd': lexmark-x1100.c:846: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'x1100_set_scan_area': lexmark-x1100.c:1141: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'sanei_lexmark_x1100_set_scan_regs': lexmark-x1100.c:1483: error: 'Lexmark_Device' has no member named 'pixel_height' lexmark-x1100.c:1484: error: 'Lexmark_Device' has no member named 'pixel_width' lexmark-x1100.c:1489: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'sanei_lexmark_x1100_start_scan': lexmark-x1100.c:2259: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'sanei_lexmark_x1100_read_scan_data': lexmark-x1100.c:2344: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'x1100_rewind': lexmark-x1100.c:2516: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c:2575: error: 'Lexmark_Device' has no member named 'pixel_height' lexmark-x1100.c: In function 'read_buffer_init': lexmark-x1100.c:2645: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'read_buffer_free': lexmark-x1100.c:2679: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'read_buffer_bytes_available': lexmark-x1100.c:2693: error: 'sanei_debug_lexmark' undeclared (first use in this function) lexmark-x1100.c: In function 'read_buffer_add_bit_lineart': lexmark-x1100.c:2819: error:
[sane-devel] Experimental lexmark backend inclusion in regular CVS
Hello, the experimental lexmark backend is now quite in a good shape. It brings other the current backend: - 2 new USB id support (Dell A920 and Lexmark X12xx models) - add support for new X11xx models - add arbitrary scan area selection - offset and gain calibration - software shading correction It has been tested on A920, X1200 in USB1.1 and newer X1100 model. Only the orignal model supported by the current backend should need some testing. So I'd like to know what everybody, and especially Fred, think about moving the experimental backend into regular CVS. Regards, Stef
[sane-devel] [sane-commit] CVS update of (16 files)
Hello, I have mistakenly commit some experimental changes in the main tree. I have reverted them back: wrong version pushed - previous one sane-backends/backend/Makefile.in1.142 - 1.141 sane-backends/backend/lexmark-x1100.c 1.3 - 1.2 sane-backends/backend/lexmark.c 1.3 - 1.2 sane-backends/backend/lexmark.h 1.3 - 1.2 sane-backends/backend/lexmark.conf.in 1.2 - 1.1 sane-backends/doc/sane-lexmark.man1.6 - 1.5 Sorry for the inconvenience, Stef
[sane-devel] Intend to write driver(s)
Le samedi 4 ao?t 2007, Robert Brijder a ?crit?: Hi Leandro, Sorry for the very late reaction. I do have some information for you which may help. Look at the site http://zub.fei.tuke.sk/primax/ of Peter Popovec. It contains a sane backend for the E3 ASIC, which our scanners have. The only thing lacking in this backend is that it is for parallel port scanners and not for USB. Luckily, the chip which does the bridging of parallel port over USB is well known, it is the GeneSys Logic GL640. There are many duplicate implementations of this USB bridge already in the SANE backends, it appears to reside in at least 3 backends: genesys, canon630u, and u12. So I guess it wouldn't be hard to implement this in your sane backend. BTW: Does anybody know, Is there a good reason for implementing this chip this many times? Where is there an USB bridge in the genesys backend ? For the 2 others, I don't know. But you have two implementation where you can choose the best one. And may be separate it into a library to use for your future backend, and that maybe would let refactor the two other. It seems the modifications are mostly necessary in the port.c file (of the sane backend of Peter Popovec) to get it working. I guess there should be a USB version for the following functions. epp_off(); epp_read(); epp_read_one(); epp_write(); epp_write_one(); switcher_online (); switcher_offline (); The first five are not that hard I think, but I do not really have a clue yet how to do the last two functions. If we can get USB support working, at least 6 new devices would be supported. This would be nice. I contacted Peter Popovec, but since he does not have such a USB scanner he would rather not implemented this himself. I guess I answered your first question: we should edit the backend of Peter Popovec. The second question: I don't know if it is possible to damage the scanner. The third question: the backend of Peter Popovec does not seem to have any licencing issues, this in contrast to the viceo backend. All the best, Robert Regards, Stef
[sane-devel] help required to use umax astra 4100 on linux
Le jeudi 2 ao?t 2007, Siddharth Naik a ?crit?: Hi, Am not able to access Umax astra 2000p scanner on my linux machines its not getting detected. Where as it gets detected on windows machine. Am using parallel port Scanner. When I issue scanimmage -l It says no sane devices found. SIDDHARTH NAIK, PES AIROLI, EXT 3805. Tough times never last but tough men do http://www.patni.com World-Wide Partnerships. World-Class Solutions. _ This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netadmin at patni.com and delete this mail. _ Hello, the umax_pp backend which handles the 2000P is disabled by default in dll.conf . Check it is enabled. Alos check if the user running the test has the rights to acces the parallel port. Regards, Stef
[sane-devel] convert standalone programa to backend
Le jeudi 26 juillet 2007, Miguel a ?crit?: I've working with the kodak i1320, making a standalone program to scan, based on sniffing the usb port. In the actual state the program scans and saves the images (both sides), at the same speed than in windows, and the next step for me is convert it to a sane backend, using sane-usb. here is where i need some help. How do i include the .c and .h files in the makefile? Which sane headers should i include? Do i have to modify any where else in sane? i have some questions on using sane-usb, mainly regarding the attach function callback. I can provide the source for the scanning program, if you think it is useful, and i have the intention to submit the backend to the sane project. Your help will be greatly appreciated -- Miguel Ruiz Velasco Hello, Ive done such a thing with th umax_pp backend. The scanning program is in the tools subdirectory of SANE, and I turned it into a backend (umax_pp). This will give an idea of one way of doing what you want. Regards, Stef
[sane-devel] Error Messages
Le jeudi 19 juillet 2007, Edward Barton a ?crit?: Trying to get a Lexmark scanner portion of a X1185 to work in Ubuntu 6.06 with Sane. Consistently get 3 error messages as follows: a) Error during save: Broken pipes b) Error during save: Success c) Failed to execute printer command: lpr Have no idea of the meanings! Any idea's will be appreciated Hello, I didn't answered earlier since I was on hollydays. The X1185 model is only supported with the experimental version of the lexmark backend. You can get it at http://stef.dev.free.fr/sane/lexmark . This is a testing version that let you test scanning. It is allready working for at least one person. Once it will work for you, I'll consider moving this experimental version into regular sane backends. Let me know if it works or any problem you could have. Regards, Stef
[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] 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
[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] Adding Scanner to Backend Configuration
Le mardi 15 mai 2007, Hugh McMaster a ?crit?: Hi Gerald, On 12/05/07, Gerald Murray wrote: The chipset in the Canon Lide 70 is not yet known, but it did not respond positively to gl841 or gl646, so it is will not at present work with the genesys backend. It has only 2 bulk endpoints, but no isosynchronous endpoint, so it is different. Some work is required to identify the chip, and the protocol. Using usbsnoop on a small scan may provide helpful information. In any case, quite a bit of work lies between now and a successful sane scan. I suggest obtaining a usbsnoop log and/or identifying the chipset. The recompile is not likely to work or provide useful information, in my humble opinion. Someone needs to initiage and carry that project forward into development. Where should I submit the usbsnoop log to? Hugh Hello, you can either put it on some site and give us the URL, or send it directly to me if it is smaller than about 10MB when compressed. I'll try to look if it is close the gl646. Regards, Stef
[sane-devel] Problem with alioth, additional problem with Lexmark X1170
Le samedi 5 mai 2007, Stefan G?ttsche a ?crit?: Hi, I'm unsure if I am correct in posting this here. To introduce myself shortly, I am a german living in France, and I run openSUSE Linux 10.2, KDE 3.5.6. First of all, I've got a problem with the sane-project website, or more precisely alioth. I wanted to report a bug, but a button to report bugs was nowhere to be seen. I figured that I have to create an account for just this one bug, and proceeded to registration. After quite a bit of information about me I finally got the email, clicked, and got the error message : Alioth cannot connect to database on an otherwise blank page. Now, I should register that as a website bug, but since I need to log in for the bugtracker I simply can't. I don't know if the server is down for maintenance, or something else along that line, I'll try again later. Second, the reason for my bug report : I own a Lexmark X1170 printer/scanner, and the printer works just fine. I used SANE to install the scanner, and upon testing, something goes majorly wrong : Instead of moving the scanning unit towards the glass window it starts moving the unit -in the other direction- ! Since there is a point the mechanic inside can't overcome, the motor starts to whine under torture, and after two or three seconds the scanner just stops. The scanner is correctly detected by sane using scanimage to list the scanners. I have tried and experienced this problem with Xsane, scanimage and Kooka, which exhausts all the frontends I have. I conclude that this must be a problem inside Sane or with my hardware, although the last time I scanned under Windows it functioned normally. I will check that out though as soon as I have some time to boot up windows XP. I have not tried to further deepen the diagnostic, as the scanner does this at every attempt to scan or preview, and the unit starts smelling a bit of overheated electronics when trying. I don't want to destroy the scanner motor. Any advice on this would be very appreciated, as it is the only (rare) task on the computer left for which I have to boot Win XP now. I don't like to boot it anymore, and until now I am very happy with OpenSuse :) Thanks Stefan Hello, there are at least 2 variant of X11xx models. The regular lexmark backend only handles one. The experimental now fully support both (and color scans for X1xx models). You can either get the code from the cvs/experimental area or get a full patched source archive at http://stef.dev.free.fr/sane/lexmark . Once this version will be regression tested on A920, I'm considering removing all debugging code and moving it to the regular cvs. Regards, Stef
[sane-devel] [RFC] DBG levels
Hello I found myself defining debugging levels quite a few time, and not allways in a consistent manner. So I'm thinking that having well knowns debugging levels defined in sanei_debug.h would be a good idea. However, it seems that after a quick grep for DBG_ in .h that there are at least 2 different usage: increasing debugging levels (most backends) and 'bitmap' (at least one backend): DBG_ALL 0xFF DBG_ASIC6 DBG_ASSERT 1 DBG_CRIT0 DBG_data8 DBG_DBG 10 DBG_DET 4 DBG_ERR 1 DBG_ERR 16 DBG_error0 0 DBG_error 1 DBG_FUNC5 DBG_HELPERS 0x08 DBG_HIGH0x04 DBG_info2 6 DBG_INFO3 DBG_info4 DBG_info5 DBG_init2 DBG_inquiry 4 DBG_IO 0x40 DBG_io2 7 DBG_io 6 DBG_IOF 0x80 DBG_LOW 0x01 DBG_MEDIUM 0x02 DBG_MSG 32 DBG_proc5 DBG_proc7 DBG_read8 DBG_sane_info 12 DBG_sane_init 10 DBG_sane_option 13 DBG_sane_proc 11 DBG_SCAN0x20 DBG_sense 2 DBG_TIMEOUT 0x10 DBG_WARN2 DBG_warn3 DBG_warning 3 IMHO, having only one way of defining debugging levels would be great, but I haven't set my mind on the best approach. Any thoughts ? Regards, Stef
[sane-devel] sane-commit working ?
Le mardi 17 avril 2007, m. allan noah a ?crit?: On 4/16/07, m. allan noah kitno...@gmail.com wrote: i dont subscribe to sane-commit, but i notice that cvs is tossing several errors every time i commit a change. i think the scripts that feed sane-commit are broken... seems to be an incompatibility between the newer cvs (which was pretending to be the old cvs) and the program cvslog. also looked like there had been some local changes in CVSROOT that were not checked in, so i tried to preserve those. i converted to new loginfo format, and that seems to have fixed it. however, alioth seems broken, so i cant be sure that is the correct url for cvsweb. allan Thanks, I'm receiving commit messages again. Regards, Stef
[sane-devel] sane-commit working ?
Hello, I haven't received any mail from sane-commit since 15/01. I've checked my membership and options, everythings seems right. Has anyone received mail from sane-commit ? Regards, Stef
[sane-devel] Tevion MD90092 flat bed scanner, started to analyze
Le mardi 3 avril 2007, Jochen Lauber a ?crit?: Hello to everyone, I bought a TEVION MD90092 flatbed scanner at ALDI Sued two weeks ago. Since no support for Linux is included, I started to write a backend derived from the mustek_usb2. My Email with information request to the www.MEDION.de support was automatically answered with a not helpfull FAQ list, and since then I wait for a further answer. (The hope dies at last). With the USBsniffer under Windows XP I found out, that there is a lot of data traffic to the scanner beforer the slider moves at all. There is usually quite a lot of activity before scanning. Things like verifying that scanning head is at home, doing a scan to locate geometric patterns 'under the roof' to compute physical scan area start, sensor calibration (offsets, gains and shading) are done before the effective scan. Also constant button polling may end up filling logs. NOTE: A newer DbgViewer.exe can be downloaded at microsoft , which supports also XP. However the USB trace with these tools is incomplete, data gets lost. - so I will have to change the USBsniffer as well - OR - Who could send me a tool for complete USB traces? I have satisfying results with the usbsniff program. I have mirrored the latest version at http//stef.dev.free.fr/sane/outils/index.html . There some awk/perl scripts that turn produced logs in more compact forms. They usually discard scanned data, which I think is a drawback. In case you want, I can send or post my own version of the 'parse1.awk' script which keep everything it can. Regards, Stef
[sane-devel] hp2400 some problem
Le mercredi 28 mars 2007, ??? ??? ??? a ?crit?: Good day, I have some problem with you patch for sane-backends-1.0.17 pre-alpha-scanner.tar.bz2. After patching, my linux find the scaner, beginning scan, but not stopping. It knock some times in end and then return. In finish I kill process and result file is corrupt and no one application read it. I think is error in the long scan. Please, help my. I think if i change some parametrs, it will scan. Kernel is 2.6.17-1.2157.1aspsmp, the system is ASP Linux 11.2 __ www.newmail.ru -- ? . HP2400 isn't yet supported by the genesys backend. Some people started to look into this, but no progress have been done lately. Regards, Stef
[sane-devel] lexmark X1150
Le dimanche 18 mars 2007, Fred Odendaal a ?crit?: Probably a permissions thing. I experienced a similar thing when upgrading to FC6. If you can see your scanner as root then for sure that is what the problem is. The workaround is to add a group called scanner and add the group to the users who want to scan. Then you can scan as a regular user. Note, the lexmark backend is incomplete. It lacks colour calibration and darkness compensation (amongst other things :-) ). There is a fellow named Stephan Voltz, who has created an experimental backend and he is trying to add these things. regards, Fred O. Mark Fonnemann wrote: Hello- Hello, you can get a source archive patched with an experimental version of the lexmark backend at http://stef.dev.free.fr/sane/lexmark . It should be able to detect your scanner and do 75 dpi color scans. BTW, Fred, if it happens you have the time needed to record the usbsnoop windows log of a preview right after plug-in your scanner. I'd be very grateful if you send me this log. The X1185/X1190 have the same usb id than your model but work slightly differently. I have to find how to differentiate them from your model. Regards, Stef
[sane-devel] lexmark x1190 doing the funky chicken
Hello, the current backend only handles early X1100 models. It is allready known that X1185 models can't work with it. I am currently working on an experimental version of the lexmark backend. Currently, it detects X1185 variants (and X1200 models) and is able to do 75 dpi color scans. What is still missing is tuning the color calibration and add other dpi and gray scans. You can test this work in progress with the source archive you can get at http://stef.dev.free.fr/sane/lexmark . You'll have to recompile it (just type make in the lexmar_testing/sane-backends-1.0.18 subdirectory). Then you can run the list.sh script to see if your scanner is detected, then the scan.sh which will try to do a color preview. This test will produce a scan.log and a scan.pnm files in lexmark_testing/sane-backends-1.0.18/backend Please send them to me so I can fix any bugs, and validate the latest changes (since I've no device to test). Regards, Stef
[sane-devel] Hello!
Le jeudi 8 mars 2007, Daniel Padula a ?crit?: My name is Daniel, first of all, I am sorry for my english, I am from argentina. I am working on a linux distribution and I need to make Lexmark x1270 work, using Debian Testing. When I plug it, its detected by sane as 1100 series, and when I try to scan, its seems that try to move itself to a wrong side and even I cannot turn it off, it hang up, I have to turn it off by unplugging. How can I make it work ? Is it possible? Any suggestion is accepted. I really appreciate your help. Daniel Padula Hello, I am currently working to add support to X1200 models in the experimental version of the lexmark backend. I excpect to put a version able to park head and do a color preview by the start of next week. Regards, Stef
[sane-devel] Can't use Scanjet 3200c
Hi Stef, I removed the # from the dll.conf file, and from the dll.conf.rpmsave file and when I do scanimage -L it says: [umax_pp_low] sanei_umax_pp_InitPort cannot use direct hardware access [umax_pp_low] if not compiled with --enable-parport-directio 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). What do I have to do? Thank you for helping It seems the ppdev character device isn't working, or the backend is configured to use direct hardware access, which isn't compiled in. Check that th ppdev kernel module is loaded and that your user account has rights to access the /dev/parport0 device. Then edit umax_pp.conf (in the same directory than dll.conf) and change the line: port some-value to: port /dev/parport0 Things should get better. Regards, Stef
[sane-devel] Lexmark x1190 does the funky chicken
Le dimanche 4 mars 2007, Bryn Nobbs a ?crit?: Hi all, im having a problem with my Lexmark all-in-one X1190, I am under the impression the scanner is supported by the Lexmark backend but when I try to scan anything firstly the scanner makes a lot of noise for around 30 seconds, then it seems to find home and scan. The problem is that once it has scanned I just get a lot of coloured stripes as the output? It looks as though the scanner is working, but the backend isn't understanding what the scanner is sending to it.Also if I run scanimage -T the scanner doesn't seen to do anything and the program just hangs, if I press ctrl-c to quit it responds with trying to stop scanner and then just hangs again, a second ctrl-c is required to exit, then a reboot to get any functionality from the scanner again. Not sure if it helps but the printer works perfectly, in fact its better than it was under windows. I have included the output of scanimage -V if it helps, but I'm at a loss! # scanimage -V scanimage (sane-backends) 1.0.18; backend version 1.0.18 also, not sure if this helps either, but im running Debian Unstable and have installed sane-utils and sanelibs-dev from the Unstable repository. The machine is a 266Mhz ARM based NSLU2 as advised by a user a long time ago, i have installed ubuntu 6.10 on my i386 based pc and i have the exact same results. i am willing to send any log files or additional information you may need. also im not a programmer but i know my way around linux ok (please note ok) so i am willing to help in any way possible. im also competent with a screwdriver so if you need any extra hardware info i can supply this too. cheers for an help anyone can give me! bryn Hello, the current lexmakr backend only supports the early X110 series model. I allready found that while having the same USB ID, the X1185 has a diffrent sensor, so current backend won't work. I'm currently modifying the lexmark backend to add support for X1185 and X1200, and also getting current X1100 color calibration right. You may try a snapshot of these current developpements. You can get pre-configured sources at http://stef.dev.free.fr/sane/lexmark . I expect this version to detect your scanner as a X1185, and be able to do a preview (only 75 dpi scans could be working), but with colours slightly wrong since colour calibration hasn't been tuned yet. regards, Stef
[sane-devel] Lexmark X1130 test
Le lundi 26 f?vrier 2007, Carlos a ?crit?: Hi I have a Lexmark X1130 AIO scanner-printer and Im glad to see there is a backend for this device. Ive tested it and the results are not so bad as the opinions in the sane page suggest. It needs some work with colors (maybe there is some way of calibrating it in Linux) and a couple of minor issues, but the average impression is quite good. Ive prepared a page with my tests for your information. You can find it at http://butterbrot.googlepages.com/lexmarkscanner I hope it will be useful for someone. I intend to improve it with more documentation in the future. Thanks a lot for your great work!! Hello, the current version of the lexmark backend doesn't od calibration and has fixed size area. I am currently working on an experimental version (which allready work for the Dell A920) that brings color calibration. However, to tune it for the X1135, I'd need an usbsniff log recorded under windows. There are a couple of pointer on how to do it at http://stef.dev.free.fr/sane/outils . What I need would be the log of a simple color preview at 75 dpi. The log is several MB but compresses well. You can either pu it on your site or send it to me. Regards, Stef
[sane-devel] HP scanjet 2400
Hello, I've set up a page with tools and doc at http://stef.dev.free.fr/sane/genesys which let you start up some work. I haven't got the log yet, since the time I created an email account to log in, the site is currently down. I'll try later to get it, so we know at which point the adaptation for the HP2400 will have to start. Regards, Stef
[sane-devel] HP scanjet 2400
Le lundi 12 f?vrier 2007, Emmanuel Counasse a ?crit?: Hi, I have activated debug information and attached to this mail the output of : scanimage -d genesys:libusb:001:005 2 debug.txt (see : http://www.sharebigfile.com/file/80076/debug-tar-bz2.html) The scanner has start its motor (make noise) but did not do anything, so I decided to stop scanimage by pressing CTRL+C because I don't want to damage my scanner's motor. What do you think about it ? You proposed me to send me scripts, documentation and log, in think it xould be ionteresting to look inside so you can send me them in private, thanks. Best regards. Hello, thanks for the data. I'll have it a look this week. I'll also post updated information. Meanwhile, you may have a look at the code via tools such as kscope to find all the occurences of the *_HP2300 defines where you'll have to modify code to handle the HP2400. Regards, Stef
[sane-devel] Result of SANE_DEBUG_UMAX_PP
Le mercredi 7 f?vrier 2007, adrian a ?crit?: Stef Thanks for prompt reply and thanks for the encouraging news. I was not looking forward to throwing out a perfectly good scanner! Results of your suggestions: [root@localhost adrian]# export -p declare -x SANE_DEBUG_UMAX_PP=255 declare -x SANE_DEBUG_UMAX_PP_LOW=255 [root@localhost adrian]# export SANE_DEBUG_UMAX_PP=255 [root@localhost adrian]# [root@localhost adrian]# export SANE_DEBUG_UMAX_PP_LOW=255 [root@localhost adrian]# [root@localhost adrian]# scanimage -L [sanei_debug] Setting debug level of umax_pp to 255. [umax_pp] init: SANE_Auth_Callback not supported (yet) ... [umax_pp] init: SANE v1.0.18, backend v1.0.604-dev [umax_pp] init: evaluating option option buffer 2097152 [umax_pp] init: option buffer 2097152 [umax_pp] init: option buffer 2097152 [umax_pp] init: setting global option buffer to 2097152 [umax_pp] init: don't know what to do with `device : /dev/parport0' [umax_pp] umax_pp_try_ports: trying port `/dev/parport0' [sanei_debug] Setting debug level of umax_pp_low to 255. [umax_pp_low] SANE_INB level 0 [umax_pp_low] sanei_umax_pp_InitPort(0x0,/dev/parport0) [umax_pp_low] parport modes: 47 [umax_pp_low] parport modes:PARPORT_MODE_EPP [umax_pp_low] umax_pp: ppdev couldn't negociate mode IEEE1284_MODE_EPP for '/dev/parport0' (ignored) [umax_pp_low] umax_pp: mode set to PARPORT_MODE_EPP for '/dev/parport0' [umax_pp_low] Using /dev/parport0 ... [umax_pp_low] status 120 doesn't match! umax_pp_low.c:5091 [umax_pp_low] No scanner detected by 'ringScanner(2,0)'... [umax_pp_low] status 120 doesn't match! umax_pp_low.c:5091 [umax_pp_low] No scanner detected by 'ringScanner(5,0)'... [umax_pp_low] status 120 doesn't match! umax_pp_low.c:5091 [umax_pp_low] No scanner detected by 'ringScanner(5,1)'... [umax_pp_low] status 120 doesn't match! umax_pp_low.c:5091 [umax_pp_low] No scanner detected by 'ringScanner(5,1)'... [umax_pp_low] No 1220P/2000P scanner detected by 'ringScanner()'... [umax_pp_low] ringScanner passed... [umax_pp_low] sendCommand(0x30) passed ... (umax_pp_low.c:7367) [umax_pp_low] sendCommand(0x00) passed... (umax_pp_low.c:7374) [umax_pp_low] status 126 doesn't match! umax_pp_low.c:5257 [umax_pp_low] testVersion(0) (umax_pp_low.c:7378) failed ... [umax_pp_low] testVersion(0) passed... [umax_pp_low] status 126 doesn't match! umax_pp_low.c:5257 [umax_pp_low] testVersion(1) failed (expected) ... (umax_pp_low.c:7385) [umax_pp_low] status 126 doesn't match! umax_pp_low.c:5257 [umax_pp_low] testVersion(0) (umax_pp_low.c:7394) failed ... [umax_pp_low] testVersion(0) passed... [umax_pp_low] status 126 doesn't match! umax_pp_low.c:5257 [umax_pp_low] testVersion(1) failed (expected) ... (umax_pp_low.c:7401) [umax_pp_low] sendCommand(0x40) passed... [umax_pp_low] sendCommand(0xE0) passed... [umax_pp_low] ClearRegister(0) passed... [umax_pp_low] SPPResetLPT() passed... [umax_pp_low] Found 0x77 expected 0xC7 (umax_pp_low.c:7474) [umax_pp_low] Trying 610p (umax_pp_low.c:7483) [umax_pp_low] sync610p failed (got 0x78 expected 0x38)! (umax_pp_low.c:3733) [umax_pp_low] sync610p failed! Scanner not present or powered off ... (umax_pp_low.c:6363) [umax_pp_low] initTransport610p() failed (umax_pp_low.c:6673) [umax_pp] attach: failed to probe scanner on /dev/parport0 [umax_pp] attach: couldn't attach to `/dev/parport0' (Error during device I/O) [umax_pp] umax_pp(v1.0.604-dev): line 254: debug exception [umax_pp] init: couldn't attach to port `/dev/parport0' [umax_pp] init: safe-auto attach failed ![umax_pp] init: don't know what to do with `astra 1220' [umax_pp] get_devices [umax_pp] unused arg: local_only = 0 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). [umax_pp] sane_exit: (...) Not sure what to make of the above . . . . Does it mean that parport0 is the incorrect address? Should I be using port 0x378 or port 0x38 Is safe-port auto more likely to work? What do you read? Adrian Hello, I think that the umax_pp.conf has some unexpected keyword in it (such as 'device'), hence the 'don't know what to do with ...' messages. You only need these 2 lines in it: option buffer 2097152 port safe-auto The log shows that parport communication is non-working. From your previous mail, I think your parallel port is OK: parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] ppdev: user-space parallel port driver: However, double check in BIOS that the parallel port settings are really these ones. You may force correct detection by giving the settings to the kernel module: options parport_pc io=0x378 irq=7 dma=none An other option would be
[sane-devel] Problem Detecting Scanner (HP3200C / Umax Astra 1220P) in Mandriva 2007 Cooker
Le mardi 6 f?vrier 2007, Adrian a ?crit?: Problem Detecting Scanner (HP3200C / Umax Astra 1220P) in Mandriva 2007 Scanner worked under Mandriva 2006 (kernel 2.6.12) but not under Mandriva 2007 Cooker (kernel 2.6.17) Extracted from output from dmesg: (snip) loop: loaded (max 8 devices, max 1 partitions per device) parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] ppdev: user-space parallel port driver Scanner is HP3200C / Umax Astra 1220P. Using Mandriva Hardware Configuration: configure scanner manually - results in message: Astra 1220P is configured and ready to use with Xsane or Kooka. Output from xsane: [root@localhost adrian]# xsane [umax_pp_low] sync610p failed (got 0x78 expected 0x38)! (umax_pp_low.c:3733) [umax_pp_low] sync610p failed! Scanner not present or powered off ... (umax_pp_low.c:6363) [umax_pp_low] initTransport610p() failed (umax_pp_low.c:6673 Output from kooka: [root@localhost /]# kooka kbuildsycoca running... KWrited - Listening on Device /dev/pts/6 [umax_pp_low] sync610p failed (got 0x78 expected 0x38)! (umax_pp_low.c:3733) [umax_pp_low] sync610p failed! Scanner not present or powered off ... (umax_pp_low.c:6363) [umax_pp_low] initTransport610p() failed (umax_pp_low.c:6673) /etc/sane.d/dll.conf: device: /dev/parport0 port safe-auto astra 1220 In /etc/sane.d/umax_pp.conf all are commented (#) except: net umax_pp If I uncomment test then test0 appears in xsane as available device, but not Umax 1220P!! Have tried resetting scanner but no effect. Can't think of anything else to try - am at my wits end. My ageing brain is going in cricles. Do I just give up and reload Mandriva 2006 as a last resort? Mandriva Club Forum moderator gave the following suggestions: Parallel port scanners have been reduced to lovely but non-functional desktop ornaments. I've tried many times to build a custom 2007 kernel that will bring mine to life again but no joy. Don't blame Mandriva. Apparently the kernel.org developers have thrown their PP scanners into the recycle bin. Mandriva's kernel dev's took pity on us and kept PP scanners on life-support long after other distros had already held a funeral and buried them. You can file a Bugzilla report and I'd even vote for it but don't hold your breath on getting resources assigned to this one. However, there may be a way we can hit this thing with the defibrillator one more time: Oh Danny...at one time, Svetljo did some magic to keep these scanners working. Do you by any chance know about those patches that used to be in mm? I think they were actually applied to the 2006 main kernel per this Bugzilla report: http://qa.mandriva.com/show_bug.cgi?id=16743 Perhaps they can be resurrected in mm? Can the same kernel patch/module that was used in Mandriva 2006 be loaded in current kernel in Mandriva 2007? If so where might I find the patch? The Bugzilla report mentioned above did not appear to point to any relevant patch. Hello, to see what's really going on do: export SANE_DEBUG_UMAX_PP=255 export SANE_DEBUG_UMAX_PP_LOW=255 and send the debug output of scanimage -L . Get sure that /dev/parport0 can be accessed read/write for the user that run the command. I wouldn't blame the kernel too fast. My HP3200C is currently working fine here on an ubuntu 6.10 . More this bug id 16743 is related to ppscsi devices, which are indeed orphaned, but the umax_pp is another thing. It only needs a working ppdev. Debug traces will tell what's going on. Regards, Stef
[sane-devel] Backend: lexmark (1.0-0, NEW!) x1150
Le vendredi 2 f?vrier 2007, fsl a ?crit?: Greetings. Just a quick note tested against my Lexmark x1150 the lexmark x1100 backend driver works well accept for one issue. When scanning as Lineart the image colors are inverted. Aka what should be white is black and what should be black is white. Is there a fix? MrFSL Hello, this issue is fixed in the experimental version of the lexmark backend. I'd be interesting if you give it a try. I've put up a SANE version reduced to the lexmark backend, with a couple of scripts to run it without installing it system-wide. It is at http://stef.dev.free.fr/sane/lexmark/ . If you have some free time I'd appreciate if you try it. Especially I'd like to have the log file done by the 'scan.sh' script that has to be run from the top directory of the archive. Another way to fix would be to get sources of the regular SANE backends and change the line (in lexmark-x1100.c, lne 2793) from: if (*byte_pointer = threshold) to if (*byte_pointer = threshold) and recompile/install the backend. Regards, Stef
[sane-devel] Lexmark x1185 Can't Find Home
Le lundi 29 janvier 2007, Robert Price a ?crit?: Thanks. Using this package, the scanner tries to back up past the physical end, then moves forward a bit, then tries backing up again repeatedly till killed. While this is happening, the debug output repeats: [lexmark] x1100_usb_bulk_read: returned size = 3 (required 3) [lexmark] x1100_usb_bulk_read: returned size = 3 (required 3) [lexmark] x1100_usb_bulk_read: returned size = 2500 (required 2500) [lexmark] x1100_usb_bulk_read: returned size = 3 (required 3) [lexmark] x1100_usb_bulk_read: returned size = 3 (required 3) [lexmark] x1100_usb_bulk_read: returned size = 2500 (required 2500) This does appear to be progress, however, as before it would just keep straining to back up past the physical end and now it seems to recognize it is at the end after a second or less and moves forward then tries again. Again, your efforts are deeply appreciated and hope the above suggests a solution. Bob Hello, could you use scanimage to try to do a scan and send debug output to a log file ? The attached file will create a scan.log in lexmark_testing/sane-backend-1.0.18 will do such. It has to be saved and run in the lexmark_testing directory. There will be also a number of *.pnm file in the lexmark_testing/sane-backend-1.0.18 directory. Please send the log and image files to me (they will be to big for the list), so I can try to see how to make things further. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: scan.sh Type: application/x-shellscript Size: 154 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070130/08b753cd/scan.bin From r...@exactcode.de Tue Jan 30 11:07:40 2007 From: r...@exactcode.de (Rene Rebe) Date: Tue Jan 30 11:38:49 2007 Subject: [sane-devel] JPEG compression slipped in? In-Reply-To: 1170117376.29296.5.ca...@kirk.lan References: 1170117376.29296.5.ca...@kirk.lan Message-ID: 200701301107.40853.r...@exactcode.de On Tuesday 30 January 2007 01:36:16 PF wrote: Hi... If I scan a page of text at 200dpi in color mode (for example) with xsane, then zoom in to 400%, I can see jpeg-like artifacts around letters and other sharp lines. This isn't an artifact of the xsane zooming process, as saving the file as a TIFF and examining the individual pixels with another program will also show the artifacts. Is there an option to turn this off? Maybe your device sends JPEG data and the backend is transparently decompressing it ? Which scanner are you using? -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name +49 (0)30 / 255 897 45
[sane-devel] Lexmark x1185 Can't Find Home
Oops, forgot to upload the archive. It's fixed now ! Regards, Stef
[sane-devel] x1250 not work
Le samedi 20 janvier 2007 09:58, Dani ele a ?crit?: found USB scanner (vendor=0x043d, product=0x007d, chip=rts8858c) at libusb:002:006 Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. The backend lexmark from our site failes to compile but fortunatelly the lexmark library is before the error. make install copy perfectly these library but not work (xsane,xscanimage) An help please? The chip seems the same of other scanner supported. My system is a gentoo linux amd64 updated _ Esprimiti: personalizza la tua home page con Live.com. http://www.live.com/ Hello, it isn't clear to me what version of the backend you tried. Was it the regular sane-backends or the experimental lexmark repository ? In both cases the failling compilation messages would have interesting. You can provide more details why the frontends don't work by running scanimage in a command shell with debug activated by typing the following commands: export SANE_DEBUG_LEXMARK=255 scanimage -L Send the output of these commands so we can understand what is going on. Regards, Stef
[sane-devel] Umax 2000P
Le samedi 30 d?cembre 2006 23:02, Frank McCormick a ?crit?: Hello all I am trying to get a Umax 2000p scanner to work with my Ubuntu installation. So far no luck - I keep getting an error message which seems to indicate the SANE frontend or maybe the backends were not compiled with an option. This is the error: frank@ubuntu:~$ xsane [umax_pp_low] sanei_umax_pp_InitPort cannot use direct hardware access [umax_pp_low] if not compiled with --enable-parport-directio In googling the problem it seems there are 2 ways of accessing the parallel port directly or through ppdev. However when I load that module (sudo modprobe ppdev) I am no further ahead. I also tried downloading the sources and compiling but when it came to compiling the front end it failed because it seems to think the backends have not been compiled, when in fact they have been. I am using Ubuntu Dapper and Edgy but both distributions give me the same error. Is it possible to use a Debian distros files ? Is there any other way to resolve this ? Thanks Hello, if the --enable-parport-directio hasn't been used to build the umax_pp backend, you can only make it work with ppdev. Loading the ppdev module might not be enough, you must have permission to access the device. Check the owner and group of the /dev/parport0 device that is created when the module is loaded. To see if it's only a permission problem try 'sudo scanimage -L'. Also, in umax_pp.conf, you can change the 'port' line to 'port safe-auto' or 'port /dev/parport0 if you're sure you'll allways use ppdev. Regards, Stef
[sane-devel] infrared, SANE_FRAME_RGBA
Le jeudi 14 d?cembre 2006 21:18, m. allan noah a ?crit?: On Thu, 14 Dec 2006, Giuseppe Sacco wrote: Hi Gerard and all SANE developers, Il giorno gio, 14/12/2006 alle 13.40 +0100, Gerhard Jaeger ha scritto: [...] But I think you are right, we are moving into a dead-end. We have devices that are able to do much more than we are able to support with the SANE 1 standard AND we have a not yet finished (if finished ever) SANE 2 standard. I'd like to hear/read some more opinions on that. Any? i would vote for re-openning the discussion of SANE2, and begin a project to port a limited number of backends forward. use a whole new SONAME, such that sane1 and 2 libs can co-exist for awhile. many backends will never be ported to sane2, because the scanners have not been made in 10+ years, and there is no-one to do it. my personal list of things other folks have mentioned: 1. i hate threading/forking in backends. it makes debugging a mess, and there are plenty of non-interactive uses for sane that dont need it (the single most popular front-end, scanimage, for one :) As per recent discussions on this list, any frontend that cares about non-blocking, has already implemented a threading solution to deal with all the backends that block. lets drop the non-blocking functions. 2. network protocol overhaul- this keeps coming up, but i dont understand it fully. 3. stackable/modular compression libs- lots of scanners give back jpeg as their native format, and we usually open it up to a huge pixmap, just to hand to front-end. this is esp. noticable over saned. zlib, jpeg, what else? 4. inconsistent option names and arguments between backends. 5. inconsistent gamma/brightness/contrast implementations (sanei_gamma i have been playing with here) 6. persistent device naming. none of this libusb:xxx stuff, i want the backend to provide the name, using something like serial number, rather than using the sanei_usb name. 7. inconsistent conf file layouts- i actually would like to see something more like samba.conf, with [sections], etc. Some months ago, it was thought of exposing configuration parameters the same way the scanning parameters are exposed. That would allow frontends or other tools to configure backends easily. 8. inconsistent debug levels. not that big of a deal i guess. i would rather that they were a bitmask instead of a linear progression. 9. i HATE the frontends changing br-x/y and tl-x/y into t/b/l/r- i have a front-end that takes cli args like scanimage, and i have to do the same option manipulations so that users can use their scanimage commands in my prog. it also means that my back-ends provided help text for those options is not useful. 10. button support. getting better, but not there yet. comments? allan -- 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 Regards, Stef
[sane-devel] Plustek ST24
Le lundi 11 d?cembre 2006 17:34, Tymoteusz.Drozd a ?crit?: hello, ok i've done log of preview and i compress its output by bzip, its weight approximately is 3.5MB. should i send it at sane-delvel ? or directly to you :). regards There is a ~20K threshold on the list that would prevent such mail. You can send it directly to me. If you have some spce and time, you can put it on a web site and send the URL to the list. Regards, Stef
[sane-devel] Plustek ST24
Le jeudi 7 d?cembre 2006 22:59, Tymoteusz.Drozd a ?crit?: Hi I have done scan under windows and i have decode of usbsnoop.log. This log should contain only preview scan but im not sure that. Log may contain more then only preview scan and i dont know how decode.sh and cmd.sh work in such situation. Also im not sure how those scripts work on cuted logs(for example on log which contain preview scan and interupted log of scan in 600dpi) Cuted log is becuse my windows become very slow and unstable after enabling of usbsnoop, i tried 600 dpi scan but i have to giveup after 45 minuts and 220MB log size. In attachment i sent results of decode.sh cmd.sh (bzip2 compressed). I will read something more about those scripts and logs but i have busy week before/after :. i think i should have time in next week to do more logs and read gl646 documentation. regards Hello, since data is logged in hexadecimal, it expands a lot in logs. So when logging high dpi scans, you have to reduce the target area to the smallest possible area. The log you sent ends too early. I guess the raw data has something scripts can't handle. Can you send me the raw usbsnoop.log of a color preview ? I'll try to understand what's going on. Regards, Stef
[sane-devel] Plustek ST24
Hello, here's the mentioned scripts. There are 2 main ones: - decode.sh : turns raw usb log in higher level form - cmd.sh : turns the output of the decoding in high level status dumps The first script uses a swarm of little awk scripts that handle a little step of decoding each. At the end, there shoudn't be any lines 'URB .' remaining if everything has been decoded. In case any are left, they're meaning has to be understood so that the scripts can handle them. Usually the left over are custom button or power saving handling. If needed, they can be filtered out as shown in decode.sh . The second script parses the high level output and builds a in memory status of the scanner. Each time a motor start is found (motor start is use as a 'commit'), the whole status (slope tables, analog fronted and registers) is dumped. It allow to compare the debugging output of the backend with the expected status of the scanner. This filters out the many useless registers writing/reading done by drivers. All scripts keeps data, so logs may be huge, but you can then rebuild pictures of scans from the recorded data. which help understanding what the scanner is doing. Doing such his explained in http://perso.modulonet.fr/~stefdev/sane/gl646-wip03.odt I'll be out for a couple of day, so I will answer any question/point when I'll be back. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: dist.tar.bz2 Type: application/x-tbz Size: 10784 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061203/17f783d6/dist.tar-0001.bin From jkds...@gmail.com Sun Dec 3 21:41:22 2006 From: jkds...@gmail.com (JKD) Date: Sun Dec 3 22:05:10 2006 Subject: [sane-devel] Location of some backend's files In-Reply-To: pine.lnx.4.61.0612031104310.29...@limos.pfeiffer.edu References: eb141f9e0612021648k1fd05544ge830c3c8c4d3a...@mail.gmail.com pine.lnx.4.61.0612031104310.29...@limos.pfeiffer.edu Message-ID: 20061203204122.gl3...@jkdsoftware.dyndns.org El Sun, 03 de Dec de 2006, a las 11:13:07AM -0500, m. allan noah dijo: On Sun, 3 Dec 2006, JKD wrote: Hello, I'm hp3900 backend's developer. Due to this backend supports some scanners and new devices could be supported in the future I'm thinking about the possibility to create different config files for each scanner capabilities to maintain code's structure legible. but you will have to add code that parses these files, and builds them into an array of structs. having that array compiled into the backend will be faster, and maybe less code. Code to parse files would be done the first time. Sources wouldn't need to be rewriten each time a new scanner is added. Due to config is out of code, application's size is much lower and only is necessary to allocate dynamic memory for one scanner instead of all supported scanners. Another advantage is that any change in structs wouldn't affect configuration causing compilation problems. The only disadvantage as you say is that there is a little lapsus of time (may be not perceptible) when using sane_open function. But after sane_open, backend works as fast as it was before. It's not simple configuration which user should change but internal values to program RTS8822 chip in each case (area constrains to scan, sensor timing values, motor curves...) so I wouldn't set them at sane.d/hp3900.conf if they are not user-changeable, then why do they need to be a separate file? Because it's easier for any developer or anyone who wants to try to support his new scanner, under his own responsability, editing desired values without compiling backend in each change (It's faster in this way). For security reasons these files can be read only so normal users can not make any change. Is there any standard path in SANE to locate such files? Something like sane.d/backend's name/ or may be /usr/share/backend's name/ i would consider it a security risk to have such a low-level control file read from the home-dir of the user, and non-linux systems may not have a /usr/share, but they will have the sane.d config-file dir, so perhaps sane.d/backendname/ is best (though i dont see the need for it...) allan If all of you think that it's not a good idea I'll keep config inside code. Jonathan Bravo Lopez
[sane-devel] A920 / Lexmark X1150 Not Detected by XSANE
Hello, the Dell A920 is indeed a rebranded Lexmark. But the version of the lexmark backend only handles one model that does not match this one. It is also very basic (no color offset/light calibration, and no shading correction). The experimental version handles 2 models (the current and A920) and has a few improvements. But is not packaged in the official release. So you'll have to build it from CVS sources. Regards, Stef
[sane-devel] Epson Perfection V100/V350 Photo scanners
Le jeudi 2 novembre 2006 01:31, Olaf Meeuwissen a ?crit?: piotr_n piot...@o2.pl writes: Hi, Hi, I have question if model Epson Perfection V100/V350 Photo scanners are currently supported directly by sane. Yes I know iscan driver (Image Scan! 2.3.0) exist but the plugins is only for rpm systems and as a Slackware user I have not an idea where I can find normal source (tar.gz) file for this model. rpm2tgz (see http://www.slackware.com/config/packages.php) allow you to convert from rpm to tgz so that you can install it the way you need. Regards, Stef
[sane-devel] [TRANSLATION] French translation update
Hello, only a very few things left: - 111 : S?lectione = S?lectionne - 122 : faile = faible - 124: ?utiliser = ? utiliser - 141: cannaux = canaux - 182: Experimentation = Exp?rimentation - 199: doceument = document - 206: horizontallement = horizontalement - 208: verticallement = verticalement - 471: could it be that Calibration de qualit? is meant, instead of Calibration de la qualit? ? - 549 to 555: Definit = D?finit Regards, Stef
[sane-devel] HP 2300C (GL646) head bumps and screams
If you wish -- so you don't need to keep checking stuff into cvs without knowing how the test will go -- I'd be happy to alter my copy of the sources in any way you suggest, then try it out and let you know how it goes. -- Whichever way you'd like to do it is good for me. Many thanks again for your help. Regards, bill Hello, now the detection bug is fixed, the other issue has to be fixed. From the logs, we can see that gl646_slow_back_home() is failing. Since an usb read suddenly fails, I suppose it is when you unplug it. The question is was the scanner's head really stuck ? Sometimes head parking may takes time. If when trying to park the sensor doesn't move, you may change the flags in genesys_devices to make HP2300 make use of gl646_park_head() by adding the GENESYS_FLAG_USE_PARK flag. This function is ready to handle your scanner model. But since slow back home is working for others, there is something wrong. Maybe you have to tune the y_offset and height of scan area now origin detection is working. Current values are surely based on wrong detection. By scanning the corner of paper rotated by 45? and placed at the very top of the scanning area, you can modify the y_offset until you get it fully on the scan. You may also tweak the height of the scanning area. Regards, Stef
[sane-devel] HP 2300C (GL646) head bumps and screams
Le samedi 5 ao?t 2006 01:33, Bill Dawson a ?crit?: Hi Folks, I reviewed the few threads concerning the 2300C from early in May of this year. E.g. here: http://lists.alioth.debian.org/pipermail/sane-devel/2006-May/016724.html I have the latest sources (2006-08-04) and have looked through genesys_devices.c, and it looks like Stef did indeed make the changes exactly as he said he would in those previous threads. So I was hoping that everything would work... But, alas, I get the problem of the head bumping into the end and screaming at me until I put it out of its misery by pulling the plug. The good news is that I get a nice looking image file. But of course it's no fun pulling the plug every time it's done. I ran scanimage --mode Color scan.pnm 2debug.log (with the appropriate debug level 255 environment vars exported) and uploaded the results to... http://www.billdawson.com/misc/genesys_scan.tar.gz ... in case someone can have a look for me and maybe offer some advice. Many thx, bill Hello, with the debugging data you posted, I have found where the problem comes. It is hopefully fixed in CVS version, but since I don't have an HP2300 to test, you'll have to do it ... but I expect it to be OK. The bug is in the sanei_genesys_search_reference_point() function which wasn't detecting y edge of the 'position pattern' because the picture wasn't contrasted enough. So the y offset detected was too big, shifting all scans to the bottom of the scanner. It could be noticed in final scan, since it was lacking the top of the picture. Regards, Stef
[sane-devel] Debug output from Lexmark X1270 scanner
Le mardi 25 juillet 2006 01:00, Fred Odendaal a ?crit?: The X1270 is not supported by the X1100 backend. You are somewhat correct in your assumption of what is happening. The scanner is trying to find the home position by scanning in the reverse direction - looking for a set pattern off the glass. If it can't find it, it will make a loud noise as the scan head bangs against the end. This is bad for your scanner, so I'd advise against continuing to try it. regards, Fred Odendaal Hello Fred, by the way, what are your plans regarding the experimental version of the lexmark backend ? It has the inital groundwork needed for multi-models support. Also it has some improvements such as calibration and arbitrary scan size area. As far I understood, the blocking point you got was calibration tuning for your model. Did you have some time to give a look ? Regards, Stef
[sane-devel] gl646 doc update
Hello, I've put up an updated (codeflow+some tricks to extract picturs from usblogs) documention for genesys backend -for the GL646 part- at: http://perso.modulonet.fr/~stefdev/sane/gl646-wip02.odt I plan to add howt to fill the Genesys_Sensor struct with valeus from usb log, allthough fields name are allready explanatory. Regards, Stef
[sane-devel] HP Scanjet 2400c for genesys
Hello, I have started a document at http://perso.modulonet.fr/~stefdev/sane/gl646.odt which is in early stages, I'll improve it this next days. Regards, Stef
[sane-devel] using parallel port scanner as ordinary user in recent version of Fedora
Le mardi 11 juillet 2006 01:36, Andre Robatino a ?crit?:
My father has a Umax Astra 2000P parallel port scanner. At present
it's accessible only as root. Before the advent of udev, it was
possible to access as an ordinary user by changing the permission of
/dev/parport0 from 660 to 666. Since udev appeared in Fedora 2, another
solution is needed. After reading sane man pages, we've done the
following:
1) In /etc/sane.d/dll.conf, uncommented umax_pp.
2) In /etc/sane.d/net.conf, uncommented localhost.
3) In /etc/xinetd.d, created a file sane-port with the contents:
# default: off
# description: The sane server accepts requests
# for network access to a local scanner via the
# network.
service sane-port
{
port= 6566
socket_type = stream
wait= no
user= root
group = root
server = /usr/sbin/saned
}
This is copied from the template in the saned man page, with the user
and group changed from saned to root, since user and group saned don't
exist, and since running as root would allow direct hardware access. I
didn't add localhost to /etc/sane.d/sane.conf since the saned man page
says that connections from localhost are always permitted. The file
/etc/services already contains the lines
sane-port 6566/tcp# SANE Control Port
sane-port 6566/udp# SANE Control Port
Ordinary user access still doesn't work. What's wrong?
Hello,
I haven't enough saned experience to tell you what might going on. But
I have
the feeling the trouble oyu have with /dev/parport0 may just be an issue
with 'ppdev' kernel module autoloading.
Can you send the debug messages of 'scanimage -L' with the environment
variables SANE_DEBUG_UMAX_PP and SANE_DEBUG_UMAX_PP_LOW set to 255 ?
There will be traces of which device is used or not, and some informations why
they are used.
Regards,
Stef
[sane-devel] HP Scanjet 2400c for genesys
Le mardi 4 juillet 2006 11:51, Thomas Mader a ?crit?: Hello, I have a HP Scanjet 2400c and would like to know if I can help somehow to speed up the development of the driver for this? Can I provide some information about it or something else? Hello, this topic has come a few time on the list. The way I see 2400 support added is to record usb activity under windows, decode it. Then modify the genesys backend accordingly. Test the changes, and compare debug output until it is close enough to windows behaviour. However, I think there is a 'roadmap': take the functions one after the other in the sequence they are used by the backend. For instance, it make no sense to directly jump to the final scan and trying to hack it, since it relies on values detected by previous functions. Here's the call graph for a preview: sane_open gl646_init gl646_init_regs sanei_genesys_create_slope_table sanei_genesys_create_gamma_table gl646_set_fe gl646_slow_back_home gl646_send_gamma_table gl646_set_powersaving sane_start gl646_save_power gl646_set_fe gl646_search_start_position gl646_setup_sensor sanei_genesys_exposure_time gl646_setup_steps sanei_genesys_create_slope_table gl646_send_slope_table gl646_set_fe gl646_begin_scan sanei_genesys_read_data_from_scanner this function generates a searh_position16.pnm and search_position.pnm which are pictures of the innings of the scanner. These should contain black and white areas that will be basis for postion detection. gl646_end_scan sanei_genesys_search_reference_point ... more to come ... I'm currently compelting this, but I think making gl646_search_start_position working will take enough time to let me finish. Some on these functions already test for HP2300. You can add tests and values for 2400 there. However, there are two points to take into account: - for the HP2300 I made the analog frontend work like the MD5345 one since I couldn't make it work like it is in usb logs. - motor slope creation should favor sanei_genesys_create_slope_table3() over the sanei_genesys_create_slope_table() currently used. I append the latest version of the scripts that I use for log decoding. The cmd.sh takes a decoded log and emits scanner status at each motor start (which is used as a 'commit'). It is usefull since you can take it's output to compare scanner internal state with the one from the backend log (output of gl646_bulk_write_register() ) right before gl646_begin_scan(). Don't hesitate to ask for more or send patches ... Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: scripts.tar.bz2 Type: application/x-tbz Size: 15628 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060706/db074ddb/scripts.tar.bin From ni...@rmk.co.il Thu Jul 6 06:49:39 2006 From: ni...@rmk.co.il (Nigel Ridley) Date: Thu Jul 6 06:50:29 2006 Subject: [sane-devel] Only superuser can scan In-Reply-To: 44a9414c.3050...@wayforth.co.uk References: 44a9414c.3050...@wayforth.co.uk Message-ID: 44acb283.8080...@rmk.co.il Antony Gelberg wrote: Hi all, This is a Debian testing box. The normal user can't scan, but it's different to permissions problems that I've seen before. He can see a scanner, but there is a question mark in the (incomplete) output of sane-find-scanner. It's a Canon lide 60 (genesys backend). I have bodged the permissions on /proc/bus/usb/001/002 to allow all rw, but no difference. It's running 2.6.15, with udev, not hotplug. aft:/home/dr# sane-find-scanner -q found USB scanner (vendor=0x04a9 [Canon], product=0x221c [CanoScan], chip=GL841) at libusb:001:002 aft:/home/dr# su dr dr@aft:~$ sane-find-scanner -q found USB scanner (vendor=0x04a9, product=0x221c, chip=GL841?) at libusb:001:002 dr@aft:~$ id uid=1001(dr) gid=513(Domain Users) groups=46(plugdev),110(scanner),111(saned),513(Domain Users) dr@aft:~$ ls -l /proc/bus/usb/001/002 -rw-rw-rw- 1 root root 57 2006-07-02 17:26 /proc/bus/usb/001/002 dr@aft:~$ scanimage --version scanimage (sane-backends) 1.0.17; backend version 1.0.17 dr@aft:~$ uname -a Linux aft 2.6.15-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686 GNU/Linux Any advice would be appreciated. Antony -- PrayingForIsrael.net http://www.prayingforisrael.net/ Messianic E-Cards.com http://www.messianicecards.com/
[sane-devel] Lexmark X1185 Scanner
Hello, could you give the experimental lexmark backend a try ? Here are quick instructions to build it from cvs, and run it without system-wide install. First we get sane sources and patch them to get experimental version, and compile it. cd /tmp mkdir testing cd testing cvs -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane login (type return when asked for a password). cvs -z3 -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane co sane-backends cvs -z3 -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane co experimental/lexmark cd experimental/lexmark sh link.sh ../../sane-backends cd ../../sane-backends ./configure make You have now an experimental version in /tmp/testing/sane-backends. Now to run it without install (assuming you don't change from the /tmp/testing/sane-backends directory): export LD_PRELOAD=backend/.libs/libsane-lexmark.so.1.0.17 You can now run xsane/xscanimage/scanimage from the command line. Regards, Stef
[sane-devel] Genesys Backend and Umax Astra 4700
Le lundi 19 juin 2006 19:24, mfi3 a ?crit?: Hello, I am an unhappy owner of Astra 4700 scanner. I cannot use it for some years (I am using almost only linux), since it isn't supported under my OS. A two or three years ago I had hope that my scanner will be supported by Genesys backend - but now, when backend is released, Umax Astra 4700 still isn't supported (Astra 4500 at least will be added in the future). So I started to think about selling my scanner. So it's question mainly for Genesys backend developers - are You planning to add support for Astra 4700 to Genesys backend, and are there any chances that it will be added in predictable future ? sorry for my english, and thanks in advance for reply :) Michael. Hello, adding support for it involved recording the USB activity of the windows driver, then use them to figure out hiow to operate it. Then the backend can be modified and tested. This process isn't that hard, but involves having such a scanner. Since I don't have one, I can't do it. But I you feel like doing it, I can help you in this process, and share my tools with you. Regards, Stef
Fwd: Re: [sane-devel] Lexmark experimental backend]
Le Dimanche 28 Mai 2006 20:20, Fred Odendaal a ?crit?: Stef, You are correct about the dot. I've attached 2 files: find_start_lexmark1.pnm - This was with SANE_DEBUG_SANEI_USB=255 find_start_lexmark2.pnm - This was with SANE_DEBUG_SANEI_USB unset. As you can see the picture gets better with usb logging turned off. I think the real problem function is sanei_lexmark_x1100_search_home_bwd(). It should have stopped the scan head and positioned it inside the dot. The white space at the top of each file is the distance past the dot that the scan head moved in the reverse direction. In this function after the scan is stopped from moving in the backward direction it is moved forward half the distance of the dot plus the maximum no. of lines the buffer will hold. This is done by the call to sanei_lexmark_x1100_move_fwd(). When I comment this line out the picture gets even better. In other words, this function isn't moving forward, but continuing backwards making our position even worse! The sanei_lexmark_x1100_find_start_line() function is working as it should. It simply scans what should be enough lines to scan past the dot into white space and return the number of white lines past the dot. Since the distance to the scanning area from the dot is known we simply subtract how far past the dot we've moved from this number to see how far we still have to go. regards, Fred O. Hello, you wre right, the trouble was with sanei_lexmark_x1100_search_home_bwd() which was scanning too far. To correct it, I made it read only one line of data (2500 bytes) at a time. So when it finds the dot and then stop, it is right on it. So we don't need to move forward a little. Now origin finding is slower but much more reliable. This change uncovered a bug in the way I modified rewind. So I had to change it. It now goes back by the bottom right y coordinate plus a fixed amount which is the distance between start of visible area and the origin dot. I tweaked a little the calibration values. Picture are now close to the quality of my other scanner. I think that the current version is in good shape. Regards, Stef ---
[sane-devel] Snanner MD 3545 hang up with sane-1.0.17-0.pm.0.i586.rpm
Le Dimanche 4 Juin 2006 18:51, Klaus K?bler a ?crit?: Hallo, I have installed the sane back end sane-1.0.17-0.pm.0.i586.rpm on my SUSE LINUX 10.0 system (Kernel Linux 2.6.13-15-default) using YAST2. I have got a incomplete error message from YAST2 when tying to install my MEDION MD 3545 USB scanner, nevertheless I can find the scanner within the sane KDE menu. I can start the preview scan and will get the expected preview image exactly one time. Each additional scan (preview ore final) will fail. The resulting image is all the times the same, it seems that the first pixel row will be repeated over all rows of the whole image. The scanner mechanic itself will work well all the time. The scanner will respond with this constant image up to a power down and up cycle of the scanner! Rebooting the computer will have no impact to this behaviour. Did you have any idea how to solve this problem? Thanks Klaus Hello, I don't know what scanning program you are using, but there is a bug in SANE 1.0.17 where the first scan of a second frontend session (ie a previous was finished) would hang and fail.It is fixed in CVS by now. So I think it is worth testing with this version. By using LD_PRELOAD, you can force your favorite frontend to use a hand-compiled version without installing systerm-wide. Regards, Stef
[sane-devel] Lexmark experimental backend
Grr, here's the mentioned picture . -- next part -- A non-text attachment was scrubbed... Name: find_start.pnm Type: image/x-portable-pixmap Size: 5205 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060523/0e4e80a1/find_start.ppm From moiti...@civil.ist.utl.pt Tue May 23 14:07:36 2006 From: moiti...@civil.ist.utl.pt (Jose Paulo Moitinho de Almeida) Date: Tue May 23 14:08:43 2006 Subject: [sane-devel] re: Minolta Dimage Scan Dual II In-Reply-To: 200605231156.20148.r...@exactcode.de References: 9uMBTQsAjyB@didi.segbert 56612.87.196.204.182.1148323840.squir...@www.civil.ist.utl.pt 200605231156.20148.r...@exactcode.de Message-ID: 200605231507.38010.moiti...@civil.ist.utl.pt On Tuesday 23 May 2006 10:56, Rene Rebe wrote: On Monday 22 May 2006 20:50, moiti...@civil.ist.utl.pt wrote: . The scanner needs to be calibrated and that has to be done with the scanner door closed. But in order to scan you need to have a film holder and the door open This problem might deserve a special solution but it was never implemented... Meanwhile my solution was to make an empty scan (no film holder, door closed), without setting the frame, which would of course fail (but only after calibrating the scanner) before starting to do normal scans. Oh, I do not rember anyone notified me about this issue :-( We talked about it in February 2002... but I never mentioned it as something important. I got used to apply the sequence 1) Power on scanner. Close door. Execute $ scanimage -d avision test.pnm 2) Open door. Insert film holder. Execute $ scanimage -d avision --resolution 2800 --frame 1 test.pnm 3) Repeat scanimage as needed I just verified that I mentioned the possibility of creating an option --calibrate, which would calibrate without trying to scan. My doubt is wether this fits nicelly with all frontends. Regards ZP
[sane-devel] cmd.sh script not working on windows Log
Le Lundi 15 Mai 2006 15:02, Parag N() a ?crit?: Hi, I have your awk and shell scripts for decoding windows usb log. I first used decode.sh on usb2.log, it worked fine. Then on decoded log i used cmd.sh but its not giving at all any register values. why? attached 1)original windows log file = http://download.yousendit.com/705A9E3605DB223C 2)decoded log =http://download.yousendit.com/83880D321083B0EF 3)cmd log =http://download.yousendit.com/D2985DE3716CFCB4 Regards, parag. Hello, the motor is started by a bulk register write of size one. I've updated the scripts to take care of that. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: dist.tar.bz2 Type: application/x-tbz Size: 10846 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060520/fddc36cb/dist.tar-0001.bin From stef...@modulonet.fr Sat May 20 12:53:08 2006 From: stef...@modulonet.fr (=?iso-8859-15?q?St=E9phane_VOLTZ?=) Date: Sat May 20 12:53:47 2006 Subject: [sane-devel] Lexmark experimental backend In-Reply-To: 446d3754.4000...@rogers.com References: 200605191356.18305.stef...@modulonet.fr 446d3754.4000...@rogers.com Message-ID: 200605201453.08964.stef...@modulonet.fr Le Vendredi 19 Mai 2006 05:11, Fred Odendaal a ?crit?: St?phane, I tested it on my Lexmark X1185. It is broken really badly. It hangs in the function sanei_lexmark_x1100_search_home_fwd - infinite read loop in a poll after trying to move the scan head. I did a register compare from usb dumps of a good scan (sane-backends-1.0.17) and a bad scan (experimental) and none of the lexmark register defaults are set! There are 35 registers that used to have non-zero default values and now have 0x00 and one register that was 0x01 and is now 0x81. Fred Hello, after checking I only got register 0xC3 different. however while commiting this change, I noticed that more files were updated than I'd expected. I think I did my previous commit wrongly. Things should be much better now. But in case there are other problems I'd like to have the logs. I can override model detection to make the regular backend to think my A920 is a X1100, and so get registers values before the chnages, but I won't be able to do it past sanei_lexmark_x1100_search_home_bwd(). Regards, Stef
[sane-devel] Umax Astra 4100:Genesys bakend development
Le Vendredi 12 Mai 2006 16:02, Parag N() a ?crit?: Hi, Anybody is working on developing a backend for UMAX Astra 4100 usb scanner?? It's having a Genesys GL646_HP chipset. Need Help in developing this backend. Here are those results that you people may want to look at My Results:- This scanner works only as root. sane-find-scanner can only detect this scanner as root not as normal user. so i followed instructions given in README.linux *** ** sane-find-scanner found USB scanner (vendor=0x0461 [Primax], product=0x038c [USB Scanner], chip=GL646_HP) at libusb:002:003 *** *** *** scanimage -L [sanei_debug] Setting debug level of genesys to 255. [genesys] SANE Genesys backend version 1.0 build 8 from sane-backends 1.0.17-cvs [genesys] sane_init: authorize != null [genesys] sane_init: little endian machine [genesys] sane_init: reading config file `genesys.conf' [genesys] sane_init: config file line 1: ignoring comment line [genesys] sane_init: config file line 2: ignoring empty line [genesys] sane_init: config file line 3: ignoring comment line [genesys] sane_init: config file line 4: ignoring comment line [genesys] sane_init: config file line 5: ignoring comment line [genesys] sane_init: config file line 6: ignoring comment line [genesys] sane_init: config file line 7: ignoring empty line [genesys] sane_init: config file line 8: ignoring comment line [genesys] sane_init: config file line 9: trying to attach `usb 0x0461 0x038c' [genesys] attach: start: devp != NULL, may_wait = 0 [genesys] attach: trying to open device `libusb:002:003' [genesys] attach: device `libusb:002:003' successfully opened [genesys] attach: found UMAX flatbed scanner Astra 4100 at libusb:002:003 [genesys] attach: exit [genesys] sane_init: config file line 10: ignoring empty line [genesys] sane_init: config file line 11: ignoring comment line [genesys] sane_init: config file line 12: ignoring comment line [genesys] sane_init: config file line 13: ignoring empty line [genesys] sane_init: config file line 14: ignoring comment line [genesys] sane_init: config file line 15: trying to attach `usb 0x03f0 0x0a01' [genesys] sane_init: config file line 16: ignoring empty line [genesys] sane_init: config file line 17: ignoring comment line [genesys] sane_init: config file line 18: ignoring comment line [genesys] sane_init: config file line 19: ignoring empty line [genesys] sane_init: config file line 20: ignoring comment line [genesys] sane_init: config file line 21: ignoring comment line [genesys] sane_init: config file line 22: ignoring empty line [genesys] sane_init: config file line 23: ignoring empty line [genesys] sane_init: config file line 24: ignoring comment line [genesys] sane_init: config file line 25: ignoring comment line [genesys] sane_init: config file line 26: ignoring comment line [genesys] sane_init: config file line 27: ignoring empty line [genesys] sane_init: config file line 28: ignoring comment line [genesys] sane_init: config file line 29: trying to attach `usb 0x0461 0x0377' [genesys] sane_init: config file line 30: ignoring empty line [genesys] sane_init: config file line 31: ignoring comment line [genesys] sane_init: config file line 32: trying to attach `usb 0x03f0 0x0901' [genesys] sane_init: config file line 33: ignoring empty line [genesys] sane_init: config file line 34: ignoring comment line [genesys] sane_init: config file line 35: trying to attach `usb 0x04a9 0x2213' [genesys] sane_init: config file line 36: ignoring empty line [genesys] sane_init: config file line 37: ignoring comment line [genesys] sane_init: config file line 38: trying to attach `usb 0x04a9 0x221c' [genesys] sane_init: exit [genesys] sane_get_devices: start: local_only = false [genesys] sane_get_devices: exit device `genesys:libusb:002:003' is a UMAX Astra 4100 flatbed scanner [genesys] sane_exit: start [genesys] sane_exit: exit *** ** Even I want to know why URB packets are captured in random order in usbsnoop log file under windows?? I used sniff-usb-1.8 version under windows and it captures packets as 263 then 256 then 257 then 261 like that. Because of that the awk scripts from decode.sh are stopping at first non sequential packet and i am able to get decoded log upto that packet. how to overcome this problem?? Also whats the status of UMAX 4500 scanner? Will post updates on adding new entry in genesys_devices.c for this scanner. Regards, Parag. Hello, URB packets that don't come in sequence are surely reads waiting for an interrupt. For my MD6471, they are related to
[sane-devel] HP scanjet 2300c
Hello,
after searching the debug data, I think there is no problem in start
position
detection (which is correclty reported to be 'top = 65'). In fact it seems
that it is the value added to the detected y position is bogus. Currently, we
add -2.0 mm which may lead in a negative y movement if the inital y offset is
low.
So I think you should try to tune this value to exactly match your
scanner.
In the geometry settings, chage 'Start of scan area in mm (y_offset)' to a
value like SANE_FIX (1.0), and decrease it until the scanned picture doesn't
miss the very top of the scanning area. Since scanning succeeded with an
offset (-t 2), a value of SANE_FIX(0.0) should work.
In this cas we could keep the y size of area at 297 mm.
in genesys_devices:
static Genesys_Model hp2300c_model = {
hewlett-packard-scanjet-2300c, /* Name */
Hewlett Packard,/* Device vendor string */
ScanJet 2300c, /* Device model name */
GENESYS_GL646,
NULL,
{600, 300, 150, 75, 0}, /* possible x-resolutions */
{1200, 600, 300, 150, 75, 0}, /* possible y-resolutions, motor can go up to
1200 dpi */
{16, 8, 0}, /* possible depths in gray mode */
{16, 8, 0}, /* possible depths in color mode */
SANE_FIX (-2.0), /* Start of scan area in mm (x_offset) */
SANE_FIX (-2.0), /* Start of scan area in mm (y_offset) */
SANE_FIX (215.9), /* Size of scan area in mm (x) */
SANE_FIX (297.1), /* Size of scan area in mm (y) */
Regards,
Stef
[sane-devel] GL646 genesys, 2300c head problem
Le Samedi 6 Mai 2006 13:15, Mark Hatton a ?crit?: I have tried with a value of 295 and it works great. No head crashes - everything just works. Thanks for your help, Mark OK, I'll put it in CVS soon. Regards, Stef
[sane-devel] HP scanjet 2300c
Le Samedi 6 Mai 2006 00:02, Michael Schachtebeck a ?crit?: ok, I'm using the daily cvs snapshot now, and even the command scanimage --mode Color -y 20 scan.pnm drives the head very fast to the end until it crashes instead of scanning only the first 20mm... But if I use scanimage --mode Color -t 2 scan.pnm (or any other value for -t greater than 1), it works fine - strange... Is this a problem with my scanner, or is it a problem with scanimage? And how do I tell applications to use this parameter (for example xsane or kooka)? Michael. Hello, I believe this is because start position detection fails, giving some zero value which is decreased by start offset, giving a negative value. When the scan starts, the scanner gets a negative location, and the scanning head moves wrongly. By adding a start offset, the value gets positive again and everything goes right. To fix origin detection (and get sure this is the real bug), I need the log file and all the pnm files (search_position.pnm and search_position16.pnm) created by doing: export SANE_DEBUG_GENESYS_GL646=255 export SANE_DEBUG_GENESYS=255 scanimage --mode Color -t 2 scan.pnm 2debug.log Doing this with the CVS version would be the best. Regards, Stef
[sane-devel] HP scanjet 2300c
Thanks, I've dowloaded what I need. You can get rid of it. From a first glance the search_position.pnm seems too white. I'd expect that the dark area darker. I'll let you know what I find. Regards, Stef
[sane-devel] GL646 genesys, 2300c head problem
Le Jeudi 27 Avril 2006 12:32, Benedict a ?crit?: Hi, I'd need help in fixing the head not stopping at the end problem. Here is the hardware information: lsusb Bus 005 Device 001: ID : Bus 004 Device 001: ID : Bus 003 Device 004: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse Bus 003 Device 001: ID : Bus 002 Device 004: ID 03f0:0901 Hewlett-Packard ScanJet 2300c Bus 002 Device 001: ID : Bus 001 Device 003: ID 0ea0:6858 Ours Technology, Inc. Bus 001 Device 001: ID : scanimage -L device `genesys:libusb:002:004' is a Hewlett Packard ScanJet 2300c flatbed scanner It works like a charm but the head doesn't go back and makes a lot of noise at the end of the scanning area. Is there an easy fix for this? -- Benedict Hello, The scanning head may be going to far for at least 3 reasons: - the defined scan area for 2300 is too wide for your device - origin detection fails and there is an offset toward the bottom of the scanning area. - your model has an unkown motor, and command sent move the scanning head too far. In order to fin out what is going wrong, try to scan only the top of a picture with 'scanimage --mode Color -h 200 scan.pnm'. If the picture is ok, but is missing the top part, it is surely a problem with origin detection. If the image is vertically distorted, it is a motor issue. In any case, send to the list (if the zipped data are below 40K size), and me the scan.log file produced by doing: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 scanimage --mode Color -h 200 2scan.log scan.pnm There will also some debug pnm files created: 'search_position16.pnm' and 'search_position.pnm' for origin detection, please send them with the log. Last, which version of sane backends do you use? Be sure to run at least version 1.0.17. CVS version has a couple of interesting fixes, so it may be worth to try it. Regards, Stef
[sane-devel] GL646 genesys, 2300c head problem
Le Vendredi 5 Mai 2006 12:06, Mark Hatton a ?crit?:
The latest version in CVS fixes another issue with the 2300c for me. The
stable version only lets you scan once and then the scanner can't be
accessed again unless it is powered off and on again. The version in the
CVS HEAD seems to solve that.
When accessing the scanner using XSane, the default settings make the
scanner head crash in to the end of the scan bed (giving the horrible
noise). However, if I lower the length of the scan area by as little as
2mm, the problem goes away and the scan head stops and returns properly.
I have looked for a way to change the value of the available scanning
area but I can't find it. If someone can tell me which file it is
defined in, I am happy to change it myself and give it a try.
Thanks,
Mark
Hello,
look at genesys_devices.c in the backends sub-directory. Line 529 there
a
struct that describes the geometry for the 2300. You'll have to adjust
the Start of scan area in mm (x_offset) value, or the Size of scan area
in mm (y) . From your mail, I guess that a value of SANE_FIX (295.0) would
do the job:
static Genesys_Model hp2300c_model = {
hewlett-packard-scanjet-2300c, /* Name */
Hewlett Packard,/* Device vendor string */
ScanJet 2300c, /* Device model name */
GENESYS_GL646,
NULL,
{600, 300, 150, 75, 0}, /* possible x-resolutions */
{1200, 600, 300, 150, 75, 0}, /* possible y-resolutions, motor can go up to
1200 dpi */
{16, 8, 0}, /* possible depths in gray mode */
{16, 8, 0}, /* possible depths in color mode */
SANE_FIX (-2.0), /* Start of scan area in mm (x_offset) */
SANE_FIX (-2.0), /* Start of scan area in mm (y_offset) */
SANE_FIX (215.9), /* Size of scan area in mm (x) */
SANE_FIX (297.1), /* Size of scan area in mm (y) */
SANE_FIX (0.0), /* Start of white strip in mm (y) */
SANE_FIX (1.0), /* Start of black mark in mm (x) */
SANE_FIX (0.0), /* Start of scan area in TA mode in mm (x) */
SANE_FIX (0.0), /* Start of scan area in TA mode in mm (y) */
SANE_FIX (100.0), /* Size of scan area in TA mode in mm (x) */
SANE_FIX (100.0), /* Size of scan area in TA mode in mm (y) */
SANE_FIX (0.0), /* Start of white strip in TA mode in mm (y)
*/
16, 8, 0, /* RGB CCD Line-distance correction in pixel
*/
COLOR_ORDER_RGB, /* Order of the CCD/CIS colors */
SANE_FALSE, /* Is this a CIS scanner? */
CCD_HP2300,
DAC_WOLFSON_HP2300,
GPO_HP2300,
MOTOR_HP2300,
GENESYS_FLAG_REPARK
| GENESYS_FLAG_14BIT_GAMMA
| GENESYS_FLAG_SEARCH_START
| GENESYS_FLAG_MUST_WAIT
| GENESYS_FLAG_DARK_CALIBRATION | GENESYS_FLAG_OFFSET_CALIBRATION,
9,
132
};
Let me know the values that work best, I'll put them in CVS.
Regards,
Stef
[sane-devel] Genesys HP scanjet 2400
Hello, you're right. Here's the latest package of the scripts. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: dist.tar.bz2 Type: application/x-tbz Size: 9193 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060420/ce728e23/dist.tar-0001.bin From panem...@gmail.com Thu Apr 20 04:43:28 2006 From: panem...@gmail.com (=?UTF-8?Q?Parag_N(=E0=A4=AA=E0=A4=B0=E0=A4=BE=E0=A5=9A)?=) Date: Thu Apr 20 04:43:36 2006 Subject: [sane-devel] Genesys HP scanjet 2400 In-Reply-To: 200604200637.10834.stef...@modulonet.fr References: 1133488098.438fa7e2c4...@webmail.cloudnet.com 200512062230.21457.stef...@modulonet.fr 20060419213843.ga4...@superkaos.jazztel.es 200604200637.10834.stef...@modulonet.fr Message-ID: f4586a2e0604192143l2a12afddwdae0e67d99a7e...@mail.gmail.com Hi, Any progress for HP 2400 scanner? I gave up my all efforts as nothing is working for me after a big analysis on HP 2400 debug data. Regards, Parag. On 4/20/06, St?phane VOLTZ stef...@modulonet.fr wrote: Hello, you're right. Here's the latest package of the scripts. Regards, Stef -- 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] Preparation for sane-backends release 1.0.18
Le Mardi 18 Avril 2006 17:54, Henning Meier-Geinitz a ?crit?: Hi developers! I intend to start the countdown for the release of sane-backends 1.0.18 in a few weeks. So it's now the right time to include any big changes into sane-backends that are available. Especially big updates of existing backends and new backends should be included in the following weeks. What's the status of the following external backends? Can they be included into sane-backends? Keep in mind that this gives you a much bigger audience and many more testers. cs3200f geniusvp2 hp3900 hp_rts88xx pixma stv680 What about the lexmark backend in experimental CVS? Can the code be imported into main CVS to get the Dell a)20 working? Hello, I have yet to check in my latest developpements. Will do it tomorrow. Everything is finished: - arbitrary scan area - offset calibration - gain calibration - shading calibration is in place The only item left is to balance shading calibration. I have now all the data I need and I expect to have it work by the end of this week. However, it's up to the maintainer to give his opinion about inclusion. Regards, Stef
[sane-devel] genesys endianess
Hello, I tested it and has expected it works. So I removed the idefed part and only keep your code. regards, Stef
[sane-devel] genesys endianess
Hello, I had to put an ifdef WORDS_BIGENDIAN (like for slope tables), so that my MD6471 could work again after the endianess changes you done. Regards, Stef
[sane-devel] scanjet 2300c
Hello, I have disabled power saving for GL646 based scanners in CVS, as it is certainly the cause of your problems. This was overwritting some per model CCD settings that aren't reset later, leading to 'black scans'. Could you please test CVS version ? Regards, Stef
[sane-devel] backend 1.0.17 dell A920 no movement
Le Vendredi 10 F?vrier 2006 13:40, Maarten Storm a ?crit?: ... Thanks for helping. I messed up the installation myself. The scanner works now! The colors are a bit strange. Do I have to change some sane-settings or is it because of the experimental stage? Regards, Maarten Hello, scanner calibration isn't implemented at all. So current fixed setting values may not be suited. With latest experimental version, you can adjust gains manually. However, you'll still have vertical lines due to lack of shading calibration. I hope adding software shading calibration this week. Regards, Stef
[sane-devel] scanjet 2300c
Le Lundi 6 F?vrier 2006 09:24, fr?d?ric hamelin a ?crit?:
Hello,
here is the log file.
Thanks for your help !
fh
Hello,
this log is not enough. I wrongly asked you for a 'scanimage -L', while
I
needed the log of a preview... ('scanimage 2scan.log scan.pnm'). Also,
with :
export SANE_DEBUG_GENESYS=255
export SANE_DEBUG_GENESYS_GL646=255
quite a few '*.pnm' files will be created. They contain raw data read from
scanner at various calibration stages. You can send them directly to me,
since the will be too big for the list.
And last, is there a chance that you can try latest version (1.0.17) ?
Regards,
Stef
[sane-devel] scanjet 2300c
Le Dimanche 5 F?vrier 2006 17:23, fr?d?ric hamelin a ?crit?: Hello, I have Sane 1.0.16 on Mandriva 2006 and my scanjet 2300c is recognised but I can't use it : it makes a stange noise and nothing happens. Can someone help me ? Thanks Hello, in a command shell, in order to produce debugging informations,execute the following commands: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 scanimage -L 2probe.log And send the probe.log (only to me if the file is too big even compressed), so that we can find what's going on. Regards, Stef
[sane-devel] Canon Lide 60
Le Dimanche 5 F?vrier 2006 12:18, CSORDAS Laszlo a ?crit?: Canon Lide 60 working with backend MEDION MD5345 (genesys) :-))) -destitute 4 speed button- csola Hello, did you configure anything or did it work 'out of the box' ? Regards, Stef
[sane-devel] backend 1.0.17 dell A920 no movement
Le Jeudi 2 F?vrier 2006 18:41, Maarten Storm a ?crit?: Stef Thanks for your fast reply. I tried installing the experimental cvs, but still same problem. The scanner seems to start and then it locks. I think there is another problem also. I have attached the new log. Regards, Maarten Hello, it seems you are still running th 1.0.17 version of the backend, not the experimental one. You should have version 1.0-1 not : [lexmark] SANE Lexmark backend version 1.0-0 You can double check by doing 'scanimage -L', if a Dell A920 is listed, you are running the experimental version. To test withtout installing, you can go to the sane-backends/backend directory where the backend is compiled, then do export LD_PRELOAD=.libs/libsane-lexmark.so.1.0.17 so when running scanimage, xscanimage or xsane from the sane-backends/backend directory, you'll be using local version. Once everything works, you may install it. Regards, Stef
[sane-devel] backend 1.0.17 dell A920 no movement
Le Mercredi 1 F?vrier 2006 22:52, Maarten Storm a ?crit?: Hello, I have a dell A920 printer/scanner and thought that might be working with the lexmark backend in 1.0.17. It didn't work and I thought it might have to do with the dell thing. But in the january archives I read a post of someone with a lexmark with the same problem but there's no solution there. I was wondering if a solution was found there. I have a debug log made while using xsane. I only hear a lot of noice and in the scanner seems nothing to move. Hope someone can help me, Thanks, Maarten Hello, the A920 sensor is different from the one used to develop the lexmark backend. So it won't work with the current version.. However I am working adding support fo it on an experimental version. It currenly scans in color at 75/150/300 and 600 dpi. Gray scanning will come very soon. You'll have to use CVS to get the code and compile it. You'll also need sane-backends sources (1.0.17 or cvs). To get experimental lexmark do: cvs -z3 -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane co experimental/lexmark Then cd into experimental/lexmark and run links.sh giving it the path to the directory where you put sane-backend sources. Let's say it's in /usr/src : sh link.sh /usr/src/sane-backends-1.0.17 Then cd to /usr/src/sane-backends-1.0.17, do 'configure', 'make' and 'make install'. You should be able to run the A290. Regards, Stef
[sane-devel] Lexmark backend / Dell A920
Hello, I have done the planned changes in cvs/experimental/lexmark directory. The Dell A920 is partially supported since only 75 dpi color scans are working. Other modes will follow soon. Although I checked that the registers written are unchanged for the X1100, there may be bugs, since I don't have such a scanner to test. Next on my todo list is to add software shading correction, since this scanner doesn't have hardware calibration. Regards, Stef
[sane-devel] Decoding scripts for genesys backend
Hello, here are the scripts I talked to you. You run the 'cmd.sh' against the log file processed by the 'decode.sh' I sent previously. What it does is gathering high level actions, building a map of shadow registers, shading tables and motor slopes. Then it dump the complete status it at each motor start (which is used as a commit signal). So all the 'atomic' actions are gathered, and all you have to do is to compare this global status with the one of the backend at each motor start. The way I use it is to run scanimage to gut a debug log, and compare slope/registers at a particular action with the status dumped by 'cmd.sh'. Then I modify the code until both logs match. While the most interesting thing is getting data, I really do think you'll have to fix all the calibration steps before tackling with this. For a start, I'll get sure that gl646_search_start_position() does work properly, even it may almost work currently. If you need to generate new motor slope tables (as extracted by the script), I'd recommend to use the methode used by gl841. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: cmd.tar.gz Type: application/x-tgz Size: 4063 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060114/da0cd23a/cmd.tar.bin From henn...@meier-geinitz.de Sat Jan 14 14:54:13 2006 From: henn...@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat Jan 14 14:55:31 2006 Subject: [sane-devel] Fix in check-usb-chip.c for rts8822l-01h In-Reply-To: 20060113172510.ga5...@jkdsoftware.dyndns.org References: 20060113172510.ga5...@jkdsoftware.dyndns.org Message-ID: 20060114145413.gc30...@meier-geinitz.de Hi, On 2006-01-13 18:25, JKD wrote: I hope this patch improves rts8822l-01h chipset detection adding check for descriptor.bcdUSB == 0x110 reported by some scanners and accepting any value diferent to 0, read from 0xfe11 register. Thanks. It's in CVS now. Bye, Henning
[sane-devel] uninitialized variables in sane-backends
Le Jeudi 5 Janvier 2006 13:57, Johannes Meixner a ?crit?:
Hello,
in sane-backends 1.0.17 our compiler recognized the following
uninitialized variables which I simply initialized with 0:
===
--- backend/umax_pp_low.c.orig 2004-10-08 12:01:29.0 +0200
+++ backend/umax_pp_low.c 2005-05-17 15:01:59.0 +0200
@@ -6136,7 +6136,7 @@
int
sanei_umax_pp_initScanner (int recover)
{
- int i, j;
+ int i, j = 0;
int status;
int readcmd[64];
/* in umax1220u, this buffer is opc[16] */
--- backend/genesys.c.orig 2006-01-03 11:57:23.0 +0100
+++ backend/genesys.c 2006-01-03 12:04:25.0 +0100
@@ -2686,7 +2686,7 @@
u_int8_t channels;
int x, j, o;
unsigned int i;
- unsigned int coeff, target_code, val, avgpixels, dk, words_per_color;
+ unsigned int coeff, target_code, val, avgpixels, dk, words_per_color =
0;
DBG (DBG_proc, genesys_send_shading_coefficient\n);
===
In umax_pp_low.c in it seems j is incremented but never used
so that it might be better to remove j at all.
I removed this now unused variable. It is in CVS by now.
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de
90409 Nuernberg, GermanyWWW: http://www.suse.de/
Regards,
Stef
[sane-devel] extracting values from windows USB log to initialize registers for genesys GL646 backend
Le Mardi 3 Janvier 2006 11:16, Parag N a ?crit?: Hello, It seems something is going wrong with my modification to genesys backend for HP2400 so i decided to ask one simple question again to have confirmation of modification of code. Does gl646_init_regs_for_warmup and gl646_init_regs_for_scan functions must have initial values of sets of register 0x00 to 0x6f from the first set of initialized values in windows USB log? Regards, Parag. Hello, the functions setting up registers for an action only need to set those who differ from the current state of the shadow registers, as set by previous actions of the backend. It's easier that way because this means less code, and makes the register usage more obvious. The initial full state is loaded in gl646_init_regs(). Regards, Stef
[sane-devel] Require Windows USB log for HP 2300C scanner
Le Mardi 3 Janvier 2006 13:01, Henning Meier-Geinitz a ?crit?: Hi, On 2006-01-03 16:09, Parag N() wrote: Thanks for reply but logs didnt work for me as they had taken with some other usb sniffer. do you have any other working link also. No. But you could ask the person who created that website if he as more logs. Or look at the original hp2300 page, there are links to other users of this scanner: http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/html/unsupported/Attic/hp-s canjet-2300c.html?rev=1.7content-type=text/x-cvsweb-markupcvsroot=sane Also i would like to suggest you how about storing at least one original windows usb capture file + same windows decoded debug file for each scanner type under its respective backend. or at least one I won't store such data on the SANE website as its legal status is not clear, at least in some countries. The same is true for my website. working scanner analysis under each backend, so that it can be used in future for development of backedn for other scanner havinf same chipset? If there is such an analysis, I'm happy to add it to the backend homepages I maintain. Bye, Henning Hello Parag, comparing with the 2300 is a good idea. I have quite a few logs for it. This is quite big ( ~38Mb compressed). Would it fit in mail, or do you prefer some http donwload ? Regards, Stef
[sane-devel] genesys-backend and ML5345 test results with 1.0.17
Le Mardi 27 D?cembre 2005 15:20, Martin Jacobs a ?crit?: Hello, after downloading libusb-0.1.10a and 1.0.17 I repeated my tests with USB-Scanner Medion MD5345 and got the following results: Test environment: Linux box based on SuSE 8.1, dual P3 933MHz, 768MB, m/b MSI 694D-Pro (MS-6321). Resolution 100 200 300600 Color ok okok 3) ok 3) Gray ok 1,2) okok ok 3) Lineartok 1,2) ok 4) ok 4) ok 3,5) Test conditions: each scan was done at least two times. Tests have been done using scanimage. Footnotes 1) Reset of scanner (power off) does not help, hotplug service has to be restarted with unloading of module usbcore. You can generate debug logs by doing: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 scanimage 2scan.log scan.pnm Send me log of a failed scan so that I can search what's going wrong. Having USB logs of the same sort of scan under windows, recorded with 'usbsnoop' (http://benoit.papillault.free.fr/usbsnoop/index.php.en) would be great. 2) Only first scan is successful, any other fails. How does it fails ? Does it hang or do you get black/garbage image ? 3) Head is moving back and forth. This is normal. At thes resolutions the amount of data to send is higher than the USB bandwidth. The data are read slower than they are produced. So the scanner as to pause, or even go backward to the place for which data have been sent. This is commonly called 'backtracking' and is not specific to this backend. By specifying a narrower width, needed bandwidth decrease and this goes away. 4) Second scan out of 5 was scrambeled. 5) Third scan out of 5 was scrambeled. 4 and 5 are surely related, and I got one other report of this. I did try it, and obviously this doesn't happen here. However I did seen such with cvs version, but got it fixed by disabling power saving helpers. You could try to compare with SANE 1.0.16 to see if you have also this 'scrambling'. I will try it on another PC, it may be related to USB subsystem (or the way it is used by the backend). Maybe you could try this also. Is your mother board USB 1.1 or 2.0 ? Compared with sane-backends there is a great improvement! Congratulation. But why do the simple test modes Gray and Lineart fail? Regards Martin Jacobs Regards, Stef
RV: [sane-devel] Agfa Scanner
Le Lundi 12 D?cembre 2005 20:35, dmeret...@repsolypf.com a ?crit?: All/Oliver, how can I do a logic analysis? should i make it on Windows or Linux?. I would like to write a driver, but, i never did it before, if you help me, we'll do it. Thanks Hello, what you can do is to make the scanner under windows, record all the I/O flowing through parallel port, then try to understand it so that you can write a backend doing the same. This takes time, and for parallel port scanners, you are almost alone since the protocol used differ from one scanner model to another. If you still feel like doing it I can send you a custom VxD (win 98/win me only) that set hardware breakpoint on parallel port to log all in/out into a file. Since it does file access in ring 0, it has some stability issues. But it proved usefull enough to record the data (typical log is ~ 30 MB) I needed to analyse Umax 610P and 1220P protocols. Regards, Stef
[sane-devel] Genesys backend update to Dec 06, cvs
Le Mercredi 7 D?cembre 2005 10:06, Gerald Murray a ?crit?: Stef: Thanks for your comment on the no warmup will succeed area. I had not thought about that. I will continue working on it, my pace is rather slow, and I am missing the log that would show values to test/try in the registers, as I am only using Linux to work with. I am willing to do some tests with mine. Not knowing the range of values that are workable does pose some risk to the device here. best regards, Gerald Hello, since you have the scanner but not the logs, I sent you an usb log directly, since it's too big for the list. Regards, Stef
[sane-devel] GL646 part and 1.0.17 upcoming release
Le Mardi 6 D?cembre 2005 10:59, Pierre Willenbrock a ?crit?: Please move those changes over to sane-backends cvs. I forgot you were still hunting bugs. Regards, Pierre OK, it's in CVS by now. Regards, Stef
[sane-devel] Genesys HP scanjet 2400
Hello, sorry to have taken so long to answer, but I have little time and many things to do ... However, I believe it isn't helpful to modify the warmup that way. You have to set up the right register values instead. Also, you have to make sure that the scanner is using an area suitable for it, if the head is on a black area, no warmup will succeed. If I had enough time, here's how I'd do: - get a windows usb log of a colour preview, just after powering-up scanner - extract from it the values to put in genesys_devices regarding constants in Genesys_Frontend, Genesys_Sensor, Genesys_Gpo, Genesys_Motor. Current values aren't considered exact, testing is needed. - by running scanimage with full debug and comparing it's output with decode usb log, modify the genesys_gl646.c file to take 2400 specifics into account. Every places where is a xxx_HP2300 constant is a candidate. The HP2300 and MD5345 use a method to build slope tables which is superseded by the method used for GL841 parts. This newer method should be preferred. That involves using the newer exposure time comptuing function. I again attach the scripts I use to turn an usb log into something more suitable for developpement. I tested it on HP2400 logs I have. I think have all the elements to finish support for 2400 but I'm missing an essential thing: the scanner itself. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: kit.tar.gz Type: application/x-tgz Size: 7003 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051206/3fd8d673/kit.tar.bin From gerh...@gjaeger.de Wed Dec 7 07:37:11 2005 From: gerh...@gjaeger.de (Gerhard Jaeger) Date: Wed Dec 7 07:38:35 2005 Subject: [sane-devel] GL646 part and 1.0.17 upcoming release In-Reply-To: 200512062114.jb6le8hl010...@mailin.webmailer.de References: 200512062114.jb6le8hl010...@mailin.webmailer.de Message-ID: 200512070837.11559.gerh...@gjaeger.de Hi Franz, On Tuesday 06 December 2005 22:10, Franz Bakan wrote: On Tue, 6 Dec 2005 21:56:10 +0100, St?phane VOLTZ wrote: it's in CVS by now. when I try to compile CVS now on OS/2 I get: genesys_gl646.o: Undefined symbol _sanei_usb_get_timeout referenced from text segment make[1]: *** [libsane-genesys.la] Fehler 1 make: *** [all-recursive] Fehler 1 Bye Franz got the same problem here, but go ahead, and find the occurance in genesys_gl646.c - remove this line and everything is fine... HTH Gerhard
[sane-devel] HP 2400 Status
Hello, the HP2400 is no yet supported. There early elements in the genesys backend but it won't work. In theory, the 2400 is supposed to be like the 2300, but with a 1200 dpi max resolution instead of 600. What is left to do is to put the exact values needed in genesys_devices.c . These values will have to be found in usb logs of the scanner operating under windows. Then, you can use all HP2300 constants as a guide to find all the places where you'll have to update the code for 2400 handling. Be aware that doing such will use the 'old methods' for building slope tables and computing exposure. It is worth evaluating the 'new methods' used in the gl841, since we may swith the 2300 and MD5345 to it some time in the futur. One problem I got with the 2300 was the way it sets the frontend. I couldn't get it work like in the usb logs, and fall back to the working current method which modelled after the MD5345 method. I used usbsniff+ a bunch of awk scripts to decode them. They are appended to the message. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: dist.tar.bz2 Type: application/x-tbz Size: 8224 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051201/075f229b/dist.tar.bin From jsm...@suse.de Thu Dec 1 09:35:40 2005 From: jsm...@suse.de (Johannes Meixner) Date: Fri Dec 2 20:12:22 2005 Subject: [sane-devel] Epson Stylus CX4200 In-Reply-To: 7790b6530511301552n69a033dfw2f347759bbfe8...@mail.gmail.com References: 7790b6530511292210x28b8d487h86a5b098d896d...@mail.gmail.com 20051130185827.gk10...@meier-geinitz.de 7790b6530511301552n69a033dfw2f347759bbfe8...@mail.gmail.com Message-ID: pine.lnx.4.58.0512011028180@wotan.suse.de Hello, On Nov 30 18:52 Chris AtLee wrote (shortened): ... if the usblp module is claiming the device and won't let sane access it. See the Epson CX3200's scanner isn't detected with recent thread on the sane-devel mailing list: http://lists.alioth.debian.org/pipermail/sane-devel/2005-September/014721.html http://lists.alioth.debian.org/pipermail/sane-devel/2005-September/014727.html If you have Suse Linux 10.0 see http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html USB access conflicts for Epson all-in-one devices The updates of sane and iscan are also available at http://www.novell.com/linux/download/updates/index.html Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] [ANNOUNCE] Feature freeze for sane-backends 1.0.17
Le Mercredi 30 Novembre 2005 19:09, Henning Meier-Geinitz a ?crit?: Hi, On Mon, Nov 21, 2005 at 08:56:47PM +0100, St?phane VOLTZ wrote: I'm afraid that fixing gl646 part of the genesys backend may take some time. Maybe I'll have to ask for a delay. Do you have an estimate how much time you'll need to get the genesys backend working again for the gl646 scanners? Bye, Henning Hello, since Pierre has added lineart emulation. There are only 2 things left: - 'staggering' handling has a bug in gray mode - sometimes, calibration is wrong and leads to greenish scans, it happens when toggling color mode or resolution. I think a one week delay would be enough. Regards, Stef
[sane-devel] (no subject)
Le Dimanche 20 Novembre 2005 23:14, martin.jac...@an-netz.de a ?crit?: Hi, I have a MD5345 USB sanner, sane-backend 1.0.16 installed and some problems. Currently I can only scan in monochrome (gray) mode with default resolution. Any other configuration fails. In this (failing) case, the scanner head starts it's initialisation, short move forward and back and then it remains in the start position. After some time I get an timeout error. scanimage -L works scanimage -T works After having done a couple of bw scans, mostly I have to skip the first 10mm or so (shift the image about 10mm in y direction). My Linux box is dual PIII, 768 MB, based on SuSE 8.1. sane-backends-1.0.16 is compiled from scratch without problems. Any idea, how to fix those problems? Most important are color scans. Regards Martin Jacobs Hello, could you please do : export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 Then do scanimage --resolution=100 --mode=color 2scan.log out.pnm Then send me the 'scan.log' file, maybe directly since there is a 45K threshold on the posts within this list. I hope the differences between your MD5345 and my MD6471 aren't big, since htey share the same USB ID and it could be difficult to autodetect which is plugged ... Regards, Stef
[sane-devel] [ANNOUNCE] Feature freeze for sane-backends 1.0.17
Le Lundi 21 Novembre 2005 18:37, Henning Meier-Geinitz a ?crit?: Hi everyone, Feature freeze for sane-backends 1.0.17 is now active. This means, that no new backends or new features for existing backends should be committed to CVS anymore. Bug fixes, documentation and translation updates are still ok. Time table: 2005-12-04 Code freeze 2005-12-11 Release After code freeze only fixes of grave bugs that render a backend completely unusable or break compilation and documentation updates are accepted. There have been quite some changes since the last release. Therefore please test the current version of sane-backends carefully, so all bugs are found until release. Current snapshots are available here: I'm afraid that fixing gl646 part of the genesys backend may take some time. Maybe I'll have to ask for a delay. Regards, Stef
[sane-devel] genesys backend
Hello, there are quite some issues with gl646: - 250, 400 and 500 dpi modes fail with 'invalid argument'. - lineart mode is broken . - after a few scan, especially when changing dpi, I get 'color noise' instead of pictures. Restarting the scanning program fix it. Regards, Stef
[sane-devel] HP ScanJet 2400c
Le Lundi 14 Novembre 2005 21:54, carlos a ?crit?: Hi Stef, I know how to program in C, but I know nothing about how a scanner works, in any case, I have an hp2400c which has been doing a great job as a brick, if you would be so kind so as to send me those scripts I may give it a try to write a backend for that scanner. thanks, carlos. Hello, here they are. Don't hesitate to ask further questions on the list. Regards, Stef -- next part -- A non-text attachment was scrubbed... Name: scripts.tar.bz2 Type: application/x-tbz Size: 8219 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051117/804ea5a8/scripts.tar.bin From lno...@dragon.unideb.hu Thu Nov 17 08:17:34 2005 From: lno...@dragon.unideb.hu (Levente =?ISO-8859-1?Q?Nov=E1k?=) Date: Thu Nov 17 08:33:08 2005 Subject: [sane-devel] Re: Re: Re: epson 3490 - transparency unit problem In-Reply-To: 200511162349.28532.oliver.schwa...@gmx.de References: 4376277f.3090...@free.fr 200511152113.01824.oliver.schwa...@gmx.de 437b7dfb.20...@free.fr 200511162349.28532.oliver.schwa...@gmx.de Message-ID: 1132215454.12161.7.ca...@novak.chem.klte.hu On Wed, 2005-11-16 at 23:49 +0100, Oliver Schwartz wrote: I can somehow understand that it happens at 2400 dpi. In fact I think that 2400 dpi won't ever work and should be disabled, or replaced by 1800 dpi, which should be ok. Please wait until I test it out. And I suppose you meant 1600 dpi (which is a multiple of 800) instead of 1800 dpi (and Patrick wanted to say 3200 dpi instead of 3600). AFAIK our scanner's maximum resolution is 3200 dpi. If I'm right, the PF 3490 has a 800 dpi of linear CCD resolution, higher ones are 'faked' by offsetted sensor elements. In this case multiples of 800 should work. I'm a bit surprised about the effect at 3600 dpi. Can you send me an image which shows the effect? I did not have any problems at 3200 dpi. And before the CVS change, the only problem was the now solved interlacing phenomenon. Levente
[sane-devel] HP ScanJet 2400c
Le Lundi 7 Novembre 2005 18:49, Kristoffer a ?crit?: On Mon, 07 Nov 2005 17:49:06 +0100, Kristoffer k...@online.no wrote: I want to get it working! And I see that the genesys author in genesys.conf have it commented out and to be uncommented only for development purposes. Can the author comment on the state of 2400? I would be delighted to help, Maybe i could also make the support in genesys backend complete for this driver, if he/you can't, but since i've never made a c program before(or anything other than very basic bash/dos batch scripts and MMF) i could use some help. what i'm thinking is 1. grab the source 2. change the code to what it looks like windows driver is doing(by snooping) 3. then i'd need help on howto compile it and test it fast to see if it is functioning correctly. 4.maybe you could implement it in your driver or tell me howto ;) hey it's fun! If you wish, I can provide you with my awk scripts that turn usb logs into low/mid level genesys functions. Which ease the developpement. I'd recommend to play with sane 1.016 sources, since the experimental version is now not working any more for hp2300/md6471 due to some exposure_time improvement. When this will be resolved, you may bring back you change into it. The code path to modifiy is the one taken by th hp2300 (look fo HP2300) in code. You'll have to figure how the right register related constants to put into genesys_devices.c . Regards, Stef
[sane-devel] Compiling: make doesn't do anything?
Hello, shouldn't the 'depend' target take care of dependencies ? After a 'make depend', everything should work fine. You can avoid installing each time by using the LD_PRELOAD environment variable and running xsane from the backend subdir: export LD_PRELOAD=.libs/libsane-mybackend.so.1.0.16 Regards, Stef
[sane-devel] TWAIN 2.0 targetting Linux
Le Lundi 10 Octobre 2005 10:23, Ren? Rebe a ?crit?: Hi all, aside my SANE Avision backend I do various other stuff - including a commercial TWAIN driver, recently. I noticed the TWAIN 2.0 work in progress list includes the target Linux and a rewritten Data Souce Manager released under /a/ /open/ source license. http://www.twain.org/docs/TWAIN2.pdf I'm not sure if I'm too happy about that, since it might bring new diversity into the already difuse Linux land and might hinder SANE 2 from ever beeing started. What do other think? Hello, I believe this is a great thing. Some time in the future, people will be able to bought scanner with the software to have it run immediatly under linux. It is what most people (including me) want. A good point for the so-called 'linux desktop'. The diversity wouldn't be a bad thing. We can think the situation would be like for video drivers were ATI/NVidia provides closed sources drivers, and the free software community open ones. People have then the choice, which is good. Personnaly, this wouldn't make me stop working on SANE. I do it for fun, and this won't go away. I'm sure there will be still scanners 'windows only' in the future to keep the 'game' interesting. Regards, Stef
[sane-devel] Lexmark X1100 backend available
Le Mardi 27 Septembre 2005 15:55, Henning Meier-Geinitz a ?crit?: Hi, On Mon, Sep 26, 2005 at 08:06:09PM -0400, Fred Odendaal wrote: Currently, I use the size to set the window so having a freely selectable range wouldn't be much of a stretch. However, the motion of the scan head is jerky at some sizes so I don't think I have it fully figured out yet. Just to make this clear: My comments about the fixed sizes doesn't mean that the backend can't be added to CVS the way it currently is. I was just curious because most backends use free window sizes. Bye, Henning Hello, since I'm also fiddling with a Dell A920 (a X1100 in fact, only USB id change...), I can tell you that the register details available at http://www.lychnis.net/wiki/HP3500C are really accurate, since the rts8858 is only slightly different. Horizontal position is expressed in pixel at sensor hardware dpi in registers 0x66-0x67 and 0x6c-0x6d. Vertical position is given by registers 0x60-0x61 and 0x62-0x63. Regards, Stef
[sane-devel] genesys backend
Hello, it looks genesys_reorder_components_cis_8 and genesys_reorder_components_cis_16 are missing from your patch. The quick test I did hang at the end of scan (which happens when we try to read more data than the scanning area holds). Is there a test case where a scan succeeds ? I'd like to time how it takes for a scan. Because my main concern is that (as you wrote in a previous mail) data may be copied too much. For the rest, I gone through your code, and it looks sensible to me. What I need is a test case that allow me to compare speed to make up my mind. Regards, Stef
