Jane85 schrieb:
>
>
>
> Pierre Willenbrock-2 wrote:
>>
>>
>> Okay, i am officially out of ideas. To me, this looks very much like
>> defective hardware.
>>
>> Does this scanner work with any other systems, for example with the
>&g
Jane85 schrieb:
>
>
> Pierre Willenbrock-2 wrote:
>>
>>
>> Oops, patch was wrong, used incorrect register. Please try the attached
>> patch(reverting the original one before). (Or manually replace the 6D/6d
>> by 6C/6c in the affected code.)
>>
>
Jane85 schrieb:
>
>
>
> Pierre Willenbrock-2 wrote:
>>
>>
>> Okay, then please try the attached patch. If that works, try to reduce
>> the time in the usleep until it breaks again.
>>
>> Regards,
>> Pierre
>>
>>
>
> I
Jane85 schrieb:
>
> There are two usb ports on my computer. I tried both ports, also I tried
> another usb cable. If it is necessary I can attach the logs. But the new
> logs are identical with the old logs.
>
> I able to recompile sane-backends with a patch.
>
> Regards,
> Jane.
Okay, the
This first puts a 27 Ohm resistor between USB power and non-gl841
electronics before actually directly connecting.
---
backend/genesys_gl841.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/backend/genesys_gl841.c b/backend/genesys_gl841.c
index 0a614fa..4a4fabf 1
This first puts a 27 Ohm resistor between USB power and non-gl841
electronics before actually directly connecting.
---
backend/genesys_gl841.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/backend/genesys_gl841.c b/backend/genesys_gl841.c
index 0a614fa..4a4fabf 1
Jane85 schrieb:
>
> I used 'export SANE_DEBUG_SANEI_USB=255' then retried 'scanimage ?d genesys >
> picture1.pnm'.
> New log is attached. The file with the result of 'dmesg' is attached also.
>
> Regards,
> Jane.
>
> http://old.nabble.com/file/p29211849/xeroxTS100.sanei.log
> xeroxTS100.sa
CCing sane-devel, as i don't really know the policy for the last item.
Gernot Hassenpflug schrieb:
> Hello Pierre,
>
> I attach the diff for the genesys doc/description/genesys.desc where I
> added the LiDE40 as "good" (change from "untested").
When sending patches, please use git format-patch,
m. allan noah schrieb:
> On Mon, Apr 19, 2010 at 10:33 AM, Fabian Eichst?dt
> wrote:
>> Hi all!
>> We recently aquired a Canon DR-2020U scanner and I tried to test it
>> with a recent sane git-snapshot. It compiled without problems and
>> I tried to use it with the canon_dr backend. This failed.
stef schrieb:
> Le mardi 2 mars 2010 16:40:21 Chris Berry, vous avez ?crit :
>> Hey guys, I resolved the issue I was having with the dark_shading
>> calibration. The lamp was turning off fine but the | REG03_LAMPPWR in
>> gl842_begin_scan was turning the light back on for the scan :/ . Having
>> re
Gernot Hassenpflug schrieb:
> On Thu, Feb 25, 2010 at 7:05 PM, Pierre Willenbrock
> wrote:
>> Gernot Hassenpflug schrieb:
>>> On Thu, Feb 25, 2010 at 1:05 AM, m. allan noah
>>> wrote:
>>> /../
>>> Are endpoints apart from the default 0x000
Gernot Hassenpflug schrieb:
> On Thu, Feb 25, 2010 at 1:05 AM, m. allan noah wrote:
>> Attached is a copy of a script I wrote that clears up these verbose
>> logs. I don't know if it is the most recent version, I cannot reach my
>> development machine, and i just found this copy with google :)
>
Chris Berry schrieb:
> On 02/24/2010 10:33 AM, Pierre Willenbrock wrote:
>> stef schrieb:
>>
>>> Le mercredi 24 f?vrier 2010 03:00:16 Chris Berry, vous avez ?crit :
>>>
>>>> Hey Stef,
>>>>
>>>> I think I have sorted out
stef schrieb:
> Le mercredi 24 f?vrier 2010 03:00:16 Chris Berry, vous avez ?crit :
>> Hey Stef,
>>
>> I think I have sorted out the white shading data but the black is still
>> a mystery. I have uploaded some files to the project site (here
>> http://sites.google.com/site/bez625/updates-1/update24
chrome://messenger/locale/messengercompose/composeMsgs.properties:
> Hello Stef,
>
> Thank you for your prompt reply.
>
> Please find in the attachment the requested debug.log file.
>
> Thank you in advance for your help, have a good day.
Hi Georg,
thanks for the log, this is a known and fixed
Hi Sivananda,
sivananda schrieb:
> Dear Mr. Pierre,
>
> I have problem with CanoScan LiDE 100 to work with ubuntu. The reason
> behind my worry is I have purchased these scanners( more than 5000
> pieces) for school at very remote places but found not working. I got
> your references from the com
Ozan ?a?layan schrieb:
> Hi,
>
> I've just noticed that my Canon LiDE 50 is broken with sane-backends 1.0.20
> (1.0.19 was OK). I've bisected it to:
>
Thanks for bisecting, but this bug should be fixed in git master. See
bug #311691.
Regards,
Pierre
Julien BLACHE schrieb:
> Ilia Sotnikov wrote:
>
> Hi,
>
>> ** Updating scanners lists
>> From git://git.debian.org/sane/sane-backends
>>764aa7c..e232f54 master -> origin/master
>> Updating 354b9a5..e232f54
>> backend/.gitignore: needs update
>> frontend/.gitignore: needs update
>> inclu
Charles Dahl schrieb:
> Hi,
>
> Just a quick line to see if anyone knows when this will be
> accomplished? It seems this has been going on for quite a while.
>
> CanoScan 8600FUSB 0x04a9/0x2229 Unsupported GL841 based, to
> be
> added to genesys backend
>
Hi Charles,
to my k
Hi Jack,
Jack McGill schrieb:
> To list and Pierre,
>
> I recently received a Visioneer XP100, rev 3, usb vid x04a7 pid
> 0x049b, which has a GL842 chip inside. The model number on the
> bottom of the scanner is 85-0110-200. This scanner works very well
> using the Visioneer Roadwarrior settin
Hi,
i added support for Ambir(Syscan) DocketPort 665 and Visioneer
Roadwarrior, thanks to the hardware donation of Jack McGill. Those two
use the same mainboard, only differently sized sensors. There may be
other models using this mainboard, and adding support should be simple.
Attached is a photo
Hello,
stef schrieb:
> I'm answering you through the mailing list since my private mail has
> been
> bounced back by some blacklisting system.
Sorry about that, looks like that blacklist is collecting more
legitimate smtp-servers than it used to. I removed it from my
mailserver-config.
>
y, if you agree.
No VoIP, and i usually don't use IRC, but i can dust my irc client off,
if needed.
Regards,
Pierre
>
>
> Am Sonntag 08 Februar 2009 16:49:12 schrieb Pierre Willenbrock:
>> Roland Graf schrieb:
>>> Hallo Pierre,
>>>
>>> the te
Hello,
stef schrieb:
> the genesys backend as been updated. Thanks to an hardware donation of
> Jack
> McGill, there is now support for the sheet-fed Visioneer Strobe XP200. It can
> scan at 75, 100, 200, 300 and 600 dpi in color or gray and at 8 or 16 bits.
> Scans are uncalibrated, ie
Roland Graf schrieb:
> Hallo Pierre,
>
> the testprogram gives me only an:
>
> roland roland # /home/roland/Doku/G4010/testprog
> Fatal: Device not found!
> roland roland #
>
> With #lsusb I can see the scanner. I
> Best regards
>
> Roland
>
Hello Roland,
either my guess for your device-id w
robert w hall schrieb:
> In message <498B15E0.9070805 at pirsoft.dnsalias.org>, Pierre Willenbrock
> writes
>
>> it decodes fine, but i need to find some time to put the test program
>> together. My scripts decode the usbsniff into some pseudo c-code, that
>> nee
Roland Graf schrieb:
> Hallo Pierre,
>
> was it possible to decode my log?
>
> Thanks
>
> Roland
>
Hi Roland,
it decodes fine, but i need to find some time to put the test program
together. My scripts decode the usbsniff into some pseudo c-code, that
needs to be cleaned/modified to work.
Reg
Yes, feeder jammed is a bad error message. I see we have
SANE_STATUS_HW_LOCKED now -- that is probably a better error code. Fixed
in cvs.
Regards,
Pierre
Tobias Preclik schrieb:
> Thanks for sorting this out. Didn't know the device has a lock switch
> and was confused by the "document feeder ja
Roland Graf schrieb:
> Am Samstag, 17. Januar 2009 15:41:51 schrieben Sie:
>> Roland Graf schrieb:
>>> Hello Pierre,
>>>
>>> I'm the owner of an HP G4010, and I would collaborate with you to insert
>>> this scanner in the genesys backend.
>>>
>>> I read in the mailing lists that it is not absolutel
Dhi Aurrahman schrieb:
> Dear All!
>
> I have CanonScan LiDE 50 with me (working well with SANE genesys backend),
> but I need to have a buttons-daemon for it.
> Anyone could help me how to do it? I think the first step is to snoop the
> USB message sent by the button when it is pressed.
> If you
Hi list,
i tried to build sane with different source and build directories and
ended up needing the attached patch to tools/Makefile.in. I am not sure
if i got the build-directory creation right, but it works for different
source/build directories as well as when they are identical. If no one
obje
m. allan noah schrieb:
> On Sat, Jan 10, 2009 at 2:55 PM, Pierre Willenbrock
> wrote:
>> m. allan noah schrieb:
>>> On Sat, Jan 10, 2009 at 1:11 PM, Pierre Willenbrock
>>> wrote:
>>>> m. allan noah schrieb:
>>>>> On Fri
m. allan noah schrieb:
> On Sat, Jan 10, 2009 at 1:11 PM, Pierre Willenbrock
> wrote:
>> m. allan noah schrieb:
>>> On Fri, Jan 9, 2009 at 5:02 PM, Pierre Willenbrock
>>> wrote:
>> [...]
>>>> Another question: Is it okay to only look at the hardwa
m. allan noah schrieb:
> On Fri, Jan 9, 2009 at 5:02 PM, Pierre Willenbrock
> wrote:
[...]
>
>> Another question: Is it okay to only look at the hardware state if the
>> frontend asks for the state of the option? That way shorter presses can
>> be lost, if the frontend
m. allan noah schrieb:
> On Wed, Jan 7, 2009 at 1:09 PM, Pierre Willenbrock
> wrote:
[...]
>>
>> I have no experience with the sane interface itself, so comments/patches
>> are gladly accepted.
>
> We have settled on exposing buttons via options with:
>
Dhi Aurrahman schrieb:
> Dear All!
>
> I have CanonScan LiDE 50 with me (working well with SANE genesys backend),
> but I need to have a buttons-daemon for it.
> Anyone could help me how to do it? I think the first step is to snoop the
> USB message sent by the button when it is pressed.
> If you
Tom Brush schrieb:
> For a scanner-camera project featured in Make magazine, (
> http://makezine.com/14/scannercamera/ ) the author uses SANE to bypass the
> calibration step, because it would fail after his physical modifications to
> the sensor. The model he uses is a Canon CanoScan LiDE 20. Hi
guillaume.gastebois at free.fr schrieb:
> Hello,
>
> I'm back with my LiDE 90. No more significant result since month. I don't
> know where to find.
> Just a little question. I see in windows snoop that inversion bit is set in
> frontend, not in sane.
> Is it possible that this inversion has an
stef schrieb:
> Hello Pierre,
>
> I am currently studying how to add support for the HP2400/G2410 to the
> gl646
> part of the genesys backend. I am currently trying to figure out how to fill
> the values for the motor struct in genesys_devices. How did you find the
> current value
guillaume.gastebois at free.fr schrieb:
> Hello,
>
> It seems that in Windows snoop calibration of LiDE 90 is done with
> half CCD even if scanning is in full sensor resolution.
> Is it so in sane ?
>
> If not, is it usefull to implement it ? Where to do that ?
To be on the safe side, all calib
Hi Keith,
Vital Mission Software schrieb:
> I would like to see if I can get my LiDE 80 to work. It is marked as
> unsupported since 2007-01-28. It appears in the udev/libsane.rules, but
> not in genesys_devices.c. However, that does include support for LiDE
> up to 60 and I note that the table
Hi,
guillaume.gastebois at free.fr schrieb:
> Hello,
> Thank you for answer Pierre.
> Some questions again !
>
>> Hi Guillaume,
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> I'm back with my LiDE 90 !
>>>
>>> I see in my windows logs the following sequence for gpios (reg 0x6C) :
>>> 02
>>> 1
Hi Guillaume,
Guillaume Gastebois schrieb:
> Hello,
>
> I'm back with my LiDE 90 !
>
> I see in my windows logs the following sequence for gpios (reg 0x6C) :
> 02
> 12
> 0e
> 1a
> 0a
> 0e/3e (3e for half ccd log) (seems to be scanning moment)
> 0e
> 0a
> 0e/3e (3e for half ccd log)
> 02
>
> With
Rene Rebe schrieb:
> litlle girl wrote:
>> AFE settings looks more stable:
>>
>> grep "\[gt68xx\] afe" ./*
>> ./color-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04
>> ./color-2.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04
>> ./color-3.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04
>> ./gray-1.
Hi David,
David Lochrin schrieb:
> Hi,
>
>I'm trying to decide which current Canon flat-bed scanner to
>run on SuSE 10.1. It seems Canon may have rationalised the LiDE
>20, 30, & 60 by rebadging the "LiDE 60" as "LiDE 25" with minor
>mechanical changes, and removed the old
Guillaume Gastebois schrieb:
> Hello,
>
> No progress on 2400dpi. DPIHW is 2400 and dpiset 600 for a 300dpi scan.
> Don't know where to look yet for that problem !
I'd try to get a log from a 2400dpi scan from windows and compare.
> about byte nibbles modifying reg_0x79 from 0x3f to 0x3e (very f
Guillaume Gastebois schrieb:
> Hello,
>
> In genesys backend, we can find :
>
> typedef struct
> {
>u_int8_t reg[4];
>u_int8_t sign[3];
>u_int8_t offset[3];
>u_int8_t gain[3];
>u_int8_t reg2[3];
> } Genesys_Frontend;
>
>
> but in WM8199 regs don't have the same name.
> For m
Guillaume Gastebois schrieb:
> Hello,
>
> Is there a possibility to determine a maximum of parameter like :
>
> typedef struct
> {
> int optical_res; (OK, for me 2400)
> int black_pixels;(don't know how to determine)
> int dummy_pixel; (content of 0x34 ?)
Guillaume Gastebois schrieb:
> Hello,
>
> I remember that LiDE 90 is a 2400DPI scanner. And I did nothing in code to
> port
> that. I backend ready for 2400dpi (I think so regarding portion of code) ?
I am not sure, as there could not happen any testing. But in theory, it
should work. In the fu
Hi,
Guillaume Gastebois schrieb:
> Hello,
>
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> Me again !
>>>
>>> I'm trying to find what are GPIO14,13,12 and 11 for.
>>>
>>> I find GPIO11=home switch and must be 0.
>>> I thought I found GPIO14 was half CCD but by adding :
>>> /* gpio part. here:
Guillaume Gastebois schrieb:
> Hello,
>
> Me again !
>
> I'm trying to find what are GPIO14,13,12 and 11 for.
>
> I find GPIO11=home switch and must be 0.
> I thought I found GPIO14 was half CCD but by adding :
> /* gpio part. here: for canon lide 90 */
> if (dev->model->gpo_type == GPO_CANONLID
Guillaume Gastebois schrieb:
> Hello,
>
> Me again !
>
> I'm trying to find what are GPIO14,13,12 and 11 for.
>
> I find GPIO11=home switch and must be 0.
> I thought I found GPIO14 was half CCD but by adding :
> /* gpio part. here: for canon lide 90 */
> if (dev->model->gpo_type == GPO_CANONLID
Guillaume Gastebois schrieb:
> Hello,
>
> I see in genesys_gl841.c line 2503 :
>
> /* gpio part. here: for canon lide 35 */
>
> r = sanei_genesys_get_address (reg, 0x6c);
> if (half_ccd)
> r->value &= ~0x80;
> else
> r->value |= 0x80;
>
> Does it mean that for LiDE 35 GP
Pierre Willenbrock schrieb:
>
> Now for the real reason i am answering: I did play around with my
> scanner, trying to get the shading calibration to work only on the white
> strip. The trick was to do a real scan over the white strip, not just
> sampling a single line over
Hi Guillaume,
Sorry for not answering sooner.
Guillaume Gastebois schrieb:
> Hello,
>
> Selon Pierre Willenbrock :
>> Guillaume Gastebois schrieb:
>>> > Hello,
>>> > > Yesterday I added CCD_CANONLIDE90 in genesys.c. I did two
>>> successi
Guillaume Gastebois schrieb:
> Hello,
>
> Yesterday I added CCD_CANONLIDE90 in genesys.c. I did two successive scans
> (result on http://ggastebois.free.fr/lide90_snoop/25_test1.zip).
> The first one gives a bright image (1_test1.txt), the second a dark image
> (3_test1.txt). Which log seeems to b
Guillaume Gastebois schrieb:
> Hello,
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>> > Hello,
>> >
>> > You can find attached a patch which works like my original code (with
>> > different contrast and calibration betw
Ralf Haueisen schrieb:
> I tried again, an now not even pressing a button help.
> What code do you need, and how can i get it?
>
Please try the patch from Guillaume Gastebois.
Regards,
Pierre
Guillaume Gastebois schrieb:
> Hello,
>
> You can find attached a patch which works like my original code (with
> different contrast and calibration between 2 scans...).
>
> I removed controversed comments (sorry).
Thanks for the patch. I see that you added DAC_CANONLIDE90 at one place.
This
Guillaume Gastebois schrieb:
> Hello,
>
>
> > > Volker Grabsch schrieb:
> > > > > On Wed, Mar 19, 2008 at 03:24:45PM +0100, Pierre Willenbrock wrote:
> >> > > >> + ,
> >> > > >> + /* CANONLIDE90 */
> >> &
Ralf Haueisen schrieb:
> Hi.
>
> I just downloaded the current version from the CVS, an applied the patches.
> But sane does not find the scanner.
> sane-find-scanner is ok, but scanimage not. in /etc/sane.d/genesys.conf I
> have added the ID of the scanner.
> I tried everything as root, so acce
Volker Grabsch schrieb:
> On Wed, Mar 19, 2008 at 03:24:45PM +0100, Pierre Willenbrock wrote:
>> + ,
>> + /* CANONLIDE90 */
>> + {
>> +/*
>> +00 :
>> +02 : image ?? la con et inverse video
>> +0a : image ?? la con et inverse video et moteur ne
Hi Guillaume,
Pierre Willenbrock schrieb:
> Guillaume Gastebois schrieb:
>> Pierre Willenbrock schrieb:
>>> But this seems to be basically working. Please send your changes leading
>>> to a usable scan, so i can integrate them.
>> For now, my code is ugly. I on
Hi,
Guillaume Gastebois schrieb:
> Hello,
>
>
>> What about only setting register 0x7f? that one should do something
>> without needing to setup reg 0x1a.
>
> Not better I think. Result :
> http://ggastebois.free.fr/lide90_snoop/10_test0.tar
I forgot that there is a switch-on-bit for that, to
ase send your changes leading
to a usable scan, so i can integrate them.
Regards,
Pierre
> Regards
> Guillaume
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> I modified these registers. But the scanner locks writ
I'd play around with different sets of
registers and see if they work. But i guess, register 0x1a is a key to
get the rest working.
> I will be long for next answer as I take one week holidays !
I hope you had a nice week holidays.
Regards,
Pierre
> regards
> Guillaume
>
>
Gernot Hassenpflug schrieb:
> Hello all,
>
> Ive been looking through the archives of this list, and especially the
> LiDE90 discussion, on the recommendation of Stef.
> The last message was apparently on 21 Feb:
>
> http://lists.alioth.debian.org/pipermail/sane-devel/2008-February/021184.html
>
Pierre Willenbrock schrieb:
> Hi list,
>
> anybody knows if/where to find $subject on the web? Something that
> describes some details of motor control, lamp control and analog/digital
> postprocessing, as well as the general scanning operating. Just enough
> for a developer
>
> Further, we need to figure out a way to get the LEDs go completely dark.
> 0x101 is just about half of 675. I will experiment a bit with my
> scanner, to find out if the gl842 can do that.
>
cvs now gives completely dark LEDs when needed.
Regards,
Pierre
Hi,
Guillaume Gastebois schrieb:
> Hello,
>
>> So, we need to check what parts of the clocking we need to setup
>> differently.
>>
>> Candidates:
>>
>> reg sane windows
>> 0x1a 0x00 0x24 enable clock 3,4 manual output, invert clock 4
>> 0x1d 0x04 0x02 just a smaller toggle "shoulde
c, gl841_set_lamp_power.
Oh, and please update from cvs again. A small mistake in
gl841_bulk_write_registers made the debug register dumps useless.
Regards,
Pierre
> Pierre Willenbrock a ?crit :
>> Pierre Willenbrock schrieb:
>>> Hi,
>>>
>>> Guillaume Gastebois
Guillaume Gastebois schrieb:
> Hello,
>
> Selon Pierre Willenbrock :
>
>> Hi,
>>
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> So, what's the next step ? Re-enabling shading ?
>> Yes, but only after the shading-calibr
Pierre Willenbrock schrieb:
> Hi,
>
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> So, what's the next step ? Re-enabling shading ?
>
> Yes, but only after the shading-calibration is able to get black level
> information.(This really needs a better api.
et1_0.pnm is only black).
The image should show a fuzzy vertical and horizontal bar, near
top/left. Currently, the horizontal bar is more a line, the vertical bar
is correct(it shows the relationship between the low byte of one pixel
and the high byte of the _next_ pixel).
> Regards
> Guillaume
idn't realize until just now. I
missed that the calibration dump images are really grayscale images,
although stored in color pnms. 1 pixel in image is 3 pixels for the
calibration...
I hope this fixes that part of the calibration.
Regards,
Pierre
> Regards
> Guillaume
>
&
em(misplaced
brackets perhaps? copy+pasto when calculating the second set?), or send
the source.
Regards,
Pierre
> Regards
> Guillaume
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> OK, I'll try this tonight.
rre
>
> Regards
> Guillaume
>
> Selon Pierre Willenbrock :
>
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> I made two tests today :
>>>
>>> test 1 : too bright/too dard = 10/65525 WITH flag :
>>> SCAN_FLAG_DISABLE_LAMP.
Guillaume Gastebois schrieb:
> Hello,
>
> I made two tests today :
>
> test 1 : too bright/too dard = 10/65525 WITH flag :
> SCAN_FLAG_DISABLE_LAMP. Result can bee found on :
> http://ggastebois.free.fr/lide90_snoop/18_test1.tar
>
> test 2 : too bright/too dard = 10/65525 WITHOUT flag :
> SCA
Guillaume Gastebois schrieb:
> Hello,
>
> I try both {0x00, 0x3f, 0x03, 0x26}, and {0x00, 0x3f, 0x00, 0x26},
> you can find result under :
> http://ggastebois.free.fr/lide90_snoop/17_test1.tar
> and http://ggastebois.free.fr/lide90_snoop/17_test2.tar
Looks a lot better. The offset*.pnm actually s
Guillaume Gastebois schrieb:
> Hello,
>
> You can find the result of this test here :
>
> http://ggastebois.free.fr/lide90_snoop/no_shading_2bright_2dark.tar
>
> The calibration is about 25s long.
> Resulting image is bad (as befor).
>
Please try with bit 4+5 of frontend setup register 1 set t
Vidar S?terb? schrieb:
> Hi,
>
> FYI, I was googling for information on the GL646 (I have a HP Scanjet
> 2400) when I came across this datasheet:
> http://www.ic-on-line.cn/IOL_gl646/PdfView/833184.htm
>
Another source for that datasheet is probably
http://www.genesyslogic.com/_en/product_01_1.p
Pierre Willenbrock schrieb:
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> You can find all of that on :
>> http://ggastebois.free.fr/lide90_snoop/no_shading.tar
>>
>> What seems strange in calibration ?
>>
>
> The minimum/maximum values retr
Guillaume Gastebois schrieb:
> Hello,
>
> You can find all of that on :
> http://ggastebois.free.fr/lide90_snoop/no_shading.tar
>
> What seems strange in calibration ?
>
The minimum/maximum values retrieved from the scans do not scale with
the offset values, but in a rather random manner. The
Guillaume Gastebois schrieb:
> Hello,
>
> So. I tryed your patch with and without shading calibration :
>
> with shading : same as bevor but calibration is now 4s long (see
> http://ggastebois.free.fr/lide90_snoop/no_shading.jpg and
> http://ggastebois.free.fr/lide90_snoop/no_shading.txt)
>
>
Stefan Lucke schrieb:
> On Monday 11 February 2008, Pierre Willenbrock wrote:
>> Reinhard Biegel schrieb:
>>> Am Monday, 11. February 2008 schrieb Stefan Lucke:
>
>>>> At that moment, I guess you'll see messages like:
>>>>new high speed USB d
Guillaume Gastebois schrieb:
> Hello,
>
> OK, I'll try it tonight.
> How do I cleanly remove shading_calibration ?
The code for the actual calibration is in genesys.c, line 3362:
/* shading calibration */
to line 3414, before
/* send gamma tables if needed */
>
> Regards
> Guillaume
>
Pierre Willenbrock schrieb:
> Stefan Lucke schrieb:
>> Hi,
>> I guess there are 3 possibilities for infinite loops.
>> Attached patch fixes this and adjusts loop threshold
>> to given comments..
>>
>
> Thanks for spotting these.
>
> We have ne
Pierre Willenbrock schrieb:
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> I see that reg[2] was like 0x07. So INVOP was still set !!!
>> I comment out offset_calibration in genesys_flatbed_calibration, set
>> reg[2] to 0x03, and I get a black image with a gra
Guillaume Gastebois schrieb:
> Hello,
>
> I see that reg[2] was like 0x07. So INVOP was still set !!!
> I comment out offset_calibration in genesys_flatbed_calibration, set
> reg[2] to 0x03, and I get a black image with a gray vertical line in the
> middle !!!
> I try to reenable offset_calibrat
Guillaume Gastebois schrieb:
> Hello,
>
> I modified registers 10-1d with :
>
> {0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00, 0xff, 0x24, 0x00,
> 0x00, 0x04},
>
> and now the led is really white (red green and blue by moving eyes).
>
> Led calibration seems to be good.
>
> But calibr
Gerhard Jaeger schrieb:
> On Tuesday 12 February 2008 03:41:49 Reinhard Biegel wrote:
>> On Monday, 11. February 2008, Pierre Willenbrock wrote:
>>> Did someone post the bcdDevice value of a LiDE 80? GL841 goes up to
>>> 3.0.5, as someone said, and GL842 begins with
Reinhard Biegel schrieb:
> Am Monday, 11. February 2008 schrieb Stefan Lucke:
>>> ...
>>> [genesys_gl841] reg[0x6b] = 0x02
>>> [genesys_gl841] reg[0x6e] = 0x6d
>>> [genesys_gl841] gl841_bulk_write_register: failed while writing command:
>>> Invalid argument
>>> scanimage: open of device gen
Hi list,
anybody knows if/where to find $subject on the web? Something that
describes some details of motor control, lamp control and analog/digital
postprocessing, as well as the general scanning operating. Just enough
for a developer of a driver for a dumb chip(like the genesys chips).
If noone
Hi Guillaume,
Guillaume Gastebois schrieb:
> Hello,
>
> Why calibration is so long (~50/60s) ?
It is probably failing. Should take about 3-5 seconds. Look at the logs,
the calculated averages and calibration are dumped there.
> What are /* Start of white strip in mm (y) */ and /* Start of black
Guillaume Gastebois schrieb:
> Hello,
>
> I need a little bit more informations befor testing (sorry for my poor
> knowledge
> in scanner)
>
> Selon Pierre Willenbrock :
>
>> I don't know why the image colors are reversed, but it may be worth
>> trying
Stefan Lucke schrieb:
> Hi,
> I guess there are 3 possibilities for infinite loops.
> Attached patch fixes this and adjusts loop threshold
> to given comments..
>
Thanks for spotting these.
We have never had a problem with those loops, but it is certainly a good
idea to have the code working as
Guillaume Gastebois schrieb:
> Hello,
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> It's a little bit better with these values.
>>> In Genesys_Sensor I have :
>>> regs_0x08_0x0b : {0x00, 0x2
Stefan Lucke schrieb:
> On Wednesday 06 February 2008, Pierre Willenbrock wrote:
>> Hi Stefan,
>>
>> (more text inline)
>>
>> Stefan Lucke schrieb:
>>> On Tuesday 05 February 2008, Stefan Lucke wrote:
>>>> Hi,
>>>>
>>
>
> Regards
> Guillaume
>
> P.S : attached a sample image with my values.
Regarding the image: is this with x|y_offset == 0? and are the
horizontal bright lines original?
Regards,
Pierre
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>>> OK, bu
Hi Stefan,
(more text inline)
Stefan Lucke schrieb:
> On Tuesday 05 February 2008, Stefan Lucke wrote:
>> Hi,
>>
>> I've seen there is some progress on lide 90 and I want to step in and
>> like to ask if there could be done something for my LiDE 80 too.
>> I cloned the canon_lide_60_model entry
>
1 - 100 of 199 matches
Mail list logo
