[sane-devel] [PATCH] Add support to snapscan for Benq Scanwit 2720S film scanner
Andrew, >> What is the current status? > > I would call it at least 'Good'. I have used this code to scan over a hundred > negatives. But then only I have used it. Others may want something else. I am > open to adding to it although I would prefer to get an initial implementation > committed before doing so. Thanks again for your work. I've committed your revised patch to GIT now, with just one additional change to snapscan.desc to get the scanner listed on the sane-project homepage. Kind regards, Oliver
[sane-devel] Support for Benq Scanwit 2720S
Andrew, I'm sorry, but I haven't received any emails from you lately. The last message I got from you is from January 26th. Can you please resent your emails, I'll double check for any over-eager spam filter. Kind regards, Oliver > I was working with Oliver Schwartz to add support to the snapscan backend for > the Benq Scanwit 2720S, a SCSI film scanner. This was greatly helped by also > referring to the incomplete scanwit backend by Max Ushakov. Oliver has not > responded to my emails for several weeks now. There was a problem early on > when my email landed in his spam folder but he does not have much time spare > at the moment anyway and his replies often took some time to come back so I > am not sure if he is just busy or my emails are going astray. > I have a patch ready that I would like to be reviewed and then possibly > committed. Is anyone in contact with Oliver? Is there someone else who can > look at this patch?
[sane-devel] Benq S2W 4300U Scanner...
Zed, the log from "scanimage -L" looks fine (there is no error in the log) and the console output shows that the scanner is correctly detected. The Gtk-warnings are xsane related and you can probably ignore them. If you still cannot scan in xsane I need the backend log while running xsane, i.e. run SANE_DEBUG_SNAPSCAN=255 xsane 2>snapscan.log and send me the log file, together with the actual error message from xsane. Please compress the log before sending if it's more than a few kilobytes. Regards, Oliver On 04.02.2010, at 20:59, Zed wrote: > I attach a copy of the logfile, together with the result of terminal > commands running as Root and as user, in the hope that it may be of > some > assistance.
[sane-devel] Benq S2W 4300U Scanner...
Hi, >> Please remove the line containing the USB device from your config >> file >> (/dev/usb/scanner0) - it's no longer useable for systems using >> libusb and >> the specified device does not exist on your system. After removing >> the >> line the scanner should be found automatically. > > Thsnk you for your quick response. > > Did as you suggested but still get the error message: Error. Failed > to open > device snapscan:libusb:002:003: Error during device I/O > > lusb confirms that the scanner is Bus 002 Device 003: ID 04a5:20b0 > Acer > Peripherals Inc. (now BenQ Corp.) A2W 3300U4300U. To rule out permission problems you should try to run scanimage as root. If that still results in an error please send a log file with SANE_DEBUG_SNAPSCAN=255 scanimage -L 2>snapscan.log Regards, Oliver
[sane-devel] Benq S2W 4300U Scanner...
Hi, On 02.02.2010, at 10:09, Zed wrote: > I am using LinuxMint v8.0 and having difficulty in getting my Benq > S2W 4300U > Scanner to work on my system. > > After installing u176v046.bin in .usr/share/sane/snapscan, and editing > /etc/sane.d/snapscan.con to read: > > #-- General > --- > > # Change to the fully qualified filename of your firmware file, if > # firmware upload is needed by the scanner > firmware /usr/share/sane/snapscan/u176v046.bin > > # If not automatically found you may manually specify a device name. > > # For USB scanners also specify bus=usb, e.g. > /dev/usb/scanner0 bus=usb > > I get an error message: Failed to start scanner: Error during device > I/O Please remove the line containing the USB device from your config file (/dev/usb/scanner0) - it's no longer useable for systems using libusb and the specified device does not exist on your system. After removing the line the scanner should be found automatically. Regards, Oliver
[sane-devel] Has anyone managed to get Snapscan backend working with FreeBSD 8.0 (which uses libusb)?
Hi Allan, >> Anyway, I've commited a hash function now. The new code should also >> work on FreeBSD 8.0. If anyone can try it, I'd be much obliged. > > > I did not see any commit message. did you git push? Err - yes, and it told me that it had pushed 4 or 5 objects. That was my first git commit/push, so I may well have missed something. A 'git status' told me I was in sync with the main branch (or something to that effect, I don't have access to my Linux machine at the moment). I'm not subscribed to sane-commit, so I haven't been able to verify the commit. Kind regards, Oliver
[sane-devel] Has anyone managed to get Snapscan backend working with FreeBSD 8.0 (which uses libusb)?
Hi all, On 28.01.2010 at 14:39 m. allan noah wrote: > I would do both- process ID combined with a hash of the device name, I believe that would defeat the purpose. The whole point of the mutex is to protect the USB device from simultaneous access from two processes, e.g. the reader process and the main process. If the key to create the mutex is different in both processes they end up with different mutexes and the USB device is unprotected. Anyway, I've commited a hash function now. The new code should also work on FreeBSD 8.0. If anyone can try it, I'd be much obliged. Kind regards, Oliver
[sane-devel] Has anyone managed to get Snapscan backend working with FreeBSD 8.0 (which uses libusb)?
Hi all, On 26.01.2010, at 15:46, m. allan noah wrote: > Seems like an individual backend should not need to parse the device > string. Isn't there some other way to come up with a unique semaphore, > like process id? the process id could be used, but it may fail theoretically. One example is a frontend that uses two (snapscan-)scanners at the same time (not that I think anybody actually does that). The clean solution is a semaphore per device. In the days before libusb the backend used ftok(). The current code was written by Julien, as far as I know, because the ftok() call failed miserably and the unique id was always 0. So I guess I'll stay with the device string, but maybe use some sort of crc instead of parsing it. Other ideas are, of course, welcome. Kind regards, Oliver
[sane-devel] Has anyone managed to get Snapscan backend working with FreeBSD 8.0 (which uses libusb)?
Hi all, On 25.01.2010, at 12:26, Torfinn Ingolfsen wrote: > In the meantime, another FreeBSD user found a way to fix it, it is > just a one-line patch: > http://lists.freebsd.org/pipermail/freebsd-usb/2010-January/ > 008172.html > > With Andrew's patch, my scanner now works: > root at kg-v2# sane-find-scanner -q > found USB scanner (vendor=0x03f0 [HP], product=0xc202 [Photosmart > 8200 series]) at libusb:/dev/usb:/dev/ugen1.2 > found USB scanner (vendor=0x06bd [AGFA], product=0x2061 > [ Snapscan1212u_2]) at libusb:/dev/usb:/dev/ugen2.2 > root at kg-v2# scanimage -L > device `snapscan:libusb:/dev/usb:/dev/ugen2.2' is a AGFA SNAPSCAN > 1212U_2 flatbed scanner Thanks for the pointer, I'll try to get this fixed in the backend. The code in question was added recently to fix another problem with calculating a unique identifier. Maybe one of the guys who's experienced with autoconf can give me a hint on how to do this the best way. Should I just use "#ifdef BSD" around the code in question or is there some autoconf magic that would allow me to do a more advanced query? I also have to retest this on OS X - the code in question looks very Linux specific. Kind regards, Oliver
[sane-devel] Has anyone managed to get Snapscan backend working with FreeBSD 8.0 (which uses libusb)?
Hi, > I have an old Agfa Snapscan 1212U scanner which have served me well for > years, using SANE under FreeBSD. > > To make a long story short; FreeBSD 8.0-release came with a new usb stack, > and is using libusb. > And my scanner no longer works. Has anyone managed to get the snapscan > backend working under FreeBSD 8.0? what does you snapscan.conf look like? If libusb is used, you mustn't use a device entry such as "/dev/..." or "libusb:/dev/...". All that is needed is the entry containing the vendor and product ID of your scanner, i.e "usb 0x06bd 0x2061" and the firmware entry. Hope this helps, Oliver
[sane-devel] Acer ScanPrisa640U Scanner isn't in your list and there are alot of us trying to use it!
Hi, What list exactly are you referring to? On http://www.sane-project.org you'll find it listed under Benq 640U (Acer Peripherals renamed itself to Benq several years ago, as is also mentioned in the same list). The scanner has been supported for more than seven years. So, what exactly are the problems that a you and the lot of others that you are referring to have with this scanner? Kind regards, Oliver
[sane-devel] Lost with udev and sane
John, You don't need to create any '/dev/usb/scanner' device, nor should you specify the scanner device in snapscan.conf. Your scanner will be detected automatically provided that the USB ID is listed in snapscan.conf, which should be the case for the snapscan 1212 on any standard sane installation. Concerning your log: All read and write operations to the scanner fail, so either the scanner does not respond (possible reasons: scanner hangs from previous communication attempts or is broken) or the backend does not communicate with the scanner at all. My advice is to remove the udev rules (the only udev rule that make sense is to set proper access permissions on the scanner device file), than power-cycle the scanner and try again. You can send me the resulting log if the problems persist. If you get permission problems, try as root first before creating new udev rules. Regards, Oliver On 14.03.2009, at 20:05, John Coppens wrote: > > 5) Checked that the firmware was available, and the firmware command > set > in snapscan.conf > > 6) with DEBUG level set to 255, I get: > > [sanei_debug] Setting debug level of snapscan to 255. > [snapscan] sane_snapscan_init > [snapscan] sane_snapscan_init: Snapscan backend version 1.4.53 > [snapscan] add_usb_device(/dev/usb/scanner bus=usb) > [snapscan] add_usb_device: Detected (kind of) an USB device > [snapscan] snapscani_usb_open(/dev/usb/scanner) > [snapscan] snapscani_check_device() > [snapscan] mini_inquiry > [snapscan] snapscan_cmd > [snapscan] snapscani_usb_cmd(0,0xbfe52212,6,0xbfe521ee,0xbfe52218 > (36)) > [snapscan] atomic_usb_cmd(0,0xbfe52212,6,0xbfe521ee,0xbfe52218 (36)) > [snapscan] usb_cmd(0,0xbfe52212,6,0xbfe521ee,0xbfe52218 (36)) > [snapscan] usb_cmd: cmdlen=6, datalen=0 > [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00 > [snapscan] usb_write Only 0 bytes written > [snapscan] Written 0 bytes > [snapscan] mini_inquiry: snapscan_cmd command failed: Error during > device > I/O [snapscan] snapscani_check_device: mini_inquiry failed with Error > during device I/O. [snapscan] snapscani_usb_close(0) > [snapscan] 1st read 0 write 0 > [snapscan] sane_snapscan_get_devices (0xbfe533a8, 0) > device `v4l:/dev/video0' is a Noname LifeView/Typhoon FlyVIDEO2000 > virtual device [snapscan] sane_snapscan_exit
[sane-devel] How to accurately scan A4(210mmx297mm) size paper?
Hello all, > IIRC the person who wrote XSane is indeed german (Oliver Schwartz) well, I'm german, but I didn't write XSane :-( That honour belongs to Oliver Rauch (who is also german AFAIK). Regards, Oliver
[sane-devel] Problem: X-Server crashes when using XSane
Hi, the interesting part of the log is at the end: [snapscan] sense_handler(6, 0x84ba800, 0x8265d78) [snapscan] sense_handler: sense key: 0x04, asc: 0x00, ascq: 0x00, i1: 0x00, i2: 0x4c [snapscan] sense_handler: Hardware error. (0x00, 0x4c) [snapscan] read_calibration_data: snapscan_cmd command failed: Error during devi ce I/O [snapscan] calibrate: read_calibration_data command failed: Error during device I/O [snapscan] sane_snapscan_start: calibration failed. [snapscan] release_unit [snapscan] snapscan_cmd [snapscan] sane_snapscan_cancel [snapscan] >>>>>>>> killing reader_process <<<<<<<< According to my docs the hardware error is a "scan module locked error". Maybe the transportation lock is still engaged? Do you get the error only if you use the transparency adapter or also in flatbed mode? I'm not sure why the Xserver crashes when a child process is killed, but maybe the people at X.org would find the information useful. Kind regards, Oliver Am 24.06.2008 um 18:07 schrieb Christoph M. Schr?der: > Sorry, now i got it. > > Oliver Schwartz schrieb: >> Hi, >> >> the interesting part is the contents of the file 'debug.log', >> which should be created in the directory from which you started >> xsane. >> >> Regards, >> >> Oliver >> >> On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: >> >>> Hi, >>> >>> thanks Oliver. >>> >>> This is what i'm getting showed in the terminal: >>> $ SANE_DEBUG_SNAPSCAN=255 xsane 2>debug.log >>> User defined signal 1 >>> $ >> >> >> >> > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org ! Oliver Schwartz Tel.: +41 / (0)44 / 461 06 29 (fest) ! ! D?ltschiweg 3 +41 / (0)76 / 566 29 72 (mobil) ! ! CH-8055 Z?richE-Mail: Oliver.Schwartz at gmx.de!
[sane-devel] Problem: X-Server crashes when using XSane
Hi, the interesting part is the contents of the file 'debug.log', which should be created in the directory from which you started xsane. Regards, Oliver On 24.06.2008, at 17:50, Christoph M. Schr?der wrote: > Hi, > > thanks Oliver. > > This is what i'm getting showed in the terminal: > $ SANE_DEBUG_SNAPSCAN=255 xsane 2>debug.log > User defined signal 1 > $
[sane-devel] Problem: X-Server crashes when using XSane
Hi, please also provide the log produced by SANE_DEBUG_SNAPSCAN=255 xsane 2 > debug.log then use xsane until the error occurs. The logs tend to get quite big, so you should compress it. Regards, Oliver On 21.06.2008, at 17:46, Christoph M. Schr?der wrote: > Hi, > > thanks for the information. My fault. > > You can now find them here: > http://home.mnet-online.de/hta/syslog.txt > http://home.mnet-online.de/hta/messages.txt > > Christoph > > Julien BLACHE schrieb: >> "Christoph M. Schr?der" wrote: >> >> Hi, >> >> >>> i wrote, i sometimes also get this "Failed to start scanner: error >>> during device I/O" message. And in the sane-project.org FAQ is >>> written >>> to connect the mailing list, if an error like this appears. >>> >>> I'd really be happy if i could solve this problem... >>> >>
[sane-devel] Snapscan Backend - Mac OSX Tiger don't work
Hi,
you need the firmware file for your scanner ("Snapscan 1212U_2.bin"
from your scanner driver CD). Save it under a name without spaces and
specify the filename (with full path) in the file /usr/local/etc/
sane.d/snapscan.conf
After that, check if "scanimage -L" on the command line finds the
scanner.
If the scanner still isn't found, run
SANE_DEBUG_SNAPSCAN=255 scanimage -L > debug.log
and send me the resulting debug.log file.
Regards,
Oliver
Am 10.05.2008 um 04:33 schrieb Radulph Kader:
> Dear Mrs. and Mr.,
>
> I?m trying to configure TWAIN-SANE for Mac OSX Tiger (10.4.11) from
> Matthias
> Ellert on an old G4/500 with an AGFA Snapscan 1212u_2. All the time
> the
> system forget the scanner. And Image Capture don?t find the
> scanner. And
> when I try to make scanner-sharing ON the fields are empty.
>
> So I took a look in the FAQ vom Mr. Ellert and tested in Terminal the
> command ?scanimage?. Nothing.
>
> Then I tried to use sudo scanimage ?d test:0 > test.pnm [password]
> test.pnm is produced in my home folder but scanner isn't responding.
>
> Mr. Ellert writes in his FAQ in this case it is allowed to send you a
> message, because maybe it is a bug.
>
> Could you help me? Please note: I am an absolutely novice with the
> command
> line tool.
>
> Best and many thanks in advance
>
> Radulph Kader
>
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
[sane-devel] Proposed patch for the snapscan semaphore issue
Hi, > The patch only works for libusb devices. Applying it as is means the > backend will now fail hard if you're using a non-pthread build of SANE > with a non-libusb access method. > > I'm not sure such a combination exists. If I'm not mistaken, OS/2 uses > pthread by default, so does OS X and all other OSes use libusb. If I read your patch correctly it would also break support for the old USB access by device /dev/usb/scanner0 on Linux 2.4.x (or was it 2.2.x?) without libusb. Maybe it's a good idea to fall back to the old ftok() method if the device name doesn't start with "libusb:". Apart from that the patch looks ok to me. Regards, Oliver
[sane-devel] command for stupid people?
Hi, I assume you are using the snapscan backend. In this case: > My Epson 3490 works just fine if the firm ware is loaded from a > Windows > box first. I also have located the binary that needs to be loaded. > > Is there a bash command I can run to manually load the binary file > into > the scanner? > > Would something like: > > echo esfw52.bin > some device > > Work? No. You need to edit snapscan.conf (either in /etc/sane.d or /usr/ local/etc/sane.d, depending on you setup and add the fully qualified filename of esfw52.bin to the "firmware" line, e.g. firmware=/var/lib/sane/esfw52.bin Regards, Oliver
[sane-devel] USB device locking in the snapscan backend
Hi all,
> The snapscan backend uses a mutex to lock the USB device it's
> working with when sending "atomic" commands.
First off, the original code wasn't written by me and I don't claim I
fully understand it. The background, as far as I understand it, is
this:
The backend may fork a reader process or thread who's only purpose is
to fetch image data from the scanner. It seems that this was invented
to speed up data transfer from the scanner without depending on the
frontend to read the data fast enough. As a result there could be two
processes/threads that access the scanner device at the same time.
This code, as far as I can tell, was in the backend from the very
beginning.
When USB support was added measures were taken to protect access to
the scanner on command level, i.e. only one process/thread can send a
command to the scanner and receive the result. This should allow for
mixed access from both processes/threads when implemented correctly.
It seems, however, that for SCSI no such measures were taken.
To make matters more complicated an USB command queueing was
introduced in the USB part of the backend. The purpose, according to
the comment, was this:
The "Set window" command returns with status "Device busy" when
the scanner is busy. One consequence is that some frontends exits
with an error message if it's started when the scanner is warming
up. A solution was suggested by Dmitri (dmitri at advantrix.com)
The idea is that a SCSI command which returns "device busy" is
stored in a "TODO" queue. The send command function is modified
to first send commands in the queue before the intended command.
So far this strategy has worked flawlessly.
As far as I understand it this code makes the locking necessary in the
first place, since both processes/threads may theoretically add
commands to the queue while the scanner is busy.
Currently there are three implementations for the mutex: One for BeOS,
one for pthread (used on OS/2 and OS-X), one for fork(). The one that
is causing problems is the one for fork() which is used on all Linux
platforms IIRC.
> We're not talking about pthread mutexes here, which is one of the
> available implementations, but IPC semaphores.
>
> Let's look at the code:
>
> static int snapscani_mutex_open(snapscan_mutex_t* sem_id, const
> char* dev) {
> *sem_id = semget( ftok(dev,0x12), 1, IPC_CREAT | 0660 );
> if (*sem_id != -1)
> {
> semop(*sem_id, &sem_signal, 1);
> return 1;
> }
> return 0;
> }
>
> ftok() requires its first argument to be a real, accessible
> file. Obviously, when the code was written, USB scanners were
> driven through the kernel scanner driver and this was not a
> problem.
>
> But today, dev is something like "libusb:001:003" which is all but
> a real, accessible file.
>
> ftok() returns -1 in this case, but this isn't checked for in this
> code, so it happily goes on and semget(0x, 1, ...).
>
> As it happens, most of the time, that works. Except when another
> similarly careless piece of code has already used 0x as the
> IPC key.
>
> In which case, all hell breaks loose.
>
> So, 2 bugs in this code:
> - ftok() return value is not checked (BAD BAD BAD)
> - dev is not a real file
>
> Now, two questions:
> - is that locking really useful in the backend?
Honest answer: I don't know for sure. I'd sleep better if I knew that
there was _some_ locking done when there's the remote chance of two
processes writing to the same device.
> - if yes, how do we fix this?
Good question. Maybe the easiest solution is to remove all forking /
threading / locking since it probably won't make a difference on any
machine faster than 100 MHz. At least I never noticed any difference
when testing the backend in single-thread mode. But I'm open to other
suggestions (or even implementations, given my lack of time to
support the backend...)
Regards,
Oliver
[sane-devel] Epson Perfection 1670 USB on Mac 10.3.9
Hi, you also need to specify the path to the firmware file in snapscan.conf, which is installed in /usr/local/etc/sane.d/ on OS X, IIRC. The firmware file itself (esfw30.bin) should be contained on the windows driver CD. See http://snapscan.sourceforge.net for some additional infos on the firmware files. Let me know if that doesn't solve your problem. Regards, Oliver On 18.12.2007, at 05:51, andy whelan wrote: > Andy-Whelans-Computer:~ andywhelan$ scanimage -L > [sanei_debug] Setting debug level of snapscan to 2. > [snapscan] add_usb_device: error opening device libusb: > 002:002-04b8-011f-ff-ff: Invalid argument
[sane-devel] Epson 3490 quirk?
Hi, On 07.12.2007, at 15:26, Patrick wrote: > I have an Epson 3490. It did work in Ubuntu Edgy but not too well. > If I > used it in Windoze and then Ubuntu it worked fine. However if it > was not > re-initialized under windoze every so often it would not work. > ... > but I get this message when I use xsane: > > Failed to open device 'snapscan:libusb:005:002"; > Invalid argument > > > Someone posted a configuration file fix but I can't find any > mention of > a firmware file in test.conf > > you then edit /etc/sane.d/snapscan.conf and replace : > > firmware /etc/sane.d/test.conf > > with the full path to the firmware and it should work fine and dandy ! > You need to replace /etc/sane.d/test.conf with the path and filename to your firmware file. The firmware file can be found on your windows driver CD and is named esfw52.bin. For additional information see http://snapscan.sourceforge.net . If you don't get it to work feel free to contact me. Regards, Oliver
[sane-devel] benoit's sniffer
Hi, I've written a small perl script that parses the output of usbsnoop and translates it to snapscan commands. I'll send it to you tomorrow. Regards, Oliver On 26.10.2007, at 11:20, matei kolt wrote: > > OK, the code with benoit's usb sniffer. > Pluging in, a few prewiews and a scan. > > http://matei.upcnet.ro/usbsnoop.log.tar.bz2 > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org
[sane-devel] I compressed the file
Hi all, from a first look the log is similar to other Benq Scanners, so I guess there's a good chance to make it work with the Snapscan backend. I don't have my documentation and sources here at work but if time permit's I'll take a look at it over the weekend. You may be able to do some hacking before that - mainly, add "FlatbedScanner53" to the list of known IDs in snapscan.h, find out which firmware file it uses (if any). It may be necessary to add another ID to snapscan.h if the scanner changes the ID after firmware upload. You can find some information on the snapscan backend on http:// snapscan.sf.net Regards, Oliver On 25.10.2007, at 23:38, matei kolt wrote: > Damn good idea, where the hell were I thinking at? > So, the new link: > http://www.matei.upcnet.ro/scanner.zip > Ok, I must admit it's th first time I'm working with > mailing lists.. > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org ! Oliver Schwartz Tel.: +41 / (0)44 / 461 06 29 (fest) ! ! D?ltschiweg 3 +41 / (0)76 / 566 29 72 (mobil) ! ! CH-8055 Z?richE-Mail: Oliver.Schwartz at gmx.de!
[sane-devel] epson perfection 1670 problem
Hi, On Sunday 30 September 2007 18:01, Tanguy Eric wrote: > When i launch xsane from command line i can see this > warming : > [snapscan] Scanner warming up - waiting 6 seconds. > [snapscan] Scanner warming up - waiting 36 seconds. > > and after when i ask a scan xsane spend also times warming : > [snapscan] Scanner warming up - waiting 4 seconds. > [snapscan] Scanner warming up - waiting 36 seconds. > > It's a lot of warming! Yes. Unfortunately the time is specified by the scanner, the backend just does what the scanner asks for. If the backend sends any commands before the warming up is completed the scanner will return an error. There's probably some way to shorten the warming up phase of the 1670, but I haven't a clue how to do it. > Sometimes also when i launch xsane it comes up immediately but when > i ask a scan i obtain an error message : > Failed to start scanner: Invalid argument That sounds like a different problem. Please run SANE_DEBUG_SNAPSCAN=255 xsane 2>debug.log and send me the debug.log file for such an error. Regards, Oliver
[sane-devel] Scanner Benq 7650T
checking for ICM532B ... > this is not a ICM532B (check 2, bcdUSB = 0x200) > checking for PV8630/LM9830 ... > this is not a PV8630/LM9830 (bDeviceClass = 255) > checking for M011 ... > this is not a M011 (bcdUSB = 0x200) > checking for RTS8822L-01H ... > this is not a RTS8822L-01H (bDeviceClass = 255) > checking for rts8858c ... > this is not a rts8858c (bDeviceClass = 255) > checking for SQ113 ... > this is not a SQ113 (bDeviceClass = 255) > backends > 1.0.18)> > > found USB scanner (vendor=0x04a5 [Color], product=0x2119 [ > FlatbedScanner 22]) at libusb:001:030 > > [...] > # Your USB scanner was (probably) detected. It may or may not be > supported by > # SANE. Try scanimage -L and read the backend's manpage. > > # Not checking for parallel port scanners. > > # Most Scanners connected to the parallel port or other > proprietary ports > # can't be detected by this program. > done > > # cat /proc/bus/usb/devices > [...] > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 30 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 > P: Vendor=04a5 ProdID=2119 Rev= 1.10 > S: Manufacturer=Color > S: Product= FlatbedScanner 22 > C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA > I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=4096ms > [...] > > # lspci -vv > [...] > Bus 001 Device 030: ID 04a5:2119 Acer Peripherals Inc. (now BenQ > Corp.) > Device Descriptor: > bLength18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 255 Vendor Specific Subclass > bDeviceProtocol 255 Vendor Specific Protocol > bMaxPacketSize064 > idVendor 0x04a5 Acer Peripherals Inc. (now BenQ Corp.) > idProduct 0x2119 > bcdDevice1.10 > iManufacturer 1 Color > iProduct2 FlatbedScanner 22 > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 39 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xc0 > Self Powered > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 255 Vendor Specific Class > bInterfaceSubClass255 Vendor Specific Subclass > bInterfaceProtocol255 Vendor Specific Protocol > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 EP 2 OUT > bmAttributes2 > Transfer TypeBulk > Synch Type None > Usage Type Data > wMaxPacketSize 0x0200 1x 512 bytes > bInterval 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes3 > Transfer TypeInterrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 16 > Device Qualifier (for other device speed): > bLength10 > bDescriptorType 6 > bcdUSB 2.00 > bDeviceClass 255 Vendor Specific Class > bDeviceSubClass 255 Vendor Specific Subclass > bDeviceProtocol 255 Vendor Specific Protocol > bMaxPacketSize064 > bNumConfigurations 1 > Device Status: 0x0001 > Self Powered > > Anything else I can provide to you, please ask, I will be more than > happy to help you. I even can get some coding done if there is nothing > developed yet, please send me some starting docs and I will gladly > do it! > > Thanks, > Adrian > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org > > ! Oliver Schwartz Tel.: +41 / (0)44 / 461 06 29 (fest) ! ! D?ltschiweg 3 +41 / (0)76 / 566 29 72 (mobil) ! ! CH-8055 Z?richE-Mail: Oliver.Schwartz at gmx.de!
[sane-devel] problem while found SCSI scanner "AGFA SNAPSCAN 1236 1.50" at /dev/sg0
Hi, On Monday 30 April 2007 21:34, Y P wrote: > as you will see, the scanner is found/recognized, > but xsane seems to find his Logitech QuickCam and doesn't give him > the choice to tell that's his intensions are to scan, not to webcam > > :-) > > He also did tried to add ln -s /dev/sg0 /dev/scanner > but the scanner symlink is removed at each reboot. The scanner should be detected automatically by the snapscan backend. There is no symlink needed. The only necessary entry in snapscan.conf (usually in /etc/sane.d/snapscan.conf) is the following line: scsi AGFA * Scanner" If the automatic detection does not work you *can* specify the device direcly, by adding a line in snapscan.conf with just the devicename, e.g. "/dev/sg0" (without quotes). Also make sure that the snapscan backend is enabled in /etc/sane.d/dll.conf, i.e. there's a line "snapscan" (without quotes) in dll.conf which is not commented out. You don't need any firmware for SCSI scanners. If all this doesn't help please send a debug log (run "SANE_DEBUG_SNAPSCAN=255 scanimage -L 2>debug.log). Regards, Oliver
[sane-devel] Firmware for Epson Stylus CX-1500?
Hi, On Monday 30 April 2007 16:57, L? H?ng B?i wrote: > Hi everybody, > I'm using an Epson Stylus CX-1500. I can scan image from it with > snapscan backend. However, the image is green, no red, no blue. It > seems that I need to specify a firmware to upload to the scanner. I > look in Windows installation and there are many .bin files > installed. They are C:\WINDOWS\system32\epscan6\1500\211bv040.bin, > c:\windows\system32\twain_32\cmt1500.bin, > c:\windows\system32\twain_32\cmt1500t.bin, > c:\windows\system32\twain_32\sat121.bin. Which is the firmware file > to upload? I have only one confirmed report about a working Epson Stylus CX-1500. It seems that this scanner does not need a firmware file at all. You would get an error message and no scanning would be possible at all if the scanner needed a firmware file. According to the report that I got the scanner works flawlessly. Did you try different resolutions? What versions of SANE are you using (scanimage --version)? Regards, Oliver
[sane-devel] Out of memory in sanei_scsi_cmd [was: "Annoying Out of MEmory Error..."]
Hi Abel, > > As far as I can tell I'm issuing a sanei_scsi_cmd with a send > > buffer of ten bytes and a receive buffer of 130176 bytes. Both > > should fit into the SCSI buffer of 131072 bytes easily. > > is 130176 a typo, or does the backend really wants to read 4 bytes > more than reserved? (or do I misunderstand something?) I could not > find the the number 130176 anywhere else. No, it's not a typo, it's just a bit tricky to read :-) The buffer size is 131072 bytes, not 130172 bytes, so it's bigger than the requested 130176 bytes. I fell into the same trap when I first looked at the numbers :-) The 130176 bytes are taken from the snapscan source code and some part of the log which was missing in my mail, it's the effective buffer size rounded up to the next 128 bytes boundary: > [snapscan] inquiry: effective buffer size = 130101 bytes, 37 lines > This point aside, I don't have a really good hint, except that I > have the impression that the Linux atp870u driver is not the best > piece of code in the kernel. Maintainance of the driver was, at > least some time ago, a bit unclear. Moreover, another user recently > reported problems with this driver on the list; he could use his > scanner fine after replacing the adapter with a properly supported > one. Ok, I didn't know that. I'll try on linux-scsi and recommend another SCSI controller to the user reporting the bug. Thanks a lot for your input, Oliver
[sane-devel] Out of memory in sanei_scsi_cmd [was: "Annoying Out of MEmory Error..."]
Hi SCSI experts, a user reported a problem with an Acer 620ST plugged into a Artop Electronic Corp AEC6712D SCSI controller (atp870u driver). The system causing problems is running linux-2.6.17-gentoo-r8, gcc 4.1.1 and glibc-2.4, sane-backends-1.0.18. On this system the following error occurs: ... [snapscan] open_scanner [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: SG driver version: 30533 [sanei_scsi] sanei_scsi_open_extended: using 131072 bytes as SCSI buffer [sanei_scsi] trying to enable low level command queueing [sanei_scsi] sanei_scsi_open: Host adapter queue depth: 1 [sanei_scsi] sanei_scsi_open: SG driver can change buffer size at run time [sanei_scsi] sanei_scsi_open: using new SG header structure [snapscan] sane_snapscan_open: waiting for scanner to warm up. [snapscan] wait_scanner_ready ... [snapscan] send [snapscan] snapscan_cmd [sanei_scsi] scsi_req_enter: entered 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 dev_max(currently)=32 max_active_device=1 (origin 1) def_reserved_size=32768 >>> device=sg0 scsi1 chan=0 id=2 lun=0 em=0 sg_tablesize=128 excl=1 FD(1): timeout=12ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 rb>> act: id=9 blen=1024 t_o/elap=12/8ms sgat=1 op=0x2a [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 dev_max(currently)=32 max_active_device=1 (origin 1) def_reserved_size=32768 >>> device=sg0 scsi1 chan=0 id=2 lun=0 em=0 sg_tablesize=128 excl=1 FD(1): timeout=12ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 rb>> rcv: id=9 blen=1024 dur=108ms sgat=1 op=0x2a [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [snapscan] measure_transfer_rate: have ring buffer [snapscan] scsi_read [snapscan] snapscan_cmd [sanei_scsi] scsi_req_enter: entered 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 dev_max(currently)=32 max_active_device=1 (origin 1) def_reserved_size=32768 >>> device=sg0 scsi1 chan=0 id=2 lun=0 em=0 sg_tablesize=128 excl=1 FD(1): timeout=12ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 No requests active [sanei_scsi] sanei_scsi.issue: bad write (errno=12) Cannot allocate memory -1 [sanei_scsi] sanei_scsi.issue: SG_BIG_BUF inconsistency? Check file PROBLEMS. [sanei_scsi] scsi_req_enter: queue_used: 0, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 [snapscan] scsi_read: snapscan_cmd command failed: Out of memory [snapscan] measure_transfer_rate: scsi_read command failed: Out of memory [snapscan] sane_snapscan_start: measure_transfer_rate command failed: Out of memory scanimage: sane_start: Out of memory ... As far as I can tell I'm issuing a sanei_scsi_cmd with a send buffer of ten bytes and a receive buffer of 130176 bytes. Both should fit into the SCSI buffer of 131072 bytes easily. To make matters even stranger, the same SCSI card and scanner works fine on Ubuntu 6.06 LTS, kernel: 2.6.15-23-386 gcc: GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5) glibc:2.3.6 sane-backends: 1.0.17 Does anybody of the experts have any idea what's going on? Regards, Oliver
[sane-devel] Annoying "Out of MEmory Error..."
Hi, > I own a Acer Flatbed scanner (620 ST) which I use rarely. So I can > not exactly tell you, when this error started to occur on my > computer. > > # scanimage > scanimage: sane_start: Out of memory > > Does anybody have an idea, what the heck is going wrong, or how to > get rid of that problem? Can you provide a debug log for the scan session? I.e. run SANE_DEBUG_SNAPSCAN=255 scanimage 2>debug.log and send me the log file. Another important information is the type of SCSI card you're using. /Oliver
[sane-devel] Epson perfection 660 usb - problem with lineart scanning - snapscan backend
Hi, > > When I try to scan in lineart mode, it makes garbage on output. > > The scan seems "misaligned". > > But if I first make a scan in gray or color mode, and then switch > > to lineart, it works ! > > It works ... sometimes :( > > I acquire a scan in Lineart mode and make a log : > http://www.starox.org/pub/sane/snapscan/lineart.log > It makes dirty squares in the image : > http://www.starox.org/pub/sane/snapscan/lineart.pnm So... is this the best result you can get or does it work ok (without the dirty squares) if you scan in grayscale first? Unfortunately it seems that lineart mode is less and less supported in newer scanners. These scanners always scan in grayscale mode, the conversion to lineart has to be done in the backend. I don't know if this is the case for the Perfection 660, but on the other hand there's not much that can fail on lineart mode. Maybe you can provide an USB trace of a lineart scan on windows. You need to install an USB sniffer first. I prefer USBSnoop which is available from http://benoit.papillault.free.fr/usbsnoop/ . The page also gives basic instructions on how to use it. To produce the log you should - unplug and replug the scanner - Start the scanning software - Do a preview scan - Do a very small scan with lowest resolution You can send the (compressed) log to me in private mail /Oliver
[sane-devel] Assistance please!
Hi, On Tuesday 01 August 2006 08:31, marcela castro wrote: > Who may concernI have Open source software in my PC > and I would like to configure my scanner "Benq Saw 4300U" to work > with this system Suse 10.1 http://www.novell.com/linux/ but it is > require the firmware upload. driver snapscan (package sane) that > will provide good functionality. Could you please let me know from > where can I download this firmware upload and the driver snapscan? > Thank you very much for your wonderful assistance and advice. You need to install the packages "sane", "sane-frontends" and "xsane" from you Suse CD / DVD. The "sane" package already contains the snapscan driver, there's no need for a separate download of the driver. The firmware file can be found on the CD that came with your scanner. Depending on the USB ID of your scanner you either need u176v046.bin or u222v067.bin. See http://snapscan.sourceforge.net for details. /Oliver
[sane-devel] Epson 2480 and scanner lamp
Hi, > I just upgraded to SANE-Backends-1.0.18 and my Epson 2480 works > better than ever. Thanks! > > I have a question/comment about the scanner lamp. This scanner > doesn't have an on/off button, so it remains on whenever it's > plugged in (I remember a Dilbert strip about this very theory of > design, but anyway...) > > I have noticed that, if I run xsane, then after a few minutes of > inactivity the scanner lamp is turned off (by the firmware, I > assume). However, if I don't run xsane first, the lamp stays on > indefinitely. You didn't specify which backend you're using. As far as the snapscan backend is concerned, there's no explicit command sent to turn off the lamp. I can only assume that the scanner firmware turns off the lamp by itself. When powered up the scanner only runs a very limited firmware. The real firmware is downloaded once the backend is initialized (e.g. by starting xsane). > I'm concerned about the life span of the lamp. Is there a way to > make it turn off, even if I don't run xsane? Right now my > alternatives are either run xsane everytime I turn the computer on, > or just keep the scanner unplugged most of the time. If you put "scanimage --help > /dev/null" into some hotplug or resmgr script it should also initiate a firmware download. /Oliver
[sane-devel] Fwd: BENQ 4300 Failed to open device snapscan ; linusb :004:008 error during device I/O
Hi, it seems that there's a problem with your snapscan.conf file. If you're using libusb you *must not* have a device line, i.e. you should delete any line stating /dev/usb/scanner0 or similar. The backend will automatically probe all USB devices for a suitable scanner. However, in all the logs on pastebin.ca the scanner is correctly identified. Most likely you're using the wrong firmware file. For your scanner the correct file is u176v***.bin (*** may be any 3-digit number, depending on the version of the firmware shipped with the scanner). If this doesn't help please send me a log with SANE_DEBUG_SNAPSCAN=255 of a scan that results in an error message. /Oliver On Monday 26 June 2006 13:39, Mohammed Ahmed wrote: > Dear Oliver > I have weird problem with my sane back end > > I have suse 10.0 retail edition, scanimage (sane-backends) 1.0.15; > backend version 1.0.15 > > > i did all the procedure on the HOW to and i still get that error > > Failed to open device snapscan ;linusb :004:008 error during device > I/O > > even as root > > that is conversation between me and some one on the #sane channel > > http://pastebin.ca/71929 > > that is the debug out put > SANE_DEBUG_SNAPSCAN=255 > http://pastebin.ca/71903 > > > export SANE_DEBUG_SANEI_USB=255 > http://pastebin.ca/71917 > > > we reached a conclusion says that the back end couldn't create usb > device
[sane-devel] Epson Stylus CX3700 all in one
Hi, > I have searched the archives, but found nothing definitive; read > all the docs and other stuff on sane-project.org/ and > snapscan.sourceforge.net/ websites. > > I know that the scanner part of the CX3700 works > [http://www.sane-project.org/cgi-bin/driver.pl?manu=epson&model=cx3 >700&bus=usb&v=&p=] It seems the CX-3700 is currently supported by both the epkowa backend and the epson backend. It's definitely not supported by the snapscan backend, so anything mentioned on snapscan.sourceforge.net doesn't apply. > but I am somewhat lost as to where I need to put the relevant > output of 'sane-find-scanner': > found USB scanner (vendor=0x04b8, product=0x0818) at libusb:001:002 > > and do I need to copy the firmware from the Epson cd ? > > The docs are a bit old and a little bit confusing as they are > mainly still talking about 'scanner module' rather than 'libusb'. > > I promise to write a 'howto' when I get it all working :-) I'm not an expert on the epson backend, but it should be able to recognize your scanner if you just put the IDs into epson.conf, e.g. usb 0x04b8 0x0818 After that your sanner should be recognized by scanimage -L. The epkowa backend is not part of the SANE distribution, you have to install it separately. You can get it from http://www.avasys.jp/english/linux_e/dl_scan.html . It also provides it's own documentation. /Oliver
[sane-devel] Snapscan 310 unimplemented features
Hi, >I'm using an Agfa SnapScan 310 scanner, its working just fine. > However, its status shows 'good' rather than 'complete' in the > support matrix at sane-project site. I would like to know which > features are still unimplemented (or where to find this information > if it's available) and if there is any work in progress to > implement missing functionality, otherwise I'd be very happy to > contribute. Well - this question shouldn't be asked by a user - a user should simply demand missing functionality :-) Honestly though, I guess there aren't many features left that can be added to the snapscan backend with regard to the SnapScan 310. The only thing which comes to my mind is vertical resolution: The scanner is able to support 300 DPI in horizontal direction, which is the optical resolution of the sensor. In vertical direction the resolution is determined by the stepper motor. In principle it's possible to get higher resolutions here (I'm not sure about the SnapScan 310, but I guess something up to 1200 DPI). The only difficulty in implementing higher resolutions is that the horizontal resolution will always stay at 300 DPI. The backend would need some kind of interpolation to also expand the horizontal resolution to match the vertical resolution. As far as I know such a feature could be used by several backends, so it would be best to have something reusable. The other question is if such a feature does make sense at all, i.e. whether you'll acually notice any increased resolution. I rather doubt that the resolution of the sensor in it's vertical direction really is good enough for 1200 DPI. >Not that I'm really an expert in the field of scanners drivers > development, but I've been coding in c/c++ for some years now, and > I think I'm able to make my small contribution if welcome. > >Please accept my apologies if this wasn't the right place to > ask, but I couldn't find a more suitable one, If you'd like to contribute anything I'd be happy to assist. To be honest the resolution problem isn't very high on my priority list. Maybe you have also noticed other shortcomings that could be enhanced. Regards, Oliver
[sane-devel] Epson 3490 and Slide/Negative scaning.
Hi, > Epson 3490 is inexpensive scaner and is listed on the sane page as > beeing supported (as "good"). > The question is.. does sane supporr olso slide/negative scaning, > and how good this scaner behaves under Linux... > Does anybody on the list had any experience with this scaner and > transparencie scaning? as Krzysztof already pointed out scanning of slides and negatives is supported. However, automatic film feeding (available with the 3590) does not work in SANE. /Oliver
[sane-devel] Wanted: SnoopyPro and SniiffUSB Informations
Hi, I've used usbsnoop (version 1.8, http://benoit.papillault.free.fr/usbsnoop/) successfully several times, on various flavours of Windows. There is some documentation (http://benoit.papillault.free.fr/usbsnoop/doc.php.en) available. It doesn't answer each and every question but was sufficient for me up to now. /Oliver
[sane-devel] Benq 5300U not working with sane-backends-1.0.17
Hi, > Here goes, with first sane-find-scanner and then with scanimage -L, > both > as root: The interesting information is after the firmware download, which doesn't happen with scanimage -L. You can send the (compressed) log of a regular "scanimage" command to me in a private mail. > You will notice from the above that both sane-find-scanner and > scanimage > -L detect it as FlatbedScanner 22, not the correct FlatbedScanner 24. You'll see FlatbedScanner24 only after the firmware download. The firmware changes the ID string. Flatbed Scanner 22 should be ok initially. /Oliver
[sane-devel] problem with Epson perfection 2480 photo scanner in FreeBSD
Hi, > i reinstalled sane-backends-1.0.16_2 from freebsd ports > > i get: > > [sanei_debug] Setting debug level of snapscan to 255. > [snapscan] sane_snapscan_init > [snapscan] sane_snapscan_init: Snapscan backend version 1.4.50 This is _not_ sane-backends-1.0.16. The snapscan backend version in sane-backends-1.0.16 is 1.4.42. Backend version 1.4.50 is part of sane-backends-1.0.17. Maybe you now have two versions of SANE installed? /Oliver
[sane-devel] CVS problem?
Hi, it seems there's a problem with CVS. My password is not accepted, cvs keeps asking for it. Anonymous access doesn't work either: oliver@oliverspc:/tmp> cvs -z3 -d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane co sane Fatal error, aborting. anoncvs_sane: no such system user /Oliver
[sane-devel] Benq 5300U not working with sane-backends-1.0.17
Hi, > The above appears to agree with the information on the > sane-snapscan page, which gives the USB ID for the Acer/Benq 5300 > as "0x04a5, 0x20fe" and identifies the firmware to use is > u254v042.bin. Yes, that should be correct. > Of course, the firmware file I have might be corrupt. I downloaded > it from benq.com along with a raft of other firmware files, but > there was no checksum to make sure that it downloaded correctly. The file is most probably ok. > Note that my scanner is a 5300U, and the sane-snapscan page only > mentions 5300 (without the "U". I have been assuming that this is > not significant, given that the USB IDs are the same. You're right - the 5300 entry is the one for the 5300U. The problem you're reporting has been experienced before by other people (hence my remark on that scanner on the snapscan page). I don't know yet how to solve this problem - maybe the log from the USB layer can shed some more light. To produce it, use SANE_DEBUG_SANEI_USB=255. /Oliver
[sane-devel] Epson PF 3590 film feeder
On Saturday 25 March 2006 05:00, Olaf Meeuwissen wrote: > didi.segb...@arcor.de (Dietmar Segbert) writes: > > Hello, > > > > does the auto film feeder of the epson perfection 3590 photo work > > to scan negative films? > > Not with the epkowa backend (as per limitations in the iscan > README). Maybe the snapscan backend does, but I doubt that. No, the film feeder is not supported with the snapscan backend either. /Oliver
[sane-devel] problem with Epson perfection 2480 photo scanner in FreeBSD
On Thursday 23 March 2006 15:18, breach0r wrote: > Hi, > > I tried, now sane-backends-1.0.16_2 is installed, i still get I/O > error when trying to init the scanner. I/O error the first try and > device unavailable the next tries. set SANE_DEBUG_SNAPSCAN=255 no > longer produces any output (but i tried in csh should i try with > export in bash?). I don't know much about csh. Try again in bash, or use SANE_DEBUG_SNAPSCAN=255 xsane 2>debug.log (all in one line). /Oliver
[sane-devel] Benq 5300U not working with sane-backends-1.0.17
Hi, > Once that was done, "scanimage -L" finds an "Acer FlatbedScanner22 > flatbed scanner", which corresponds to an Benq 4300 scanner. (I was > expecting FlatbedScanner24, which corresponds to my scanner.) The scanner should report FlatbedScanner24 after a successful firmware download. Before that it's usually some other value, e.g. FlatbedScanner22. > Using > either the firmware for the 5300U (u254v042.bin) or the the 4300 > (u222v067.bin), I get a device I/O error. Specifically, "scanimage > > test.pnm" returns "scanimage: open of device > snapscan:libusb:001:003 failed: Error during device I/O", and > "sane-troubleshoot" generates a lengthy log ending with: > I notice that the sane-snapscan page mentions that firmware upload > problems have been reported with my scanner, but if I am reading > the log above correctly this does not appear to be a problem here. The scanner stops responding after the firmware has been sent to the scanner. The transfer itself seems to be fine. It's possible that neither of the two firmware files is the correct one for your scanner. What's the USB ID of your scanner (e.g. output from "lsusb")? /Oliver
[sane-devel] problem with Epson perfection 2480 photo scanner in FreeBSD
Hi, > I have a major issue with my Epson perfection 2480 photo scanner. > It used to run in FreeBSD. I haven't used it in a few weeks during > which upgrades occured and I noticed this week it stopped working. > Portupgrade of sane had replaced the snapscan.conf file, I put back > there my correct firmware file with full pathname but it still > doesn't work. > > Since I track 5.4/5-STABLE, I first reverted to 5.4-RELEASE. When > the scanner worked, it used to be initialised at boot time (makes > the double noise) but even after the downgrade it wasn't. I also > downgraded Xsane to 0.98 but it didn't help either. I don't have > any older tar of sane-backends in distfiles and didn't delete those > for a long time, so I haven't tried downgrading backends. I don't > understand. Usual errors are either "No device available" or : > > Failed to open device 'snapscan:libusb:/dev/usb1:/dev/ugen0': Error > during device I/O. The debug log may provide more hints on what's going wrong. Can you try to set the environment variable SANE_DEBUG_SNAPSCAN=255, reproduce the error and post the debug log? /Oliver
[sane-devel] Problems with Epson 3490 Photo
Hi, > [snapscan] usb_read Only 64 bytes read > [snapscan] usb_read: reading: 0x06 0x00 0x02 0x02 0x49 0x00 0x00 > 0x00 0x45 0x50 ... > [snapscan] Read 64 bytes > [snapscan] inquiry: snapscan_cmd command failed: Error during > device I/O [snapscan] sane_snapscan_open: error in inquiry command: This seems to be a problem with the inquiry command. I got a similar message from another user. I have a (yet untested) fix for it which I can send to you, but it requires recompiling the sane-backend package. Another workaround is an older firmware file. If you're interested in testing either fix please contact me. /Oliver
[sane-devel] epson 3490 problem (I/O error after scanimage)
Hi, > also with mac and official cd found in the box the scanner would go > nut and block itself. i am clueless > [snapscan] sense_handler: sense key: 0x04, asc: 0x00, ascq: 0x00, > i1: 0x00, i2: 0x04 [snapscan] sense_handler: Hardware error. (0x00, > 0x04) > [snapscan] test_unit_ready: snapscan_cmd command failed: Error > during device I/O [snapscan] wait_scanner_ready: hardware error > detected. This is definitely confirms what I've been suggesting before: You didn't unlock the transportation lock. Now would be a good time to take the scanner's manual and read it. Usually there's also some leaflet like "Quick start guide" which explains how to unlock the scanner /Oliver
[sane-devel] Help with Epson Perfection 3490 Photo
Hi, > I just bought this scanner -- it seems that the problem is related > to one I've just seen on the mailing list. Yes, probably. In your case it is definitely a "scan module locked error" - which means you should check the manual and remove the transportation lock. > [snapscan] sense_handler: sense key: 0x04, asc: 0x00, ascq: 0x00, > i1: 0x00, i2: 0x04 > [snapscan] sense_handler: Hardware error. (0x00, 0x04) /Oliver
[sane-devel] epson 3490 problem (I/O error after scanimage)
Hi, > i report from the chat since i dunno if someone is listening :))) > > hi everybody > got a problem with an epson 3490 > it should work > from web research > it works for anybody > but I get an ERROR :(( > nihil:/etc/udev/rules.d# /usr/bin/scanimage > [sanei_debug] Setting debug level of snapscan to 2. > [snapscan] test_unit_ready: snapscan_cmd command failed: > Device busy [snapscan] Scanner warming up - waiting 8 > seconds. [snapscan] test_unit_ready: snapscan_cmd command > failed: Error during device I/O > [snapscan] wait_scanner_ready: hardware error detected. > [snapscan] sane_snapscan_open: wait_scanner_ready after > firmware upload command failed: Error during device I/O > scanimage: open of device snapscan:libusb:001:008 failed: > Error during device I/O > can someone tell me if it's the scanner that's dead > or me that am useless :) Hardware error usually means either - transportation lock not unlocked - wrong firmware file. If you send me the full debug log (SANE_DEBUG_SNAPSCAN=255) I may be able to give you more details. /Oliver
[sane-devel] snapscan: scanner model
Hi, > result is here: > http://rmrmg.com/jaroslav/scanner-debug/SANE_DEBUG_SNAPSCAN_255-xsa >ne.log According to the log the scanner is correctly identified. The margins of the transparency range should be set correctly. > however, I've got strange issues. Sometimes after turning on the > scanner works good But sometimes a LED on it starts to pulsate with > red light about 15 seconds after the scanner is connected to > computer. And then I'm not able to scan: > 'sane-find-scanner' finds the device properly, but scanimage/xsane > say that no device found. Please provide a log for this case if you can reproduce it. /Oliver
[sane-devel] snapscan: scanner model
Hi, > I've got Epson Perfection 2580 Photo which is recognized by > snapscan as 2480, because they both got the same id: 0x04b8/0x0121. > > I'm wondering if there is a way to know real model in such a > situation. It can be helpful, because 2580 differs from 2480 (has a > motor which transports 36mm film). Which version of sane backends are you using? The latest version, sane-backends-1.0.17, should automatically distinguish between 2480 and 2580 and adjust the preview range accordingly. The code, however, is not very well tested and relies on a few data logs from 2480 / 2580 users that I've received. If it doesn't work for your scanner please send me the output of SANE_DEBUG_SNAPSCAN=255 xsane 2>debug.log (No need to do any scans, just close xsane after it has started). /Oliver
[sane-devel] Try it out: SANE, JNI and Java all in an applet
Hi, > On another subject, can we get the JNI code rolled > into the SANE project distribution? The current japi > code in sane-backend has not been maintained for about > 9 years now. Our company will sponsor the code and > code maintenance. Can we do this please? Java is > part of the future of the Linux desktop, with some > major and very active projects (Jakarta, gcj, Apache > Harmony, and Kaffe) all very active. Scanner access > is a small but important part of it. Whoever has > control over what goes in the dist, please contact me > so we can do this. If the code is under GPL + SANE exception / pure GPL / LGPL or some similar license I don't see why it shouldn't be possible. Ideally the code should be reviewed first. Maybe you can put the sources online on your webserver? If nobody objects I can put the sources into CVS after the review. It may also be possible to get you a CVS account on alioth. I'm not sure about the state of the existing japi code. Is it currently in use for any application? /Oliver
[sane-devel] Try it out: SANE, JNI and Java all in an applet
Hi, > I have made an updated version that should fix the > bugs you reported on the depth issue, and on the > no-scanners issue. yes, it works now - nice. One thing I noticed is that the scan button becomes inactive after the scan, so you can only run the applet once. The clear button seems to have no effect at all. > Also, as soon as I get a x64 (soon!) I'll compile the > binary for that. I'm not sure it will work at all - as far as I can tell there's no 64 bit java plugin available for firefox. It may work in konqueror though. /Oliver
[sane-devel] Epson Perfection 1270 recognized, but not scanning
Hi, > I didn't include more verbose output from the commands here, to > avoid making this mail very big, but I'll gladly include output > with > SANE_DEBUG_SNAPSCAN=2 > level, as well as the output of any command, if needed. Please send me the log in private mail, preferably with SANE_DEBUG_SNAPSCAN=50 /Oliver
[sane-devel] USB sanner only as root
Hi, > Thank you for the orientaion. > On both computers I simply changed the id in the corresponding line > of /etc/sane.d/hotplug/libsane.db from 0664 to 0660 and it worked > fine. In case of BenQ 5000 it was also necessary to change the > product code from 0x20fc to 0x20f8, acording to the information > obtained trough sane-find-scanner, and to insert the firmware > 20F8V115 (and not 20F8V116 as idicated in snapscan.sourceforge.net) > in /etc/sane.d/sanapscan.conf. Thanks > Gustavo Bayer 20F8V116 is the newest version of the firmware (the last 3 digits of the filename are the version of the file). V116 is contained in the driver from Benq's website, V115 is probably a slightly older version from your driver CD. I guess it works just as well. /Oliver
[sane-devel] Benq 5150C / 5250C users: please test
Hi, > Ok, I did some testing with my BenQ 5150C. > > My first try was in 300dpi color mode (because this was default). > There are no color stripes anymore. However, the scanned area was > not very wide. Although the full available range > ((0,0)x(216.0,297.0)mm^2) was selected in xscanimage. The resulting > image had only 109 mm in width and approx. 145 mm in height > (measured with millimetre graph paper) > > This is independent of selected resolution and colour mode. Looks like the measurements are off by a factor of 2. That should be easy to fix. > 'Gray' doesn't work. It still results in very distorted Images. > When doing 'gray' with xsane there is a message box saying "Backend > sends more image data than it defined in parameters", after > scanning in preview mode. Hm, ok. The backend currently always sends some static calibration data for color mode. I'll try to get some gray scale mode calibration data as well. > 'Halftone' sends wrong colours, and sometimes the same patterns as > gray. In xscanimage, preview crashes in this mode. This may be related. However, a lot of modern scanners don't support halftoning at all. Does the windows driver offer something similar? > > At present the calibration algorithm for the 5150 / 5250 is > > unknown. The calibration data sent to the scanner is currently > > some static data which may or may not work for all scanners. > > I'm not a hardware developer. But if you need any data, be free to > ask. But as my attempt to sniff on the USB-bus in Windows fired up > the whole system and I could not scan anymore until the next > reinstall of W2K, I won't do that anymore. I have some data samples, but the hard part is to make an educated guess on the used algorithm. /Oliver
[sane-devel] Intended change of config file handling
Hi, > I do not understand how automated firmware upload should work > if there is more than one scanner connected which use the same > backend but which need different firmware files. For the snapscan backend that's currently not possible, as there is only a single firmware file entry in snapscan.conf. Eventually I'd like to change this to a single directory entry and a filename entry for each USB scanner (e.g. after the corresponding USB ID entry in snapscan.conf). > But my question is: > Can the backend automatically determine the right firmware file > for a particular model? Not really, at least for the snapscan backend. Benq uses the version number of the firmware as part of the filename, so either the files would have to be renamed or the backend would have to do some wildcard matching. I prefer to list the most common name in snapscan.conf where it can be changed if needed. > If yes, it would be great because then it would be possible to > ask the manufacturers to allow re-distribution of their firmware > files "as is" so that all firmware files for all models of a > backend could be stored in the same firmware directory > and the backend would pick the right one for a particular model. I'd like that as well. It would also be nice to link to the firmware files from the snapscan page or the SANE page of supported scanners - unfortunately I've never received a single answer from Acer/Benq to any of my emails. Regards, Oliver
[sane-devel] sane SCSI 32bit emulation on 64bit
Hi, > He doesn't want to recompile > for 64bit because the amount of money he makes from the Linux > version doesn't justify it. Err... excuse me? I don't think the amount of money any of the SANE developers makes from SANE development justifies any effort on this behalf. > I can understand your attitude, and I can understand the vuescan > author's attitude. Between the two, the net result is no functional > scanning application is available for SCSI scanners on a 64bit > Linux workstation. There goes "Linux is suitable for the desktop". No, there goes "Vuescan is suitable for the desktop". Some difference. If you want to ask someone for a favour you better choose your words carefully. /Oliver
[sane-devel] Benq 5150C / 5250C users: please test
Hi all, I've added some basic support for the Benq 5150C / 5250C scanner to the snapscan backend. Anyone owning such a scanner is encouraged to test it and inform me of any problems. You can get a snapshot of the latest SANE sources from http://www.sane-project.org/snapshots At present the calibration algorithm for the 5150 / 5250 is unknown. The calibration data sent to the scanner is currently some static data which may or may not work for all scanners. I hope to get this fixed at some point. Anyone who'd like to look into it is welcome to contact me. Regards, Oliver
[sane-devel] Epson All-in-One stylus CX-1500
Hi, > I'm writting this to know if anyone are/have > write/written a backend for this scanner. (Guttenprint > have support for printing). > > If not, i have one of these i "will ***TRY***" (I'm no > a programmer any longer since some years ago, but i > can remember C more or less clearly) to write a > backend or implement this scanner in one of the > existing ones (AFAIK the snapscan backend is the more > closer to the data i've reverse engineered for it so > far) but i need to know if somebody has started to > write one to prevent dupplicate effort. As far as the Snapscan backend is concerned there are currently no efforts to support this scanner. If you have any USB logs you can send them to me in private mail. It should be easy to find out if this scanner can be made to work with the snapscan backend. /Oliver
[sane-devel] Epson Perfection 3490 PHOTO
Hi, > 1. Someone should change the sane compatibility list to show that > it does NOT work as of sane-backends-1.0.16. It should be noted > you need CVS or .17 once it's released. Where did you get the information that it does work with sane-backends-1.0.16? The device list for 1.0.16 doesn't list the 3490, as far as I can see. It only shows up in the CVS list. The Snapscan homepage on http://snapscan.sf.net also mentions that you need at least 1.0.16-CVS. Most of your other points are FC3 related, as far as I can tell. It may be a good idea to post these issues on a FC3 mailing list. /Oliver
[sane-devel] Agfa Scanner
Hi, On Monday 12 December 2005 13:22, dmeret...@repsolypf.com wrote: > Sorry for disturbing, but I would like to know if there are someone > with experience in Agfa SnapScan 1212p (parallel). Or some place to > go. The parallel protocol for Agfa scanners is unknown. It's probably some sort of SCSI emulation, i.e. the higher levels of the protocol are probably identical to the 1212u. However, nothing is known about the low level part of the protocol, so this scanner is not supported at all. To make matters worse, unless someone attaches a logic analyser to his scanner and writes a scsi emulation driver this situation is unlikely to change. /Oliver
[sane-devel] BenQ Scanner 5250C support
Hi, > I've 5250C benq scanner that I would like to get working under > linux. I've tried the sane CVS snapshot from December 4th 2005 > without any luck. After some time spent by googling I've found > following information: > > http://lists.alioth.debian.org/pipermail/sane-devel/2004-December/0 >12769.html > > After adjustments according the the mail above I've managed to get > at least some output - the same (I guess) as Benjamin got: scanned > image with color strips when scanning b&w original. Both the 5150 and the 5250 (which seem to have the same hardware) currently suffer from this problem. I got a usb trace of a windows scan from Andrew Walrond last week and started to do some analysis. The colour problem is currently unsolved, however. There are two commands which work differently from other scanners. One of the command is the calibration command. Currently it's my main suspect for the colour problem. However, since there is no documentation at all, I can't promise that the 5150/5250 will be supported any time soon. > I have tried the "acerfirm -q" as described here: > > http://lists.alioth.debian.org/pipermail/sane-devel/2004-April/0107 >16.html > > but with following results: > > $ ./acerfirm -q > Can't open scanner device at ./acerfirm line 142. acerfirm does not work with libusb. It's obsolete anyway since the firmware is downloaded by the backend directly. /Oliver
[sane-devel] Re: Epson Perfection 3490 PHOTO
Hi, > Is there anything I can do to help get the Transparency unit to > work? As far as I know the transparency unit of the 3490 works ok. The only thing not supported is the automatic film feeder of the 3590. Please make sure you use the latest version of the snapscan backend from CVS. If your problems persist please send me a debug log resulting from SANE_DEBUG_SNAPSCAN=255 xsane 2>debug.log Regards, Oliver
[sane-devel] BenQ Scanner 5150C
Hi, > A little googling turned up this thread from last December: > http://lists.alioth.debian.org/pipermail/sane-devel/2004-December/0 >12758.html > ... > The image is recognisable, but has vertical colour bars all the way > across it. (*For reference, a test scan is attached, so you can see > what I mean) > > I would dearly love to get this working; Can anyone suggest a way > forward? I'll gladly help/test etc etc. The result you described is more or less how far we've come with this scanner when it was first mentioned last year. In the meantime I haven't done any work on it. What I need is a USB trace from a windows scan session to see if any command uses different parameters than other other scanners. You can get an USB tracer from http://benoit.papillault.free.fr/usbsnoop/, the page also gives some instructions on how to use it. The scan session should contain an preview scan and a "real" scan of a small area at lowest resolution. The traces tend to become very large, so please gzip with highest compression rate before sending. Regards, Oliver
[sane-devel] Lineart emulation
Hi, > > Same applies to interpoliation. I have a huge patch in my inbox > > that adds scaling to my avision backend just because some > > el-cheapo OEM scanners do not appear to deliver any resolution - > > and for the highest resolution of 2400 dpi have a memory shortage > > and thus the author implemented amorphic scans @1200x2400 with > > software scaling to 2400x2400 to compensate this. > > > > In the long run some plugin subsystem (think ALSA) to plug > > scalers together would be a big win. Trivially one could > > implement this by adding a backend (simillar to the dll one) with > > that functionality shadowing any other backend. > > Well, also the plustek backends do have such scaling/interpoliation > stuff, maybe I'll find some time to make a proposal for such a lib yes please. Interpolation should be added to the snapscan backend as well at some point (for the same reason as in the avision backend, to scale from amorphic scan). /Oliver
[sane-devel] Lineart emulation
On Wednesday 30 November 2005 21:12, St?phane VOLTZ wrote: > since Pierre has added lineart emulation. I'll need to add something similar to the snapscan backend in the long run, since some new scanners don't support lineart mode. It still would be nice to have lineart for OCR etc. on those scanners. Would it be a good idea to have a common library for the conversation from grayscale to lineart? Is it used in any other backend? /Oliver
[sane-devel] Epson PF 3490: still lineart combing at 3200 dpi
Hi, > The new CVS code did not completely solve the remaining interlacing > problems at 3200 dpi. While now grayscale work well at both 8bit > and 16bit, lineart is still combing, but rather differently than > before. Now interlacing is periodically present or absent by blocks > of 8 vertical scancolumns, as can be seen in the attached picture. ah yes, lineart requires some more bitfiddling. I did some in CVS, hope I got it right this time. /Oliver
[sane-devel] Try #2 Epson Perfection 3490 on Ubuntu
Hi, > When I power up the scanner, I get pretty much the same behavior I > was getting before, although maybe slightly improved. The scanner > seems to be resetting every second or so... in dmesg I get a series > of messages like this: > > [4352427.799000] usb 5-7: new high speed USB device using ehci_hcd > and address 63 > [4352428.131000] usb 5-7: USB disconnect, address 63 > [4352428.30] usb 5-7: new high speed USB device using ehci_hcd > and address 64 > [4352428.631000] usb 5-7: USB disconnect, address 64 > > which never stop. This sounds like a problem with the hotplug management in Ubuntu. It could also indicate a problem with the power supply via the USB bus (AFAIK the 3490 has no power supply of it's own). In any case it seems it's not related to sane. You could try unloading ehci_hcd and see if that changes anything. This will force the bus to USB 1.1 mode. Another possibility to try is to connect the scanner via an USB hub with a dedicated power supply. Regards, Oliver
[sane-devel] Re: Re: Re: epson 3490 - transparency unit problem
Hi, > > Lineart and grayscale should be fixable. I've commited a fix to CVS, please test. > What does the snapscan backend for halftoning? Are there halftoning > algorithms implemented in software or does it only pass a flag to > the scanner? I'm asking this because there is a kind of halftoning, > though broken. If it's done by the scanner, it could indicate then > it is capable of some kind of halftoning. The backend only calculates some matrices and downloads them to the scanner. The actual halftoning is done by the scanner itself. > > > PS: will be 2400 dpi enabled in the future? And why does the > > > windows driver allow 2400 dpi but not 1600? > > > > You'd have to ask the epson guys. My guess is that the scanner > > scans at 3200 DPI if 2400 DPI is requested and the decimating to > > 2400 DPI is done in software. > > Yes, it was also my guess. There is also decimation at 1600 dpi, > isn't it (and at all resolutions below 3200)? The decimation > patterns are evident for most if not all small resolution modes (I > checked it last time), only this decimation is maybe done in > hardware instead of software. But of course it is easier to throw > away every other column/line instead of one of four. Below 3200 DPI only one sensor line is used. 3200 DPI uses two sensor lines with a small offset (that's why the deinterlacer is needed for this resolution). For all other resolutions the decimation is done by the scanner itself. > One further question: do you know what the real hardware resolution > of the Perfection 3490 is? In the technical data sheet Epson states > it is 3200x6400 dpi. These 6400 dpi are maybe attained with the > stepper motor (as was the case with my former 600x1200 dpi > scanner). Yes, thats correct. However, the vertical resolution is fixed at 3200 DPI. For a usable image the backend would have to do some kind of interpolation to deliver 6400x6400 DPI. /Oliver -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051125/8624a326/attachment.pgp From s...@geekpages.co.uk Fri Nov 25 19:10:03 2005 From: s...@geekpages.co.uk (Chris) Date: Fri Nov 25 19:10:11 2005 Subject: [sane-devel] Canoscan LiDE 25 detected by find-scanner, not scanimage In-Reply-To: <20051125174609.gj7...@meier-geinitz.de> References: <20051125174609.gj7...@meier-geinitz.de> Message-ID: Hi Guys, Thanks for the suggestions. I haven't got it working yet, but I think the reason for the failure may be getting closer. First I removed everything except plustek from the dll.conf file. As expected the TV card was no longer picked up by scanimage but unfortunately, neither was the CanoScan. So I did the following as per Henning's suggestion: export SANE_DEBUG_PLUSTEK=12 export SANE_DEBUG_DLL=12 export SANE_DEBUG_SANEI_USB=255 scanimage -L The output was as follows: [sanei_debug] Setting debug level of dll to 12. [dll] sane_init: SANE dll backend version 1.0.11 from sane-backends1.0.16-cvs [dll] sane_init: reading dll.conf [dll] add_backend: adding backend `plustek' [dll] sane_get_devices [dll] load: searching backend `plustek' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-plustek.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-plustek.so.1' [dll] init: initializing backend `plustek' [sanei_debug] Setting debug level of plustek to 12. [sanei_debug] Setting debug level of sanei_usb to 255. [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory [sanei_usb] sanei_usb_init: found 0 devices [plustek] Plustek backend V0.50-7, part of sane-backends 1.0.16-cvs [plustek] Retrieving all supported and conntected devices [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0010 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0011 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0015 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0013 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0013 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0011 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0010 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0014 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0015 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0014 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0016 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0007 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x000f [sanei_usb] sanei_usb_find_devices: vendor=0x07b3
[sane-devel] Epson 3490 / 3590
Hi, > Can i hope, that the auto film feeder of the epson 3590 will work? At the moment the film feed for the 3590 is not supported. I'll need to get USB traces from a windows scan with film feeder before there's any chance of supporting it. Anybody who'd like to provide a trace is welcome to contact me. Since feature freeze for the next release of sane-backends is active already there won't be any support for the film feeder in sane-backends 1.0.17. Regards, Oliver
[sane-devel] Re: Re: Re: epson 3490 - transparency unit problem
Hi, > I confirm the 3200 dpi works well for me, and there isn't any > interlacing problems. I apologise for my previous message which was > not enough clear. > > In fact, it seem's that if I do a 2400 dpi scan which does not > work, then the following 3200 dpi scan are bad. But it works again > if I restart xscanimage. ah, ok. That makes more sense. I guess I'll disable 2400 dpi to make sure the error doesn't occur. > But for me the 16 bit depth doesn't work. If I try to open the file > with gimp, the following message is displayed : > > PNM : invalid intensity maximum value That's a gimp problem. AFAIK gimp still can't handle more than 8 bits/color. /Oliver
[sane-devel] Re: Re: Re: epson 3490 - transparency unit problem
Hi, > - at 2400 dpi : > I have done several try, at least a dozen. > Sometimes it's all dark, sometimes all white, sometimes a > succession of colored bands, and sometimes I have a good scanning, > but at least it doesn't scale the entire selection I have made on > the preview screen. And I have always the shaking between line. > (and I am sure I have the latest snapshot of the snapscan backend > and of xscanimage frontend) > > - at 3600 dpi : > it's in part all the same, except that when it's work, the scan > cover the entire selection I have done. The shaking seems always > visible, but I am not sure because of the quality of my film. 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. I'm a bit surprised about the effect at 3600 dpi. Can you send me an image which shows the effect? /Oliver
[sane-devel] Re: Re: Re: epson 3490 - transparency unit problem
Hi, > I don't think the sensors is defective, because it works very well > on Windows2000 with the Epson software. And I have try the quality > calibration with no result. Hm - I don't think so. Quality calibration (i.e. the option named "Quality calibration", not "Quality scan") was disabled for the 3490 until now. > Could you explain the calibration process with much details. Is it > possible that the calibration process be different whith snapscan > backend than with the epson software ? > I mean : the position of the calibration is done under the controle > of the firmware, or under the controle of the backend ? There was no quality calibration at all done for the 3490 up to now. That is to say, no quality calibration where the backend was involved. I don't know if the firmware does some "simple" quality calibration that may explain the green line. I've now adapted the quality calibration code for the 2480 and enabled it for the 3490. It's a pitty that you solved the problem already ;-) otherwise it would be nice to know if quality calibration solves it, too The code is in CVS now, it should show up in the snapshots tomorrow - please test. /Oliver
[sane-devel] Re: epson 3490 - transparency unit problem
Hi, > I'm using the tpu on the 3490 with backend-11-10. It works ok > though the scans seem quite dark compared to the original slide. > However adjusting the gamma settings on the scanned file gives a > nice 1024x768 display size. I'm very much a newbie at this so sorry > I can't give more detailed info. Can you send me the version of your firmware file? Run strings esfw52.bin | grep -i epson to extract it from the file /Oliver
[sane-devel] epson 3490 - transparency unit problem
Hi, > I've just bought an epson 3490, and download the > sane-backends-2005-11-10.tar.gz and > sane-frontends-2005-11-10.tar.gz. > > While the flatbed seems to work as expected, the transparency unit > doesn't. > > I want to scan a negative film, but the resulting file is crossed > by a thick green line. > I've tried to scan at different scan resolution and bit depth, but > the resulting scan is always bad. The higher the resolution is the > thicker the green line is. I haven't looked at the transparency specific stuff for the 3490 yet. As it doesn't work out of the box I'll need an USB trace from the windows driver first. Do you think you can provide one? You need to install an USB sniffer first. I prefer USBSnoop which is available from http://benoit.papillault.free.fr/usbsnoop/ . The page also gives basic instructions on how to use it. Once it works you should start logging and do a preview scan and a scan of a very small area in low resolution, both times using the transparency adapter. The log files tend to get quite large, but it should shrink to a manageable size after zipping. Please send it to me directly, not to the list. Regards, Oliver
[sane-devel] Snapscan + Epson PF 3490
Hi, > I own an Epson Perfection 3490 and I am beginning to use it with > the CVS version of SANE (snapscan backend). While it seems to work > well at resolutions up to 1200 dpi (but I did not yet perform > really thorough testing), I noticed a kind of interlacing behaviour > when scanning negatives/diapositives with the TPU at 3200 dpi. The > scanlines are periodically offset from each other. Maybe it is > alsoi present for the flatbed part, but I don't have such high > resolution reflective stuff to test it out. > > I would like to help the snapscand backend maintainer to fix the > problem, as I would like to scan slides and negatives besides the > usual flatbed content. What is needed in order to help as much as > possible? I am thinking about scanning e.g. a small area with > different resolutions and bit depths, then visually compare the > results. But what should I do with these test images and the > backend logs? I don't want to post binary data directly to the list > for bandwidth reasons. Should I use the bug page at alioth? The effect is known from other scanners such as the Epson perfection 2480. For this model the correction is already done in the Snapscan backend. If you can provide me with a high resolution scan that shows the effect (i.e. an image that allows to count the pixel offset between two adjacent lines) the changes for the 3490 should be easy to implement. /Oliver
[sane-devel] Experiences with AGFA Snapscan 1212U?
Hi, > I have a chance to pick up a used AGFA Snapscan 1212U from a friend > (he moved to XP and it's not supported, and gives dire warnings > against trying). > > I see that the support on both the current stable version and the > dev version is marked as "good". Is there any important features > known to be missing that stop it from being marked "complete"? Or > is it just because "complete" is hard to achieve/prove (I saw the > recent thread on the definitions of "good" and "complete")? > > Any particular positive or negatives experiences? There have been no reports from users for the 1212U in recent month, so I assume it works ok ;-) The maximum resolution for this scanner supported by the snapscan backend is 600 DPI, which is the optical resolution. As far as I know the stepper driver of the scanner supports 1200 DPI, so theoretically it's possible to have a resolution of 600x1200 DPI, but currently that's not implemented. There also is one open bug report for the 1212U: http://alioth.debian.org/tracker/index.php?func=detail&aid=300657&group_id=30186&atid=410366 However, I never got any details so this bug is not likely to be fixed (if it really is a bug). Once these two issues are solved I may be tempted to even change the status to "complete" ;-) /Oliver
[sane-devel] Re: request for extra xsane functionality
Hi, > When you scan a DIN-A4 page with 200x200 dpi and save it e.g. as a > tiff file then you get an image with about 1700 x 2200 pixels. At > this point there is no relation to a size in millimeter, > centimeter, inch or DIN-A3 or something like that. I don't think this is completely true. Tiff allows you to add a "Resolution" tag that specifies the pixels/inch. So even after saving as a tiff file it's possible to deduce it's original size. The tag, btw, is set correctly by xsane (run tiffinfo on a tiff file saved from SANE). > But there will be nothing like "Scale to DIN-A4", this is not > possible when you do not know the size of a pixel! If you manage to get the resolution (in DPI) of the display then you could even display the image in it's original size. Don't ask me how, but I think it's possible for X11R6. /Oliver
[sane-devel] Epson 2480/2580: Testers needed
Hi, >> > Argh, my 2480 is changing to 5.5cm by 7.5cm (judging from the >> > preview window). Debug log attached. Your boundaries are fine. From the output of your scanimage command: > ? Geometry: > ? ? -l auto|0..55mm [0] > ? ? ? ? Top-left x position of scan area. > ? ? -t auto|0..125mm [0] > ? ? ? ? Top-left y position of scan area. > ? ? -x auto|0..55mm [55] > ? ? ? ? Width of scan-area. > ? ? -y auto|0..125mm [125] > ? ? ? ? Height of scan-area. > I posted a screenshot: > http://thewizardstower.org/sshot.jpg It's just the xsane logo that doesn't fill the complete scan area. There should be no problems with scanning in transparency mode. /Oliver
[sane-devel] Epson 2480/2580: Testers needed
Hi, > Argh, my 2480 is changing to 5.5cm by 7.5cm (judging from the > preview window). Debug log attached. That's very strange. It can either be 5.5 cm x 8 cm or 5.5 cm x 12.0 cm. Everything else is, well, extremely unlikely. Please send me the file scanimage.txt, resulting from executing scanimage --source="Transparency Adapter" --help 1>scanimage.txt > BTW, is this correct: > > $ sane-config --version > 1.0.16 > > I installed today's cvs over 1.0.16; I did 'make uninstall' first. Yes, your installation is fine. You're definitely using the new version. /Oliver
[sane-devel] Epson 2480/2580: Testers needed
Hi, In the last weeks there have been some improvements to the SnapScan backend for 2480/2580. Most of them were contributed by Simon Munton, who deserves all the credit :-) In particular there is now support for 16 bit/color scans for the 2480/2580. The backend also distinguishes now between the 2480 and the 2580 and sets the boundaries for transparency scanning accordingly. This part needs some broad testing since the distinction is not documented anywhere. I also hope to have fixed the preview issue for the 2580. To test, please compile and install the latest SANE backends from CVS (but make sure that you don't install two version of SANE at the same time, see the README file that comes with the SANE sources). After starting xsane and selecting the transparency unit as source the boundaries of the preview window should change automatically to 5.5 cm x 12.5 cm for the 2480 and to 5.5 cm x 8.0 cm for the 2580. IMPORTANT: If the boundaries are not changed correctly don't attempt to scan, not even for previewing. Instead, please send me an email with the debug log from "SANE_DEBUG_SNAPSCAN=50 scanimage --help 2>debug.log" If the preview area changes correctly everything should work fine :-) The sources are available from the daily CVS snapshot at http://www.sane-project.org/snapshots/ Regards, Oliver
[sane-devel] offtopic 35-mm scanner question
Hi, > I have an Epson 2480 and I'm quite satisfied with it. I haven't > used it for negatives, only slides; for many purposes the results > are quite good. Some random thoughts: > > * Sane support is very good, but native support (in windows) is > still better. In particular: > The windows driver detects and crops the slide area; under > sane, you have to manually crop the slide mount. > The windows driver supports 16 bit per channel, and this really > makes a difference > for high-quality scans. 16 bit support for the 2480 has just been added in CVS, thanks to the effort of Simon Munton. It's going to be included in the next release of sane-backends. For the impatient there's also the CVS snapshot :-) /Oliver
[sane-devel] Epson Perfection 3590
Hi, > I just downloaded the CVS-version of the snapscan backend and > tested it. It works (for the flatbed part of the scanner)! > > The only thing that needs correction is the list of resolutions, > which at present is > > Options specific to device `snapscan:libusb:004:002': > Scan Mode: > --resolution > auto||150|200|240|266|300|350|360|400|600|720|800|1200|2400|3200|0| >10|50| > 75|100|150|200|300|400|600|1200|2400|0|0|0|0|0|10|50|75|100|150|200 >|300| 400|600|800|1600|0|0|0|0|0|10|50|75dpi [300] > Sets the resolution of the scanned image. > > This is probably not what was intended. :-) Are you sure you did a clean install? There's not much code involved in setting the resolution list (and it seems to work fine here). /Oliver
[sane-devel] Epson 3590
Hi, > I tried more resolutions. The results are funny: > - 200 dpi is OK > - 150 dpi works, too > - 100 dpi works, but the scanned area was displaced in y direction > - 75 dpi works, but scans a larger y distance than expected > - 50 dpi is OK, > - values under 50 are rounded to 50 I've added 150 and 50 DPI to the resolution list in CVS. I've also added some code to set the preview bit correctly for the 3490. The code is in CVS. Please test :-) /Oliver
[sane-devel] snapscan options
Hi, > i use a epson perfection 3590 photo with sane-cvs 2005-10-09 > version.if i use the options > > -x auto and -y auto > > scanimage gives back a error. Can i not use the options -x auto and > -y auto to detect the scanmaterial automaticaly? "auto" in this case just means that you do not have to specify the option at the command line. If you don't specify the option the whole scanning area is scanned. There is no possibility in scanimage to detect the scanmaterial automatically. /Oliver
[sane-devel] Epson 3590
Hi, On Monday 03 October 2005 18:43, Bauke Jan Douma wrote: > On Fri, Sep 30, 2005 at 03:15:41AM +0200, Ulrich Deiters wrote: > > I set the no-preview bit (source |= 0x40;) in snapscan-scsi.c > > after line 922, and the problem vanished, i.e., the scanner > > does a quick, undistorted scan of the whole scan area without > > hanging itself. > > That's odd, I have a 3490, and --although I don't often use it-- > I was under the impression that the few times I did use it, preview > worked fine. I never experienced any 'hangs', and got a quick > scan that looked and smelled like a preview. It's possible that the behaviour depends on the version of the firmware. Maybe you can both check the version that you have in use. The easiest way to identify the firmware version is to run strings esfw52.bin | tail You'll get some garbage strings, but the version string should be easy to recognize. /Oliver
[sane-devel] Weird snapscan firmware behaviour (bug?)
Hi, the behaviour you describe is perfectly normal, as far as the ID of the scanner is concerned. Initially the scanner identifies itself as FlatbedScanner_13. After downloading the firmware (which seems to work only in windows in your case) the scanner identifies itself as FlatbedScanner_21. However, the scanner should work in Linux without having to download the firmware in Windows first. > 3) I then configured /etc/sane.d/snapscan.conf as follows: > --- > firmware /etc/u176v046.bin > /dev/usb/scanner0 bus=usb > --- You only need the first line. You should remove the second line, since the scanner is probably accessed via libusb anyway. > 1) The scanner is detected as an 'Acer FlatbedScanner_13'. This is > a problem, because it does not work unless it is detected as an > 'Acer FlatbedScanner_21'. After this point I can try whatever I > want, the scanner is never detected as an 'Acer FlatbedScanner_21' > again, only as an 'Acer FlatbedScanner_13'. In short, when the > scanner is detected as an 'Acer FlatbedScanner_13', it never works. > If it is detected as an 'Acer FlatbedScanner_21', it always works. As I pointed out above that's ok, as long as the firmware is not downloaded. Once you start a frontend like xsane or kooka the firmware should be downloaded automatically. Does "scanimage -L" detect the scanner before firmware download? If no, please provide a debug log (SANE_DEBUG_SNAPSCAN=50 scanimage -L 2>debug.log). If xsane or kooka doesn't detect the scanner there's most likely a problem with your firmware file. Note that there are two versions of the 3300 which use different firmware files. Depending on the USB ID you have to use either u176v... or u222v... as firmware file. See the scanner list on http://snapscan.sf.net. If all else fails send me the debug log of the xsane/kooka session (SANE_DEBUG_SNAPSCAN=50 kooka 2>debug.log) /Oliver
[sane-devel] Epson 3590
Hi,
> The scanner is slow in preview mode and makes a different noise
> (probably because it is doing very small y steps). Right now
> the preview mode is not the same as the normal 200 dpi mode.
> But this is not surprising: Somewhere around line 870 in
> snapscan-scsi.c you inform the scanner that it is in preview mode:
>
> source = 0x0;
> if (pss->preview) {
> source |= 0x80; /* no high quality in preview */
> }
> else {
> source |= 0x40; /* no preview */
> }
>
> I suspect that the scanner takes that as an excuse to get lazy
> (with respect to the y motion). :-)
Can you find out if this behaviour is due to the high quality bit or
the preview bit? You can set the high quality bit separately from the
gui by selecting the "Quality scan" option within the standard option
screen.
> I will download the latest CVS version during the weekend and
> see if the problem still persists.
No need really, the code in question hasn't been changed for about 3
years...
/Oliver
[sane-devel] Epson 3590
Hi, > I installed the latest SANE backend version, applied Jan Bouke's > correction, and got the scanner working (after some confusion > about the firmware file) - at least for paper scanning. > > The only problem I have is with the preview mode: > "scanimage --preview=yes" uses a too high y rsolution, i.e., it > produces a picture with a correct number of lines, but fills > them with top part of the document only. Preview scans from > XSane and Kooka hang the scanner. But this might be a problem > of my installation: Perhaps I overlooked a file from the > previous 1.0.15 backends version. Has somone else observed a > similar behaviour? I got reports from similar problems with the 3490, but apparently previewing works for some people. Maybe it's a problem with the firmware version. The latest CVS version shouldn't need Jan's patch anymore. /Oliver
[sane-devel] Epson Pferection 3590 Photo
Hi, > scanner Epson Perfection 3590 Photo Firmware esfw52.bin > > The scanner did not work. > sane-findscanner finds the scanner: > > ... > found usb scanner vendor 0x04b8 epson scanner productid 0x0122 The 3590 is not tested yet but should work with the snapscan backend. The latest version from CVS should be working. sane-backends 1.0.16 does not support the 3490/3590. If you have any problems please let me know. Regards, Oliver
[sane-devel] xsane support of 16-bit grayscale scanner output
Hi, > I have an Epson 2580 scanner, which is capable of 16-bit output for each > channel, including what it calls monochrome. I'd like to use xsane to > preview the old black-and-white photographs that I have, and to set the > tone levels appropriately for each photograph, and then acquire the scan > with 16-bit depth. Currently the snapscan backend supports 8 bit/channel only. I have some information for 16 bit/channel so hopefully I'll be able to implement support for it sometime soon. /Oliver
[sane-devel] xsane preview problem
Hi, > I am using xsane v0.97 together with the snapscan backend (from > sane-backends v1.0.15) to drive an Epson 2580 Photo scanner. I'm > scanning old black and white photographs. Scanning works fine, but the > preview does not. There seems to be a problem with previews on the 2580 in the snapscan backend. I've no idea what the problem is, apparently it works for the 2480. AFAIK you can disconnect the transparency unit as a workaround. /Oliver
[sane-devel] Epson 3490
Hi, > The CVS snapshot I downloaded for 20050815 didn't contain that > patch. And the CVS version doesn't work for me now (whether I make > that modification or not), I alternately get messages like > > scanimage: open of device snapscan:libusb:001:003 failed: Error > during device I/O > > and > > scanimage: no SANE devices found Can you send me a debug log? Run export SANE_DEBUG_SNAPSCAN=255 then scanimage 1>/dev/null 2>debug.log > > Yes. The parameter is called "Threshold" in lineart mode. It's > > available in the Standard Options window in xsane or as option > > --threshold in scanimage. > > I get (with the 20050815 version) > > scanimage: attempted to set inactive option threshold It's supposed to be active in lineart mode only. Running scanimage --mode=Lineart --threshold=70 works fine here (although on another scanner model). /Oliver
[sane-devel] Epson 3490
Hi, > > If it is always the same ratio of real distance to scanned > > distance (also for -l and -t) it is most likely that the > > calculation of the scan area is not handled correctly. That could > > be corrected by changing the value of pos_factor in function > > set_window() in snapscan-scsi.c. > > That would seem to be the case here. Yes, so maybe it's enough to just change that value for the 3490. It's set in line snapscan-scsi.c, line 810. The value is currently set to 1600 for resolutions below 1600, 3200 for resolutions above. If your distances are off by 25%, try setting it to 1600/0.75 = 2130. > > For the guy that developed the patch that didn't help, though. > > Hm. Is that the guy that you say below has the scanner working for > him, or is it someone else? Yes. Unfortunately I've lost contact to him, i.e. he doesn't answer my mail. > > I don't think that this is an unsolvable problem. It may be > > necessary to do some deeper analysis and maybe get some USB > > traces from the windows driver, though. > > How do I go about getting such traces for you (or whoever it is > who'll likely be working on this)? You can use usbsnoop: http://benoit.papillault.free.fr/usbsnoop/ The files tend to get very large, so chose a very small scan area and a low resolution. You can send them to me in private mail. > > Also keep in mind that the scanner seems to work for at least one > > guy, so the solution can't be that difficult :-) > > I certainly hope that is the case! What did that guy do to make it > work? I.e. scanning over the whole area? He developed the patch. His last mail stated it works, so I applied it to CVS. > (On a side note: Is brightness supposed to work for lineart mode? > As it is, it tends to make Lineart mode scans too dark - things > that are clearly (but somewhat faded) white paper gets smothered in > black. My UMAX Astra 1200 didn't have that problem at all.) Yes. The parameter is called "Threshold" in lineart mode. It's available in the Standard Options window in xsane or as option --threshold in scanimage. /Oliver
[sane-devel] Epson 3490
Hi, > I don't have access to that information right now, so I'll check > that tonight also. It is whatever firmware came with the scanner - > esfw52.bin. yes, but at least for other epson scanners these firmware files are available in different versions. The filename is always the same. Another thing that I'm interested in is whether only the size of the scan area is wrong or if the origins of the scan area are also not set correctly (i.e. options -l and -t in scanimage) If it is always the same ratio of real distance to scanned distance (also for -l and -t) it is most likely that the calculation of the scan area is not handled correctly. That could be corrected by changing the value of pos_factor in function set_window() in snapscan-scsi.c. For the guy that developed the patch that didn't help, though. > My main interest at this point is to understand whether this issue > is something that can be solved with some patch to the backend, or > whether it's inherently related to the scanner's firmware or > something that is Epson-proprietary that the SANE developers won't > get access to. Is anyone able to shed some light on this issue? I don't think that this is an unsolvable problem. It may be necessary to do some deeper analysis and maybe get some USB traces from the windows driver, though. Also keep in mind that the scanner seems to work for at least one guy, so the solution can't be that difficult :-) /Oliver
[sane-devel] Epson 3490
Hi, > That made scanimage recognize and use the scanner, but it is unable > to scan the full page. It only scans 75-80% of the width and > height. Subsequent questions have gone unanswered and I've had > limited time to look into the backend code myself so I think my > solution is to return the scanner within the next few days and > rather get one that is supported by SANE. The guy who sent me the patch for the 3490 had the same problem when using low resolutions for previews. He reported that the problem disappeared after the lowest possible resolution was set to 200. The version I checked into CVS should already use 200 dpi as lowest possible values. Can you please check a few things: - What frontend are you using? - Does "scanimage" as frontend scan the correct area? E.g. does "scanimage -x 10 -y 10" scan an area of 10x10 cm? Please try with different resolutions. - What firmware file version are you using? The easiest way to find out is running strings firmware.bin | tail on your firmware file. Unfortunately I won't have much time to look into this in the next weeks. /Oliver
[sane-devel] Epson 3490
Hi, > It says that that scanner is supported with support level "basic" > by the snapscan backend. > > > sane-find-scanner gets vendor and product code but scanimage -L > > finds nothing. > > Maybe your sane-backends package is just too old? As far as I know, > you need version 1.0.16 for that scanner. You'll need the current CVS version for this scanner. 1.0.16 won't work at all (and see Bjorn's mail for the problems that still exist. I haven't yet found the time to look into it.) /Oliver
