Ralf Haueisen schrieb:
Ralf Haueisen schrieb:
Hi all.
I am just working to get my Canon LiDE 90 working. I took in the
genesys_devices.c the LiDE60 an did some changes. I have a sniffer
log taken with usbsnoop. Some registers i could firgue out where to
set them. The image still looks like
Ralf Haueisen schrieb:
Ralf Haueisen schrieb:
Hi all.
I am just working to get my Canon LiDE 90 working. I took in the
genesys_devices.c the LiDE60 an did some changes. I have a sniffer
log taken with usbsnoop. Some registers i could firgue out where to
set them. The image still looks like
Ralf Haueisen schrieb:
Can you send a small image?
The image shows the cover of a book...
This looks like the shading correction(corrects for the properties of
each ccd cell) is making the image worse. please disable it by changing
gl841_init_optical_regs_scan to only disable it:
/*
Volker Grabsch schrieb:
On Fri, Nov 16, 2007 at 10:24:05AM -0500, m. allan noah wrote:
This is the proposed timetable for the release of sane-backends 1.0.19:
2008-01-06 Feature freeze
2008-01-20 Code freeze
2008-02-03 Release
[...]
If there are any new backends that should be included in
Pierre Willenbrock schrieb:
Volker Grabsch schrieb:
On Fri, Nov 16, 2007 at 10:24:05AM -0500, m. allan noah wrote:
This is the proposed timetable for the release of sane-backends 1.0.19:
2008-01-06 Feature freeze
2008-01-20 Code freeze
2008-02-03 Release
[...]
If there are any new
Ralf Haueisen schrieb:
-Urspr?ngliche Nachricht-
Von: Pierre Willenbrock pierre at pirsoft.dnsalias.org
Gesendet: 27.11.07 22:23:19
An: Ralf Haueisen ralf.haueisen at web.de
CC: sane-devel at lists.alioth.debian.org
Betreff: Re: [sane-devel] Canon LIDE 90
Ralf Haueisen schrieb
Hi Volker,
Volker Grabsch schrieb:
Dear Sane Developers,
I just started to analyze my scanner CanoScan LiDE 90.
I'm using the current sane-backends tools (CVS version) with the
experimental genesys drivers (CVS version).
According to sane-find-scanner it contains a GL842 chipset.
stef schrieb:
Le Saturday 10 November 2007 07:48:52 stef, vous avez ?crit :
Le Friday 09 November 2007 11:57:57 Pierre Willenbrock, vous avez ?crit :
Hi list,
i need someone with a gl646-based scanner to test the attached patch.
It is my solution for problems on e.g. arm system which align
Hi list,
i need someone with a gl646-based scanner to test the attached patch.
It is my solution for problems on e.g. arm system which align byte
values on 2 byte boundaries, without resorting to attribute((packed)).
The dirty byte in Genesys_Register_Set is just for testing purposes
and will
Mohammad Tabbara schrieb:
Hi all,
I've installed backends 1.0.18 on debian etch on arm and have a Canon
Lide 50 attached that is detected by the backend but results in a seg
fault when trying to scan. I've tried the various combinations of the
following:
pre-built debian packages
kent whitten schrieb:
I'm trying to get this going, and could use any hints
what the gpio pins might be used for. This guy has
lots more pins set for output, than any other genesys
device. I'm actually scanning, but getting nothing
back but zeros, so I'm taking all 200 passes in
Ren? Kjellerup schrieb:
Hi' all,
Now I've made a few logs, and I've come across something
odd.
I start the sniffer, then open the preview/scanning
interface from my photo editor (PS7).
And when it's running, the sniffer just stops getting any
more packets even when scanning an image
Hi Igncio,
J. Ignacio Gij?n schrieb:
Sorry if you receive this message twice, I sent a similar one
yesterday but it looks
like it is lost.
It is right there.
My question es about the HP G4050 scanner that uses a gl843 chip. I
have had
one of this for a couple of weeks now, and have been
Pierre Willenbrock schrieb:
Luke Campagnola schrieb:
It's been a while since I originally brought this up, but I've pulled out
the ol' scanner for another go.
to recap: color calibration isn't quite right on my canon lide35--the dark
colors drop out to black. I turned
there.. the darks may be slightly better but now the
lights are clipped too. I've attached output + pnms.
Thanks.
On 1/4/07, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Luke Campagnola schrieb:
It's been a while since I originally brought this up, but I've pulled
out
the ol' scanner
colors, use SANE_DEBUG_GENESYS=255 and
SANE_DEBUG_GENESYS_GL841=255 with scanimage in color mode, and send the
resulting error output and the generated .pnms.
Regards,
Pierre
On 3/7/06, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
- Color reproduction is better with the sane driver
Maximilian Fabricius schrieb:
On 1/1/07, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
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
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
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
Hi Henrik
Henrik Uggla schrieb:
I've got a Canoscan Lide 50. I have discovered that when I scan at 150
dpi or more the greys are missing in depth (in the black end). But when
I scan at only 75 dpi the result looks much better since darker and
lighter pixels are mixed to show the right grey
Maik Musall schrieb:
Hi,
I'm newly subscribed here, and found just two postings about this
scanner in the archives. I purchased one today and am trying to get
support for it. So far, no success. I tried to just add a struct
canon_lide_70_model into genesys_devices.c by copying the lide_60
Aaron Lawrence schrieb:
Hello all,
[...]
I used the awk and perl script on http://john.daltons.info/lide60/ to
generate some output of plugging in the scanner, initializing and a
300dpi color scan. It was a while ago when I took the usb log but I
believe I canceled the scan partway
Hi Ralph,
Ralph Sontag schrieb:
These scanners are pretty low-level. To do anything useful, you need to
setup the motor and ccd. This includes calibration. The calibration is
done only once in win98.
So I will setup win98 once again and made a start the sniffer before the
first connect.
Hi Ralph,
Ralph Sontag schrieb:
Hi Pierre,
I put my scripts here:
http://pirsoft-dsl-dropzone.de
I made a new scan:
0 .. ~ 5 MB : USB starts
5 .. ~ 15 MB : ScanGear - the Canon-Program starts
15 .. ~ 110 MB : Calibration.
110 .. ~ 200 MB : Scan (visiting card, 300, ca. 1.5
...
Name: canon-500f.diff
Type: text/x-patch
Size: 26419 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060512/6ada0c43/canon-500f-0001.bin
From pie...@pirsoft.dnsalias.org Fri May 12 21:18:52 2006
From: pie...@pirsoft.dnsalias.org (Pierre Willenbrock
Hi list,
i am trying to make the scanning speed of my scanner depend on the usb
speed available. I first attempted to use the detection from the cs3200f
backend, but found that it only detects if the device is high speed
capable, not if it is currently communicating with high speed.
On further
Hi Ralph,
Ralph Sontag schrieb:
I have an Canon CanoScan LiDE 500F.
I've added in backend/genesys_devices.c a section as a copy from
the LiDE 60 - ok, now scanimage list the device:
scanimage -L
device `genesys:libusb:001:050' is a Canon LiDE 500F flatbed scanner
But it don't
Gerald Murray schrieb:
Quoting Pierre Willenbrock pie...@pirsoft.dnsalias.org:
Hi Gerald,
Gerald Murray schrieb:
Tested:
LiDE 35: 150,300,600,1200 using usb-1.1.
--snip--
That is probably a calibration problem. There is no easy way to fix
that. What helped Henning was to clean
Hi Gerald,
Gerald Murray schrieb:
Tested:
LiDE 35: 150,300,600,1200 using usb-1.1.
Motor ok. Scans at 150,300 are excellent quality.
At 600, 1200 minor image flaws: there is faint but noticable streaks
down the longest length of the image, from color reception or brightness
not being
Hi,
Parag N() schrieb:
Is that experimental module can be used with HP 2400 scanner also?
It can be used for development and other experimental code. So, yes, the
experimental cvs module can be used for developing support for the HP
2400 scanner. But no, there is no code supporting
Hi List,
as some of you may have noticed, the genesys backend now has the ability
to set a motor power level, leading to much quieter scans in high dpi
modes(if it is implemented for the scanner).
This feature is currently available in the experimental module, as the
settings for this new mode
Laurent Charpentier schrieb:
I would like to submit a patch for the genesys backend (Canon LIDE 50). The
patch adds the threshold feature for black/white mode (in 1.0.17 the threshold
is set to 50% and can't be changed).
The attached patch is relative to sane-backends-1.0.17 (files
Laurent Charpentier schrieb:
Hi Everyone,
I would like to submit a patch for the genesys backend (Canon LIDE 50). The
patch adds the threshold feature for black/white mode (in 1.0.17 the threshold
is set to 50% and can't be changed).
The attached patch is relative to sane-backends-1.0.17
Jeff Shrowder schrieb:
Michael and Pierre,
Looking through the archives I see a number of postings on developing a
driver for the Canon Canoscan LiDE 500F. How far did you get?
I didn't do any further work, apart from those postings. I don't know if
Michael made any progress.
If you are
St?phane VOLTZ schrieb:
I had to put an ifdef WORDS_BIGENDIAN (like for slope tables), so that
my
MD6471 could work again after the endianess changes you done.
To be exact, the code i used for gamma was meant to work for both
endianesses, but does not work for either.. I forgot to
Hi Jon,
Jon Chambers schrieb:
On Tue, 7 Mar 2006, Pierre Willenbrock wrote:
[...] I am planning to add a function that swaps the
bytes in place if needed which should be called on the pixel data.
You may find the byte ordering calls built into the socket library
(htons, htonl, etc) useful
Hi Luke,
Luke Campagnola schrieb:
First I want to thank everybody for their great work on the genesys backend,
we really appreciate your hard work!
Now the complaining bit. I've been comparing the sane driver to the windows
driver and I've come up with a few notes:
- The windows driver
Hi all,
i am planning to complete the endian conversion code in the genesys backend.
I identified the following fields where endian conversion is neccessary:
Going down to scanner:
* slope tables
* shading tables
* gamma tables
The registers need to be addressed bytewise anyways, so they don't
Hello
Jean-Baka Domelevo-Entfellner schrieb:
Following on my project to include support for the OpticFilm 7200 (by
Plustek) to the genesys backend, I have some questions to the
maintainer(s) of the latter:
1) Are the AFEs taken into account for the moment all made by Wolfson
? The
Jean-Baka Domelevo schrieb:
[...]
Okay, I don't like the question mark after the name of the chip. On
the sane-project webpage listing the unsupported devices, it is said
probably a GL841, based upon a trial by sane-find-scanner, probably.
To make sure, the first thing I did after unpacking my
Jean-Baka Domelevo schrieb:
On 1/28/06, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
gl841 and gl842 are identical from the driver side. The genesys backend
works for my scanner which is a gl842 based Canon LiDE 35.
Hi Pierre,
I've downloaded the genesys files from the CVS
Hi Aaron,
golan...@aol.com schrieb:
After patching the backend and a recompile I get the following when
attempting a 'scanimage image.pnm' :
[more log]
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 131,
index =, len = 2
[sanei_usb] : 06 18
Parag N() schrieb:
Hello Pierre,
On 12/29/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Hello Parag,
[...]
--- 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
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] =
Hi,
golan...@aol.com schrieb:
I made the changes you suggested and troubleshot a few things and got
the scanner to be found as a LiDE 60 with scanimage. I got an invalid
argument error when I tried to do 'scanimage image.pnm'.
Below is a debugging log after I issued 'export
Michael Roitzsch schrieb:
Since the CanoScan LiDE 500F is still unsupported and I consider to buy
such a thing, I would like to now, how much work is still missing on
this. I have some usable programming skills, but I have no experience
in reverse engineering USB protocols, so it would be
Michael Roitzsch schrieb:
I think these are the steps needed for full support:
- acquire logs from windows scans
Would that be possible from Mac OS X, too? I only have an old Win98 and
I am not sure that the scanner will work there.
Win98 should be fine. Thats where my logs are from. I
Hi all,
I moved the genesys backend in experimental cvs to sane-backends cvs
yesterday evening. I tried to send a notification to the list twice, but
haydn didn't want to relay that mail(it didn't relay the commit mails
either). Changes are in ChangeLog.
St?phane VOLTZ schrieb:
I finally
Hi all,
Seems like the mailing system on haydn had an outtime. At least the cvs
commit mails didn't arrive here, and i couldn't send this mail the first
try.
I updated the genesys backend in cvs. It is in sync with experimental
cvs now again.
If you own a genesys based scanner which should be
Hi
Henning Meier-Geinitz schrieb:
On Tue, Dec 06, 2005 at 10:59:51AM +0100, Pierre Willenbrock wrote:
I moved the genesys backend in experimental cvs to sane-backends cvs
yesterday evening. I tried to send a notification to the list twice, but
haydn didn't want to relay that mail(it didn't
Henning Meier-Geinitz schrieb:
I only get backtracking here with high load of the computer. However
I can confirm the horizontal lines. Looks like something connected to
backtracking at 16 bit doesn't fully work yet. I don't have
these lines in 8 bit mode.
Those corrupted horizontal
Hi Pierre,
Do you have genesys in your dll.conf?
To my knowledge sane now uses libusb for usb support, so the scanner
module is not needed.
Regards,
Pierre
Pierre Lambion schrieb:
Hi, I have a cansocan lide35. I use it with a test program written by Pierre
Willenbrock but it seems
Hi,
Henning Meier-Geinitz schrieb:
Hi,
Thanks for all your work!
As far as I know, you use a LiDE 35. So i marked this scanner's
support as good. If you think the level of support is different,
please change it in genesys.desc.
It is working for me in daily use, so good seems to be
Hi,
St?phane VOLTZ schrieb:
Hello,
there are quite some issues with gl646:
- 250, 400 and 500 dpi modes fail with 'invalid argument'.
At least in the log you sent me it fails in gl646_search_start_position,
trying to read the last 64 bytes of a scan. I am not aware of
Cameron Harris schrieb:
On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Does it always stop there? It looks like the usb connection somehow
broke while transfering data. Does the scanner re-register with your
system at the moment the transmission stops? There will be some
Cameron Harris schrieb:
Right.. got a full compressed log, attached it to this message.
Thanks :)
Thanks for the log.
Please try the attached patch.
I don't know if it helps. The backend is trying to read 156 bytes
from the scanner, but libusb does not provide that much. We need to
Cameron Harris schrieb:
On 10/30/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Thanks for the log.
Please try the attached patch.
I don't know if it helps. The backend is trying to read 156 bytes
from the scanner, but libusb does not provide that much. We need to find
out
Cameron Harris schrieb:
Fantastic! I just messed around with the lock button on the bottom of
the scanner, locking and unlocking a few times, then tilting it to the
side a bit.. and it works now!
All I can guess is that someone picked up the scanner when it was
unlocked and I wasn't looking
John William Dalton schrieb:
I've managed to get sane/xsane working with my Canon LiDE 60.
I did this by compiling the experimental CVS genesys
backend (including Pierre's recent support for the LiDE35/40/50).
Before compilation I replaced every instance of the LiDE 35
USB ID (0x2213) with
Ashley Caire schrieb:
I'm trying to test my Canon LIDE50 scanner with the latest CVS, but all
the scanner does is flash pink, then red, then yellow quickly, then a
continuous white.. Is there anything obvious i'm doing wrong?
If you got this with the code from experimental cvs i am interested
Brian J Densmore schrieb:
Pierre Willenbrock wrote:
I did a major restructuring on the gl841 part. You may want to take a
look at that.
Are you referring to the patch you created? I've already applied that.
Just wanted to make sure you are not working with old code ;-).
Essentially
Pierre Willenbrock schrieb:
Hi Philip,
The LiDE60 scanner probably is a LiDE35/40/50 with a modified case.
There may be some technical differences, which would require changes in
the backend, but i can't tell without any reports.
Regards,
Pierre
I do have a report that the LiDE60
Hi
Currently we have a working backend for either gl646 or gl841. The code
in experimental cvs only allows scans on gl646 at low resolutions, but
apart from that is ready for the rest of gl841 support, without breaking
gl646 support even more. But we certainly don't want to include code
which
Hi Philip,
The LiDE60 scanner probably is a LiDE35/40/50 with a modified case.
There may be some technical differences, which would require changes in
the backend, but i can't tell without any reports.
Regards,
Pierre
=255
Mathias Lang schrieb:
Hi,
Pierre Willenbrock wrote:
It is now ready to be extensively tested.
i don't know if this is my lack of skills to set up the backend properly
(tested it on my two boxes), but i get device I/O's with the genesys-cvs
backend patched with the patch from
Hi
I spent some time on fixing the last few bugs in the gl841 part known to
me and preparing the backend for the final inclusion of gl841 support
needed for my scanner.
The attached patch primarily adds yet another shading calibration
method, using the black and white strips at the top of the
Hi
Daniel Franke schrieb:
On Sunday 11 September 2005 18:29, I wrote:
Is currently anyone working on this specific driver? If not, is there any
code to pick up? Any docs from HP someone already acquired? I would also
appriciate some hints/documentation about GL841/GL646 (which seems to be
This one should have been sent to the list. I double-checked the From:
field, but didn't realize i just removed the wrong To: field.
(sent on 2005-09-07 to St?phane VOLTZ stef...@modulonet.fr)
Hi
St?phane VOLTZ schrieb:
Hello,
it looks genesys_reorder_components_cis_8 and
Hi
As you might guess, i'm having another patch ready for review.
St?phane VOLTZ schrieb:
Hello,
I have applied your slope table patch in the experimental/genesys. I
tested
it wtih my MD6571 and everything I tried worked fine.
The 'stagger' pattern is indeed :
Jens Luedicke schrieb:
Hiya...
I get the following compiler errors when trying to build the
genesys backend:
...
genesys.c:2144: error: structure has no member named `bulk_write_register'
genesys.c:2191: error: structure has no member named `bulk_write_register'
genesys.c: In function
Jens Luedicke schrieb:
St?phane VOLTZ wrote:
I checked the geneys_low.h that I forgot this morning.
btw, the current changes don't work at all for me (LiDE 50):
scanimage: open of device genesys:libusb:001:006 failed: Error during
device I/O
I prefer to not change too much
Hi
St?phane VOLTZ schrieb:
Le Lundi 29 Ao?t 2005 20:01, Pierre Willenbrock a ?crit :
...
Next i'd like to rewrite genesys_read_ordered_data to be more
maintainable and able to convert the cis style planar data to chunky
data.
It is indeed a rather complicated function. Data
Hi
As promised
Pierre Willenbrock schrieb:
Next i will implement the slope table generation in the way St?phane
suggested.
i am sending the result of this work. I introduced a new flag
GENESYS_FLAG_ALT_SLOPE_CREATE to indicate that the alternate slope
creation functions should be used
Hi
The attached patch against experimental cvs leads to a mostly working
Canon LiDE 35. There is support for color and grey scans at arbitrary
resolutions. There are some shortcomings in the code, but those are
mostly structural.
Currently known bugs:
1 You need to replug the scanner every
Hi
stef schrieb:
On Sat, Aug 27, 2005 at 12:43:38AM +0200, Pierre Willenbrock wrote:
...
Currently known bugs:
1 You need to replug the scanner every other retry
2 Sometimes the calibration process hangs
...
Hello,
I got the same 1 an 2 issue. I don't know if you
Jens Luedicke schrieb:
On 8/15/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Hi
[proposed changes to slope generation]
I attached the code i am using.
Could you create a patch for use with current CVS?
I tried to apply your code, but some things don't work out for me
Hi
The canon lide 35 is now scanning in color at any resolution. No
calibration yet. I'd like the calibration code to use a more generic
interface to the scanning logic before. But that will have to wait.
This time i want to propose a new mechanism for generating slope tables
in the genesys
Hi,
This is the newest and hopefully final version of my genesys_com patch.
This patch makes the bulk transfer functions chip specific and completes
the gl841 side with a gamma bulk transfer function. It also moves the
last two occurances of send_slope_table inside the chip specific init
St?phane VOLTZ schrieb:
Le Mercredi 3 Ao?t 2005 16:35, Pierre Willenbrock a ?crit :
So i conclude that the gl646 expects the shortest pixeltime first, while
the gl841 wants the longest pixeltime first.
Is this correct or am i doing something wrong?
GL646 behaves like GL841 in this case
Pierre Willenbrock schrieb:
Bulk access differs in all cases between gl646 and gl841.
genesys_com.diff.gz moves the bulk functions into the chip specific
source files. I also moved the last two occurences of send_slope_table
in genesys.c to genesys_gl646.c and genesys_gl841.c, since the gl841
Hi
Yesterday i got gl841_slow_back_home to work correctly.
I noticed that sanei_genesys_create_slope_tables generates a slope table
which starts at about 100 and ends at 2100. This table is unusable (at
least with my canon lide 35). The windows driver sends a linear table
starting with a value
I did some minimal work on the driver recently. My goal was to get the
scanner(canon lide35) to physically do something.
The gl841 does not understand the bulk register transfer used for gl646,
so i modified sanei_genesys_bulk_write_register to do single register
writes. After fixing
101 - 182 of 182 matches
Mail list logo
