[sane-devel] Does the Canon Lide 80 work?
Quoting Henning Meier-Geinitz henn...@meier-geinitz.de:
Hi,
On Tue, Dec 27, 2005 at 08:35:39PM -0500, golan...@aol.com wrote:
I've noticed lots of talk of the genesys backend working with canon
lide 35, 40, 50 and 60 but what of Lide 80? Is support already in
there or is it planned?
It doesn't work yet.
As none of the genesys developers seems to own such a scanner, it's up
to you to add it to the backend. See the ongoing discussions on this
list about the genesys backend.
As a quick'n'dirty trst. you could get the source code of
sane-backends (1.0.17 at least) and change the code of
backend/genesys_devices.c (at the end):
Change
{0x04a9, 0x221c, canon_lide_60_model},
to
{0x04a9, 0x2214, canon_lide_60_model},
and also add
usb 0x04a9 0x2214
to genesys.conf.
Bye,
Henning
For quick, that provides a nice start. If I remember from some of the
available comments, the LiDE 80 has a Holtek HT82V36 chip which
has some registers to initialize in the frontend, so differences might
be needed there.
best regards,
Gerald
[sane-devel] genesys-backend and ML5345 test results with 1.0.17
Le Mardi 27 D?cembre 2005 15:20, Martin Jacobs a ?crit?: Hello, after downloading libusb-0.1.10a and 1.0.17 I repeated my tests with USB-Scanner Medion MD5345 and got the following results: Test environment: Linux box based on SuSE 8.1, dual P3 933MHz, 768MB, m/b MSI 694D-Pro (MS-6321). Resolution 100 200 300600 Color ok okok 3) ok 3) Gray ok 1,2) okok ok 3) Lineartok 1,2) ok 4) ok 4) ok 3,5) Test conditions: each scan was done at least two times. Tests have been done using scanimage. Footnotes 1) Reset of scanner (power off) does not help, hotplug service has to be restarted with unloading of module usbcore. You can generate debug logs by doing: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 scanimage 2scan.log scan.pnm Send me log of a failed scan so that I can search what's going wrong. Having USB logs of the same sort of scan under windows, recorded with 'usbsnoop' (http://benoit.papillault.free.fr/usbsnoop/index.php.en) would be great. 2) Only first scan is successful, any other fails. How does it fails ? Does it hang or do you get black/garbage image ? 3) Head is moving back and forth. This is normal. At thes resolutions the amount of data to send is higher than the USB bandwidth. The data are read slower than they are produced. So the scanner as to pause, or even go backward to the place for which data have been sent. This is commonly called 'backtracking' and is not specific to this backend. By specifying a narrower width, needed bandwidth decrease and this goes away. 4) Second scan out of 5 was scrambeled. 5) Third scan out of 5 was scrambeled. 4 and 5 are surely related, and I got one other report of this. I did try it, and obviously this doesn't happen here. However I did seen such with cvs version, but got it fixed by disabling power saving helpers. You could try to compare with SANE 1.0.16 to see if you have also this 'scrambling'. I will try it on another PC, it may be related to USB subsystem (or the way it is used by the backend). Maybe you could try this also. Is your mother board USB 1.1 or 2.0 ? Compared with sane-backends there is a great improvement! Congratulation. But why do the simple test modes Gray and Lineart fail? Regards Martin Jacobs Regards, Stef
[sane-devel] genesys-backend and ML5345 test results with 1.0.17
Hi, On Thu, Dec 29, 2005 at 08:48:43AM +0100, St?phane VOLTZ wrote: 2) Only first scan is successful, any other fails. How does it fails ? Does it hang or do you get black/garbage image ? There is also a bug report in our bug tracker for the MD6471 which talks about a similar problem: The first scan works but all later scans result in black images: https://alioth.debian.org/tracker/index.php?func=detailaid=302753group_id=30186atid=410366 Bye, Henning
[sane-devel] usbsnoop for colorpage slim 1200
Henning Meier-Geinitz wrote: Hi, On Thu, Dec 29, 2005 at 03:15:33AM +0100, Juan Jose Pablos wrote: I managed to get a log for the usb transation for this scanner. I do not Which scanner exactly? The Genius Colorpage Slim 1200 this one: http://www.sane-project.org/unsupported/genius-colorpage-slim-1200-usb2.html Is it a Genius Colorpage Slim 1200 USB2? yes Here is the log: http://apertus.es/~cheche/usbsnoop_cps1200_051229.log.gz if anyone is interested, just have a look I'll add a link to it once I know for which scanner it is :-) Sorry for not giving enought information
[sane-devel] scanning problem for HP 2400
Hello,
On 12/29/05, Parag N() panem...@gmail.com wrote:
Hello Pierre,
On 12/28/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Parag N() schrieb:
Hello,
In version 1.0.17 Genesys_Frontend for HP 2400 was written as
- {{0x00, 0x03, 0x05, 0x02}
- , {0x00, 0x00, 0x00}
- , {0xc0, 0xc0, 0xc0}
- , {0x07, 0x07, 0x07}
- , {0x00, 0x00, 0x00}
which i replaced with
+ {{0x00, 0x31, 0x1f, 0x13}
+ , {0x08, 0x02, 0x16}
+ , {0x20, 0x80, 0x10}
+ , {0x80, 0x00, 0x00}
+ , {0x01, 0xff, 0x00}
Typically the .sign part is identical for all color channels.
Also i found you mentioned reset register which is not present in
structure declaration.
Writes to the reset register lead to a reset of the frontend.
But i am not getting what to send for which frontend registers are
played with during
calibration?
Sorry, i was not very clear.
I wanted to know which frontend registers are written to in your windows
log. Some registers always get the same values, while others are set to
varying values during calibration. I am guessing this frontend is
incompatible with the current implementation.
I get these information for my scanner:
[0x01] = 0x03d
[0x02] = 0x008
[0x03] = 0x000
[0x05] = 0x005
[0x06] = 0x000
[0x08] = 0x019
[0x09] = 0x006
[0x20] = 0x0e1
[0x21] = 0x0e1
[0x22] = 0x0e1
[0x24] = 0x000
[0x25] = 0x000
[0x26] = 0x000
[0x28] = 0x093
[0x29] = 0x093
[0x2a] = 0x093
Actually, the windows driver keeps the gain and offset constant for my
scanner.
here i am attaching my windows USB log + linux debug log where after
modification(i already mailed to list) + new frontend structre from my
windows log is
[0x01] = 0x000
[0x02] = 0x031
[0x03] = 0x01f
[0x04] = 0x013
[0x06] = 0x008
[0x08] = 0x002
[0x09] = 0x016
[0x20] = 0x020
[0x21] = 0x080
[0x22] = 0x010
[0x24] = 0x080
[0x25] = 0x000
[0x26] = 0x000
[0x28] = 0x001
[0x29] = 0x0ff
[0x2a] = 0x093
Please kindly tell me why head is not moving back as i make it to
scanner 1755 lines instead its default 3510 which exceeds. I then have
to disconnect scanner then only genesys debug message logging stops.
I want to know relationship between scanning no. of lines. In
genesys backend for HP 2400 i got no. of lines to scan are 3510. does
that mean scanner has to scan 1755 lines from start to other end and
then remaining 1755 from other end to start ?
regards,
Parag.
From ar...@ptic.pl Thu Dec 29 12:22:37 2005
From: ar...@ptic.pl (ar...@ptic.pl)
Date: Thu Dec 29 12:29:42 2005
Subject: [sane-devel] [genesys driver - Plustek ST24] prescan impressions
Message-ID: 43b3d50d.4000...@ptic.pl
Hi
I just to try scan witch sane-backends-1.0.17 on this scanner
(Plustek ST24). I do prescan with xsane:
- scanner do prescan only for half area---xsane fill full area
- prescan was greenish (scan too)
I do above in gray/color mode, 8/16bpp.
So, If I could help in anything, please tell me how can I do this.
Artur Pierscinski
[sane-devel] scanning problem for HP 2400
Hello Parag,
Parag N() schrieb:
Hello,
On 12/29/05, Parag N() panem...@gmail.com wrote:
Hello Pierre,
[...]
here i am attaching my windows USB log + linux debug log where after
modification(i already mailed to list) + new frontend structre from my
windows log is
[0x01] = 0x000
[0x02] = 0x031
[0x03] = 0x01f
[0x04] = 0x013
[0x06] = 0x008
[0x08] = 0x002
[0x09] = 0x016
[0x20] = 0x020
[0x21] = 0x080
[0x22] = 0x010
[0x24] = 0x080
[0x25] = 0x000
[0x26] = 0x000
[0x28] = 0x001
[0x29] = 0x0ff
[0x2a] = 0x093
This is a completely different type of frontend, incompatible with
current code. You will probably need to modify gl646_set_fe(). Making it
only write the above values for your frontend should be enough.
Please kindly tell me why head is not moving back as i make it to
scanner 1755 lines instead its default 3510 which exceeds. I then have
to disconnect scanner then only genesys debug message logging stops.
Looks to me like there is a bug. Please try park_head.diff.
I want to know relationship between scanning no. of lines. In
genesys backend for HP 2400 i got no. of lines to scan are 3510. does
that mean scanner has to scan 1755 lines from start to other end and
then remaining 1755 from other end to start ?
The problem is, the first slope generation function is severly broken.
The second version works better. create_slope.diff will make your
scanner use the second version.
Regards,
Pierre
-- next part --
--- genesys_gl646.c 2005-12-29 15:32:52.078821000 +0100
+++ genesys_gl646.c.patched 2005-12-29 15:30:29.209892250 +0100
@@ -1772,6 +1772,17 @@
return status;
}
+ /* sends slope table 0 (move before scan area) */
+ status = gl646_send_slope_table (dev, 0, dev-slope_table1,
+ reg[reg_0x6b].value);
+ if (status != SANE_STATUS_GOOD)
+{
+ DBG (DBG_error,
+ gl646_park_head: failed to send slope table 1: %s\n,
+ sane_strstatus (status));
+ return status;
+}
+
/* sends slope table 1 (move before scan area) */
status = gl646_send_slope_table (dev, 1, dev-slope_table1,
reg[reg_0x6b].value);
-- next part --
--- genesys.c 2005-12-28 14:45:00.751717000 +0100
+++ genesys.c.patched 2005-12-29 15:41:08.445842000 +0100
@@ -914,7 +914,8 @@
same_speed, yres);
if (dev-model-motor_type == MOTOR_5345
- || dev-model-motor_type == MOTOR_HP2300)
+ || dev-model-motor_type == MOTOR_HP2300
+ || dev-model-motor_type == MOTOR_HP2400)
return genesys_create_slope_table2 (dev, slope_table, steps,
step_type, exposure_time,
same_speed, yres);
From henn...@meier-geinitz.de Thu Dec 29 17:54:07 2005
From: henn...@meier-geinitz.de (Henning Meier-Geinitz)
Date: Thu Dec 29 17:54:18 2005
Subject: [sane-devel] Agfa Scanner
In-Reply-To: 20051227160207.ga1...@daniel.bse
References: 20051226221530.ga10...@daniel.bse
20051227133702.gj14...@meier-geinitz.de
20051227160207.ga1...@daniel.bse
Message-ID: 20051229175407.ga11...@meier-geinitz.de
Hi,
On 2005-12-27 17:02, Daniel Gl?ckner wrote:
On Tue, Dec 27, 2005 at 02:37:02PM +0100, Henning Meier-Geinitz wrote:
Which Agfa scanners excatly you are writing about? The 1212P and ...?
http://www.agfa.com/digicam_scanner_drivers/faq/index.html
lists four scanners which are not supported in WinXP but have a beta
driver for Win2k.
Thanks for your explanation. I added the missing scanners to our lists
and added a summary page pointing to your mail.
If you haven't noticed yet: Somebody claimed that the Agfa 1212P works
with the plustek_pp backend:
http://lists.alioth.debian.org/pipermail/sane-devel/2005-December/015658.html
Bye,
Henning
[sane-devel] [genesys driver - Plustek ST24] prescan impressions
Hi, On 2005-12-29 13:22, ar...@ptic.pl wrote: I just to try scan witch sane-backends-1.0.17 on this scanner (Plustek ST24). I do prescan with xsane: I assume the only thing you did was removing the comment sign in front of this scanner's USB ids in genesys.conf? - scanner do prescan only for half area---xsane fill full area - prescan was greenish (scan too) I do above in gray/color mode, 8/16bpp. Doesn't look that bad. So, If I could help in anything, please tell me how can I do this. Search the archive of this mailing list for several hints and tools concerning the genesys backend. Bye, Henning
[sane-devel] genesys-backend and ML5345 test results with 1.0.17
Hi, On 2005-12-29 21:27, St?phane VOLTZ wrote: BTW I can't connect to alioth: Your mail to sane-devel went through, however. And the mailing lists are also handled by alioth. nslookup alioth.debian.org Server: 127.0.0.1 Address:127.0.0.1#53 ** server can't find alioth.debian.org: SERVFAIL $ dig alioth.debian.org [...] ;; ANSWER SECTION: alioth.debian.org. 322 IN A 192.25.206.28 Works for me. However, alioth's root file system is nearly full again so mail errors are expected. Bye, Henning
[sane-devel] Canon LiDE 35: test report
Hi, On 2005-12-29 20:55, Bert Kortenbosch wrote: I did some tests with the Canon LiDE 35 Scanner and the sane genesys backend, based on the CVS snapshot snapshotsane-backends-2005-12-29.tar 2400: text distorted, width/height ratio wrong This is a known issue. Color (Scan Mode, Bit depth 16) 75: ok, color distortion visable (viewer mode) Could you show us a small sample of this effect? I can confirm a slight line distance problem when looked at high magnification, but it's also visable at 8 bit per color. It may be a hardware problem... Optical resolution 1200 x 2400 dpi That's the problem, the optical resolution is only 1200 dpi in X direction. Selectable resolution 25 - 9600 dpi (software) This is just marketing. Is the 2400 dpi mode correctable from within the backend or is this an Xsane issue? It's a backend issue. The backend must double the x resolution in the 1200/2400 dpi mode. Or better yet, interpolate the missing pixels. As a work aound, you can use gimp or similar programs to double the number of pixels in x direction. Bye, Henning
[sane-devel] AMD64 problem with 32bit apps and SCSI scanners
I have a commercial 32bit application which is linked with sanei_scsi.c, and which fails to detect any connected SCSI scanner when running on an AMD64 system. Communication with the scanner is via /dev/sgX, it fails in a write() call returning EINVAL. The author of said app refuses to compile a 64bit version, but is prepared to link a version of sanei_scsi.c which has its write() wrapped in such a way that it works on both 32bit and 64bit systems. At first glance, there are two write() calls involved. Before I have a detailed look at the code, is someone knowledgable able to give a guess as to whether this seems to be at all possible? I would at this point imagine that the problem is in 32/64bit byte ordering and structure packing, and that some byte shuffling would be nececassry. Thanks, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
[sane-devel] os/2 specific change needed in sane-frontends/src/xscanimage.c line 2206ff
Hi, in sane-frontends/src/xscanimage.c lines 2206 - 2208 make trouble when I compile xscanimage for OS/2 with GTK2 as GIMP2-Plugin Could someone please change lines 2206ff to something like # ifdef ENABLE_GIMP_1_2 # ifdef HAVE_OS_H set_gimp_PLUG_IN_INFO (PLUG_IN_INFO); # endif # endif Thanks Franz
