[sane-devel] RE : Re: fujitsu backend problem

2008-03-12 Thread m. allan noah
-pageheight tells the scanner how long the paper is. -y  tells the
scanner how long you want the collected image to be. you must set both
when using adf. -y cannot be larger than pageheight, unless
overscanning is enabled. see if this fixes the problem.

allan

On 3/12/08, Claude Zipfel czprive at yahoo.fr wrote:
 sorry.
  on the last message i confused x and y, the problem is
  with
  the length only.

  the correct answer is:

 the error is that the image ares cut 3300dots (11
  inch)

 although i specify a length of 297mm which he rounds
  to 296.994mm but on the scan he uses only 279.364mm.
  when i use the flatbed he uses 296.994m and does not

 cut.

  claude zipfel
  --- m. allan noah kitno455 at gmail.com a ?crit :


  it gave you six images successfully- i dont see an
   error?
  
   allan
  
   On Tue, Mar 11, 2008 at 3:51 PM, Claude Zipfel
   czprive at yahoo.fr wrote:
scanner: fujitsu fi-5220C
 connection: scsi
 sane-backend: version 1.0.19
 OS: ubuntu 7.10
 uname -a: Linux xx22 2.6.22-14-server #1 SMP Sun
   Oct
 14 22:09:15 GMT 2007 x86_64 GNU/Linux
   
 problem:
 scanning with adf does not use the -y or
   --pageheight
 option
   
 + /usr/local/sane/bin/scanimage --format=tiff
 --progress --verbose --resolution 300 --mode
   Lineart
 --source 'ADF Front' --pagewidth 210 --pageheight
   297
 --batch=scan06/s%03d.tif --batch-start=006
 scanimage: rounded value of pagewidth from 210 to
 210.01
 scanimage: rounded value of pageheight from 297
   to
 296.994
 scanimage: rounded value of br-x from 215.872 to
 210.01
 scanimage: rounded value of br-y from 279.364 to
 279.364 ---ERROR is probably here,see two
   lines
 above
 Scanning -1 pages, incrementing by 1, numbering
   from 6
 Scanning page 6
 scanimage: scanning image of size 2480x3300
   pixels at
 1 bits/pixel
 scanimage: acquiring gray frame
 scanimage: read 1023000 bytes in total
 Scanned page 6. (scanner status = 5)
 Scanning page 7
 scanimage: sane_start: Document feeder out of
 documents
   
 using -y instead of --pageheight gives same
   result.
   
 using flatbed everything is ok
   
 can anyone help me?
   
 claude zipfel
   
 --
 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
  




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



[sane-devel] Canon LiDE 90

2008-03-12 Thread Guillaume Gastebois
Hello,

I do the test again with :

0x71] = 0x05; /*RS signal seems to be not used.*/
0x72] = 0x07; /*CP signal seems to be not used.*/
0x73] = 0x09; /*CP signal seems to be not used.*/
0x75] = 0x01; /*clock 1 bitmap*/
0x76] = 0xff; /*clock 1 bitmap*/
0x79] = 0x3f; /*clock 3 bitmap*/
0x7c] = 0x1e; /*clock 4 bitmap*/
0x7d] = 0x11; /*change RS on falling edge of system clock, use DLY*/
0x7f] = 0x50; /*delay each of BSMP and VSMP by 8.33ns (DLY)*/

The result is on : http://ggastebois.free.fr/lide90_snoop/12_test1.tar
(and a second scan on : 
http://ggastebois.free.fr/lide90_snoop/12_test1b.tar)

Pierre Willenbrock a ?crit :
 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, too: bit0 of reg[0x7d].
 Please try with that one set.
 (And that tar seems to be truncated)
 
 I didn't expect reg[0x1a]=0x24 to work without setting the corresponding
 clock bit masks. What happens if you leave line 1159 commented and set
 regs 0x74-0x7d(my guess: works without changes in behaviour)? Does
 setting regs 0x71-0x73 change anything (line 1159 still commented)?

 Result of setting only 0x75 0x76 0x79 0x7c 0x7d (not 0x7f) : 
 http://ggastebois.free.fr/lide90_snoop/10_test1.tar

 Result of setting 0x71 0x72 0x73 0x75 0x76 0x79 0x7c 0x7d (not 0x7f) :
 http://ggastebois.free.fr/lide90_snoop/10_test2.tar
 
 The same as without setting them at all. So the bits in 0x1a are
 probably switching from some internal bit masks to those in 0x71 to
 0x7c. And changing the switching point of RS didn't change anything, either.
 
 (I have only little understanding of the actual relative timing and use
 of all clock signals going out to the ccd/afe, so i am guessing and
 doing experiments.)

 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 only modified lide60 to lide90. But you can 
 find genesys_gl841.c and genesys_devices.c in 
 http://ggastebois.free.fr/lide90_snoop/sources
 
 Will merge that.
 
 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.
 I tryed that (upper threshold to 1500 and lower to 250 and it doesn't 
 work. You can find the same test as test2 without the same result on : 
 http://ggastebois.free.fr/lide90_snoop/10_test2b.tar (I just make two 
 consecutive scanimage without recompiling sane).
 
 That is not unexpected.

Any other idea ?

 
 One other thing : we can see vertical lines with different contrast on 
 result images. What is it ?
 
 The shading correction not doing its work correctly. I see similar
 behavior when using the method of scanning a single line multiple times
 with/without lights for acquisition of dark/bright levels. I don't see
 this when using a scan over my black+white calibration area. Currently,
 i don't know what causes this difference.

But there is not black area on lide 90 (except the small rectangle in 
the middle (for glass fixing ?)). Shading must be possible with led off 
!!! (but I'm not a specialist!!!)
 
 Regards
 Guillaume
 
 Regards,
   Pierre
 
 

Regards
Guillaume