[sane-devel] Re: [solved?] Re: Plustec OpticSlim 12M - calibration
On Sat, 02 Dec 2006 22:34:37 +0100, Maciej Piechotka wrote: On Fri, 01 Dec 2006 00:21:08 +0100, Maciej Piechotka wrote: I have probably not calibrated scanner (If I scan something it returns blue sheet). How can I do it? Regards I do 2 calibration on windows and it works ok. I think I do not update nothing. Anyway thanks... Regards Sorry - It's only for one page... Regards -- I've probably left my head... somewhere. Please wait untill I find it. Homepage (pl_PL): http://uzytkownik.jogger.pl/ (GNU/)Linux User: #425935 (see http://counter.li.org/)
[sane-devel] [Announce] JSane
Hello Andi, nice work. Just to mention: when I run ScanPage (with the server-name and options adopted to my setup), there seems to be a problem with device.close(). The first time, the image gets scanned correctly and is shown in the JFrame which pops up, but a second run fails with: Scanning a page uk.org.jsane.JSane_Exceptions.JSane_Exception_Invalid: Invalid operation at uk.org.jsane.JSane_Exceptions.JSane_Exception.getException(JSane_Exception.java:53) at uk.org.jsane.JSane_Net.JSane_Net_Device._open(JSane_Net_Device.java:235) at uk.org.jsane.JSane_Net.JSane_Net_Device.open(JSane_Net_Device.java:88) at uk.org.jsane.JSane_Frontends.ScanPage.init(ScanPage.java:66) at uk.org.jsane.JSane_Frontends.ScanPage.main(ScanPage.java:119) Also, scanimage says: scanimage: open of device net:10.0.0.100:brother:bus1;dev1 failed: Invalid argument This can only be fixed by disconnecting the scanner's USB cable and reconnect it again. The device is a Brother MFC3420C with the driver delivered by Brother, brscan-0.2.1-0.i386.deb. The server runs on Debian packages libsane 1.0.16-4, sane 1.0.14-1 and sane-utils 1.0.16-4. Btw, closing the JFrame after the first run does not terminate the application, I have to manually kill it. Don't know if that's the normal behaviour. This is not a problem for me because I don't practically use JSane, but I thought you'd like to know. best Jens Andi McLean schrieb: In case any body is interested, I've just released version 0.8 of JSane. It is now under the LGPL, It contains a few improvements suggested by users, also experimental GUI code for reading and setting options and performing a scan. I've also (finally) updated the website. There is now a couple of tutorials on using JSane, with another one on using the GUI dialogs coming soon. Many thanks Andi
[sane-devel] Preview scan fails with ScanJet 5370C (avision backend)
Hello, I'm having problems with an HP ScanJet 5370C, using the Avision backend, on the second and all following preview scans. On the first attempt, the preview scan is successful. On the second, and all further, attempts the scan head moves back and forth a small amount (initial alignment?), then makes a noise (a fairly unsettling one - possibly motor strain?) like it's trying to take the preview scan - but the scan head doesn't move. All further attempts fail until _all_ the following have been performed: 1) unplug the scanner from mains and USB 2) modprobe out, then modprobe back in ehci_usb 3) plug the scanner back in 4) run a preview scan in VueScan Now, 4) seems odd - but if I don't do this then xsane hangs on startup with device I/O errors. This behaviour bears a striking similarity to the problems I experienced due to another bug that was apparently fixed with version 1.0.18 of sane-backends [1]; indeed after the first failed preview scan, if I unplug the scanners USB cable then plug it back in (without bus or scanner reset) I get the error: localhost kernel: usb 1-1.3: new full speed USB device using ehci_hcd and address 8 localhost kernel: usb 1-1.3: device descriptor read/64, error -110 This would appear, at least superficially, to be similar to the bug I was previously experiencing with this scanner [1]; I DON'T believe it to be related to kernel/usb/hub issues I've experienced with this scanner [2]. xsane debug output with successful preview scan: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=136043 xsane debug output with second preview scan that fails: https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=136044 I also reported the bug in the Fedora bugzilla (though there's no extra information beyond what I've described here): https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=206094 [1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205092#c1 [2] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200122 Best regards, Kevin Page
[sane-devel] Location of some backend's files
On Sun, 3 Dec 2006, JKD wrote: El Sun, 03 de Dec de 2006, a las 11:13:07AM -0500, m. allan noah dijo: On Sun, 3 Dec 2006, JKD wrote: Hello, I'm hp3900 backend's developer. Due to this backend supports some scanners and new devices could be supported in the future I'm thinking about the possibility to create different config files for each scanner capabilities to maintain code's structure legible. but you will have to add code that parses these files, and builds them into an array of structs. having that array compiled into the backend will be faster, and maybe less code. Code to parse files would be done the first time. Sources wouldn't need to be rewriten each time a new scanner is added. Due to config is out of code, application's size is much lower and only is necessary to allocate dynamic memory for one scanner instead of all supported scanners. the app will not be smaller, unless you are talking about dozens of scanners. the packed c structs will be smaller than your parsing code. Another advantage is that any change in structs wouldn't affect configuration causing compilation problems. i do not understand this point. perhaps something lost in translation? The only disadvantage as you say is that there is a little lapsus of time (may be not perceptible) when using sane_open function. But after sane_open, backend works as fast as it was before. It's not simple configuration which user should change but internal values to program RTS8822 chip in each case (area constrains to scan, sensor timing values, motor curves...) so I wouldn't set them at sane.d/hp3900.conf if they are not user-changeable, then why do they need to be a separate file? Because it's easier for any developer or anyone who wants to try to support his new scanner, under his own responsability, editing desired values without compiling backend in each change (It's faster in this way). For security reasons these files can be read only so normal users can not make any change. ok, so if you only anticipate this being used by an advanced user, then why not put overrides for all these settings in your regular config file? that is how all the other backends do it, IIRC. you could have a default series of slow, small parameters that are used for any unknown scanners, and the user can change them. Is there any standard path in SANE to locate such files? Something like sane.d/backend's name/ or may be /usr/share/backend's name/ i would consider it a security risk to have such a low-level control file read from the home-dir of the user, and non-linux systems may not have a /usr/share, but they will have the sane.d config-file dir, so perhaps sane.d/backendname/ is best (though i dont see the need for it...) If all of you think that it's not a good idea I'll keep config inside code. i should have stated that i also am only a single backend developer, so i dont speak for SANE at all, just myself. allan Jonathan Bravo Lopez -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera
[sane-devel] Plustek ST24
St?phane VOLTZ napisa?(a): Hello, here's the mentioned scripts. There are 2 main ones: - decode.sh : turns raw usb log in higher level form - cmd.sh : turns the output of the decoding in high level status dumps The first script uses a swarm of little awk scripts that handle a little step of decoding each. At the end, there shoudn't be any lines 'URB .' remaining if everything has been decoded. In case any are left, they're meaning has to be understood so that the scripts can handle them. Usually the left over are custom button or power saving handling. If needed, they can be filtered out as shown in decode.sh . The second script parses the high level output and builds a in memory status of the scanner. Each time a motor start is found (motor start is use as a 'commit'), the whole status (slope tables, analog fronted and registers) is dumped. It allow to compare the debugging output of the backend with the expected status of the scanner. This filters out the many useless registers writing/reading done by drivers. All scripts keeps data, so logs may be huge, but you can then rebuild pictures of scans from the recorded data. which help understanding what the scanner is doing. Doing such his explained in http://perso.modulonet.fr/~stefdev/sane/gl646-wip03.odt I'll be out for a couple of day, so I will answer any question/point when I'll be back. Regards, Stef Ok thx! i will work on it :)
[sane-devel] 3 minor problems with current (20061202) CVS code on OS/2
On Saturday 02 December 2006 22:11, Alessandro Zummo wrote: On Sat, 02 Dec 2006 21:26:25 +0100 (CET) Franz Bakan fba...@gmx.net wrote: On Sat, 2 Dec 2006 20:31:06 +0100, Alessandro Zummo wrote: well, you need to check where are those functions/types defined on os/2 :) Yes, I know and already checked, but unfortunattely there is not place where __le16_to_cpup(), __u16,, __le32_to_cpup(), __u32, __le32 or __cpu_to_le32() are defined on OS/2. What do you suggest? mmm.. you should try to find similar macros we can use/adapt in some OS/2 include file... I guess endianness conversion is performed even on OS/2 ;) Hmmm, I think you should not use these macros in userspace anyway! They are not portable an I'm pretty sure building SANE on any platform but Linux will fail. my 2 cents Gerhard
[sane-devel] 3 minor problems with current (20061202) CVS code on OS/2
On Mon, 4 Dec 2006 19:28:43 +0100 (MET) Gerhard Jaeger gerh...@gjaeger.de wrote: __le16_to_cpup(), __u16,, __le32_to_cpup(), __u32, __le32 or __cpu_to_le32() are defined on OS/2. What do you suggest? mmm.. you should try to find similar macros we can use/adapt in some OS/2 include file... I guess endianness conversion is performed even on OS/2 ;) Hmmm, I think you should not use these macros in userspace anyway! They are not portable an I'm pretty sure building SANE on any platform but Linux will fail. mm. right. So I need to find some portable macros or include appropriate one in sane. any suggestion? -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it
[Fwd: Re: [sane-devel] Re: Plustec OpticSlim 12M - calibration]
Just to inform about this usb sniff file (link from Maciej Piechotka), should include calibration info for the Plustec OpticSlim 12M (gt68xx backend) -- m.vr.gr. Gerard Klaver -- next part -- An embedded message was scrubbed... From: Maciej Piechotka uzytkown...@gmail.com Subject: Re: [sane-devel] Re: Plustec OpticSlim 12M - calibration Date: Sun, 3 Dec 2006 20:57:37 +0100 Size: 6455 Url: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061203/fffd7e7e/attachment.mht From keith.che...@wanadoo.fr Mon Dec 4 12:51:37 2006 From: keith.che...@wanadoo.fr (Keith Cheong) Date: Mon Dec 4 22:39:30 2006 Subject: [sane-devel] epson scanner 4180 Photo Message-ID: 45740bc9.1090...@wanadoo.fr Dear sirs, hope you can help me! I'm new to Linux systems. So I'm very confused as to how to set up and use my Epson Perfection 4180 Photo scanner. I've tried downloading the driver from epson and have the iscan-2.4.0-0.c2.tar.gz file on my desktop and followed the instructions to install. But it falters after ./configure, so I can not 'make' or 'make install'. I'm using Ubuntu-Linux 6.10. If you can offer any assistance I would be extremely grateful. Yours sincerely Keith Cheong.
[sane-devel] scanner found by sane-find-scanner but not by scanimage -L
Hi, I don't know if this email is sent to the correct list. Please tell me if not. My problem is as follow: I have a Snapscan e25 (agfa) on a ubuntu 6.06 machine. This was working nice until I add a Samsung printer (ML2010). Apparently, the proprietary driver of the printer does some nasty things, including altering the sane configuration (in case the printer is a multifunction, which it isn't in my case). Since I installed the printer, xsane was working as root. I did some googling today, and found that re-installing sane solved the problem. I tried, and since then, my scanner is no longer found (I reinstalled Snape25.bin as well, and the files in /etc/sane.d haven't changed after the reinstall). Basically, if I run sane-find-scanner, it returns: found USB scanner (vendor=0x06b9, product=0x4061) at libusb:001:003 if I run scanimage -L (as user or root): No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). SANE_DEBUG_DLL=128 scanimage -L doesn''t mention anything special around the snapscan lines: [dll] init: backend `sp15c' is version 1.0.0 [dll] load: searching backend `snapscan' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-snapscan.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-snapscan.so.1' [dll] init: initializing backend `snapscan' [dll] init: backend `snapscan' is version 1.4.50 [dll] load: searching backend `sm3840' in `/usr/lib/sane' I also found that it might be better to remove sane completely, to make sure there is no conflict between two installs, but there is apparently a dependency on gnome-desktop, so I would prefer not to do this... I'm a bit lost, because in most of the similar issues that I can found, people check the scanner module, which apparently is not used anymore (and by the way I don't have it) Any ideas? Regards Cyril
