[sane-devel] HP ScanJet 5300c only partially detected
Hi, On 2006-05-12 18:46, Damon Butler wrote: If this doesn't happen, try: SANE_DEBUG_DLL=255 scanimage -L and send the output. I set both environment variables, and here's the output I got. [...] [avision] sane_init: Trying to find USB device 3f0 701 ... [avision] sane_init: Trying to find USB device 3f0 701 ... This is the id of the HP 5300c. It doesn't seem to be plugged in. Are you sure that this is your device? The id you gave in your original posting is the one of the HP 3500. That scanner is supported only by the development version of sane-backends. Bye, Henning
[sane-devel] LIDE 60
Hi, On 2006-05-13 17:24, Trent Michael Gamblin wrote: Hi. I have a Canon LiDE 60, and the product ID is 0x221c. Otherwise it's the same as the LiDE 50. You can add it to the list of scanners. Thanks. Thanks. It's already in our lists: http://www.sane-project.org/cgi-bin/driver.pl?manu=canonmodel=%22LiDE+60%22bus=anyv=p= Bye, Henning
[sane-devel] Nikon CoolScan IV and next sane release
Giuseppe, Henning, another problem I think I found on this patch is at about line 1525 of the patched file, where it is i = (xfer_len_in 0x3f); while it should be i = (xfer_len_in 0x3f); with a single ampersand. I'm afraid I haven't had time recently to do anything about the coolscan2 backend, and SANE-devel email delivery has been quite intermittent over here (I only got one copy of this email, for instance, although you sent it both to the list and to me separately). I'm so tied up in other things that I won't have time to work on SANE for a while, so I'd appreciate it if someone else took care of coolscan2 instead. I only have an LS-4000 and therefore can't really help with the LS-5*, which I've tried to get working several times by remote access (without success, though). The one thing I'd like to avoid is seeing SANE development retarded because of me. I'd like to believe that the backend is written in a reasonably readable way, so adding support for new scanners shouldn't be hard provided the new code is either tested for backward compatibility or made conditional based on the type of scanner. I've also found that it's a good idea to use case switches for this without specifying a default case -- gcc will then warn you if you've forgotten to list any type of scanner. Andras
[sane-devel] About Backend driver for Canon/HP USB scanner
Hi folks, FedoraCore5 64 bit I'm considering to purchase either USB CanoScan 4200F (preferrable) or USB HP Scanjet 4370. But they are unsupported on SANE. [url]http://www.sane-project.org/sane-mfgs.html#Z-CANON[/url] [url]http://www.sane-project.org/sane-mfgs.html#Z-HEWLETT-PACKARD[/url] I have been searching The sane-devel Archives [url]http://lists.alioth.debian.org/pipermail/sane-devel/[/url] and could not find available Backend driver for them. Can any folk on the forum shed me somelight. TIA Furthermore I found; http://lists.alioth.debian.org/pipermail/sane-devel/2005-August/014256.html http://lists.alioth.debian.org/pipermail/sane-devel/2005-August/014398.html Hi serja, Could you please post the link. TIA B.R. SL
[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] CanoScan LiDE20 still jamming
On Sunday 14 May 2006 19:26, Fibonacci Prower wrote: Hello, I tried downloading the sources for the SANE frontends and backends from http://www.sane-project.org/source.html. Then compiled and installed them under Fedora Core 5, ran scanimage, and my scanner (a CanoScan LiDE20 USB) jammed right at the beginning, with the lamps on. Then, I booted Knoppix, copied to ramdisk the same sources I had downloaded, compiled and installed just as I had done under Fedora, ran scanimage, and the scanner worked without a problem! What can I do to make my scanner work under Fedora? Tell me which version of SANE is incluced in Knoppix, to find out the diffs. Ciao Gerhard
[sane-devel] CanoScan LiDE20 still jamming
2006/5/15, Gerhard Jaeger gerh...@gjaeger.de: On Sunday 14 May 2006 19:26, Fibonacci Prower wrote: Hello, I tried downloading the sources for the SANE frontends and backends from http://www.sane-project.org/source.html. Then compiled and installed them under Fedora Core 5, ran scanimage, and my scanner (a CanoScan LiDE20 USB) jammed right at the beginning, with the lamps on. Then, I booted Knoppix, copied to ramdisk the same sources I had downloaded, compiled and installed just as I had done under Fedora, ran scanimage, and the scanner worked without a problem! What can I do to make my scanner work under Fedora? Tell me which version of SANE is incluced in Knoppix, to find out the diffs. I don't remember (it's Knoppix 4.0.2, though). But is it really relevant? I didn't use the version that came with Knoppix, but the sources which I had already downloaded on Fedora, which, I believe, are version 1.0.17 for the backends, and 1.0.14 for the frontends. Ciao Gerhard -- 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 -- Eye halve a spelling chequer, it came with my pea see It plane lee marques four my revue miss steaks aye can knot sea Eye ran this poem threw it - your shore reel glad two no Its vary polished in it's weigh, my chequer tolled me sew.
[sane-devel] CanoScan LiDE20 still jamming
On Monday 15 May 2006 09:29, Fibonacci Prower wrote: 2006/5/15, Gerhard Jaeger gerh...@gjaeger.de: On Sunday 14 May 2006 19:26, Fibonacci Prower wrote: Hello, I tried downloading the sources for the SANE frontends and backends from http://www.sane-project.org/source.html. Then compiled and installed them under Fedora Core 5, ran scanimage, and my scanner (a CanoScan LiDE20 USB) jammed right at the beginning, with the lamps on. Then, I booted Knoppix, copied to ramdisk the same sources I had downloaded, compiled and installed just as I had done under Fedora, ran scanimage, and the scanner worked without a problem! What can I do to make my scanner work under Fedora? Tell me which version of SANE is incluced in Knoppix, to find out the diffs. I don't remember (it's Knoppix 4.0.2, though). But is it really relevant? I didn't use the version that came with Knoppix, but the sources which I had already downloaded on Fedora, which, I believe, are version 1.0.17 for the backends, and 1.0.14 for the frontends. So for the records: - booting Fedora Core 5 AND using the self-compiled CVS-SANE, the Lide20 jams - booting Knoppix 4.0.2 AND using also the self-compiled CVS-SANE, the Lide20 works Is that right? If not, I really need to know the version of the Plustek- Backend that is working to fix that! You might wanna start Fedora and then try: export SANE_DEBUG_PLUSTEK=10 ; scanimage -L right at the beginning you'll get something like: Plustek backend V0.51-9, part of sane-backends 1.0.17-cvs Send me that output and repeat that with Knoppix. TIA Gerhard
[sane-devel] CanoScan LiDE20 still jamming
2006/5/15, Gerhard Jaeger gerh...@gjaeger.de: On Monday 15 May 2006 09:29, Fibonacci Prower wrote: 2006/5/15, Gerhard Jaeger gerh...@gjaeger.de: On Sunday 14 May 2006 19:26, Fibonacci Prower wrote: Hello, I tried downloading the sources for the SANE frontends and backends from http://www.sane-project.org/source.html. Then compiled and installed them under Fedora Core 5, ran scanimage, and my scanner (a CanoScan LiDE20 USB) jammed right at the beginning, with the lamps on. Then, I booted Knoppix, copied to ramdisk the same sources I had downloaded, compiled and installed just as I had done under Fedora, ran scanimage, and the scanner worked without a problem! What can I do to make my scanner work under Fedora? Tell me which version of SANE is incluced in Knoppix, to find out the diffs. I don't remember (it's Knoppix 4.0.2, though). But is it really relevant? I didn't use the version that came with Knoppix, but the sources which I had already downloaded on Fedora, which, I believe, are version 1.0.17 for the backends, and 1.0.14 for the frontends. So for the records: - booting Fedora Core 5 AND using the self-compiled CVS-SANE, the Lide20 jams - booting Knoppix 4.0.2 AND using also the self-compiled CVS-SANE, the Lide20 works Not CVS. I'm using the latest stable sources from http://www.sane-project.org/source.html. But apart from that, everything you said is right. Is that right? If not, I really need to know the version of the Plustek- Backend that is working to fix that! You might wanna start Fedora and then try: export SANE_DEBUG_PLUSTEK=10 ; scanimage -L I've attached the log. right at the beginning you'll get something like: Plustek backend V0.51-9, part of sane-backends 1.0.17-cvs [plustek] Plustek backend V0.50-7, part of sane-backends 1.0.17 Send me that output and repeat that with Knoppix. I'll check Knoppix on next reboot. TIA Gerhard -- 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 -- Eye halve a spelling chequer, it came with my pea see It plane lee marques four my revue miss steaks aye can knot sea Eye ran this poem threw it - your shore reel glad two no Its vary polished in it's weigh, my chequer tolled me sew. -- next part -- A non-text attachment was scrubbed... Name: fedora.log Type: text/x-log Size: 9248 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060515/b4d19305/fedora-0001.bin From son...@mathematik.tu-chemnitz.de Mon May 15 09:44:43 2006 From: son...@mathematik.tu-chemnitz.de (Ralph Sontag) Date: Mon May 15 09:44:54 2006 Subject: [sane-devel] LiDE 500F: how to go further? In-Reply-To: 4464fa2d.8060...@pirsoft.dnsalias.org References: 200605021417.39020.chri...@attglobal.net 200605021830.56197.chri...@attglobal.net pine.lnx.4.61.0605021338560.19...@limos.pfeiffer.edu 200605032139.27907.chri...@attglobal.net pine.lnx.4.61.0605041002530.14...@catan.informatik.tu-chemnitz.de 445d1051.5050...@pirsoft.dnsalias.org pine.lnx.4.61.0605081140090.7...@catan.informatik.tu-chemnitz.de 4464fa2d.8060...@pirsoft.dnsalias.org Message-ID: pine.lnx.4.61.0605151138570.7...@catan.informatik.tu-chemnitz.de Hi Pierre, Your scanner is 2400dpi x 4800dpi? Perhaps the attached patch is more usable. It reduces the maximum speed of the head, and adjusts the maximum y-resolution. yes, it is 2400dpi x 4800dpi. These scanners are pretty low-level. To do anything useful, you need to setup the motor and ccd. This includes calibration. The calibration is done only once in win98. So I will setup win98 once again and made a start the sniffer before the first connect. I put my scripts here: http://pirsoft-dsl-dropzone.de Fine - but I got a error 403: Forbidden for http://pirsoft-dsl-dropzone.de/usbsnoop-stage1.pl http://pirsoft-dsl-dropzone.de/usbsnoop-collect.pl Can you send me the files or made it available? After patching with the new patch, the scanner ist jerking in a frequency around 30 Hz, but it make no move. Thanks! Ralph. -- Ralph Sontag | Str. der Nationen 62/B204 | 09107 Chemnitz | MIME | e-mail: son...@mathematik.tu-chemnitz.de | Tel. +49 371 531 31384 | welcome! |
[sane-devel] LiDE 500F: how to go further?
Hi Ralph, Ralph Sontag schrieb: These scanners are pretty low-level. To do anything useful, you need to setup the motor and ccd. This includes calibration. The calibration is done only once in win98. So I will setup win98 once again and made a start the sniffer before the first connect. I put my scripts here: http://pirsoft-dsl-dropzone.de Fine - but I got a error 403: Forbidden for http://pirsoft-dsl-dropzone.de/usbsnoop-stage1.pl http://pirsoft-dsl-dropzone.de/usbsnoop-collect.pl Can you send me the files or made it available? I didn't check the permissions after upload, sorry. Should be available now. After patching with the new patch, the scanner ist jerking in a frequency around 30 Hz, but it make no move. So, there is still something missing. I will try to create another patch during this week. Regards, Pierre
[sane-devel] Fujitsu backend update 7
On Saturday 13 May 2006 20:53, Giuseppe Sacco wrote: fi-4010CU Most probably Avision. Can you try adding the ID into the avision backend and give it a try? A USB snoop of the window driver would be nice as well. Yours, -- Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany) http://exactcode.de | http://t2-project.org | http://rebe.name +49 (0)30 / 255 897 45
[sane-devel] OCR software
Hi, On Sunday 14 May 2006 04:39, Greg Furmanek wrote: Hi gang :-) I have been lurking on the list for quite some time. There are a lot of good info I got from you guys. I am just wondering if you have any recommendations when it comes to open source OCR libraries. It would be nice if they were portable to win32 but not necessary. I am mostly interested in the recognition algorithms and techniques. There are some open source OCR engines available - you might like to review: http://jocr.sourceforge.net/ http://freshmeat.net/projects/ocrad/ http://freshmeat.net/projects/claraocr/ http://freshmeat.net/projects/ocre/ However for my taks none has an recognition ratio high enough to be useful :-( Yours, -- Ren? Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany) http://exactcode.de | http://t2-project.org | http://rebe.name +49 (0)30 / 255 897 45
[sane-devel] cmd.sh script not working on windows Log
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.
[sane-devel] Please Help with Epson Stylus CX-5800
Hi Craig, Cc:d sane-devel@lists.alioth.debian.org for the record. Craig Setera craigj...@setera.org writes: Olaf, Thanks for your response. It appears that iscan does support this scanner. Does iscan replace sane or does sane take advantage of iscan? I'd like to get remote scanning going using winsane, so that is why I'd like to make sure I have full Sane support. Hate to disappoint you, but the Avasys site gives me a This driver is currently not supported. It is scheduled for release though, so please check again in a couple of days. for the scanner driver part. I think you only got the printer driver. As for iscan, it contains a SANE backend (epkowa, modified from the regular epson backend) and a SANE frontend that only works with the epkowa backend. FYI, you can use it with the net backend as well but only for devices supported by the epkowa backend. You can use the epkowa backend with any SANE frontend. Iff the CX-5800 will be supported by iscan, it will be through one of those binary-only interpreter modules that only work on i386 systems. The epkowa backend uses them if they are installed and your device seems to need one. If the appropriate interpreter for your device is not installed, it will be treated as unsupported by the epkowa backend. Also, do you know of any reason that the Debian binaries would not install on my Ubuntu Dapper system? If so, I can compile from source, but it would be nice to use the package if possible. There are, to the best of my knowledge, no Debian packages for iscan. That notwithstanding, I am not aware of any reason why the open source part would not work on Debian. Last time I checked (iscan-1.18.0), it worked fine even with that libesmod BLOB on Debian testing. # Just pulled down iscan-2.0.0 today. # FTR, the main developer of iscan (hey, that's me!) does all his work # hacking on Debian testing (and has of course full access to all the # closed source bits for native compilation). On the other side of # the boundary, I do all my home hacking on Debian testing using the # released source tarballs - no access to closed sources. Hope this helps, Thanks, Craig Olaf Meeuwissen wrote: Hi Craig, I saw your mail on the list but did not have time to look at this at work. I've taken a look at the usbsnoop log you made. The CX-5800 obviously doesn't use the ESC/I protocol assumed and supported by the epson and epkowa backends. As Oliver already confirmed that it also does not use the SnapScan protocol, changes are slim that it will work at all but you could give the plustek backend a chance (at the risk of damaging your device, mind you!). The EPSON Perfection 1250 and 1260 are supported by this backend. # Gerhard, could you take a look at the logs to see if there is even a # chance? If that also doesn't work you could inquire whether the CX-5800 will eventually be supported by iscan (and therefore the epkowa backend) via a proprietary and binary-only plugin at the Avasys website. http://www.avasys.jp/ Craig Setera craigj...@setera.org writes: Oliver, thanks for taking a look. For those kinds souls that would be willing to take a look, the USB snoop log is stashed up on my web site. You can grab it from here http://www.gizmo-a-gogo.org/sane/usbsnoop.zip Thanks, Craig Oliver Schwartz wrote: Hi, I've taken a look at the USB trace the Craig provided. The protocol of the scanner is not compatible with the SnapScan protocol. Maybe one of the epson backend maintainers is able to help. /Oliver On 2006-05-06 21:25, Craig Setera wrote: I just bought an Epson Stylus CX-5800 All-In-One machine the other day This scanner is not in our lists at all so it's not known, if it is supported at all. Maybe the epkowa backend maintainer knows more about this scanner? Maybe it works with the snapscan backend? Bye, Henning Hope this helps, -- Olaf Meeuwissen FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 30EF893A/2774 815B DE83 06C8 D733 6B5B 033C C857 30EF 893A Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] LiDE 500F: how to go further?
Hi Pierre, I put my scripts here: http://pirsoft-dsl-dropzone.de I made a new scan: 0 .. ~ 5 MB : USB starts 5 .. ~ 15 MB : ScanGear - the Canon-Program starts 15 .. ~ 110 MB : Calibration. 110 .. ~ 200 MB : Scan (visiting card, 300, ca. 1.5 MB) 200 .. ~ 215 MB : ScanGear ends So I have 215 MB raw log file, and after running the scripts 168.8 MB. I've put it to http://www-user.tu-chemnitz.de/~sontag/sane/ (bzip2, 21 MB). It's very usefull to pipe the file in uniq -c - it enlarges the size, but we can jump over the block of identical lines. At first lot of blocks of 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, are read. The last of this blocks ends at line 65433, then the scanner starts writing blocks: write_register(0x00) set_write_register(0x2b, 0x00) set_register(0x3c) buf_prepaccess(0xf000,BULK_OUT) Data: 01 00 82 00 00 f0 00 00 Index: 0 BULK(61440) 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, ... next block around line 73122: 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, buf_prepaccess(0xf000,BULK_OUT) Data: 01 00 82 00 00 f0 00 00 Index: 0 BULK(61440) 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, This repeats 4 times until line 98226: 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, set_write_register(0x2a, 0x00) set_write_register(0x2b, 0x00) set_register(0x45) buf_prepaccess(0x00040002,BULK_IN) Data: 00 00 82 00 02 00 04 00 Index: 0 BULK(65024) 0xeb, 0xff, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, - and I think, here the calibration starts with setting registers and write data. But I can'nt interprete these registers ... Greetings! Ralph. -- Ralph Sontag | Str. der Nationen 62/B204 | 09107 Chemnitz | MIME | e-mail: son...@mathematik.tu-chemnitz.de | Tel. +49 371 531 31384 | welcome! |
[sane-devel] Please Help with Epson Stylus CX-5800
Hi Craig, Cc:d sane-devel@lists.alioth.debian.org for the record. Craig Setera craigj...@setera.org writes: Olaf, Thanks for your response. It appears that iscan does support this scanner. Does iscan replace sane or does sane take advantage of iscan? I'd like to get remote scanning going using winsane, so that is why I'd like to make sure I have full Sane support. Hate to disappoint you, but the Avasys site gives me a This driver is currently not supported. It is scheduled for release though, so please check again in a couple of days. for the scanner driver part. I think you only got the printer driver. As for iscan, it contains a SANE backend (epkowa, modified from the regular epson backend) and a SANE frontend that only works with the epkowa backend. FYI, you can use it with the net backend as well but only for devices supported by the epkowa backend. You can use the epkowa backend with any SANE frontend. Iff the CX-5800 will be supported by iscan, it will be through one of those binary-only interpreter modules that only work on i386 systems. The epkowa backend uses them if they are installed and your device seems to need one. If the appropriate interpreter for your device is not installed, it will be treated as unsupported by the epkowa backend. Also, do you know of any reason that the Debian binaries would not install on my Ubuntu Dapper system? If so, I can compile from source, but it would be nice to use the package if possible. There are, to the best of my knowledge, no Debian packages for iscan. That notwithstanding, I am not aware of any reason why the open source part would not work on Debian. Last time I checked (iscan-1.18.0), it worked fine even with that libesmod BLOB on Debian testing. # Just pulled down iscan-2.0.0 today. # FTR, the main developer of iscan (hey, that's me!) does all his work # hacking on Debian testing (and has of course full access to all the # closed source bits for native compilation). On the other side of # the boundary, I do all my home hacking on Debian testing using the # released source tarballs - no access to closed sources. Hope this helps, Thanks, Craig Olaf Meeuwissen wrote: Hi Craig, I saw your mail on the list but did not have time to look at this at work. I've taken a look at the usbsnoop log you made. The CX-5800 obviously doesn't use the ESC/I protocol assumed and supported by the epson and epkowa backends. As Oliver already confirmed that it also does not use the SnapScan protocol, changes are slim that it will work at all but you could give the plustek backend a chance (at the risk of damaging your device, mind you!). The EPSON Perfection 1250 and 1260 are supported by this backend. # Gerhard, could you take a look at the logs to see if there is even a # chance? If that also doesn't work you could inquire whether the CX-5800 will eventually be supported by iscan (and therefore the epkowa backend) via a proprietary and binary-only plugin at the Avasys website. http://www.avasys.jp/ Craig Setera craigj...@setera.org writes: Oliver, thanks for taking a look. For those kinds souls that would be willing to take a look, the USB snoop log is stashed up on my web site. You can grab it from here http://www.gizmo-a-gogo.org/sane/usbsnoop.zip Thanks, Craig Oliver Schwartz wrote: Hi, I've taken a look at the USB trace the Craig provided. The protocol of the scanner is not compatible with the SnapScan protocol. Maybe one of the epson backend maintainers is able to help. /Oliver On 2006-05-06 21:25, Craig Setera wrote: I just bought an Epson Stylus CX-5800 All-In-One machine the other day This scanner is not in our lists at all so it's not known, if it is supported at all. Maybe the epkowa backend maintainer knows more about this scanner? Maybe it works with the snapscan backend? Bye, Henning Hope this helps, -- Olaf Meeuwissen FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 30EF893A/2774 815B DE83 06C8 D733 6B5B 033C C857 30EF 893A Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] dell1600n_net backend
Hi, On 2006-05-11 21:47, Jon Chambers wrote: On Wed, 10 May 2006, Julien BLACHE wrote: Create an account on http://alioth.debian.org and give us your login name so you can be added to the sane project. My login is phap016-guest. I just added you to the project. It can take some hours until CVS write access works. Bye, Henning
[sane-devel] dell1600n_net backend
Hi, On 2006-05-10 07:44, Julien BLACHE wrote: backend myself as a diff to the most recent major release until it is stable or can it be got into the main repository before that? Henning will correct me if I'm wrong, but the backend can probably go in if it has at least basic support for the scanner and won't cause data loss if something goes wrong. Yes, my rule of thumb is something like if it does something useful, complies with the rules in backend-writing.txt (and the SANE standard), doesn't break compilation and doesn't cause hardware damage it can go in. For more fine-grained control we have the status levels for each scanner. Bye, Henning
[sane-devel] LiDE 500F: how to go further?
Hi Ralph, Ralph Sontag schrieb: Hi Pierre, I put my scripts here: http://pirsoft-dsl-dropzone.de I made a new scan: 0 .. ~ 5 MB : USB starts 5 .. ~ 15 MB : ScanGear - the Canon-Program starts 15 .. ~ 110 MB : Calibration. 110 .. ~ 200 MB : Scan (visiting card, 300, ca. 1.5 MB) 200 .. ~ 215 MB : ScanGear ends So I have 215 MB raw log file, and after running the scripts 168.8 MB. I've put it to http://www-user.tu-chemnitz.de/~sontag/sane/ (bzip2, 21 MB). It's very usefull to pipe the file in uniq -c - it enlarges the size, but we can jump over the block of identical lines. Didn't know about uniq. Thanks for the hint. At first lot of blocks of 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, 0x55, are read. Not exactly. First the driver fills main memory with 0x55, (BULK means bulk output), each time preparing the bulk-transfer with a buf_prepaccess. Then it reads all the memory back in one read(scattered over multiple usb bulk in packets, BULK). The same for 0xaa. Just the driver checking the memory. The write register for main memory is 0x3c, the read register is 0x45. It does the same for gamma memory. Similar for some registers. But the accesses before this are interesting, too. The driver fiddles with the gpio pins, which may be the key to get the scan head moving. The last of this blocks ends at line 65433, then the scanner starts writing blocks: write_register(0x00) set_write_register(0x2b, 0x00) set_register(0x3c) buf_prepaccess(0xf000,BULK_OUT) Data: 01 00 82 00 00 f0 00 00 Index: 0 BULK(61440) 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, ... next block around line 73122: 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, buf_prepaccess(0xf000,BULK_OUT) Data: 01 00 82 00 00 f0 00 00 Index: 0 BULK(61440) 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, This repeats 4 times until line 98226: 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, set_write_register(0x2a, 0x00) set_write_register(0x2b, 0x00) set_register(0x45) buf_prepaccess(0x00040002,BULK_IN) Data: 00 00 82 00 02 00 04 00 Index: 0 BULK(65024) 0xeb, 0xff, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, 0xaa, - and I think, here the calibration starts with setting registers and write data. But I can'nt interprete these registers ... Datasheets can be downloaded here: http://www.genesyslogic.com/ Also try the other languages. At least for one gl84x there is a datasheet available on one of the non-english pages, but not on the english pages. It is currently not clear to me, which chip is in your scanner. Regards, Pierre
[sane-devel] OCR software
Greg Furmanek g...@esdlc.com writes: Hi gang :-) I have been lurking on the list for quite some time. There are a lot of good info I got from you guys. I am just wondering if you have any recommendations when it comes to open source OCR libraries. It would be nice if they were portable to win32 but not necessary. I am mostly interested in the recognition algorithms and techniques. I am only aware of the following bits of free software. Have not used any of them. gocr - (sorry no URL handy) hocr - http://hocr.berlios.de/ ocrad - http://www.gnu.org/software/ocrad/ocrad.html BTW, hocr-gtk says it's for Hebrew OCR. Hope this helps, -- Olaf Meeuwissen FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 30EF893A/2774 815B DE83 06C8 D733 6B5B 033C C857 30EF 893A Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] Epson Perfection V700 Photo
Henning Meier-Geinitz henn...@meier-geinitz.de writes: Hi, On 2006-05-10 10:50, Fredrik Sandstrom wrote: I'm considering buying the scanner of the Subject line, but it seems it's not (yet?) supported by any SANE backend. What's its status, has anyone tried it, and can it be expected to be supported soon? As it's not in our list, nobody has reported anything about it. So we don't know. If it's compatible to some alsready supported scanners, it may be easy to support it. If it's a completely new scanner with a new chip set, this means developing a new backend. This is up to a user of such scanners. Usually, it won't be done by any of the current SANE developers. I have a hunch that this scanner speaks the ESC/I protocol. Try adding the USB device info directly to the epson.conf file but don't blame me if that breaks your scanner. If anyone can make a USB log from the Windows driver available I should be able to tell whether the Perfection V700 speaks ESC/I or not. Hope this helps, -- Olaf Meeuwissen FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 30EF893A/2774 815B DE83 06C8 D733 6B5B 033C C857 30EF 893A Penguin's lib! -- I hack, therefore I am -- LPIC-2
