[sane-devel] Possible Solution Canon Lide 20 noise-problem
Hi! If still current: In order to solve the problem with the noise in Canon Lide 20 on Linux (I'm using Debian): Uninstall sane, xsane and libsane in Synaptic (package manager). Install libsane version 1.0.15-9 instead of the current default 1.0.18 version (you can find it here: http://packages.debian.org/stable/libs/libsane). Then install sane again. Synaptic, as I understand, can only install sane version 1.0.14-1 after this because of the dependencies with the older libsane version. That sane version seems to work! (in contrast to sane version 1.0.18.) Install xsane again in Synaptic and that's it. Don't forget to block the installed libsane 1.0.15-9 version and the sane 1.0.14-1 version in the package menu, otherwise it will be replaced by an update with time. Happy new year to all! PS: The new Debian test version (Etch) is just cool! -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal f?r Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
[sane-devel] Re: Canon 4400F
On 12/31/06, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Jaagup Rep?n schrieb:
Jaagup Rep?n wrote:
Hello.
I have Canon 4400F scanner. This is not supported, but it must to be
added to genesys backend. I am trying to add, but I need help. I
have to find SENSOR, DAC, GPO and motor type, shading and search lines,
start of scan area, white strip and black mark.
I forgot to say that I have USB sniffer log
file(http://jrepan.pri.ee/usbsnoop.log.decode) and I found some
information from
http://lists.alioth.debian.org/pipermail/sane-devel/2005-December/015750.html
I got frontend:
{{0x02, 0x20, 0x30, 0xdc}
, {0x32, 0x00, 0x03}
, {0x10, 0x32, 0xc8}
, {0xda, 0x00, 0x00}
, {0xf0, 0x00, 0x00}
Is this correct?
From your log i get this:
{{0x00, 0x23, 0x24, 0x2f}
, {0x00,0x00,0x00} //never set in log
, {0x60,0x60,0x60}
, {0xfa,0xfa,0xfa}
, {0x00,0x00,0x00} //never set in log
look for this sequence:
wrote 0x51 frontend register address
wrote 0x3b high bit of data
wrote 0x3a low bits of data
those are frontend register writes(at least in your log).
Regarding the Motor struct, this will probably work(without looking at
your log)
{
2400,
4800,
1,
{
12000,
12000,
1,
1.0
},
{
12000,
12000,
1,
1.0
}}
This should lead to very slow movements of the scanning head, but it
should move if the scanner is correctly initialized(the Canon LiDE
35/50/60 are a bit tricky, and the 500F seems to be similar).
As you can see, i use half of the real resolution here. The reason is,
the backend is not (yet) capable of using something other than 2400,
1200 or 600 as sensor resolution. In the meantime, we can make double
the scanner dimensions, to accommodate for the real 4800dpi.
The gl841 part of the backend also lacks support for non-LiDE color sources.
Hope that helps,
Pierre
On 12/31/06, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Jaagup Rep?n schrieb:
Jaagup Rep?n wrote:
Hello.
I have Canon 4400F scanner. This is not supported, but it must to be
added to genesys backend. I am trying to add, but I need help. I
have to find SENSOR, DAC, GPO and motor type, shading and search lines,
start of scan area, white strip and black mark.
I forgot to say that I have USB sniffer log
file(http://jrepan.pri.ee/usbsnoop.log.decode) and I found some
information from
http://lists.alioth.debian.org/pipermail/sane-devel/2005-December/015750.html
I got frontend:
{{0x02, 0x20, 0x30, 0xdc}
, {0x32, 0x00, 0x03}
, {0x10, 0x32, 0xc8}
, {0xda, 0x00, 0x00}
, {0xf0, 0x00, 0x00}
Is this correct?
From your log i get this:
{{0x00, 0x23, 0x24, 0x2f}
, {0x00,0x00,0x00} //never set in log
, {0x60,0x60,0x60}
, {0xfa,0xfa,0xfa}
, {0x00,0x00,0x00} //never set in log
look for this sequence:
wrote 0x51 frontend register address
wrote 0x3b high bit of data
wrote 0x3a low bits of data
those are frontend register writes(at least in your log).
Regarding the Motor struct, this will probably work(without looking at
your log)
{
2400,
4800,
1,
{
12000,
12000,
1,
1.0
},
{
12000,
12000,
1,
1.0
}}
This should lead to very slow movements of the scanning head, but it
should move if the scanner is correctly initialized(the Canon LiDE
35/50/60 are a bit tricky, and the 500F seems to be similar).
As you can see, i use half of the real resolution here. The reason is,
the backend is not (yet) capable of using something other than 2400,
1200 or 600 as sensor resolution. In the meantime, we can make double
the scanner dimensions, to accommodate for the real 4800dpi.
The gl841 part of the backend also lacks support for non-LiDE color sources.
Hope that helps,
Pierre
I habe a similar log, not decodes as nicely though.
I try to get the Plustek OpticSlim 2420 with GL842 to work.
I find in the log that the frontend registers are modified many times.
How do I know which values to take for the frontend?
I scanned through the snoop log
(also uploaded here: http://www.physik.tu-berlin.de/~mxhf/OS2420/PreviewScan.rar
SnoopyPro 0.22)
by hand and found
following writes to the frontend registers:
URB#REG(from 51)Values (from 3b, 3a zero alway)
Plugging scanner in
...
42 :00-03 00 23 24 07
...
URB 48 was the last one after plugging the scanner in,
started preview scan.
...
88 :00-03 00 23 24 07
...
150 : 00-03 00 27 24 0f
04-06 00 00 0f
20-22 80 80 80
28-2a 4b 4b xx
...
152 : 28-2a xx xx 4b
...
192 : 29 4b
2a 4b
28 4b
21 7f
22 7f
20 7f
...
250 : 21 00
22 00
20 00
...
322 : 21
[sane-devel] [claudesut...@suttonmachine.com: lib/libjpeg.la]
Sorry. I meant to advise that I am running Ubuntu Dapper. - Forwarded message from Claude Sutton claudesut...@suttonmachine.com - From: Claude Sutton claudesut...@suttonmachine.com Date: Mon, 1 Jan 2007 12:12:30 -0500 To: sane-devel@lists.alioth.debian.org Subject: lib/libjpeg.la I am attempting to install iscan for an Epson PHOTO 4490. When I run ./compile, I get the error message /usr/lib/libjpeg.la: No such file or directory googling this problem found a post that libjpeg is in lib64, so I checked to see if I have lib64 and I do. So what to do? CSSJR -- If we do not wish to lose our freedom, we must learn to tolerate our neighbor's right to freedom even though he might express that freedom in a manner we consider to be eccentric. - End forwarded message - -- If we do not wish to lose our freedom, we must learn to tolerate our neighbor's right to freedom even though he might express that freedom in a manner we consider to be eccentric.
[sane-devel] Plustek Optic Slim 2420
Maximilian Fabricius schrieb: Hi all, I have been working on trying to get the OpticSlim 2420 to work. Is disassembled the scanner (hardware) and made pictures. they may be found here http://rosa.physik.tu-berlin.de/~mxhf/OS2420/ They are fairly high resolution ~1MB per image so that you can see all details. lease excuse the German on the navigation bar. This scanner has a Wolfson Micro WM8196 analog frontend, an ICSI IC41LV16256-35K memory chip(256k 16bit words), LB1940 motor driver chip. From this I learned that the scanner has a GL842 chip (not GL841). The GL842 seems to be very similar to the 841 though as a quick scan through the data sheet revealed. In fact, at least the things documented in genesys' datasheets are identical. So far I cloned the ST24 section in genesys_gl841 and I got as far as being able to execute tstbackend without getting an error. I had to comment the Init_Devices lines 4990-4993 in genesys_gl841.c. I am somewhat stuck now. Starting scanimage results in strange noise from the scanner. Try the motor struct i sent in the Canon-4400F thread[1]. Concerning your frontend settings, use the register state just before the preview scan starts(which probably is urb 1367 in the log referenced in [2]). By the way: i am preferring usbsnoop[3], which dumps the usb log into a plain text file, making parsing it way easier. Also, it does not stop logging, when it encounters an urb larger than 16k or so(fortunately for you, the plustek driver does not use that large urbs). Regards, Pierre [1] http://lists.alioth.debian.org/pipermail/sane-devel/2006-December/018335.html [2] http://lists.alioth.debian.org/pipermail/sane-devel/2007-January/018338.html [3] http://benoit.papillault.free.fr/usbsnoop/
[sane-devel] [claudesut...@suttonmachine.com: lib/libjpeg.la]
On Mon, 2007-01-01 at 12:14 -0500, Claude Sutton wrote: Sorry. I meant to advise that I am running Ubuntu Dapper. - Forwarded message from Claude Sutton claudesut...@suttonmachine.com - From: Claude Sutton claudesut...@suttonmachine.com Date: Mon, 1 Jan 2007 12:12:30 -0500 To: sane-devel@lists.alioth.debian.org Subject: lib/libjpeg.la I am attempting to install iscan for an Epson PHOTO 4490. When I run ./compile, I get the error message /usr/lib/libjpeg.la: No such file or directory googling this problem found a post that libjpeg is in lib64, so I checked to see if I have lib64 and I do. So what to do? CSSJR -- Did you install the -dev packages (header files)? -- m.vr.gr. Gerard Klaver
[sane-devel] scanner's buttons daemon+gui
Le lundi 1 janvier 2007 07:50, JKD a ?crit : El Sat, 30 de Dec de 2006, a las 05:27:43PM +0100, Jean-Christophe 'Jice' Cardot dijo: Hi I've developped a GUI + daemon (based on code by Rene Rebe - avision backend) for buttons support through SANE. Web site: http://cardot.net/KScannerButtons At the moment the daemon is a quick and dirty hack based on Rene's code, but at least working. The GUI is built using Kommander from kde-webdev; only the daemon is mandatory. It's using the SANE backend to talk to the scanner (and not adressing the scanner directly through libusb as scanbuttond does - see scanbuttond.sourceforge.net). I tested it only with the avision backend and a HP 5300 C scanner. I was wondering wether or not there is a convention for buttons among backends: in the avision backend, the option name is equal to button-button number. Also, which backend support buttons? Could you please test my software with your scanner (if your backend support buttons) to help me build a list of supported devices? I've added support for buttons in hp3900 scanner in the same way avision does (SVN server at sourceforge). So at least these scanners should work with KScannerButtons: - hp scanjet 3800 (3 buttons) - hp scanjet 3970 (4 buttons) [tested] - hp scanjet 4070 (4 buttons) - hp scanjet 4370 (4 buttons) [tested] - umax astra 4900 (4 buttons) - umax astra 4950 (4 buttons) Changes in hp3900 will be official in the next version. I included a module in scanbuttond project to manage these scanners too. Hi Jonathan This will be reflected on the web site soon. I hope some more backend developpers will answer my email so that we can expand that list. I've translated your frontend to spanish. If you want to add that language to your project you can download .po file at this location: Thanks! Will be in next version :) http://jkdsoftware.dyndns.org/files/others/kscannerbuttons-es.tar.gz PS: I was also wondering why the button support as found in scanbuttond is not (or is it?) in the backends. For me SANE is the preferred way to access scanners, and any button daemon should make use of SANE backends... I agree with you. I suppose this stuff is going to be solved when SANE2 arrives but I think that will take a long time. IMHO sanebuttonsd (and your frontend) is better solution than scanbuttond. yep. But do you know if there is a specification on how should the SANE backends handle the buttons? Jonathan Bravo Lopez bye -- Jean-Christophe Jic? Cardot - http://lea-linux.org -- 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/20070101/8ebdfb06/attachment.pgp From adeur...@gmx.net Mon Jan 1 23:16:53 2007 From: adeur...@gmx.net (abel deuring) Date: Mon Jan 1 23:17:39 2007 Subject: [sane-devel] Sane and HAL Message-ID: 45998855.1060...@gmx.net Hi all, a happy new year to you all! I tried to become a bit more familiar with HAL (http://freedesktop.org/wiki/Software_2fhal) and I think that this is a project that Sane should support. And no, it will not create any compatibility problems, as feared by some colleagues during the short discussion in December last year. As I understand it, HAL is mainly a daemon that manages a list/database of hardware resources, monitors hotplugging, and provides mechanisms for device configuration and other things like automatic launch of an application, if a certain device is detected/plugged in. The minimum we can (and IMO should) do is to provide an XML file (or .fdi file in HAL terminology) that describes the scanners supported by Sane, and optionally the unsupported scanners. The fdi file contains information like scanner vendor/model name, interface type (USB/SCSI/parport...), Sane backend(s) for the device, and unique device information, like USB vendor/product ID or the SCSI vendor/product strings. This file can be easily generated from our *.desc files. Right now, the latter contain already all required information for USB scanners; for the SCSI interface, we would need to add the keyword :scsiid; an entry for this keyword should look like :scsiid SHARP JX250 SCSI A similar keyword would be needed for the Firewire interface, but I have no idea, how Firewire devices can be identified; if some parport scanners supported by a Sane backend can also tell something about themselves in some standardized way, this should be included too in the *.desc files. I wrote a little Python script that transforms the data from the *.desc files into an .fdi file; if this file if placed at /usr/share/hal/fdi/... , the program lshal for example lists a number of details about the available scanners (e.g., vendor/model name and useable backend(s)); similary, interested applications can use this data to find a scanner and a suitable
[sane-devel] scanner's buttons daemon+gui
El Sat, 30 de Dec de 2006, a las 05:27:43PM +0100, Jean-Christophe 'Jice' Cardot dijo: Hi I've developped a GUI + daemon (based on code by Rene Rebe - avision backend) for buttons support through SANE. Web site: http://cardot.net/KScannerButtons At the moment the daemon is a quick and dirty hack based on Rene's code, but at least working. The GUI is built using Kommander from kde-webdev; only the daemon is mandatory. It's using the SANE backend to talk to the scanner (and not adressing the scanner directly through libusb as scanbuttond does - see scanbuttond.sourceforge.net). I tested it only with the avision backend and a HP 5300 C scanner. I was wondering wether or not there is a convention for buttons among backends: in the avision backend, the option name is equal to button-button number. Also, which backend support buttons? Could you please test my software with your scanner (if your backend support buttons) to help me build a list of supported devices? I've added support for buttons in hp3900 scanner in the same way avision does (SVN server at sourceforge). So at least these scanners should work with KScannerButtons: - hp scanjet 3800 (3 buttons) - hp scanjet 3970 (4 buttons) [tested] - hp scanjet 4070 (4 buttons) - hp scanjet 4370 (4 buttons) [tested] - umax astra 4900 (4 buttons) - umax astra 4950 (4 buttons) Changes in hp3900 will be official in the next version. I included a module in scanbuttond project to manage these scanners too. I've translated your frontend to spanish. If you want to add that language to your project you can download .po file at this location: http://jkdsoftware.dyndns.org/files/others/kscannerbuttons-es.tar.gz PS: I was also wondering why the button support as found in scanbuttond is not (or is it?) in the backends. For me SANE is the preferred way to access scanners, and any button daemon should make use of SANE backends... I agree with you. I suppose this stuff is going to be solved when SANE2 arrives but I think that will take a long time. IMHO sanebuttonsd (and your frontend) is better solution than scanbuttond. Jonathan Bravo Lopez
