[sane-devel] Fwd: LIDE 60. configure scanner

[Ben Green]

Begin forwarded message:

> From: Ben Green <greenb1 at mac.com>
> Date: 19 March 2011 12:53:43 GMT
> To: "m. allan noah" <kitno455 at gmail.com>
> Cc: sane-devel at lists.alioth.debian.org
> Subject: Re: [sane-devel] LIDE 60. configure scanner
>
> Hi Allan,
>
> I'm still hammering away at this scanner. I think I'm getting  
> somewhere, however I am afraid I have not killed off that  
> calibration completely yet.
> Basically, the scanner is still going through some initial short  
> test sweeps to set the light levels. This might not be such a  
> problem, however the scanner now has its light disabled and will  
> eventually be covered and sealed in darkness with the only open area  
> being a 5" square in the middle of the scanning plate.
>
> At the moment if I cover the calibration area when scanning, I get  
> the following message..
>
> scanimage > foo.png
> [genesys_gl841] **********************************************
> [genesys_gl841] **********************************************
> [genesys_gl841] ****                                      ****
> [genesys_gl841] ****  Extremely low Brightness detected.  ****
> [genesys_gl841] ****  Check the scanning head is          ****
> [genesys_gl841] ****  unlocked and moving.                ****
> [genesys_gl841] ****                                      ****
> [genesys_gl841] **********************************************
> [genesys_gl841] **********************************************
> scanimage: sane_start: Document feeder jammed
> greenb1:~ greenb1$
>
> Which stops the scan all together, so that's one bit of calibration  
> I need to override. I can still scan successfully with the cover off  
> (some ambient light hits the scan head initially).
>
>  But also in the debug info, I can still see quite a bit of  
> calibrating and shading going on. I can now see "[genesys]  
> Calibration: Cannot open /Users/greenb1/.sane/canon-lide-60.cal"  so  
> perhaps that's a good start?  I'm hoping that you might be able to  
> see whether our _GENESYS_FLAG_NO_CALIBRATION edits in the backend  
> were successful?, or did I screw up the compiling part?
>
> If the GENESYS_FLAG_NO_CALIBRATION did work, then it looks like I  
> need to dig further to remove these calibration steps. But perhaps  
> it's just not compiled properly or I am still using the old backend  
> somehow.
>
> I have included the debug info from a normal (open top) scan as well  
> as the error (document jam) scan with the cover over the calibration  
> area.
>
> Any Ideas?
>
> also - just so I can get a handle on what the scanner is doing, I  
> assume the slope tables are something about setting the motor speed  
> to match the sampling rate. Is this correct? - is it a problem that  
> I can see
>
> "
> [genesys] sanei_genesys_generate_slope_table: target slope: vstart:  
> 3500, vend: 1300, steps: 60, g: 0.8
> [genesys] Can not reach target speed(1300) in 1 steps.
> [genesys] Expect image to be distorted. Ignore this if only feeding."
>
>
>
> Many Thanks for your advice,
>
> best
>
> Ben
>
large att removed.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110319/1e883859/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sane scan with black cover.rtf
Type: text/rtf
Size: 66210 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110319/1e883859/attachment-0001.bin>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110319/1e883859/attachment-0003.htm>