[sane-devel] Canon LiDE 90

2008-03-04 Thread Guillaume Gastebois
Hello,

I'm back.

Today I made two tests : one with un commenting line 1159 and adding 
regs 0x71, 0x72, 0x73, 0x75, 0x76, 0x79, 0x7c, 0x7d, 0x7f in 
gl841_init_registers.
Result is a totally black image 
(http://ggastebois.free.fr/lide90_snoop/04_test1.tar).

The other is with un commenting line 1159 and without adding regs 0x71, 
0x72, 0x73, 0x75, 0x76, 0x79, 0x7c, 0x7d, 0x7f in gl841_init_registers.
Result is a totally black image too 
(http://ggastebois.free.fr/lide90_snoop/04_test2.tar).

Regards
Guillaume

Pierre Willenbrock a ?crit :
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> I modified these registers. But the scanner locks writting continiously :
>> "[genesys] sanei_genesys_read_register (0x41, 0xf4) completed".
>>
>> I modified 0x1a=0x24 and 0x1d=0x02 in Genesys_Sensor. In log I see 
>> 0x1d=0x02 but 0x1a=0x00 ??
> 
> For the missing change of 0x1a: The code block for setting this value
> (along with 0x1b..0x1d, which is then hardcoded to 0x02) is commented
> out, genesys_gl841.c:1159. This is probably the case, because they were
> not needed for my specific scanner.
> 
> I cannot explain the lockup. 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
>>
>> Pierre Willenbrock a ?crit :
>>> 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 "shoulder".
> 0x71  0x00  0x05 RS signal seems to be not used.
> 0x72  0x00  0x07 CP signal seems to be not used.
> 0x73  0x00  0x09 CP signal seems to be not used.
> 0x75  0x00  0x01 clock 1 bitmap
> 0x76  0x00  0xff clock 1 bitmap
> 0x79  0x00  0x3f clock 3 bitmap
> 0x7c  0x00  0x1e clock 4 bitmap
> 0x7d  0x00  0x11 change RS on falling edge of system clock, use DLY
> 0x7f  0x00  0x50 delay each of BSMP and VSMP by 8.33ns (DLY)
>
> The clock 1 stuff seems to be not needed, as it is in automatic mode.
> But clock 3/4 look interesting. The delay of BSMP/VSMP may be useful, too.
>
 0x1a was still 0x24. I modified 0x1d which was 0x04 to 0x02. Result is 
 on http://ggastebois.free.fr/lide90_snoop/22_test1.tar.

 I doesn't find where to modify 0x71-0x7f !!!
>>> Add them to gl841_init_registers.
>>>
>> Another thing : I always have a brither vertical line where there is a
>> small black rectangle in the calibration area.
> The small black rectangle is included when acquiring the white level.
> Reduce shading_lines(second to last entry) in Genesys_Model to 250, that
> way it is not seen anymore.
>
 Done, works.

> Oh, and please update from cvs again. A small mistake in
> gl841_bulk_write_registers made the debug register dumps useless.
>
 Done.


 Another thing : when I make several scan with sane backend and sane 
 command line, I have alternatively brite and dark images !!! Why ???
>>> The calibration is probably giving widely differing results with
>>> different starting conditions. It swings between two states. But you
>>> shouldn't see this after the gl842 did its shading correction. Then, the
>>> problem is probably overexposure of the ccd cells. Try reducing the
>>> upper threshold in genesys_gl841.c:4383
>>>
>>>   if (avge > 2000) {
>>>   expr = (expr * 2000) / avge;
>>>   expg = (expg * 2000) / avge;
>>>   expb = (expb * 2000) / avge;
>>>
>>> Reducing the lower threshold may be needed, too. The current values for
>>> your scanner are:
>>> expr: 1235
>>> expg: 1235
>>> expb: 675
>>>
>>> No guarantee that this helps at all.
>>>
 Regards
 Guillaume
>>> 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.
>>>
>>> Regards,
>>>   Pierre
>>>
>>>
> 
> 
> 



[sane-devel] Wired behavior of hp scanjet 6200C

2008-03-04 Thread Tobias Lohner
Hi there,

i've some trouble with my HP ScanJet 6200C which is connected via USB  
to my PC.

First time i run 'sane-find-scanner' it's output is

found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0201 [HP  
ScanJet 6200C]) at libusb:002:003

So i tried to run scanimage without any options (since i've only one  
scanner connected)...:

> scanimage
P4
# SANE data follows
2550 3507
scanimage: sane_read: Error during device I/O

Ok, I/O errors are common these days, so i tried again, but it just  
said 'scanimage: no SANE devices found'. Running sane-find-scanner  
again outputs the following now:

found USB scanner (vendor=0x03f0, product=0x0201) at libusb:002:003

What's gone wrong? I'm running Debian etch with Debian kernel  
2.6.18-6-k7 on AMD with an nVidia MCP51 USB host controller.

dmesg says:

ohci_hcd :00:0b.0: wakeup
usb 2-1: new full speed USB device using ohci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann rqt 128 rq  
6 len 2 ret -110
usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann rqt 128 rq  
6 len 2 ret -110

I'm wondering if that error is sane or kernel-driven since  
sane-find-scanner seems to find the scanner but doesn't recognise the  
driver for it after trying to scan.

Any thoughts?

Tobias

-- 
Remember, gravity is not just a good idea.
It's the law.
And it's not subject to repeal.


-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digitale PGP-Unterschrift
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080304/f7ff813f/attachment.pgp
 


[sane-devel] Wired behavior of hp scanjet 6200C

2008-03-04 Thread m. allan noah
i have a similar 6300C scanner, and have found it to be quite flakey
connected to any nForce usb controller, sometimes works, sometimes
not, but never the same thing two times in a row. These machines seem
to be not-quite usb 1.1 compatible, so i only use mine on scsi.

allan

2008/3/4 Tobias Lohner :
> Hi there,
>
>  i've some trouble with my HP ScanJet 6200C which is connected via USB
>  to my PC.
>
>  First time i run 'sane-find-scanner' it's output is
>
>  found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0201 [HP
>  ScanJet 6200C]) at libusb:002:003
>
>  So i tried to run scanimage without any options (since i've only one
>  scanner connected)...:
>
>  > scanimage
>  P4
>  # SANE data follows
>  2550 3507
>  scanimage: sane_read: Error during device I/O
>
>  Ok, I/O errors are common these days, so i tried again, but it just
>  said 'scanimage: no SANE devices found'. Running sane-find-scanner
>  again outputs the following now:
>
>  found USB scanner (vendor=0x03f0, product=0x0201) at libusb:002:003
>
>  What's gone wrong? I'm running Debian etch with Debian kernel
>  2.6.18-6-k7 on AMD with an nVidia MCP51 USB host controller.
>
>  dmesg says:
>
>  ohci_hcd :00:0b.0: wakeup
>  usb 2-1: new full speed USB device using ohci_hcd and address 3
>  usb 2-1: configuration #1 chosen from 1 choice
>  usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann rqt 128 rq
>  6 len 2 ret -110
>  usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann rqt 128 rq
>  6 len 2 ret -110
>
>  I'm wondering if that error is sane or kernel-driven since
>  sane-find-scanner seems to find the scanner but doesn't recognise the
>  driver for it after trying to scan.
>
>  Any thoughts?
>
>  Tobias
>
>  --
>  Remember, gravity is not just a good idea.
>  It's the law.
>  And it's not subject to repeal.
>
>
>
> --
>  sane-devel mailing list: sane-devel at lists.alioth.debian.org
>  http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>  Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-request at lists.alioth.debian.org
>



-- 
"The truth is an offense, but not a sin"



[sane-devel] Formulardaten

2008-03-04 Thread cgi-mai...@kundenserver.de


===
== Neuer Eintrag
===

  
---
-- Formular: 'adddev'
---

1. Your email address:
   'mssa at yahoo.com'
2. Manufacturer (e.g. "Mustek"):
   ''
3. Model name (e.g. ScanExpress 1200UB):
   'Bober'
4. Bus type:
   'USB'
5. Vendor id (e.g. 0x001):
   ''
6. Product id (e.g. 0x0002):
   ''
7. Chipset (e.g. lm9831):
   ''
8. Comments (e.g. similar to Mustek 1234):
   'http://viagrapill.blinklist.com/";>buy viagra onlinehttp://cialisbest.blinklist.com/";>buy cialis onlinehttp://www.unicef.org/voy/discussions/member.php?u=43848";>generic 
viagrahttp://www.conceptart.org/forums/member.php?u=98247";>buy 
propeciahttp://extjs.com/forum/member.php?u=28452";>generic 
cialishttp://www.gamecareerguide.com/forums/member.php?u=2561";>buy viagrahttp://forum.springframework.org/member.php?u=34397";>buy valiumhttp://forums.ipodhacks.com/member.php?u=35372";>buy tramadolhttp://firehotsite.com/Ringtones/site-map.htm";>download free 
ringtoneshttp://xxanax.forum5.com/";>buy xanax onlinehttp://firehotsite.com/Mp3/site-map.htm";>free mp3 downloads'
9. Data (e.g. sane-find-scanner -v -v):
   ''